Database Users

[Q] Freezing issues resolved with mod?

I'm now on my third G2. Sent the first two back in because they were having the freezing issue that's been documented here and on other forums that require a battery pull to get the phone back up. The second phone also had a dead pixel.
I have not yet had the issue with the latest phone, but have only been using it for a day and am not super optimistic given my experience with the first two. I'm still curious if the freezing is a hardware or software issue.
I'm wondering if anyone had this issue with their G2 and had it resolved by installing cyanogenmod or another mod. I have not tried rooting/modding yet as I knew I'd likely be returning the phones and didn't want to go through the work of having to undo it. It just dawned on me today that perhaps it's something tmobile has installed on the phone that is causing it to freeze. So I was thinking it might be possible that a non-tmobile mod might resolve it.

I had the issue on RC1 and haven't had it freeze since installing RC2. It would freeze while the screen was off and I had to pull the battery and let it boot up again.
Sent from my T-Mobile G2 running Cyanogenmod.

ibemad1 said:
I had the issue on RC1 and haven't had it freeze since installing RC2. It would freeze while the screen was off and I had to pull the battery and let it boot up again.
Click to expand...
Click to collapse
Thanks for the reply. How long have you been running RC2?

Since it came out. On RC1 I had about 2~3 crashes within the first week of using it.
Sent from my T-Mobile G2 running Cyanogenmod.

All of my problems were gone after the OTA update. It has been running like an absolute champ since.
Sent from my T-Mobile G2 using XDA App

I stopped having the reboots once I turned off the wifi sleep. If you live somewhere with lousy Tmobile coverage, but have wifi @ home, it helps a lot. Even helps battery life.
Sent from my T-Mobile G2 using Tapatalk

so much for the 2.3.3 reboot fix

simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?

no.. wrong section
try wiping dalvik/cache/factory

No reboots over here.
Sent from my Nexus S

dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
what kernel? And if you're going to ***** about problems with 2.3.3 you should run fully stock to make sure some customization is causing the issue.

Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?

I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.

kenvan19 said:
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
Click to expand...
Click to collapse
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".

Highland3r said:
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Click to expand...
Click to collapse
My G2 (pure stock) rebooted once in a while. In fact I watched it happen while i was in a meeting there day before I got the nexus s. It must be the same bug!
nexus s has not reboot once, though ill give it time its only been three days.
Sent from my Nexus S using Tapatalk

On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\

dinan said:
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
Click to expand...
Click to collapse
is this from benchmarks or are you seeing real world performance decrease? I am not trusting benchmarks as my g2 performed better in quadrant, yet real world the ns feels much faster.
Sent from my Nexus S using Tapatalk

Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App

dinan said:
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk

I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Anyway, just had a reboot while trying to do the pattern unlock to wake my phone. It booted with a little "Safe Mode" thing at the bottom left, never seen that before. Then shortly after that it promptly rebooted itself again and it's back to normal CM7, but all my widgets mysteriously vanished from my home screen... great.
[hfm] said:
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse

dinan said:
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Click to expand...
Click to collapse
True, that was just my impression switching phones. I suppose it was a stability/compatability play as I hope they wouldn't unknowingly release a build with an unknown gross performance deficiency in the display driver.
Sent from my Nexus S using Tapatalk

prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.

cygnum said:
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
Click to expand...
Click to collapse
My phone is doing the exact same thing.
On 2.3.2, CM7 nightly 2.3.3, and stock 2.3.3.
Wiped or not. Rooted or not. Same damn reboot/shutoff.
It just reboot/shutoff with screen off, and hangs dead there sometimes with LED lights on. Have to remove battery to boot. Sometimes takes a dozen time battery removal to get it pass bootloader.
I am fed up. Now I am using wiped non-root 2.3.3 with a broken CMR, and still reboots!
I am going to flash the stock Recovery back and lock the bootloader before sending back to Samsung for replacement.
But seriously, what would you recommend as my next phone. I am thinking about Tbolt or Atrix.

rocketragz said:
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
Click to expand...
Click to collapse
It's not.
I have 2 Nexus S, both of them have spontaneously rebooted on 2.3.3.
It was much worse on 2.3.2, though.
Both are stock, not even rooted. Even most of the apps are different (my wife uses very few).

delete....

dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call. Also You're running CM7, so any random reboots is an issue with CM7 itself. It's still buggy as heck.
And ummm actually for me. Build 11/12 has been strong, not a single reboot. Used to have random soft-reboots, soft-reboot loops, and can't unwake the phone. All needing battery pulls. Haven't had a single random reboot with CM7 build 12.

nxt said:
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call....
Click to expand...
Click to collapse
Except that it's happening to way too many of us, NOT during a call. I call that a "reboot" bug.
My phones are stock.

Anyone with CM7 getting random reboots still?

Just wondering if you had random reboot issue and then it stopped after flashing cm7? Thanks

I am and it's getting really annoying

mithoss76 said:
I am and it's getting really annoying
Click to expand...
Click to collapse
Have you flashed a different kernel? Or are you over clocked or undervolted? I was getting randome reboots because I was undervolting incorrectly. I am now running Faux's latest .2.0 1.3ghz kernel and have had no reboots.

I get them on rare occasions .... but I'm experimenting with UV ... not frequent enough for me to pinpoint an issue or to be annoyed by it. Last time occurred after after doing a system setting.

I dont get random reboots anymore, cm7 and last faux kernel at stock 1.0ghz fixed it.

I've been on CM7 for a week and no reboots.

been running it for 2 weeks or so. Had one minor glitch yesterday with my device when I locked the screen- she wouldnt wake back up and had to battery pull. Other than that, no issues. I am running Faux's 0.2.0 Stock CM kernel as well.

I had one reboot on my Atrix since running CM7. Compare that with several a week on the stock Motorola software. Using whatever kernel shipped with CM7. Overall, a great improvement!
Sent from my MB860 using xda premium

Reboot here this morning. Actually had to do a battery pull. Faux 2.0 1.3 no undervolt
Sent from my alien

not really random but does anyone else get
a reboot if you leave the torch on to long? It may be a known issue I haven't looked but it seems to happen to me every time..
Sent from my MB860 using XDA App

It could be due to something not getting flashed right. Depending on what rom/fruitcake/etc is flashed, not all images are replaced. That's by design, because the good ol' fashioned SBF flashes EVERYTHING, which you really don't always need, and can be potentially dangerous. Assuming something got corrupted somewhere, or there's an older version of part "x" that doesn't like to play with the never version of part "y", that could cause a crash. You might want to look at a safe way to get a clean wipe, and then redoing CM7. I'm not suggesting SBFs or anything. But I'd check out samcripps' Fruit Cakes @ http://forum.xda-developers.com/showthread.php?t=1163009 though.

ICS/job ROMs without headset bug?

Sorry guys im new to the my touch comin from the g2 recently. Is anyone aware of what ROMs don't have the bug where the battery drain is high when headset is plugged in?
Thanks in advance
Sent from my Toasted Marshmallow using Tapatalk 2

From what I have found all ROMs based on 3.x kernel have this issue. Some even get very hot. The work-around I have found...is to use bluetooth headphones, however I also found that most do not allow GPS to work whilst bluetooth is on.

In the g2 ROMs the issue was cause by a camera driver... could this be the same case? I'm far from a dev but it was easy implemented by flinny in the g2 forums
Sent from my Toasted Marshmallow using Tapatalk 2

shady503403 said:
In the g2 ROMs the issue was cause by a camera driver... could this be the same case? I'm far from a dev but it was easy implemented by flinny in the g2 forums
Sent from my Toasted Marshmallow using Tapatalk 2
Click to expand...
Click to collapse
i really hope they figure it out, i listen to music alot and battery dies in 1 hour with phone getting cooked. All the ICS/sense 4.x roms work perfectly though except minor lag. I wonder if their kernels could be used in jellybean because i once flashed elgins kernel on the oneV port and the heating issue appeared, reverted kernel it disappeared. Loved the PACman and CM10 but cant last 3hours with charge and superheated pockets

osaedu said:
i really hope they figure it out, i listen to music alot and battery dies in 1 hour with phone getting cooked. All the ICS/sense 4.x roms work perfectly though except minor lag. I wonder if their kernels could be used in jellybean because i once flashed elgins kernel on the oneV port and the heating issue appeared, reverted kernel it disappeared. Loved the PACman and CM10 but cant last 3hours with charge and superheated pockets
Click to expand...
Click to collapse
Same here. I get about 45 minutes of usage before the battery dies
I wonder if perhaps the camera can be frozen and have a 3rd party one in place...or is it the actual driver itself that causes the issue? (though why a camera driver would affect sound...)

