yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] delj:
which version would you recommend?

Thank you s0be and arco86 for putting this out. I'm still using the S4 Mini and I really appreciate this build being available.

I just installed the 20150815 version before realizing that there were newer versions available. I realize you have probably moved on and may not do any more development on this ROM, but would you recommend the most recent (20151205) version, or which do you consider the closest to being "OFFICIAL"?
[Galaxy S 4 Mini Original Android Development] RyanTzor:
Updating this rom still?

Does anyone know if development on this is still ongoing? I would love to contribute because i love my phone i just got and I thought there was a bunch of support for it, but it looks like the spring version of this phone is extremely unsupported. Thanks !
[Galaxy S 4 Mini Original Android Development] glkanth77:
Guys we r trying to build OCTOS 6.0 for SPH-L520 we r looking for testers if any one interested pls pm [MENTION=6614989]jason972000[/MENTION]
[Galaxy S 4 Mini Original Android Development] RyanTzor:
I really wish I still had this phone but it ended up not working on sprints network when I bought it. Moved on :/ best of luck OctOS you guys rock!:cowboy:
[Galaxy S 4 Mini Original Android Development] teknoweanie:
Cool! If it doesn't take a whole lot I could help a bit. :) I recently messed up my right hand so not a lot to do except play with my phone. Been playing with a s3 but I have a l520 as well as a few others. Even if I can't help im happy to see this. *Hugs cat*
[Galaxy S 4 Mini Original Android Development] Michael24884:
Anyone know where I can find the kernel for this device?
[Galaxy S 4 Mini Original Android Development] Michael24884:
Nvm I found it, although I'm pretty sure the S4 mini Sprint community is dead. I'll still be making the Lineage Marshmallow Rom
[Galaxy S 4 Mini Original Android Development] jason972000:
I'll be interested in how the Sprint variant goes for you. I tried to get one going on octos but the tester was finding issues I couldn't explain or fix. But I think he was on a "pay as you go" third party mobile service plan which could have been part of the problem. I could only get the serranolteusc build to boot on it for marshmallow. Something strange with Sprints blobs.
[Galaxy S 4 Mini Original Android Development] Michael24884:
So far the ROM is still compiling it's been at least 12 hours, but there hasn't been any errors yet. Is it normal to take this long? It'd make sense anyways as I only have a 1.89 GB ram with a 4 GB swap

[MENTION=6614989]jason972000[/MENTION] btw is OctoOs an AOSP? If so would you have a copy of it. I know it's easier to compile MIUI wait an AOSP base
[Galaxy S 4 Mini Original Android Development] jason972000:
Octos has been cm/lineage based.

12 hours is really a long time but depends on your processors and ram. I would think you would want at least 4gb ram and more than 1 cpu to even try a compile. I've been fine using 8gb ram and a quad core which takes just over 2 hours on first time compile. Once ccache is populated, additional builds take about 1.5 hours.
[Galaxy S 4 Mini Original Android Development] Michael24884:
Quick newb question: is the kernel responsible for soft-keys, sound,charging port?
[Galaxy S 4 Mini Original Android Development] Michael24884:
Update: build stopped, apparently there are lots of errors in the kernel, most of them which are unallowed
[Galaxy S 4 Mini Original Android Development] umuturunc:
That build time. That's cool. Do you have ssd? Which distribution you are using?
[Galaxy S 4 Mini Original Android Development] Michael24884:
BBQ Linux which is made specifically for compiling

Decided to use LineageOs kernel tree, as the CyanogenMod kernel had to many errors. I'll report the results later

Edit: woops thought u were quoting me
[Galaxy S 4 Mini Original Android Development] Michael24884:
I'm confused, I built the LineageOs 13 , but flashing it I can't get past the Samsung splash screen, instead it starts to colorize the screen
[Galaxy S 4 Mini Original Android Development] Michael24884:
I attached a recovery log, and I'm certain that the problem lies with loading the /misc. I however can't find a solution to this
[Galaxy S 4 Mini Original Android Development] droidputz:
can't flash recovery

