yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] systemcrash:
Not sure whether it is - I understand changes were committed in the last few months which permit this to work. It would be like the old Nokia days again when this works :p

Edit: just tested on latest nightly, and powered down. Nothing. Also tested on stock 6.0.1 same model G900F, did nothing.

PS - how much disk space should I expect to commit to a pull of the G900 source tree to (be able to) submit patches?
[Samsung Galaxy S 5 Unified Development] fitittome:
The interesting bit, that I have missed out on, is here and onwards:- O thread Just way too much to keep up with and something else to subscribe to. :)

edit: Binderized
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Samsung has just turned 40 Galaxy S5 into a large Bitcoin mining machine

https://www.phonearena.com/news/Sam...s-into-a-large-Bitcoin-mining-machine_id99371
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Lots, LOL

Takes a LOT of space, took around a hundred gig on my drive if I remember correctly, and syncing the repo took forever
[Samsung Galaxy S 5 Unified Development] mobi74:
How I can discover what eat all my battery, my phone can do 10-12 hours without use or few hours if I use it, my system battery statistics (and also the app GSam Battery monitor) blame my stock kernel and the "system lineageOS, but how I can exactly know what in the kernel and what in the lineageOS eat all my battery power?

thanks
[Samsung Galaxy S 5 Unified Development] fbs:
you can check its usage in real time if you know how to "adb shell" to it

just type "toybox top"
[Samsung Galaxy S 5 Unified Development] SB4BBs:
So it's a kernel then? I thought it's a bug on Los.
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Did my own build the other day, worked great tried today and it kicked me out because of missing libraries that should have been extracted with the extract-files.sh script, seems these files aren't in the previous builds, any idea on that or do I just have to wait until the next build in order to extract the missing files? They don't exist in the previous 4 builds.

adb: error: remote object '/system/vendor/lib/soundfx/libqcbassboost.so' does not exist

adb: error: remote object '/system/vendor/lib/soundfx/libqcbassboost.so' does not exist

adb: error: remote object '/system/vendor/lib/soundfx/libqcreverb.so' does not exist

adb: error: remote object '/system/vendor/lib/soundfx/libqcreverb.so' does not exist

adb: error: remote object '/system/vendor/lib/soundfx/libqcvirt.so' does not exist

adb: error: remote object '/system/vendor/lib/soundfx/libqcvirt.so' does not exist
[Samsung Galaxy S 5 Unified Development] fitittome:
It might have something to do with this:-

klte-common: Use QC soundfx libs it looks like a work in progress. Maybe it will resolve itself after the next nightly.
[Samsung Galaxy S 5 Unified Development] Couchy:
[MENTION=5795145]javelinanddart[/MENTION] I got a newer SIM card (SIMOLW216R), and that seems to have gotten rid of the APN menu crash, but I still have massive instability with frequent random(?) phone crashes that revert my roaming setting to home only and the "Carrier settings" crash is still there. Any chance the new RIL will fix any of this?
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Libs

Thanks, guess I'll just have to pull those after I install today's build, I noticed that they are also going towards oss ril libs. I just installed my own source so I can perhaps help with tracking down bugs and errors, been a while since I've done a any coding but messing with android is as good a place as any to get my feet wet again.
[Samsung Galaxy S 5 Unified Development] fitittome:
You are brave! I have been thinking of taking the plunge but my programming/linux skills are limited. I am more windows web/sql orientated. I'm content to just sit back a try to learn how the whole ecosystem works. I've a new (second hand) Nexus heading my direction which may help debugging and testing things, I can't really afford to splash out on such a meaty linux box to do my own builds.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Flash stock and update your PRL and get it all set up there first, then flash Lineage again. That fixes a lot of provisioning issues on Sprint. The carrier settings crash cannot be fixed, unfortunately.
[Samsung Galaxy S 5 Unified Development] Couchy:
Welp, I'm an idiot - looks like I accidentally downloaded and installed klte instead of kltespr.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Either way, if you have time, flashing stock is always a good way to get provisioning set up properly on sprint to get stuff working on AOSP (especially since you just got a sim card)
[Samsung Galaxy S 5 Unified Development] fipsy:
Same here. :highfive:

What about a virtual machine in VMware for example? This is the perfect environment to play with Android. I've even got a marshmallow running on it. Works great!
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Lol, I'm exactly the opposite, Linux is my main os, have windows running in a virtual machine in virtualbox just so I have Odin in case I really screw up.

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

