yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] Do you think that the modload.zip would work on NB1? I know that NB1 and NC1 are very similar, but I don't know. Probably gonna upgrade to NC1 just to mess around with the modload stuffs.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
I am not sure, but I do know that we can use NC1, I have successfully tested that before. I am pretty positive, although as of yet untested, that we can use any Nxx kernel.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
[MENTION=5083211]Evant28[/MENTION]

Would you be willing and able to test the wifi upload with NC1, NI1, and NJ4 kernels and modules? If so, you could report back to this thread if they do/do not work. We already know that NB1 works.

In theory it should, but it would be nice to officially test them.
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Modules should match the kernel right? I didn't seem to have Wi-Fi using NC1 kernel and modules, but that may just be because I have OC4 bootloader. Someone with the correct bootloader should probably confirm that. I did get a nice successful boot using a ROM slot though.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Sure thing. I'll report back in a bit.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
My phone is OC4 also. As you know, you can still flash the stock kernels and modules. As for me, using the NB1 kernel and modules, I have noticed that I had to reboot twice to get it working after I flashed, but on another flash I was able to use it the first boot. I think that is why it is a good idea to test these a few times.

We may find that some kernel/module setups do not work.

Thanks for testing these out too! :)
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] I went into my personal AOSP build and remembered I ported over the CM camera2.apk and decided to try it out on this rom, and what do you know. It works! Uploaded it in an attachment.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Also, I've been trying out some gapps packages and all of them result in working Play Store, but Google Play Services crashing non-stop.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Quick update on testing. Haven't had a chance to do the kernel upgrades but on NB1 I've noticed a few things which you might have seen as well.

1. Reboot and Power Off functions in the power menu are completely useless.

2. After each reboot 'Disable Hardware Overlays' has to be re-enabled

3. Like Alaska mentioned earlier, I had to reboot twice for WiFi to work. On the next reboot it wasn't functioning again as well.

I'll test the other kernels later when I have time.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Really? I haven't any of those problems except for the one with 'Disable Hardware Overlays'. When I use the reboot function it works flawlessly. To fix wifi after reboot you need to do a Soft Reboot. You'd need to enable the 'Advanced reboot' option in developer settings to do a Soft Reboot.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Whups, I forgot about that menu. The thought crossed my mind to soft reboot but then I didn't follow through. Have you tried using the teleservice apk from a working GPE build yet?
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
I've been thinking about it, but haven't had time today. Doing it tonight.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
If you install the cm11 to the ROM slot, reboot and power off may not work. They don't on my phone. However, if I install to the stock slot, the power off and reboot work flawlessly. So I believe this is a safestrap problem with ss 3.75.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Great question, I did try the one from Joe-Techs ROM before making the OP, and it errored relentlessly. I have not tried the ones from jmsqs Roms yet.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Great! Does it work for pics and video?
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
I just tried the one from Joe's ROM and am getting no force-close errors, haven't checked logcat tho. Sadly calling still fails.

---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------

Aah good point, I am using a ROM slot.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Yeah, would post an attachment with a quick vid and pic, but I can't upload the files to xda site from my phone ;-;
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Great work! I need to get Joe's permission to use his. I will PM him. Have you tried any from jmsqs? We have permission to use his stuff. Perhaps the other fixes have enabled the apk to work? Can you attach yours here so we can test it too? Also to verify against the one I tried.

Great work! Once we get permission, I'll add it in and update the OP.

As for phone calls, we need to fix the APN settings so you can link up with your carrier. You could try editing the APN XML file directly, it is very straight forward. You can edit it with any text editor.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Awesome! I'll fold it in and get the updated ROM posted tomorrow! Great work!
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Sorry, looking back I might have mislead you a bit. I am getting the force close error on the dialer when I try to place the call, but I am not getting any crazy errors obviously related to the teleservice.apk. I'll upload the apk anyways.

http://www.filedropper.com/teleservice

EDIT: Changing APNs doesn't seem to change anything.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
I'm compiling a build with the apn fix. Will report back with result in around 1 hour.

EDIT: Oh, editing apns has no effect? In that cade I'll be looking through jmsq's ROM for some files related to apns/cellular service and research them.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
I may not have done the APN config right but I think I did. Also...I copied everything related to Google from the priv-app folder in Joe's ROM; so no crazy force-close festivals. I was able to add my account and browse apps on the play store. No such luck on installing apps though (Error retrieving information from the server). The Google app will launch, allow me to opt-into Google Now, but then force close; same result if I clear data and opt-out of Google Now.

