CM11 issues on SHV-E300 - Galaxy S 4 Developer Discussion [Developers-Only]

I am developing CM11 for the Korean models of the S4. Right now I am currently running the build I just compiled. Here is a list of what is not working:
USB Storage : no /emulated/0/sdcard error when trying to mount or download anything not from play store.
Video Camera
Camera takes blank pictures : believe this is because of the storage issue
No sound : we use the yamaha chipset
Can't make or receive calls
I am trying to figure out how to fix the USB storage bug on my end but I think I am at a loss. As for the other issues, I think that just might be the kernel side of things, but not for sure. Can someone help me out with a little advice for some of these issues? Thanks.
Edit: I forgot to add that with not being able to make or receive calls, I do have data (2g, 3g, and LTE). So I really don't know what is going on.

---

Okay, so now I have everything working except for the making/receiving phone calls and the sound. Is there anyone that might could help me with this?? I really don't know what I am doing when it comes to the kernel and getting things like that working. I know that on the native touch wiz system that my CBD file is located under the root dir under sbin, but on the CM version I have to put it in the system/bin folder. Any help would be greatly appreciated. Thanks.

---

Seems like I am asking the wrong question
Okay, since it seems like the wrong question is being answered here. Here is the correct way to ask this. While working with the kernel, how do I know what modules I need for audio, signal and everything else to work with Cyanogenmod??

---

Sorry, just saw this - is that a Exynos or QC variant?

---

garwynn said:
Sorry, just saw this - is that a Exynos or QC variant?
Click to expand...
Click to collapse
It is a exynos varient with yamaha audio. It is also LTE. Thank you for any advice you might can give.
Sent from my SHV-E300K using Tapatalk 2

---

lunerceli said:
It is a exynos varient with yamaha audio. It is also LTE. Thank you for any advice you might can give.
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
If you're still having issues, I would check your device tree against this:
https://github.com/CyanogenMod/android_device_samsung_i9500
and vendor blobs against this:
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/i9500
From what I've been reading the SHV-E300 is a i9500 variant so they should be nearly identical.
You should be able to use that device tree and the kernel referred as a comparison.
The list of proprietary files in device tree should also help make sure you grabbed everything off of the stock ROM that you need.
Good luck! Hope this helps you straighten out the remaining issues!

---

garwynn said:
If you're still having issues, I would check your device tree against this:
https://github.com/CyanogenMod/android_device_samsung_i9500
and vendor blobs against this:
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/i9500
From what I've been reading the SHV-E300 is a i9500 variant so they should be nearly identical.
You should be able to use that device tree and the kernel referred as a comparison.
The list of proprietary files in device tree should also help make sure you grabbed everything off of the stock ROM that you need.
Good luck! Hope this helps you straighten out the remaining issues!
Click to expand...
Click to collapse
Thank you for the advice, but I have already been using parts of the I9500 to get to where I now. I just completed another build last night after playing around with the ramdisk but it wouldn't boot. LOL ... I still don't have sound or calling. I know that with the SGS2, they don't have an audio folder in their device tree for the Yamaha audio. I don't know if I need one or not since I cannot find any lib file or driver that corresponds to audio. My question though is that I did find a file that has the same layout as the es325_fw.bin file that the I9500 uses. I can't remember the name of it right now, but it is filename_fw.bin. Do you think that could be my audio? As far as calling goes, I know that on the stock firmware, the pda and the baseband both have to be the same in order to make or receive calls, so how am I supposed to do that one for CM??
@garwynn .. I just built another aplha build, and I just realized I can't get the usb mass storage to show up when the phone is connected to the computer. Any advice for that??

---

lunerceli said:
Thank you for the advice, but I have already been using parts of the I9500 to get to where I now. I just completed another build last night after playing around with the ramdisk but it wouldn't boot. LOL ... I still don't have sound or calling. I know that with the SGS2, they don't have an audio folder in their device tree for the Yamaha audio. I don't know if I need one or not since I cannot find any lib file or driver that corresponds to audio. My question though is that I did find a file that has the same layout as the es325_fw.bin file that the I9500 uses. I can't remember the name of it right now, but it is filename_fw.bin. Do you think that could be my audio? As far as calling goes, I know that on the stock firmware, the pda and the baseband both have to be the same in order to make or receive calls, so how am I supposed to do that one for CM??
@garwynn .. I just built another aplha build, and I just realized I can't get the usb mass storage to show up when the phone is connected to the computer. Any advice for that??
Click to expand...
Click to collapse
Any of those .bin files that you think are missing in the blobs.... I'm of the opinion that you can throw them in and test adding/removing one at a time to see if it changes. The logcat may also help give clues as to what is going on.
USB storage = check your build.prop and see what options you have set for USB. you could also edit your usb script to force usb mass storage.
I need to check on the firmware question. I though this wasn't the case, you just need a valid fingerprint and ROM doesn't have to match baseband. Is it possible that some of the RIL blobs may be missing?

---

I just compiled another build. I made sure that the build fingerprint was exactly like it should be. When I installed CM11, I went to about phone and it showed that my fingerprint was KVT49L and not the KOH49T that I had set it to. It kept telling me to insert sim again, which I think I may have fixed. As far as the sound goes, I went through all the bin files and looked them up on google. They all pertained to video and not audio. Inside my stock system, there is a ysounds.xml with a reference to etc/ymc/param. Here is a pastbin of the ysounds.xml file if you wouldn't mind looking at it and letting me know what you think.
YSOUNDS.XML
I have never developed for a high end device before, so this is none the less getting really interesting and fun. LOL.
When looking through the file, it looks almost exactly like the mixers_path of I9500.

