yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] MclDev00:
You can delete everything and flash a stock rom before returning it. Which model of phone are you using?
[General Questions and Answers] leo_kendall:
rthats what i did.
[MDA II, XDA II, 2060 General] Fais:
This is my first pda so please forgive the stupid questions...

1. I am at a loss as to how i can switch off the xdaII completely. I can dim the screen, and switch off the screen, but not the entire xdaII. The bluetooth light and the green light flash continuously, unless i remove the battery catch down.

2. is there a way of getting a better battery indicator at the top, without having to go through the settings menu all the time. I can't seem to create shortcust of any kind.

3. ultra profiler... is it just me... i switch it to silent and it makes no difference.

Thanks...
[MDA II, XDA II, 2060 General] pdhenry:
Why would you want to turn it all the way off? This results in what is known as a "cold boot" - everythng in RAM (even the current date & time) is erased and the phone goes back to the way you bought it.

I don't know how to do it on the XDAII. On the XDA you press a piece of the stylus into a little hole on the bottom.
[MDA II, XDA II, 2060 General] cruisin-thru:
Fais, on the XDA 1, to switch off both phone and pda, first either hold down the red handset button for a while or tap the signal meter top right of screen and switch off radio/phone, then hit the power button once for a very short time. This will switch off phone and pda. I cant comment on xda2, dont you have a user guide?
[MDA II, XDA II, 2060 General] tadzio:
Well, you must turn off the PDA part and the telephone part separately. For the PDA part, there's a hardware button (which I guess you knew already... :D). To turn off the phone part, tap on the antenna indicator and select the first "link" in the bubble that appears. On an MDA I, the phone could also be turned off by holding the red "hang-up" hardware button for a few seconds. This does not work with the MDA II. It's not clear if this is a bug that will be corrected through a software update or if it's a feature.

Note that all that does not really turn your MDA II completely off. But you don't want that anyway, because you'd lose all your data and installed programs, as they are in RAM only.

There are many programs that can display battery and/or storage indicators on your "today" screen. Try searching for "battery" at Handango. The only program I found so far that indicates the battery status directly in the navigation bar is SmallMenu (http://tillanosoft.com/ce/smenu.html)

Cheers

Daniel
[MDA II, XDA II, 2060 General] Tekflow:
1. Tap on the network indicator, on the right middle part of the Navigation Bar (at the top of the screen), then click on "Turn Wireless Off". Then click on the Bluetooth connection on the right side of the command bar (bottom bar), and select OFF. All your flashing lights will go off.

2. Download "BatMemTime" (find it on Google). It is a free today plug-in

3. I don't use ultra profiler. You may try "My Phone Profile" by JGUI, I think it has more features.
[MDA II, XDA II, 2060 General] Fais:
Thanks everyone for the replies and links to batt indicators... that was a big help!! :) i've been so used to the p800 that all this is so new to me... :oops: The manual doesn't make it clear for a non-pda user about switching the xdaII off.... not to me anyway.

