[UNOFFICIAL][ROM][11][Marlin/Sailfish] LineageOS 18.0 [06/10/2020] - Google Pixel XL ROMs, Kernels, Recoveries, & Other

[UNOFFICIAL][ROM][11][Marlin/Sailfish] LineageOS 18.0 [06/10/2020] - Google Pixel XL ROMs, Kernels, Recoveries, & Other

Seems for marlin I didn't apply some fixes since I work on Sailfish as my main device, will update the links to a fixed build in about an hour.

Dude, you're awesome!

Links are updated, happy flashing!

Lunarixus said:
Links are updated, happy flashing!
Click to expand...
Click to collapse
The only issues I've found so far is that Magisk will not work, after install it reboots on the google logo.

Voltz100999 said:
The only issues I've found so far is that Magisk will not work, after install it reboots on the google logo.
Click to expand...
Click to collapse
Are you installing it and installing TWRP? That might be the problem.

yagyaxt1068 said:
Are you installing it and installing TWRP? That might be the problem.
Click to expand...
Click to collapse
Yes sir, I am. I just found out that it wont really work that way though.

Hello! Loving this rom so far. No issues have been seriously experience breaking but there are a few things worth addressing:
1. Changing wallpapers crashes by default - fixed by installing the Google Wallpapers app from the play store.
2. Ringtones are unable to be changed as selecting the option to change it in settings > sound - crashes settings - tried 3rd party apps no workaround. Default ringtone for notification is an actual ringtone so notification tones are ~30 seconds and unable to be changed. (Update: I was able to change ringtones through the Audiko app)
3. Apps that utilize the finger print scanner previously do not seem to have access (i.e. Lastpass) noting in the app settings that the feature is unavailable on this device.
4. Hotspot is unable to be enabled - simply gives "Error" when trying to enable.
5. Google Fi users are forced to complete the Pixel setup again when activating through the Fi app
6. Latest versions of Magisk (20 and 21) do not work with this rom and will cause it to boot loop.
Aside from the above it's been a mostly solid experience. When you get a lot of apps running it gets a bit bogged down and some things are just somewhat choppy to load. That being said, performance is not something I'm expecting with a bleeding edge port of an unsupported OS

My bad. Didnt realize this was los18

DudemanJenkins said:
Hello! Loving this rom so far. No issues have been seriously experience breaking but there are a few things worth addressing:
1. Changing wallpapers crashes by default - fixed by installing the Google Wallpapers app from the play store.
2. Ringtones are unable to be changed as selecting the option to change it in settings > sound - crashes settings - tried 3rd party apps no workaround. Default ringtone for notification is an actual ringtone so notification tones are ~30 seconds and unable to be changed. (Update: I was able to change ringtones through the Audiko app)
3. Apps that utilize the finger print scanner previously do not seem to have access (i.e. Lastpass) noting in the app settings that the feature is unavailable on this device.
4. Hotspot is unable to be enabled - simply gives "Error" when trying to enable.
5. Google Fi users are forced to complete the Pixel setup again when activating through the Fi app
6. Latest versions of Magisk (20 and 21) do not work with this rom and will cause it to boot loop.
Aside from the above it's been a mostly solid experience. When you get a lot of apps running it gets a bit bogged down and some things are just somewhat choppy to load. That being said, performance is not something I'm expecting with a bleeding edge port of an unsupported OS
Click to expand...
Click to collapse
Hello DudemanJenkins,
1. I understand the concern with the wallpapers app, it is something I did source side and I am researching into possible fixes.
2. Ringtone options are broken in LOS 18 at the moment, I am expecting them to be fixed soon but I have no ETA on that, hopefully by next build.
3. I believe I have identified what causes apps to not see fingerprint and have addressed it in hopes it'll be fixed next build.
4. I will look into this.
5. I don't own a Google Fi phone so I cannot speak too much but this sounds like a normal thing.
6. There are multiple people rooted on this ROM, check your flashing method is correct.
As for performance and battery life I believe I have found the cause of why both of those are so bad at the moment, hopefully will be fixed next release.

found handful of bugs
some options in the settings dosent work
google chrome keeps crashing
overall camera quality was also not good like on the official android 10
kindly look into this

I did get Magisk 21 installed, and it works fine. My main issues are the battery percentage not enabling and Chrome (in all forms I believe) crashes very frequently. Other than that the ROM is actually quite a bit quicker feeling than Android 10 was on my XL.

anas aleem said:
...
overall camera quality was also not good like on the official android 10
...
Click to expand...
Click to collapse
The camera installed is the open source Camera2 app. Install a GCam port.

Lunarixus said:
5. I don't own a Google Fi phone so I cannot speak too much but this sounds like a normal thing.
6. There are multiple people rooted on this ROM, check your flashing method is correct.
Click to expand...
Click to collapse
5. It will usually take you to activation where it will then just take you to the Fi app. It could be that there's some kind of call that has it skip the rest as the activation is one of the first parts of android setup? Just a thought from someone with minimal understanding . Also very niche so totally understand if this is a nofix.
---------- Post added at 01:26 PM ---------- Previous post was at 01:21 PM ----------
Voltz100999 said:
I did get Magisk 21 installed, and it works fine. My main issues are the battery percentage not enabling and Chrome (in all forms I believe) crashes very frequently. Other than that the ROM is actually quite a bit quicker feeling than Android 10 was on my XL.
Click to expand...
Click to collapse
If you don't mind, what steps did you take to get Magisk working? I'm still a bit stuck there

Thanks for this build! I tried it out on my OG Pixel XL, and was able to get it to boot. I did run into a few issues:
1. GApps was installed by default, and went through the initial setup, however GMail and Calendar both did not recognize that the account was installed. I waited overnight for all of the apps to update, and eventually they synchronized and allowed access to the accounts. Very strange.
2. Chrome is very glitchy. It crashes frequently and freezes a lot, especially when switching between apps.
3. Ran into the wallpaper issue, but resolved as others mentioned.
4. Ran into the ringtone issue, with phantom alarm/ringtones happening randomly. I ended up having to put the phone on vibrate as it was quite loud sometimes.
5. I have two calendar apps for some reason. They both seem to be synchronizing for the same account, but have different icons on the launcher screen.

device tree
yum yum yummy!
curious what device tree looks like for XL (either, I guess )
awesome koods!! :good:
edit: looks like GSI,perhaps

scube said:
yum yum yummy!
curious what device tree looks like for XL (either, I guess )
awesome koods!! :good:
edit: looks like GSI,perhaps
Click to expand...
Click to collapse
Nothing of the sort, all source built, look at your build number lmfao

