After a few hours stock camera stopped work (after restarting or making a factory reset still the same), dont know if the update to pie has something to do.
anyone having same problem?
Here you see
reset your phone
Brugos27 said:
After a few hours stock camera stopped work (after restarting or making a factory reset still the same), dont know if the update to pie has something to do.
anyone having same problem?
Click to expand...
Click to collapse
I had the same problem, i resetted the phone via settings and this fixed it for me
Do not disturb is active
That happens when "Do not disturb" is active, deactivate it and go!
jerryortiz2100 said:
That happens when "Do not disturb" is active, deactivate it and go!
Click to expand...
Click to collapse
This helped thank you
How did you update?
Did you get the update normally? I used a VPN to get it since it was not yet being offered directly. And now I have this bug as well. So I wanted to see if it's happening to everyone or just people who updated with a VPN.
ryanhossain9797 said:
Did you get the update normally? I used a VPN to get it since it was not yet being offered directly. And now I have this bug as well. So I wanted to see if it's happening to everyone or just people who updated with a VPN.
Click to expand...
Click to collapse
It's not about how you updated, it's because of the used build which is the same like the first released beta build.
thorin0815 said:
It's not about how you updated, it's because of the used build which is the same like the first released beta build.
Click to expand...
Click to collapse
That's kind of the point of my question. Did me using vpn somewhy cause me to get the beta build for some strange reason or a mistake on their end? or is this build being OTA'd normally to other people as a stable update in some regions?
Related
In just one day, Android OS used 269mb of data. Anyone know what's going on? Saw a thread for the Android OS draining battery, and my issue is a bit different. Also, on wifi it used 2.66g in about 4 days.
7.11 Rooted.
I do not nor ever have favebook installed.
Thanks!
I have the same problem. I just posted the same question. Wish I had have seen this beforehand.
It's probably trying to update and failing due to being rooted. This will cause the device to continually download the update. Are you on the latest uodate/January security patch?
bjoostema said:
It's probably trying to update and failing due to being rooted. This will cause the device to continually download the update. Are you on the latest uodate/January security patch?
Click to expand...
Click to collapse
Yea, it seems like the update thing is what causes it.
Disabling automatic updates doesn't seem to help either. This is a pretty huge bug...
So my only option is to update, and then CONSTANTLY check if theres an update, and if there is then IMMEDIATELY turn off networking... ****ing great.
Maybe a custom rom wont have this issue...
Arekku said:
Yea, it seems like the update thing is what causes it.
Disabling automatic updates doesn't seem to help either. This is a pretty huge bug...
So my only option is to update, and then CONSTANTLY check if theres an update, and if there is then IMMEDIATELY turn off networking... ****ing great.
Maybe a custom rom wont have this issue...
Click to expand...
Click to collapse
It is a super annoying bug. This is exactly why I haven't even bothered rooting yet, Nougat coupled with dual boot is gonna take a while to become mature with development. A custom rom would def solve this particular issue but they're all kind of young right now. Though I have read a few are dd status. Glad that is all that it was! On the plus side, you only have to worry about it after the 5th of every month! Looks like you'll just have to reflash twrp and superu https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
I need a bit of help here. I "unrooted" via the Super SU app. Rebooted, tried to update. Still failed. I also have lost root. Super annoying. Is there anything else that the updater is expecting that i haven't restored???
Came across this this morning https://m.reddit.com/r/GooglePixel/comments/5o816g/solved_extreme_data_usage_by_android_os/. This should help you guys with the drain and then you only have to take the OTA via flashing it whenever you choose. Do note, I haven't tried this yet, so I can't confirm but others report it working.
heardamir said:
I need a bit of help here. I "unrooted" via the Super SU app. Rebooted, tried to update. Still failed. I also have lost root. Super annoying. Is there anything else that the updater is expecting that i haven't restored???
Click to expand...
Click to collapse
Easiest way is to just download the full factory image and use the flashall.bat to do it. Edit out the -w so your apps and data are saved. Then reroot it.
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.
mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.
mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!
mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?
mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage
mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.
Hi, A lot of people are having issue regarding security of device as you cant change your pin and it wont let you enter your pin by showing wrong pin. You cant even have any security after doing a factory reset.
I have done everything to fix it , even took it to samsung repair center, still no success so I have sent it to samsung warranty today.
I have done these things to fix it but nothing worked.
1. Tried online samsung and google "find my phone" service" to fix it as it is shown on some sites for older phones.
2. Reset the phone through recovery.
3. Install fresh firmware through Odin. Then installed both beta versions.
4. Installed orignial firmware mine was VAU.
5. Installed the first firmware of s10 plus. With Nand reset and partition using PIT file.
6. Took it to samsung, they tried 2 different firmwares to fix it but all in vain.
In the end Samsung told me that it might be issue after security patch done for screen protector. They cant do anything at the moment and I have to wait for a fix through update but I have sent my phone to warranty.
I posted this issue in Q&A last day after having issue. But now I can see There are a lot of people affected by this. In my opinion it is Beta 2 issue.
Once you encounter this issue, you are helpless until samsung fixes it. Until then just keep your data, no need to do factory reset or new firmware, as it wont do any help.
What?... Never had any of these issues dude
twoxa said:
What?... Never had any of these issues dude
Click to expand...
Click to collapse
I also got this first time. It is very frustrating and I spend 7 hours to fix it but nothing worked. Until now i have seen 5-6 people who are facing this issue after beta 2. More might come.
I'm also facing this problem, hope Samsung fix this ASAP.
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
madvinegar said:
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
Click to expand...
Click to collapse
I sideloaded it.
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
madvinegar said:
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
Click to expand...
Click to collapse
I did rolled it back but didnt work for me. my issue is persistent and even samsung service centre could not fix it. I gave my phone in warranty because I am not sure how much samsung will take to fix this issue and they might be able to fix it. Lets see what samsung will say.
am not having any of these issues on S10+ Beta 2
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
bomp306 said:
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
Click to expand...
Click to collapse
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Does this have anything to do with the recent update in the biometrics (fingerprint issue).?
I cannot understand why this bug was not seen right after the update to Beta2, but only after 3-4 days...
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
The good thing is that this bug affects also the ones who officially enrolled to the Beta program, so this means that Samsung must be working to release a fix. At least I hope...
kazim.asghar said:
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Click to expand...
Click to collapse
I'm on latest android 9 stable via ODIN but the problem with biometrics and pin lock keep in the phone, I did every wipes with no results
Hotfix rolling out now OTA
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
AshishV95 said:
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
Click to expand...
Click to collapse
It's already shared in the appropriate thread.
Intratech said:
Hotfix rolling out now OTA
Click to expand...
Click to collapse
Fixed!!
Just need to restore all my apps again now..
should change the thread to SOLVED now that samsung has released a hotfix for it
bomp306 said:
Fixed!!
Just need to restore all my apps again now..
Click to expand...
Click to collapse
Is it fixed? Can you change pin code?
I flashed it and I have absolutely non of the issues you're having. I have an unlocked S10+ on Verizon and I'm running the ZSJF build
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
thayl0 said:
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
Click to expand...
Click to collapse
try to wype partition cache
UNIK97122 said:
try to wype partition cache
Click to expand...
Click to collapse
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
thayl0 said:
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
Click to expand...
Click to collapse
do you have the same with another camera app ?
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
blackhawk said:
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
Click to expand...
Click to collapse
Sadly I don't think I can go back to pie I believe there's a different bootloader version
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Try the new Beta,it might fix it
TheViciousGames said:
Try the new Beta,it might fix it
Click to expand...
Click to collapse
Trying to find the first beta so it can update to latest. No luck so far
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Yeah they like to lock the doors behind you... just remember the lesson.
I learned the hard way with Kitkat; the last update did nothing except make easy root impossible.
With lollipop AT&T/Samsung purposely screwed up the graphics on just that old model for contacts and the music play list making the S4+ next to unusable.
They'll say it will run better, be more secure.
BS.
Never had a OS "upgrade" that wasn't bigger, hoggier and slower then the original on Android.
Never in 6 years of running outdated OS's on Androids had to do a reload from a virus or worm.
Sure it can happen but rarely does if you don't do stupid things.
Play with it, eventually you'll sort it out
Androids wuv being played with...
Hello community,
I have a Oneplus 8 pro laying around with unlocked bootloader, Magisk, (possibly TWRP), and a firmware which was one of the first in around may 2020.
The issue is, I want to use this phone now, but I cannot update it throught the full package of OxygenOS updater. It gives "update failed" at the 0% mark. It seems I cannot update through the conventional way. After some thinking, it might be unsuccessful as I am not even sure what firmware it runs.
The next step I wanted to take was go back to stock through the TWRP backup that was made in june 2020 (I'm not sure if it even has this backup), yet I now read it is unrecommended to use TWRP. I am not even sure if TWRP was working at that time (where would the backup be located?).
And finally I read OxygenOS 12 might ruin the phone if things are not done right due to firmware mix-up in case of the memory.
What now? Can anyone help me with some steps and advice to get the phone to at least the latest software, and preferably working with Magisk (included call recorder)?
Thanks in advance.
If your OS is fast, stable and fulfilling its mission let it be!!! The age is irrelevant if Android 9 or higher.
Don't fix it if it's not broken... if you value your time and device functionality.
blackhawk said:
If your OS is fast, stable and fulfilling its mission let it be!!! The age is irrelevant if Android 9 or higher.
Don't fix it if it's not broken... if you value your time and device functionality.
Click to expand...
Click to collapse
All works like a charm currently, except that VoWIFI tends to fail and not reconnect. Any ideas on that?
And what about security patches?
Thanks
Unfortunateburden said:
All works like a charm currently, except that VoWIFI tends to fail and not reconnect. Any ideas on that?
And what about security patches?
Thanks
Click to expand...
Click to collapse
Let me put it this way, this heavily used stock N10+ hasn't been updated in over 3 years, still running on Pie.
Current load is over 2.5 yo, still fast and stable with minimal maintenance.
Security simply isn't a issue. Nothing's got through with only some simple protocols being used to secure it. One is wifi, disabled, I never use it. This what Android is capable of...
blackhawk said:
Let me put it this way, this heavily used stock N10+ hasn't been updated in over 3 years, still running on Pie.
Current load is over 2.5 yo, still fast and stable with minimal maintenance.
Security simply isn't a issue. Nothing's got through with only some simple protocols being used to secure it. One is wifi, disabled, I never use it. This what Android is capable of...
Click to expand...
Click to collapse
Sounds good.
What if someone really requires to have Wifi working because they have zero reception inside?
Unfortunateburden said:
Sounds good.
What if someone really requires to have Wifi working because they have zero reception inside?
Click to expand...
Click to collapse
You'll have to work that out. For me wifi is a hugh security risk. Since I have a grandfathered unlimited data plan wifi is irrelevant.
You could use a signal booster...
blackhawk said:
You could use a signal booster...
Click to expand...
Click to collapse
Not legal in every country sadly.
Back to my first question, do you have any steps to get back to stock if I ever wanted to?
You could use the MSM tool and factory reset it back to OOS10 and from there on update it OTA.
Deavy said:
You could use the MSM tool and factory reset it back to OOS10 and from there on update it OTA.
Click to expand...
Click to collapse
Thanks alot!