i have a sclc dinc that i cant get to clock past 998mhz. i have tried alot of diff kernals and roms to c if that would help. on my old dinc i never had a problem finding one that would work.. im currently running the new gingerbread rom and i went to c if i could go over the 998 and it bootlooped on me.. so couldnt get it on this rom either.. ive tried KK, Hydra, and a few others and nothing will get over 998. anyone else had this issue or have a solution? thanks
All cpus behave differently and the only guarantee is that it should be stable at 998. As there's no defect, there is unfortunately no solution. As crappy as it sounds, your phone is operating within its design parameters.
It is also possible that the ROM you're using isn't compatible with those kernals enough to allow it to overclock without bootlooping. Try it with Skyraider, Myn's, or Virtuous (just to name 3 I've used and overclocked) to see if you get the same results.
I have tried different roms with different kernals. Cm6, SR, etc... and still have same results with trying different kernals. I never had a prob with my old dinc but seems to b every thing I try on this one
Related
Just got my Evo replaced. I had an early 002 version that OC'd to 1228 24/7, ran great, only 3 point touch. I could run each and every kernel released without problems. My USB Charging jack busted and phone wouldn't charge so sprint replaced it. Rev 003 of course. My problem is that every custom kernel i try , i get re-boots, even at stock clocks. Well not full reboots, like a sense reboot. I can use set CPU with all my same profiles, set at 998 max with the stock kernels, and have absolutely no problems. Same CPU settings, or even removing set cpu all together i get the reboots with Kings and Netarchies kernels. I haven't tried them all, but a lot of them. No pattern to the reboots, just randomly happens. Any ideas? Has anybody heard of others with this problem? I can OC to 1192 and it doesn't increase the frequency of the reboots. It doesn't feel like the same stability issues i've experienced with previous high Overclocks. My 002 felt bulletproof when it came to tweaking. i hate that i broke it. This 003 feels fragile
I don't care.
Flash cm6 with snap and never need overclock.
beastmods said:
Flash cm6 with snap and never need overclock.
Click to expand...
Click to collapse
It happens when not overclocked. at stock settings with custom kernel. I know its a lot of rambling, but i think it is all pertinent information. But i have not tried CM6 with the new EVO. Didnt really care for it, but willing to try it for diagnostic purposes. Maybe it'll win me over this time.
[email protected] said:
I don't care.
Click to expand...
Click to collapse
Awesome, I dont care that you dont care.
Bump. Bump.
Anybody? This is why i originally posted in dev section. Kernel pros are not hanging around in Q&A.....
Bumpity 10char
i don't use sense based roms or kernels, but i assume this may hold true for them as well.
I've had a couple times where i flashed a kernel that afterwards prevented flashing other kernels. i was unable to successfully flash any kernel (even known good versions...ie: the same .zip i had used in the past).
once i did a full wipe and that fixed it.
the other time i restored a nandroid and after that i could flash as expected.
good luck.
DraginMagik said:
i don't use sense based roms or kernels, but i assume this may hold true for them as well.
I've had a couple times where i flashed a kernel that afterwards prevented flashing other kernels. i was unable to successfully flash any kernel (even known good versions...ie: the same .zip i had used in the past).
once i did a full wipe and that fixed it.
the other time i restored a nandroid and after that i could flash as expected.
good luck.
Click to expand...
Click to collapse
Thanks for input. I've actually done all of that multiple times Even complete un root re-root. Since i couldnt use any custom kernel at all, my 2 week old evo suddenly had a bad usb port so sad. I got my new one today and i've been at 1267 for the past 2 hours.. Awesome!
Ya i have frequent and random reboots running Ava v9 with kings 10 cfs. Plz help. Any fix?
i was running Froyo on my epic for the longest time and i used odin to go back to 2.1 just recently because i missed how smooth it was. i noticed that no matter what i do, my notification light won't work anymore. even when the screens off. im running stock DI18 right now (unrooted) and i have no idea why it hasnt worked. any ideas? they would be greatly appreciated.
sniperwitagun said:
i was running Froyo on my epic for the longest time and i used odin to go back to 2.1 just recently because i missed how smooth it was. i noticed that no matter what i do, my notification light won't work anymore. even when the screens off. im running stock DI18 right now (unrooted) and i have no idea why it hasnt worked. any ideas? they would be greatly appreciated.
Click to expand...
Click to collapse
Weird, why not run Bonsai, midNIGHT or Viper 2.2 ROMs?
I have been using midNight for about 3 months (since I got my epic for xmas) and it is VERY fast with no lagginess what so ever
Mine didn't work on 2.1 either.
Sent from my Evo Killer!!!
does it work if you odin back to dk28?
try it first and see what happens
musclehead84 said:
Mine didn't work on 2.1 either.
Sent from my Evo Killer!!!
Click to expand...
Click to collapse
Mine has worked on 2.1 stock, 2.1 epic experience, 2.1 noobnls rom and other 2.1 roms ive tried as well as now running bonsai..
i was running bonsai. i switch roms every day until i find one i like. ive run almost all of the dk28 roms at this point. i was running viper with the gingerbread theme with ext4 and i really liked that setup. but the notification led let me stealthily text at work or school so really miss it. i re-rooted my epic and put the latest epic experience for eclair back on my phone and ran phoenix kernel but for some reason the newer builds of that for me make my touchscreen unresponsive whenever it feels like it, so i went back to fluff kernel. however, the notification light still doesnt work. ive tried wiping the phone, using odin to go back to stock, ive tried third party notification led programs, tried playing with the stock settings, installing handcent again and playing with those led settings, and just about everything else i can think of. im thinking there must be something i can run in the terminal emu to make it reset or something. im a pretty avid linux user, but im no expert when it comes to android so this is something slightly out of my expertize. but from googling and browsing xda somewhat, its a growing problem. most people dont care enough to fix it though and like 75% of xda members with epics moved to froyo anyway.
Every time I root my phone install custom ROMS or Kernels it will always Crash or reboot it self every time. I have tried unrooting the device several times I also tried Tried very popular ROMs like AOKP & CM and still they end up crashing within a day of use. I don't know what I am doing wrong here... I assumed it was the phone so I called Verizon to send me a replacement one but if anyone knows why this is only happening to me and not all the rest of my friends even Fiance then please let me know....
At the moment I am on stock ROM and Stock Kernel and still rebooting and crashing every time and its rooted so if anyone has any idea please let me know i am about to give me on this Phone....
P.S. If you have recommendations on ROMS or Kernels I can try besides Franco or Trinity that will be great, I also tried them and also the same problem
My gnex has recently started to do this as well. I think its an overheating issue because it'll "crash" when it feels really hot.
Sent from my Galaxy Nexus using xda premium
so i recently got my Note 2, and i love it. i decided to go ahead and start tinkering with it, but i'm having some strange issues. i've searched the forums, and havent found any concrete answers. after i flashed a new rom, all my sensors are out of whack, and i only have intermittant bluetooth connectivity. i also seem to have issues with cell signal strength. if i go down to one bar of LTE, it gets slow as hell.
i've tried several different ROMS. JellyBam, JellyBeer, and i'm currently on Paranoid Android, running SPB 3D shell. none of my sensors are back online, and i miss my auto rotate. should i try a new kernal or new radio? i also seem to have a ton of freezes and force closes when running the Deus Ex theme.
any body have any ideas? i'm almost tempted to go back to bone stock...
thanks for your help guys.
oh, and if it matters, ive been using the team win recovery instead of CWM.
Try the newer Jellybeer or Jellybam, It should fix your sensors and BT
i was using the latest JellyBeer, and they still didnt work, i'll try JellyBam again tonight and see if it helps. i heard someone say something about the Perseus kernel, but that its a touchwiz only kernel. any other ideas?
Why not go completely stock ,that will fix your sensors,then continue on flashing?
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app