Related
I decided to put up or shut up.
Alpha is in the title, but I guess I will call this first version a developer preview edition.
Thanks goes to Hashcode, without whose original work, this would not be possible.
ROM: http://www.mediafire.com/download/zq55o2ec9wbzzh2/Slim-ovation-5.1.alpha.0.1-UNOFFICIAL-20150709-1624.zip
MD5: http://www.mediafire.com/download/k616385vb78cfbv/Slim-ovation-5.1.alpha.0.1-UNOFFICIAL-20150709-1624.zip.md5sum
I haven't had much time to play with it (no zram script, etc). I expect to improve this some with time.
https://github.com/SlimRoms/platform_manifest
I'm sure everyone knows what kernel I used and where to find the latest source...
BUT, this is what you want.
http://www.mediafire.com/download/yuukg3kofubfpap/omap4.tar.gz
I will post complete kernel and device source within a day or so for whoever wants to build this.
XDA:DevDB Information
Slim-ovation-5.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
Jon Lee, Hashcode
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Current Beta Version: 20150709-1624
Beta Release Date: 2015-07-09
Created 2015-07-10
Last Updated 2015-07-09
system - ext4
data & cache - ext4 or f2fs
Is it Christmas already? Will be testing this ASAP
Setting it up now, so far so good. It seems to have fixed the audio issue with Amaces CM12, where keyboard sounds aren't affected by volume. Will keep updating as I use it.
Getting some graphical glitches when rotating the screen, and a few missing items in the Settings window, but not too bad so far.
There is a frustratingly large number of settings missing, compared to CM12, from status bar options to the power menu. Hopefully, these can be added later on.
Given a little time, I think I can fix the rotation graphics glitches.
(I'm going to try some omapfb/dss kernel boot arguments and try to get rotation out of system/build.prop).
There's lots of other little things to play with.
Noticed it won't retain my wi-fi password through a reboot.
I had read something about a new secure storage container to retain secrets?
Settings... I'm sure that's slimrom's "slimming"...
The graphics side of things held me up for a long time. That's mainly what I'm concerned about right now.
As promised, here's a source dump and another test build.
device_bn
http://www.mediafire.com/download/3a4c321rta43ezm/slimlp_device_bn.tar.gz
hardware_ti_omap4
http://www.mediafire.com/download/1c2py11c95b7p3d/omap4-20150713.tar.gz
kernel
http://www.mediafire.com/download/g2dh13gj93fvun7/kernel-20150713.tar.gz
ROM: http://www.mediafire.com/download/a...on-5.1.alpha.0.1-UNOFFICIAL-20150713-1918.zip
MD5: http://www.mediafire.com/download/9...alpha.0.1-UNOFFICIAL-20150713-1918.zip.md5sum
If anyone wants to build this and be added to the contributor list, let me know....
It shouldn't take too much to polish it up.
I'd love to, but when it comes to baking my own ROM, I'm very much the nubcake. I WILL offer my hardware to be a test subject though. I have a spare on hand that is not a daily driver.
I will go ahead to say that at first glance, it is very smooth, and responsive. I'll give it a couple days, see how it does as if used as normal, and work from there.
I tried to flash this, but it seems to have an endless boot. I waited about 30 minutes and lost patience. Do I need to flash something else first, like extracting the boot.img? At one point, I wiped everything including cache, system, data, internal sd, and had a pretty blank slate. I am using TWRP 2.8.7.0 and 2.8.7.1. Also tried f2fs on cache and data and ext4. I must be missing something.
Was going to ask which device until o read the list you have. M8 s a on CE phone, I love mine with the same ROM! I don't know why it would not boot fornyou though, unless you have system set to f2fs by mistake, as this ROM does not support it on system like @amaces does. Maybe if younused his, and hopped to this one, that little bit was overlooked?
Here's what I got so far: when changing between land scape, and portrait there is some graphical distortion, and a touch of lag which clears up after about a second. There is no advanced reboot option, and when I sure down, it reboots instead. When multitasking, there is a general UI lag which clears up spoon after., and it does not save WiFi information so you have to reenter WiFi information after every boot. So far, aside from slims slimming causing a desire for menu options, and theming, this is all I found.
Is this in continued development?
DarkWolffe said:
Is this in continued development?
Click to expand...
Click to collapse
No, unless someone wants to take over. Basically it was an experiment for me to see if graphics in lollipop could match that of cm10(.2). In short the answer is they can't... (without a ducati upgrade).
The other reasons are twofold. First, the lollipop browser completely sucks (I know, there's alternatives).
Lastly, I don't believe I would ever achieve the level of performance as I have with my yellow kernel 10.2 ROM (which is my daily driver), this again is related to the ducati.
I would like to take another stab at a kitkat ROM and see if I can incorporate some of the stuff I have picked up recently.
I would have updated liquidsmooth, but they have already pulled kitkat source. So I am debating which ROM repo to use (I'm thinking probably Carbon 4.4? Tabletui is important to me...)
Hey Jon, I'm excited to hear you might be building a Kit Kat ROM. Would like to try one that has your improvements such as no screen flicker and still be able to use screen casting. Looking forward to your build.
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.
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
IMPORTANT INFORMATION
Hi all,
This ROM is in a very early development stage, so you can expect a lot of things broken.
Please don't expect to use this ROM as a daily driver.
What is working:
Audio (playback)
Bluetooth
Graphics
Camera - photo, video recording (w/out audio)
Sensors
RIL
GPS
Wifi
USB
Video playback (HW/SW)
What is not working:
Audio recording
Proximity & Orientation sensors
GPS
Camera may not start at times
System time issues (alarm might not work or start with a delay)
maybe yet something
Download:
AndroidFileHost
Installation order:
The installation below requires a repartition of the phone internal sdcard in order this ROM fit on /system partition. DO NOT proceed an installation if you are unsure what you're doing and how to deal with a possible consequencies.
before installation make sure you have a TWRP recovery
install chrono kernel (both ROM and the corresponding kernel are located in the same directory - see ROM link below)
reboot recovery
flash ReParted zip. This will wipe system, data and cache partitions!
install ROM
install chrono kernel again
*please note a possibly undesirable effect of the repartition: cache partition will be decreased to 15 MB and some ROMs that rely upon this partition won't boot. To restore original sdcard partition layout, flash stock 4.1.2 ROM (with PIT file).
Credits:
@SergeyL
@rINanDO
@AdrianDC
@3liteking148
@Meticulus
@Unjustified Dev
@golden-guy
@nieltg
@isaak
@NovaFusion
@TeamCanjica
LineageOS community
Google
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
Source code:
Manifest: LOS 16.0
Device tree: LOS 16.0,
Kernel: LOS 16.0
other repos
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP recovery 3.x
Version Information
Status: Alpha
Created 2018-12-31
Last Updated 2018-12-31
Reserved
Reserved
Wow, works better than Oreo
Srsly, little more tweaking and this is suitable for daily use
is it possible to implement these functions in the janice kernel?
github.com/pelya/android-keyboard-gadget
Gonna try it today in 5 hours maybe, use it for a day and give my feedback. thanks for keeping this phone alive. Also have u tried magisk with this rom? I will try it anyway but i just wanted to know.
Here is my feedback.
1- No space for flashing pico gapps so I guess we will have to use microG.
2- Random freezes that takes like a minute then locks the phone.
3-Sometimes, WiFi didn't work and I had to restart. When pressing the icon it flashes green then goes back to grey again.
4-Bluetooth isn't working at all ( not sure if it's only me or what because it never worked on LOS 15.1 too ).
5-GPS not working as well.
6-I hope you add HardwareKeys remap, navigation gestures and Traffic monitor, of course if you don't mind.
..
That's pretty much it. If you can fix the second and third problems, this ROM can be used as a daily driver.
Sent from my GT-I9070 using XDA Labs
Sorry for OT but, @ChronoMonochrome you considered working on PMOS for 9070?
It's nice idea and porting require talented people like you
https://wiki.postmarketos.org/wiki/Samsung_Galaxy_S_Advance_(samsung-i9070)
Bx16 said:
Sorry for OT but, @ChronoMonochrome you considered working on PMOS for 9070?
It's nice idea and porting require talented people like you
https://wiki.postmarketos.org/wiki/Samsung_Galaxy_S_Advance_(samsung-i9070)
Click to expand...
Click to collapse
Nice to see some efforts of developing custom ROMs here, but amount of non-working features scares me
I would rather stick updating some my older ROMs like UltimateROM (but no promises though).
Mainlining/forward porting work always comes handy, irrespective of whether one's interested to Android/Linux or GNU/Linux.
I cannot believe this device is still getting updates
excuse my rudeness but do u plan on updating this rom or should i lose hope ?
How do i install this room? I tried everything but always got or error 7 or infinite samsung screen without being able to go to recovery mode, so found myself going back to stock over and over again :/
DeathArcanaXIII said:
How do i install this room? I tried everything but always got or error 7 or infinite samsung screen without being able to go to recovery mode, so found myself going back to stock over and over again :/
Click to expand...
Click to collapse
You have to upgrade from 2.3 rom to a 4.2 rom first like this (if it didn't work, consider using this )in order to upgrade the bootloader then you can install this rom. But i wouldn't recommend this rom as its not stable. LOS 15.1 is far more stable for a daily driver.
Pie works great, but one (maybe silly) question...
Where to get GApps for this ROM?
.czarodziej said:
Pie works great, but one (maybe silly) question...
Where to get GApps for this ROM?
Click to expand...
Click to collapse
https://wiki.lineageos.org/gapps.html (you need GApps for ARM platform).
Does this ROM work on the Galaxy S gts7582? Would the developer of this ROM solve the 15.1 Lineageos bugs for the gts7582?
oseiasrodrigues0 said:
Does this ROM work on the Galaxy S gts7582? Would the developer of this ROM solve the 15.1 Lineageos bugs for the gts7582?
Click to expand...
Click to collapse
Provably not, they're completely different devices.
The dev need access to the device or at least a very very similar one to look at bugs properly so I guess no.
enkflr said:
Provably not, they're completely different devices.
The dev need access to the device or at least a very very similar one to look at bugs properly so I guess no.
Click to expand...
Click to collapse
Is that the gts7582 has lineageos 15 It initializes only does not work anything video, audio, etc. So I thought some dev could solve the bugs of this ROM. But thank you very much for the answer
I installed lineage os 16 on my s advance this is how it went:
1. Bluetooth kept crashing idk why but i uninstalled the bluetooth apk so it dosen't work at all
2. MicroG
It works fine i flashed it and it has signuature spoofing already on yay and it dosen't get stuck in the boot animation after restart
3. Kernel
Oh yeah overclocking is fun i overclocked the cpu to the max and it works amazing
4. Camera
Works but not video
Its ok but bluetooth sadly not working but idc
Its not my main phone anyway thankgod <3
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* We are not responsible for bricked devices, dead SD cards,
* lost data due to failed backups, etc, etc.
* flash at your own risk
*/
How to flash this ROM:
Download the zip file. (Make sure to download the file for your specific device)
Make sure this zip file is saved to your device (I prefer transferring to sd card to allow for full wipe of data on phone).
If you want Google Play functionality, download OpenGApps (link below). (optional)
Reboot into TWRP (latest version recommended)
Make a backup (optional).
Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (I like wiping internal data too, do NOT wipe SD Card!)
Flash the ROM you just downloaded.
Flash OpenGApps for Android 9.0 if you want Google services (optional) (I prefer nano or pico).
If you want root, flash Magisk.
Reboot and proceed normally with installation.
Download links:
Official 16.0 coming out soon from actual developers.
OpenGApps 9.0 (I use pico): http://opengapps.org
Source code:
LineageOS on GitHub
jfuginay (forked from LineageOS, and rest of the developers mentioned in the following Credits) on Github
Credits:
The LineageOS Team
haggertk
Trader418
andr01dfr3ak
temasek
TheMuppets
Version Information:
ROM OS Version: Android 9.0 Pie
Known Bugs: not sure, needs testing, so you tell me. bluetooth calls may not be working
Please report bugs with logcat
Screenshots
Known bugs:
None reported yet, in testing.
Any meaningful reason why you're posting inofficial builds?
AFAIK you're not affiliated with us in any way. And you haven't done any work for shamu. So users reporting bugs to you is just a waste of their time, as you're not going to fix them.
You're just picking some very low hanging fruits.
There's really no need for them especially because we're shipping soon.
Also proper credits would have been nice.
I have a good friend with a shamu phone, he wanted to upgrade his phone so I helped him out. As of yet, I haven't seen any Lineage OS 16.0 ROMs so I spent all yesterday attempting to build one.
It finally completed with no errors, and that seems like a meaningful enough reason to post an unofficial build to me.
I don't own a shamu, and sorry if I left out credits where credit is due for people bringing shamu specific code up to pie, feel free to message me names and I'll include them in the credit section.
Jfuginay said:
I have a good friend with a shamu phone, he wanted to upgrade his phone so I helped him out. As of yet, I haven't seen any Lineage OS 16.0 ROMs so I spent all yesterday attempting to build one.
It finally completed with no errors, and that seems like a meaningful enough reason to post an unofficial build to me.
I don't own a shamu, and sorry if I left out credits where credit is due for people bringing shamu specific code up to pie, feel free to message me names and I'll include them in the credit section.
Click to expand...
Click to collapse
The reason why there are no unoffical builds is that we don't really want to have any for devices which are going to be supported officially.
I know that you had good intentions, but posting inofficial builds doesn't make it easier for us devs.
Elektroschmock said:
The reason why there are no unoffical builds is that we don't really want to have any for devices which are going to be supported officially.
I know that you had good intentions, but posting inofficial builds doesn't make it easier for us devs.
Click to expand...
Click to collapse
Alright, that makes sense. I wasn't aware shamu was going to be included in the devices receiving official Lineage 16.0 ROMs. I'll go ahead and remove the download link, and refer my friend to your signature to download ROMs for his phone.
Like I mentioned, I don't have a shamu, I'm on a Note 3 (hltetmo) and have been building my own LineageOS 16.0 (even though members of the official Lineage team such as Haggertk are building unofficial ROMs for my Note 3 too).
You're correct that my building hasn't included any actual fixing of bugs and getting those fixes submitted into official builds, but you have to start somewhere, right?
Jfuginay said:
Alright, that makes sense. I wasn't aware shamu was going to be included in the devices receiving official Lineage 16.0 ROMs. I'll go ahead and remove the download link, and refer my friend to your signature to download ROMs for his phone.
Like I mentioned, I don't have a shamu, I'm on a Note 3 (hltetmo) and have been building my own LineageOS 16.0 (even though members of the official Lineage team such as Haggertk are building unofficial ROMs for my Note 3 too).
You're correct that my building hasn't included any actual fixing of bugs and getting those fixes submitted into official builds, but you have to start somewhere, right?
Click to expand...
Click to collapse
Yes I know that haggert and others are distributing unofficial builds. What I meant is we are not to eager of unofficial builds of people not affiliated with us in any way.
It's always getting messy if 2-3 people post unofficial builds and users think they're using the real thing.
I'm always happy if someone wants to help, but without a test device it's going to be close to impossible for you to test anything properly.
Where is the download?
girkev said:
Where is the download?
Click to expand...
Click to collapse
Now that I post here - the link is above and below your post.
Elektroschmock said:
Now that I post here - the link is above and below your post.
Click to expand...
Click to collapse
Sorry don't see link
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!