yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] stovie75:
Seeing the same thing on straight talk...

Now straight talk and net10 are sharing the tfdata APN settings... (Some straight people have been migrated to this tfdata, some are still on att.mvno)

Its really hit or miss... and seems to get better at night..

I can do a speed test and get 6 Mb down in Tulsa ok area, then not be able to load a web page.. I can tell when its acting up because the plus sign next to the H cycles.. On At&t and Net10 (At&t simm) for me that did not used to happened until just a week or so ago. Tmobile's + sign would cycle all the time. Now when I am having difficulty with a page loading I see it cycling.. When things are going "good" (fast page loads, consistent speedtest.net tests) + sign doesn't cycle at all.

Its frustrating to say the least..
[Nexus 4 Q&A, Help & Troubleshooting] vanvalks:
Has anyone else been seeing grey bars on the signal icon lately? My phone will shows H+ and full signal, but grey bars which means it's not connecting to google services. Have the apn settings changed recently?
[Nexus 4 Q&A, Help & Troubleshooting] acejavelin:
I got this all the time, it means the phone can't connect to Google services... Usually also means internet is broken or to slow, when it happens to me nothing would load for several second. Switched to AT&T GoPhone and haven't had a single issue with that again.
[Nexus 4 Q&A, Help & Troubleshooting] vanvalks:
It's only been the past month or so that it's been doing that, before that it was fine. I've seen on another thread that the apn settings have changed after the roll out of LTE or that I might need a new sim card possibly.
[Nexus 4 Q&A, Help & Troubleshooting] acejavelin:
To be honest, mine started doing it in early August (although MMS has never worked) and I gave up after 4 hours on the phone with their tech support telling me it was an issue with my phone and not their problem. Switched to GoPhone and haven't had a single issue since.

Not sure if this is it either, but an AT&T wireless tech (I work in telecom, this is an actual tech that works on switches and tower sites), that the towers give priority to certain customers like AT&T post/pre paid accounts over MVNOs and if the equipment gets busy it will actually block "nonessential" services like data to lower grade APNs. He said they have seen traffic increases much more than expected from MVNOs in the last couple months... Take it for what's worth I guess.
[Nexus 4 Q&A, Help & Troubleshooting] Shamrock6699:
Well finally got mms working for first time in 2 years. Downloaded a free app that gives you Correct apn settings. It tells you to create two separate apn's, one for mms and one for data. Worked great. It's called tweaker apn.
[Nexus 4 Q&A, Help & Troubleshooting] CaribouLou620:
2 years?? Wow i wish i would have known. I could have helped you out. I figured this problem was already taken care of. Glad to know you got it working tho.
[Nexus 4 Q&A, Help & Troubleshooting] Shamrock6699:
Might actually still need help. For the first time I was able to send a picture message out so I thought it was working. However my friend tried to send a picture back to me and I didn't receive it. Can anyone confirm 100% what the exact settings should be to receive and send MMS message for Nexus 4 running 4.4.3 on Net 10's ATT network?
[Nexus 4 Q&A, Help & Troubleshooting] CaribouLou620:
Hey bud, did you ever get MMS working again??? They changed their APN settings again! These are the new ones Net10 gave me and i have confirmed with several different CS reps.

Please turn your phone off and on. Update your APN settings with the following values:

Name: NET10

APN: att.mvno

Proxy: proxy.mvno.tracfone.com

Port: 80

Username: (blank)

Password: (blank)

Server: (blank)

MMSC: http://mmsc.cingular.com

MMS Proxy: proxy.mvno.tracfone.com (although 1 other CS rep said 66.209.11.33 was the correct IP for this field)

MMS Port: 80

MCC: 310

MNC: 410

Authentication Type: None

APN Type: default,mms,supl
[AT&T Samsung Galaxy Note I717] LuckyStrike88:
I'm running CM10.1 RC1, stock kernel and am interested in swapping memories. I can find threads about this for other phones but so far nothing for the i717. I have a class 10 sandisk 64gb card in fat32 currently and would LOVE to be able to use that as my phone storage for apps. So does anyone have experience editing vold.fstab for these phones? Any help is greatly appreciated.

inb4 16gb is plenty etc etc etc
[AT&T Samsung Galaxy Note I717] LuckyStrike88:
Using root explorer I do not see vold.fstab in system/etc.

I'm currently running the latest carbon nightly (4.3)
[AT&T Samsung Galaxy Note I717] LuckyStrike88:
Anyone?
[AT&T Samsung Galaxy Note I717] sergio2007:
I'm befuddled!? In Root Explorer go to the highest Parent folder, and perform a search for "vold". It will probably take about 5 minutes to search your entire phone, but those two files are bound to pop up somewhere.