Tekflow thanks... i can switch off the bt quickly and switch on just as easily now... and more important sleep without having to cover the phone with by jacket at night :roll:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] JJ Chuckles:
Are there any ROMs for KindleFireHD that work well? If so, how do I use get/them?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] DroidIt!:
Only one ROM so far. Kinology ROM. Just go to 7 inch KFHD android development forum and follow the instructions exactly. I found the Tom to be much better than stock. Much easier to intall all the Google apps and whatever launcher you want.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] quan_1986:
install Kinology ...nice....but very brief Battery : (
[7" Kindle Fire HD Q&A, Help & Troubleshooting] mrkhigh:
These responses assume you own the 7 inch variety...

There is no good kernel for the kfhd7, so no real Roms yet.. just modded stock roms
[7" Kindle Fire HD Q&A, Help & Troubleshooting] JJ Chuckles:
I think I will stick to my current root, seeing as my battery is already down. Although, if this Kinology ROM will change my status bar and such, I will probably do it. Also, will Titanium backup work with it?
[Atrix 4G Q&A, Help & Troubleshooting] mmmmm12:
Hi, i'm using this ROm http://xdaforums.com/showthread.php?t=2060064, it's exellent accpect the scrolling is quiet lag, i mean in setting menu and searching on Web, it's doesnt as smooth as other, in the past when i make a big scroll, it comes straight to the end of the page but with your Rom it comes to the middle and stop right there, tks, Hope u guys could help me
[T-Mobile, Samsung Galaxy SIII] OneIdiotInATree:
Hey guys,

So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.

Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.

Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)

I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.

Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.

Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.

Thanks so much for any and all help.
[T-Mobile, Samsung Galaxy SIII] monkeypaws:
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
[T-Mobile, Samsung Galaxy SIII] OneIdiotInATree:
It auto-wiped to upgrade to 4.2.2, so if there is a way to downgrade it to get it to work, I'd love to know. At the moment all I can access is the Clockwork Mod boot list from the vol+pow+home route. Did a battery pull and entered recovery. Still nothing. If I try to boot without going through the vol+pow+home method, it just vibrates and then nothing.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Update recovery.

Wipe everything except sd cards.

Install rom.

Install Gapps.

Factory reset.

Done.
[T-Mobile, Samsung Galaxy SIII] OneIdiotInATree:
I formatted everything from that vol+pow+home menu.

Gapps? Is that something I should install from SD?

Sorry, I'm just a bit overwhelmed by something I thought would be easy...
[T-Mobile, Samsung Galaxy SIII] monkeypaws:
Gapps are Google apps that are required to flash after flashing an aosp ROM. They are usually included as a separate download in the first post of the wrong you are downloading. Make sure you download the right gapps. There shod be a setti ng in cwm to turn on USB connection when connected to comp. So you can load the gapps to your SD card. Then re wipe phone through recovery, reflash the rom , the in the same menu reflash gapps. Then reboot. It should then load properly . Otherwise. If you can access download mode, restore stock rom with Odin, reroot and try again from step one.
[T-Mobile, Samsung Galaxy SIII] SamsungGui:
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
[T-Mobile, Samsung Galaxy SIII] OneIdiotInATree:
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?

At this point, I just want to restore to the original loadout, but I've been unable to do that too.

By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
[T-Mobile, Samsung Galaxy SIII] Da Kine:
Make sure you have the ROM of choice and compatible Google apps on your SD card.

Now do the following

1. Pull battery out of phone

2. Put battery into phone

3. Boot into recovery (volume +, home button, power button)

4. Wipe cache

5. Wipe dalvik cache

6. Wipe data/factory reset

7. Install ROM

8. Install gapps (Google apps)

9. Wipe cache

10. Wipe dalvik cache

11. Reboot phone

Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).

|When Emotion Goes Up, Logic Goes Down|

|Even If You Fall Face First You're Still Moving Forward|
[T-Mobile, Samsung Galaxy SIII] OneIdiotInATree:
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
[T-Mobile, Samsung Galaxy SIII] monkeypaws:
Okay follow this to get to stock and make sure it can at least do that. http://xdaforums.com/showthread.php?t=2136921
[T-Mobile, Samsung Galaxy SIII] Don_Perrignon:
Are you sure you have a T-Mobile phone?
[T-Mobile, Samsung Galaxy SIII] OneIdiotInATree:
Thanks for the set of instructions, but I am unable to either start it (power button), put it in cwm (pwr+up+home) or download mode as mentioned (pwr+down+home). I don't get a vibration; I don't get anything. Is this totally bricked now? Since the device isn't on, I can't do anything with Odin or the SD card.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
What country do you live in, and how did you acquire your phone? Looks like you maybe have the intl version.
[T-Mobile, Samsung Galaxy SIII] kitila:
I would say try to get into download mode with the physical bottons if that dint work try a jig u can get on ebay like 5 bucks they are always handy.if u can get in to dl mode odin a root66.tar then install recovery.if that dobt worj u prib install liquid rom but fir diff device abd hard brixk u f that case hope u have insurance ti replace they will never know u rooted ir have it jtaged
[T-Mobile, Samsung Galaxy SIII] lojak29:
Its bricked, jtag repair only way .

Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .

Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
[T-Mobile, Samsung Galaxy SIII] ziggy46:
it honestly sounds like he has he international version not the US variant. so i think thats the mistake not the phone
[T-Mobile, Samsung Galaxy SIII] majic12:
99% of the bricking is user error...the reason for the increase in "bricked" topics is cause by the amount of users of the T999...its the most heavily used phone by a wide margin now.

Ive far from an expert but have been flashing since the G1 days and have experience with many phones...in my opinion the t999 is darn near unbrickable unless you didnt follow the directions or use a reputable developer when selecting a rom...

To the OP:

What is the actual model of your phone ? you came with an issue and have not really posted much about the specifics of your phone...

sounds like your phone is not partitioned correctly which probably happened by not following the correct directions

there is so much more info needed to diagnose your issue its silly...

Ive been using wicked roms from day one on the t999 and I dont remember seeing anyone hardbrick a phone yet and there are thousands of users using wicked roms...

---------- Post added at 10:58 AM ---------- Previous post was at 10:16 AM ----------

Also...was your phone charged when you last tried to flash something? long ago my phone died while flashing ( lessoned learned) ...

pull the battery for awhile...put it back in and try to charge it...

then try to odin back to stock after its charged...
[T-Mobile, Samsung Galaxy SIII] Pennycake:
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).

