[ROM] [Unofficial] Lilly's "Yet another LOS 18.0" - Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De

[ROM] [Unofficial] Lilly's "Yet another LOS 18.0" - Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De

Hello, ladies, gentlemen and non-booleans!
Since I prefer building my own ROMs for various reasons, especially when the device tree source isn't made public, I have now finally gotten a LineageOS 18.0 build together.
"But there's already a build there!"
Fair point, but the sources of the device tree and kernel aren't public anywhere, to my knowleadge.
While I'm nowhere near as much of an open source fanatic as to demand all the source everywhere, it doesn't feel right either.
So since I've got a habit of having my own builds so I myself decide when I get an update, I decided to spin one up and at the same time provide a workaround for others who want to build their own versions.
So, what did I do? Voodoo? Other black magic? No!
I looked at crDroid's Github and the source tree seemed to be largely compatible with the LOS build system customisations.
They seem to often be working pretty closely with LOS build conventions.
They even specifically host a kernel there that has got an Android 11 branch!
And with that, we come to the sources used section:
Sources used:
Xiaomi-common
device
Kernel
So, how would you get your own private builds?
Do a repo sync as normal, then put into
.repo/local_manifests/roomservice.xml the following:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/tissot" name="crdroidandroid/android_device_xiaomi_xiaomi" remote="github" revision="11.0" />
<project path="kernel/xiaomi/msm8953" name="crdroidandroid/android_kernel_xiaomi_tissot" remote="github" revision="11.0" />
<project path="vendor/xiaomi/" name="crdroidandroid/proprietary_vendor_xiaomi" remote="github" revision="11.0-tissot" />
<project path="device/xiaomi/msm8953-common" name="crdroidandroid/android_device_xiaomi_msm8953-common-tissot" remote="github" revision="11.0" />
</manifest>
Do another sync and you're going to have everything you need downloaded. From there it's the usual procedure for builds.
"So, Lilly, that's all well and good, but why upload yet another LOS build?"
Because I've got itchy fingers and while I'm definetely not qualified myself to improve the device tree myself, you could profit from my addiction to doing builds quite frequently and get the latest feature changes pretty quickly.
Aside from that, I also plan on integrating Opengapps into the builds using their build system plugin. I didn't do it right away because last time there were some errors I couldn't figure out and I wanted a build right now.
Another thing I want to get working is having LuciferKernel preinstalled in the overclocked variant, because that overclock is definitely helping performance in my experience. Keep that in mind before installing. If you've got gripes about overclocking and I get the kernel to work (last in tree compilation resulted in an unbootable kernel) you're going to be stuck on the first vanilla version.
All in all, it's just sharing something what I use and trying to fill a tiny niche.
Do keep in mind that I'm definetely not a complete wizard and not an Android ROM developer. I just about know how to build a ROM and how to manipulate it here and there. I provide no support aside from "this build is borked, could you try again?".
That said, here's the download link:
ROM Downloads - Google Drive
drive.google.com
The first build hasn't been tested yet so do not expect to plug and play. I'm in the process of flashing it as I type this. MAKE BACKUPS!
Right, that should just about cover everything. Cheers!

Update: So far it's not booting and throwing up a couple of errors in the logcat. Hm.
I'll examine it a bit tomorrow.

Another update: Flashed crDroid and the same opengapps I used for my LOS build and now it's failing to boot in a similar manner... Weird.

Another update: It boots without that borked opengapps package.

Here's some proof that it boots successfully!

_I did a derp_
I noticed I had synced LOS 18 instead of 18.1
I just finished syncing the other branch and a new build will follow. Should be directly upgradable.

crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards

murtaza1326 said:
crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards
Click to expand...
Click to collapse
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?

lillywho said:
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?
Click to expand...
Click to collapse
i never said that you should not make your own builds but it device side source stuff take reasonable amount of time & hardwork they put about it
imagine you are one of dt maintainers & you publically share your work & people will use it before even waiting for you & giving you first chance (happens alot here)
thus he does this until they get green flag to do so from source side he won't do it
also if i decided to keep my stuff private literally no rom execept abhinav's & sooti (aosp gsi)
would exist for this device (i bet)
you are free to use any of my trees & stuff & make builds but please don't hop over multiple roms (like a mad person) (happens in our community alot)
there are more rom on telegram built by BBots (but they don't regularly update those)
if this is just a personal build & you are not going to update it in feature just don't share it
thanks & regards

What is the current situation?

Related

[ROM] [WIP] Unofficial CM12.1 for the p880

Hey guys
I guess you already know the drill It's more-less the same as we did on CM11, but Adam77Root isn't actively developing for the device anymore and also Demetris isn't working on this project anymore. I am pretty busy lately myself, which is why you shouldn't expect any miracles soon.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, and we will most likely merge it happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let us know about it before you release it and give credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
You tell me
Possibly more
Working:
Everything else 
Now, the most important part:
Download
All builds can be found on my goo.im account:
CM12
CM12.1
Please note that goo.im is currently having issues, which is why the latest builds are available from the devDB downloads tab.
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[ROM] [WIP] Unofficial CM12.1 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf, Adam77Root, sunsettrack4
Source Code: https://github.com/P880-dev/android_kernel_lge_x3/tree/cm-12.0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-11-09
Last Updated 2015-04-06

Reserved
I have used the following local_manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- p880 specific stuff -->
<project name="P880-dev/android_device_lge_p880" path="device/lge/p880" remote="github" revision="cm-12.0" />
<project name="P880-dev/android_kernel_lge_x3" path="kernel/lge/x3" remote="github" revision="cm-12.0" />
<project path="vendor/lge" name="P880-dev/proprietary_vendor_lge" revision="cm-12.0" />
<remove-project path="device/asus/fugu" name="device/asus/fugu" groups="device,fugu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/fugu-kernel" name="device/asus/fugu-kernel" groups="device,fugu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/grouper" name="device/asus/grouper" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/tilapia" name="device/asus/tilapia" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder" name="device/htc/flounder" groups="device,flounder" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder-kernel" name="device/htc/flounder-kernel" groups="device,flounder" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu" name="device/moto/shamu" groups="device,shamu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu-kernel" name="device/moto/shamu-kernel" groups="device,shamu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/samsung/manta" name="device/samsung/manta" groups="device,manta" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
</manifest>
if you run into some errors, just remove the according "remove-project" line and you should be fine

Thank you!
Thank you @laufersteppenwolf, @Demetris for all your efforts! I'll build it later, and try to help you with logs and anything else i can do, as much as i can! Keep up, mates, brilliant job!

Thanks man! I will go download sources now!

SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz

Tim_Pan said:
SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
Click to expand...
Click to collapse
SF issues should be gone, is you've got the latest sources. It was related to SELinux, which is why I completely killed it via kernel for now
Also, I highly doubt that you're gonna have much success using the stock blobs (which is why I'm not even gonna try)

I wil try building when I get home

Any News?

If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.

iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
Yeah good idea.

fritzcola said:
Any News?
Click to expand...
Click to collapse
Not really haven't got much free time lately to test...
iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.

laufersteppenwolf said:
Not really haven't got much free time lately to test...
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
No Problem
Keep up the great work.
Im sure you are going to fix it soon.:good:

laufersteppenwolf said:
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.

If anyone get a bootable Build, can he upload it!!
Thx

fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
Help us to achieve that

If i could of course i would but im sure i cant help you. My skills are very little

iSWORD14 said:
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.
Click to expand...
Click to collapse
Well, some may do that, but I am not like that I have seen just too many things happen to phones just because people didn't read and just downloaded something with the name of their device on it.
fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
The same thing as last time is going to happen: As soon as we've got a halfway working build, it will be released. Until then, there won't be a public release.
And I also ask anyone to please not publically post a build until it doesn't properly work (and by properly I mean the important things like network, audio, ... )
Alright, a general update on the situation:
SF issues are gone and we've got a boonanimation. But ATM, we are bootlooping due to audio issues.
The problem is, I have no idea what exactly is causing the issues, as the logs do not specify it (it's literally being shown as <unknown>). I was hoping that fixing the AudioWrappers would at least resolve the bootloop, but no dice.
If you want to look into it yourself, logcat and a strace from mediaserver is located HERE
Thanks to @LGaljo for the logs

News?

Busaton said:
News?
Click to expand...
Click to collapse
Dont think so

There are no news, because we keep everything private and deliberately not telling anything about the progress that have been made. :beer:

[ROM][5.1.1][6.0.1][Haxynox] AOSP for i9300

What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, dexter93 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-12-12

Reserved
Changelog
20150921-1824: Changelog: Fixed recovery issues <<-- building
20150918-1152 : initial release [5.1.1_r16]
Downloads
haxynox-6.0-i9300-20151211-2331.zip 236.6MB
33aeb6e59ec686818cd4088502b75fd1
haxynox-i9300-20150921-1824.zip 208MB
MD5:130cea4633f0e9b278aeb3def6d67d08

Reserved
GApps
For Marshmallow 6.0 Roms I recommend the PICO version of OpenGapps
http://opengapps.org/
I have tested @dankoman s GApps ZERO package with this ROM and it works fine.
Here is the link
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
If you want to use anything else, please feel free to post about your experience, but be aware that if you GApps package of choice doesn't work on this AOSP rom, you'll need to convince the GApps maintainer to take a look into it. That being said I am happy to talk with any maintainer.

mcgi5sr2 said:

What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, mcgi5sr2 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-09-21
Click to expand...
Click to collapse
^
That is what we always needed. Finnaly someone made it. THANK YOU!

Is there any screen shoots? And do we need GAPPS or is it included? I will try the rom. Thanks for taking your time to make annother ROM for our old S3

@mcgi5sr2 Hey man, I really commend you for doing this. All I've seen lately is Archi, Moster, & co.'s work (Apologies to the many unmentioned) being used as "base" for other users "projects", and of course all the real work is going on at source in the aforementioned dev's repos. I feel XDA has become a really unoriginal and user- (rather than dev-) oriented place recently.
Of course, you're not radically rewriting the fundamental Android code like the PA team did with Hybrid, but with such a ***ch of a chipset* it's pretty sick that you've taken it head-on to get AOSP up.
Sorry if this was a bit aggrandizing, I've just been tired of the constant stream of Sammy ROM ports and zip kangs.
By the way, you refer to yourself: "Ivan_Meler, mcgi5sr2 and myself", I think it should be "Ivan_Meler, dexter93 and myself"?
* "If you've ever glanced upon the sources" ... you bet you ... a glance was too much, I'm scarred ...

Thread cleaned, if you think you spotted a bug please attach logfiles and/or what you tried to fix it yourself etc.
Whiskey
Forum Moderator

Excellent, thanks for creating a thread for haxynox. Better than people posting in the slim/omni thread.

Any idea on how to fix the fact im getting bootloops on this particular rom?

I waited a long time for this! Thanks to all team :highfive::highfive:

So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??

The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
it's pure AOSP code ... without cyanogenmod 12.1 modifications.
if i understood correctly

The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.

hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply

center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?

lukewilliams418 said:
Any idea on how to fix the fact im getting bootloops on this particular rom?
Click to expand...
Click to collapse
Could you provide a little more info please?
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
No, in fact it has a lot less, but that is the point.
b0unty said:
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
Click to expand...
Click to collapse
The sources are all freely available, feel free to use them
lukaaa477 said:
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
Click to expand...
Click to collapse
see above...

myshakugan said:
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
Click to expand...
Click to collapse
Yea,sure it does,but i mean something else.
What i mean is, is there anything specific to the device changed, eg. Ram management,performance gains,optimizations etc.

mcgi5sr2 said:
Could you provide a little more info please?
No, in fact it has a lot less, but that is the point.
The sources are all freely available, feel free to use them
see above...
Click to expand...
Click to collapse
I used the latest version of TWRP to wipe all data and then I Installed the haxynox zip file with TWRP and then it just goes in a bootloop.

Bootloop
Enviado desde mi GT-I9300 mediante Tapatalk

any fix for this bootloop???

[ROM][6.0][jem] CM redux

I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07

Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)

Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!

Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages

I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.

So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.

Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.

Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.

More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.

Good version,thanks. But it often wifi reconnect , can it fix?

wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?

monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time

Android system cost battery drain more than screen, is it normal?

wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.

I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?

wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.

sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks

monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.

wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.

monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!

[WIP] TWRP Development for SM-P205 (Tab A 8.0 2019 Exynos model)

Ok, so I have been working on this for a couple of days and I wanted to update everyone on my progress. Since rooting my SM-P205, I have been working on porting TWRP to this device. I have hit a couple of roadblocks, so I am making my way through them as I encounter them. This thread will be used to update on progress as it occurs.
UNLESS YOU ARE BEING CONSTRUCTIVE AND TRYING TO ASSIST IN DEVELOPMENT, DON'T SPAM THIS THREAD. As I make developments, I will post them. No, I don't need testers, I have my own device.
Current Status: Everything builds, and it boots, but the screen just flashes repeatedly. Doing some digging to see if I can find the issue.
What have I done?
Well, I have made a device tree and posted kernel sources. The kernel sources are not 100% current, but I doubt Samsung has changed much in the kernel in a single release. Anywho, I have also tried to install the TWRP for the SM-T515, since they are literally the same device, except this one has an 8" screen and an S-Pen, but no dice; Odin just gets stuck on the file analysis. So, in the meantime, I have posted links to the repositories for what work I have done up to this point, but I am far from finished. If building from the full Omni sources fails, I guess I'll have to try Lineage (much to my dismay).
Side note, if you look at my repository and think to yourself, "gee this looks awfully similar to the repo for the SM-T515", well that's not a coincidence. As I stated earlier, they're basically the same device: same chipset, same RAM, heck even the same resolution.
Device Repository: https://github.com/eagerestwolf/android_device_samsung_wisdom/
Kernel Repository: https://github.com/eagerestwolf/andtoid_kernel_samsung_wisdom/

Status update (12/26/2019 0034 EST)
The recovery image has built successfully using the full OmniROM source. I am currently building the boot image and testing will begin shortly...maybe.
Status update (12/26/2019 0041 EST)
The boot image has built successfully, going to make the ODIN package and flash it now.
Status update (12/26/2019 0046 EST)
Does not boot...error validating footer...I think I know why, I'm pretty sure the board id is wrong in the config...gotta fix that...somehow.

Developer Information for the futurez
This device...like so many others these days is using Android Verified Boot. More importantly, it uses the Treble configuration with A/B verity under the guise of "data integrity" (we all know that Google and Samsung would love for everyone to stop rooting and installing custom ROMs).
So how does that affect me?
Well, first off. You CANNOT touch the boot partition...at all. If you do...boom Download Mode for you. Secondly, when rooting (even with TWRP) NOTHING can be installed to /system. If you do...boom Download Mode for you too. Currently, I am working to create a TWRP package with dm-verity disabled, BUT that will only allow flashing unverified images...it does NOT bypass the restrictions of Android Verified Boot...sadly. Also, the flashing process is VERY different. You have to flash two system images, so ROM installs will take twice as long...be aware.

To build TWRP for this device, you cannot use the minimal manifest. Not sure why, but it will fail on the Toybox compilation (Toybox is Google's codename for Android's implementation of SELinux). So what you need to do is sync the FULL omnirom sources (could probably also use AOSP or Lineage, I just used Omni):
Code:
repo init -u git://github.com/omnirom/android.git -b android-9.0
DON'T SYNC YET!. You need to modify some manifests first. In .repo/local_manifests/twrp.xml, add the following:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="TeamWin"
fetch="https://github.com/TeamWin"
review="https://gerrit.twrp.me" />
<!-- TWRP lives in TeamWin android-9.0 (not AOSP!) -->
<remove-project name="platform/bootable/recovery"/>
<project path="bootable/recovery" name="android_bootable_recovery" remote="TeamWin" revision="android-9.0"/>
<!-- Include external Magisk repo for repack binaries -->
<project path="external/magisk-prebuilt" name="external_magisk-prebuilt" remote="TeamWin" revision="master" />
<!-- Include TeamWin android_system_update_engine to build a good update_engine_sideload -->
<remove-project name="android_system_update_engine" />
<project path="system/update_engine" name="android_system_update_engine" remote="TeamWin" revision="android-9.0" />
</manifest>
You might as well add your device sources at this point as well. Then sync and build.

Good info, thanks. I know on the pixel 3 any system mod has to be done through magisk. No twrp available at all.
Sent from my Pixel 3 XL using Tapatalk

lafester said:
Good info, thanks. I know on the pixel 3 any system mod has to be done through magisk. No twrp available at all.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yeah, it's a pain. On this particular device, even mods installed via Magisk cause a bootloop.

Can something similar like this work on the SM-T290 model??

secretwolf98 said:
Can something similar like this work on the SM-T290 model??
Click to expand...
Click to collapse
No, sadly not. The SM-P205 (and SM-P200 [<-- the WiFi model]) is the international model, so it has the Exynos chipset. The SM-T290 and SM-T295 are US models, so they use the Qualcomm chipet. Due to the legal troubles Samsung and Qualcomm have had in the past, Samsung cannot directly sell Exynos device models in US retail locations (they can, however, still sell them online). Additionally, due to the very open nature of the Exynos chipset, I doubt the US carriers would even stock them.
EDIT:
Actually, I misread the question...sorry. So long as you can unlock the bootloader (which on most QC US models you cannot, but I may be wrong on this one), then a similar process would work yes, but you need to scope out the information for your device. The closest match, I would guess, is probably the Galaxy S10e, so I would use that as a starting point.

EagerestWolf said:
No, sadly not. The SM-P205 (and SM-P200 [<-- the WiFi model]) is the international model, so it has the Exynos chipset. The SM-T290 and SM-T295 are US models, so they use the Qualcomm chipet. Due to the legal troubles Samsung and Qualcomm have had in the past, Samsung cannot directly sell Exynos device models in US retail locations (they can, however, still sell them online). Additionally, due to the very open nature of the Exynos chipset, I doubt the US carriers would even stock them.
EDIT:
Actually, I misread the question...sorry. So long as you can unlock the bootloader (which on most QC US models you cannot, but I may be wrong on this one), then a similar process would work yes, but you need to scope out the information for your device. The closest match, I would guess, is probably the Galaxy S10e, so I would use that as a starting point.
Click to expand...
Click to collapse
Ok, thank you for that information. You said the US can't sell exynos chips, Walmart in the US currently has the SM-T510 model with exynos?? That was in the store, I saw it my self.

secretwolf98 said:
Ok, thank you for that information. You said the US can't sell exynos chips, Walmart in the US currently has the SM-T510 model with exynos?? That was in the store, I saw it my self.
Click to expand...
Click to collapse
That may have changed then. Samsung may now be paying Qualcomm for a license. There was a patent infringement lawsuit involving those two a couple of years ago, so idk. I do know that the SM-T290 is a Qualcomm device though.

Any updates for the project? I've been waiting to get a proper twrp and root this device. I hope anyone gets to make it soon.

Been wanting to see updates for this too. Any progress?

is the project dead?

Thread closed.

[DISCONTINUED][A11] Exthm-UI for Sofiar

THIS ROM IS DISCONTINUED. LEAVING IT UP FOR ARCHIVAL PURPOSES.
As usual, you and you ALONE are responsible for what you do with your device. If something goes wrong by flashing this mod or any other mods, don't blame it on the dev.My buddy just told me about this ROM that was Touhou based so I was like "oh god yes I gotta port this ASAP". This is my first ROM I've built in a while. Built it and rushed here really quick to make a post about it so maybe I can score some juicy Internet Points.
What is exthm-UI:
It's a combination of Lineage and ArrowOS features with Touhou based themes on it. So if you like AOSP and want your bullet-hell waifus loaded by default, this may be the ROM for you.
What works:
Identical to Lineage 18.1 since it was made with those trees
What doesn't work:
AudioFX not included, because I hate that thing
Terminal app not included, it was giving me build errors that I couldn't get around
Default browser (Via browser) seems to be in Chinese, just have F-Droid or something handy so you can install it right away and get another browser
Charging LED doesn't work, even if you enable the light to come on while plugged in it still wont (but the LED itself works for other things)
You tell me
Source Code:
ROM Source: https://github.com/exthmui
Roomservice manifest (device tree, kernel tree, vendor tree can all be found in here): https://pastebin.com/XGE185jY
Kernel source alone: https://github.com/S4muel007/kernel_motorola_trinket
You'll want to delete the highlighted line in the following file before you build: LINK HERE
You'll want to delete Terminal (and probably AudioFX too because it sucks) in packages/apps/ before building
Screenshots:

does the status bar hovers over the punch hole camera on rav variant? it annoyed me so much on other ROMs

LOLCATpl said:
does the status bar hovers over the punch hole camera on rav variant? it annoyed me so much on other ROMs
Click to expand...
Click to collapse
Yes the status bar is over the camera hole, but the icons go next to it

Abandoning this thread. Literally one freakin' week after I build this, the GitHub repo goes into read only and the project is abandoned. Jeez, talk about bad luck.

Previously, this ROM just dropped support for Android 11. Now I found out that the entire ROM is dead altogether.
And yes, I am still running this by the way (as of writing this post). I was waiting for A12 or A13 to finally upgrade, and now it looks like we have that.
Anyway, this was probably the last device that was ever ported to this ROM... spooky!

jasonmerc said:
Previously, this ROM just dropped support for Android 11. Now I found out that the entire ROM is dead altogether.
And yes, I am still running this by the way (as of writing this post). I was waiting for A12 or A13 to finally upgrade, and now it looks like we have that.
Anyway, this was probably the last device that was ever ported to this ROM... spooky!
Click to expand...
Click to collapse
so you do have an a12 or 13 rom?

spiral777 said:
so you do have an a12 or 13 rom?
Click to expand...
Click to collapse
Nope

Database Develop

welcome