shadowharbinger said:
Same here. I get about 45 minutes of usage before the battery dies
I wonder if perhaps the camera can be frozen and have a 3rd party one in place...or is it the actual driver itself that causes the issue? (though why a camera driver would affect sound...)
Click to expand...
Click to collapse
Ya.. idk why it causes it but it was fixed in the g2 forums by a dev and a swear he said it was a camera driver. Basically keeps the device awake while plugged in.. hopefully a dev sees this and contacts flinny in The g2 forums. He had it fixed. Or maybe someone will port his jb build.. ....damn if only I was smarter
Sent from my myTouch 4G using Tapatalk 2

shady503403 said:
Ya.. idk why it causes it but it was fixed in the g2 forums by a dev and a swear he said it was a camera driver. Basically keeps the device awake while plugged in.. hopefully a dev sees this and contacts flinny in The g2 forums. He had it fixed. Or maybe someone will port his jb build.. ....damn if only I was smarter
Sent from my myTouch 4G using Tapatalk 2
Click to expand...
Click to collapse
So I froze the camera, as I said I would try, I ran music for 2 hours (while plugged in) and surprisingly, the phone got warm but it did not get hot! I then unplugged it and ran it for 50 minutes, (up from 45), so the battery drain was also diminished but not very significantly. Still the phone only ran warm and not hot. So I think that the issue might be related in part to the camera.

On noice... ya like I said that's what a dev mentioned over in the g2 forum that got the other jb builds working too. Are any kernels (non 3.0) able to be flashed on jb without causing major issues?
Sent from my myTouch 4G using Tapatalk 2

Horrible battery life

https://imgur.com/a/uw1yr
I'm running Resurrection Remix on the latest build and have been having horrible battery life (about 2 hours sot) since quite a while now. I now charge like 2-3 times a day and overnight...
I recently did a clean wipe and reinstalled all my apps while only restoring Google authenticator and wifi passwords with titanium backup. I'm rooted with Magisk. I bought my Axon7 quite exactly one year ago. Have I fried my battery?

vadsvads said:
https://imgur.com/a/uw1yr
I'm running Resurrection Remix on the latest build and have been having horrible battery life (about 2 hours sot) since quite a while now. I now charge like 2-3 times a day and overnight...
I recently did a clean wipe and reinstalled all my apps while only restoring Google authenticator and wifi passwords with titanium backup. I'm rooted with Magisk. I bought my Axon7 quite exactly one year ago. Have I fried my battery?
Click to expand...
Click to collapse
thats the same symptoms ive been having as well even my brother im not sure if its the battery fried lol

I've had mine ZTE axon 7 on RR for almost a year and has had amazing battery life

M25201 said:
I've had mine ZTE axon 7 on RR for almost a year and has had amazing battery life
Click to expand...
Click to collapse
Are you rooted? Do you use titanium backup?

Does RR have anything like the stock power manager?

RobboW said:
Does RR have anything like the stock power manager?
Click to expand...
Click to collapse
No, not really... I mean I can set a power profile, but that doesn't really do much.
I have to confirm that again, but if I turn on Airplane mode, my battery is a beast. I think there's some sort of drain coming from the kernel or something

vadsvads said:
No, not really... I mean I can set a power profile, but that doesn't really do much.
I have to confirm that again, but if I turn on Airplane mode, my battery is a beast. I think there's some sort of drain coming from the kernel or something
Click to expand...
Click to collapse
even if i have amplify and greenify it does the same thing so it must be a kernel thing might to flash a EAS one then

gecko702 said:
even if i have amplify and greenify it does the same thing so it must be a kernel thing might to flash a EAS one then
Click to expand...
Click to collapse
What does EAS stand for? Never saw that abbreviation before

vadsvads said:
What does EAS stand for? Never saw that abbreviation before
Click to expand...
Click to collapse
means energy aware scheduling
edit: heres a kernel: https://forum.xda-developers.com/axon-7/development/kernel-t3664743
not sure if itll help ill test this maybe tomorrow

vadsvads said:
No, not really... I mean I can set a power profile, but that doesn't really do much.
I have to confirm that again, but if I turn on Airplane mode, my battery is a beast. I think there's some sort of drain coming from the kernel or something
Click to expand...
Click to collapse
You could try flashing a different modem for your model.

Maybe an app or two also keeping it awake and trying for a network? Not getting a deep sleep in doze.
Stock ROM has power manager and I suspect that is the only reason I get a day from mine.

