[Q] Need help with Fascinate rooting and rom. - Fascinate Q&A, Help & Troubleshooting

I have rooted phones over the years and never had as much as an issue as I am with my wifes Fascinate.
It all started when it updated to 2.3.5 and the wicked battery drain (2-3 hours of normal use and dead).
I tried re-calibrating the battery to no avail, then told her babe just going to get rid of 2.3.5 and replace it with MIUI (which I use on my D2G).
I went to many forum sites including here and have tried countless ways to get the ROM changed. 99.9% of the time being stuck at reboot in waiting for sdcard 20.19.18.......etc before it reboots.
CWM just reboots, Glitch Kernal does the SDcard waiting reboot etc.
Like I have said tried everything on many sites and cant get it to work. My wife says let it go and she will take it to Verizon and replace the battery. My fear is if its 2.3.5 causing the drain as I believe it is since she had no issues prior, then what difference will a new battery make.
Any points in the right direction would be greatly appreciated so i can solve this issue for her asap.
THANK YOU!!!!

Buzz4infinity said:
I have rooted phones over the years and never had as much as an issue as I am with my wifes Fascinate.
It all started when it updated to 2.3.5 and the wicked battery drain (2-3 hours of normal use and dead).
I tried re-calibrating the battery to no avail, then told her babe just going to get rid of 2.3.5 and replace it with MIUI (which I use on my D2G).
I went to many forum sites including here and have tried countless ways to get the ROM changed. 99.9% of the time being stuck at reboot in waiting for sdcard 20.19.18.......etc before it reboots.
CWM just reboots, Glitch Kernal does the SDcard waiting reboot etc.
Like I have said tried everything on many sites and cant get it to work. My wife says let it go and she will take it to Verizon and replace the battery. My fear is if its 2.3.5 causing the drain as I believe it is since she had no issues prior, then what difference will a new battery make.
Any points in the right direction would be greatly appreciated so i can solve this issue for her asap.
THANK YOU!!!!
Click to expand...
Click to collapse
I had the same proble with a 2.3.5. AND 2.3.6. too, 10hours tops.
So i've ODIN it back to 2.3.4. now I'm at 2 days, on medium use.

do you have a link to that rom? and how do you prevent it from updating to 2.3.5?

Buzz4infinity said:
do you have a link to that rom? and how do you prevent it from updating to 2.3.5?
Click to expand...
Click to collapse
Go to my guide in the general section and look up section 4. I would odin the stock 2.3.5 and see if that fixes your issue. Many folks are having issues with the ota 2.3.5 update.

