yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] najdv:
It's nobody's fault? even with crdroid it's the same thing. So maybe your contacts do not make you notice in any case me it's commercial if I was away from the phone. And more why with lollipop the sound is very correct? instead of saying that I criticize the rom. The goal is to make our return, no? in this case more criticism and to tell you from other people on other forums say the same thing he recommends to increase the value of the internal files of the phone but likewise it does not change anything. So with official functional and custom not ROM for my parts in any case happy for you if it works
[Galaxy S 4 i9506 Android Development] :
Did you search for a solution on Google? There are a couple of suggestions you could try. I would test it myself, but as I mentioned I don't have this bug.
[Galaxy S 4 i9506 Android Development] najdv:
Yes of course I have already searched on google before posting here. What I found is that you have to change all rx 1 to rx7 and set to 90 as a value for others it works for other no. I may get the mixer file in the lollipop 5.0.1 etc folder and transfer it to the 7.1.2 once installed maybe it will work
[Galaxy S 4 i9506 Android Development] najdv:
I check the difference between the two files mixer_path.xml lollipop 5.0.1 and 7.1.2. The code is the same so change the values I think it is not used for nothing it will not make the original sound
[Galaxy S 4 i9506 Android Development] DiamondJohn:
It could still be your phone; but simply less likely. Different versions of Android can and may use your hardware differently. I previously had a phone that became unuseable with ZRam turned on; the lag was unbelievable. There were>100 other users that found ZRam helped them, it appeared to be only me. Manufacturers may change component sources during a production run, and this could be a possible source for the same device behaving differently for different users. On another device my GPS was flakey, but only to me and a very small number of other users, not everyone. On stock, previous and the next iteration of Android, the GPS worked flawlessly. I attribute it my physical device.

Have you taken a logcat? I personally like the following steps:

1. Connect to phone via ADB

2. Clear your current log

logcat -c;

3. Start the app and duplicate the issue

4. Get a fresh logcat

logcat -d > /sdcard/$(date +"%Y%m%d%H%M%S")_logcat.log;

5. READ the logcat and/or post/attach it to the thread in question

Other things to investigate/try

1. Do a FULLY CLEAN install.By this I mean clearing/reformatting ALL partitions (including the internal SDCard) and re-install LOS 15.1 (crDroid will simply add outside factors). Do not install anything apart from the ROM, GApps and WhatsApp; nothing else.

2.Try step 1 with a change to the DATA and CACHE partition formats. Try F2FS on data and cache (or vice versa). I personally use F2FS instead of EXT4 on these partitions, but I realise these may induce issues otherwise not present in a ROM. On a previous device (not either one I mentioned earlier), any Nougat ROMs would not run, unless the data partition was explicitly formatted as F2FS and not EXT4.

Test 1 would also be a good opportunity to take a logcat since the device should be relatively "clean"

You also appear confused by the reaction you generated to your post identifying your issue. I think it is simply a wording thing. If you had posed the post as a question if anyone else experienced the issue and how they are getting around it, I think there would of been less issues with your post. just my thoughts. Also, you said you searched the web and found others had a similar issue, which to me implies there is something not specific to only this ROM, and it may be an issue with the AOSP source shared between devices. I personally would put my money on a change to the device specific source, but with others not having your issue, numbers wise its not looking good for your belief its the ROM (see my GPS issue above).
[Galaxy S 4 i9506 Android Development] najdv:
good evening I sent you an email did you receive it?
[Galaxy S 4 i9506 Android Development] :
CM/LOS is known to have issues with this. The CM14.1 builds by kyasu used to have this bug (reported by many people) but he has fixed it a long time ago. Since this bug was never reported before for this rom I assumed that it's either not present on Oreo anymore or the fix is still implemented in the device tree for this rom.

Edit: I found the commit: https://github.com/kyasu/android_de...mmit/03160674480d8d5e598eced0a5b977ace0e34a9b
[Galaxy S 4 i9506 Android Development] DiamondJohn:
No email, but unless its very specific to me, then I would suggest to post it publicly in a thread, in case it would help someone else.
[Galaxy S 4 i9506 Android Development] najdv:
Hello, thank you for your answer. I already tested the patch that you bring but it does not matter for my case the output of the microphone is mediocre by cons when I record a video the sound is beautiful
[Galaxy S 4 i9506 Android Development] najdv:
Hello, thank you for your answer. No, there is nothing personal it was just to ask you this:

