yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] Geonaute:
Hello [MENTION=4861355]kyasu[/MENTION]

Do you think you can update the ROM using the gps.conf from post #373 please? It seems that many people changed it successfully, and it's one of the big issues on this LineageOS portage..! ;)

Thanks ahead, and thanks for all the work you've already done! :)
[Galaxy S 4 i9506 Android Development] DiamondJohn:
The GPS.conf file is region specific, so the one at the other post is NOT targeted for most people. Its actually targeted specifically for Germany. ie that GPS.conf file should not go into any international ROM.

The fact many people have already done it, already shows its easy to do., if you wish to do it anyway.
[Galaxy S 4 i9506 Android Development] Geonaute:
Thank you, I didn't know that... I'm sorry...

I had a few questions concerning the file though, if you can help :

My phone is not rooted, and the gps fix would be the only reason for me to do so... and then block some other apps (such as Netflix)so...

Do you think I can edit the file through my computer if I mount my device via USB in recovery mode? Or is there absolutely no other way to access these files without rooting the phone?

If its possible to do so, could you show me the post where they explain how to set the file up? I couldn't find it...

Thanks ahead for your help! :)
[Galaxy S 4 i9506 Android Development] :
It's possible to make a flashable zip. Just out of interest: Since the builds from this month my GPS performance is reasonable (before that it was terrible). Is it still that bad for where you live?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Once you have custom recovery, you can use the file manager in TWRP. Just remember to also set the permission of the file when your done. ie the phone does not need to be rooted. I have assumed you have flashed this ROM and therefore must be using a custom recovery.

Make a back-up and I'd be interested how you go with the file I used for my ROM. I get the best GPS performance I have ever had with this phone.:eek:

https://xdaforums.com/showpost.php?p=77460904&postcount=102

Also, before you try my file, I noticed a really big improvement in my previous ROM with GPS after I calibrated my compass. REALLY big improvement.:eek: try that first.
[Galaxy S 4 i9506 Android Development] 000001a:
thx, now it works.

- performed a cold boot (battery removed)

- used odin 3.12.7

- flashed the last modem in the AP mode

- reboot

- works with 20180826

I should perform a cold start more often.

maybe they should include this in the description...

people do forget little details... ;)
[Galaxy S 4 i9506 Android Development] :
It was mention here just a few pages ago, but glad you figured it out now :good:
[Galaxy S 4 i9506 Android Development] elijo_otro:
help me! i updated the last one version...and don't work sim for me.

Don't ask me the pin, and i don't have network
[Galaxy S 4 i9506 Android Development] eccko:
Flash recommended Bootloader/Modem I9506XXUDRB1_I9506XXUDRA1_bootmodem.tar from kyasu via ODIN to AP slot.

Link - https://www.androidfilehost.com/?fid=3700668719832239236
[Galaxy S 4 i9506 Android Development] elijo_otro:
i thought that recommended was DOJ2 (i have it). I0m going to flash this ... thanks

yeah! this fix the problem! thanks you very very veery much
[Galaxy S 4 i9506 Android Development] eccko:
No problem. :)
[Galaxy S 4 i9506 Android Development] lalu:
Hey guys. I just updated to the latest Magisk Manager app and after installing the latest zip (17.0) it gets into a bootloop (not even getting over the first screen). I reinstalled le Lineage OS zip and got rid of the bootloop, but it seems I can't get root. Does this happen to anyone else? Thanks!
[Galaxy S 4 i9506 Android Development] DiamondJohn:
16.0 is the latest stable version. 17.0 is beta, so bugs can be expected, and thus it could/would happen to others. Its not a stable release.

You would be best to ask over on the Magisk beta thread, and provide them logs. it is not a ROM issue.
[Galaxy S 4 i9506 Android Development] lalu:
Got it. Thank you and sorry if I spammed.
[Galaxy S 4 i9506 Android Development] aelfinn:
As of today, the latest stable version is actually 17.1 . :)
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Remember to flash the addonsu zip for lineageos roms...
[Galaxy S 4 i9506 Android Development] Hemuli:
No. Either addonsu if you want the old way of rooting, or Magisk if you want the new systemless way. Not both.

There was a rapid update to 17.1 because 17.0 caused boot loops for some.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Look at what he wrote: he reinstalled lineageos to get rid og the bootloop, then he noticed he could not get root anymore ;)

