[OFFICIAL] LineageOS 18.1 for the LG G5 - LG G5 ROMs, Kernels, Recoveries, & Other Developme

[OFFICIAL] LineageOS 18.1 for the LG G5 - LG G5 ROMs, Kernels, Recoveries, & Other Developme

{
"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"
}
LG G5
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the LG G5.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
h830
h850
rs988
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
IMS (VoLTE/Wi-Fi Calling) doesn't work due to framework tie-ins used by the LG proprietary binaries.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_lge_msm8996

Well done!
Best wishes,
Bob

Official now, I'm still using this device thanks to npjohnson, x86cpu and aleasto Well done

bicho2015 said:
Official now, I'm still using this device thanks to npjohnson, x86cpu and aleasto Well done 
Click to expand...
Click to collapse
I think it has been official for a while now...this is just the first official, official thread.

I have a question to someone smarter than me. I've already looked this up on XDA forums and even submited a bug report (via Lineage's official bug report page alongside a logcat) but it seems this particular problem is still present in Lineage 18.1 (and has been present throughout all builds I've tried - beginning with Lineage 15.1). In fact, it's a two-sided problem I'm really surprised to see no one else is reporting for the H850 (International).
The issue concerns microphone gain level and speaker sound (but just the speaker - headphones work fine).
In case of the microphone, its gain level is particualry nonexistant. If I record using the camera app, I can't hear almost any sound in recorded videos, except for massive distortion and crackling sounds (unless I boost the volume level to max - in which case I can hear some of the recoded sounds, but the distortion/crackling also gets louder to the point of being completely unacceptable). It's the same when I use the built-in sound recording app and listen to what I recorded.
The second thing - related in a way - is the speaker audio quality. The speaker produces tons of distortion and crackling sounds - whether its watching videos, listening to music etc. Up to the point I get worried that I'll damage the speaker by continuing using it. Again - just the speakers, not the headphones.
What I've tried to do to resolve the problem(s) so far:
- Downloaded various audio / equalizer apps nad tried to deal with the distortion/crackiling sounds - none of them helped.
- Used an app to boost micrphone gain level - gain level increased, but so did the distortion/crackling.
- Tried reverting back to stock OS (problem dosen't occur on stock OS) and then installing first Lineage 15.1, then 16 and then 17.1 - but the issue remains on all builds.
- I replaced the chin/bottom panel (the one containing the microphone and speaker) thinking it might be a hardware issue. It's not - it didn't change anything.
I assume it has something to do with the audio driver Lineage is using for LG G5 H850? I found a post here on the forum, where someone mentioned that Lineage is using a driver/audio frequency which is dedicated for newer phones, and not for older ones, like the LG G5.
Is there a way to perhaps extract the audio/microphone/speaker drivers from stock androind 8.0 and use it with Lineage 18.1? Perhaps that would resolve the issue, but I'm not sure if that's at all possible. Has anyone else using H850 encountered this issue and found a soultuion? I'd love to continue using Lineage but it's really diffcoult without resolving the matter. Sorry about the lenght of the post and many thanks to anyone interested in looking into this.
P.S. To be a bit more specific: a subtle audio distrotion / crackling sound is present on stock Android 8 Oreo, but it's barely hearable unless I put my ear next to the speaker and actually look for it. It's like a subtle white noise / hissing in the background. When I Install Lineage, this "noise" gets strenghtened and boosted into forground, as if Lineage magnifies it and turns into crackling.

I just checked my phone. I'm using 18.1 self built on 30 March, with no changes to audio. The phone is H850. I've gone from lineage 14 -> 15 -> 16 -> 17 -> 18. I've never used stock on it.
1. Playing music or audio books over the speakers sounds fine (given the quality of the speakers). No crackling or distortion.
2. Recording with the Recorder produces an audio file that is on the low side with regard to volume, but no particular distortion.
3. Ditto for recording with Open Camera.
Best wishes,
Bob

rfrazier said:
I just checked my phone. I'm using 18.1 self built on 30 March, with no changes to audio. The phone is H850. I've gone from lineage 14 -> 15 -> 16 -> 17 -> 18. I've never used stock on it.
1. Playing music or audio books over the speakers sounds fine (given the quality of the speakers). No crackling or distortion.
2. Recording with the Recorder produces an audio file that is on the low side with regard to volume, but no particular distortion.
3. Ditto for recording with Open Camera.
Best wishes,
Bob
Click to expand...
Click to collapse
Thank you for your reply. I was about to ask which version of stock Android you migrated from, but then I noticed you never used stock. Maybe I could recerate the same route (starting with 14 and stopping at 18) to see if the problem persists. I'm not entirely sure how should I go from zero to Lineage 14 though. Does this indicate formatting all data (in TWRP recorvey/wpie) - as this would presubmly wipe any traces of previous audio drivers - or should I check other options in the 'advanced wipe' section of TWRP and avoid formatting data, as that would wipe everything whatsoever and leave no ground at all for Lineage to be installed? Just thinking where should I start to make a clean install as if no stock was involved.
As far as the microphone and video recording is concrened, I've tried using a different camera app - including Open Camera - but this didn't help with the crackling audio nor increase the microphone gain.
Many thanks

ToltecCat said:
Thank you for your reply. I was about to ask which version of stock Android you migrated from, but then I noticed you never used stock. Maybe I could recerate the same route (starting with 14 and stopping at 18) to see if the problem persists. I'm not entirely sure how should I go from zero to Lineage 14 though. Does this indicate formatting all data (in TWRP recorvey/wpie) - as this would presubmly wipe any traces of previous audio drivers - or should I check other options in the 'advanced wipe' section of TWRP and avoid formatting data, as that would wipe everything whatsoever and leave no ground at all for Lineage to be installed? Just thinking where should I start to make a clean install as if no stock was involved.
As far as the microphone and video recording is concrened, I've tried using a different camera app - including Open Camera - but this didn't help with the crackling audio nor increase the microphone gain.
Many thanks
Click to expand...
Click to collapse
I don't see the advantage to cycling through all these versions. Have you just tried a clean install? This would require wiping data, caches, and, perhaps, system. Then installing lineage via sideload or from external storage, adding GAPPS if you use them..
Indeed, just following the instructions for installing lineage given on the wiki is going to give you as clean a system as you are likely to get.
Best wishes,
Bob

The first official nightly build released just today
djskribbles said:
I think it has been official for a while now...this is just the first official, official thread.
Click to expand...
Click to collapse

rfrazier said:
I don't see the advantage to cycling through all these versions. Have you just tried a clean install? This would require wiping data, caches, and, perhaps, system. Then installing lineage via sideload or from external storage, adding GAPPS if you use them..
Indeed, just following the instructions for installing lineage given on the wiki is going to give you as clean a system as you are likely to get.
Best wishes,
Bob
Click to expand...
Click to collapse
I see. I've made a full cycle like that once (stock Android 8 -> 15.1 -> 16 -> 17.1) only beacuse I stumbled upon a post which said this might resolve my issue. It included a dirty flash from 15.1 to 16. Back then - but also this morning, when I installed 18.1 for the first time - I began with wiping data, caches and system. I guess that counts for a clean install then.
When I first heard about Lineage (that was in January I think) I initially went from stock Android 8 -> 17.1 and I've followed all the insturctions found on Lineage wiki (I've even used Lineage recovery instead of TWRP).
By the way, when you say "I've never used stock on it", do you mean the phone came with Lineage 14? Or did you - initially - have some other stock android before moving to Lineage, just never used it?
Other than that, I guess I'm back at square one as I don't have other ideas at present. But still, thanks for the insightful reply!

ToltecCat said:
I have a question to someone smarter than me. I've already looked this up on XDA forums and even submited a bug report (via Lineage's official bug report page alongside a logcat) but it seems this particular problem is still present in Lineage 18.1 (and has been present throughout all builds I've tried - beginning with Lineage 15.1). In fact, it's a two-sided problem I'm really surprised to see no one else is reporting for the H850 (International).
The issue concerns microphone gain level and speaker sound (but just the speaker - headphones work fine).
In case of the microphone, its gain level is particualry nonexistant. If I record using the camera app, I can't hear almost any sound in recorded videos, except for massive distortion and crackling sounds (unless I boost the volume level to max - in which case I can hear some of the recoded sounds, but the distortion/crackling also gets louder to the point of being completely unacceptable). It's the same when I use the built-in sound recording app and listen to what I recorded.
The second thing - related in a way - is the speaker audio quality. The speaker produces tons of distortion and crackling sounds - whether its watching videos, listening to music etc. Up to the point I get worried that I'll damage the speaker by continuing using it. Again - just the speakers, not the headphones.
What I've tried to do to resolve the problem(s) so far:
- Downloaded various audio / equalizer apps nad tried to deal with the distortion/crackiling sounds - none of them helped.
- Used an app to boost micrphone gain level - gain level increased, but so did the distortion/crackling.
- Tried reverting back to stock OS (problem dosen't occur on stock OS) and then installing first Lineage 15.1, then 16 and then 17.1 - but the issue remains on all builds.
- I replaced the chin/bottom panel (the one containing the microphone and speaker) thinking it might be a hardware issue. It's not - it didn't change anything.
I assume it has something to do with the audio driver Lineage is using for LG G5 H850? I found a post here on the forum, where someone mentioned that Lineage is using a driver/audio frequency which is dedicated for newer phones, and not for older ones, like the LG G5.
Is there a way to perhaps extract the audio/microphone/speaker drivers from stock androind 8.0 and use it with Lineage 18.1? Perhaps that would resolve the issue, but I'm not sure if that's at all possible. Has anyone else using H850 encountered this issue and found a soultuion? I'd love to continue using Lineage but it's really diffcoult without resolving the matter. Sorry about the lenght of the post and many thanks to anyone interested in looking into this.
P.S. To be a bit more specific: a subtle audio distrotion / crackling sound is present on stock Android 8 Oreo, but it's barely hearable unless I put my ear next to the speaker and actually look for it. It's like a subtle white noise / hissing in the background. When I Install Lineage, this "noise" gets strenghtened and boosted into forground, as if Lineage magnifies it and turns into crackling.
Click to expand...
Click to collapse
Just wanted to report small progress here.
The good: I've used TWRP recovery -> Wpie -> Format data. Then I've flashed official Lineage 14 and checked the microphone & speaker again. Resoult: everything works falwlessly! Microphone gain level is top notch and speaker works loud and clear with no crackling, hissing sounds or whatever. It's the first time it worked for me on a Lineage OS, that's whay I consider it "small progress".
The bad:
- If I execute the above steps and flash the new/official Lineage 18.1 (instead of Lineage 14), the problem is still there.
- If I try to make a manual upgrade (via adb sideload) from Lineage 14 to 18.1, the problem is still there.
- If I dirty flash Lineage 18.1 over Lineage 14... the problem is still there.
That's that for now. Hopefully a proper solution will sprout sooner or later!

bicho2015 said:
The first official nightly build released just today
Click to expand...
Click to collapse
Sorry I thought you meant the LG going official in general, not specifically 18.1.

OK, I think I messed up bad. I've been applying the 17.1 nighties without issues.
Lineage popped up saying an update was availble. Without me realising it was 18.1, I downloaded and installed like it was 17.1 and now it just loops, is it ****ed up?
Have I lost everything !! noooo. I knew I should of done a backup...Feck!

davestuarts said:
OK, I think I messed up bad. I've been applying the 17.1 nighties without issues.
Lineage popped up saying an update was availble. Without me realising it was 18.1, I downloaded and installed like it was 17.1 and now it just loops, is it ****ed up?
Have I lost everything !! noooo. I knew I should of done a backup...Feck!
Click to expand...
Click to collapse
I installed lineage 18.1 and mindthegapps for android 11 over lineage 17.1 and it works fine .
Try installing gapps for android 11 from sd card, it may fix the loop.

bicho2015 said:
I installed lineage 18.1 and mindthegapps for android 11 over lineage 17.1 and it works fine .
Try installing gapps for android 11 from sd card, it may fix the loop.
Click to expand...
Click to collapse
Oh. I went the other way and I installed the last 17.1 nightly and it's still looping.
When you installed 18.1 and mindthegapps, were all files and apps as normal with settings?
I need a few apps and sms to be accessible at the least if not all?. I'm losing it I think.
My recovery is twrp 3.5.0_9-0.

davestuarts said:
Oh. I went the other way and I installed the last 17.1 nightly and it's still looping.
When you installed 18.1 and mindthegapps, were all files and apps as normal with settings?
I need a few apps and sms to be accessible at the least if not all?. I'm losing it I think.
My recovery is twrp 3.5.0_9-0.
Click to expand...
Click to collapse
I lost nothing, all apps and data the same, just like normal 17.1 update.
I use orangefox recovery.
You may try installing magisk canary zip, it also fix the bootloop sometimes.

bicho2015 said:
I installed lineage 18.1 and mindthegapps for android 11 over lineage 17.1 and it works fine .
Try installing gapps for android 11 from sd card, it may fix the loop.
Click to expand...
Click to collapse
Oh. I went the other way and I installed the last 17.1 nightly and it's still looping.
When you installed 18.1 and mindthegapps, were all files and apps as normal with settings?
I need a few apps and sms to be accessible at the least if not all?. I'm losing it I think.
bicho2015 said:
I lost nothing, all apps and data the same, just like normal 17.1 update.
I use orangefox recovery.
You may try installing magisk canary zip, it also fix the bootloop sometimes.
Click to expand...
Click to collapse
Ok thx, really appreciate this, I'm still panicking. I'll install 18.1 again and mindthegapps. I cannot find the magisk canary as a zip, apparantly its all changed to an apk install.
update: Mate you're awesome!! So glad it worked! I'm just trying to figure out new magisk install method, but I'm back in. Phew! Appreciate the support.
Back to doing backups! Been doing this for years, and this time..damn...

If you're phone is misbehaving and you never did Stock updates, I highly recommend doing a full wipe/format and flashing the latest Autoprime's COMPLETE flashable stock packages for your G5 via TWRP (whichever specific model you have)
I've experienced odd issues when using custom ROMs on the G5 that were fixed once doing so. Those full updates made an update to something important to whichever partition (boot, modem, who knows) that later Lineage builds are based off of.

Ok, so far so good. This accidental update from 17.1 to 18.1 had me sweating for a few hours.
My fault for not noticing the update number and noit creating a backup.
I've been on custom roms a while with this phone and each major update, I'll always start with a fresh one, so my 17.1 was fresh but as this time thinks got messed up, I've essentially had to dirty flash to 18.1, with reassring advice from here.
This rom has randonly crashed and restarted 3 times so far, and I think it was down to twitter app, so I've updated my most used apps to see if that helps.
If things continue to crash/restart, I'l lsave important apps/data (migrateGPE app worked well before) and then do a fresh install of 18.1. After having a panick mode before, I've already created a twrp backup.
The ROM generally works fine, quite speedy and all connectivity works as it should.
Appreciate the continued support for this phone

I'm back on LOS from Havoc not wiping data partition, but wiping everything else. Settings are crushing on me when I try to enter About System. Is it just me or not?
Now phone restarted randomly. That never happened before on LOS.

Related

Xperia XZ Pie ROMs Questions and Answers Thread

Unified support thread for Pie Xperia XZ ROMs
You can discuss the following here:
Unofficial OmniROM 9.0 for Xperia XZ
Project Treble for Xperia XZ
AOSP Nightly Pie builds for Xperia XZ
Please keep the development threads clean and help each other out in this thread instead.
Telegram Group for General Discussion

Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
DO NOT REPORT ISSUES WITH GSIs! Ask the GSI maintainer to fix them!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat, we CANNOT help you otherwise! (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!

Reserved #2

Im a hour ago flashed an newest Omni build and its stucks on bootanimation ? I had flashed: OEM Tone V5, Omni 24-01-2019, Magisk 18.0 and Open Gapps Pico 27-01-2019
---------- Post added at 08:04 PM ---------- Previous post was at 07:13 PM ----------
Now i have the answer. With gapps is smthg not good for Omni. I used RR Treble with that and there it was working :/

How about camera? Still dark photos or maybe something change in New builds?

i just flashed aosp_f8331_2019-02-06-NIGHTLY.zip.
then... my telephone receiver and microphone not work (no voice)

delichik said:
i just flashed aosp_f8331_2019-02-06-NIGHTLY.zip.
then... my telephone receiver and microphone not work (no voice)
Click to expand...
Click to collapse
Post logs or we can't help you. Are you running GApps? Do you mean you can't call at all? Or just no sound? This level of information you're providing is useless for helping you.
Slawek1995 said:
How about camera? Still dark photos or maybe something change in New builds?
Click to expand...
Click to collapse
You can help out with the calibration of the RGBC-IR sensor(named "CASH"
Stick this into /vendor/etc/cash_expcol_calibration.xml https://git.ix5.org/felix/device-sony-kagura/commit/a0253f3de75c52bccb9275ee7eda6cd2f9db539c and tweak the values. You need to restart the CASH server via "stop cashsvr" and then "start cashsvr" after you've modified the values. You can then grep the logcat for "cash" and see the generated values.
The "clear" value is for brightness, you can then adjust the exposure and ISO for the individual steps.

local__hero said:
Post logs or we can't help you. Are you running GApps? Do you mean you can't call at all? Or just no sound? This level of information you're providing is useless for helping you.
You can help out with the calibration of the RGBC-IR sensor(named CASH
Stick this into /vendor/etc/cash_expcol_calibration.xml and tweak the values. You need to restart the CASH server via "stop cashsvr" and then "start cashsvr" after you've modified the values. You can then grep the logcat for "cash" and see the generated values.
The "clear" value is for brightness, you can then adjust the exposure and ISO for the individual steps.
Click to expand...
Click to collapse
oh sorry, i found it is my mistake.
i flashed the official ftf, then flash your rom. now its alright.
thanks for your work

I didn't try aosp roms since long time. Still front camera focus problems(stuck on macro)? Gcam mod works? If yes wich version is adviced? Thanks.

porting of xperia xz3 (pie)
why are developers not make porting of xperia xz3 (pie) to xperia xz dual and use it for stock and unlocked stock?

Which of the 3 versions is the most stable and could be the candidate to remove the official ROM? ... or would I have to wait a little longer? ... I'm tired of not receiving updates, and I get the feeling that the phone is getting slower

When headset connected and playing music (blackplayer) if a notification comes up music stops giving sound but playing. After trying opening volume up & down closing all applications it comes back. Same thing happens if a call comes in when listening music. Music stops but i can't hear any voice from call, doing some things and closing call waiting for the another or i call back it fixes.
Anyone having same problems?
Using oem5 f8331, feb 06 build android 9.0 from sx.ix5.org

RGBC-IR sensor corrects when? The camera quality is really bad

Hey guys!
Sorry if I write in the wrong place. But I flashed OmniROM 9.0 and have some problems:
- If I call they don't hear me and I don't hear them (Not even calling sounds, tried with 100% working Bluetooth headset too)
- Microphone not work in any apps
- Only the lower speaker works
- When phone turn on the first thing I see after boot animation is an error message; "There is an internal problem with your device" or something like this in my language
- IDK why but the phone slows down extremly for no reason sometimes. But the bigger plreblem is the call problem.
Xperia XZ Single SIM

Hello
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I have attached the dmesg and logcat Hello
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I have attached the dmesg and logcat on del.dog <slash> arepacivaf.coffeescript
(seems I cannot post links due to forum rules)
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
I am running the latest FTF for my region (192) and OEM version 6.
If you need more info or I should be posting this somewhere else, please point me in the right direction
Thank you
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
I am running the latest FTF for my region (192) and OEM version 6.
If you need more info or I should be posting this somewhere else, please point me in the right direction
Thank you

Okay... I installed latest rom, latest oem, the old (working) TWRP and...
It's okay now. Everything seems to work.

SoulJahN2 said:
When headset connected and playing music (blackplayer) if a notification comes up music stops giving sound but playing. After trying opening volume up & down closing all applications it comes back. Same thing happens if a call comes in when listening music. Music stops but i can't hear any voice from call, doing some things and closing call waiting for the another or i call back it fixes.
Anyone having same problems?
Using oem5 f8331, feb 06 build android 9.0 from sx.ix5.org
Click to expand...
Click to collapse
Please give us a clean log and file a bug report at the sonyxperiadev bug tracker.
Make a clean re-install without Magisk or GApps and get a logcat and dmesg from boot until your calling issue.
Botchcamp said:
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I am running the latest FTF for my region (192) and OEM version 6.
Click to expand...
Click to collapse
What ROM are you running? Which version? Did you wipe/format userdata before installing the ROM?
Botchcamp said:
I have attached the dmesg and logcat on del.dog/arepacivaf.coffeescript
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
Click to expand...
Click to collapse
It looks like you are running Magisk and GApps. Please clean-install without them and get us a clean log.
Then open an issue at the sonyxperiadev bug tracker.
xda is a horrible place to to actual development, so please try to follow the guides and report bugs in the appropriate places, we cannot monitor everything here.

Se Neo said:
why are developers not make porting of xperia xz3 (pie) to xperia xz dual and use it for stock and unlocked stock?
Click to expand...
Click to collapse
For a number of reasons, here are some examples:
Copyright. Sony software is copyrighted and if we "ported" it, we could get sued.
Different platforms: The Xperia XZ is based on the Snapdragon 820 chipset. The XZ3 is based on the SDM845 chipset. They have different CPU architectures and capabilities.
It's hard when you don't have the source. We compile everything from open-source projects here. If you try to port stuff from the XZ3, you have to decompile the binaries to make them work with the Xperia XZ.

Hello there, i have a problem here about installing aosp rom on my XZ F8831 phone, can i ask it here? So i followed everything on your page including latest tft, flashing oem, flashing dsp, but my phone stuck on white sony logo without installing magisk/gapps. When i try to reinstall it but with gapps, i got this message when i try to flash the gapps, "this gapps is for device that have 9.0 android, your device is 8.0" something like that, so i assume anything i do before is useless, because my phone still on 8.0. Please can someone help me? Im sorry for the bad english

Hey guys!
I have problem with Treble on XZ (Single SIM)
I want to try some interesting GSIs but I never able to make any of them work. I tried like 10 different GSIs already.
So if someone can help me telling what I do wrong and someone can help me to make even one GSI work I would be super happy.
So I started everything from the beggining so reflashing the stock rom with flashtool, then flash the modded TWRP oem-vendor and then flash AOSP treble.
Then wipe everything (I tried without wipe and wipe system too not just caches and data. Every combination)
Then "fastboot flash system gsi.img"
When done I turn on phone SONY logo then restart and loop
So I read need to fix dsp (I not really understand this part) but I don't know how to use the codes or if I use them I got errors (I will write down errors if need)
So I used this;
https://sx.ix5.org/files/builds/kagura/misc/dsp-label-fixer.zip
After I installed gsi I turn on phone in recovery mode then flash dsp-label-fixer.zip. Is this ok? Need to do after every single flash or not even need?
Or if I need to use the codes where to write to make it work?;
Code:
[COLOR="DimGray"]su
# It might be either /system/vendor/dsp or /vendor/dsp depending on your device
# Just try both until one succeeds
mount -o remount,rw /system/vendor/dsp
chcon -R u:object_r:adsprpcd_file:s0 /dsp[/COLOR]
When I ask help last time you I get an answer about selinux. I don't really know if it's help or not, but I downloaded permissiver and flashed it. Same question than with dsp. Need to flash every time or after every rom install and before boot it?
What can be wrong? Why I never make trough the SONY logo with GSIs?
I already isntalled OmniROM and Pie 9.0 rom without problem. Even Treble is boot but without GSI, after installing a GSI image bootloop.
I read a lot and watched videos but still the same problem.
I hope someone will help me, I want to learn but I don't know what I do wrong and what to learn exactly. ?
Sorry for a lot long questions and bad English and being dumb.
Thank you for the answer!
KikiGames

[DISCONTINUED][ROM][STABLE] LineageOS 16.0 (unofficial) for ZTE Axon 7 Mini (aka tulip)

Unfortunately the hoster where my build server is located raised the fees and i had no way to download a backup of my data... As i can't afford it now i had to delete everything. With a heavy heart I have to discontinue this great ROM for a great phone..
- first of all, thanks to @tdm for his tremendous effort to have us all enjoy LineageOS in the first place, without his contribution this thread would never exist. Also thanks for tdm's Lineage 14.1 where I took this post's layout from -
{
"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"
}
Gentlemen,
The time has come to share what's due to be shared.
Supported devices
* US model running 7.1.1 b14 firmware
* EU model running 7.1.1 b12 firmware
Pre-requisites
Make sure to have at least this TWRP version installed
Patience as first start takes a while
First time install Instructions
Use these instructions when coming from any other ROM (stock, AOKP, LineageOS 15.1, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe 'Dalvik/ART Cache', 'System', 'Data' and 'Cache'
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage 16.0 build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
This is currently stable quality
Known issues
Very minor graphical glitches
sometimes videos don't play, you have to remove the relevant all from your recent app list and restart (e.g. WhatsApp)
AKM DAC is not supported
Selinux permissive
To Do list
Implement Camera2 API Thanks for customizing libraries and not sharing any code or insight ZTE
Get DSP to kick in for high quality audio again
Download
Google Drive
* works well with open gapps
Sources
Device tree
Kernel
Vendor
Note: please refrain from requesting other Android distributions from me, like AOKP, AOSP, etc - this is most likely not going to happen from my end. As I provided all my sources you can fork the stuff yourself and try to build
Special thanks
@R3bornD4rth for having provided me an axon 7 mini for my testing/debugging, which is heavily in use and doing great so far
@tdm for his original work on this
@armandop_ for his ZMAX Pro Repo and help getting LiveDisplay to work (flawlessly, thanks mate)
intervigilium aka Ethan Chen for his work on HTC One A9 (hiae) (which shares the same chipset as our phones)

Thanks for this rom, there's a way to make work the camera API 2 (in the future)?

jose_777.mx said:
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
Click to expand...
Click to collapse
Good question, no clue if I will be making it to work somehow I can try to get some pointers if there are just some drivers to be altered or whatever is needed to have this done

I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!

bius88 said:
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
Click to expand...
Click to collapse
Cool!
Would be better if GPS and Cam would work though I am working on GPS right now, will soon test my latest build, so fingers crossed

Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks

Holyoblation said:
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Click to expand...
Click to collapse
What? The camera really works? Then I shall replace the camera app with another one maybe ?

Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.

koktey14 said:
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
Click to expand...
Click to collapse
I see 2 issues here to be fixed. first with the video playing will be added to my known bugs post, the flashlight thing is related to the camera not working (pretty sure at least)

Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now

TheSSJ said:
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
Click to expand...
Click to collapse
Can there be a chain problem with sim card, graphics or camera maybe

koktey14 said:
Can there be a chain problem with sim card, graphics or camera maybe
Click to expand...
Click to collapse
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)

TheSSJ said:
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
Click to expand...
Click to collapse
Apparently I fixed wifi I rebooted 15 times to be sure and it always turned on, GPS still functioning as well!
I will update the OP and proceed with cam (which is so broken that not even 3rd party apps work at the moment)
EDIT: Notification lights fixed as well

@TheSSJ -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?

Hi, thanks for the hard work. Does the firmware support fast charging?

BAPK said:
Hi, thanks for the hard work. Does the firmware support fast charging?
Click to expand...
Click to collapse
Yes, as this is setup on kernel side the stock settings have been just kept

k500zm;79544339 [user=2388665 said:
@TheSSJ[/user] -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Click to expand...
Click to collapse
Twrp is the same with oreo i installed it.
I was thinking about aokp too but didnt want to put pressure on you. you are already busy. @TheSSJ what do you think about this?

Once I fixed all issues with LOS16, compiling aokp should not be too hard, but I can't promise it

Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.

koktey14 said:
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
Click to expand...
Click to collapse
Strange,i just clean installed and it is working really fast
Can you provide dmesg and logcat please, then I can check

[Treble GSI] [Umidigi One Max] GSI Experiments

Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10
Apparently it works as shown here: https://forum.xda-developers.com/showpost.php?p=80319007&postcount=13 credits to @4ctiv_
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Tethering doesn't work with data ON !
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
NFC doesn't appear at all. There is a fix with magisk tho ! See here (NFC4PRA)
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone

Make sure to check out my guide on installing GSIs at https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/

I downloaded system-arm64-ab-gapps-su.xz, extracted the file, booted into TWRP, did a full wipe, and installed "image" system-arm64-ab-gapps-su.img. TWRP asks which partition to install it to. I selected "system". However, after install I go to reboot, and TWRP complains there is no OS. Am I missing something?
I did a complete backup in TWRP of all important partitions first (nvram, modem, system Etc.), so going back to my stock setup was not difficult. Those trying this, backup all important partitions from TWRP on to microsd!

For everyone, make sure you download AONLY images, not AB !

_cab13_ said:
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10 Q Beta
Beta 4 : Probably not working, as our device is not system-as-root (but is VNDK isolation compatible)
Still needs testing
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Wifi access point doesn't work.
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Click to expand...
Click to collapse
I posted this in another forum, but for the life of me I do not know what is causing this issue. I installed RR rom located here:
https://get.resurrectionremix.com/?dir=gsi/
system-190120-arm64-aonly-vanilla-nosu.img
I also install, Gapps (pico), and Magisk.
It runs great, for the most part. However, if I start streaming a video from any app or start streaming music, after a short amount of time my Umidigi One Max:
A.) Announces, "Powering Down"
B.) Boots directly into TWRP
C.) If I reboot, it again boots directly into recovery. Almost as if the partition became corrupted.
D.) Try to recover a backup I made in twrp, reboot, again boots straight into recovery.
E.) If SP Flash can communicate with the phone, I can usually push all the stock images back to the phone. If not, I have to push the images via fastboot with my Ubuntu PC.
If I do any other CPU intensive task under a GSI ROM, it doesn't have this issue, only when I stream video. I haven't tried any games to see if it causes this behavior.
I have tried multiple GSI Roms located here too, same problem:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I do not believe the device is overheating, it's usually around 32-34C from the TWRP menu at that point. I really like the RR Rom, but if I cannot figure out what is causing this, I'll have to stray away from GSI for now.
As a sidenote, this issue of the device suddenly powering down after starting to stream a video, does not happen with the stock ROM. I am kind of at a loss on this one.
Weirdest thing I have experienced running a custom ROM.

Yeah it happened to me sometimes as well... The phone goes straight into recovery and then never goes to system again. I haven't found the cause of it.

Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)

phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.

w1lh3lm3d said:
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
Click to expand...
Click to collapse
I posted a fix that works. Here it is if you didn't see : https://forum.xda-developers.com/p8...pment/flashable-nfc-kirin655-devices-t3811916
tomprc said:
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
Click to expand...
Click to collapse
I don't get any performance issue. The only issues is that some ongoing calls doesn't come, and sometimes 4G totally glitches out. Other than that it's pretty much all.

@ _cab13_
i cant find the vendor folder in twrp in the mount section or in the file manager.
what have i done wrong? ok i started from scratch and then it worked porfectly
thx you for your work and help

Engineering mode access or work around
On the 9.0 ROM I cant seem to access engineering mode via the keypad, I need to sort the handset speaker out. Is there any other way to access it or some way of tweaking the voice settings through the shell?
Any help would be appreciated.

Please help
I'm trying to get the new phh Android q to boot and and I'm a newbiew

Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )

On Phh's 9 v119 Is the headphone jack sensor working for anyone. (If so how)

4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
Click to expand...
Click to collapse
did you use the a only or ab image?

I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!

seiyria said:
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
Click to expand...
Click to collapse
I'm in the same boat bro. I've just tried both the latest phhusson AOSP 10 ROM as well as an older version of the same ROM, and both time I get caught in a loop after install. Completely wiped beforehand, tried installing with and without Magisk/Disable-Force-Encryption. Going to have to bring it back down to Android 9. I wonder how 4ctiv_ got it working?