I'm surprised this hasn't gotten more replies in comparison to other previous unofficial release of 17.0/17.1. Have people been having trouble with this release?

Extremeblight said:
I'm surprised this hasn't gotten more replies in comparison to other previous unofficial release of 17.0/17.1. Have people been having trouble with this release?
Click to expand...
Click to collapse
+1

Extremeblight said:
I'm surprised this hasn't gotten more replies in comparison to other previous unofficial release of 17.0/17.1. Have people been having trouble with this release?
Click to expand...
Click to collapse
I'm using this build since a week more or less, and it's working normally for me. Indeed it needs some performance improvements

Related

[ROM][Redmi 2][Unofficial][KZ][UBERTC-4.9.4] Cyanogenmod 13.0

Cyanogenmod 13.0 , Android 6.0.1 [Marshmallow]
*Please take note that installing this ROM assumes that you take responsibility of what may happen to your device (eg: bricks)
Issues
- VOLUP+VOLDOWN to boot into recovery
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
Latest build: https://goo.gl/i69cg5
ROM folder: https://goo.gl/XpMdGC
Stock TWRP: https://goo.gl/DD7Xss [Use twrp_r4.img]
Credits
- balika011 [Open Source Kernel]
- Kumajaya [Kernel Base]
- Zwliew [Some Fixes]
- Tarun93 [Kernel Features, Governors]
- kirananto [Upstream Kernel]
- nick37332001 [Free Time]
- Cyanogenmod
- AOSP
Sauces
Device Tree: https://github.com/kumajaya/android_device_wingtech_wt88047
Kernel Tree: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Big thanks to @ketut.kumajaya on guiding me on how to properly compile Cyanogenmod 13, and also thank beta testers VIZKILL3R for testing out the ROM.

Works as advertised.
However, in addition to the mentioned bugs, these are also of concern:
1. MTP doesn't work via USB when not in recovery mode, most of the time. In recovery mode, it works fine. Plus, when it works while CM is running, the SD card slow has a very long random name.
2. Camera is very laggy. Not just at starting, but taking settings, going back to camera screen - all are laggy.
3. ES File Explorer works (but stops loading folders different from internal and external storage after a while). CM File Manager, and MiXplorer both had issues (CMFM apparently requires elevated privileges, while MiXplorer shows something like what is shown in the screenshot). The stock Android Documents app, works fine.
4. Camera button controls aren't applicable to our device, are they?
5. Loudspeaker output seems to have reduced slightly from the default MIUI ROM.
That's all I could gather in half an hour of testing.
Thanks a lot for your effort to bring the sweetness to Redmi 2 (and variants).
In addition, is there any GApps package that works?

zeomal said:
However, in addition to the mentioned bugs, these are also of concern:
1. MTP doesn't work via USB when not in recovery mode, most of the time. In recovery mode, it works fine. Plus, when it works while CM is running, the SD card slow has a very long random name.
2. Camera is very laggy. Not just at starting, but taking settings, going back to camera screen - all are laggy.
3. ES File Explorer works (but stops loading folders different from internal and external storage after a while). CM File Manager, and MiXplorer both had issues (CMFM apparently requires elevated privileges, while MiXplorer shows something like what is shown in the screenshot). The stock Android Documents app, works fine.
4. Camera button controls aren't applicable to our device, are they?
5. Loudspeaker output seems to have reduced slightly from the default MIUI ROM.
That's all I could gather in half an hour of testing.
Thanks a lot for your effort to bring the sweetness to Redmi 2 (and variants).
In addition, is there any GApps package that works?
Click to expand...
Click to collapse
Most file managers don't work because of Marshmallow's new file system. First version, SD Card does not show up at all. I think Cyanogen is working hard on fixing the CMFile bugs. Take pictures from camera is a known bug and it will be patched soon. Loudspeaker cannot be helped since miui had different audio steps compared to stock android. As for MTP, it is set as USB charging by default. So you have to pull down notification bar and change connection type to file transfer.

nick37332001 said:
PS to kumajaya: If you don't want me to have this thread up, PM me
Click to expand...
Click to collapse
First of all.. thank you for working on our redmi2..
BUT, you should have asked kumajaya for permission BEFORE opening this thread, this is at least unfair.
You can make builds for your self without asking, but NOT for public usage.
What do you think kumajaya could say now.. "don't do this, close this thread..?? "
You have already spilled the milk, there is no reason to ask for a permission now.
If you wanted to go public.. make something else, like aosp, or omnirom, or... whatever rom that's DIFFERENT than the original work that the original developer did, or is doing..
As far i know kumajaya is working on CM13, and now whats the point for him to publish HIS work, with HIS sources.. when you already did that WITHOUT asking FIRST.
Again, thank you for working on redmi2, im doing something my self too , but im keeping my working sources private because of things like this.
I already made aosp 5.1.1 with kernel 3.10.85 , i just didn't published it on xda

The preferred network type (obtained by *#*#4636#*#*) cannot be changed from WCDMA preferred.
The same thing in Settngs --> Mobile Networks cannot be changed from LTE.

pirej said:
First of all.. thank you for working on our redmi2..
BUT, you should have asked kumajaya for permission BEFORE opening this thread, this is at least unfair.
You can make builds for your self without asking, but NOT for public usage.
What do you think kumajaya could say now.. "don't do this, close this thread..?? "
You have already spilled the milk, there is no reason to ask for a permission now.
If you wanted to go public.. make something else, like aosp, or omnirom, or... whatever rom that's DIFFERENT than the original work that the original developer did, or is doing..
As far i know kumajaya is working on CM13, and now whats the point for him to publish HIS work, with HIS sources.. when you already did that WITHOUT asking FIRST.
Again, thank you for working on redmi2, im doing something my self too , but im keeping my working sources private because of things like this.
I already made aosp 5.1.1 with kernel 3.10.85 , i just didn't published it on xda
Click to expand...
Click to collapse
The only reason I open this thread is to let impatient users get their hands on a cm-13.0 build. I have no intentions of plagiarism. This ROM is together build with god kernel r2 cos I am trying to bring in the best of both worlds. If you have any misunderstandings, I am sorry.

nick37332001 said:
The only reason I open this thread is to let impatient users get their hands on a cm-13.0 build. I have no intentions of plagiarism. This ROM is together build with god kernel r2 cos I am trying to bring in the best of both worlds. If you have any misunderstandings, I am sorry.
Click to expand...
Click to collapse
As i said, thank you for working on redmi2, its great to see development for our device.
I just want a fair play, nothing else, and if this is fine with kumajaya.. i have nothing against any kind of development.
Good luck.

nick37332001 said:
**This ROM is in beta, expect bugs that come along with it.
Cyanogenmod 13.0 , Android 6.0 [Marshmallow]
*Please take note that installing this ROM assumes that you take responsibility of what may happen to your device (eg: bricks)
Issues
- VOLUP+VOLDOWN to boot into recovery
- YAS537 Compass Sensor is not working
- GPS not working properly
- FM Radio not patched to work on marshmallow
- Pictures cannot be taken but video recordings possible
Screenshots
View attachment 3542159View attachment 3542160View attachment 3542161View attachment 3542162View attachment 3542163
Downloads
Latest build: https://goo.gl/H8lboS
ROM folder: https://goo.gl/XpMdGC
Stock TWRP: https://goo.gl/DD7Xss [Use twrp_r4.img]
Credits
- Kumajaya [Open Source Kernel]
- Zwliew [Some Fixes]
- Tarun93 [Kernel Features, Governors & OC 1.4GHz]
- nick37332001 [Free Time]
- Cyanogenmod
- AOSP
Sauces
Device Tree: https://github.com/kumajaya/android_device_wingtech_wt88047
Kernel Tree: https://github.com/nick37332001/android_kernel_cyanogen_msm8916
Big thanks to @ketut.kumajaya on guiding me on how to properly compile Cyanogenmod 13, and also thank beta testers VIZKILL3R for testing out the ROM.
PS to kumajaya: If you don't want me to have this thread up, PM me
Click to expand...
Click to collapse
i hope.. soon i will able use this rom as daily driver !
Good luck for your work :good:

As for MTP, it is set as USB charging by default. So you have to pull down notification bar and change connection type to file transfer.
Click to expand...
Click to collapse
I did change it to MTP. The same issue persists.
Waking the phone up after a while causes the phone to become very slow. Sometime it even crawls. Why?
Also, does this ROM have the "necessary patch" (as mentioned here) to install GApps?

Going to try...

zeomal said:
I did change it to MTP. The same issue persists.
Waking the phone up after a while causes the phone to become very slow. Sometime it even crawls. Why?
Also, does this ROM have the "necessary patch" (as mentioned here) to install GApps?
Click to expand...
Click to collapse
Use SlimGapps, It does not need any patch since its latest update

New build
https://goo.gl/Wsmwzs
Updated to latest commits of @ketut.kumajaya
Includes GPS fix I think

nick37332001 said:
Use SlimGapps, It does not need any patch since its latest update
Click to expand...
Click to collapse
SlimGApps causes major issues. Greeted with a "Unfortunately setup wizard has stopped working" message that keeps coming everytime I press "OK". In addition, it causes other crashes for several Google Apps, including Google Play Services.

zeomal said:
SlimGApps causes major issues. Greeted with a "Unfortunately setup wizard has stopped working" message that keeps coming everytime I press "OK". In addition, it causes other crashes for several Google Apps, including Google Play Services.
Click to expand...
Click to collapse
Have you tried the latest version yet? It fixes the problem

nick37332001 said:
Have you tried the latest version yet? It fixes the problem
Click to expand...
Click to collapse
Both the Zero GApps and the Mini GApps cause the same issue.
(Tried flashing ROM, rebooting, flashing GApps, and flashing ROM and GApps and rebooting.)

Try the mini version and remember to wipe data partition also... It helps
Sent from my 2014817 using Tapatalk

nick37332001 said:
Try the mini version and remember to wipe data partition also... It helps
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
Confirmed working.
I hadn't wiped data partition.
And yes, GPS is fixed.

zeomal said:
Confirmed working.
I hadn't wiped data partition.
Click to expand...
Click to collapse
Working which? Mini version?

hjs85 said:
Working which? Mini version?
Click to expand...
Click to collapse
I tried on Zero GApps.
Mini should work too, but as nick37332001 suggested, data partition should be wiped.

Flash gapps reboot factory reset > work for me
Odesláno z mého 2014811 pomocí Tapatalk

[ROM][OMS][7.1.1_r33] Candy7 Final v6.0

XDA:DevDB Information
CandyRoms, ROM for the Sony Xperia SP
Contributors
dic1911
Source Code: http://github.com/CandyRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP-CAF
Version Information
Status: Testing
Current Beta Version: v3.0
Created 2017-03-21
Last Updated 2017-09-02

Downloads
See Post #3 for a list of what is working or not if you have concerns. Thanks!
ROM:
As usual, I uploaded it on AFH (https://www.androidfilehost.com/?w=files&flid=164175)
(Magisk removed cause not supported, causes soft brick)
GAPPS:
I recommand OpenGapps

Issues/FAQ
FAQ
1. This is a test build, it works fine for me, but not everything is tested, try and report!
Issues
You tell me!

hi there.
i flashed this rom and supersu-v2.52. then reset my phone,after 20 minutes in boot animation nothing happened . why is that?
so i flashed xosp and my phone is working fine.

Beh2ad said:
hi there.
i flashed this rom and supersu-v2.52. then reset my phone,after 20 minutes in boot animation nothing happened . why is that?
so i flashed xosp and my phone is working fine.
Click to expand...
Click to collapse
I guess this is your first for manually rooting nougat on your phone, you'll need to flash newer SuperSU(like 2.78) via BootBridge by AdrianDC.
Old SuperSU will give you soft brick on nougat.

hi there
after one day using this rom everything is working fine. gps , FMradio , ussd , Camera ,etc.
only on thing that is bugging me is that screen recorder should save videos on movies folder not Pictures folder.
i attached some screenshot of this rom.
peace out :good:

So, after something broke on my phone and Settings > Apps would always crash reading some folder (and Play Store too), I went to redownload Candy5 and found that you made a Candy7 ROM. So I flashed that instead
Android 7 feels much more snappy, and the pixel launcher stays in RAM unlike the Google launcher in 5.1. And I got more free storage space, though that will probably go down once I start using all the apps.
Things I did not find yet, maybe they are gone?
I can't find where I can configure the shutter button. In Candy5, I had it set to open the camera on long-press.
I can't find the option to make the grid pattern unlock bigger. It is 3x3 now, I had it set to 5x5 in Candy5 and it would be great if I could use this size again.
Overall, I am very pleased, thanks for creating this ROM Now to some real world test in the next days.

noggernogger said:
So, after something broke on my phone and Settings > Apps would always crash reading some folder (and Play Store too), I went to redownload Candy5 and found that you made a Candy7 ROM. So I flashed that instead
Android 7 feels much more snappy, and the pixel launcher stays in RAM unlike the Google launcher in 5.1. And I got more free storage space, though that will probably go down once I start using all the apps.
Things I did not find yet, maybe they are gone?
I can't find where I can configure the shutter button. In Candy5, I had it set to open the camera on long-press.
I can't find the option to make the grid pattern unlock bigger. It is 3x3 now, I had it set to 5x5 in Candy5 and it would be great if I could use this size again.
Overall, I am very pleased, thanks for creating this ROM Now to some real world test in the next days.
Click to expand...
Click to collapse
Yeah, most fancy things in most ROMs weren't added in Nougat like the lollipop/kitkat days(and for your questions, I would say 'yup, they're gone'), I haven't release any update recently because I'm in the army, and I'll get out on 9/5, will get some time to make another build, til then please be patient

Too bad, I am missing the built-in adblocker already. Good to hear about the upcoming updates, looking forward to it. Stay save!

Bootloader
Hello, it's necessary to have the bootloader open?

Migui_gg said:
Hello, it's necessary to have the bootloader open?
Click to expand...
Click to collapse
Of course
Sent from my LG-H818 using Tapatalk

Migui_gg said:
Hello, it's necessary to have the bootloader open?
Click to expand...
Click to collapse
Yes, since lollipop, most ROMs requires unlocked bootloader

Final build is up!
The final nougat build of CandyRom is uploaded on my AFH folder!
This build ships substratum and some feature along with fixes added :good:

Thanks for the update! I flashed the 7.1.2 ROM today, all went well Will you update the project if Google releases updates to Android 7? I hope final build does not mean you are done with the project
Now I have to test it some more. At first glance, this version seems to perform a little bit worse than the previous 7.1.1 beta. Like a slight stutter here and there. Might be related to the new Lawnchair launcher and the Substratum engine maybe? They add some nice additional features and customization though.
I'd like to verify that hunch. Can I simply uninstall "substratum theme engine rooted/oms-tw-rootless" in the Google play store, or is that not enough / will break stuff? To get the plain Pixel launcher from 7.1.1, do I just install "Google Now Launcher" in the Google play store?

noggernogger said:
Thanks for the update! I flashed the 7.1.2 ROM today, all went well Will you update the project if Google releases updates to Android 7? I hope final build does not mean you are done with the project
Now I have to test it some more. At first glance, this version seems to perform a little bit worse than the previous 7.1.1 beta. Like a slight stutter here and there. Might be related to the new Lawnchair launcher and the Substratum engine maybe? They add some nice additional features and customization though.
I'd like to verify that hunch. Can I simply uninstall "substratum theme engine rooted/oms-tw-rootless" in the Google play store, or is that not enough / will break stuff? To get the plain Pixel launcher from 7.1.1, do I just install "Google Now Launcher" in the Google play store?
Click to expand...
Click to collapse
nope, it won't break anything, and actually I don't think substratum app will affect the performance if you just leave it there + don't use apply any theme, for the Pixel flavored launcher, there's already plenty launchers out there, just pick the one you like the most.
oh yeah, I'm not done with building ROMs as long as Adrian teh huashan god still working on the device

I saw there are first beta versions of Android O, looking forward to that I just have to say it again, going from Android 5 to Android 7 makes the phone feel much more alive, it is amazing! Uses less space (I was constantly getting out of space messages for the system partition when updating apps in Android 5), better memory usage, faster app installation, much snappier feel, etc. I was seriously thinking about scratching together some money for a new phone because I did not want to endure the problems any more, especially the storage space one. No more
I uninstalled substratum and its background service using link2sd and kept lawnchair. Seems to be working en par with the 7.1.1 beta. So maybe substratum still uses resources even when not configured, or maybe it is a placebo effect, or the JIT compiler warmed up, I don't know. Either way, that's what I stick with for the time being.
Thanks again for your work on this ROM!

BETA[ROM][AOKP 8.1/Oreo][HLTE] AOKP Oreo for Galaxy Note 3 (Unified)BETA

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned.
[ROM][AOKP 8.1/OREO][HLTE] AOKP Oreo for Galaxy Note 3 (Unified) Beta Builds
These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned. Again.
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Read the above warnings again! These are BETA builds!
They are [B]NOT[/B] feature-complete, nor are they guaranteed to run!
By installing them, [B]YOU[/B] are assuming the risk of any potential problems!
Introduction
AOKP is a ROM developed by TeamKang, based on AOSP with magical unicorn bytes (awesome features) baked right in!
These builds have been tested on SM-N9005/SM-N900P
Features
Android 8.1 Oreo
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
More features coming soon! (P.S. Asking for ETA's is bad, unless you like NOT getting new features! )
Click to expand...
Click to collapse
Known Issues
Bluetooth does not work with some devices - This is a known issue that also affects LineageOS-15.1Fixed?
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
shane87 AndroidFileHost page:
shane87's AFH page for AOKP Oreo Builds (BETA)
Source:
AOKP Source
Click to expand...
Click to collapse
Changelog
Code:
[B][U]Detailed changelogs between each version can be found at download link[/U][/B]
[B][U]Current changelog: 07/21/2019[/U][/B]
*[fix]BT bug fixed......again......maybe? lol
*[update]Latest AOSP/LOS upstream changes (No AOKP changes since last build - We are all focused on Pie, when we have time!)
[B][U]Changelog: 07/06/2019[/U][/B]
*[fix]BT bug finally squashed! - I hope anyway, let me know guys!
*[update]Latest AOSP/AOKP/LOS upstream changes
[B][U]Changelog: 12/09/2018[/U][/B]
*[fix?]Changes in hardware/samsung (6 commits) - MAY fix BT issues!
*[update]Latest AOSP/AOKP/LOS upstream changes
[B][U]Changelog: 11/18/2018[/U][/B]
*[fix?]Set proper WBS sample rate - MAY fix BT issues!
*[update]Update to Android 8.1_r50 base
*[update]All upstream changes since 09/16
[B][U]Changelog: 09/16/2018[/U][/B]
*[update]Update to Android 8.1_r46 base
*[new/update]Add SystemProfiles QS Tiles
*[fix]Fix some QS tiles, remove some deprecated QS Tile code
*[fix?]Fix spacing in bluetooth_vnd.txt, [i]possible[/i] BT issue fix?
*Full changelog available at download link
[B][U]Changelog: 08/19/2018[/U][/B]
*[fix]Remove reference to mIsTap and Handler in absListViewWidgets.java (frameworks/base) - Fixes ListView mod widget issue
*[fix]Camera regression from 08/12 build fixed - No clue what happened, but everything is working again.
*[update]Add QS animation options to ROM Control
*[update]Add QS title hide option to ROM Control
*[update]Add AOKP logo on status bar option to ROM Control
*Full changelog available at download link
[B][U]Changelog: 08/12/2018[/U][/B]
*[fix]su issues from previous build fixed
*[update]Revert soundboost to stop speaker distortion [update]SoundBoost mods available at dl links!
*Full changelog available at download link
[B][U]Changelog: 07/31/2018[/U][/B]
*[update/fix?]Remove CarrierConfigs from hlte/hltetmo device trees; CarrierConfigs was duplicated in msm8974-common
*[update/fix]Remove vendor security patch level from device trees, move to common tree
*Full changelog available at download link
[B][U]Changelog: 06/24/2018[/U][/B]
*[update]Use mpdecision from G900FXXU1CRA2_G900FOXA1CRA2_BTU
*[update]Drop lib_cutils_atomic shim (was only needed for old mpdecision)
*[fix?]Changing mpdecision and dropping the shim [B][U]SEEMS[/U][/B] to have fixed rotation on LOS, hopefully fixed for us
*Full changelog available at download link
[B][U]Changelog: 06/03/2018[/U][/B]
*[fix]Boost sound levels across all devices
*Full changelog available at download link
[B][U]Changelog: 05/14/2018[/U][/B]
*[fix?]Commit pulled in from AOKP source to fix camera recording issues.
*[update]Latest changes from AOKP source
*Full changelog available at download link
[B][U]Changelog: 05/06/2018[/U][/B]
*[update]Minor changes to QS header images support
*[new]Scrollable QS tiles
*[new]Add builds for hltechn/hltekor/hltetmo
*Full changelog available at download link
[B][U]Changelog: 4/30/18[/U][/B]
*[fix?]Changes to phone call audio routing, may help BT phone audio issues
*[fix?]New overlay that may help with auto-rotation bug
*[new]Customizable header images
*Full changelog available at download link
[B][U]Changelog: 4/23/2018[/U][/B]
*[new]Initial AOKP Oreo Beta release for hlte
Thanks To/Credits
TeamKang
tdm
LineageOS
@stonedead - for finding sensor batching overlay; a potential rotation bug fix!
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Oreo Android Open Kang Project for Samsung Galaxy Note 3 (HLTE), ROM for the Sprint Samsung Galaxy Note 3
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.2.1-1
Based On: AOKP
Version Information
Status: Beta
Current Beta Version: 2019-07-21
Beta Release Date: 2019-07-21
Created 2018-04-24
Last Updated 2019-07-21

Reserved

As far as an update schedule goes, I will TRY to do weekly builds with the latest commits. I will also TRY to pull in pending commits when possible, assuming I can get them to build.

this is pretty good news I will try to get this installed this weekend thanks for keeping this phone alive

I also installed this ROM and will do some testing. So far what I have tried, voice, data, GPS have worked as expected. It also connects with my Asus smart watch. I will continue to test things out and provide feedback as appropriate. BTW BT phone audio is not working as noted on OP. If that is corrected this would be my daily driver. Thanks to the dev for the work on this Note 3 ROM!

len207 said:
I also installed this ROM and will do some testing. So far what I have tried, voice, data, GPS have worked as expected. It also connects with my Asus smart watch. I will continue to test things out and provide feedback as appropriate. BTW BT phone audio is not working as noted on OP. If that is corrected this would be my daily driver. Thanks to the dev for the work on this Note 3 ROM!
Click to expand...
Click to collapse
What bt device did you try phone audio on?

shane87 said:
What bt device did you try phone audio on?
Click to expand...
Click to collapse
I've tried two BT headsets the 6xxPlantronics and Motorola H19txt. They both work fine on Nougat ROM including AOKP and they also work with LineageOS 15.1 on the Note 4. I have also paired it with my car's BT Hands Free system with the same results. In all cases BT is seen and used for phone audio however, there is initially some white noise followed (after about 5 seconds) with silence.

len207 said:
I've tried two BT headsets the 6xxPlantronics and Motorola H19txt. They both work fine on Nougat ROM including AOKP and they also work with LineageOS 15.1 on the Note 4. I have also paired it with my car's BT Hands Free system with the same results. In all cases BT is seen and used for phone audio however, there is initially some white noise followed (after about 5 seconds) with silence.
Click to expand...
Click to collapse
Alright,I'll do some testing this weekend. I have a Plantronics Legend headset. It works perfect with AOKP Oreo on my LG g3. I'll test on my wife's Note 3 this weekend and see what I get.

Decided to make the jump!
Hooray for O.R.E.O.!
I was able to do an easy upgrade and so far its running along but had a few observations...
1. Do we not have to "allow instillation from unknown sources" under 'security' anymore?
2. GPS, DATA, CELL all working well. Will test bluetooth with my fitbit and speakers later today.
3. I am using Nova Launcher. I would like to put in a calendar widget, but it says "problems loading widget" no matter what widget I use. Google Calendar, Calendar Widget, and Chronos all not working. Chronos says it does not have OREO support anymore. Can anyone recommend a nice transparent calendar widget?
4. Hotspot Works... YAY!!
5. When trying to select my quick setting tiles, I can of course edit what I want to have appear. However, when I select to edit additional choices, the additional options are white on a white background so kinda hard to see.
I will be happy to provide logcats anyone is interested. But be advised. I am still unable to update my baseband from NC5 to PL1. But I dont think that has anything to do with the minor errors I am getting.
My thanks to all! And I will be happy to help further test this ROM if there is anything I can do, just ask!

Unidave199 said:
Hooray for O.R.E.O.!
I was able to do an easy upgrade and so far its running along but had a few observations...
1. Do we not have to "allow instillation from unknown sources" under 'security' anymore?
2. GPS, DATA, CELL all working well. Will test bluetooth with my fitbit and speakers later today.
3. I am using Nova Launcher. I would like to put in a calendar widget, but it says "problems loading widget" no matter what widget I use. Google Calendar, Calendar Widget, and Chronos all not working. Chronos says it does not have OREO support anymore. Can anyone recommend a nice transparent calendar widget?
4. Hotspot Works... YAY!!
5. When trying to select my quick setting tiles, I can of course edit what I want to have appear. However, when I select to edit additional choices, the additional options are white on a white background so kinda hard to see.
I will be happy to provide logcats anyone is interested. Bt be advised. I am still unable to update my baseband from NC5 to PL1. But I dont think that has anything to do with the minor errors I am getting.
My thanks to all! And I will be happy to help further test this ROM if there is anything I can do, just ask!
Click to expand...
Click to collapse
1. Installation from unknown sources is now handled like Nougat/Oreo permissions: on an app-by-app basis as each app tries to install an app from unknown sources. You will be prompted to give permission for it. For example, my Amazon app had an update yesterday, and when I hit install it prompted me to give Amazon permission to install from unknown sources.
2. Awesome to hear. Let me know how bt goes.
3. That must be a Nova issue. I run Apex, and I was able to add a calendar widget (from Google Calendar), with no issue. To be fair, I am also using an LG G3 right now, though I can't imagine that would make a difference, since I built the hlte and d855 builds back to back.
4. Good to hear. I haven't tested hotspot.
5. We are still ironing out some issues!

shane87 said:
2. Awesome to hear. Let me know how bt goes.
So... more good news! Paired with my Fitbit just fine, also paired with my stereo and speaker
3. That must be a Nova issue. I run Apex, and I was able to add a calendar widget (from Google Calendar), with no issue. To be fair, I am also using an LG G3 right now, though I can't imagine that would make a difference, since I built the hlte and d855 builds back to back.
I also tried the Trebouchet launcher that came with the ROM and it was acting weird too. Seems to be that the Analogue clock will post but not the digital one. Also size changes seem to prevent the digital clock from working
The voice input doesn't seem to be working as part of the keyboard. It does work for Google Assistant though...
Click to expand...
Click to collapse
Thank you again! I hope this is not nit picking.
Dave

Unidave199 said:
Thank you again! I hope this is not nit picking.
Dave
Click to expand...
Click to collapse
Not at all. I need someone to find all these little bugs, lol. I haven't tried voice input, I don't have much use for it, tbh. I'll do some digging this weekend, and see what I find in testing.

Unidave199 said:
Thank you again! I hope this is not nit picking.
Dave
Click to expand...
Click to collapse
Dig away! So I decided to load the Nugat ROM on my phone and I see that the Clock/Calendar applications work fine with Nova Launcher. As to the voice issue I think it is my fault. I need to "enable voice typing" on the system. I did so with Nougat and it works just fine.
I would love to play a deeper role with compiling and code writing but I am still way too much of a noob but happy to do my part. I am a fairly heavy "power user" of almost all the systems so I give this GREAT phone a good workout.
I even use the infra red. Peel remote seems to be working......
Dave

Alright guys, I have been doing some digging into @trader418 and I can't find anything in particular that helps the rotation bug. In his unofficial Lineage 14 thread, he mentions some cm/los updates that fixed the rotation issues, but doesn't mention the exact commit. Also, it sounds like those changes should already be in these builds, since AOKP's hlte device trees, and kernel source, are forked from LineageOS trees. And I do make sure to pull in the latest LOS changes. So I am still stumped on the rotation bug. On to better news. I have just finished a new build, with the latest AOKP changes synced in. I also pulled in some open commits that add customizable header image support. Along with a few open commits from LOS, mostly to do with phone call audio, so hopefully that may help with BT issues. I am going to do some personal testing before I upload, so be patient, new goodies are on their way!

New Release!
Alright guys, I have a new build up at the download link in the OP. For this build, I pulled in some LOS changes that deal with phone call audio routing, which could help with bt phone audio issues, and I also enabled an overlay that may help with the rotation bug. The overlay was discovered by @stonedead so a HUGE thanks to him! I may have never discovered the overlay on my own. I also have included pending AOKP commits to add customizable header images. This build also includes all of the latest AOKP commits that have been merged, including fixes and some tweaked features. As always, I upload a changelog with all of the commits pulled in since the last build, so detailed information on the changes between the 4/23 build and todays build can be found there.
I HAVE NOT had a chance to personally test this build! As I have mentioned before, my only test phone is my wife's daily driver, and if she is busy using it, not much of a chance for me to test lol. With that being said, there shouldn't be any major bugs introduced in this build.
Changelog:
Changes to phone call audio routing, may help BT phone audio issues
New overlay that may help with auto-rotation bug
Customizable header images
Full changelog available at download link

Thank you for your ongoing efforts but unfortunately the BT phone audio on my n900p has not changed. The BT headphone is seen by the system and pairs just fine. In phone app the BT headphone is also seen. However, when making a call the earpiece only produces white noise slowly decreasing in volume to silence. The person on the other end of the connection hears nothing...

[SOLVED] Control Backlighting.
I seem to recall someone having problems with their backlights on the menu and 'back' button. I had it too until i went to SETTINGS> BUTTONS>HARDWARE KEYS...
Just toggle them off and back on then the buttons should respond to your desired preference...
As a side note... I wrote earler about using Clock and Calendar displays in NOVA launcher and they just don't seem to work... but they work fine in Apex Launcher which is free and very similar to NOVA..
Keep up the GREAT ROM! Thank you for the snack jump from KitKat to Oreo!
D-

New Release!
Hey guys, new builds are up. Nothing major with these builds, some minor changes to QS Header image support, and scrollable QS Tiles. The big news with this release is
Wait for it...
Wait some more...
Builds for hltechn/hltekor/hltetmo!!!
I have NOT tested these builds! I don't have access to anything other than hlte, so PLEASE test these builds if you have the device! And let me know what you find!
The info and download links for the new builds can be found on my main thread

I will give the new build a try tonight!
Unfortunately I had the hotspot function working, and then it stopped. I will get the nerve to Odin the PL1 update and then see if that fixes the problem...
Can we just dirty flash the new builds? Do we need to re flash GAPPS as well? I tired doing that and it would crash out so I had just dirty flashed the new build without GAPPS and without wipe of cache which seems to work better for me..
Thank you for keeping this build alive!!
D-

Unidave199 said:
I will give the new build a try tonight!
Unfortunately I had the hotspot function working, and then it stopped. I will get the nerve to Odin the PL1 update and then see if that fixes the problem...
Can we just dirty flash the new builds? Do we need to re flash GAPPS as well? I tired doing that and it would crash out so I had just dirty flashed the new build without GAPPS and without wipe of cache which seems to work better for me..
Thank you for keeping this build alive!!
D-
Click to expand...
Click to collapse
Dirty flashing is ok. The only caveat with dirty flashing is, if you run into issues, wipe and clean flash to see if that fixes the issue BEFORE reporting the problem.
As far as GApps, you don't need to reflash GApps on a dirty flash. In theory, reflashing GApps shouldn't hurt, since it should remove existing GApps before installing. However, if you have updated any of the GApps through the playstore, and you flash and older GApps build, you will downgrade the app in question, which may cause issues.
I hope that makes things clear as mud!
TL;DR:
Dirty flashing is ok, as long as you clean flash BEFORE reporting issues.
On a dirty flash, no need to flash GApps again.

[DEPRECATED][ROM][UNOFFICIAL][N|14.1][SM-T285] LineageOS for Samsung Galaxy Tab A 7.0 LTE (gtexslte)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Features
Check out all the great stuff of LineageOS here
My builds are signed by a custom key for better security
F-Droid + priv ext + a bunch of additional repos included
AuroraStore included
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Known issues
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
LineageOS Camera does not work -> install "Open Camera". I am NOT working on a fix sorry.
Open Camera does work but only for photo, i.e. video recording fails. I am NOT working on a fix sorry.
Bluetooth might crash/stop working when enable + disable afterwards (reboot to fix that)
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash the ROM
Optional (if you want root): Flash Magisk
Optional (if you want to use google stuff): Flash GApps (ARM, 7.1)
Boot it (will take a bit on first boot!!! be patient!)
Enjoy
Download
Get your build from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/lineage/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
Join my Telegram groups (see "Support" topic)
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS team, devs, contributors
and all I forgot to mention ....!
Sources
build manifest

Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it.
Often selinux can cause issues so try that at very first:
Code:
adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official LOS builds?
no.
Q #04: Google Play shows that my device is not "certified" - how can I fix that?
First of all you must be on the latest build.
If your issue persists click here to proceed:
The second thing is you must not be rooted by the LOS root addon (afaik). Magisk has its own protections to ensure you stay certified but I hadn't the time to test the LOS root-addon.
You also need to know that google play remembers your devices last state so if you are on the latest build and still having that issue do this and it will be certified again:
android settings -> apps -> find play store -> clear data (yes data, not cache) -> reboot -> open play store -> wait 2..5 minutes -> check certified state again
Q #5: A life without Google?! Read here how:
A life without Google ? Is that possible ? ...and why you should consider it ?
So why? That's easy to answer and if those are worth it depends totally on your personal needs:
1) BATTERY. Google services are draining a LOT of your battery, so to get the most out of your battery you should abandon Google gapps
2) PRIVACY. Almost all Google apps phoning home to Google! You don't care about that? You really should. You have nothing to hide? Oh dear believe me you have no idea how much of your private data you do NOT want to share. Keep also in mind that you give your private data not to a company only , there are always humans behind and what they do.. You do not believe me? Read on
BREAKING NEWS:
You can go on with the following steps or simply head-over to /e/ OS which is LOS but completely Google-Free + microG fully working pre-installed:
check it out here!
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org