I also wonder if this phone is actually an International version instead of the T-Mobile one.

OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
[T-Mobile, Samsung Galaxy SIII] Da Kine:
OP just has to remove the battery cover and battery and bam! There's a label with Sammy's logo along with device model and other info about the phone.

|When Emotion Goes Up, Logic Goes Down|

|Even If You Fall Face First You're Still Moving Forward|
[T-Mobile, Samsung Galaxy SIII] majic12:
This is why I call user error...

OP...post some more info and let us know if you fixed your problem so I can rest easy...Ive lost a few phones over the years and I know how devastating it can be...but im also pretty sure your phone can be saved...

from what limited info I see I think you formatted wrong but an odin back to stock should fix that...

I also think that your battery died while flashing and thats why your phone is not responding to anything...pretty sure a long battery pull would fix that ( it did mine )
[T-Mobile, Samsung Galaxy SIII] cobra85ec:
unbrick

from what i understand.. your phone just need to be jtag and that should get you back up and running... we fix this problem all the time in my store..pm me if u have not fix it yet
[T-Mobile, Samsung Galaxy SIII] AMRivlin:
Hard Bricked over night, now what?

I have a 9 month old S3 (Canadian/Mobilicity Variant)

I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. If I pulled the battery I could reboot.

I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.

It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.

Last night while on the charger, I noticed it was hard locked, so I batt pulled, rebooted and went to sleep.

Now (this morning) it wont boot at all. I thought maybe it was the charger and I just didn't get a proper charge (I have 3) none make any difference.

So. What now?

Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?
[T-Mobile, Samsung Galaxy SIII] GalaxyBoi14:
most likely you did a dirty wipe

you need to probably wipe data, cache, and dalvik cache to make sure nothing goes wrong.... and make sure the rom your using is for your specific galaxy s3 because there is different variants
[T-Mobile, Samsung Galaxy SIII] Dano79:
Wow dont know whats worse the actual topic at hand or some of these answers lmao

Im sure the OP has it figured out now maybe
[T-Mobile, Samsung Galaxy SIII] DesperateScorpion:
Just out of my curiosity OP. Did you make sure your battery has charge left in it? People tend to forget that aspect when you are looking at the recovery page during the process. All the restarts, flashing, recovery etc does drain the battery.
[T-Mobile, Samsung Galaxy SIII] xdaTizen:
really dont know what happend, lets see if other can help
[T-Mobile, Samsung Galaxy SIII] IXChicharitoXI:
Op username made me lol
[T-Mobile, Samsung Galaxy SIII] Zeda15:
Hi I'm not the OP But I'm having very similar problems that he had, In fact everything happened pretty much the same all the way to our phones turning off and and not being able to turn on... but here's where things get different my phone rebooted with liquid smooth and 4.2.2 but I've lost everything I can't connect to internet I can't receive incoming calls I can only text and make outgoing calls oh and I have no play store... Now I figure someone will say something about my Sd card and I have one yes but my computer will not let me access it through my phone any and all help will be GREATLY APPRECIATED Thank you- Zeda
[LG Optimus 3D] mchartier:
I am on xbsalls XBSAVX3D custom rom and when i try and use wifi everything connects properly, but when i try and use it at all it says its not connected at all, ive had this problem with the 28b rom too, im fine with stock rom though. Any help is appreciated :)
[LG Optimus 3D] the ManaWhoney:
I'm on XBSAVX3D as well but my wifi is working fine as I'm answering you right now with it :) I did have an issue earlier that I was watching youtube on data and then connected to wifi later...said no network connection. No idea why but a simple reboot fixed for me. Hope it helped. Also I'm running a different kernel with unlocked bootloaders instead of the stock kernel that came with the rom. No idea if that makes any difference or not.
[LG Optimus 3D] mchartier:
Lol i dont have data :eek: so wifi is my only option haha and rebooting doesnt help and im using unlocked bootloaders and ive tried iodaks kernel and Pesach85s kernel each with the same result
[LG Optimus 3D] the ManaWhoney:
Sorry my bad I totally got backwards on that. If you are in the US like me, did you alter the build.prop target country from EU to US and flash the V30B baseband followed by a factory reset? If so have you tried to flash V28B baseband instead? If those options don't work my friend I'm clueless.
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Is it?
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
TricksterMod always shows that even after gaming for 30 mins or so CPU temperature does not go beyond 60'c