---

New build with audio changes in my device/audio folder caused the system not to Boot. It got to the cm loading screen and there it stayed. Any ideas??
Sent from my SHV-E300K using Tapatalk 2

---

lunerceli said:
New build with audio changes in my device/audio folder caused the system not to Boot. It got to the cm loading screen and there it stayed. Any ideas??
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
Able to get a logcat?
Sent from my LG-LS980 using Tapatalk

---

Nope. Adb sets on waiting for device for about 5 minutes and then says no devices available.
@garwynn , I just got a new build. I have the correct fingerprint and it is still ending the call as soon as I dial the number. I tried using the yumc files that I had found that were on the phone, but still no sound. I am going to try to add the other files like the ysound and the files it references to the build as well to get sound, but I don't know. It is worth a shot I reckon. LOL. Also, I looked in the build.prop file and there is nothing in there about usb or storage. So I don't know what is going on with that one. I am going to check more on it and see what is going on. Do you have any more advice that you might can give? I don't know if I have said this before, but this is the first time that I have developed for a high end device so this is proving to be a challenge. LOL. Thank you again.
Sent from my SHV-E300K using Tapatalk 2

---

I've been dropping by here a lot lately hopeing for some updates~ anything new?
btw, thanks for trying so! I know nothing on building, and yet its hopeful to see someone working on this!

---

eungholee2 said:
I've been dropping by here a lot lately hopeing for some updates~ anything new?
btw, thanks for trying so! I know nothing on building, and yet its hopeful to see someone working on this!
Click to expand...
Click to collapse
None as of late I am afraid. I havent had much time to work on things. My system had crashed so I had to get back to where I was. Lol. I did however get the storage bug fixed, the mic can hear things but still cannot transmit sound. It is a pita working with this stupid yamaha dac. Hopefully soon though.
Sent from my SHV-E300K using Tapatalk 2

---

lunerceli said:
None as of late I am afraid. I havent had much time to work on things. My system had crashed so I had to get back to where I was. Lol. I did however get the storage bug fixed, the mic can hear things but still cannot transmit sound. It is a pita working with this stupid yamaha dac. Hopefully soon though.
Click to expand...
Click to collapse
Isn't the Yamaha DAC the same as in the lte-a models? (E330K/S) -They have roms for that model, so maybe you could try pulling them from there
also, there's a patch for MIUI that I found here: http://opnay.tistory.com/23 that has working audio I think, but you can't end calls.

---

eungholee2 said:
Isn't the Yamaha DAC the same as in the lte-a models? (E330K/S) -They have roms for that model, so maybe you could try pulling them from there
also, there's a patch for MIUI that I found here: http://opnay.tistory.com/23 that has working audio I think, but you can't end calls.
Click to expand...
Click to collapse
Sadly its not. The e330 models use the qualcomm and wolfson chips. It sucks but I think I know where the hickup is. Just have to learn more about the kernel to fix it. When I go to build, it tells me that there are uninitialized modules for the kernel and to recompile the kernel with the modules enabled. So when I have time I will delve into that.
As far as that pitch goes, I looked into it and it was 4.3 so that would lead to a dead end. Also it was specific to MIUI. I am trying to ask for help from seasoned developers but never get an answer back from most of them. Only a couple have given me advice. Lol. So if you know if anyone that would like to help, just have them pm me . thanks.
Sent from my SHV-E300K using Tapatalk 2

---

please add the ultra power saving mode as you can

---

NK-SOFT said:
please add the ultra power saving mode as you can
Click to expand...
Click to collapse
On my test builds it usually goes about a day and a half using wifi and playing games. So that's not that bad. Lol. I am still working on it though.
Sent from my SHV-E300K using Tapatalk 2

---

thank you good luck love you dev

---

lunerceli said:
Sadly its not. The e330 models use the qualcomm and wolfson chips. It sucks but I think I know where the hickup is. Just have to learn more about the kernel to fix it. When I go to build, it tells me that there are uninitialized modules for the kernel and to recompile the kernel with the modules enabled. So when I have time I will delve into that.
As far as that pitch goes, I looked into it and it was 4.3 so that would lead to a dead end. Also it was specific to MIUI. I am trying to ask for help from seasoned developers but never get an answer back from most of them. Only a couple have given me advice. Lol. So if you know if anyone that would like to help, just have them pm me . thanks.
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
The guys at Dokdo Project have working sound! but no phone calls as of yet. They seem pretty slow to update, I'm checking out their blogs, but still a no go as of yet.
It's all in korean, but if you want to give them a shot:
http://dokdo-project.com/
---------- Post added at 02:40 PM ---------- Previous post was at 02:33 PM ----------
just another quick tip: Apparently in Korea they have usim (simcard) locks that prevent other models from calling,
You have to manually change the build.prop and change the ro.product.model= to whatever your model is, in my case:
ro.product.model=SHV-E300K
also, I think this might apply to other places in the build.prop as well, but haven't been able to go that far.
---------- Post added at 02:46 PM ---------- Previous post was at 02:40 PM ----------
just another quick tip: Apparently in Korea they have usim (simcard) locks that prevent other models from calling,
You have to manually change the build.prop and change the ro.product.model= to whatever your model is, in my case:
ro.product.model=SHV-E300K
also, I think this might apply to other places in the build.prop as well, but haven't been able to go that far.