Related
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.
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
First thanks o.o
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Brawn_Sg said:
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Click to expand...
Click to collapse
Philz doesn't support --block flashing or the new method of flashing LP.our twrp has not properly implemented fstab for installation and I'm not able to make twrp with new fstab in cm-12.0 tree as it is throwing a lot of error messages and I currently don't have any kitkat based ROM tree due to my computer corruption few days ago.
I will be trying a clean build 2day.
ashwin007 said:
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
Click to expand...
Click to collapse
Which version of cwm recovery is in the build?
gud work
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
goutamniwas said:
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
Click to expand...
Click to collapse
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
EDIT:Well @ace312 its no more cwm in cm tree.its cyanogen recovery made by cm
ashwin007 said:
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
Click to expand...
Click to collapse
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
goutamniwas said:
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
Click to expand...
Click to collapse
nevermind.i think i made a dirty build by replacing cmr with twrp without mka clean.so rebuilding now.hopefully it'll work.
Hey,
Why don't you flash system.img and boot.img with fastboot?
ace312 said:
Which version of cwm recovery is in the build?
Click to expand...
Click to collapse
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
GeekyDroid said:
Hey,
Why don't you flash system.img and boot.img with fastboot?
Click to expand...
Click to collapse
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
okay. it's been months I left ROM development. Sorry about that.
ashwin007 said:
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
Click to expand...
Click to collapse
Well, sorry I thought it is less than 215MB. I didn't think of it.
My last device was a motorola defy and developer @Quarx has a booting 5.0 lolipop build. perhaps he could enlighten us on how to make a booting build for out device.
Moto defy came with android 2.1 and kernel 2.6 so he should be able to help.
Now even moto e has received the "motorola update services app" update!! So maybe we are pretty close enough to get android L now!!! I think rather than rushing up things for condor cm12 and getting a buggy build after soo much hardwork wouldn't feel good!! Maybe we can wait a while for the android L to hit moto e ans then finally build cm12 which would be more stable too!!
•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•
see the attachment...
Lolipop is more closer...
This is a development thread.Refrain from posting those monotonous posts.I would like to keep this thread clean.
http://www.stjsgadgets-portal.com/2015/02/moto-e-users-start-getting-lollipop.html?m=1
I've received several reports for this thread in the past 2 days, so now it's time to issue a global warning here:
Let's keep this thread on topic, DEVELOPMENT, which is clearly stated in the title AND in the OP.
If you have a question, SEARCH FIRST, per the Forum Rules
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
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.
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921