yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy Note II] goodpup420:
I'm sure ull probably protest this statement but it sounds like you didn't follow instructions when flashing. I've been using Jellybomb since the inception and I never had one of those bugs on 13. We have to ask ourselves when we run into problems no one else has what did I do wrong? If no one is helping you figure out ur problems no one else is experiencing them. Sometimes jellybomb works better when u dirty flash on top of an older version sometimes a clean install is better. Every rom and every phone is different. There is somewhat of a luck factor when flashing that everyone expects should be universal to all roms and every phone should act the same. I've literally flashed and restored 20x in different ways and combinations to get some roms working perfect. Sometimes u just have to make sure u have all the files to fix ur phone then just play around. You only get more comfortable with the process each time u flash f it up fix it and reflash. It's not as easy as expecting others to figure it out for you but u get more out of it and u won't feel so helpless in the future. Just my $.02. Also pulling the battery in the middle of a boot cycle is never recommended for any computing device. I suspect u could be right in that ur still experiencing issues from that. U should probably Odin back to stock and try again. Also if ur firmware version isn't lk8 then that firmware is not compatible with Jellybomb 13. 13 is lk8 only. The newer 15.3 is a hybrid so u can use any firmware with the rom. And why are you still on 13 when 15.3 is out anyway?

Sent from my SPH-L900 using JellyBombed Tapatalk 2
[Verizon Samsung Galaxy S III] fatalfuryy:
I would like to know if someone could point me to the correct file to change the clock, am/pm and day abbreviation from Grey to ICS Blue. I have been changing the status_bar.xml and tw_status_bar.xml but i could be changing the wrong files or inputting the incorrect information. Could someone provide some assistance with this request?
[Verizon Samsung Galaxy S III] ddurandSGS3:
you need to provide information about your phone in order to get help.
[Verizon Samsung Galaxy S III] fatalfuryy:
Verizon Samsung Galaxy S3 VRBMB1. I am also using AndyBones's CR 6R2 AOSP Theme. I attached my SystemUI to this post. Hopefully that will help.
[Verizon Samsung Galaxy S III] fatalfuryy:
CLOSE Post. I figured it out
[Samsung Galaxy Nexus] majorpay:
I've done some research on this issue, and I'm afraid the answer is going to be: "it is what it is," but I recently acquired this phone and have noticed a decrease in cell coverage over my (*wildly awful*) LG Revolution.

For starters, 4G seems flaky at best. It has 4G coverage, but it is very spotty, unpredictable, and sometimes, even when it says 4G, I'm getting speeds equivalent to dial up (much worse than 3G). I can safely state it has significantly lower 4G coverage than my Revolution did. As for voice reception, while it has not cut out on me when I'm "above ground," it is non-existent in my basement. While this would seem to equate to a "well duh" statement, my previous Revolution was able to get a bar.

My phone is up to date with the latest updates, and is running on 4.2.2 with a baseband version FK01/FK02.

I'll say that it is a beautiful phone that was crafted fantastically as a solid Android device that would put my old phone to shame, but it seems like maybe this phone was crafted as a 4.75" tablet first, then the radios were slapped on as an after-thought? Has this been anyone else's experience? Are there fixes for these issues, or is this an inherent hardware issue?

This is my first Samsung phone on top of several Samsung tablets I've owned. While they are winning me over as an Android manufacturer, they are sliding off a cliff as a phone manufacturer so far (LG took that dive from 20,000 ft.)...

On an aside, battery life is a bit of a joke as well. I have orders in for batteries, extended batteries, etc. to fix that problem, though.
[Samsung Galaxy Nexus] t1.8matt:
these are all issues that have been covered many times over. yes, the lte version has crappy signal pickup. mine is horrible for being in a decent size city with full 4g coverage, and 3g is even worse, a complete joke if you will. you can try flashing different radio combos to see what works for you. and battery, you hit it on the head, all you can do is get a bigger battery and try different kernel and setting combos to try and max out battery life. good luck with your phone, it's a great phone though for being over a year old now.
[Verizon Samsung Galaxy Note II] TabGuy:
When navigating in maps I still get a voice telling me to turn but it no longer says the street names. I'm sure it's some kind of setting or conflict but I can figure out what caused the voice turn by turn to stop saying the street names.

