Related
Cannot disable system updates on Pixel. Changed settings but still OS updates are running.
Developer options > on > automatic system updates > off
You really like to have many vulnerabilities and old software on your phone do not you?
Leave it alone. Nowadays so many vulnerabilities are found each day it's crazy to not being able to protect yourself from them.
The option on stock Android 10 is only to "not apply updates at next reboot" You would have to stop update services. Root will be required. File manager to edit files. I have no idea how involved that would be, but then if a rollback to older version is your preference. Factory Images flashing, then stopping required services.
I would even consider to downgrade to ver. 9. After installation of ver. 10 the phone freezes often .
geo1001 said:
I would even consider to downgrade to ver. 9. After installation of ver. 10 the phone freezes often .
Click to expand...
Click to collapse
ive only been having issues on the october patch, once i updated to this then the issues were persistent between resets, downgrades and roms
sudoxd said:
ive only been having issues on the october patch, once i updated to this then the issues were persistent between resets, downgrades and roms
Click to expand...
Click to collapse
With my Pixel happened the opposite. After this patch , about a week, the freezings stopped. Believe or not, the battery stopped draining quickly and came back to normal discharge.
EDIT & TL;DR:
(i) Some people on this thread say they have "no problems with the upgrade", but many, many people do. To me that confirms the advice of this post: don't gamble, it's not worth it.
(ii) Also note that some people say that their battery life improved with Android 10… but then it turned out that on Pie, for some reason, they had a battery life of three hours, instead of the awesome times that the rest of us are getting. In short: if someone says that Android 10 is awesome, try to read between the lines.
Original Post:
Long story short.
Upgraded to Android 10.
"Search" stopped working within Settings
Battery life went from Awesome to Awful, Awful, Awful (known issue)
Fought the battery issue for two days (requested help with BBS dump)
Downgraded to Pie using TWRP backup (mistake)
This bricked the phone
Spent a whole day unbricking
Have my phone back but lost local files (photos, documents)
Android Pie ain't broke… Don't be like me, there's nothing to fix, the OP7 on latest Pie is awesome, it's all downhill from there.
Im on android 10 OOS10.0.1, rooted, magisked, viper installed, blu_spark-r57 installed. everything is perfect. search is also working.
but i fully clean flashed the entire android 10 firmware. maybe try that? i backed my stuff up on my PC prior to this.
who ah way said:
Long story short.
Upgraded to Android 10.
"Search" stopped working within Settings
Battery life went from Awesome to Awful, Awful, Awful (known issue)
Fought the battery issue for two days (requested help with BBS dump)
Downgraded to Pie using TWRP backup (mistake)
This bricked the phone
Spent a whole day unbricking
Have my phone back but lost local files (photos, documents)
Android Pie ain't broke… Don't be like me, there's nothing to fix, the OP7 on latest Pie is awesome, it's all downhill from there.
Click to expand...
Click to collapse
But that's not a general recommendation to not update to Android 10
strongst said:
But that's not a general recommendation to not update to Android 10
Click to expand...
Click to collapse
Sure, it's just one person's experience. It caused me a lot of grief, and I don't see the point of taking the risk. For the few days I was on 10 I didn't see any benefits, only drawbacks.
Pie to stable 10 then beta 4, is just keeps getting awesome. But hey maybe its just me. Factory reset and no apps restore
Didit_Anshari said:
just keeps getting awesome
Click to expand...
Click to collapse
What would be one or two specific improvements you've found from Pie to Q?
who ah way said:
What would be one or two specific improvements you've found from Pie to Q?
Click to expand...
Click to collapse
battery life, and animation
I can confirm. Even on a clean install battery backup is significantly less on Android 10. Last Pie update gave me like 10+ hours of SOT.
Saadkhalid786 said:
Im on android 10 OOS10.0.1, rooted, magisked, viper installed, blu_spark-r57 installed. everything is perfect. search is also working.
but i fully clean flashed the entire android 10 firmware. maybe try that? i backed my stuff up on my PC prior to this.
Click to expand...
Click to collapse
Apps to display in full screen not working in 10
Don't know what's the problem with the battery this screenshots from OpenBeta 4 and now i'm on OpenBeta 5 will see how's the battery there :good: for me on every OpenBeta no problem with the battery life :good:
Maybe the reason is that I always to a fresh start from the scratch with every OpenBeta :good:
Sent from my OnePlus7 using XDA Labs
In android 10, Having auto brightness issue getting too low in medium litt conditions...
SherryWadhwa said:
In android 10, Having auto brightness issue getting too low in medium litt conditions...
Click to expand...
Click to collapse
Is not a issues, it's settings to aggressive. For resetting the auto brightness go in settings and tap on the in the screenshots marked points.
That resets the auto brightness and takes some days to learn it new :good:
Sent from my OnePlus7 using XDA Labs
Thanks mate! Tried it but still having a little issue at some point.
anyone can use sip calls with the default phone app and loudspeaker?
GraveDigger176 said:
Don't know what's the problem (...)
Maybe the reason is that I always to a fresh start from the scratch with every OpenBeta :good:
Click to expand...
Click to collapse
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
Let's cut through the noise for a moment.
Is there ANYONE on this thread who has actually done an UPGRADE as suggested on the guide below, and who is NOT experiencing pain with Android 10?
The Guide (see the section called 2. UPDATE):
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules
Your device is now updated via local upgrade and you keep TWRP and Root
Click to expand...
Click to collapse
who ah way said:
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
I did also the upgrade from P to Q as I was on stable OOS, but right after upgrade and boot I booted in the stock recovery and do factory reset and the wipe everything wipe and start from the scratch and I never had any mentioned issues. But anyway now i'm on Beta path :good:
Sent from my OnePlus7 using XDA Labs
Click to expand...
Click to collapse
who ah way said:
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
Let's cut through the noise for a moment.
Is there ANYONE on this thread who has actually done an UPGRADE as suggested on the guide below, and who is NOT experiencing pain with Android 10?
The Guide (see the section called 2. UPDATE):
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
Click to expand...
Click to collapse
Yes, me. I did not face any issues.
I did an upgrade from pie to Q with the same instruction.
3 issues I have.
Autobrightness
Wifi is sometimes disconnecting for a sec and connecting again
Gap below the keyboard
Personally don't have any issues whatsoever with Android 10 - Magisk, kernel, and all. Though its true that if you're on pie there's no point in upgrading. Only added feature that you might enjoy is ever so slightly more customization and android 10 navigation gestures, that's it.
I upgraded to A10 and latest Oxygen and everything is working fine for a month and more, haven't experienced any issues listed above.
Hi,
I am running last Android 11 xiaomi.eu weekly rom and i use xiaomi.eu since 6 month and i have a problem since beginning, some app dont work properly due to some micro disconnection (i think) because some app don't load, i can open app but i can't connect/login on it or i must to load it 2 or 3 or more time like facebook.
When i use wifi no problem but with cellular it's difficult.
Can you help me to solve this problem?
Thanks by advance
Fangstergangsta said:
Hi,
I am running last Android 11 xiaomi.eu weekly rom and i use xiaomi.eu since 6 month and i have a problem since beginning, some app dont work properly due to some micro disconnection (i think) because some app don't load, i can open app but i can't connect/login on it or i must to load it 2 or 3 or more time like facebook.
When i use wifi no problem but with cellular it's difficult.
Can you help me to solve this problem?
Thanks by advance
Click to expand...
Click to collapse
Surely already done:
check the permissions of the affected apps
settings / management of applications / installed applications.
Uninstalled and reinstalled the affected applications.
If you have updated roms on roms, try a clean flash with the latest android 11 version.
Yes already done i think this is micro cuts on cellular reception for exemple when i use tethering with ftp soft on my comp i can't keep connection because the connection is unstable or micro cuts on cellular datas...
Have you an idea to solve this problem i am the only one facing this issue?
Fangstergangsta said:
Yes already done i think this is micro cuts on cellular reception for exemple when i use tethering with ftp soft on my comp i can't keep connection because the connection is unstable or micro cuts on cellular datas...
Have you an idea to solve this problem i am the only one facing this issue?
Click to expand...
Click to collapse
Did you install the rom in cleanflash?
For tethering try activate Usb debugging in developer option.
Special features /miui lab/AI preloading
Yes cleanflash....
I Hope Android 12 solve this problem...
But am waiting for compatible twrp...
Fangstergangsta said:
Yes cleanflash....
I Hope Android 12 solve this problem...
But am waiting for compatible twrp...
Click to expand...
Click to collapse
the twrp work if you deactivate the protections on the lock screen or if you format the data.
here Twrp for android 12.
Okay if i understand correctly i can flash xiaomi.eu Android 12 rom using this twrp (this is already the one i have 1206) but before i must to disable the unlock pattern and finger print?
1) disable security pattern
2) flash the xiaomi.eu rom Android 12
3) enable security pattern
And do this every Time?
I read about some users loosing their twrp?
Fangstergangsta said:
Okay if i understand correctly i can flash xiaomi.eu Android 12 rom using this twrp (this is already the one i have 1206) but before i must to disable the unlock pattern and finger print?
1) disable security pattern
2) flash the xiaomi.eu rom Android 12
3) enable security pattern
And do this every Time?
I read about some users loosing their twrp?
Click to expand...
Click to collapse
No,you can't.
Xiaomi eu rom A12 only Fastboot.
I read about some users loosing their twrp?
For the TWRP you flash it after installing the rom.
Thanks for all your help i will wait for a fullly compatible twrp
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that
I briefly tested Android 12 as well as Android 13 GSIs on my TB-Q706F, with necessary and hopefully up-to-date vendors flashed for the purpose.
While most of the OS functionalities work fine, I noticed there are major issues with touchscreen, as when gaming, from time to time touchscreen would stop responding altogether, disrupting gameplay. I originally noticed this when I started using A12 GSI, but it appears the issue persists with A13 GSI as I have tested recently.
I'm not sure if other users on A12/A13 GSIs are also having the issue. In my case, the issue with touchscreen doesn't appear to manifest in Android 11 GSIs. When I reverted my tablet back to Android 11 GSI, the issue went away and touchscreen is now working fine.
So far I've only tested GSIs, so I don't know whether stock ZUI 14 is also affected like any other A12 GSI. I can't really test too much about this as I need the tablet to be in a usable state, and that touchscreen-related issues are not trivial to capture and inspect.
It's strange that no one else reported this issue. I encountered the same when I recently flashed to the official global Android 12L via Lenovo rescue assistant and encountered intermittent unresponsive touchscreen during gaming also.
Over the course of using this tablet on Android 11 for more than 1 year and I had never encountered such issues.
When I encountered this issue, I just quickly press the power button to put it on standby and wake it up again.
NSC779 said:
It's strange that no one else reported this issue. I encountered the same when I recently flashed to the official global Android 12L via Lenovo rescue assistant and encountered intermittent unresponsive touchscreen during gaming also.
Over the course of using this tablet on Android 11 for more than 1 year and I had never encountered such issues.
When I encountered this issue, I just quickly press the power button to put it on standby and wake it up again.
Click to expand...
Click to collapse
Touch screen works fine with no major issues when using Android 11. It's only when using Android 12 and onwards that the touchscreen would intermittently stop responding.
The problem is, touch-related issues may not be noticeable if not doing any intensive gaming, and are very hard to pinpoint.
I recall Lenovo was aware of some touch-related issues at least according to the official A12L Developer Preview image at some point. Not sure if the issues have been resolved by the time ZUI 14 came out.
Had Lenovo ever released kernel sources for our device (Q706F/Q706Z)? I don't know where one can request kernel sources from them...
EDIT: So turning off the screen then turn it back on would restore the touchscreen functionality? If this works 100%, then logcats during the moment when you turn the screen off, as well as the moment when you turn the screen on, may contain hints.
Hello ! I have Q706F (wifi only) can I get a clean Android 11 on it ? or some custom A12 rom ? I reallly want to be stock to android as possible. You guys mostly use A11 ? Thanks
bernek said:
Hello ! I have Q706F (wifi only) can I get a clean Android 11 on it ? or some custom A12 rom ? I reallly want to be stock to android as possible. You guys mostly use A11 ? Thanks
Click to expand...
Click to collapse
If you want a clean Android you can try Phh's AOSP GSI. You should be able to find an A11 build there.