EDIT: Voice search fails to launch as well.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Hmmm... That means the gapps problem is something with the rom, and we need to find out what that would be. I have no idea what it could be. Do any of you?
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
If I try to launch the Google Search app I get ... [CRASH] com.google.android.googlequicksearchbox threw java.lang.UnsatisfiedLinkError

According to this link, "The UnsatisfiedLinkError is thrown when an application attempts to load a native library like .so in Linux".
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
I tested out the apn-config from both Joe-Tech's and jmsq's rom with no success. I'm gonna test out the modload script real quick and see what I can do with it on NB1.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
One thing to be careful of, is not turning this CM ROM into a GPE ROM. CM apks have different features built in, which we only want to replace if we have to.

Swapping all the priv-apps is a good idea for testing, but we want to keep as much CM goodness as possible. :)
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
It ran in terminal, but I don't see a difference in the phone. I slapped in some modules I had from another cm build and my personal rom, but no luck. We need to focus on cell service right now. If we don't focus on it, then, even if we fix everything else, but have no signal, then the rom would be pointless. Does anyone have any suggestions on what the problem could be?
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
This is the key to a ROM, it's not much of a phone if you can't make a phone call. ;)
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Very good point.

---------- Post added at 07:41 AM ---------- Previous post was at 07:41 AM ----------

Also very good point.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
We need to find more people to help test and find solutions to the problems we're having in the rom. Like, we fixed a great amount within the 3 days of the rom being on XDA we fixed/worked around essential problems like Wi-Fi, internal storage, SoD, and the CM camera issues. If we had more than just 4 people working with us we could probably make huge leaps in progress within the next week or so and have a much more usable rom. This thread has over 800 views and and there are only 4 people actively participating. Like, come on now. I understand that most people don't know much about the internals of a rom, but at least contribute a little. Sorry for going on this little rant. It was bothering me a bit earlier today so I decided to let it out.

---------- Post added at 01:55 AM ---------- Previous post was at 01:36 AM ----------

I think I might have found a fix for the external sd, but I'm not too sure yet. I remembered an issue with one of the sd cards a while back on one of my old devices and they mentioned the file 'vold.fstab' which I just found out is located in /system/etc/ I'll report back after I finish compiling and flashing the rom.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Sounds good, I'm gonna just keep poking around. I should probably test the other kernels too.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Wooooooo! I've made some progress! Now, I can see an extSdCard folder in /mnt/ but it say's I need root access. Gonna try the temporary root method and report my findings.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Awesome!

---------- Post added at 07:40 PM ---------- Previous post was at 07:28 PM ----------

About the kernel thing...it looks like I'd have to take the OTA and then do the whole upgrade process. Unless it's really necessary I'd like to avoid having to do a complete wipe.

Sorry :(
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
It ends up saying "The file or folder was not found." I've got a couple more things I'm gonna test, but at least the external sd is being recognized.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Easy champ! :)

By the grace of God, a bit of elbow grease, and determination has enabled us to fix lots of problems. It would be great to have more help, but we are getting a lot done. We should have this finished in no time! ;)
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
I just got a PM from Joe-Tech giving us permission to use it. I added it to my ROM, but it causes FC errors. Which ROM date did it work with for you? Did you edit/change anything else? What kernel were you using? Thanks, let's keep up the good work!
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
I'm on the NB1 kernel and I was using the 2016311 build. I'm going to flash today's build and try again. Will report back in a few.

EDIT: If you don't disable the lockscreen before the screen locks you get relentless System UI FCs even after reboot. Just thought I'd throw that out there.

EDIT 2: At least for me anyways

EDIT 3: TeleService still FCs when trying to place a call but doesn't give me any crazy fiestas otherwise on the 2016311 build.

Random Idea: Would it be possible to bundle towelroot into the next build?

Random Idea Edit: Actually would it be possible to bundle towelroot, and pushbullet portal into the rom?
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
That'd be a good idea for transferring files less then 200 MB to PC. I use a micro SD adapter, but some may not have one. So this might help in the mean time while we are working on a fix for the external SD. By the way, I might have found the fix, but I'm not too sure. I'm at school so I can't test right now. Will test tonight when I get home.

