Anyone have a changlog for this?
Day-0 update, that I have been putting off in case it causes any issues with gaining root in the near future.
http://www.droid-life.com/2013/08/2...o-12-7-7-on-first-boot-here-is-the-changelog/
Related
Update includes "Vodafone Rescue" app.
New build is 1.35.161.2.
Anyone know if there's actually anything worthwhile in this release ?
Same as the others, bug fixes and some speed ups. Do it, always worth keeping up to date
Looks like the postcode problem has been fixed. This pleases me.
EddyOS said:
Same as the others, bug fixes and some speed ups. Do it, always worth keeping up to date
Click to expand...
Click to collapse
I prefer to tread with caution. I did an OTA update on my DHD to Gingerbread, and lost the ability t root it when they locked down the bootloader.
Look before you leap I think is the right approach with this!
I also just got advised there is a 1.35.707.1 update available for mine.. but will wait a few days and see whats in it.
There's nothing in it, it's just bug fixes. Temp-root still works and it improves the phone. There's no benefit in holding off updating. Once we get S-OFF it won't even matter
Charging my Sensation now takes 2.5 hours instead of 5 hours. This alone was worth updating from my perspective.
Couple questions here.
360 Mobile Security gets plenty press by claiming it provides hotfixes. I haven't noticed new ones since 2012. I've noticed the same hotfixes offered to users upon installation of the app put onto any android I've observed to date. Obviously we're well into KitKat now, so are these hotfixes redundant by now due to upgraded systems since then? If not, then why haven't these issues been resolved with carrier or custom firmware by now? still claim to be exploits that your android needs even on the most recent phones. They explain what kind of exploits they'e patching, but not referencing the specific alleged exploit.
For older phones not yet rooted, does CM Security and/or 360 Security fix the MasterKey exploit and other older ones now fixed by JB 4.3 and KitKat? They don't mention that they do, yet they may do so. They also do not discuss whether they address dirty USDD issues, etc.
Thanks for any responses.
If you check the code from CM, these two commits are all binarys.
Can anyone explain what is the software problem and how they fix it?
A lot of us are still thinking this "fix" is just a workaround on software level. Some even suspect that the "fix" will cause battery drain.
I think if they can explain to us what was happening, it will make the users a lot more confident in the product.
As the title says, is it safe to update the 6 if you just got it or should you wait until Asus pushes out a fix? The only information I can find is what update caused the issue but not if the update has been fixed.
XDA article for context: https://www.xda-developers.com/asus-zenfone-6-devices-motherboard-malfunction/
Hoodnj said:
As the title says, is it safe to update the 6 if you just got it or should you wait until Asus pushes out a fix? The only information I can find is what update caused the issue but not if the update has been fixed.
XDA article for context: https://www.xda-developers.com/asus-zenfone-6-devices-motherboard-malfunction/
Click to expand...
Click to collapse
I have updated from v156 to v174 without problems but as is mentioned in the article the issues mostly likely seem to come from motherboard malfunctions not effectively fixable via software updates. Furthermore they don't seem to be widespread/affect all devices.
If your phone is still stock/unmodified you could update and if any issues arise you can take their offer to send it in for repair and not have eventual problems with them because the phone is rooted or modified (depending on your country).
regenwurm16 said:
I have updated from v156 to v174 without problems but as is mentioned in the article the issues mostly likely seem to come from motherboard malfunctions not effectively fixable via software updates. Furthermore they don't seem to be widespread/affect all devices.
If your phone is still stock/unmodified you could update and if any issues arise you can take their offer to send it in for repair and not have eventual problems with them because the phone is rooted or modified (depending on your country).
Click to expand...
Click to collapse
Yes that wasn't clear it me either. It seems from the article that the software update is causing the hardware to malfunction but if what you're saying is true then it's strictly a HW issue that could pop up at any point.
In that case I'll update and hope for the best. Thanks for the response!
Shall I update ??
https://photos.app.goo.gl/chjiaTbQLZBZAcmL9
From what I read the problem was the .167 update and it was that update that caused the hardware problem. They pulled that update so it should be safe to update now
Sent from my ASUS_Z01RD using Tapatalk
Nothing is broke, I dont see why I should update. I've learned my lesson about updating when everything is working fine. I'm on Tmobile with an unlocked N10+.
Updates are more likely to bring improvements than problems. And without updates, you have no protection from newly discovered security vulnerabilities. So I'd recommend updating unless you're ok with the possibility of someone remotely and covertly taking over your phone.