Related
I recently installed Cyanogen on the girlfriends Wildfire, I am using the 'stock' kernel with the ROM, however from time to time she was getting random restarts and the screen was turning a yellowish green colour, only a reboot would solve the issue. I moved SetCPU back to stock clocks (It was only at ~610Mhz overclock) however the problem persists.
I've literally just changed to HCDR.Kernel v4.1 and on first reboot I've gotten the yellow screen. Does anyone know what could be causing this issue? The phone was absolutely fine before installing Cyanogen, and I don't really want to keep messing about with her phone flashing from ROM to ROM, it was hard enough to convince her that an AOSP ROM would be better than stock!
I've had a quick search and I can only see one instance of this happening and it's a two post thread , which is of no help to me, any light anyone could shed on the issue would be greatly appreciated.
Do not set your cpu min. Value too low. Keep it above 250mhz
Sent from my HTC Wildfire using XDA App
Profiler08 said:
Do not set your cpu min. Value too low. Keep it above 250mhz
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
As on all of my Android phones I keep it at 250Mhz for the lowest value.
The nexus s reboots many times a day and its battery performance is also decreased. Can any body help me in this regards.
If that happened to me I would return it for a new one.
Sent from my Nexus S using XDA App
Knock on wood, but I think that issue could be caused by not using a stable kernel. Mines been restarting for the longest and since I switched to Netarchy older more stable kernel so far no reboots. If I do experience any reboots I will be sure to let you know. I just made the switch last night to the older kernel which Netarchy claim is more stable than the newer one. I'm on CFS, not BFS.
Sent from my Nexus S using XDA Premium App
I have the (mis)fortune to be using my GNS in Singapore. I have noticed reboots when making calls outdoors when I am sweating a lot and the screen gets wet wet wet. Dry it off with a clean cloth (toilet paper is too scratchy LOL) and it is fine. Get the screen too wet and the device reboots randomly.... A strange problem but very repeatable.....
Just wondering if you had random reboot issue and then it stopped after flashing cm7? Thanks
I am and it's getting really annoying
mithoss76 said:
I am and it's getting really annoying
Click to expand...
Click to collapse
Have you flashed a different kernel? Or are you over clocked or undervolted? I was getting randome reboots because I was undervolting incorrectly. I am now running Faux's latest .2.0 1.3ghz kernel and have had no reboots.
I get them on rare occasions .... but I'm experimenting with UV ... not frequent enough for me to pinpoint an issue or to be annoyed by it. Last time occurred after after doing a system setting.
I dont get random reboots anymore, cm7 and last faux kernel at stock 1.0ghz fixed it.
I've been on CM7 for a week and no reboots.
been running it for 2 weeks or so. Had one minor glitch yesterday with my device when I locked the screen- she wouldnt wake back up and had to battery pull. Other than that, no issues. I am running Faux's 0.2.0 Stock CM kernel as well.
I had one reboot on my Atrix since running CM7. Compare that with several a week on the stock Motorola software. Using whatever kernel shipped with CM7. Overall, a great improvement!
Sent from my MB860 using xda premium
Reboot here this morning. Actually had to do a battery pull. Faux 2.0 1.3 no undervolt
Sent from my alien
not really random but does anyone else get
a reboot if you leave the torch on to long? It may be a known issue I haven't looked but it seems to happen to me every time..
Sent from my MB860 using XDA App
It could be due to something not getting flashed right. Depending on what rom/fruitcake/etc is flashed, not all images are replaced. That's by design, because the good ol' fashioned SBF flashes EVERYTHING, which you really don't always need, and can be potentially dangerous. Assuming something got corrupted somewhere, or there's an older version of part "x" that doesn't like to play with the never version of part "y", that could cause a crash. You might want to look at a safe way to get a clean wipe, and then redoing CM7. I'm not suggesting SBFs or anything. But I'd check out samcripps' Fruit Cakes @ http://forum.xda-developers.com/showthread.php?t=1163009 though.
So I've had this problem for some time maybe a couple of weeks.
The problem is that I sometimes cannot wake up my device after setting it down for sometime. For example if I go to sleep get up the next morning and then screen will not turn on. I have to hold power button down for multiple seconds and press it multiple times. Also one recent occurrence of this there was massive battery use. See attached photo.
If anyone knows why this is occurring or knows any remedies that would be appreciated.
Using PA 2.54
Franco Kernel
I can provide more information if needed. Just ask.
Thanks
Sent from my Nexus 7 using xda app-developers app
I was having serious issues with my 16gb. Very hard to turn on, sometimes hold power for 10 seconds, sometimes 30, sometimes 5.. all over the place. And it only started after I believe the 4.2 update.
Also, it was draining battery while off. Charge it overnight, leave it off the entire time, come back 8 hours later. Turn it on and only have 50% battery.
Sometimes the charging animation would lock up while off as well. And if the device was turned off, and you plug it in to charge, it turns on. It shouldn't.
I think I've narrowed it down to the bootloader. My bootloader was at 4.13, and Flashing the 4.2.1 and 4.1.2 factory images didn't help.
Last night I finally fixed it. I ran the 4.1.1 factory image. Which put the 3.34 bootloader back in place. This wipes the device. So I flashed the recovery back and then reflashed Paranoid Android 2.99B6. All is good now, it turns on like it should, doesnt come on when plugged in, etc.
Meanwhile a new 32gb I have I can flash the 4.2.1 factory image, and I have no issues with that one.
Which bootloader are you on?
Hmm. That seems to be the exact same issue I have!
I just checked my bootloader and I have 3.41. But I never went up to 4.2. I stayed at 4.1.2 with PA 2.54.
Hmm. Maybe I'll try what you tried!
Sent from my Nexus 7 using xda app-developers app
kazemitsui said:
Hmm. That seems to be the exact same issue I have!
I just checked my bootloader and I have 3.41. But I never went up to 4.2. I stayed at 4.1.2 with PA 2.54.
Hmm. Maybe I'll try what you tried!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You can flash the 4.1.3 bootloader from JB 4.2 and use it with 4.1.2. I am, and it works perfectly and I never have a problem booting or bringing it out of sleep mode.
I think it was just your Franco kernel. Kernels are typically the cause.
I'm running PAb6 and no problems.
Sent from my Nexus 7 using XDA Premium HD app
player911 said:
I think it was just your Franco kernel. Kernels are typically the cause.
I'm running PAb6 and no problems.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi, which kernel are you using? I just changed my bootloader back to 3.34 and my kernel to motley. See if that helps.
Thanks for the tips.
Sent from my Nexus 7 using xda app-developers app
----------------------------------------------------------------------------------
seems after flashing a new kernel to motley the problem still occurs...
I think ill factory reset. reinstall PA gapps and everything... see what happens.
anyone else have any insights into this... flashing a new kernel and it still occurs
Sometimes you have to set you're minimum cpu frequency above 200 using one of the various cpu or kernel tuners
Sent from my HTC One X using xda app-developers app
Just had this similar problem. I drained the battery to about 11% on wednesday night, so i shut it off and charged it to 100% on that very same night. Turned it on on friday night (It should have been turned OFF all this while) and it wont start. After the help of the AC charger, it came back on and found out the batt was at 0%. Which should not be the case even if the tablet was accidentally switched on because theres no way it can drain from 100% to 0% in just 2 days. And everytime i leave it plugged into AC it suddenly turns on and shuts down due to low power. Am using TWN ROM V1 (Android 4.2.1) with M-Kernel A17 kernel if that has anything to do with it.
So I think I have it figured out that if I set my wife policy to keep awake always no problems, but if it is set to keep awake only during charging, I will have problems
I will try it out on a higher cpu setting with semi awake
Sent from my Nexus 7 using xda app-developers app
Just wiped the device and flashed CleanROM 3.0 on it and NOTHING else (No extra scripts, custom kernels, radios..etc) and it seems to have been stabilized. Although the battery drained pretty quick while i was using it last night, but I was installing apps and setting up stuff on the nexus so its not a very accurate benchmark. Will continue to monitor.
Hmm, I see. Well that's great that you solved it
It seems after switching my minimum cpu to 200. It still froze when I was trying to wake it up this morning
Maybe a full wipe is needed...
Sent from my Nexus 7 using xda app-developers app
Yes you should have done a full wipe like I did. All still seems to be good on my side. Looks like for my case it was M-Kernel a17 causing the problem. I doubt such a thing would happen due to a faulty bootloader.
So I did a full wipe of my tablet and instead installed PA 2.99 b6, flashed correct gapps, then flashed the beats audio v3b2 and the same thing occurs.
im using franco kernel v30 no OC just gpu oc to 446.
my tab if i leave it unplugged and set wifi policy to keep wifi on during sleep only when plugged in I get this problem that I cannot fix... which is the tablet freezes or something and i cannot turn the screen back on until i hold the power button, Then turn it back on. Also on a side note for the first time this morning, the back of my tab was hot, which never occurred when i was on PA 2.54
Any insights on this issue anyone?
full wipe and flash a ROM that comes with the stock kernel. I did that with CleanROM 3.0 and its still working fine to this day. Will probably try flashing franco or M-kernel again when I have the time. But for now it seems that a custom kernel might be the issue here.
cr0wnest said:
full wipe and flash a ROM that comes with the stock kernel. I did that with CleanROM 3.0 and its still working fine to this day. Will probably try flashing franco or M-kernel again when I have the time. But for now it seems that a custom kernel might be the issue here.
Click to expand...
Click to collapse
Thanks for all your replies. It seems to have fixed it after updating my ROM im really not sure what happened with PA 2.54 but with PA 2.99b6/8 it has not freezed at all, but then again the min cpu freq i have is at 340 heh...
Hello,
from yesterday are available version version cm 10.1 monthly.
here limks:
http://get.cm/?device=crespo&type=snapshot
http://get.cm/?device=crespo4g&type=snapshot
*Delete
Sent from my Baked Nexus S using Tapatalk 2
ops...where is it?
*Delete
Sent from my Baked Nexus S using Tapatalk 2
Are different release!!!
monthly are between nightly and stable version!
ziociccio said:
Are different release!!!
monthly are between nightly and stable version!
Click to expand...
Click to collapse
Oops. I read nightly in your title.
Sent from my Baked Nexus S using Tapatalk 2
I couldn't click anything in the dock when i installed this yesterday? Was a clean install.
Edit: Just had to update Nova and it's fine.
R: [ROM][4.2.1] Official Cm10.1 monthly for Nexus S & Nexus S 4G
any feedback?
i flashed this rom over xylon rom,based on cm10.1
no issue or problem.
I'm on this ROM from yesterday (full wipe), with stock CM kernel.. no issues so far.. Only one Trebuchet FC, but probably was my fault..
BatteryLife seems normal, no drain etc..
Everything work good, and smooth enough for a 4.2 rom.. but too many animation ...
I give you some feedback using this ROM as my daily driver..
Put the M release on last night. Using marmite 7.2.3. Works well, smooth and battery life seems ok.
Installed it straight over the top of the CM 10.1 nightly i was on.
Will try marmite 7.3 sometime soon, but had a few issues with that for battery life on the recent nightlies.
Many thanks for this ROM CM people.
Just as an aside, i had a horrible time with the phone over the last few days. Not sur what happened but it wouldn't boot past the bootloader, and somehow i lost the recovery (TWRP). Had to go back to the factory 4.1 version and rebuild the lot from there. Then it all happened again.
Finally worked out why, apart from me being an idiot. I had used Titanium Backup to load apps and settings back after an update, and they were backups of 4.2 apps, not 4.1. So, rebuilt from scratch on 4.1, got a nandroid backup of that. then built from scratch on a CM10.1 nightly from December that i knew was good and reinstalled all apps and settings manually. Much cursing and gnashing of teeth.
battery drain is very very slow.
I lost only 2% after 9h in stand-by mode. with others roms ithe minimun was 6%.
Keep in mind that this is the first 4.2 ROM i've installed:
I'm facing the AndroidOS 50% battery drain sometimes... Yesterday this value was 45-50%; today, after a full charge and a reboot, the value is 7-10% (Stock CM Kernel)..
I've noticed that even with other ROMs and Kernels on 4.1.. probably it is related to apps installation and first launch.. so not a real issues...
Two minor "aesthetic-personal-issues":
- "clear all recent apps" is in the top-right corner, totally invisible when more than 3 apps are running, hope CM team will set it on the top left or leave the decision to user...
- sometimes is hard to know if some "toggle" in user bar are ON, OFF or inactive (like WiFi On but not connected, Gps etc).. probably this needs some work2do to clarify the behaviour of this tiles... or maybe it is just personal taste...
And I hope that in future they add the option to set 4 or 5 tiles per rows in user bar...
Battery life is not different from CM10 or other 4.1 ROMs...
I just had a literal nightmare with this rom. While I was just swiping through the desktop with the phone charging suddenly everything started to black out. What was scary was how gradual it was happening i almost thought my phone is going to explode now or something lol. Didn't help the fact that I was using the phone at night in pitch darkness.
Took out the battery immediately and rebooted just fine for now. I updated from cm 10 stable without wipe as i was prompted for an ota update.
Sent from my Nexus S using xda app-developers app
Gambler_3 said:
.....While I was just swiping through the desktop with the phone charging suddenly everything started to black out...
Click to expand...
Click to collapse
same happened to me, but without the charger and stock CM kernel... Now I'm testing Marmite 7.3 and everything work good...
I think that this is related to some background operation that slow down the device..