Good luck!
[AT&T Samsung Galaxy Note I717] LuckyStrike88:
The only thing that comes up is system/bin/vold but no vold.fstab

I have the setting on which shows hidden files too, definitely odd.
[AT&T Samsung Galaxy Note I717] JamieD81:
https://github.com/CyanogenMod/andr...mmit/d63bd455f4ef664263dda0986bbfee3d3907de31

it was removed in 4.3 with this commit, removed in favor of the new minivold method or something along those lines. you wont see it again.
[AT&T Samsung Galaxy Note I717] sergio2007:
[Q]Where is Vold.Fstab on Android 4.3?

...and the mystery thickens...I just found this. Hopefully, it works: http://xdaforums.com/showthread.php?t=2426804
[AT&T Samsung Galaxy Note I717] LuckyStrike88:
10-4, at least I'm not losing my mind :)

Not the end of the world at this point I'm most likely Note 3 bound anyway.

Thanks for clearing it up and to Sergio for the help as well.
[AT&T Samsung Galaxy Note I717] GT247:
Awesome :)

Would you happen to know if this is only for jb or might work for ics?
[Galaxy S 4 Q&A, Help & Troubleshooting] xologist:
Hello,

Do I have the Samsung i9000 or i9505

This is my phone's info:

SGH-M919	USA (T-Mobile)

- Also, please consider adding a question like this to the "Rom Bible" , or "General" section, it will help people a lot.
[Galaxy S 4 Q&A, Help & Troubleshooting] StuartTheFish:
Look in "about device" in settings and it'll tell you.
[Galaxy S 4 Q&A, Help & Troubleshooting] xologist:
It doesn't say anywhere.

In baseband version it says:

M919UV.... . . .. ...

I looked all over the "about my phone" screen, and it doesn't say neither 9000 nor 9505
[Galaxy S 4 Q&A, Help & Troubleshooting] gruuvin:
I agree... this info should actually be stickied. But it is in a wiki (see link below).

SGH-M919 is your phone's model number. That is the SGS4 model number for T-Mobile USA SGS4 phones.

I9505 is the model number for international versions of the SGS4.

I believe the only difference between those two models is software and not hardware. And by that I don't mean only the bloat (like T-Mobile apps), but which hardware radios are enabled via software, specifically for the T-Mobile operating frequencies and protocols.

Look here:.

http://en.wikipedia.org/wiki/Samsung_Galaxy_S4#Model_variants

I9505 vs I9500 is often used to identify a SGS4 by the difference in processors, where the i9500 switches between two quad core processors (Samsung Exynos) and the I9505 has only one quad core processor (Qualcomm Snapdragon).

All the U.S. variants have Qualcomm Snapdragon processors, so often when someone references the I9505 model with respect to a matter that is processor specific (like rooting guides), your SGH-M919 is implicitly included in the reference. If it is a matter that is radio specific (like performance on specific carriers), your SGH-M919 probably does not apply.

Hope this helps.
[Galaxy S 4 Q&A, Help & Troubleshooting] xologist:
Thank you,

so based on the Table on the wikipedia page, having T-mobile USA, I would have:

Qualcomm Snapdragon 600 APQ8064AB

Which means that I would have the:

i9505

I think I'm correct..
[Galaxy S 4 Q&A, Help & Troubleshooting] StuartTheFish:
Really? Mine does:

Also, did yours not have a sticker on the top near the headphone plug saying "snapdragon 4g" or anything else when you first unboxed it?
[Galaxy S 4 Q&A, Help & Troubleshooting] xologist:
Aha! You sir have won the prize!

Yes, there is a sticker on top of the phone by the headphone that say "Qualcomm 4G"
[Galaxy S 4 Q&A, Help & Troubleshooting] StuartTheFish:
That's the one. There you go then, qualcomm make the snapdragon cpu, which means yours is an i9505.

So does yours not say gt-i9505 in the model number bit then like mine does?
[Galaxy S 4 Q&A, Help & Troubleshooting] gruuvin:
I have the SGH-M919 model like xologist does.

Where you have I9505 listed as the model number in settings>about, I have SGH-M919 listed, and I expect xologist should as well.

The SGH-M919 is is NOT the I9505, although, for most intents and purposes, it is (all same hardware) -- the difference is the programming of the phone for T-Mobile (which radios are enabled, which T-Mobile apps are added).
[Galaxy S 4 Q&A, Help & Troubleshooting] xologist:
You're wrong. I have Qualcom, which is 9505 and I am in the USA.

