Related
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
I just got my droid turbo about a week ago, and I've since Been hearing about all the battery drainage issues and charging issues, all of the apps I use are compatible with 4.4 KitKat, so I'm a little leery of upgrading because I use my phone a ton and the massive battery was the main reason I got it over an S6, and so if that is negated, is there any reason to upgrade?
Jordaneer said:
I just got my droid turbo about a week ago, and I've since Been hearing about all the battery drainage issues and charging issues, all of the apps I use are compatible with 4.4 KitKat, so I'm a little leery of upgrading because I use my phone a ton and the massive battery was the main reason I got it over an S6, and so if that is negated, is there any reason to upgrade?
Click to expand...
Click to collapse
My Turbo never had any of the issues others had. Easily get over a day with moderate to heavy use; 2 days with light usage. I'm still on 4.4.4. If you're worried about it, head over to the development section and follow the steps to flash 5.1 without eliminating your option to go back to KitKat.
As is all too common in these forums, those who experience problems go out of their way to publish them, giving the impression that everyone has issues when most, like I, experience none of them. If you are comfortable with the rather detailed (but manageable) process for getting rooted and reversible 5.1, then by all means go that route.
Otherwise, if you are happy with KitKat, don't feel pressured to go to Lollipop. On the other hand, most users (but by no means ever all users) that have taken the OTA upgrade are just fine with the results, with comparable battery life and improved performance in some functions.
Most users have reported that wiping cache solves their performance and battery issues. In your case, I would recommend a full wipe after the upgrade, ask around and you'll find that full wipe after update has almost 99.9% success rate.
So today was my first day being on rooted 5.1.
I unplugged at about 11am, and am now hitting 10% battery 9 hours later. That should suck right?
Well I also wanted to drain my battery today so I just let my phone stream video (plex library ftw) at max brightness.. 8 hours of straight screen on time...
I think in a normal usage day (where Im not trying to kill the battery) I clock 2-3 hours of on screen time...
So if we extrapolate that out, I'm just guessing... I would've made it 20-30 hours of battery at my normal usage.
Is that good? Dunno. No worse than when I was on rooted KK.. perhaps, I think, even better?
I also dirty flashed 5.1 over my 4.4.4.. never wiped cache or FDR.
Hearing that, its up to you to decide what to do, for me I'm sticking with rooted 5.1 and couldn't be happier.
I didn't know you could root 5.1 on droid turbo
Kiwironic said:
I didn't know you could root 5.1 on droid turbo
Click to expand...
Click to collapse
The breakthrough came from this thread yesterday: FrankenPop
Which then lead to this thread late last night: Instructions and first released image
Computerfreek released his image early this morning: Thread
Working from home has its benefits.
EDIT: I am surprised Droid-life or no other outlet has really picked up on this yet.
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Kiwironic said:
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Click to expand...
Click to collapse
You can't root from the ota so do not update that way!!!!
Kiwironic said:
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Click to expand...
Click to collapse
Well if you go to the threads you'll see the root method requires 4..4.4 boatloader.. so taking the official update overwrites the bootloader to 5.1 and at that point there is no going back.
So for the average user, taking the upgrade is a major deal.. for those that don't mind some adb/fastboot work.. absolutely, go back and forth from KK to LP everyday! Just dont touch that 4.4.4 bootloader.
Thanks for the update. It makes sense now. We not talking upgrade vs staying on 4.4.4 we are talking upgrade path.
I see, I am still looking forward to finding a way to upgrade my xt1225 to 5.1 without data wipe, but so far there is nothing for us, no OTA or images yet. No upgrade path in sight
No. You would going from best to OK.
I upgraded to 5.1 and for me it was a mistake. My most valuable app (Record My Call) doesn't work with 5.1 and no other similar app will work either. I'm going to buy another another Droid Turbo on KitKat and sell my 5.1.
Ken
I updated both my and my wife's DT via the OTA. We didn't have root before and I simply haven't needed it, so I figured I'd just go ahead (if anything went wrong, I would have to harass Verizon, but so be it). In the end, both phones are working well (knock on wood)... and I didn't do the cache or factory reset either. Battery life is fine, even with some gaming... so it might be better than KK was, but it's certainly not worse for me.
emgo said:
I upgraded to 5.1 and for me it was a mistake. My most valuable app (Record My Call) doesn't work with 5.1 and no other similar app will work either. I'm going to buy another another Droid Turbo on KitKat and sell my 5.1.
Click to expand...
Click to collapse
Google Voice does this without needing an app.... that might get you a solution for free?
Seems like there are plenty of updated apps that can work in LP as well: https://www.androidpit.com/forum/632761/best-call-recorder-app-for-android-5-lollipop
schwinn8 said:
I updated both my and my wife's DT via the OTA. We didn't have root before and I simply haven't needed it, so I figured I'd just go ahead (if anything went wrong, I would have to harass Verizon, but so be it). In the end, both phones are working well (knock on wood)... and I didn't do the cache or factory reset either. Battery life is fine, even with some gaming... so it might be better than KK was, but it's certainly not worse for me.
Google Voice does this without needing an app.... that might get you a solution for free?
Seems like there are plenty of updated apps that can work in LP as well: https://www.androidpit.com/forum/632761/best-call-recorder-app-for-android-5-lollipop
Click to expand...
Click to collapse
This is from google Voice help.
"It's not currently possible to record outbound calls made through your Google number at this time."
Tried many recommend apps, none work. Found this information in a couple of places.
https://bitbucket.org/copluk/acr/issues/257/after-upgrading-to-android-5-cannot-record
"Motorola has stopped 2 way call recording support with Android 5. This is not our fault. Try any other call recording app you'll see that none works.
Your only option is to set audio source to MIC and set loudspeaker on.
I hope you understand and increase your star rating"
I'm currently looking for a used Turbo still on KitKat
Thanks,
Ken
emgo said:
This is from google Voice help.
"It's not currently possible to record outbound calls made through your Google number at this time."
Click to expand...
Click to collapse
Thanks for the info on Google voice not supporting outgoing calls. I didn't need it, so I never tested it.
emgo said:
Tried many recommend apps, none work.
Click to expand...
Click to collapse
I did a quick search and the recommended app was BoldBeast Recorder. I just tried it with a standard voice call (not GV) I had with my wife (outgoing if it matters) and it worked just fine in Mode 1. After the install, it defaulted to Mode 4 and didn't work, so i was going to start with Mode 1 and go from there... but it just worked there, so i didn't have to go further. To recap, I'm on the OTA updated Lollipop... no factory reset and no cache wipe.
schwinn8 said:
Thanks for the info on Google voice not supporting outgoing calls. I didn't need it, so I never tested it.
I did a quick search and the recommended app was BoldBeast Recorder. I just tried it with a standard voice call (not GV) I had with my wife (outgoing if it matters) and it worked just fine in Mode 1. After the install, it defaulted to Mode 4 and didn't work, so i was going to start with Mode 1 and go from there... but it just worked there, so i didn't have to go further. To recap, I'm on the OTA updated Lollipop... no factory reset and no cache wipe.
Click to expand...
Click to collapse
In mode 1 it records the call but like every app I've tried after the update to Lollipop it's using the microphone to record the call. My voice is loud and clear but the other person's voice is very faint or not heard at all. Did you get different results? Before the update "Record My Call" worked perfectly, it recorded the actually conversation somehow without using the mic.
Thanks,
Ken
emgo said:
In mode 1 it records the call but like every app I've tried after the update to Lollipop it's using the microphone to record the call. My voice is loud and clear but the other person's voice is very faint or not heard at all. Did you get different results? Before the update "Record My Call" worked perfectly, it recorded the actually conversation somehow without using the mic.
Thanks,
Ken
Click to expand...
Click to collapse
I did find my voice was a little louder, but my wife's was perfectly audible. Both required me to turn the volume up, but they worked fine and both were clear...
Maybe another mode would work better, but this was fine for my limited usage.
So I read these complaints and have decided to opt out of the upgrade to Lollipop on my Droid Turbo. When the upgrade notification screen came up, I just put no, and I haven't gotten a notification since. It's been a few weeks for me. A few other people in my family have the same phone. Unfortunately when they click "no" they seems to get the upgrade prompt again a few days later. I'm not sure why the prompt hasn't come up for me again.
Is there a way to stop the upgrade notification prompt for showing up repeatedly without root? I know that there are apps on a rooted system that can prevent the notification. I'm hoping there's a way to prevent it without root. Thanks for any info!
schwinn8 said:
I did find my voice was a little louder, but my wife's was perfectly audible. Both required me to turn the volume up, but they worked fine and both were clear...
Maybe another mode would work better, but this was fine for my limited usage.
Click to expand...
Click to collapse
I tried all modes and mode 1 seems best. I tried many apps that use the microphone and they are all about the same. They work OK if you are in a quite area but a noisy environment or step outside when the wind is blowing and the microphone recorders don't work well at all, not for me. I'm watching Ebay and Craigslist for one still on Lollipop. 64GB models are bringing around $400 no matter which OS they are on. Mine should bring about the same amount that I pay for one with KitKat so hopefully it won't cost much to correct my mistake of upgrading.
Ken
IF there is something I really don't need then it is to know that there's about 1/3 of the power left in the battery! I would like to stop that warning, but I can't find anywhere to do that. Is it possible, or is it a quirk I'll have to live with on this phone? They all have some quirks, just in different areas.
Mastiff said:
IF there is something I really don't need then it is to know that there's about 1/3 of the power left in the battery! I would like to stop that warning, but I can't find anywhere to do that. Is it possible, or is it a quirk I'll have to live with on this phone? They all have some quirks, just in different areas.
Click to expand...
Click to collapse
And the warning is so loud.. I have reported this to Sony so I hope they will change it
Sent from my F8131 using XDA-Developers mobile app
Yeah, hope is always eternal, but I'm afraid that's not likely, since the accelerometer problem (which means that the screen won't follow the phone's direction, but stay in portrait mode) hasn't yet been fixed several months after the first reports. So the best would be if it was possible to fix through an app with a rooted phone or something like that.
Mastiff said:
Yeah, hope is always eternal, but I'm afraid that's not likely, since the accelerometer problem (which means that the screen won't follow the phone's direction, but stay in portrait mode) hasn't yet been fixed several months after the first reports. So the best would be if it was possible to fix through an app with a rooted phone or something like that.
Click to expand...
Click to collapse
That one is fixed... Have you not yet received the nougat update?
Sent from my F8131 using XDA-Developers mobile app
I am on Nougat from about a week ago (Telenor for Norway), and it is most definitively not fixed, at least not in this phone. The phone doesn't rotate at all except for when I use an app, Screen rotate.
Mastiff said:
I am on Nougat from about a week ago (Telenor for Norway), and it is most definitively not fixed, at least not in this phone. The phone doesn't rotate at all except for when I use an app, Screen rotate.
Click to expand...
Click to collapse
I am on beta and it worked from day one here.
I guess you should try a software reset.
Sent from my F8131 using XDA-Developers mobile app
How about three resets in two days? I bought the phone a week ago, after years of Samsung. Took me days to figure out how to root, and in the meantime it had upgraded itself to N because I didn't see what I clicked on (eye operation makes it a bit difficult these days). So I got it downgraded to MM, reset it, backed up the TA files, upgraded to N again, reset it and activated USB debugging for Flashtool, unlocked the bootloader, reset it again and finally set it up the day before yesterday. So I seriously doubt that another rest would change much.
Edit: Oh, and it may be different from phone to phone. According to your sig you do not have the same phone as me.
Mastiff said:
How about three resets in two days? I bought the phone a week ago, after years of Samsung. Took me days to figure out how to root, and in the meantime it had upgraded itself to N because I didn't see what I clicked on (eye operation makes it a bit difficult these days). So I got it downgraded to MM, reset it, backed up the TA files, upgraded to N again, reset it and activated USB debugging for Flashtool, unlocked the bootloader, reset it again and finally set it up the day before yesterday. So I seriously doubt that another rest would change much.
Edit: Oh, and it may be different from phone to phone. According to your sig you do not have the same phone as me.
Click to expand...
Click to collapse
I have not updated my signature...I have the xp.
It is quite funny as all I know of have gotten their screen rotation fixed with the software update. I guess you are unlucky... Which nougat firmware have you installed?
Sent from my F8131 using XDA-Developers mobile app
I see. So it's the map not fitting the terrain.
Well, maybe I should try yet another reset. I have Titanium, so it's quite easy to get back to where I am now if it doesn't help. I have F8131_Telenor Mobil NO_1303-3350_39.2.A.0.361_R7C
So I did. Reset, and didn't do anything but log into my Google account. When I got through the setup process there was no rotation at all. Then I started thinking. Could it have anything to do with the rooting? I use TWRP and the ANdroPlus kernel, and I checked the AndroPlus website. Turned out that they had a new kernel out just yesterday, and the note got me thinking:
v19
Add support for 39.2.A.0.361
Click to expand...
Click to collapse
That was the number on the firmware I'm using. So I flashed that, and bingo! Now I'm rotating! Well, at least my screen is, I don't even dare to think about rotating after yesterday's celebration. Keywords: Crayfish and shrimps, duck breast and chocolate mousse, followed by as many beers as my 50 year old body can take. And that's quite a lot! So today is not my most productive day this year... But thanks for getting me on the right track, if you knew it or not!
Edit: There's a new TWRP recovery as well for the phone, 3.0.3.0, dated a couple of days ago.
Mastiff said:
So I did. Reset, and didn't do anything but log into my Google account. When I got through the setup process there was no rotation at all. Then I started thinking. Could it have anything to do with the rooting? I use TWRP and the ANdroPlus kernel, and I checked the AndroPlus website. Turned out that they had a new kernel out just yesterday, and the note got me thinking:
That was the number on the firmware I'm using. So I flashed that, and bingo! Now I'm rotating! Well, at least my screen is, I don't even dare to think about rotating after yesterday's celebration. Keywords: Crayfish and shrimps, duck breast and chocolate mousse, followed by as many beers as my 50 year old body can take. And that's quite a lot! So today is not my most productive day this year... But thanks for getting me on the right track, if you knew it or not!
Edit: There's a new TWRP recovery as well for the phone, 3.0.3.0, dated a couple of days ago.
Click to expand...
Click to collapse
Hilarious ??? good that it worked out for you.
I am glad for the info as it then was kernel related.
Sounds like you had a great time last night. I hope you get a great year to follow ?
Enjoy your rotating Xperia ?
Sent from my F8131 using XDA-Developers mobile app
I have so say that I hope for a great year too, but it may be an intersting one!
Oh, and found out that it wasn't the kernel after all. It was regular rooting with SuperSU that broke the rotation, so now I'm trying the systemless root from phh. I'll let you now if that works, just to complete this part of the thread (which is really so off the original topic that it should have been split to another thread!).
Mastiff said:
I have so say that I hope for a great year too, but it may be an intersting one!
Oh, and found out that it wasn't the kernel after all. It was regular rooting with SuperSU that broke the rotation, so now I'm trying the systemless root from phh. I'll let you now if that works, just to complete this part of the thread (which is really so off the original topic that it should have been split to another thread!).
Click to expand...
Click to collapse
Thanks man.. I have rooted a lot in the past but I don't want to unlock my bootloader anymore... Back in the days when phones were slower it made sense to root and mess with the config and custom roms.. But today... Not much, what is the reason to why you are rooting?
Sent from my F8131 using XDA-Developers mobile app
I root for two main reasons:
1. You can't do a really good backup in any other way than with Titanium backup, and I like to start semi-fresh every now and then when there's been too much bull tested and tried on the phone.
2, and this is the real kicker: For some idiotic reason a non-rooted Android phone can't do AirPlay in any way. I have a whole-house system that incorporates streaming over WiFi from my phone, and if I don't root, I can't use any of the streaming apps that support AirPlay (my favourite is AirAudio) to stream audio from whatever app I want to, since it can stream the actual phone audio. DLNA is totally useless because I have to use particular apps to stream with that, and they are not the apps I actually use. So basically Google has with a rather dumb choice forced me to root.
Mastiff said:
I root for two main reasons:
1. You can't do a really good backup in any other way than with Titanium backup, and I like to start semi-fresh every now and then when there's been too much bull tested and tried on the phone.
2, and this is the real kicker: For some idiotic reason a non-rooted Android phone can't do AirPlay in any way. I have a whole-house system that incorporates streaming over WiFi from my phone, and if I don't root, I can't use any of the streaming apps that support AirPlay (my favourite is AirAudio) to stream audio from whatever app I want to, since it can stream the actual phone audio. DLNA is totally useless because I have to use particular apps to stream with that, and they are not the apps I actually use. So basically Google has with a rather dumb choice forced me to root.
Click to expand...
Click to collapse
The Xperia backup does the trick for me... It saves data so I have a complete backup.
The second makes good sense, I don't use apple so I don't know the problem but hope it will work out in the future mate ?
Sent from my F8131 using XDA-Developers mobile app
Doubful. It's a proprietary Apple system so they won't support it in Android, and from what I've heard that's why they make it as difficult as possible to support it, so root is necessary. Anyway, I'm good with that, as long as I get root. It took me some days, but Sony's a new thing to me. Still love that ability to work with a wet screen. Samsung really has a problem there.
I only get the warning at 15%, this is where I set the auto stamina to notifiy me when stamina kicks in.
How weird. I have turned off that bull totally, don't need it. I'm never that far from a charger, in my boat, car, house or motorcycle. So no stamina mode at all, still it wines at 30 %.
Mastiff said:
How weird. I have turned off that bull totally, don't need it. I'm never that far from a charger, in my boat, car, house or motorcycle. So no stamina mode at all, still it wines at 30 %.
Click to expand...
Click to collapse
try setting auto stamina at 15%, it's the lowest you can set, and see if the 30% will stop.
Good point, I'll try. I seldom let the battery go so low, while 30 is not that uncommon. I'll try and see what happens later today, thanks!
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Just as a follow up question, would the 'turn Doze off' option help with this? Surely I shouldn't have to do this though?
Am I the only one having this issue? That would suck. Even so, would anybody more adept at these things than me like to have a guess at solving the issue.
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Greedyfly said:
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Click to expand...
Click to collapse
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
smilirulz said:
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
Click to expand...
Click to collapse
I haven't 'cried' about anything, pal, so keep your unhelpful comments to yourself or help. Don't middle ground-it by offering your own personal, and incorrect, opinions.
I hadn't upgraded anything, I was running stock OS and stock marshmallow, so I had literally done nothing to my device other than switch it on and download the same apps I've been using for years.
I've also rooted several devices in the past with no issues and chime in when I can to help, but I'm not a dev and there are far more technologically gifted individuals operating in this forum which is why I sought help here... Not that I got much from you. But I'm more than capable of reading release notes and making sure I can revert backwards before installing anything.
Now to anyone still here, and with the same issue, it appears that carrying out the update to Nougat, re-adding my WiFi networks and clearing system cache solved the problem or at least for the first night. Should this change I'll update here.
ISO_Metric said:
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Click to expand...
Click to collapse
Hi Iso, thank you for your response, I hadn't seen this until now.
The upgrade to 4.0.1 does appear to have done the trick somewhat as it stayed on overnight without issue. I did notice it wasn't on a little later this morning but I am giving the device the benefit of the doubt on that one as I have been messing about with certain things and it's possible I or a profile in tasker switched it off.
As an aside do you recommend any other potential fixes, just to be on the safe side.
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
ISO_Metric said:
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
Click to expand...
Click to collapse
I didn't factory reset, only Cache wipe after the upgrade, and as it seems ok so far, I am reluctant to factory reset the device as it took so long to set up in the first instance.
Should it start becoming an issue again I'll try it but for now...
Also I know there are backup options though I haven't found one that works flawlessly which gives me the confidence to explore this avenue just yet.
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
ISO_Metric said:
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
Click to expand...
Click to collapse
Are you sure ISO? The UI has been updated and the already snappy OS feels snappier. Is there a way to tell for sure if it's required?
If so, any good recommendations for backup capability. I have used Helium to mixed results and I can't use Titanium as I have no root (and don't wish to).
Maybe not but it all elts fails
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(