If you're still suffering I suggest you go back to stock or reflash properly as in step by step and make sure nothing has gone wrong.

joaste said:
You could try flashing a different modem for your model.
Click to expand...
Click to collapse
Where would I get that? I believe a friend helped me flash one a few weeks ago, but I don't remember where it was from. (I've had the issue before too, though)

I get this too. Absolutely horrible battery life. Well this started happening after I flashed the B32 bootstack and stock system to fix my camera issues. At first I thought it was the stock rom but I flashed candyrom and the llama sweet kernel EAS version and I still get it. I do think it's the phone signal but I'm not sure yet. I used to drop to 98% in about 10-20 minutes with WiFi on and screen on. Now I lose 10% in that time. I went from 98% (it doesn't even want to fill charge anymore but I think it's the kernel) to 92 in 10 minutes.

Teet1 said:
I get this too. Absolutely horrible battery life. Well this started happening after I flashed the B32 bootstack and stock system to fix my camera issues. At first I thought it was the stock rom but I flashed candyrom and the llama sweet kernel EAS version and I still get it. I do think it's the phone signal but I'm not sure yet. I used to drop to 98% in about 10-20 minutes with WiFi on and screen on. Now I lose 10% in that time. I went from 98% (it doesn't even want to fill charge anymore but I think it's the kernel) to 92 in 10 minutes.
Click to expand...
Click to collapse
I feel you... I really hope it's just basically a software issue... If you have any solution, please, please update me and the others here - i just flashed the kernel that got recommended to me and I'll try if it makes things better. Otherwise I'll wait for Oreo, I guess...
I'm not even that sensible to bad battery life in phones because i always carry a powerbank, but if the phone barely makes it to work in the morning and I have to recharge it at work at 25% or so, it gets a little annoying ^^

vadsvads said:
I feel you... I really hope it's just basically a software issue... If you have any solution, please, please update me and the others here - i just flashed the kernel that got recommended to me and I'll try if it makes things better. Otherwise I'll wait for Oreo, I guess...
I'm not even that sensible to bad battery life in phones because i always carry a powerbank, but if the phone barely makes it to work in the morning and I have to recharge it at work at 25% or so, it gets a little annoying ^^
Click to expand...
Click to collapse
True that...I don't believe it to be the battery. It could be software. I noticed that my battery usage spikes up to 1140+ mAh and stablizes at 460 mAh which is way too much. I remember only getting up to 430+ in worst cases and stabilizes at 200-300+
Here's what my battery usage looks like:
https://imgur.com/a/va5Tb
Logcat: https://drive.google.com/file/d/1fUbNjqgodSk8098HBR2OJr1HtWiXLCyI/view?usp=sharing
(because for some reason I cannot upload in attachments)
Candyrom 6.0 Android version 7.1.2 and Llama Sweet Kernel EAS v.02 10-02-17 release
I hope you find a solution too. If you do, please let me know.

vadsvads said:
Where would I get that? I believe a friend helped me flash one a few weeks ago, but I don't remember where it was from. (I've had the issue before too, though)
Click to expand...
Click to collapse
Check out the download center or the LOS thread.

joaste said:
Check out the download center or the LOS thread.
Click to expand...
Click to collapse
Download center is all A2017G, unfortunately not for me as I'm on U and in the LOS thread the latest modem is from February so I'm almost certain I have that already flashed. Too bad. I guess we'll figure out what the problem is.

Teet1 said:
Download center is all A2017G, unfortunately not for me as I'm on U and in the LOS thread the latest modem is from February so I'm almost certain I have that already flashed. Too bad. I guess we'll figure out what the problem is.
Click to expand...
Click to collapse
My bad. Check out post #6 here. Not sure about the versions there.
Edit: you could also flash the full stock b32 system and then go back to whatever

joaste said:
My bad. Check out post #6 here. Not sure about the versions there.
Edit: you could also flash the full stock b32 system and then go back to whatever
Click to expand...
Click to collapse
Fullstock is how I got into this mess i think, since this started happening as soon as I flashed B25 bootstack and stocksystem. But the new baseband, I'll try that and see how it goes. However that's B25, we're on B32 so hopefully someone posts the new modem. I have not tried flashing an older bootstack as I somehow doubt that will fix it. Granted, i noticed my battery life starting to wear while I was on an older bootstack while on DARK rom.
ediit: it seems i'm already running this modem version. https://imgur.com/a/8jeEh