It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance ?
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
dodjob said:
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance
Click to expand...
Click to collapse
Hmm, i will try this when I get home from work, thanx.
Benjamin_L said:
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
Click to expand...
Click to collapse
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
minnuss said:
Hmm, i will try this when I get home from work, thanx.
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
Click to expand...
Click to collapse
Let us know!
dodjob said:
Let us know!
Click to expand...
Click to collapse
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
minnuss said:
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
Click to expand...
Click to collapse
That sucks big time ? the only time I got a freeze was as I wanted to empty chrome beta cache. After the reboot, all went back as it should be...
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
minnuss said:
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
Adb root shell. Can't think of a way this could damage anything if you just set the one property
hacktek said:
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
Click to expand...
Click to collapse
Did you have device rooted for a while, or it was always stock ?
Benjamin_L said:
Adb root shell. Can't think of a way this could damage anything if you just set the one property
Click to expand...
Click to collapse
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
minnuss said:
Did you have device rooted for a while, or it was always stock ?
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
Click to expand...
Click to collapse
It's always been stock.
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
kaiwanted said:
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
Click to expand...
Click to collapse
Yes this happens when lots of I/o is done on the internal disk. I hope this is just a missing optimization and not a hardware issue. But let's bug xiaomi with it. I assume you also have the 64GB version?
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
I read a lot regarding how people brick their phone with TWRP and rooting, so for now I will not use this future. But to reset my phone I will think about. Anyway I need this phone to use all my applications, not only a couple of them, because of this freezing (.
Thanks for suggestions.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
kaiwanted said:
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
Click to expand...
Click to collapse
I did the same thing. Went through my application list, uninstalled everything I didn't need and the issue went away. I cleared like 5% of storage space with still over 50% left but it seems to have helped.
reflashed all stock, enabled camera 2 api using mi a2 toolkit (magisk method) and I have the same. Cleared everything and run flash_all.bat. enable cam 2 api again and still have the same issue. clean install of apps doesn't fix it. Any idea on how to fix the sudden freeze?
Thanks
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
if I completely root the device, I will still have the random freeze?
also, if I factory reset the device in the settings, the camera 2 api will be gone? thanks
minnuss said:
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
I did it via twrp and adb shell setprop persist...
No issues here at all.
Related
Hi guys I need some help. I just wiped my phone and restored it back to factory and I'm getting
Unfortunately, the process com.android.phone has stopped.
Click to expand...
Click to collapse
everytime my phone boots up. This happened as soon as it booted up right after I reset it and it's happening every single time now. It happens EVERY boot, exactly 2 times. It will freeze up my lock/home screen temporarily and give me the error message. After it displays it twice then everything goes back to normal working order and I am able to make phone calls etc.
I do think I f'd up somewhere messing with xposed installer and the wanam module. My phone would go into boot loops when I had it previously set up so this is why I reset it.
It IS rooted. Factory kernel/rom (I don't think it's possible to change them at this moment but please correct me if I'm wrong.) I tried wiping cache and still nothing. Everything in Titanium backup is defrosted meaning its all there except for the things that I uninstalled on my last setup but I was caeful not to remove anything important (only At&t bloatware). Also I did have 'App Ops X' installed and it's installed now.
So please help if you can and thanks in advance.
Fixed!!!
Not sure how exactly but I went into Titanium Backup and disabled a bunch of things that I wouldn't use. I get no errors now. Might be disabling of the 'Knox' that fixed it, who knows.
Thanks for the update,
I wasn't receiving this everytime like you were but I was getting it every so often. I tried using Titanium Backup to freeze some unwanted crap also and I haven't seen the Error since.
Don't know what we got rid of but it works lol
the_real_vlad said:
Fixed!!!
Not sure how exactly but I went into Titanium Backup and disabled a bunch of things that I wouldn't use. I get no errors now. Might be disabling of the 'Knox' that fixed it, who knows.
Click to expand...
Click to collapse
hi can you please share what you disabled
thanks
d3aded said:
hi can you please share what you disabled
thanks
Click to expand...
Click to collapse
Hi,
I can barely remember but I did remove Samsung Knox and everything with 'knox' in it. I would freeze a few things at a time that you don't think you need and keep rebooting until it's fixed. I went through many trial and errors until I finally got it 100% working.
Wiping contacts storage data usually fixes it
RErick said:
Wiping contacts storage data usually fixes it
Click to expand...
Click to collapse
Hello. I have been getting this error after installing the latest polish update to 4.4.2
I have done hard reset a couple of time but the same thing.
Any ideas?
Also how do I wipe contacts storage?
RErick said:
Wiping contacts storage data usually fixes it
Click to expand...
Click to collapse
it did not work for me either
any other ideas?
I don't know if this will help..had this issue when I used Xposed module Flying Android ....it messed up my dialer with the same message...I uninstalled it and it works perfectly now.
Sent from my SM-P600 using XDA Premium HD app
Hi severybode
i have the same : http://forum.xda-developers.com/showthread.php?t=2568386
i think this is cause of my sim card !!! cause mine is 2G , anyway , if anyone knows that witch app should i freez please let me know .
your help is appreciated
thanks
100% is a sim related problem as if i boot up phone without sim i do not get any error.
Sent from my SM-N9005 using Tapatalk
yes , you right
but is works on 4.3
is it 4.4.2. bug ?
should i report it to samsung ?
So I successfully unlocked and rooted my phone with various methods because Boost Mobile didn't make it easy, and then managed to root via TWRP,
The reason why I rooted the phone is because I want to remove bloatware like Connection Optimizer and Boost Zone.
I got a hold of a root explorer copy and managed to delete the .apk files with their respective helping files.
On top of that, I got another application to remove the installed apps and it worked.
So, after a while of using the phone without a hassle, it just randomly turns off.
And when I boot it up again, the apps are back and more annoying than before.
I have no idea how to change folder permissions (I forgot, I did it once on LG Venice but that was a while ago)
And I really need help, the bloatware takes up to 2gb and its annoying with the constant bombardment of notifications.
Please, if you can, HELP ME.
CHR$+RND said:
So I successfully unlocked and rooted my phone with various methods because Boost Mobile didn't make it easy, and then managed to root via TWRP,
The reason why I rooted the phone is because I want to remove bloatware like Connection Optimizer and Boost Zone.
I got a hold of a root explorer copy and managed to delete the .apk files with their respective helping files.
On top of that, I got another application to remove the installed apps and it worked.
So, after a while of using the phone without a hassle, it just randomly turns off.
And when I boot it up again, the apps are back and more annoying than before.
I have no idea how to change folder permissions (I forgot, I did it once on LG Venice but that was a while ago)
And I really need help, the bloatware takes up to 2gb and its annoying with the constant bombardment of notifications.
Please, if you can, HELP ME.
Click to expand...
Click to collapse
Have you flashed a kernel with write protection removed? http://forum.xda-developers.com/showpost.php?p=57174863&postcount=1
I've got the BOOST as well and that kept the bloatware off but occasionally they will try and re-download from the Play Store so I had to turn automatic updating of apps off and update apps manually as they come.
EDIT: I was waiting for my new user time limit to submit this. Didn't see the exact same answer posted above. That kernel worked for me (Boost 510). The later ones with performance enhancements did not. I am now bloat free.
emaggot said:
EDIT: I was waiting for my new user time limit to submit this. Didn't see the exact same answer posted above. That kernel worked for me (Boost 510). The later ones with performance enhancements did not. I am now bloat free.
Click to expand...
Click to collapse
I have that already flashed, that's the one I posted. I've now got just a base system by uninstalling EVERYTHING you can imagine. I'm just saying occasionally it would try and re-download some apps but now I've got automatic updating turned off it doesn't do it anymore.
dipspit said:
Have you flashed a kernel with write protection removed? http://forum.xda-developers.com/showpost.php?p=57174863&postcount=1
I've got the BOOST as well and that kept the bloatware off but occasionally they will try and re-download from the Play Store so I had to turn automatic updating of apps off and update apps manually as they come.
Click to expand...
Click to collapse
This method didn't work out, every time I do the command it either doesn't go through or fastboot stops responding.
CHR$+RND said:
This method didn't work out, every time I do the command it either doesn't go through or fastboot stops responding.
Click to expand...
Click to collapse
Your phone has to be in FASTBOOT not the os, but I assume you know that. Try adb kill-server and then adb start-server and then do the fastboot flash boot b.img or turn the computer off and turn it back on and try again. I've had this problem a couple times, these two methods worked.
dipspit said:
Have you flashed a kernel with write protection removed? http://forum.xda-developers.com/showpostphp?p=57174863&postcount=1
I've got the BOOST as well and that kept the bloatware off but occasionally they will try and re-download from the Play Store so I had to turn automatic updating of apps off and update apps manually as they come.
Click to expand...
Click to collapse
I did this and it worked. However, the ability to change cameras is now missing. I had an option where I could change to front camera and now no camera app I get gives me the option to switch.
CHR$+RND said:
I did this and it worked. However, the ability to change cameras is now missing. I had an option where I could change to front camera and now no camera app I get gives me the option to switch.
Click to expand...
Click to collapse
Yeah, the dev's are looking into it. It's a known issue.
Was handing off my phone to my son, moving on to an LG G2, I let him test it out under my account, he added his account and phone was a little sluggish since the extra account was taking up more RAM, so he hands it to me while I was in bed and needs help, I factory reset it thinking it would just wipe out my personal data and allow him to enter his, well it did, but now he lost Root and I am stuck on the 1st nightly with memory leak...
Any method available to reroot this phone when in 5.0 so I can continue upgrading with nightlies? Or am I in a world of hurt now?
Justatechie replied in another thread, THANKS!!
Thats not going to work, it only works with the stock atrix hd 4.1.1
Cm12 can be rooted by going into developer options on the phone,
under root access (its disabled by default)
Just tap on it and allow apps or app and adb and it should be all set.
Other people prefer to flash supersu by going into recovery, just download the latest and put it where you will find it when you use the recovery.
I completely forgot about that, I had enabled developer mode, but nothing else, thought the reboot into advanced options was default, which it was not and slightly had a panic attack.. Thanks for the save...
Running apps stay running after a flash...
First thing odd I noticed, after giving him my phone and his adding his apps, is that when you click square to see running apps and click the 3 bars to turn them all off, they do not turn off, you have to swipe each one off now.
When I had the phone that process would end all apps I had started, now they stay on unless you swipe them off.
Also, after flashing the update to latest nightly, all the apps that were running before I flashed it and entered recovery to perform the flash, were running again upon a reboot. I have never seen this on any build, don't know if it is one of his apps causing this or what??
And I cleaned cache, cleaned dalvik, flashed both zips, cm12 and gapps, then cleaned cache again as instructed in the 5.0 threads.
I tried to see if it would happen again so I opened 3 apps, then performed a reboot, after phone rebooted, clicked the square and those same 3 apps were active...
What may have caused this?
Factory reset may have some bug as the phone was performing normally before I used that method to clear out my user data.
And if I ever decide to part with the phone I would expect that feature to work or I would be forced to keep it...
sobitthen said:
First thing odd I noticed, after giving him my phone and his adding his apps, is that when you click square to see running apps and click the 3 bars to turn them all off, they do not turn off, you have to swipe each one off now.
When I had the phone that process would end all apps I had started, now they stay on unless you swipe them off.
Also, after flashing the update to latest nightly, all the apps that were running before I flashed it and entered recovery to perform the flash, were running again upon a reboot. I have never seen this on any build, don't know if it is one of his apps causing this or what??
And I cleaned cache, cleaned dalvik, flashed both zips, cm12 and gapps, then cleaned cache again as instructed in the 5.0 threads.
I tried to see if it would happen again so I opened 3 apps, then performed a reboot, after phone rebooted, clicked the square and those same 3 apps were active...
What may have caused this?
Factory reset may have some bug as the phone was performing normally before I used that method to clear out my user data.
And if I ever decide to part with the phone I would expect that feature to work or I would be forced to keep it...
Click to expand...
Click to collapse
Apps will continue to run if you reboot. This is not a bug but a feature from Lollipop
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Sorry I don't have a solution but I just wanted to bump this thread because I'm having the same issues as you. Wakelock detector also gets stuck on loading screen and supersu fails to open.
vahx129 said:
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I also had the same issue. I am using the image with busy box and Xposed framework installed. After a an hour or so super user said that the binary was not installed, and most of my root apps stopped working. Root checker said my Turbo was not rooted, though gravity box and a few other Xposed modules continued to work. I rebooted the phone, but had the same problem. I turned notifications for the supersu app back on, and after about a minute it said the binary had to be updated, and I had root again. I'm not sure what is going on, but I will come back if I find anything
I'm not having any issues. I would reboot the phone into recovery and wipe the cache there. Hope that helps.
Glad I saw this thread...I'm having the exact same issue!
A hard reboot will solve the problem every time...but its quite annoying...
I'm going to try a factory reset and see if that helps
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Seems to have resolved itself
I just wanted to mention that between clearing the cache and flashing a different rooted image this issue appears to have resolved itself.
I will update after some time to see if this fix maintains or if anything else pops up. Thanks for the suggestions!
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
What cache did you clear? I tried to clear the cache from the recovery, but my phone freezes and I have to reboot. Then I loose root a while later.
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
I cleared cache in recovery...didn't help...gonna have to try a factory reset
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk