Related
Although I have used Android (phones & tablet) for about 4 years, I have only just started dipping my toes into the exciting world of rooting and mods. And so I have just wiped my Samsung Galaxy S3 and flashed the most recent Omnirom - a process which was so painless as to be almost pleasant!
It seems, however, that multiview/split screen is not available in this particular version of Omnirom (or if it is, it's so well hidden that I've not been able to find it!). So I'm wondering if it's possible to compile my own version of Omnirom from source, with just those parts of it I need. I used to compile linux kernels (before the days of loadable modules); can I do the same with Omnirom? That is, can I compile a version of Omnirom which might contain different fuctionailty that the nightly build?
Thanks!
It's pretty straightforward of you have a Linux box, and doable on Mac as well. There are great instructions on the OmniROM wiki. Plan on the source sync taking several hours (or overnight) the first time. Make sure you set up ccache so that subsequent builds go quickly.
http://docs.omnirom.org/Main_Page
Once you've built a straight-up version that works, you can branch and cherry-pick the multi-window patches from the OmniROM Gerrit instance.
---
Posted from whatever phone booted today
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
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.
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!
Yesterday I replaced my ailing 2017 battery for a nice and shiny 2020 one. Naturally, along came the 50% battery bug.
Unfortunately, this is the most confusing flash process I've come across yet. Even the LG G3 was not as straightforward. Either that, or I'm getting old. At any rate, I managed to get LOS 15.2 running with a zip image containing everything I needed - which I obtained as per this post. When it comes to flashing a kernel... well, I'm a bit lost. Before I even get to that, however, I would like to know the following:
- Was deega's kernel fix ever incorporated into the baddar90 kernel?
- Why did the ownership of the baddar90 kernel github change? Did OrdernKrieger take over development?
- Is the most recent kernel going to play nice with my installation of LOS 15.1? (No, I am not going to change the LOS installation for now)
Finally, if the kernel fix was not incorporated, how do I get a copy of deega's release? Do I have to compile it myself?
Never mind. I finally discovered an updated kernel that included the fix: https://forum.xda-developers.com/t/...-linux-stable-update-11-7-2019.3929878/page-5