Related
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
I didn't know how else to title this thread, so I'm hoping this makes sense.
Awhile ago I flashed the CM6 ROM to my Hero. I haven't added much to it, nor adjusted any of the settings. However, when my phone is not plugged in and getting charged, when I hit the End Call or Menu button to bring it from sleep mode, it takes it almost 2 seconds before the lockscreen appears.
I know that a stock Hero will awake from sleep mode almost instantly. And, when I had a previous 1.5 ROM flashed, it took the phone about maybe 1.2 seconds to awake. Is this normal or is there something that I'm missing that is causing this lag? I haven't really installed any misc apps, and I only removed some "bloatware" from the phone (safely, and ones that don't cause FCs).
Any help or suggestions is appreciated.
I know that overclocking a rom adds lag to waking up the lock screen. Did you flash a overclocked kernel or have you had this issue since flashing this rom?
I believe, when I flashed this new ROM, I reverted back to a normal clocking speed. I used to have an OC kernel of 710, but could've sworn I've gotten it back to stock.
Is there a way to get it back to stock speed, if I didn't revert it back, tho?
Bump.
Is there a way to revert the kernel back to stock?
Option
1. If you have OC kernel install, either use setCPU or Overclock widget to set your min and max.
2. If you running ASOP rom, I'm not sure ASOP ROM comes with stock Kernel or OC Kernel. If it come with stock you may just flash the ROM again w/o wiping data, might have to wipe dalvik cache and it should revert back to stock kernel. If it comes with OC kernel, then option 1 would be best.
my .2 cent hope it helps.
Unfortunately, OverClock Widget didn't do anything to fix the problem. :/ And, if it can't fix it, I don't think that paying for SetCPU will fix it either.
Is there a way I can download the stock kernel?
You cab download setcpu for free here on xda or from their website
I forgot what file it is that changes the CPU speed, but I would look into modifying that file. I also have this problem with cm6 8/17 nightly, but did not have the problem with the early test releases
Sent from my HERO200 using XDA App
Thanks a lot, I'm giving it a shot now. I do have a question, tho: when I ran SetCPU, it said that root access was not detected. Is there a trick I have to do with the phone to have SetCPU recognize the phone? I have done some searching, but haven't found much. I tried checking on SuperUser, but it doesn't list SetCPU in it. Plus, when I tap on "Log", it crashes.
Is my phone messed up or something?
First off, I have an autonootered 1.0.1 NC which has been upgraded using Decad3nce's Nook Color V1.1.0_r2.
My question is which overclocking option should I try?
I'm using the Eclair 1.1 GHz kernel. It's SUPER snappy, and flashed fine! Make sure you download the one for Eclaire, not Froyo!
http://forum.xda-developers.com/showthread.php?t=925451
Agreed. The 1.1 GHz kernel has been rock solid for me for several days now. If you use it with SetCPU, you can help retain as much battery life as possible, since the 1.1 GHz kernel uses a little more power.
I use:
MAX 1100 MHz
Min 800 MHz
OnDemand
Then set a custom profile for "screen off"
Max 600 MHz
Min 300 MHz
OnDemand
This means when you're using the device, the system will automatically select a speed between 800 MHz and 1100 MHz depending on what the system demands. Then it'll throttle down to either 300 or 600 MHz when the screen is off to conserve power.
I saw a very small difference between the stock kernel and this one in terms of battery life. I still get days of moderate use out of my NC between charges.
Sent from my LogicPD Zoom2 using XDA App
Maybe this is an obvious question: If I flash Decad3nce's Nook Color V1.1.0_r2 rom, but then flash the 1.1Ghz overclocking kernel, doesn't that effectively 'overwrite' the newer kernel from B&N's 1.1 update that Decad3nce incorprated into his r2 Rom?
I'm using the 1.1Ghz one for Eclair. Love it... Running with no issues.
For you other guys... did you set a profile for "Charging" in Set CPU? And if so... what parameters are you guys running? 1100max/600min?
Yes it does. The only way to OC your NC is to install a custom kernel. The majority of the ROM is left alone.
This is what I did:
- Installed CWR from the maket and installed it.
- Flashed 1.1.0_r2 (changed the name to update.zip and did it through CWR)
- Flashed eclair 1.1Ghz (changed the name to update.zip and did it through CWR)
One random reboot. Since then flawless. Over 48 hours.
Question:
I did just as you did, but I installed quadrant and I'm only getting a score of 962. I never had the option in setCPU for turning it up higher than 800 in any profile. Does that indicate that I did something wrong? It's running very stable, but not the screaming speed that others seem to be getting.
jblues1969 said:
Question:
I did just as you did, but I installed quadrant and I'm only getting a score of 962. I never had the option in setCPU for turning it up higher than 800 in any profile. Does that indicate that I did something wrong? It's running very stable, but not the screaming speed that others seem to be getting.
Click to expand...
Click to collapse
Make sure that SetCPU has root access and you should be able to make the changes.
Just checked and SetCPU does have root. Still won't let me go past 800.
Sent from my Nook Color using XDA App
Flashed with the 1.1 and all seems good.
Jblues, sounds like your overclock kernel wasn't installed properly. Did you use ClockworkMod Recovery and ROM Manager to install the 1.1 GHz kernel?
Sent from my LogicPD Zoom2 using XDA App
That's what I was afraid of. OK, I'll work up the courage to try again.
I was using these instructions. Could you take a look and let me know if there's a glaring error in them that could result in failure of the 1.1GhZ kernel install?
jblues1969 said:
That's what I was afraid of. OK, I'll work up the courage to try again.
I was using these instructions. Could you take a look and let me know if there's a glaring error in them that could result in failure of the 1.1GhZ kernel install?
Click to expand...
Click to collapse
Sorry, I didn't see a link to which instructions you were using. Really easy:
1. Put the 1.1 GHz kernel still in zip format on the root of your SD Card.
2. Go to ROM Manager and select "Install ROM from SD Card"
3. Select the zip file you just put on your SD Card
4. DO NOT choose to Wipe Data and Cache. Backing up existing ROM is up to you. Click OK.
5. You'll reboot into ClockworkMod Recovery and the new kernel will install. Should only take a few seconds to install. Then, you'll automatically reboot.
6. Check SetCPU and see if you can now choose 1100 MHz as a speed.
Hi,
I had first version of 1,1. just re flashed with r2 and then flashed 1.1 ghz kernal in the same step.
It works like a charm. Just had to re-map my volume keys like I prefer, and was good to go!
Thank you
My set-up...
I also want to put in a good word for the Eclair 1.1GHZ kernel. I'm running an auto-nootered 1.01 NC upgraded to Decad3nce's v1.10_r1. So far so good with the 1.1GHZ kernel. My Quadrant scores range between 1125 and 1180.
Bonus Tip: Like some other users, while attempting to flash the overclocked kernel I got stuck during the 'clear dalvik cache' step in CWR. Upon clearing the dalvik cache, I would hit the power button but it was frozen and would not send me back to the main recovery menu. As it turned out, I needed to wait ~30 second after clearing the dalvik cache before pressing any buttons. As instructed by another user, I tried this trick on my next attempt to flash the kernel and it worked flawlessly.
Absolutely. the 1.1 kernel works beautifulyy, and the difference is incredible. setcpu works perfectly as well. Some minor install notes
1. I had to reinstall the ADHOC fix wpa supplicant. (20 seconds in root explorer)
2. Like almost everybody, I had to switch on uSB debugging again
3. Somehow zeam grabbed hold of being the defualt launcher and i had to resent softkeys to the default lanucher using switch lancher.
All told maybe a minute of tweaking afetr the final install. it is just gorgeous. There some nice user friendsly instructions, and faster mirrored downloads available here.
http://community.saugususd.org/jklein/weblog/1350.html
Yep, those are the instructions I was using (I don't have enough posts to be able to post links, I guess.) I'll do it again tonight.
Got it done this time. New quadrant score is 1214!!! You guys rock. Thanks!
Glad it worked!
Hey all, I'm running CM7 7.1 rc-1... I just installed dalingrin's latest oc kernel... And it killed my wifi.. It's really bugging me. My nc is currently oc'd @ 1200.. With a min speed of 600. Is the kernel killing my wifi? Or is it the overclocking?
Thanks in advance.
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Olivier! said:
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Click to expand...
Click to collapse
hmm.. interesting. I'll give that a try and tell you what happens.
update:
I tried to install the stock firmware by deleting cwm, repartitioning boot to stock (after installing stock 1.1)... now it just loops on the "nook color by bn" screen. any suggestions?
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
patruns said:
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Click to expand...
Click to collapse
brilliant! that worked wonderfully. for future reference, the latest version of CWR seemed to do the trick. thanks!
Hi,
Very recently i bought a Galaxy tab 8.9 wifi only (P7310), and decided to flash the 'Overcome 8.9 Series v2.3.1' ROM by alterbridge86.
Obtaining root en flashing CWM went very smooth. After full wipe + dalvik wipe I flashed the overcome rom. Still everything was fine and the rom felt very smooth. However, when I woke the tab from standby the first time, my screen was glitching so bad I had to re-boot the tab. After a reboot everything was fine again, at least until i tried to wake it up again. The same glitching occurred..
The strange thing is, during the glitching I could still open apps and everything, so it doesn't look like sleep of death issues i had with custom roms on my Hannspad.
I already tried to flash the rom again and again but every time the same issues. Someone suggested to increase the min. frequency of the cpu to 312Mhz, but this also didn't do the trick..
Right now i'm running the Galaxiansoup ICS rom without any issues, but i would really like to use the camera (for video skype) which doesn't work right now with ICS.
Does this problem sound familiar to anyone? I already searched the dev topic, but couldn't find a solution. Hope you guys can help me out!! Thnx
I added a short video to show what I mean with the glitches, hope you guys can help me out here!
I dont have any issues when use it..p7300
Try to download the file again.. Maybe a bad download make your file corrupt.
Already tried to re download (checksum verified), but unfortunately still the same issue...
Hi Ruurd V.
What Kernel do you use ?
Is it this one ?
http://forum.xda-developers.com/showthread.php?t=1344330
And did you check step
4. Install SetCPU and use to set governor to "interactive" and desired OC frequency (recommend 1.4 to start). The default governor has been set to On Demand on purpose even though it is not the recommended governor to use in SetCPU. Setting the recommended interactive governor will help SetCPU trigger the instructions to sysfs causing it to take hold. Sometimes it is finicky and a reboot can help once you have the interactive governor set with your desired frequency.
Until now I used the kernel that came with the rom. I was under the impression that the rom included the latest kernel.
I tried the kernel from the thread you posted, however the v2d version didn't work for me (no lock screen, no play store acces, home button did not work).
I just flashed the v2c version and that one works fine so far! Haven't tried messing with the cpu though, but for now I will continue using this one! Thanks for the help!
I too had some screen issues with that ROM's kernel until I installed motley's v2d kernel, so yeah, it's the default kernel.