yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] jayrell85:
cricket messaging app not working right after 4.3 update on S3

Okay, seems like everyone is having problems with sending and/or receiving MMS on flashed (to Cricket) Sprint S3. Just recently, I purchased a Sprint Samsung Galaxy S3. The guy flashed it to Cricket and when I got home, I noticed that I couldn't receive MMS. Instead of calling him back, I decided to find a fix myself to be able to receive MMS on the native messaging app. So this is what I did:

1.Dial ##3282# (this opens the Data Programming Menu)

2.Tap on "Edit" and enter your MSL Code (000000)

3.Go to "MMSC", then "MMSC URL"

4.Change the url to: (see attached image) and hit Okay to apply.

5.Go to MMSC Proxy and change that to "0.0.0.0"

6.Reboot phone and make sure you're connected to 3G.

7.Have someone send you a MMS and it should download and open, using the native messaging app, with no problem!!!

It worked for me and I haven't had a problem since I changed the MMSC URL and Proxy.

Have Fun Sending & Receiving MMS!!!! :D
[Sprint LG Optimus G] bocaccio:
I am coming from the galaxy note 2 and that stock kboard was great but i tend to misspell more on this one and the backspace key can end up erasing a whole sentence sometimes. However i do really like this device. what is the one most widely used?
[Sprint LG Optimus G] BadFish79:
http://xdaforums.com/showthread.php?t=2267687

My choice lately is the Google keyboard on the play store.

Sent from my LG-LS970
[Sprint LG Optimus G] zomgalama:
Swiftkey, Swype, and the stock Google keyboard seem too be the most popular universally on any device.

Personally I've used all 3 and I prefer swype, solely because it's swiping is very accurate, if in some ridiculous circumstance I could no longer swype I would use swiftkey, it seems to do better at detecting what I am trying to tap.

Honestly I find swiftkey flow to be the most inaccurate out of the 3. Meaning the default Google keyboard is a good balance between the two if you switch between tapping and swiping a lot.

Sent from my Sprint LG Optimus G
[Sprint LG Optimus G] MikeDroid:
I've been using SwiftKey. It learns well and the predictive text saves me and my fat fingers hours.
[Verizon Samsung Galaxy S 4] igdawgi:
I'm currently running liquid smooth. Do I just flash the kernel over and wipe cashed and davik; or do I need to do a full wipe then install ROM, Gapps, then kernel?

Thanks in advance!
[Verizon Samsung Galaxy S 4] klabit87:
you only need to install kernel then wipe cache and dalvik and according to ktoonsez instructions fix permissions also.

no need to start all over just to swap kernels
[JAM, MDA Compact, S100 General] Guest:
I know that the cost will vary depending on your network and messenger usage, but I just want to know roughly what to expect. I use T-mobile UK, contract "Relax 100", and would probably be a medium to light MSN user.

How much do you guys pay for MSN usage? and what does price per Mb mean in terms of how many messages you can send? (ie 1 Mb = 1000 lines of MSN input = £5 cost)

Thanks
[General Questions and Answers] droidfun09:
Okay so I went to at&t and bought the HTC one silver/white 32GB. Now I'm somewhat thinking about paying the restocking fee to either get the black one because I feel the white on the silver will turn yellow after time... Or the s4 because we don't know where HTC will be in 2 years (as long as ill have to have the phone for). I'm in love with the build quality and blink feed but I also would like to have 4g lte advance, and a company that won't be dead in 2 years or the possibility....

Would love peoples feed back.

Thank you an advance
[General Questions and Answers] Trozzul:
I would personaly recommend the s4 but if your happy with your htc one Stay with it! I have heard the blink feed can get old after awhile.
[General Questions and Answers] droidfun09:
I mean i guess its just like flip board in a way, but i enjoy my news being in a somewhat organized way... idk i might just have to take the risk... or wait for others to chip in. i appreciate your input.
[General Questions and Answers] jnne2012:
Stay with HTC! Trust me! Htc has never have false financial year and it is always be a profitable company!
[HTC Pico (Explorer)] Crepiii:
Hey there!