Hey all I picked up one of these phones stupid cheap from the egg recently with no intention of ever activating - just wanted to flash a ROM and use it for a media player. I figured the S4 mini would have plenty of development but this variant seems scant. I made the newb mistake of connecting the phone to wifi and letting it update when I turned it on - now I am able to root the phone and verify with root checker but I am unable to flash the recovery linked in this thread - keeps failing with unsupported_dev_type or something to that effect.

Follow up research indicates I may have triggered Knox, but my software version doesn't look like what others had posted for Knox-enabled or whatever you would call it. I've flashed custom ROMs to several devices thanks to the efforts of people smarter than I here at XDA but still have a pretty tenuous grasp on the whole process and don't know where to go from here. Can someone nudge me in the right direction? Do I need to use Odin to flash a downlevel stock ROM and start over not letting it update before flashing custom ROM? If so can someone point me toward the right file for that - seems like I could easily brick my new phone if I choose a file not specific to this variant? Any help would be most appreciated.
[Galaxy S 4 Mini Original Android Development] Michael24884:
Use Odin to flash the Recovery, or use Odin to flash the stock rom
[Galaxy S 4 Mini Original Android Development] Michael24884:
hey guys check this link out: https://xdaforums.com/galaxy-s4-mini/orig-development/rom-t3694246
[Galaxy S 4 Mini Original Android Development] Lowcho98:
Help help help help help help

I have sph l520 with linage os 16 I want to go back to factory settings I have twrp it says unable to mount preload any files on here for stock rom ? Current has to many bugs and no picture messages help please

lowcho937@gmail.com
[Galaxy S 4 Mini Original Android Development] s0be:
Sorry I didn't reply sooner. The config you sent over worked with the addition of:

CONFIG_SEC_DEBUG=y
CONFIG_SEC_DEBUG_SCHED_LOG=y
CONFIG_SEC_DEBUG_SUBSYS=y

Along with the stock msm8930_serrano_spr_defconfig.

Fixups:

include/linux/i2c/cypress_touchkey.h systemrev -> int to unsigned int

arch/arm/mach-msm/Makefile -> use board-8930-input-tkey-serrano.c instead of board-8930-input-tkey.c

So I wouldn't be too worried about merging kernel changes.

On the CDMA side, I'm having a heck of a time figuring out which ril files and whatnot I need for this blasted device. I've tried the ril from propietary/blobs/cdma/ in the jftle tree, but that didn't work either. As it stands, using the ril stuff from serranoltexx gets 1x/LTE working, but it doesn't seem to like calls/etc.
[Galaxy S 4 Mini Original Android Development] arco68:
Do you have a copy of build.prop from stock rom?
[Galaxy S 4 Mini Original Android Development] s0be:
Attached.
[Galaxy S 4 Mini Original Android Development] arco68:
Sync your sources, s0be. Upstream kermel and common device should now support the Sprint variant. Attached is a copy of your serranoltespr device repo, with some changes I did. See if it fixes the radio issues. I've built it locally without any problems.
[Galaxy S 4 Mini Original Android Development] arco68:
s0be, if you could pull /proc/config.gz from stock rom, that would be great. Then I can properly compare the defconfigs.
[Galaxy S 4 Mini Original Android Development] s0be:
Testing now, thanks!
[Galaxy S 4 Mini Original Android Development] s0be:
That's exactly what I used to build my 'working' config earlier. Attaching.
[Galaxy S 4 Mini Original Android Development] s0be:
Which proprietary files is this with? Should I pull from my device, or use the ones from serranoltexx?
[Galaxy S 4 Mini Original Android Development] arco68:
I just cloned vendor/samsung/serranoltexx to vendor/samsung/serranoltespr

You shouldn't need to to anything with the ones in serrano-common, as those should be common for all variants. You should only use the RIL based libs from your device in serranoltespr, although it will probably work with the ones from serranoltexx also.

