yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] yitzi:
Thank you for your work on the P7500 /P4 Galaxy Tab 10.1 3G Rom, I just read that you needed to replace the device and I'm late responding, but I wanted you to know I value your work so even though you said you had enough to purchase another device, I'm made a donation.

Yitzi
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Thank you again to the donators for my replacement tablet!

Got today the used GT-P7500. It is in a very good shape, never saw a custom recovery or a custom ROM.

10 minutes after I was back home the tablet was rooted and has TWRP recovery. 15 minutes later it has Nameless ROM build date May 5th running on it. Looks good so far, but I want to make some tests before I publish it.

Thank you again to the donators for my replacement tablet!

Attached first 3 screenshots with navigation bar left, middle and right and the settings window to select the position. Next screenshot show settings window for navigation bar in status bar and the navigation buttons in the top right corner.
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
Glad you have your good old tab back :P paypal still didn't top up my account so i have to wait a little longer forna small donation... Thank you [MENTION=1360332]BeeGee_Tokyo[/MENTION] and all others who donated :)
[Paranoid Android Q&A] Kenneth.Kong:
gee,after flashed the latest build,it always took me a long time to charge,and it always display USB when charging,is it a bug? anybody has the problem or how to solve?
[Networking] kasperjamhard:
Hi. i am working on a project with arduino and android wifi. i wanna connect my arduino to my smartphone, using my smartphone as a router with a wifi hotspot, but i don't wanna share my data connection. how do i do this? i just wanna test something regarding wifi range, so all i need is my arduino to connect to the smartphone as if the smartphone was a router. is this possible?

TL;DR

Can i use my smartphone as a router, allowing me to connect my arduino to it?
[Networking] aarongillion63:
My question is why would you want to specifically not share data? Simplest answer is to put your phone on Airplaine Mode... AFAIK

I found an article that doesn't quite match your question but may give you some insight: http://stackoverflow.com/questions/...by-using-the-shell-on-a-rooted-android-device

Personally I think you would have to use some shell commands and some iptables modifications to achieve what you want.. I use DroidWall to modify iptables and block apps from connecting to the internet. Possibly you could block "Tethering" from the Internet using this app.

