yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] npjohnson:
Ok, some good & bad news;

1. UMS cannot be implemented and it is Verizon's fault. I've spent. Literally all day on this.

Explanation here:

So, the at the kernel level, Verizon replaced the UMS service with the stupid "Verizon Wireless CD Driver" service, which re-routes all attempts at UMS through that, the reason this works for the ATT version is that the ATT version doesn't have that stupid CD mode built in their kernel.

Due to this, UMS /WORKS/, but cannot access the SD Card, as the stupid thing just shows up as a black CD. Ugh.

Possible Fixes:

- Disabling the Verizon CD via a kernel module... do you think this would be possible/would you know where to start [MENTION=4939386]Surge1223[/MENTION]?

- Finding a way to reroute the Verizon CD to the SDCARD (unlikely)

- A working MTP kernel Module (even more unlikely)

2. WiFiAP is working via the app by [MENTION=4168602]klabit87[/MENTION]! Will include when 1.3 is ready.

3. Init.d appears to be working after [MENTION=4168602]klabit87[/MENTION] fix.

4. For the life of me, I can't get the K01shutdown script to run at reboot! I have tried so many solutions/fixes, and just can't get it. This is the one that's purpose is to unload the WiFi module to kill the need to soft reboot for WiFi.

5. PRL update wont stick in the ROM zip, tried many times, it, however, does work by calling *228 option 2 in the dialer.

Any ideas anybody?

Also, any requests for 1.3 that I may have missed?/Any new ideas? Now would be the time to let me know *wink*
[Verizon Samsung Galaxy S 4] klabit87:
Surge did mention that mtp can be achieved through an insecure module in the nc5 source.

I have tried and tried to compile the kernel and spit out as many .ko modules as I can but it appears I just can't seem to set the kernel .config options quite right.

If you would like to look at my errors to see what I may be overlooking I have a screenshot of the terminal output.
[Verizon Samsung Galaxy S 4] npjohnson:
If you wouldn't mind, could I see it?
[Verizon Samsung Galaxy S 4] Legitsu:
[MENTION=5848265]npjohnson[/MENTION]

instead of trying to make the init.d script work why not just edit the command used for the roms reboot menu

you could maby replace the reboot command with a symlinkd shell script containing the modunload command followed by the actual reboot

,else somebody may need to write a xposed module
[Verizon Samsung Galaxy S 4] klabit87:
Well I said I had a screenshot. Lol

I took one but it was of an error that I had already fixed.

I am mobile right now so I will try to compile and see about the errors once I get home. I will send a screenshot as soon as I can as I'm sure there probably will be.

Instead of holding you up though we could have the mtp fix included in a flashable zip.

Then add it to your next version.
[Verizon Samsung Galaxy S 4] Legitsu:
We have the MTP MODULES we can load them the problem is the API is different compiling them does us no good we already have access to the touchwiz MTP Modules the problem is rom-side,ASOP handles a bunch of stuff different then VZW-TOUCHWIZZ as [MENTION=5848265]npjohnson[/MENTION] is finding out

and the end of the day there is no quick fix here if we really want stuff to function 100%,then its gonna be a lot of code-diffing and writing compatibility fixes into the ASOP Codebase
[Verizon Samsung Galaxy S 4] klabit87:
Ah ok.

I'm sure it's because of its nature but I am able to load the conservative cpu governor while running aosp.

As far as I understand it was compiled for tw correct?

If you don't mind could you link me to the mtp modules?

I would like to look at them and try a few things.

Thanks.
[Verizon Samsung Galaxy S 4] Legitsu:
The Governor API is pretty standardized that doesn't get messed with,thats a core kernel level thing

the modules you can rip right from this rom;

http://www.androidfilehost.com/?fid=23487008491962522
[Verizon Samsung Galaxy S 4] klabit87:
That's what I figured.

But doesn't hurt to try a few things.

