yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] millopr:
Hey, since you are the only dev working on this version of the gs4mini... could you explain whats the differences between ours and the International lte?... like... why can't we flash those other roms?...
[Galaxy S 4 Mini Original Android Development] philly0128:
Special Thanks to s0be

s0be and I have been PM'ing each other back and forth for a couple of days and I just want to say THANK YOU. I solved my problem and where's what I did to break it and what I did to fix it.

1. What I did to break it. I was to anxious and didn't do my full research like I normally have done. When I a little research I saw alot of people reference i9195 I thought that's what everyone version of the mini was using since I didn't see anyone calling with roms for SPH-L520 (found sobe) after the fact.

So needless to say I put the wrong recovery. I couldn't get samsung kies to work and when I downloaded the stock firmware it would break in ODIN 100% which made the phone say "firmware upgrade encountered an issue, please select recovery mode in kies and try again" (kies did nothing when I tried it again)

s0be recovery was a .img file so I used "Caboomi's_Recovery_img2tar_odin_maker.zip" (google it)maker to convert it to a MD5 and I was able to load it via ODIN. and then I load CM but it bootloop on the logo.

I spoke to samsung reps online and samsung at best buy and they couldn't help me.

s0be had me try heimdall to flash the recovery but I had to convert that to a .tar file and that failed. I open the tar and took the recovery.img out of it. I converted it to .md5 and flashed with ODIN.

I was able to get into the recovery and I was able to wipe data/factory. Reinstall CM and BOOM! the phone is no longer brick or looping at the startup screen.

My girlfriend is happy and i'm out of the doghouse :)

So again s0be Thank you for your time, your patience, thank you for helping me brain storm on this and thank you for being from what I can see the only dev to supply a rom for this sprint s4 mini.
[Galaxy S 4 Mini Original Android Development] s0be:
The two biggest differences:

Our phone uses a Tri-Band LTE Single Radio Cellular Modem. This leads to the RIL Interface being completely different (Not actually completely, but certainly very different).

Our phone has a different charging/battery control chip. This leads to the two devices not being able to share a kernel easily.

The unimportant difference:

We have a notification LED
[Galaxy S 4 Mini Original Android Development] s0be:
Also, missed the 'only dev' statement there. To be fair, I'm just the only dev USING this device that's working with what we have. Cell phones can have a lot of overlap (particularly samsung, from what I've seen). Arco is also a dev 'working' on our device in that he (and likely others whose names I've not yet learned) got the basics worked out already. Our device is msm89x0, so we inherit a lot of 'already just works' from there, and samsung released a working kernel source for our device, which was a great source of fixes. The only 'dev' work I really had to do was pick and choose the right pieces to go together.

So yes, I'm currently the only dev with a SPH-L520, but I'm not the only dev working on our device.
[Galaxy S 4 Mini Original Android Development] arco68:
Finally finished downloading the stock rom. Must have been the slowest download I've ever done, but at least I have a copy now. :p

I've moved some things around in serrano-common and the device repos, to make things easier for both parties. I'll be making a test build a bit later so s0be can check if things are working ok.

Regarding the carrier partition, what exactly does it contain, and what happens if you don't mount it? I'm just trying to figure out if it's really needed in CM, as I'm sure other Sprint devices also has this partition, but I don't see them mount it.

Also, was there any difference after adding

ro.telephony.ril.v3=newDriverCallU,newDialCode

If not, I think it can be removed.
[Galaxy S 4 Mini Original Android Development] s0be:
Without the carrier partition, our ril stuff fails to detect the modem. I'll test again without it now that I have a good working baseline, but it wasn't until I added that that I was able to get any cell service with our ril.

Yes, without those we cannot place calls, nor can we hang up.
[Galaxy S 4 Mini Original Android Development] s0be:
root@serranoltespr:/carrier # ls -al
-rw------- system system 16 2014-03-01 14:18 .chameleon.hash
-rw-r--r-- system system 2865 2014-03-01 14:18 chameleon.xml
drwx--x--x system system 2014-03-01 14:18 data
drwx------ root root 1969-12-31 18:00 lost+found
-rw-rw---- system system 20480 2014-03-06 14:03 properties.db
-rw------- system system 12824 2014-03-06 14:03 properties.db-journal
root@serranoltespr:/carrier # ls lost+found/
root@serranoltespr:/carrier # ls lost+found/ -al
root@serranoltespr:/carrier # ls data/app/Settings/
Customization_CarrierLegal.zip privacy_ko.html
privacy_en.html privacy_vi.html
privacy_es.html privacy_zh_cn.html
root@serranoltespr:/carrier # ls data/app/Settings/ -al
-rw-r--r-- system system 4277 2014-03-01 14:18 Customization_CarrierLegal.zip
-rw-r--r-- system system 1289 2014-03-01 14:18 privacy_en.html
-rw-r--r-- system system 1693 2014-03-01 14:18 privacy_es.html
-rw-r--r-- system system 1541 2014-03-01 14:18 privacy_ko.html
-rw-r--r-- system system 1845 2014-03-01 14:18 privacy_vi.html
-rw-r--r-- system system 1216 2014-03-01 14:18 privacy_zh_cn.html