Hope all goes well,
[HTC Droid DNA] pcwizkid1994:
Every KK rom I flash will not let me send sms. I have tryed changing the sms size and I am on the beta twp recovery. Any help would be greatly appreciated.
[HTC Droid DNA] Uzephi:
Which hboot and radio are you on? Also, try the official 2.7.x.x it works for me on latest radio and eng hboot (use the latest shipped hboot of you don't plan on using eng commands)
[HTC Droid DNA] pcwizkid1994:
I am useing radio . 1.01.01.11122
[HTC Droid DNA] Uzephi:
Flash the most recent radio for kk roms to have sms work
[HTC Droid DNA] pcwizkid1994:
Where would this be found? I have looked and can not find it. I know how to flash off I just can't find it
[HTC Droid DNA] Uzephi:
http://xdaforums.com/showthread.php?t=2236633

http://goo.im/devs/T1gArtist/Radios/PL83IMG-3.06.zip is the 3.06 radio
[HTC Droid DNA] pcwizkid1994:
Any other ideas? I updated and now I am trying a error 3 on sending texts
[HTC Droid DNA] KohanTech:
Do u get sms on original jb? (not stock htc sense rom)
[HTC Droid DNA] pcwizkid1994:
Like cm 10?
[HTC Droid DNA] KohanTech:
Yup. I lost it on kk, then checked cm 10 and lost it there too. Just seeing if we share the problem.

Edit: 1.01.01.1112 is the latest radio... But I guess you could reflash it...
[HTC Droid DNA] pcwizkid1994:
Ya I have lost it there to
[HTC Droid DNA] KohanTech:
Yup. I lost it on kk, then checked cm 10 and lost it there too. Just seeing if we share the problem.
[HTC Droid DNA] pcwizkid1994:
I am on a higher radio version then that
[HTC Droid DNA] KohanTech:
I thought it was. I don't know... I have a newborn and unable to confront this problem the way I'd like. My current radio is from here. I was trying nusenseSIX from santod. His stuff is always solid :good:

Anyway I've tried flashing all radios. It seems the only way I got sms working again is to break my 4g. I used *228 option 1 and messed up my SIM. I got sms back but *228 botches sims. Got a replacement from Verizon and sms was broken again.

Edit: let me tell u how desperate I got. I decided to ruu about a month ago when my wife's iPhone 5 went belly up and I gave her my DNA and took my old fascinate out the drawer until I fixed her phone...

So I RUU'd 3.06... fixed her phone... Took my phone back and s-off'd with rumrunner. It worked great except I could not send sms. This was with carbon KK. Found out I could only send sms with stock oem based roms.

So I got desperate and RUU'd 1.15 updated via ota to 2.04 and moonshined to s-off. Still have the same problem... any takers?
[HTC Droid DNA] Uzephi:
Have you tried going back to stock and seeing if sms works bone stock, s-on, locked, etc?
[HTC Droid DNA] pcwizkid1994:
Ya I have and it does
[HTC Droid DNA] matthall9815:
Please post the radio version you are on then. .1112 is the 3.06 shipped version. Thanks
[HTC Droid DNA] pcwizkid1994:
This is what I am on.
[HTC Droid DNA] matthall9815:
OK, I've tried the 2.06 and 3.06 radios hboot 1.54, and both 2.6 and 2.7 twrp. I just got back from VZW with a new sim card that didn't fix it either. Not sure where to go from here. I still get the same error 65523 or what ever it was after the first message goes out all others fail. I've got another phone complete minus the screen maybe I'll switch the board later. Anyone else got any ideas? Also is it correct that 1.01.01.1112 radio shipped after 1.01.04.0308?

Thanks
[HTC Droid DNA] iamjonmiller:
You are not alone

Just to let you know this has been a problem across many ROMs and devices on Verizon for weeks now. Nobody knows what exactly is causing it as it seems to pick users, devices and OS versions at random.

I personally have a scary hunch that Verizon is testing a blocking method for rooted users that flash newer OS versions than are available naturally. Kinda like an OS check that runs every SMS and results in a ban that requires a radio toggle to fix.

I am probably totally crazy with that theory, but it seems a bit sane. After all, this isn't a bug that plagues all users of custom ROMs or all users of any specific ROM or device, and none of the people that this is happening to are idiots who have made changes to their device. It just stops working one day. Kinda like Verizon flipped a switch on a new program and picked some guinea pigs.

One other thing; It seems that a lot of these problems are originating in East Coast states, specifically VA, MD and PA, with only a few recent occurrences in CA and several in my very own 540 area code. Where are you located?
[HTC Droid DNA] pcwizkid1994:
****... I am in pa
[HTC Droid DNA] KohanTech:
Pa as well. I would not put that past big red...
[HTC Droid DNA] Jaggar345:
Thank god I'm leaving big red when my contract runs out. How can they not expect people to load customs software of their phones. It's their fault they decide to roll updates out so slow or just not at all.
[HTC Droid DNA] JinxtPhoto:
I'm in the same boat. Every ROM I flash that isn't based on the stock Sense 5 ota throws an Error 3 when I try to send a text message until I flip it into airplane mode. After toggling airplane mode I can send one text and the next one will throw the same error code until I toggle airplane mode again. I'm in Virginia though, so the PA thing doesn't apply.

When I initially S-Off'd I was on the most current OTA update and I used the 605 Rumrunner. I'm on the newest radios from having originally done the latest OTA while stock, but I'm still using whatever hboot rumrunner installed during S-Off. Might that have something to do with it? My baseband is 1.01.01.1112
[HTC Droid DNA] iamjonmiller:
Thee problems have mostly been in VA, PA and MD.
[HTC Droid DNA] santod040:
Just curious how many of you folks having these issues, use apps like Titanium to restore your messages?

If you are, have you tried sending any prior to doing any restoring.

In other words, flash stock Rom and recovery and do a factory reset.

Flash a known working custom Rom, do not restore anything....and send and receive texts.

Have any of you tried that? Are you restoring?

Some apps set themselves as the default message app now after using them to restore messages, such as Titanium Backup.

So then when you go to send it tries to use Titanium to send and of course fails.

Just something I thought maybe some of you are unaware of.

Maybe it helps, maybe not...I wish you luck.

Glad I haven't experienced this at all.

For the record, I never restore messages, ever.
[HTC Droid DNA] KohanTech:
I don't use titanium. But I haven't tried the stock Rom and recovery and factory reset yet. I will try that in the a.m.
[HTC Droid DNA] iamjonmiller:
Yes, I am aware of that. Sadly, it is much worse than a simple toggle. Nevertheless, thanks for the advice! I have tried the stock recovery and factory reset btw, to no avail.
[HTC Droid DNA] JinxtPhoto:
I use titanium backup but only for user apps. I've never used it to backup or restore texts or any system apps.
[HTC Droid DNA] matthall9815:
I got a new Sim card, ran the ruu, unlocked, loaded twrp, flashed your rom and tested. Messages failed after the first.

I was using your sense 5.5 when messaging quit a couple weeks ago. I certainly wouldn't put it past vzw to try and block us from using newer roms.
[HTC Droid DNA] Uzephi:
Question, would editing the build prop to be like the stock Rom bypass this rumored custom Rom check?

Edit: I am in AZ where this issue hasn't risen yet, just providing insightful feedback
[HTC Droid DNA] JinxtPhoto:
I've done both the RUU.exe and the 3 file fastboot RUU method, doing factory resets in the factory recovery. Any of the sense 5 based Roms work fine, any of the KK Roms or Sense 5.5 and 6 base will not send more than one text without having to toggle airplane mode. If I toggle airplane mode it will send one text, but if I send another I get the error until I toggle it again.

*edit*

And I've been trying it without using TiBackup at all. Not restoring anything or even installing the app.

Official DNA KK is only a few weeks off so I'll just stay stock for now.
[HTC Droid DNA] pcwizkid1994:
We'll with the official Kitkat stock rom beig pushed out on the 24th. I will wait and update to that and see if there will be a unlock and root for that
[HTC Droid DNA] KohanTech:
Hopefully it'll fix this problem. Here is something else I have tried if it helps anyone.

Today I swapped my DNA with my old Thunderbolt on my Verizon account. Waited a couple of hours then reactivated my DNA. This made no difference. With anything else except stock based roms sms fails.

Funny note: My s-off thunderbolt has no issues going from stock Rom to custom. Sms works great either way.
[HTC Droid DNA] orangechoochoo:
I've been following this for a while and have been hesitant to go to a KK ROM because once the problem arises there is no going back.

I did the original unlock method and did try a KK ROM a couple months ago but i went back to 4.3 because I didn't like KK and have never had a problem. What I've noticed is you guys ruu the latest release and probably use the latest method to unlock. I'm wondering if the combination of the latest ruu and KK ROMs are somehow incompatible.

Can one of you guys relock your device, ruu back to 1.15, flash the stock rom & recovery, factory reset in stock recovery, unlock using the original method or moonshine, don't accept any update, and flash a KK ROM. That's where I am and have not had an sms problem.
[HTC Droid DNA] Jaggar345:
I did the new combinations and everything has been working great for a while. I'm not in PA or VA or MD I'm in CT so it very well maybe that big red is indeed blocking the network in their area.
[HTC Droid DNA] donnieseech:
okay so this sounds dumb but how do i ruu back to 1.15. i went to do it last night and it wont quite reach the progress bar then crashes. any ideas or suggestions? im at my wits end trying to get something running that isnt viper or stock. oh and im in new mexico with the issue
[HTC Droid DNA] KohanTech:
Hey did u flash the 1.15 hboot? A lot of times I forget this step.
[HTC Droid DNA] donnieseech:
Now I did and yeah it still fails to send
[HTC Droid DNA] iamjonmiller:
I'll give that a shot.
[HTC Droid DNA] KohanTech:
Does it give an error?
[HTC Droid DNA] donnieseech:
Yeah on sense it's the 65535 error 3( I've already tried troubleshotting) then on aosp it just says not sent
[HTC Droid DNA] JinxtPhoto:
Alright. I'm going at it full-bore just to make sure it's fully troubleshot.

