Related
Android police just announced that a 4.1.2 update has been released to AOSP, and the Nexus 7 is apparently already receiving it!
We're releasing Android 4.1.2 to AOSP today, which is a minor update
on top of 4.1.1.
As a note to maintainers of community builds running on Nexus 7: please update to 4.1.2 at the first opportunity. Future variants of the grouper hardware will have a minor change in one of the components (the power management chip) that will not be compatible with 4.1.1.
The build number is JZO54K, and the tag is android-4.1.2_r1.
Enjoy,
Conley and JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Update #1: 4.1.2 has already started rolling out to the Nexus 7, though mine doesn't see it yet.
Update #2: Since I mentioned seeing 4.1.2 with this very build number in the server logs, I'll throw in the devices that I saw running it, in addition to the Nexus 7 (this doesn't mean the updates for them are out now, but rather a good indication of what's to come):
Are we ready?
JellyBean 4.1.2, the incremental follow up to 4.1.1 isn’t a major update by any means, but promises to improve performance, increase stability and fix certain bugs.
It also adds rotation ability to the homescreen, something that wasn’t possible in the previous version of the software.
Could someone please post a dump of this (or point me towards the easiest way to download it while running a custom ROM on my N7)? I'd like to hack away at pulling out the launcher and making an update.zip for it.
Hi everyone, I hope this update will fix the lag problem with few mb/gb free on my N7.
I dont want to flash the factory image cause it wipes everything.
If I flash a nexus 7 stock rooted odexed will I receive the update? What do u suggest?
Hopefully Google fixed the bad display calibration!
http://tinyurl.com/8ouzlks
dragpyre said:
Android police just announced that a 4.1.2 update has been released to AOSP, and the Nexus 7 is apparently already receiving it!
Are we ready?
Click to expand...
Click to collapse
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now, I will soon I'm sure,
JBQ also said that the updated factory images will be available as soon as the OTA is, and that the change can be pulled from the commits in the repository..
That's all for now.
So I have my Nexus 7 rooted and unlocked running stock software, will I be fine to get the OTA?
Sent from my Nexus 7 using xda app-developers app
rootusr said:
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now, I will soon I'm sure,
JBQ also said that the updated factory images will be available as soon as the OTA is, and that the change can be pulled from the commits in the repository..
That's all for now.
Click to expand...
Click to collapse
No OTA is available now!
rootusr said:
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now
Click to expand...
Click to collapse
Actually, there are many reports of Nexus 7 users getting the update so it is rolling out now. It also adds home screen rotation to the stock launcher.
ezegm said:
So I have my Nexus 7 rooted and unlocked running stock software, will I be fine to get the OTA?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think you will get the update-notification at least..
The question is if a custom-recovery prevents updating.
edit: xda-user dalew729 says he uses CWM and updated OTA without problems....
rockvoid said:
No OTA is available now!
Click to expand...
Click to collapse
Unfortunately, because I'm new i can't post links. If you check the other 4.1.2 thread, and follow the Android Police link, you'll see screenshots detailing this.
dragpyre said:
Unfortunately, because I'm new i can't post links. If you check the other 4.1.2 thread, and follow the Android Police link, you'll see screenshots detailing this.
Click to expand...
Click to collapse
sorry i wanted to post "no, OTA is available now!"
rockvoid said:
sorry i wanted to post "no, OTA is available now!"
Click to expand...
Click to collapse
I'm going from Glazed JellyBean back to stock for this! XD
bozzykid said:
Actually, there are many reports of Nexus 7 users getting the update so it is rolling out now. It also adds home screen rotation to the stock launcher.
Click to expand...
Click to collapse
Yeap, that is what Im Looking now, no word about that from JBQ but there are those reports, No update for me yet.
Saw the 4.1.2 being reported on twitter. Has me all tingly, curious to see what else is included besides home screen rotation. Currently running Codename android rom so I have to wait. :fingers-crossed:
rootusr said:
Yeap, that is what Im Looking now, no word about that from JBQ but there are those reports, No update for me yet.
Click to expand...
Click to collapse
JBQ has nothing to do with the OTAs so he will not be announcing it.
I really can't wait to try this update out!
Unfortunately, I'm not getting any OTA updates. D:
http://forum.xda-developers.com/showthread.php?t=1928731
Beaten by 2 minutes.
Closed
Which device is more like the razr i? I mean, same specs.
Which device you had greater success when porting (rom) to the razr i?
"Google it" didn't help at all.
Hey I have the answer
diw's said:
Which device is more like the razr i? I mean, same specs.
Which device you had greater success when porting (rom) to the razr i?
"Google it" didn't help at all.
Click to expand...
Click to collapse
Hi!
I did the same search and i find that the razr m have almost same specs, except for the processor:
Motorola Razr i have Intel Atom
Motorola Razr M have Qualcomm MSM8960 Snapdragon S4
There is a cyanogenmod 11 rom for the razr i, but i want to port a cyanogenmod 12 rom made for the razr m.
Sorry For My Bad English
It isnt possible because the source code isnt the same, the drivers too. And the razr i runs on Intel Medfield x86 platform. So its completely different from the ARM platform and Qualcomm processor.
droidsaur said:
Hi!
There is a cyanogenmod 11 rom for the razr i, but i want to port a cyanogenmod 12 rom made for the razr m.
Click to expand...
Click to collapse
Looks great! Thanks a lot!
Hey lelapincretin8 , wouldn't it be just a hard rewrite? If you know what I mean.
My bad. Bad english!
diw's said:
Hey lelapincretin8 , wouldn't it be just a hard rewrite? If you know what I mean.
My bad. Bad english!
Click to expand...
Click to collapse
No. The library's used in the CM12 rom are for ARM architecture. ARM code doesn't run on x86 architecture like on the Razr I. You can't rewrite that. Like lelapincretin8 said
Few new phones with intel cpu and android 5.0 should be released soon:
- Nokia C1
- Asus Zenfone 2 (source code - http://forum.xda-developers.com/showpost.php?p=59365057&postcount=19)
- Asus Zenfone Zoom
That looks a good idea but their own Intel platforms are more recent and more enhanced than ours. We run on Medfield and it's a too Intel plateform. So, we might have issues by patching or by inspiring the code from the recents Intel plateforms. Correct me if Im not right.
lelapincretin8 said:
That looks a good idea but their own Intel platforms are more recent and more enhanced than ours. We run on Medfield and it's a too Intel plateform. So, we might have issues by patching or by inspiring the code from the recents Intel plateforms. Correct me if Im not right.
Click to expand...
Click to collapse
Some software if usable, some isn't. Like the new Houdini Lib. We are now using the version 4.1.1* or something from our 4.4 rom. But the newest version is 5.0 and can be found in those devices. We just need to try and figure out. But i need the kernel code to set SElinux to permissive to start testing CM12. It now runs in trouble with permissions (surfaceflinger crash), gkisystem crash (dunno if we can solve that and i need to use the 'init' file from CM11. CM12 'init' executable doesn't mount the partitions. I don't even know if it does for recovery.
Has Houdini been disappeared for ART on LL? I heard that ART manages automatically multiples codes for the applications like x86, ARM, ARM 64, etc... Isn't it?
Hazou said:
No. The library's used in the CM12 rom are for ARM architecture. ARM code doesn't run on x86 architecture like on the Razr I. You can't rewrite that. Like lelapincretin8 said
Click to expand...
Click to collapse
Ok. I got it. Tnx Hazou and lelapincretin8!
My bad. Bad english!
i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?
I pulled the source via repo, but I haven't got around to a build yet.
Gene Poole said:
I pulled the source via repo, but I haven't got around to a build yet.
Click to expand...
Click to collapse
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?
opssemnik said:
i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?
Click to expand...
Click to collapse
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.
F4uzan said:
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.
Click to expand...
Click to collapse
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing
cell2011 said:
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?
Click to expand...
Click to collapse
gapps relly on the system framework (sdk), radio and bootloader rely on nothing, they control the device in a really low level state, in fact the bootloader is the lowest level, since it starts the kernel.
Sometimes radios/bootloader causes issuses depending on the combination but thats because of the blobs system wise, not because of the os version.
And gapps were updated on M
opssemnik said:
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing
Click to expand...
Click to collapse
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.
F4uzan said:
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.
Click to expand...
Click to collapse
Does anyone happen to see what android ver this will be? 5.2?
cell2011 said:
Does anyone happen to see what android ver this will be? 5.2?
Click to expand...
Click to collapse
Nah, just m-preview. It's just like L, the development tag is l-preview.
F4uzan said:
Nah, just m-preview. It's just like L, the development tag is l-preview.
Click to expand...
Click to collapse
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.
dekefake said:
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.
Click to expand...
Click to collapse
Thanks for pointing out ! I totally missed the point that the SDK version is still 22.
I'll try rebuilding M again, the fault could be on my side.
So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5
cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5
Click to expand...
Click to collapse
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M
opssemnik said:
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M
Click to expand...
Click to collapse
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is
cell2011 said:
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is
Click to expand...
Click to collapse
im just thinkering with it, nothing for public release.
however you guys can use ext4 image unpacker to work directly with the factory images
http://i.imgur.com/T9SCUSR.png
cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
Click to expand...
Click to collapse
I think a combo build with 5.1.1 - M is possible, adding M commits to a 5.1.1 source code, and then, try to build.
Qualcomm posted a few days ago a set of new drivers for our nexus 5, this time its for 5.1.1 LMY48I
no changelog provided.
Source: https://developer.qualcomm.com/download/adreno_nexus_sept2015.zip
Download(specific zip for the nexus 5, tested under TWRP and Chroma rom):
https://drive.google.com/file/d/0BwduAK2l37OaNmlqcDNZcjVTc1k/view?usp=sharing
opssemnik said:
Qualcomm posted a few days ago a set of new drivers for our nexus 5, this time its for 5.1.1 LMY48I
no changelog provided.
Source: https://developer.qualcomm.com/download/adreno_nexus_sept2015.zip
Download(specific zip for the nexus 5, tested under TWRP and Chroma rom):
https://drive.google.com/file/d/0BwduAK2l37OaNmlqcDNZcjVTc1k/view?usp=sharing
Click to expand...
Click to collapse
There is already a thread about it.
Most people say either they're having problems with that driver (not sure if it is 48M version related) or the gain with it is at best negligible .
wizardwiz said:
There is already a thread about it.
Most people say either they're having problems with that driver (not sure if it is 48M version related) or the gain with it is at best negligible .
Click to expand...
Click to collapse
the only thread i see is for 4.4 and op hasnt updated it in a year, and these drivers are for more stability or adding features(i.e opengl extensions), you should not have a huge or noticiable performance increase.
opssemnik said:
the only thread i see is for 4.4 and op hasnt updated it in a year, and these drivers are for more stability or adding features(i.e opengl extensions), you should not have a huge or noticiable performance increase.
Click to expand...
Click to collapse
Actually the 4.4 thread has evolved and it covers 5.5.X
As for myself, crashed me android with 48M ver
opssemnik said:
the only thread i see is for 4.4 and op hasnt updated it in a year, and these drivers are for more stability or adding features(i.e opengl extensions), you should not have a huge or noticiable performance increase.
Click to expand...
Click to collapse
I post updates in the OG thread sometimes for these drivers since the OP and most users who used to maintain them seem to have moved on. I did already post these (if you searched the other thread [emoji14]). You would also have seen that most users did report several different bugs which were also confirmed with other users.
Oh and as per Qualcomm;
"This release is intended only for developers, and does not meet our customer release quality."
Expect bugs. Read the established thread for more info!
This work in Android M Preview 3?
Is this working on LMY48M?
parag60288 said:
Is this working on LMY48M?
Click to expand...
Click to collapse
It didn't work for me. got me stuck on android screen. Had to re-flash system.img (LMY48M)
Can anyone update xposed to work with the new security fixes applied to newer android 4.4.4 builds ?
New fix: Install the apk file found here:
Http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
edit: old fix:
read the attachment txt file and copy two files from an older build for your device to those folders (/system/lib & (/system/bin)
http://forum.xda-developers.com/showpost.php?p=63864337&postcount=35
@rovo89 : can you update it please?
robuser007 said:
Can anyone update xposed for the new security fixes found in newer android 4.4.4 builds ?
Click to expand...
Click to collapse
Black_Focus_X said:
@rovo89 : can you update it please?
Click to expand...
Click to collapse
What devices and ROMs are you using that have these problems, and what is in the error logs and logcat?
Without this information, no one can help you, not even rovo89 himself.
Also, have you searched the forum to see if others have this issue and what's been learned about it?
It's Samsung Galaxy S3 with Cyanogenmod 11 official! I searched the forum but couldn't find an answer. Maybe my english isn't good enough
My device is Motorola RAZR XT910, with a TI OMAP4 ARMv7-A SoC.
Right now, I am on an Unofficial CyanogenMod 11 (Android 4.4.4) ROM which contains the latest security fixes for the Stagefright vulnerability and was built on November 15. When I try to install Xposed framework, using the latest official stable installer from Xposed Repo, I get an the following error: "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
When I was on the latest Official CyanogenMod 11 ROM for my device, that was built back on September 1st, Xposed would install and work properly on it, withour any troubles / warnings / errors. Now, I just want to use the latest build that has me protected against Stagefright but I can not install Xposed framework on it at all.
@rovo89 Is there / will there be any fix for this issue?
Having the same problem with the latest build of CM11 (2015.11.15).
unknownsoldierx said:
Having the same problem with the latest build of CM11 (2015.11.15).
Click to expand...
Click to collapse
Same on XT910 on 15.11 CM11 build!
from XT910 or XT925 using Tapatalk
me 2
samsung n5120, just update the new cm11 then show the error message
Yes, i got the same error message when I updated my Redmi 1S to the newest CM11.
I tried to search in MIUI forum but the answer only for MIUI OS.
I tried the patch for my Redmi 1S, it gave me bootloop.
Are there any explanation for this?
Thanks
Same issue here...Redmi 1s..CM 11 4.4.4 ...xposed not working...any solution ??
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Ok, i'll try
But it can't be a right solution
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
derf elot said:
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
Click to expand...
Click to collapse
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Thank you. I tried it and. Yes it works. Xposed working
---------- Post added at 16:36 ---------- Previous post was at 16:34 ----------
ldeveraux said:
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Click to expand...
Click to collapse
Can you look into his head or what?
LG Optimus 4X HD Nightly 15112015 Xposed not working.
View attachment 3544451
Sorry about the pic being in spanish but is my girlfriend phone and i was giving her instructions via skype. It says "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
derf elot said:
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Click to expand...
Click to collapse
Can someone make an update.zip for recovery ?
Feel free to try the zip I posted here. Make a backup first. Normally re-flashing your ROM should solve any issues, but you never know.
Xposed dead in latest CM11 *Unofficial* rom
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Ohmster said:
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Click to expand...
Click to collapse
You just posted what some other guys posted before you...
And if you would read the thread then you would know there is an update.zip for this problem! With this, Xposed is working without problems!