Thanks for the link.
[Verizon Samsung Galaxy S 4] Legitsu:
the otherway around it which what [MENTION=4939386]Surge1223[/MENTION] was talking about was to take the NC5 source modify the code for the mtp modules to be asop compatible then it would work,I haven't looked into it but it doesn't seem like it would be to much patching just the relavent API's for MTP
[Verizon Samsung Galaxy S 4] klabit87:
If memory serves correct there are some modules in the source that did not make it in the final build.

The governor being one of them?
[Verizon Samsung Galaxy S 4] Legitsu:
no idea I been "out of the game" for too long
[Verizon Samsung Galaxy S 4] klabit87:
That's why I want to build from source and push out as many standalone modules as I can.

There could quite possibly be more modules that didn't make the final cut.
[Verizon Samsung Galaxy S 4] Legitsu:
I doubt it,there is nothing extra in the source released by Samsung for NC5 NOR NK1,Not that I have seen anyway
[Verizon Samsung Galaxy S 4] jam0688:
So assuming mtp fixing is in the works, what's the verdict on 1.3 [MENTION=5848265]npjohnson[/MENTION]?
[Verizon Samsung Galaxy S 4] Legitsu:
MTP Is awhile off yet ... don't expect it to make 1.3
[Verizon Samsung Galaxy S 4] jam0688:
I don't believe it will myself either. I agree with klabit87 though I think 1.3 should be released that way everyone has an idea of what he's working on. With the issues in 1.2 is was hard to get a good idea of things. Overall it's an amazing rom to say the least.
[Verizon Samsung Galaxy S 4] npjohnson:
That's a good idea (the symlink), I'll try that. I'm uploading 1.3 right now, so I'll just work on that and MTP for 1.4

Not in 1.3, but definitely possible, requires more research & work.

Honestly, 1.3 carries few new features, but includes a bunch of new under the hood optimizations, and stability fixes, as well as WiFi AP, init.d, and Exchange support in GMail.

Note: 1.3 will now require flashing your specific modules, and, depending on your setup, the NC2-Wifi Fix.

I decided to remove the NC2 WiFi Fix as part of the ROM install, because, users just ended up flashing the Non-HLOS's and Modems back to normal, and that was conflicting with the NC2 Hidden.IMG, so, if you can't get WiFi working, you're gonna have to flash your modules, and then if that doesn't work, the NC2-Wifi Fix.

The ROM is also now compatible with all JFLTExxx devices (ATT, VZW, TMO, SPR, etc.), and many I-950x series devices, as it no longer flashes device specific partitions, and it includes some other generic device set drivers.
[Verizon Samsung Galaxy S 4] Legitsu:
sweet ill flash it as soon as its up

what did you end up patching for the LTE ?,just out of curiosity
[Verizon Samsung Galaxy S 4] jam0688:
That's what im talking about man! You're awesome. I'm sure yall will work out the mtp issue though and get it going. Keep up the good work
[Verizon Samsung Galaxy S 4] npjohnson:
Honestly, I dropped the NC2-Wifi Fix altogether from the installer Zip, and then manually used the dialer to update PRL (*228 option 2)

I think the LTE handoff issue was a combination of how the WiFi Fix patches the Hidden.IMG (Which surprisingly does more than I expected it would've...), and after some messing around, I think the ROM should default to Global mode (it does for me), and I pulled an old CM commit from the S3 that was about how vigorous the LTE handoff would be, if I can refind the Gerrit link, I'll post it.

I've changed so many other things though.... its really hard to tell specifically what stabilized it. But on my end at least, its working better than it was.

Addition: 378/684 MB Uploaded.... :p
[Verizon Samsung Galaxy S 4] damnyouwaffles:
So should I cancel my download of 1.2 that's going on right now??
[Verizon Samsung Galaxy S 4] npjohnson:
Haha. Yes. Your choice though.
[Verizon Samsung Galaxy S 4] Legitsu:
is the installer going to restore the proper hidden.img ,if you are post wifi fix or do we need to odin back to stock again ...
[Verizon Samsung Galaxy S 4] npjohnson:
Sigh... Damnit. Slight oversight... ODIN may be required if you are having Cell issues, if not, then don't ODIN.
[Verizon Samsung Galaxy S 4] Legitsu:
*downloads odin full-wipe package AGAIN* ...

anyway you could package the hidden.img for NC5 as a flash-able .zip ?
[Verizon Samsung Galaxy S 4] npjohnson:
I don't have it, and mine is *tainted* as well :p, if someone wants to upload it, I'll definitely package it, though honestly, after examining the NC2 Fix, it patched a lot more than that, if you get the chance, look through it some time, I've begun to wonder how much of it is necessary.
[Verizon Samsung Galaxy S 4] Legitsu:
I knew the wifi fix was part of why things where so screwy its why I was so "adamant" about making sure everything is a version match ;)