You told me to format the phone completely as well as SD card, so if I understand correctly I formate all this:

dalvik / art cache

system

data

internal storage

cache

micro sd card

usb storage

The micro sd card is not an external sd card? because this is where I have the rom for installation after formatting and converting to F2FS

ps: I joined the log on my post (While running the log I use whatsapp to leave a voice message can be that if there is a bug it will appear in the log but I am unable to read it.)
[Galaxy S 4 i9506 Android Development] plmq:
Thanks you for your continues support of S4-lteA!!

I clean-flashed 20180414 build .

I'm having GPS locking problem . i.e., Gps test shows "NO Fix" (although is it shows 20 Sat "in view", 6 "in use").

[IMG="No-Fix, screenshot"]https://imgur.com/a/obxf7c1[/IMG]

Also each time when powering on, it cycles boot logo 2 times , only the third time it succeeds booting ....

Earlier I was using LOS 14.1, all was running smooth....

Any idea ?

Using LOS on my samsung gt-i9506
[Galaxy S 4 i9506 Android Development] :
I have exactly the same problem with GPS. However Google maps still works so it is not too bad (because I won't get lost ;)), but my tracking app for running does not work (tried more than one app).
[Galaxy S 4 i9506 Android Development] marcinadd:
Is Google Pay fixed on latest update? Maybe some changes?
[Galaxy S 4 i9506 Android Development] lospuegos:
I'm wondering if they ever announce an official rom for this device again ...
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I am running my own RR build of 14.1 as my daily. However, I have tested my own build of Oreo crDroid (which uses the device tree from [MENTION=4861355]kyasu[/MENTION]) and actually found the GPS to have a more accurate reading (ie <5m) than my daily. What I have noticed is that GPS reception on my daily (14.1) is very sensitive to outside factors eg overcast/cloud cover or, I don't know, maybe Space weather (NB: the suns output could potentially knock out GPS satellites and it does cause radio signal interference, and many warn of electricity transmission possibilities).

That's weird, at least to me, I normally use Waze and/or Here and have found that their ability to get a fix is much weaker than GPS test apps (such as used above, I also use GNSS as it is clearer on which is Glonass and which is GPS). Sometimes I will actually switch over to the GPS test app to get a fix, which is then held/used by the nav software.
[Galaxy S 4 i9506 Android Development] ranjan838:
bugs in my device

Just installed in my s4 i9506. These are the bugs I found . however,It may be problem in my device only.

1. AM and PM is not displayed in the status bar.

2. Notification light is not allowed for modification in the settings menu for different apps.

3 Infrared remote does not work.
[Galaxy S 4 i9506 Android Development] supachris:
Thank you. I did also clean up, it works now better, but there are still BT connection drops sometimes. I will see if it's going better in future builds.
[Galaxy S 4 i9506 Android Development] kyasu:
lineage-15.1-20180506-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).

Sync with the latest LineageOS source.

Video recording is now working.

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] supachris:
Thank you!

Are there any changes to AGPS? The A GPS seems to be broken again. Regardless of the NTP server settings in the gps.conf the fix takes extremely long...2 minutes ore more.
[Galaxy S 4 i9506 Android Development] TheBlackMini:
Having an issue flashing this ROM...

TWRP 3.2.1-1 flashed by Odin on a stock phone (no root, no prior custom ROM)

TWRP keeps reporting that the zip is corrupt

I've tried

lineage-15.1-20180506-UNOFFICIAL-ks01ltexx

lineage-15.1-20180414-UNOFFICIAL-ks01ltexx

lineage-14.1-20180316-UNOFFICIAL-ks01ltexx

crDroidAndroid-8.1-20180430-ks01ltexx-v4.2-DiamondJohnDroid

any hints as to how to get this going?
[Galaxy S 4 i9506 Android Development] supachris:
Hm, it seems like the xtra servers now have to be stated in gps.conf again. Strange. With xtra servers here the GPS fixes within some seconds.
[Galaxy S 4 i9506 Android Development] jegogo99:
You could try with oficial TWRP 3.2.1.0

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] :
Would you mind sharing your gps.conf for testing purposes?
[Galaxy S 4 i9506 Android Development] supachris:
No Problem! Please share your test results also.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Comparing to the source (and therefore what I would expect to be found from flashing the ROM) at https://github.com/LineageOS/androi...974-common/blob/lineage-15.1/gps/etc/gps.conf You have done a few steps more than you suggest. Apart from supplying NTP_SERVER(s) specific to your region (always a good thing in my eyes), AND un-commenting the XTRA_SERVERS, you also have changed the following:

