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
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
My congrats for the great autonomy ?
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Simone98RC said:
My congrats for the great autonomy
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Click to expand...
Click to collapse
everything is stock, still new of android so and ty
athais said:
everything is stock, still new of android so and ty
Click to expand...
Click to collapse
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Simone98RC said:
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Click to expand...
Click to collapse
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
athais said:
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
Click to expand...
Click to collapse
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Simone98RC said:
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Click to expand...
Click to collapse
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Flash another room
Seems to be an issue with OOS, I had the same problem, and flashed MIUI 8 and had 0 reboots. But when I flashed Fredoom OS based on OOS 3.2.7 my phone kept rebooting.
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Are you using a case? I had a cheap eBay clear case on my phone and it wasn't moulded properly over the power button, there was no indent on the inside for the button to sit in so it used to turn off in my pocket and back on later and produced battery graphs similar to yours.
Hope this is a help.
athais said:
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Click to expand...
Click to collapse
Did your problem solved? I am having same problem.
I have the same problem. I am currently on 3.2.8 and also had this problem on beta 9. Few days ago it happened in front of me, the phone was on the desk nothing running in the background. That was kind of the soft reboot, didn't triggered my locked sim, (my sim card is locked needs to enter PIN when phone startup) and after that I checked Settings=>About Phone=>Status, the uptime didn't affected too, seemed nothing was happened. I think this also happened to some other people but they just didn't realize it.
Karthi91 said:
Did your problem solved? I am having same problem.
Click to expand...
Click to collapse
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Click to expand...
Click to collapse
Yes.. I'm on 3.2.8 and did factory rest also. No use
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Same for me. Is your problem solved? Please help me. It is really annoying. I have Pin setup for restart so when boot happens in night, if no input for pin phone stays off.
Can this be related to SIM carrier:Radio drivers?
I dont think so.. Because i havent changed Sim
Karthi91 said:
I dont think so.. Because i havent changed Sim
Click to expand...
Click to collapse
Try using non 4G/LTE SIMS.
I am facing the same problem.
My device is at service center.
Day one:No reboots.I asked them to put some SIM & then check.
I did that after reading your post. No luck. Are they replacing it? How many days since it is in service center?
Facing problem from last 2 weeks.
I submitted once last week.They clean flashed older rom.Worked fine for one day,then reboots started again.
Then this technician had remote session and flashed the rom OnePlus3_16_A.17_161118(OOS 3.2.8):Reboot frequency went too high.
Had to go to Service center for diagnose. 2 days now.No proper response from them.
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Belyakovni said:
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Click to expand...
Click to collapse
Seriously? That sounds like one of those hilarious Microsoft Answers sort of posts! Running the battery down will not get rid of "electricity or static from the phone", apart from anything else the battery protection circuit would not allow the battery to drop to zero volts as it's not good for li-on batteries.
The Oneplus 3 seems to like to soft restart, mine sometimes decides to do it 3-4 times a night (rarely during the day) and then is fine for awhile. Tell tale sign is the battery graph showing large gaps in the usage pattern. I would suggest that there is an inherent firmware issue judging by the number of people reporting the same issue on a number of different forums.
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.
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
TheIgster said:
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
Click to expand...
Click to collapse
+1 Can confirm that I have the same issue as well.
I haven't contacted Google yet because ultimately their advice is to format the device and that's a silly way to fix issues and takes so much time.
After a certain amount of time the updates listed under the Updates section will go away. My last one went away yesterday afternoon (Snapchat). If you don't have any updates to apps then you won't see anything there. There's nothing wrong with that. It's funny that you post about it because I just happen to take a screenshot of mine last night. It was empty like yours, but today I got one update, and now that one app shows.
bobbyphoenix said:
After a certain amount of time the updates listed under the Updates section will go away. My last one went away yesterday afternoon (Snapchat). If you don't have any updates to apps then you won't see anything there. There's nothing wrong with that. It's funny that you post about it because I just happen to take a screenshot of mine last night. It was empty like yours, but today I got one update, and now that one app shows.
Click to expand...
Click to collapse
Sorry, that's not the issue. Look at your screen shot and look at mine. See all the white space where apps are supposed to be on mine and see how there is no white space on yours? I have had it like your screen as well. But not with all the white space. There is truly an issue here.
TheIgster said:
Sorry, that's not the issue. Look at your screen shot and look at mine. See all the white space where apps are supposed to be on mine and see how there is no white space on yours? I have had it like your screen as well. But not with all the white space. There is truly an issue here.
Click to expand...
Click to collapse
Gotcha. I read what you tried also, and you don't mention if you tried uninstalling updates for the Play Store. Did you try that?
bobbyphoenix said:
Gotcha. I read what you tried also, and you don't mention if you tried uninstalling updates for the Play Store. Did you try that?
Click to expand...
Click to collapse
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
TheIgster said:
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
Click to expand...
Click to collapse
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
TheIgster said:
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
Click to expand...
Click to collapse
bobby janow said:
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
Click to expand...
Click to collapse
They will likely keep replying to you (from different "specialists") asking you to do a ton of extra work that has no more reliability than the methods you could think of. Like bobby mentioned, flashing the factory image would be the best 1st step, but if not possible have you tried side loading the OTA through stock recovery?
sliding_billy said:
They will likely keep replying to you (from different "specialists") asking you to do a ton of extra work that has no more reliability than the methods you could think of. Like bobby mentioned, flashing the factory image would be the best 1st step, but if not possible have you tried side loading the OTA through stock recovery?
Click to expand...
Click to collapse
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
bobby janow said:
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
Click to expand...
Click to collapse
Pretty much, Bobby. If Verizon/locked BL, sideload current OTA (no downgrade possible). If you have a Google variant, you can still sideload OTA or unlock the BL (causing a reset) and then flash the factory image. If you go that route, I probably wouldn't re-lock the BL since stuff like this is as much a reason to keep the BL unlocked as rooting and other tinkering.
sliding_billy said:
Pretty much, Bobby. If Verizon/locked BL, sideload current OTA (no downgrade possible). If you have a Google variant, you can still sideload OTA or unlock the BL (causing a reset) and then flash the factory image. If you go that route, I probably wouldn't re-lock the BL since stuff like this is as much a reason to keep the BL unlocked as rooting and other tinkering.
Click to expand...
Click to collapse
Great, thanks. Only thing is if the OP is as security conscience as I am then relock. If not leave it as is. Being able to recover with a factory image is the only thing I miss. It's a big one too but I'm on VZW so I have no option. He could always leave the OEM switch enabled if ever it was needed again I guess.
I'm curious how this gets resolved as he's not the only one with this issue.
bobby janow said:
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
Click to expand...
Click to collapse
Oh this will definitely take longer than factory resetting the device, but as an ex software developer, I have to see this through and make Google work. If they find and solve the issue, this will help others who have the issue or stop them from having the problem in the first place. It's a bug that needs to be fixed IMO and being on them about this is the way to go. Sure I could just go away and factory reset, but this way, they have to deal with it.
See the attached pic I took today. After installing an app, this appeared on the updates page. The white space is clearly a bug and it needs to be addressed. If they don't solve this by the new year and I can't get updates for apps I use a lot, then fine, I'll factory reset, but I think they should be aware of this issue and they should have to fix it.
bobby janow said:
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
Click to expand...
Click to collapse
It's not the factory reset, it's remembering all the passwords for the various apps I have, settings, placement of icons, widgets, etc. It is a pain in the a** to reset a device. Besides, I just got this thing set the way I wanted it setup in the last couple of weeks. I haven't even had it for a month.
TheIgster said:
It's not the factory reset, it's remembering all the passwords for the various apps I have, settings, placement of icons, widgets, etc. It is a pain in the a** to reset a device. Besides, I just got this thing set the way I wanted it setup in the last couple of weeks. I haven't even had it for a month.
Click to expand...
Click to collapse
I can certainly appreciate making Google fix this as well as your setup you currently have. However, I seem to recall that when I did a factory reset all the apps and wallpaper and location of icons were imported from I guess Google cloud? Passwords were not though. Time to pull out that yellow notepad and go over those. lol BTW, are you bl unlocked and have you rooted or modified the system in any way? That was not clear from you OP.
bobby janow said:
lol BTW, are you bl unlocked and have you rooted or modified the system in any way? That was not clear from you OP.
Click to expand...
Click to collapse
My bootloader is locked and I've never rooted my pixel 3 XL, yet I'm experiencing the same issue that the op is facing.
MadCow809 said:
My bootloader is locked and I've never rooted my pixel 3 XL, yet I'm experiencing the same issue that the op is facing.
Click to expand...
Click to collapse
And this happened just all of a sudden? You have any thoughts on why or if perhaps an app screwed things up? Stock launcher? Some setting perhaps? Very curious isn't it? And since it's not very widespread it would be nice to know in order to avoid it.
TheIgster said:
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
Click to expand...
Click to collapse
Just to clarify, is it just a cosmetic issue with displaying extra white space on that screen, or is there some other functional problem?
samnada said:
Just to clarify, is it just a cosmetic issue with displaying extra white space on that screen, or is there some other functional problem?
Click to expand...
Click to collapse
The white space was never there before and is not there on other devices that I have encountered. Do you have the white space on your device? Also, updates are not appearing to happen properly either. The only reason I saw that one update is because I just installed another app and it updated one app right after that. I normally have numerous updates, daily.
Google has already admitted to and are working on this as a bug.
TheIgster said:
The white space was never there before and is not there on other devices that I have encountered. Do you have the white space on your device? Also, updates are not appearing to happen properly either. The only reason I saw that one update is because I just installed another app and it updated one app right after that. I normally have numerous updates, daily.
Google has already admitted to and are working on this as a bug.
Click to expand...
Click to collapse
But.. But. 3 people with this issue and they are calling it a bug? Are they blowing some smoke your way? Is there a tracker for this? CSR are notorious for playing the game until you give up. Be wary. I say factory reset and fix it yourself. You have spent way too much time on this I fear. But it's your call at this point. Keep us posted.
I just received OTA on my 975U ASF6, includes night mode in the stock camera app!!!! New Charging animation. Only had it for 5 minutes. Anybody else get it? If so post what changes you've noticed it was 522.5 Mb
iteam said:
I just received OTA on my 975U ASF6, includes night mode in the stock camera app!!!! New Charging animation. Only had it for 5 minutes. Anybody else get it? If so post what changes you've noticed it was 522.5 Mb
Click to expand...
Click to collapse
What carrier do you have? Nothing showing up anywhere for Sprint yet.
There was an article about it. ATT is the only US carrier to get the night mode feature (ASF6)
The rest of us will have to wait.
innocentone1 said:
There was an article about it. ATT is the only US carrier to get the night mode feature (ASF6)
The rest of us will have to wait.
Click to expand...
Click to collapse
Well that sucks ass....
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Atomicmuffin said:
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Click to expand...
Click to collapse
Usually I'd be in the same boat as you, but since I'm on Sprint it wouldn't even let me sideload the firmware science update
mistermidas said:
What carrier do you have? Nothing showing up anywhere for Sprint yet.
Click to expand...
Click to collapse
AT&T
I saw it on firmware science and set my clock to July 4th as it wouldn't update at first. Said it was up to date. Set my date to July 4th and it updated! Camera is sweet! Fingerprint works way better for me and battery is better as well. Phone feels "smoother" all around as well. After a cache wipe and a reboot
mistermidas said:
Usually I'd be in the same boat as you, but since I'm on Sprint it wouldn't even let me sideload the firmware science update
Click to expand...
Click to collapse
I've been recovering from Samsung/Odin modding addiction for about 3-4 years now. My first relapse and this happens
I'll give it a few hours, and if an Odin file for ASF6 doesn't show up somewhere, I'll just suck it up and Factory reset.
On a side note does anyone see their signatures or others???? I have had one for ages, it's in my control panel but not showing and I don't see anybody elses....
iteam said:
On a side note does anyone see their signatures or others???? I have had one for ages, it's in my control panel but not showing and I don't see anybody elses....
Click to expand...
Click to collapse
Seems fine to me. Your sig is:
S10+ Ceramic White 512 GB
PIE 9.0 / ONE UI
Samsung EVO 128GB Class 10 / UHS-I 100MB/sec
Click to expand...
Click to collapse
mistermidas said:
What carrier do you have? Nothing showing up anywhere for Sprint yet.
Click to expand...
Click to collapse
innocentone1 said:
There was an article about it. ATT is the only US carrier to get the night mode feature (ASF6)
The rest of us will have to wait.
Click to expand...
Click to collapse
mistermidas said:
Well that sucks ass....
Click to expand...
Click to collapse
Atomicmuffin said:
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Click to expand...
Click to collapse
mistermidas said:
Usually I'd be in the same boat as you, but since I'm on Sprint it wouldn't even let me sideload the firmware science update
Click to expand...
Click to collapse
iteam said:
AT&T
I saw it on firmware science and set my clock to July 4th as it wouldn't update at first. Said it was up to date. Set my date to July 4th and it updated! Camera is sweet! Fingerprint works way better for me and battery is better as well. Phone feels "smoother" all around as well. After a cache wipe and a reboot
Click to expand...
Click to collapse
Atomicmuffin said:
I've been recovering from Samsung/Odin modding addiction for about 3-4 years now. My first relapse and this happens
I'll give it a few hours, and if an Odin file for ASF6 doesn't show up somewhere, I'll just suck it up and Factory reset.
Click to expand...
Click to collapse
Atomicmuffin said:
Seems fine to me. Your sig is:
Click to expand...
Click to collapse
Ugh, why don't I see mine or anybody elses? I logged out and logged back in, checked my control panel settings and nothing... Not a huge deal but I don't know why
The new update has also dropped for Verizon. So Verizon and AT&T are the only ones with the new night mode for the camera.
Atomicmuffin said:
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Click to expand...
Click to collapse
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
innocentone1 said:
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
Click to expand...
Click to collapse
Regardless of using HOME_CSC? Well that's a shame.
Damn. Back when I was flashing stuff daily I was on USC & VZW, so this is my first rodeo with an ATT phone. Thanks for the heads up.
innocentone1 said:
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
Click to expand...
Click to collapse
You sure about that? Last 2 phones I've had were purchased directly from Samsung, but ATT model, and I never received a single OTA update from ATT. So I've resorted to upgrading via Odin. Haven't had to do a factory reset once.
Lavman72 said:
You sure about that? Last 2 phones I've had were purchased directly from Samsung, but ATT model, and I never received a single OTA update from ATT. So I've resorted to upgrading via Odin. Haven't had to do a factory reset once.
Click to expand...
Click to collapse
Hmm. Now I just don't know what to think
waiting for U1 firmware
innocentone1 said:
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
Click to expand...
Click to collapse
You would be wrong. I Odin'd numerous times on the S9+ and twice on the 10+. As long as you use Home CSC, it doesn't wipe. The 10+ says it's wiping but doesn't (or is only wiping cache).
Using an update.zip on the other hand wipes an ATT device.
---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------
Atomicmuffin said:
Hmm. Now I just don't know what to think
Click to expand...
Click to collapse
As long as you use a HOME CSC, Odin does NOT wipe an ATT device. Only if you use an update.zip
todd3835 said:
You would be wrong. I Odin'd numerous times on the S9+ and twice on the 10+. As long as you use Home CSC, it doesn't wipe. The 10+ says it's wiping but doesn't (or is only wiping cache).
Using an update.zip on the other hand wipes an ATT device.
---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------
As long as you use a HOME CSC, Odin does NOT wipe an ATT device. Only if you use an update.zip
Click to expand...
Click to collapse
That's what I thought (about HOME_CSC, I mean).
Are you referring to sideloading a FOTA update ZIP via ADB? Maybe i'm missing something, but before I sideload anything I always comb through the updater-script. Old habit from CWM-Zip flashing. Nothing seemed out of the ordinary, nor do I recall seeing the userdata partition even mentioned in it, let alone any kind of factory reset initiation.
I DO recall seeing "Failed to update vendor image." towards the end of the sideload. When checking the last.log, looked pretty messed up. Almost like a kind of corruption of some kind. The log is gone now though, because first thing I did was Wipe Cache when it hung at "Starting Android"
May be too early to know for sure but I think I'm finally getting good reception and the signal strenth is now displaying in settings/connections/mobile networks.
On Verizon with the ASD9 firmware it would display not available now its giving me actually numbers.