o well just means a extra 25m to get odin'd back to stock NC5 Re-rooted and re-safestrapped

busybox has been giving me fits every-time I try and install it

I think from now on it should be the 'recommendation' that everybody start from NC5

edit:nm I forgot I had a copy already downloaded let me see if I can rip the hidden.img.ext4 out of it

edit2:yep ... np pming you

edit3: huh pm wont send

http://cl.ly/ZtC1/download/hidden.img.ext4
[Verizon Samsung Galaxy S 4] npjohnson:
I got the PM, thanks. I'm hitting the hay for tonight, but will make a flushable tomorrow.

PS... Its Live!
[Verizon Samsung Galaxy S 4] npjohnson:
v1.3 is live, see changelog

If you are having WiFi/data/voice issues, then Odin to stock, and flash v1.3, then your modules.

If everything is working & you are currently on KitPop v1.2, then dirty flashing it /should/ work fine (no guarantees), no need for your modules.

If you are a new user, follow the install instructions in the OP.
[Verizon Samsung Galaxy S 4] will1417721:
Problems

So I was running v 1.2 without any problems then 1.3 was released and I did odin to stock NC5 and then went from there and flashed in my stock slot like I did previously. I can't disable the navbar on the bottom and re-enable captive keys and there are a lot of apps that have no icons. Other than that everything work fine.
[Verizon Samsung Galaxy S 4] jam0688:
rom flashes fine. only issue im having is getting mobile data. wifi works fine as does everything else. any ideas?
[Verizon Samsung Galaxy S 4] klabit87:
Apps with no icons? Sounds like selinux is enforcing.

Have you tried the selinux changer?
[Verizon Samsung Galaxy S 4] Jraider44:
Anybody have any thoughts on 1.3 yet? Really want to try the rom out...

Also is there any benefit to using NC5 versus NK1 (Im on NK1, but can downgrade) ?

Are you guys having luck flashing to the stock slot or to a ROm slot in safestrap?

Sorry for the questions, thanks in advance!
[Verizon Samsung Galaxy S 4] skepticmisfit:
dude this is awesome, theoretically I should be able to be freed of touchwiz on nk1 (a seemingly impossible task up until this point)

but a question: do I need to flash WiFi modules with this and/or a wifi fix module? Or does this ROM come with said modules?

---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------

also will this ROM have feature parity with Joe-Tech's? and will updates to your ROM be pretty similar in time frame to updates to his ROM?
[Verizon Samsung Galaxy S 4] npjohnson:
Yes. That's the goal. (:

About the modules, make SURE to flash the NK1 SELinux fix. And /theoretically/ WiFi and Data should be good to go. The most you would need would be the NK1 modules (No WiFi fix!), but try without them first.
[Verizon Samsung Galaxy S 4] npjohnson:
On the subject of Pure-Nexus.

I used his as a base. It will be updated just as frequently, if not a bit more, depends on how much free time I have. Though, the feature set may be a tad different In the future, if you see something in his ROM that you like, let me know and I'll talk to him\see what I can do.

Let me know of your experience on NK1. I've had a report that all was good, but 2 user testimonials is always better than one. (:
[Verizon Samsung Galaxy S 4] klabit87:
I'm on NC5 so I flashed the NC5 nonhlos modem zip after the rom since the NK1 would nuke my wifi.

