Seing android n just got out, would be able to port it to our device? Using cm13, as base rom? And what about sailfish os?
It would be interesting, but I don't thing someone will do this, its a preview.
Enviado desde mi ONE A2005 mediante Tapatalk
No source code till like June-July and we don't even have an vanilla AOSP build yet to even act as a base for some Frankenstein action.
Sent from my ONE A2003 using Tapatalk
I'm waiting for miui. Android N won't be available to anything else than nexus before source release.
Men, CM 13 just came out with all features supported (LAF/Fingerprint) and you already ask for something new. Come on, please.
I think that the priority now should be get a stable cyanogenmod 13.
casual_kikoo said:
Men, CM 13 just came out with all features supported (LAF/Fingerprint) and you already ask for something new. Come on, please.
Click to expand...
Click to collapse
Not asking for it. Asking if possible, cause then i would look into it.
rascal0pl said:
I'm waiting for miui. Android N won't be available to anything else than nexus before source release.
Click to expand...
Click to collapse
override182 said:
No source code till like June-July and we don't even have an vanilla AOSP build yet to even act as a base for some Frankenstein action.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Migdilu said:
It would be interesting, but I don't thing someone will do this, its a preview.
Enviado desde mi ONE A2005 mediante Tapatalk
Click to expand...
Click to collapse
Well turns out, someone is porting it!
theonlykamph said:
Well turns out, someone is porting it!
Click to expand...
Click to collapse
It would be better to port vanilla M and prepare an AOSP tree. From there collaborations can happen to speed it up and make our device even future proof and next can be enhanced to further builds of android. Having a bootable vanilla M will grant a working ramdisk and such instead of Frankenstein build which is hard to be a daily driver
Sent from my ONE A2003 using Tapatalk
override182 said:
It would be better to port vanilla M and prepare an AOSP tree. From there collaborations can happen to speed it up and make our device even future proof and next can be enhanced to further builds of android. Having a bootable vanilla M will grant a working ramdisk and such instead of Frankenstein build which is hard to be a daily driver
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Yes, and also more devlopment to Oneplus 2 please!
For your kind information guys, android n preview 1 source code is out. Check it out - https://android.googlesource.com/platform/manifest/+/android-n-preview-1 .
You can sync it using the repo tool, repo init -u https://android.googlesource.com/platform/manifest -b android-n-preview-1 .
Good luck.
If anybody downloads it please let me know ?.
Related
Hey guys,
I've set up an organization on github und uploaded my config there.
Could you please provide me your github usernames via PN so I can add you to the team?
Thanks,
Daniel
Doublepranks. But I just wanna join for learning if you would let me in....
Sent from my XT1033 using Tapatalk
swordrune10, don't have a moto g yet but most likely getting one for xmas
Sent from my Galaxy Nexus using Tapatalk
Josalaito, i'm working in cm 10.2 now, and i think we need a hard work because msm8x26 is not fully supported by cyanogen and we need to use 8960(The same happened in my old y300 cm doesnt support 8x25 and we use msm7x27a)
Hi, my username is debaj, I hope I can help anything as a geneal Android developer since I have no experience in ROM development except building Cyanogenmod for my old Nexus S
My Username on github is: denizkoekden
Regards,
Deniz
Still don't have a Moto G but wanna buy one for christmas...
My username on GitHub is: Lopicl
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
immortal_yash said:
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
Click to expand...
Click to collapse
I think it's best to begin with msm8226 from the outset rather than trying to kang a different board
I'm seapoint on Git by the way. https://github.com/seapoint
My Moto G arrives Tomorrow
too bad I won't have time to do anything
I am Scrizz on github
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8926 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
7alvi reporting for call of booty..jk
Count me in. Will be getting mine by January (most likely) and for my work I have built Carbon, Mokee, Slim, AOKP, baked, anir, etc etc for HTC Pico..!
kaliberx said:
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8626 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
Click to expand...
Click to collapse
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
immortal_yash said:
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
Click to expand...
Click to collapse
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
kaliberx said:
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
Click to expand...
Click to collapse
try using mine or alpha or any pre started device tree willl save you some time
BTW any knows which audio blob is being used in Motog?
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
a1Pha said:
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
don't worry, I got u
Sent from my Nexus 7 using Tapatalk
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Lopicl.00 said:
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Click to expand...
Click to collapse
we really do need a kernel tree and if someone could pull the prop files that would be great
Sent from my Nexus 7 using Tapatalk
If you want, you can fork my kernel project.
Note, this is for the LTE model, GT-I9195. I compiled a build for someone who posted a request for it on RR Google+ site. I don't own the device, but it works OK according to him.
https://plus.google.com/112662517583200054973/posts/GfBf1Swvh1D
I have the Mega 6.3 which is similar in hardware to the mini.
The download link & md5 is given below. If users can confirm that it works OK, I can create a thread in the development forum.
https://mega.co.nz/#!cgdEmKYI!FFrOm2Gpu8UliMdUbKYUdz8YxOkMRjabPUdflRQIeXU
MD5 : feb05eaff29173c8245af54c78eaf341
Sent from my GT_I9205 using Tapatalk
i downloaded it, now i'm copying the zip to the phone..
EDIT: Working! Open the thread, it's the best rom for the s4 mini!
Is this the whole rom? Found this link and it looks amazing
http://forum.xda-developers.com/gal...m-gt-i9100-resurrection-remix-v4-0-7-t1436854
OK. Will create a thread in a couple of hours.
Sent from my GT_I9205 using Tapatalk
charliebigpot said:
Is this the whole rom? Found this link and it looks amazing
http://forum.xda-developers.com/gal...m-gt-i9100-resurrection-remix-v4-0-7-t1436854
Click to expand...
Click to collapse
Yup. That's the one.
Sent from my GT_I9205 using Tapatalk
Silesh.Nair said:
Yup. That's the one.
Sent from my GT_I9205 using Tapatalk
Click to expand...
Click to collapse
The only problem that i encountered is that there are some little lags in the ui, and when the screen is off after many time, whatsapp answers doesn't arrives
Rom looks good, will try it soon. Do you plan on providing updates to the rom?
Sent from my GT-I9195 using Tapatalk
spanish33 said:
Rom looks good, will try it soon. Do you plan on providing updates to the rom?
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
Yes, I do.
Thread created...
http://forum.xda-developers.com/showthread.php?p=52119212
Just want to say thanks for this its is the best ROM out of them all as i have tried them all for the S4 mini, One bug i hate on 4.4 is opening a message notification and it remaining there but i don't seem to have this problem on your ROM, I found the boot logo to be a tad to big but that's the only problem i have with it so far please support S4 Mini.
Is there a AOKP build for serranolte/serrano3g?
Oooo!!! I love AOKP builds...jeje
Enviado desde mi GT-P7510 mediante Tapatalk
kioshio said:
Oooo!!! I love AOKP builds...jeje
Enviado desde mi GT-P7510 mediante Tapatalk
Click to expand...
Click to collapse
I'll send you the build tomorrow morning. Gonna sleep now. Test and let me know.
A lot of thanks for your work!!!!
Enviado desde mi GT-P7510 mediante Tapatalk
I always wanted PA on my phone now I've got it. Couldn't ask for anything more just waiting for the rest of the features to be added by PA.
Glad you are here with us!!! :good:
You got official PA
FYI...
Serranolte and Serrano3g have been added to aospa-legacy, meaning you will be getting official builds from now on and can use the OTA app to update.
https://github.com/AOSPA-legacy/android_vendor_pa/commit/99120361c36189be4170e202b2adfe9657671158
Downloads will be available at this link when they are ready. Serranoltexx and Serrano3gxx folders would show up when the build is ready.
Hey dude. I'm not sure if you got my PM, UC Browser does funny stuff sometimes so I will post this here.
Just woke up a couple of hours ago. Testing AOKP now, everything seems to be working fine. At first it appeared that Bluetooth didn't work. After a reboot and installing gapps it seemed to be working. Not sure if that was due to gapps or just the reboot. Other then that everything seems to be fine.
P.S. I also tried Mahdi, excellent ROM, can confirm Bluetooth is not working there either, plus the gallery app crashed from the get go until a reboot
Pure AOSP gives issues sometimes. Will take a look when I update. Thanks for testing. I'll create a new thread when I get feedback for the LTE version.
Sent from my GT-I9205 using Tapatalk
Silesh.Nair said:
Pure AOSP gives issues sometimes. Will take a look when I update. Thanks for testing. I'll create a new thread when I get feedback for the LTE version.
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Testing akop now everything seems OK so far apart from network says 23415 not Vodafone.
Sent from my unknown using Tapatalk
Silesh.Nair said:
Pure AOSP gives issues sometimes. Will take a look when I update. Thanks for testing. I'll create a new thread when I get feedback for the LTE version.
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
ha ?! strange ...
Pure AOSP (like Nexus roms ) are généraly more stable than CM roms ..."in théory" .
And it will be perfect for users who want the simplicity on parameters, a pure google experience (like stock ) ...and a good "clean" base ( without "frills" ) for eventualy to personalize oneself for some people .
And for some people who like Touchwiz :add very goods Samsung Touchwiz theme + launcher will be great ! ==> it fully replace stock rom!
It's sure that when stock KK will be released for S4 mini by Samsung, with the code-source ( scheduled in May 2014...according to the "good" rumors enought reliable ) ==> a pure AOSP build will be the best choise for our phone ( lighten,performance and stability ) ....with a very good Customised Kernel for better phone ( a strong battery save ,without decreasing performance )
As far as i'm concerned ,i personaly wait this way for the future of my phone !
Otherwise ,there are stable CM11 ... but cyanogenmod have done many additional features on her rom .
Android 6.0 is being uploaded to AOSP:
http://www.androidpolice.com/2015/10/05/android-6-0-marshmallow-is-being-uploaded-to-aosp-right-now/
@Alberto97
@Flashhhh
What do you think ? it will be difficult to port it over ?
Too early to say.
I hope I can find some custom rom after Android 6.0 release.....
The 2nd gen moto g is being updated via motorola to 6.0, the first and second gen motos are pretty much similar in every aspect part screen size and camera. Roms have been ported over from the 2nd gen to the 1st gen before so it maybe done again for 6.0.
Lets hope for the best...
CM13 branch is created, also with falcon device tree repo (https://github.com/CyanogenMod/android_device_motorola_falcon/tree/cm-13.0)
TheXorg said:
CM13 branch is created, also with falcon device tree repo (https://github.com/CyanogenMod/android_device_motorola_falcon/tree/cm-13.0)
Click to expand...
Click to collapse
ok, then how long it will take till we got a build of Android 6.0 ?
Eurofighter_ty said:
ok, then how long it will take till we got a build of Android 6.0 ?
Click to expand...
Click to collapse
i'm currently syncing it, althrough i dont think it compiles ^^
TheXorg said:
i'm currently syncing it, althrough i dont think it compiles ^^
Click to expand...
Click to collapse
I don't have any knowledge about building Android. But I have 2 questions:
Why the compile can fail ? There are no drivers ?
If compiles then we need to see if it's boots and if at least 2-3 things are working. like wifi, or something like that. I am just interested.
Eurofighter_ty said:
Why the compile can fail ? There are no drivers ?
Click to expand...
Click to collapse
Millions of lines of code -> millions of possible reasons for failure.
Also, the closed source libraries (lib/hw/* and vendor/lib/*) could be incompatible and workarounds may need to be found and implemented.
_that said:
Millions of lines of code -> millions of possible reasons for failure.
Also, the closed source libraries (lib/hw/* and vendor/lib/*) could be incompatible and workarounds may need to be found and implemented.
Click to expand...
Click to collapse
If you compile it and it works then post it
This could take weeks or even months, not a few hours.
If anyone needs beta test I am available and only send a private message
Eurofighter_ty said:
I don't have any knowledge about building Android. But I have 2 questions:
Why the compile can fail ? There are no drivers ?
If compiles then we need to see if it's boots and if at least 2-3 things are working. like wifi, or something like that. I am just interested.
Click to expand...
Click to collapse
first, the downloaded sourcecode was only about 2gb (normal AOSP sourcecode is more than 20gb)
then, they are still updating many repos, you can watch them update https://github.com/CyanogenMod
TheXorg said:
first, the downloaded sourcecode was only about 2gb (normal AOSP sourcecode is more than 20gb)
then, they are still updating many repos, you can watch them update https://github.com/CyanogenMod
Click to expand...
Click to collapse
ok so then we have to wait at least 1-2 weeks to get Android 6.0 on our device...
Avoid the impatients
Lets avoid asking for builds and ETAs please, remember that devs have jobs or study to do, and sometimes being bothered about when they will release something could annoy them.
Rule 4
I'd be open for testing any kind of builds in the future, although I have the xt1031 boost variant but that might help out too for certain things
So our Moto G 2013 will receive the Android 6.0 with CyanogenMod 13 ?
Enviado de meu Moto G usando Tapatalk
xxmarsubxx said:
So our Moto G 2013 will receive the Android 6.0 with CyanogenMod 13 ?
Enviado de meu Moto G usando Tapatalk
Click to expand...
Click to collapse
for sure.
Any updates??
Anyone have any latest news regarding status of falcon in cm13?? As moto g2 already got a test build of cm13
Why is that most of the custom ROMs other then based on OxygenOS does not have working Fingerprint and Laser Autofocus?
Sent from my ONE A2003 using Tapatalk
subbathegim said:
Why is that most of the custom ROMs other then based on OxygenOS does not have working Fingerprint and Laser Autofocus?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Because OnePlus has not supplied the drivers and source to utilize them. They promised they would with the marshmallow oos build so you can expect working cm roms shortly after that
Probably because the source code is to ugly to release for the Lollipop source tree ? best way to hide poor coding, don't show it to anyone ?
wtoj34 said:
Because OnePlus has not supplied the drivers and source to utilize them. They promised they would with the marshmallow oos build so you can expect working cm roms shortly after that
Click to expand...
Click to collapse
Source or they only promise to stick to mm fp api afaik?
y7038862 said:
Source or they only promise to stick to mm fp api afaik?
Click to expand...
Click to collapse
Check out @getpeid's Tweet: https://twitter.com/getpeid/status/661133323561926656?s=09
And another thing..
Check out @getpeid's Tweet: https://twitter.com/getpeid/status/682143021287133184?s=09
Sent from my ONE A2005 using Tapatalk
pitrus- said:
Probably because the source code is to ugly to release for the Lollipop source tree best way to hide poor coding, don't show it to anyone
Click to expand...
Click to collapse
true story :fingers-crossed:
Will someone port Android N beta from Nexus 6P to our OnePlus Two? :laugh:
We still don't have Official stable Marshmallow so it's imposible to have it now and wait that the stable N comes that Cyanogen Team work for CyanogenMod 14, too bad we don't have CyanogenOS on our OnePlus 2 #LuckyOPOuser
Just wait for stable n out, porting a preview is just a waste of time, when source is release someone will do
Sent from my ONE A2005 using Tapatalk
There isn't even N source code.
Seraph08 said:
There isn't even N source code.
Click to expand...
Click to collapse
The source code is already available
Here you can see
'Branches and Tags are different.'
regalstreak
Okey :/