Lol, I don't know about that, haven't done any programming in ages, and most of mine was machine and assembly language, a little c++, just learning java. Figured android was as good a way as any to get back into it and I have the time on my hands so why not get back into it and maybe contribute a little.

---------- Post added at 12:19 PM ---------- Previous post was at 12:02 PM ----------

Since Lineage is moving to the OSS ril libraries I suppose it will open up the way for Oreo development for our devices
[Samsung Galaxy S 5 Unified Development] nx111:
From change "klte-common: Import libril from hardware/ril", my kltechnduo SG-9008w sim card can not work.

Here is some log message:

11-01 01:09:17.783 3757 3757 D RILD : RIL_Init argc = 3 clientId = 0
11-01 01:09:17.783 3757 3757 E RILD : First Ril
11-01 01:09:17.783 3757 3757 E RILD : LoadLogLevel: Log level is 3.
11-01 01:09:17.784 3757 3757 E RILD : RIL_Init: version(8)
11-01 01:09:17.784 3757 3757 D RILD : RIL_Init rilInit completed
11-01 01:09:17.784 3757 3757 I RILC : SIM_COUNT: 2
11-01 01:09:17.784 3757 3757 E RILC : RIL_register: RIL version 8
11-01 01:09:17.784 3757 3757 I RILC : s_registerCalled flag set, 1
11-01 01:09:17.784 3757 3757 I RILC : Start to listen RIL_SOCKET_1
11-01 01:09:17.784 3757 3757 I RILC : Start to listen RIL_SOCKET_2
11-01 01:09:17.784 3757 3757 E RILC : Failed to get socket rild2
11-01 01:09:20.697 329 556 E use-Rlog/RLOG-RIL-QMI: qmuxd: TX message on fd=20, to qmux_client_id=0x0, len=56
11-01 01:09:20.698 348 624 E RILD2 : QmiUnsolicitedCallback: msgId(81)
11-01 01:09:20.698 348 459 E RILD2 : ReceiveMessage: svc(NAS), msg(0x51:QMI_NAS_SIG_INFO_IND), indi(1), size(56), err(0)
11-01 01:09:20.698 348 459 E RILD2 : IsConsideredRegistered: Cache hit 1
11-01 01:09:20.698 348 459 E RILD2 : need sig info-1, need err rate-0
11-01 01:09:20.698 348 459 E RILD2 : Request for Signal Info
11-01 01:09:20.698 348 459 E RILD2 : SendMessage: svc(NAS), msg(0x4F:QMI_NAS_GET_SIG_INFO), sync(1), internal(1), size(0)
11-01 01:09:20.698 329 329 E use-Rlog/RLOG-RIL-QMI: qmuxd: RX 47 bytes on fd=20 from qmux_client_id=0x0
11-01 01:09:20.699 329 556 E use-Rlog/RLOG-RIL-QMI: qmuxd: TX message on fd=20, to qmux_client_id=0x0, len=63
11-01 01:09:20.699 348 459 E RILD2 : ReceiveMessage: svc(NAS), msg(0x4F:QMI_NAS_GET_SIG_INFO), indi(0), size(68), err(0)
11-01 01:09:20.699 348 459 E RILD2 : Result(0), Error(0)
11-01 01:09:20.699 348 459 E RILD2 : RSSI level = 0x0000 - LTE: 0, EVDO: 4, CDMA: 0, GSM: 0
11-01 01:09:20.699 348 459 E RILD2 : RSSI level = 0x0000 - LTE: 0, EVDO: 4, CDMA: 0, GSM: 0
11-01 01:09:20.699 348 459 E RILD2 : Signal Strength: [0, 21, 255, -1, -1, -1, -1, -1, -1, -1, -1, 2147483647, -1, 2147483647]
11-01 01:09:20.699 348 771 E RILD2 : GNET-MGR: evt(201)
11-01 01:09:20.699 348 771 E RILD2 : NET-MGR: EVENT_NETWORK_SIGNAL_STRENGTH
11-01 01:09:20.699 348 771 E RILD2 : OnNetworkSignalStrength() - mSignalBar: 0
11-01 01:09:20.699 348 771 E RILD2 : IsRegisteredNetworkType(): netType[1] feature[00] state[0]
11-01 01:09:20.699 348 771 E RILD2 : OnUnsolicitedResponse: unsolId: 1009
11-01 01:09:22.830 3844 3844 D RILD : **RIL Daemon Started**
11-01 01:09:22.830 3844 3844 D RILD : **RILd param count=1**
11-01 01:09:22.916 3844 3844 W RILD : RIL_SAP_Init not defined or exported in /system/vendor/lib/libsec-ril.06w.so: undefined symbol: RIL_SAP_Init
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Your own build?