[strike]CAPABILITIES=0x3[COLOR="Red"]7[/COLOR][/strike]
CAPABILITIES=0x31

[strike][COLOR="red"]# [/COLOR]ACCURACY_THRES=5000[/strike]
ACCURACY_THRES=2000

[strike][COLOR="Red"]#[/color]SUPL_HOST=supl.google.com
[COLOR="Red"]#[/color]SUPL_PORT=7275[/strike]
SUPL_HOST=supl.google.com
SUPL_PORT=7275

Did you make each change incrementally to see which made the difference? or did you make the changes in a single pass? and therefore not really know which change made the fix, fix it?;)

I *think* the ACCURACY_THRES is in meters, so a value of 2000 (ie 2Km / > 1 mile) is a VERY inaccurate position to accept, and therefore will provide a very quick "fix".
[Galaxy S 4 i9506 Android Development] supachris:
OK, let me explain.

The accuracy threshold is only valid if the intermediate position is enabled.

I have always disabled this.

The 0x37 capabilities came from LOS14.1 releases, I don't know why this was changed.

Until today I had only the 0x37 and the NTP servers changed in comparison to the conf from sources.

Today, I first copied the my conf file and rebooted as usual after update. No fix.

Then I uncommented the SUPL servers, reboot. No fix.

After this, I uncommented the Xtra servers, reboot: Fix ater few seconds. Accuracy less then 10 meters!

For comparison, installed the today's update again, to have the conf from sources, no fix.

Copied the above conf, reboot. Fix.

Strange.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I dont think that is the case. To further support this, an accuracy threshold of 0 turns intermediate positioning on. So any value > 0 (unless it is explicitly set) means intermediate position is not enabled. Yet, you have a value for this setting. Try commenting out this setting, and I think you may notice the change even though you have immediate positioning off.

I also have been meaning to play with this value, and your extreme value inspired me to finally give it a go. So I set my value to 20 (ie 20 meters, where I normally get an accuracy of 15 down to 9), What surprised me was that it locked (inside with curtains drawn) pretty quickly, but more surprisingly it got down to 3m accuracy, inside :eek:. I can only guess that it was triangulating better with more satellites of lower accuracy than it previously did with less satellites of higher accuracy. I am also getting a fix in a room (ie inside) that I would previously very rarely get a fix in.

It is definitely acting differently, even though immediate positioning is still off. My understanding is the immediate positioning will mean that a location based solely off network towers (ie not GPS fix) will be reported as a GPS fix, until a true GPS fix is attained.

As for why the changes you saw are in the source, my guess is that the changes were Kanged from another device that may have slightly different hardware.
[Galaxy S 4 i9506 Android Development] supachris:
Hm, maybe, the accuracy threshold is related to wifi/cell based location assist. I have turned this off, as I don't want to be tracked by Google every step.

So I changed the value also down to 20 and get nearly the same result here for fixing time and accuracy.

20 seconds in house with 6 usable sats and about 10 seconds outside with more sats.

The 0x37 AFAIR were the source settings in 14.1 for this device.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I am pretty sure its not only WiFi/cell as GPS satellites also have an accuracy. Try setting it to 1 and I would guess you will have a very hard time to get a fix. A Wiper fix I think will almost always precede the GPS fix. I think. I haven't actually tried turning it off completely to see if the Network location actually can be totally disabled; without going to Airplane mode. I would not be too surprised if it was still working.

Guess again, as one of the differences you have between the ROM and your modded one is the following

SUPL_HOST=supl.google.com
SUPL_PORT=7275

which explicitly connects to google server with location information. If you search online you will find lots of information regarding this setting and google being aware of your position. Re-comment these settings if you truly want to reduce googles awareness on you. There are other providers you may be able to use, but from memory they have been mostly device specific such as nokia and sony or network/carrier dependent.

