Related
Help! My phone is freezing / locking up and rebooting several times a day now!
I successfully did the stock AT&T Jellybean update this week when it became available via Kies.
I had no issues with the initial upgrade…it seemed to go smooth.
After a day…or a few hours….I can’t remember…I did start noticing a few issues with Touch Wiz closing or freezing and some other apps misbehaving. I can’t even remember what exactly the issues were.
I was also having some other quirky issues with the phone on stock ICS before the JB update…so I have been meaning to do a factory reset and reinstall everything.
So with the phone being even more flakey with JB I went ahead and did a factory reset with my new JB setup.
After a few hours setting up the phone with all my apps, settings, etc I noticed two issues. Swiftkey would not remain selected as my default keyboard and AT&T Voicemail viewer would not retain any of my account settings after a reboot.
After some Googling I learned that this is a know issue with JB 4.1.1 for many apps…they don’t quite install properly and something happens during shutdown that causes the settings to be lost. The only work around seemed to be:
Root Phone
Install apps
Backup with Titanium or other backup program
Uninstall apps
Restore apps – then they somehow install properly and work
I did this…first time rooting the phone….and the root and work around worked perfectly first time.
But after continuing to install apps and tweak my phone the real problems have now begun.
The phone is completely freezing at random times…in any app or in the TW launcher. It seems to just sit there frozen until I hold down the power key long enough to force a reboot or take out the battery.
There are no force closes or other error messages and I have found no other pattern to the freezes.
So now the phone is almost totally useless. It may work for a few hours…or just a few minutes before locking up. Worse…I have no way to know this has happened if the phone is in my pocket.
I did another full factory reset using the Recovery Mode and reinstalled everything again and am having the same issues.
I fear the root somehow corrupted my phone or one of my apps is totally incompatible with JB but I have to many (~70) it will be very hard to tell which one.
The other issue I am having is the battery is draining in just 4-5 hours even with light use.
Coincidentally….4G LTE was just turned on in my area this week so that would be a factor in both the battery drain and maybe even the lockups. I have a Microcell at home…wondering if 4G LTE and my Microcell are not behaving.
There are just too many variables with a new ROM (JB), fresh rooting of the phone plus recovery app installed, plus 70+ apps, plus new 4G LTE, plus my Microcell.
I don’t know what to try next to get the phone stable or to get the battery use reasonable.
Please post any and all suggestions….
One thing I’d like to clear up or eliminate is the root issue…is there any way that is the cause of my phone’s current problems?
What a mess of a week! Instead of the total awesomeness of JB, 4G LTE, and the fresh experience of using a rooted phone...all happening for me in the same week...I get a total headache and useless phone. Sure hope I can dig my way out of this.
Thanks for reading my long post!
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
wujiku said:
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Thanks for the ideas....had not heard of the "Hard Factory reset *2767*3855#"....how is that different from a factory restet initiated from winthing Android or from the recovery program?
Also - is there any quick / easy way to know which of my apps are supposed to be compatible with JB?
Sure will be a pain to reconfigure everything again.
Should I be safe installing my apps via Titanium backup restores? (as long as I don't restore data)
Also - what about restoring my IMs and call logs from Kies? Is that safe?
Boomer6345 said:
Thanks for the ideas....had not heard of the "Hard Factory reset *2767*3855#"....how is that different from a factory restet initiated from winthing Android or from the recovery program?
Also - is there any quick / easy way to know which of my apps are supposed to be compatible with JB?
Sure will be a pain to reconfigure everything again.
Should I be safe installing my apps via Titanium backup restores? (as long as I don't restore data)
Also - what about restoring my IMs and call logs from Kies? Is that safe?
Click to expand...
Click to collapse
Do you happen to have juice defender? I had the same problem, and noticed it only happened when I was on battery. I uninstalled that and it stopped rebooting.
stbtigerr said:
Do you happen to have juice defender? I had the same problem, and noticed it only happened when I was on battery. I uninstalled that and it stopped rebooting.
Click to expand...
Click to collapse
Nope....juice defender...
And my phone doesn't really seem to be rebooting....just freezing up. I have to force it to reboot by holding down the power button for 10 seconds.
About to try a fresh factory ROM install (pre-rooted) and a hard factory reset.
Then I'll add my apps back very slowly to see....
What a pain in the you know what!
wujiku said:
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Well...I did all that...and no luck. Still freezing up.
I could not actually do the exact *2767*3855# reset...the phone would not respond to that command. So I used CWM to format the SDCard and also did a factory reset there.
Reinstalled my apps carefully and without data restore...boom....phone is locking up all the time again after maybe 12 hours of good operation.
Either this build of JB is not working on my phone or it somehow got fubar'ed during that first upgrade.
My plan now is to restore to factory ICS un-rooted....reset the flash counter if possible....and return the phone under warranty if possible.
Any recommendations for this?
Got replacement phone - still freezing up!
Boomer6345 said:
Well...I did all that...and no luck. Still freezing up.
I could not actually do the exact *2767*3855# reset...the phone would not respond to that command. So I used CWM to format the SDCard and also did a factory reset there.
Reinstalled my apps carefully and without data restore...boom....phone is locking up all the time again after maybe 12 hours of good operation.
Either this build of JB is not working on my phone or it somehow got fubar'ed during that first upgrade.
My plan now is to restore to factory ICS un-rooted....reset the flash counter if possible....and return the phone under warranty if possible.
Any recommendations for this?
Click to expand...
Click to collapse
HELP!!!! Please!!!!!
I did a warranty RMA and got a new (refurbed) phone from AT&T. I set it up with stock ICS and it seemed to work fine. I installed CWM without rooting via ODIN and did a Nandroid backup. I then used CWM to load TWRP recovery and did a backup with that.
Then I loaded the stock JB room with root. Tweaked the phone and app settings a little and things seemed to be fine for 1/2 a day. I reinstalled TWRP since the ROM flash replaced it with stock recovery. Things still seemed fine.
So...with JB rooted and seeming to work fine....I booted into Recovery (TWRP) and did a fresh Nandroid backup since the phone was finally all configured and working (apparently).
Well after rebooting from the backup...the phone is acting all crazy again. It seemed to crash my home WiFi network....had to reboot my router. Now the phone freezes or locks up any time I disable WiFi or change WiFi settings.
I am just cursed with the GS3!
Two separate phones with stock AT&T JB with root...one running CWM Touch and the new one running TWRP and both lock up or freeze all the time.
Should I give up and try custom ROMs? Give up on rooting?
I want TouchWiz for SBeam and some of the Samsung apps that I like better than stock...would rather just stay stock with Root.
What can I do to get this phone stabilized with root and JB???
Just did another test...
If I leave my house and walk a couple hundred yards away...as soon as the phone finally loses the WiFi signal and disconnects it locks up.
Seems like all my issues (with first phone maybe too) are tied to WiFi.
Is no one else having WiFi issues with JB? Could it be tied to rooting somehow? For instance...maybe the stock rooted ROM has different modem or WiFi drivers...or different kernel than the actual stock JB ROM I first used via Kies update?
Boomer6345 said:
Just did another test...
If I leave my house and walk a couple hundred yards away...as soon as the phone finally loses the WiFi signal and disconnects it locks up.
Seems like all my issues (with first phone maybe too) are tied to WiFi.
Is no one else having WiFi issues with JB? Could it be tied to rooting somehow? For instance...maybe the stock rooted ROM has different modem or WiFi drivers...or different kernel than the actual stock JB ROM I first used via Kies update?
Click to expand...
Click to collapse
I've got the KIES JB Update, & rooted. I am not experiencing any of the issues your having. It might be helpful if you could post a list of apps & widgets that you have installed, If you have frozen or removed stock files.
It sounds like you may be experiencing some app conflict issues.
MasterDecker said:
I've got the KIES JB Update, & rooted. I am not experiencing any of the issues your having. It might be helpful if you could post a list of apps & widgets that you have installed, If you have frozen or removed stock files.
It sounds like you may be experiencing some app conflict issues.
Click to expand...
Click to collapse
I have not frozen any apps or done anything I would consider advanced or risky....
I tried running with what I thought would be just "safe" apps....no luck. I've got most all of my apps installed and did a Titanium Backup so here is a dump of all the user apps backed up:
Code:
cgeo.geocaching-20121219-204517.tar.gz
com.amazon.kindle-20121219-204309.tar.gz
com.amazon.mp3-20121219-204326.tar.gz
com.amazon.mShop.android-20121219-204301.tar.gz
com.anddoes.launcher-20121219-205011.tar.gz
com.anddoes.launcher.pro-20121219-205016.tar.gz
com.android.chrome-20121219-204524.tar.gz
com.ap.advml-20121219-204732.tar.gz
com.apksoftware.compass-20121219-204539.tar.gz
com.ArtInGames.AirAttackHD-20121219-204225.tar.gz
com.asksven.betterbatterystats-20121219-204516.tar.gz
com.att.android.uverse-20121219-204944.tar.gz
com.att.mobile.android.vvm-20121219-204953.tar.gz
com.att.um.androidvmv-20121219-204448.tar.gz
com.aws.android-20121219-204954.tar.gz
com.careerbuilder.SugarDrone-20121219-204718.tar.gz
com.devuni.flashlight-20121219-204654.tar.gz
com.dominospizza-20121219-204542.tar.gz
com.duduapps.craigslistfree-20121219-204542.tar.gz
com.ea.tetrisfree_na-20121219-204932.tar.gz
com.ebay.mobile-20121219-204552.tar.gz
com.espn.score_center-20121219-204826.tar.gz
com.evernote-20121219-204602.tar.gz
com.facebook.katana-20121219-204621.tar.gz
com.gamestar.pianoperfect-20121219-204756.tar.gz
com.google.android.stardroid-20121219-204659.tar.gz
com.greatclips.android-20121219-204659.tar.gz
com.imangi.templerun-20121219-204915.tar.gz
com.imdb.mobile-20121219-204702.tar.gz
com.instagram.android-20121219-204708.tar.gz
com.jawbone.companion-20121219-204719.tar.gz
com.joeykrim.rootcheck-20121219-204826.tar.gz
com.july.cbssports.activity-20121219-204649.tar.gz
com.kb.Carrom3D-20121219-204804.tar.gz
com.keramidas.TitaniumBackupPro-20121219-205010.tar.gz
com.lastpass.lpandroid-20121219-204723.tar.gz
com.maxmpz.audioplayer-20121219-204808.tar.gz
com.maxmpz.audioplayer.unlock-20121219-204825.tar.gz
com.meijer.rx.android-20121219-204730.tar.gz
com.melodis.midomiMusicIdentifier.freemium-20121219-204849.tar.gz
com.metago.astro-20121219-204444.tar.gz
com.mxtech.videoplayer.ad-20121219-204733.tar.gz
com.netflix.mediaclient-20121219-204744.tar.gz
com.outfit7.talkingtom-20121219-204911.tar.gz
com.pandora.android-20121219-204752.tar.gz
com.photox.touchwhiz-20121219-204212.tar.gz
com.q2e.unitedfcu5017android.ufcu.uwnmobile-20121219-204953.tar.gz
com.rovio.angrybirds-20121219-204333.tar.gz
com.rovio.angrybirdsspace.ads-20121219-204352.tar.gz
com.rovio.angrybirdsstarwarshd.premium.iap-20121219-204414.tar.gz
com.rovio.BadPiggiesHD-20121219-204449.tar.gz
com.s0up.goomanager-20121219-205017.tar.gz
com.shazam.android-20121219-204827.tar.gz
com.shotzoom.golfshot-20121219-204655.tar.gz
com.skype.raider-20121219-204832.tar.gz
com.smugmug.android-20121219-204847.tar.gz
com.spotify.mobile.android.ui-20121219-204855.tar.gz
com.thewolverine.app-20121219-204944.tar.gz
com.touchtype.swiftkey-20121219-204859.tar.gz
com.trimble.allsportle-20121219-204258.tar.gz
com.vp.alarmClockPlusDock-20121219-204255.tar.gz
com.weather.Weather-20121219-204938.tar.gz
com.yelp.android-20121219-204959.tar.gz
com.yum.pizzahut-20121219-204759.tar.gz
de.heimlich.gut.solitaire.hd-20121219-204847.tar.gz
eu.chainfire.triangleaway-20121219-204224.tar.gz
jackpal.androidterm-20121219-204224.tar.gz
la.droid.qr-20121219-204813.tar.gz
net.androgames.level-20121219-204515.tar.gz
net.zedge.android-20121219-205008.tar.gz
nl.rogro.GScriptLite-20121219-204702.tar.gz
org.wikipedia-20121219-204958.tar.gz
Having the exact same problems as you. Please help. I'm also considering giving the phone back at Best Buy and having them give me a new one with ICS and leaving ICS on there. My steps are very simple. I had the stock ICS ROM from AT&T and I used Kies to upgrade to stock JB. That's it, nothing else, no rooting, nothing.
I am seeing exactly the same behavior, when wifi switches to 4G or even sometimes when bluetooth comes on, etc I will see the lockup and hang. Have to hold down power button to restart. But I don't think this is completely the issue, because even if I turn off wifi, bluetooth and only leave on 4G, then I still will see random reboots, but a lot lot less frequent. Also, I have always had 4G and I see the battery only lasting 4-6 hrs, so I think this is normal with 4G. I saw this even with ICS.
I have not done any factory reset or anything - I would assume if you use the Kies s/w to update and it leaves your files and apps on there, then it should just work. But I will try the factory reset once I backup my contacts, etc.
I'm a little shocked that people are having this problem with a newly released ROM.
abhansali said:
Having the exact same problems as you. Please help. I'm also considering giving the phone back at Best Buy and having them give me a new one with ICS and leaving ICS on there. My steps are very simple. I had the stock ICS ROM from AT&T and I used Kies to upgrade to stock JB. That's it, nothing else, no rooting, nothing.
I am seeing exactly the same behavior, when wifi switches to 4G or even sometimes when bluetooth comes on, etc I will see the lockup and hang. Have to hold down power button to restart. But I don't think this is completely the issue, because even if I turn off wifi, bluetooth and only leave on 4G, then I still will see random reboots, but a lot lot less frequent. Also, I have always had 4G and I see the battery only lasting 4-6 hrs, so I think this is normal with 4G. I saw this even with ICS.
I have not done any factory reset or anything - I would assume if you use the Kies s/w to update and it leaves your files and apps on there, then it should just work. But I will try the factory reset once I backup my contacts, etc.
I'm a little shocked that people are having this problem with a newly released ROM.
Click to expand...
Click to collapse
After several re-flashes to stock JB with root and still more freezing with WiFi, etc....I gave up and loaded a custom ROM this morning.
I'm running BlackJelly...and after about 8 hours it seems be be running great so far. It is TW JB-based...and having very few issues with it. Battery is poor but it takes a few days of charging and use I guess to get the battery / phone / ROM calibrated. AT&T Visual Voicemail is not working and the phone shows H instead of 4G LTE...but I'm sure I can fix those issues by searching through the hundreds of thread pages on that ROM is this forum.
Give it a try before you switch to ICS or trade in the phone. You can always flash back to stock un-rooted and use Triangle Away to reset flash counter.
Good luck!
Still stuck with crashing phone!
Boomer6345 said:
After several re-flashes to stock JB with root and still more freezing with WiFi, etc....I gave up and loaded a custom ROM this morning.
I'm running BlackJelly...and after about 8 hours it seems be be running great so far. It is TW JB-based...and having very few issues with it. Battery is poor but it takes a few days of charging and use I guess to get the battery / phone / ROM calibrated. AT&T Visual Voicemail is not working and the phone shows H instead of 4G LTE...but I'm sure I can fix those issues by searching through the hundreds of thread pages on that ROM is this forum.
Give it a try before you switch to ICS or trade in the phone. You can always flash back to stock un-rooted and use Triangle Away to reset flash counter.
Good luck!
Click to expand...
Click to collapse
Well...after over a week of trying it out....BlackJelly did not help me. Still had freezes / lock-ups.
I can't tell if the phone is re-booting itself or just re-launching the Launcher (I us Nova but tried stock and Apex too). The phone appears to re-boot on it's own but the up-time under status would not reset...making it seem like not a re-boot but a launcher reload or something. Pretty much same issues as with stock JB.
So I gave up and tried CM10.1 nightlies....and wow....crashing all the time now. Whereas stock JB and BlackJelly seemed to crash when I left my home or left any WiFi network or even just when I disabled WiFi while connected....CM10.1 crashes all the time while at home seemingly at random. I can get 5 hours of great use...then have it crash 5 times in an hour. Seems to crash a lot in the settings menus.
This is with my second (replacement) phone. I am just cursed!
How do I effectively use a LogCat app or something to find out what apps or services or whatever are crashing my phone? Help!
Read through this whole thread and no where did you ever mention clearing your cache. Clear your system cache/davlik cache and reboot.
cjranucci said:
Read through this whole thread and no where did you ever mention clearing your cache. Clear your system cache/davlik cache and reboot.
Click to expand...
Click to collapse
Sorry...should have mentioned that. I've cleared the system and davlik cache many times...before and after flashing. I've done full system wipes / resets, formatted my SD card...everything I can think of.
I either have a rouge app that I seem to install right away after clean flashes....or a rouge Wifi router in my house that messes up my phone even when I leave and use other networks...or a rouge ATT&T microcell that does the same....or a rogue LTE area in West Michigan....
Or a second bad phone sent from AT&T. But no form of JB seems to work for me no matter what. Guess I could run a clean install with no apps for several days...and then add in an app a day for the next 2+ months until I find the bad app...if that is even the case.
So bummed with this mess!
My phone freeze after rotation on landscape only with JB. all kind roms of JB stock, cyanogen,, aokp.
makamobile said:
My phone freeze after rotation on landscape only with JB. all kind roms of JB stock, cyanogen,, aokp.
Click to expand...
Click to collapse
Interesting....that might be what I was experiencing....but I never thought that was it....did not notice that cause/effect.
I gave up and went back to stock / rooted ICS / TW...version LH9. Loaded it yesterday and have had 24 hours of great use...no issues.
I miss JB and Google Now...but at least my phone works!
I'm not sure for stock JB but on other ROMs, you could try changing your governor and scheduler.
BWolf56 said:
I'm not sure for stock JB but on other ROMs, you could try changing your governor and scheduler.
Click to expand...
Click to collapse
When on CM10.1 I tried bumping the minimum CPU speed to 484 and 5xx (can't remember the actual numbers)....and the maximum CPU speed to to 14xx and 13xx (again, can't remember)....and this did not help.
Not sure if that is what you meant tho.
Anyway...I gave up and went back to rooted stock ICS (LH9) and the phone is working great. I've given up on JB for now. I will wait for a new major JB release from Samsung before I try again.
copy paste from gs3 verizon forum
Q: The phone keeps freezing when I go into landscape mode.
A: This has been covered many times in the thread, but to reiterate: If you are using the AOSP lockscreen you must disable "Ripple Effect" in Settings -> Lock Screen -> Lock Screen Options
Hi,
I bought my Note 2 about 2 weeks ago and kept it to OTA Updates, until recently updated via ODIN and CWM to a few different Original Custom FWs (PA3, RootBox, Carbon, ETC)
Thing is, i like charging my phone overnight, and it just freezes right when i plug it into the charger if the phone is turned off, even if it's on the power block that came with the phone box or via any usb port in my computer.
I've read that it's the kernel, but i've tried many kernels (perseus, limaro, neak, etc) and it always freezes. Also tried different base (official stock roms from sammobile, but i confess i haven't tried charging with stock because i always root it, and cwm it and custom rom it right away, i have no plans on coming back to stock)
I know this is no dealbreaker, but i'd like to be able to do it, since i only like to charge the phone once in a day, and it's when i'm sleeping.
Appreciate any help, thanks in advance.
Bump!
Factory reset.
this is XXXDDDAAA
Try to Charge with any other power adopter. QUOTE=Sojiryu;39628968]Hi,
I bought my Note 2 about 2 weeks ago and kept it to OTA Updates, until recently updated via ODIN and CWM to a few different Original Custom FWs (PA3, RootBox, Carbon, ETC)
Thing is, i like charging my phone overnight, and it just freezes right when i plug it into the charger if the phone is turned off, even if it's on the power block that came with the phone box or via any usb port in my computer.
I've read that it's the kernel, but i've tried many kernels (perseus, limaro, neak, etc) and it always freezes. Also tried different base (official stock roms from sammobile, but i confess i haven't tried charging with stock because i always root it, and cwm it and custom rom it right away, i have no plans on coming back to stock)
I know this is no dealbreaker, but i'd like to be able to do it, since i only like to charge the phone once in a day, and it's when i'm sleeping.
Appreciate any help, thanks in advance.[/QUOTE]
UtkarshGupta said:
Factory reset.
this is XXXDDDAAA
Click to expand...
Click to collapse
I did, CWM Fatory Data/Cache Wipe and didn't work, not sure if it's the same from the rom factory reset option, willing to try (and reinstall everything from scratch) if you or anyone confirms this.
Thanks.
jdomadia said:
Try to Charge with any other power adopter.
Click to expand...
Click to collapse
I did, Doesn't work with the original, or with any other, or USB to PC, just freezes, however it works on stock rom, just not any custom rom.
Thanks.
Try a super wipe and flash back stock rom. We need to cross out custom roms.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Try a super wipe and flash back stock rom. We need to cross out custom roms.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
It charges while off on Stock ROM just fine, Just not on ANY CUSTOM 4.1.2/4.2.2 AOSP/AOKP, went to stock and came back to, say Carbon, or Rootbox with no luck, Still unable to charge while off,
Try not to undervolt it...when you try to undervolt too much there will be freezes when you lock the screen.. i had the same problem..
Thats my advice..
Make full wipe and install a custom rom..at the very first boot..try to access to stweak...grant it root pernission...and overvolt every cpu frequency step by+50mV.
Give it a try...i hope i helped you...ifbyes ..plz hit the thanks button..
If you have further question...feel free to pm me..or start a new thread.
Sent from my GT-N7100 using xda premium
It just started happening to me a few days ago on Jedi Master ROM... was working fine for about a month... if the screen stays off for a while or if it's charging for awhile it locks up... have to pull the battery
Have the same problem on slimbean 4.2.2 rom
Wysłane z mojego GT-N7100 za pomocą Tapatalk 4
Similar problem here, whenever screen is off for more than 8 seconds it will not wake up... Any ideas? I am trying stock roms and others, no solution so far...
Same problem with my GT-N7100.
I've tried both CWM & TWRP. It happens after flashing stock ROM to any of 4.3 AOSP based (CM10.2, ReVolt, Carbon, AOKP). When I'm trying to charge in power-off state, empty battery with white circle on center appears and freezes. Device doesn't charge and the only way to boot something (recovery/bootloader/system) is to reinsert the battery.
Changing build-in kernel to N.E.A.K. didn't help either.
I'm out of options. Please help :crying:
Happened here exactly after downgrading from 4.3 custom back to stock Samsung ROM. Of course lost IMEI but I managed to fix it and after applying ARIZA patch all worked well, however I flashed another stock, bit never and freezing started... Out of options so far as well. I will keep trying.
EDIT: Tried suggested in another thread RECOVERY software, however ODIN fails on sboot.bin every time...
My guess - trouble is in AOSP kernel. For example, if you install any AOSP based ROM and then install N.E.A.K. v2.2x SAMSUNG FW kernel (for TouchWiz) - problem goes away. You can't start ROM after that, but that's not the point.
I think we should post our issue in some kernel development discussion, like N.E.A.K. and hope they find solution.
btw 4.2 and 4.3 ROMs both has that issue.
mellax said:
My guess - trouble is in AOSP kernel. For example, if you install any AOSP based ROM and then install N.E.A.K. v2.2x SAMSUNG FW kernel (for TouchWiz) - problem goes away. You can't start ROM after that, but that's not the point.
I think we should post our issue in some kernel development discussion, like N.E.A.K. and hope they find solution.
btw 4.2 and 4.3 ROMs both has that issue.
Click to expand...
Click to collapse
---------------------------------------------------------
Just installed Omnirom 4.4.2 on my Note 10.1 (2012) and am having the same issue. As soon as I dock it / charge it when locked, can't unlock and it appears to crash. I did not have this issue with stock.
Any further progress?
Thanks in advance.
Anybody ever found a solution for this? My note 2, N7100 hangs if charged when switched off.
Only when switched off, I shows the battery with the white circle and that's it.
AOSB KK 1.3.6, 4.4.4, krn 3.0.64-CM, latest modem, TWRP etc.
Brammieman said:
Anybody ever found a solution for this? My note 2, N7100 hangs if charged when switched off.
Only when switched off, I shows the battery with the white circle and that's it.
AOSB KK 1.3.6, 4.4.4, krn 3.0.64-CM, latest modem, TWRP etc.
Click to expand...
Click to collapse
Try Resurrection Remix 4.4.2 KitKat v5.1.5 They fixed it somehow.
plz help
I have note 2 its all fine
but when i turn the screen off for a while the phone freeze and not turning on unless i unplug and replug the battery
this thing happens even in the charger i tried replacing the battery but the same thing
any ideas
So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated
Was the problem present on the stock ROM?
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.
Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
gasburger said:
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
Click to expand...
Click to collapse
Same problem. Did you solve this problem?
Has anyone found a permanent solution to this? Or at least a reason? My op 5t also stops responding randomly to the touch. This is really bad.
I also have this problem as well. It seems that many users have this issue. OnePlus should take a close look at it
I have been having this issue for more than 6 months. The problem came after one update during android Oreo if not mistaken (Which update i can't remember)
For my phone, the screen will be unresponsive during the below occasions:
1. After rebooting the phone, touchscreen is unresponsive for up to a minute
2. When browsing pictures in gallery
3. When taking picture using portrait mode
4. When google play is updating apps
5. When google photo is backing up photos.
I am also doubting if is a hardware or software issue, because it only happened in some occasion previously for my case. Tried wipe and install stable/open beta a few times, same thing.
After the latest open beta update, it got even worst, other than the above occasions, the screen start to stop working randomly (be it watching a youtube video or using chrome), its getting annoying as i need to restart my phone a few times a day.
I saw alot of people having this issue, but has yet to raise concern of OnePlus.
I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing lineage didn't help. In the end I somehow got it to work again by flashing the last open beta - but even then it didn't work right after flashing it, I had to leave it over night then it mysteriously started responding again in the morning.
I've just had it happen again and I have tried removing the screen protector and completely discharging the battery as some people on the oneplus forum have reported this helps, but it did not work for me. I really can't be bothered going through the whole process of re-flashing open beta then flashing back to lineage and installing all my apps an restoring my data again, but the only other option at this point is to try take it apart to check the screen is still connected to the motherboard properly....
solution
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
karyy said:
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
Click to expand...
Click to collapse
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Facing same issue..
I have a similar issue too..
It started several months ago, when the screen used to randomly stop working, a quick hard reboot usually solved the issue.
But about a month ago, the screen stopped responding altogether and any amount of reboot did not work. So too the device to Oneplus service, there they flashed it to 9.0.7, and the screen started working again, and continued working for a few more hours, until it stopped responding again.
Tried flashing several times using the unbricking tool, but all efforts in vain.
Finally after a month or so, I bought a new phone, and today I just wanted to see if anything has changed on OP5T, and to my surprise, the touch screen started working again.
So this time I enabled USB Debugging, permanently enabled OTG, so that even if the screen stops working, I can use an external keyboard/mouse.
But OP5T is no longer my primary device, and hence I have moved on to a different manufacturer, as I saw absolutely no point in buying another Oneplus and god knows what will happen a year down the line...
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
chandle-stick said:
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
Click to expand...
Click to collapse
I had the problem. Had to send it back to OnePlus. They replaced the cpu under warrenty. Call 0neplus.
i have this problem on LineageOS 16, in stock is good
k-ninja said:
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Click to expand...
Click to collapse
I was just searching this issue online. I'm currently facing it as well.
Rebooting the phone makes it go away. I face this issue while charging the phone via official dash charger.
I'm running stock Oxygen OS 5.1.7 running Oreo 8.1.0. I faced this issue 6-8 months ago as well. I cleared 7gb free space in my phone then it started working fine then. My device is 64GB variant. I never updated to Android Pie.
This is a major problem in OnePlus 5 and 5t. I've seen many posts on both XDA and official oneplus forums but found no guaranteed solution so far. I was thinking of flashing custom kernel but then saw here that people are still facing this issue in custom ROMs.
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
k-ninja said:
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
Click to expand...
Click to collapse
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
archz2 said:
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
Click to expand...
Click to collapse
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
archz2 said:
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once the screen works again. I managed to get to about 6 hours of normal usage last night before the screen stopped responding again - after fighting with the phone all day and most times not getting much past installing magisk modules.
I am starting to think the problem is related to either Magisk, or the riru kernel hooking modules necessary for Xprivacylua (which is mandatory to install IMO) - I had been using the YAHFA module mostly but yesterday I tried Sandhook to see if it made any difference - that was when I managed to get to 6 hours instead of 30 minutes, but it was also when I went back to Magisk 19.3 instead of installing 20.2. Now that I think back, I am wondering if it was upgrading Magisk from 19.x to 20.x that made the issue resurface after a couple of months without it.... Can't remember for certain, but it seems like the most plausible explanation. I tried flashing Magisk uninstaller this time when the screen stopped, but it didn't help - only reflashing back to stock works (sometimes it even takes a few goes). Whatever the problem is, it seems like it is tripping some hardware related switch which only gets reset when installing stock FW.
the other thought I had was that perhaps the hooking framework is getting in the way - like it intercepts the screen touches before they are processed, but it bugs out for some reason and they never get passed on to the OS. I don't know enough about how it works honestly, or any idea how to go about debugging such a weird problem, so no way to look into it.
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
I'm close to my wits end here. IF the problem turns out to be magisk related, it's pretty much new phone time - I doubt even if I logged a bug report it will get looked at any time soon much less resovled, and I simply refuse to run an android phone without xprivacylua.
k-ninja said:
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
Click to expand...
Click to collapse
Edexposed is for Pie ROMS as there's been no development for Pie from official developer for xposed. Chances are you were running xposed only on Oreo 8.1.0.
Today I flashed Franco Kernel on my phone, been running smooth so far. I used to get non-responsiveness while dash charging specifically. Let's see how it goes. Will keep you updated.
Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again.
This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually started installing magisk, riru, edexposed, then finally xprivacylua - Didn't have any problems up to there. Then I installed pico gapps, and used the Play store to do a fresh install of Mobius Final Fantasy instead of restoring from Titanium backup (this game is actually the only real reason I need gapps at all :-/). Mobius is a PITA because its like a 5Gb download, so it takes a long time to reinstall rather than restore from TB. Anyway it seemed like it was working ok for a few days after the fresh install but I just picked up the phone as couldn't unlock it. I have noticed that often the problem does occur while I am playing the game and I have wondered if there is something about it which makes it more likely to trigger, but it can't be the only thing as it happens even during the setup wizard sometimes.... bloody infuriating.
Anyway... not sure what to do now. Really CBF going through the back-to-stock dance again. Meh.