reserved

Finally new living for my old tablet, gonna review thing later after flashing it.
Smoothest rom ever performance better than stock or any other rom that i had tried. Except the bug u mention above but thats no big deal. Well finally can instal youtube and google map.

Really love it!
The most stable build for t285!would recommend to everyone who is looking for a custom ROM for t285.But the audio is really low can barely hear it any type of help will be appreciated using it with gapps mini package works as a charm

Gtexlte user said:
Really love it!
The most stable build for t285!would recommend to everyone who is looking for a custom ROM for t285.But the audio is really low can barely hear it any type of help will be appreciated using it with gapps mini package works as a charm
Click to expand...
Click to collapse
Are their any plains for adding oms support?

Gtexlte user said:
Really love it!
[..] the audio is really low can barely hear it any type of help will be appreciated
Click to expand...
Click to collapse
I guess you mean the speaker?
Gtexlte user said:
Are their any plains for adding oms support?
Click to expand...
Click to collapse
nope. oms is a deep hack in the sources and this will never be implemented by me

Yes I mean the speaker
Is there any way to increase it I can root the device.

Gtexlte user said:
Yes I mean the speaker
Is there any way to increase it I can root the device.
Click to expand...
Click to collapse
For me its loud enough, maybe try enable audio fx built in apps

kaishi12 said:
For me its loud enough, maybe try enable audio fx built in apps
Click to expand...
Click to collapse
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.

