yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] Telone:
Yes when it works but only a few times. 50% of time it tells me that there is no service even if 1 minute earlier was working very well. The only solution is a wipe cache.

I can't stay with phone that sometimes work and sometimes doesnt work.

---------- Post added at 11:53 AM ---------- Previous post was at 11:49 AM ----------

Doesnt do anything :(
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
I'm having this problem too.

Now it's like this all the time, but before (since los 14.1) it only happened sometimes (most oftenly when moving the phone out of wifi range), and i could easily fix it by enabling flight mode, then wait a few seconds, then disable flight mode and mobile data would work again.

I'm currently building a build with kyasu's sources, modified for trying out some changes that might fix this. I won't know if it works until later today, as I'm at work at the moment, and I'm building at home on a slow computer since last night. If it works, then I'll let you know, because there are several other people having this problem.
[Galaxy S 4 i9506 Android Development] Telone:
Oh it would be amazing
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Hi. I got it working. I now have mobile data working again on my device. [MENTION=4861355]kyasu[/MENTION] : I've committed a change in msm8974-common that's up for review at the moment: https://review.lineageos.org/#/c/LineageOS/android_device_samsung_msm8974-common/+/225136/

You can pick this for a future build if you like.

Edit: It might not be merged to msm8974-common, but I guess it can be put elsewhere

Edit2: I've uploaded the build to androidfilehost but I'm usure if i can post the link in this thread
[Galaxy S 4 i9506 Android Development] Telone:
So we need to wait for [MENTION=4861355]kyasu[/MENTION]
[Galaxy S 4 i9506 Android Development] kyasu:
Thank you for your commit. I picked your commit.

https://github.com/kyasu/android_de...mmit/242b9e8eeeb3dd9cab8ea3d6e45ead6567086bd6

I also uploaded the build with your commit.

lineage-15.1-20180821-UNOFFICIAL-ks01ltexx.zip

https://www.androidfilehost.com/?fid=1322778262903986223

Please test it.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Thanks. Mobile data working good so far on my device :)
[Galaxy S 4 i9506 Android Development] Telone:
Amazing!:)
[Galaxy S 4 i9506 Android Development] :
[MENTION=5417899]DiamondJohn[/MENTION]

About the AudioFX: Setting the build prop "audio.offload.disable=0" to "audio.offload.disable=true" helps. AudioFX is now partly working with the build in music player. Unfortunately only the equalizer is working, no special effects like bass boost or reverberation. So more research could possibly go into that, maybe [MENTION=4861355]kyasu[/MENTION] got an idea as well.
[Galaxy S 4 i9506 Android Development] balakor:
Hi!

I have problem with bootmodem flashing. After I flash it with Odin, there is no change, the old bootloader and modem stay. I tried several Odin version (lateset 3.13.1 3B patched too), tried BL+AP+CP (all together also), but no success. Please help. I have No Sim Card message after boot. (LineageOS 15.1_20180821) Thanks!
[Galaxy S 4 i9506 Android Development] :
Does Odin display the "pass" message on the left after the flash? If yes and it still does not work: Did you make sure to power the phone off before booting to download mode?
[Galaxy S 4 i9506 Android Development] balakor:
Yes, I have PASS message.

Thanks, I will try powering the phone off. I restarted directly to Download mode.

UPDATE: Thank you very much! It worked. I turned off the phone, took out the battery and put it back. Then entered Download mode, flashed via Odin in BL, after that I turned off the phone again, entered Download mode again and flashed one more time, and it WORKED. I've been trying for hours without success before...
[Galaxy S 4 i9506 Android Development] :
The button combination to start into download mode is power+home+volume down
[Galaxy S 4 i9506 Android Development] DiamondJohn:
last_kmsg of bootloop

[MENTION=4861355]kyasu[/MENTION]

I think I have "trapped" the difference between a normal reboot and a boot-loop within a last_kmsg log. You can find the details within the post https://xdaforums.com/showpost.php?p=77404654&postcount=8955 which also shows the point at which they diverge. Below are direct links to each of the logs.

last_kmsg: Good Boot: https://www.hastebin.com/avabopojug.bash

last_kmsg: Bad Boot: https://www.hastebin.com/odajuqonit.bash

View attachment 4578035

I really hope you have some time to fix it.:fingers-crossed:
[Galaxy S 4 i9506 Android Development] Jelges:
Thank You very mich with Build 2018-08-21 SIM works again. Now I can use my Main user account again. Thank You both.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Yes, this is the proper way to do it. Sometimes just powering down won't work either. The correct procedure is to remove the battery for a couple of seconds, reinsert it, and use the buttons to boot to download mode..
[Galaxy S 4 i9506 Android Development] :
[MENTION=4861355]kyasu[/MENTION] [MENTION=5417899]DiamondJohn[/MENTION] [MENTION=6459107]darkness[/MENTION]

