yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] titos1997:
I have network extender and seem that 1/2 the time when making or receiving a call it will show the call connected but I can't hear amything
[Verizon Samsung Galaxy S 4] scarmon25:
Honestly. It depends on if the bootloader ever gets cracked. That's what is holding it back. Unfortunately unless that happens it won't be possible unless someone figured out some ingenious way of side stepping the bootloader

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] HowardZ:
OK, I finally managed to build CM11.0 - had to switch from using Java 7 to using Java 6.
[Verizon Samsung Galaxy S 4] scarmon25:
So it seems CM11 nightlies will start tonight. From what I understand most all the main CM features are there. A few little things here and there aren't working but will be fixed in the upcoming builds.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] ahoslc:
Where did you get this news?
[Verizon Samsung Galaxy S 4] scarmon25:
IRC. https://groups.google.com/forum/m/#!topic/cyanogenmod-dev/GIRIkbVxDb0

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] ahoslc:
Didn't see our phone in the list
[Verizon Samsung Galaxy S 4] scarmon25:
Hmm. The way it was talked in there was we would be getting it too. But sure enough jf isn't in that list. Unless they just haven't updated it again.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] ahoslc:
So they were talking about the JF in chat?
[Verizon Samsung Galaxy S 4] scarmon25:
It was being discussed in the JF irc. Its possible I misunderstood what was being said. It wasn't an one on one conversation. There was several in the convo.

CM 10.2 | Latest Nightly | jfltevzw

---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------

I'm going to try and get some clarification.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] Lw00d:
hell yeah. xbox one on friday. now we are getting CM11 ,, thats what im talking about.. :highfive:
[Verizon Samsung Galaxy S 4] crossen0:
PS4 is already out... :p
[Verizon Samsung Galaxy S 4] Lw00d:
if i was a casual gamer , i guess i would be content with the ps4. :cool:

or maybe the wii u
[Verizon Samsung Galaxy S 4] crossen0:
Nothing causal about it
[Verizon Samsung Galaxy S 4] Schoat333:
So you are a hardcore gamer? Shouldn't you be playing on a PC? :p
[Verizon Samsung Galaxy S 4] Lw00d:
who said i didn't???

anyways. CM11 yesss
[Verizon Samsung Galaxy S 4] Schoat333:
Why so excited for the xbone then?
[Verizon Samsung Galaxy S 4] lecapitan:
Does anyone have issues with their phone getting really hot during games or while using the GPS?

My phone gets very hot, to the point where i feel pain when touching the screen.

My friend's S4 on stock touchwiz does not get hot at all, does touchwiz underclock the CPU?

I underclocked my CPU to half (1026MHz) and it does not get hot like before but I cannot imagine touchwiz underclocks the CPU that much.
[Verizon Samsung Galaxy S 4] HowardZ:
On the afternoon of 20NOV the sync took a long time. Seems a new kitkat revision is in CM-11.0
[Verizon Samsung Galaxy S 4] Zmnypit:
Looking & waiting
[Verizon Samsung Galaxy S 4] HowardZ:
Looks like it changed from KRT16M to KRT16S
[Verizon Samsung Galaxy S 4] scarmon25:
Well it looks like I was completely wrong on my info. Consider it an epic fail on my part. I haven't seen the first CM11 official build roll off just yet for any device. Possible there was a hiccup as they have a list of devices that should have got their build today. But even those haven't had one yet. I know its not far off. Truthfully every little of extra bit of time they take before launch just means a more solid build when it does drop.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] keithce:
If you're jonesing to running it:

unofficial-cm/files/Nightlies/jfltevzw/

In 11/21 they've re-introduced the quick settings tile configuration again! :)
[Verizon Samsung Galaxy S 4] scarmon25:
Sweet. What gapps are you using.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] kyuubi08:
Working in the newest build, and im having issues getting my phone to mount properly to my computer. I am getting error messages when i try to copy files over, and the on my phone it says that it has disconnected.
[Verizon Samsung Galaxy S 4] keithce:
PA Gapps
[Verizon Samsung Galaxy S 4] HowardZ:
here's my copy - I got it from invisiblek's web site

