yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] mixxy:
is it worth it to buy official equipment for wireless charging? no

is it worth it if you buy after market? yes! less than $25 bucks and you can have a wireless charger. yes it won't charge as fast as a plugged in charger but if you are charging overnight and want to protect your usb ports, check emails thru the night (i do it for business), and don't necessarily like wires on the side of your bed, i can't see a reason not to.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
I can definitely agree to that. I like a wire free mess on my night stand as well.
[T-Mobile Samsung Galaxy Note 3] ROADKING17:
Comes in handy when charging at night no need for a cable... Wireless charger is Shhhhnice!
[T-Mobile Samsung Galaxy Note 3] XxLostSoulxX:
It's not so wireless when you pick up the phone and stops charging. Again what's the point if you're not going to use the phone how was the cable gonna mess anything up.
[T-Mobile Samsung Galaxy Note 3] ROADKING17:
Easier way to charge at my desk or night stand maybe I don't wanna bend down and grab the wire then plug it in, call me lazy but I like it. I had a s3 and s4 before try plugging in the wire into the device without turning the lights on in the dark, my s3 was cracked from the charging port area of phone all because it was dark and I'm trying to plug it in
[T-Mobile Samsung Galaxy Note 3] phil.culler:
Can you link to the kit if you don't mind? I'm a bit paranoid about most aftermarket power accessories. Nice to hear about one that works.
[T-Mobile Samsung Galaxy Note 3] oka1:
From the moderator

To all in this thread post respectfully or do not post, if you are unsure what respectfully means look it up in a dictionary.

Thank you ~~ oka1
[T-Mobile Samsung Galaxy Note 3] inflewence:
No problem http://www.amazon.com/Charging-Wire...arging+Pad+and+Wireless+Charging+Receiver ...charger

I don't have some of the cons that the reviews talk about. My phone doesn't get really hot. I don't have the little bump in the back cover. It doesn't come with a plug but does come with the USB cord. I just use the original plug.

Sent from my SM-N900T http://www.inflewential.com
[T-Mobile Samsung Galaxy Note 3] phil.culler:
Thanks, I've been looking to get a wireless charger for quite some time, maybe this will be the one.
[T-Mobile Samsung Galaxy Note 3] farfromovin:
The benefit is 2 fold for me:

1) Ease. I have a Panasonic base that adjusts it's coil to line up with the phone so at night I just drop my phone on the base and KNOW that it's charging. Better than fumbling with a cable in the dark.

2) Less physical wear on the micro USB connector.
[T-Mobile Samsung Galaxy Note 3] detroitguy1:
While not a wireless charger, the Amazon 9w speed charger & the Samsung USB 3.0 wire charge my phone super fast.
[T-Mobile Samsung Galaxy Note 3] CravingMender9:
Wireless Charging

I did it just for the novelty factor initially. It was a good thrill, DIY mod types.