Wifi worked no problems but I could never get mobile data to work. No 4g or 3g.

Also when I placed a phone call the dialer closed out but the call was still in progress.

So I opened the dialer again and selected return to call and it closed out and sent me to the home screen.

Not sure what is going on there but thought you should know.

Also I'm on 3.72 safestrap, shouldn't make a difference since I don't really care to use slots I just use the stock slot.

Thanks for the rom though great work! I look forward to testing further versions as they progress.
[Verizon Samsung Galaxy S 4] npjohnson:
Actually 3.72 is EXACTLY why. It corrupts the Non-HLOS partition when flashing, that was one of the major upgrades made by 3.75. Upgrade to 3.75 and try again. That should solve it, but then don't flash the NC5 Non-HLOS.

Edit: A common confusion is that that package (named NC5 Non-HLOS only includes the Non-HLOS, it doesn't, it includes the Non-HLOS, Modem & Hidden.IMG, and that's for the modem packages by Surge, but if you use the ones by Giggle, it also flashes modules and a lockscreen fix.) Moral of the story, know what is in the package, as some packages contain more than they say.
[Verizon Samsung Galaxy S 4] klabit87:
oh ok....didnt realize that.

gonna try that real quick then.

thanks
[Verizon Samsung Galaxy S 4] npjohnson:
The sad part is that to recover from that may require ODIN. Never been in that specific situation, so your treading new territory.;)
[Verizon Samsung Galaxy S 4] Michaelmansour1997:
Downloading Now :))