https://drive.google.com/file/d/0B88bR12MKYUKY0lzSzdtenhwRnM/edit?usp=sharing
[Verizon Samsung Galaxy S 4] Halfie53:
Only issue I'm having with this build is that I cant install any app bigger than 500MBs. It just says downloading but never actually downloads.
[Verizon Samsung Galaxy S 4] scarmon25:
I notice CM 10.2 RC1 is being built for a majority of devices today. Good things may be close if they follow suit like last time.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] djj624:
Just loaded up the experimental 11 build from the link above. Pretty good. Rotation is fixed as well as screen off when on a call. Only issue still going on is green lines on FFC pictures. Overall great build..
[Verizon Samsung Galaxy S 4] crossen0:
I just flashed it on top of euroskanks build and it seems a bit snappier. FFC isn't fully functional but that's not biggie when pretty much everything else works. This a fantastic start.
[Verizon Samsung Galaxy S 4] Lw00d:
just clean flash the new 11/23 nightly. they put a new boot animation.
[Verizon Samsung Galaxy S 4] scarmon25:
The CM 11 or 10.2 nightly.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] josephpalozzi:
Not sure if that was a question or not, but 10.2 nightly has a new boot animation with Cid's head.
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah that came out wrong. Didn't even notice that

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] Lw00d:
guys i just flash super su chainfire. now i dont have super user. how do i make super su work on CM10.2??
[Verizon Samsung Galaxy S 4] Ironclad Lou:
Try opening the supersu app, does it prompt you to update the binary? If so, select yes then normal. When it's done, reboot.
[Verizon Samsung Galaxy S 4] Lw00d:
no it doesnt

when i run TBup it says i lost root
[Verizon Samsung Galaxy S 4] Lw00d:
i remember something with deleting something with a file manager.
[Verizon Samsung Galaxy S 4] Ironclad Lou:
Not sure about that. Are you running the most recent supersu app? No update in the Play Store?
[Verizon Samsung Galaxy S 4] ThugosaurusRex:
I have a strange issue with the cm11 test build. When I call someone with Skype, they can't hear my voice.
[Verizon Samsung Galaxy S 4] FernBch:
Today I clean flashed the 11/24 build (and flashed the proper gapps package) and I have noticed a couple items.

The issue where it would freeze at the Samsung logo when rebooting has returned in earnest. Right now it seems to hang about every two to three reboots.

After the initial reboot and setup process the restore process did not seem to do everything it should have. I have things set to auto restore from my Google account, but the only thing that restored was my contacts. Everything else had to be manually entered.

As for the Google apps, the only things that installed was Gmail, search, and Google+. All the other apps (Maps and such) had to be manually installed from Google Play. I don't remember having to do so much on previous clean flashes.