I notice when I go into TTS settings there's nothing there. Have I lost TTS and that's why there are no street names being announced?

How do I get TTS back?

Any ideas on how to fix this?
[Verizon Samsung Galaxy Note II] Kryptonian_Knight:
I second this question
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
ok so i have an AT&t HTC one xl running the latest jellybam rom and on rohans B6 kernel. last night on my way to work i plugged my phone into my OEM car charger, the phone rebooted and was stuck on the red text screen saying its a development build....the phone has been dead since. I let my phone "charge" for ten hours but nothing. normally when the phone charges on or off it still gives off some heat but ice cold. when i woke up this afternoon i tried to plug my phone into the computer and run adb but no luck. But i know its not completely dead. the phone shows up in device manager and makes a little toggle sound when plugged in. its still under warrenty but im worried that if i send it in they will make me pay for the repair since its rooted and bootloader unlocked. ive attached a picture of my device manager. Anyone know of a way to fix this or where to look?
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
So your screen still turns on? Or is it dead and unresponsive?

If the latter, it sounds like the power management bug. I've seen a number of phones brick from this.

If your screen still comes on, it's just a matter of getting into the bootloader. Hold down power and vol down until the buttons flash, then release power until the bootloader screen comes on. Once there, you can run a ruu or reflash your rom/kernel.
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
i guess its the power management bug then. the only response i get from the phone is when i plug into the computer and the computer tries to install drivers but fails. screen wont turn on, no led, and no flashing buttons....is there any fix other then warranty claim?
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
You might try the JET tool in the development section.
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
ok would that be in the OG development or the other also thank you for your help.

EDIT: nevermind i found it. ill give it a try before work
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Re: [Q] bricked one xl after charging

http://xdaforums.com/showthread.php?t=1966850
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
For some reason i couldn't get jet to work so i tried the manual unbricking thread method and couldn't get my partitions to shw up in linux. Im gonn send it in for warranty and pray they dont charge me for root and s off lol thanks for your help anyways guys
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
is your car charger a real "htc charger" or some generic crap? i've had generic crap kill good phones.

have you volume down + power to get into bootloader?
[AT&T, Rogers HTC One X, Telstra One XL] exad:
If he could reach bootloader his phone would not boot to QDL mode. It would boot to HTC Screen and not past that. the HTC boot Screen is comparable to a PC's POST. if no EMMC partition table is not detected, it's HTC replacement or JTAG.

I'm sorry for your bad luck OP. Please post back to let us know if HTC did in fact replace your phone. I am curious to see how things play out.
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
it was a legit htc one x charger....its safe to sqy ill never use a car charger again. and ill let you know im a little worried cause ive seen alot of horror storys about their warranty policy but i hope it works out
[AT&T, Rogers HTC One X, Telstra One XL] mcnaught82:
I did a warranty claim on my first htc one x that was rooted. AT&T gave me no hassle and shipped me out a new phone right away. They asked me what my phone was doing and i said its stuck at the htc screen. I did leave out tho that the phone was rooted.
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
update

BUMP for an update

So HTC received my phone last Friday and had it shipped back to me by Saturday night and I just got it today. Pretty sure it's the same phone. I had an otterbox on mine day one so it was in mint condition but pretty sure its mine. I'm not rooted or s-off anymore I have 2.20 firmware as well so ether they couldn't see that I tampered with it or they just didn't care lol. Not gonna complain though cause I got my baby back. Thanks everyone for all their help.
[AT&T, Rogers HTC One X, Telstra One XL] Herc08:
Should be able to root and gain everything back. Glad everything worked out.
[AT&T, Rogers HTC One X, Telstra One XL] SkizzyNinja:
Thanks...I'll probably just update the firmware to get rid of the stupid push notification. My upgrade is ready may 20th so I'll just get an s4 and root that when available lol
[AT&T, Rogers HTC One X, Telstra One XL] area51avenger:
Unlock. Root. Soff. Then take use 3.18 ruu. So if the person who you sell it to wants to root they can