If you still have propblems with radio, I noticed something in your stock build.prop.

#rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libpath=/system/lib/libsec-ril.so

So it seems your device is using a different lib than the other variants. You can try to grab libsec-ril.so from stock rom (and other libs it might depend on which aren't in serrano-common), and push them to the device. And then modify the rild.libpath in build.prop.
[Galaxy S 4 Mini Original Android Development] s0be:
Everything went wonky on me with this. I clobbered my tree and went back to a pure clean repo and am rebuilding now using vendor/samsung/serranoltexx ril stuffs (as at least that worked 'kinda' before)
[Galaxy S 4 Mini Original Android Development] arco68:
This is the one I built:

https://www.mediafire.com/?icd6il355ic153x
[Galaxy S 4 Mini Original Android Development] s0be:
Thanks, trying out your build. Will validate against my build to see if it's any different.
[Galaxy S 4 Mini Original Android Development] s0be:
Here's the status with your build:

LTE works (Alone)

EVDO/cdma works (Together)

If you select the 'LTE/EVDO/cdma', texting/calls don't work.

At the very least, that's much better than before. About to try my build.
[Galaxy S 4 Mini Original Android Development] s0be:
Also, tested:

Front Camera

Back Camera

Video Recording

FM Radio

Wifi

Wifi-AP

Just don't have any way to test NFC :-/
[Galaxy S 4 Mini Original Android Development] arco68:
As long as you can enable/disable NFC in the settings, it should work. :)

What about the notification LED? Does that work now?
[Galaxy S 4 Mini Original Android Development] arco68:
Forgot to add permissions for the LED. Just submitted and merged patch for it.

http://review.cyanogenmod.org/#/c/60857/
[Galaxy S 4 Mini Original Android Development] s0be:
Rebuilding with that now. My build differed slightly from yours (the options in network selection), but other than that, exact same status. Yep, can enable NFC.
[Galaxy S 4 Mini Original Android Development] s0be:
Yep, that fixed the LEDs.
[Galaxy S 4 Mini Original Android Development] s0be:
arco,

So how would you like to go forward? I don't really have any interest in becoming a maintainer or anything, just wanted to get CM on my S4 mini. Do you want to attempt to unify like jflte? Want to try to upstream serranoltespr first? Where can I help out?
[Galaxy S 4 Mini Original Android Development] arco68:
I'm not really sure. Unifying will be difficult or impossible I think. Mostly since we can't have a unified kernel, because of the differences between the EU and US variants.

If everything in the device works, I can try to get it merged in official nightlies. There shouldn't be much needed for maintaining it, since most work is done in msm8930/serrano-common and kernel anyway. So if the basics for the device is already in place, the rest should be pretty straight forward. I can take care of that, and you just send me patches if needed or let me know if something needs changing.

I did some additional tweaks in the device config. Test it out when you have the time.
[Galaxy S 4 Mini Original Android Development] s0be:
There are only 2 small issues, and I'm not certain they're not upstream related:

1. The whole LTE/CDMA handoff doesn't work. While connected to LTE, you don't have phone/texting. I've seen people on IRC complaining about this on the s4 (regular) nightlies, which leads me to suspect it's upstream related.

2. The notification LED doesn't seem to work for anything but battery. I've used custom colors for battery status, so I know that the LED works 'normally-ish'.

I'm building your new tree now.
[Galaxy S 4 Mini Original Android Development] arco68:
I made an error in liblights patch that added multicolor LED.

Modify the following:

https://github.com/CyanogenMod/andr...e7d#diff-c408926fdf296d75b96dfbdf5b1ecb2aR342

from:

#if defined(GENERIC_BLN) && defined(MULTI_COLOR_LED)

to:

#if defined(GENERIC_BLN) || defined(MULTI_COLOR_LED)
[Galaxy S 4 Mini Original Android Development] s0be:
This didn't fix anything, but didn't break anything either.
[Galaxy S 4 Mini Original Android Development] s0be:
Making that change just caused build failure with unresolved symbols. I made a couple of other changes to get the build to finish... but it was apparent that they are wrong. I'm doing the build again with GENERIC_BLN set.
[Galaxy S 4 Mini Original Android Development] arco68:
Yeah, I see what's wrong now.

s/set_light_notifications/set_light_leds_notifications/g

I'll fix it up later.
[Galaxy S 4 Mini Original Android Development] s0be:
Cool, I appreciate it.
[Galaxy S 4 Mini Original Android Development] arco68:
Fix merged.
[Galaxy S 4 Mini Original Android Development] s0be:
Worked. Perfect. The 'white' setting doesn't work very well (the LEDs in this are obviously 3 distinct lights), but I don't see there being any software fix for that.

Any guides you know of to debugging RIL stuff? I'd really like to get the LTE <=> EVDO/CDMA stuff sorted.
[Galaxy S 4 Mini Original Android Development] s0be:
ro.telephony.ril.v3=newDriverCallU

That causes hanging up calls not to work it seems.
[Galaxy S 4 Mini Original Android Development] arco68:
Nope, sorry. RIL stuff is pretty much way over my head. :(

Ah ok. I saw the jf cdma devices was using it, so thought it was worth a shot. It's probably only meant for >4.3 modems, so just remote that setting.

Have you tried replacing the 2 RIL blobs in vendor/samsung/serranoltespr with ones from your stock rom, or are you already using them?
[Galaxy S 4 Mini Original Android Development] s0be:
Yep. Swapped in libril.so and libsec-ril.so, changed rild.libpath. That was just worse(with just the right voodoo incantations, I was able to get an LTE connection, but that's it). I'll keep begging on IRC for help, haha.
[Galaxy S 4 Mini Original Android Development] arco68:
Ok. :)

And you also tested libril-qc-qmi-1.so from stock rom?
[Galaxy S 4 Mini Original Android Development] s0be:
Doesn't exist in stock rom ;)

I have however tried:

./bin
./bin/btnvtool
./bin/ds_fmc_appd
./bin/time_daemon
./bin/rild
./bin/hci_qcomm_init
./bin/mpdecision
./bin/geomagneticd
./bin/qseecomd
./bin/rmt_storage
./bin/qmuxd
./bin/mm-qcamera-daemon
./bin/thermald
./bin/fm_qsoc_patches
./lib
./lib/libqmi_cci.so
./lib/libidl.so
./lib/libmmjpeg.so
./lib/libdiag.so
./lib/libril-qcril-hook-oem.so
./lib/libsec-ril.so
./lib/libqmiservices.so
./lib/libqmi_client_qmux.so
./lib/libsecnativefeature.so
./lib/libqmi.so
./lib/libqcci_legacy.so
./lib/libdsutils.so
./lib/libqmi_csi.so
./lib/libril.so
./lib/libqmi_encdec.so
./lib/libdrmfs.so
./lib/libqmi_common_so.so
./lib/libmercury.so
./lib/libQSEEComAPI.so
./lib/liboemcamera.so
./lib/libgemini.so

Will try pulling some of the /init.* from stock next.
[Galaxy S 4 Mini Original Android Development] s0be:
Added a download in the first post for anyone wanting to try. Just make sure to force 3g ;)
[Galaxy S 4 Mini Original Android Development] s0be:
After doing research, it appears the radio portion of this device is very similar to the melius, so I'm playing with merging it's ril/rild stuffs into our tree, see if maybe that makes magic.
[Galaxy S 4 Mini Original Android Development] s0be:
New build uploaded. This one behaves better on 3g (CallU build prop removed). No other changes in this build.
[Galaxy S 4 Mini Original Android Development] s0be:
Ok, here's where we're at, what's up with 4g/lte vs evdo/1x:

Our radios do not support svdo/svlte. This is part of the weird radio we have to support tri-band LTE (AKA, Sprint Spark). It appears the sprint s4 (720t version, not 720 version), s5, and galaxy mega 6.4 or whatever have also suffered this unfortunate fate. The difference being, their ril/rild setups handle the eCSFB signaling to hand-off between evdo/lte/1x smoothely. As it stands, the phone transitions between 3g and 1x perfectly, so if 3g is good enough, this rom is probably close to daily driver status. I've been using it for a few days now happily.
[Galaxy S 4 Mini Original Android Development] s0be:
Here's a build that defaults to 3g instead of lte. Still takes a while to connect to 3g/cdma. Still working on finding a way to get a eCSFB ril to work on our device... I believe we'll need to not run the SamsungQualcommRIL build.prop as well as using the correct libril/libsec-ril/etc. Anyone who knows anything about this stuff, feel free to chime in! I don't know about this stuff.

http://goo.im/devs/s0be//cm-11-20140312-UNOFFICIAL-serranoltespr-3g.zip
[Galaxy S 4 Mini Original Android Development] s0be:
Now that I understand what's going on, I've 'jumped into the deep end'. I won't be doing any more build releases that don't have LTE/3g handoff fixed unless someone requests one with a specific fix from upstream linked that they're requesting. As I don't do any independed dev work on this, I won't really be fixing any bugs without reports (of which I've had zero, which kinda scares me). You can watch my github to see what I'm trying.
[Galaxy S 4 Mini Original Android Development] arco68:
Thanks for keeping us informed, s0be. :)

CDMA doesn't exist where I live, so unfortunately I don't know much about it.
[Galaxy S 4 Mini Original Android Development] s0be:
This isn't just a CDMA issue, but the fact that the Sprint S4 mini is a single radio device. It can, literally, only talk to one of LTE/CDMA/EVDO/Gsm(? still not sure it supports it) at a time. Decad3nce has been helping me with my ril issues while I wait for some other (to be left unnamed) dev to get back from vacation.
[Galaxy S 4 Mini Original Android Development] s0be:
I've gotten LTE/3g/cdma working (preliminary, anyways, too late to call someone and verify). I just need to work out a few possible bugs and I'll shoot for tomorrow night for another release with this fixed(feature complete?).
[Galaxy S 4 Mini Original Android Development] s0be:
http://goo.im/devs/s0be//cm-11-20140315-UNOFFICIAL-serranoltespr.zip

Here's a build with working 3g/cdma/lte/calling. Currently breaks GPS and Camera (at least).
[Galaxy S 4 Mini Original Android Development] arco68:
Hey s0be.

Just some helpful tips from me. I don't think moving completely away from inheriting serrano-common is a good idea, as that defeats the purpose of having a common repo, and will make maintaining devices a bit more work Basically almost all blobs are common for all variants, except for maybe a few radio related blobs.

Most of the blobs in serrano-common should work just fine for you, so I would suggest you try to figure out exactly which of the radio related blobs you need to replace, so it works better for you. I suggest starting with how it was originally, and then push one and one blob from your stock rom, until you find which ones you need. Then we can make appropriate changes to common and device vendor.
[Galaxy S 4 Mini Original Android Development] s0be:
I agree 100%. But it was easier to have it all in one place to figure out what exactly needs overridden to make it work. I've already un-unified the device tree, and am working on the breakage from that now. Next I'm ununifying the blobs tree, trying to widdle it down to just the ril stuff.
[Galaxy S 4 Mini Original Android Development] s0be:
I went the inverted route, but am back to inheriting serrano-common now. The only non overridable change I need is serrano-common to not provide bin/sec-ril (or maybe the init file for that to not be called for my device). I have to override init.carrier.rc for the /carrier partition (for chameleon support) which fixes lte/3g/cdma when using my RIL files. Not having that partition mounted causes all sorts of problems for the sprint rill for my device.
[Galaxy S 4 Mini Original Android Development] s0be:
Just pushed a fix for camera. Only thing left that I've found is compass doesn't work right now.
[Galaxy S 4 Mini Original Android Development] s0be:
AAAAAAAnd just pushed a fix for compass. I'm uploading what I believe is a feature complete build right now. Please report any problems with it.