Other than that I have not noticed anything else out of the ordinary, yet.
[Verizon Samsung Galaxy S 4] scarmon25:
So apparently the Google play edition. Got 4.4 source files released. Wonder if that will help the other S4s?

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] crossen0:
New boot ani is sick!
[Verizon Samsung Galaxy S 4] Schoat333:
Some of it should definitely help. Especially for getting the camera working.
[Verizon Samsung Galaxy S 4] scarmon25:
Something I've noticed with the camera if you open it and turn it too fast you get a partially transparent black bar across the screen. Closing and opening the camera fixes it. Its random but figured I would mention it.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] DipRip:
Anybody getting a black screen when you pull the phone away from your face during a call? Seems like sensor isn't working and I have to turn off and back on the screen
[Verizon Samsung Galaxy S 4] daventodd123:
Same thing happens to me. When I attempt to bring the screen back up, the screen never lights back up, so I'm dependent on the other caller to hang-up
[Verizon Samsung Galaxy S 4] scarmon25:
I haven't really noticed this on mine. On the few calls I have made I was able to use the keypad on call even after having at my face.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] iwearthebelt:
I don't think it has anything to do with the ROM. I'm still on stock 4.2.2 mdk and have the same issue with the black screen during calls.
[Verizon Samsung Galaxy S 4] dougmod:
I'm on liquidsmooth and have the exact same issue. Sounds like everyone implemented something that messed up the sensor
[Verizon Samsung Galaxy S 4] flyinj54:
Had the same issues on any ROM and figured out that it's not a ROM issue but a dirt/dust issue on my proximity sensor. The earpiece takes in dust which affects the sensor. Try blowing air into your earpiece right above the samsung logo. This fixed mine worth a shot for you guys with this issues.
[Verizon Samsung Galaxy S 4] riphamilton:
agreed. not a rom issue.

it's not limited to the proximity sensor; my ambient light sensor has never worked, so i have to manually adjust brightness if i'm outside. it's incredibly annoying, but i don't want to ask for a warranty replacement and be stuck with a locked bootloader.
[Verizon Samsung Galaxy S 4] scarmon25:
Started using the Google Experience Launcher on CM 10.2 and other than the big icons it is pretty slick. Runs like a champ.

CM 10.2 | Latest Nightly | jfltevzw
[Verizon Samsung Galaxy S 4] dougmod:
Some may report dust but flashing to a tw rom makes the proximity sensor work. Also why would everyone fail at the same time? There are people in the s3 forum reporting proximity sensor issues too
[Verizon Samsung Galaxy S 4] HowardZ:
This booting problem has me regretting having purchased the phone.

Also the locked down bootloader.

Also Samsung eliminating fastboot (or turning it into something very different)

My S4 is usually powered off, and its SIM card is in my Nexus 7 LTE, and using GrooveIP/GoogleVoice.
[Verizon Samsung Galaxy S 4] Schoat333:
Isn't the answer to that obvious? Clearly the CM code for the proximity sensor is slightly more sensitive than the stock TW code. Hense why dust is a problem on CM.

I have no issues with my screen turning on and off while in call.
[Verizon Samsung Galaxy S 4] dougmod:
I don't think it's clear because when was that merge? Has it always been more sensative? If people are reporting it across multiple roms that use cm and multiple phones, how can it be dust? it's fantastic you don't have an issue, we are just trying to figure it out becauseiit's much more widespread than someone with dust on their s4. Take a look in the s3, note 2 and I forums and you'll see it appears to be a Samsung issue. We will try to figure it out and see what happens
[Verizon Samsung Galaxy S 4] Schoat333:
Well that just further proves my point. These are all Samsung devices that probably utilize the same sensor. Sounds like the CM code for sensitivity needs to be tweaked a bit for Samsung proximity sensors.
[Verizon Samsung Galaxy S 4] DipRip:
Does anyone have issues dialing numbers after call has been connected? I cannot get the numbers to register if I am stuck talking to an automated machine. I have had this problem for a long time.

I thought it was because I use flex dial, but I turned it off and it still does not register.

Any ideas?
[Verizon Samsung Galaxy S 4] FernBch:
If I remember what I read a few pages back it has something to with whether or not you are dialing from the dial pad or the contacts list. Try dialing from the pad and then entering the additional info and see if it works for you.
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
I'm uploading a build as soon as its finished with fixed proximity, ambient light and gyroscope sensor.
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
ROM- https://drive.google.com/file/d/0B_Rfw845C8PWTW03bXg2c1lFMHc/edit?usp=sharing

MD5- 6143292dfb60392d8d03b0407bee9d3a
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
What the hell.. Ill give it a go.
[Verizon Samsung Galaxy S 4] ahoslc:
Is Nav bar in this build?
[Verizon Samsung Galaxy S 4] crossen0:
Running great!
[Verizon Samsung Galaxy S 4] saul1991:
Downloading it now and going to give it a try . Edit: flashed it wiped data/cache/dalvik and got nothing but fcs
[Verizon Samsung Galaxy S 4] fmxbrando:
I can not for the life of me get CM to work anymore. I wanted to come back to CM, but when I install it I can boot it fine the first time but subsequent reboots get stuck on the screen that says "Samsung Galaxy S4". When I am flashing, I do a full wipe (data, internal storage, both caches, etc.) and flash the rom without GAPPS then reboot. It works fine once but not the second time I try boot.
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
This is sort of common from what I've seen. Annoying but pulling the battery and rebooting does the trick.

Maybe you're using old gapps?
[Verizon Samsung Galaxy S 4] fmxbrando:
That doesn't seem to work either, I'm going to try to go back to stock and start over completely with a fresh recovery and everything.
[Verizon Samsung Galaxy S 4] ahoslc:
Let me know if that works I also have the issue a lot of the time.
[Verizon Samsung Galaxy S 4] Chris123NT:
What did you do to fix this? I was unaware of there being a sensor issue on 10.2. Sensors were just fixed on 11 but that was a whole different issue.
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
There wasn't an issue with 10.2. I was talking about 11.
[Verizon Samsung Galaxy S 4] ITGuy11:
It is your recovery that is the issue. Use TWRP 2.5.0.2, I bet it fixes your boot hangs. This specific version of TWRP is the only recovery that doesn't suffer from hanging at the Samsung screen.
[Verizon Samsung Galaxy S 4] ahoslc:
I use CWM I was told it does not have issues either.
[Verizon Samsung Galaxy S 4] DroidForLife33:
I flashed the build from yesterday. After my phone reboot my phone says it's roaming and I have no data. All I see is this in the notification bar. I called Verizon they side it was the sim card. I replaced it but nothing. I really don't what to lose my mdk build phone please help.
[Verizon Samsung Galaxy S 4] fmxbrando:
I updated my recovery and restored a stock rom then reflashed and finally got past the Samsung hang but I now have the roaming w/o data problem as well haha.. Not a fun day for me
[Verizon Samsung Galaxy S 4] D0CTOR:
I don't know what you did or are running, but you can always try reinstalling the radio. They're available here, If that doesn't do it, you can always Odin back to the build you were on before these problems. AFAIK all builds are available from Samsung.
[Verizon Samsung Galaxy S 4] DroidForLife33:
I flashed the mdk radio using twrp and still nothing I still get the same roaming message.
[Verizon Samsung Galaxy S 4] scarmon25:
I had the same issue. Went into mobile networks and changed CDMA subscription to RUIM/SIM and rebooted. Works fine now

---------- Post added at 01:50 AM ---------- Previous post was at 01:50 AM ----------

Also make sure roaming is set to auto and network mode is CDMA/LTE/EVDO
[Verizon Samsung Galaxy S 4] DroidForLife33:
Thanks so much for your help.. I did not what get a new phone with new build:)
[Verizon Samsung Galaxy S 4] fmxbrando:
Did you get it fixed? I used Odin to get back to stock and still can't get it to work.
[Verizon Samsung Galaxy S 4] scarmon25:
I had to flash CM 10.2 and make the changes in there for it to fix. Then after that it was fine. The biggest part is that CDMA subscription. Changing it from NV to RUIM/SIM is what really fixed it for me. Somehow it got set to that by default.
[Verizon Samsung Galaxy S 4] DroidForLife33:
Ya you'll have to root and install twrp then flash cm10.2. It worked great.
[Verizon Samsung Galaxy S 4] heath2805:
Apparently I flashed cm10.2 earlier today and had the same problems. Odin'd back to stock and still had issues. Tested my sim and it passed on other devices. So it turns out flashing cm10.2 again and changing CDMA subscription fixed everything. Genius man thanks!
[Verizon Samsung Galaxy S 4] keith.mcintyre26:
So insanity. Much not coolness. I'm sorry guys- not sure what happened to your phones. I have never had an issue with these builds but I have a weird flashing ritual because qualcomm nv items are prissy as hell. I turn off WiFi, get a hard lock on GPS and reboot recovery from maps. 10 million strongggggg...and growing.
[Verizon Samsung Galaxy S 4] saul1991:
i got the same issue going on man. i odin back to stock and still roaming it gets stuck in a wait till phone activates and phone doesnt do anything. i cant go into settings or anything...