Here's the files list on the /carrier partition

looking in chameleon.xml, that looks like it dictates some of the behaviors of the ril (can send you privately).

Looking in properties.db, that looks like it carries information about the account subscription (at the very least, it has my account number in it), and details like pre/post pay, some proxy information, and pointers to the APNs it's using.
[Galaxy S 4 Mini Original Android Development] s0be:
First bug found:

the ThemeChooser modules is not being compiled in/included.

Working on the 'correct' solution to this. Arco, any tips?
[Galaxy S 4 Mini Original Android Development] s0be:
Found the solution (had random Android.mk sitting in /vendor) but build broke gps. I consider GPS more important, so I'm not uploading a new build until I get that resolved.
[Galaxy S 4 Mini Original Android Development] lexxy2000:
i will test if you need testers. is the currently upload ok to run. could not quiet follow the conversation.
[Galaxy S 4 Mini Original Android Development] s0be:
Yep, the upload in the first post is fine to run. I haven't yet figured out how to install the recovery in windows (no windows here for me to try out), but I have reports that the recovery.tar.md5 works with odin. I'd love someone to write up a description of how to use that.

Under Linux, I used the recovery-blah-blah-blah.img and heimdall command line to install it:

heimdall flash --RECOVERY recovery-blahblahblah.img