So I got AudioFX fully working. I attach the build.prop for everybody to test and see the changes. It might be that I changed more than necessary, but I tested quite a bit and this works well for now.

To test it you can simply replace the build.prop in /system and reboot. Back up your current build.prop first or flash the rom.zip one more time, if you wish to undo the changes.

A few words were the changes came from: I deleted all entries in build.prop related to audio (there were also some in additional buildprops at the bottom) and replaced them with the ones from hlte from here: https://github.com/LineageOS/android_device_samsung_hlte-common/blob/lineage-15.1/system.prop

Since it was still not working I added this entry: "audio.offload.disable=true".
[Galaxy S 4 i9506 Android Development] DualJoe:
Anyone getting xposed properly running on latest rom (20180821)?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Just an FYI for clarity sake. I will not personally use a ROM unless I can get Viper (ie AudioFX replacement) working, and for Oreo, I have got it working, so AudioFX was only of concern regarding the ROMs I built for others, who may wish to use AudioFX instead of Viper. However, as I type this, I realise I may look into adding this property change to my build.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
I've narrowed down the bug to this file: kernel/samsung/msm8974/drivers/video/msm/mdss/mdss_samsung_dsi_panel.c, Line 1229 ..

BUG_ON(msd.sdimconf->generate_gamma == NULL);

I'm will investigate it further this evening...
[Galaxy S 4 i9506 Android Development] :
https://github.com/kyasu/android_de...mmit/eecc88591fdefd52fa5d682e1657793a2f47afa9

:good:

So AudioFX should be fixed from the next build on. Btw GPS works fine with the latest build for me without any changes needed to gps.conf.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I have a modified init.qcom.rc that now creates a build that does not bootloop! :victory: Give me a little bit and i will expand on this soon, so I wouldnt suggest spending time specifically on the above.

---------- Post added at 12:02 PM ---------- Previous post was at 11:08 AM ----------

[MENTION=4861355]kyasu[/MENTION]

[MENTION=6459107]darkness[/MENTION] contacted me telling me he tried a few different init.qcom.rc files from different devices (but similar) and found they did not boot loop, but also failed numerous other features eg no network connection.

To cut a long story short, now that init.qcom.rc appeared to be a possible candidate for resolving the boot-loop, I tried the following, and it worked (mind you I did have 15+ other attempts before I thought of this idea...:silly:)

The idea: :angel: When the ROM booted, it appeared for the most part good, so it was the actual boot sequence that was triggering the loop. The other file found by [MENTION=6459107]darkness[/MENTION] didn't boot-loop, but it also did not prepare the phone for full functionality. My idea was since once it booted, it appeared ok, was to move a bunch of the initialisation to occur AFTER the phone had finished booting. It WORKED! :highfive:

The file I came up with has changes that are a bit of a dogs breakfast (ie a coding mess), but it appears to be working, and after 15 to 20 boot-ups I had noooo boot-loops. At this stage it is simply a "proof of concept" and not in any way a proposal as a final fix.

Anyway, for your info, the file I used can be found at: https://www.hastebin.com/royikazohu.pl

To change the boot sequence, I moved a bunch of lines (with some logic by comparing to other devices) to occur on "service.bootanim.exit". ie after the phone had finished booting.

In addition to changing the boot sequence, some of the other things I found were:

* The path "/sys/class/devfreq/qcom,cpubw.34/" does not exists on our phone, I changed it to "/sys/class/devfreq/qcom,cpubw.42/"

* The service audiod does not appear to exist on our phone, so I commented that out

* I found a bunch of other paths that I couldn't find on a booted phone, so I commented them out. For the most part I commented / prefixed these lines with "#*#"