Gtexlte user said:
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Click to expand...
Click to collapse
I do clean instal from stock rom, well i forgot to mention i using max volume, but strangely theres no noise

kaishi12 said:
I do clean instal from stock rom, well i forgot to mention i using max volume, but strangely theres no noise
Click to expand...
Click to collapse
What do you mean by max volume you set the volume to the max or is it the name of an app or something.thanks for replying.

Gtexlte user said:
What do you mean by max volume you set the volume to the max or is it the name of an app or something.thanks for replying.
Click to expand...
Click to collapse
Set volumw to the max

Gtexlte user said:
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Click to expand...
Click to collapse
You don't have that issue in jedlds build?

steadfasterX said:
You don't have that issue in jedlds build?
Click to expand...
Click to collapse
Yes I don't have it in jedld builds

Gtexlte user said:
Yes I don't have this issue in jedld builds
Click to expand...
Click to collapse
I switched to your LOS builds because some stuff was broken there.but the speaker was the same as stock over there

Is there any way to fix the camera recording issue.

I notice update but it say installation blocked, its for the device?

Clean installed your rom. Everything was smooth but i cant use face unlock in this rom. it keeps showing starting up.i think its because of the recording bug.i installed face unlock in jedld cm 13 build it worked in that rom but it didnt worked in yours. Other than that thi rom is perfect.