As you have made a few other changes, they may have a greater effect on your fix time than this setting. ie you are actually getting a fix with less than 20m accuracy. A way to check is to go back to the original conf file and only make this one change. This is why asked if you made the change incrementally or in a batch. Trying to work out what is happening when making multiple changes is not the way to diagnose what is happening, I made this one change independently of anything else, and it has made a big difference. I also remember playing with this figure a few years back (leaving it at 5000m) and it did exactly what it said on the tin. Although my first fix was better than 5000m, it was still over 50m, but super fast.

I am actually running 14.1 RR as my daily, and I too have this same setting. I think I once searched the ROM source for where the GPS settings are read in, but didn't find it, so I am guessing it would be part of the device/Samsung supplied blobs/firmware, which would imply you would be correct in using this setting even in 8.1. IF i am correct, even better would be to check the original stock values.
[Galaxy S 4 i9506 Android Development] Siggi0904:
Hello,

I try to flash my phone from Lineageos 14.1 to 15.1 in TWRP 3.1.1.0. I cleaned cache, dalvik and data in TWRP.

But I get error 7. In E3004 Line is written that the found device is empty.

What should I do? Pease help me.
[Galaxy S 4 i9506 Android Development] doirat:
Almost perfect

Hi everybody,

I've installed this rom successfully.

The first time, i've got a bootloop after restarting. This was resolved by going back in TWRP and doing a wipe including the system partition before reinstalling the rom.

I confirm that everything works fine. Indeed, You can get good video with the apps Footej Cam.

Something strange, data connection was only in 3G; but you can easily change that in the option to go into 4G.

I didn't install google apps. I don't want it. I use instead Fdroid (which allows me to install YALP Apps to have apk from play store) and Aptoide. I notice that without google apps you gain almost 1.5 to 2 time batteries!!

However in Android 8, there isn't anymore option to install apk from unknown source. Default File manager do nothing when you click on apk files!

Thus, I activate the developper options. Then in developper option, I have activated "Terminal". Then I've launched terminal and do the following command :

>> su (go into super user, need to install su addon)
>> cd mnt/sdcard/Download (where aptoide and fdroid apk have been downloaded with the android browser)
>> pm install <name of your apk>.apk

Go back to the main menu android, into your apps; then launch Aptoide or Fdroid and allow them to install apk when android asks you.

The only thing missing is the visual voice mail in the phone app which has disappeared compared to lineage os 13 that I used before (but was horribly buggy with bluetooth).

Big thanks for your Job kyasu!!
[Galaxy S 4 i9506 Android Development] wkwk:
Pin works fine, I was able to add card to android pay. However I added the card after Magisk root.
[Galaxy S 4 i9506 Android Development] Mickeyvdb:
Also on my device the pin setting just works fine. No issues.

Using it on ext4 and Magisk.
[Galaxy S 4 i9506 Android Development] Clebinhocuzau:
i get a error

I tried to install, but i get a error

Error 7
[Galaxy S 4 i9506 Android Development] zardak:
Nice to hear, enjoy your error. Maybe next time give more details.

Regards.
[Galaxy S 4 i9506 Android Development] Clebinhocuzau:
I can't send a screenshot, cause i'm create my account today lol

But is a "error 7" in TWRP
[Galaxy S 4 i9506 Android Development] zardak:
Great ROM [MENTION=4861355]kyasu[/MENTION]. The main disadvantage is the high battery drain and that the WiFi turns itself off when the phone is asleep for a while. I didn't execute the ADB command
[Galaxy S 4 i9506 Android Development] marcinadd:
Update TWRP to newest version and re-download rom (maybe download file is corrupted).
[Galaxy S 4 i9506 Android Development] Mickeyvdb:
No battery drain here.

I can get two days of use with around 1 hour of usage per day.

In standby around 1% drop per hour.

Also no wifi drop.
[Galaxy S 4 i9506 Android Development] Clebinhocuzau:
I managed to install the rom, the problem was the outdated TWRP ?
[Galaxy S 4 i9506 Android Development] DrAcula04:
I've used the device as a alarm clock. The batterydrain with all wireless conections disabled has rised at a noticeable amount on the new version. (On 14.1It lost around 2-3%, now up to 10% overnight.)

[Edit]: It seems like it is one the same level as Nougat now. Maybe the the battery stats are now calibrated.
[Galaxy S 4 i9506 Android Development] karbon1992:
thank you Kyasu for supporting s4 ! :)