---------- Post added at 05:49 AM ---------- Previous post was at 05:43 AM ----------

how do i go into those settings?
[Verizon Samsung Galaxy S 4] heath2805:
You need to re-root, re-flash cm10.2 nightly and go into mobile network settings like Scarmon25 said. CDMA subscription needs to be changed from NV to RUIM/SIM. You won't see those settings on stock TW builds.
[Verizon Samsung Galaxy S 4] scarmon25:
Its under settings - more - mobile networks. Then set CDMA subscription to RUIM/SIM and Network Mode to CDMA+LTE/EVDO
[Verizon Samsung Galaxy S 4] saul1991:
i get tstuck here. cant go into settings or hang up call

---------- Post added at 05:54 AM ---------- Previous post was at 05:53 AM ----------

i cant re root i get stuck here
[Verizon Samsung Galaxy S 4] scarmon25:
Check. Post above yours.
[Verizon Samsung Galaxy S 4] saul1991:
is there any way to bypass this screeen? i cant reroot the phone gets stuck there
[Verizon Samsung Galaxy S 4] fmxbrando:
So I might be ****ed.. the stock rom I flashed with Odin was ME7 not MDK..
[Verizon Samsung Galaxy S 4] scarmon25:
Remove the sim
[Verizon Samsung Galaxy S 4] saul1991:
ok so after reroot and then flash cm and try swtiching it?
[Verizon Samsung Galaxy S 4] scarmon25:
What thread did you get the ROM from?
[Verizon Samsung Galaxy S 4] saul1991:
ahhh man i feel you like wtf im odin try to fix it and send it to verizon
[Verizon Samsung Galaxy S 4] scarmon25:
Reroot. Flash cm and put the Sim back in. Then change the settings and reboot. Should be good.
[Verizon Samsung Galaxy S 4] saul1991:
thanks man im going to try be back in a few
[Verizon Samsung Galaxy S 4] fmxbrando:
It was from when I unbricked a friend's, I think from http://xdaforums.com/showthread.php?t=2301259. I didn't realize until after.
[Verizon Samsung Galaxy S 4] scarmon25:
Seems to be some confusion on how to fix this roaming issue. You need to get back on CM 10.2. If you're on stock pull the Sim card to get past the activation screen. Root it and then flash cm. Put the Sim back in and boot it up. Once on CM go to settings-more-mobile networks. Chang CDMA subscription to RUIM/SIM. Reboot and profit.

---------- Post added at 06:14 AM ---------- Previous post was at 06:13 AM ----------

That may not have included aboot. If it didn't you're fine. Unzip and zee
[Verizon Samsung Galaxy S 4] heath2805:
Its a shame there isn't an app we can install on stock TW to be able to change CDMA subscription.
[Verizon Samsung Galaxy S 4] fmxbrando:
I unzipped it.. top file is aboot.mbn
[Verizon Samsung Galaxy S 4] saul1991:
[ROM][Official][4.3] CyanogenMod 10.2 Nightlies for the Verizon Galaxy S4

thanks man it sort of worked but i still dont have 4g it manage to activate by dialing *228 but i still dont get any data on it i cant text. ok it connected to 3g but cant make phone calls lol