steadfasterX said:
You don't have that issue in jedlds build?
Click to expand...
Click to collapse
i Had this issue in jedld build too

[ROM][12L][WIP] LineageOS 19.1 [UNOFFICIAL] [harpia]

Reserved

On my device (XT 1602) I do not face any lag in UI. will you fix the other problems like mobile data? Great work BTW.

Just curious, where are you getting the vendor blobs to build this? I'm trying to build from the source, but when I try to build, I get:
Code:
In file included from build/make/core/envsetup.mk:312:
vendor/lineage/config/telephony.mk:20: error: _nic.PRODUCTS.[[device/motorola/harpia/lineage_harpia.mk]]: "vendor/motorola/msm8916-common/msm8916-common-vendor.mk" does not exist.
14:32:49 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
vendor/lineage/config/telephony.mk:20: error: _nic.PRODUCTS.[[device/motorola/harpia/lineage_harpia.mk]]: "vendor/motorola/msm8916-common/msm8916-common-vendor.mk" does not exist.
14:32:50 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_harpia'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
I also am unable to find a repo for proprietary_motorola_msm8916-common anywhere either.

my god I can't believe that today 02/17/2022 my harpia is running android 12 (S) I swear to God that today I was looking at the forum and I found this I was speechless just today I had done a review of Lineage OS (11) sincerely, you deserve a lot of recognition for continuing to do this and continue to maintain a cell phone that is years old, it is my daily phone now that I found out about this, I did not sit idly by and flash it, I congratulate you, it is a rom very stable and fast, I want to comment on something and it is that with android 11 it took me 2 minutes to start the launcher, here it only takes me 17-18 seconds to start the system I can tell you that this system can become the most stable and quickly for this mobile I will continue waiting for more updates of this version of android and thank you very much for allowing me to continue using my cell phone I have had the opportunity to obtain high-end cell phones but I love my harpia and as a friend told me If something works well for you, don't change it for anything. thankful to all the maintainers who work hard to get updates out.
I want to say that I have only had a small mistake and it is that when I lower the notification bar the cell phone becomes very slow and it takes a few seconds to lower it, I hope they correct the rest, it is perfectly fine, thank you very much! for everything soon a review for this rom so that more people see and appreciate your work.