Sent from my VENOMized HoxL
[Nexus 4 Q&A, Help & Troubleshooting] michaelsp9:
I've had my Nexus 4 for about 2 weeks now and currently it is taking a ridiculously long time to charge. It has been hooked up with the original USB to Micro-USB cable for about 3 hours at it went from 12% to 8% (wtf...) to 10% now and hasn't moved for the past hour. Someone help please :)
[Nexus 4 Q&A, Help & Troubleshooting] steviewevie:
Try charging it from another charger it or a PC. Sounds like your charger is probably faulty.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] michaelsp9:
Thanks for the reply, I switched USBs and it is not going any faster
[Nexus 4 Q&A, Help & Troubleshooting] Sherrillface:
Reboot
[Nexus 4 Q&A, Help & Troubleshooting] steviewevie:
When you say you switched USBs, you mean a different charger?

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] michaelsp9:
Yea
[Nexus 4 Q&A, Help & Troubleshooting] dangtd2:
i've got the same issue.

reset the phone may help.
[Nexus 4 Q&A, Help & Troubleshooting] steviewevie:
Yeah you could try a factory reset. Failing that, re-flash the stock ROM. Failing that, RMA it.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] Foxnov1990:
I'm not entirely sure wether this is a "good" answer but are you charging by USB meaning plugged in your computer or laptop?

Because I've had it with several phones that if you put it in your laptop it doesn't charge or very very slowly. In the PC it goes faster but not as fast as straight from the wall.

Try plugging the charger in a wallplug, see if that helps? And also if you really want to charge by PC, flash a kernel (see Franco's thread) and put it on "Fast charge USB", then it should go at the same speed as wallcharged. (dunno how on stock rom)

-------------

If you meant that you've charged by plugging it into the wall in OP, then I'm sorry, I don't know :o Or just a faulty charger.
[Nexus 4 Q&A, Help & Troubleshooting] jibin717:
Daydream

disable daydream (while charging)
[Nexus 4 Q&A, Help & Troubleshooting] shinewithme:
This also happens to me and I found out that when I plug my phone wall charger, in the battery menu it shows that the phone is charging using "USB" instead of“AC".....any help?
[Nexus 4 Q&A, Help & Troubleshooting] ShinnAsuka:
Do you have a custom kernel installed? Maybe there is a faulty setting in there. Worst case scenario is RMA, but try having the phone plugged in and then power the phone down. Once it's off, press the power button (don't hold it) and see if a battery animation comes up. If it does, then keep it plugged in for a few hours and see if it charges any faster...
[Nexus 4 Q&A, Help & Troubleshooting] flintdragon:
try a different cable. For me, the cable went bad. when connected to the oem wall wart, my phone would sometimes be charging USB, sometimes A/C. After changing the cable (not the wart), always charges A/C now.
[Nexus 4 Q&A, Help & Troubleshooting] Solutions Etcetera:
Install a battery utility and verify how much current it is drawing.
[Nexus 4 Q&A, Help & Troubleshooting] gpvecchi:
I don't have a backup of stock file (my fault!), could someone share it, please? Thanks!
[Nexus 4 Q&A, Help & Troubleshooting] steviewevie:
http://db.tt/92eBPCHs

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] gpvecchi:
Thank you very much!
[MDA II, XDA II, 2060 General] sleekool:
Is it possible? It seems so easy...

Will the warrantor do that?
[MDA II, XDA II, 2060 General] sleekool:
Possible? not? thanks
[MDA II, XDA II, 2060 General] cruisin-thru:
Wear and tear due to operator use will not normally be covered by warranty, make sure you keep your phone in a case and always use a screen protector is best.
[MDA II, XDA II, 2060 General] sleekool:
I know but will it be possible to cover the scratches? or bumps? with the same color paint of the xda II? thanks for the reply
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
Hello...

is the new firmware XXEMC2 safe from brickbug?

greetz
[Galaxy S III Q&A, Help & Troubleshooting] AndroidPlant:
Im running fine on that on my S3.
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
AW: XXEMC2 safe?