UPDATE: thanks man it worked i can make calls lol. still waiting for my 4g stuck in 3g. thanks again.
[Verizon Samsung Galaxy S 4] fmxbrando:
Well after hours of agony, I found a safestrappable ROM with this option (Google Play Edition for VZW) and was able to switch from NV to RUIM/SIM. I rebooted and got a text message which is a very good sign I guess. I will update when I get data and 4G back.
[Verizon Samsung Galaxy S 4] heath2805:
If you dialied *228 you probably fried your Sim. Dialing that will force it in a 3G signal only. *228 is only for 3G phones.
[Verizon Samsung Galaxy S 4] saul1991:
Ahhhhhhgg wtf lol :( thanks man
[Verizon Samsung Galaxy S 4] heath2805:
lol No prob, were you able to change those CDMA subscription settings back to RUIM/SIM?

Edit: You may be able to call Verizon from another number and see if they can send a PRL update( Preferred Roaming List) to see if that fixes your SIM. If not, SIM cards are free @ corporate stores. Retail stores will charge a fee for them. Hope this helps :)
[Verizon Samsung Galaxy S 4] saul1991:
Yeah I manage to switch them I can text and make calls fine. just that I messed up by dialing *228. There's a corporate store up here where I live so I'll end up going over there for a sim card. The *227 won't mess up my data right?
[Verizon Samsung Galaxy S 4] heath2805:
Don't think it will. Just pushes PRL in 3G only. New SIM should work great. Just remember to never dial that again lol 4GLTE devices update PRL automatically.
[Verizon Samsung Galaxy S 4] scarmon25:
Make sure you change your roaming to automatic
[Verizon Samsung Galaxy S 4] saul1991:
Thanks for the help appreciate it

---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------

Thanks for the help. I was freaking out yesterday
[Verizon Samsung Galaxy S 4] scarmon25:
No prob. I was too when it started calling into USCC to activate. Even after I odined. The issue is when it gets set to NV then it kills it. Even if you Odin to stock that setting still sticks. So until you go back and change it it won't work right. Crazy I know but as long as you change it and change roaming to automatic as well as set it to CDMA+LTE/EVDO then you should be good to go. But yes I was freaking out majorly.
[Verizon Samsung Galaxy S 4] saul1991:
so when im in stock i have 4g everything is good but as soon as i flash cm the issues restart and even after switching the settings it still roams. Im going to stay away from cm for a while lol
[Verizon Samsung Galaxy S 4] heath2805:
lol I'm actually running 11-30 build with no issues. Did you get a new SIM?
[Verizon Samsung Galaxy S 4] saul1991:
Not yet verizon is sending me a replacement ill take it in to their stores and have them activate it. Hopefully it doesnt come updated already.
[Verizon Samsung Galaxy S 4] scarmon25:
The Sim wouldn't have any effect on the build.
[Verizon Samsung Galaxy S 4] rpitera:
Much thanks to all for the activation help

I was freaking out that I had bricked my S4, but thanks to all the posts here I was able to get things up and running again. I was coming from Hyperdrive and going back to my old friend CM and couldn't understand what had happened. Now here's the weird thing; in between restores from backups of HD and reflashes of the last nightly something odd has happened. My unlock counter seems to have reset itself. I no longer have the Sammy custom rom banner, but I can still reboot into CWM (just checked again to make sure) and I still have root. It now shows the standard Samsung S4 boot logo.

Not sure how this happened as I really didn't do anything during all of this except the usual wipes and formatting the system partition. I just thought I'd mention this in case it is helpful to someone or if I somehow stumbled onto some method of resetting the counter. The only thing that I did do was to restore to a nandroid I had that I made right after rooting and unlocking. (I did the root/unlock back in the day before the ME7 update screwed everybody up). If there's any info I can provide that might help someone, let me know via PM and I'll be glad to tell you what I know.

Nice to be back in business; for 24hrs I had to do an ESN swap and use my old HTC incredible - ironically enough it was running an old CM build! LOL... Thanks again!