Related
I am trying to sign up for the Android N beta but get this notification on the site:
Unfortunately, there are no eligible devices associated with this Google account.
I am not sure why, signed in under the right Google account.
lazerus06 said:
I am trying to sign up for the Android N beta but get this notification on the site:
Unfortunately, there are no eligible devices associated with this Google account.
I am not sure why, signed in under the right Google account.
Click to expand...
Click to collapse
same account that's on your nexus 6?
I had the same issue, thought it was because I was on a custom ROM , changed to stock and it was the same. Manually flashed the beta through adb and even when I'm on android N its still the same. Weird
I didn't want to flash N and be locked out of updates
Add another Google account to your phone. Then go to google.com/android/beta and sign in to the same account that you recently added. In 20 minutes or so, you'll have the ability to enroll
Same thing here, this is what worked for me:
Clear Data on Android Device Manager
Force stop it.
Go to settings > security > Device Administrators
Untick, and then re-tick Android Device Manager.
Open it, sign in with the Google account you want to use.
Then, check online again if your device is visible.
Idk about Custom ROMs, but this worked fine for me. My N6 appears on the website now.
I just made a new Google account and now I just have two Google accounts which is fine with me. Soon as I signed in on my N6 with new account my device immediately showed up on beta page.
I just synced both accounts so I can keep all my contacts and bookmark
Just flash the images with fastboot, Google has clarified you will still get ota preview updates if you enroll in the beta program.
From the dev page:
"If you decide you want to get OTA updates after manually flashing a device, all you need to do is enroll the device in the Android Beta Program. You can enroll the device at any time to receive the next Preview update over the air."
murtaza02 said:
Same thing here, this is what worked for me:
Clear Data on Android Device Manager
Force stop it.
Go to settings > security > Device Administrators
Untick, and then re-tick Android Device Manager.
Open it, sign in with the Google account you want to use.
Then, check online again if your device is visible.
Idk about Custom ROMs, but this worked fine for me. My N6 appears on the website now.
Click to expand...
Click to collapse
How do you clear data on Android Device Manager? It's not showing up under Settings > Apps (Show System Apps enabled) nor Titanium Backup. But it does show up as a Device Administrator.
MrBrady said:
How do you clear data on Android Device Manager? It's not showing up under Settings > Apps (Show System Apps enabled) nor Titanium Backup. But it does show up as a Device Administrator.
Click to expand...
Click to collapse
It will always show under device administrators.
You need to install it from the Play Store to be able to clear data. For some odd reason, it's not pre-installed anymore.
Sent from my HTC One_M8
lazerus06 said:
I am trying to sign up for the Android N beta but get this notification on the site:
Unfortunately, there are no eligible devices associated with this Google account.
I am not sure why, signed in under the right Google account.
Click to expand...
Click to collapse
Make a bugrepport and send both the zip and png file as an attachment to googleplay[email protected] and ask for support for your issue. I did the same and its under investigation.
No eligible devices
Im running into the same issue. Nexus 6 shows no eligible devices when trying to enroll. Have made sure device is visible and have gone through every setting in my google account to see if anything would prevent it. My phone does show able to enroll on another account I tried but not mine. I know manual flashing is a way around this but looking for OTA updates. Anyone have any ideas on a fix?
Running into the same issue. Nexus 6 not showing up on beta website. Force stopped/deactivated android device manager. Just getting the ota would be easier. Tried flashing and its telling me I need a newer adb on my mac. bleh
This can help
There's a way to do it without flash boot. Your Nexus 6 usually has tow copies for some reason. Go to the page, click on which devices are available?, and click on the link to play.google/settings, unchecked the checked Nexus 6, and check the unchecked one, then there will be the enroll option, sorry for the long explanation
Drewman50 said:
There's a way to do it without flash boot. Your Nexus 6 usually has tow copies for some reason. Go to the page, click on which devices are available?, and click on the link to play.google/settings, unchecked the checked Nexus 6, and check the unchecked one, then there will be the enroll option, sorry for the long explanation
Click to expand...
Click to collapse
Could you please explain a little more in detail?
murtaza02 said:
Same thing here, this is what worked for me:
Clear Data on Android Device Manager
Force stop it.
Go to settings > security > Device Administrators
Untick, and then re-tick Android Device Manager.
Open it, sign in with the Google account you want to use.
Then, check online again if your device is visible.
Idk about Custom ROMs, but this worked fine for me. My N6 appears on the website now.
Click to expand...
Click to collapse
How you clear data on Android Device Manager?
alainalemany said:
How you clear data on Android Device Manager?
Click to expand...
Click to collapse
In /settings/apps/android device manager/storage.
gee2012 said:
In /settings/apps/android device manager/storage.
Click to expand...
Click to collapse
Well, at least under /settings/apps I have no android device manager.
alainalemany said:
Well, at least under /settings/apps I have no android device manager.
Click to expand...
Click to collapse
You can download it in Google Play.
Zer0_Cool said:
Just flash the images with fastboot, Google has clarified you will still get ota preview updates if you enroll in the beta program.
From the dev page:
"If you decide you want to get OTA updates after manually flashing a device, all you need to do is enroll the device in the Android Beta Program. You can enroll the device at any time to receive the next Preview update over the air."
Click to expand...
Click to collapse
where did you get the beta images for Nexus 6? I am enrolled in the Beta and Nothing is happening. I wonder if they have stopped in anticipation for the upcoming release
Hello I have a P9 EVA-L09C636B134. I live in the US.
EMUI 4.1
Android 6.0
Phone works ok, it feels slow at times. A reboot usually fixes it for a day.
I have my FIRST EVER UPDATE from the updater (B168). Should I do it? It says there are 2 patches: first one is entirely in chinese, the second one says a few things like add watermarks, fix UI issue, optimize startup, etc.
Yes. Why are you still on marshmallow? Nougat has been available since last year.
Twisted Prime said:
Yes. Why are you still on marshmallow? Nougat has been available since last year.
Click to expand...
Click to collapse
I read that the update made their phones use more battery or something. Also I don't know how to manually update, I assumed it would hit this updater thing but I never got an update off the updater. No risk to update you think? I should just do it?
jibbbyy said:
I read that the update made their phones use more battery or something. Also I don't know how to manually update, I assumed it would hit this updater thing but I never got an update off the updater. No risk to update you think? I should just do it?
Click to expand...
Click to collapse
Im on latest firmware and I get 5-6 hours sot, emui 5 performs much better and you can use greenify for better battery life. I think you should update because we are getting emui 8 soon which has machine learning and provides better performance and battery.
Twisted Prime said:
Im on latest firmware and I get 5-6 hours sot, emui 5 performs much better and you can use greenify for better battery life. I think you should update because we are getting emui 8 soon which has machine learning and provides better performance and battery.
Click to expand...
Click to collapse
Ok updated! I don't notice anything different. I am still at EMUI 4.1 and Android 6.0. Should I update these? How do I do it? I am interested in risk free updates. Thanks!
jibbbyy said:
Ok updated! I don't notice anything different. I am still at EMUI 4.1 and Android 6.0. Should I update these? How do I do it? I am interested in risk free updates. Thanks!
Click to expand...
Click to collapse
There should be 2 more OTA updates to get to nougat. Didn't you get them in the built in updater? if not use firmware finder.
Twisted Prime said:
There should be 2 more OTA updates to get to nougat. Didn't you get them in the built in updater? if not use firmware finder.
Click to expand...
Click to collapse
Thanks, but I don't know what OTA is or what firmware finder is.
jibbbyy said:
Thanks, but I don't know what OTA is or what firmware finder is.
Click to expand...
Click to collapse
OTA = Over the Air. Official update delivered by Huawei. Go to Settings > System Update and check for updates.
FirmwareFinder = App to show/browse/download available and future firmware updates on Huaweis servers. Only necessary for those who flash updates manually.
In your case go to System Update. There should be an update. Maybe you have to do this a couple of times to reach latest Nougat-Version. Good luck!
Jan Philipp said:
OTA = Over the Air. Official update delivered by Huawei. Go to Settings > System Update and check for updates.
FirmwareFinder = App to show/browse/download available and future firmware updates on Huaweis servers. Only necessary for those who flash updates manually.
In your case go to System Update. There should be an update. Maybe you have to do this a couple of times to reach latest Nougat-Version. Good luck!
Click to expand...
Click to collapse
Yea so Like I said this update was the first that ever showed up in the "updater"... And there are no more. I always thought its cuz I live in the US but idk
Twisted Prime said:
There should be 2 more OTA updates to get to nougat. Didn't you get them in the built in updater? if not use firmware finder.
Click to expand...
Click to collapse
Hello,
I have firmware finder. Can you tell me how to properly update my phone using this? I have never used it and only received one OTA update EVER on my phone.
jibbbyy said:
Hello,
I have firmware finder. Can you tell me how to properly update my phone using this? I have never used it and only received one OTA update EVER on my phone.
Click to expand...
Click to collapse
1. Set proxy settings on your wifi: (Server: localhost Port: 8080)
2. Search your model number
3. Select an update package (FullOTA-MF recommended) (FullOTA-MF-PV for android version updates)
4. Select in-app proxy (should get a notification proxy is running)
5. Download the package in system updater
Twisted Prime said:
1. Set proxy settings on your wifi: (Server: localhost Port: 8080)
2. Search your model number
3. Select an update package (FullOTA-MF recommended) (FullOTA-MF-PV for android version updates)
4. Select in-app proxy (should get a notification proxy is running)
5. Download the package in system updater
Click to expand...
Click to collapse
Thank you. Perhaps I did something wrong.
1) set proxy to "localhost" and port "8080"
2) my model number was there, clicked it
3) went back to check settings: settings are (show packages for current region OFF, in app proxy port 8080, use simple OFF, show only fullOTA ON)
4) clicked first package (full OTA - MF)
5) clicked in app proxy
6) go to "updater" in settings
7) updater has package, click download and install
8) error "package checksum error." (immediately, before 1% downloaded).
Is it possible I need to not update the most recent one? I am still on android 6.0, EMUI 4.1 and like I said never had any other update OTA before (never used firmware finder). Thank you!
edit: restarted the phone, the package is now gone. Maybe I should do a different package, maybe an older one, not the most recent one?
jibbbyy said:
Thank you. Perhaps I did something wrong.
1) set proxy to "localhost" and port "8080"
2) my model number was there, clicked it
3) went back to check settings: settings are (show packages for current region OFF, in app proxy port 8080, use simple OFF, show only fullOTA ON)
4) clicked first package (full OTA - MF)
5) clicked in app proxy
6) go to "updater" in settings
7) updater has package, click download and install
8) error "package checksum error." (immediately, before 1% downloaded).
Is it possible I need to not update the most recent one? I am still on android 6.0, EMUI 4.1 and like I said never had any other update OTA before (never used firmware finder). Thank you!
edit: restarted the phone, the package is now gone. Maybe I should do a different package, maybe an older one, not the most recent one?
Click to expand...
Click to collapse
Try the next build number up from your current one, one by one. When you get to the last marshmallow build, install the PV package to get to nougat.
Twisted Prime said:
Try the next build number up from your current one, one by one. When you get to the last marshmallow build, install the PV package to get to nougat.
Click to expand...
Click to collapse
Ok thanks, I am trying the oldest build B361 from B168. The download started.
There are 19 total packages, 14 before the first VD package. Holy **** this is going to take forever!
Thank you very much for your help.
Can you explain why these dont come automatically, why I need to do this manual process? Is it because I am in the US?
Also why do I need this proxy port thing?
Thanks again!
jibbbyy said:
Ok thanks, I am trying the oldest build B361 from B168. The download started.
There are 19 total packages, 14 before the first VD package. Holy **** this is going to take forever!
Thank you very much for your help.
Can you explain why these dont come automatically, why I need to do this manual process? Is it because I am in the US?
Also why do I need this proxy port thing?
Thanks again!
Click to expand...
Click to collapse
You just need the proxy so the package goes to your updater. You can set it back to default after.
What model number do you have?
Twisted Prime said:
You just need the proxy so the package goes to your updater. You can set it back to default after.
What model number do you have?
Click to expand...
Click to collapse
I have a L09C636!
jibbbyy said:
I have a L09C636!
Click to expand...
Click to collapse
You should Just need to install b193 (FullOTA) > b394 (PV) and your on nougat
Twisted Prime said:
You should Just need to install b193 (FullOTA) > b394 (PV) and your on nougat
Click to expand...
Click to collapse
There is no option for B193. all of the packages are in the 300's.
The download finished (I think) but it could not install. It said I needed to free up some space. I uninstalled some apps and now it will not let me view the progress (I clicked new custom version, it just takes me back to my setting page). in my notification screen, it as EMU download percetnage at -930% and it is not moving. I tried restarting a few times it all stays the same. Current version still says B168.
edit: I clicked menu and then "download latest full package" and it seemed to have reset everything. Should I try this package again? To repeat, this is the oldest package on firmware finder, B361. I also noticed there are duplicates in firmware finder... and some of the packages are for L09,L19 and L29, these are all safe to download? Should I keep doing oldest 1 by 1?
Thanks again for your help, sorry I am so noob.
jibbbyy said:
There is no option for B193. all of the packages are in the 300's.
The download finished (I think) but it could not install. It said I needed to free up some space. I uninstalled some apps and now it will not let me view the progress (I clicked new custom version, it just takes me back to my setting page). in my notification screen, it as EMU download percetnage at -930% and it is not moving. I tried restarting a few times it all stays the same. Current version still says B168.
edit: I clicked menu and then "download latest full package" and it seemed to have reset everything. Should I try this package again? To repeat, this is the oldest package on firmware finder, B361. I also noticed there are duplicates in firmware finder... and some of the packages are for L09,L19 and L29, these are all safe to download? Should I keep doing oldest 1 by 1?
Thanks again for your help, sorry I am so noob.
Click to expand...
Click to collapse
Just try any PV package.
Only download those for LO9C636
Try this one:
Twisted Prime said:
Just try any PV package.
Only download those for LO9C636
Click to expand...
Click to collapse
There are two PV packages and they look like this
https://imgur.com/a/6VzOgZf
it says all 3 models but when you click on it it says L19 for both...
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
sFranKv said:
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
Click to expand...
Click to collapse
Does doing that wipe my device? Or do I get to keep my stuff?
I wanted to add this for anyone who kept tapping the register button but was simply returned to the banner like nothing happened.
If this is happening and you dont get a toast msg saying "thank you for your support of the One UI Beta" and no OTA follows, try deleting the (beta) Samsung + app data, rebooting and try again.
I tried all day before doing this and got the OTA 5 mins after wiping app data.
Nachorl250 said:
Does doing that wipe my device? Or do I get to keep my stuff?
Click to expand...
Click to collapse
Nope, its a regular update so no need to wipe anything
Already try my apps and games (fortnite, arena of valor) and they work perfect!
Ed Murray said:
I wanted to add this for anyone who kept tapping the register button but was simply returned to the banner like nothing happened.
If this is happening and you dont get a toast msg saying "thank you for your support of the One UI Beta" and no OTA follows, try deleting the (beta) Samsung + app data, rebooting and try again.
I tried all day before doing this and got the OTA 5 mins after wiping app data.
Click to expand...
Click to collapse
Tried everything, to be honest I was just sure that the Samsung+ app would check where you are in the world and if your not on the US it will simply not let you join the beta, the method above worked flawlessly for me!, I'm running One UI at the moment with the dark theme and its awesome!
sFranKv said:
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
Click to expand...
Click to collapse
I have the N960U (T-Mobile) and I am on version ARK1. My version isn't in the list of options? Or will this not work for the 960U from T-Mobile?
BigMosely said:
I have the N960U (T-Mobile) and I am on version ARK1. My version isn't in the list of options? Or will this not work for the 960U from T-Mobile?
Click to expand...
Click to collapse
Keep in mind that this Beta Update its just for the unlocked firmware, if you want to flash the update you need to first flash this firmware: https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/download/N960U1UES1ARJ9/244752/
After that you will be able to flash the Beta Update
sFranKv said:
Keep in mind that this Beta Update its just for the unlocked firmware, if you want to flash the update you need to first flash this firmware: https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/download/N960U1UES1ARJ9/244752/
After that you will be able to flash the Beta Update
Click to expand...
Click to collapse
Can you flash the unlocked firmware without loosing data?
BigMosely said:
Can you flash the unlocked firmware without loosing data?
Click to expand...
Click to collapse
Yes, I did. No data loss.
I flashed the same zrkp from firmware. Science on my us unlocked note 9 with arj9 firmware. It did a full factory reset. I would have done so anyway as I always do with major updates.
Working flawlessly so far.
Edit: 2 exceptions found. Themes are not working and cannot connect to my gear s3. Android wear watch works as expected.
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
papashex said:
I flashed the same zrkp from firmware. Science on my us unlocked note 9 with arj9 firmware. It did a full factory reset. I would have done so anyway as I always do with major updates.
Working flawlessly so far.
Edit: 2 exceptions found. Themes are not working and cannot connect to my gear s3. Android wear watch works as expected.
Click to expand...
Click to collapse
Yea themes are not on beta for some reason, good it worked for you!
GBPackerFanForLife said:
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
Click to expand...
Click to collapse
I would not know, I guess we need to wait until beta 2 update and see, probably won't be getting it and we will need to download the new OTA and flash again on recovery
GBPackerFanForLife said:
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
Click to expand...
Click to collapse
Ok. First of all. Green and gold till I'm dead and cold.
Second of all, if you flash the U1 firmware and sign up for the beta, then you'll get OTAs automatically through settings.
If you flash the U1 firmware and can't get into the beta program, you can download the update.zip from firmware.science. You will have the official beta build, but you won't get updates through settings, because you aren't part of the beta program.
When I run Odin soon as I goto add the AP file Odin freezes an says not responding..I'm useing Windows 10 on my laptop..Any ideas??Also I have put the correct files in odin but it fails Everytime.. I do the BL an the AP an the CP an then for the CSC I use the Home CsC is that correct then hit start??I can't get it to work at all..do I put any file in USERDATA slot???
GBPackerFanForLife said:
When I run Odin soon as I goto add the AP file Odin freezes an says not responding..I'm useing Windows 10 on my laptop..Any ideas??Also I have put the correct files in odin but it fails Everytime.. I do the BL an the AP an the CP an then for the CSC I use the Home CsC is that correct then hit start??I can't get it to work at all..do I put any file in USERDATA slot???
Click to expand...
Click to collapse
That is normal. Just wait. It will eventually load the AP file. If you're flashing the U1 firmware, there is no Userdata file, so you don't use that slot.
Make sure you are using the modified version of ODIN 3.13.1 and run it as an administrator. There are links to it on XDA. Or if you go to the main beta thread there's links to it in the thread.
Just put the files in their respective slots. BL in BL, AP in AP, etc...
CSC_OYN performs a factory reset. HOME_CSC does not wipe the phone. I always use CSC_OYN when switching from carrier firmware to U1 firmware or vice versa, but it's up to you.
After everything is all loaded up in ODIN, put your phone in download mode. Power off. Then hold power, Bixby, and volume down button all at the same time until it boots to a blue-green screen. Then press volume up to continue.
Plug your phone into your computer and hit start. Then sit back and wait. This will take a while.
That's all the steps. If you have any issues, I encourage you to use the search bar on the forum. These steps and solutions to any issues you may run into have been posted many times in several threads. The search bar is your friend and should always be the first thing you do before posting questions.
Mr. Orange 645 said:
That is normal. Just wait. It will eventually load the AP file. If you're flashing the U1 firmware, there is no Userdata file, so you don't use that slot.
Make sure you are using the modified version of ODIN 3.13.1 and run it as an administrator. There are links to it on XDA. Or if you go to the main beta thread there's links to it in the thread.
Just put the files in their respective slots. BL in BL, AP in AP, etc...
CSC_OYN performs a factory reset. HOME_CSC does not wipe the phone. I always use CSC_OYN when switching from carrier firmware to U1 firmware or vice versa, but it's up to you.
After everything is all loaded up in ODIN, put your phone in download mode. Power off. Then hold power, Bixby, and volume down button all at the same time until it boots to a blue-green screen. Then press volume up to continue.
Plug your phone into your computer and hit start. Then sit back and wait. This will take a while.
That's all the steps. If you have any issues, I encourage you to use the search bar on the forum. These steps and solutions to any issues you may run into have been posted many times in several threads. The search bar is your friend and should always be the first thing you do before posting questions.
Click to expand...
Click to collapse
I wonder since I'm not useing the modified version of Odin that's why it keeps Failing on me..
GBPackerFanForLife said:
I wonder since I'm not useing the modified version of Odin that's why it keeps Failing on me..
Click to expand...
Click to collapse
Yes. That's why I said use the modified version.
I'm assuming since I installed the Firmware then the Beta One Samsung + app won't open..then if I click on the Samsung Members app it says Beta but everything i click on say I'm not registered for the Beta..is that because I manually install the Beta update file..So basically Everytime a new beta version comes out I'm going to have to manually install it..
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
One thing I have noticed on the new Unlocked version of the Firmware an being on the Beta software is that the Stereo speakers on the phone aren't as loud as they were when I was running the ATT version Firmware..Any ideas..
GBPackerFanForLife said:
I'm assuming since I installed the Firmware then the Beta One Samsung + app won't open..then if I click on the Samsung Members app it says Beta but everything i click on say I'm not registered for the Beta..is that because I manually install the Beta update file..So basically Everytime a new beta version comes out I'm going to have to manually install it..
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
One thing I have noticed on the new Unlocked version of the Firmware an being on the Beta software is that the Stereo speakers on the phone aren't as loud as they were when I was running the ATT version Firmware..Any ideas..
Click to expand...
Click to collapse
Yes, you are not part of the official beta.
As far as speaker loudness I have no idea.
Hi all,
Today I have updated my Note 9 from 8.1 to 9.0
Everything went smoothly, and the update was installed without any issues.
Seems to be that everything works fine, except one small little thing:
Contact information on the AOD.
It does exist, and it's visible on the lock screen.
Tried to remove it, re-add it, phone restart, cache removal, app cache+data removal, but without any luck....
I'm using the up-to-date version of the app, 4.1.37.
Basically, everything is stock and up to date.
Does anyone have the same problem?
[UPDATE] I have just talked to Samsung Support, and looks like it's a bug.
Her advice was to do the factory reset.
I need to do the backup first, and then I will let you know the outcome.
Could you share how you updated to Pie please? I'm getting mixed, confusing info. after browsing thru all the forum threads...
Thanks!
rodrigofd said:
Could you share how you updated to Pie please? I'm getting mixed, confusing info. after browsing thru all the forum threads...
Thanks!
Click to expand...
Click to collapse
Hi,
I have received an updated OTA.
Full stock, not rooted.
Settings - Software Update - Download and install updates.
Best regards.
rodrigofd said:
Could you share how you updated to Pie please? I'm getting mixed, confusing info. after browsing thru all the forum threads...
Thanks!
Click to expand...
Click to collapse
*#1234# <--- Type that into phone dialer and see if it's the same as the screen shot firmware Note 9 version info i have posted! if yes then follow below!
NOTE: THESE UPDATE.ZIP's ARE ONLY FOR DEVICES WITH MULTI-CSC OXM!!!
You can check this, to type in your dialer *#1234#, and check if OXM is in the CSC-build...
Managed to get the UPDATE.ZIP if your Note9 is currently on ARL3 (Oreo) to CSA2 (Pie)
ARL3 -> CSA2
If your device is still on ARK2, then update first to ARL3:
ARK2 -> ARL3
* If you have sd card place update.zip in it boot to recovery by holding power up + power +bixby button.
* Go to apply update from SD card.
* just choose install update, If no sd card choose adb in recovery.
* Download adb from here https://dl.google.com/android/reposi...st-windows.zip
Please NOTE this is not my guide!! All Thanks and all credits go to @jaylence for taking the effort to reset his device, and getting the "update.zip" for you!
Original Thread --> https://forum.xda-developers.com/showpost.php?p=78660727&postcount=384
N1NJATH3ORY said:
*#1234# <--- Type that into phone dialer and see if it's the same as the screen shot firmware Note 9 version info i have posted! if yes then follow below!
NOTE: THESE UPDATE.ZIP's ARE ONLY FOR DEVICES WITH MULTI-CSC OXM!!!
You can check this, to type in your dialer *#1234#, and check if OXM is in the CSC-build...
Managed to get the UPDATE.ZIP if your Note9 is currently on ARL3 (Oreo) to CSA2 (Pie)
ARL3 -> CSA2
If your device is still on ARK2, then update first to ARL3:
ARK2 -> ARL3
* If you have sd card place update.zip in it boot to recovery by holding power up + power +bixby button.
* Go to apply update from SD card.
* just choose install update, If no sd card choose adb in recovery.
* Download adb from here https://dl.google.com/android/reposi...st-windows.zip
Click to expand...
Click to collapse
Hi,
1.) Please credit the OP.
2.) Both of you are off-topic.
If you have already upgraded your Note 9, can you please check it out and answer my questions?
Thank you!
i also have a problem
dorianborovina said:
Hi,
1.) Please credit the OP.
2.) Both of you are off-topic.
If you have already upgraded your Note 9, can you please check it out and answer my questions?
Thank you!
Click to expand...
Click to collapse
Apologies i'll credit and edit above guide! Thanks
---------- Post added at 01:26 AM ---------- Previous post was at 01:09 AM ----------
dorianborovina said:
Hi all,
Today I have updated my Note 9 from 8.1 to 9.0
Everything went smoothly, and the update was installed without any issues.
Seems to be that everything works fine, except one small little thing:
Contact information on the AOD.
It does exist, and it's visible on the lock screen.
Tried to remove it, re-add it, phone restart, cache removal, app cache+data removal, but without any luck....
I'm using the up-to-date version of the app, 4.1.37.
Basically, everything is stock and up to date.
Does anyone have the same problem?
Click to expand...
Click to collapse
Yep i have the same issue, i typed out N1NJATH3ORY saved it, put NOTE-9 to sleep so AOD comes on. i can’t see N1NJATH3ORY i even tried different AOD face to see if that fixes it, but it don’t. I can’t see no contact info being displayed on AOD.. Your not the only one, I am on Android PIE 9.ONE UI NOTE-9 EXYNOS!
N1NJATH3ORY said:
Apologies i'll credit and edit above guide! Thanks
---------- Post added at 01:26 AM ---------- Previous post was at 01:09 AM ----------
Yep i have the same issue, i typed out N1NJATH3ORY saved it, put NOTE-9 to sleep so AOD comes on. i can’t see N1NJATH3ORY i even tried different AOD face to see if that fixes it, but it don’t. I can’t see no contact info being displayed on AOD.. Your not the only one, I am on Android PIE 9.ONE UI NOTE-9 EXYNOS!
Click to expand...
Click to collapse
Hi,
Thank you for your time and effort!
Looks like it's a Android 9 feature.
Just to make it sure, contact information text does appear on the lock screen?
Best regards,
Dorian Borovina
dorianborovina said:
Hi,
Thank you for your time and effort!
Looks like it's a Android 9 feature.
Just to make it sure, contact information text does appear on the lock screen?
Best regards,
Dorian Borovina
Click to expand...
Click to collapse
That's correct i can see contact info on lock screen! But no contact info on AOD!
N1NJATH3ORY said:
That's correct i can see contact info on lock screen! But no contact info on AOD!
Click to expand...
Click to collapse
Thank you for your confirmation.
I just wanted to know if it was a problem only on my side.
Best regards,
Dorian Borovina
same problem
No problem
biyolog4472 said:
No problem
Click to expand...
Click to collapse
Strange,
Please can you compare my signature data with your mobile phone software versions?
Thanks!
Exactly the same issue.
Exynos Version of Note 9 (Android Pie).
Micheal86 said:
Exactly the same issue.
Exynos Version of Note 9 (Android Pie).
Click to expand...
Click to collapse
Customer support told me to do the factory reset.
Not sure if I want to do it, and reconfigure the whole thing back again.
Has anyone tried to do and restore the complete phone backup with Samsung Switch?
dorianborovina said:
Customer support told me to do the factory reset.
Not sure if I want to do it, and reconfigure the whole thing back again.
Has anyone tried to do and restore the complete phone backup with Samsung Switch?
Click to expand...
Click to collapse
I`ve done factory reset after the update and then set up the device. And after installing all the apps wipe cache.
But still, have the same issue.
Micheal86 said:
I`ve done factory reset after the update and then set up the device. And after installing all the apps wipe cache.
But still, have the same issue.
Click to expand...
Click to collapse
Thank you for your reply, I appreciate it!
I was wondering if I should do the factory reset, because I've done everything except factory reset.
But, now you told me that you did it, and that the problem still persists, you have really saved me some time!
I'm going to contact the Samsung support one more time, and let them know what's going on.
Stay in touch!
Best regards,
Dorian Borovina
dorianborovina said:
Hi all,
Today I have updated my Note 9 from 8.1 to 9.0
Everything went smoothly, and the update was installed without any issues.
Seems to be that everything works fine, except one small little thing:
Contact information on the AOD.
It does exist, and it's visible on the lock screen.
Tried to remove it, re-add it, phone restart, cache removal, app cache+data removal, but without any luck....
I'm using the up-to-date version of the app, 4.1.37.
Basically, everything is stock and up to date.
Does anyone have the same problem?
[UPDATE] I have just talked to Samsung Support, and looks like it's a bug.
Her advice was to do the factory reset.
I need to do the backup first, and then I will let you know the outcome.
Click to expand...
Click to collapse
another reason i will not be updating! cant get the Senselessness of pushing out half - baked updates
dorianborovina said:
Thank you for your reply, I appreciate it!
I was wondering if I should do the factory reset, because I've done everything except factory reset.
But, now you told me that you did it, and that the problem still persists, you have really saved me some time!
I'm going to contact the Samsung support one more time, and let them know what's going on.
Stay in touch!
Best regards,
Dorian Borovina
Click to expand...
Click to collapse
You`re welcome mate.
BTW, how is your battery life in Android Pie?
Mine is not satisfactory. I used to get better battery backup in Android O. Though I know this new OS would take some time to be stable, and battery backup might be increased.
Sorry for the off-topic.
Micheal86 said:
You`re welcome mate.
BTW, how is your battery life in Android Pie?
Mine is not satisfactory. I used to get better battery backup in Android O. Though I know this new OS would take some time to be stable, and battery backup might be increased.
Sorry for the off-topic.
Click to expand...
Click to collapse
To be honest, I haven't noticed any difference.
I'm able to go through the day without recharging it, and that's the most important thing for me.
How often do you charge it?
This is the first time that my Pixel 5 refuses to see an update. Even when I tell it to check for an update, it says I am current with the november update, and this is now December 16. Anyone have any idea why? What can I do to fix this?
That's a weird issue. Maybe you could try to update manually through the official factory images site?
If you use the 'flash-all.bat', make sure to right-click -> edit the 'flash-all.bat' file and remove the '-w' from the last command line and save the file. The '-w' will wipe your phone.
Just update manually via OTA image, its easy and without the risk of data loss.
I do that almost every month.
ulxerker said:
Just update manually via OTA image, its easy and without the risk of data loss.
I do that almost every month.
Click to expand...
Click to collapse
Yeah, do this.
Easy instructions on doing a manual OTA image?
wilderja said:
Easy instructions on doing a manual OTA image?
Click to expand...
Click to collapse
The instructions are written here: https://developers.google.com/android/ota
It should be fairly straight forward to follow, although it does kinda assume you know some basics.
To help get you started:
Download the SDK Platform Tools to desktop and unzip.
Open notepad, type in "cmd" then click file->save as->
File name: platformtools.bat (do not name the file "cmd")
Save as type: All files (<- important!)
Move the platformtools.bat file into the Platform Tools folder that you unzipped.
(You can watch my video to help guide you through steps 2 and 3 from time stamp 0:45 to 1:10)
Double click the platformtools.bat file.
On your device, go to Settings->About phone. Scroll to the bottom and tap the "Build number" 7 times. You will get a pop up saying Developer options enabled.
Go to Settings->System->Advanced->Developer options. Find "USB debugging" and enable it.
(For steps 5 and 6, you can watch the same video above from time stamp 1:43 to 2:05)
Plug in your phone to your PC. The phone will give a prompt asking do you allow usb debugging. Tap the checkbox to say "always" and then "yes".
Download the latest december ota file and move the file into the Platform Tools folder.
From here on out, go to the ota link at the top and start at step 4.
The first time doing these kind of things may be overwhelming. But the more you do, the more you'll understand what each step does and you'll gain confidence doing this again in the future.
swangjang said:
The instructions are written here: https://developers.google.com/android/ota
It should be fairly straight forward to follow, although it does kinda assume you know some basics.
To help get you started:
Download the SDK Platform Tools to desktop and unzip.
Open notepad, type in "cmd" then click file->save as->
File name: platformtools.bat (do not name the file "cmd")
Save as type: All files (<- important!)
Move the platformtools.bat file into the Platform Tools folder that you unzipped.
(You can watch my video to help guide you through steps 2 and 3 from time stamp 0:45 to 1:10)
Double click the platformtools.bat file.
On your device, go to Settings->About phone. Scroll to the bottom and tap the "Build number" 7 times. You will get a pop up saying Developer options enabled.
Go to Settings->System->Advanced->Developer options. Find "USB debugging" and enable it.
(For steps 5 and 6, you can watch the same video above from time stamp 1:43 to 2:05)
Plug in your phone to your PC. The phone will give a prompt asking do you allow usb debugging. Tap the checkbox to say "always" and then "yes".
Download the latest december ota file and move the file into the Platform Tools folder.
From here on out, go to the ota link at the top and start at step 4.
The first time doing these kind of things may be overwhelming. But the more you do, the more you'll understand what each step does and you'll gain confidence doing this again in the future.
Click to expand...
Click to collapse
Thanks for the info. Updated via sideload. No idea what happened with this update, but it is installed now. THANKS!
wilderja said:
Thanks for the info. Updated via sideload. No idea what happened with this update, but it is installed now. THANKS!
Click to expand...
Click to collapse
My pleasure Glad it worked.
There is no official announcement but I'd bet the roll out was paused on Pixel 5 and 5a because it has a serious 5g to LTE issue, whenever it tries to switch over the phone crashes.. the only way I've been able to stop it from happening to set mine to LTE.. this happens on TMobile network (unlocked devices) and it's happened to all three of my Pixel 5's that updated to the December 2022 update (I side load all the updates since it's faster then the OTA push).
Bupahs said:
There is no official announcement but I'd bet the roll out was paused on Pixel 5 and 5a because it has a serious 5g to LTE issue, whenever it tries to switch over the phone crashes.. the only way I've been able to stop it from happening to set mine to LTE.. this happens on TMobile network (unlocked devices) and it's happened to all three of my Pixel 5's that updated to the December 2022 update (I side load all the updates since it's faster then the OTA push).
Click to expand...
Click to collapse
You would not believe how thankful I am that you solved this for me. I scoured reddit asking people if their Pixel 5's were shutting down and all of them were like, "bad battery" or "faulty motherboard". But it didn't explain why the November update was stable for me. Setting my device to LTE only fixed my shutdowns, thank you for sharing this.
For other interested, there is a longer discussion here: https://github.com/GrapheneOS/os-issue-tracker/issues/1809
It is now mid January and I'm still on the November update. Has anyone on T-Mobile/Fi been able to get the update?
laughs said:
It is now mid January and I'm still on the November update. Has anyone on T-Mobile/Fi been able to get the update?
Click to expand...
Click to collapse
Why can't you update manually?
V0latyle said:
Why can't you update manually?
Click to expand...
Click to collapse
The reason I bought a Google phone was to try to get a good product experience. I really didn't want to have to go through such a manual process to get updates. And I read that some people seem to report crashes after manually updating.
laughs said:
The reason I bought a Google phone was to try to get a good product experience. I really didn't want to have to go through such a manual process to get updates. And I read that some people seem to report crashes after manually updating.
Click to expand...
Click to collapse
It's rather easy, you don't really need much if any coding experience.
Android Flash Tool
Pixel Flasher, is a very simple amazing tool as well.
laughs said:
The reason I bought a Google phone was to try to get a good product experience. I really didn't want to have to go through such a manual process to get updates. And I read that some people seem to report crashes after manually updating.
Click to expand...
Click to collapse
Use this page to download the OTA for your device, and follow the instructions on the page to sideload the OTA. This is the safest method for updating.