Edit: You are correct when installing lineageos + Magisk
[Galaxy S 4 i9506 Android Development] zaphod666:
Hey so I am really liking this rom so far but have come across a few problems. First sometimes on a phone reboot I lose the baseband and my signal. Restoring the EFS partition fixes this for a while but its still a bit annoying. Second I noticed that rebooting the phone logs me out of various app accounts like Spotify and Reddit is Fun.

Anybody have any thoughts on this? Aside from these issues I am really enjoying the rom.
[Galaxy S 4 i9506 Android Development] Chris Miller94:
Magisk 16.0 was a stable version but its updated to 17.0 stable

If you checked the changelog in 17.0 you can see the new "policies" for updates.

Every release is public release and you can use it as a daily driver.

Check the 4 digit number (eg. 1700)

This release stable but 1720 will be beta.

1710 stable too, because - i think - something goes wrong in 1700 and thats fixed in 1710 stable release.

When i like to install 17.0 - my recovery is the latest TWRP 2.3.2.0 - during the install session i get corrupted file and another errors from TWRP, and i cant use 16.0 and Magisk remove zips.

I havent root until 17.1 released. Now everything is good like in 16.0
[Galaxy S 4 i9506 Android Development] DiamondJohn:
ummm... sure.. you can... but only if you wish to live on the edge. If its released, I think that would mean its public, but not necessarily stable.

17.1 is the stable version, many people had issues with 17.0 so 17.1 was released pretty soon after.

I have a second phone, and that just auto-updated to 17.1 ie it skipped 17.0 as I have it linked to the stable channel for updates.

Just to clarify, when I made the statement that 16.0 was the stable version, 17.1 was released something like, less than 24hrs before I had made the statement.:silly: Please, lets stop beating a dead horse.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
For the baseband bug, try to reproduce it, and do "adb bugreport mybugreport.zip" or using root terminal: "bugreport mybugreport.zip" ...

Then post the mybugreport.zip here...

Edit: you should use the adb method for now

Edit2: you can do it from within developer options on your device. Tap on "take bug report", then you can share the zipfile for example via email, then send the email to yourself.

Just remember that the bugreport might contain personal info, such as which telephone numbers you called since the last reboot.
[Galaxy S 4 i9506 Android Development] Telone:
Will be fixed the delay of 2-3 seconds to wake up phone?
[Galaxy S 4 i9506 Android Development] elijo_otro:
the rom is TOP, but spend a lot of batery in repose. too much :(

In addition, In 14 version, i had better coverage (i think that coverage is the problemn of batery)
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Sorry for being off topic here.

Interesting, as I had previously always used bugreport > /sdcard/mybugreport.txt I never knew it could create a zip file directly. However, when I tried it (ie bugreport mybugreport.zip), it failed :o and simply echo'd the output to the terminal. I also checked on line, and what you are saying is documented as being correct. :confused:

Furthermore, when I tried bugreport > /sdcard/mybugreport.txt it actually told me this method was deprecated and I should use your suggested method. However, this deprecated method was the only way I could get it to work, but is was a txt file not a zip.

Is there a specific location where the zip file is stored? I tried adding a path, and that did not work ie bugreport /sdcard/mybugreport.zip

I also tried running it from a specific directory, and that also failed. ie cd /sdcard; bugreport mybugreport.zip

Am I missing something?
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
To be honest, I havent used the zip method from within a terminal before, only as text. (Maybe i should not have assumed it would work that way, but i don't have time to investigate it atm).

But with adb, the zip gets downloaded to your computer automaticly.

The zipfile contains very detailed information, including snapshots of certain settings, anr logs, tombstones, mount info and recovery logs.

Edit: you can do it from within developer options on your device. Tap on "take bug report", then you can share the zipfile for example via email, then send the email to yourself.

Edit2: You can find the bugreports in: /data/user_de/0/com.android.shell/files/bugreports/ (requires root).

You generate a bugreport with the command bugreport. That's it.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
ALL an FYI

Even if you had the time, I would not of been expecting you to debug something which is probably a problem in google source code.

Yep, I tried running it directly via adb and not from a shell, and it all appeared to work as you say. Pity for me it does not work directly from a shell within android.

I tried turning it on under developer options into the power menu, and it did not appear there. I am running a custom ROM (ie crDroid not LOS), which may help explain that not working.

And running it from the PC via adb did leave some files in that path, which for me actually means I will manually clean them up, since the zip file is on my computer (in the actual path I ran the command from)
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Favor?

Could someone who is running the latest LOS 15.1 build provide me a last_kmsg ? You can get it simply by running the following in a shell

su;
cat /proc/last_kmsg > /sdcard/last_kmsg.log;

Or use an app such as https://xdaforums.com/android/apps-...rehensive-documentation-t3806260#post77516597 (it is under Logcat>Last Kmsg)
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Here you go.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
If you didn't find a zipfile in the location i specified previously, then you can check here:

/data/data/com.android.shell/files/bugreports/
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I obviously was not clear. The zip file was pulled by adb onto my local pc, in my directory from where i run adb. As to its location on the device, the console output tells you exactly where to find it (on the device, but not the pc)

C:\Java\x86\Android\android-sdk\platform-tools>adb bugreport
/data/user_de/0/com.android.shell/files/bugreports/bugreport-ks01ltexx-OPM6.171019.030.H1-2018-09-05-00-38-30.zip: 1 file pulled. 1.3 MB/s (1657987 bytes in 1.254s)

the first time I ran it, the above folder did not exist:confused: but the file was easy to find on the PC. weird.

---------- Post added at 01:10 AM ---------- Previous post was at 12:51 AM ----------

yep, as I thought. There are 15 cases of "samsung_dsi_panel_event_handler : unknown event"

I recently did a build of crDroid, and on first boot it got stuck on the bootanimation, and the last kmsg log was just all these. All the following boots went fine. Your log has 15 of them, with no indicator of what the unknown "event" is equal to, if its the same or different every time etc etc etc

I looked at the logging line in source, and a really simple change also includes the value of the unknown event ie what the heck is not known.

+++ b/drivers/video/msm/mdss/mdss_samsung_dsi_panel.c
@@ -4422,7 +4422,7 @@ static int samsung_dsi_panel_event_handler(int event)
break;
#endif
default:
[COLOR="Red"]-	pr_err("%s : unknown event \n", __func__);[/COLOR]
[COLOR="Green"]+	pr_err("%s : unknown event (%d) \n", __func__, event);[/COLOR]
break;

}

Even if the info doesn't help now, I think the above is still something [MENTION=4861355]kyasu[/MENTION] may wish to add to the source if he gets a chance. i am especially interested since "drivers/video/msm/mdss/mdss_samsung_dsi_panel.c" was part of the fix he put in for the bootloop issue.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
I wasn't actually clear either.

I'm not sure if you understood what i meant, but just to clarify (just in case):

If you do:

bugreport

In console, then the bugreport zipfile will be saved in that dir. But if you use the adb method, then the zip will be deleted after adb pulls it to the computer.

About the commit to mdss_samsung_dsi_panel.c:

I agree, it would be useful to debug the unknown event(s).
[Galaxy S 4 i9506 Android Development] 1Johan3Anderson:
No Network connection

Hello,

I have flashed the latest variant of the LineageOS 15.1 from your build. Before I had installed also one of your builds (15.1 as well). However, now I get no network connection, something that did not happen before.

I did a wipe for cache&dalvik cache as well as a complete wipe to install a new ROM. No changes.

When I try to search for networks I get "Error while searching for networks". I tried setting LTE in testing mode, but no luck here either. I see there that my IMEI is unknown. Is it possibly because of this?

Cheers,

Joahn
[Galaxy S 4 i9506 Android Development] BarryViper:
Did you flash the latest boot/modem and set your preferred network to "Global"?
[Galaxy S 4 i9506 Android Development] ave20:
This ROM has this network connection problem since the beginning of this topic and first release. There are several other problems and yet, every new release is only about "security update" from LOS.

Ppl reported at least few really alarming issues - no changes at all. Sadly, this ROM is a waste of time and I tried it 3 times by now. Same old bugs.
[Galaxy S 4 i9506 Android Development] 1Johan3Anderson:
The strange thing is that it worked on the previous version. I did not have any serious problems with this ROM until now. I will try flashing the latest boot/modem and see if it works.

---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------

Thank you for the fast reply! No I did not flash the latest boot/modem as it worked with the previous version. Is this the latest: I9506XXUDRB1_I9506XXUDRA1_bootmodem.tar? Is there any way to flash it with TWRP instead of ODIN?
[Galaxy S 4 i9506 Android Development] BarryViper:
Thank you for the fast reply! No I did not flash the latest boot/modem as it worked with the previous version. Is this the latest: I9506XXUDRB1_I9506XXUDRA1_bootmodem.tar? Is there any way to flash it with TWRP instead of ODIN?[/QUOTE]

That's the tar file. Power off your device and boot to download mode with Volume down + Home + Power buttons and flash it via Odin (AP) slot. Don't forget to set preferred network to Global after flashing is done. Good Luck.
[Galaxy S 4 i9506 Android Development] 1Johan3Anderson:
That's the tar file. Power off your device and boot to download mode with Volume down + Home + Power buttons and flash it via Odin (AP) slot. Don't forget to set preferred network to Global after flashing is done. Good Luck.[/QUOTE]

Thanks BarryViper. It did work after the update. Awesome! Now I can keep using this great ROM!
[Galaxy S 4 i9506 Android Development] :
The ROM is for sure not 100% free from bugs, but claiming that nothing gets fixed is just rude towards the dev, especially because in the very last build some major bugs were fixed. Also keep in mind: The last official Android version released for this device was Android 5.0, so we are already 3 versions (or 6, if you count the .1 versions) beyond that and I am honestly amazed how well Android 8 performs on this device. It's still absolutely a daily driver with Android 8 for me!
[Galaxy S 4 i9506 Android Development] BarryViper:
Can't agree more. Give credits where it's due and if one is not even appreciative, just go back to stock firmware and stick with it. There's no need to repeat one's grousing here.
[Galaxy S 4 i9506 Android Development] msin84:
Hello, I wanted to upgraded from 14.1 to 15.1. I did a full wipe, updadet the recovery and the modem. The rom comes installed, but when I install the gapps I alway get a loop error with google play services...I also tried also a sequential install after the rom but no luck. The last try was to install the stand alone APK but no luck. Any idea?

Thanks to everyone.
[Galaxy S 4 i9506 Android Development] :
Flash gapps right after flashing the ROM without booting up in-between and if this does not solve the issue try downloading an older gapps package (like from a few days ago or something)
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
We kinda fixed the mobile network issue... It is actually more stable now than it was before on los15.1 and even los14.1... (Remember to also flash latest bootmodem, or you will get unknown imei).

If you are using the latest version of odin (v3.13.x iirc), then you should use the BL or CP slot instead (or else all the files in the bootmodem package won't be flashed)

Nice!
[Galaxy S 4 i9506 Android Development] msin84:
Unluckly It doesn't work....On march I tried a beta CM 15 with unofficial gapps and was working.....at the moment I will setup the secondary i9506 with 14.1. ....after the migration is completed I will test again the CM 15.1 on the primary i9506 (Yes...I really love this phone since 2014).

Thank you anyway!
[Galaxy S 4 i9506 Android Development] Nicholas.K:
Problem with imei after flash

Hi everyone,

When I flash lineage 15.1, my imei disappears with "unknown" written under it. And my sim card doesn't work anymore. I thought efs could be corrupted, then I flashed stock rom back, and it restored imei number and sim card worked again.

Then a flashed lineage 15.1 again and once again, imei disappeared with same problem as above. I didn't have this problem with lineage 14.

Can someone point me to the right direction?

Thank you.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Did you read even the current page?
[Galaxy S 4 i9506 Android Development] Angel-OD:
Little modification please!

Everything is working on E330S except for the mobile network. I hope you can fix this issue and launch for E330S. Thanks.
[Galaxy S 4 i9506 Android Development] BarryViper:
Are you using gapps version: Arm, 8.1, pico?
[Galaxy S 4 i9506 Android Development] msin84:
I'm using the 8.1 nano package...I will try the pico one in the next days!

Thank you!
[Galaxy S 4 i9506 Android Development] DiamondJohn:
FYI: samsung_dsi_panel_event_handler : unknown event (?)

So I made a build of Oreo crDroid, with the above adjustment. I am also running with a slightly modified init.qcom.rc file. Anyway, the lines I am getting logged are:

samsung_dsi_panel_event_handler : unknown event (1)
samsung_dsi_panel_event_handler : unknown event (6)
samsung_dsi_panel_event_handler : unknown event (7)
samsung_dsi_panel_event_handler : unknown event (8)

Not in that order, and multiple cases of each. I think the above was after a wipe of dalvik/cache as another last_kmsg log only has the (1) logged.
[Galaxy S 4 i9506 Android Development] Nicholas.K:
Thank you for the help you provided. It fixed the problem. Though I read the page and have flashed the bootmodem before I asked my question here, the workaround was to flash it twice! First time I flashed the

bootmodem, the imei stayed the same "unknown", but one thing I noticed was that it deleted the baseband too. The second time I flashed it, both came back. So short said, for those who have the same problem as me with unknown IMEI after flashing to Lineage 15.1:

May be you should also flash the bootmodem twice.

Once again, thanks for the help.
[Galaxy S 4 i9506 Android Development] msin84:
I just reflashed for the 6th time, now with PICO package...IT WORKS!!

Thanks a lot!!:good:
[Galaxy S 4 i9506 Android Development] elijo_otro:
Last night the phone spent 12% of battery without touching it.

I charged it up to 100% before go to bed, I unplugged it, and this morning it had 88% (the battery only has one month)

Can it be fixed in next releases? All the other thing works PERFECT
[Galaxy S 4 i9506 Android Development] BarryViper:
Losing 12% battery overnight for a new custom rom is decent enough. Give it a few more days, it will be even better.

I have tried other roms, I lost 40% or more overnight. So I'm sticking with LOS 15.1
[Galaxy S 4 i9506 Android Development] :
What helped me a lot was turning off GPS (or set it to device only). There a various tips how to save battery, but that one made the biggest difference for me.
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
Wifi drains more than mobile data of of battery, if you don't need it at night time, disable it.

I personally have wifi enabled at night, but i have the charger connected. When i go to work in the morning, i disable wifi, keep mobile data enabled, and i can listen to downloaded podcasts for 8 hours at work without completely draining the battery. Including browsing news sites at the breaks (I have two 15 minute breaks and one 30 minute break (lunch), and that using the old battery that came with the phone new). (Battery saving mode at 25% is recommended).

I agree. Gps at high accuracy drains a lot!
[Galaxy S 4 i9506 Android Development] jegogo99:
7600mah battery and problem out[emoji12]

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] elijo_otro:
sure, my GPS is always off
[Galaxy S 4 i9506 Android Development] Telone:
Will be fixed the delay to wake up phone?
[Galaxy S 4 i9506 Android Development] DonAndress:
Is it specific to LOS 15.1?

I'm still on 14.1 and I have very different observation. In my case wifi drains considerably less battery so whenever I can I switch to wifi :)
[Galaxy S 4 i9506 Android Development] Sub_Zero2:
I haven't actually measured it.

I forgot I've been having mobile data always enabled... I will try to disable it, to see what is using most....
[Galaxy S 4 i9506 Android Development] kyasu:
lineage-15.1-20180915-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).

Sync with the latest LineageOS source (September 2018 Security Patch).

Back to the I9506XXUDOJ2 ril/modem.

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] Hemuli:
Does this mean we should flash back to DOJ2 even if there were no issues with the newer DRA1?
[Galaxy S 4 i9506 Android Development] elijo_otro:
Confirmed. It's the coverage (not mobile data). Tonight he has been in airplane mode, and has spent 1%
[Galaxy S 4 i9506 Android Development] BarryViper:
Dirty flashed the new build without reverting to old bootmodem. Lost Magisk, had to reinstall it.

Vendor security patch is December 2016 while previous build was August 2017. I don't see any improvements in performance or snappier wake delays.

Don't understand the backwards, can anyone enlighten me?
[Galaxy S 4 i9506 Android Development] tester_95:
Hello

When I login to my Google account, or I open some website on my phone, I get information that I'm in USA. On LineageOS 14.1 I didn't have this problem. There is a way to fix it?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
So you are running the latest ROM build with the new bootloader & modem? instead of the previous one as reccommended.

That is a change to align with the old modem/bootloader.

That is a question I guess only [MENTION=4861355]kyasu[/MENTION] can answer, ie as to why he did it?

I am only guessing, but there is a setting in build.prop for "ro.product.locale" which may be set to "eng-US", with the US indicating you are in the USA. As for it not being an issue with 14.1, maybe it wasn't enforced/used to its fullest in 14.1. As I say, a guess.