Related
Hey everyone,
Just wanted to ask a quick question regarding the firmware
I got my UK unlocked S5 last week and as soon as I set it up, an update came through, which is 100mb, the note regarding say "Improved performance", the update download, but I haven't installed it yet. Mainly because of a bad experience I had after updating my S3. I haven't come across any bugs since I've been using it, and I'm concerned that if I update, the battery will drain quicker, or perhaps cause an error in the recovery mode(these things happened to my S3 after updating to 4.3). So 2 main questions.
1. Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
2. Suppose I updated and wasn't happy with the new changes? Would it be possible to go back to the original firmware version that my phone came with when I took it out of the box, *without rooting my S5?
Hope some people on here can shed some light on these questions.
Thank you in advance*
1. It's just a system update. The phone is new there are bound to be updates as issues are ironed out
2. You can odin any firmware whenever you want
Sent from my SM-G900F using Tapatalk
MasterfulNinja said:
Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
Click to expand...
Click to collapse
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
International Business Times said:
Issues Spotted for the Android 4.4.3 Kitkat
The Android 4.4.3 Kitkat system update is pretty much all about improving performances, strengthening stability and fixing a couple of bugs. However, it reels in a couple of issues experienced by users of Nexus devices that have already been upgraded to the latest update.
According to IT Pro, some of these issues include wi-fi problems, crashes and reboots and bugs found in apps. Google has not yet given any statement about how to deal with these issues nor has there been any word if these issues are only experienced by a handful.
Click to expand...
Click to collapse
.
.
fffft said:
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
.
.
Click to expand...
Click to collapse
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
MasterfulNinja said:
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
Click to expand...
Click to collapse
1. Yes, a data factory reset after a update/flash a rom is remmended and gives best performance and stability;
2. I haven`t tried flashing a older rom itself but it should be possible i guess as this is not dowgrading like from 4.4.2 to 4.3. You could try it and if it fails there`s no harm done as you can flash your current rom back.
3. Installing a update or flash a rom usualy will kill root, though superSU Pro offers a survival mode to keep root after a update. You can also flash a rom with Mobile Odin Pro and enable everroot and the 2 other options so you will not loose root.
@MasterfulNinja
I don't automatically accept updates. Someone more impulsive, or indifferent can be the guinea pig. That approach is effective in avoiding some unpleasant firmware surprises. Often an older firmware version runs smoother and is more stable as in your IOS 5 vs 7 example. Running an older firmware means that you may have unpatched security vulnerabilities but in practice this usually isn't a great or unmanageable problem. It is a point to keep in mind though.
Rooting isn't nearly as dangerous as many people think it is. Someone who can follow directions and avoid flashing firmware from a completely different device will rarely brick a phone. And even if you did, you can usually recover from the mishap. I mention this because one of the best ways to maintain a stable phone OS is to install a decent custom ROM (which typically requires root). And then most of the heavy lifting is done by the developer who has already removed bloat, restrictions and other objectionable pieces. And monitors and releases tailored and usually stable updates for those using his ROM.
Android updates vary in size because they are screened by carriers, each deciding what update components and /or custom bits goes into their version of the update. More restrictive Apple manages all IOS updates centrally from their California servers i.e. they don't relinquish direct control to carriers. Still it isn't hard to find articles giving a good summary of what issues android firmware updates are addressing.
Some people believe that you should accept every update and as soon as it becomes available. I don't see a compelling need to update unless you are trying to resolve a current bug or are enticed by a specific new feature. I don't recommend a factory reset after each update. I do recommend that you clear the system cache from recovery mode though. A factory reset usually won't benefit you but it is time consuming to reinstall and reconfigure your phone.
Having said that, if you have a specific issue, such as the 4.3 battery drain then you have a rationale for doing so. But I have to say that I experienced the same S3 issue and clearing the cache was sufficient to stabilize the phone for me. Some phones will develop corruption or configuration conflicts over time, especially if you install a lot of apps. Or if you have a specific app that makes a mess of your file system. With that in mind, I do do a factory reset about once a year to clean up the phone, the same as I would do for a laptop OS. But I don't see a reason to do it after every update.
Odin is a Samsung product, complete with DRM. So no, you cannot flash anything with Odin. You can flash most stock firmware and in particular Odin will look for OEM signatures if you try to change the bootloader or modem. In the case of downgrading, it is the Knox qfuse on your phone that will cause the Odin flash to fail. If you try to downgrade you end up with a partial flash which can soft brick your phone and trip the Knox flag.
.
Simple answer - NO.
When a new software release is made for an OS, all the developers would have done is test it on a very few devices within the developers and then roll it out to testers. And after analyzing the bugs identified from these testers, the developers sit on fixing it and finally come up with a release. Now would this release be bug-less? Absolutely not! Remember, its only been tested amongst a very few number of people and the rolling out happens to thousands residing in different parts of the world. If you think about it, what these updates are gonna deal with is a varied number of users, different carriers, sim make etc etc.
Take for example, for Indian users, the 4.4.2 update has been rolled out for quite a while. Lots of bugs were identified since then and the forum managers have been collecting data from the subscribers for quite a while now (Almost 4 months). Still the fix has not happened. And now 4.4.4 is out and issues persist.
I hvae been using 4.3, 4.4.2, then CM11, Mokee ROM etc etc, and now Im finally back to stock 4.3, coz thats the most stable version. So if you are someone who is interested in trying out new releases, please go ahead, but if you are someone who needs a stable ROM with no signal drop issues, please stick to 4.3.
totally disagree. I have european version Moto G with stock 4.4.2 and everything is working perfeclty. Try to wipe you Moto or flash any other rom.
seems like pebkac not buggy firmware . otherwise every single guy would be facing same problems and that's not happening .
ovitz said:
totally disagree. I have european version Moto G with stock 4.4.2 and everything is working perfeclty. Try to wipe you Moto or flash any other rom.
Click to expand...
Click to collapse
Just to clarify, did you receive an update package sometime after the primary update?
4.4.3 works fine on my US GSM moto G. But it might be different for others.
Also, add a warning to the OP that if you're already on 4.4.3+, you can't downgrade anymore. Motoboot from 4.4.3+ doesn't seem to like downgrading anymore, unfortunately.
4.2.2 works great, no signal drops or anything. Waiting for eupean 4.4.4. :good:
Sent from my XT1032 using Tapatalk
Question is whether downgrading is possible from 4.4.4 ?
I totally agree to ovitz. Updates are supposed to fix issues with older versions of the software. My moto came with 4.4.2 and i never had issues with signal drops. I am from India. Btw it's always better to reset phone after the update.
I agree with you OP on some extent. I also recently downgraded to 4.3 from 4.4.2 just for the lulz, because I was getting "image is too large" error but surprisingly today the flashing was successful. The battery timing has improved, dialer app is cooler than that of the 4.4.2. I'm finding these changes quite interesting because I didn't stay with 4.3 for too long; my Moto G received the KitKat update the moment I powered it on for the first time.
techpick said:
Simple answer - NO.
When a new software release is made for an OS, all the developers would have done is test it on a very few devices within the developers and then roll it out to testers. And after analyzing the bugs identified from these testers, the developers sit on fixing it and finally come up with a release. Now would this release be bug-less? Absolutely not! Remember, its only been tested amongst a very few number of people and the rolling out happens to thousands residing in different parts of the world. If you think about it, what these updates are gonna deal with is a varied number of users, different carriers, sim make etc etc.
Take for example, for Indian users, the 4.4.2 update has been rolled out for quite a while. Lots of bugs were identified since then and the forum managers have been collecting data from the subscribers for quite a while now (Almost 4 months). Still the fix has not happened. And now 4.4.4 is out and issues persist.
I hvae been using 4.3, 4.4.2, then CM11, Mokee ROM etc etc, and now Im finally back to stock 4.3, coz thats the most stable version. So if you are someone who is interested in trying out new releases, please go ahead, but if you are someone who needs a stable ROM with no signal drop issues, please stick to 4.3.
Click to expand...
Click to collapse
While I do agree with you for most of what you said, not everyone has bugs or issues with their phones on 4.4.3/4.4.4 upgrade. I myself has had one bug that came with the phone since 4.3 and it's worst now on 4.4.3 and ironically, I've gotten all the bugs on the 4.4.3 that others were getting on 4.4.2. I ended up putting on CM11 because it was getting to me.
P.S. It's impossible to downgrade from 4.4.3/4.4.4. I would love to downgrade back to 4.3. Never got the chance to see how it behaved on my phone because I updated to 4.4.2 the moment I booted for the first time.
Did I mention the "Sign in to WiFi" error on the 4.4.2? That's annoying as hell.
usertag said:
Question is whether downgrading is possible from 4.4.4 ?
Click to expand...
Click to collapse
It is possible!, download the 4.4 official ROM and do a fastboot and install all the IMG files.
Thats how I did it,
chrisdf said:
It is possible!, download the 4.4 official ROM and do a fastboot and install all the IMG files.
Thats how I did it,
Click to expand...
Click to collapse
but you can't downgrade the bootloader, so didn't you get any errors?
Not that guy, Don't touch the motoboot and you should be fine
There's no point of updating your phone unless youare receiving it over OTA. Doing it manually is risky. The only thing that you'll get is new AOSP dialer and few security fixes. There's no reward..no improvement in performance as well as in camera quality. People are reporting bugs all over the globe and they desperatly want to switch back to 4.4.2. Few have them are also facing downgrading issues.
And you want to go through all this for just a minor update? Android L could be a good reason as it is worth updating even after bugs. But a minor update is definitely not.
If some one will ask me which is best ROM for my moto g? I would say Stock 4.4.2. I tried all custom ROMs but no one was as smooth as stock 4.4.2.
Consequences be damn'ed.
Simple answer- yeah, well, that's just like your opinion man.
Indian user. Unlocker my bootloader, Converted to GPE while on 4.4.2. The GpE move was made partly because I had jo desire nor the use if a second sim and mostly because I wanted a clean OS. Period.
Got instant OTA update to 4.4.4 to the day it was pushed.
No issues so far, None in fact and it's been over a week or thereabouts(I admit to the likelihood of me being an isolated case)
Lastly, to each his own.
Android is meant to be taken care of AS WELL tinker every single detail or option if you have the cojones for it. Ciao.
:thumbup:
Sent from my XT1032 using XDA Free mobile app
I have just upgrade to 4.4.4 XT1033 (Malaysian), noted the missing 2 empty simcard icone and new rather flat dialer! nothing much has changed and certainly hasn't noticed any issue mentioned herein!
If one were to go by op opinion then they would be using 4.3 for the rest of the devices life ! I wonder what his comment would be once L comes to our device.
I have to disagree the OP as an xt1033 owner since march 2014.
Android 4.4.4 OTA for moto g helps fix various sw issues and increased performance,new baseband to aid the radio issues. Media playback is improved. The device is more of a swiss-tool now.
GPe edition of Moto G running KTU84P.M003 like a dream and eats more battery,too. I wish i could have flashed it earlier.
Semseddin said:
GPe edition of Moto G running KTU84P.M003 like a dream and eats more battery,too. I wish i could have flashed it earlier.
Click to expand...
Click to collapse
Just curious, if it eats more battery how come you call it a dream?
Yes, this has probably been gone over ad nauseum throughout the site. Due to time constraints I cannot dig through the forums as much as I'd like, so I'm simply going to ask.
Phone: Samsung Note III (SM-N900V)
Carrier: Verizon Wireless
OS Version: 4.4.2
Baseband Version: N900VVRUCNC4
Kernal Version: 3.4.0
Build Number: KOT49H.N900VVRUCNC4
Hardware Version: N900V.07
It was purchased November 2013 with OS 4.3. Over the summer I accepted the OTA update to 4.4.2. My phone went to hell. Battery gets chewed through like a woodchipper, phone is horribly laggy, antenna connection is always 1-2 bars under where it was prior to update (and doesn't get reception in areas it did before), changes to the UI are less than desirable, etc.
The phone was never rooted, as this was the first phone I've ever had that worked well enough on stock software that I skipped it.
After giving it a few months on the update and trying changes/tweaks within the updated stock software to fix the issues the update caused, I'm at the end of my patience. Contacting support at both Verizon and Samsung was pointless, with one blaming the other for the problems.
What I'd love is to take the OS back to 4.3 and leave it, but in lieu of that I want to root the hell out of it and put a build on without these issues and a better antenna software. I'd prefer not to void the KNOX, but at this point I'd microwave it if it'd help.
I have no backups or root access from before the update to base a root on. I tried towelroot; install button doesn't work and I understand the maker Geohot works for Google now. I started to play with Odin, however the install seems to have an oddly high amount of other software it wants to install, and even after declining those it doesn't want to install (tried 3.09 and 3.10, I'm using Windows 7 w/latest SP and updates). Also, it drives my AV software crazy, so even turning that off and working with it didn't get me very far.
So, at this point, I'm open to most anything to get this crap off my phone, and my only requirement is that I don't brick it.
Options?
Thanks in advance for any help.
HarlockTaliesin said:
Yes, this has probably been gone over ad nauseum throughout the site. Due to time constraints I cannot dig through the forums as much as I'd like, so I'm simply going to ask.
Phone: Samsung Note III (SM-N900V)
Carrier: Verizon Wireless
OS Version: 4.4.2
Baseband Version: N900VVRUCNC4
Kernal Version: 3.4.0
Build Number: KOT49H.N900VVRUCNC4
Hardware Version: N900V.07
It was purchased November 2013 with OS 4.3. Over the summer I accepted the OTA update to 4.4.2. My phone went to hell. Battery gets chewed through like a woodchipper, phone is horribly laggy, antenna connection is always 1-2 bars under where it was prior to update (and doesn't get reception in areas it did before), changes to the UI are less than desirable, etc.
The phone was never rooted, as this was the first phone I've ever had that worked well enough on stock software that I skipped it.
After giving it a few months on the update and trying changes/tweaks within the updated stock software to fix the issues the update caused, I'm at the end of my patience. Contacting support at both Verizon and Samsung was pointless, with one blaming the other for the problems.
What I'd love is to take the OS back to 4.3 and leave it, but in lieu of that I want to root the hell out of it and put a build on without these issues and a better antenna software. I'd prefer not to void the KNOX, but at this point I'd microwave it if it'd help.
I have no backups or root access from before the update to base a root on. I tried towelroot; install button doesn't work and I understand the maker Geohot works for Google now. I started to play with Odin, however the install seems to have an oddly high amount of other software it wants to install, and even after declining those it doesn't want to install (tried 3.09 and 3.10, I'm using Windows 7 w/latest SP and updates). Also, it drives my AV software crazy, so even turning that off and working with it didn't get me very far.
So, at this point, I'm open to most anything to get this crap off my phone, and my only requirement is that I don't brick it.
Options?
Thanks in advance for any help.
Click to expand...
Click to collapse
This is the best breakdown of what you need to do. Click here, scroll till you see the blue outline for NC4 OTA.
Be sure to hit "thanks" on @az_biker link for this tutorial!
Unfortunately this won't work, I've already tried. When running the towelroot installer the Install button is not clickable. The other buttons function normally.
Op did you ever hey the note rooted....did you get the towel root to work
chefb said:
Op did you ever hey the note rooted....did you get the towel root to work
Click to expand...
Click to collapse
No to both, unfortunately.
I've had no issues with towelroot. But for giggles make sure you have install from unknown source checked, and then unlock your developer options and make sure USB debug is enabled, then give it another shot.
Sent from my Baja'd 4.4.2 Note 3
cjamison08 said:
I've had no issues with towelroot. But for giggles make sure you have install from unknown source checked, and then unlock your developer options and make sure USB debug is enabled, then give it another shot.
Sent from my Baja'd 4.4.2 Note 3
Click to expand...
Click to collapse
did you take a ota
I have not, since the leaked NC2 firmware was leaked out. However on my s4 I just used towelroot with the latest NC5 firmware, and it worked flawlessly.
Sent from my Alliance 4.4.2 Note 3
Are we expecting any updates soon or the 5.0.1/2 update to fix the bugs that were, presumably, introduced with 5.0?
For instance, the Pebble watch disconnecting constantly. Seems perfect on my M7 with 5.0.2.
Really hope this is done quickly, as it's pretty much unusable right now.
No one knows when 5.0.1 will come, but keeping in mind that 5.1 will be released later this month I guess there's chance that Sammy might go crazy and skip 5.0.1/2 altogether and jump directly to 5.1!
If you want this topic as some request kind then its better to create it in sammobile.
Thanks for the reply.
I just hope Samsung can push through some small bugfix update then in regards to the bluetooth then. It's a big shame I can't really use the Pebble anymore.
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
s1m4an said:
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
Click to expand...
Click to collapse
Hello
May I direct you here: http://forum.xda-developers.com/gal...-official-5-0-firmware-galaxy-t3029557/page79
dariox provided this workaround, which has been working very well for me and keeping my Pebble connected.
"Download BlueTooth auto connect (UniqTec developer)
Set:
"set last device" Flag
Profiles : select all
devices : select your device, and flag in the options "healt hdp" in case of smartband ecc...
Set flag on : Bluetooth on
Device Disconnected
Device Connected"
Unfortunately, it seems to come at the cost of a constant wakelock, and battery drain, but at the moment we don't really have any other choice apart from rolling back to kitkat, getting a new phone, or stop using the Pebble.
Hope this helps.
It's Lollipop's fault, I had the same problem when I upgraded, both the early version and the official version had the same result.
I downgraded back down to KitKat and it's fine now.
I have read some reports about bad battery life with Lollipop. Is this true?
KitKat has nicer system UI regarding the use of E-ink screen because KitKat menus, settings etc. use darker backgrounds than Lollipop. That looks better on E-ink on black YotaPhone 2.
What are your thoughts on KitKat vs Lollipop with YotaPhone 2?
I also read some reports about Wifi issues with Lollipop but maybe they were relating to wrong radio being flashed, I don't know.
sonof said:
I have read some reports about bad battery life with Lollipop. Is this true?
KitKat has nicer system UI regarding the use of E-ink screen because KitKat menus, settings etc. use darker backgrounds than Lollipop. That looks better on E-ink on black YotaPhone 2.
What are your thoughts on KitKat vs Lollipop with YotaPhone 2?
I also read some reports about Wifi issues with Lollipop but maybe they were relating to wrong radio being flashed, I don't know.
Click to expand...
Click to collapse
Your post just crossed mine (http://forum.xda-developers.com/yotaphone-one/general/battery-life-ru-134-firmware-using-app-t3490355) but for me battery life on Lollipop is great and I have no WiFi issues. The latest RU firmware also has the september 2016 security update. For me it is Lollipop all the way.
Where did you download the latest RU firmware?
In here:
ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
The latest is 5.0.0-RU1.1.124.zip
Where to find 134?
sonof said:
Where did you download the latest RU firmware?
In here:
ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
The latest is 5.0.0-RU1.1.124.zip
Where to find 134?
Click to expand...
Click to collapse
134 is indeed not yet up on the FTP site but if you flash your phone to the 124 version using YotaFlasher it will then update itself to 134 using OTA.
I hate lollipop myself and going to flash back to KitKat toninght.
spinecki said:
I hate lollipop myself and going to flash back to KitKat toninght.
Click to expand...
Click to collapse
Why? What problems do you have?
I've noticed my phone got laggy after 3 months or so on Lolopop, but I never used KK.
JernejKobal said:
Why? What problems do you have?
I've noticed my phone got laggy after 3 months or so on Lolopop, but I never used KK.
Click to expand...
Click to collapse
I hate LP dialer and menus. I just loved KK and that's mostly why I want to go back
spinecki said:
I hate LP dialer and menus. I just loved KK and that's mostly why I want to go back
Click to expand...
Click to collapse
I decided to go back KK but i could't find the stock firmwares for Turkey. Yes i can use RU or EU firmware but i am not sure for finding the right baseband for me. Any idea will be appreciated?
sozen said:
I decided to go back KK but i could't find the stock firmwares for Turkey. Yes i can use RU or EU firmware but i am not sure for finding the right baseband for me. Any idea will be appreciated?
Click to expand...
Click to collapse
Both will work. Baseband is not a firmware thing.
Am going to downgrade from Marshmallow to Kitkat.
There are issues such as more battery drain than its supposed to be, phone overheats too much (never happened on kitkat before) and Marshmallow's white theme makes me sick as there is no option to change it to dark so it doesn't really fit in Yotaphone 2 unless you have white version which is pretty rare one. YotaStore apps arent compatibile with MM 6.0.1 so..
There are new things that are improved or added but still wont use it
Sukalya said:
Am going to downgrade from Marshmallow to Kitkat.
There are issues such as more battery drain than its supposed to be, phone overheats too much (never happened on kitkat before) and Marshmallow's white theme makes me sick as there is no option to change it to dark so it doesn't really fit in Yotaphone 2 unless you have white version which is pretty rare one. YotaStore apps arent compatibile with MM 6.0.1 so..
There are new things that are improved or added but still wont use it
Click to expand...
Click to collapse
I have used mine with Nova launcher which allows you to make dark theme. But I am still going to do the same for especially overheating problem. Indeed i've faced lots of problems with MM:
- Overheating on almost every situation including EPD reading/browsing/maps etc.
- if (esp. extreme) YotaEnergy is activated, Mobile Network is killed/blocked until restart the phone. Disabling YotaEnergy again doesn't solve the problem
- EPD screen lock insensibility randomly
- very restricted settings on MM
- etc.
Update1:
I have installed KK (4.4.3-S01-003-RU1.0.3.61a). Findings:
- battery seems a little bit ok compared MM
- overheating problem is same i think
- EPD screen resolution is awfull
- As known, all apps are outdated
- KK interface is also offensive compared with my old KitKat installed Optimus G Pro
So, i have to try Lollipop
Update2:
I have finally installed LP (5.0.0-RU1.1.134 ). It is ok:
- battery is optimum, there is no drain and stable
- no unexpected overheating, it is ok!
- EPD screen resolution is good
- I wish i could launch the color screen directly from EPD screen like on MM shortcut. For EPD, MM is better.
Unfortunately even after downgrading to kitkat then update to lollipop (RU or EU) I still get the overheating issues
Before upgrading to MM it was fine, but from that point it began to overheat and I can't get it to stay cool again.
bohwaz said:
Unfortunately even after downgrading to kitkat then update to lollipop (RU or EU) I still get the overheating issues
Before upgrading to MM it was fine, but from that point it began to overheat and I can't get it to stay cool again.
Click to expand...
Click to collapse
You are right! After a few week trying, heating problem seems same. Because of that i have decreased CPU clock Frequency to 1267MHz+conservative. The heating problem decreases nearly fifty fifty.
bohwaz said:
Unfortunately even after downgrading to kitkat then update to lollipop (RU or EU) I still get the overheating issues
Before upgrading to MM it was fine, but from that point it began to overheat and I can't get it to stay cool again.
Click to expand...
Click to collapse
If you want to try the first stock rom which is preinstalled 4.4.3-S01-003-ME1.0.3.61a for me, i can provide you a full TWRP backup (system, data, boot).