Your own build? That change is implemented in the build coming out today, not in the 10/25 build
[Samsung Galaxy S 5 Unified Development] fipsy:
I think that we all have to pay very close attention to how things develop with mobile phone reception (telephony and SMS) in tomorrow's nightly. Working on the RIL seems to be a very difficult task because there are so many different networks, SIM cards and standards.
[Samsung Galaxy S 5 Unified Development] haggertk:
It looks like the G9006W libsec-ril didn't get the SAP capability in LL like the rest of them (guess a check of the other chinese variants would be in good order). I'm at work and don't have ready access to do development right now. Can you extract the files in the attached .zip and replace your current ones (either pushing to phone in /system/vendor/lib/ or including in vendor/samsung/kltechnduo/proprietary/vendor/lib/ and then building)? And of course, report back.

These are from G9006WZNU1CPJ2_G9006WCHU1CPJ2_CHU.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Can you get me a logcat -b radio from boot? And are both sims not working, or only the 2nd sim? From what I can tell it looks only like the 2nd sim isn't working.

Also, I wish you would've PM'ed me when I was asking for kltechnduo testers, as this could've been prevented, and this is exactly what I was afraid of.

Correct, although GSM folks should be fine.

I don't think the SAP thing is the problem here, none of the klte libsec-ril's have RIL_SAP_Init defined as far as I can tell.
[Samsung Galaxy S 5 Unified Development] haggertk:
Yeah, you are correct, scary error message that doesn't mean anything. Note to self: never comment on things that require dev env access to verify without having dev env access.
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
So are others also having issues getting LTE to work with the sprint G900P? With the sim card installed I get no data at all. If I remove the sim card 3g seems to work but LTE won't.

If I flash back to stock the LTE works with the sim card inserted.
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Newest Build

Did a build with all the changes listed on the lineage download site, so far so good with the OSS ril stuff (at least on the single sim gsm models) as far as I can tell right now, picks up the sim and I can make calls, don't know about incoming yet as very few people actually call me, and SMS works as it should.

OSS ril seems to be a good idea, with the work on that it might be able to go over to the lineage 15 work and solve the ril problems there.
[Samsung Galaxy S 5 Unified Development] nx111:
I build the lastest for kltechnduo, SIM card not work still.

Here is the log by run 'adb logcat -b radio'.

radio.log-20171101
[Samsung Galaxy S 5 Unified Development] Henki98:
In your opinion, which kernel is best between Tuned kernel and boeffla Venom kernel ?
[Samsung Galaxy S 5 Unified Development] bytes2bits:
I'm on CQD1 and a clean flash and I have no issues whatsoever. LTE is rock solid and it switches seamlessly to 3G and back when necessary. SMS in and out flawlessly.
[Samsung Galaxy S 5 Unified Development] fitittome:
Off topic here. Check with their respective forums.
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
Strange, how did you flash the modem? What order did you do everything in?

I flashed the stock CQD1 firmware, ran the PRL/Profile updates, LTE worked.

I then wiped everything and flashed 10/25

It didn't give me an error, it simply would not connect to data with the sim card inserted. If I remove the sim card it will connect to 3G.

I will try the whole process again, maybe something went sideways somewhere.

Did I read correctly that a new nightly is being released today? Might as well wait for that and see if it helps.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
It was quite a while ago so I'm not sure but I believe I did the same thing as you. I know I was on a stock sprint rom at some point and did the hands free activation too but I guess that has the same effect as updating profile and prl but I'm not certain. I'm on crDroid at this point because I like the extra tweaks but it should be the same as Lineage as far as LTE, etc.

Oh yeah, also... you should have your Preferred network type set to CDMA+LTE/EVDO. Anything else will give you odd problems. That can be found under Settings/More/Cellular networks/.
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
What nightly are you on? Seems like the latest versions have had some issues with data on sprint.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
I'm on the latest crDroid which was compiled from the 10/25 Lineage. The Sprint issues were definitely resolved as of 10/25. I was testing for javelinanddart just prior to 10/25 and he discovered something related to the Sprint radio issues.
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
I will admit, I have no idea what CRdroid is but it sounds like you are on 10/25 as well.

Strange, gonna try the whole process again and see what happens.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
It's definitely 10/25. I ran Lineage 10/25 first and everything was perfect on it and then the developer of crDroid kindly updated his base to 10/25 and I flashed that. It's all the same.
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
So is CRdroid another rom? based on lineage I suppose? ok, got it.