But later, I realized it is actually useful for me. I usually walk around while talking, and with Wired charger, I had to plug/unplug again and again after every call. Also, many times after unplugging, the wire slides down, and I actually have to crouch below my desk to recover it :P (call me sloppy, hehe). With Wireless charging, I just talk, place it back on the pad, nothing to worry about. It keeps charging while I do my work, and I also save the port (I've had port failing problems with other phones before).
[T-Mobile Samsung Galaxy Note 3] phil.culler:
Thank you for posting this! Sadly, it needs to be said.
[General Questions and Answers] kbolt:
Hello all.

I need a (simple?) way to tell if the bootloader of an Android device is locked or unlocked. Could someone please assist me with this?
[Verizon Samsung Galaxy S 4] TxdoHawk:
So, I suddenly started having an issue with SMS a day and a half ago with my Galaxy S4 on CM 11.0. Receiving texts works with no issues, but sending texts is hit or miss.

- Off a fresh reboot, the first text I send to someone always works.

- If I immediately text them again, it fails to send 100% of the time.

- Retrying doesn't work.

- If I reboot and try to resend that failed message, it works. If I send another message immediately after that, it fails.

- Sometimes, if I don't reboot but try to resend the failed message hours later, it suddenly works.

I tried a clean flash (with data/cache/dalvik wipe) of the latest nightly, but it didn't fix the problem.

I also tried reseating my SIM card.

I thought maybe this was a tower issue, but I travel a lot for my work and this is everywhere, strong or weak signals.

Research has told me that my APN settings may be screwed up, but when I go to check them the option is grayed out under Settings -> Mobile Networks. I tried using APNManager to check, but it force closes (Unfortunately, APNManager has stopped).

Just in case it helps, I'm attaching a ZIP containing syslog files. These were pulled after a fresh reboot and two texts sent (one succeeded, one failed).
[Verizon Samsung Galaxy S 4] TxdoHawk:
Small update: I've determined that forcing airplane mode on/off will also let me send another text message.

At this point I'm going to try flashing a different modem and hope that fixes the issue. Will report back.
[Verizon Samsung Galaxy S 4] TxdoHawk:
Unfortunately a new modem did not help. I'm still having the same texting issues. Any suggestions at this point are appreciated, I am once again out of ideas.
[Verizon Samsung Galaxy S 4] nolethemole:
Do you have Google voice installed? If so make sure that the sms feature is disabled. Or just remove google voice. For more help visit the source.

(Source: http://xdaforums.com/showthread.php?t=2561308 )
[Verizon Samsung Galaxy S 4] TxdoHawk:
I don't, but I think I may have found out what the problem is anyway.

If I go in and check my SMSC, it comes up as +19037029920. The wiki tells me it should be +316540951000. I tried changing it, but the changes don't stick, something keeps changing it back to +19037029920.
[Verizon Samsung Galaxy S 4] nolethemole:
So you did the *#*#4636#*#* method?
[Verizon Samsung Galaxy S 4] TxdoHawk:
Correct.
[Verizon Samsung Galaxy S 4] Cilraaz:
I'm having the exact same problem. It started at the same time and has the same symptoms. I can receive texts, but not send texts. If I toggle airplane mode, I can send a single text. I've also tried a factory reset. I attempted to change the SMSC, but it reverted on me also. I was running KitKang (Fitsnugly's) nightly from Jan 24, 2014 when the issue happened. I upgraded to the Feb 19, 2014 nightly, which didn't help.

I've been working with VZW support and they want to replace the device and SIM (though I'm obviously going to try just the SIM before handing back an MDK device). I was hoping someone here would find a fix before the replacement arrives on Monday.
[Verizon Samsung Galaxy S 4] nolethemole:
That was going to be my next suggestion is to get a new SIM card
[Verizon Samsung Galaxy S 4] Cilraaz:
The SIM card replacement made sense when I thought I was alone in the issue. Now, when there are at least two of us who had the problem starting around the same time......
[Verizon Samsung Galaxy S 4] TxdoHawk:
For what it's worth, Googling that SMSC gives me Github results for a piece of code that seems to change the SMSC of a device to that code as a test of some sort. Perhaps something like this unintentionally snuck into codebases?
[Verizon Samsung Galaxy S 4] Cilraaz:
Except it wouldn't explain why on Feb 19th, my Jan 24th build randomly did this. It had been working fine since then. I'm holding out hope that it's just a fried SIM card, but our timing is rather suspicious.
[Verizon Samsung Galaxy S 4] TxdoHawk:
Similarly I find this strange. I hadn't changed or flashed a build in awhile and then poof, I suddenly started having this issue.

Now that I have ten posts, I posted in the CM KitKat nightly thread with a link here, hopefully a dev will figure this out.
[Verizon Samsung Galaxy S 4] Cilraaz:
I convinced my wife to let me try her SIM card in my phone, so hopefully it doesn't blow hers up and makes mine work. I'll come back when I'm done testing with the results.

Edit: Texting did not work using her SIM card. I guess it's time to try backing up and reverting to stock.

Edit2: Reverting to bone stock MDK worked. My texts flow freely now. I guess I'll try reloading CM.

Edit3: Flashed back to KitKang 2/19 nightly and the issue came back.

Edit4: Flashed back to KitKang 1/24 (which was working for me until 2/19) and the issue still exists. I'm at a loss.
[Verizon Samsung Galaxy S 4] TxdoHawk:
Thank you for testing. At least we know now that this is definitely code and not some weird SIM card thing.
[Verizon Samsung Galaxy S 4] Cilraaz:
I just don't understand why my 1/24 nightly worked for 3 and a half weeks and suddenly stopped working.
[Verizon Samsung Galaxy S 4] Cilraaz:
I tried today's nightly of the official CM branch. It still had problems.
[Verizon Samsung Galaxy S 4] Mistertac:
I've noticed some issues popping up since the builds have been unified.

Sent From My Verizon S4
[Verizon Samsung Galaxy S 4] Cilraaz:
I'm going to try clean flashing my old 1/24 build. When I tried it earlier, I flashed the 1/24 build over the 2/19 build, so maybe something was left behind? I'm grasping at straws, but I really want to be back on CM. I almost forgot how much I hate stock TouchWiz.

Edit: As expected, no dice.
[Verizon Samsung Galaxy S 4] Cilraaz:
And after all of 12 hours using stock MDK, I'm going back to the SMS-broken CM11 builds. Routing SMS via Voice+ and Hangouts is less of a pain than using a stock TouchWiz ROM.
[Verizon Samsung Galaxy S 4] swordmastr54:
I had this issue when I tried to go from cm11 to a tw, I learned Odin and went back to stock then went all over from there.
[Verizon Samsung Galaxy S 4] lv128:
Does anyone know if there is anything else involved with sms sending besides the SMSC? I tried the two known SMSC numbers for verizon:

Verizon: +316540951000 and +19037029920 in Go SMS where I can change to use custom smsc, (I even changed them in the phone information page but it reverts to the 903 number every time I reboot the phone)

I even tried in PDU format, no go.

I've also tried a number of other random smsc, which I knew probably wouldn't work, but I'm getting desperate.

Verizon rep says on saturday "I will own this issue and I'll be in touch with you on Tuesday at 3:30PM" so we'll see what comes from that, he also said "I'll be the last person you talk to on this, I got this for you."

Seems confident in a hilarious sort of way, but with any luck, I'll get an answer.
[Verizon Samsung Galaxy S 4] Mistertac:
Lol a Verizon rep once tried to get me to cut my Data plan in half even though I come extremely close each month to going over. I lost alllll faith in them after that. But like anywhere else, its all in who answers the phone. I hope you have better luck!!
[Verizon Samsung Galaxy S 4] DreamFX:
Good luck. Please keep us updated.
[Verizon Samsung Galaxy S 4] E01010100:
24544382 410

So I tried swapping out my CM kernel with Ktoonsez ; while the kernel flashing was successful Verizon still appears to ban my phone after 1 message.

So much for that work around.
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
So are all nightly builds dead in the water for everyone for SMS? My 3/07 nightly works fine but every build I've tried since won't send a single text, so I keep having to revert back. I used to update every day or two but have stopped hoping that this would resolve itself. Finally tried today's build after 10 days of holding off and same thing.

Just wondering if maybe this has been fixed by doing a clean update? It's quite frustrating...

Thanks.
[Verizon Samsung Galaxy S 4] Kevin M:
I looked at another CDMA / LTE Verizon phone and the SMSC was nearly identical.

CM 11 Droid Razr Maxx (working)

+19037029920

CM 11 Galaxy S4 (not working)

"+19037029920",145
[Verizon Samsung Galaxy S 4] neganox:
I clean flashed slimkat 3.10 nightly last night. Texting appears to be working fine now. Tested several times, rebooted, tested some more. I have NOT integrated sms into hangouts. I have google voice handling voicemail.

xda's captcha usage is horrible.
[Verizon Samsung Galaxy S 4] lv128:
I think this is unrelated, it's for some reason however the samsung phones format the smsc, don't know why this would be different from mfg to mfg, since they're all running the same rom. If you type the top smsc into a samsung under the Phone Information page, it just reformats it to the lower number and adds the ,145. perhaps like a checksum.

some of the smsc I've tried added a ,123 and a ,129
[Verizon Samsung Galaxy S 4] Kevin M:
So right now are we going with a localized network protocol upgrade that unearths a previously unknown bug in CyanogenMod?
[Verizon Samsung Galaxy S 4] lv128:
I can confirm on the i535 with Verizon, slimkat doesn't work any differently or better than CM11, the problem still exists.

So anyone with the s3 on Verizon will not get any relief from flashing Slimkat.

---------- Post added at 03:32 PM ---------- Previous post was at 03:20 PM ----------

That seems likely, or Verizon targeting the specific method in which AOSP (not just CM) sends SMS, and TW either does it differently or has a different header that provides additional handset information that the network protocol now requires to prevent "banning"

Logical guess is that TW is sending extra information that the network is expecting and when it doesn't see it, it treats it as a rogue app/device that might have been used in the past for spamming.

I've tried restoring all of the messaging components with titanium from the stock TW rom, and that did not help so it's something in the source.

If TW source is available somewhere, that would be the best way to find out. And then patch it into AOSP.

It seems that the touchwiz source is available, but it's above my ability to interpret. I downloaded it anyway, I used to do some programming, but I'm not hopeful I'll be able to understand it or know where I need to look for the SMS sending portions. it's available from http://opensource.samsung.com
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
I don't see the logic in blaming VZW - I have no issues on CM11 3/7 nightly. It's only any later builds that it happens. Each time I revert back it works fine again. Wouldn't that point to a CM bug?
[Verizon Samsung Galaxy S 4] lv128:
The logic is in that I was on CM 10.2 when it happened on Feb 16th and have been a long time before that without any upgrades or changes, it started at 5pm in the evening and that was it. I haven't even so much as TRIED a build of CM11 until after the problem occurred. The first CM11 build I tried was 2/22 nightly and that had the "error" as well and Slimkat (flashed today), and every AOSP build I've flashed since 2/16 (approximately 12 total) have ALL had the same issue. Even tried a 4.0.4 rom for the S3 as that ALSO does the same thing.

So, that is how I come to the conclusion that it is VZW at fault.

I don't know what phone you're using but I've been on the 3/7 nightly and the problem was still there. That aside, 3/7 had horrible camera freezing glitches up until 3/18-3/19. If you read the thread you'll see I've also been on every available flashable modem.

So if for some reason you're able to use 3/7 nightly on an S3 i535 that hasn't been modified in any other way you're an incredibly lucky person. :shrug:
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
Gotcha. For reference I'm on an S4. Guess I will consider myself lucky and will just hold tight until the mystery unfolds. Good luck tracking down the issue.
[Verizon Samsung Galaxy S 4] riddick72:
Same Issue

So, I have finally seen this happen to others. Same issue I have been having for about 2 weeks now. I am running Beanstalk 4.4, the x.225 version released in January on my verizon S4. No updates, no changes, and the problem magically started. Called Verizon and their solution was to send me a new phone!! Of course, they didn't know I was not on stock. It's something Verizon has done within the last several weeks. I send a text, it goes, send another and it sits. I am trying other ROMS to see if I can get past it. If I can duplicate it on the new phone I get in several days, it's DEF Verizon. My co-worker had to roll back to stock, deo/rooted version to get it to work because he experienced the exact same issue.

Update...I called back and since I was quite furious was able to elevate it to a network issue. They still insist they want to see what happens with the new phone. OF COURSE it will work; IT'S STOCK!!
[Verizon Samsung Galaxy S 4] neganox:
I should've noted that I'm using a VZW S4. Additionally I had switched to a GPE rom and had zero issues with texting.
[Verizon Samsung Galaxy S 4] dadoc04:
Thx Neganox... Ill have to clean flash a gpe rom and try out text... Then clean flash slim and try text again

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] lv128:
I agree with the logic in that statement, so it'll tone down my feelings of persecution by verizon. I did do the nvrestore as suggested, however it didn't fix my problem, it did boot loop and I fixed it as was logical at the point by reflashing the rom and gapps without doing a data reset.

I'm wondering what is happening during boot of a AOSP rom that doesn't happen on an ancient ICS TW rom (or any TW rom for that matter) that corrupted the nvram to the point where out of everything that these phones can do, the only side effect is the ability to send SMS messages, no problem with receives or MMS in or out.

As I pointed out earlier in the thread too, if you drop your phone down to 1x CDMA, even without doing any of the above items you suggested with the nvrestore, you get 100% send rate for sms. (you have to drop it to CDMA only in the Phone Info page, cycle the radio, then also make sure it's CDMA 1x in the Settings -> Preferred network type)

Doing this of course makes the phone almost unbearable to use for anything data related. This is why I had originally discounted the nvram issue, although it could be a combo of both.

So knowing that, what's so special about the handoff for SMS from LTE/3g vs cdma 1x that the AOSP roms are not doing?
[Verizon Samsung Galaxy S 4] Kevin M:
Any way to reliably achieve 1X? I can only select 1X/3G auto.
[Verizon Samsung Galaxy S 4] dadoc04:
Ok guys..... My text is working again.

Here what i did.....

1. Factory reset and wipe system

2. Flash the GPE rom

3. Send multiple texts and saw them go through

4. Rebooted & set hangouts to default (text still working)

5. Clean flash slim, cm11, or liquid smooth

6. Tested text and all is well.

Hope this helps somebody

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Kevin M:
Please let us know if this regresses.
[Verizon Samsung Galaxy S 4] yooeee:
Hey, I went for it and did a similar thing, and it might / seems to be working.

1) NANDROID BACKUP

2) Standard wipe with TWRP recovery (any wipe / recovery probably works)

