Running Sho3. Was running fine, then yesterday started noticing screen time out wasn't working (set to 30 seconds like always). The screen still dims like when your not touching it for a couple seconds, but then it stays like that. Tried reflashing, wiping etc. I pulled the battery and that worked, but then just noticed I got a text and it stayed on, checked the browser and same thing, won't time out (but still dims).
I'm stumped... and this is annoying as I gotta keep manually doing it which I don't since not used to that all these years lol, so battery keeps draining faster.
surf1 said:
Running Sho3. Was running fine, then yesterday started noticing screen time out wasn't working (set to 30 seconds like always). The screen still dims like when your not touching it for a couple seconds, but then it stays like that. Tried reflashing, wiping etc. I pulled the battery and that worked, but then just noticed I got a text and it stayed on, checked the browser and same thing, won't time out (but still dims).
I'm stumped... and this is annoying as I gotta keep manually doing it which I don't since not used to that all these years lol, so battery keeps draining faster.
Click to expand...
Click to collapse
Running Shostock3 as well and I am not having this problem..but i'm wondering....Do you have smart stay checked under settings/display? Maybe checked it accidently?
Sent from my SGH-I777 using xda premium
Yeh its unchecked, that was one of the first things I thought of lol
surf1 said:
Yeh its unchecked, that was one of the first things I thought of lol
Click to expand...
Click to collapse
Lol...I did it before that's why I asked. Have you changed kernels? I'm on Ajk 1.52s running good.
Sent from my SGH-I777 using xda premium
EQ2192012 said:
Lol...I did it before that's why I asked. Have you changed kernels? I'm on Ajk 1.52s running good.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
No same kernal that came with it, Jeboo v1.3b. I'm honestly stumped, pulling the battery was the only thing that worked but that was only temporary for like an hour or 2. Nothing shows out of wack in BBS
surf1 said:
No same kernal that came with it, Jeboo v1.3b. I'm honestly stumped, pulling the battery was the only thing that worked but that was only temporary for like an hour or 2. Nothing shows out of wack in BBS
Click to expand...
Click to collapse
Jeboo was running good for me to. Sooooo....uhhhh...er..um..you got me stumped to. Lol. Someone will come along that has a better idea. Good luck!
Sent from my SGH-I777 using xda premium
Tried a reflash with a new download, worked perfect yesterday. Then this morning it was still working, got a text, and now screen time out doesn't work again (doubt it's text related as a I got a ton yesterday and had no probs).
Flashed AJs kernel to see if there was a difference but screen time out still doesn't work. I've searched and searched on XDA and no clue what the issue could be, the only threads about this are the normal fixes that are common sense (uncheck something etc).
this sucks lol
surf1 said:
Tried a reflash with a new download, worked perfect yesterday. Then this morning it was still working, got a text, and now screen time out doesn't work again (doubt it's text related as a I got a ton yesterday and had no probs).
Flashed AJs kernel to see if there was a difference but screen time out still doesn't work. I've searched and searched on XDA and no clue what the issue could be, the only threads about this are the normal fixes that are common sense (uncheck something etc).
this sucks lol
Click to expand...
Click to collapse
This is not a rom issue. Best guess, from a distance of course, is that some installed app is at fault. Have you flashed back to stock to verify that the problem goes away? You would need to wipe and install stock without any additional apps to be sure.
If it works normally on stock, then go back and wipe data/factory reset and install Sho3 without reinstalling anything, and see if you have the problem. That will tell you if it's an app.
Also you can turn off the screen turn on when you get a text option in messaging. May help.
creepyncrawly said:
This is not a rom issue. Best guess, from a distance of course, is that some installed app is at fault. Have you flashed back to stock to verify that the problem goes away? You would need to wipe and install stock without any additional apps to be sure.
If it works normally on stock, then go back and wipe data/factory reset and install Sho3 without reinstalling anything, and see if you have the problem. That will tell you if it's an app.
Click to expand...
Click to collapse
Yeh I had tried that and it seemed fine (then again Sho3 runs fine and then out of nowhere like a day or two later the screen won't time out), but the odd thing is all the apps I have are the apps I normally use. Checking wakelocks etc, everything seems a-ok, nothing unusual. I've always ran Sho's roms. Haven't downloaded any new app's, only 1 in the last month (Scramble), had installed that to re-check but the issue still happened, don't run widgets either.
I've did find a few threads as well as searching online about people having similar problems and looks like nobody could figure this out as a fix was never given. Seems to be all JB users though reporting this, especially with GSIII where even turning off stay awake etc doesn't help, some said they just had to keep rebooting the phones or hard reset removing the battery but that's only temporary fix.
Phalanx7621 said:
Also you can turn off the screen turn on when you get a text option in messaging. May help.
Click to expand...
Click to collapse
OK wtf LOL... I always actually keep that off as it's useless to me. But I just checked and it was on, but I know I had it off with Jeboo, AJs must have turned it back on?
This looks to of fixed the problem, I don't know why since this is a text setting, but I could of been in the browser, email, game, music, even the lock screen and it would stay on.... no clue how that option in text affects everything???
I'll update if any changes but as of now turned it off and screen timed out when I opened the browser and left as is.
thanks!
Np man, glad you got it fixed
Related
Please try this patch.
http://dl.dropbox.com/u/2056318/update-template/sod_patch1.zip
Install via clockwork and please report your findings.
Stopped by the IRC chat earlier and was given this. Worked for me. Thanks for all your work. I take it this has been a developing issue..?
I'm assuming that sleep of death us the phone not sleeping. Is this true? Hate to assume and install a clockwork file for something I don't need.
Sent from my SCH-I500 using XDA App
nmyeti said:
I'm assuming that sleep of death us the phone not sleeping. Is this true? Hate to assume and install a clockwork file for something I don't need.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Opposite rather. Phone not waking up and essentially shutting off. Goes to sleep, and never wakes up, hence, sleep of death
Huh, that's what that was. Had it happen with 2.3 wiped and updated to 2.4 and it seems to be okay. Wondered if it was only me.
Sent from my SCH-I500 using XDA App
jbjarko said:
Opposite rather. Phone not waking up and essentially shutting off. Goes to sleep, and never wakes up, hence, sleep of death
Click to expand...
Click to collapse
Permanantly never wakes up? I'm having an issue with the phone sleeping. I usually just have to hit the power button a few times.
Sent from my SCH-I500 using XDA App
papstar said:
Permanantly never wakes up? I'm having an issue with the phone sleeping. I usually just have to hit the power button a few times.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've read that too. Mine just flat out wouldn't wake up. Same issue I believe.
papstar said:
Permanantly never wakes up? I'm having an issue with the phone sleeping. I usually just have to hit the power button a few times.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've been having this problem rather frequently as well.
Wheww...I'm relieved it's not just me. Started happening to me yesterday with Blackhole 4.2. I'd press the power button to wake my phone and nothing...just like it's off, except that it won't turn back on until I pull the battery first. Reflashed everything and then it worked most of the day then started doing it again. Also nearly tanked my battery.
Anyway, gonna flash SC and this patch and see how that goes.
Just out of curiosity Adrynalyne...what is causing this that the patch fixes?
So we finally have the name for this problem.. I was having a hard time looking for info on this problem with no luck and just switched back to dl30. This problem always drained my battery pretty bad after I battery pulled.
Sent from my SCH-I500 using XDA App
Thank you so much this fixed the problem I was having. When my screen would go to sleep it would not wake the phone up until I pressed the power button 3 times and the lock screen would come on....thanks again
Sent from my SCH-I500 using XDA App
I don't know if this would help anyone but I'm curious to know if it's the case for anyone else:
For those of you who have not applied this patch that are having problems getting your screen to come back on until you pull your battery, does it unlock if you hit the power button and the volume keys a couple times?
When I was having this issue, I just got into the habit of squeezing both sides of my phone (power button and volume up key) twice and my screen would always come back on.
Somehow or another, it seems to have stopped. Not sure what I did to make it stop since I've done so much trying to figure out an unrelated issue. I never looked through the logcat to see what was happening back when I was having the screen lock issue, so now I am curious.
I remember this was a common term used in Windows Mobile development (Omnia, Omnia II)
Which is where I first admired Adryn's work
Thank you for making my devices the way they should have been
Said my Frozen Yogurt-filled Fascinate (EB01)
thanks for the patch. i didnt know what the hell was wrong with my phone.
Installed SC 2.4 and the patch, but I'm still getting the sod. This is really driving me crazy now and there seems to be almost no information out there. I ran the stock bloated rom for several days without any problems so I'm just about to the point of going back to it.
For informational purposes, I'm running SC 2.4 with ADW EX Launcher. The only apps I've installed other than what comes with SC are Beautiful Widgets, PowerAmp Pro, Switchpro widget, and HanDbase. I do not have a theme installed.
I patched this file yesterday and everything was fine. Woke up this morning to a phone that was off and it has been doing it intermintly all day long. I'm flashing again now. We'll see.
jbjarko said:
I patched this file yesterday and everything was fine. Woke up this morning to a phone that was off and it has been doing it intermintly all day long. I'm flashing again now. We'll see.
Click to expand...
Click to collapse
Doubt it'll work. I've re-flashed the rom and the patch several times and it hasn't worked for me. FWIW, it does the same thing with Blackhole 4.2. The only thing that has worked for me is to go back to the original stock eb01 rom.
Also should probably mention I'm running the non-voodoo version. Anyone have any thoughts as to whether I'd have better luck with the voodoo kernel or would it make things worse.
Strangely enough, I loaded this up today for occasional lag at wake up, not for sod & now I've seen sod... Might be an app I just loaded tho. Anyone ever try process monitor widget? It has a setcpu type function & I'm not so sure it wasn't the culprit
Sent from my SuperClean'd SGS
I've loaded the patch, but haven't had a chance to test if it works.
When it happened to me (SOD), it was only when running on battery, never when the charger was plugged in. I'm just waiting for my batt to charge back up to full, then I'll pull it off of the charger and see if it reoccurs.
JJRocker said:
Doubt it'll work. I've re-flashed the rom and the patch several times and it hasn't worked for me. FWIW, it does the same thing with Blackhole 4.2. The only thing that has worked for me is to go back to the original stock eb01 rom.
Also should probably mention I'm running the non-voodoo version. Anyone have any thoughts as to whether I'd have better luck with the voodoo kernel or would it make things worse.
Click to expand...
Click to collapse
FWIW, I am running voodoo. No dice. I had high hopes yesterday. But today is a different story.
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.
My Htc amaze 4g after one day or maybe less using is going automaticly shut down,,,and this is happening this few days...i want to know what the reason why it is shuting down everytime???(((
Sent from my HTC_Amaze_4G using xda premium
a little more info would be nice, are you stock? rooted? were you doing anything in particular when it shut down, like using any particular app?
just to clarify, does it shut down or does it reboot?
gogjhan said:
My Htc amaze 4g after one day or maybe less using is going automaticly shut down,,,and this is happening this few days...i want to know what the reason why it is shuting down everytime???(((
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Yes make it clear, shuts down or bootloops? My phone has shut down only once and i noticed was overheated...
This happend to me too. I just got an exchange and problem solved .
Sent from my HTC_Amaze_4G using xda premium
smatthew45 said:
a little more info would be nice, are you stock? rooted? were you doing anything in particular when it shut down, like using any particular app?
just to clarify, does it shut down or does it reboot?
Click to expand...
Click to collapse
noo stock 2.3 sense 3.0 rom)no im not doing anything at that time,,,for example ima putting it somewhere and then i come and i can see that it is shuted down,,,or in the pocket sometimes is shutting down and i cant receive calls,,,but when i bought it there wasnt such problem,,,i am using it 1 month,,,but i cant go change it because i take it from america to armenia)))!what to do can you help???
Factory reset is an option
Root, flash custom ROM
Flashing will increase battery life, and the responsiveness of your phone
Same thing happened to it kept doing it over n over T-Mobile didn't do anything they're gonna send u a battery. That's all I rooted flashed new rom n one of faux older kernels new ones not stable I'd say underclocked to 1188 n phones been running great and battery last me 10-12 hours which for anyone with an amaze knows that's alot lol
Sent from my HTC_Amaze_4G using xda premium
raiden9250 said:
Factory reset is an option
Root, flash custom ROM
Flashing will increase battery life, and the responsiveness of your phone
Click to expand...
Click to collapse
+1
this is what i would try if i were you
The same exact thing happened to me when my Amaze was new. It shut down on it's own almost daily, but sometimes it would take a few days until it shut itself off and I think it went as long as 4 days one time. My phone is stock. I thought about returning the phone, but never got around to it and now that I have had it for a few months it has just stopped shutting off on it's own. I don't think I changed anything, but the phone works perfectly now.
I wish I could give a definitive answer on how to stop the shut down's, but I tried various things and nothing seemed to help. Somehow it fixed itself over time.
j181 said:
The same exact thing happened to me when my Amaze was new. It shut down on it's own almost daily, but sometimes it would take a few days until it shut itself off and I think it went as long as 4 days one time. My phone is stock. I thought about returning the phone, but never got around to it and now that I have had it for a few months it has just stopped shutting off on it's own. I don't think I changed anything, but the phone works perfectly now.
I wish I could give a definitive answer on how to stop the shut down's, but I tried various things and nothing seemed to help. Somehow it fixed itself over time.
Click to expand...
Click to collapse
sometimes the kernel and rom even from the factory need a little time to settle
j181 said:
The same exact thing happened to me when my Amaze was new. It shut down on it's own almost daily, but sometimes it would take a few days until it shut itself off and I think it went as long as 4 days one time. My phone is stock. I thought about returning the phone, but never got around to it and now that I have had it for a few months it has just stopped shutting off on it's own. I don't think I changed anything, but the phone works perfectly now.
I wish I could give a definitive answer on how to stop the shut down's, but I tried various things and nothing seemed to help. Somehow it fixed itself over time.
Click to expand...
Click to collapse
Soo i dont need to flash new rom or delete all???)but i think mine get better,because it is almost two days that it isnt shutting down itself,,,but 4days later it shutted down in the night and the alarm didnt work and i get late from university))))what to do now ????((((
Sent from my HTC_Amaze_4G using xda premium
I'm in the same boat as the OP.
Bought the Amaze brand new and it would reboot itself 2-3 a day when it was just sitting on my desk at work or home.
I rooted it and removed the T-Mobile bloatware, made no difference.
I then put Bulletproof rom on it and made no difference.
I then put Faux123 kernal on it with the Bulletproof rom...no difference.
I got a new battery and it made no difference.
Phone just reboots 2-3 times a day. It locked up overnight last night and I overslept since I use it as an alarm too.
Dunno what else to do...
dnslammers said:
I'm in the same boat as the OP.
Bought the Amaze brand new and it would reboot itself 2-3 a day when it was just sitting on my desk at work or home.
I rooted it and removed the T-Mobile bloatware, made no difference.
I then put Bulletproof rom on it and made no difference.
I then put Faux123 kernal on it with the Bulletproof rom...no difference.
I got a new battery and it made no difference.
Phone just reboots 2-3 times a day. It locked up overnight last night and I overslept since I use it as an alarm too.
Dunno what else to do...
Click to expand...
Click to collapse
Mine get better itself,,,now it can be one week or more that it is not auto shutting down,,,!but i didnt do anything with it,,,!only deleted some programs but i dont thing that it was the reason of getting better)!WAIT and it will get better too)!
Same problem here, completly stock tmobile rom and kernel.
It seems to shut down by itself when its on a period of inactivity.
Will try rooting and flashing soon.
c4t said:
Same problem here, completly stock tmobile rom and kernel.
It seems to shut down by itself when its on a period of inactivity.
Will try rooting and flashing soon.
Click to expand...
Click to collapse
rooted and flashed rom with quicksense 3.0 and still shutting down by itself when not being used.
Will flash Amaze Kernel 008 and see if it solves the problem.
I will update soon
c4t said:
rooted and flashed rom with quicksense 3.0 and still shutting down by itself when not being used.
Will flash Amaze Kernel 008 and see if it solves the problem.
I will update soon
Click to expand...
Click to collapse
Changing from Stock kernal to Faux123's didn't resolve it for me either. In the Energy Rom thread a couple people said once they flashed his rom that their reboot's went away. I just flashed it today and we'll see what happens.
I'm still on Faux123's kernal with the Energy Rom. If it reboots still, I might switch back to Stock kernal with Energy Rom to see if that makes a difference.
Phone just locked up and rebooted using Energy Rom with Faux123 kernal. Just installed Stock kernal, we'll see what happens...
Well I'm stumped and frustrated. The Amaze is a great piece of hardware but it seems to have rebooting issues just like the LG G2x did.
I have the stock kernal with Energy Rom and I've wiped it and have no apps installed. And after a couple hours it still locks up and reboots.
I'm about ready to dump the phone.
No matter what kernal/Rom I use...it just reboots after a couple hours time...
Are you using any sort of task managers or probably a certain app causing it to reboot. Do a factory/data reset and don't install anything for 24hrs and see if the problems continue. Also, you should backup the contents of you external sdcard and re-format it. And do the same with your phones internal memory card. There could be a file on there (maybe from a previous Android Device) that is not cooperating with the Amaze. Just gotta figure it out. Good Luck.
Sent by accident from my Amaze using Tapatalk
dnslammers said:
Well I'm stumped and frustrated. The Amaze is a great piece of hardware but it seems to have rebooting issues just like the LG G2x did.
I have the stock kernal with Energy Rom and I've wiped it and have no apps installed. And after a couple hours it still locks up and reboots.
I'm about ready to dump the phone.
No matter what kernal/Rom I use...it just reboots after a couple hours time...
Click to expand...
Click to collapse
I don't know if T-Mo will see it this way, but assuming you take, or have already taken, Double0EK's advice above, I'd try to get T-Mo to replace it as hardware defective. I've had zero reboots and I ran stock for 6 weeks and the Energy ROM for nearly two.
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Seems like your system files might be corrupted. Wipe system partition from fastboot or cwm then reflash your rom. Any time I had weird stuff happen on a rom, I wipe the system then it goes away. Hope this helps you get rid of this issue. Good luck!
Sent from my MB860 on CM7.2.0 Stable
Doesn't work, just wiped system, cache and dalvik, then flashed rom and sod's still happen.
I have also tried flashing several radios, all with sod's. Any suggestions?
wakelock
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
affiatic said:
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
Click to expand...
Click to collapse
So you've had SODs since you got the phone? Wakelock seems to work, but kills the battery.
For anyone who does NOT have SODs what modem/radio are you using?
Yes had them since I got the phone. Wakelok fixed it for me. Battery life is not horrible. It still last me like 14 hrs moderate use. I have tried radios and everything else I could thing of. Think mine is hardware related. That is why I am sending it in. I was surprised to find out it was still under warranty
I've just noticed that when mine shuts down, it gives a green notification first, then when I try turning the screen it, it reboots.
Unfortunately, my phone is out of warranty, I bought it used
SODs still happen in airplane mode.
Try wakelock and post if that fixes it.
Call Motorola directly. I bought two used. Had the same problem. They replaced them both with new units.
Motorola Android Department
1-800-734-5870
Just don't say anything about buying it used.
Good luck.
As posted above, wake lock works but uses battery.
I live in Canada and am out of warranty, would I still be able to call?
It's worth a try. You have nothing to lose.
Sent from my MB860 using xda premium
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
javinavas said:
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
Click to expand...
Click to collapse
Is there something specific about 35C, and are you sure it is exactly that?
I have installed 2.3.6 Bell and I still get reboots, anyone have a link to stock 2.2.1 Bell SBF that I can try?
sometime 35 sometime 36.. but above that temp.. sod kills me.. under that temp phone runs smooth..
I'm a system enginner but I haven't program in years.. I'm thinking seriously in create just a services to read temp and launch a wake lock when temp reache some level..
I'm pretty sure I will help lot of people but aint sure when i can start doing some work
dancom96 said:
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Click to expand...
Click to collapse
my phone would not actually reboot but in went into SOD (sleep of death) so every time this has happened to me i installed a new kernel or reinstalled the one i had.........always rectified the issue.
Same issue
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
jediknightbrodie said:
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
Click to expand...
Click to collapse
Tried several of them, this seems to happen on stock 2.3.6 as well.
I flashed a stock sbf to return to stock. Still had the sleep of death. Reboots after and during phone calls, and touch screen problems. I believe it is hardware related.
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.