droidstyle said:
Go to my guide in the general section and look up section 4. I would odin the stock 2.3.5 and see if that fixes your issue. Many folks are having issues with the ota 2.3.5 update.
Click to expand...
Click to collapse
OK so tried the stock 2.3.5 an still had battery drain issues. So I did section 4, then Section 3 using the latest Miui Fascinate Rom (1.12.9) and it went back to the Vodoo Glitch where it reboots at waiting for sdcard reboot.
I then did section #4 and section #3 again using your step by step to ICS Teamhacksung. Same thing happened CWM waiting for Sdcard bootloop. So I tried taking out Sdcard as suggested.
What I did not do since i was doing Section 4 first was follow steps 6-11 in section 3, (didn't think I needed to since did section 4).
I see the comment at end of Section 3 that says if pulling card etc doesn't work to get a class 6 or higher card. (wife has a 16gb class 2 stock card)
Was wondering since my D2G was able to go to Miui with a 8gb class 4 card if i put that in her fascinate (copied her data to it, she doesn't use even close to 8gb) would it work and would her card work in mine if I tried to flash a rom on it.
or would you say just go get a class 6 card, and if so what local retailers sell one for under $30 in store . (sears, walmart, office depot, staples, best buy, frys etc)
THANK YOU for all your guides and guidance

swapped microsd cards with D2G 8gb class 4 and got Miui to work like a champ....
installed battery spy and re calibrated battery at full charge. It went from 100% to 80% in 20-30 minutes of just sitting on the counter. I saw gps was on so shut that off. Wife left for work with it and told her to let it die completely before recharge so will see when she gets home.

battery issues still....gonna return to stock and take to verizon tomorrow.
Unless any other ideas?

Sure it's not an issue with the battery itself? Have you tried restoring the phone to froyo? From what you said in the first post, it sounds like battery drain was normal back then so that's what I'd try.

Related

[Q] Battery on GB Nameless

I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
I can't speak on the new build, but I was running the 4.0 build and my battery ran down so quickly that I thought I left my gps running with a connection. I also was having quite a lot of issues with the rom, so I thought it was a fluke. I'm on 4.1 and it's been running much better, so hopefully the battery drain isn't as great.
Definitely sounds like you've got a runaway process or wake-lock occurring somewhere. Have a look around the processes and see if something's keeping the CPU running hard. Also run a dumpsys power from adb and see if something's keeping it from sleeping.
Im getting quite the opposite here. It's been almost a day and after moderate use I have a little over 50%. It's amazing because I would be getting half of that on a full charge in froyo.
Looks like it may have been the Widget itself.
But i am not sure, if i closed the running application of Battery Monitor it dropped down to -1 or -2 but then ten mins later its back up to -300.
The other possibility is when i kill the app the widget gets no information and defaults to a low number.
Thank you everyone for your input. I will keep on testing to find my battery killer.
I also may try uninstalling K-9 mail and reverting to the stock Mail client
It being on stock kernel and a lot of debugging features being enabled will do that to your battery.
Sent from my SCH-I500 using XDA App
A lot of people have reported poor battery life with K-9, FWIW, though the K-9 devs say there isn't an issue. I haven't used it myself so I can't really say... you could try this though:
https://market.android.com/details?id=org.r3pek.k9datakiller&feature=also_installed
4.1 drained my battery from 100% to 10% in about 4 hours today. But then I plugged in and rebooted and I had 40%, so I would imagine a battery stats wipe is needed on my phone.
My home button does not work as well, so I am going to re-install again and see if it fixes these issues.
Anyone else had the home button issue?
Edit: The re install fix the home button/lock screen issue. Will report back on the battery tomorrow.
Weird, my battery is AMAZING on Nameless. After 11 hours with using Screeble, with moderate use, I'm at 50%.
xwhofarted said:
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
Click to expand...
Click to collapse
I tried Nameless 4.0 and it used less than 20% during the first 6 hours.
Whenever I flash a new rom, it uses more power at first and less and less as you use the phone. Some people insist that you do not have to kill the apps especially on Gingerbread.
zas311 said:
Some people insist that you do not have to kill the apps especially on Gingerbread.
Click to expand...
Click to collapse
Assuming you're talking about task killers, "some people" = Google. With the exception of apps like Watchdog (which just notifies you of apps using excessive CPU, like >50%), task killers hurt more than they help -- they're all effectively scams.
Google's serious techy explanation:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.
An excellent, understandable article from Lifehacker:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
I thought I read somewhere (either the EC09 Leak thread on the Nameless v4 thread) that auto-rotate is causing 50% cpu for this EC09 leak, would that have something to do with battery drain?
http://forum.xda-developers.com/showthread.php?t=1131213&page=15
Thanks
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
xwhofarted said:
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
Click to expand...
Click to collapse
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Scrappy1 said:
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Click to expand...
Click to collapse
This. My battery life (and signal dBm) has been MUCH better even at work, which is notoriously hard on the battery due to being so well insulated.
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
sarkozy said:
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
Click to expand...
Click to collapse
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
That's definitely what I'd be leaning towards. I also took the added (though not really needed) step of using the GB root exploit app, and confirming all was well before ever flashing CWM3.xx in ODIN, then going onto the nameless ROMs. I've actually tried to re-create the problem since I stuck in a spare 4GB card waiting for it to happen, but nothing so far.
Everything is so new, it's really all speculation for the time being. I personally don't think it's the ROM or the leak causing the problem, although it's obviously a factor. There are so many different combinations of recoveries being used (as if all of us read directions in full) and ROMs were flashed in different sequences that it's impossible to nail it down.
Aside from disabling auto rotate, I've had no complaints about the leak or ROM. I ran CM7 forever on my Eris before getting this Fascinate, and while I like it, it's a pain to deal with the missing functionality at times.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
detox07 said:
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
Click to expand...
Click to collapse
So, immediately upon flashing the sd card was corrupted?
It'd be nice if there was more cooperation among everyone to figure out the common problem. It seems like for all the trouble reports, there are as many or more of us with no issues. I can't see anything in logs that would tip off a problem, so it needs to be someone who has the issue.
I'm still leaning towards it being a recovery issue. It's odd that some people are saying the files still appear on the sd when viewed through the CWM interface.
Sent from my SCH-I500 using Tapatalk
Man, that would be awful if the CWM we were told to use is what is killing the SD cards, and a diffr version would have worked :O
I used the CWM linked in the nameless thread and no issue so far, but only 2 days so far.

Horrible battery life after 2.3.6

Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.
Batter Usage shows the Android OS at 93%!!!
Not using my phone, it is dead in about 7 hours.
Kernel Version
2.6.35.7
Build Number
GINGERBREAD.UCKK6
I am not rooted and dont want to root.
HELP!
Tymong said:
Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.
Batter Usage shows the Android OS at 93%!!!
Not using my phone, it is dead in about 7 hours.
Kernel Version
2.6.35.7
Build Number
GINGERBREAD.UCKK6
I am not rooted and dont want to root.
HELP!
Click to expand...
Click to collapse
You have an app that is driving data to your phone, causing the wifi chip to wake the phone all the time. Apparently a system app - a lot of people have been having this issue with KK6.
Beyond this - sorry, but if you are not rooted you will have to live with it. Identifying what is triggering the wifi interrupts requires obtaining a Wireshark capture, this is not possible without root. Even if a common root cause is found for what's going on with KK6, it's most likely in /system itself so can't be fixed without a custom ROM or at least rooting.
If you're not willing to root, why are you on a firmware developer forum? Have AT&T help you instead if you're on 100% bone stock unrooted.
Well if it's an APP causing it, then many many people must be running the same app cause all of the various forums out there are a lot of people with the battery drain after updating to 2.3.6. Even a lot of my customers have mentioned it also.
I doubt it is an APP doing it. I'd bet it is just some bad coding on Samsung's part. They are probably getting a lot of complaints and are most likely already looking into it.
As far as the why he is here if he doesn't root. Well I don't root as well and have no desire to being as stock works just great. (other than the battery drain)
This is a great place to hang out and keep up on other people using various phones. He posted in the General section, not the Developer's section for this phone. So I think his/her question was valid.
If he was asking the question in the Developers section I would understand your concern. But I don't feel you have to be into cooked ROMS to value this forum.
That's like saying to the people who like the "Fast and the Furious" moves to stop watching them because they have a Chevy and not a pimped up Civic.
Tymong said:
Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.
Batter Usage shows the Android OS at 93%!!!
Not using my phone, it is dead in about 7 hours.
Kernel Version
2.6.35.7
Build Number
GINGERBREAD.UCKK6
I am not rooted and dont want to root.
HELP!
Click to expand...
Click to collapse
I'm not rooted with wifi on all the time just got the phone 3 days ago and I'm getting 14-15hrs with no issue down to about 15-20% battery life left before I have to stick back on charger. Could be a bad battery or device, I'm coming over from Sprint after using rooted evo3d and rooted photon.
Sent from my SAMSUNG-SGH-I777 using xda premium
The forum is called xda-DEVELOPERS.com
If you don't want to root, you're probably better off in the AT&T support forums, because honestly, it isn't worth our time to try and help someone who doesn't want to root fix a problem that is almost sure to require root access to fix, or in this case, even diagnose.
I do believe many are having this issue after upgrading to kk6 (with same apps installed). I had the issue as well.
May be a system app, or something in /system causing an app to become unhappy.
Either way, it's not going to get fixed without Shark for Root captures from those encountering problems.
Sent from my GT-P7510 using Tapatalk
browncarpet said:
I do believe many are having this issue after upgrading to kk6 (with same apps installed). I had the issue as well.
Click to expand...
Click to collapse
I don't think it anything to do with KK6. As Entropy said its an app causing a wake lock. I'm run Ingram KK6 without any issues with battery.
Sent from my sgh-i777 using xda premium
Having this issue as well. Phone is stock. Ive been here since the captivate but I hang around with the sgs2. Never needed to root this phone as it works perfectly for me. But I did the update this morning at 100% charge and 9 hours later with no use it's down to 9%. I could go all day with moderate use and be at 30-40% by the time I go to bed.
I read on a rather long on a google forum that many had this issue after upgrading via ota but who knows. I found that wiping dalvik and flashing unnamed update again I have much better batter life. I did read in update that he reverted to an earlier kernel signature to fix the battery drain.
Im going back to 2.3.4 via this method.
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/
Losing 10% of my battery at idle /hour is ridiculous lol. Android os was at 87+% within 3 hours of restart.
Edit:
Okay so I did this method. Took about 5 mins after I got everything downloaded. I did not do the factory reset since it's not needed. Phones back to 2.3.4 and nothing was reset. Have all my sms's contacts, aps, wallpapers etc. Battery seems to be back to normal.
I recommend everyone who did that 2.3.6 update to revert back. To many problems with it.
I never entered download mode on this phone before. Just a tip: Keep holding all the buttons till the phone seems like it shuts off and keep holding them till you get into download mode. Do not let go or else it just powers off.
For the purposes of attempting to fix the problem, I really would like some people to take some Shark for Root captures as described in my Known Battery Drainers thread.
With that data, the root cause of the problem might be identifiable.
So far I've only seen one capture, I really need more unless I can reproduce the problem myself.
Entropy512 said:
For the purposes of attempting to fix the problem, I really would like some people to take some Shark for Root captures as described in my Known Battery Drainers thread.
With that data, the root cause of the problem might be identifiable.
So far I've only seen one capture, I really need more unless I can reproduce the problem myself.
Click to expand...
Click to collapse
I'm also having battery issues but would like to try to fix it before giving up.
I've searched a bunch but can't find that thread. Not at home to try it on my PC so if you'll link it here, I'll do what I can to get some captures for you.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
[REF] Known identified battery drainers
n7slc said:
I've searched a bunch but can't find that thread. Not at home to try it on my PC so if you'll link it here, I'll do what I can to get some captures for you.
Click to expand...
Click to collapse
[REF] Known identified battery drainers
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.
Worth a shot as it does not require anything more than charging your phone and pulling the battery.
Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.
That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.
Screen grab of my current battery use after trying this method this morning is attached.
radeon962 said:
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.
Worth a shot as it does not require anything more than charging your phone and pulling the battery.
Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.
That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.
Screen grab of my current battery use after trying this method this morning is attached.
Click to expand...
Click to collapse
Placebo effect - did nothing a plain old reboot would not have done.
Entropy512 said:
Placebo effect - did nothing a plain old reboot would not have done.
Click to expand...
Click to collapse
Quite possible, but still running on the same charge from this morning and am at 28% battery after 14+ hours of normal use which is all I expect (calls, texts and light web browsing during the day over data) and then couple hours of web use at night over Wi-Fi when at home.
The last few days I was charging the phone when I got home from the office if I wanted to use it at night. Android OS was way up in the 60+ range after I first updated OTA and today it has been under 20% and more near 15%, so I'll take it.
---------- Post added at 11:09 PM ---------- Previous post was at 10:59 PM ----------
Come to think, I probably did not do a reboot after the update and could have been all that was needed.
radeon962 said:
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.
Worth a shot as it does not require anything more than charging your phone and pulling the battery.
Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.
That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.
Screen grab of my current battery use after trying this method this morning is attached.
Click to expand...
Click to collapse
I did this and saw absolutely no change. 2.3.6 is draining my battery far faster than 2.3.4 ever did. The culprit is the Android OS running at 90%.
I read that it might be an issue with the wifi so I have turned that off and will report back if that seems to fix it.
I read on another forum that att and Samsung are trying to blame it on bad batteries and shipping out new batteries.
What a bunch of crap. People everywhere wouldn't suddenly all have bad batteries at the same time. Sounds like usual BS.
I personally think its just some bad coding that Samsung needs to figure out.
On a different note, I played with the Verizon Droid Razr yesterday. Man that is a really nice phone. I'm tempted to get it, but I work for att and get free cell service, so it wouldn't make sense to pay for Verizon service, even though I think their network is better.
Sent from my SAMSUNG-SGH-I777 using XDA App
chocodough said:
I read on another forum that att and Samsung are trying to blame it on bad batteries and shipping out new batteries.
What a bunch of crap. People everywhere wouldn't suddenly all have bad batteries at the same time. Sounds like usual BS.
I personally think its just some bad coding that Samsung needs to figure out.
On a different note, I played with the Verizon Droid Razr yesterday. Man that is a really nice phone. I'm tempted to get it, but I work for att and get free cell service, so it wouldn't make sense to pay for Verizon service, even though I think their network is better.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Android OS is definately eating up the battery now. I think it does have to do with wifi, because it seems to be much improved with it off. I'll take a free battery as long as I don't need to exchange the old one.

Atrix random reboots and screen not turning back on

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

[Q] Battery Calibration Problem?

I'm not sure if other X2's do this, but my battery runs fine. I get a solid 10 hours of hard use out of it.
But lately I noticed that if I simply reboot I get another 20%-50% out of it. Yesterday, it was down to around 30%, restarted, went back up to 80% and drained normally the rest of the night.
Is this normal? Is there a fix or something I can do? I wish I could just get the most out of the battery without having to restart.
I'm just running rooted 2.3.4. I do the whole drain it to 0% once a month thing & fully charge.
--
P.S. I'm not making this up. Lol.
2.3.4 is the problem. There is a battery bug in the software where it reports less battery power than you have. Then, when you reboot, it might shoot up 5% to 10%.
Many custom ROMs have a fix in it. Not sure what the fix is or if you can apply it to the stock ROM.
Eclipse 2.0.x has the fix, but it also requires updating to the unofficial 2.3.5 OTA upgrade.
CM7 is based on 2.3.4 kernel and seems to have the issue resolved as well.
I see. Well, thank you for your help. Sorry if this is a repeated topic.
I just got started in the whole root/flashing "scene" so I'll have to see what I can do about CM7 now.
For those that want to stay on the stock rom, the fix is here.
Thanks, I'll try this out later.
I could use it too but the download link is dead. Thanks
Tried using new file from updated link but it would not work. Hung up at installing. Had to pull battery to restart phone. Any ideas?? Thanks
Probably something wrong with Peppermint's script. I have the original one from my phone. You can give it a try if you want.
http://www.mediafire.com/?a52x45m3dou19us
Thanks. It installed OK this time. I'll be checking to see if it makes a difference. Thanks again for the help.
You're welcome. Hope it works for you.
xtel said:
I see. Well, thank you for your help. Sorry if this is a repeated topic.
I just got started in the whole root/flashing "scene" so I'll have to see what I can do about CM7 now.
Click to expand...
Click to collapse
I bought my mother an x2, rooted and flashed CM7, she gets around 15 hours on the stock battery.
You will notice a huge change in performance, battery and more while you flash any ROM... Good luck, just follow the tutorials here in the forum.
SMILE It's Not Illegal Yet
Hey can anyone help with my battery prob? I got the extended battery from verizon I wiped battery stats after draining it fully and recharging fully twice. I'm running eclipse 1.3, speedy v7, and the cdma unthrottle mods. For some reason my phone eats this battery faster than my stock battery.
Sent from my DROID X2 using Xparent Cyan Tapatalk

[Q] Yet another battery issue thread. But, this one's a "different" problem. No joke.

[Q] Yet another battery issue thread. But, this one's a "different" problem. No joke.
Hello Everyone,
I know I know... You're too tired to read through another sad tale of a battery issue. But, this one's weird. It shouldn't be happening, but is happening. I desperately desperately desperately need help solving this.
I own a Galaxy S2 i9100 (bought in July 2011, with Android 2.3.3 installed).
With 2.3.3 on the phone, I could manage getting juice for 24-26 hours.
I recently upgraded Android via Samsung Kies to Jelly Bean 4.1.2, and the battery life immediately tanked. I tested it for a week, and there was no improvement. That's when a friend of mine gave me the ICS 4.0.4 tar file that he managed to copy (from the temp folder in Windows) while upgrading his S2 via Kies.
I thought ICS would solve the battery woes, but it's only marginally better than JB. So, the battery life that I get out of my phone still sucks A LOT. The build I have on my phone is IMM76D.XWLPW. When I use the phone's display, play music, or am on a call, or have the GPRS on, the battery drains drastically. The stand-by time is pretty decent though.
Here's the most recent-est stat: I played music for 1 hour 10 minutes, had about 15 pings exchanged on WhatsApp, and the battery had tanked 14% in that much time.
I badly need this issue sorted. Otherwise, using apps like WhatsApp & Facebook (where people are constantly buzzing me every few minutes) will cause my phone to run out of juice every 6 hours. I used to use these apps (and pretty frequently) when I had Android 2.3.3 and the phone would manage to last 24-26 hours.
What could be the solution?
First thing, if you're still using the battery that came with the phone, replace it. Whether you got 143 hr on GB is irrelevant, a two year old battery is going to fail sooner or later.
Second thing, there is no easy solution (at least not one that doesn't involve messing with your phone, and even then you may not find one). If GB was so good for you, why not go back to it ? Get the GB rom you were running from Samfirmware, flash it with Odin. Done (And don't accept any future OTA updates).
If you want to stay with ICS or JB, search for the BetterBatteryStats thread here, install the app & allow it to run while you use your phone 'normally' for a day or so. Then post logs/etc to the BBS thread; people who post there regularly should be able to help you work out what's causing drain & if anything can be done about it.
Android 4.0.4 ? Oh, dude...you are lucky you haven't done a factory reset.Immediately flash ICS 4.0.3 or JB! You have 100% eMMC brickbug.Look at my signature and flash JB 4.1.2. eMMC bug + factory reset from recovery = phone dead forever.Follow my guide exactly and flash JB and root it !Then flash Apolo kernel for extreme bttery life.

Categories

Resources