SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Unofficial Downloads J500F and M - Build0.13
Unofficial Downloads J500FN - Build0.13
For information on bugs, requirements, notes and more, read the second post.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
Can you pour me some coffee?
XDA:DevDB Information
SlimRoms Slim7 Android Nougat, ROM for the Samsung Galaxy J5
Contributors
EsromG5
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader LP and Modem MM (modem mm for FM works)
Based On: Aosp, Slim
Version Information
Status: Testing
Current Beta Version: Build0.13
Beta Release Date: 2017-02-15
Created 2017-02-15
Last Updated 2017-03-04
Reserved
What works?
RIL (Calls, sms, data)
Bluetooth (also with audio)
Camcorder
Camera general (1080p works fine)
Video Playback
Dados and RIL
Wifi
Audio
Sensors
LED
Flash
Hostpot
InCall
GPS
OTG
FM (use modem MM)
What does not work?
No, you tell me
Notice:
n/a
First
Good job, waiting for FN
second ....
good job bro.. i m so lucky that I own j5f :fingers-crossed:
wooow j5 developement is skyrocking this month, i will install it when theres the proper incall audio (im not crying for fix, just sayin)
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Booted on FN, but System UI has stopped
Telepracity said:
Booted on FN, but System UI has stopped
Click to expand...
Click to collapse
Without patch?
Deleted
JosephDM said:
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Click to expand...
Click to collapse
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
EsromG5 said:
Without patch?
Click to expand...
Click to collapse
With a patch from lineage os
MM kernel
Amarius1 said:
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
Click to expand...
Click to collapse
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
I didn't mean in call audio. I meant this ROM doesn't even boot normally and they have no clue why, yet instead of trying to debug they release bunch of not working builds. Camera doesn't work and it will not work since you'd either have to use updated open source HAL or revert Nougat media changes and it won't be a surprise if I'll tell you they have no idea how to do it. The only real devs, who knew what they were doing left because their work was posted by someone else and now he's making blind commits in hope that things will magically fix themself. They won't. I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in. Don't expect any significant changes. We can't even take patches from any other msm8916 devices, because they have more advanced development and use a lot of open source projects instead of prebuilt libs like we do. Even camera in CM13 is not fully fixed because open source cam doesn't work for us and after debugging it for 3 weeks I've still didn't come up with reliable solution to make it work (only made some errors dissapear).
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
The name of the forum is XDA - DEVELOPERS, this means that it is of full use to developers, if the person does not know how to help, it just stays silent while someone else can do it. Your help in testing is much appreciated since we are trying to do something free for you, and still prefer to say things like that.
I thank you and respect your concept, but try to help instead.
Amarius1 said:
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
Click to expand...
Click to collapse
The problem with incall and other stuff is already encountered by SoUnd001, but the big problem is that we're not hitting what it does so it's not booted, you're getting errors with incall and stuff because of the patch you're installing, not because of Rom or current kernel.
NOTICE:
I'm finishing a build for J500FN, we know it may not start properly, but I want to know the result for these users. I hope the sooner I have it all working.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Considering our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
Click to expand...
Click to collapse
I think there will not be an official nougat firmware from Samsung.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
In the Skies telegram group there was confirmation for official Nougat
EsromG5 said:
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
Click to expand...
Click to collapse
FYI: ALL custom ROM are using the same hardware repo's maintained by CAF, CM(Lineage now) or AOSP. There won't be any different results. The most important repos are all the same. The fact that you don't know that and your friend's github sources show that there is nothing to be helped. You're just playing games with users pretending you could make things work. What for? In the end they will be the ones left with nothing but promises. People, who could actually do something left, because someone took their work and published it to take all the applause for it and now you're blindly trying changes hoping they would somehow fix things.
[email protected]@!3Z said:
Considering that they have built nougat from source
Click to expand...
Click to collapse
They built from the source already made by ganesh. Their own changes are blindly trying things that have no right to work in the first place. Builiding android from someone's ready sources is like walk in a park.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
Certainly not for J5 2015, maybe 2016 but it could benefit us anyway since these devices are similiar.
I'm done, Moderator will probably soon come and delete my posts since all they care about is keeping forum clean. You may consider this device dead at the moment.
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs.
Click to expand...
Click to collapse
I understand from your post that Sound001 or EsromG5 did the hard work, but its not like that.
@Nick Verse and @ganesh varma were the ones who built cm12.1 and cm13 from source. They were also working on cm14 source while they were working on cm13.
So, please edit your post and dont mislead people.
Koloses said everything.
Since Nick and Ganesh left J5 development because their project which were working on was posted by someone else, the issues of Nougat CM/AOSP based roms wont be solved.
This:
I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in.
Click to expand...
Click to collapse
Related
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.
All the blah blah about "as is", you being responsible for what you choose to do and do to your device, no guarantees implied nor stated... And all the usual to install. I wont be paying much attention to bugs, however, PLEASE post them as you find them to let others know what they can expect.
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
Of course, thanks to the crDroid team for providing the ROM source itself; and making it so easy to build using LineageOS device trees.:good:
Changes from the default source:
Code:
[FONT="Verdana"] Added the MiXplorer [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
I got the OK first too include in my unofficial ROMs that I build, visit the forum, they are very helpful for this VERY powerful file explorer. [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
You can thank @HootanParsa for building it, and letting me include it:good: Be sure to share some thanks.
Switched over to the ResurrectionRemox launcher. I had issues with the default launcher in crDroid. Also on another device, and I think I have read some other users had the same on even more devices.
Vinyl Music Player and removed crDroid music.
It has more features but is based off the same original app in crDroid. Including a dark theme!
Just to be polite I checked with the dev to get his ok, even though its open source. It can also be fund on F-Droid
OmniClock replaces the standard deskclock. Sourced from OmniROM, so a big thanks to them. It has a nicer dark skinn also.
[/FONT]
I have only done a rudimentary test on it. I flashed PICO Gapps, and there aint much room left in the system partition.
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
You can download this build, and flash at your own risk, from:
crDroidAndroid-8.1-20180614-hammerhead-v4.4-DiamondJohnDroid.zip
MD5: 25e05c3f02d34968f308ac6b4ad32b8b
Thanks a bunch, I am eager to test this out and will update once I get a chance.
Good news, love crdroid rom, downloading. , thanks
Thank you so much for taking this project, I'm waiting for updates
Greetings
Krizthian said:
Thank you so much for taking this project, I'm waiting for updates
Click to expand...
Click to collapse
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
DiamondJohn said:
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
...snip....
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
...snip....
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Click to expand...
Click to collapse
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
DiamondJohn said:
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
Click to expand...
Click to collapse
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
4.4 is working like a champ here. Many thanks. Tried to install ElementalX 9.02 but it wouldn't take. Will investigate further soon.
Galaxyninja66 said:
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
Click to expand...
Click to collapse
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
DiamondJohn said:
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
Click to expand...
Click to collapse
Hmmm... messed up Nexus 5 you say... maybe we can trade mother boards via mail?
eh who am I kidding my Nexus 5 is worthless to me, the modem still works making it's purpose as a backup phone fulfilled
Thank you so much!!!!!!
@DiamondJohn : thanks man
4.5 will be?
see post https://forum.xda-developers.com/showpost.php?p=77301143&postcount=50
OP request.
THREAD CLOSED
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
Pixel Experience ROM for the Galaxy Note9
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Click to expand...
Click to collapse
This it not a GSI. It is built on actual device trees
What's working/not working?
First up:
-Sometimes after setting the brightness to maximum, it doesn't want to lower its value and gets stuck. is fixed only by a reboot.
-HWC is disabled
-The signalbar always shows 0, altho calling and data have no issue and should work as intended.
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS Pixel Experience. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS PixelExperience.
Click to expand...
Click to collapse
Instructions:
Make sure TWRP has been installed and functional.
Make sure you are on the CSA2 based vendor and fw
Download the latest build linked below
Reboot to recovery
Wipe system, data and cache from the wipe menu
Flash the rom zip(and gapps). DONT flash gapps. they are already included in the rom.
(optionally) flash magisk
Reboot and enjoy :victory:
Downloads:
20.02.2019 NOTE9 build
NOTE9 CSA2 VENDOR
Providing feedback:
You are more than welcome to provide any kind of feedback here.
(limited only to feature requests; it's called "pixel experience" for a reason and it should stay that way)
You can also msg me anytime on telegram @ Rainbow_Alex_Dash
Telegram group?
HERE
Changelog:
20.02.2019
Initial build
Troubleshooting/FAQ:
Q: Videos aren't playing on youtube
A: Make sure you don't have any kind of adblock installed
Q: I'm on a dualsim variant and (a) sim isn't detected.
A: Try reinserting your sim and rebooting. This wierdly nuff only happens on some* dualsim variants and no one has sent me a logcat yet.
Q: My mobile data (3G/4G) is not working/only 3g shows
A: Go into mobile network settings and select/create an apn, also select 4G as the preferred network type.
Q: How does this compare to GSIS?
A: Much better all around. Faster,smoother etc. I don't think there's any reasons to use pie gsis anymore.
Q: How good is the camera?
A: Actually,(by my standards), pretty good. Almost comparable to stock. Ofc the aosp cam doesn't have the fancy filtering, features and stuff but by far not bad. Alot better than 8.1 roms anyway.
Q: Safetynet doesn't pass?
A: Yeah, i guess that's a thing. Go into magisk and download some module called props hide or something. Don't forget to run it from terminal. It should work from there
Q: The rom isn't booting/camera doesn't work
A: Flash/make sure you have the CSA2 vendor and fw, and try again. This has been tested. It's prolly something on ur end.
Q: The rom is in a bootloop/google apps keep crashing
A: You did read the instructions and NOT flash any gapps riighhttt?? smh, wipe /system,/data and /cache and start over
Q: I have another bug; How can i tell it to you while slightly increasing my changes of it ever getting fixed.
A: You can tell me what's going on either here or on telegram WITH A LOGCAT attached(required);if rom isn't booting at all attach /proc/last_kmsg.
Q: I don't know what/how to logcat. Is it really necessary?
A: Logcat or gtfo
Q: How can i support you?
A: Awwww thanks; On most of my posts on the left side there's a "donate to me" paypal button;. Send the seal some fish. Seriously. The seal realllyyyyy loves fish. You can do that,donations are more than welcome, or if you don't have any $ to spare you can also post here about how awesome i am (this surprisingly helps very much)
Credits:
BIG thankies to @Ivan_Meler. He was at the center of all of this, and he single handedly did the pie bringup
Jesec for the initial trees
@Vaughnell for major contributions in the note9 bringup from the original s9 trees.
The pixel experience team for creating the rom we so do enjoy
Many good people from the telegram group (linked above) that helped me create this project and spamming for etas
XDA:DevDB Information
PixelExperience 9.0, ROM for the Samsung Galaxy Note 9
Contributors
Rainbow_Dash, Ivan_Meler,jesec
Source Code: [url]http://github.com/rainbowdashh[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: CSA2 pie vendor and fw
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2019-02-20
Created 2019-02-20
Last Updated 2019-02-21
reserved
also full disclosure: i don't own a note9, nor am i sure how much i'm interested in maintaining it, so take this as-is
Rainbow_Dash said:
also full disclosure: i don't own a note9, nor am i sure how much i'm interested in maintaining it, so take this as-is
Click to expand...
Click to collapse
Note 9 users should be very glad that although there are basically no aosp devs left for their device they still got a build. Maybe if you guys give Alex some beers he might get motivated for you crownlte guys
thank u
Everything works so far. Will report if I find any issues. Nice work brotha
Always wanted to try a Pixel Experience ROM but I keep getting turned off by the Camera
Hot damn! We got a live one! Thank you for giving us some AOSP goodness, was beginning to wonder if it would ever come.
Do you think we'll see more AOSP ROMs start to pop up for the Note 9?
PieceofSlice said:
Hot damn! We got a live one! Thank you for giving us some AOSP goodness, was beginning to wonder if it would ever come.
Do you think we'll see more AOSP ROMs start to pop up for the Note 9?
Click to expand...
Click to collapse
Mmmmmperhaps
aussiesausage said:
Always wanted to try a Pixel Experience ROM but I keep getting turned off by the Camera
Click to expand...
Click to collapse
Eh, it's not bad at all, but that's subjective and something you have to try yourself
Rainbow_Dash said:
Eh, it's not bad at all, but that's subjective and something you have to try yourself
Click to expand...
Click to collapse
Does it keep up with the stock camera or gcam port even?
This is the moment I wonder what's more important - warranty or geek happiness...
awesome
glad this isn't GSI though i had no problem with GSI roms
Rom working great beside the known bugs. Sadly hwc isnt working, on the s9 forum they also cant get it working sadly. Google camera works great for the people thinking of switching. Battery life is just very bad because of no hwc. Gsi roms are very stable with endurance kernel.
Good to see your work over here , I been tested so far very good on stable initial release
Great rom! Must have!
Thanks to the xda writers for this making it to the news section.
Dear Ranibow_Dash
May I ask you about the boot animation?
Is this rom using zips for boot animation?
If so is there a way to get it to work on a stock rom as well?
Sent from my SM-N960N using XDA Labs
Rainbow_Dash said:
Thanks to the xda writers for this making it to the news section.
Click to expand...
Click to collapse
Sir iris scanur and jio volte not work! plis fix!
malinathani said:
Sir iris scanur and jio volte not work! plis fix!
Click to expand...
Click to collapse
Sar u need to plug unplug wallplug re?️lug sim, wipe efs,reflash baseband ez uuart force enable hardwear flash tab s3 ?️ootloader thanks to iqbal sareem credits to iqbal sareem
/s
We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Device-specific issues
Logcat gets spammed by gralloc errors
Note: Custom kernels are NOT supported! It already comes with LunarKernel.
Downloads
Downloads (from Drive)
TWRP (download 3.4)
GApps already included, don't click on this link
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them.
Paranoid Android Quartz released
Instructions
Reboot to bootloader
Boot into TWRP recovery via fastboot
Code:
fastboot boot twrp-3.4.0-0-marlin.img
Wipe data
Flash the ROM (no need for GApps since they're included)
(Optional) Reboot bootloader, boot TWRP again, and flash any addons you want.
Reboot to the system
Important/Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Help us improve PA by submitting detailed bug reports with logs. Learn how to take logs here.
Send the logs to me, as this is a unofficial build.
Here's the various sources used for this ROM (feel free to fix stuff):
Kernel source (for GPL compliance): https://github.com/Lunarixus/LunarKernel-marlin
The rest (contains locations for all the device-specific sources required to build PA): https://github.com/yagyaxt1034/android_vendor_pa/blob/quartz/products/marlin/pa.dependencies
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android Quartz for Pixel and Pixel XL, ROM for the Google Pixel XL
Contributors
yagyaxt1068, Lunarixus, spezi77, AOSPA team, PixelDust-CAF, Qualcomm Android for MSM, probably a bit of Lineage in there somewhere, you get the idea.
Source Code: https://github.com/yagyaxt1034/android_vendor_pa
ROM OS Version: Android 10
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Latest 10 bootloader and radio
Based On: CAF
Version Information
Status: Testing
Current Beta Version: 5
Beta Release Date: 2020-08-17
Created 2020-08-18
Last Updated 2020-08-27
Thanks for bringing PA to our device. The install went perfectly, but setup kept asking me to insert my SIM card. I have Verizon. I was able to connect to WiFi, but couldn't get it to recognize the mobile network. I did try turning airplane mode on and off, but no luck.
beeewell said:
Thanks for bringing PA to our device. The install went perfectly, but setup kept asking me to insert my SIM card. I have Verizon. I was able to connect to WiFi, but couldn't get it to recognize the mobile network. I did try turning airplane mode on and off, but no luck.
Click to expand...
Click to collapse
Oh sorry, that's my bad. I accidentally forgot to switch to AOSP's RIL, as CAF RIL will not work. I'll fix it and upload a new build soon.
Same here, will wait, thanks for the fix in advance:good:
yagyaxt1068 said:
{Mod edit: Quoted OP shortened for better reading experience!}
Click to expand...
Click to collapse
Usually when I flash other rom I copied the rom zip to internal storage. In twrp I wiped system/data/delvik and flash the rom but here the instructions is different. could you plz elaborate I am newbie
imna357 said:
Same here, will wait, thanks for the fix in advance:good:
Click to expand...
Click to collapse
I've pushed an updated build with fixed RIL. Try it out.
bhaskarjyotisarmah51 said:
Usually when I flash other rom I copied the rom zip to internal storage. In twrp I wiped system/data/delvik and flash the rom but here the instructions is different. could you plz elaborate I am newbie
Click to expand...
Click to collapse
Most ROM instructions usually tell you to wipe /system, but this is not actually necessary on Pixels, since there's an A/B setup, so that's up to you whether you want to wipe system. I usually don't. And a factory reset should wipe both /data and dalvik, so that's not too hard.
The mobile network fix worked !! Good Job.
I'm getting Carrier Provisioning Service force close. I sent you a PM with a link to a logfile and hope you can read it.
A feature I'd love to see in future builds is Volume Steps.
Again, Thanks for your work here.
No bells and whistles but fast and smooth as to be expected
from PARANOID ANDROID brilliant thanks love it ?.
Excited to install again once it becomes stable
Apps take over the screen and I am not able to access screen buttons. I love that it is a CAF ROM.
cranialbug13 said:
Apps take over the screen and I am not able to access screen buttons. I love that it is a CAF ROM.
Click to expand...
Click to collapse
Sounds like a hostage situation intriguing very very intriguing ?.
You gave the wrong zip for sailfish, it's actually marlin.
Hey there!
Can we expect an Android 11 build in the future? That would be amazing! :fingers-crossed:
Help The Peace said:
Hey there!
Can we expect an Android 11 build in the future? That would be amazing! :fingers-crossed:
Click to expand...
Click to collapse
I'll try it once 11 is available for marlin and PA updates to it.
As the description says pixel and pixel xl ..just wanted to be sure if it would actually work in sailfish cause there's no such thread for this rom in sailfish.please reply
shtma said:
As the description says pixel and pixel xl ..just wanted to be sure if it would actually work in sailfish cause there's no such thread for this rom in sailfish.please reply
Click to expand...
Click to collapse
Unfortunately, the sailfish build didn't work right, so it's only on marlin for now. However, I'll come back to building PA on 11.
yagyaxt1068 said:
Unfortunately, the sailfish build didn't work right, so it's only on marlin for now. However, I'll come back to building PA on 11.
Click to expand...
Click to collapse
I see. It would be nice if in the future we're going to see other builds for sailfish/marlin. (official ones would be really awesome)