Booting and installing the image works like a charm and pretty easy.
I tried different GApps but none of them did install. They fail with
Code:
“! Unable to find installation layout. Aboriting...” ?
as shown
in FAQ Point 25 for BiTGApps https://github-wiki-see.page/m/BiTGApps/BiTGApps/wiki/Frequently-Asked-Questions-(FAQ)
w/a does not work. I tried arm (not arm64).
Tested one arm64 NikGApps, this one did install but as expected did not show up.
Can anyone recommend gapps for arm and LOS 19.0?
Thanks
Christian

On my device (XT 1602) I do not face any lag in UI. will you fix the other problems like mobile data? Great work BTW.
visit :
Daftar situs judi slot online terbaik dengan permainan judi online terlengkap dapat dimainkan di MGO303 yang terpercaya sebagai agen slot gacor terbaik

chi70 said:
Booting and installing the image works like a charm and pretty easy.
I tried different GApps but none of them did install. They fail with
Code:
“! Unable to find installation layout. Aboriting...” ?
as shown
in FAQ Point 25 for BiTGApps https://github-wiki-see.page/m/BiTGApps/BiTGApps/wiki/Frequently-Asked-Questions-(FAQ)
w/a does not work. I tried arm (not arm64).
Tested one arm64 NikGApps, this one did install but as expected did not show up.
Can anyone recommend gapps for arm and LOS 19.0?
Thanks
Christian
Click to expand...
Click to collapse
I used BiTGapps but not with Lineage recovery. I was able to install with the latest version of TWRP.