But i found one bug. Everything works except charging. It very very slow. Also battery is losing % while charging, when I'm using phone :(

Update

I've changed cable and everything seems to work fine.
[Galaxy S 4 i9506 Android Development] zardak:
The high battery drain seems disappeared now as I can do 2h30 SOT in 50%, but the wifi keeps turning itself OFF when the phone is asleep for a while
[Galaxy S 4 i9506 Android Development] wkwk:
I had the same problem some times, turns out my wifi policy was set to 1. I've changed it to 2.

ADB shell instructions are as provided by kyasu in first post.
[Galaxy S 4 i9506 Android Development] :
I did not change any settings via adb and I lose literally 0% over night (with flight mode enabled of course, so wifi policy doesn't matter). The great battery life is not too surprising tho, because Android O is supposed to be very restrictive regarding background activities in standby mode.
[Galaxy S 4 i9506 Android Development] sura25:
Info

I have one bug, everything work good, camera, bluetooth, wifi etc.

But if ill try set lockscreen PIN, symbol i cant save or mostly i got freezed screen, wibration in back and menu button work. But that nothing do with smartphone. Screen is freezed on that screen. Not woerrk home, power off, cant turn off and do anything without remove battery and restart phone... but after restart we have set lock screen symbol/pin and if we insert password worng we see error, worng password/symbol, but if we insert it good, we have again freezed phone... and i cant set any lockscreen :/ For "repair" that i need to again reset > format system etc and renew install that rom.

I have first time bug with install that rom i have error 7, so i deleted in meta-inf>google>android>script-updater > first line with model prefer for remove that but (i have samsung s4 i9506 lte-a [earlier with lineage 13.1]).

More bugs i dont saw. I had downloaded last version of lineage 15.1 from 11.02.2018.

And for now lineage os 14 (with android nougat 7) battery works better i think. I had marshmallow and looks simmilar when phone is used. When is locked has better batteryuseage in background (freezes apps like Greenify app) so when u let smartphone w8 all night i lose now max 1% of battery (not 10-13% like in marshmallow) when i go sleep.

Sorry for my english. Maybe only i have that bug.
[Galaxy S 4 i9506 Android Development] marcinadd:
If you stucked in freezed screen after reboot check my post #11 to fix. Next time if you set lock screen you must wait some time. Don't reboot phone. Give it a second :D.

It's better to update TWRP. On other phone flashing new rom with old recovery make rom buggy. Do a clean install with newest version of TWRP :D.
[Galaxy S 4 i9506 Android Development] sura25:
Ok, thanks for now everything is working fine :)
[Galaxy S 4 i9506 Android Development] elijo_otro:
[MENTION=4861355]kyasu[/MENTION] you are TOP! thanks!
[Galaxy S 4 i9506 Android Development] kyasu:
lineage-15.1-20180218-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).

Sync with the latest LineageOS source.

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] DiamondJohn:
[MENTION=4861355]kyasu[/MENTION] I am trying to build RR Oreo using your device/kernel & vendor trees and I had an issue with the file https://github.com/kyasu/android_device_samsung_ks01ltexx/blob/lineage-15.1/rootdir/Android.mk

The destination paths cause errors in my last_kmsg

Should this be: https://www.hastebin.com/foratihuru.makefile ?
[Galaxy S 4 i9506 Android Development] :
After a few days of testing I can say that your gps.conf improved the situation for me. I have no clue of the values and all the other stuff in this file, so I can't tell which change made the difference and what other changes might be superflous or even impair the GPS performance (as brought up to the discussion by [MENTION=5417899]DiamondJohn[/MENTION]). Also for the first time GPS test apps work for me. As I have mentioned before I was not able to get a fix with the default gps.conf with theses apps, even though plenty of sats were reported to be in use ( for example 24 in view, 6 in use - but still no fixed location). But this works now and also Google maps works fine so your gps.conf is for sure a step in the right direction. Thx for that!
[Galaxy S 4 i9506 Android Development] jegogo99:
in which folder is that gps.conf file?

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] :
/system/etc
[Galaxy S 4 i9506 Android Development] jegogo99:
Now i get signal in a few seconds. Great!!

Enviado desde mi GT-I9506 mediante Tapatalk