Currently, the theme chooser is broken, but everything else appears to work (all my testing, I haven't found other problems)

Again, just make sure you have a sprint s4 mini before flashing this stuff. I've already helped 2 people get back from cross flashes and I really don't want that to become a full time task.
[Galaxy S 4 Mini Original Android Development] arco68:
Try this: http://www.mediafire.com/download/c3a6d926xa2da1q/cm-11-20140318-UNOFFICIAL-serranoltespr.zip
[Galaxy S 4 Mini Original Android Development] s0be:
no cell service

radio logcat http://pastebin.com/mhV9hD5z
[Galaxy S 4 Mini Original Android Development] arco68:
Try copying rild binary from stock rom to system/bin, and set permissions:

chown root.shell rild

chmod 755 rild

and reboot.
[Galaxy S 4 Mini Original Android Development] s0be:
If it'd be easier, you can push changes to a github that I'll just add as a remote and merge onto my tree. My github currently reflects my local working trees.
[Galaxy S 4 Mini Original Android Development] s0be:
Different error, still no cell coverage. Swapping qmuxd also didn't help, but that's to be expected because our qmuxd requires our qmi libs.
[Galaxy S 4 Mini Original Android Development] arco68:
Yeah, try pushing qmuxd and qmi libs from your stock rom. I think that should get it going, together with the rild binary.

I'm hitting the bed right now, so will try to push proposed changes tomorrow.
[Galaxy S 4 Mini Original Android Development] s0be:
Hope it doesn't cause you headaches. I just realized I never committed/pushed my cleaned up vendor. It's pushed now. There was a lot in there that wasn't actually used. It should almost all be gone now.
[Galaxy S 4 Mini Original Android Development] s0be:
Btw, that's the exact process that lead to the list of files I'm currently using. I may have a few overriden that don't need to be, but for the most part, the 20 files we currently use from stock is pretty damn close to minimal.

edit: Down to 13 files now. Pushed another commit showing where I'm at. I verified the md5sum on a couple of the files to make sure the device hadn't found old copies in out/ somewhere.
[Galaxy S 4 Mini Original Android Development] s0be:
New build uploaded with working theme chooser.

New bug discovered: Camera crashes when switching to external storage. Researching this one now. If you run into this, you can reset the camera back to internal storage by going to:

Settings->Apps ->All ->Camera ->Clear Data

I've run into other settings that seem to be able to crash the camera, so using a market camera for daily use might be a better option for now. That being said, if you don't futz with settings much, the camera is rock solid.
[Galaxy S 4 Mini Original Android Development] s0be:
Switching to video in camera also crashes it. These bugs have also been reported on the Non sprint edition of the phone, so it's not a 'us specific' bug.
[Galaxy S 4 Mini Original Android Development] RealMrFun:
So far the only issue I ran into was "No Apn Specified On Device" error massage when using mms, so I switch to EvolveSMS to updated the mms apn.
[Galaxy S 4 Mini Original Android Development] s0be:
Upon research, there are a LOT of devices complaining about this, so I suspect it isn't specific to us. That being said, I just sent a picture using hangouts (while connected to LTE). Will try again when on 3g, and a 3rd time on CDMA.
[Galaxy S 4 Mini Original Android Development] s0be:
Now tested sending 3g mms using stock messaging. Anyone else having problems sending mms? Connected to wifi or cell data only? Anyone tested other cases? (Not on home network/roaming/connected to wifi/etc). Please report mms successes and failures with any of these details.
[Galaxy S 4 Mini Original Android Development] arco68:
They removed some MMS related stuff lately, including something specific to Spring. I'm working on putting that back into serrano-common instead.

Also, something else interesting... I'm working on maybe implementing the Sprint variants RIL blobs for all variants. Preliminary testing shows that it seems to work fine for non-CDMA devices as well. I think these are more updated than we have for the GSM variant, and I also for the first time is able to get a H+ connection instead of just a H connection. That's why I'm keen on using them.
[Galaxy S 4 Mini Original Android Development] s0be:
I'm not convinced mms is broken on sprint for our device. I've tested:

mms with hangouts on lte, and 3g

mms with hangouts on cdma w/ wifi

mms with messaging on lte and 3g

mms with messaging on cdma w/ wifi

and all sent successfully. I've not yet found a way to force disable 3g and lte for a pure cdma test.

Excellent. I'd be surprised if a 'newer' device used an older ril. Glad to hear it's preliminarily compatible with serranoltexx. That will certainly help out the integration!
[Galaxy S 4 Mini Original Android Development] arco68:
New test: https://www.mediafire.com/?7e757dbczzq5lv2
[Galaxy S 4 Mini Original Android Development] s0be:
I've run it through the full barrage of tests and it seems fine. Still the weird camera crashes, but no worse than my builds.
[Galaxy S 4 Mini Original Android Development] s0be:
I'm guessing it's the same crashes seen on the serranoltexx builds. I'll dig into the backtrace from it. It looks like a problem in the video preview not handling something in the frames from the camera (at initial glance).
[Galaxy S 4 Mini Original Android Development] arco68:
Was it on a fresh install? There was some camera changes a few days ago which caused some crashes, but it should be fixed now.

Alright, I'm trying to find the best route to go for this RIL blob difference between the Sprint variant versus all the others. Can you test this build?

https://www.mediafire.com/?dp6f1bmplmcpu66
[Galaxy S 4 Mini Original Android Development] s0be:
Yes, I always do:

Nandroid

Factory Wipe

Format System

Install Build

Install Gapps

Reboot

Test <Here camera crashes. This isn't hte QCOM Camera settings crash, but a page fault in between the surface flinger and the kgsl stuff

Nandroid Restore

Install Build

Test
[Galaxy S 4 Mini Original Android Development] s0be:
That works fine for us, although GPS wasn't able to see any satellites.

Compass/gyro worked, however.
[Galaxy S 4 Mini Original Android Development] s0be:
Here's a logcat of the camera crash:

http://pastebin.com/3xGvwvdc

Edit:

The easiest way to reproduce this seems to be having the camera save to sdcard, then swiping over to view previous shots. Recording video/taking pictures still works fine (unless the camera crashes before then). If it crashes at certain points, it can leave you unable to re-open the camera without a reboot.
[Galaxy S 4 Mini Original Android Development] arco68:
GPS worked previously?

Try setting ro.gps.set_privacy=1 in build.prop. I understand that some CDMA devices need it.
[Galaxy S 4 Mini Original Android Development] s0be:
Yep, gps has worked in most/all the builds so far.
[Galaxy S 4 Mini Original Android Development] s0be:
Haven't tested that yet, but GPS DOES sorta work, just only 1 app at a time.
[Galaxy S 4 Mini Original Android Development] arco68:
Weird about the camera. I remember having the same errors a while ago, but can't remember what happened because I haven't seen them since.

I've merged a bunch of stuff to both device common and vendor, and updated serranoltespr here: https://github.com/arco/android_device_samsung_serranoltespr

If you sync now, you'll also get an updated kitkat revision it seems (KVT49L). :)
[Galaxy S 4 Mini Original Android Development] s0be:
It could be related to corrupted/crap videos on my sd card. Either way, it's 'back'.

I reviewed your commit, nothing jumped out at me. I'm going to swap over and build from your tree. Does now seem like a good time to 'handoff' and I'll rebase forked off your tree and send you pull requests?
[Galaxy S 4 Mini Original Android Development] arco68:
Yeah, test it a little first, and then I'll try to get the device merged upstream.
[Galaxy S 4 Mini Original Android Development] s0be:
That would be great, I'll still try to help fix bugs, but I am WAY underknowledged to actually be a device maintainer. I'm ONLY an experienced Kernel developer. I was shocked that, even building off your work, I managed to get something to boot and be functional.
[Galaxy S 4 Mini Original Android Development] s0be:
Building off a fresh repo sync with your changes. Is:

https://github.com/arco/android_device_samsung_serranoltespr.git

Updated to reflect your changes (IE: Can I build off that and be fine?)
[Galaxy S 4 Mini Original Android Development] s0be:
Ignore this, I see we only have 1 proprietary files folder now.
[Galaxy S 4 Mini Original Android Development] s0be:
It may have been a dirty tree, but building off merging your github onto mine, using the latest vendor/samsung/ from upsteream, lead to no cell. Will make clobber and test again in the morning.
[Galaxy S 4 Mini Original Android Development] s0be:
Clobbered my tree and build worked. Probably unrelated to us specifically, but weird homescreen alpha issues.
[Galaxy S 4 Mini Original Android Development] arco68:
Hmm, haven't noticed that here.
[Galaxy S 4 Mini Original Android Development] s0be:
I've seen it twice so far. Seems to be related to the homescreen transition 'stack'. If I do various swipes between 2 screens, sometimes the widget alpha never makes it back to completely visible. Rebooting resets it. Like I said, I really suspect it's unrelated to our device specifically.
[Galaxy S 4 Mini Original Android Development] s0be:
New build up. This is using arco's device/samsung/serranoltespr/ as well as the unified device/samsung/serrano-common/
[Galaxy S 4 Mini Original Android Development] RealMrFun:
I have been experiencing the following 2 issues

• App sorting won’t stick after a reboot, it will go back to “install time”

• Volume rocker does not work during a phone call, it stays on max volume

EDIT: the indicator moves up and down, but the actual volume does not change
[Galaxy S 4 Mini Original Android Development] arco68:
s0be, are you able to test the following 2 patches?

http://review.cyanogenmod.org/#/c/61251/

http://review.cyanogenmod.org/#/c/61609/

Also, are you able to verify the volume issue mentioned in the previous post?
[Galaxy S 4 Mini Original Android Development] s0be:
I'm bisecting a host kernel bug right now, but after I get that done, I'll do a build with those 2 patches.

Yep, I can confirm the volume bug.
[Galaxy S 4 Mini Original Android Development] arco68:
Ok, try the following libs from stock rom, and see if one of them fixes it.

libacdbloader.so

libadsprpc.so

libaudcal.so
[Galaxy S 4 Mini Original Android Development] s0be:
Just finished bisection of the bug i was hitting(not android related). Will test those and the the previous patches tomorrow.
[Galaxy S 4 Mini Original Android Development] Joanzin:
Hello,

I just put this on my phone and love the rom! Thank you!! However...I'm on US sprint and I have no data what so ever. I can get calls and call out, I am on the network but have no data. I can't even get my MMS messages even tho I can get text and send text. Is there a fix for this or can someone post the stock rom so I can flash back until there is a fix for data on the rom?

Thanks in advance.
[Galaxy S 4 Mini Original Android Development] s0be:
Odd, all works fine for me (On sprint). I haven't seen anyone post a stock rom update for our device yet (and I tried and failed to make one). I always use either my nandroid backup of stock, or used heimdall to flash individual partitions back from stock.

You could try one of the previous builds at:

http://goo.im/devs/s0be/cm11

to see if any of them work better for you. Has anyone else had issues with data connectivity with the latest nightly?
[Galaxy S 4 Mini Original Android Development] Whosat:
Sounds like an APN setting issue.

Go to Settings - More - Mobile Network - Access Point Names and take a screenshot to post here. Maybe someone here can post your working APNs for reference or you could call in to Sprint to ask for those values. A quick Google for it might work too
[Galaxy S 4 Mini Original Android Development] RealMrFun:
With the latest build, I cant make/receive calls or SMS on LTE, only on 3G, I changed the preferred network type not to connect me to LTE. Even with this, every time I turn my phone on, move away from wifi, or go from a place with no service to a place with service, I have to manually select the APN.

I tried erasing the the 5 default APS and add the one suggested on other forms, but if wont let me save it.

I have had the APN problems with the previous builds too, but on the previous builds I had no phone/sms issues once connected to LTE (maybe no MMS, I don't remember).

There is a tar.md5 stock rom available, but I cant get it to work, maybe someone else has better luck.

http://www.mediafire.com/download/ittpe38u843mdm0/SPR-L520VPUAMK2-20131115204826.zip

Can you upload your nandroid backup of stock (if it does not have any personal data)?
[Galaxy S 4 Mini Original Android Development] s0be:
I'll hammer on this stuff tonight (in about an hour I'll get home from work), and see if I can get anywhere. I'll try to make a stock rooted zip before working on the other stuff, as I figured someone who's done this before would have stepped up and done it by now.
[Galaxy S 4 Mini Original Android Development] Joanzin:
I have no network operator and when I try to add a new APN it will not save and it also shows no APN settings at all when I open them. It just will let me add then the APN sttings will open for me to add information. I just did a wide and reinstalled the rom and still the same thing. I hope this helps.

Thank you!! =)
[Galaxy S 4 Mini Original Android Development] Joanzin:
You can't use the stock rom. It's a previous version. The boot loader updated with kit kat. It will not allow you to down grade once you have upgraded to kit kat. But thanks.
[Galaxy S 4 Mini Original Android Development] s0be:
Ahhh, I never took the kitkat update (disabled auto update at the store, in front of the salesman). Anyone have a copy of the OTA file?
[Galaxy S 4 Mini Original Android Development] Joanzin:
Another thing that might be relevant to this issue issue is that I am having errors come up telling me I have no sim card in the slot when I do. My sim is not being read by the looks of it. Hope this helps.