I have also noticed a few more items when comparing to other devices. eg mkdir /persist in hammerhead, but in your one, there are many references (chmod etc) but no makedir (haven't made this change in the above file)

I think I read it somewhere above, but I also found I had to set the preferred network type to global manually. Maybe a change to this init file would also do this automatically.
[Galaxy S 4 i9506 Android Development] kyasu:
[MENTION=5417899]DiamondJohn[/MENTION], [MENTION=2696268]Sub_Zero2[/MENTION], and others.

Thank you so much for your efforts.

I found that the bootloop (kernel panic) is caused by a call of the backlight control before the panel is initialized.

The solution of this are (a) kernel patch or (b) boot sequence (init.qcom.rc) change.

I uploaded a kernel patch. I will check the init.qcom.rc of [MENTION=5417899]DiamondJohn[/MENTION].

https://github.com/kyasu/android_ke...mmit/da88a34ac1709aa922bf1adae3045b5f6be6d961

Thanks!
[Galaxy S 4 i9506 Android Development] khalvat:
Hi every one [MENTION=4861355]kyasu[/MENTION] Sorry my english is very bad but i want help u as much as I can

I found in build.prop a few more and repetitive sentences in other rows.

I think my bootloop different from editing. I do not know

I wish can help
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Its a mess!

---------- Post added at 03:15 PM ---------- Previous post was at 03:02 PM ----------

oh... and these are the lines I found iin hammerhead for "on init"

on init
[COLOR="Green"] # Set permissions for persist partition
mkdir /persist 0771 system system
[/COLOR]
# Support legacy paths
symlink /sdcard /storage/sdcard0

write /proc/sys/vm/page-cluster 0
[Galaxy S 4 i9506 Android Development] Vickeey:
Hi Folks

I have Found Something

If you stuck on Bootloop then go to recovery mode wipe cache and wipe dalvik cache and then Reboot your Phone.

Using Phone S4 I9506 LTE-A (SHV-E330L)
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Brilliant!
[Galaxy S 4 i9506 Android Development] wkwk:
Thanks guys for dedicating so much time towards improving this device. Keeps my E330s alive even after 6 years.
[Galaxy S 4 i9506 Android Development] kyasu:
lineage-15.1-20180826-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).

Sync with the latest LineageOS source.

Fix mobile data issue (Enable SVELTE).

Fix AudioFX issue (Disable audio offloading).

Fix bootloop issue.

Changes:

https://github.com/kyasu/android_device_samsung_ks01ltexx/commits/lineage-15.1

https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-15.1
[Galaxy S 4 i9506 Android Development] DonAndress:
So I guess what is still left to do is to reverse engineer the camera performance... [emoji23]
[Galaxy S 4 i9506 Android Development] Telone:
Is there a way to remove set warranty bit:kernel on boot?
[Galaxy S 4 i9506 Android Development] sakibm47:
I think that's normal
[Galaxy S 4 i9506 Android Development] 000001a:
hello,

i have a problem with my SIM with your ROM

i have tested around:

model: GT-I9506

modem: I9506XXUDRB1_I9506XXUDRA1_bootmodem.tar

full wipe & clean install, without opengapps & SU

lineage-15.1-20180708-UNOFFICIAL-ks01ltexx: works

lineage-15.1-20180812-UNOFFICIAL-ks01ltexx: do not work

lineage-15.1-20180826-UNOFFICIAL-ks01ltexx: do not work

other roms:

AospExtended-v5.8-ks01ltexx-20180825-0330-UNOFFICIAL: do not work

RR-O-v6.1.0-20180816-ks01ltexx-Unofficial: do not work

look like a major problem after 20180708...
[Galaxy S 4 i9506 Android Development] khalvat:
Thank u [MENTION=4861355]kyasu[/MENTION] so much??
[Galaxy S 4 i9506 Android Development] khalvat:
Every thing working great

Thank guys for this rom
[Galaxy S 4 i9506 Android Development] Telone:
Ok but is there a way to remove?
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
There's an app called Triangle away on google play... But I don't think our device is supported (GT-I9505 Is supported though)
[Galaxy S 4 i9506 Android Development] Telone:
So no way to remove?

*Triangle away doesnt work*
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I'm pretty sure the above is caused by unlocking your bootloader (hence the term "warranty", to tell you your warranty is now broken, and let the repair guys know), and once it has been unlocked, a physical diode is burnt out (at least on some phones). ie it cant be rolled-back/removed. Well, thats what happens on other devices, apart from the good old Nexus ;) which was basically earmarked for further dev.
[Galaxy S 4 i9506 Android Development] Telone:
Everyone with this rom have this warranty?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Everyone with any custom ROM flashed via custom recovery (ie an unocked bootloader) would have this. If I am right, no app will be able to remove it, as it appears before the ROM (ie Android) is running. ie while the bootloader is loading/running and the bootloader is closed source.
[Galaxy S 4 i9506 Android Development] Telone:
Damn, I dont like but if I cant remove it is not a problem. Thanks for answering! :)

*Another question: is there a way to flash without a custom recovery?
[Galaxy S 4 i9506 Android Development] wkwk:
The Rom has no stability issues. Its my daily driver, have zero issues to report.
[Galaxy S 4 i9506 Android Development] jegogo99:
I can't create Weather widget and I can't find a valid weather provider

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] quindecimo:
Is there any suggested bootloader for this ROM? my bootloader is I9506XXUDOL1.
[Galaxy S 4 i9506 Android Development] :
Yes, there is a link in the op (and it's a different one than your current modem)
[Galaxy S 4 i9506 Android Development] wkwk:
Anyone tried face unlock?. Am getting FC with both magisk and direct GAPPS nano package.
[Galaxy S 4 i9506 Android Development] :
I tried face id with the magisk module. I got fcs too and didn't bother to investigate any further.
[Galaxy S 4 i9506 Android Development] wkwk:
This works with the google nano package -

https://github.com/opengapps/opengapps/issues/555

Look for the zip file in the thread.

Its really fast and impressive.
[Galaxy S 4 i9506 Android Development] DSMNCIHAGT:
My battery is draining way faster than with lineage os 14, does anyone know what could be the reason for this?

also how do i install the bootloader/modem recommended in this thread, ive watched video tutorials and they use odin to flash 2 files while the download link for the bootloader in this thread only has one .tar file. can i not use odin and instead use adb sideload?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
To update your bootloader and modem.

1. Download and install the latest version of Odin (v3.10.7 I think)

2. Download the file from the OP

3. Start Odin

4. Boot the phone into download mode. This can be done by holding power+home+volume down. (oopss... missed this step, thanks to [MENTION=7302398]PixelChris95[/MENTION] for reminding me)

5. Connect your phone via USB to computer

6. Select the file you downloaded into the AP slot. It should auto select the checkbox next to it

7. Press the "START" button

8. Wait

9. Enjoy.
[Galaxy S 4 i9506 Android Development] :
After 3. you first have to power off your phone and boot into download mode. This can be done by holding power+home+volume down. Then proceed with 4.
[Galaxy S 4 i9506 Android Development] foxrft:
I'm using this rom for few days now, I noticed that the camera app language doesn't change as well as some text in setting. The weather providers on Lineage website doesn't work on Oreo and if I use the blur effect in Lawnchair Launcher it will force close.
[Galaxy S 4 i9506 Android Development] :
I am sure the translations will get updated soon. Don't forget that los 15.1 was not officially released yet. What blur effect do you mean, because this sounds like a bug of lawnchair, not this rom.
[Galaxy S 4 i9506 Android Development] jegogo99:
You can use chronus app for weather widget. In classic mode is similar to lineage weather widged

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] :
It's still crashing for me. Strange...
[Galaxy S 4 i9506 Android Development] foxrft:
Yes I read that Lawnchair isn't fully supported on Oreo yet!
[Galaxy S 4 i9506 Android Development] wkwk:
Are you using Nano GAPPS?. It may not work with magisk version.

Also I used the second zip file in the thread, facelock-all.zip
[Galaxy S 4 i9506 Android Development] jegogo99:
I have DOL1 too. With this, battery lasts longer than if I use last modem

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] :
Got it working now! Thx mate :good:
[Galaxy S 4 i9506 Android Development] DSMNCIHAGT:
I managed to install the recommended bootloader/modem but later installed another modem that a user here said gave better battery than that one, but I still have bad battery. Anything I can try?
[Galaxy S 4 i9506 Android Development] jegogo99:
I test different modem and compared result. For now, DOL1 is better than others in my phone

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Triangle away (requires root) patches the bootloader, but the GT-I9506 is not supported by that app...

[MENTION=9382716]Telone[/MENTION]: Don't worry, the yellow text is quite normal when flashing a rom. A custom rom will give you this yellow text, it doesn't matter what recovery you have in place (also stock)...

---------- Post added at 08:19 PM ---------- Previous post was at 07:38 PM ----------

Problem with your sim...

Can you give a more detailed description of the problem?
[Galaxy S 4 i9506 Android Development] Telone:
Yes it is only because is not very cool..
[Galaxy S 4 i9506 Android Development] derflasher:
What is SVELTE?
[Galaxy S 4 i9506 Android Development] 000001a:
i do not believe, my SIM have a problem.

the older ROM does work.

in other devices it works to.

how can i help you to discover the problem?

i have no developer skills :(

it just do not detect the SIM in the newer ROMs (no carrier)

i cannot scan for carrier, i get a network error.

the SIM status shows "emergency calls", but i will not test it (abuse is punishable).
[Galaxy S 4 i9506 Android Development] Telone:
I was having the exact same issue but with latest build (26 August) there is no problem...

Have you flashed with a full reset (I mean the complete reset from TWRP? ?
[Galaxy S 4 i9506 Android Development] eccko:
"Svelte is an ongoing effort by Google to minimize RAM use by system and apps across the range of Android devices in the ecosystem. In Android N, Project Svelte is focused on optimizing the way apps run in the background."

Source - https://www.quora.com/Android-operating-system-What-is-project-Svelte
[Galaxy S 4 i9506 Android Development] khalvat:
I had this broblem too. You should after install lineage15.1. 20180826 download modem from first page and flash modem with odin (CP) maybe your odin cant flash modem I9506XXUDRB1_I9506XXUDRA1_bootmodem pls use another odin or quit battery and try again

Good luck;)
[Galaxy S 4 i9506 Android Development] DiamondJohn:
AP not CP unless its a language thing.
[Galaxy S 4 i9506 Android Development] khalvat:
No [MENTION=5417899]DiamondJohn[/MENTION]

CSC is for language

AP for recovery and official rom...

CP for modem

He should flash modem with odin CP

I had problem too and use odin 3.12.7 CP for modem
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Your in the minority,

and then theres my own personal experience. I am using Odin3_v3.12.10 I have flashed back and forward a number of times.
[Galaxy S 4 i9506 Android Development] djrys:
still fix gps and will be super :svetius::D
[Galaxy S 4 i9506 Android Development] DiamondJohn:
[MENTION=4861355]kyasu[/MENTION] FYI: In my iinit.qcom,rc file, I have added the lines

[COLOR="Silver"] setprop ro.telephony.call_ring.multiple false[/COLOR]
[COLOR="Green"] # set preferred network to GLOBAL
setprop ro.telephony.default_network 10[/COLOR]

To default the phone to Global on boot, and it appears to have worked

10 was taken from line 153 of https://github.com/LineageOS/androi.../android/internal/telephony/RILConstants.java
[Galaxy S 4 i9506 Android Development] 000001a:
[MENTION=9382716]Telone[/MENTION]

full wipe / clean install (rom only)

[MENTION=6582800]khalvat[/MENTION]

i use the last modem (page1/post1)

i will try to reflash it again (CP-mode)

---

i see, after odin (3.10.7) flash, my baseband has not changed.

but odin said success, weird... o.O

p.s. in the past odin didn't chare if i flash over AP or CP

by default i always flash via AP.

till today, i never had a problem with it...

maybe there are issues/differences with the version numbers...

ok, I got it to work.

i used the last odin (3.13.1) & the CP-mode

the funny thing is:

my baseband still shows I9506XXUDOJ2

but i flashed I9506XXUDRB1

...wierd

(i will try a full stock-rom flash to fix this..., later)

thanks for help.
[Galaxy S 4 i9506 Android Development] khalvat:
You cant flash modem with 3.13.1 because its for android 8 flash. Use 3.12.x CP for modem. Good luck bro
[Galaxy S 4 i9506 Android Development] henkka22:
is there way to flash this modem with heimdall. If you have package for it, can you link please.. (#neverusingwindows) :D
[Galaxy S 4 i9506 Android Development] aelfinn:
Of course. Put your phone in Download Mode (start it up by holding Power+Home+VolDown) and connect to your computer. Open a terminal, type

heimdall detect

which should return “Device detected”. Then make sure you know what the correct partition is called by typing (assuming you’re on Ubuntu linux)

sudo heimdall print-pit --no-reboot

Assuming that the returned text contains “Partition Name: MODEM”, and that the modem.bin file you want to flash is located in the directory you started the terminal from, you can flash the modem by typing

sudo heimdall flash --MODEM modem.bin --no-reboot

The “no-reboot” parameter prevents the phone from rebooting, in case you wanted to flash something else or boot into recovery. You can also flash more than one thing at once, eg:

sudo heimdall flash --ABOOT aboot.mbn --MODEM modem.bin

If the flash was successful, the returned text should be unambiguous. Likewise if it wasn’t.
[Galaxy S 4 i9506 Android Development] 000001a:
hmm...

still I9506XXUDOJ2 :(

i do not know what is broken,

i have to fix it with the sock rom/kies

this sux...
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
1. Power off the phone.

2. Remove battery for 5 seconds

3. Insert battery

4. Boot to download mode using Volume down + Home + Power keys

5. Flash modem

(Don't reboot to download mode from within lineageos, flasing modem won't work then)

Voila
[Galaxy S 4 i9506 Android Development] DiamondJohn:
when flashing modem and bootloder via ODIN (Odin3_v3.12.10) , place it in the AP slot.