[ROM][GT-I9195I][UNOFFICIAL][9.0] LineageOS 16

[Simon1511]

Hey, does it works for the I9195 ? When not where can I find this version for I9195 ?

No, this version is only for I9195I.

Just search for Lineage 16 for I9195 in the S4 Mini forum
In dont know if theres a Lineage 16 ROM for I9195I, but if there is one you will find it

 

[MrGoodtunes]

No, this version is only for I9195I.

Just search for Lineage 16 for I9195 in the S4 Mini forum
In dont know if theres a Lineage 16 ROM for I9195I, but if there is one you will find it

There is an excellent LOS-16 for i9195 (without "i" at end) by well-respected dev, here:

https://forum.xda-developers.com/galaxy-s4-mini/orig-development/rom-lineageos-16-0-s4-mini-t3833063

 

[cristihan]

@christihan, I have this issue as well and want to try your fix adjusting the mixer_paths.xml. However, your updater-script targets the file in /system/etc whereas mine is located in /system/vendor/etc (I'm running Danil's LOS16 w. pico gapps). Do I need to update your updater-script and file location structure accordingly before flashing? Thx

Sorry for the delayed response ... yes, you need to change the zip archive structure in accordance with the new path: system / vendor / etc or you can try this one from here: https://androidfilehost.com/?fid=1395089523397965903

 

[cristihan]

TWRP-3.3.0 for our i9195i device has been made available by @mernurisha in first post of his Pixel Experience thread. Has anybody tried it here?

https://forum.xda-developers.com/galaxy-s4-mini/development/rom-pixel-experience-t3870945

Yes, I installed it and it works very well.

 

[DroidHero2002]

Current builds of twrp and los 16 work great with my I9195I, keep up the great work Danil. If anyone else here ever mains an S7 exynos like I do now, there's a fantastic LOS 16 build by a well respected dev over there too.

 

[thessy]

Installation

1. Make a backup!
2. Install recovery here
3. Reboot into recovery
4. Wipe data (You may get a "staus 7" error if you fail to wipe.)
   [*]Install the Current ROM
   [*]Optionally install Gapps
   [*]Boot phone into normal mode
   

Hi,

after bricking up a little bit my i9195i with LOS 14.1 (?) on updating, I reflashed stock rom from samsung. Now I want to start with LOS 16.

The link in the "installation list" (second item "2. install recovery here") is wrong, I think.

So where to find the latest twrp recovery?

I know https://github.com/Galaxy-MSM8916 but I'm too stupid to find under 'releases' other things but 'rr-oreo'

Regards
thessy

 

[MrGoodtunes]

... where to find the latest twrp recovery?