The way you worded it earlier it sounded like you did it months ago.
[Samsung Galaxy S 5 Unified Development] airidosas252:
11/01 download link is broken... Patiently waiting
[Samsung Galaxy S 5 Unified Development] fitittome:
You are as sad as me! https://www.reddit.com/r/LineageOS/comments/7a3epy/downloadlineageosorg/

The web gets updated before the mirrors, it's up now.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
Sorry, I was referring to the baseband update. That was many months ago.
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
Gotya ;)

---------- Post added at 08:38 AM ---------- Previous post was at 08:28 AM ----------

Where is the link to the 11/01? I didn't see it listed on https://download.lineageos.org/kltespr, does it show up someplace else first? Got the stock firmware all installed and working happily with LTE and ready for a flash to lineage.
[Samsung Galaxy S 5 Unified Development] haggertk:
kltespr is dead, kltedv is your new build. This was mentioned here in the last week.
[Samsung Galaxy S 5 Unified Development] fitittome:
Just wanted to report back that the klte (G900F) install of the NOV01 Nightly was flawless and the phone works great. :)
[Samsung Galaxy S 5 Unified Development] KazuDante:
so as a user regarding the ril changes should we be looking for changes in the experience we have regarding the ril , or is it more of a under-the-hood change that users would not notice a change or improvement?

i mean from what i read of the Lin15 dev thread it's a stepping stone to get ril working on Lin15 but i dont really understand all of this so i kind of was expecting like an improvement . (of course this is an improvement but yea....ima shut-up now...lolz)
[Samsung Galaxy S 5 Unified Development] fitittome:
The dev was saying a few pages back that GSM will be fine but keep an eye on the others.
[Samsung Galaxy S 5 Unified Development] systemcrash:
Can also confirm. Works well. See below. G900FFXXS1CQA3 MODEM

Potential RIL bug/hiccup:

Possibly as a result of network preference, on start-up, my phone first finds a network, then "emergency calls only" as no network is available for several seconds, then again finds a network - and then remains connected. This is consistent across reboots. This did not happen on previous nightlies. I have:

LTE/TDSCDMA/WCDMA (my roaming SIM does not have access to any LTE nets locally, I believe)

Attached logcat.

Edit: Change network preference to TDSCDMA/WCDMA and my connection does not drop after first connection. See attached profile images.

Edit: my local LTE compatible SIM does not exhibit the above behaviour. It started briefly no connection, LTE, then stays that way. Successive connections are almost immediate.

(Long time) Bug: [MENTION=2693412]haggertk[/MENTION] [MENTION=5795145]javelinanddart[/MENTION]

Go to Developer Options settings menu

Find "Select USB Configuration" option

Does not matter what you choose, always reverts to "Charging". Get phone, cable disconnected. Choose MTP. "Select USB Configuration" option shows "Charging". Connect cable. It's actually MTP. AFT opens on cable connect. Now disconnect. Reverts to "Charging". Change nothing. Reconnect cable. Still Charging. AFT does not open.

Cosmetic:

My /proc/last_kmsg file is filled with:

...

[ 73.572816] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.605426] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.639462] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.671852] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.706082] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.738627] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.772929] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.805310] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.839589] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.872021] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.906194] samsung_dsi_panel_event_handler : unknown event (9)

[ 73.938670] samsung_dsi_panel_event_handler : unknown event (9)

[ 74.193223] samsung_dsi_panel_event_handler : unknown event (7)
[Samsung Galaxy S 5 Unified Development] Texas_Ace:
G900P, just got done flashing 11/01 and LTE still won't work for some reason. Works fine while on the stock rom but not once on lineage. Now it won't even work with 3G, even with a twrp nandroid restore to the setup that used to work with 3G. So something is going on with my phone.

I am going to flash back to 10/25 and try that and might even try an older version like 8/30 to see what it does.

At this point I just want the 3G back. I can live without LTE but I need some kind of connection.

---------- Post added at 12:35 PM ---------- Previous post was at 11:42 AM ----------

After redoing everything from the stock flash to lineage 11/01 again it is now working as it should. Just one of those things I suppose.
[Samsung Galaxy S 5 Unified Development] revjamescarver:
G900T works fine