Is the Kernel safe with Update7 libraries? :o
[Galaxy S III Q&A, Help & Troubleshooting] AndroidPlant:
Not sure. I am running custom.
[Galaxy S III Q&A, Help & Troubleshooting] LenAsh:
It has update 10 kernel source so yes it's as safe as any since ELLA.
[Galaxy S III Q&A, Help & Troubleshooting] aureliomilitao:
this new update , any better in s3 ???
[Galaxy S III Q&A, Help & Troubleshooting] xeroxide:
well, the ella update started freezing my phone, this new update fixed that.
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
:(((

I've flashed the new Firmware.... all is working fine... except Framaroot... :( It's very bad!

I hope that the devs of Framaroot will add Support of XXEMC2....

Greetzz....
[Galaxy S III Q&A, Help & Troubleshooting] blackhand64:
Why not just use the good old Odin flash

What's so good about Framaroot?
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
Because Framaroot is very fast, don't increases the FlashCounter and it keeps the Device Status on Normal....

CF AutoRoot isn't very fast, increases the FlashCounter and makes the Device Status on Custom.

Framaroot roots my device in less than 15 seconds on my device....

For CF AutoRoot I need my Computer....

Greetzzzzzzzzzzz....
[Galaxy S III Q&A, Help & Troubleshooting] delsus:
You know you could use mobile Odin, which flashes the ROM from your phone, and if you check ever root it will root whilst it flashes.
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Need root for mobile Odin ;)
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
Yeah; on my device XEMC2 batterylife is better!

Did you wipe your data?

And.... Great News.... Framaroot is now working for XXEMC2!!! :)) Aragorn Exploit will do it!

greeeetzzz

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] phillim:
No, I didn't. I'll try a factory reset.

Thanks for the tip.

Mark
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
Oh, now I feel that my battery drain a lilbit harder ~7-16% per hour....

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] phillim:
Yes, that's about what I see. A factory reset hasn't changed anything.

Still, at least there have been no more crashes.

M
[Galaxy S III Q&A, Help & Troubleshooting] toxic34:
Its good but it is only a temporary root as soon as you factory reset your phone it disappears
[Galaxy S III Q&A, Help & Troubleshooting] TheRealFelix0212:
Nope! I tested it. It's full root. If you reset it, it'll be still there

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] rtufeanu:
Framaroot

[MENTION=4720993]TheRealFelix0212[/MENTION]

What version you used Framaroot: v1.3, 1.4 or 1.4.1?

Once the device has been root can install Custom ROMs?

The procedure involves no risk?

Thanks a lot!

Samsung Galaxy S3 16GB Blue

GTI-I9300XXEMC2

Android 4.1.2
[Android General] brakke97:
What's Project butter?

​

Google’s Project Butter addresses speed to make the user experience “buttery smooth” in three distinct areas. Project Butter applies to the entire OS, not just the launcher, so this smoothness should be immediately available in every app running on Jelly Bean.

Vsync

Vsync improves graphical performance and increases the frame rate to 60fps! To ensure a consistent frame rate across the entire experience, Android 4.1 extends vsync timing across all drawing and animation that the Android framework handles. Everything is coordinated to a 16 millisecond vsync “heartbeat” — application rendering, touch events, screen composition, and display refresh. So frames don’t get ahead or behind.

Triple Buffering

There are three major components involved in showing something on the screen: the CPU, GPU, and the display itself. Triple Buffering allows the CPU, GPU, and display to work together for much smoother animation. Triple Buffering brings more consistent rendering that makes everything feel smoother, from scrolling to paging and animations.

Touch Responsiveness

Touch Responsiveness “anticipates” or predicts where you’re likely to put your finger on the screen, and gets ready for that tap, making whatever action is behind it that much faster to load.

Jelly Bean reduces touch latency by synchronizing touch to vsync timing (which we mentioned above). By anticipating where your finger will be at the time of the screen refresh, Android 4.1 is more reactive and and presents a more uniform touch response. Also, after periods of inactivity when Android has dropped the CPU speed to extend your battery life, the OS will apply a CPU “input boost” at the next touch event, to make sure the CPU is ramped up to speed so there’s no latency.
[HTC Amaze 4G] avenged_sevenfold27:
I'm currently running viper sense 4 when I'm using adownloader to download torrents the download is always freezing not the app freezing just the download and when I open up shadowgun dead zone then click signin the screen glitches like colored lines across the screen like you would notice on the first Nintendo when the game wasn't fully connected to the system and it caused me to remove my battery to turn it off and turn back on is there a fix?
[HTC Amaze 4G] Shadow Samurai:
I've just got a bad download of the game. Nothing is wrong with the ROM. I play shadowgun on my amaze and it works perfectly