Would like to install HTC Sense 4.1 Lite Build#1 from [MENTION=4649424]cute_prince[/MENTION], but i have a question... What do i have to download?

Just update 3 or also Build#1?Also what Kernel to use? Can you provide a link pls?

Is this a stable ROM and smoth just for texting? And is there anything else to do after installing ROM? Like apply Mount2SD script?

Thank you in advance,

Crepi
[HTC Pico (Explorer)] nachiketa.ramesh:
You have to download and flash the rom followed by each patch. It includes the kernel so don't install anything else.
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Hi guys, Total Noob here.

I've been reading through the forums over the last week and am still at a total loss. Despite trying numerous things, nothing I've tried has worked.. If anything, I'm afraid I've made things worse.

The back story: The NC we have is a newer one purchased *just* over a year ago, given to my 10yr old daughter as a bday gift. It's never been rooted or modded in anyway whatsoever. Two weeks ago while she was playing a game on it, it locked up, and wouldn't power off. We let it sit for a couple of days for the battery to drain. After that, the battery wouldn't charge, the NC would not boot and the cable indicator stayed orange. So I purchased, and replaced the battery. I let it sit overnight after replacing the battery, and we got a green light. On boot up, it would hang at the 'N Screen', and do nothing more.

I tried running the NC recovery, but that only resulted in an "INSTALL FAILED" error message, and that was the last sign of life to have been seen coming out of the NC.

At this point, it will only boot off the SD card, (currently using an 8gb with CWR 6.0.1.2), I no longer get even the 'N screen' anymore. I've tried leapinlars partitioning and formatting .zips, I've tried every stock image I could find, but the result is always the same. No partitions are mounted, and nothing but errors are generated.

I've tried connecting through ADB, but 'ADB DEVICES" only returns:

C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery

...and nothing more.

Since this NC is for my daughters use, I'm really not interested in rooting or opening up android for her, I'd really like it to be nothing more than stock, but at this point I'd be grateful just to see some sign of life come out of this thing. All help would be greatly appreciated.

I hope I've provided enough info, anybody have a clue whats going on here?
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
You need to type

fdisk -l /dev/block/mmcblk0

in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.

Report here the output of the command.
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Thanks for the suggestion leapinlar, I assumed fdisk -l would show all disk info by default if a specific disk wasnt specified. For some reason when I plugged the NC into the USB port today, My Win7 box did not recognize it or want to reload the drivers the same way it did last night, and I was unable to connect to the NC through ADB.

I will try to figure out that later on, or try to use ADB through my Fedora box when I get a chance. In the meantime, I once again tried your repair-partions.zip and copied CWM's error log, which is pasted below. Hopefully this gives some insight:
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Okay, got adb working again. Here's the result:

fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #

Well now, isnt that special?

So that got me curious and I took a look/see in the /dev/block folder:

/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
/dev/block # ls -l
ls -l
brw------- 1 root root 7, 0 Jan 9 18:13 loop0
brw------- 1 root root 7, 1 Jan 9 18:13 loop1
brw------- 1 root root 7, 2 Jan 9 18:13 loop2
brw------- 1 root root 7, 3 Jan 9 18:13 loop3
brw------- 1 root root 7, 4 Jan 9 18:13 loop4
brw------- 1 root root 7, 5 Jan 9 18:13 loop5
brw------- 1 root root 7, 6 Jan 9 18:13 loop6
brw------- 1 root root 7, 7 Jan 9 18:13 loop7
brw------- 1 root root 179, 0 Jan 9 18:13 mmcblk0
-rw-rw-rw- 1 root root 73995264 Jan 9 18:14 mmcblk0p1
drwxr-xr-x 4 root root 80 Jan 9 18:13 platform
brw------- 1 root root 1, 0 Jan 9 18:13 ram0
brw------- 1 root root 1, 1 Jan 9 18:13 ram1
brw------- 1 root root 1, 10 Jan 9 18:13 ram10
brw------- 1 root root 1, 11 Jan 9 18:13 ram11
brw------- 1 root root 1, 12 Jan 9 18:13 ram12
brw------- 1 root root 1, 13 Jan 9 18:13 ram13
brw------- 1 root root 1, 14 Jan 9 18:13 ram14
brw------- 1 root root 1, 15 Jan 9 18:13 ram15
brw------- 1 root root 1, 2 Jan 9 18:13 ram2
brw------- 1 root root 1, 3 Jan 9 18:13 ram3
brw------- 1 root root 1, 4 Jan 9 18:13 ram4
brw------- 1 root root 1, 5 Jan 9 18:13 ram5
brw------- 1 root root 1, 6 Jan 9 18:13 ram6
brw------- 1 root root 1, 7 Jan 9 18:13 ram7
brw------- 1 root root 1, 8 Jan 9 18:13 ram8
brw------- 1 root root 1, 9 Jan 9 18:13 ram9
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1

Disk /dev/block/mmcblk0p1: 73 MB, 73995264 bytes
255 heads, 63 sectors/track, 8 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block #
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Do either of these things indicate anything of importance that could potentially be of help?

1) 'adb devices' lists the Device ID as "RECOVERY"

2) The internal memory seems to be in a 'read only' mode of some sort.

The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.

fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0

Then do an

fdisk -l /dev/block/mmcblk0

to see what you get.

If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Here's the result - as before, it just doesn't 'stick'.

C:\android-sdk-windows\platform-tools>adb shell
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.

Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #

Thanks for your help, I really do appreciate it.
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
I have had SD chips that became ready only by some mysterious means. It is possible that your emmc has done the same. In fact, one other user said that happened to his emmc.
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Alrighty then, I confirmed this much at least:

with

dmesg | grep mmc0

The emmc chip in my NC is the Samsung M8G2FA, which is prone to the "Brick Bug", and from the little I've read on it so far, the bug is brought on merely by wiping the cache partitions clean. I got me some more reading up to do...
[Nook Color Q&A, Help & Troubleshooting] MaGoober:
Today, I called BN tech support for the second time in a week, after visiting the local store to see if anybody there could offer up assistance. Long story short, because our NC was just out of warranty (by three weeks) they did offer to exchange it with a 'certified pre-owned' . When that comes in, the very first thing I'm going to do is see what memory chip it has in it, Evidently just trying to do a 'hard reset' and run the stock recovery bricks the M8G2FA EMMC. :( However, I still don't know what caused our NC to lock up in the first place. I guess at this point, that's moot.

leapinlar, I've read through many of your posts, although I couldn't fix my problems, you were instrumental in keeping me sane. ... well, depending on how loosely you define sane, :cool:
[Sony Xperia ZL] danieldp1990:
I still have problems with the notification LED ..... ..... Im i the only one?:(

WELL i decided to open my phone and I just fixed the Notification led lol !!!!! i think its not software problme now charging red works, green works, white yellow blue etc. i can now change whatsapp color and everyting its perfect. im really happy now :D
[Sony Xperia ZL] butatx:
Can you share what have you did to make it work?
[Sony Xperia ZL] danieldp1990:
sure, tell me whats your problema, cause for example mine, sometimes some color woks and some other dont , specially the White yellow and some times the Green.

tell me you exact problema so i can tell you how to fix it.:good:
[Sony Xperia ZL] Faddy89:
In stamina mode it only shows white

But if you switch off screen and with in 5-7 mins if some notifications came it will show other colors according to the app. But if phones goes to deep sleep it shows only white to me.. :/
[Sony Xperia ZL] danieldp1990:
hmmmm well. ok look this is how i fixed mine. and its working great:

first i open my phone. its easy i did it by myself cause i dint find any video on youtube.

when you open your phone there is a black plastic just back the notification led. that black plastic was making to much presure on the led circuit causing it to be crazy and not 100% working at all. so i figure that the piece of plastic have some kind of soft plastic that i took off and that was the problem.

maybe later i will post a video on how to open the phone xperia zl.
[Xperia Z Q&A, Help & Troubleshooting] defsix:
I'm have problems with the social life app. It used to work fine but when I updated to FW to a Euro generic when ever I try to start the app it asks me to pick my language/country and gives me the T&C's , I accept but then I am sent to the Play store to download Sony Account Manager which it says isn't compatible with my device.

Any ideas how to fix this ?
[Xperia Z Q&A, Help & Troubleshooting] LitoNi:
LOL can't stop laughing at your title.

Anyway, wipe the data settings / apps / social life / clear data. Do a reboot.

If that doesn't work uninstall social life, titanium backup may be needed to remove it.

Then go play store and download it again.
[Xperia Z Q&A, Help & Troubleshooting] defsix:
Thanks for the reply, I have tried this several times. Everytime I try to sign up I pick Sony Entertainment Network and it takes me to the Play Store to download Account Manager. I don't use/have a Facebook account. I am trying to think have I removed something from System/Apps that I shouldn't have done.
[Xperia Z Q&A, Help & Troubleshooting] LitoNi:
To my extent of knowledge, it may actually have something to do with that "Account Manager." I remember seeing that on my phone as well but I deleted also, since I do not use SEN.

your best way is to start fresh again if you dont know what you've deleted that may have caused this issue.

1-Back up all your internal files (whatsapp, data counter, messages, etc...) and sync whatever (calenders. task, notes etc...)

2-Repair it through Sony PCC or Sony Update Service, or Flash another FTF file and wipe everything.

3-Download all your apps again and restore them one by one.
[Xperia Z Q&A, Help & Troubleshooting] Metallijim:
Flash German .253 ftf. I had same problem, but the German firmware had this preloaded.

Sent from Z Beast
[Xperia Z Q&A, Help & Troubleshooting] defsix:
Thanks, I'll wait till the next update, 4.2, and give it a try then.

Sent from my Brain via my Keyboard on my Xperia Z
[Xperia Z Q&A, Help & Troubleshooting] danw_oz:
Thanks for the laugh :), I was going to say something about your title yesterday.
[Xperia Z Q&A, Help & Troubleshooting] defsix:
The time I posted - 12.52AM said it all ! :laugh:
[Samsung Galaxy Nexus] MikeMurphy:
Hi guys,

I had my Gnex for more than a year and thought I was one of the lucky ones without USB wake problems. That is, the USB port thinks it's being plugged in or unplugged causing the screen to turn on and subsequently kill your battery. Unfortunately, I started noticing the phone turn on occasionally. Then, it progressively got worse over the course of about 6 weeks to the point where it had to be plugged in several times a day.

One of the tricks that helped in the short-term was to move nudge/coax the contacts in the port in an upward direction. So, with your phone facing up insert something very thin (ideally plastic or paper-based) between the bottom of the port housing and the nipple thing that sticks out that has all the copper contacts on it. There is almost zero room, so you'll need to search for a suitable tool. Once you put a bit of pressure in an upward direction for a few moments you'll find your phone doesn't wake up at all, or as much. Unfortunately, that only helped for a while.

I'm not sure what the cause of problem is. I hypothesize that corrosion occurred when I left my phone in the washroom while I had a steamy shower every day for a few months, but who knows.

I found no suitable software workarounds.

I didn't want to junk the phone, so I ordered a replacement part for only $5.99 + shipping. You can find the part here: Witrigs. Given the price, I suggest you order two. I don't recall the shipping, but it wasn't expensive. Delivery was around 7 days to Canada (from Hong Kong). Website is definitely legit. Maybe add some other parts to your order, if you feel so inclined.