Thanks!
[Galaxy S 4 Mini Original Android Development] s0be:
very likely the exact cause. Did you try any of the previous builds?

http://goo.im/devs/s0be/cm11/cm-11-20140319-UNOFFICIAL-serranoltespr.zip

I don't have a device I'm willing to OTA to KK to get the new bootloader/radio/etc for testing.
[Galaxy S 4 Mini Original Android Development] Joanzin:
I haven't yet. I will try. I figured the reason for this was the sim card not being read as it dies pull the APN settings from the sim card from what I understand. I will give it a try and report back. I'm hoping someone around here updated thru kies and managed to save a copy of the KK update.

*Fingers Crossed*

Thanks.
[Galaxy S 4 Mini Original Android Development] s0be:
It doesn't pull the APN from the sim or anything like that. If it's not able to read the sim, it means that the ril/rild/libsec-ril aren't playing nicely together. This could be related to the new bootloader/modem/whatever came with the kitkat upgrade. I'm wagering the latest build I released only happened to work on my setup due to some remnant on my phone from any number of other possible differences. Doing a factory wipe test with the 19th build might help.
[Galaxy S 4 Mini Original Android Development] Joanzin:
Nope! Just installed it and same thing....=(
[Galaxy S 4 Mini Original Android Development] s0be:
Well, unfortunately, you're going to have to find a way back to stock. I've (on at least 2 occasions), put my phone into a state that only going back to stock and resetting/reactivating. I know'knew all the ways to trigger that, so I only dropped releases that I couldn't make it happen on. I'm pulling the latest build. After you get back to stock, and get that re-activated, try going back to the 19th build. I could really use someone with the ability to go back and forth between my builds and the stock kitkat build (or better, a copy of the kitkat update.zip)
[Galaxy S 4 Mini Original Android Development] Joanzin:
If I can get back to stock I can do that for you no problem. I'll just have to keep backups.
[Galaxy S 4 Mini Original Android Development] thatgurllizz:
A
[Galaxy S 4 Mini Original Android Development] angruvidal:
Unforuntately, prior to finding this thread, I made *exactly* the same mistake. I tried the 3/19 ROM and it gave me the same "this devices is a serranolte" error. I was able to restore to a clockworkmod ROM with root, but it's exhibiting odd behavior here and there. I can't restore to the stock rom because KitKat is already installed.

Would it be possible to get a build that accepts serranolte as well? I think it's my only shot of having a fully functional device. Also, would this force the device to correctly recognize itself as serranoltespr?

Any help appreciated. This is my wife's phone and I'm iin the doghouse.
[Galaxy S 4 Mini Original Android Development] arco68:
You should install the CWM version linked to in first post.