pulling my hair out - Galaxy S II Q&A, Help & Troubleshooting

Hi all,ive 3x galaxy s2 gt-i9100 phones,i need android 7.XX+ on them to run a nanovna app on them,ive flashed 2 of them with lineage 15.1 using stock gapps and a 1.5gb pit file,they sort of work ok but the 3rd one just goes into a bootloop,all the phones are identicle,the problem phone works with other roms fine so it looks like its ok,but just bootloops with lineage 14.xx or 15.1 os,any ideas how to fix this?,cheers in advance m3vuv,p.s i hope this is the right section to ask.m3vuv.

m3vuv said:
Hi all,ive 3x galaxy s2 gt-i9100 phones,i need android 7.XX+ on them to run a nanovna app on them,ive flashed 2 of them with lineage 15.1 using stock gapps and a 1.5gb pit file,they sort of work ok but the 3rd one just goes into a bootloop,all the phones are identicle,the problem phone works with other roms fine so it looks like its ok,but just bootloops with lineage 14.xx or 15.1 os,any ideas how to fix this?,cheers in advance m3vuv,p.s i hope this is the right section to ask.m3vuv.
Click to expand...
Click to collapse
If you have followed the same procedure with all 3 devices, I would say it is a hardware issue. Try formatting /data in TWRP and flashing again.

i gave up on this,i installed lineage 14.2 instead,seems to work fine apart from the two buttons remain illuminated on the bottom left and right on the phone( it does the same on all 3 s2 phones i have) is there a fix for this as it eats my batterys .?

