thought id share this with you guys
https://www.youtube.com/watch?v=wJYXx3J-AWc
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Sent from my XT1254 using XDA Labs
I would expect it to arrive in March, probably with some bugs.
jeffkahlo777 said:
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Click to expand...
Click to collapse
It will take @bhb27 coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@bhb27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @bhb27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @bhb27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @bhb27 did the work to let Nougat ROMs use that kernel.
Will be the same thing with Oreo. But @bhb27 still has to code it to work smoothly with Oreo.
Also, there is no more CM. We now have LOS as the "base". @bhb27 does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @bhb27 will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)
@bhb27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.
The kernel will be the foundation of any Oreo ROMs and it will all depend on @bhb27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @bhb27 is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.
ceelos218 said:
thought id share this with you guys
https://www.youtube.com/watch?v=wJYXx3J-AWc
Click to expand...
Click to collapse
I going have to check with my local church about that, I may not be able to work on Oreo....
how comes up with those videos
https://www.youtube.com/watch?v=twZggnNbFqo
bhb27 said:
how comes up with those videos
https://www.youtube.com/watch?v=twZggnNbFqo
Click to expand...
Click to collapse
first, technically a cross in general and period is sun god worship in itself. so if your church doesn't have any issues with a cross i don't see why it would care about a double cross.
second, that double cross is just on the oreo. it is the nabisco symbol. so if it is evil so is nabisco
I agree with you though where do people come up with this stuff
Safer, smarter, more powerful! All with the Movie trailers voice. Coming this fall*
*TBD
ready to provide support!
bhb27 said:
I going have to check with my local church about that, I may not be able to work on Oreo....
Click to expand...
Click to collapse
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
I got impatient and I tried to build LOS 15 using the existing kernel. It didn't work (because of course it didn't).
GeekyTanuj said:
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
Click to expand...
Click to collapse
you need to search on how is done what you wanna to do, simple things as build a ROM there is plenty of tutorial, kernel not so many but there is tutorial + my how to on kernel tread helps you to understand how I do build a kernel (of course is needed basic shell and/or kernel Knowledge, those are available is searches) or the readme in the device tree can explain the basic, I do this for years this is not a thing I learn over night took me years to now a little thing, some times took me weeks to do a very simple thing to work the things is if you wanna don't ever give it up, rest and try again later but don't just give it up, so you search about, like I wrote there is dedicated xda thread on how to build tihngs, you find those and post yours problems there, if is a quark specific help, open yours on general help thread and post the specific problem you have, but really search before you post anything somethings are simple like I wrote is just a question of patiently read and do exactly hat the tutorial says.
TheSt33v said:
I got impatient and I tried to build LOS 15 using the existing kernel. It didn't work (because of course it didn't).
Click to expand...
Click to collapse
source is not ready yet for any device, even after it may not be ready for quark for some time... + kernel, device and vendor changes are needed...
GeekyTanuj said:
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
Click to expand...
Click to collapse
Well I've looked in the same way of you and now I've made it (twice actually (AEX and ViperOS)). Everything that I learned it was just searching here in XDA, taking a look on some videos at YouTube and Google it. But we can't forget the stuff necessary, like a strong computer with Linux (any distro it's fine) or Google Cloud, and, of course, a good internet and patience.
Just building it's simple when you look for the "real" development (working in kernels, device trees, and vendors)
[EDIT]Have a bunch of good ROMs to build. Try look for someone that you liked.
It feels like I'm getting really close, but I didn't get to test to see if it boots . Hopefully I can get it to recognize the device, install, then boot! If I get something stable then I will share it soon.
...
Hey @bhb27. Sorry to bug you, but quick question. I got the kernel to compile (and ROM) but I still get the unfound device (error 7 in TWRP). If I bypass and flash it anyhow, I see my boot logo, then it just keeps resetting back to the bootloader.
I'm sure I've just configured something incorrectly in the kernel, but do you have any suggestion on how I could trace it? It almost makes me think it's not even finding the image. I've only seen methods involving a custom ttl terminal board when I Google it (other than trying to edit the kernel command line using fastboot). Don't want to take up your time but just curious if you had any idea. I'm betting it will just require your knowledge at a later time (since sources aren't ready other than my modifications).
Thanks again.
calsurferpunk said:
Hey @bhb27. Sorry to bug you, but quick question. I got the kernel to compile (and ROM) but I still get the unfound device (error 7 in TWRP). If I bypass and flash it anyhow, I see my boot logo, then it just keeps resetting back to the bootloader.
I'm sure I've just configured something incorrectly in the kernel, but do you have any suggestion on how I could trace it? It almost makes me think it's not even finding the image. I've only seen methods involving a custom ttl terminal board when I Google it (other than trying to edit the kernel command line using fastboot). Don't want to take up your time but just curious if you had any idea. I'm betting it will just require your knowledge at a later time (since sources aren't ready other than my modifications).
Thanks again.
Click to expand...
Click to collapse
you need to update the kernel to boot O, there is a lot of changes to it, like I wrote before shamu and victara must have the changes... shamu lineage source are update for O already, victara is not update yet but you may find the repo of developer releasing the ROM on they threads...
bhb27 said:
you need to update the kernel to boot O, there is a lot of changes to it, like I wrote before shamu and victara must have the changes... shamu lineage source are update for O already, victara is not update yet but you may find the repo of developer releasing the ROM on they threads...
Click to expand...
Click to collapse
Thanks for your patience. I've been looking at a bootable Oreo Shamu build source. I'm guessing it involves lots of kconfig changes and such, just wanted to see if you thought it was anything simple (which I doubted). I appreciate your input.
calsurferpunk said:
Thanks for your patience. I've been looking at a bootable Oreo Shamu build source. I'm guessing it involves lots of kconfig changes and such, just wanted to see if you thought it was anything simple (which I doubted). I appreciate your input.
Click to expand...
Click to collapse
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
bhb27 said:
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
Click to expand...
Click to collapse
Thanks. I'll check it out and see how far I can get. Anything I can contribute to getting it ultimately working will be worth it. I had to make a good number (not major) of device changes already so I'm comfortable with that as well.
bhb27 said:
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
Click to expand...
Click to collapse
Hey again @bhb27. I just finished incorporating all of those changes and updating other files (mainly in the fs. directory). It still just starts to boot, but quickly goes back to the bootloader again. Any other suggestions on what I could check to see what causes that?
I'm leaning towards a file partition change that it doesn't recognize now, but just a random guess. It still doesn't install the .zip either (still error 7) unless I modify the device check assert (making me think it can't find the build.prop (due to some other format/partition change).
Here's a link to my repos and the .zip in case it helps. Thanks again for the help but I understand if you don't want to get too involved at this point.
Repo: https://github.com/calsurferpunk
Zips: https://androidfilehost.com/user/?w=settings-dev-files&flid=218810
Update 1: I'm also checking to see if there was anything specific about the cm-14.1 to lineage-15.0 device tree and it looks like there might be a little more.
https://github.com/LineageOS/android_device_moto_shamu/compare/lineage-15.0
Update 2: It looks like everything should be good with the device setup as well. I'm wondering if it's more of a TWRP issue since I've seen references of needing a custom version to install AOSP 8.0/LOS 15 in other device forums.
Update 3: I noticed there were a couple kernel config flags missing according to:
https://source.android.com/devices/architecture/kernel/modular-kernels#core-kernel-requirements
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
Added those, but still no luck. I've been comparing device/kernel files locally in hopes of finding a key difference, but after seeing the kernel requirements match I'm still pretty lost.
Update 4: I was able to find the failed kernel boot log under:
/sys/fs/pstore/console-ramoops
It looks like the error preventing booting is from these lines (attached):
...
1.586240,2] init: init first stage started!
[ 1.586318,2] init: First stage mount skipped (missing/incompatible fstab in device tree)
[ 1.586345,2] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
...
[ 2.131621,0] ueventd: fixup /sys/devices/virtual/stm401/stm401_as/rv_6axis_update_rate 1008 1008 660
[ 2.131679,0] ueventd: fixup /sys/devices/virtual/stm401/stm401_as/rv_9axis_update_rate 1008 1008 660
[ 2.145657,0] drv260x driver found: drv2605.
[ 2.146248,0] drv260x probe work succeeded[ 2.246181,0] ueventd: Coldboot took 0.310706 seconds
[ 2.255910,3] init: Command 'wait_for_coldboot_done' action=wait_for_coldboot_done returned 0 took 262.268ms.
[ 2.255959,3] init: processing action (mix_hwrng_into_linux_rng)
[ 2.256179,3] init: Mixed 512 bytes from /dev/hw_random into /dev/urandom
[ 2.256212,3] init: processing action (set_mmap_rnd_bits)
[ 2.256263,3] init: Cannot open for reading: /proc/sys/vm/mmap_rnd_bits
[ 2.256287,3] init: Unable to set adequate mmap entropy value!
[ 2.256303,3] init: Security failure...
[ 2.256318,3] init: panic: rebooting to bootloader
[ 2.256336,3] init: Reboot start, reason: reboot, rebootTarget: bootloader
[ 2.256367,3] init: android::WriteStringToFile open failed: No such file or directory
[ 2.256391,3] init: Shutdown timeout: 6
[ 2.256422,3] init: terminating init services
[ 2.256476,3] init: Terminating running services took 0.000134532 seconds with remaining services:0
[ 2.256892,3] init: vold not running, skipping vold shutdown
[ 2.357286,3] init: powerctl_shutdown_time_ms:100:0
[ 2.357305,3] init: Reboot ending, jumping to kernel
[ 2.658702,0] mdss_fb_release_all: try to close unopened fb 1! from pid:1 name:init
[ 2.658715,0] mdss_fb_release_all: try to close unopened fb 0! from pid:1 name:init
[ 2.659433,0] Restarting system with command 'bootloader'.
[ 2.659442,0] Current task:init(1) Parent task:swapper/0(0)
[ 2.659457,0] Going down for restart now
[ 2.660756,0] Calling SCM to disable SPMI PMIC arbiter
It appears to be related to not finding the file partitions and this: https://lkml.org/lkml/2015/12/21/336 and https://lkml.org/lkml/2015/10/28/828.
Related
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.
I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^
Awesome!
I'm eager to hear about your endeavors in this!
L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant
L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.
@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule
Here is the screenshot I mentioned in my previous post.
I forgot to include it ...
Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?
I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first
31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Xperia z1 has carbon Android pie and gapps link
This may help you.
Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.
No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning
Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.
Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?
I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.
Hello
For the past couple (weeks) I've been trying to compile Android 10 for tenderloin using the Android 9 sources but it's not going so well. First thing I ran into multiple sepolicy errors and I feel as if I fixed them in inappropriate ways but the errors went away. Other errors regarding camera and audio and such, that are regarding that tenderloin no longer uses the legacy audio format. Made me confused because I used the device sources form Evervolv and DIrty unicorns and if i'm correct they built it exactly the same way they uploaded it. After these errors were wrapped up, I got a error at zipping the rom that it could not zip due to failure of being able to read build.prop. This made me believe that the sources are not correctly formatted. If anyone can help me find a manifest, I can build for all you guys. Please keep tenderloin alive!
Now, I did something and I'm getting plenty of perl errors. Maybe I'm just very unlucky. I'm gonna attempt to reinstall on a fresh drive on my server.
If its anyone's concern, I was building lineage 17.1. I noticed for example, Lineage's "qcom-device" repo was shaped completely differently than Evervolvs qcom-device repo.
This led me to thought that Android 10 is going to be extremely difficult because of all the upstream dev changes that was pushed to Q. If any of you would like, I could probably push out March patches Pie rom because over there I'm mostly safe of complying with the source.
My manifest shape
DirtyUnicorn's device-tree
DirtyUnicorn's device-tree-common
DirtyUnicorn's htc-msm8960-kernel
Evervolv's vendor
And dirty unicorn's atheros wlan driver
I have been changing up the device tree so much, it almost looks ridiculous . From what I heard lots of properties on the device tree haven't been touched for years. Maybe tomorrow I can try Evervolv's Q rom. If you guys can help me build up my manifest, we can push out a fully working Q rom for tenderloin. And it would be just in time when Android 11 comes out. Thank you everyone!
I wish that I could offer any help, but I never tried to compile any Android ROM or for the HP_TP.
To my knowledge the only users that I know that could offer some insight on the process would be:
@flintman
@elginsk8r
Also the LuneOS project could offer some help:
https://pivotce.com/tag/luneos/
If Android Q(10) can not be ported to the HP_TP, then at least P(9) is a good ROM to keep updating that could provide many years of App support.
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
djared704 said:
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
Click to expand...
Click to collapse
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
HP_TOUCHPAD said:
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
Click to expand...
Click to collapse
When I look at the tenderloin source, the script to gather the camera driver is disabled. Camera isnt a huge deal though because its only 1.3 MP. However we use the MSM 8960 kernel from HTC and that is the one m7,, but the one m7 is a SD 600 device so it loses sense. I was gonna get some help with one of my kernel developer buddies to dev a kernel for android 10 for tenderloin. If you see the one m7 has Lineage 17.1 available and even though it doesnt have same chipset, if im correct both chipsets went off of the same assembly line process. Lineage 17.1 for the one m7 also packages it as a "uimage" which is what we use. I believe this was only a very small select of devices. Yeah about that ive been getting so many complaints during build about "mkimage" which should've been a prebuilt tool in the lineage source. Don't know why they removed it, or if our developers added it in by their selves, etc. Anyways I fixed that error by just "allowing" mkimage in one of the permission files in my environment. But yeah i went as far as the build packaging the ROM and it complaining it cannot read build.prop. Note the build.props are generated by the environment , not the source (even though the device data is gathered by the source, its not what im talking about). I even go to the directory it was complaining about and it was all there. One of my friends suggested a permission error. I changed permissions to 777 (rw to all users) and it would still output that error. By that point I trashed my build meaning I may of done something wrong early on. I will let someone else continue building 10 but I will continue building 9 with latest patches.
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
HP_TOUCHPAD said:
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
Click to expand...
Click to collapse
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
djared704 said:
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
Click to expand...
Click to collapse
I have only recompile the Kernel and all of them work, but the correct branch must be use. I can not say about building a ROM, never done it.
But Evervovs Pie by elginsk8r works very well and stable as it uses the same kernel, but the framework is different. I guess elginsk8r will be the only that can guide you on the right direction or flintman.
Have fun learning, it takes a lot of TIME!
I'm kinda new here, so please excuse me if this is not the best place to ask and it should instead be posted in another section.
First, a bit of context: I recently bought a refurbished H910 to practice android development since it was fairly cheap, and after testing its features and unlocking the bootloader to install custom roms, i opted to start compiling a kernel of my own with some changes to begin involving myself with the development side of things. For now, i am using the Lineage OS 18.1 kernel sources on github as a base for the kernel, then after making sure that the kernel compiled, i flashed it into the phone and basically everything works with the only exception being the bluetooth, and maybe the IR Blaster, but that one is working just like the stock kernels on different Android 11 roms.
Now getting to the issue itself in more details... it boils down to the phone's bluetooth refusing to turn on while running that custom kernel of mine on any Android 11 ROM, be it Lighthouse, Superior OS Xcalibur or Lineage 18.1, the bluetooth tile gets stuck on the "Turning on..." icon animation for a while and then returns to the disabled state. Reverting to the stock kernels or even using other custom kernels like Lyb's or Gamma make the Bluetooth work again without needing a wipe, which tells me that the problem is definitely somewhere in my kernel. I could of course test it on some Android 10 ROMs, but the outcome will most likely be the same.
I even took some logcats via ADB Shell but they are kind of broad and mostly explain that the service had some problems with "com.android.bluetooth service has died: psvc PER", followed by a "scheduled restart of crashed service com.android.bluetooth...". Both of which never happen on those ROM's stock kernels, where the bluetooth works as expected. I looked around on Lyb/Gamma kernel sources on github, and there aren't any major differences to the defconfigs for example with the bluetooth driver configuration also being just about the same.
I'm not sure if this will be of any help, but as for the toolchains and compilers, i am using clang 11.0.2 383902b1 as the main compiler, gcc 4.9 as the ARM32 cross-compiler, and gcc from 4.9 up to 10.3 as the AARCH64 cross-compiler, all running on Manjaro. I also changed that combination dozens of times, but to no avail.
So am i missing something during the compilation process? With all those things i already checked, i keep getting a feeling that something really simple is going over my head. Also, i can post the link to my github repository here if needed, there's a branch made specifically to check the BT since it has only the changes made to assure that the kernel compiles.
Edit: The problem was solved!!! It actually comes down to using the exact toolchains provided by the lineage OS source tree for the device (that might be optional, but it's how i managed to get it working) and checking if everything has been installed correctly. It seems some files failed to download the last time i did a 'repo sync' on the source and that was what might have caused this.