Related
I am using the Focus and I used the Cheveronupdate tool like as soon as it came out, I have just done a 3min search to see what this update does for the focus. Has anyone else had this occur recently?
And the Update PR stunt (note)
I guess the generic MS saying it will prevent your phone from updating is now proven false as well, granted I don't know if this update has done anything yet since I am on step 7 of it creating a backup file.
ATT Focus
I also used the Chevron Updater and updated to 7390. I received a notification via Zune for the standard update last night and tried to update. Went through all steps and then I got an error 80180005 for which I could find no explanation, but the update failed. I then plugged my USB cable to the back USB ports on my laptop and the installation succeeded and changed the bootloader number, firmware and radio software numbers. These numbers were NOT CHANGED with the NoDo update from the CXhevron Updater method.
This is the Samsung firmware update.
I also unlocked my phone using Chevron to update to NOdO weeks ago but am yet to see the samsung firmware update.
buffalosolja42 said:
I guess the generic MS saying it will prevent your phone from updating is now proven false as well, granted I don't know if this update has done anything yet since I am on step 7 of it creating a backup file.
Click to expand...
Click to collapse
Not quite the case.
@BrandonWatson said:
@Strider_Aus our guidance remains - Walshed phones will not update past NoDo (specififcally build 7390)
Click to expand...
Click to collapse
well mine went through
without a hitch yes OS revision numbers didn't change and I am not sure about firmware. Can't tell you that I see any difference right now.
capacitive buttons should be less sensitive, and dont work if you press the screen on a different place at the same time (for gaming or video playback etc, accidently hitting back button, it should be disabled now)
camera should auto default to anti-shake setting ON.
screen should be responsive even on a soft surface (pillow)
this is what I read, not sure, can people confirm this? Is this also for the omnia7? Mine is at the store for repair but these things were some annoying things and will be nice if they are fixed on the omnia as well.
I got the latest update to the wear app and after was getting delayed notifications. Decided to try reseting the watch and now it's not installing any apps to the watch and the watch is heating up and dying quickly. I've reset the watch again, cleared out the data and uninstalling android wear and reinstalled and it does the same thing I went from line 80% battery to 26% in like a half hour. Anyone have any thoughts
Edit: also the watch is stock no root or anything
Yup, I just updated. Lost 10% battery in the last 20 minutes. Something is not right.
I'm not seeing this, but it does show that Google really needs to have a way of reapplying an update and/or reverting back. This can be done via ADB sideload for phones/tablets, and we need an equivalent for AW. (This may already exist, but I'm just not aware of it... at least not an official way.)
There's an update to the Wear app in the Play Store now.
hush66 said:
There's an update to the Wear app in the Play Store now.
Click to expand...
Click to collapse
Is this another update newer than the one on the Play Store with a date of 07 Sept? Or are you talking about that one?
jms_uk said:
Is this another update newer than the one on the Play Store with a date of 07 Sept? Or are you talking about that one?
Click to expand...
Click to collapse
Oh, I think it's the 07 Oct one, version 1.0.2.1476973. I didn't see it until this morning (8 Oct Singapore time). No issues with it thus far.
hush66 said:
Oh, I think it's the 07 Oct one, version 1.0.2.1476973. I didn't see it until this morning (8 Oct Singapore time). No issues with it thus far.
Click to expand...
Click to collapse
Yeah me too. Just updated. App didn't force close or anything and watch seems to be the same still. Dropped 2% after update though -.-
The Oct 7 wear update just crashes on my Moto X. Had to uninstall and reinstall the older verwion from titanium backup. It did that with the earlier release too, I think it's date was Oct 3. There is something wrong somewhere.
Well after a recharge and another reset along with deleting all wear app data and uninstalling it and removing the 360 from the Bluetooth menu it synced and send ok again today. Plus the original slow notification issue is gone now too. Now if they'd just give be an option to show the step card less often is be set
mward7221 said:
The Oct 7 wear update just crashes on my Moto X. Had to uninstall and reinstall the older verwion from titanium backup. It did that with the earlier release too, I think it's date was Oct 3. There is something wrong somewhere.
Click to expand...
Click to collapse
Hi, same situation here on Droid Mini.
Can you send me your backup for older Wear?
Thanks
heres the apk before the update, uninstall updated app and install this one.
https://dl.dropboxusercontent.com/u/28511905/com.google.android.wearable.app-1.apk
The new release today (1.0.2.1534065 Oct 23) doesn't seem to fix the problem either. Both of the most recent updates cause this issue for me:
Android Wear 1.0.2.1534065 (current, Oct 23 release) Google Play or apkmirror
Android Wear 1.0.2.1476973 (Oct 6 release) apkmirror
Work arounds I've unsuccessfully tired so far:
Install/re-install, clearing Android Wear data & cache
Removed all other Wear apps
Cleared data & cache from Google Play Services
Factory reset Moto 360
Switched from ART to Dalvik & back
Direct install of v1.0.2.15 and v1.0.2.14
Upgrade from functioning v1.0.1.13 to v1.0.2.15 and to v1.0.2.14
Even tried to re-enable all of the pre-installed Moto bloat I had previously frozen
Multiple combinations of the above, with reboots between steps
I can, however, still use the older version of the Android Wear app without issue:
Android Wear 1.0.1.1379611 (Oct 2 release) apkmirror
Anyone with any other suggestions?
hungmung said:
Well after a recharge and another reset along with deleting all wear app data and uninstalling it and removing the 360 from the Bluetooth menu it synced and send ok again today. Plus the original slow notification issue is gone now too. Now if they'd just give be an option to show the step card less often is be set
Click to expand...
Click to collapse
You can turn the step cards off. That's what I did. When u receive one. Just swipe until u get to settings and turn it off.
I have a european no brand G3 D855 3GB (non rooted). Near the end of March I checked for updates and it showed the M available, with change log, etc. I was low on battery so I choose not to apply it at the moment, counting on completing it the day after.
Except when I checked again the next day, it said that I was on the latest available versions (5.0!), with no further updates available.
I kept checking on various occasions, but it seems definitely gone.
Has this happened to anyone other?
Is there a way to clear whatever "flag" may have been set and redo the proper search & discovery?
Thx!
I just updated to the new T-mobile October update today and ever since then, I have a constant notification from "Carrier Hub" that says "Processing requests" and "MCM Client requests are processing...". My research shows this is a Sprint app, and I am a Sprint customer, but this SIM is a T-mobile SIM because it is all becoming T-mobile and the Sprint network is being shut down in January. It won't allow me to uninstall the app. Before the update, I would occasionally see the notification for a second or two before it went away, but now this is constant. It can't be swiped away. I can tell it to not give notifications, but since it can't be found in Settings or apps, in the future I won't be able to undo that setting. It seems to say it isn't using up battery, thankfully, but I don't know why it isn't processing whatever requests. Seems like there have been these issues with it for over a year on others' phones.
Anyone else have this issue after the new update? Anyone know how to fix it? (A factory reset is NOT an option.)
ButterflyFlutterflyMyOhMy said:
I just updated to the new T-mobile October update today and ever since then, I have a constant notification from "Carrier Hub" that says "Processing requests" and "MCM Client requests are processing...". My research shows this is a Sprint app, and I am a Sprint customer, but this SIM is a T-mobile SIM because it is all becoming T-mobile and the Sprint network is being shut down in January. It won't allow me to uninstall the app. Before the update, I would occasionally see the notification for a second or two before it went away, but now this is constant. It can't be swiped away. I can tell it to not give notifications, but since it can't be found in Settings or apps, in the future I won't be able to undo that setting. It seems to say it isn't using up battery, thankfully, but I don't know why it isn't processing whatever requests. Seems like there have been these issues with it for over a year on others' phones.
Anyone else have this issue after the new update? Anyone know how to fix it? (A factory reset is NOT an option.)
Click to expand...
Click to collapse
Try app pops using shizuku
ButterflyFlutterflyMyOhMy said:
I just updated to the new T-mobile October update today and ever since then, I have a constant notification from "Carrier Hub" that says "Processing requests" and "MCM Client requests are processing...". My research shows this is a Sprint app, and I am a Sprint customer, but this SIM is a T-mobile SIM because it is all becoming T-mobile and the Sprint network is being shut down in January. It won't allow me to uninstall the app. Before the update, I would occasionally see the notification for a second or two before it went away, but now this is constant. It can't be swiped away. I can tell it to not give notifications, but since it can't be found in Settings or apps, in the future I won't be able to undo that setting. It seems to say it isn't using up battery, thankfully, but I don't know why it isn't processing whatever requests. Seems like there have been these issues with it for over a year on others' phones.
Anyone else have this issue after the new update? Anyone know how to fix it? (A factory reset is NOT an option.)
Click to expand...
Click to collapse
I'm on T-Mobile and have the same issue. I disabled the carrier hub service notification and that stopped the notification from appearing. I am able to access the app when I enable "show system apps" from the filter and sort menu of the apps menu under settings.
rsfinsrq said:
I'm on T-Mobile and have the same issue. I disabled the carrier hub service notification and that stopped the notification from appearing. I am able to access the app when I enable "show system apps" from the filter and sort menu of the apps menu under settings.
Click to expand...
Click to collapse
Thank you!! I just disabled the notification. Thankfully, it still says it has used 0% battery after running for 6 hrs. 45 min., so it doesn't affect battery life somehow, but I don't know if affects our signal or what.
ButterflyFlutterflyMyOhMy said:
Thank you!! I just disabled the notification. Thankfully, it still says it has used 0% battery after running for 6 hrs. 45 min., so it doesn't affect battery life somehow, but I don't know if affects our signal or what.
Click to expand...
Click to collapse
Hopefully it gets sorted out with the next update. I'm not going to worry about it for now as it doesn't seem to be affecting anything. Just happy to get rid of the annoying notification.
I was able to turn it off in the developer options last night and this morning it came on again. What gives?
Neufaze said:
I was able to turn it off in the developer options last night and this morning it came on again. What gives?
Click to expand...
Click to collapse
I turned it off as described in my previous post and it has not returned. Not sure why the developer options route did not work but might want to give it a try and see if it sticks. Hopefully a future firmware update or service provider configuration update fixes it.
I went into the apps and turned it off. Hopefully it sticks. Thanks
Mine normally clears after I let it sit for a couple hours and then reboot.
I don't want to just turn off the notification because then it'll be doing something but I just won't see it. I want it to just stop running. I tried to force stop and that worked for about a day then it came back. Anyone got any updates on this yet?
No update yet. I'm leaving the service notification off until the next update, then I'll turn it back on and see if the issue has been resolved.
Neufaze said:
I don't want to just turn off the notification because then it'll be doing something but I just won't see it. I want it to just stop running. I tried to force stop and that worked for about a day then it came back. Anyone got any updates on this yet?
Click to expand...
Click to collapse
I am fine with turning the notification off because it doesn't drain the battery, but maybe you can try downloading the T-mobile version of the app from the Play Store and see if it works and fixes the problem?
Just had a new Play System Update 55mb. I'm now on Nov 1 instead of the August 1 after the last update.
https://imgur.com/a/yknsVGp
Same here.
Still on September. Won't find any update.
There is no way to force/sideload this, right?
@m1ckbr1t
Thanks for the heads up.
I have been checking a couple of times per week to update to the November patch, but I hadn't checked since Wednesday last week; I didn't realize the update was there until I saw your post
I went from Nov. 5 to Nov. 1
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Bxrider117 said:
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Click to expand...
Click to collapse
Yes it did
Bxrider117 said:
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Click to expand...
Click to collapse
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
MacGuy2006 said:
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
I've had none of these issues
MacGuy2006 said:
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
have you guys seen this page. I dunno what to think anymore. the hype around Pixels is such a weird thing. I get that there are bugs (and I've had a few glitches) but none of the bugs I've had are even listed here:
Google Pixel 6, 6 Pro, & 6a new updates, bugs, issues, problems tracker
A detailed & continuously updated round-up of everything related to Google Pixel 6, 6 Pro, & 6a updates, bugs, issues, & problems.
piunikaweb.com
MacGuy2006 said:
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
When the phone fails to read your Fingerprint (something along the lines of three or four times in a row), it automatically blocks/deactivates the FPS, until you unlock it with your TO KNOW security measure (in your case PIN).
I had it happen to me a couple of times over the course of this month, and it was a tad too annoying to shrug off. I definitely miss my old P4 Faceunlock, never bothered me (except when I wore masks, lel).
I had it as well ... was on Nov 1, update, reboot and still on Nov 1 ...
Note there are two things: (a) security update (Nov 5 in my case) and (b) Play-systemupdate (Nov 1 in my case).
See screenshot.
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
roirraW edor ehT said:
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
Click to expand...
Click to collapse
Damn that's huge for a play system update. You have an unlocked device or carrier?
roirraW edor ehT said:
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
Click to expand...
Click to collapse
You apparently ordered the supersize version at the drive-thru
pimpmaneaton said:
Damn that's huge for a play system update. You have an unlocked device or carrier?
Click to expand...
Click to collapse
Yes, I have the Unlocked (and rooted) 512 GB model, using on AT&T. Maybe it hadn't checked for any Play System updates since I rooted - since I waited to root (and disable verity and verification, and flash the stock firmware and wipe) until just a week and a half ago (I think).
I confirm it now says November 1. Thank goodness Settings has search and I'm also glad it remembers my last several searches in settings, even after a reboot.
Lughnasadh said:
You apparently ordered the supersize version at the drive-thru
Click to expand...
Click to collapse
LOL!!!!
Lughnasadh said:
I went from Nov. 5 to Nov. 1
Click to expand...
Click to collapse
You do realize that Google Play system update (Settings > About phone > Android version > Google Play system update) is different from the monthly security patch (Settings > System > System update), right?
snoopygum said:
You do realize that Google Play system update (Settings > About phone > Android version > Google Play system update) is different from the monthly security patch (Settings > System > System update), right?
Click to expand...
Click to collapse
Yes, of course.
Lughnasadh said:
Yes, of course.
Click to expand...
Click to collapse
Excellent, because judging by some of the posts here that's not quite universal.
In case anyone is still confused:
Monthly patch - Nov 5
Google Play system Update - Nov 1
any noticeable changes? I'm asked to reboot... but I rather not until the next system update