Related
Disclaimer: did several forum searches and google searches and came up empty, so if I missed the exact wording and this is covered elsewhere please don't flame me into oblivion.
For some reason my Nexus One running FRF85B is unable to install or uninstall any apk's. It just hangs at the installing... or uninstalling... respectively. Has anyone else ever seen that?
Installing has always been really darn quick. Now it just appears to be hanging.
EDIT: Adding new symptom: "Manage Applications" shows the apps installed , but their space is forever listed as "Computing...". It's like the manage applications service is just hosed.
Randy
I have seen that as well. I would have to exit (back or home) then when I got back to the applications screen again it wouldn't have to load at all.
Same here, AT&T Nexus One using FRF85B.
The weird thing is, the app(s) actually DO uninstall or install correctly, just that the Market page shows it's not, and hangs at it.
When I force stop the market, then relaunch and check my downloads, they're now reset to the correct info.
Well I'm glad it is not just me. Thinking it was a bad ROM I reinstalled (with complete wipe) Modaco's ROM, then stock Froyo, etc.
Problem went away when I just said screw it and installed CM 5.0.8.
The only problem that persists now is the server error going to the downloads tab of the market. I can't seem to lick that one even though apps download and install fine from the market.
On a side note CM5.0.8 still is snappier than Froyo. I'm salivating at the thought of CM6.
If anyone is also getting persistent errors with the market downloads tab, please chime in. I find it suspicious that I'm having this problem regardless of which ROM is installed.
Sent from my Nexus One using Tapatalk
No matter what I do I still get the server error in the Android Market application when I go to the downloads tab.
I've re-flashed the Froyo Radio and tried both CM 5.0.8 and Froyo.
I don't see others complaining about this so I have to imagine there's something wrong on my end. I just don't know how to diagnose it. Does anyone have any ideas? At All?
Randy
nxt said:
Same here, AT&T Nexus One using FRF85B.
The weird thing is, the app(s) actually DO uninstall or install correctly, just that the Market page shows it's not, and hangs at it.
When I force stop the market, then relaunch and check my downloads, they're now reset to the correct info.
Click to expand...
Click to collapse
I did see that in the CM 5.0.8 ROM, but Froyo is a complete no-go. I've reflashed the radio, and have been using Modaco's ROM because it is the only one I know of that is just a rooted update I can flash with Amon-RA's recovery, but still no luck.
This is scary.
UPDATE
I went all the way back to Stock, Unrooted 2.1 from January, and still get the server error in the downloads page of the Market app. So for giggles, I wiped, created a new gmail account, and lo and behold, everything works. I could download apps, and they showed up in the download tab as installed.
That pretty much puts an end to thinking it's an app/ROM/radio problem, I think.
I then wiped again, went through initial setup with my primary Google account and I'm back to server errors on the downloads tab.
I guess maybe it really IS a server error. Don't know what I can do about it, except gripe...but at least I can stop scratching my head over what ROM/Radio is installed.
After several days of experimenting, the fact is that on any Froyo rom, whether it's stock or rooted, google's or cyanogen's, wiped or not wiped, new gmail account or existing gmail account, what I'm seeing is that, even if I wipe, go into Android and DO NOT enter a google account, going straight to settings | Manage Applications | running applications, shows "Computing..." forever.
Now, if I do a full wipe, it doesn't know anything about my account, right? And the cache, and all that are all wiped. So, what could possibly cause the infinite "Computing..." in the apps?
Does anyone know?
It happened to me as well last night. I was installing an apk (updating over an older version), and it showed "Installing...." forever. No hardware button gave me any response and I eventually had to reboot the machine by pressing the 3 buttons (luckily this worked. I really hate the thought of pulling the battery out...). After the reboot I tried again and it installed without a problem.
I m on a stock Nexus One FRF91, never hv an issue b4 that latest system update. Looks like it is bringing more issues to me...
what 3 buttons reboot the phone?
The same thing is happening to me. When trying to install any market app, it just hangs at "installing. I have to reboot the phone to get it to stop doing it.
Every once in a while, about 1 out of 15 times, I can get an app to install correctly and quickly, but all the other times it hangs.
It started happening when going to froyo. I have tried several different froyo mods and the same thing happens on all of them. When I nandroid back to 2.1 it is fine.
It happens to me with the Rodriguezstyle mod, the Kang-O_rama mod and the evil n-one shot Noir mod.
In order to fix this issue. You MUST do the following steps:
1. Wipe the SD card.
2. Wipe ext partition (if there)
3. Delete spareparts if you have it ANYWHERE on the system
4. Reboot the system into recovery
5. Wipe all cache's
Tada! Fixed!
This fixed it for me on Kang-O-Rama.
I belive the problem is when moving ROMs and the new app2SD feature stores files on the SD. When moving ROM's, it try's to scan them but fails. Something is stuck in a loop and wont stop .
When taking out the SD card, it ALL works flawlessly (give it a go if you need to install some apps to help)
rmagruder said:
what 3 buttons reboot the phone?
Click to expand...
Click to collapse
Press the trackball, volume down and the power button all at the same time.
If you have root then the app quick boot is a one click solution.
When I was or do have a stalling at the install. I clear the market data and this works for me. I also try to keep the cache clear.
Since I manually upgraded from EPE54B to FRF85B to FRF91, my phone has been freezing a lot. I don't really see a pattern to it as far as which apps are open when it freezes. It has happened on Handcent, browsing, Gmail, and probably a couple other apps. Anybody know what could be causing this?
yes u are right, its freezing.
Try this, from lostinbeta:
Yes, boot into recovery (turn off the device, then hold down the trackball while powering on the device)... then follow the instructions to navigate to the recovery window)... I believe when you get to recovery you get an android with an exclamation point.... press volume up, volume down, and power button all at the same time to access the submenus. Wipe should be in there. Works for non-rooted and locked phones. It's the same way I did my manual 2.2 update.
Wouldn't that wipe all the data on my phone?
Select the wipe cache option first and see if that fixes the issue. That only clears the cache partition and not the phone data.
If it doesnt then you might want/have to do a factory wipe which will delete all ur info (so back them up first).
I wiped the cache, but that didn't help. I decided to try disabling some applications to see if one of them was causing the problem. I think I may have found it. I disabled some of the options on LauncherPro that said they could cause instability, and I haven't had a problem since.
I'm having problems with the phone freezing as well.
i had a problem freezing too and i jus did a factory reset/data wipe in recovery and everything came out good no freezes, did manual updates too
I ended up doing a factory reset/wipe as well, and that fixed the problem for me.
Go to the market and grab Process Manager Full. Kill some of the apps running in the background like mail, browser, music or stuff that isn't a service. Free up some memory and see it that temporarily fixes freezing. We all deal with this and for myself, closing apps always unfreezes the phone.
Is there a way to solve this problem without factory wipe? Mine freezes 5 times a day....
On FRF91
Sent from my Nexus One using XDA App
I was going through this as well. If I fell back to the original ERD PASSIMG and then updated to ERE27 and stayed there things were fine.
As soon as FRF91 got pushed to my phone it would begin running hotter and lock up / restart many times per day. Yesterday alone I counted five lock-ups in 45 minutes while out shopping with my wife.
I finally got frustrated and last night I rooted my phone and did the hack needed to block the 2.2 OTA. I am currently running rooted 2.1 ERE27 (otherwise stock) and my phone is behaving nicely.
I haven't had a single lock-up/reboot since I rooted. There are some things I miss from FroYo now (like properly working hands-free Bluetooth) but I can live without if it means my phone is behaving properly.
Your still going to get the OTA, I restored one of my nandriod backups FRF85, and the OTA was waiting for me after bootup. You can't flash it though if you have custom recovery. They have rooted stock FROYO, try it out maybe you'll like. I would never go back to 2.1 that's insane.
Sent from my Nexus One using XDA App
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
Hello XDA geniuses; If anyone can figure out and provide me some suggestions, its here!
So, I've been running Benzo ROM for the last few months, its perfect for me. I've tried others but have settled on it. In the last update, it required a clean flash, which I did. TWRP -> Advanced Wipe -> System, Data, Dalvik and Cache. Never had an issue before, but in this build I can't use Google Wallet or Tap and Pay.
When I go to start either of those 2 apps, they just sit at the initial screens. Thats all, they just sit there.
I've made sure I'm signed into my account, no ad blocking or security issues I can see. I've wiped and re-flashed 4 times. Made sure I have the right ROM and gapps. I've uninstalled and reinstalled Wallet a bunch of times.
The dev did say in this build he; "AOSP Webview to Google's Webview", hence the clean flash.
Nothing I've tried yet has made any difference. I did a logcat, but did not see anything notable.
And, yes of course I posted this in the ROM forum, unfortunately I've not received much response and figured I would ask in the Help section.
Thanks in advance and if you have any suggestions at all, please let me know. I use Wallet daily and I hate to move off this rom, but I have been trying others and I do rely on Wallet at this point.
jackpollard said:
Hello XDA geniuses; If anyone can figure out and provide me some suggestions, its here!
So, I've been running Benzo ROM for the last few months, its perfect for me. I've tried others but have settled on it. In the last update, it required a clean flash, which I did. TWRP -> Advanced Wipe -> System, Data, Dalvik and Cache. Never had an issue before, but in this build I can't use Google Wallet or Tap and Pay.
When I go to start either of those 2 apps, they just sit at the initial screens. Thats all, they just sit there.
I've made sure I'm signed into my account, no ad blocking or security issues I can see. I've wiped and re-flashed 4 times. Made sure I have the right ROM and gapps. I've uninstalled and reinstalled Wallet a bunch of times.
The dev did say in this build he; "AOSP Webview to Google's Webview", hence the clean flash.
Nothing I've tried yet has made any difference. I did a logcat, but did not see anything notable.
And, yes of course I posted this in the ROM forum, unfortunately I've not received much response and figured I would ask in the Help section.
Thanks in advance and if you have any suggestions at all, please let me know. I use Wallet daily and I hate to move off this rom, but I have been trying others and I do rely on Wallet at this point.
Click to expand...
Click to collapse
Have you tried going into settings>apps>all and force stopping and clearing data?
i just got my n6 yesterday and installed stock android m preview. so far evreything seems to work fine, but my venmo app just shows a blue screen. ive tried force closing and clearing cache/data.
strangeeeeeeeeeeeee
Evolution_Tech said:
Have you tried going into settings>apps>all and force stopping and clearing data?
Click to expand...
Click to collapse
Hey Evolution_Tech, super appreciate the feedback! Yes, I tried it again, just to make double sure. I force stopped Wallet, even went into Show Cached Process and killed it. Same thing for both T&P and Wallet; I bring up the app, it goes to the 1st screen and boom just sits. In T&P I cant even press the Display link. So freaking odd.
Again, Thanks!!
jackpollard said:
Hey Evolution_Tech, super appreciate the feedback! Yes, I tried it again, just to make double sure. I force stopped Wallet, even went into Show Cached Process and killed it. Same thing for both T&P and Wallet; I bring up the app, it goes to the 1st screen and boom just sits. In T&P I cant even press the Display link. So freaking odd.
Again, Thanks!!
Click to expand...
Click to collapse
You could try logging out of your Google account completely then logging back in.
Any update on this?
Sent from my Nexus 6 using Tapatalk
nlua said:
Any update on this?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hello; Here is what worked for me, but I have to preface it with make sure you do a good backup. When the Rom I use asked for a full refresh including wiping data, is when I had the issue. I eventually tried it with not wiping data and that's what worked. I think wallet keeps some persistent data there and when you wipe it out, it gets stuck. Good luck.
I will try and make this my last update; I finally got wallet to work with a complete wipe, including data.
I used dev options and found the package in data/data for wallet, its com.google.android.apps.walletnfcrel
I copied com.google.android.apps.walletnfcrel from data/data into a folder on my sd card. Then I did my clean wipe. I installed wallet and let it build the structure. Then when I tried it, it would hang. I stopped it, then I copied all the files back in from my backup and it worked. I overwrote the files and used es file explorer that had root.
Make sure, as always you have a good backup.
If you have any questions just give me a shout.
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.