Steps:

- Flashed the 1.15 hboot.

- Re-locked bootloader.

- Ran the 1.15 RUU.exe from my PC.

- After initial boot I bypassed the install wizard, rebooted to bootloader and did a factory reset.

- Rebooted and again bypassed install wizard.

- Installed SuperCID

- Got my token

- Used HTCDev to get my Unlock_code.bin (I received the phone originally with the stock latest OTA and used RumRunner)

- Unlocked the bootloader manually via fastboot

- Flashed the 3.06.605.4 firmware.zip via fastboot oem rebootRUU to update my firmware, hboot, and radios

- Flashed TWRP 2.7.0.0. using fastboot

- Rebooted to copy over a KK Rom

- Rebooted to recovery, wiped data/cache/dalvik/system

- Flashed NuSenseSIX RC5.2

- After the successful flash screen I hit "Reboot System"

- Booted and did the setup wizard. Let contacts populate and all that good stuff. Send a text. Successful as usual. Sent another text, BAM "SMS Error. Cause Code 65535 Error Class 3"

Don't know what else to say or do, so I'm going to RUU back to the latest OTA and wait for the stock KK rom to start rolling out tomorrow.
[HTC Droid DNA] santod040:
Google-ing that error code, takes me to forums for various Vzw devices, as far back as 2011.(including the Thunderboltwhich I owned and never had that issue, and Inc 4G Lte)

