Database Users

[ROM][May8][RC1.6] WebCM9 with Cornerstone! AOKP #34 Beta1 live! Now with Themes!

VIDEO REVIEW:http://www.youtube.com/watch?v=na-iugam4eQ&feature=youtu.be
Disclaimer: I am not responsible for any damage to your device due to flashing this ROM! Flash at your own risk!
Special thanks to the CM9 team, AOKP team, and Onskreen!
Extra special thanks to zanderman112 for the video review and new screenshots!
This is more-or-less a straight kang of CM9 and AOKP for the HP Touchpad with Onskreen's Cornerstone baked in. If you're not familiar with Cornerstone, check out http://www.onskreen.com/cornerstone/
In a nutshell, Cornerstone is a Android modification that allows for true multitasking. Not the "Press the Back button to go to the previous app"-type of multitasking, but actually being able to have 3 applications running at once. Cornerstone utilizes the additional screen real estate on tablets to keep up to 3 applications on your screen at one time. It's kind of hard to understate what a different experience Android is using Cornerstone. Check out the screenshots to see what I mean!
Cyanogen himself is using it and loves it, and is trying to incorporate it into CM9, although there are some roadblocks: https://plus.google.com/u/0/100275307499530023476/posts/ViCME1bb8F6 Having said that, Cornerstone isn't perfect- there are still some rough edges to iron out, and porting it to the Touchpad was a little tricky, but it should be
BUGS:
- All the known CM9 bugs (i.e. no camera)
- Wifi is buggy for some (see comments below) (FIXED)
- Bluetooth (?)
- Recent apps out of focus in landscape (looking into it)
- Changing the DPI messes with the CSPanel (although the functionality remains intact) (FIXED)
- Videos will not run with the CSPanel active, you'll need to minimize it for full screen (FIXED)
- Some apps get "stuck"- either rotate landscape to portrait or vice versa, or close Cornerstone and launch it again (FIXED)
- The Home selection menu is buggy- working on a fix (FIXED)
- Probably others
UPCOMING/TO-DO'S:
- Wifi fix (FIXED)
- You tell me
CHANGELOG:
RC 1.6
- Synced to CM9 repo 5/7/12- Now supports themes! (Note: CM7 themes do install and can be chosen from the Themes tab in Settings, however they make not look exactly the same as they did on CM7. Ask your themer to update the theme for CM9 for best results!)
- Updated wifi firmware for ath6kl (cherry pick of change 11/15011/2)
- Disabled Cornerstone on bootup. This is to fix the wifi issue- yes I can confidently say that this fixes the wifi issue. To start Cornerstone, you will need to manually press the application icon. (Thanks to OaT and viskon for pointing that out!)
RC 1.5
- Fixed disappearing taskbar
- Fixed FC's
RC 1.4
- Synced to CM9 repo 4/24/12
- Ported WebCM9 to Cornerstone for even more multitasking goodness! (Special thanks to tbob18!!!) See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1514235
RC 1.3
- Updated to Android 4.0.4
- Source code released
- Cleaned up various things
- CM9 version updated 4/18/12
- AOKP version built on build 32
RC 1.2
- Synced to 3/16/12 CM Repo
- Includes charger control settings (in HP Touchpad Settings)
- Switched to CM9 Nightly kernel (should help with wifi- please see notes below)
- 120dp and 160dp versions now available (patches are for RC 1.2 only- so please update to RC 1.2 before using the patches)
RC1.0
Current up to CM9 nightly- 3/14/12
Full hardware video acceleration! (Special thanks to jcsullins!)
Fixed graphics issues! All windows/headers line up properly now!
(Note- wifi sometimes doesn't work after you first flash the ROM. After the second reboot, it should work!)
0.5
Updated to Cornerstone 85.1- new ICS skin, button fixes, and other tweaks
Updated to latest CM9 nightly build- (full hw video acceleration coming soon)
GAPS included now
Full wipe recommended
0.4
private build
0.3
- Kernel pmem changes- wifi fixed (finally!)
- Touchscreen improvements
- Full wipe recommended
0.2
- Updated to latest CM nightly (2/18/12). (FYI, build dates can be found in Settings -> About Phone. I always sync immediately prior to building unless otherwise noted)
- Added wifi fix CM change #12341 (should hopefully fix wifi for those experiencing issues)
- Minor CSPanel resizing
0.1
- initial release
INSTALLATION INSTRUCTIONS::
1. Download ROM to SD card
2. Download 120dp or 132dp patch (optional)
3. Reboot to Recovery
4. Perform Nandroid backup
5. Install ROM
6. Install GAPPS
7. Install 120dp or 132dp patch (optional)
8. Reboot
DOWNLOAD SOURCE:
https://github.com/antiphon1/CS_Touchpad_SRC
DOWNLOAD LATEST VERSION:
RC 1.6
http://www.mediafire.com/?mliurxi429f8130
120dp patch: http://www.mediafire.com/?6ytbo8c4otr5dlr
132dp patch: http://www.mediafire.com/?52yvq22ff2jvrib
Superuser: http://www.mediafire.com/?53eygr4w5zuraii
AOKP Beta 1: http://www.mediafire.com/?tsqho88xjinaknp
(Note: the AOKP version is Beta so expect some bugs. However, it is stable enough for daily use. Also, wifi works MUCH better on this ROM- no need for Rohan's Mod. Known issues so far: Lock screen is currently not working in AOKP Beta 1- if you absolutely need a lock screen, this is not the ROM for you!)
Patches for AOKP Only:
AOKP 120dp patch: http://www.mediafire.com/?cji2e118yu46ut2
AOKP 132dp patch: http://www.mediafire.com/?mrjtz4ymgag523w
To make AOKP your default ROM, boot into Recovery and mount /system and /boot. Then type:
adb shell
cd /boot
echo AOKP > moboot.default
cat moboot.default (make sure it says "AOKP")
exit
adb reboot
OLDER BUILDS:
RC 1.5b (4/27/12)
http://www.mediafire.com/file/n605yyrw0kbts66/42712-v15b-Cornerstone-WebCM9-tenderloin.zip
RC 1.4
WebCM9: http://www.mediafire.com/?6wrw18f8k3t6zgg
RC 1.3
CM9: http://www.mediafire.com/?qf12ucctv21rb5h
(previous 120dp and 132dp patches should still work)
RC 1.2
160dp Full: http://www.mediafire.com/?sd19mcladw4qyp9
160dp patch: http://www.mediafire.com/?66o38yzg73of30u
120dp Full: http://www.mediafire.com/?iwyjmr7x2re78ib
120dp patch: http://www.mediafire.com/?04a9pkkiqqc564d
132dp patch: http://www.mediafire.com/?vhgn2p6ypr40pc3
(Note: Since Rohan has apparently discontinued the 132dp version of his Supreme Mods patch, if you plan on using his mod, first flash the Cornerstone patch, then Rohan's 120dp or 160 dp patch, then you will manually have to change your build.prop to 132dp. It's a pain, I know, but I don't want to use or modify Rohan's patch until I get his approval.)
RC1.0 http://www.mediafire.com/?fepajcr67ljpcd5
0.5 http://www.mediafire.com/download.php?8tghg76np2rqi3i
0.3 http://dl.dropbox.com/u/10510443/021912-03-%20Cornerstone-cm-9.0.0-RC0-Touchpad-KANG-signed.zip

5/8/12
Starting with RC 1.6, wifi issues should be resolved. Please let me know if you are still having issues though.
NOTES ON WIFI (PLEASE READ BEFORE POSTING!)
Update- 4/24/12
Wifi seems to stay connected without Rohan's Mod- AFTER rebooting 1-2 times. Try this first and please report back. Also, wifi will get flaky again if you reboot to WebOS and back to Android. Again, you will have to reboot a few times or flash Rohan's Mod again.
Update- 3/19/12
Many users are reporting that wifi works for them after installing Rohan's Supreme Tweaks 1.5. If you are still having wifi issues, here is the link.
Others are also reporting alternate wifi drivers helped them with their wifi issues: Thread here, direct download link here.
3/17/12
So I have noticed there are a couple of people with wifi issues using my Cornerstone ROMs. I also had a lot of issues with wifi, mainly with it not turning on after a restart, or finally turning on and seeing my wifi network, but not actually being able to connect to it. It was frustrating. Wifi is the lifeblood of the Touchpad! So I read through all the threads and posts about wifi, trying a bunch of different things, but there was one fix that solved my wifi issues permanently, regardless of what ROM I used-I switched my router's wifi channel to 1 (if you have a dual-band router, switching the 5ghz channel to 157 also helps, to a lesser extent). After that, I could connect after each reboot without fail. So if you are having wifi issues, please try that first.
Now, I realize some of you don't have the luxury of being able to switch wifi channels (for those connecting through work or school networks, for example) and I feel your pain. So I've switched to the CM Nightly kernel. This is the same kernel used in the CM9 nightlies, so you should have the exact same performance. So until there is a permanent solution to the wifi issues for everyone, please bear this in mind and leave comments on whether wifi is working for you or not.

One more for the road

Sounds great man. Thanks for the hard work. Will test asap.

this is great and I appreciate the hard work, but it makes really appreciate webOS in the fact that apps on the TouchPad like Glimpse does just this and works near flawlessly... Glad you guys are incorporating these different items.

Looks very promising, nice work so far!

wifi
does thsi have the wifi fix implemented in cherry kang?
this one
http://review.cyanogenmod.com/#change,12342
if not, it works wonders!!!

After watching Cornerstone in action yesterday, I can't wait to try this! AWESOME!!

rochford77 said:
does thsi have the wifi fix implemented in cherry kang?
this one
http://review.cyanogenmod.com/#change,12342
if not, it works wonders!!!
Click to expand...
Click to collapse
The "fix" in cherry kang makes things better but it is by no means a permanent fix sadly.
Sent from my Nexus S 4G using Tapatalk

Whatttt, trying this at home in a few hours. OnSkreen was the next thing to look for.
edit: wipe data/cache or flash on top?

I just want to reiterate that anyone wanting to use this should probably read the google plus discussion linked in the OP for the very real concerns. I just want the end user to use this responsibly in order that we can continue getting cutting edge features added to our devices. Pay particular attention to the concerns expressed by diana hackborn and the founder of onskreen (forgot his name, but cant seem to reopen the g+ site at the moment).
Thank you and have fun!

This is a no drama zone. Thread cleaned...of bickering. Here is what you missed;
THE MIC IS NOT WORKING ON THIS BUILD...LIKE ALL THE REST.
Now, let's get back on topic.
Sent from my HTC_Amaze_4G using xda premium

Which build of CM9 was this based on?
This build seems to have killed my wifi totally - I can confirm after several resets via ACMEUninstaller and starting fresh with both Alpha 0.5 and 0.6 (Wifi both working fine, I don't recall any issues with Alpha 0 either) Wifi was working - able to connect and access wifi, I then booted into CWM and flashed this and unable to even turn wifi on. (To clarify, my latest test was: Remove Android via ACMEUninstaller, Flashed Alpha 0.6, tested wifi was functional, flashed cornerstone ROM over 0.6 - wifi broken, cornerstone functional)
It's a really tough choice - having cornerstone is really quite cool, but I can't live without the wifi.
Am I doing something wrong (Am I supposed to flash via cminstall/ACMEInstaller2?) or is anybody else getting this?

Dislexsick said:
Which build of CM9 was this based on?
This build seems to have killed my wifi totally - I can confirm after several resets via ACMEUninstaller and starting fresh with both Alpha 0.5 and 0.6 (Wifi both working fine, I don't recall any issues with Alpha 0 either) Wifi was working - able to connect and access wifi, I then booted into CWM and flashed this and unable to even turn wifi on. (To clarify, my latest test was: Remove Android via ACMEUninstaller, Flashed Alpha 0.6, tested wifi was functional, flashed cornerstone ROM over 0.6 - wifi broken, cornerstone functional)
It's a really tough choice - having cornerstone is really quite cool, but I can't live without the wifi.
Am I doing something wrong (Am I supposed to flash via cminstall/ACMEInstaller2?) or is anybody else getting this?
Click to expand...
Click to collapse
You're probably not doing anything wrong....my WIFI was almost useless with this build also. I backed it up so that I can easily restore for when the bugs get worked out, but I had to go back to the ClassicNerd ROM for now since it runs flawlessly for me.

Dislexsick said:
Which build of CM9 was this based on?
This build seems to have killed my wifi totally - I can confirm after several resets via ACMEUninstaller and starting fresh with both Alpha 0.5 and 0.6 (Wifi both working fine, I don't recall any issues with Alpha 0 either) Wifi was working - able to connect and access wifi, I then booted into CWM and flashed this and unable to even turn wifi on. (To clarify, my latest test was: Remove Android via ACMEUninstaller, Flashed Alpha 0.6, tested wifi was functional, flashed cornerstone ROM over 0.6 - wifi broken, cornerstone functional)
It's a really tough choice - having cornerstone is really quite cool, but I can't live without the wifi.
Am I doing something wrong (Am I supposed to flash via cminstall/ACMEInstaller2?) or is anybody else getting this?
Click to expand...
Click to collapse
Yes, there was a reported problem with Cornerstone keeping Wifi toggled on startup. I'm working on another build that includes the latest CM wifi fix. It should be up later today.

Newb here ... I don't seem to have the market app installed after booting up this rom. How would I go about getting this installed.

davejr021 said:
Newb here ... I don't seem to have the market app installed after booting up this rom. How would I go about getting this installed.
Click to expand...
Click to collapse
Download gapps v11 from the thread with GAPPS v11 in its title.
Sent from my cm_tenderloin using xda premium

davejr021 said:
Newb here ... I don't seem to have the market app installed after booting up this rom. How would I go about getting this installed.
Click to expand...
Click to collapse
Wait, I thought you needed 10 posts to at least post in a dev thread, you only have 5 at this moment.
@antiphon
Which build is based off of? Is it strictly a 0.6a + onskreen or is it later than 0.6a + onskreen or is it closer to a nightly + onskreen? Kang seems too broad a description, it should at least mention the base, or when it was synced with the repo.

antiphon said:
Yes, there was a reported problem with Cornerstone keeping Wifi toggled on startup. I'm working on another build that includes the latest CM wifi fix. It should be up later today.
Click to expand...
Click to collapse
Sweet....will there be an update to the Cornerstone app included? The one from the current ROM had an issue with the lower side screen where the app overlapped into the title bar of the lowerscreen. Also, in the demo vid from Onskreen, it shows a button that allows you to swap the apps from one of the smaller side screens to the larger main screen...this feature isn't in the current ROM so was curious...thanks!

Watching this thread VERY closely! I am so glad I got my Touchpad when I did.

[TOOL]TWRP-F2FS[M7UL]

This is a personal build of TWRP with F2FS support(proper way) based off 2.8.1.0 branch from Omnirom(recovery) which I butchered and added F2FS..
This was tested with CM11 way back last year..I just posted it for the heck of sharing it since I have not seen the same idea/achievement here on M7 forums..and seems this phone needs a "refresh"(in a good way)..
Now whats F2FS?? Googling can give you trivial INFO yet you can start your way here
This Files system developed by Samsung Developers lean towards a much less noisier, less workloads, and a faster throughput File System that can substitute EXT4 in the near future(they already use it)..extensively if you rely heavy on Benchmarks it has been put to the test by some Devs here on XDA like this one
Now enough with the chit-chat..on this TWRP build I only converted /DATA as F2FS..now you might be wondering why?? Answer is because its the most actively used partition on your phone..System apps use it to store settings/info/etc...Framework uses it too for caching and storage...Extensively your Apps(the ones you install) use it as well..so there completely no point converting the whole phone to F2FS which in the latter can just cause you more issues when you want to return to stock..
This only works on AOSP based ROMs(i tried it on CM11) though you'll need a kernel with F2FS support baked in for things to work properly.. (Who wants me to build one? I know for sure you don't..)
DO NOT TRY ON SENSE(You have been warned) Tried it once well it boots up but you'll end up on a security windows and you might not get out if it..OR you may be able to boot it up but you cannot install apps(happened to me twice and no Dice on installing anything)..well you're free to play with it so who knows who might get a lucky pick on getting this working on HTC Sense ROM's, but for now I'll safely say/advise to use on AOSP ROMS only..
Download here
**I won't be liable for any damage on your phone..you are on your own here..
**This project does not come with a warranty..
XDA:DevDB Information
Recovery with F2FS, Tool/Utility for the HTC One
Contributors
kairi_zeroblade
Version Information
Status: Stable
Stable Release Date: 2015-02-05
Created 2015-02-05
Last Updated 2015-02-05

Newsmy Carpad NU3001 CM13 ROM

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.

Regarding Android 10 on the HP Touchpad

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!

What does kernel cross-compatibility look like, and who runs the baddar90 show now?

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