3) Flash GPE (http://xdaforums.com/showthread.php?t=2643031 make sure you scroll down to the Installation Instructions on how to get LTE going)

4) Followed the instructions on that link to let the configuration run (I'm thinking let it sit there after you run setup for a little while before configuring LTE). (i actually ran into some FC phone errors on this part, which could be due to xposed being around. For what it's worth, I went back, wiped, and flashed GPE again). Eventually LTE stuck and no FC.

5) Sent multiple texts with the stock messaging app and they went through. (I did not do anything with hangouts. I didn't restore anything through the store or install any kernels or GAPPs. I didn't even have hangouts installed)

6) Made a nvbackup in case

7) RESTORED my nandroid backup

8) Texting is working for now (there's a delay compared to TW on receiving my own text, like a minute, but they are going through)

9) Rebooted to make sure this isn't bull****. Texting still works, still a delay, but definitely going through on LTE

I'll update if this fails from here on out, but I think the solution might be in GPE ROMS.

Possible explanation?

I don't know if GPE installation reprovisions the phone, but this is a possibility (Reviewing the S3 boards that have / had this issue at http://xdaforums.com/showthread.php?t=2657822, they went back to ICS stock and used the *2767*3855# code to reprovision the phone, then nvbackup in case, then clean flash or restore nandroid, and sms sending works / sticks. Unfortunately, this code doesn't work for verizon S4's. I checked by unlocking the hidden menus and everything for jellybean, but that specific code is disabled despite test codes working. I was on stock MDK, which was the earliest stock build I could find)

