hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J
reserved
@jerpelea
What about software binaries for Z Ultra? will Z1 do the job?
@jerpelea
Can you please share a bit more details about the precompiled kernel for other devices there at SonyXperiaDev's git is made from which sources?
So that by then we can compile a kernel.
I'll have a look tonight and see if there is anything I can try
I'm trying to build aosp 5 using z1 binaries from the sony dev site at the moment
blueether said:
I'll have a look tonight and see if there is anything I can try
I'm trying to build aosp 5 using z1 binaries from the sony dev site at the moment
Click to expand...
Click to collapse
you and me both but at the same time i'm following @jerpelea guide to build lollipop with new binaries
My VM takes ages to compile
blueether said:
I'll have a look tonight and see if there is anything I can try
I'm trying to build aosp 5 using z1 binaries from the sony dev site at the moment
Click to expand...
Click to collapse
I have been trying since almost one week.
Have been stuck at points i couldnt get past.
Lets hope this time something sweet comes :angel:
Many thanks jerpelea.
A device-sony-togari repository is referenced in the readme for the rhine common device tree, but It's not yet public. Can we expect this, along with togari specific binaries any time soon?
Compiling Sucessfull
Not made with lollipop binaries.
#### make completed successfully (02:10:52 (hh:mm:ss)) ####
Anyone care to try? I'm not responsable for any bricking or the cat in the house catching fire.
Saatvik Shukla said:
@jerpelea
Can you please share a bit more details about the precompiled kernel for other devices there at SonyXperiaDev's git is made from which sources?
So that by then we can compile a kernel.
Click to expand...
Click to collapse
the kernel is precompiled from the kernel repo of the sonyxperiadev git. (latest 3.5 branch should be used for compiling).
May i suggest adding "5.0" or "lollipop" to the thread title?
tsiros said:
May i suggest adding "5.0" or "lollipop" to the thread title?
Click to expand...
Click to collapse
Yeah, that would draw some extra attention. Maybe a mod can add it?
you can use honami blobs but kernel and dts have to be recompiled from unified kernel source
kernel is same unified kernel and has all configs for togari
please be patient and we will add new devices soon
br
J
Ok... building kernel right now... let's see
Sm0L said:
Compiling Sucessfull
Not made with lollipop binaries.
#### make completed successfully (02:10:52 (hh:mm:ss)) ####
Anyone care to try? I'm not responsable for any bricking or the cat in the house catching fire.
Click to expand...
Click to collapse
Sure bring it on. Still animal crulety is not fun
KalleEatingBrain said:
Sure bring it on. Still animal crulety is not fun
Click to expand...
Click to collapse
You probably should check out this thread.
updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
jerpelea said:
updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Click to expand...
Click to collapse
Thanks for the hard work. AOSP id my daily at the moment, only real bug seems to be that cores 1-3 don't go off line (it is using CM's kernel at the moment as the AOSP one had more bugs I think)
blueether said:
Thanks for the hard work. AOSP id my daily at the moment, only real bug seems to be that cores 1-3 don't go off line (it is using CM's kernel at the moment as the AOSP one had more bugs I think)
Click to expand...
Click to collapse
cm and aosp in this moment are same kernel
br
J
jerpelea said:
cm and aosp in this moment are same kernel
br
J
Click to expand...
Click to collapse
blueether said:
Thanks for the hard work. AOSP id my daily at the moment, only real bug seems to be that cores 1-3 don't go off line (it is using CM's kernel at the moment as the AOSP one had more bugs I think)
Click to expand...
Click to collapse
Cm11 kernel to be precise.
If I remember right cm12 kernel didn't boot at all.
Related
Hey guys, I'm compiling SlimKat for this device right now, and since I don't own the device, I'll need testers...so, who's interested in the fun?
pandasa123 said:
Hey guys, I'm compiling SlimKat for this device right now, and since I don't own the device, I'll need testers...so, who's interested in the fun?
Click to expand...
Click to collapse
I always like the fun....pm me
pandasa123 said:
Hey guys, I'm compiling SlimKat for this device right now, and since I don't own the device, I'll need testers...so, who's interested in the fun?
Click to expand...
Click to collapse
I am also in..let me know when ready for testing.
Kernel!?
How is it possible without xiaomi releasing the kernel source?
sivasagaru said:
How is it possible without xiaomi releasing the kernel source?
Click to expand...
Click to collapse
People have ported cm11. Use their boot.img
....i having such a difficult time with this...there are so many build errors because of the lack of cm kernel source...
pandasa123 said:
....i having such a difficult time with this...there are so many build errors because of the lack of cm kernel source...
Click to expand...
Click to collapse
Cm posts all their kernel source. Slim roms require a custom kernel. I build slim for a few devices and cm kernels seldom work so without the kernel source for the device it may not be an option.
I'm in! haha been using SlimKat on my i9100G so quite some times already
pandasa123 said:
....i having such a difficult time with this...there are so many build errors because of the lack of cm kernel source...
Click to expand...
Click to collapse
download the caf kernel sources (can't remember which tag. 3.5.2.2?), map the kernel source from the device config as usual.
then make bootimage (which will install the headers),
finally, remove the configs for source built kernel, and map the dt image and zImage
the compiling is making it further and further...hopefully it won't break
BUILD FINISHED! http://forum.xda-developers.com/xiaomi-mi-3/orig-development/rom-slimkat-t2846759
I'm pretty sure I can build OmniROM. Anyone interested in that? (High chance of it not working though)
don't worry Just do it
pandasa123 said:
I'm pretty sure I can build OmniROM. Anyone interested in that? (High chance of it not working though)
Click to expand...
Click to collapse
Did I just read Omni Rom ? 200 % up for it !! let it boot or not .. But I'll test for sure
TheDj408 said:
Did I just read Omni Rom ? 200 % up for it !! let it boot or not .. But I'll test for sure
Click to expand...
Click to collapse
Lol I'm trying to get enough money for a small server. My laptop is super full (see SIG). But I want to build omni and 2 other ROMs for the cancro.
I would advise all to read this. Action will be taken in the next few days.
http://forum.xda-developers.com/xiaomi-mi-3/orig-development/attention-devs-t2848736
zelendel said:
I would advise all to read this. Action will be taken in the next few days.
http://forum.xda-developers.com/xiaomi-mi-3/orig-development/attention-devs-t2848736
Click to expand...
Click to collapse
Ok guys, I am petitioning Xiaomi. Help me keep some development alive.
https://www.change.org/petitions/xiaomi-release-mi3-kernel-source
LET'S GO!
Hi Guys,
do you know of any updates on a CM12 port to OPX?
I am very unsatisfied with the Oxygen OS and very used (and satisfied) to CM. I cannot find any information about this...
Thanks!
I doubt anyone would put the effort into porting CM12 for the X or building 12.1 nightlies for it with CM13 on the horizon. But I'm not a dev, so I could be wrong.
I'm waiting for this too, but these are the disadvantages of getting such a young phone...
But arent the Specs very similar to other phones (minimizing the effort of porting)?
But I am no Dev as well, so I have no idea. Just thoughts
Happily, I am wrong:
Quasar said:
A CM bringup is already in the works.
Click to expand...
Click to collapse
Link
CafeKampuchia said:
Happily, I am wrong: Link
Click to expand...
Click to collapse
After CM12, 13 should be relatively easy, but that would require the kernel sources to be out soon. CM12 is with a prebuilt kernel as of now.
CafeKampuchia said:
Happily, I am wrong: Link
Click to expand...
Click to collapse
Best news today. Thanks a lot!
I didn't notice that posts...I was looking for a dedicated CM for OPX thread
I think OPX development will pick up more pace once it hits the US stores on 19th November. The phones only a week old after all
Savya said:
I think OPX development will pick up more pace once it hits the US stores on 19th November. The phones only a week old after all
Click to expand...
Click to collapse
I first thought the same thing...
But a lot of capable CM devs are from India apparently. And India sales already started
CafeKampuchia said:
I doubt anyone would put the effort into porting CM12 for the X or building 12.1 nightlies for it with CM13 on the horizon. But I'm not a dev, so I could be wrong.
Click to expand...
Click to collapse
hard to port cm13 without kernel sources
its easier to go for cm12.1 first and then focus on cm13
ckret said:
hard to port cm13 without kernel sources
its easier to go for cm12.1 first and then focus on cm13
Click to expand...
Click to collapse
I would already be happy as a clam, if CM12(.1) would be successfully ported
Props to the AOSParadox effort guys, nice job
Hope to see a thread soon :fingers-crossed:
https://github.com/h2o64/android_device_oneplus_onyx/commits/cm-12.1
eng.stk said:
Props to the AOSParadox effort guys, nice job
Hope to see a thread soon :fingers-crossed:
https://github.com/h2o64/android_device_oneplus_onyx/commits/cm-12.1
Click to expand...
Click to collapse
Looks Promising
eng.stk said:
Props to the AOSParadox effort guys, nice job
Hope to see a thread soon :fingers-crossed:
https://github.com/h2o64/android_device_oneplus_onyx/commits/cm-12.1
Click to expand...
Click to collapse
I Don't Know What Are Those ,, But It Bought Smile ON My Face ... Lol
gaurav247star said:
I Don't Know What Are Those ,, But It Bought Smile ON My Face ... Lol
Click to expand...
Click to collapse
Device tree and proprietary blobs are needed to build custom ROMs.
It's using stock kernel since we do not have source yet
eng.stk said:
Device tree and proprietary blobs are needed to build custom ROMs.
It's using stock kernel since we do not have source yet
Click to expand...
Click to collapse
And here, we have a tease.
EDIT: LOL I'm not kanging from h2o64. We work on the same team (matching signatures....?).
Quasar said:
And here, we have a tease.
Click to expand...
Click to collapse
Oh yeah!
eng.stk said:
Props to the AOSParadox effort guys, nice job
Hope to see a thread soon :fingers-crossed:
https://github.com/h2o64/android_device_oneplus_onyx/commits/cm-12.1
Click to expand...
Click to collapse
Quiet a surprising device actually ... They backported MSM8994 stuff on MSM8974. Don't know how that will end up.
Here's my TO-DO list if you are curious
Code:
TO DO :
- adjust firmware symlinks
- update init
- cleanup ramdisk
- custom liblight
- finish overlay
Would be nice if a lot of people could get me
Code:
getprop > getprop.txt
it will help for multinational radio
eng.stk said:
Device tree and proprietary blobs are needed to build custom ROMs.
It's using stock kernel since we do not have source yet
Click to expand...
Click to collapse
Hello!
I assume you're here to give us the best kernel for our device?
h2o64 said:
Would be nice if a lot of people could get me
Code:
getprop > getprop.txt
it will help for multinational radio
Click to expand...
Click to collapse
Here's mine...
Hello guys . I'm a dev from bacon , and i'm interested on expanding my work to other devices. Already have a couple of test roms ready but need testers to see if i have the correct blobs as also the correct kernel and device tree. IF you are free please let me know
Might you be working on the "blu pure xl" by any chance?
jgcaap said:
Hello guys . I'm a dev from bacon , and i'm interested on expanding my work to other devices. Already have a couple of test roms ready but need testers to see if i have the correct blobs as also the correct kernel and device tree. IF you are free please let me know
Click to expand...
Click to collapse
Shoot something out for testing, results will come flocking in.
Sent from my Nexus 6P using Tapatalk
Alright. I'm just not sure if I set the correct blobs and kernel. Results are harmless worst thing is not booting. If that happens please flash a kernel of your choice and let me know the thread.
http://download.jgcaap.xyz/files/angler/cm-13.0/
If is not that is the device tree. But I think should work. After looking to the sources they seem to be all the same.
It's a bit big because is odexed.
Ill be adding more functionalities soon.
Thanks.
jgcaap said:
Alright. I'm just not sure if I set the correct blobs and kernel. Results are harmless worst thing is not booting. If that happens please flash a kernel of your choice and let me know the thread.
http://download.jgcaap.xyz/files/angler/cm-13.0/
If is not that is the device tree. But I think should work. After looking to the sources they seem to be all the same.
It's a bit big because is odexed.
Ill be adding more functionalities soon.
Thanks.
Click to expand...
Click to collapse
Will try and give this a whirl when I get home. Any changes from CM 13 sources? Are you using your custom toolchain, etc? Thanks!
jgcaap said:
Hello guys . I'm a dev from bacon , and i'm interested on expanding my work to other devices. Already have a couple of test roms ready but need testers to see if i have the correct blobs as also the correct kernel and device tree. IF you are free please let me know
Click to expand...
Click to collapse
Free and available @galaxy s4 nutjob downloading now will report back,
Fired up and working great, flashed as is booted extremely quick. Nice job
http://imgur.com/y3liwJp
Booted up fine. Seems smooth with very little bloat. Great work.
thanks
jgcaap said:
thanks
Click to expand...
Click to collapse
Any details on what the rom is based on and what theme engine?
jgcaap said:
thanks
Click to expand...
Click to collapse
Just FYI I think your kernel may have force encryption enabled but I'm not entirely sure. It may have just been me messing with the settings.
android4life92 said:
Any details on what the rom is based on and what theme engine?
Click to expand...
Click to collapse
Screenshot says CM13 version..
Is kernel force encryption?
Sent from my Nexus 6P using Tapatalk
bigdave79 said:
Will try and give this a whirl when I get home. Any changes from CM 13 sources? Are you using your custom toolchain, etc? Thanks!
Click to expand...
Click to collapse
many many changes! only left untouched kernel and device tree
Ok, first i had done this for cm13, let's see what I can do for AOSP! Lulz. Think my earlier thread for cm13 created too much of hype and development restarted (joy++)
So, First of all, i haven't built AOSP as of yet for op2, will do it. If anyone can get the recovery working, or any progress, report here.
If we have AOSP caf tree, we will be able to port UBUNTU TOUCH, and many other ROMs based of aosp directly.
So here we go!
regalstreak said:
Ok, first i had done this for cm13, let's see what I can do for AOSP! Lulz. Think my earlier thread for cm13 created too much of hype and development restarted (joy++)
So, First of all, i haven't built AOSP as of yet for op2, will do it. If anyone can get the recovery working, or any progress, report here.
If we have AOSP caf tree, we will be able to port UBUNTU TOUCH, and many other ROMs based of aosp directly.
So here we go!
Click to expand...
Click to collapse
If I can help you in any way, let me know mate, will be a pleasure !
I don't have much experience with AOSP source code but I would help you as good as possible.
If you give me some instructions or ask some questions I could help you out a bit, just let me know!
xdvs23 said:
I don't have much experience with AOSP source code but I would help you as good as possible.
If you give me some instructions or ask some questions I could help you out a bit, just let me know!
Click to expand...
Click to collapse
casual_kikoo said:
If I can help you in any way, let me know mate, will be a pleasure !
Click to expand...
Click to collapse
Umm, the problem is that, that there is no guide for editing the cm source to make it run aosp, nevertheless we will make it boot no probs. Logcat will help. @k2wl you had a semibooting caf build or something?
Sent from my ONE A2003 using Tapatalk
regalstreak said:
Umm, the problem is that, that there is no guide for editing the cm source to make it run aosp, nevertheless we will make it boot no probs. Logcat will help. @k2wl you had a semibooting caf build or something?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Maybe we can try this method : http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code ?
Edit: forgot there is no source code for OOS. Shame on me.
@regalstreak i've wrote to you on telegram, check this out
@regalstreak you can't have a caf free build since kernel and blobs of oneplus2 (oxygenos and hydrogenos) are based on caf
regalstreak said:
Ok, first i had done this for cm13, let's see what I can do for AOSP! Lulz. Think my earlier thread for cm13 created too much of hype and development restarted (joy++)
So, First of all, i haven't built AOSP as of yet for op2, will do it. If anyone can get the recovery working, or any progress, report here.
If we have AOSP caf tree, we will be able to port UBUNTU TOUCH, and many other ROMs based of aosp directly.
So here we go!
Click to expand...
Click to collapse
Dude I have no idea on how to do it, but I actually started looking in it. I installed Ubuntu on my computer and downloaded the software but I don't know how to start it
manups4e said:
@regalstreak you can't have a caf free build since kernel and blobs of oneplus2 (oxygenos and hydrogenos) are based on caf
Click to expand...
Click to collapse
So cant we do any thing to compile aosp? We will try atleast
Sent from my ONE A2003 using Tapatalk
regalstreak said:
So cant we do any thing to compile aosp? We will try atleast
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
sure of course you can i already did it while cyanogenmod 13 was not yet booting.. the only thing is that you will have to modify tons of things into the device tree and tons of things into the aosp code to make hardware to work.. the only things that will work without modifications will be wifi and bluetooth.. maybe audio too but i'm not sure about that
regalstreak said:
Umm, the problem is that, that there is no guide for editing the cm source to make it run aosp, nevertheless we will make it boot no probs. Logcat will help. @k2wl you had a semibooting caf build or something?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I have some experience with git (because I am developing a browser which is on github) and I can download and edit sources, but I am a very beginner in C/C++ so don't expect me to do much, but I can try to help you anyways if possible.
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
AndroidBeginNinja said:
Dude I have no idea on how to do it, but I actually started looking in it. I installed Ubuntu on my computer and downloaded the software but I don't know how to start it
Click to expand...
Click to collapse
AFAIK First of all you need to install JDK, a toolchain, git etc. and then you can clone the repos and start modifying them and compile them using breakfast and lunch or similar.
Guys keep calm! I have an alpha ROM based on CAF/AOSP that is booting, something is broken, but I will share sources with regal and we will try to make it stable
WaxLarry said:
Guys keep calm! I have an alpha ROM based on CAF/AOSP that is booting, something is broken, but I will share sources with regal and we will try to make it stable
Click to expand...
Click to collapse
Finally, i was trying to compile omni rom but kept getting errors. It was too much work. Way beyond my capabilities and even if i tried it would have taken me months to even make any sort of build. Bootable was not even in the equation. So i dropped it.
Will definitely try to compile omni again once we have AOSP build.
WaxLarry said:
Guys keep calm! I have an alpha ROM based on CAF/AOSP that is booting, something is broken, but I will share sources with regal and we will try to make it stable
Click to expand...
Click to collapse
Thanks for your effort, remember to add Paypal donation button.. :highfive:
Maxximo88 said:
Thanks for your effort, remember to add Paypal donation button.. :highfive:
Click to expand...
Click to collapse
Off course, when we have something ready to be released :highfive:
---------- Post added at 10:14 AM ---------- Previous post was at 10:12 AM ----------
Kapiljhajhria said:
Finally, i was trying to compile omni rom but kept getting errors. It was too much work. Way beyond my capabilities and even if i tried it would have taken me months to even make any sort of build. Bootable was not even in the equation. So i dropped it.
Will definitely try to compile omni again once we have AOSP build.
Click to expand...
Click to collapse
I know, is an huge work, I've spent a lot of time on this to get it compile and boot
This seems to be based on AOSP CAF, and Exodus 6.0 OP2 is also AOSP based.
Guys tipsy os , broken os , vanir ROM these Roms are based on aosp Right,
All of these Roms are there for oneplus 2
Not a Dev of any kind , just ignore if the info is of no use
#noob_who_wanted_2_help
Cheers and best of luck guys
Edit
Vanir Roms -Team Vanir
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/oneplus2/
Broken Os build by Naman Bhalla
Tipsy OS- martinsube
Yes right, you can ask tipsy devs for help
Thanks brother. I wanted a pure AOSP. Even I created a request thread and u did it.
Many thanks for your continued efforts @regalstreak, I look forward to seeing and using the end product!
Sent from my ONE A2001 using Tapatalk
Does someone wants to help me making an AOSP device tree?
Would bring some more roms to our device
I already started with a branch and commented out some compiling errors:
https://github.com/benschhold/android_device_oneplus_oneplus2/tree/aosp
Any help is appreciated.
@regalstreak
maybe something for you if you are interested
benschhold said:
@regalstreak
maybe something for you if you are interested
Click to expand...
Click to collapse
The problem is the kernel source. Ain't it? We need to rebegin from the plain linux kernel src imo idk
regalstreak
regalstreak said:
The problem is the kernel source. Ain't it? We need to rebegin from the plain linux kernel src imo idk
regalstreak
Click to expand...
Click to collapse
angler custom kernel work on both cm/aosp so i didnt thought about that
and isnt oxygen stock kernel aosp + oneplus patches? maybe we could start from there
benschhold said:
angler custom kernel work on both cm/aosp so i didnt thought about that
and isnt oxygen stock kernel aosp + oneplus patches? maybe we could start from there
Click to expand...
Click to collapse
Oxygen is based on caf so it is difficult. But not impossible. Did you build tho? We can get it booting easily. But ril and some stuff womt work.
regalstreak
regalstreak said:
Oxygen is based on caf so it is difficult. But not impossible. Did you build tho? We can get it booting easily. But ril and some stuff womt work.
regalstreak
Click to expand...
Click to collapse
im currently stuck at busybox error which i couldnt solve but not sure if its device related, tried on screwd rom and that have a lot of optimizations which cought caused that
i have to try again on another aosp source
benschhold said:
im currently stuck at busybox error which i couldnt solve but not sure if its device related, tried on screwd rom and that have a lot of optimizations which cought caused that
i have to try again on another aosp source
Click to expand...
Click to collapse
Make pure aosp source. And clone busybox from cm if its still not fixed. Its not a device error.
regalstreak said:
Make pure aosp source. And clone busybox from cm if its still not fixed. Its not a device error.
Click to expand...
Click to collapse
yep, im syncing
will try cm busybox if errer persists
benschhold said:
yep, im syncing
will try cm busybox if errer persists
Click to expand...
Click to collapse
screwd rom woo my fav rom !!
Sent from my ONE A2003 using XDA-Developers mobile app
does someone know where to define where kernel source is stored?
the typical TARGET_KERNEL_SOURCE is not working
when to try to build inline its always looking in out/ folder
Man, wish I could help but lack the skills.. Plenty of Linux machines on hand though.. Where do I start?
@benschhold, @King_lilrowrow wrote on his Twitter acc about 20 days ago he built NX Rom using only AOSP code. Doesn't that mean he had to make an AOSP tree? I would ask him for help
MaxtremePL said:
@benschhold, @King_lilrowrow wrote on his Twitter acc about 20 days ago he built NX Rom using only AOSP code. Doesn't that mean he had to make an AOSP tree? I would ask him for help
Click to expand...
Click to collapse
Trees or it didn't happen!
builds are going through compiling now
but are not booting
lets see
benschhold said:
builds are going through compiling now
but are not booting
lets see
Click to expand...
Click to collapse
Take your time [emoji1] [emoji7]. Can't wait. I have always loved pure AOSP
Sent from my ONE A2003 using Tapatalk
benschhold said:
builds are going through compiling now
but are not booting
lets see
Click to expand...
Click to collapse
Post some logcat, maybe we can help
WaxLarry said:
Post some logcat, maybe we can help
Click to expand...
Click to collapse
as far as i now its not possible to take one when not passing oneplus logo
i just compile another one and lets hope for the best :fingers-crossed:
i've already built aosp for lg g3.. i'm downloading right now n-preview2 sources i will help, i'll let you know once i will have everything ready
benschhold said:
as far as i now its not possible to take one when not passing oneplus logo
i just compile another one and lets hope for the best :fingers-crossed:
Click to expand...
Click to collapse
The problem is the kernel, i've already had this kind of problem.
Are you compiling your own kernel? If yes, which sources?
Basically in lollipop the kernel is compiled uncompressed with appended dtb, since MM, kernel is compressed and dtb is included in kernel.
WaxLarry said:
The problem is the kernel, i've already had this kind of problem.
Are you compiling your own kernel? If yes, which sources?
Basically in lollipop the kernel is compiled uncompressed with appended dtb, since MM, kernel is compressed and dtb is included in kernel.
Click to expand...
Click to collapse
no i went back to screwd cause aosp just wont find my kernel source
i fckd it up elsewhere
there is a solution for this. set in your baord config like this
Code:
BOARD_CUSTOM_BOOTIMG_MK := device/oneplus/oneplus2/mkbootimg.mk
and take the file from cm for example