Related
What does it take for a ROM to move from unofficial to official or is that not how it works? For example, I run cm11 official because its official. I would like to run cm12 but it says unofficial.
Sent from my LG-VS985 using XDA Free mobile app
Someone can correct me if I'm wrong.. But... Unofficial is usually when someone compiles the build themselves and share. They sometimes add commits that have not been merged into official builds. Sometimes add add-ons that may not be supported in official builds. Sometimes a dev team may not have a maintainer for a specific official build. Most times unofficial builds aren't always as dependant as official. Sometimes they can be better.
As for CM 12. It went official last night. They are nightly builds, but they are official now. The thread is in the original development section. You can go to the CM site and it shows all the official 11 builds and then starting with 1/6 it is now on official 12 nightly. Hope that helps. ?
Just to clarify. The official CM11 thread is where to go for more info right now. Sure they will probably start a new one soon, but the link still takes you to CM and the latest build is the CM 12 from today 1/6. http://download.cyanogenmod.org/?device=vs985&type=nightly
*** 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.
Hello,
@sir_bazz mentioned that this needed its own thread, thus I'm creating one.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
Deb is at https://lineageos.disavowed.jp/deb/. Flo is at https://lineageos.disavowed.jp/flo/. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Have been testing the latest weekly for a couple of days now, and no issues to report.
My Deb device is relegated to a dedicated Pogo tablet and I think Lineage 14.1 is a better match for my use as there's noteably more memory available after system startup than with the Pie ROMs I've tested.
It just feels much smoother.
Would've been more than happy with monthly updates but thanks for building the ROM and also making weeklies available for us Nexus 7 diehards.
sir_bazz said:
Have been testing the latest weekly for a couple of days now, and no issues to report.
My Deb device is relegated to a dedicated Pogo tablet and I think Lineage 14.1 is a better match for my use as there's noteably more memory available after system startup than with the Pie ROMs I've tested.
It just feels much smoother.
Would've been more than happy with monthly updates but thanks for building the ROM and also making weeklies available for us Nexus 7 diehards.
Click to expand...
Click to collapse
Likewise. I was just about to junk a (relatively) new N7 (flo) on stock MM. but wanted to give a newer ROM a try (Oreo). I didn't like my O options and stumbled upon these N builds on the backend of another thread. Flashed/Magisk couple Mods. Been up a week now and not one problem whatsoever!
Really appreciate the work as this ROM (I had never used a LinOS rom before) is running so well the N7 is almost my daily house driver again. The N7 FF really has never been matched/surpassed and once you've become accustomed to it its just hard to give up that "sweet spot".
wileyc said:
Hello,
@sir_bazz mentioned that this needed its own thread, thus I'm creating one.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
Deb is at https://lineageos.disavowed.jp/deb/. Flo is at https://lineageos.disavowed.jp/flo/. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Click to expand...
Click to collapse
Hi, I've just updated both my Hammerhead 15.1 and Flo 14.1. Everything has gone smoothly and all is working. I was just hoping you could clarify something that occurred to me regarding the builds.
When you say there are no modifications, does that mean that the basic ROM is frozen at the point when LineageOS stopped releasing official builds, and does that also mean that builds in between the monthly security updates are all the same or can there be other security/bug fixing updates from LineageOS? Also Lineage 15 was never official for the Nexus 5 or 7? I'm a bit in the dark as to how these things work.
Thanks in advance.
anivegmin said:
Hi, I've just updated both my Hammerhead 15.1 and Flo 14.1. Everything has gone smoothly and all is working. I was just hoping you could clarify something that occurred to me regarding the builds.
When you say there are no modifications, does that mean that the basic ROM is frozen at the point when LineageOS stopped releasing official builds, and does that also mean that builds in between the monthly security updates are all the same or can there be other security/bug fixing updates from LineageOS? Also Lineage 15 was never official for the Nexus 5 or 7? I'm a bit in the dark as to how these things work.
Thanks in advance.
Click to expand...
Click to collapse
No worries. By "no modifications", I mean that these are built directly from a clone of the LineageOS repository. I've made absolutely no changes to the source code. No kernel tweaks, no new features, no hidden spyware, no bugfixes (no matter how much I am tempted to do so!).
The LineageOS folks merge the monthly Google security patches into the 14.1 and 15.1 trees, but they don't make official builds for devices that no longer have a maintainer. Their official recommendation is to build it yourself if you want to keep your devices patched, but a non-trivial number of users can't make their own builds, so ...
... since I'm doing builds for my own devices anyway, it would be a good thing to make them available to others. Thus I have done so
Edit: argh, rereading I realize I didn't directly answer your exact question. From an end-user perspective, these builds are indeed frozen in time compared to the last official LineageOS build. Security patches happen as described above.
The Nexus 7 never received an official 15.1 build as far as I can tell, so I'm generating 14.1 for it.
The Nexus 5 is a bit of a grey area, in that builds generated from the 15.1 branch work fine with the exception of Bluetooth (from what I hear, as I don't use Bluetooth on my device). It appears to require a device repartition if you want to use Google apps, though, so I'm building both 14.1 and 15.1 to keep options option.
wileyc said:
No worries. By "no modifications", I mean that these are built directly from a clone of the LineageOS repository. I've made absolutely no changes to the source code. No kernel tweaks, no new features, no hidden spyware, no bugfixes (no matter how much I am tempted to do so!).
The LineageOS folks merge the monthly Google security patches into the 14.1 and 15.1 trees, but they don't make official builds for devices that no longer have a maintainer. Their official recommendation is to build it yourself if you want to keep your devices patched, but a non-trivial number of users can't make their own builds, so ...
... since I'm doing builds for my own devices anyway, it would be a good thing to make them available to others. Thus I have done so
Edit: argh, rereading I realize I didn't directly answer your exact question. From an end-user perspective, these builds are indeed frozen in time compared to the last official LineageOS build. Security patches happen as described above.
The Nexus 7 never received an official 15.1 build as far as I can tell, so I'm generating 14.1 for it.
The Nexus 5 is a bit of a grey area, in that builds generated from the 15.1 branch work fine with the exception of Bluetooth (from what I hear, as I don't use Bluetooth on my device). It appears to require a device repartition if you want to use Google apps, though, so I'm building both 14.1 and 15.1 to keep options option.
Click to expand...
Click to collapse
OK. Thanks for the explanation. Sorry to ask again, but does that mean that I only have to update once a month for the security updates, and that the other weekly builds are basically just repeats? Or am I misunderstanding?
anivegmin said:
OK. Thanks for the explanation. Sorry to ask again, but does that mean that I only have to update once a month for the security updates, and that the other weekly builds are basically just repeats? Or am I misunderstanding?
Click to expand...
Click to collapse
They're repeats. I'm doing them weekly to reduce the amount of time between the security patch hitting the tree and having a patched build available.
wileyc said:
They're repeats. I'm doing them weekly to reduce the amount of time between the security patch hitting the tree and having a patched build available.
Click to expand...
Click to collapse
OK. That's clear now. Thanks for your time.
smw6230 said:
I was just about to junk a (relatively) new N7 (flo) on stock MM
(...)
the N7 is almost my daily house driver again. The N7 FF really has never been matched/surpassed and once you've become accustomed to it its just hard to give up that "sweet spot".
Click to expand...
Click to collapse
Outstanding. That is exactly the reason why I'm making these builds. There's no reason to trash perfectly good hardware. Kudos to the LineageOS folks for keeping the tree patched -- the only thing missing were, um, actual builds.
Hi !
Thank you for your LOS 14.1 updating release, but I have error 7 with TWRP when I try flash it.
arkansis said:
Hi !
Thank you for your LOS 14.1 updating release, but I have error 7 with TWRP when I try flash it.
Click to expand...
Click to collapse
Make certain you're flashing the correct image. Boot into the bootloader and verify that the platform is the same as the build variant you are flashing. Good luck.
Thank you so much for this @wileyc , is possible to add 15.1 for flo?
Enviado desde mi Nexus 7 mediante Tapatalk
Thank you so much for keeping 14.1 alive!!!
DorianX said:
Thank you so much for this @wileyc , is possible to add 15.1 for flo?
Click to expand...
Click to collapse
I'm afraid not. These are built from unmodified LineageOS source repo; I'm just providing sustaining builds, not doing new development/porting.
Thank you for these!! This rom runs perfect on the FLO. I hope you continue the updates for a long time!!
wileyc said:
There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
Click to expand...
Click to collapse
Good day sir, would you consider adding to the roster and doing sustaining builds for the Moto Z Play, https://wiki.lineageos.org/devices/addison?
Many thanks for providing these builds for the Nexus 7 2013.
braveheartleo said:
Good day sir, would you consider adding to the roster and doing sustaining builds for the Moto Z Play, https://wiki.lineageos.org/devices/addison?
Click to expand...
Click to collapse
No problem at all. I've added it to the weekly roster, and a one-off build is at https://lineageos.disavowed.jp/addison/.
wileyc said:
No problem at all. I've added it to the weekly roster, and a one-off build is at https://lineageos.disavowed.jp/addison/.
Click to expand...
Click to collapse
Awesome turnaround sir. And thank you very much. ?
Thanks for running these builds! Out of curiosity what's the monthly cost like? You running these on a home machine or something like DigitalOcean?
Hi. One Question, can i update over last zeelogs LOS Build?
Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?
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)