back button does it's own thing - Sprint Samsung Galaxy S III

while using my phone, my back button will light up, vibrate, and just do its own thing. open multi window. take me out of apps. just goes crazy. anyone else have this issue?

What Rom are you running ? What Recovery ? Did you do a Clean install of the Rom ?

No matter what rom. It takes about 12 hours after install. Yesterday I woped everything, data, everything and no problem. Woke up this morning and it started doing it again.
galaxy s3 running supernova or goodness......

Try going back to stock unrooted...if the problem persists, unfortunately, it's probably hardware related
Sent from my S3 on Sense 5 (you jelly?)

duncakes said:
No matter what rom. It takes about 12 hours after install. Yesterday I woped everything, data, everything and no problem. Woke up this morning and it started doing it again.
galaxy s3 running supernova or goodness......
Click to expand...
Click to collapse
By wiped everything do you mean : system - data - dalvik cache - cache - factory reset ? If the answer is yes then I'd suggest trying what CNexus posted.
TEAM MiK
MikROMs Since 3/13/11

Related

[Q] G2 Stuck on CM Splashscreen on Reboot(CM7 Stable)

Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
SpeedBlue47 said:
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
Click to expand...
Click to collapse
Have you tried a full wipe and then reflash? What rom did you come from? A few details about those things might make it easier for people to help u
dont send me pm's crying about how i hurt your feelings in a thread
I came from the stock post-ota ROM. I did a full wipe when I installed RC4, but I haven't since, just wipe data then re-flash. Should I wipe everything - data, cache, dalvik, etc and then re-flash? Of course Nandroid before...
just cache and dalvik was enough... no data wipe needed (at least.. I haven't needed that before)
But I still need to re-flash the ROM after I clear cache and Dalvik though, right?
Well, apparently, that worked out. Everything is humming along just fine. Thanks a lot for the help everyone.

[Q] Liquidsmooth ROM 2.9 and gapps-jb-20130301-signed causing frequent freezes

Hi,
I have been using custom roms for a while on my note II N7100. From my last rom my phone was restarting on its own at least once a day and complete freezing quite a few times. Only solution was to reboot the phone by holding the power button for few seconds, nothing else would work. Even tried leaving the phone for 10-15 minutes however it did not help.
I was using Carbon Rom earlier. I changed Liquidsmooth 2.9 however the same thing happened. In fact the frequency increased with Liquidsmooth. I was worried about a hardware problem as even after complete wipe and with different rom same thing was happening.
I decided to perform a complete factory reset, wipe cache/dalvik cache. After flashing liquidsmooth 2.9 I did not flashed the gapps, used the phone for couple of hours and things were fine. After I flashed the requied gapps - gapps-jb-20130301 - same thing started happening.
Somebody please let me know if I can flash the earlier version of Gapps or later version if available.
Regards

Strange occurence of phone constantly restarting.

Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
At first it sounded like sudden death syndrome (a power button failure) but when you said turning off 4G fixed it that is very weird. Have you tried asking in the M.O.A.R thread?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Sprint Evo 4G "OG"
Stock - Cyanogenmod 7 - MIUI - Swagged Out Stock
Hit That "Thanks" Button if I Helped You!
Could be your kernel. Or any kernel tweaks you are using
joebeem said:
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
Click to expand...
Click to collapse
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
prboy1969 said:
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Click to expand...
Click to collapse
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
well, now it happened at home when turning on 4g... damn.
joebeem said:
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
Click to expand...
Click to collapse
joebeem said:
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
Click to expand...
Click to collapse
You did not mention wiping system. If you do not Wipe system, and also Factory Reset then it's really not a Clean install. I would still suggest a FULL Wipe, and Clean install. Then run the Device for a while without adding anything. See how it performs.
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
If you never wipe system you are definitely going to run into problems.
joebeem said:
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
Click to expand...
Click to collapse
You just do it in Recovery before you flash. If you look at my Sig on a PC / Internet Mode there is a link on how to do Full Wipe before flashing a Rom.
TEAM MiK
MikROMs Since 3/13/11

Phone rebooting every 2 minutes

Hey,
I have been using the ROM since version 1. I love it.
Two days ago, my phone suddenly started rebooting every 2 minutes. I re-installed the ROM after wiping everything (system, cache, internal memory, ...). This didn't help.
I have no idea what is causing that. It is driving me crazy.
Anyone knows what could be the reason?
Thanks
which ROM..?
Sent from my SGH-T999 using Tapatalk
mpharb said:
Hey,
I have been using the ROM since version 1. I love it.
Two days ago, my phone suddenly started rebooting every 2 minutes. I re-installed the ROM after wiping everything (system, cache, internal memory, ...). This didn't help.
I have no idea what is causing that. It is driving me crazy.
Anyone knows what could be the reason?
Thanks
Click to expand...
Click to collapse
I also am having the same problem reboot 3-4 times in a hour. first i thought it was the power. cleaned it but now it seem to always reboot coming up from sleep. .. I have try everything I can remember, wipe , reset, installing clean ROMs or changing recovery Tried New 4.3 roms and same ROM DocHoliday77 43 stock and i have us. Only have if you press the slee/power bottons
I have even changed recover
.. Help
Still it does not tell me what Rom has this issue and what Kernel ?
Based on what you have mentioned, I didn't see you mention anything about Restored apps.
Please do a System Reset and re-flash just the DocHoliday's Rom. Do not attempt to restore any apps. Please observe for a day or two to see if the problem recurs. If it does not then you can restore the apps one by one. Observe after each one to see if the problem appears.

Problem Booting

so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Are you still using the same version of TWRP you used to flash slimbean 4.1? If you are trying to flash newer ROMS with an older version of TWRP, that could be causing the problem.
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Try TWRP 2.6.1.0

Categories

Resources