m3vuv said:
i gave up on this,i installed lineage 14.2 instead,seems to work fine apart from the two buttons remain illuminated on the bottom left and right on the phone( it does the same on all 3 s2 phones i have) is there a fix for this as it eats my batterys .?
Click to expand...
Click to collapse
I never had this problem on LOS 14.1 (I'm assuming this is what you mean, not 14.2). IIRC, the kernel had a limited BLN implementation, where the buttons would light up for notifications, but they shouldn't be lit up all the time.
Was this on a clean install? Can you see if there is an option in settings for button illumination?

buttons always on
the install was a clean install,the lineage version is 14.1-20190308,i cant find any settings for button ilumination,help!!

m3vuv said:
the install was a clean install,the lineage version is 14.1-20190308,i cant find any settings for button ilumination,help!!
Click to expand...
Click to collapse
I don't recall any such issue from Lineage 14.1. You could try a more recent version from the last few pages of the official thread, (unofficial versions with updated security patches). Or try one of the derivative roms based on Lineage 14.1 if you like android nougat.
Just make sure you follow the instructions from the OP if you are not 100% confident of the process. Make sure you use a compatible recovery, and search the relevant thread for issues/trouble shooting.
Oh, and if you want to make sure the person you are replying to sees that you have posted, either mention them (such as @noppy22 ) or quote the post so there is a notification

Related

Moto G4/G4 Plus [Official Cyanogenmod 14.1] Nougat Discussion

Official Cyanogenmod 14.1 Motorola athene Released for Moto G4/G4 Plus.Find the below link for Download.
https://download.cyanogenmod.org/?device=athene
stkpxl said:
Yay! Guessing you need the latest soak test modem and bootloader to install though?
Click to expand...
Click to collapse
That's a negative. My understanding is the soak test is needed in the plus because of finger print scanner issues. I have the XT1625 and it runs great without the soak test. Flash the quark kernel too. Waaaaaay better benchmark results.
stkpxl said:
I just installed it. Definitely didn't need the soak test. VoLTE works too when I called my voicemail to check. No crash on the Gallery app either like I've seen reported. And the best part for me is that Republic Wireless works with it and the app works too! Usually they don't support custom ROMs but this time everything works.
Click to expand...
Click to collapse
Glad to hear you're all set up. Try quark kernel when you get a chance. Makes sure you get 2.0,because the other ones caused a boot loop for me.
I've just rooted my phone, I'm in 6.0.1, I just need to download and put this in SdCard, later Install w/o gapps and it will works?
I flashed the ROM and wiped and then flashed gapps, gallery is crashing for me.
mikemelbrooks said:
I flashed the ROM and wiped and then flashed gapps, gallery is crashing for me.
Click to expand...
Click to collapse
Same here, issues with gallery, I couldnt install Gapps, I got error code 20.
Mexickano said:
Same here, issues with gallery, I couldnt install Gapps, I got error code 20.
Click to expand...
Click to collapse
Were you trying to install the arm64 gapps? I could only install the arm gapps.
I updated to the last nightly build which seems to have fixed the gallery bug for me, but now the camera can't access the sdcard to save pictures or videos when the card is set as internal.
Running 12222016 as of this morning. Have been using it since it first hit the streets. Seems a little unstable. While it's running, it runs great. However, for no apparent reason it reboots my device. I can't seem to pinpoint the cause as it happens sporadically and randomly.
I noted that the blue light filter "sort of" works. It has to be manually activated. Tried the automatic route but it's hit or miss.
hooks024 said:
Glad to hear you're all set up. Try quark kernel when you get a chance. Makes sure you get 2.0,because the other ones caused a boot loop for me.
Click to expand...
Click to collapse
That would be because the "other ones" are for MM based ROM's and 2.0/2.2 are for Nougat.
mikemelbrooks said:
I updated to the last nightly build which seems to have fixed the gallery bug for me, but now the camera can't access the sdcard to save pictures or videos when the card is set as internal.
Click to expand...
Click to collapse
Fixed the camera by clearing the camera data and cache!
chrisjwild said:
Were you trying to install the arm64 gapps? I could only install the arm gapps.
Click to expand...
Click to collapse
Im a dumb, I was installing other gapps, now Im not getting any issue, only about video recording but I'll fix it flashing a boot.img.
Thanks to all.
I always install ROM boot it then go to browser and search Gapps it automatically finds the one I need then just download and reboot to recovery and install so I don't have any issues the Roms are all comparable for bothering devices but I think arm is different between devices if that helps anybody
:crying: Sad News Guys Cyanogen is shutting down all its services from 31st Dec 2016.
But
http://lineageos.org/
Hi,
I bought a Moto G4 for Christmas. I'll receive it tomorrow, and so I'm looking for a good custom rom. I had the Moto G 2014 LTE (thea) running CM14.1. I notice that the last CM build available for athene is the 20161225, and I'd like to know if it's stable. Does it have an option to make volume buttons control media volume instead of ringtone, for instance ?
Thank you, 'n have a nice day !
Yo is cm 14.1 gonna get xposed
I installed the CM 14.1 12/25 nightly on a XT1625 motoG4 non-plus. Upon reboot, the OS asked me to input my password. It was unable to decrypt my data.
I had a pattern PIN, so I looked up the proper numeric sequence and entered it, and the OS told me "my password was correct but the data was corrupt" and suggested I wipe my phone.
I tried this several times with different passwords, and even with completely incorrect passwords it said it was correct but the data corrupt. So I had to wipe my data. After wiping data, nougat 7.1 came up fine.
Note I have a SDcard set as adaptable storage. My guess (and it is only a guess) is this is what screwed me over.
Has anyone been using this for a while? I know it's nightly, but just curious if it's mostly usable. Would like to get off MM and tired of waiting for Official Nougat
slatteew said:
Has anyone been using this for a while? I know it's nightly, but just curious if it's mostly usable. Would like to get off MM and tired of waiting for Official Nougat
Click to expand...
Click to collapse
You can use the latest official version of CyanogenMod. So far I had neither bugs nor crashes. The last version is cm-14.1-20161225-NIGHTLY-athene.zip
Otherwise, you can also use the official soak test from Motorola. This is also based on Anroid 7.0
yakzockt said:
You can use the latest official version of CyanogenMod. So far I had neither bugs nor crashes. The last version is cm-14.1-20161225-NIGHTLY-athene.zip
Otherwise, you can also use the official soak test from Motorola. This is also based on Anroid 7.0
Click to expand...
Click to collapse
Thanks! I found the latest Nightly and also an updated LineageOS (replacement for Cyanogen since they've stopped) version, might try them both out. I was perusing the Soak Test and saw it doesn't work with XT1625 devices unfortunately. I have the XT1625 non-Amazon version with Republic Wireless. Saw someone posted earlier in this thread that Republic Wireless was working fine on CM 14.1 Nightly, so that gave me some incentive as well.

Touch screen doesn't work after custom rom install.

I have tried installing Aosp Oreo AND pure nexus on my redmi note 3 kenzo , install seems fine but when the roms open, the touch screen is not responsive! The phone isn't frozen because the volume up and power buttons work fine (Volume goes down or up) but the touch screen and the bottom buttons don't work. Any help would be really appreciated!
Edit: I previously had the latest china rom 7.9.7 when installing
I have this same exact problem on 3 different roms I've tried. Any solutions?
A little more imformation would help. Like do you flash your roms using twrp or something else. Like where have you gotten your rom and is the rom made for your own model. Like have you tried other nougat roms like rr or lineage or omnirom etc. Are they working fine? Is you bootloader locked or not and stuff like that.
I purchased a replacement screen from AliExpress. Display works but the touch screen is not. What's interesting is another guy mentioned the same issue on the PureNexus thread. He's claiming that it works on other ROMs but not on that particular AOSP one. Cant confirm this yet cause PureNexus have been my daily driver for quite a long time now, I've only tested the replacement screen with PN and MIUI Multirom. I'll test other ROMs, but if it still wont work, I guess I'll be stuck with my original broken screen.
I have the same problem with an old Redmi note 3 after replacing screen. On MIUI dev screen works fine, but no other Roms. Seen somewhere that auto brightness might be responsible. As a matter of fact, MIUI dev gets installed with auto brightness on and most custom Roms not. I turned off auto brightness after reading that and on Chrome, which I was using for browsing at that moment, the screen became unresponsive. Other apps worked fine. seems like auto brightness is somehow involved. On search of a custom ROM that comes with auto brightness on by default to test my hypothesis now.
Edit: if anyone knows of a custom ROM coming with auto brightness on by default, I'll greatly appreciate the info.
This is simple fix! Clean Flash the ROM should fix your problem!
sreekantshenoy said:
This is simple fix! Clean Flash the ROM should fix your problem!
Click to expand...
Click to collapse
Nope, if touchscreen is not original it is not a simple fix at all, I clean flashed several ROMs, some will work and some won't, must be a driver problem. NOS works.
The same question, who can tell me on what rom can work?
https://forum.xda-developers.com/redmi-note-3/help/please-help-touch-screen-driver-problem-t3554610
I have a replacement screen on my phone. I have tried clean flashing and can testify that Nitrogen OS Oreo Rom works, Lineage OS 14.1 doesn't work, and neither does AOSP Oreo ROM
drt1 said:
I have the same problem with an old Redmi note 3 after replacing screen. On MIUI dev screen works fine, but no other Roms. Seen somewhere that auto brightness might be responsible. As a matter of fact, MIUI dev gets installed with auto brightness on and most custom Roms not. I turned off auto brightness after reading that and on Chrome, which I was using for browsing at that moment, the screen became unresponsive. Other apps worked fine. seems like auto brightness is somehow involved. On search of a custom ROM that comes with auto brightness on by default to test my hypothesis now.
Edit: if anyone knows of a custom ROM coming with auto brightness on by default, I'll greatly appreciate the info.
Click to expand...
Click to collapse
found any fix???, thanks
Magnatiz90 said:
found any fix???, thanks
Click to expand...
Click to collapse
Not a problem anymore. Almost all oreo ROMs I tried until now work fine. Radon kernel will fix the issue on every nougat rom too.
drt1 said:
Not a problem anymore. Almost all oreo ROMs I tried until now work fine. Radon kernel will fix the issue on every nougat rom too.
Click to expand...
Click to collapse
I'm about to replace my screen and have NOS(8.1) installed, will it work out of the box or should I flash agni or something?
Thanks
idiotoretardado said:
I'm about to replace my screen and have NOS(8.1) installed, will it work out of the box or should I flash agni or something?
Thanks
Click to expand...
Click to collapse
Never tried NOS to be honest. I tested Omni, LOS from LokManSiu, and Elixir, all work fine out of the box. Radon should make every ROM work with third party screens, Agni works too as far as I remember, I did test it once. One more thing though, redwolf recovery won't work, you'll have to stick to twrp.
Edit: resurrection remix works out of the box too.
drt1 said:
Never tried NOS to be honest. I tested Omni, LOS from LokManSiu, and Elixir, all work fine out of the box. Radon should make every ROM work with third party screens, Agni works too as far as I remember, I did test it once. One more thing though, redwolf recovery won't work, you'll have to stick to twrp.
Edit: resurrection remix works out of the box too.
Click to expand...
Click to collapse
Thanks for the warning man, I have redwolf installed, I'm gonna switch to stock twrp, you prolly saved my a$$
idiotoretardado said:
Thanks for the warning man, I have redwolf installed, I'm gonna switch to stock twrp, you prolly saved my a$$
Click to expand...
Click to collapse
I learned the hard way . Always used twrp, decided to try redwolf few days ago, with the latest update. Stuck now until I find time to flash through fastboot. Good thing I'm using Omni, which updates through open recovery script.
kernal
when i flash kernal radeon it work on my touch screen ? i triedly to flash custom rom but it not work . i hope this way can me flash rom . thx
I have the same problem, some roms doesn't work but with RR o NOS works without problem. When the touch panel doesn't work with some roms, is only problem from the sreen, because I can use OTG with a mouse to use my phone. I changed the panel too. Sorry for my poor english level

Touch screen is not working on custom ROMs and Kernels

I see more and more people had problem like this, touch screen on new phones is not working at all in custom ROMs and also in OrangeFox. Nobody changed display nor play with phone internals.
DarthJabba9 said:
Do I have an ebbg display? You will already know if you do, because your touchscreen will not work on most custom ROMs, and will not have worked on any earlier version of OrangeFox. So, if you have been using any earlier release of OrangeFox, then you clearly do not have an ebbg display. You can check by installing the "Device HW Info" app from the Play Store. When you run it, check the "LCM" on the start page. If you see "ebbg" appearing anywhere in that, then you do have an ebbg display.
Click to expand...
Click to collapse
Phones manufactured 05/2018 and later can face this issue.
Manufactured date is located at sticker at the back of the phone box.
Despcription:
Seems that kernel is responsible to make touch to work. Its not easy to make ebbg display touch work in custom GPL kernels, only ROM which use prebuilt kernel that comes with the device tree is working right now.
Big thanks to DarthJabba9 who is fix that in OrangeFox recovery. https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
What is working:
Recovery:
- OrangeFox R7
- TWRP official
- RedWolf Unofficial
ROMs:
- Xiaomi roms global stable ROM 7.1, global dev beta 8.1,
- Dirty unicorns 7.1 posted here: https://forum.xda-developers.com/red...-plus-t3812630
- AOSP Extended 5.7
What is not working:
- OrangeFox 5.1, r6
- KERNEL: Dark ages Segundo, LH kernel
- Pixel experience https://forum.xda-developers.com/redmi-note-5/development/rom-pixel-experience-t3797696
- Liquid remix https://forum.xda-developers.com/redmi-note-5/development/rom-liquid-remix-t3809286
- AOSP Extended 5.6
---account closed
It's not a "feature". Xiaomi probably used a different screen for later batches of Vince. What month was your phone manufactured?
what works:
moved to main post
sigma392 said:
It's not a "feature". Xiaomi probably used a different screen for later batches of Vince. What month was your phone manufactured?
Click to expand...
Click to collapse
where I can find this, in CIT?
I found this App called Device info HW on the Appstore. When i open it on my redmi 5 plus it says: Touchscreen -> synaptics_dsx_i2c
But I'm not sure if thats what youre looking for ...
Btw my phone has the same problem too
Mine has same info in aida64 and device info hw and touch works in every rom, kernel and recovery.
jes0411 said:
Mine has same info in aida64 and device info hw and touch works in every rom, kernel and recovery.
Click to expand...
Click to collapse
can you please share what rom,kernel and recovery you using right now?
mik.y said:
can you please share what rom,kernel and recovery you using right now?
Click to expand...
Click to collapse
Recovery: orangefox r6
Rom: omnirom official
Kernel: default from the rom
I used previously resurrection remix and then havoc and used all kernel (DA, LH and Universe)
Also used TWRP and Red Wolf.
Edit:
Sorry, I missed that ebbg thing in aida64 screenshot.
I have all the same except ebbg.
I am having same issue. Touchscreen sometimes hang during regular use. Its annoying. DotOs
mubeenshahid said:
I am having same issue. Touchscreen sometimes hang during regular use. Its annoying. DotOs
Click to expand...
Click to collapse
sorry,you dont. we are talking about not working touch screen all the time,not just sometimes.
jes0411 said:
Recovery: orangefox r6
Rom: omnirom official
Kernel: default from the rom
I used previously resurrection remix and then havoc and used all kernel (DA, LH and Universe)
Also used TWRP and Red Wolf.
Edit:
Sorry, I missed that ebbg thing in aida64 screenshot.
I have all the same except ebbg.
Click to expand...
Click to collapse
can you please post your aida screenshot? thanks
mik.y said:
can you please post your aida screenshot? thanks
Click to expand...
Click to collapse
Here it is.
mik.y said:
where I can find this, in CIT?
Click to expand...
Click to collapse
It's located at sticker at the back of the phone and at the Box. Interesting to note that we share the same sensor yet your touch doesn't work. Mine was Manufactured last 12/2017
mubeenshahid said:
I am having same issue. Touchscreen sometimes hang during regular use. Its annoying. DotOs
Click to expand...
Click to collapse
For this, flash the baseband at the main post. If it fails, your FP sensor may be dirty. I had instances where a dirty FP causes some intermittent touch issues.
I just saw, and mine was manufactured on 06/2018
But anyways i got some progress ....
I tried installing various custom roms this afternoon, after some flashing i got one to work. It's the AOSP Extended mod for Vince. I think it worked cause the rom has a miui (Oreo 8.1) based bootloader, kernel or both ... I'm not sure what it is. The rom looks good (It's similar to the Pixel Experience). I had some bootloop problems at the beginning, but after i updated the bootloader it works fine.
Qu4k3_92 said:
I just saw, and mine was manufactured on 06/2018
But anyways i got some progress ....
I tried installing various custom roms this afternoon, after some flashing i got one to work. It's the AOSP Extended mod for Vince. I think it worked cause the rom has a miui (Oreo 8.1) based bootloader, kernel or both ... I'm not sure what it is. The rom looks good (It's similar to the Pixel Experience). I had some bootloop problems at the beginning, but after i updated the bootloader it works fine.
Click to expand...
Click to collapse
there are 4 versions, which one?
mik.y said:
there are 4 versions, which one?
Click to expand...
Click to collapse
This one, the v5.7: https://www.google.com/amp/s/forum....pment/rom-aospextended-rom-v4-6-t3752135/amp/
mik.y said:
I see more and more people had problem like this, touch screen on new phones is not working at all in custom ROMs and also in OrangeFox. Nobody changed display nor play with phone insides. Maybe some new "feature" introduced by Xaiomi? I would like to somebody help me investigate this.
Plase notice that this display is "ebbg".
what is working:
Recovery:
- TWRP official 3.2.2.0
- RedWolf Unofficial
ROMs:
Xiaomi roms global stable ROM 7.1, global dev beta 8.1,
Dirty unicorns 7.1 posted here: https://forum.xda-developers.com/red...-plus-t3812630
what is not working:
- TWRP official 3.2.2.0 + OrangeFox 5.1, r6
- Pixel experience https://forum.xda-developers.com/redmi-note-5/development/rom-pixel-experience-t3797696
Click to expand...
Click to collapse
I see the driver is not loaded in kernel
Will be fixed on next release
blacksuan19 said:
I see the driver is not loaded in kernel
Will be fixed on next release
Click to expand...
Click to collapse
in what kernell/rom?
blacksuan19 said:
I see the driver is not loaded in kernel
Will be fixed on next release
Click to expand...
Click to collapse
I saw there is a new release.... Did they fix it?
(I would try it by myself but i dont have enough connection a the moment)

[ROM][UNOFFICIAL][AOSP][8.1] Pixel Experience 8.1 [NOTE9][Exynos][30.09.2018]

HTML:
Pixel Experience ROM for the Galaxy Note 9​
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 8.1
Click to expand...
Click to collapse
What's working?
Everything seems to be working as on the official s9 los15 build; with minor exceptions (screen recording can sometimes be a lil buggy, nfc can be a lil hicky etc)
What's not working?
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS Pixel Experience. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS PixelExperience.
Click to expand...
Click to collapse
Disclaimer: This rom is not built by me. That has been done by @malinathani with some help from myself. After that he insisted that I make this thread :highfive:
Instructions:
Make sure TWRP has been installed and functional.
Download the latest build linked below
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs). Even better if you have nothing to loose and wipe system,data,cache,storage etc
Flash the latest build (and gapps). DONT flash gapps. they are already included in the rom.
Reboot and enjoy :victory:
Downloads:
Galaxy Note9 (N960F): MEGA Onedrive
Providing feedback:
You are more than welcome to provide any kind of feedback here.
(limited only to feature requests; it's called "pixel experience" for a reason and it should stay that way)
You can also msg me anytime on telegram @ Rainbow_Alex_Dash
OR YOU CAN JOIN OUR TELEGRAM GROUP!
https://t.me/joinchat/E_rQyU__5M_5wph6FrnpKA
Changelog:
30.09.2018: Initial release
Troubleshooting/FAQ:
Q: Whaaaaaa??? You are developing for the note9 now?
A: Nah, not really. This isn't even built by me. I just helped the guy who did it so much he insisted I create the thread. I'm not promising any future development on my end but hey
Q: The rom isn't booting/camera doesn't work
A: Flash/make sure you have the ARH5 vendor and try again.
Q: The rom is in a bootloop/google apps keep crashing
A: You did read the instructions and NOT flash any gapps riighhttt?? smh, wipe /system,/data and /cache and start over
Q: I have another bug; How can i tell it to you while slightly increasing my changes of it ever getting fixed.
A: You can tell me what's going on either here or on telegram WITH A LOGCAT attached(required);if rom isn't booting at all attach /proc/last_kmsg.
Q: I don't know what/how to logcat. Is it really necessary?
A: Logcat or gtfo
Q: How can i support you?
A: Awwww thanks; On most of my posts on the left side there's a "donate to me" paypal button; You can use that,donations are more than welcome, or if you don't have any $ to spare you can also post here about how awesome i am (this surprisingly helps very much)
XDA:DevDB Information
Pixel Experience 8.1, ROM for the Samsung Galaxy Note 9
Contributors
Rainbow_Dash, malinathani, jesec,Vaughnn,farovitus
Source Code: https://github.com/malinathani
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 30.09.2018
Stable Release Date: 2018-09-30
Created 2018-09-30
Last Updated 2018-10-03
reserved
It seems that no one wants to brush the machine.
But still thank you very much
Does the pen work ?
giorgior.r said:
Does the pen work ?
Click to expand...
Click to collapse
Does work as a stylus, you can check it out and let us know!
Thanks for this. Was waiting for an AOSP Based ROM before rooting. Will root and flash later and report back .
Test it out and let us know what you guys think! Feedback is appreciated
Good day,
1. Is there a link/attachment for an official ARH5/ARH6 vendor image that we can use with this ROM?
2. I wiped /system,/data and /cache flashed the ROM with and without an ARH6 image (https://androidfilehost.com/?fid=1322778262904015418) within TWRP and got bootloop.
What am I missing?
Swarai said:
Good day,
1. Is there a link/attachment for an official ARH5/ARH6 vendor image that we can use with this ROM?
2. I wiped /system,/data and /cache flashed the ROM with and without an ARH6 image (https://androidfilehost.com/?fid=1322778262904015418) within TWRP and got bootloop.
What am I missing?
Click to expand...
Click to collapse
Ummm, you can try flashing vendor from the Light Rom thread or try flashing noverity.zip after flashing the ROM.
There are a bunch of them. In treble forums
Surprised no one bothered to upload them here
All pie gsi roms work with note 9
TheUndertaker21 said:
There are a bunch of them. In treble forums
Surprised no one bothered to upload them here
All pie gsi roms work with note 9
Click to expand...
Click to collapse
I totally agree, but give this a shot once, it's noticeably smooth compared to the gsis out there (I've used many myself) it also has dual speakers working. As for pie gsis they have this animation lag while switching and opening apps. Give it a shot and I hope you'll like it.
malinathani said:
I totally agree, but give this a shot once, it's noticeably smooth compared to the gsis out there (I've used many myself) it also has dual speakers working. As for pie gsis they have this animation lag while switching and opening apps. Give it a shot and I hope you'll like it.
Click to expand...
Click to collapse
Thank you. Great to have specific support just for Note9!
I've tried other GSIs from Treble forums and yes on those roms only mono audio output works and also had brightness issues last time I tried it. I will try this out
---------- Post added 1st October 2018 at 12:31 AM ---------- Previous post was 30th September 2018 at 11:49 PM ----------
I flashed it and I gotta say, this is very good. I'll keep this as my daily driver if I don't run into any issues which I haven't so far
I really like that there's bixby button custom options included. Rom is super smooth. Definitely smoother than other GSIs on the treble forums. Dual speakers are working but volume seems lower than stock (can anyone confirm this?)
Regarding the vendor, I am using ARH6 vendor. Like I said, so far I haven't gotten any issues.
I think you should include in OP that root isn't included. I flashed Magisk zip and it works fine though
Nasty_z said:
Thank you. Great to have specific support just for Note9!
I've tried other GSIs from Treble forums and yes on those roms only mono audio output works and also had brightness issues last time I tried it. I will try this out
---------- Post added 1st October 2018 at 12:31 AM ---------- Previous post was 30th September 2018 at 11:49 PM ----------
I flashed it and I gotta say, this is very good. I'll keep this as my daily driver if I don't run into any issues which I haven't so far
I really like that there's bixby button custom options included. Rom is super smooth. Definitely smoother than other GSIs on the treble forums. Dual speakers are working but volume seems lower than stock (can anyone confirm this?)
Regarding the vendor, I am using ARH6 vendor. Like I said, so far I haven't gotten any issues.
I think you should include in OP that root isn't included. I flashed Magisk zip and it works fine though
Click to expand...
Click to collapse
How well does it handle memory? I heard AOSP roms on GS9 doesn't keep apps in memory as well as stock.
Also for the low volume thing. Have you tried Dolby Atmos? It has always helped me in the past with my phones.
Okay so.. I'm having a weird issue. The rom was working perfectly fine and then it started to register every single tap as a long press. Every time I touch the screen, it registers a long press. If this issue can be fixed, everything else was working great. At first, I thought it was because I installed magisk modules but I just uninstalled magisk completely and the issue is still there. Logcat is attached.
@Fiso I'll try Dolby Atmos and keep an eye on memory as soon as the touchscreen issue goes away.
Logcat: https://mega.nz/#!90YFDArb!Yz_d5eHQPXfjZ2NIp6OLCTgzUBJ04bcwPbyAxZ3V3jE
Nasty_z said:
Okay so.. I'm having a weird issue. The rom was working perfectly fine and then it started to register every single tap as a long press. Every time I touch the screen, it registers a long press. If this issue can be fixed, everything else was working great. At first, I thought it was because I installed magisk modules but I just uninstalled magisk completely and the issue is still there. Logcat is attached.
@Fiso I'll try Dolby Atmos and keep an eye on memory as soon as the touchscreen issue goes away.
Logcat: https://mega.nz/#!90YFDArb!Yz_d5eHQPXfjZ2NIp6OLCTgzUBJ04bcwPbyAxZ3V3jE
Click to expand...
Click to collapse
Hmmmm, that's weird, which module did you install btw? If you still have this issue you can try dirty flashing the ROM or clean installing it again. I tested the ROM myself for almost a week before releasing it. Also which model are you using?
malinathani said:
Hmmmm, that's weird, which module did you install btw? If you still have this issue you can try dirty flashing the ROM or clean installing it again. I tested the ROM myself for almost a week before releasing it. Also which model are you using?
Click to expand...
Click to collapse
The module was xposed installer for the latest SDK. Model is N960F. Dirty flashing did not help. So I did a clean flash and it's fine for now. I'll flash magisk and install modules other than xposed and try
Nasty_z said:
The module was xposed installer for the latest SDK. Model is N960F. Dirty flashing did not help. So I did a clean flash and it's fine for now. I'll flash magisk and install modules other than xposed and try
Click to expand...
Click to collapse
I currently have xposed installed myself, I installed xposed framework module which automatically installs it for the correct SDK version.
Nice rom, but there is no mirrorlink :crying:
malinathani said:
I currently have xposed installed myself, I installed xposed framework module which automatically installs it for the correct SDK version.
Click to expand...
Click to collapse
Yeah it isn't the module. I've done some more tests. The issue only happens if I install or restore multiple applications. Not sure why. Can you tell me what vendor you use?
Also, the keyboard seems sluggish. I don't mean the UI, like the touch responsivenes? If you type really fast, keyboard can't keep up (compared to stock)? Can you confirm this?
Nasty_z said:
Yeah it isn't the module. I've done some more tests. The issue only happens if I install or restore multiple applications. Not sure why. Can you tell me what vendor you use?
Also, the keyboard seems sluggish. I don't mean the UI, like the touch responsivenes? If you type really fast, keyboard can't keep up (compared to stock)? Can you confirm this?
Click to expand...
Click to collapse
I would recommend you to reinstall apps only from playstore and not restore them because that is known to break stuff. I have no lag issues even on keyboard which you are saying. if you still have issues you can try with ARH5 vendor.

[Treble] [Pie] [UNOFFICIAL] LineageOS 16 For Xperia X

Lineage OS 16 For Xperia X [Treble]​Based on Sony Open Devices​I am not responsible for bricked devices, dead SD cards,.​Suitable for F5121 and F5122​Reboot after your first boot please!​
Opinional files:
Disable ForceEncrypt:Link
Required files:
[Tested]
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v6_loire.zip
[OEM-Files]
Download Link
How to flash
Read README.txt in zip file please.
Optional step If you want to use a GSI
Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Because of Anti-Rollback, If you want to Use GSI, You need to choose the same or newer one as the treble build date.
Update and known BUG:
V20190323:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll Script
Contributors
Sjll @infixremix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-03-31
Last Updated 2019-03-31
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
LOLisLIFE said:
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Click to expand...
Click to collapse
lookmanns14 said:
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
Click to expand...
Click to collapse
I will try to build a optimize kernel in free time.
Hi,
Can you please help me with the download from the GSI? Where can I get the right file from?
after install, bluetooth and settings tell me that it stops all the time and sim cant be detected. Also there is some encryption so i can't access data or system anymore with twrp... even magisk can't be installed. great...
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
iH8Ecchi said:
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
Click to expand...
Click to collapse
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Some random said:
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Click to expand...
Click to collapse
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
iH8Ecchi said:
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
Click to expand...
Click to collapse
Hmmmmm
Well like that it worked with all pie ROMs that I used
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Fardin Rehman said:
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Click to expand...
Click to collapse
Use Twrp-Q (Ask Simeone for Link)
Some random said:
Use Twrp-Q (Ask Simeone for Link)
Click to expand...
Click to collapse
Yeah I have TWRP-Q just need to flash recovery and then try again. Thank you very much for helping
Can anyone please tell me which Gcam can i use on this ROM?
New version of LOS 16 + Treble
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
iH8Ecchi said:
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
Click to expand...
Click to collapse
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Fardin Rehman said:
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Click to expand...
Click to collapse
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
iH8Ecchi said:
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
Click to expand...
Click to collapse
Yeah I am using the gcam port and I get pretty good pictures with it but not very good video quality so I guess I'm gonna give it a try to Chippa_a's Unofficial LOS16.

Categories

Resources