A lot of those errors were tracked back to users that had imported a bunch of contacts via Facebook or another method, which pre-pended the contacts number with a +1.

Sending to users with a +1 will typically fail with that code.

In order to fix, some have had to remove and resync their contacts(not sync from facebook or fix them on facebook) and other various methods, including making sure to remove all traces of that previous message thread.

I don't know if any of that helps or not or if it will persist or not for you once you move on, but just thought I'd mention it as well.

Hopefully the update is good for you and maybe will be all you need. :good:
[HTC Droid DNA] JinxtPhoto:
Yeah, I've seen that too. But the problem only happens when not using a Sense 5 based Rom, so I dunno.
[HTC Droid DNA] iamjonmiller:
Thanks for the research, but that definitely isn't the problem here. I checked through my contacts, and that isn't happening. Also, it's interesting to note that everything works fine on Sense 5 roms.
[HTC Droid DNA] pcwizkid1994:
Yum I can confirm that everything works in sense 5 roms but anything higher then that they don't work
[HTC Droid DNA] JinxtPhoto:
FFS... Lol. Went back to stock 3.06 and did the new stock 4.4.2 OTA. Sense 6 roms still won't send more than one text without needing a toggle. Anyone know if the One+ One is going to work on Verizon? I've just about had it with the DNA at this point and I have to buy phones off contract so I can maintain my unlimited data.
[HTC Droid DNA] KohanTech:
I'm in the same boat. Looks like stock till I get rid of the red menace.
[HTC Droid DNA] micahl88:
I know I talked to you about this in your nusense 6 rom forum, but this is exactly what I am talking about. The last time I installed a rom, I completely wiped the phone, even system and pushed the rom through adb to clear anything and everything. I did not push any data to recover, tried using stock and 3rd party messaging apps, tried global and cdma/lte network settings with a reboot inbetween and I still get this exact issue. Same error codes, doesn't seem to matter what rom, I receive texts and can send one per boot then error 3/65535. Would sending a adb catlog help?