EDIT: I found a nice post by Google that someone can read and do what I was gonna do. Just skim through it and test it out if possible. I'm really hoping this will work.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Currently uploading 0314 to media fire, then I will update the OP.

I added in TowelRoot, Pushbullet, and UltraExplorer (an opensource explorer like root explorer). I think you are right, these tools should make it a little easier for us to work, and we will remove them from the final build. Good idea [MENTION=5083211]Evant28[/MENTION] !

I did edit the build.prop so that the phone model number shows up in About phone.

Also, I did some testing:

The rom works with NB1, NC1, NI1, and NJ4, although with NJ4, I could not get the WiFi to work, even after three hot boots and two module flashes. It is good to know that we can use any of these Kernels.

I also edited my APN settings, which I thought was the problem, but it is not. Even on GPE, if I choose the wrong APN, I still have signal, but no data. On CM11, about phone shows the baseband as Unknown. I have been doing some reading and research, but still working on this. Flashing the modems after the rom does not make a difference, either. I am continuing to investigate.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Awesome! Looks great!
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Hopefully this build works, fingers crossed.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Putting the vold file in /system/bin/ seems to make the rom not boot. I just extracted the boot.img from the NB1_kernel.tar.md5 and I'm gonna see what happens when I use that instead of the stock CM boot.img

---------- Post added at 11:37 PM ---------- Previous post was at 11:29 PM ----------

What in the world. It changed nothing. [MENTION=7026648]AlaskaLinuxUser[/MENTION] is that the stock boot.img that came with the rom?
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Try the boot.img from jmsq's or joe's?
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Those roms don't have boot.img's. I'm curious if the cm build has the original boot.img or if alaska changed it.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
As you can see, the boot image from cm is about 6 MB, and nb1 is about 8 MB, so it is easy to tell which boot image is which. However, I do not believe SS flashes the kernel. All kernel flashing I have done with this phone has been with Odin.

I did at one point try putting the nc1 kernel in, but again, my findings was that SS did not actually flash the kernel. However, I found that if I took out the boot image all together, the ROM would fail to flash.

It should be the cm kernel in the load, but we can double check.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Both 20160313 and 20160314 have the cm kernel.
[AT&T Samsung Galaxy S 4 Android Development] nokia6686:
Waiting for good news!!
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
There are probably some things we won't be able to fix due to them being embedded in the CM kernel. Flashing the CM kernel in a .tar.md5 on Odin will probably just brick. I'm trying to think of something we can do here.

---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------

[MENTION=5417447]Legitsu[/MENTION] [MENTION=5848265]npjohnson[/MENTION] sorry to bother, but do you guys have any suggestions/actions we can take to fix the remaining problems?
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Thanks for taking the time to make an encouraging post! Be sure to check back regularly, we are making progress regularly! :D
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Yes, we cannot flash the CM kernel, the locked bootloader will simply not allow this. That is, of course, why we are making these work arounds. Good thought to get some more assistance! We'll keep working it, bound to get there soon! :)
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Easier temporary root.

I just found an easier way to provide a temporary root. I added Kingo Root to the rom. So flash the rom and modules as normal, and then once up and running use kingo root one click. Takes about 5 minutes, then you have root permission.

However, it is lost on reboot, but I could then just re-run kingo root on next boot and give myself temp root again. So, I think this is smoother/easier to use than flashing/installing/running/and updating binaries. ;)

I'll update the OP download link shortly.
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Sounds good but tr was pretty simple as well. Always good to simplify tho :)
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
You bet, the plus side here is you don't have to flash supersu, and you can re-root again after every reboot with one click and no flashing anything, if that makes sense. :D
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
True enough[emoji14]always good to simplify
[AT&T Samsung Galaxy S 4 Android Development] Joe-Tech:
I'm really glad you guys still supporting this device, finally a taste of CM. Nice job guys, keep up the good work:p
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Thanks Joe., but if it wasn't for you and jmsq we wouldn't have made this progress in so little time. You guys are the real champs :good:
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
I second that! :D
[AT&T Samsung Galaxy S 4 Android Development] Evant28:
Too late for a third?[emoji14]
[AT&T Samsung Galaxy S 4 Android Development] Joe-Tech:
No problem, it was a pleasure working for you guys. Good luck with the project, i can see success already:good::D:p
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Okay! I finally got my external sdcard mounted. That was way more painful than it should have been!