Arco, how do I go about starting the upstreaming process? Aside from my device/ and vendor/ stuff, the only change required is pushing the sec-ril binary down to serranoltexx and serrano3gxx
[Galaxy S 4 Mini Original Android Development] s0be:
First post updated with new build. Please report any problems (preferably with logcats and how to reproduce)
[Galaxy S 4 Mini Original Android Development] philly0128:
trying to download this but the gapps link isn't working.
[Galaxy S 4 Mini Original Android Development] s0be:
It's just the stock CM11 Kitkat gapps. Can be found at:

http://wiki.cyanogenmod.org/w/Google_Apps
[Galaxy S 4 Mini Original Android Development] philly0128:
Thanks for the info.

So I have the correct recovery and when I try to install the the update I get "This package is for "serranoltespr.L520.sph-l520" device this is a serranolte"

E: error in /storage/sdcard1/cm-11-20140317-unofficial serranoltespr.zip (status 7) installation aborted.

I'm not sure if this is due to me accidently flashing the wrong ROM earlier today. I installed Liquid Smooth 3.0 KK serranltexx.zip. this is just giving me a boot loop, hence the reason to try your Rom.

I've tried running Samsung kies and it doesn't connect. I tried flashing L520VPUAMK2_L520SPTAMK2_L520VPUAMK2_HOME.tar.md5 to stock and it fails 100%

I'm just screwed
[Galaxy S 4 Mini Original Android Development] s0be:
One sec, I can put together one real fast that will accept serranolte.
[Galaxy S 4 Mini Original Android Development] s0be:
I just PM'd you a link for a zip that will accept serranolte for installation. Arco, think this should be a default for this rom, or not?
[Galaxy S 4 Mini Original Android Development] arco68:
Does there exist a system and boot image dump of stock rom? I would like to have a copy to compare with the GSM version, and see if any additional changes are needed. From what I can see on your github, the device config needs a little bit cleanup, and we really need to consolidate the proprietary files. Everything but the RIL blobs are shareable, and will make maintaining it a lot easier.

I'll work on it a bit tomorrow.

No, he's using the recovery for serranoltexx, which is not the recommended one for this device. He's just lucky that it seems to work. :) The differences between these two devices are more than enough that I'm not comfortable with allowing cross-using of recoveries.
[Galaxy S 4 Mini Original Android Development] s0be:
http://samsung-updates.com/device/?id=SPH-L520

A lot of what's in my vendor github is now obsolete, just haven't done a git rm on them yet. I've already got it to the point that it "should" only be copying the stuff for the RIL, the rest is just still there because I haven't removed it. Also, my device/ tree is back to being much closer to the serranoltexx tree, but I know I have a property setting splatted everywhere due to serrano-common clobbering it. Getting serrano-common not to set rild.libpath would be a big help in the cleanup.

I agree completely. Due to the drastic ril differences, I'd say that this device should NOT NOT NOT ever share anything (recovery/rom wise) with the ltexx and 3gxx, just so we have less cross flashers.
[Galaxy S 4 Mini Original Android Development] millopr:
Do you have a link for serranolte?
[Galaxy S 4 Mini Original Android Development] s0be:
You need to use the recovery from the first post. serranolte (generally) is the euro s4 mini lte.
[Galaxy S 4 Mini Original Android Development] s0be:
It's been brought to my attention that Odin requires recoveries in some funky md5 appended tar file. I've uploaded a test odin compatible recovery to my Goo.im, if any brave soul wants to try it out.
[Galaxy S 4 Mini Original Android Development] s0be:
And before you poke fun, I've only had a samsung device for.... 17 days... and only been poking at it's bootloader for 2 weeks. Cut me some slack.