so first you have to no encryption then erase and format data
flash android 10 arm 64 a without gapps build (image) to system i use havoc 3.5 and everything exept nfc works
then install gapps (it failed for me so i had to resize system in twrp and install gapps again
last step is to flash the custom phhson magisk
then just reboot wihout wipping

Thank you so much for your work...
Hi, I'm a long time Android user and I used to code apps, if I can be of any help please let me know but I'm now disabled wheel chair user with dystonia so I find it extremely difficult to type now so I use voice to text... I really enjoy using the umidigi one max it has the storage and usability of a much more expensive phone, also functionally for me the wireless charging and NFC make my life so much easier as I find cables akward and payments at shops much easier.
I read about the Treble programmea while ago and recently read this article and if it is possible to get the NFC working on this update, I will be so greatful as it will extend the life of this great phone for me.
Good luck with your work and thank you in advance.
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
Click to expand...
Click to collapse

[GSI][10] Lineage OS 17.0 For Galaxy J6

DICLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM 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.
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
[GSI][10.0] Lineage OS 17.0 Galaxy J6
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, Gerrit code
Click to expand...
Click to collapse
SO, Here Is The Unofficial Lineage OS 17.0 GSI Working On Galaxy J6.
Follow The Instructions To Flash It .
REQUIREMENTS/DOWNLOADS :
Unlocked Bootloader
TWRP Installed
GSI Image : DOWNLOAD
10.0 j6 Vendor : DOWNLOAD
Flashing Instructions
[*]Unzip Downloaded GSI Image , You Got an .img file
[*]Boot In TWRP
[*]Wipe system, data, dalvik&cache, cache
[*]Install Vendor.Zip file
[*]Reboot To Recovery
[*]Select Install Image Option In TWRP
[*]Install extracted Image File
[*]Again Reboot To Recover (Don't worry if no OS installed error comes just go ahead )
[*]Now, At last reboot to System
[*]OPTIONAL : Flash Gapps (DOWNLOAD) After first Boot (It Takes Around 10min For First Boot )
SCREENSHOTS
https://ibb.co/CsLdW2k
https://ibb.co/mFFPMv3
https://ibb.co/8smXSqM
https://ibb.co/MRX7sQr
https://ibb.co/f9SDK0n
https://ibb.co/YtHrsXp
video tutorial :
https://youtu.be/Zz-VZ9sXlX0
creditsAndyYan
Sent from my J6 using XDA-Developers Legacy app

Ok so I have a bug while using this rom(j600fn). Except from the casual sim calls, I also get this even in apps,for example messenger. The problem occurs not all times, but it's not rare, someone calls me, I pick it up and I can hear them but they can't hear me. After they hung up and call me again everything works fine. Any piece of advice? Thanks for reading and also thanks for keeping the j6 alive.

Kostas172 said:
Ok so I have a bug while using this rom(j600fn). Except from the casual sim calls, I also get this even in apps,for example messenger. The problem occurs not all times, but it's not rare, someone calls me, I pick it up and I can hear them but they can't hear me. After they hung up and call me again everything works fine. Any piece of advice? Thanks for reading and also thanks for keeping the j6 alive.
Click to expand...
Click to collapse
Hi @Kostas172
Thats a bug,no solutions till now .wait for next build.
Sent from my [device_name] using XDA-Developers Legacy app

This is from telegram right ? Nice kang man

Help
Can this be installed on 32bit one ui? Asking this because i saw many arm64 gsi where it said not to install on 32bit one ui

some things that i can relate and maybe will help you with debbuging
!!this was meant to be posted on reddit but lineage community is all sicko about unofficial builds!!
model: Samsung Galaxy J6 (j600GT/DS) 64GB 3G
Let's get started:
IMGUR link: imgur. com /gallery/E76ffQF
Camera issues:
1- video streches and morphes as i turn the camera (SOLVED: downscale video settings to 720p)
2- recorded video file corrupted (3 seconds video turn into 30sec video with just a static image and sound) (FIXED: install camera2api module with magisk)
Calling/Broadband issues:
3- LTE/phone signal too low, sometimes NO SIGNAL
4- Calls don't work in loudspeaker mode
Battery issues:
5- Battery takes hella time to charge (2 hours in ONE UI, and in LOS i plug the phone, go to sleep, and wake up in the next day in 80-90% [still charging]. Comparison made with a non-turbo charger, starting at 15%)
6- Battery drains hella fast, i need to keep my phone in Battery Saving mode to make it last almost to the end of the day (on ONE UI it last until midnight with 10% left) (i also tried deactivating the AOD, but it is not what is consuming all of the battery). (ammenized by turning off AOD)
Play store issues (it's more of a question):
7- some apps (like netflix) count as "This app is not compatible with your device", is that because of the security of lineage not being approved by google?
i also have some questions on things as:
q1- does lineage have a app like samsung's theme store? and can you customize the AOD?
q2- will i receive normal updates as i'm using an UNOFFICIAL release?
EDIT 1:
-whatsapp video call gets all black, but the video is rolling on the other user's phone

I have a fairly serious bug every 20/30 minutes the device restarts me on my own. is there a solution?

henks99 said:
I have a fairly serious bug every 20/30 minutes the device restarts me on my own. is there a solution?
Click to expand...
Click to collapse
Yes, get a new ROM and kernel.

The rom is very wonderful ... Thank you very much ...

henks99 said:
I have a fairly serious bug every 20/30 minutes the device restarts me on my own. is there a solution?
Click to expand...
Click to collapse
From recovery. Wipe Cache and Dalvik Cache..
If problem Still Exists..
Reinstall rom...
Sent from my [device_name] using XDA-Developers Legacy app

Is work samsung pass with root?

Its support VOLTE ?

Well,
I gave it a fair shot. Had trouble getting superuser, untill I read somewhere that Magisk is breaking things like adb. Also some other functions apparently... So SuperUser it was..
However... things happened that made me revert to the previous version:
- The device reboots regularly, like twice an hour.
- LastPass refuses to start...
- Battery drain
- File Transfer over USB (mtp) is broken
pity...

FreakyJoost said:
Well,
I gave it a fair shot. Had trouble getting superuser, untill I read somewhere that Magisk is breaking things like adb. Also some other functions apparently... So SuperUser it was..
However... things happened that made me revert to the previous version:
- The device reboots regularly, like twice an hour.
- LastPass refuses to start...
- Battery drain
- File Transfer over USB (mtp) is broken
pity...
Click to expand...
Click to collapse
well, it took me a few nights but i found the problem.
so basically, when you flash the vendor file it flashes magisk 20.X
but the rom has it's own su built in!
so magisk and the phh su fight and cause random reboots.
this is the procedure to fix the issue:
1. open adb
2. type "adb shell"
3. type "su 0"
4. type "/system/bin/phh-securize.sh"
5. download magisk 22 apk, and rename it to be a zip file(just change the .apk to .zip at the end)
6. flash it in twrp
7. rename the zip to apk and install it, or just download it again and install it.
8. you're done!
i got mine to work perfectly after that. no battery drain(except for AOD), mtp started working again and all the problems were fixed.
please let me know if it had worked out to you!

Well, been a long time now... Good to hear someone did find a solution.
I never read this until now, and I got a different phone now.
But hey, maybe I'll give it a try once I find some spare hobby-time. I still have the device.
Cheers on you for making it work!

[ROM]|SM-T520|SM-T900|[UNOFFICIAL] LineageOS 17.1 | Android 10

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Special thanks to Exynos5420 team and LineageOS for all the sources.
Use SM-T900 build at your own risk. I can't guarantee you it will work, because I have no device to test it on.
Work
Almost everything
It has pretty much the same functionality as Lineage 14.1
Known Issues
Built in mic not working
USB problems
You tell me...
Installation:
1. Flash latest official Samsung Firmware with ODIN
2. Flash latest TWRP Recovery: SM-T520 - SM-T900
3. Backup all partitions
4. Wipe Cache and Data
5. Install ROM.ZIP
6. Install latest GApps (ARM/Android10) https://opengapps.org/
7. Reboot and Enjoy
8. Optional: Install Magisk
For SM-T520 TWRP recoveries 3.1.1.0 and older will not flash this rom ending up with error 7: incompatible device.
Make sure to flash TWRP mentioned above.
Download:
SM-T520
SM-T900
I ll probably create builds with updated security and device code patches occasionally.
Enjoy fresh new Android!
Sources:
https://github.com/LineageOS (LineageOS 17.1)
https://github.com/exynos5420/ (Kernel, Device, Vendor)

Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!

@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.

manix01 said:
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
Click to expand...
Click to collapse
You got it there try it out!

Larision said:
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
Click to expand...
Click to collapse
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)

pjotrski1000 said:
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
Click to expand...
Click to collapse
You don't need to go stock, just backup your data using TWRP and follow installation steps above. I am little unsure about build for T900 because I do not own this device, so I wait for someone who can report me if it works or not.

@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.

kb8no said:
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
Click to expand...
Click to collapse
It has probably something to do with missing play protect certification. I will try to sign device for certification but need someone with T900 who will cooperate with me. For now easiest way to avoid problem is going to browser version of play store and installing paid app to specific device from there. It should work fine. Also thanks for testing and reporting that T900 build works.

Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?

@TechDriver SELinux is not enforcing. That may be why Google Play does not recognized my purchased apps. Installing purchased apps trick from Google Play on the web worked as expected. Booting tablet, it does not accept passcode on the first try, but works on second try. This is repeatable. I will be happy to be your T900 tester if you make some test builds.

hamudistan said:
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
Click to expand...
Click to collapse
Exynos5420 is 32bit SoC. It doesn't support arm64

@TechDriver The pass code works the first time if you are not impatient and click the accept arrow before the last number changes to a dot. There is a delay and the passcode entry is laggy and you have to be patient for a few seconds. twrp-3.5.1_9-0 is able to back up and restore 17.1 with no problem.

@TechDriver The first login with PIN after booting will fail. The second and future screen saver logins will work with the caveat that you are patient until the last number turns into a dot.
Pixel launcher does not work correctly with mouse clicks and has a focus graphics glitch. It works right as long as you don't click the mouse. If you click with the mouse to open a group of icons in a folder it leaves a residual grey box behind. You can see this same grey box where the PIN numbers appear on the screen saver as well. I changed to Nova Launcher and the problem improved with the grey box occurring if I open the icon folder and actually open an app but then disappearing on moving into a different folder. This is all with the exception of the PIN screen saver which causes the same grey box on both launchers. Something is not quite right with the graphics using mouse.
I mostly use this tablet with keyboard and mouse and Nova is more acceptable now. I prefer Nova Launcher anyway as it is much better at using the whole screen.
The camera is extremely basic. Open Camera seems to be an improvement. Any Google Camera port available that might work?

Just to make things clear, I am not developer of code and not skilled enough to make changes in it. For this job, there is team exynos5420 and other cool contributors to make device sources. I use their device sources from exynos5420 and LineageOS github to build together final product... Rom.zip you install on device. I can't fix bugs, i only can wait until some contributor fixes it and I will build rom with fixes and updated security patches included.

@TechDriver Got it. Will the devs be watching this thread for feedback?

kb8no said:
@TechDriver Got it. Will the devs be watching this thread for feedback?
Click to expand...
Click to collapse
I am unsure about that, most of original devs for n2awifi and v2awifi stopped developing code for this devices. Keep an eye on exynos542X github for new commits.

First of all I want to thank you for the this ROM.
I tried this ROM with the latest TWRP version for two days and I want to inform that it is working good with some small non-conformities:
I had some random reboots and the system crashed and freezing
After rebooting there is a long time after entering the unlock pattern, sometimes it is necessary to enter the pattern several times.
I have installed ROM, gapps nano rebooted and after that install Magisk 22.1
my model is SM-T900

@TechDriver ,Great work on this build! Never thought I would see this accomplished. Many thanks and keep up the good work. This is fully usable with Nova beta 7.0.27.

Works perfectly on my T900, many thanks! Keep up the good work!

stanl56 said:
@TechDriver ,Great work on this build! Never This is fully usable with Nova beta 7.0.27.
Click to expand...
Click to collapse
Can you provide a link for this latest Nova beta? APK mirror seems booked.
Nova 7.0.27 Works smoother and scrolling and moving icons is better. PIN screen on first login is same problem and will not work on the first try. Mouse clicks and mouse related screen painting remains an issue. If you don't use a mouse you may not notice any problems other than first login. Come to think about it, 7.1 had issues with the mouse most noticeable when I used Collabora and I had attributed it to the app.

Database Info

welcome