Both the Category states Qualcom is 9505, and the wikipedia page for USA says I am 9505.
[Galaxy S 4 Q&A, Help & Troubleshooting] datura77:
Mine is showing "SGH-I337" in the model number on this screen. so which one am I??
[Galaxy S 4 Q&A, Help & Troubleshooting] nikzDHD:
I9505 all the American carrier versions should be Qualcomm ones.
[HTC Amaze 4G] ericdjobs:
Fixed it, going to start a new thread for CarbonROM.. considering progress has started to come along very nicely and it's very functional now.
[HTC Amaze 4G] Old-school:
If I remember correctly, intervigil had to build a new RIL for the Amaze to get data to be stable. The HTC ril never worked for data on CM10.

And then some other behind the scenes, which I am too stupid to know.
[HTC Amaze 4G] ericdjobs:
Hmm.. well I'm using the RIL included with CM10.1

DHCP requests go through, I get an IP (mobile data)

android_net_utils_resetConnections seems to be what's resetting the connection

I've been up all morning porting, spent the better part of the last three hours or so... I had to restore my usable backup for work.... but I will continue to work on it

If anyone has any more information, it would be much appreciated :)
[HTC Amaze 4G] sportsstar89:
No its in framework its using the wrong rmnet interface
[HTC Amaze 4G] _Le0.<3!:
string.xml in value folder in framework-res.apk,right?Change rmnet0 to rmnet_sdio0,right?
[HTC Amaze 4G] ericdjobs:
Ah I see it.

<string name="config_datause_iface">rmnet_sdio0</string>

There's a couple other strings that are diff'ing that seem to be the cause of some other bugs I was having.. great! I'll recompile this and give it a shot..
[HTC Amaze 4G] SuperAfnan:
I hope that will lead to the rest of the fixes.

With that we will have more options on the table. :)
[HTC Amaze 4G] _Le0.<3!:
But I use this way to fix the data problem about CM9.But stuck at bootamination.
[HTC Amaze 4G] ericdjobs:
Hmm you have a logcat?

That sounds like maybe the signature verification on the framework-res file is not passing because of the modification? Lucky Patcher can actually modify core.jar to bypass this.

Could also be that there's other places that need modification maybe?

Best bet is to modify the kernel to be insecure and to modify the ramdisk init.rc to throw up adbd ASAP; also check BOOTCLASSPATH always, but usually isn't a problem if porting from very similar devices

(I ported CarbonROM from the HTC VIlle)
[HTC Amaze 4G] xDC23:
hadn't heard of carbonRom....but after looking it up it looks really nice. can't wait to see the finished product :D
[HTC Amaze 4G] _Le0.<3!:
I'm trying.Maybe I use the wrong Apktool version .

Now I'm looking forward to your CarbonRom.Can't wait to try it.:p
[HTC Amaze 4G] ericdjobs:
So guess what guys...

I totally just fixed Data :)

So yeah, I had a lot of trouble getting framework-res modified and working without botching sig verifications and all this crap, been working on this for hours now literally.

There's a ton of other bugs, too.. but now that I know a couple of tricks to modifying the framework successfully I think I can fix them as well.

When I say there's a ton of bugs... I mean there's a good TON of bugs... :P

Home button is not working properly (I believe this is another framework edit) , long press home button recent apps not working properly (This is also another framework settings I think)

Part of the 4.2 quick toggles do not work (Tile style toggles.. but luckily with Carbon you can switch them to the older style regular toggles.. which work fine it seems)

Very buggy indeed... And there's probably a good chunk of stuff I haven't even run across yet. Pretty sure bluetooth isn't working, not sure about tethering yet...

I'll upload some screenshots and a VERY VERY early alpha release here in a bit...

It seems Wifi is working (at least for the most part!) And mobile data appears to be.. working! GSM appears to work fine... was having a bit of an issue with notifications I think but I think I have that fixed.

Also I'm having issues with storage getting mounted... I think I may have fixed but not totally sure yet. Logcat is going absolutely INSANE RETARDO, FYI.. so there's a lot of work to be done.. but hey! Getting a lot of permissions problems, which I think is the source of a lot of these bugs... this is pretty new territory for me so.. heh, going as much as it can be.

BTW the trick for the framework-res.apk edit is to retain the signature from the original file. If you use APK Multi-Tool and use the "Compile System App" option.

Now, once you do that, you want to take the AndroidManifest.xml out of the ORIGINAL framework-res.apk and put it inside your modified framework-res.apk