I think this is a safe method since you have your nandroid backup in case is doesn't work.

Thanks and hopefully this is the end of this nonsense...
[Verizon Samsung Galaxy S 4] dadoc04:
Still going strong.... Rebooted and set hangouts as my default. Still no issue.

Everybody having this issue please clean install the GPE rom or touchwiz rom. Send multiple texts and make sure they are being sent.

Reboot or whatever..... Send a few more

Then flash your favorite rom and should be good to go.

After running GPE, ive flashed liquidsmooth, cm11 and slimkat.... All are sending receiving texts just fine.

Thanks again [MENTION=3476009]neganox[/MENTION]

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] lv128:
Well, I don't think reflashing anything is really a scientific method, since I've already been on TW stock and jumped through all those hoops, no matter what, on the s3 with verizon, the issue returns in a few hours or a day at most.

In any case, keep the thread updated, there has to be a "works for everyone" approach.:confused:

Also I think the majority of people with this issue are using an s3, no?
[Verizon Samsung Galaxy S 4] neganox:
No one said it was a scientific method. We just posted what works for us. If it works for you, awesome. If it didn't then that's unfortunate. You also have an S3 and we have S4s. Maybe that's the different. Maybe its unicorns. Who knows.
[Verizon Samsung Galaxy S 4] dadoc04:
we arent on the s3 though, and maybe its not flashing touchwiz thats fixing it but flashing the GPE rom thats doing it.