Sent from my Jelly Beaned HTC Amaze!
[HTC Amaze 4G] avenged_sevenfold27:
I figured out the issue the game needed an update lol I'm such a noob lol and I knew it wasn't the rom I just knew I was doing something wrong lol
[Samsung Galaxy Nexus] Icebluemale30:
For the past few i have not had any data connection phone works fine but no data im in New York anyone else have same trouble im also on AOKP MR1 build 6 thanks for any help
[Samsung Galaxy Nexus] FrostyF7:
When did the problem occur? Did it randomly just start happening or was it after a flash?
[Samsung Galaxy Nexus] Icebluemale30:
Thanks for the concere but i just switched roms and its all good dont know what happened it must have been the rom i was on AOKP build 6 i just switched to CM 10.1 and i get it all now 3G 4G and even my voicemails poped back in crazy .........
[Galaxy S III General] AndroidPlant:
Restoring A Stuck Samsung Galaxy SI, SII and SIII​

Is your phone stuck like this?

Then read on! If not, this may only be useful for those who want to go back to the original Samsung Firmware.

Introduction

Too many people are getting stuck on the Samsung logo so I decided to make a tutorial on how to

get yourself off it. It is a simple tutoiral and noob friendly, but it will take time and patience because

the stock firmware is not just 300mb but can go into 1GB and more. This should on Samsung

Galaxy SI, SII, SIII. They are all tested and working, you may experiment on other phones if you

wish and you have no other choice. Read on for the downloads and instructions.

Downloads

Odin v3.07 - Click Here

Your Firmware - Find Here

Instructions

1. Go here and select your phone and its correct version's official firmware here: http://samsung-updates.com/latest-firmware/

2. Download Odin v3.07

3. Turn phone off completely and put it into download mode (Down Volume, Home Button and Power Button together).

4. After downloading the official firmware extract it and open Odin.

5. Select Auto Boot and F. Reset and put that .md5 file in the PDA section. NOTE: There should be COM: (PORT NUMB) in the first box.

6. Click Start and wait. If it succeeded then it will say PASS in green.

NOTE: This has worked for me and other people have confirmed it working for them after testing.

But if something more happens to your phone, I am not responsible.

Good luck.
[Galaxy S III General] AndroidPlant:
Will be attaching more tutorials soon.
[Galaxy S III General] JJEgan:
This is just a stock firmware flash via Odin as per multiple guides on the forum .

Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .

Multiple exact same guides in my view only confuse noobs .

jje
[Galaxy S III General] AndroidPlant:
Got me off stuck on a logo.
[Galaxy S III General] slaphead20:
A wipe data often fixes that too, if you have custom recovery,a dalvik/cache wipe could potentially fix it.

A re-flash of the Rom could fix it

.....indeed many things "could" fix it........I know your intentions are good, but could you refrain from posting links to this thread every time a problem comes up, because often the solution is much easier ;)
[Galaxy S III General] krisando:
There doesn't seem to be any i9300 firmwares on that site.
[Galaxy S III General] SocrasPt:
Hi, im doing everything as it says but gives me this

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Added!!

<ID:0/007> Odin engine v(ID:3.1005)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> SingleDownload.

<ID:0/007> recovery.img

<ID:0/007> NAND Write Start!!

<ID:0/007> cache.img

<ID:0/007> FAIL!

<ID:0/007>

<ID:0/007> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

please help me
[Galaxy S III General] audit13:
Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.
[Galaxy S III General] SocrasPt:
help plz

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9300XXUGOF1_I9300OXXGOF1_I9300XXUGNB1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> sboot.bin

<ID:0/004> NAND Write Start!!

<ID:0/004> tz.img

<ID:0/004> boot.img

<ID:0/004> recovery.img

<ID:0/004> system.img

<ID:0/004> FAIL!

<OSM> All threads completed. (succeed 0 / failed 1)

Cant pass this part.
[Galaxy S III General] SocrasPt:
Yes, i've already done that still nothing.

Could it be hardware related issue?