Indiawallah71 said:
I used BiTGapps but not with Lineage recovery. I was able to install with the latest version of TWRP.
Click to expand...
Click to collapse
:+1 That's it.
Now my nearly oldest HW runs the newest Android Version.
So far no lag at all, it feels really fast
Camera does work, but inside Apps like QRCOde scanner nothing is shown so far.
Christian

I was very happy to see that someone made android 12 run on harpia, great job by the way.
I had the problems of ui lag and mobile data but nothing that bothers me, I hope you bring more updates

Will it come officially one day?

Updated to 12L (check OP for links)

althafvly said:
Updated to 12L (check OP for links)
Click to expand...
Click to collapse
is monet already working in this version?

I just installed this ROM twice on my harpy, first impression I found quite fluid even for this model. Then when lowering the notification bar the system would slow down too slow and bug, then give interface error dai or the screen would go dark and erase, after that it gave bootloop. Despite this it seems to be a good ROM hopefully improve this so I can use. Monet's not working.

althafvly said:
Updated to 12L (check OP for links)
Click to expand...
Click to collapse
Hello dear @althafvly. First of all, thank you very much for this awesome ROM based on Android 12L (LineageOS 19.1).
It's very stable, fast and battery-friendly. Please dear friend, continue improving this ROM. I really hope the Encryption, SELinux enforcing and UI Lag can be fixed.
One week ago, I had AICP ROM (Android 11) ( @jeferson1979 ), and It is a very stable ROM, but it has two big problems: It's kinda slow and everytime I try to install an weekly update, the whole system is damaged. I really don't know why this happen. I only boot to Recovery and flash the updated ROM, after that I cannot boot.
Tired of that, I tried this Android 12 ROM and wow it's amazing.
Please althafvly, can you add the Security Features that Disable the Quick Settings (Notification Bar) and Disable the Power Menu from Lockscreen???
Thanks again both developers.

Wait....

Testing on my XT1607. I'm getting "System UI isn't responding" once the pulldown menu finally loads (very laggy). One idea is this could be happening whenever the camera & flashlight options aren't working? When the camera and flashlight started working after a few reboots, the pulldown menu stopped being laggy.
The ability to connect to a Wi-Fi hidden SSID has now become fully broken in harpia with 19.1. For some reason, the initial setup wizard *can* connect to a hidden SSID, but, after that, if you ever disconnect from it, you can't connect to it ever again, nor can you ever add it fresh and connect to it. This is further deterioration of the following bug: https://gitlab.com/LineageOS/issues/android/-/issues/2678
Btw, I was able to get data and SMS to work, but not calling, for whatever reason.

mmortal03 said:
Testing on my XT1607. I'm getting "System UI isn't responding" once the pulldown menu finally loads (very laggy). One idea is this could be happening whenever the camera & flashlight options aren't working? When the camera and flashlight started working after a few reboots, the pulldown menu stopped being laggy.
The ability to connect to a Wi-Fi hidden SSID has now become fully broken in harpia with 19.1. For some reason, the initial setup wizard *can* connect to a hidden SSID, but, after that, if you ever disconnect from it, you can't connect to it ever again, nor can you ever add it fresh and connect to it. This is further deterioration of the following bug: https://gitlab.com/LineageOS/issues/android/-/issues/2678
Btw, I was able to get data and SMS to work, but not calling, for whatever reason.
Click to expand...
Click to collapse
the same thing happened to me "System UI isn't responding" once the pulldown menu finally loads (very laggy)." and after that it goes into bootloop. It looks like a good rom, but maybe the ram consumption will be less than the other rons ? | Which rom do you think has the lowest ram usage/light for the moto g4 play ?

Victoraguiart said:
Which rom do you think has the lowest ram usage/light for the moto g4 play ?
Click to expand...
Click to collapse
Good question. Unfortunately, I haven't done that test.

mmortal03 said:
Good question. Unfortunately, I haven't done that test.
Click to expand...
Click to collapse
I think there is the cornerstone

Better Mobile App

welcome