Has anyone else experienced this with their unrooted OP3? About two hours after my phone got the update it alerted me that the safenet check failed...
Only thing I can think is that I changed my DPI with fastboot some time before this update. Not sure if that caused it or not, but heads up if you've changed your DPI on an otherwise stock phone.
cadbomb said:
Has anyone else experienced this with their unrooted OP3? About two hours after my phone got the update it alerted me that the safenet check failed...
Only thing I can think is that I changed my DPI with fastboot some time before this update. Not sure if that caused it or not, but heads up if you've changed your DPI on an otherwise stock phone.
Click to expand...
Click to collapse
I have the issue with a freshly wiped, never rooted system (http://forum.xda-developers.com/showpost.php?p=68162872&postcount=59)
So I think something is broken with this update when it comes to SafetyNet.
Other people have the same issue on a never rooted system:
http://forum.xda-developers.com/showpost.php?p=68163301&postcount=8
I can confirm that android pay doesn't work.. even when you are not rooted. something is messed up with this update it seems
Yes, I concur. Android Pay is broken in 3.2.4 in the UK too. Very disappointed. I'm beginning to think the OnePlus name really means plus one new bug with every software update.
CTS profile match is "false" after getting the OOS 3.2.4 OTA update, breaking Android Pay
cadbomb said:
Has anyone else experienced this with their unrooted OP3? About two hours after my phone got the update it alerted me that the safenet check failed...
Only thing I can think is that I changed my DPI with fastboot some time before this update. Not sure if that caused it or not, but heads up if you've changed your DPI on an otherwise stock phone.
Click to expand...
Click to collapse
I saw it somewhere that OP is going to Breng another update 3.2.6 which is going to fix that
They seems to have fixed it in the backend, it is working now.
Related
"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.
I didn't get this "comp patch" as an individual update. Last week, I got the update with the security patches from July 1 (German G4, no branding), and it looks like that this patch was included. It now shows in the list of installed LG applications, where it didn't appear before. My wife (LG G3) got this patch as a single install (~1 week ago).
I have got this compatibility patch too, and in description of this app is 20160809 so it is 1 week old. But what was going about in that "fix"... :/
I've got the patch today too. But haven't rebooted yet.
U talking about this one? What is that supposed to do?
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
If you have the encryption on then turn it off and reboot. That should resolve the issue and then you can turn it back on. Hope it works for you.
akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.
Problem with the Patch
I got the same patch on my LG V10. Thinking nothing of it I agreed to install and reboot. Once I had done so, I now have the Yellow Boot Warning at every boot. And also a bunch of my system apps stopped working. Camera, Phone, Music. I don't remember ever flashing a ROM that would trigger the warning seeing as how I got the update to 6.0.1 a few days before and hadn't done anything since. So I flashed back to stock with LGUP and the problems still persist. This is my first post ever, any advice. I apologize as I know this is a LGG4 thread.
If you did anything to the system image, you may have issues applying the OTA. @SixTheAmateur: did you modify in any way your V10? Did you flash a KDZ not officially available to your V10?
Index100 said:
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.
Click to expand...
Click to collapse
Yes that was the problem. Solved after disabling encryption
Guys the compatibility patch dissappeared??? Help yesterday it showed up Today nothing
Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?
Copperwolf said:
Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?
Click to expand...
Click to collapse
I've had massive compatibility issues with my g4 and apps I like to use. I noticed this today and definitely installed it. I have been able to use the apps I hadn't been able to use.
It seems to be going well so far. I'd say do it.
It seems to be frozen/disabled after installing, odd.
Sent from my LG-H811 using XDA Labs
Press and hold on notifications to see which app is giving them
Compatibility Patch Mystery to T-Mobile and LG
I got a notice for a compatibility patch several weeks ago.
Rather than click I contacted LG, who knew nothing of it.
So I contacted T-Mobile, my carrier, and they knew nothing of it and suggested I don't down load it.
It popped up again today and I'm going to ignore it until I understand what it will do.
Good Luck!
Similar experience. I had issues with my phone afterward and had to get a new one.
Similar experience. I had issues with my phone afterward and had to get a new one.
nikooe said:
"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.
Click to expand...
Click to collapse
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.
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
sliding_billy said:
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
Click to expand...
Click to collapse
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
bcradu69 said:
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
Click to expand...
Click to collapse
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
ndd53 said:
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
Click to expand...
Click to collapse
I don't, but to make sure... I am using 16.0 of Magisk.
ndd53 said:
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
Click to expand...
Click to collapse
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
bcradu69 said:
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
Click to expand...
Click to collapse
that was it! I turned off Crossbreeder lite (didn't have Greenify) and now bluetooth is working again. thanks!
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?
Just received this
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Oh no, seems like I have to stuck in version 10.0.10.0 forever ... :crying:
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Hopefully we will get it back with Android 10. I'm using superior os 10 till we get it.. so far it works pretty nicely.
Also got the update. The size looks ok for a simple security patch and minor fixes so nothing major.
Phone starts ok, no problems so far.
This is the first update that no one is complaining about yet... so it's a change in the right direction for the Xiaomi OTAs.
Xiaomi Mi A2 users (they got it 3 days earlier) said that it even works fine with Magisk.
I had 2 odd things happen as a result of installing this OTA.
1) USB Debugging was turned off. No other developer things seem to have changed, just that toggle was off.
2) My timezone was changed. Almost like the phone temporarily forgot I didn't want to use network-provided timezone (it often picks the neighbouring state, which has a 1-hour offset from here).
I've never had this happen with previous OTAs.
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
My dad didn't have this issue. Make sure it isn't your network provider having this problem
If you don't enroll your fingerprint before updating to v 10.0.16 ,you can't do it after the update
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
Hello, if someone is experiencing the same problem, I resolved it flashing the official stock rom with Miflash tool. Cheers
This update has definitely done something to the signal mine is falling onto 2G a lot, before that I was steady on 4G. Once it hits 2G it stays on it regardless of the signal strength until you restart the phone. It is very annoying.
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
downloadonlyaccount said:
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
Click to expand...
Click to collapse
This sounds like the known issue with new/fast cards. There's a thread where it was discussed.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
That's a problem that sometimes occurs since Pie came out. Restarting the mobile should fix it.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
My multitasking seems to be very bad after the update...
Hello,
I have Mi A2 lite with magisk installed, and I am unable to perform the november OTA update.
here is what I do:
1. In magisk : Uninstall > restore images
After doing this, magisk still looks the same:
2. Launch the OTA update.
I first have this screen:
red message translation: "Install will resume when the phone is not active. Click on resume to finish installation now"
3. Clicking on resume will start the installation, but it fails after some moment:
4. After that, I go back to Magisk: Install > Direst install to avoid having Magisk uninstalled after reboot. When doing this, here is the screen:
I don't understand why my OTA is refused...
Is there something to setup in magisk hide ? In order to hide magisk from the OTA updater ? or anything else ?
/system could have been modified, you can try flashing only that partition to solve the issue
nehuy said:
/system could have been modified, you can try flashing only that partition to solve the issue
Click to expand...
Click to collapse
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
takhama said:
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
Click to expand...
Click to collapse
The upgrade tool writes a log to logcat. It says which partition it does not like.
adb logcat | grep update_engine
There have been no fastboot image released for 10.0.15.0. I have backups of both system and vendor (since they both seem to be modified every OTA for me). If you can confirm that either of these is needed I can try to upload it somewhere. Note that these are very large partitions.
Alternatively, you could use the 10.0.13.0 fastboot and OTA from there. Make sure to backup data before doing this.