Thanks for this beautiful rom, im downloading now and will let you know how it goes!
[Verizon Samsung Galaxy S 4] klabit87:
I don't mind. For the sake of development!:fingers-crossed:
[Verizon Samsung Galaxy S 4] npjohnson:
Wish more people had this attitude! Thanks man. Hey, I noticed that you have ME7 Bootloader in your signature, is that accurate? If so, are you running the NC5 Kernel? What's you partition setup?
[Verizon Samsung Galaxy S 4] npjohnson:
New poll in the OP! Let me know what you want.
[Verizon Samsung Galaxy S 4] skepticmisfit:
so after flashing and setting up the ROM (only needing the ROM, nk1 selinux fix, and supersu [didn't want to use towelroot])

WiFi did work doing that. however,gps is broken. not too big a deal, I don't use gps that often. but I'm going to try and fix it eventually
[Verizon Samsung Galaxy S 4] npjohnson:
Good to hear. I'm looking into GPS
[Verizon Samsung Galaxy S 4] skepticmisfit:
I think the fix for GPS is:

go into a ROM where GPS was working, then turn it on and test it there. leave the GPS on, then reboot into ss and restore the gpe ROM.
[Verizon Samsung Galaxy S 4] npjohnson:
I know that that works, but would prefer to isolate an easier way
[Verizon Samsung Galaxy S 4] npjohnson:
Just tested on NC5 on my side and GPS is working. I'll reupgrade to NK1 and mess with it tomorrow.
[Verizon Samsung Galaxy S 4] klabit87:
Yeah I used the Surge method to upgrade long time ago

So I have the MJ7 bootloader, NC5 kernel and now the NK1 modem.

But I flashed again and this time only the rom plus the supersu 2.4 and still no 4g. :(

wifi works but no 4g or 3g not sure what else to try right now
[Verizon Samsung Galaxy S 4] npjohnson:
It probably has something to do with the mismatched partitions. If I were you, I'd ODIN up to NC5 and start from there, that's where I am, and I'm loving it. Feel free to fiddle with it and post your findings, but I can't promise anything unless you came from full NK1 or full NC5.

You could attempt to use the NC5 WiFi fix and see if that changes something? That's the only ideas I have for that.
[Verizon Samsung Galaxy S 4] klabit87:
ok I will probably just bite the bullet and odin to NC5 and start fresh.

Looking at getting a new phone this summer anyways and doesnt look like the bootloader will be cracked anytime soon

thanks for the help

will continue tomorrow.
[Verizon Samsung Galaxy S 4] npjohnson:
I actually got and love the Nexus 6, just FYI though.

If you are gonna go up, look into possibly just going to NK1 (newest), check out the how to root thread and see if you want to, either should work.
[Verizon Samsung Galaxy S 4] will1417721:
I didn't know that could cause the problem. I'll try a reflash tonight.
[Verizon Samsung Galaxy S 4] npjohnson:
Are you on NK1? Did u flash the SELinux Fix?
[Verizon Samsung Galaxy S 4] npjohnson:
APNFix. And then one soft reboot
[Verizon Samsung Galaxy S 4] npjohnson:
Your choice, I have people on NC5 who say it works well as well as people on NK1, the known issues are the same on both, and in the WIP section of the OP. Only thing with NK1, is that if you need SELinux Permissive, it does not switch.
[Verizon Samsung Galaxy S 4] klabit87:
Decided to flash rom in slot 1 this morning.

Backup, flash, ---no mobile data.

Get 3g but no lte.

Start odin.

Should have checked thread before flashing lol

Oh well
[Verizon Samsung Galaxy S 4] npjohnson:
I've had no success in ROM slots.... Period. A lot of success in stock slot though.
[Verizon Samsung Galaxy S 4] klabit87:
Ok Thanks for the heads up.

it appears even odin hasnt brought 4g back.

gonna look into the hidden network settings in a minute once i root again
[Verizon Samsung Galaxy S 4] npjohnson:
Well, the ROM does nothing that would be persistent across odin. So it wither HW or maybe the tower is under maitnence.
[Verizon Samsung Galaxy S 4] klabit87:
yeah im still digging.

Have the emergency wipe odin file downloading also.

I used the no-wipe im sure that didnt help matters

edit: finally got it running back with Advanced Signal Status.
[Verizon Samsung Galaxy S 4] npjohnson:
Ahh. That's why.
[Verizon Samsung Galaxy S 4] klabit87:
For any of those that have lost mobile data when flashing 1.3 might try using advanced signal status.

You can go in advanced settings and toggle through many options that are not available in stock.

I'm gonna play with it once i get my backup restored.
[Verizon Samsung Galaxy S 4] Legitsu:
Upgraded to 1.3 this morning didn't have time to odin back,no change,the rom settings still aren't right ( i Did use heimdal to flash the hidden.img tho)

I am gonna be a bit jerk for a min here sorry in advance. <3

forgive me for asking are you testing using Verizon simcard,if not then that's 50% of the issue

I think making duel mode is gonna be the trick here ...

CDMA2000 + LTE /EVDO+AUTO-PRL,

Meaning it needs to be locked to the above and nothing else YES Global mode should work and it should switch but it doesn't .,...

global means GSM GSM Doesn't work like it should with this kernel ...

check this out this thread

http://xdaforums.com/showthread.php?t=1680567

that way MMS Works without weird patches ,And things should switch flawlessly

at the expense of some battery life

I think the trick is gonna be making duel mode work and keeping The "triple threat" radio active all the time its gonna suck battery but it is what it is ..

I know it should't make a difference but it does > blame Verizon for there wacky code hacks

If I force global mode on the stock touchwiz it displays the same 'symptoms' as kitpop
[Verizon Samsung Galaxy S 4] klabit87:
I agree!

It does appear that we would need all radios to be active in order to keep a stable connection.

I think the battery drain would come into play if we had bad or low signal though
[Verizon Samsung Galaxy S 4] Legitsu:
far easier said then done the lack of duel mode would explain why we have Mms issues,And some of the switching issues

I am really starting to develop a hate for verzion, I am thinking of switching to sprint ...
[Verizon Samsung Galaxy S 4] npjohnson:
Well. Sort of, I have an activated (Voice & Data) TMO Card, and an activated VZW Sim (Voice only, but pulls up the VZW Connect page in Chrome if data is working) , so that could very possibly be the issue. I always test both, but I suppose that not having a fully activated VZW SIM could cause my readout to be a bit different.

I didn't think that was a jerk thing to say BTW. Valid question.

I'm in agreement, and will see what I can do about dual mode soon. I feel bad that users are experiencing these issues with data, and will read through the referenced threads and see what I can do. The issue at hand is that this is a very finicky setup as is, I actually ran into a bootloop in testing 1.3 over attempting to get the PRL update to stick. (Just to show what I'm dealing with).

Question, have you tried manually doing PRL via *228 option 2?
[Verizon Samsung Galaxy S 4] klabit87:
delete still testing

lost calls and text but had data
[Verizon Samsung Galaxy S 4] Legitsu:
my prl didn't need to be updated most likely because I did a dirty flash ...

never use *228 on a Verizon Phone 4GLTE 1. you don't need it 2. if the simcard is not activated it will trash it ..used cause the simcard to "retire" at midnight
[Verizon Samsung Galaxy S 4] abe.froman:
I've made this mistake before and had to get a new sim card from Verizon to get 4g back.
[Verizon Samsung Galaxy S 4] Legitsu:
They "fixxed" it so it will simply refuse to program if the card is already active
[Verizon Samsung Galaxy S 4] klabit87:
I forgot about that part. I actually did succeed in updateing the prl via *228 op2

So i guess i tanked my sim?

I can get 3g and calls and such working but no lte
[Verizon Samsung Galaxy S 4] abe.froman:
I'm glad they fixed that. The sim card I ruined using *228 was in my old GS3.
[Verizon Samsung Galaxy S 4] Legitsu:
you can try a new simcard .///
[Verizon Samsung Galaxy S 4] npjohnson:
Oh my god. I apologize for that, when I did it, I didn't loose the 4G reading, buts that could be due to my lack of activation. I strongly apologize.

Oops. Everybody makes mistakes. :p
[Verizon Samsung Galaxy S 4] Legitsu:
it should't be a issue on TW roms either way .. .. as for ASOP ... no idea

my simcard should be fine because I never dialed *228

you can try odining back to stock and then dialing *2767*3855#

I am gonna do a full-odin in a min here my self ill verify that that dial er code still works
[Verizon Samsung Galaxy S 4] klabit87:
*228 option 2 does kill your sim card in aosp for sure lol

Don't even worry about it. Things happen especially when treading in uncharted waters.

got a new one and im up and running everything good to go now

---------- Post added at 01:52 PM ---------- Previous post was at 01:35 PM ----------

if anybody is on kitpop 1.3 and cant get calls,text,data working properly would you try getting Advance Signal Status

Scroll to bottom,

Go to Additional Info

Select Phone info

Scroll down to "Set preferred network type:"

change the network type to "LTE/GSM/CDMA auto (PRL)

See if that helps any.

I may possibly have one confirmed case where it did fix the problems

but he has very little to almost no lte service in his area.

I would test myself but i need to get everything setup back to where i was before.
[Verizon Samsung Galaxy S 4] jhr5474:
Thankful

Glad I am a reader and I DID NOT flash this rom. I will wait for the 1.4, read some more and see if data issues get fixed. Thanks for all of the posting guys, it is nice to not mess my phone up because I have to blindly flash a rom. If you guys didnt post all of this I would have never known. For all you non readers, get a clue, reading the forums is half the batlle with roms.
[Verizon Samsung Galaxy S 4] npjohnson:
Well, the only issue we have had that prevents every day use is the *288 problem, and that only affected 2 users that I know off b4 we nixed it.

The only known issue is it doesn't like to connect to super weak LTE signals. But LTE DOES work.
[Verizon Samsung Galaxy S 4] jhr5474:
COOL

I will flash later today then. I use page plus. I tried the *228 thing last night on empty galaxy because I had connection problems last night and it just hung there at dialer forever then greyed out the dialer. I rebooted and everything is fine.
[Verizon Samsung Galaxy S 4] klabit87:
[MENTION=5848265]npjohnson[/MENTION] are the build.prop changes no longer necessary to remove the softkeys??

I'm looking and cant seem to find the quemu line