Database Info

[ROM][DEV]Pre-Alpha CM10 for Spice Stellar Mi-425

Cyanogenmod 10.1
​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
How To Flash
​
Place ROM onto phone storage
Reboot to recovery
Make a Nandroid Backup
Install Rom: Wipe INSIDE ROM
Install Gapps
Reboot!
Click to expand...
Click to collapse
Disclaimer
This is a Pre-Alpha and does not boot.I am not responsible for any damage done to your phone.

Thread Closed

How to keep Unofficial Temasek 6.0.1 roms updated

As probably most of you know, @temasek has "left the building". Since I'm currently support his ROM for some devices, I decided to "fork" all temasek repos on github and continue his work.
If anyone want to keep temasek ROMs updated, you can use my repositories to continue build updated ROMs.
Here is all you need -> https://github.com/FSadino/android
Feel free to use my repos, you don't need to ask any permission for that, just give proper credits on your threads.
Let's keep this developer "awake" on XDA

[Unoffical] Xenon-Hd Android 8 Build Out

What is XenonHD?
XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 15.0 with additional features, performance and battery life improvements.
The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".
MAIN FEATURES :
XenonHD Changelog
NovaLauncher, Adaway, Kernel Adiutor, SuperSU
Root, adb, dev options, advanced reboot & installing apks enabled by default
Pixel UI, Pixel Navbar + Animation, Wallpaper
Material sounds & icons
Day/Night theme
Network indicator & battery bar in status bar
Live Volume Steps
DT2S on lockscreen
Custom Quick Settings Tiles
Removed unnecessary things
Under the hood improvements and optimizations
...and more on the way!
BUG :
Volte
HOW TO FLASH
Install latest TWRP recovery on your device.
Make a backup of your current ROM.
Wipe system, data, cache and dalvik.
Flash ROM.zip and Googleapps.zip.
Reboot system and setup!
Download :https://drive.google.com/file/d/0B72tZGCxrlDicjJHWG0wV3VLdWM/view?usp=sharing
CREDITS
Team Horizon and Xenon HD Team for the rom source
@[email protected]
XDA:DevDB Information
[Unoffical] Xenon-Hd Android 8 Build, ROM for the Xiaomi Redmi Note 4
Contributors
ZH_Alone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Beta
Current Beta Version: V 1.0
Beta Release Date: 2017-10-07
Created 2017-10-07
Last Updated 2017-10-07

Thanks for your work. Definitely going to test it now. Just one thing : you forgot to add a space after the ":" so the link is not clickable

Remove it please. We didn't allow to release oreo builds and mido will be officially supported anyway

dadi11 said:
Remove it please. We didn't allow to release oreo builds and mido will be officially supported anyway
Click to expand...
Click to collapse

thanks for sharing but please remove it. if anyone is to build oreo based xenon hd, it' s @dadi11 not you or anyone else. He is the official maintainer and developer and no one builds it better than he does. So, keep it for yourself and delete your post please.

Wait so bug is only Volte??
How about goodix fp???

jack_hunter97 said:
Wait so bug is only Volte??
How about goodix fp???
Click to expand...
Click to collapse
Please read #3 : https://forum.xda-developers.com/showpost.php?p=74067496&postcount=3

No link?

Thread closed
First NO placeholders are allowed. All ROM threads must have a download link at time of posting
Second always seek permission to build and post someone else's work as per rule 12 the developer can request take down:
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!

[DEV DISCUSSION] Let's fix the device tree

We all know that device trees which are available for Tissot is currently buggy. And no matter if we compile Resurrection Remix, Dot OS, Lineage OS or any other custom rom, we'll definitely have the same bugs present.
If all the developers work alone, then it'll take a lot of time to fix all the bugs. So, let's collaborate & work together.
To start with, I'm dropping the links for my tree:
Device Tree: https://github.com/ghpranav/android_device_xiaomi_tissot
Kernel Source: https://github.com/ghpranav/android_kernel_xiaomi_tissot
Vendor Blobs: https://github.com/ghpranav/android_vendor_xiaomi_tissot

ghpranav said:
We all know that device trees which are available for Tissot is currently buggy. And no matter if we compile Resurrection Remix, Dot OS, Lineage OS or any other custom rom, we'll definitely have the same bugs present.
If all the developers work alone, then it'll take a lot of time to fix all the bugs. So, let's collaborate & work together.
To start with, I'm dropping the links for my tree:
Device Tree: https://github.com/ghpranav/android_device_xiaomi_tissot
Kernel Source: https://github.com/ghpranav/android_kernel_xiaomi_tissot
Vendor Blobs: https://github.com/ghpranav/android_vendor_xiaomi_tissot
Click to expand...
Click to collapse
I am already fixing bugs in lineage. Base build will be out soon

Guys many thanks for your efforts. Great to know that someone is working hard on this stuff!

Good job. Hope we see collaboration and some great team activity. Unified tree from where the community can reap benefits. Hope this works for all and if not all, most developers contribute to this base plan.

Thank you for doing this, i hope we have a good kernel soon

Thanks devs, u guys rock! Wish u all the best ?

Hope i can understanding about building ROM.
So i can help you guys, but i not understand

Wow xiaomi should something from you guys ... Great work devs ... You guys are always here to make our Android experience great..

Wow! thank you so much for your efforts!

If tree is stable I will contribute
I am waiting for stable tree only
Hope it will be stable soon

arunassain said:
If tree is stable I will contribute
I am waiting for stable tree only
Hope it will be stable soon
Click to expand...
Click to collapse
Than you may want to check out the device tree from the unofficial lineage os 14.1 by deadman96385. He has a booting LOs with minor bugs. probably others can also contribute as that is the only functional build.

How to make a ROM compatible?

Good morning, I have a Samsung Galaxy s5, I would like to change the ROM for carbonROM cr-9.0 (if I am not mistaken, it is the latest version), I currently have lineageOS 18.1, the problem is that there is currently no updated carbonROM support for my device So, I would like to know how I can adapt a ROM to be compatible with my device, I understand that it is something that requires work, but I want to know the steps that I should follow to be able to adapt a ROM, things to keep in mind, that programs to use, useful links, all the information you can give me, I would greatly appreciate it.

Martin19941994 said:
Good morning, I have a Samsung Galaxy s5, I would like to change the ROM for carbonROM cr-9.0 (if I am not mistaken, it is the latest version), I currently have lineageOS 18.1, the problem is that there is currently no updated carbonROM support for my device So, I would like to know how I can adapt a ROM to be compatible with my device, I understand that it is something that requires work, but I want to know the steps that I should follow to be able to adapt a ROM, things to keep in mind, that programs to use, useful links, all the information you can give me, I would greatly appreciate it.
Click to expand...
Click to collapse
You would have to build your own ROM using a mixture of the updated Lineage 18.1 ROM or the Lineage source code that it was built from and the carbonROM ROM or the carbonROM source code that was used to build your current carbonROM.
If you don't know how to build from source, you will have to try porting the carbonROM by mixing elements of the carbonROM and the LineageOS ROM. There are guides available that give a "rough" outline of how to port Samsung ROMs.
You can find guides and videos by doing a Google search for:
"How to port Samsung custom ROMs"
That should find some results but none of them are complete 100% start to finish guaranteed to work. It will require doing some research, reading, asking questions when you run into roadblocks along with a lot of trial and error testing and fixing mistakes along the way until you get a working generally bug free ROM.
All in all, you're probably better off just using the LineageOS 18.1 that you currently have.