As I sit here and wait for 2.2.2 for my N1, it occurs to me I know nothing about the OTA process. A quick search of XDA reveals some of the same questions but few answers. Here's some things I'd like explained:
- How does the rollout process work?
- Are they controlled by HTC or Google or Tmobile?
- How does the selection of IMEIs work?
- How are the carriers involved in the distribution process?
- Is country of residence a factor?
- Does the update process work faster over WiFi? Or maybe require a cellular data connection?
- What does *#*#CHECKIN#*#* do exactly?
- What does clicking Settings...About Phone...System Updates do?
- Is the signing and structure of the update package understood?
- Would I get an OTA if I had no cellular data plan (only WiFi)?
Can anyone point me to a thread/page/wiki that has these answers?
To the best of my knowledge:
James Bell said:
As I sit here and wait for 2.2.2 for my N1, it occurs to me I know nothing about the OTA process. A quick search of XDA reveals some of the same questions but few answers. Here's some things I'd like explained:
- How does the rollout process work?
Click to expand...
Click to collapse
Google puts the update on their server, your phone checks in for updates every once in a while. If the Google servers tell your phone there is an update, it downloads it and prompts you to install it.
- Are they controlled by HTC or Google or Tmobile?
Click to expand...
Click to collapse
100% Google controlled
- How does the selection of IMEIs work?
Click to expand...
Click to collapse
No one knows for sure. Seemingly random unless you have one of the "Holiday" Nexus Ones which seem to get preferential treatment to update first. Not always the case though.
- How are the carriers involved in the distribution process?
Click to expand...
Click to collapse
Aside from the data being downloaded across their network, the carriers are not involved in any way with the Nexus One's update distribution.
- Is country of residence a factor?
Click to expand...
Click to collapse
I don't believe so. It goes off your IMEI and whether Google has chosen you.
- Does the update process work faster over WiFi? Or maybe require a cellular data connection?
Click to expand...
Click to collapse
That depends on the speed of your wifi or 3G connection. It is like downloading any other file off the internet (wifi will probably be faster).
- What does *#*#CHECKIN#*#* do exactly?
Click to expand...
Click to collapse
It forces your phone to check Google's servers for an update. But, if your IMEI isn't in the approved pool that the update is being sent to, it will NOT cause your phone to get the update ahead of time. IMO, the checkin code is worthless as you will almost always see the update file posted here long before your phone will tell you there is an update.
- What does clicking Settings...About Phone...System Updates do?
Click to expand...
Click to collapse
That only lists updates your phone has already downloaded and are ready to apply. It does not check for new updates.
- Is the signing and structure of the update package understood?
Click to expand...
Click to collapse
Yes.
- Would I get an OTA if I had no cellular data plan (only WiFi)?
Click to expand...
Click to collapse
Yes.
Can anyone point me to a thread/page/wiki that has these answers?
Click to expand...
Click to collapse
The wiki is located in a link at the top, labeled appropriately enough "WIKI".
It may not have these specific answers, but is an excellent place to go before asking any questions here.
Oh, and one more thing. You have posted this in the wrong forum. This forum is not for questions. The forum labeled "Nexus One Q&A" would have been the appropriate forum to start this thread in.
I have a korean nexus and it got updates which slighty different from stock rom, i think it maded by kt itself, not google.
My opinion is thats because its a operator model. And yours t-mobile nexuse one wouldnt be one of the first wholl recieve ota.
Btw my korean nexus stll didnt recieved FRG83D
There are no operator models in the US, only Vodafone in Europe and KT in Korea have them.
The updates of the operator ones still come from Google, but they're delayed for testing/modification by the networks.
- What does clicking Settings...About Phone...System Updates do?
That only lists updates your phone has already downloaded and are ready to apply. It does not check for new updates.
Click to expand...
Click to collapse
Curious: Why, for example, sense'd phones can have "check for updates" button, and we have to just stare and wait?
Cheers!
Because HTC decided that's how they wanted it.
Rusty! said:
Because HTC decided that's how they wanted it.
Click to expand...
Click to collapse
Yes, but I can't find any reason to NOT give the option to manually chceck for updates. I had that option in stock android 2.1 on the Milestone, so it can't be to difficult if Moto Europe lazy devs could do that. Am I missing something or it's just illogical?
Hm. Maybe google didn't want hteir servers to be DDoS'd when new update arrives
Rusty! said:
There are no operator models in the US, only Vodafone in Europe and KT in Korea have them.
The updates of the operator ones still come from Google, but they're delayed for testing/modification by the networks.
Click to expand...
Click to collapse
Hi Rusty, how do define operator models? I have FRG83D installed! Before that I had FRF91 (Vodafone)! Is my phone still a operator model? In which way does it effect the OTA process?
Unless you've deliberately made the effort to switch to the untouched Google firmware, you'll still have the Voda variant.
What this means is you will receive updates much later than the Google bought handsets, if you tried to install the 2.2.2 update (FRG83G), you'll find that it will fail.
Rusty! said:
Unless you've deliberately made the effort to switch to the untouched Google firmware, you'll still have the Voda variant.
What this means is you will receive updates much later than the Google bought handsets, if you tried to install the 2.2.2 update (FRG83G), you'll find that it will fail.
Click to expand...
Click to collapse
I've unlocked the bootloader and installed FRG83D. Prior to that I had FRF91 2.1 Vodafone Version!
Got ya. You are on par with the Google bought phones then.
Rusty! said:
Got ya. You are on par with the Google bought phones then.
Click to expand...
Click to collapse
Thanks Rusty!
it's really a hard work to wait OTA with google's official version. So I can't wait and just flash a lot of vendor room from the XDA.
the "checkin" seemed to force the phone to check update...
I've rooted my FRG83D, and received my 2.2.2 yesterday, but failed to go through the update due to not found carhome.apk which I deleted manually...
Related
So that's it-- will I get updates without hacking the phone since it's unlocked? I'm not really looking to hack, ROM, etc.
Also-- the locale I had to choose was definitely not the US. Philippines, Singapore and Thailand were my options... so far this hasn't caused me any problems. Does it matter?
Data & SMS/MMS are working great. I am in LOVE.
Finally, is there a way to disable the HTC theming? I love it the way it is but would like to get a better understanding of what is pure Android and what is the HTC theming?
Thanks and best regards,
THATCH
thatchman1 said:
So that's it-- will I get updates without hacking the phone since it's unlocked? I'm not really looking to hack, ROM, etc.
Click to expand...
Click to collapse
I believe the Android phones currently on the market use an OTA (over the air) updating feature. Since AT&T does not have the Hero, they are not going to be providing updates. To get updated software/firmware, you would have to download and install a ROM, either from here or HTC's website.
Also-- the locale I had to choose was definitely not the US. Philippines, Singapore and Thailand were my options... so far this hasn't caused me any problems. Does it matter?
Click to expand...
Click to collapse
If you are fine running a non-US locale, then more power to you. The first thing I did when I got my Hero was to install a custom ROM on it which included an application which let me set US as an locale.
martey said:
I believe the Android phones currently on the market use an OTA (over the air) updating feature. Since AT&T does not have the Hero, they are not going to be providing updates. To get updated software/firmware, you would have to download and install a ROM, either from here or HTC's website.
Click to expand...
Click to collapse
Thus far, the GSM Hero has never received an OTA update, though the facility does exist. The update to 2.73 was delivered as an RUU that you needed to manually load onto the phone. I expect future updates to be delivered the same way.
Regards,
Dave
Just curiosity: Are people that are reporting "bugs" (though to me it sounds like apps that need to be updated for full compatibility with Froyo) running the OTA updated 2.2, or manually updated 2.2?
Edit: Changed name to Froyo(HACK) as recommended by someone since no one seems to be running a genuine OTA updated Froyo
Manually-updated using the official signed update from Google, for me. I don't have most of the bugs that have been reported here; the only one I'm currently aware of is that two applications I updated via the market this morning are no longer shown in the "Downloads" list, although they are labeled as "installed" when I search for them in the market. Other than that, no problems here.
crackness said:
Just curiosity: Are people that are reporting "bugs" (though to me it sounds like apps that need to be updated for full compatibility with Froyo) running the OTA updated 2.2, or manually updated 2.2?
Click to expand...
Click to collapse
No one on the entirety of XDA has upgraded via the OTA update. Everyone hacked.
(The OTA was press-only for people who attended Google I/O.)
Paul22000 said:
No one on the entirety of XDA has upgraded via the OTA update. Everyone hacked.
(The OTA was press-only for people who attended Google I/O.)
Click to expand...
Click to collapse
Ahhh.... I thought that was only speculation :/
/trying my hardest not to ***** and moan...
Paul22000 said:
No one on the entirety of XDA has upgraded via the OTA update. Everyone hacked.
(The OTA was press-only for people who attended Google I/O.)
Click to expand...
Click to collapse
Exactly.. About time more people acknowledged this.
logger said:
Exactly.. About time more people acknowledged this.
Click to expand...
Click to collapse
I understand what you're saying.
However Google have released an OTA update to the MEDIA!
They'll grab this with both hands and show how the NEW messiah has fallen over again and how we should have all bought iPhones.....
I do believe this Froyo is HIGHLY unpolished and very dissapointing. It should have been released when it was fully ready.
I'm desperately trying to get back to CM but it seems to have screwed my phone and I'm stuck........
wmm said:
Manually-updated using the official signed update from Google, for me. I don't have most of the bugs that have been reported here; the only one I'm currently aware of is that two applications I updated via the market this morning are no longer shown in the "Downloads" list, although they are labeled as "installed" when I search for them in the market. Other than that, no problems here.
Click to expand...
Click to collapse
The market problem has a fix in this thread:
http://forum.xda-developers.com/showthread.php?p=6572697#post6572697
google needs to provide an official fix for the issue so we don't have to use the hack one
punk4bc said:
The market problem has a fix in this thread...google needs to provide an official fix for the issue so we don't have to use the hack one
Click to expand...
Click to collapse
yoo mean a hack for a hack
I think I'll just wait for the official Google OTA.
Good thing that people around here are chasing up all the last minute bugs for Google though. I am sure they would prefer to see them now rather than after releasing it to the general public.
logger said:
yoo mean a hack for a hack
I think I'll just wait for the official Google OTA.
Good thing that people around here are chasing up all the last minute bugs for Google though. I am sure they would prefer to see them now rather than after releasing it to the general public.
Click to expand...
Click to collapse
good point lol
I'm waiting for the official Google too
Yeah I updated with Paul's version and I would have stayed on froyo but having annoying camera bugs.
I dont think Google meant this as an actual release since you Market isn't allowing protected apps etc with the froyo fingerprint. etc.
So i'm back on Cyan and all is well with the world.
I did however keep the newer radio to test it out.
It would be great if someone around here could change EVERY thread title that mentions this version to FROYOHACK so that once the real official one is released, we dont have to wade through all this pre-release BS. I know it is not possible but just thought.
What were your camera bugs?
I did Paul's too and mine worked 100%. Still have the new radio and according to speed tests it is doing better than the old one
punk4bc said:
What were your camera bugs?
I did Paul's too and mine worked 100%. Still have the new radio and according to speed tests it is doing better than the old one
Click to expand...
Click to collapse
I've posted it in the general forum. QIK app didn't work and if you use the stock camera app and slide to the camcorder then BACK to the camera, N1 would crash.
I posted the logcat and it appears there are some incompatibilities somewhere deep. I tried every kind of wipe and 'band-aid' that I could to get it working and failed miserably.
But I figured since i'm on an AT&T N1 that this release wasn't intended for me and there must be some kind of subtle differences.
*shrug* we'll see.
wmm said:
Manually-updated using the official signed update from Google, for me. I don't have most of the bugs that have been reported here; the only one I'm currently aware of is that two applications I updated via the market this morning are no longer shown in the "Downloads" list, although they are labeled as "installed" when I search for them in the market. Other than that, no problems here.
Click to expand...
Click to collapse
One thing I have learn is a app has a widget and it is moved to the sdcard it will show install but not show. I moved these to the phone and they show now.
logger said:
It would be great if someone around here could change EVERY thread title that mentions this version to FROYOHACK so that once the real official one is released, we dont have to wade through all this pre-release BS. I know it is not possible but just thought.
Click to expand...
Click to collapse
Hey thanks MOD (or whoever did it) for renaming the thread. Excellent Job...
I don't know if it's a bug, but I can't find FM radio anywhere... and I believe it was announced.
logger said:
Hey thanks MOD (or whoever did it) for renaming the thread. Excellent Job...
Click to expand...
Click to collapse
Hah, as OP, I changed it. I didn't realize (though I had read it somewhere else) that the only people who got the OTA update were press/developers who went to I/O.
FOR THOSE JUST READING NOW: According to Paul (and where ever else I read online), anyone else with Froyo updated manually, so take current issues with a grain of salt.
Deusdies said:
I don't know if it's a bug, but I can't find FM radio anywhere... and I believe it was announced.
Click to expand...
Click to collapse
The FM radio stuff was never announced OFFICIALLY. I do remember it being something rumored, but I don't ever remember Google saying it was an addition to Froyo. AND, even if it was announced, read my reiteration above about no normal consumers having the Official OTA update to Froyo.
ibegary said:
I've posted it in the general forum. QIK app didn't work and if you use the stock camera app and slide to the camcorder then BACK to the camera, N1 would crash.
I posted the logcat and it appears there are some incompatibilities somewhere deep. I tried every kind of wipe and 'band-aid' that I could to get it working and failed miserably.
But I figured since i'm on an AT&T N1 that this release wasn't intended for me and there must be some kind of subtle differences.
*shrug* we'll see.
Click to expand...
Click to collapse
I running Froyo on the AT&T Nexus on Telus here in Canada and so far I am having no issues, maybe some app that you installed is causing the crash...weird tho.
crackness said:
Hah, as OP, I changed it. I didn't realize (though I had read it somewhere else) that the only people who got the OTA update were press/developers who went to I/O.
FOR THOSE JUST READING NOW: According to Paul (and where ever else I read online), anyone else with Froyo updated manually, so take current issues with a grain of salt.
Click to expand...
Click to collapse
Sort of ironic now, that people will avoid this thread in favour of ones without HACK in the title, as they will not want to accept that they have a hacked version on their device You cant win I guess.
Motorola XOOM users on the Verizon Wireless network: starting tonight, a maintenance release is rolling out to you in phases, so watch for a notification on your device that will tell you when it’s ready for download. The update includes required enhancements to support Adobe® Flash® Player 10.2 (coming soon); it also includes a fix for a bug we identified with Daylight Savings time, so be sure to install it!
Click to expand...
Click to collapse
No flash, just support for it... http://www.facebook.com/motorola
Update: Flash 10.2 announced release on market MAR18 http://blogs.adobe.com/flashplayer/2011/03/update-on-flash-player-10-2-for-mobile-devices.html
And, Flash leaked! http://www.multiupload.com/5FOUMVZI32
Manual OTA instructions via Koush (ROOT REQUIRED): http://www.koushikdutta.com/2011/03/manually-updating-your-rooted-xoom.html
well, maybe this will fix my wierd clock issue today... hmmm
At least this shows how quickly updates will come... I guess.
how will us with wifi only get this?
Any update is good news at this point I think. I wonder if there is any harm in updating, ie will it remove the ability to root and what not? I wish they would provide more details on what exactly the patch does. Also, it clearly says on the Verizon network, what about those not on it and are only on wifi?
Sent from my Xoom using XDA Premium App
Sirchuk said:
Any update is good news at this point I think. I wonder if there is any harm in updating, ie will it remove the ability to root and what not? I wish they would provide more details on what exactly the patch does. Also, it clearly says on the Verizon network, what about those not on it and are only on wifi?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
MY droid always popped up updates even when I was only on wifi. I imagine we'll all get it or someone will post the update.zip anyway.
I'm curious if the Tegra 2 versions of flash (10.1) floating around will have something to interact with, and start functioning. They have with everything else. As soon as I get the OTA (no 3G), I have a folder full of them in my Dropbox.
AndyMan386 said:
how will us with wifi only get this?
Click to expand...
Click to collapse
Through WiFi?
Droid-Life has some more details.
http://www.droid-life.com/2011/03/1...tonight-includes-adobe-flash-10-2/#more-28145
Why cant people do more research?
Wifi only will get the update too...
http://www.droid-life.com/2011/03/1...olling-out-tonight-includes-adobe-flash-10-2/
Has anyone figured out how to force a check in on the Xoom?
Inphinitizeit said:
Has anyone figured out how to force a check in on the Xoom?
Click to expand...
Click to collapse
Question of the day. No dialer :/
yesssssssssssss
Glad to see an update but there is nothing listed to get excited about except a possible problem with the upcoming daylight savings time switch. Who cares about the flash update since it does not actually include it. But this will be a good test run to see how the updates are sent out and applied.
Cann't wait for the update to start
ZanshinG1 said:
Question of the day. No dialer :/
Click to expand...
Click to collapse
You can force a check by rebooting. Not the best method, but it works.
Why do unlocked xooms need to get relocked?
I understand why you need to be on stock boot.img but i don't understand why you need to have the device relocked to get the update.
It makes no sense.
ZanshinG1 said:
You can force a check by rebooting. Not the best method, but it works.
Click to expand...
Click to collapse
According to the system update tab this didn't happen in 3 reboots since the announcement. Still last check at 5:20. Really want to see if any of the 10.1 Tegra versions work after this. I've been frantic to have Flash lately (PlayOn/Netflix).
Sent from my Xoom using XDA Premium App
morbos said:
According to the system update tab this didn't happen in 3 reboots since the announcement. Still last check at 5:20. Really want to see if any of the 10.1 Tegra versions work after this. I've been frantic to have Flash lately (PlayOn/Netflix).
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
It might have a minimum time between checkins. Mine said 9:20am, then showed current time for last checkin when I rebooted.
So would it be fair to say that those of us who have rooted should wait until this update is released to see if in fact we really do need to revert back to stock/locked condition? Because I'd really be pissed if we had to lose all of the data on our Xooms just for this update, when very few of us have actually changed anything with the boot.img, etc. I mean back when I first rooted my N1 but before I flashed custom ROMs, I never had to wipe back to stock to receive OTA updates, so why would that be the case here??
We are having 3 official versions of the android 5.1 showing up. LMY47D, LMY47E, LMY47I. Some say they are carrier specific, some say they are not, and others have no idea what is going on. So, let’s discuss all the versions here and why some may or may not think that each one is carrier specific.
My main questions to those that say they are carrier specific is, I though Nexus 6 was not carrier locked and can work on all 4 carriers just by swapping the sim card. If that is the case, the how can we have carrier specific updates? I guess in theory it can be related to the sim that we have in our phones, so then by changing the sim from one carrier to another we will need to/offered the other software version?
There was a thread pointing to a twitter from someone at T-Mobile that explained this. As I understand it, Google changed the way it handles the minor network tweaking carriers need to make for their network and SIMs. Any OS would work with any phone but the carrier specific version will work slightly better. They can't make any changes to apps or the OS, just some network parameters. I'm oversimplifying but that's what I got out of it.
mgerbasio said:
There was a thread pointing to a twitter from someone at T-Mobile that explained this. As I understand it, Google changed the way it handles the minor network tweaking carriers need to make for their network and SIMs. Any OS would work with any phone but the carrier specific version will work slightly better. They can't make any changes to apps or the OS, just some network parameters. I'm oversimplifying but that's what I got out of it.
Click to expand...
Click to collapse
hmm, i need to find that.
I'll assume because of the N6's "all carrier compatibility" they have released carrier specific optimizations in their different builds. Unfortunately, and in my opinion, Google caved with the N6 to get better sales. It is what it is and I'm just thankful I have a phone that I can still do as I please with it. It would be nice, and thoughtful, if the Goog would release official information on what the heck they are doing with these different builds.... is that so hard?!
So does anyone know which one matches which carrier?
kdoggy said:
So does anyone know which one matches which carrier?
Click to expand...
Click to collapse
if its carrier specific, D is sprint, E is verizon, M is t- mobile.
edit, since canada is getting version D right now, D must be just general. Who knows. lol
So nothing specific to AT&T yet? Just curious to try a carrier specific one and see if data is faster.
stas333 said:
hmm, i need to find that.
Click to expand...
Click to collapse
Try these...
http://forum.xda-developers.com/showpost.php?p=59535507&postcount=90
http://forum.xda-developers.com/showpost.php?p=59535608&postcount=92
Not so much. 47e brought in new camera proprietary binaries too so it isn't just carrier specific
stas333 said:
if its carrier specific, D is sprint, E is verizon, M is t- mobile
Click to expand...
Click to collapse
Can't be carrier specific, I am on 3 Uk and have the D variant.
Sent from my Nexus 6 using XDA Free mobile app
I would weigh in and say that if a carrier makes a change needing a new build, it gets submitted to Google, tested and the changes only affect those with that carrier, likely due to SIM detection.
The fact that the phone has radios for all the carriers means that this can be possible, tweaks to a radio or band your phone may not use won't affect you ... and at the same time Google can toss in some tweaks across the board for all of us. I suppose that what makes it confusing is that while any of them can be flashed, they'll only push out the one to a carrier specific imei set, like E to Verizon.
For the normal user, they get an update that makes their specific network functionality better, and the others are not pushed for that, but may get the overall tweaks in the next update to their phone in general, or if before that there is a carrier requested tweak for them that requires a build release.
But we here, see all of this because we have that "wanting to have the latest build" mentality, the questions arise.
westers035 said:
Can't be carrier specific, I am on 3 Uk and have the D variant.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
What was suggested was that every build would work but a specific variant would be slightly better. For example m would be better for t mobile but any variant would work. For carriers other than sprint, verizon and t mobile I don't know if there'd be any real difference.
Has anyone on ATT received a 5.1 OTA?
If so, which one?
sykopompos said:
Not so much. 47e brought in new camera proprietary binaries too so it isn't just carrier specific
Click to expand...
Click to collapse
I knew something seemed different about the camera. Photos in low light looked better to me.
Sent from my Nexus 6
stas333 said:
if its carrier specific, D is sprint, E is verizon, M is t- mobile
Click to expand...
Click to collapse
Exactly. But some will never admit it
The real question is this:
Can someone on T-mobile who is on 47D or 47E see if they get an OTA update to 47M?
If the builds are carrier specific, would google push them based off the the SIM or the IEMI? It would have to be the SIM right? For people that purchased a phone through Google/Motorola and are using it on Verizon. Or switch networks, whatever the case may be.
buschris said:
Exactly. But some will never admit it
Click to expand...
Click to collapse
Admit what? If it it carrier specific then explain why E has Camera updates that D does not? What does that have to do with the carrier?
If everything was the same except for the Radio.img then I'd buy the carrier only thing, but there are more that's changed.
buschris said:
Exactly. But some will never admit it
Click to expand...
Click to collapse
i edited my post. D is not Sprint. It must be general version since Canada is getting it right now.
buschris said:
Exactly. But some will never admit it
Click to expand...
Click to collapse
Because its not true, then why did i get the 47D version in the Netherlands Europe. Btw i also have Sprint and Verizon files in my firmware, so that tells me they are universal roms that contain specific (network) optimisations that will be triggered when using a specific carrier.
phoenixus said:
The real question is this:
Can someone on T-mobile who is on 47D or 47E see if they get an OTA update to 47M?
Click to expand...
Click to collapse
According to the T-Mobile Support page, the requirements to upgrade to 47M is that your current build must be LRX22C, so I'm guessing that those with 47D or 47E won't be able to get an OTA update to 47M.
I'm on T-Mobile with 47D, and I didn't receive any OTA update as of now.
Got this update today, still no '*****by'.
What's that about then, Samsung?
kxdaorbit said:
Got this update today, still no '*****by'.
What's that about then, Samsung?
Click to expand...
Click to collapse
Evidently some are, don't know if UK or US. I've recieved the update plus the July security update but I have Bixby disabled, not interested.
https://forum.xda-developers.com/galaxy-s8+/how-to/to-try-bixby-t3641558
https://forum.xda-developers.com/galaxy-s8+/help/bixby-voice-t3599867
ggrant3876 said:
Evidently some are, don't know if UK or US. I've recieved the update plus the July security update but I have Bixby disabled, not interested.
https://forum.xda-developers.com/galaxy-s8+/how-to/to-try-bixby-t3641558
https://forum.xda-developers.com/galaxy-s8+/help/bixby-voice-t3599867
Click to expand...
Click to collapse
I think these are US.
Just updated feels smoother somewhat.
Battery life is much better...
We were all waiting for the new update to come but Once more Samsung has manage to destroy some things
One of them is screen auto light adjustment... At least at Exynos AQG5 version
Before the update you could just adjust the bar wherever you like and then with one off - on to auto switch you have return to full auto light adjustment...
Now this is impossible
With auto on if you move the bar this setting is saved like the ideal auto lighting condition and stays that way...that means that auto lighting is working good but from the base of your previous adjustment and not full stock auto.. If you deactivate and activate again the auto switch nothing happens because of the previous "saved condition"
Search 1st b4 post!
kxdaorbit said:
Got this update today, still no '*****by'.
What's that about then, Samsung?
Click to expand...
Click to collapse
Why starting this thread when there is already a BIG thread about FW-updates?
https://forum.xda-developers.com/galaxy-s8+/how-to/official-stock-firmware-update-odin-t3582175
henklbr said:
Why starting this thread when there is already a BIG thread about FW-updates?
https://forum.xda-developers.com/galaxy-s8+/how-to/official-stock-firmware-update-odin-t3582175
Click to expand...
Click to collapse
Sorry, but I don't see 'Moderator' after your name. If the mods have no problem with this thread, why have you? If this thread has been created inappropriately I'm sure they'll close it.
With all due respect, if you don't like it, please just move on and stop trolling.
Plus, there are plenty of threads here about updates that are not in the firmware thread.
kxdaorbit said:
Sorry, but I don't see 'Moderator' after your name. If the mods have no problem with this thread, why have you? If this thread has been created inappropriately I'm sure they'll close it.
With all due respect, if you don't like it, please just move on and stop trolling.
Plus, there are plenty of threads here about updates that are not in the firmware thread.
Click to expand...
Click to collapse
He started the thread he linked. Personally, I like threads like this one that speak to specific updates as they're released. I don't feel like wading through 40 pages of a thread when 37 have nothing to do with my particular phone/region.
BarryH_GEG said:
He started the thread he linked. Personally, I like threads like this one that speak to specific updates as they're released. I don't feel like wading through 40 pages of a thread when 37 have nothing to do with my particular phone/region.
Click to expand...
Click to collapse
^This
henklbr said:
Why starting this thread when there is already a BIG thread about FW-updates?
https://forum.xda-developers.com/galaxy-s8+/how-to/official-stock-firmware-update-odin-t3582175
Click to expand...
Click to collapse
That thread is a nightmare to read through. Sometimes when a new update comes out especially when it's in a new region, it's useful to read a nice fresh thread from page one detailing issues.
Also that thread is for ODIN not OTA.
Carrier update?
kxdaorbit said:
Got this update today, still no '*****by'.
What's that about then, Samsung?
Click to expand...
Click to collapse
Hi mate, just wondering if your S8+ is on a carrier?
I've got the unlocked version and I don't have any updates, I've also checked SamMobile and Updato and can't find an unlocked one. However, I did see the update for Vodafone.
Also, does anyone know if I'll get any bloatware if I flash the Vodafone version?
Thanks!
-Noob
thedarkmunk said:
Hi mate, just wondering if your S8+ is on a carrier?
I've got the unlocked version and I don't have any updates, I've also checked SamMobile and Updato and can't find an unlocked one. However, I did see the update for Vodafone.
Also, does anyone know if I'll get any bloatware if I flash the Vodafone version?
Thanks!
-Noob
Click to expand...
Click to collapse
My carrier's Sky Mobile, who 'piggyback ' off the O2 network, but I don't get any O2 bloat.
My version is XEU If that makes a difference, the wierd thing is that on Updato it showed a date for XEU of the 14th of July, but I only got it on the 24th. Would be interesting to know whether anyone from O2 has received this yet.
Not sure if flashing Vodafone will install their bloat like inserting their SIMS would.
The UK roll out never makes much sense. Some network firmwares are released before the generic ones, but its not consistent and can change at anytime. The only consistent thing is that EVR (EE) is always last, and usually skips releases entirely, often as many as 3 or 4 releases.
tsiglas said:
We were all waiting for the new update to come but Once more Samsung has manage to destroy some things
One of them is screen auto light adjustment... At least at Exynos AQG5 version
Before the update you could just adjust the bar wherever you like and then with one off - on to auto switch you have return to full auto light adjustment...
Now this is impossible
With auto on if you move the bar this setting is saved like the ideal auto lighting condition and stays that way...that means that auto lighting is working good but from the base of your previous adjustment and not full stock auto.. If you deactivate and activate again the auto switch nothing happens because of the previous "saved condition"
Click to expand...
Click to collapse
This is how stock Android works. Auto brightness still works, it's just based off where you set it, not where the OS decided it should be.
The service mode code *#2683662# which allows you to select specific Lte bands as well as enable 4 mimo no longer works after the update, just says not supported, anyone have any workarounds or reasons why?
Just got the update , No difference i can see
Does the Bixby remap apps like bxactions still work on this update?
HUYI said:
Does the Bixby remap apps like bxactions still work on this update?
Click to expand...
Click to collapse
I'm on ".... AQG5"
and bxActions works fine.
You have to enable work around
in bxActions
See screenshot.
unlocked btu device and still no update
still on june security patch