So far, 3 people have flashed the GPE rom and been able to go back to aosp/cm roms and still have text working. Hence the reason i asked for more folks to try the method i posted to see if thats the same result. Is there a thread in the s3 section with a possible fix? it may be different from whats working for us.
[Verizon Samsung Galaxy S 4] lv128:
Honestly when I stumbled on this thread, I didn't notice it was in the s4 section, but it was the most active one I found, almost all the others fizzled out after a few IDK responses.

So I supposed I can move my posting to an s3 related thread, since yes, the steps to resolve would be different enough to matter.
[Verizon Samsung Galaxy S 4] dadoc04:
good luck man.... this issue really sucks
[Verizon Samsung Galaxy S 4] S52Stu:
http://xdaforums.com/showthread.php?t=2657822
[Verizon Samsung Galaxy S 4] yooeee:
Seriously, good luck, being in that boat was so frustrating, but three of us got out for S4, and least out for S3.

For S4, I recommend GPE clean install as I linked earlier. (Stock Touchwiz didn't work me as a permanent fix). Texts are still working great.

For S3, I'd look into the forum linked the previous post, the first post details a *2767... code that apparently reprovisions the phone.

I stand by the reprovisioning idea. If there's an easier way to do this, that'd be great, but I don't think a clean install GPE, configure LTE, then flash clean or flash nandroid is that difficult compared to the other hoops we've tried. Try it, and report if it works or doesn't. No one has reported GPE not fixing things, so we're 3-0
[Verizon Samsung Galaxy S 4] jharris0221:
Thank you so much! I followed this exactly and it worked. No issues sending text on 3/25 CM11 nightly (VZW S4), Thanks!:good:
[Verizon Samsung Galaxy S 4] dadoc04:
Fistpump..... 4-0 now

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] yooeee:
YES!!! #winning
[Verizon Samsung Galaxy S 4] efaden:
Going to be trying this tomorrow.