Yeah, my T-Mobile S5 is working fine with the oss ril libraries, hooked it up to my Linux box and did a adb logcat -b radio right when it was booting up just to see and didn't see any errors or strange s*** cropping up, since I only have the one S5 at the moment I can only really speak of my own specific device, but it should be working fine on single sim gsm varieties of the S5.
[Samsung Galaxy S 5 Unified Development] Nico1544:
Did someone expect long set up time after ota on bootanimation?
[Samsung Galaxy S 5 Unified Development] Immortal0907:
First boot after OTA can be longer. If thats what are you asking...
[Samsung Galaxy S 5 Unified Development] Nico1544:
Yeah i know but its normal that takes the first boot over 20 minutes?
[Samsung Galaxy S 5 Unified Development] cdrivex4:
Yeah, not very comforting that.

On 900fd it's no longer picking up the single installed sim, and therefore not connecting to telco.. Annoying..

rolling back to the safety of 1025.

will try and post bug report file after I've sanitized it, though at 25mb most text editors on android have a hard time with it... any recommendations?..
[Samsung Galaxy S 5 Unified Development] Immortal0907:
smells like a bootloop... something went wrong.. try wipeing cache and dalvik cache in twrp if that doesnt help idk maybe flash previous build without wipeing anything...
[Samsung Galaxy S 5 Unified Development] javelinanddart:
RIL stuff

So dual sim stuff is all broken. I think I found out why. This week's build will be pulled, and it'll run again next week, but if and only if I can get some confirmation here.

klteduos: http://downloads.codefi.re/jdcteam/...-14.1-20171101_200308-UNOFFICIAL-klteduos.zip

kltechnduo: http://downloads.codefi.re/jdcteam/...4.1-20171101_221013-UNOFFICIAL-kltechnduo.zip
[MENTION=5510581]nx111[/MENTION] ^

If you're running an unofficial build, you can flash this right over it. Otherwise, you need to wipe fully and then flash my build.

Calls/Sms/Data on both sims are what I would like tested.

If I don't know that this stuff is working, I will have to discontinue support for these models, as I do not own them, and cannot support them without testers.

On a related note: [MENTION=8098052]Couchy[/MENTION] after the RIL updates in this build and a new sim card, is stuff working right for you?
[Samsung Galaxy S 5 Unified Development] eurohunter:
to all G900P users that are having issues, can you try to dirty flash the rom once more? I wiped the phone and installed 11/1 build, and I was having issues with GSM-CDMA bouncing, as well as sometimes forced LTE not working at all, losing service entirely. After dirty flashing the rom, it seems the GSM-CDMA bouncing goes away. I still encountered occasionally this issue of LTE not connecting at all, making the phone lose service entirely until you change it to 3g. Same thing happened when i wiped and installed crdroid 10/26 and LOS 10/25.

P.S. is it my bad installation, or LineageOS does not allow us to connect to wifi during initial setup? I wanted to restore my apps and didnt have data, but it said I wasnt connected to the internet, even though it never prompted me to connect to a wifi network. For what is worth, crdroid allowed me to connect to wifi before restoring apps, but lineage os didn't prompt me for wifi twice.
[Samsung Galaxy S 5 Unified Development] Couchy:
I got a good signal after doing carrier/PRL updates on stock with the new SIM. I just installed the latest build, and no problems to report so far - LTE works, as do incoming and outgoing calls. :good:
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Testers

Hope you can find some testers for those two devices, something is definitely wrong with ril on those two, I don't know about any of the other variants of the S5, or is the problem just confined to the dual sim devices? I know on my G900T the oss ril is working fine, did several logcats using adb, when booting and while making calls and doing SMS, and didn't see any errors or strange s***, you definitely need testers so you can get to the bottom of it.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Just dual sim as far as I can tell, I think I found why: there were some rogue build flags that weren't relevant when we were using a prebuilt libril/rild, but now that we use a source built one, those are actually applied, which breaks rild, I think. These flags were present on only on the dual sim devices.

As for find testers, I will shed a tear to drop variants, but if I cannot get testers to help, I will have no other option.
[Samsung Galaxy S 5 Unified Development] Nico1544:
have tried both but boot up take again 20+ minutes so i did clean install with 17/11/1 build i think it was because the art optimation module from magisk
[Samsung Galaxy S 5 Unified Development] javelinanddart:
The idea of restricted topics of discussion in official LineageOS discussion threads has been well fleshed out before. Please talk about magisk elsewhere, and don't report bugs with magisk installed.

For reference: https://www.reddit.com/r/LineageOS/about/rules/ <- good idea of rules for discussion. (Don't mind "do not report bug reports", but don't report bugs with any unsupported modifications)