Thanks
[HTC Droid DNA] KohanTech:
Here is a little bit of info... I think it is definitely a Verizon issue focused on a geographic area. Possibly a test roll-out to black list CM/AOSP ext...

It looks like touchwiz is having this same problem. They, however, seem to have a working work-around. I have been trying to duplicate the basics of what they are doing with their S3's on my DNA, however I am moving slow due to the knowledge I have and my crazy work schedule. Anyway here is what I found... (I posted this link in another thread as well)

http://xdaforums.com/showthread.php?t=2657822
[HTC Droid DNA] Jaggar345:
I agree with you. I think they are testing it on PA and VT. I believe that slowly they are going to do it to all of the United States. Hopefully it doesn't happen in CT until after I am off their network. Sorry to hear that you have to deal with this bs, but that's is Verizon. Have you tried changing your area code. I know a lot of people don't want to change their numbers but it may work and if your willing to do it, it may fix it.
[HTC Droid DNA] Uzephi:
Essentially the way the S3 works: install your preferred Rom having the issues. Make a nandroid. Install a stock Rom that has sms working. Send a few texts and get a GPS lock. Go into recovery wipe cache. Then restore your nandroid.

I don't think this workaround will work with our DNAs have different partitions. I don't think our stock roms flash a radio like the S3s do. That is how their workaround works.
[HTC Droid DNA] iamjonmiller:
And VA and MD
[HTC Droid DNA] mdphoenix:
This explains SO much....
[HTC Droid DNA] pcwizkid1994:
Has anyone got this working? I remember some were someone said that they got it working on a older radio but can't find it anymore.
[HTC Droid DNA] barkandlink:
SMS sending
[HTC Droid DNA] superchaos:
First time I have had to apply changes

I use ChompSMS instead of the stock messaging service. This is the first time I actually have to place information into the ChompSMS MMSC setting. I had to copy the "http://mms.vtext.com/servlets/mms" in the APN settings MMSC field of the stock messaging ap to the ChompSMS APN settings MMSC field. Probably a whole different issue but if it helps, great.

I am on the stock KitKat rom, rooted, S-Off
[HTC Droid DNA] Unphazed MD:
Tried updating to Viper4.1 and I am having the same 1 sms sends and the rest give 'message not sent'. (I live in MD so its consistent with what this thread is saying about it being a geographic VZN issue)
[HTC Droid DNA] pcwizkid1994:
Go in and change it to CDMA only that's what worked for me. I was useing it like that for a day or 2 then switched back to lte and CDMA and now I can have lte and msm send without havering to toggle radio
[HTC Droid DNA] biggiesmalls657:
You still have to do that? Mine works out of the box.
[HTC Droid DNA] pcwizkid1994:
No. Just saying when I did have it that's what I did
[Galaxy S 5 Q&A, Help & Troubleshooting] Eye4Tech:
I have my S5 since yesterday and in every call I make I hear a pretty loud hissing sound like there's wind blowing in to the mic on the other side (even though they're not outside). I've tried calling to different phones but the noise is always there.

Is it just my phone or are there more?
[Galaxy S 5 Q&A, Help & Troubleshooting] eyecon82:
Did you enable noise reduction?
[Galaxy S 5 Q&A, Help & Troubleshooting] Eye4Tech:
Yes it is enabled

