Related
I got my Transformer yesterday, and I'm still discovering all its features.
But I'm having a little problem...
My unit when I turned it on for the first time was missing some apps, like MyDesktop.
Also, I was experiencing some issued which I believe were fixed, like MyNet being in Spanish instead of English (I'm Italian but I use English on all my systems)
I thought it wasn't fully updated, went to Settings->About Tablet->System Update, and checked for updates.
The result was (and still is) "There is no update currently available for your device"
Any ideas?
Hi, I have been trying to update my Transformer for the past couple of days with the same results, no update found I can only think that either the server is busy or the update has been removed temporarily.
Neil
bobcollege said:
Hi, I have been trying to update my Transformer for the past couple of days with the same results, no update found I can only think that either the server is busy or the update has been removed temporarily.
Neil
Click to expand...
Click to collapse
Thanks, Neil.
Knowing that I'm not the only one having this issue at least calms a bit the fear that something isn't working on my side.
Let's hope we manage to update as soon as possible - I'd really like to check the new stuff
Have you tried clearing the caches for all the system and Asus apps in the settings, rebooted, and then attempted the update again? Or a full reset?
If i were you two i would seriously consider rooting it and apply the update via the rooted update in the android development thread. Just my .02$
stuntdouble said:
Have you tried clearing the caches for all the system and Asus apps in the settings, rebooted, and then attempted the update again? Or a full reset?
Click to expand...
Click to collapse
Yup, cleared the cache for all the apps, rebooted, and... same result.
I haven't done a complete restore to factory settings yet, but yesterday I tried the update as soon as I turned the thing on, before installing anything, so that should be as close to factory settings as possible.
dcmtnbkr said:
If i were you two i would seriously consider rooting it and apply the update via the rooted update in the android development thread. Just my .02$
Click to expand...
Click to collapse
Actually, I'm a bit scared about rooting the device. I know I won't install alternative OS's and I'll never tamper with the system innards, so rooting is not really a priority for me.
Meanwhile, I've also dropped a note to Asus support, let's see if they can shed some light...
PublicJohnDoe said:
Actually, I'm a bit scared about rooting the device. I know I won't install alternative OS's and I'll never tamper with the system innards, so rooting is not really a priority for me.
Meanwhile, I've also dropped a note to Asus support, let's see if they can shed some light...
Click to expand...
Click to collapse
That's fair, I like to tinker a lot Hopefully asus sheds some light. Enjoy the new device!
dcmtnbkr said:
If i were you two i would seriously consider rooting it and apply the update via the rooted update in the android development thread. Just my .02$
Click to expand...
Click to collapse
I did see the post for the ota rooted stock rom, guess i will have a tinker with that or maybe the one on modaco forums. Lets see how easy it is first
Neil
In the end the update (the new one, Apr 26) did come through!!!
Hi Guys,
I had recently updated my Oneplus One to 5.0.2 through OTA system updates. Now I wanted to update the same to 5.1.1 (i.e OS 12.1). But the problem is that I am not able to see the system updates anymore. It says the System is up to date whereas it's not the case in reality. It also asks to update cyanogen recovery, which I ignore. Attaching the snapshots of device for your reference.
The device is NOT rooted. I tried switch OFF and Switch ON multiple times. I also manually force stopped the System Update app, cleared it's cache, disabled it then enabled it. tried all combinations for the same. But no luck.
Can someone please advice what should I do to see the system updates as usual the way I was seeing earlier? Thanks for your help.
Its seems images are not visible. I have raised the same question on OPO forums. Here is the link to see the images: https:// forums.oneplus.net/threads/oneplus-one-ota-system-updates-not-working-shows-no-update.500862/
Well As you Know CyanogenMod Died so that's why you can't find any updates
So I suggest you to follow this link
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
الفلسطيني said:
Well As you Know CyanogenMod Died so that's why you can't find any updates
So I suggest you to follow this link
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Click to expand...
Click to collapse
Thanks a lot for this information. In that thread, its mentioned that "there are two different versions of some OTA updates." In such a case can I go ahead and install any of the zip file? I will be downloading the incremental updates which are similar to System updates. Please let me know.
TheOfficialJoker said:
Hi Guys,
I had recently updated my Oneplus One to 5.0.2 through OTA system updates. Now I wanted to update the same to 5.1.1 (i.e OS 12.1). But the problem is that I am not able to see the system updates anymore. It says the System is up to date whereas it's not the case in reality. It also asks to update cyanogen recovery, which I ignore. Attaching the snapshots of device for your reference.
The device is NOT rooted. I tried switch OFF and Switch ON multiple times. I also manually force stopped the System Update app, cleared it's cache, disabled it then enabled it. tried all combinations for the same. But no luck.
Can someone please advice what should I do to see the system updates as usual the way I was seeing earlier? Thanks for your help.
Its seems images are not visible. I have raised the same question on OPO forums. Here is the link to see the images: https:// forums.oneplus.net/threads/oneplus-one-ota-system-updates-not-working-shows-no-update.500862/
Click to expand...
Click to collapse
Hi man,
easier way
search google play for the app (Cyanogen Update Tracker) , then open it and follow the instructions .
it's good and works for my bacon .
MedoStartSmart said:
Hi man,
easier way
search google play for the app (Cyanogen Update Tracker) , then open it and follow the instructions .
it's good and works for my bacon .
Click to expand...
Click to collapse
Thanks a lot for your reply. I actually have that app and it shows me the new update for 5.1.1 too. But the issue is when I first tried to update thru this app from kitkat to 05Q update, it somehow messed up my device. The zip installed was somehow corrupt due to which the installation had issues. Thats why I am actually worried to take that risk again.
That screwed up installation thru that app was the reason why I switched to OTA system updates which updated from 05Q to 5.0.2 lollypop. And now I cant see cyanogen system updates as it seem to have died.
Are you sure that app has no issues at all? Have you updated till 5.1.1 or 6.0.1 using that app? Please let me know.
TheOfficialJoker said:
Thanks a lot for your reply. I actually have that app and it shows me the new update for 5.1.1 too. But the issue is when I first tried to update thru this app from kitkat to 05Q update, it somehow messed up my device. The zip installed was somehow corrupt due to which the installation had issues. Thats why I am actually worried to take that risk again.
That screwed up installation thru that app was the reason why I switched to OTA system updates which updated from 05Q to 5.0.2 lollypop. And now I cant see cyanogen system updates as it seem to have died.
Are you sure that app has no issues at all? Have you updated till 5.1.1 or 6.0.1 using that app? Please let me know.
Click to expand...
Click to collapse
Why not just get the cos13.1.2 signed zip, flash it and factory reset. I have the file and i can upload it in a couple minute to my gdrive.
TheOfficialJoker said:
Thanks a lot for your reply. I actually have that app and it shows me the new update for 5.1.1 too. But the issue is when I first tried to update thru this app from kitkat to 05Q update, it somehow messed up my device. The zip installed was somehow corrupt due to which the installation had issues. Thats why I am actually worried to take that risk again.
That screwed up installation thru that app was the reason why I switched to OTA system updates which updated from 05Q to 5.0.2 lollypop. And now I cant see cyanogen system updates as it seem to have died.
Are you sure that app has no issues at all? Have you updated till 5.1.1 or 6.0.1 using that app? Please let me know.
Click to expand...
Click to collapse
i used it to update from kitkat to the latest marshmallow version available throw the full update method, and it worked like a charm.
C4SCA said:
Why not just get the cos13.1.2 signed zip, flash it and factory reset. I have the file and i can upload it in a couple minute to my gdrive.
Click to expand...
Click to collapse
Thanks a lot for your help man. But flashing and factory reset will wipe the mobile data I guess. I don't really want to do that. I need to keep the mobile data intact. Also, will it be advisable to jump from 5.0.2 to 6.0 directly? Or should I go incrementally only?
MedoStartSmart said:
i used it to update from kitkat to the latest marshmallow version available throw the full update method, and it worked like a charm.
Click to expand...
Click to collapse
I can also see the full update option. But if I do full update directly, will it wipe all data from my device? I am not sure about it. Can you confirm whether your data was wiped when you updated from Kitkat to the latest marshmallow thru this App? That would help me decide. Or if anyone else can confirm the same, that would also help.
TheOfficialJoker said:
I can also see the full update option. But if I do full update directly, will it wipe all data from my device? I am not sure about it. Can you confirm whether your data was wiped when you updated from Kitkat to the latest marshmallow thru this App? That would help me decide. Or if anyone else can confirm the same, that would also help.
Click to expand...
Click to collapse
no, it didn't wipe any of my data or apps
sorry for late reply.
MedoStartSmart said:
no, it didn't wipe any of my data or apps
sorry for late reply.
Click to expand...
Click to collapse
Thanks man. I will try the full update then.
anybody seeing uncertified device in google play after upgrade firmware B225 in mate 9 Chinese version? it was certified in B213
Interesting. I have the same for B225. What does this mean?
not sure, maybe because of the integration of GMS into the FW but so far all gapps work fine without any issues, v8.X supposed to come out yesterday or today so hope it will update without any issues.
May be its a reason that Android pay stop working on this firmware.
Anybody know how to fix this?
MMX2 said:
May be its a reason that Android pay stop working on this firmware.
Anybody know how to fix this?
Click to expand...
Click to collapse
haven't tried it yet but you are correct, some gapps will only work on certified devices
This is a bug of Google or Huawei? Google support can't tell me anything about it.
I am think that firmware not official.
Perhaps you can contact Google support for help. Good luck to you.
anyone got this fixed? been thinking about doing a factory reset and reinstall gapps from scratch but not sure if will work or if its better to wait for a new fw update from huawei whenever that happens
This has been the case for me on the last several releases. I have not experienced any difficulties or even change whatsoever. I don't use Android Pay though.
rbt001 said:
This has been the case for me on the last several releases. I have not experienced any difficulties or even change whatsoever. I don't use Android Pay though.
Click to expand...
Click to collapse
i did in b213 but now I cant also photos and contacts dont sync automatically in the background unless I open the app other than that everything works as expected
I have the same thing installed on the MHA-L29C432B193 via FunkyH, I have had it several times before and over time, and no problems in the applications or their updates have caused it.
Same here on 193. It is because firmware is not certified by Huawei jet.
arminbih said:
Same here on 193. It is because firmware is not certified by Huawei jet.
Click to expand...
Click to collapse
I had just rebranded from C567B190 to C432B193 (for the frequent security updates as it seemed like it was getting updates every month), and now Playstore says uncertified and Google Play is refusing to work, stating:
"Android Pay can't be used on this device
This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM..."
I hope you're right about this, arminbih, I'd hate to lose the ability to run Android Pay because of what I did and I'd hate to have to do another factory reset.
My phone's bootloader is locked after the rebranding script finished flashing the official B193. Did the recommended steps, 2 script runs and factory reset, but I hope nothing was messed up during the process. I should've backed up the original partitions in TWRP before proceeding with flashing. Oh well.
Anyone else have a clue?
lostorbit said:
I had just rebranded from C567B190 to C432B193 (for the frequent security updates as it seemed like it was getting updates every month), and now Playstore says uncertified and Google Play is refusing to work, stating:
"Android Pay can't be used on this device
This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM..."
I hope you're right about this, arminbih, I'd hate to lose the ability to run Android Pay because of what I did and I'd hate to have to do another factory reset.
My phone's bootloader is locked after the rebranding script finished flashing the official B193. Did the recommended steps, 2 script runs and factory reset, but I hope nothing was messed up during the process. I should've backed up the original partitions in TWRP before proceeding with flashing. Oh well.
Anyone else have a clue?
Click to expand...
Click to collapse
193 is unstable, force closes some apps, and camera does not work in RAW mode. I suggest going back to 190 or before, they are certified.
arminbih said:
193 is unstable, force closes some apps, and camera does not work in RAW mode. I suggest going back to 190 or before, they are certified.
Click to expand...
Click to collapse
Thank you for your reply. Off-topic question, would you know if it's easy to go back to 190 without losing data?
(I certainly should look that up myself, I know, but I literally just got the phone yesterday so it's still much of uncharted territory for me)
lostorbit said:
Thank you for your reply. Off-topic question, would you know if it's easy to go back to 190 without losing data?
(I certainly should look that up myself, I know, but I literally just got the phone yesterday so it's still much of uncharted territory for me)
Click to expand...
Click to collapse
Search "firmware finder" on play store and forums. You can upgrade downgrade as much as you like via official upade changing dns.
arminbih said:
Search "firmware finder" on play store and forums. You can upgrade downgrade as much as you like via official upade changing dns.
Click to expand...
Click to collapse
Thank you very much!
lostorbit said:
I had just rebranded from C567B190 to C432B193 (for the frequent security updates as it seemed like it was getting updates every month), and now Playstore says uncertified and Google Play is refusing to work, stating:
"Android Pay can't be used on this device
This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM..."
I hope you're right about this, arminbih, I'd hate to lose the ability to run Android Pay because of what I did and I'd hate to have to do another factory reset.
My phone's bootloader is locked after the rebranding script finished flashing the official B193. Did the recommended steps, 2 script runs and factory reset, but I hope nothing was messed up during the process. I should've backed up the original partitions in TWRP before proceeding with flashing. Oh well.
Anyone else have a clue?
Click to expand...
Click to collapse
I too had B193 installed, and Android Pay wouldn't work. SafetyNet basic integrity passed but not CTS Profile, and probably because of B193 being uncertified. Went back to B190 now that it's certified and Pay works again and SafetyNet passes on both checks.
I have previously used updates the day they were released on hwmt.ru and they have worked fine with SafetyNet, even when it said uncertified. So this might be something new.
That's great to know. Thank you.
Were you able to downgrade without a wipe, and if so, what method did you use?
I've been messing with FF and the proxy method but no dice so far.
May security update OTA available now, check yours.
Caltinpla said:
May security update OTA available now, check yours.
Click to expand...
Click to collapse
Yep, locked & loaded.
garywojdan81 said:
Yep, locked & loaded.
Click to expand...
Click to collapse
The kernel has been updated from 4.4.126 to 4.4.128 as well.
How can I safely install this update if I'm already rooted? Would prefer to not have to wipe my data.
I uninstalled Magisk and then side loaded the update using ADB, it went fine.
fizz1234 said:
How can I safely install this update if I'm already rooted? Would prefer to not have to wipe my data.
Click to expand...
Click to collapse
OTA URL for anyone that wants to sideload:
https://android.googleapis.com/pack.../513e62d3319685ebb6064f5b96359cb97c4148c6.zip
Tardeaux said:
OTA URL for anyone that wants to sideload:
https://android.googleapis.com/pack.../513e62d3319685ebb6064f5b96359cb97c4148c6.zip
Click to expand...
Click to collapse
A link for the fast boot files is in the Stock ROM section.
So just a monthly security update? Nothing new ?
indrafendy said:
So just a monthly security update? Nothing new ?
Click to expand...
Click to collapse
Maybe more. It seems to have fixed the difficulty I had connecting to a Sony camera on WiFi.
indrafendy said:
So just a monthly security update? Nothing new ?
Click to expand...
Click to collapse
As far as I know, the kernel has been updated too.
Seems like my data connection has gone downhill since I did this. Probably coincidence, but I loaded this the other day and now have noticed slow data speeds. Still showing LTE+ with AT&T but speed tests show download speeds at less than 1 Mbps, if I can even get it to connect.
Seems like this May update broke my Android Auto. I updated to P Preview and AA worked fine. I reverted back to May and it doesn't work again. I reverted back to March and working fine again.
I have a '17 Honda Pilot with rooted HU. Only other thing I can think of is needing to take it to Honda to get a TSB installed on the HU.
https://developers.google.com/android/images
Pixel 3XL specific changes:
Improves Voice-Unlocking performance for Google Assistant
Adjust Wi-Fi connectivity during eSIM activation on certain carriers
Improves Bluetooth connectivity on Pixel devices
Removes screen flash when ambient display wakes for some Pixel 3 device
Improves Voice-Unlocking performance for Google Assistant
Adjust Wi-Fi connectivity during eSIM activation on certain carriers
Improves Bluetooth connectivity on Pixel devices
Removes screen flash when ambient display wakes for some Pixel 3 device
Nothing exciting :/ waiting forward to BETA 2 of Android Q
Bryandu13 said:
Nothing exciting :/ waiting forward to BETA 2 of Android Q
Click to expand...
Click to collapse
Me too...
I dunno what y'all talking about this update has improved so much for me in terms of usability and smooth operation
For manual installing April update, it's suggest to upgrade the platform-tool from https://developer.android.com/studio...orm-tools.html or the upgrade process will fail ....
Also, don't know why after upgrade (from factory image without -W option), Magisk v19 can no longer root the system... (TWRP installation is success but when reboot into the system it's not rooted). <--Edit: I uninstalled the Magisk Manager apk and reinstall and got root again!
Anyone else has same problem?
lssong99 said:
For manual installing April update, it's suggest to upgrade the platform-tool from https://developer.android.com/studio...orm-tools.html or the upgrade process will fail ....
Also, don't know why after upgrade (from factory image without -W option), Magisk v19 can no longer root the system... (TWRP installation is success but when reboot into the system it's not rooted).
Anyone else has same problem?
Click to expand...
Click to collapse
Why u using magisk 19? Why not 18.1
masri1987 said:
I dunno what y'all talking about this update has improved so much for me in terms of usability and smooth operation
Click to expand...
Click to collapse
Yeah I noticed it after installed it.
masri1987 said:
Why u using magisk 19? Why not 18.1
Click to expand...
Click to collapse
Tried V19 and V18.1 and both has the same problem. After update the April update, it seems Magisk Manager needs to be uninstall/re-install to detect root... (even after TWRP flash zip is done ok.)
Installed April update with no-wipe. Followed up with TWRP 3.2.3-3, Magisk v19.0 and Kiriskura kernel 2.1.3
Everything seems fine.
swieder711 said:
Installed April update with no-wipe. Followed up with TWRP 3.2.3-3, Magisk v19.0 and Kiriskura kernel 2.1.3
Everything seems fine.
Click to expand...
Click to collapse
Did you experience smoother experience like others above?
EMJI79 said:
Did you experience smoother experience like others above?
Click to expand...
Click to collapse
I have had smooth operations all along thanks to the custom kernel.
why am i getting notifications that aren't disappearing? i've checked them already and they only go away after i scroll down again on notification menu
masri1987 said:
why am i getting notifications that aren't disappearing? i've checked them already and they only go away after i scroll down again on notification menu
Click to expand...
Click to collapse
If you find a solution, I'd like to know it. My wife's P3 has this issue. In fact, she had the same issue on her OG Pixel. I do not have the issue on my 3 XL nor did I have it on my OG XL. There is some info here and on reddit, but mostly it is folk throwing $hit against the wall. Google has recommended full wipe as well as deleting and adding the profile back, but I am not going to bother unless that is a known fix.
https://forum.xda-developers.com/pixel-3-xl/help/notification-icons-staying-status-bar-t3860134
https://www.reddit.com/r/GooglePixel/comments/964ham/dismissing_notifications/
https://www.reddit.com/r/GooglePixel/comments/9x0df9/notifications_reappearing_after_swiped_away/
sliding_billy said:
If you find a solution, I'd like to know it. My wife's P3 has this issue. In fact, she had the same issue on her OG Pixel. I do not have the issue on my 3 XL nor did I have it on my OG XL. There is some info here and on reddit, but mostly it is folk throwing $hit against the wall. Google has recommended full wipe as well as deleting and adding the profile back, but I am not going to bother unless that is a known fix.
https://forum.xda-developers.com/pixel-3-xl/help/notification-icons-staying-status-bar-t3860134
https://www.reddit.com/r/GooglePixel/comments/964ham/dismissing_notifications/
https://www.reddit.com/r/GooglePixel/comments/9x0df9/notifications_reappearing_after_swiped_away/
Click to expand...
Click to collapse
for me it was oneplus gestures hiding the navbar doing it... sorry bud
masri1987 said:
for me it was oneplus gestures hiding the navbar doing it... sorry bud
Click to expand...
Click to collapse
Thanks anyway!
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum
Anyone else?
spuri78 said:
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum
Anyone else?
Click to expand...
Click to collapse
I'm having the same issue. I thought it was me going crazy and overlooking something in the settings. I've tried everything.
Sent from my Pixel 3 XL
spuri78 said:
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum
Anyone else?
Click to expand...
Click to collapse
Eudeferrer said:
I'm having the same issue. I thought it was me going crazy and overlooking something in the settings. I've tried everything.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
this has never worked for me on stock rom. on DU and other roms yes, but stock? no.
masri1987 said:
this has never worked for me on stock rom. on DU and other roms yes, but stock? no.
Click to expand...
Click to collapse
It used to work for me on stock.
Sent from my Pixel 3 XL