Stock kernel or rooted??

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Stock rom rooted with Motleys kernel OC AT 1.5 and 51mhz
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
I personally have not seen the temperature hitting 70 till date..i have been using it since last december...

Any specific game in particular???

Have you tried the lean kernel??

Any ZRam tweaks??

After playing does the temperature stay around 70 or it drops??

Cheers

Grouper

Vanir
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
I never used tweaks or the lean kernel and games like mc4 and dead trigger make it get to 70 degrees or even 72 or 73 but when in watch YouTube it doesnt. Do you know any good Oc settings?
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
I personally prefer the lean kernel and OC at 1500 and change the Read Ahead buffer size to 1667 .... Min at 102000 interactive governor even running benchmarks using Antutu and quadrant temp does not go beyond early 60

I do play a few racing games but not the ones you mentioned but have not seen it go beyond 60'c
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Okay I will try that now and I will be back with the results
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Okay I just did it I got a 5529 score on quadrant but the CPU hit 62
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
5529 is decent with this kernel.

How about the battery temperature???

What is the total up time for your grouper?

While holding the nexus do you feel the back rubber getting hot??

I did notice it at times but after flashing to lean kernel it was no longer there..

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Battery is 34c I do feel it get a little warm and grouper is 00:02:05
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
Battery temp seems to be in order..i found this on xda

http://xdaforums.com/showthread.php?t=2086270
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
I'm scared to oc to 1.6 man and I'm loving these settings and kernel you gave me I have 5 apps open and the CPU temp is a 54-57
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
Not a big fan of OC myself. That range is definitely what i see on my grouper too.

Just wondering any changes under developer options with regards to GPU force rendering??
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Yes I have that on
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
I normally switch that on for playing asphalt or EA racing and while flashing ROMs and checking benchmarks (more of a placebo than anything else ;))

While browsing or tweeting i switch it off

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Lmao I keep it on
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
I just played dead trigger for 5 min and the CPU hit 69
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
Any info on the game forum around safe temperature limits??
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Where is the game forums?
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
140-145 F is normal for tegra3
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
I'm talking about Celsius
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
If you convert what range do you get????

Whatever range you get is normal for grouper
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
I got 00:3:29
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
M8 i am not sure which converter you used ...
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Wait what do you mean about convert
[Nexus 7 Q&A, Help & Troubleshooting] Ciphersbak:
Temperature conversion;)
[Nexus 7 Q&A, Help & Troubleshooting] Chocobubba:
I'd say that's pretty warm, mine rarely breaks 55... I bet with Netflix and max brightness I could match your temperature though.
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
I solved the problem I just went back to the stock kernel
[Nexus 7 Q&A, Help & Troubleshooting] kel29738:
Are you overclocked?
[Galaxy Note 10.1 Themes and Apps] NadMaj:
Magicka is now on android!.. :good:

well i don't really play this game on PC but when i gave it a try last night it's friggin awsome!.. instantly became my favorite.. humorous gameplay especially co-op.. can also play cross-platform.. :)

that's why i created this thread so we note 10.1 users can maybe play together?.. :laugh: :fingers-crossed: post your username here and let's play!..

here's my username: NadMaj

:D
[Xperia Arc Q&A, Help & Troubleshooting] danisariandi:
Hi excuse me, I have a problem with OTA updater. I uploaded via dev host and I generated my ROM via OTA updater. AFTER I UPDATED, I TRIED TO DOWNLOAD AND UNFORTUNATELY "There was an error with download"

Any solution ?

Thanks