That should do the trick

*edit: Seems I have home button/recents long press working now, both internal and external SD cards are mounting now... Wifi and Mobile data both appear to be working.. had the wifi drop out for some reason for a second but hasn't happened since..

Camera is working for the most part.. wow the gallery is REALLY nice... best i've used..... Getting a decent amount of mass force-closings from what appears to be ram usage.. haven't even started to tweak any VM settings etc yet though.

GPS seems to be working now as well.
[HTC Amaze 4G] _Le0.<3!:
Great work,man.I think you can fix the other problems easily.
[HTC Amaze 4G] mikef:
Thread Closed

As you have already opened a new thread, this one would appear to be concluded, so I will close it.

Thank you,

mf2112

XDA Senior Moderator
[Upgrading, Modifying and Unlocking] pcheaven:
I have an Anteck Sp-230 Pocket PC

The GPRS on Vodafone UK with web access is unreliable, and downloads corrupted emails all the time.WAP is ok though!

How can I back up my existing ROM / Radio stack so I can then install

an XDA II ROM onto my Sp-230as my XDA II is perfect with web
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] LanceM:
Apparently you can only check for the OTA update every 24 hours... Has anyone figured out a way to get around this minor annoyance?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] raqball:
Change the time and date on the phone forward a few days
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Tenkie:
Clear cache and data from app settings.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] LanceM:
That worked... But Im getting the same error over again...

"Software Update Interrupted"
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] rbj13:
Turning off wifi made it work for me.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] modmyphone:
Fix whatever you changed inside of /system. If it doesn't match out of the box stock, it will fail. If you didn't make any backups to your changes, you'll have to ODIN back to stock and then OTA from there.
[Android Q&A, Help & Troubleshooting] Buleste:
I am trying to fix the Physical keyboard to have full functionality (smiley and symbol keys). From what I can tell the issue lies in QWERTY.kl which is missing a few lines from the stock ROM

#key 11 0
key 11	SMILE
#/* < BU5D09842 weixinghai 20100513 begin */
key 163 MEDIA_NEXT WAKE
key 165 MEDIA_PREVIOUS WAKE
#/* BU5D09842 weixinghai 20100513 end> */

key 194 SYM

Now I've tried editing the qwerty.kl that comes with Icy Tiramisu with various text editors and when I reboot it's as though the keyboard is not being recognised at all. I've even just added 1 line (key 194 SYM) with the same result.

I've had a look at the fixed HuaweiIME.apk that zenaufa made for this ROM and it seems to contain all the correct elements for the smiley and symbol button to work and from what I can tell the changes to qwerty.kl should work. Can anyone give me any insight into what could be going wrong?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jackS991:
Hi

I have a Kindle Fire HD 7. I attempt to change the original bootloader with the FireFireFire; but after rebooting the device, it won't turn on.

I bought the factory cable but my pc don't recognize the Kindle. So it won't turn on and my PC don't recognize the Kindle.

I think that the bootloader is broken.

Is there any way to restore my Kindle and unbrick it? I'm desperate. :(:(:(

Thanks
[7" Kindle Fire HD Q&A, Help & Troubleshooting] bro1:
could it be a dodgy cable, where did you get it from,have you a link
[7" Kindle Fire HD Q&A, Help & Troubleshooting] seokhun:
FireFireFire wasn't made for the Kindle Fire HD 7". It was made for the Kindle Fire 2 (I think, or the first gen). if the factory cable doesn't help, nothing can help you.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] mrkhigh:
Pretty sure you flashed an entire new non functional boot loader which means you have a paper weight at least at this time... I'm sorry...
[7" Kindle Fire HD Q&A, Help & Troubleshooting] AmrBanawan:
The KFHD has a 1 year warranty, Contact amazon and ship it back to them they'll replace it for you!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] boomtekd:
Similar Outcome

Hey, I just wanted to say I had a very similar thing happen to my Kindle Fire HD 7 also. I installed TWRP, got a weird error:

shell@android:/ # dd if=/sdcard/openrecovery-twrp-2.5.0.0-blaze.img of=/dev/block/mmcblk0p5p-2.5.0.0-blaze.img of=/dev/block/mmcblk0p5 <

/dev/block/mmcblk0p5: write error: No space left on device

5+0 records in

4+0 records out

2048 bytes transferred in 0.001 secs (2048000 bytes/sec)

Tried to do a reboot and now no power, nothing at all. I could deal with an odd boot screen, but the fact that no power or anything is recognized makes me think maybe something's wrong with the hardware. BTW, just to make sure if I try this again, I assume I should have gotten something different from the code I put in?

Also, good to know FireFireFire won't work on the Kindle Fire HD 7, but I think it's weird that wouldn't even allow the device to power on. I would at least expect some recognitiong of the device in Windows or something on the Kindle Fire HD that says "Error, you F'd up buddy". However, I am new to all this so if anyone can explain a little extra info on the subject that would be great!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] seokhun:
"Blaze" is the codename of the original Kindle Fire, I believe. You flashed the wrong recovery. And in any case, the only working recovery builds for the HDs at this point are Hashcode's. The official TWRP site doesn't have them.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Scrood:
Hi all, I'm also having similar problems as the OP and another poster in this thread. After hearing my teenage daughter complain about her KFHD7 for months (due to no google play), I thought I'd help her out by rooting and installing Play. I did so, and it worked fine. But then I got cocky and thought I'd install TWRP to later put on Kinology or CM, and that's where things went tits up.

I read over several websites, including this one, and I guess I got instructions confused amongst the various flavors of Kindle Fire. I attempted to install FireFireFire and the 'blaze' version of TWRP. Only after realizing there was a problem did I notice the "write error: No space left on device" message that is also in someone else's screenshot above (highlighted in red below).

Now I get nothing from the KFHD - no messages or logos on the screen, no detected devices in Win7, nothing listed with the 'adb devices' command. Holding power for 20+ seconds does nothing. I occasionally see a very brief flash of light, but that's it. So - at first I assumed I would need a factory cable, but after reading some of the other messages here I'm not sure that will fix it at this point. I'm sure it won't hurt to try, but I'd rather not buy more stuff and wait a few days only to be disappointed again. If that's not an option, will Amazon even take it back on warranty, considering I've already rooted the device? It was bought for her by a relative so I don't really want to have to ask them to be bothered with the return.. Anyway, here's the terminal text that lead up to the brick:

C:\adt-bundle\sdk\platform-tools>adb push u-boot.bin /sdcard/
4690 KB/s (216164 bytes in 0.045s)

C:\adt-bundle\sdk\platform-tools>adb push openrecovery-twrp-2.5.0.0-blaze.img /s
dcard/
5246 KB/s (6291456 bytes in 1.171s)

C:\adt-bundle\sdk\platform-tools>adb shell
shell@android:/ $ su
su
shell@android:/ # dd if=/sdcard/openrecovery-twrp-2.5.0.0-blaze.img of=/dev/bloc
k/mmcblk0p5
p-2.5.0.0-blaze.img of=/dev/block/mmcblk0p5 <
/dev/block/mmcblk0p5: [COLOR="Red"]write error: No space left on device[/COLOR]
5+0 records in
4+0 records out
2048 bytes transferred in 0.001 secs (2048000 bytes/sec)
1|shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.034 secs (6357764 bytes/sec)
shell@android:/ # exit
exit
shell@android:/ $ exit
exit

C:\adt-bundle\sdk\platform-tools>adb reboot

So what's my best course of action at this point? Try SkOrPn's cable or attempt a refund/exchange with Amazon?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] seokhun:
Not your best, your only option. Get the cable.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Scrood:
Ok. Thank you for the reply - at least now there's some hope.
[HTC Wildfire S] srimed85:
Hi ,

I am new to this forum. I have a problem with my HTC wild Fire S a510e. I flashed AKOP Custom ROM for JB 4.1. And all went fine till then, after using it for few days i am facing a issue now.After certain ideal time for an incoming call i am not able to see any display, screen is not getting woke up for incoming call/Text i have to push my power button repeatedly for n number of time then i am able to the caller info. I tried proximity sensor apps but nothing was working as expected.

Please help me in this issue, let me what can be done for this.

Thanks in Advance
[HTC Wildfire S] crashmekiran:
Dude It's the low brightness bug..

Check that's rom's topic for a fix..:rolleyes:
[Android General] Bryandu13:
Hello all,

does somebody is working on a Jelly Bean ROM (4.1 or 4.2) for the Acer Liquid Gallant duo E350 (duo for dual SIM) ?

It's an incredible and cheap middle class phone, under ICS 4.0.3 with a MTK MT6575 single core processor. The OS is very closed to the original one with a very thin overlay from Acer.

The modaco team has already rooted it, BUT ... I'd love to use a Jelly Bean ROM for him, it seems that your ROMs are the best

We are a lot of happy owners which are waiting for it, and we are just answering if it could come a day, .... or not.

Friendship from France and Frandroid.com forum