Look just 2 posts before yours (#184) and you will see a link to latest recovery (TWRP-3.3.0) for i9195i. There's even a screenshot, thanks to @christihan

 

[cristihan]

Hi,

after bricking up a little bit my i9195i with LOS 14.1 (?) on updating, I reflashed stock rom from samsung. Now I want to start with LOS 16.

The link in the "installation list" (second item "2. install recovery here") is wrong, I think.

So where to find the latest twrp recovery?

I know https://github.com/Galaxy-MSM8916 but I'm too stupid to find under 'releases' other things but 'rr-oreo'

Regards
thessy

TWRP 3.3.0 for i9195i device:

https://androidfilehost.com/?w=files&flid=295274

 

[thessy]

Thanks @cristihan and @MrGoodtunes.

Got my i9195i flashed with TWRP and with LOS16.

But only with "lineage-16.0-j33-20190301-NIGHTLY-serranovelte".

With "lineage-16.0-j35-20190502-NIGHTLY-serranovelte" device can not boot. After 2 seconds of LOS-logo-animation the device reboots and this in a loop.

Is this known? Where to report bugs/issues?

 

[cristihan]

Thanks @cristihan and @MrGoodtunes.

Got my i9195i flashed with TWRP and with LOS16.

But only with "lineage-16.0-j33-20190301-NIGHTLY-serranovelte".

With "lineage-16.0-j35-20190502-NIGHTLY-serranovelte" device can not boot. After 2 seconds of LOS-logo-animation the device reboots and this in a loop.

Is this known? Where to report bugs/issues?

Yes...j35 is with problems. It was reported here.

 

[thessy]

Ok, follow now every post in this thread

 

[OllyFunkster]

Does anyone have Ambient Display working on this ROM? I'm using the J33 build, AlwaysOnAMOLED from f-droid doesn't work with android 8+ and I'm looking for a way to have notifications and clock always-on / on when proximity sensor is not covered, so I enabled Ambient Display but it doesn't work - there's a brief glimpse of a clock when the power button is pressed to display the unlock screen (I have it go directly to pattern unlock if that makes any difference) but that's the only difference between ambient enabled/disabled.

Any hints would be gratefully received!

 

[chrischa]

Does anyone have Ambient Display working on this ROM? I'm using the J33 build, AlwaysOnAMOLED from f-droid doesn't work with android 8+ and I'm looking for a way to have notifications and clock always-on / on when proximity sensor is not covered, so I enabled Ambient Display but it doesn't work - there's a brief glimpse of a clock when the power button is pressed to display the unlock screen (I have it go directly to pattern unlock if that makes any difference) but that's the only difference between ambient enabled/disabled.

Any hints would be gratefully received!

Can you please check if your proximity sensor is working? For me neither AmbientDisplay nor InCallScreen is working properly. I think both is caused by the proximity sensor.

If I try to disable the sensor:
serranovelte:/sys/class/input/input6 # echo 0 > enable
dmesg tells me it is already disabled.
[ 210.523779] gp2a_prox_enable_store 852 value = 0
[ 210.523873] gp2a_prox_enable_store already disabled

If I try to enable it:
serranovelte:/sys/class/input/input6 # echo 1 > enable
my device instandly reboots
[ 478.320549] gp2a_prox_enable_store 852 value = 1
[ 478.320645] gp2a_prox_onoff : proximity turn on/off = 1



Best regards

 

[OllyFunkster]

Can you please check if your proximity sensor is working?

Yes, it appears to be working fine. cat /sys/class/input/input6/enabled gives 1, and covering it causes Telegram to blank the screen. There's a bit of a display brightness glitch when it comes back on (100% brightness for a few milliseconds), but that's not a huge problem.

I checked to see if the proximity sensor is being powered up when the screen is locked (by pointing a camera at it that can see the IR) and it is.

Thanks!

 

[cristihan]

Yes, it appears to be working fine. cat /sys/class/input/input6/enabled gives 1, and covering it causes Telegram to blank the screen. There's a bit of a display brightness glitch when it comes back on (100% brightness for a few milliseconds), but that's not a huge problem.

I checked to see if the proximity sensor is being powered up when the screen is locked (by pointing a camera at it that can see the IR) and it is.

Thanks!

Install AIDA64 an check SENSORS section.

 

[OllyFunkster]

Install AIDA64 an check SENSORS section.

Is there a trustworthy APK source of this? I am google-play-less.

 

[cristihan]

Is there a trustworthy APK source of this? I am google-play-less.

Try apkpuredotcom

 

[chrischa]

Yes, it appears to be working fine. cat /sys/class/input/input6/enabled gives 1, and covering it causes Telegram to blank the screen. There's a bit of a display brightness glitch when it comes back on (100% brightness for a few milliseconds), but that's not a huge problem.

I checked to see if the proximity sensor is being powered up when the screen is locked (by pointing a camera at it that can see the IR) and it is.

Thanks!

can you try the same with the enable (without d) file. If I understand this correctly, this file only represents the state.

EDIT: Your were right. I tested the sensor with an app and it seems to work properly

 

[MrGoodtunes]

... There's a bit of a display brightness glitch when it comes back on (100% brightness for a few milliseconds), but that's not a huge problem. ...

I have been noticing momentary brightness upon various screen-on starts with all of Danil's builds, all the way back to the first one I tried, CM-12 (Lollipop). But, as you say, we have more pressing issues.

 

[chrischa]

Hi guys,
i fixed the issue with the black dialing screen. At least in my repository.

I compiled build the whole stuff and it worked for me.
I attached you the changed Dialer.apk. Its no longer required to replace this by Google dialer.
Just replace the Dialer.apk (that stays black) in /system/priv-app/Dialer/ with this one

Best regards