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
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'm still on 4.4.2 and wondering if I should update.
Are you guys happy with the update?
When it first came out, I remember reading people complaining about lagging when starting apps.
Have you guys experienced those issues? Any other issues?
Do you guys think it's worth it?
Sorry if this has been discussed. I have tried to find a post talking about the impressions of the update but I couldn't
find something specific.
Thanks!
Mostly pretty good. I'm not fond of all the white backgrounds, but as long as I have root and can use TiBu and a few other apps, I am happy. Nice to have RAW format cameras available.
Beyond that, I couldn't really recommend the upgrade at this time, too many people having problems with it, if you do the upgrade OTA you lose root, etc.
For me Lollipop is so much better than 4.4.4, which introduced home button issues. I find the phone to be so much smoother and slightly faster. Battery life is also better---I am back to getting about 6 hours of screen on time in a 24 hour period. I am 100% stock.
I agree, in my opinion lollipop is every bit as good as the hype behind it would indicate. I updated mine today and am definitely not disappointed! Lovin it!
I have to admit that this is the best release that At$t and Samsung have done for a phone. Pretty much got everything right minus the bloatware.
Nucleartx said:
I have to admit that this is the best release that At$t and Samsung have done for a phone. Pretty much got everything right minus the bloatware.
Click to expand...
Click to collapse
Gotta love TiBu (if you rooted muniz way)
Only issue I am seeing, for me, is a weaker cell signal. Normally had 4 to 5 bars on kit kat, now I am getting 2 to 3 and sometimes down to only 1 bar. Otherwise, no other issues that I can report on.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
AT&T as expected still disabled Dropbox support for the stock file manager and gallery app and kept Samsung account cloud syncing disabled as well.
Thanks a lot for the responses, guys. I updated yesterday and everything looks good so far.
Still fiddling to get apps to sd (ext sd) AND work a few min. later. Somehow Unfortunately... has stopped toast pops up after move to sd attempt. Then unable to move back after.
I'm on rooted s5 active (5.0 & NOT 5.0.1 or 5.0.2). An xposed module worked before (like a month & a half to 2 months ago). But....
Any help greatly apreciated. And yes I'll hit the thanks button too. Lol
cmerlyn said:
Mostly pretty good. I'm not fond of all the white backgrounds, but as long as I have root and can use TiBu and a few other apps, I am happy. Nice to have RAW format cameras available.
Beyond that, I couldn't really recommend the upgrade at this time, too many people having problems with it, if you do the upgrade OTA you lose root, etc.
Click to expand...
Click to collapse
I was under the impression that RAW didn't actually work as RAW. Is that incorrect?
slicetwo said:
I was under the impression that RAW didn't actually work as RAW. Is that incorrect?
Click to expand...
Click to collapse
Yeah, it's a bit weird. Some of the camera apps save RAW format as a PNG, which is not the same. It is uncompressed, but still not the same as a DNG file, which is what RAW is supposed to use. I am not sure if there are any camera apps that use DNG. On the other hand, if you are not that fussy, the PNG files are pretty nice to work with.
cmerlyn said:
Yeah, it's a bit weird. Some of the camera apps save RAW format as a PNG, which is not the same. It is uncompressed, but still not the same as a DNG file, which is what RAW is supposed to use. I am not sure if there are any camera apps that use DNG. On the other hand, if you are not that fussy, the PNG files are pretty nice to work with.
Click to expand...
Click to collapse
Awesome! So they're still the same quality as RAW? That's all I really care about. What apps would you recommend for capturing PNG/RAW images?
slicetwo said:
Awesome! So they're still the same quality as RAW? That's all I really care about. What apps would you recommend for capturing PNG/RAW images?
Click to expand...
Click to collapse
I've been using Camera++ with good results. Note that there seem to be two camera apps called Camera++, I think the one I used has been pulled, I can't find it in the Play Store. You might try MI2RAW camera, it actually saves in DNG. Edit: that one isn't compatible. Camera FV-5 is, but it isn't free. Let me know if you find a good one.
I read that fv-5 said it wasn't compatible with the s5 when I was initially researching this. Hmm.
I also have enjoyed 5.0 battery life is better, phone feels more responsive than before, i just do not like that I cannot have a swipe + pin for my lock screen like I used to on kitkat.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
It'd be nice to have an option for vibrate notifications during calls, i.e. for incoming texts, emails, call waiting. This existed in the previous iterations of touchwiz but disappeared with lollipop. Lame. Speaking of call waiting it seems to notify late. Seems I get a tone, look at the phone, and then it's suddenly a missed call. When I try to turn call waiting on or off in the "more" tab of call settings it is grayed out.
Other than that it's decent. Battery life is good. It's fairly smooth.
There does seem to be some issues with in call notifications in general however. Sometimes I'll get no notifications during a call, then a rash of them upon ending the call.
Overall not terrible, not great. Doesn't feel like a truly finished product to me however.
This is 5.0 on a G870A
Killer Okain said:
Doesn't feel like a truly finished product to me however.
Click to expand...
Click to collapse
I've never felt like an update was a truly finished product. Maybe I haven't owned the right phones or used the right carriers in the past. I look at the update roll-out as part of the finishing process itself.
Has anyone had an issue with missed calls and missed text messages not being displayed at the icons on the screen that is shown after unlocking (the 'home' one) ?
I'm also seeing quite a few dropped calls (about once per hour if talking on the phone the entire time).
Here's another complaint... Why did they uncouple 'ringtone' and 'notification' in the sound menu, and not give an option to couple them? So now when I select a low volume using the volume key, incoming texts are still on full blast until I go in and manually lower the notification volume as well. This is ridiculous. Why do they break things that previously worked well? These touchwiz devs need to take some lessons from the CM team.
Killer Okain said:
Here's another complaint... Why did they uncouple 'ringtone' and 'notification' in the sound menu, and not give an option to couple them? So now when I select a low volume using the volume key, incoming texts are still on full blast until I go in and manually lower the notification volume as well. This is ridiculous. Why do they break things that previously worked well? These touchwiz devs need to take some lessons from the CM team.
Click to expand...
Click to collapse
I have been using an app called Audio Volume Mixer. It lets you set each volume independently, plus has settings for silent mode and vibrate only. Works very well for me.
Hi,
I have a Z3 Compact running pre-rooted Android 5.1.1 Lollipop. I got a notification about software update that i can't dismiss. i don't know if i should upgrade or not so force stopped the software update app.
What is your opinion about Marshmallow?
Are there any bugs?
Are there new features added and some features removed?
Is it worth upgrading to Mashmallow or should i keep Lollipop?
sorry i can't upgrade without user reviews
You can dismiss the update notification if you want (disable it).
MM has officially been out for only a few weeks and consequently is still full of bugs and problems.
The threads are full of the cries for help from the MM rom jumpers, oh the pain of being an early adopter.
Give it another month, by then it'll fixed.
Didgesteve said:
You can dismiss the update notification if you want (disable it).
MM has officially been out for only a few weeks and consequently is still full of bugs and problems.
The threads are full of the cries for help from the MM rom jumpers, oh the pain of being an early adopter.
Give it another month, by then it'll fixed.
Click to expand...
Click to collapse
How do you disable the notification? For which app do I have to do that?
Dont update to Mm.. There is some feature that missed..like battery stamina/ultra stamina..and also the battery drain fast..
Im a z3 compact Mm user
+1 for don't do it (now)
For me I will stay for not specified time at LP (mainly because of custom kernel).
Didgesteve said:
You can dismiss the update notification if you want (disable it).
MM has officially been out for only a few weeks and consequently is still full of bugs and problems.
The threads are full of the cries for help from the MM rom jumpers, oh the pain of being an early adopter.
Give it another month, by then it'll fixed.
Click to expand...
Click to collapse
Thanks. Is it safe to disable software update app?
i don't want unexpected bugs happen or boot loop
evildog1 said:
Thanks. Is it safe to disable software update app?
i don't want unexpected bugs happen or boot loop
Click to expand...
Click to collapse
The next time you see a notification, hold your finger on the notification and the bar will turn black and you will see an information 'i' on the right side, press this.
This will bring up the notification option.
Alternatively, go to settings\apps\scroll to the right until >all apps > 'update centre'
Then - force stop, untick notifications, clear cache/data
You won't get any more notifications about MM and no this won't harm or damage your phone in any way. Your phone will work fine on 5.1 for years and years, it doesn't need MM
Didgesteve said:
The next time you see a notification, hold your finger on the notification and the bar will turn black and you will see an information 'i' on the right side, press this.
This will bring up the notification option.
Alternatively, go to settings\apps\scroll to the right until >all apps > 'update centre'
Then - force stop, untick notifications, clear cache/data
You won't get any more notifications about MM and no this won't harm or damage your phone in any way. Your phone will work fine on 5.1 for years and years, it doesn't need MM
Click to expand...
Click to collapse
Ok i just uninstall updates, force stop, and clear data, but i could not disable the notification.
evildog1 said:
Ok i just uninstall updates, force stop, and clear data, but i could not disable the notification.
Click to expand...
Click to collapse
If you have root, then go to the market and install ES Explorer
Open it, go to menu, look at the bottom 'tools'.
tick 'root explorer'
Go back to the top of the menu and find "home/device/system/app"
Look for "com.sonyericsson.updatecenter.apk"
Make a copy and save it somewhere, like Downloads.
Then delete the original in system/app.
If there is a problem you can always put the copy back in the folder, otherwise you will never get another update message again:good:
Didgesteve said:
If you have root, then go to the market and install ES Explorer
Open it, go to menu, look at the bottom 'tools'.
tick 'root explorer'
Go back to the top of the menu and find "home/device/system/app"
Look for "com.sonyericsson.updatecenter.apk"
Make a copy and save it somewhere, like Downloads.
Then delete the original in system/app.
If there is a problem you can always put the copy back in the folder, otherwise you will never get another update message again:good:
Click to expand...
Click to collapse
Thanks. I just froze it using Titanium Backup
and i'm using X-plore with dual pane
Just like when Sony released 5.0 Lollipop, it was full of bugs and the battery life sucked. It wasn't until 5.1 came out that we finally got a usable ROM. Expect more of the same with MM. Wait until 6.1 is released before upgrading. Especially those who are not rooted. There's no fixes and no turning back for those users.
Sent from the only flagship device that can fit in my hand... Sony Experia Z3 Compact
Sorry to bring back an old thread but I just bought this phone secondhand and its on 5.1 and have received the update notification. Have the bugs that are in the above comments been fixed in 6.1 or is it still not worth upgrading to Marshmallow?
warzinak said:
Sorry to bring back an old thread but I just bought this phone secondhand and its on 5.1 and have received the update notification. Have the bugs that are in the above comments been fixed in 6.1 or is it still not worth upgrading to Marshmallow?
Click to expand...
Click to collapse
For me, the most horrible is the delay when opening apps:
Lag manifests on this way: in response to launching app (Dialer let say) "window"/app pops up immediately but is is empty/white and only after a sec/two content shows up (for Dialer recent call list, favourites/frequent contacts, search). Minimizing app and immediately opening again is ok (it is in cache, background, memory), instant content shows up. But if I launch another app after minimizing dialer and then start dialer again - lag in Dialer is there. As if somehow Dialer is killed in background and need to relaunch again from the start (even full relaunch should not take that long anyway). Same as killing it in recent activities. All other stock apps behave this way. It is really annoying to see such a powerfull phone lags in this basic stock apps, as this doesn't happen on previous android versions (4.4.4, 5.0.2 or 5.1.1).
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Fictional Reality said:
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Click to expand...
Click to collapse
Indeed, I bought an iPad mini, downgraded z3c to KK and life is good.
I use my phone now for what phones are meant to - calling, occasional e-mail, messaging, weather, etc. Battery life is 4..5 days. The car bluetooth shows addressbook again (did not work with LP, MM).
I use power toggles as lock screen widget for bluetooth, wifi, hotspot switch. Lock screen does not require additional swipe. All other things, in reality, work as they work with LP, MM.
For heavy use larger screen is recommended anyway - for the health of your eyes first of all.
Fictional Reality said:
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Click to expand...
Click to collapse
bookworth said:
Indeed, I bought an iPad mini, downgraded z3c to KK and life is good.
I use my phone now for what phones are meant to - calling, occasional e-mail, messaging, weather, etc. Battery life is 4..5 days. The car bluetooth shows addressbook again (did not work with LP, MM).
I use power toggles as lock screen widget for bluetooth, wifi, hotspot switch. Lock screen does not require additional swipe. All other things, in reality, work as they work with LP, MM.
For heavy use larger screen is recommended anyway - for the health of your eyes first of all.
Click to expand...
Click to collapse
Really? What problems did LP & MM bring to the z3c? If it is just better battery then I think I will stay with LP...(unless its twice as good on KK). The camera quality is important for me, are any of them better/worse than others?
Do I just use a 23.0.1.A.5.77 FTF file from here and flash it using Flashtool as the instructions here? I have not rooted or unlocked bootloader, all stock.
warzinak said:
Really? What problems did LP & MM bring to the z3c? If it is just better battery then I think I will stay with LP...(unless its twice as good on KK). The camera quality is important for me, are any of them better/worse than others?
Do I just use a 23.0.1.A.5.77 FTF file from here and flash it using Flashtool as the instructions here? I have not rooted or unlocked bootloader, all stock.
Click to expand...
Click to collapse
There is nothing wrong in MM.
Except for some people who do not use phone 12x7.
Since the concept ROM I was wondering why the battery gets empty even if I do nothing with it. The answer was Doze of course. Yes, I tried several ways for activating aggressive doze, but was not satisfied with these.
Then I decided to go retro and KitKat is all I really need, with its working STAMINA.
For camera I use Sony A6000 and you really can not compare real camera with phone.
If you use your phone heavily, please do not downgrade.
If you have smartwatch, please do not downgrade.
If you feel unsure about flashing, please do not downgrade.
If the warranty is dickbutt in your country - please do not downgrade.
If you still decide to downgrade, then yes, your instructions are correct.
NB! The flash will take long time. Be pacient. It seems to be stuck but it just stays in one place for 5..10 minutes and then everything is ok. I have not measured the exact time, but I was horrified at first flash - it really seemed stuck. Perhaps it is just with my phone.
Scared of MM, really?
Firstly its been out quite some time now, especially if you consider N has just been released to the Nexus range.
Stamina mode and Doze are fantastic, I get 2 days+ with my compact and it's on 24/7.
I also have audited my startup items and background apps to reduce load on then phone which pays dividends.
The initial MM upgrade didn't include Stamina but Sony have since released an update bringing it to the masses.
Your call in the end but don't let scaremongerers cloud your judgement, do some reading, reviews from good sources and make your own minds up.
I did and only issue I had, which I know probably isn't just down to MM, was the emergency dialling issue on lockscreen.
3rd party app cured that for me so now the phone doesn't sit in my pocket making random noises and dialling whoever it pleases anymore!
Fictional Reality said:
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Click to expand...
Click to collapse
LP running fine for me. I only have 1 bug is video playback freezing while buffering.
asmetoma said:
Stamina mode and Doze are fantastic, I get 2 days+ with my compact and it's on 24/7.
Click to expand...
Click to collapse
I've got 4...5 days with KitKat, phone is also on 24/7 (but of course, I do not USE it 24/7). No root.
It's not about scare - the phone is too cheap to be scared, besides there are many new phones to choose from with really good batteries.
However, I do not feel that I should change the phone and I like when I do not have to charge it often.
---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------
Perhaps one should take into consideration that the workload of the phones has been increased a lot during last few years. Specially if you have smart devices etc.
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!
To those who have updated to Android 9.0, have you seen any improvements/fixes specific to the RP2? I know many of us have noted issues with the speakers (notably at lower volumes) and the camera software (mostly fixed by using Gcam), although there's been other more isolated/random issues for some too (Bluetooth, cellular signal, etc).
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Hangouts doesn't give a notification sound when the app isn't open. I've made another thread about that earlier
------------------------------------------------------------------------------
Never mind. Had to go deep into Hangouts settings to fix it. Still annoying
I would willingly trade fully functional wifi for speakers that don't crackle and cut out at lower volumes, since I have unlimited data and solid LTE signal everywhere I go. Though I've had that wifi issue on rare occasion on Oreo too.
They moved the clock :'(
Anyone notice potential decrease in touch sensitivity after the upgrade? I had a screen protector on and it seemed like I need to push down a little more to get the touches to register. Took off the protector to test and it was fine with just the screen. Put another one on and occasionally touches aren't registering or registering but releasing early on swipes.
Sent from my Phone 2 using Tapatalk
CalebQ42 said:
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Click to expand...
Click to collapse
How do you unlock your bootloader, bro? How did you root your phone?
acegrace said:
How do you unlock your bootloader, bro? How did you root your phone?
Click to expand...
Click to collapse
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Gamesoul Master said:
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Click to expand...
Click to collapse
crap, i just updated last night - can i factory reset and do the same thing?
alawiggle said:
crap, i just updated last night - can i factory reset and do the same thing?
Click to expand...
Click to collapse
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Gamesoul Master said:
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Click to expand...
Click to collapse
nice, thanks!