The install wasn't too bad. I'm a dummy and thought I would skip steps that I didn't think were necessary, like removing my sim card. Don't skip steps! The iFixit instructions I followed don't seem to be around anymore. There are guides on YouTube etc that are helpful but they make it look way too easy. Expect to struggle with removal of the screen from the casing. Be careful when you're jamming around into the edges because there are many delicate sensors and buttons which can be broken. Credit cards work well. Overall it's safe, just use your common sense.

Overall, the replacement wasn't too bad. Unfortunately, the replacement part was IDENTICAL to the outgoing port. I was hoping there was a revision, but no dice. I'm glad I bought the second replacement port, just in case I have the same problem in the future.

Anyways, I did this a few months ago and am trying to remember the best I can. I hope this might help somebody.
[Samsung Galaxy Nexus] beekay201:
Thanks for sharing your experience,MO and advices; I can remember several that had the issue and some fix it by just working around the usb port with a suitable tool, others tried to replace the part without sucess, and others with sucess;

Offtopic: I think this thread belongs in General, no question here. Reported.
[Samsung Galaxy Nexus] sarkar1990:
Replaced my charging port + flex board yesterday. Ordered the replacement from Aliexpress for $3.something and free shipping! Took around 2 weeks to reach me, but the part works perfectly and you can get faster delivery by paying for express delivery.

The iFixit guide is still there:

1. http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/1

2. http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1

Also looked at various youtube videos before I finally undertook the replacement.

Cheers to everyone who fixed their own phones!!
[Android Q&A, Help & Troubleshooting] VoidShark:
Hello again , i managed to get my hands on a modded e3 recovery and i downloaded root explorer to put my modded e3 recovery file into the system/bin folder as instructed in another tutorial but my phone seems to be missing its recovery file from the bin folder. I found it in another location. Assistance would be great! And as always thank you :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] a.mozid:
Hi all,

I am having the same re-occuring issue with all pure android jb roms like paranoid android, carbon rom, and CM rom. After flashing the ROM the battery stops charging. After removing the battery and putting it back on the issue is still there and also each time im getting a different battery level reading. The strange thing is that when i flash a touchwiz based rom eg; ultimate JB the battery charges normally without any issues. Has anybody else experienced this issue? I would be very grateful if some could suggest a solution to this problem

Thanks,
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
Flash these ROMs cleanly with the wipes. I have used CM, Asylum, PAC, Supernexus and other ROMs which have varied bases and have not faced the problem. Clean install of the ROMs should work, and also try erasing the battery stats.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] a.mozid:
re flashed rom with all neccessary wipes

I re-flashed cm 9.1 stable, I carried out all necessary wipes, it is getting charge, but it only charged 10 percent in 1 and a half hours, also the charge drops really fast. I really love the UI of these sort of ROMS but always having the same issues :( . Might have to revert back to ultimate jb rom. :(

If you can help me please do, I so badly want an aosp rom.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
Try the AOSP based paranoidandroid or supernexus ROM. How old is you battery?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] happy3777:
I thing just flash stock jb via Odin..

Then flash ROM with cwm with all procedure..

This may fix or problem..

Be aure that phone charging on other ROM(ICS)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] a.mozid:
My battery is about a year old, I flashed supernexus yesterday and the issue with the charging was present. So I flashed back to ultimate JB ROM and the phone is charging fine, it also charges fine on rocket rom, so it seems as though the issue is only present when I flash aosp based ROMs
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] mindfck1337:
try other kernels
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] juk08gt:
having the same issue with carbon rom. wipe everything reload rom and it is fine for awhile then the battery stops charging again. swap batteries and the still doesn't work. go back to a touchwiz and all is fine. i am using a galaxy s3. funny part about it is that when i plug in the charger, the battery icon (dotted circle with text) starts rotating like it is charging but go into status and it say that it is not and the battery drains fairly fast. faster than normal use. it would be nice to figure this one out as i really like the carbon rom.