I currently am going through a two step process manually, but tomorrow I will script it into the rom (I hope).
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
External SD Card mounting automatically.

Okay, while the CM11-20160316-SS.zip is uploading to mediafire, I will post the work around for the External SD Card.

Ultimately, this is a work around, and we need to get the actual problem resolved, but for now it works.

So Touchwiz roms load the external SD card to /storage/extSdCard, and CM11 would like to load it to /storage/sdcard1. I can successfully auto mount the external sd card to /storage/extSdCard by adding

mount -t exfat -o rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=10058,gid=10058,fmask=0007,dmask=0007,allow_utime=0020,iocharset=utf8 /dev/block/mmcblk1p1 /storage/extSdCard

to /system/bin/sdcard. This simply mounts the external SD card to that position. However, you will need root permissions to view it with the CMFileManager etc.

I am still playing with Fuse, and I can successfully mount the external SD card to fuse, but for some reason, the fuse will not mount as it should. So I am still working on this. We can link /storage/extSdCard to /storage/sdcard1 but we would have to remount the root filesystem as rw, rather than ro, and make the /storage/sdcard1 folder so that we have a mount point.

All this is doable, but I am waiting to mount it to /storage/sdcard1 until I figure out the fuse thing. Getting it to load through fuse will enable the unprivileged (non-root) user to view the files, which would be ideal.

For now, however, once you root, you should be able to use your external sd card. I hope this will make moving files and keeping screenshots, etc., easier.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Team,

Next time that you are in the terminal app, can you check what your user id is as a normal user?

at the dollar prompt:

$id

It should return your UID and GID #'s. Mine is 10058, and I wanted to know if that is the first user, or if it randomly assigns a user id above 10000. Thanks.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Amazing work [MENTION=7026648]AlaskaLinuxUser[/MENTION]! Huge progress! Been taking tests all day at school so I haven't been able to check up. Downloading the new build right now, and I'm gonna be seeing what I can do about cellular service/phone.apk crash with Teleservices.apk.
[AT&T Samsung Galaxy S 4 Android Development] Sterben Pistole:
Mine is also 10058. I might have found a fix for data, but I'm still investigating. Will report back when I figure out.

EDIT: Nope, no luck with cellular service so far. I've got a couple more ideas, but I still need to look into them a bit more.
[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
So, Here are some thoughts on the cellular service. I am a Linux guy, not an Android guy, so perhaps by putting my thoughts and actions out loud, someone can help me with where things are going wrong.....

What we know:

Settings -> About Phone

IEMI = Unknown

Baseband = Unknown

Which usually points to a problem with EFS, but a comparison between the EFS as reported by the same phone in a stock rom and the CM11 rom shows that all the files are there, and that the partition is mounted and the sizes of the files are exactly the same.

So, CM11 is loading the right partition, but for some reason cannot read or use the information.

Some CM users that have had problems with IEMI and Baseband issues suggested flashing a different modem, as in the current modem may not be compatible. So, I flashed every modem known to the S4 AT&T variants, and it had no effect. (This took quite some time as I had to reboot, flash, reboot every time.) So it is not the modem variant, or one of them would/should have worked.

My limited understanding is that this must be a problem with librild or rild in general. Interesting to note, in the rom, there is a blobs folder with different sub-folders of verizon, gsm, and cdma. Each folder contains libril and secril. I would assume that the rom is supposed to choose (either at the time of install, or on the first run) which is the appropriate blob and load that. Conversely, there is already a libril and secril in the /system/bin/ folder of the rom. I did try replacing those with the GSM blob ones, but it did not help.

As I read through the build.prop, there are several options relating to radios and ril that vary dramatically between the GPE roms and the CM11 rom, leading me to believe that some property might need to be set.

Another note of interest, the CM11 settings shows the mobile cellular as "on" and gives it a blue toggle switch. You can turn it off, or set airplane mode and the icon will change to have an "x" by it for off. When on, there is no "x", indicating to me that it knows it is on, but can't use it for some odd reason.

As for other roms and phones, often if the apn settings are incorrect, or if you have selected cdma rather than gsm (international roms) or if you select 2g/3g/lte I have seen the cellular icon be empty because something is wrong. Most times, however, if the apn is wrong, the cellular icon still receives signal, but cannot receive data. So this is where I am stumped.

Further research is required. If anybody has any thoughts, I am definitely open to hearing them. :confused: