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.
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
Since everyone always loves MOAR VERSION NUMBAH...
Android 4.3 for the Xperia Tablet Z (SGP311). With a BIG shout out to Sony Mobile for hosting their own git repository for their devices - https://github.com/sonyxperiadev/device-sony-sgp321
This is compiled from AOSP, and has nothing done beyond that. Simply added the Sony repo to Android 4.3 AOSP, and built. As per the Sony AOSP releases, this does not have functional binary parts. This is not functional for practical use.
Working:
Boots
Not Working:
Wifi
Bluetooth
In light of this not being a working build, I will not post it as a zip, but as fastboot flashable images. Unlocked bootloader only. C6603 was used to test, other models entirely at your risk (ie. don't bother).
Links:
All files needed are in
http://goo.im/devs/pulser/TabletZSGP311/4.3AOSP
and will appear there shortly (upload done, it's still propogating)
This is for the SGP311 Pollux_WINDY device - the 16 GB WiFi-Only model. Don't try it on pollux with LTE, it won't boot. Might work on 32 GB wifi only model, but not tested or sure
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
To install:
fastboot flash boot boot.img
fastboot flash system system.img
Build instructions to replicate :
Get android 4.3 sources.
Get sony tablet Z information on repositories and add to local_manifests for 4.3
Get latest v3 blobs for phone and tablet Z
Put them into vendor/sony/
Repo sync
Make
Thanks, @pulser_g2. This is a very necessary and welcome first step towards further development.
And with official v4.2.2 on its way, things should get busier around here. :good:
Great work man THX. Can you make also a build for SGP321 ? I dont have ubuntu installed so i cant compile atm.
m3dd0g said:
Great work man THX. Can you make also a build for SGP321 ? I dont have ubuntu installed so i cant compile atm.
Click to expand...
Click to collapse
I can't test it, so can't be sure it works or anything. If that is the 32 GB model of the pollux_windy, this build should work fine. If it's the pollux (with LTE), then I have no intention to make builds for it, since I have no idea about the device, and I don't just post untested junk
pulser_g2 said:
I can't test it, so can't be sure it works or anything. If that is the 32 GB model of the pollux_windy, this build should work fine. If it's the pollux (with LTE), then I have no intention to make builds for it, since I have no idea about the device, and I don't just post untested junk
Click to expand...
Click to collapse
I have pollux LTE and i can test when you like...
Shanliang- said:
Thanks, @pulser_g2. This is a very necessary and welcome first step towards further development.
And with official v4.2.2 on its way, things should get busier around here. :good:
Click to expand...
Click to collapse
do we have confirmation when this is?
nycbjr said:
do we have confirmation when this is?
Click to expand...
Click to collapse
In early August 4.2.2 should start rolling out, according to XperiaBlog and a tweet from SonyDevs.
Shanliang- said:
In early August 4.2.2 should start rolling out, according to XperiaBlog and a tweet from SonyDevs.
Click to expand...
Click to collapse
thanks we need that update to get working gps on wifi only tabs (I still hate calling it pollux_windy, what a dumb name).
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
pulser_g2 said:
Since everyone always loves MOAR VERSION NUMBAH...
Android 4.3 for the Xperia Tablet Z (SGP311). With a BIG shout out to Sony Mobile for hosting their own git repository for their devices - https://github.com/sonyxperiadev/device-sony-sgp321
This is compiled from AOSP, and has nothing done beyond that. Simply added the Sony repo to Android 4.3 AOSP, and built. As per the Sony AOSP releases, this does not have functional binary parts. This is not functional for practical use.
Working:
Boots
Not Working:
Wifi
Bluetooth
In light of this not being a working build, I will not post it as a zip, but as fastboot flashable images. Unlocked bootloader only. C6603 was used to test, other models entirely at your risk (ie. don't bother).
Links:
All files needed are in
http://goo.im/devs/pulser/TabletZSGP311/4.3AOSP
and will appear there shortly (upload done, it's still propogating)
This is for the SGP311 Pollux_WINDY device - the 16 GB WiFi-Only model. Don't try it on pollux with LTE, it won't boot. Might work on 32 GB wifi only model, but not tested or sure
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
To install:
fastboot flash boot boot.img
fastboot flash system system.img
Build instructions to replicate :
Get android 4.3 sources.
Get sony tablet Z information on repositories and add to local_manifests for 4.3
Get latest v3 blobs for phone and tablet Z
Put them into vendor/sony/
Repo sync
Make
Click to expand...
Click to collapse
Hey if you want some help with porting I don't mind lending some assistance, I was going to start on a 4.3 port tonight to find the bugs and get them fixed prior to baked/cm going 4.3 (it takes some time to merge our stuff into a new aosp release)
Sorry for my ignorance but I just got my tablet Z (312)
does this work on the 312? I'm seeing that there is an lte version and 2 wifi versions. Is the only diff between the 2 wifi versions the storage size and do they typically use the same firmware?
nycbjr said:
thanks we need that update to get working gps on wifi only tabs (I still hate calling it pollux_windy, what a dumb name).
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
Hey if you want some help with porting I don't mind lending some assistance, I was going to start on a 4.3 port tonight to find the bugs and get them fixed prior to baked/cm going 4.3 (it takes some time to merge our stuff into a new aosp release)
Click to expand...
Click to collapse
Sure, I just worked off the stuff on sony's github, I need to look at getting more blobs in and fixing stuff now.
Thank you Thank you Thank you
Can't wait for MOAR
Hi All,
Did someone manage to get Wi-Fi and Bluetooth working? And GPS, if there was an issue?
Yes..if u r planning on build for yourself at least...the kernel modules weren't included in the image
Sent from my XT1053 using xda app-developers app
skiwong20 said:
Yes..if u r planning on build for yourself at least...the kernel modules weren't included in the image
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
Got it, thanks! I don't have Ubuntu, so first will look if I can find it compiled somewhere, then will try to do that myself if wont.
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
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!
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Arjunfire said:
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Click to expand...
Click to collapse
you can make
I think he asked that because he cant do this. But I think it is only a matter of time until something will be released. At least I hope so.
I want it
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
rayzen6 said:
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
Click to expand...
Click to collapse
I think there will be no drivers for Spadragon 800/801...?
Athanatos81 said:
I think there will be no drivers for Spadragon 800/801...?
Click to expand...
Click to collapse
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
I hope stil working on s5 sm g900f
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
rayzen6 said:
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
Click to expand...
Click to collapse
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
kardinal969 said:
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
Click to expand...
Click to collapse
That's what I said brother
freibergisch said:
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
Click to expand...
Click to collapse
it is possible to update drivers for gpu if you have an unlocked bootloader and are on mm aosp rom
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
chippinganimal said:
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Click to expand...
Click to collapse
They should
Paoletti said:
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
They should
Click to expand...
Click to collapse
Alright, got ubuntu installed (windows partition had a heart attack afterwards lmao) so now Ill do my best to follow that guide and see what happens i guess... Should build pretty fast since this machine has a i7 3770 and 16gb of ram and it seems the guide says 8gb of ram is fine.
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
chippinganimal said:
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
Click to expand...
Click to collapse
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Paoletti said:
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Click to expand...
Click to collapse
This is a git thing. Basically the branch name has changed. It's now in the staging branch so:
-b staging/cm-14.0
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
rayzen6 said:
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
Click to expand...
Click to collapse
We want to try that build, beta, alpha or wathever it is. We just want to try it, feel nougat in our hands, we want a download link for that build, even if it isn't stable, daily usable and public. We want that, we must have that.