sent using a Galaxy S5
[Galaxy S 5 Q&A, Help & Troubleshooting] skiddingus:
I have a couple 2 amp built-in wall receptacle 5V usb chargers in my house. They have charged everything I have ever owned just fine including my S4 that I just upgraded to an S5. For some reason, these chargers will not charge the S5. My car chargers and every other charger I own, some of which are not Samsung, still charge the S5. Does anyone know why the 5V wall chargers will not work? I have tried different cables too. Everything works fine except these wall chargers. Why would the S5 refuse to charge from them?
[Galaxy S 5 Q&A, Help & Troubleshooting] eyecon82:
Weird. My old s4 charger works properly
[Galaxy S 5 Q&A, Help & Troubleshooting] skiddingus:
So does mine. Like I said above, only the built-in wall USB recptacles do not work and I can't figure out why. They are good 2 amp models that charge anything else that I can throw at them.
[Galaxy S 5 Q&A, Help & Troubleshooting] joekadavil:
Galaxy S5 Not Charging with Micro USB

Hi,

I am purchased a T-Mobile Galaxy S5 yesterday. The supplied charger works fine. But, I have 6-8 aftermarket micro USB chargers that I purchased from Best Buy (Rocketfish) that do not work. The transformers on those are 2.4 Amp. The transformers on the supplied Samsung chargers are 2.0 Amp. Could this be the issue? Is there any hack to make my aftermarket chargers work?

Did you ever resolve your issue?
[Galaxy S 5 Q&A, Help & Troubleshooting] jatinder:
my capdase dual charger is not working with galaxy s5
[Galaxy S 5 Q&A, Help & Troubleshooting] skiddingus:
I've had a GS3, a GS4, and now a GS5. The 3 and 4 would charge with any USB charger. Only the charging rate would change. I did some experiments with an old cable and found that the thin wiring in the cable was the culprit of the slow charging. When you get a phone (or tablet) with a 2 amp capable charger, it will be supplied with a cable capable of carrying that much power without a large voltage drop. If you have a lightweight USB cable, the voltage drop in the cable itself will drop below the 4 volts needed at the phone for proper charging.

I have a couple of built-in wall outlet 2 amp capable USB chargers. They charged the S3, S4 and older tablets just fine. Now I have an S5 and just got a Samsung 10.1 pro tablet. Both refuse to charge from the universal 3 amp chargers. They will charge from only the original Samsung chargers or from my laptop. Samsung has changed something in their charging circuits recently. I think if they detect a non-samsung charger they just refuse to charge completely instead of just defaulting to a slower rate. Does anyone know if this is fact or a way I can mod my wall charger to work on the new Sammy devices? I don't mind slow charging.
[Galaxy S 5 Q&A, Help & Troubleshooting] hairykewell:
A couple of my non-samsung chargers not only don't charge but actually drain the battery.
[Galaxy S 5 Q&A, Help & Troubleshooting] russ18uk:
If it is a change then it's not recent. I charge mine from my 3-year-old S2's charger just fine.
[Galaxy S 5 Q&A, Help & Troubleshooting] Seljeskogs:
Just wondering if you ever found a fix for this.

I just got a couple of these new "built in" charging outlets. My outlets are 5VDC 3.0A and they work fine with every other device I have except the Samsung Galaxy S5. :(
[Galaxy S 5 Q&A, Help & Troubleshooting] davidk21770:
Since the latest ROM update, mine won't charge from "Apple" rated charging ports...
[Galaxy S 5 Q&A, Help & Troubleshooting] rnpasinos:
the same here... i have the capdase ampo r2 dual charger... it's able to charge my note 3 but note my note 10.1 2014 and my kid's tab 3 7.0... it has an output of 5v 3.1a (2.1a and 1a)... i'm pretty sure it's not a problem with the tablet coz it charges with i use their original samsung chargers...
[Galaxy Note 3 Q&A, Help & Troubleshooting] Extended181:
Hey Guys,

I have a Backup from my Old N9005 created with TWRP Recovery. Is it possible to Restore the backup on an other Note 3?

It's the same Model N9005
[Galaxy Note 3 Q&A, Help & Troubleshooting] antique_sonic:
if you restore data only shld be no problem. other than data, I'm not sure.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Extended181:
When I restore the whole Backup. Can i brick my device?