How stable is the cm10 18/04 ? I flashed the one before it and it would gave black screens and it would not let me download any music or documents from internet.
Try Chris's CM10 0.05.3, I've been using it for a few days now with no reboots or SODs.
Sent from my NOOK Tablet running CM10 0.05.3
Same with the sgt7 they use same kernel.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
So they are both stable? because i tried sgt7 as I mentioned and it had download problems and I also tried another one Called alien Droid that was cm10 based and it also gave me the same problems
.....btw I did wipe cache and dalvinik cache and wiped.....
Sent from my Nook Tablet using xda app-developers app
I have flashed the last three releases of sgt7 cm10 and am very pleased battery life is exceptional on the 8/10 build and i don't recall any freezing or reboots happening ... now on the 3rd day using it.
..Note using twrp recovery..
Sent from my SPH-L710 using xda app-developers app
kobhomye said:
I have flashed the last three releases of sgt7 cm10 and am very pleased battery life is exceptional on the 8/10 build and i don't recall any freezing or reboots happening ... now on the 3rd day using it.
..Note using twrp recovery..
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I,average about two to three BSODs every other day. When they occur they seem to cluster, so I get a few, stops happening, and everything runs smooth for the next few days. Other than that, this rom has been smooth as silk and stable as can be.
billy8362 said:
Same with the sgt7 they use same kernel.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Kernel is based on cm10 kernel but not the same example 1.2ghz, new i/o schedulers etc
Have you had any trouble downloading anything or is that just me?
Sent from my Nook Tablet using xda app-developers app
Taking the plunge with the sgt7 cm10 2012-10-08 ROM
I just finished installing the 2012-10-08 ROM, and wanted to report my experience so far.
My Nook Tablet was already rooted and running CM7. I have been waiting to make the move to JB once the stability of the various ROMs seemed to be improving, and the recent work seemed promising. Thus, I decided to dive on in.
Here are the steps I took:
1. Downloaded 08/10 ROM, JB gApps, and CWM as referenced in the OP. Moved them over to my SD card.
2. From Rom Manager on the NT, I booted into recovery and flashed the new CWM. Rebooted the tablet.
3. Booted back into recovery again, did a factory reset (format data/ and cache/), then formatted Dalvik cache as well.
4. Flashed the 08/10 ROM.
5. Flashed JB gapps.
6. Rebooted the tablet.
After a short while, the OS booted up. I connected to my local WiFi, and then I configured the tablet with my Google account info, installed necessary apps, etc.
Everything seemed to work very well until the screen automatically turned off after the tablet stood idle for a while. Pressing the N button or power button did not turn the screen back on. I assume that this is the dreaded "Sleep of Death" (SOD) I have heard so much about.
I held down the power button for 10 seconds or so, released it, then held the power button down until the tablet rebooted. I thought that maybe turning WiFi off before it slept might help, so I experimented a bit, and it did seem to work.
I'm home now, and the battery life of the ROM seems very nice so far. I am playing around again with WiFi left on before it sleeps, to see if I can reproduce the same problem, but so far it is waking back up and working just fine.
All in all, it is a very impressive ROM, and I am glad (so far) that I decided to take the plunge!
Bug with 4/10 version
hi,
i also want to report few bugs with version 4/10: before i went to bed, and charged my NT 16G. from the screen, it confirmed that the charging started. but next morning when i checked again, the battery is still at the same level.
this means that it doesnt really charge, even it said the charging was under-way.
i can confirm that the charge cable was properly connected to my NT, so this is a software bug i think.
Besides, it seems i have the SOD problems sometimes. i tried to reboot, but the power button didnt seem to work. finally, i removed the microSD card, and it seemed to help to reboot my NT. another problem???
thanks.
I think I have to revise my endorsement. The 4/10 rom without enhancements is a buttery smooth, very reliable, daily driver. BSODs are rare, wifi dropping rarely happens. The enhancement pack and the 8/10 rom do fix the wifi dropping and imprive battery performance. Unfortunately they also seem to break a fairn number of apps, including com2us, scrabble, and words with friends I also experienced video freezing. on youtube and netflix. Also memory use seemed higher and I had to frequently (4 or 5 x per day) run fix.permissions to prevent force.closings.on apps . That ended up being a deal breaker, I ended up reverting back to the 4/10, the enhancements ended up causing more headaches then they fixed.
Still, the 4/10 is easily the most stable, functional rom currently running on the tablet. Huge thanks to everyone.who worked on this.
Just a quick update on the 2012-10-08 ROM. Last night, I picked up my NT after having it sit for a couple hours, and pressed the "N" button to wake it back up. The screen turned on, and I briefly saw a notification message scroll up top that said something along the lines of, "SD card unexpectedly removed", and then the tablet rebooted.
I saw that someone else had a similar issue on the DEV thread, and just wanted to confirm that I, too, seem to be having the same problem.
c600g said:
Just a quick update on the 2012-10-08 ROM. Last night, I picked up my NT after having it sit for a couple hours, and pressed the "N" button to wake it back up. The screen turned on, and I briefly saw a notification message scroll up top that said something along the lines of, "SD card unexpectedly removed", and then the tablet rebooted.
I saw that someone else had a similar issue on the DEV thread, and just wanted to confirm that I, too, seem to be having the same problem.
Click to expand...
Click to collapse
I've found that manually disabling Wifi before sleeping prevents the sdcard issue. The I have no idea why they seem related but it works here on 04/10 that way.
Sent from my Barnes & Noble Nook Tablet using xda premium
LifeWOutMilk said:
I've found that manually disabling Wifi before sleeping prevents the sdcard issue. The I have no idea why they seem related but it works here on 04/10 that way.
Click to expand...
Click to collapse
Thanks for the confirmation of my suspicion. It seeps that disabling WiFi before sleeping also prevents the SOD issues, so I will just try to remember to do that when I use it.
Related
One minor and a couple of major issues...
- Notification drop-down stops accepting touch input but can still be slid up and down. Reboot fixed
- Battery life is horrible. It's better with wifi set to turn off when the screen turns off, but I'm still losing about 10% per hour. With the stock 2.3.4 ROM I was able to go 16 hours and only drop to 80%. I've read maybe I need to let the battery discharge completely so that it can calibrate? I'll try that today.
- Cell connectivity is sketchy now. I've had problems making calls. Full bars, then it tries to connect and the bars drop to 0 temporarily, then come back up and the call fails. My SMS send success rate is about 75%, sometimes down to 25%. I've had multiple text messages fail to send and some texts I end up receiving minutes and sometimes hours later. This is a huge problem.
Overall I think this is a great leap forward and the phone is very fast now, but with the battery life and sketchy cell problems I may have to go back to stock.
Anyone have any ideas?
Thanks!
I wish I could get this to be stable, and I understand it's still beta, but I have to go back to stock. If I didn't need the phone and SMS functions to be reliable then I'd stick with it, but I need my phone for work.
I'll keep an eye on how things progress and maybe try again down the road, but chances are I'll be upgrading to a Galaxy Nexus in a couple of weeks anyway. At least then I can use my X2 as a toy and not care about carrier stability.
I think these problems are rare, sorry. I do share the "wifi not reconnecting" but wifi fixer is a work around. This is a super daily driver. There was a screen blackout but I found non-compatable themes to be the problem.
We need a "This works check list kind of thread" so people know what does work. FWIW.
edit
This is the best battery life I have had on any rom.
Yeah, I also had the wifi not reconnecting problem but that was trivial. I'm back to stock now, the last straw was the phone not even reconnecting to 3G, I lost all data connectivity. I could deal with the battery and such, but the cell/data connectivity problems are a definite no-go for me.
skwoodwiva said:
I think these problems are rare, sorry. I do share the "wifi not reconnecting" but wifi fixer is a work around. This is a super daily driver. There was a screen blackout but I found non-compatable themes to be the problem.
We need a "This works check list kind of thread" so people know what does work. FWIW.
edit
This is the best battery life I have had on any rom.
Click to expand...
Click to collapse
Maybe you can start one of those threads.
I also notice a fast battery drain but the rom hasn't settled in yet and it may need more time to do so.
Sent from my MB870 using xda premium
My issues are (minor):
One of my game can not be played (Siegecraft - after downloading the game data, the system ends with "network error") all my other games play fine, so I don't know why.
Gallery app constantly re-starts when trying to view pics. No work around it. If anyone can suggest a good gallery replacement app, please let me know, I tried Gallery Plus (I think that is what it is called) and it also did the same thing.
Major issue (Maybe not an issue):
My wife claims that some phone calls are not going through (it rings from her end, but I am not hearing the ringing on my phone for some reason - I had 5 missed calls listed on my phone). That said, 3 or 4 test calls I made came through without any issues so maybe it is the issue with the ringer not being high enough for me to hear?
Overall, so far, except for the missed calls (which may not be an issue at all) it is a very good daily driver and hopefully after things settle down a bit more it will get even better.
Navigation/Maps/Latitude issue with GPS
When I go into Navigation or Maps or Latitude, especially Navigation, there is a constant message at the bottom of the screen "Searching for GPS".
When looking at Maps, you see the current position but the area is in a fuzzy circle. It didn't happen when I was on stock rooted 2.3.4.
I did see an option to use an external BT GPS but the external is not enabled.
Any ideas?
[EDIT] [Solved] After a reboot, GPS is working fine.
Notifications Blah
hoganw said:
One minor and a couple of major issues...
- Notification drop-down stops accepting touch input but can still be slid up and down. Reboot fixed
Click to expand...
Click to collapse
I had this same problem, reboot fixed but only temporarily as it returned last night again. As of right now I can't get the notification bar drop down to accept input without a reboot. I'm borderline on this being a showstopper as I live off of the notification bar...
I've poured through the settings, but haven't found anything that fixes it. I have the notification bar power widget turned on, turning that off hasn't made a difference either. I'm going to leave it off and reboot, and see if it comes back.
Do you have the notification power widget turned on?
For everyone having problems with CM7, I HIGHLY recommend going in and wiping both cache and dalvik-cache. (Not a data wipe.) This has fixed pretty much every problem I have run into with CM7.
Now for downloading large files, I have found that I have to use tasker to create a "power profile" that never turns off the screen. I do not have the WIFI loosing connection issue that has been reported, however I have noticed (on stock as well) that when the screen times out, downloads all fail or stop. Just my 2 cents.
Ciao!
Moon Shadow - NM said:
For everyone having problems with CM7, I HIGHLY recommend going in and wiping both cache and dalvik-cache. (Not a data wipe.) This has fixed pretty much every problem I have run into with CM7.
Click to expand...
Click to collapse
Even though this was done after applying CM7 in BSR? Not sure why doing it again would make any difference, but stranger things have been known to happen.
Now for downloading large files, I have found that I have to use tasker to create a "power profile" that never turns off the screen. I do not have the WIFI loosing connection issue that has been reported, however I have noticed (on stock as well) that when the screen times out, downloads all fail or stop. Just my 2 cents.
Ciao!
Click to expand...
Click to collapse
I'm not sure if people have tried this, but it works for me...
Settings -> Wireless and Networks -> WiFi Settings -> (menu button) -> Advanced -> WiFi Sleep Policy
By default it's set to turn wifi off when the screen turns off but can be set to "Never."
I would like to report the only problem I have had with CM7 on my DX2 is one of my apps not restoring data I backed up before flashing. Other than that, I LOVE THIS ROM! I used this ROM on my old Dinc and absolutely loved it then too. I feel at home with CM7, and since this is only a beta version, I can't wait for the final release!
Moon Shadow - NM said:
For everyone having problems with CM7, I HIGHLY recommend going in and wiping both cache and dalvik-cache. (Not a data wipe.) This has fixed pretty much every problem I have run into with CM7.
Click to expand...
Click to collapse
I wiped cache and dalvik (even though I did it in the install steps as well) and the frozen notifications problem has not resurfaced for me. I will post again if it returns, but thanks for the tip moon shadow!
Well, I guess I'll give it another shot. Getting back up and running is almost second-nature now, hooray for backups. haha
I'll wipe, flash, boot CM7, reboot, wipe again, and see if things behave any better. I just went back to stock a few days ago and I'm ready to kill it again. Only 2.5 weeks to upgrade devices!
So I've read through the CM7 development threads and through this one regarding some of the issues. I am currently running on Liberty. Since I am still learning the Android world (read: I'm freaking clueless), would you guys suggest changing over to CM7, or staying with Liberty?
Thanks! (from the girl who's trying to learn...)
BreatheALittle said:
So I've read through the CM7 development threads and through this one regarding some of the issues. I am currently running on Liberty. Since I am still learning the Android world (read: I'm freaking clueless), would you guys suggest changing over to CM7, or staying with Liberty?
Thanks! (from the girl who's trying to learn...)
Click to expand...
Click to collapse
I have never run the liberty rom but i do recommend cm7. The only issue I've had is with wifi. It loses connection sometimes. I downloaded wifi fixer from the market. It doesn't fix the problem but it does reconnect wifi for me. Some have this problem and some don't.
Make a nandroid and give it a try. If you don't like it you can always go back to liberty.
Sent from my cm7dx2 using XDA App
maggard5 said:
I have never run the liberty rom but i do recommend cm7. The only issue I've had is with wifi. It loses connection sometimes. I downloaded wifi fixer from the market. It doesn't fix the problem but it does reconnect wifi for me. Some have this problem and some don't.
Make a nandroid and give it a try. If you don't like it you can always go back to liberty.
Sent from my cm7dx2 using XDA App
Click to expand...
Click to collapse
Thanks so much!! I found the directions to give it a try, and realized it was waaaaay more complex than what I felt comfortable doing on my own. Plus, it said I would have to install it from Gingerbread... so that would be 2 installs to complete. May have to wait for my tech guru for this one! However, I'm excited to check it out!
(By the way, I realized that on the couple posts I have, you have helped with both of them. Double thanks. )
BreatheALittle said:
Thanks so much!! I found the directions to give it a try, and realized it was waaaaay more complex than what I felt comfortable doing on my own. Plus, it said I would have to install it from Gingerbread... so that would be 2 installs to complete. May have to wait for my tech guru for this one! However, I'm excited to check it out!
(By the way, I realized that on the couple posts I have, you have helped with both of them. Double thanks. )
Click to expand...
Click to collapse
Good luck with whatever you decide but it really isn't as complicated as it sounds. Moonshadow has created some great tutorials to guide you through each step. And you are welcome for the help.
Sent from my cm7dx2 using XDA App
Well, I guess I'll give it another shot. Getting back up and running is almost second-nature now, hooray for backups. haha
I'll wipe, flash, boot CM7, reboot, wipe again, and see if things behave any better. I just went back to stock a few days ago and I'm ready to kill it again. Only 2.5 weeks to upgrade devices!
Click to expand...
Click to collapse
Looks like the notification issues returned for me, great timing. I noticed this time, that one of the notifications that is stuck there is partially Swiped off to the left. I took a screenshot but I'm a nub here and can't post the link.
On another note, I continue to have the wireless problems... dx2 keeps trying to connect, sometimes says disabled. I have set it to never turn off in the screen timeout section. Very weird...
Sent from my MB870 using XDA App
Well, I went and reinstalled CM7 last night. I was diligent about clearing both caches both before and after install, and again a little later after reinstalling apps, plus I also cleared the battery stats.
Don't want to jinx it, but so far so good. Battery life has been very good, I easily went 16 hours and the battery was still > 50%. No call or SMS issues and no notification bug yet. We'll see how things work over the next couple of days...
I've got horrid battery life (down to 60% in 5 hours of LOW use) and some wifi issues (sometimes has a hard time connecting, sometimes not).
I'm going to try the davlic and cache wipe and report back.
Hi all,
I'm wondering if anyone can help me....I'm getting kind of desperate here! Basically my Atrix keeps randomly rebooting or getting stuck with the screen off (requiring a batter pull) . This happens about 10-20 times a day (my Atrix is far too unreliable right now to use as a daily). This seems to ONLY happen when on network (ie 2g/3g/hspa) and doesn't seem to happen on wifi. I can leave it on all night and day at home on wifi happily with no trouble but as soon as I go to work and leave it on network, the trouble starts. Its weird cause if the phone is doing something with the screen off (playing and streaming music over Bluetooth for example) it won't have any problems. Its only once I leave it at rest on the network that it turns into the most unreliable handset ever.
At first I thought it may be the neutrino rom I was running but I've since been using jokersax's amazing ics builds and the same problem persists. I did a full clean (format /data & /system plus cache and factory wipe ) and loaded on the latest beta build this morning, left it clean with zero apps except google (and xda!) and within an hour of getting to work the problem came back.
I am fully boot loader and network unlocked.
Please, if anyone has any idea I would be really grateful. I am tearing my hair out!
Sent from my MB860 using XDA App
It is happening with me too, but, I dont realize it on happen on mobile data connection
Since i flashed beta 0.1.0 2d of Jokersax's ICS and come out of home
Today, for 5 times I have to pull battery out of Atrix
Why not try a more stable ROM first and see if you get reboots.You do realize some phones just cannot handle unstable roms like the cm9 builds even though they are great for some ppl it just doesn't workout also maybe you are using an oc kernel that your phone cannot handle.I would check both things first.
Try some a bit more stable.
cm7 ba2ft
wetdream
darkside
gingermod
If you get the same with those then maybe fastboot wipe and stuff like that so you can clear everything out
EDIT: flash a radio too
sk8trix said:
Why not try a more stable ROM first and see if you get reboots.You do realize some phones just cannot handle unstable roms like the cm9 builds even though they are great for some ppl it just doesn't workout also maybe you are using an oc kernel that your phone cannot handle.I would check both things first.
Try some a bit more stable.
cm7 ba2ft
wetdream
darkside
gingermod
If you get the same with those then maybe fastboot wipe and stuff like that so you can clear everything out
EDIT: flash a radio too
Click to expand...
Click to collapse
Hey,
Thanks, I'm going to try Gingerblur tonight... I had ruled that out as I have used darkside/gingerblur before and apart from the occasional reboot they were OK. The reboot was OK really, I know its a known issue with this model even with unrooted handsets, as long as its occasional and clean boots back to system again it doesn't really matter as I don't pin lock my sim (currently my problems are either a reboot every three minutes as soon as I switch the screen off... or, more commonly, the dead screen, needing that battery pull) .
I *suspect* that it may be the radio, but really need some solid advice on this because a couple of years ago I completely bricked my G1 by flashing the wrong radio and vowed never to touch radios again if I didn't have to....I am naturally very hesitant about radio flashing from that episode. Can anyone give me some decent advice on which radios i should be looking at for an unlocked ( but formerly Orange UK) Atrix? One very nervous owner here!
The other weird thing is that is perfectly fine when on a power source.
Sent from my MB860 using XDA App
markdjj said:
Hey,
Thanks, I'm going to try Gingerblur tonight... I had ruled that out as I have used darkside/gingerblur before and apart from the occasional reboot they were OK. The reboot was OK really, I know its a known issue with this model even with unrooted handsets, as long as its occasional and clean boots back to system again it doesn't really matter as I don't pin lock my sim (currently my problems are either a reboot every three minutes as soon as I switch the screen off... or, more commonly, the dead screen, needing that battery pull) .
I *suspect* that it may be the radio, but really need some solid advice on this because a couple of years ago I completely bricked my G1 by flashing the wrong radio and vowed never to touch radios again if I didn't have to....I am naturally very hesitant about radio flashing from that episode. Can anyone give me some decent advice on which radios i should be looking at for an unlocked ( but formerly Orange UK) Atrix? One very nervous owner here!
The other weird thing is that is perfectly fine when on a power source.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hang on, I'm not making sense here, maybe it is these advanced ROMs, I was just surprised that neutrino (a cm7 based rom) also produced these reboot problems. Anyway, any advice on radios would be appreciated
Sent from my MB860 using XDA App
As long as you flash atrix radios only you should be okay. I flashed just about every applicable radio on my brother's captivate and never bricked it.
I agree with you and previous posters, it sounds like a radio issue for sure.
Sent from my MB860 using XDA App
I have the same problem with my Atrix running cm7 ba2ft. Sometimes it does not respond when you try to unlock, and I need to take out the battery to turn it on again. I bought the phone couple of weeks ago.
another thing to look at would be the battery my friend had similar problems with his nexus and tryed Roms and radios I bought him a new battery as a joke and the joke ended up on me cause he hasn't had the problem since let me know if this helped you aswell
Sent from my ics+darkside multiboot mb860 using xda premium
Same problem here. Very aggravating.
I am having the same problem. And I am 100% stock with no mods. I just installed OTA 2.3.6 so I am waiting to see if that helped.
Yeah, I'm really worried this is a hardware problem - I've been quiet these past couple of days testing the brand new GB radio and when that still had errors i then also tried the European one - the problem still persists. I have now downloaded every Atrix radio under the sun now so may try a few more...
This is quite frustrating as a) I really want to enjoy ICS as it really is a step up from previous versions of Android and b) I no longer have the option of selling this in its current state.
I'm also going to try a new battery as WikidClown suggested above, can't harm....I can pick up one on Amazon for less than a tenner.
One thing is for sure, I don't think I will be buying Moto hardware again!
ChrisSkeeles said:
I am having the same problem. And I am 100% stock with no mods. I just installed OTA 2.3.6 so I am waiting to see if that helped.
Click to expand...
Click to collapse
OK, so does anyone have any ideas? I have tested it using a load radios...and still nothing, it still randomly reboots. This is possibly the most unreliable handset I have ever owned
Sent from my MB860 using XDA App
Have you tried fastboot wipe? Maybe format internal SD and start fresh. Haven't had this issue just trying to help.
Sent from my MB860 using Tapatalk
jp2132 said:
Have you tried fastboot wipe? Maybe format internal SD and start fresh. Haven't had this issue just trying to help.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I have formatted /system and /data etc between ROM changes, how would I do a fastboot wipe? I'm willing to try anything at this point!
Sent from my MB860 using XDA App
Actually, scratch that, I know exactly how to do that...except I can't boot into fastboot. Is this indicative of something wrong? Will I have to go back to SBF?
markdjj said:
I have formatted /system and /data etc between ROM changes, how would I do a fastboot wipe? I'm willing to try anything at this point!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
i baught my atrix used. everything was stock. still had multiple reboots and battery pulls daily. on cm9 they seem to happen less. and the battery pull only happened once. but i know the issue must still be there. might try my wifes battery. her atrix has rebooted maybe 5 times ever. 3 since this last official update (she is still lock stock and 2 smoking barrels)
OK, trying a new battery is my last hope...I did a fastboot wipe this morning and for an hour and a half it was all going so well...but then the reboot happened.
I'm getting a bit fed up with this pos hardware...I can't even sell this thing in this state.
Sent from my MB860 using XDA App
Anyone have any other experiences? I have confirmed that it isn't the battery...I bought a new batter and within 45 minutes it has rebooted once and done the screen off thing where it needs a battery pull. Complete crap.
One thing to note is that it does seem to get very warm on the back, although the internals ( behind the battery) don't seem so bad. Is there any way to keep the temp down aside from underclocking? All my roms have always been under clocked so I know that doesn't make any difference.
The other thing I might try is to use something like Noled so the phone isn't completely idle. Might drain the battery a bit unnecessarily though....why couldn't Moto have put in an amoled screen?
Anyway, will report back once I've tried it.
Sent from my MB860 using XDA App
I used to get tons of random reboots and then I was told to get the app called "Wake My Android Pro". Settings -> Test Activity -> Auto Startup, and Stop Activity checked. Weird settings, I know, technically with stop activity checked it doesn't do anything, but ever since then I don't experience random reboots. This was a few months ago when I was on just CM7. I've always installed this app when I get a new rom and I've tried Neutrino, Darkside, Alien, Aura, CM7, Wet Dream, and currently on joker's CM9 beta 1 build and RARELY experience random reboots. It went from once an hour to once a month now. I'm also on the .36p radio if that helps.
SoupySauce said:
I used to get tons of random reboots and then I was told to get the app called "Wake My Android Pro". Settings -> Test Activity -> Auto Startup, and Stop Activity checked. Weird settings, I know, technically with stop activity checked it doesn't do anything, but ever since then I don't experience random reboots. This was a few months ago when I was on just CM7. I've always installed this app when I get a new rom and I've tried Neutrino, Darkside, Alien, Aura, CM7, Wet Dream, and currently on joker's CM9 beta 1 build and RARELY experience random reboots. It went from once an hour to once a month now. I'm also on the .36p radio if that helps.
Click to expand...
Click to collapse
Cheers, have downloaded and will report back. The most annoying thing about troubleshooting a problem like this is that there is no immediate 'it worked or 'it didn't work' ....it's just a waiting game! Thanks a lot though, really hope it does work (and thanks for replying, was starting to feel like I was answering threads to myself!). I have .36 radio installed already (I think, will check...it's the Brazilian one isn't it?) .
Just to check then...you have all the check boxes in wake my android ticked?
Sent from my MB860 using XDA App
Hi Guys,
Im no Genius when it comes to android, but I have done my fair share of programming before, but my SOD are killing me and a last resort is a warranty exchange as I cannot be without a phone.
So far I have been getting SOD about 5 times a day if not more, and I am one for tinkering with gadgets until i break or crash it, fix it and doing it all over again.
But anyway back on topic
I have noticed this in the build.prop
" persist.ril.mux.sleep=2 "
And so I wondered if this is causing my SOD, does anyone have any ideas regarding its uses?
Findings (as of 2155)
In my testing thus far I have changed it to "persist.ril.mux.sleep=1" using phone leaving it for an hour doing it over just for fun, And I have been SOD for 5 hours straight and haven't had any SOD or adverse battery drain
I mean this may not be the cause of the SOD for me, or anybody but I am up for trying just about anything
What is SOD?
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
Sorry, Sleep Of Death
I have SOD here too. To me it's only happens when I turned off a data connection (3G or wifi).
I use LoadMonitor app as a workaround for a while, with success.
At now I'm using Neutrino 2.5 CM7 ROM with success too. I think it's more a blur rom problem than cm7 one.
Let us know about your progress.
So if you disable load manager you would get SOD?
I am making a script to update a few things so far no SOD for me, after a few tweaks
What settings are you using on load manager ?
Any info you can give me will help in me tracking down some of the errors and temporary fixes people are using to avoid the dreaded issue
Oh, THAT's what that was!
I forgot to turn the wifi back on a few nights ago when I said "Hey, let's watch some movies on netflix with my super-duper mirroring-abled phone!" So an hour into it, LBE Privacy warns me I'm about to max out my data, and I go turn the damn wifi back on but turned OFF the 3G.
Then last night I go to wake up my phone and the screen is "black but on", & took a couple of tries to wake it. I'm on Nottachtrix.
Harrison85 said:
So if you disable load manager you would get SOD?
I am making a script to update a few things so far no SOD for me, after a few tweaks
What settings are you using on load manager ?
Any info you can give me will help in me tracking down some of the errors and temporary fixes people are using to avoid the dreaded issue
Click to expand...
Click to collapse
I'm a bit confused here. I don't know what "load manager" is.
What a sad is I used LoadMonitor app (from market) as a workaround.
LoadMonitor just monitor taks that are running in your device. But it have an option that claims to prevent device deep sleep. So, when I checked this option my device don't get SOD.
It's a workaround, as I sad, and I don't know how LoadMonitor do that.
What is load manager?
Thanks
I had a similar issue, I installed SetCPU and set my minimum speed to ~456(faux 1.45 Kernel).
Never had the problem since.
cldot said:
I had a similar issue, I installed SetCPU and set my minimum speed to ~456(faux 1.45 Kernel).
Never had the problem since.
Click to expand...
Click to collapse
cldot do you use blur rom or cm7 one?
Thanks
My bad meant load monitor
Sent from my MB860 using xda premium
I tried some roms and the only one I hadn't random reboots was jokersax11 alpha7 (ICI), now I'm on beta 0.2.0 and had reboots.
I'm having the same problem. I've tried 3 different ROMs. I used Nottachtrix, following the directions to the letter with reboots and hard locks. Recently I flashed back to 4.5.91 (w/pudding) and I was having the same issues. I noticed that on the hard locks, my phone appeared to be warm, so I used SetCPU at 216MHz and still had hard locks and random reboots. I've not set the lowest setting at 301 and so far I haven't had any reboots, but its only been about 5 hours. But I was having them at least once every few hours.
BTW - I also noticed that I only had the freezes and hard locks when the phone was running on the battery. I rarely had problems when the phone was on the dock or USB charger, however, I did have reboots when it was on the wall charger.
Another program you can try is call 'Wake Lock' available from the marketplace. I haven't used it yet, I'm still experimenting with load monitor.
Wake lock has a few different options and has some really good review.
I confirmed that Neutrino 2.5 CM7 Rom works great without reboots.
That's a patch you need to apply to correct a battery drain problem of the original version. Notorious544d are working in a 2.6 version including that patch.
To me it's working like a charm. I'm testing for two days but, of course, everyone needs to test it in your own device.
PS: Follow this instructions to install a battery drain patch in Neutrino 2.5 (or wait for a 2.6 version):
http://forum.xda-developers.com/showpost.php?p=23179486&postcount=4258
Update 13/03/2012: Notorious544d released Neutrino ROM 2.5p with battery patch and some other things.
See you!
what patch?
marcosvafg said:
I confirmed that Neutrino 2.5 CM7 Rom works great without reboots.
That's a patch you need to apply to correct a battery drain problem of the original version. Notorious544d are working in a 2.6 version including the patch.
To me it's working like a charm. I'm testing for two days but, of course, everyone needs to test in your own device.
See you!
Click to expand...
Click to collapse
Could you point me to that patch? I can't seem to find it. Thank you
Sleep Of DEATH!!!
I was encountering that problem for a while but then I figured that something went wrong when I was flashing CM7 Beta. So I flashed Aura's ROM, and then Reflashed CM7 Beta and only experienced it once a month at most after that, Hope it helps
eNorby said:
Could you point me to that patch? I can't seem to find it. Thank you
Click to expand...
Click to collapse
Follow this instructions (or wait for a 2.6 version):
http://forum.xda-developers.com/showpost.php?p=23179486&postcount=4258
Update 13/03/2012: Notorious544d released Neutrino ROM 2.5p with battery patch and some other things.
Atrix SOD & Random reboots related to Wifi?
Does anyone know if the Atrix SOD & Random reboots are related to WiFi. I've had my wifi off all day and I've had no crashes.
I'm going to run it for a few more days without Wifi and see what happens.
I don't know about other guys, but wifi and 3G was the cause of my Atrix SOD and reboot problems.
Solved it using Neutrino Rom CM7 based.
See you!
Still working on my SOD issue, but recently, I disabled most power options, turned off wifi, rebooted and I've been running for 2 days with no crashes. After day 3, I'm going to turn wifi back on reboot and see what happens.
Update 1
After 3 days with wifi disabled, I've had no crashes, no freezes or random reboots. I'm going to enable wifi again and see what happens.
Update 2
After turning enabling my wifi and using it briefly then turning it back off, I had a random reboot later that evening.
The more I used my wifi, the more frequent my crashes became.
Interesting side note
I can enable all my radios when plugged into the desktop charger and I won't experience any crashes, however, if plugged into to the AC charger, I've had reboots and freezes.
My touchpad has been draining battery even when off. You can see in the picture attached represented by the blank sections. The first blank section represents about a day of the device being off without use. And when I say off, I mean powered down through the menu, not just in sleep mode.
Anyone else seen this? Seems to be something that has recently started happening.
A little background, I was running one of the cm9 camera enabled nightlies, but wanted to try JC CM10 so used ACME Uninstaller to completely remove android. Then installed cm10 using ACME installer 3. Played with it for a few days then wiped and restored a cm9 backup instead to go back to ICS until cm10 battery is better. Since then, this battery drain has been happening even when off.
I didn't know something could be sucking battery even when device is off. Any ideas? Maybe I need to use unistaller again and start android install fresh again.
Sent from my cm_tenderloin using Tapatalk 2
On the battery does it show what apps are consuning most battery? Did this barely start? Maybe it's an app that is constantly gathering info from online. I know my Hotmail app use to drain my battery so I had to go stock email
Sent from my GT-I9300 using xda premium
This is all the info it shows for battery info. And I'm not sure how it could be an app. The tablet is powered off completely. Shut Down.
It's really very strange.
Sent from my DROID RAZR using Tapatalk 2
Unfortunately it sounds like the battery might physically be going bad. How long have you had it and does it spend a lot of time plugged in while in use?
Sent from my Galaxy S III using Xda Premium
It's a JB thing. This happens as well on my Nexus 4. It's not a battery drain problem, but more so battery reporting is a little messed up. At least that's what I've read in the N4 section.
Boot into Webos, get Dr. Battery app from preware and read what the health is. Mine is at 93%, I've had it for a little over a year and brand new it read 95%. If you're losing juice even when its completley off, I'd expect your percentage to be much lower. There's also not much that can be done about it since you can't recalibrate a TP battery.
This issue has been discussed before. It is not necissarily a defective battery and in some cases is just simply a case of how the TP is being "shutdown" it was noted over at webos nation that in some cases the TP was failing to FULLY powering down...perhaps due to some location reliant apps that maybe continued scanning if shut down from within android...This AFAIK has never been confirmed however the issue has now been Solved for some users over at http://forums.webosnation.com/hp-to...tery-drains-when-off-webos-3-0-5-problem.html
Try the "fix" on page 6 to see if it solves your issue.. Hope it helps
Pickens said:
My touchpad has been draining battery even when off. You can see in the picture attached represented by the blank sections. The first blank section represents about a day of the device being off without use. And when I say off, I mean powered down through the menu, not just in sleep mode.
Anyone else seen this? Seems to be something that has recently started happening.
A little background, I was running one of the cm9 camera enabled nightlies, but wanted to try JC CM10 so used ACME Uninstaller to completely remove android. Then installed cm10 using ACME installer 3. Played with it for a few days then wiped and restored a cm9 backup instead to go back to ICS until cm10 battery is better. Since then, this battery drain has been happening even when off.
I didn't know something could be sucking battery even when device is off. Any ideas? Maybe I need to use unistaller again and start android install fresh again.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I had this issue for months and decided to do some research to rectify the problem. My touch pad would lose charge from 100% to zero within ten days even when the device was turned off. Doesnt matter of i shutdown from cm or webos or moboot.
Here's what I did.
Basically I did a full clear reinstall of cm9 / cm10
1. Backup all apps and system data
2. Remove cm by using acmeuninstaller
3. Remove all folders (format) the hard drive
4. Restore webos to 3.0.0 using webos doctor
5. Reinstall cm
6. Restore backup data.
Afterwards I made some tests
Turned off touch pad at 100 percent each time from moboot cm and webos. Check back 4 days later. All good
zaqq1 said:
I had this issue for months and decided to do some research to rectify the problem. My touch pad would lose charge from 100% to zero within ten days even when the device was turned off. Doesnt matter of i shutdown from cm or webos or moboot.
Here's what I did.
Basically I did a full clear reinstall of cm9 / cm10
1. Backup all apps and system data
2. Remove cm by using acmeuninstaller
3. Remove all folders (format) the hard drive
4. Restore webos to 3.0.0 using webos doctor
5. Reinstall cm
6. Restore backup data.
Afterwards I made some tests
Turned off touch pad at 100 percent each time from moboot cm and webos. Check back 4 days later. All good
Click to expand...
Click to collapse
Thanks for the reply. Here is what I have done to get a start fresh.
1. Remove cm by using acmeuninstaller
2. In WebOS, installed "Remove Android" from Preware to wipe remaining Android boot stuff.
3. Followed this guide to repartition and restore 3.0.0 WebOS. http://forum.xda-developers.com/showthread.php?t=1426244
4. Factory reset to wipe everything again.
5. Performed system update to WebOS 3.0.5 (tried to upgrade through WebOS doctor 3.0.5, but would not boot. Restored back to 3.0.0 and went through System Update, and that worked fine).
What I plan to do this afternoon (didn't have time last night):
6. Install Preware, UberKernal, and GovNah (I like my WebOS to be at its fastest before a CM install, even if I never use WebOS)
7. Reinstall cm10 (JC Sullins 12/16), moboot 3.8.0, new CWM, and gapps using ACMEInstaller3.
8. Install apps fresh (don't really have anything where I need to restore data).
Once I do this, I'll run some tests where I leave it off for a couple days. I'll post back with results. Hopefully getting a fresh start will fix things like it did in your case.
synchron50 said:
Boot into Webos, get Dr. Battery app from preware and read what the health is. Mine is at 93%, I've had it for a little over a year and brand new it read 95%. If you're losing juice even when its completley off, I'd expect your percentage to be much lower. There's also not much that can be done about it since you can't recalibrate a TP battery.
Click to expand...
Click to collapse
Before I did all the wiping, I checked this and health is at 94%. So it shouldn't be a bad battery. I'll update on the results of the full CM and WebOS wipe.
Pickens said:
Before I did all the wiping, I checked this and health is at 94%. So it shouldn't be a bad battery. I'll update on the results of the full CM and WebOS wipe.
Click to expand...
Click to collapse
Mine has been doing the same thing. When I turn it off and leave it for a day or so, I have battery loss. I thank it started when the camera was added to CM9.
I am looking forward to seeing your results.
Pickens said:
Thanks for the reply. Here is what I have done to get a start fresh.
1. Remove cm by using acmeuninstaller
2. In WebOS, installed "Remove Android" from Preware to wipe remaining Android boot stuff.
3. Followed this guide to repartition and restore 3.0.0 WebOS. http://forum.xda-developers.com/showthread.php?t=1426244
4. Factory reset to wipe everything again.
5. Performed system update to WebOS 3.0.5 (tried to upgrade through WebOS doctor 3.0.5, but would not boot. Restored back to 3.0.0 and went through System Update, and that worked fine).
What I plan to do this afternoon (didn't have time last night):
6. Install Preware, UberKernal, and GovNah (I like my WebOS to be at its fastest before a CM install, even if I never use WebOS)
7. Reinstall cm10 (JC Sullins 12/16), moboot 3.8.0, new CWM, and gapps using ACMEInstaller3.
8. Install apps fresh (don't really have anything where I need to restore data).
Once I do this, I'll run some tests where I leave it off for a couple days. I'll post back with results. Hopefully getting a fresh start will fix things like it did in your case.
Click to expand...
Click to collapse
I have three touchpads and did exactly as you. Afew of my observations:
1. the 94% does not appeared to be measured. It is the current Voltage (expressed as mA's)/manufactorers hard coded spec, (6612mAh). If in Android, (I'm onCM 10+camera+gyro), using Battery Monitor Widget, I can adjust the actual to 6100, (or anything else), and get 6039/6100=99%
2. My discharge rate on WebOS in Airplane mode was arround -613 to -850mA. Screen on, (brightness affects this).
3. My discharge rate on CM10 in Airplane mode is about -520mA!!
4. A PC's USB port puts out 500mA's!!!
5. On the touchstone, (doesn't seem to matter if WiFi is on or off), with screen on 1/3 brightness + Battery Monito Widget = +853 to 945mA
6. On HP charger & cable, same as above = +1,377mA
What suprised me was the greater drain in WebOS.
I've had this issue since the beginning of installing Android on both my TP. Really annoying but I always assumed it was because of Android since I had no problems with WebOS.
I get battery drain when leaving the device unused, but it's significantly lower than it used to be in early stages of cm9 and cm10 development. I find it to drain slightly faster than WebOS but you have to remember this device was not designed around android.
This has not been a discussion of power loss in an unused state. It is power loss in an "off" state. Powered down with neither WebOS or Android running.
Sent from my DROID RAZR using Tapatalk 2
After doing all the wipes listed above, I ended up just putting the newest CM9 nightly (with GAPPS) and moboot 035 back on instead.
Results. I believe these wipes have fixed my problem. Here are some of my results:
Turned off at 96% for 18 hours, still at 96 when I booted up.
Turned off at 77% for 12 hours, still at 76 when I booted up.
Turned off at 56% for 12 hours, still at 55 when booted up.
Before I would have lost about 10-15% over these same time periods. Not seeing the drop at all now. And all of these power downs were on the Android side so don't believe the hype about Android power-down being the problem.
Sent from my DROID RAZR using Tapatalk 2
Pickens said:
After doing all the wipes listed above, I ended up just putting the newest CM9 nightly (with GAPPS) and moboot 035 back on instead.
Results. I believe these wipes have fixed my problem. Here are some of my results:
Turned off at 96% for 18 hours, still at 96 when I booted up.
Turned off at 77% for 12 hours, still at 76 when I booted up.
Turned off at 56% for 12 hours, still at 55 when booted up.
Before I would have lost about 10-15% over these same time periods. Not seeing the drop at all now. And all of these power downs were on the Android side so don't believe the hype about Android power-down being the problem.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
I restarted from scratch and it worked. I turned my TP off for 2 days and the battery read 100% after boot. Thanks for the help.
Checking back after a few weeks, glad to see that the fresh install solved the issue for some of u guys
battery health 91 % DR battery
so this means my battey is going bad
had my tp for over a year now
is that normal ?
anyone ?
Not sure how you got that from this thread. Some people suggested it might be a bad battery, but I think our results with restoring our touchpads would show that wasn't the case.
Follow the steps in post 9 and everything should be good to go. Worked for me. No more battery drain issues while the device is off. I've even returned to CM10 and still no problems.
Sent from my DROID RAZR using Tapatalk 2
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly my phone does the same with occasional random reboots and lock ups requiring battery pulls (Even the power button-menu-power up didn't restart to twrp) and even then restarting doesn't usually go without a hitch. Even when I was running stock root my phone would get stuck at the yellow sprint screen from time to time and I'd have to go TWRP and wipe Dalvik and Cache, then Dalvik again to get it to reboot.. The only reason I didn't unroot was was because even when my phone was new and out of the box, stock it wouldn't reboot cleanly all the time.
It got a little better after the firmware updates but it still hasn't gone away entirely.
I do expect it to get cleared up eventually but for now just take it as a fact of life with this phone.
demetrios3 said:
Honestly my phone does the same with occasional random reboots and lock ups requiring battery pulls (Even the power button-menu-power up didn't restart to twrp) and even then restarting doesn't usually go without a hitch. Even when I was running stock root my phone would get stuck at the yellow sprint screen from time to time and I'd have to go TWRP and wipe Dalvik and Cache, then Dalvik again to get it to reboot.. The only reason I didn't unroot was was because even when my phone was new and out of the box, stock it wouldn't reboot cleanly all the time.
It got a little better after the firmware updates but it still hasn't gone away entirely.
I do expect it to get cleared up eventually but for now just take it as a fact of life with this phone.
Click to expand...
Click to collapse
Yeah, I've been wiping dalvik and cache too, to get my phone back to normal at times too.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like its the beastmode kernel issues. Flash version 1.8 and see if that fixes your issues.
I would run the MJ4 tar via Odin to start totally fresh.
I am having a similar issue. my phone will just reboot on its own and freeze up a lot. i dont think its the kernel because it has been happening ever since i first installed the jellybomb rom and had a lite kernel installed. now switched to beast 2.3 and still having the same issues. im gonna flash 1.8 and see if it gets any better. but people are posting positive results on the 2.3 . dont know what to do. its frustrating
sillykaos said:
I am having a similar issue. my phone will just reboot on its own and freeze up a lot. i dont think its the kernel because it has been happening ever since i first installed the jellybomb rom and had a lite kernel installed. now switched to beast 2.3 and still having the same issues. im gonna flash 1.8 and see if it gets any better. but people are posting positive results on the 2.3 . dont know what to do. its frustrating
Click to expand...
Click to collapse
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Compusmurf said:
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Click to expand...
Click to collapse
Ill give it a shot when i get home. barely have service here at my office. ill post my results back.
Compusmurf said:
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Click to expand...
Click to collapse
My phone has been doing this from the time i took it out of the box on October 4. It was ever worse then, so much so that I returned the phone exchanged it for a new one. The problems continued and I questioned my decision to upgrade to the Note 3 but then the firmware upgrades improved things a little.
I can tolerate the issues now and I do expect them to go away on future updates
edgar360 said:
Sounds like its the beastmode kernel issues. Flash version 1.8 and see if that fixes your issues.
Click to expand...
Click to collapse
I flashed 2.3 kernel and it seemed to fix most problems.. I just get Internet shutdowns here and there.. So far that's the only problem.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
I flashed 2.3 kernel and it seemed to fix most problems.. I just get Internet shutdowns here and there.. So far that's the only problem.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
2.3 is the shiz, bro. I know some have issues with it, but for me it far exceeds even 1.8. Even with no overclocking, 1.8 would do odd stuff, like go to off when I'd selected restart (plugged in or not), &c. With 2.3, I've yet to run into any issues, the phone behaves as I've directed it. I overclock it using profiles in SetCPU, and the cores stay cool. With 1.8, no such luck.
As to Internet shutdowns, I have found that the browser plays a role in things. Having never used the stock browser, I switch mainly between boat browser and chrome, and both will occasionally freeze. Long back press to kill is my fallback.
Sent from my SM-N900P using Xparent BlueTapatalk 2
what your describing
Your phones should run flawlessly all the time. I would take issue that when the phone starts acting buggy, it's just normal for this phone.....I disagree with that, there is a issue somewhere if you have these issues occasionally.
Just my 2 cents
Well it took my slack ass a couple weeks to flash the stock kernel due to my issues. and after a few days my phone hasnt randomly rebooted. So i take it my phone is not liking the BEAST right now? This is just some poopoo.