Note to moderators: Due to the content, I believe this warrants its own thread. We have a separate thread for the OTA (for manual download), and a separate thread dealing with The X/G/E 4.4.4 rollout as a whole, which has long since devolved from there. I didn't see any release notes for our specific update posted, other than the false and regurgitated 4.4.3/4 hybrid notes for carriers. If you still feel that this post should be rolled into one of those separate threads, I can respect that.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/100863
ENHANCEMENTS
After installing the software update you will notice numerous enhancements and changes, including:
Android™ 4.4.4, KitKat® Android 4.4.4, KitKat, is the latest release of the Android platform and includes enhanced security updates to OpenSSL.
Click to expand...
Click to collapse
As expected, it's primarily just an OpenSSL security fix, though there are other hinted enhancements, likely bug fixes to any of Motorola's under the hood differences from AOSP.
I know that there were many people who were concerned with the delay in this update. It's because Android 4.4.4 wasn't really needed for our device, just as not all Nexus devices got 2.3.7 or 4.3.1 (device-specific changes).
The actual AOSP changes from 4.4.3 to 4.4.4 was literally one OpenSSL security fix. HTC backported this fix to their 4.4.3 software, hence why they're not rolling out 4.4.4 on their devices. Google also made changes to Google Play Services to mitigate this security issue, so any device from Android 2.3 to the present has this fix (to a degree, see * for details) with or without Android 4.4.4.
So, why did Motorola update the carrier variants to 4.4.4 ahead of the unlocked and developer editions? The unlocked/developer editions got 4.4.3 while most of the carrier variants were still on 4.4.2. Moto's 4.4.3 update provided new features for the Moto X such as pause while video recording, as well as the new Android dialer and some camera enhancements. By the time that 4.4.4 was released, most carriers delayed their update to have this security fix incorporated, while the unlocked/developer edition models were already good to go.
Most of the carrier-branded 4.4.4 variants have a Motorola software version beginning with 212, but this variant got 213. So it's likely that this update has some other Moto changes that will eventually filter out to the carriers, or be incorporated into their L-updates.
*This security fix plugs a security hole. The update to Google Play Services acts more like an anti-virus. It does two things. First, it prevents the upload of apps to the Play Store that would exploit this loophole, and it scans your devices side-loaded apps (if enabled by the user) for apps that use this. Basically, if you have Google Play services installed and up to date, you cannot be affected by this bug. If you're running a pure AOSP-based OS modified on a Chinese handset without Google Play Services, then you need 4.4.4 to avoid this security issue.
I got my 4.4.4 on Sunday. (Dev Edition)
Tapatalked from my G PAD 8.3
If it's not a major update, I'd rather wait for the next major release (L?), instead of doing all the revert to stock - reroot procedure.
Is there a way I can stop getting the OTA notifications? They are really intrusive, and it wants to install itself, but I don't see any options to not get it.
TheSaw said:
If it's not a major update, I'd rather wait for the next major release (L?), instead of doing all the revert to stock - reroot procedure.
Is there a way I can stop getting the OTA notifications? They are really intrusive, and it wants to install itself, but I don't see any options to not get it.
Click to expand...
Click to collapse
You can freeze the OTA apk its called something like moto ota or Motorola ota
it is so annoying that it prompted me to move away from stock. geez. that damn thing popup in themiddle of you typing an email!
Also, why the heck that is not available on the site? i can only download 4.4.2 and .4.2.2! not even 4.4.3... motorola support for a dev phone is sad. absolutely no help. not to mention not a word on how to integrate all the nice hardware on the custom images. sigh... sucks to be a sucker.
A500, will work with 6.0? We already had 5.0 and it's still work... Some of bugs but don't worry about them anyway... I knew that http://forum.tegraowners.com been having that ROM 5.0 but it's almost been year they didn't update yet when they're already released 5.0 for our Acer A500 and A501 but never been get updates like 4.0 did until 4.4.4 then new released 5.0 and stopped update... We do not understand why... But we're hopeful you're going release updates for fixes some bugs for 5.0 please? If you're development who still work on that, then please let us know ASAP... Because we do not want A500 and A501 become no long to be able same what we have already (6.0) and (6.0.1)...
Thank you for your time, We won't let A500 and A501 down, because they're helping us lots, lot fun too!
Hi. i am looking to upgrade my tablet to newer version of Android. It has 4.0 now. OTA upgrades there are none available. Is there a guide to follow on how to install a newer ROM in the tablet, please?
This is a really old device and the Dec community has for the most part moved on. You will most likely find no updates in the future.
Honor Started their EMUI 9 based on Android Pie 'a beta testing. They recruited 500 users for it. But now all they are doing is madness.
First they released a faulty version of beta which they send to Beta and no beta tester which make their devices to stick in eRecovery. They fixed that problem, devices were recovered. But now its even more of a different story.
They are providing beta update randomly to users. Beta tester and non beta testers are getting pie beta while in a different pace they also releasing a Feb security patch.
Now the problem is, when a non beta tester(a general user) gets the beta update they can't report any bug, they are stuck. And those who signed up, if they update the security patch they are getting kicked out from beta program. It has been such a mess.
Please XDA, you can reach to Huawei/Honor when we cannot. Please take this problems public, only maybe then they will provide these things correctly.
For a reference: https://club.hihonor.com/in/topic/361221/detail.htm
i also got kicked out from the project after updating my security patch. I was so much excited for the project but now m dissapointed badly
Sony released remote play for all Android phones this week with compatibility from Android 5.0 onward but it's recommend to have Android 10 to use a DS4 due to better compatibility drivers. Is there any chance you could rip the drivers from the OnePlus 7 or 7 pro on OOS 10 put them in a zip and flash them through TWRP or magisk?
I think you just need to wait since the official update is coming this month of October.
Graffiti Exploit said:
I think you just need to wait since the official update is coming this month of October.
Click to expand...
Click to collapse
Not to argue specifics but the beta comes out this month and the full release is next month. But I understand your point. I still want to know if it's possible to do it though.
Drivers are in the kernel in Linux based systems. You can't just 'rip' the drivers. You have to find a kernel Dev willing to work this with a soon deprecated Android version... with yet unpublished oos kernel sources, only AOSP ones. Not easy
That's why it will be more easy to wait beta / official OOS. Or perhaps be ready to try one of the Android 10 ROMs floating around there
Striatum_bdr said:
Drivers are in the kernel in Linux based systems. You can't just 'rip' the drivers. You have to find a kernel Dev willing to work this with a soon deprecated Android version... with yet unpublished oos kernel sources, only AOSP ones. Not easy
That's why it will be more easy to wait beta / official OOS. Or perhaps be ready to try one of the Android 10 ROMs floating around there
Click to expand...
Click to collapse
Understandable thanks for the answer, I thought it was more like the adreno drivers that you could update through TWRP or magisk I forget which one I just remember doing it on my V20.