I'm getting notification this morning about Update v11.2.1.1LE15AA/Global available. Weird thing is I'm already on that update. When I try to download it again I get this...
I did install it via local upgrade after grabbing the OTA file.
What's going on here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got the same update request after I had already updated to that version. For me though, it let me perform the requested update.
Same issue as OP... notification to install after it's already installed and it will not re-install. Not sure how to clear the nagging for now, hah. I can force stop play services to make it go away, but it doesn't last (not a good solution anyway).
dmarden said:
Same issue as OP... notification to install after it's already installed and it will not re-install. Not sure how to clear the nagging for now, hah. I can force stop play services to make it go away, but it doesn't last (not a good solution anyway).
Click to expand...
Click to collapse
You can turn off the notification alert under notification setting under that popup. but that's weird nonetheless.
Poloasis said:
You can turn off the notification alert under notification setting under that popup. but that's weird nonetheless.
Click to expand...
Click to collapse
Right right, that is actually what I did eventually do... hopefully this is sorted soon
The 2nd update installed for me. I'm reading it's related to the issue with the device not being play protect certified and GPay and Netflix not working. Some people report the update resolves that issue for them, but it didn't for me.
I wish it would install for me so I didn't have to turn off the notification.
You know, I'm rather curious. What if it's not the same update? When I look under build number in 'about phone' ,the 1.1 portion isn't in the number itself. That's what's confusing me about this. it's driving me nuts because it won't install, because I'm rooted. normally in magisk manager, you can temporarily uninstall magisk, but it doesn't seem to work in the newest Canary.
Are you all 100% sure that the 1.1 update isn't the same one that we already have installed on the device when it shipped? I've had my phone for only 2 days)
Burt Squirtz said:
You know, I'm rather curious. What if it's not the same update? When I look under build number in 'about phone' ,the 1.1 portion isn't in the number itself. That's what's confusing me about this. it's driving me nuts because it won't install, because I'm rooted. normally in magisk manager, you can temporarily uninstall magisk, but it doesn't seem to work in the newest Canary.
Are you all 100% sure that the 1.1 update isn't the same one that we already have installed on the device when it shipped? I've had my phone for only 2 days)
Click to expand...
Click to collapse
The full build number is displayed in About Phone for me.
Related
I just clicked on software update/check for update in the 'About Phone' section of my settings. I've never clicked it before. It said new firmware required. So I let it download the new software. Then it said charge battery before updating, and then it let me choose when to resume the update. I chose 3 hours. So I'm on stock Android 2.3.3. Gingerbread XWKE7 . What will it update to? I'm a bit worried now, is it going to wipe stuff? Everything's working good so I don't 'need' to update, but it would be nice to. Can I cancel the update? Only thing I can see is 'resume update'.
If you are from london uk. I think the OTA(over the air) version is gingerbread 2.3.4. I do not think it is a wipe device firmware but just to be safe, back it up via kies if your phone is not rooted otherwise use titanium backup if your phone is rooted.
Trust me I would go with the update. Some improvements. I wish we could update
For sure it is NO WIPE version.
Thanks guys, it's a relief it didn't wipe anything.
This is what I got. I thought it might also update Android but it hasn't. What benefits can I expect from the updated Gingerbread XWKF3?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Roman5 said:
Thanks guys, it's a relief it didn't wipe anything.
This is what I got. I thought it might also update Android but it hasn't. What benefits can I expect from the updated Gingerbread XWKF3?
Click to expand...
Click to collapse
Can you request a mod move this to Q&A please, it has nothing to do with themes or apps
and why have you made two threads?
your duplicate thread
i have reported this one...
Darkside Agent said:
Can you request a mod move this to Q&A please, it has nothing to do with themes or apps
and why have you made two threads?
your duplicate thread
i have reported this one...
Click to expand...
Click to collapse
Oh look, it's the voluntary forum policeman.
I made a duplicate thread because I wasn't sure which forum to post it in and I panicked a bit last night so needed a fast answer. OK?
Hello everyone.
I updated my note2 to 4.3 yesterday using odin stock pre rooted. But since the update my screen keeps to turn on by itself every 30-40 seconds then turn off and so on.
I have Wakelock detector and the service that is causing the problem called TrackingService2
I re flashed the rom again and this time it didn't happen until today.
The wakelock returned.
I downloaded Disable Service and tried searching for it but I didn't find.
Anyone have the same problem? Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7100 using Tapatalk 2
I have the same problem. My rom is phoenixrom v14 on note 2 n7100. I would really appreciate help with this. I have no idea what to do.
Well i had this bug too. ..but i changed my rom and it worked....try freezing the process using titanium backup...ot may work...but there is never an assurance
Thanks Sadeshmagic,
I had this problem with rooted stock rom also, but if I remember correctly it wasn't this aggressive.
I tried Titanium backup, but couldn't find UID or Trackingservice2. After some googling I understood that every app has a UID, it's a ID, so that's why I can't find UID in any process list.
I booted note 2 in safe mode and noticed that the problem didn't appear then. So if it's a 3rd party app I don't understand why I can't find out the app that has a process called Trackingservice2.
So any advice on how i can locate the app that has Trackingservice2 process?
Thanks in advance.
Ok, I just reflashed my rom to start from the beginning. The problem has gone away so it's definitely a 3rd party app.
I'm gonna install some/most of the same apps again, but maybe this time one at a time so I can see if one of the apps brings the problem back. I'll tell you if I come across that app.
Could you find out what caused the problem?
herra puh said:
Ok, I just reflashed my rom to start from the beginning. The problem has gone away so it's definitely a 3rd party app.
I'm gonna install some/most of the same apps again, but maybe this time one at a time so I can see if one of the apps brings the problem back. I'll tell you if I come across that app.
Click to expand...
Click to collapse
Hi! I have exactly the same problem. Could you find aout what caused the problem?
Holger
hello mates,
yesterday i uninstalled snapchat. cause i got beta tester and i downloaded the beta. tried to login again but yeah.. see the picture
i rooted with unlocking bootloader, flashed twrp and rooted with supersu
i searched up the issue, some say you have to uninstall the xposed framework.. did not installed it first.
also tried it with installing xposed, installed the snappref module (what sometimes did work) but this also did not work.
installed it again but no positive progress.
the snapchat webside says that rooted phones may have issues.. i have rooted my phone now almost have an year and had never issues like that.
i just don't want to fully unroot and root again.
has anyone of you a idea? or is it possible to unroot the phone for some time? like in cyanogen mod, where you can unroot your phone in the dev options.
here the webside on the pic if u want to re-read it: https://support.snapchat.com/en-GB/a/failed-login
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well Snapchat detects if you have xposed installed or not at login. It works on rooted phones otherwise.
I would suggest, install your custom ROM again , login into snapchat and then install Xposed framework. that's what I do and snapchat works.
Maybe a sync issue ?
How to fix 'Snapchat login temporarily failed' error on Android
here with root: https://www.reddit.com/r/LGG3/comments/3vqnaj/oh_no_your_login_temporarily_failed_snapchat/
Uninstall xposed
Download correct snapchat version for snappreffs
Disable automatic updates so you wont need to downdate and have to sign out
Log in
Install xposed and snappreffs plus reboot and stuff
Click to expand...
Click to collapse
Download correct snapchat version for snappreffs
Click to expand...
Click to collapse
<-- Maybe snappreffs is not compatible with the beta
http://snapchat-download.net/fix-oh-no-your-login-temporarily-failed-on-snapchat/
To manually sync your account
On your mobile device, open Settings Settings > Accounts > Google.
Touch the account whose data you want to sync.
In the top-right corner, touch menu More > Sync now.
After your Google Account is successfully synced, make sure that you have the latest version of Google Play Store and Snapchat app. To ensure this, update all your installed app under “My apps and game” on your Play Store account, then reinstall Snapchat to get the latest version of this app.
Click to expand...
Click to collapse
So I was driving back yesterday and my phone notifies me that I'm reaching my data limit. I thought, "That's odd, I've only used 0.1 GB". So I look down and see this monstrosity of data being used by the damn Android OS. How the heck can you see what would individually be using data in the "Android OS" package cause it could be any number of things. I'm guessing it could have been a system update pull but I did disable OTA updates in developer settings. I have root as well and I would like to freeze that process with Titanium Backup if anyone knows what that process might be on the Pixel. Also any other suggestions as how to further troubleshoot this would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's the update pull even though you are updated. We have seen this a few times with others. Get it updated.
TonikJDK said:
It's the update pull even though you are updated. We have seen this a few times with others. Get it updated.
Click to expand...
Click to collapse
Well when I go to system update and choose to install update it says that it failed. Any advice on that? Can you not properly install updates while rooted?
In terms of updating to the latest OTA I followed How To Geeks - FlashFire Guide which put my device into a endless bootloop so I don't recommend doing that.
Still looking to see if anyone knows what to freeze in Titanium Backup on Pixel to block OTA updates from downloading. Thanks.
ThePieMonster said:
Well when I go to system update and choose to install update it says that it failed. Any advice on that? Can you not properly install updates while rooted?
Click to expand...
Click to collapse
You must of modded something that is stopping it. There is a way to sideload the OTA, but the third post in the thread below is how I do it each month. Have ro reroot afterwards.
Pay attention to the part where you remove the-w from flashall bat file. That is what saves your data.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
TonikJDK said:
You must of modded something that is stopping it. There is a way to sideload the OTA, but the third post in the thread below is how I do it each month. Have ro reroot afterwards.
Pay attention to the part where you remove the-w from flashall bat file. That is what saves your data.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I ended up flashing the original stock ROM off Google's website and then went threw the systemless root methods mentioned here.
I now have the below:
Android: 7.1.1 ROM: Factory (Rooted) Kernel: 3.18.31-ElementalX-P-1.08 Build: NOF27B
im having tons of data through the same thing. I ran a data manager app and it said its google.uid.system:1000 . I reset the rom to original as I have not installed any other rom then googles originals. I have some of the highest data downloads its crazy. I even turned off back up picture folders. Here is the data.
Please give me some suggestion to get out of this mess
OOS 10.0.14.HD65AA
Magisk 20.4 only modules are Google dialer framework, Native OOS call recording, systemless hosts
While on 10.0.12 I installed/uninstalled the Aurora Services module.
A few days later I updated to 10.0.13, phone had not been rebooted between module & update. After update my phone could not see ANY SIM/phone network related info (see pics).
Redid the update and all of the functions were restored. The problem is that the SIM disappears after each reboot.
I reinstall the update, reboot, and everything is fine, until the next reboot. The SIM functions disappear, I reinstall the update, reboot everything fine, until the next reboot, on & on.
I've tried pulling/reinserting the card and inserting card after restart, but that doesn't help.
Now on 10.0.14 and the problem persists.
I believe the OTA updates are the full OOS so I'm at a loss as to why the SIM would disappear on the second boot after update.
Any help would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is because of OOS native call recording, it is very important to UNINSTALL the module before every update (not just disable, UNINSTALL) it is very well explained in the tread of that specific module why it is needed. I made the mistake to only disabling it instead of uninstalling before an update, fortunately I only needed to uninstall/reinstall it to fix the problem, but if you left it enabled and updated, then you might need to dirty flash the whole update again to fix it. You can find more info on the OOS native call recording thread, I hope it helped you
jacobyo7 said:
It is because of OOS native call recording, it is very important to UNINSTALL the module before every update (not just disable, UNINSTALL) it is very well explained in the tread of that specific module why it is needed. I made the mistake to only disabling it instead of uninstalling before an update, fortunately I only needed to uninstall/reinstall it to fix the problem, but if you left it enabled and updated, then you might need to dirty flash the whole update again to fix it. You can find more info on the OOS native call recording thread, I hope it helped you
Click to expand...
Click to collapse
:good:
Thank you, that was it. I had disabled it before the update, but missed that it had to be uninstalled.