yashsingh1/xdaforums huggingface dataset:
[Sony Xperia Miro, Tipo (Dual), J, E] Suxter:
Radio not working :cowboy:
[Sony Xperia Miro, Tipo (Dual), J, E] Ketcchup:
- Led only shows all colors, can't specify a color.

- Baseband Unknown and Carrier names are Unknown, but works fine.

- Video recording quality is just ****, with LGCamera it records like stock rom.

I think there are no more bugs.

There isn't radio app in CM10
[Sony Xperia Miro, Tipo (Dual), J, E] lozohcum:
Xperia J, CM10:

The ammont of total RAM is wrongly displayed in system settings/info
[Sony Xperia Miro, Tipo (Dual), J, E] n1kolaa:
? What you think by that ?
[Sony Xperia Miro, Tipo (Dual), J, E] c4cyro:
The illumination light of Miro does not work.

Also led notifications from settings, don't work.

Sent from my Xperia Miro
[Sony Xperia Miro, Tipo (Dual), J, E] n1kolaa:
for iliuminaton light it mabe wont be fixed coz it dont work on my phone eaven on stock rom :(

you can falow It here : https://github.com/LegacyCyan
[Sony Xperia Miro, Tipo (Dual), J, E] c4cyro:
Hey no it does work in stock rom.

Also, in cm10, it glows when you try to get into recovery, but not when the rom has booted.

Sent from my Xperia Miro
[Samsung Galaxy Nexus] kirt231:
more specifically the volume keys. some are saying the parts are a little different but i dont see why. just wanted a clarification thanks
[Samsung Galaxy Nexus] bpyazel:
View attachment 2376015

View attachment 2376016

Yeah, they are pretty different like a lot lf the parts are. First is verizon, second is gsm.
[Samsung Galaxy Nexus] darthleland66:
Re:

Actually, the Sprint and Verizon models are both CDMA...the Sprint one doesn't have a SIM card, and so the frame and motherboard are different. The volume keys are placed slightly differently as well. I have parts for both phones which I can post pictures of later.
[LG Optimus 2x] xda_fanboy:
Hello All,

Hoping someone will be able to assist me, though I'm starting to lose hope.

I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.

Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.

So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.

So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.

I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.

As a last resort I repartitioned. This also worked ok, but still no recovery mode.

tl;dr

Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.

Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
[LG Optimus 2x] xda_fanboy:
Bump
[LG Optimus 2x] NoDze:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
[LG Optimus 2x] xda_fanboy:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
[LG Optimus 2x] NoDze:
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
[LG Optimus 2x] citukas:
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,

EDIT: somehow from the countless attempt it fired up.
[LG Optimus 2x] SuperSkill:
Make sure to have the right bootloader before nvflashing unbrick roms....
[LG Optimus 2x] Icaros7:
Try to flash a new recovery image in apx mode.

And edit the /dev/block/mmcblk0p3 partition your self.

seek=6144 count=75 bs=1 / boot-recovery
[LG Optimus 2x] xda_fanboy:
Thanks for the added input and encouragement folks.

Just reporting an update:

Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.

Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm

Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!
[JASJAR, XDA Exec, MDA Pro General] youmeus:
shaytaan & V man

how the hell do you in stall the handheld version? I keep getting and error about not able to install on pocketpc...! please help I have a xda exec

Thanks
[Galaxy Note II Q&A, Help & Troubleshooting] dewey2999:
Hello,

Ive installed beanstalk RC1.1 yesterday and also installed the kitkat 1.03. When I change the DPI of the phone all is well until I am in an app and press the home button (center button). When pressed, I am brought to the home screen but then the keyboard pops up. I must then press the home button again to get the keyboard to drop away.

I have not re-mapped any of the keys. Its really annoying.. Does anyone know how I can change this so that when I press the home button it will bring me to my home screen and NOT bring up the keyboard?

Thanks in advance.
[Android Q&A, Help & Troubleshooting] kairnage:
Does anyone know how the Sero OTA updates use the normal google test keys or do they use a custom key?
[T-Mobile, Samsung Galaxy SIII] cleonjones:
I am running [AOSP 4.3.1 Stable [DanKang] Slim + optimizations] and my touch tone isn't working on calls. For example, when I call a support number it asks to press 1 for department A, 2 for department B and so on. When I press a number there is no response at all. I have tried a few different support numbers and it never works on my phone. I have a stock GS3 that I tested with the same support numbers and touch tones are working.

Dial pad touch tones is enabled, what could be causing this?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Open Phone Apps go to settings. Once there, make sure Phone Touch tone box is checked.
[T-Mobile, Samsung Galaxy SIII] cleonjones:
Here are my phone settings, looks like everything is correct to me. Not sure at this point
[T-Mobile, Samsung Galaxy SIII] Perseus:
What's your baseband ? Also follow these instructions.
[T-Mobile, Samsung Galaxy SIII] cleonjones:
I'm on T999UVUEMJ4 pretty sure that is the latest one from here:

http://xdaforums.com/showthread.php?t=1880987
[T-Mobile, Samsung Galaxy SIII] Perseus:
I have the same modem. I just tried T-Mo Toll Free Number with my phone successfully and was able to navigate just fine.

Did you follow the instructions link I posted ?
[T-Mobile, Samsung Galaxy SIII] cleonjones:
Yes, I did try a few other 800 numbers and it seems to be working fine now but 1 particular number I use frequently isn't. Really odd.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Must be really dilapidated old exchange. Switch to pulse instead of DTMF. Can't remember the process right now. It will come to me.
[T-Mobile, Samsung Galaxy SIII] jim45:
Can you even enable pulse dialing on a cell phone? IIRC pulse dialing works by simulating the hanging- and picking-up of the phone in quick succession, and that can only be done with landlines.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes its do-able. Just need to go through Dialer settings.
[T-Mobile, Samsung Galaxy SIII] retnec:
same issue

When certain numbers are dialed I can not select the extension. Other numbers work without incident. I am currently back to official stock, but have tried the 4.3, full stock, slim, and deodexed;

same issue. I have also tried various apps- no avail.

can any one explain how to set the pulse dialing in the dialer to see if that works?

or any other suggestions? another phone is not an option at this moment.

I have to dial this *problem number on a daily basis. It worked fine with my old mytouch ,unfortunately the phone bit the dust.
[T-Mobile, Samsung Galaxy SIII] Perseus:
DTMF is enabled by Keypad tones on my AOSP 4.3 Rom. I believe for Touchwiz stock roms its under

dialer>menu>Call Settings>Ringtones and keypad tones>Keytones

On some S3, under Call Settings > Other Call Settings > DTMF Tones

EDIT - Just realized. If you had Bluetooth on and connected, then I know for a fact these touch tones don't come over bluetooth. Best if you try without bluetooth on.
[T-Mobile, Samsung Galaxy SIII] retnec:
I have the SGH-T999. I have contacted t-mobile and they say there is no option on the SG3 to set or adjust the DTMF.

Do you have this same phone?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yup. PM me the number that's causing the grief. DO NOT POST here.
[T-Mobile, Samsung Galaxy SIII] retnec:
DTMF ISSUE WITH IVR is a kernel problem

Credit to Perseus who identified the DTMF issue with certain IVR systems to be a kernel problem.

thanks again Perseus
[Motorola Atrix 2] CreativeSin:
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
[Motorola Atrix 2] Aceofzeroz:
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.

So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).

After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.

After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://xdaforums.com/showthread.php?t=2245825 Good luck!

Sent from the Ace's MB865 using xda-developers app
[Motorola Atrix 2] CreativeSin:
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to . Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
[Motorola Atrix 2] Aceofzeroz:
You're welcome :thumbup::D I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-

So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it! :p:cool:

Sent from the Ace's MB865 using xda-developers app
[Motorola Atrix 2] CreativeSin:
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
[Motorola Atrix 2] Aceofzeroz:
Well now that you're back and rooted, if you're planning on doing any more flashing any time soon then I recommend you install boot menu manager. If you've previously installed safestrap or bootstrap, clear their data and uninstall them before installing bmm.

With that done, you've just made your phone a little safer from bricking because bmm allows multi rom booting, which are somewhat independent of the primary system. Refer to this thread for more info on how to make systems, etc.: http://xdaforums.com/showthread.php?t=2115715

The first thing you'd want to do is make sure your apps/data is always backed up at all times with apps like titanium backup. Create 2 or more systems so that you can try the bmm compatible custom ROMs which are in the dev section if you want to try any of them. But please, read all instructions, warnings, requirements, etc. carefully before attempting any flashing in general.

The thread I posted in my earlier post above will have links to the specific custom ROMs. If you're doing any other kind of flashing, make sure to again, read instructions carefully and take your time with learning all of this. ;)
[Motorola Atrix 2] kunal2711:
Hi, I soft bricked my phone recently.

I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.

It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.

I am stuck with a bricked phone and all my work is stuck up.

I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.

Any help would be very much appreciated. Thanks a lot in advance.
[Motorola Atrix 2] mithun23:
Use boot menu manager instead of bootstrap recovery
[Nexus 5 General] nikeman513:
This is for those that have to RMA their device like me and got an expected 3-4 week delivery schedule. Post the date here that you RMA'd, then post again when shipped, to give an actual expected timeframe of when to expect a shipment. Please quote your original when posting "shipped" to make it easier to track. This will undoubtedly fluctuate around now and the next couple weeks. So, let's keep this thread going, so people 3 weeks from now still have a realistic idea of when to receive a shipping confirmation.

We all hate to RMA a device we just received, so this isn't a whining thread. This is just a way to form some sort of objective information.
[Nexus 5 General] nikeman513:
I start first. I RMA'd today November the 6th at 11 AM eastern time. Expected delivery shows 3-4 weeks.
[Nexus 5 General] jphilippon:
RMA 11/5 11:30pm PST for pixels.

Estimated delivery: 2-3 weeks

California

sent from my Nexus 5
[Nexus 5 General] chakra:
May I ask why the ram? Loose volume button, like every one?
[Nexus 5 General] skylineGTR_34:
I RMA'd today November 6th and it say it will be shipped in 3-4 week. This so bad.
[Nexus 5 General] fotaz:
White 32GB Nexus 5

11/5/2013 ~5:00PM EST: Called Google Play due to 4 deal pixels

11/5/2013 ~7:30PM EST: RMA order placed (2-3 week estimate)

11/6/2013 ~6:00PM EST: Order Shipped (Goddamn Google you amazing)
[Nexus 5 General] nikeman513:
No questions. Just post information if you RMA'd. Thank you.
[Nexus 5 General] jxr94:
Black 32GB Nexus 5

RMA: 4:45pm EST on 11/06/2013

Order Shipped: 12:51pm EST on 11/11/2013
[Nexus 5 General] osugsxr:
Im probably returning mine, battery isn't going to work for me. Probably going with g2
[Nexus 5 General] chakra:
Lol. NSA thread.

It's for your own good!
[Nexus 5 General] wngmv:
Exactly the same. Just got my shipping notification a few minutes ago.

32G white.
[Nexus 5 General] chakra:
I have both, and the G2 battery is a monster. But my N5 is doing 1000 times better today than yesterday.
[Nexus 5 General] jbdan:
Delete sorry
[Nexus 5 General] mrro82:
How about posting why you're sending the phone back too? Might help in the long run to ease some people's minds.

Sent from the jaws of my Hammerhead!
[Nexus 5 General] jbdan:
Mine came 11/5 with a dead vibrator doa. Called last night and they're sending me a new one with info/label /box on how to send this one back. I had to give them the imei # and that's it.
[Nexus 5 General] chillaxnphilx:
Device: Nexus 5 32GB White

Issue: 2 black specks which could either be dust underneath the screen or dead pixels

CALLED: Nov 5 @ 1:26 AM CST

RE-PURCHASE: Nov 5 @ 5:00 PM CST

SHIPPED: Nov 6 @ 4:40 PM CST
[Nexus 5 General] nikeman513:
That can be found in defects section. This is for RMA information on date filed and date shipped. Everyone has their reasons. This is information only to provide objective data. This is not a thread to judge for their reasons. I hope everyone can respect that, and keep this thread to its purpose.
[Nexus 5 General] mrro82:
Then why not combine them as it's one in the same.

Sent from the jaws of my Hammerhead!
[Nexus 5 General] nikeman513:
Because as I stated this is to form objective data. Just facts on estimation of RMA process. There are those that ridicule people for their reasons to RMA. This will not become a thread of judgment. You can go to defects and say what's wrong and you're doing an RMA.
[Nexus 5 General] mrro82:
The defects thread is full of people saying they're returning it. Same as this so.....

Sent from the jaws of my Hammerhead!
[Nexus 5 General] onthecouchagain:
For those that RMA-ed because of the loose power button, was the new one better/tighter?
[Nexus 5 General] 7TimesCursed:
Anyone else RMA about the loose power button? I know its nitpicky but I wasn't taking any chances. Is it me or has every nexus phone had problems with the power button?
[Nexus 5 General] pinksoviet:
Submitted my request for RMA on the morning of November 7th.

Received shipping confirmation in the evening of November 11th.

It's coming from the same depot as my first one, so I believe it'll take 3 days, so I should receive it no later than this Friday (November 15)
[Nexus 5 General] mayo1024:
Submitted my RMA on 11/6 for a bad mic.

Received my shipping notice just an hour ago, 11/11

3-5 days it should be here. Hope it's by Friday.

It's a black 32gb.

Edit: Forgot to mention I had a date of 12/3 for it to leave the warehouse...Woot!!!
[Nexus 5 General] syder:
I put an RMA in on Nov 9 and shipping status was ship in 3 - 4 weekly. But I've just received an email from Google stating that my replacement has shipped Nov 11. :D
[Nexus 5 General] sovereignty68:
Same here
[Nexus 5 General] jector42:
RMA'ed on Nov 7th received shipping confirmation 2 hours ago
[Nexus 5 General] chw2006:
RMA'd on the 6th, received notification an hour ago and it's already been scanned by UPS in Kentucky.
[Nexus 5 General] lollerskating:
Question! If you end up keeping both the replacement device and the defective one, do they just charge you for the replacement? My RMA is being shipped to me now, but my brother would like to buy my current one from me (it has a weird vibration motor, but he doesn't mind it).
[Nexus 5 General] jbdan:
Yes
[Nexus 5 General] tyrellcorpnexus:
My RMA I think is going to arrive tomorrow.

If it's worse than the current one (in terms of dust count, 4 that I can see, top left, top right, bottom right, and fainter one in the middle-ish), I'll keep the current. Everything else about my current one is good, the vibrate isnt the best but I turned haptic feedback off anyways at it was 'too much' for me

I have flashed Franco kernel, and will restore to backup stock kernel via Flashify, but how do I re-lock the bootloader if I end up sending my current one off?
[Nexus 5 General] jinx626:
I posted earlier in this thread and now an update:

RMA request on 11/9/13

Initial Email said 3-4 weeks with leaving warehouse by 12/3/13

Today receive shipping notice that it is in transit 11/11/13

This is for a 16GB white Nexus 5 in the US.

I am impressed Google compared to the debacle of my Nexus 7 tablet which took over a month before i received the replacement. Restores my faith just a little.
[Nexus 5 General] Yadao:
I requested an RMA on Nov. 10th

Estimate said 3-4 weeks (Dec, 3rd)

It actually shipped today (11th)

Will arrive tomorrow (12th)

I'm impressed.
[Nexus 5 General] tyrellcorpnexus:
I'm impressed as well, they did a good job with this.
[Nexus 5 General] ihakim:
To lock your bootloader:

fastboot oem lock

or if you're on a mac

./fastboot oem lock
[Nexus 5 General] tyrellcorpnexus:
Thanks and how about flashing back stock kernel? Flashify didn't seem to back it up
[Nexus 5 General] KennyDumah:
just flash the factory image :D
[Nexus 5 General] ihakim:
There's a great guide on the Nexus 4 forum that will guide you through flashing factory images. You can either just flash just the kernel or flash all components - recovery, bootloader, radio, etc. Make sure you use the files corresponding to the Nexus 5.

http://xdaforums.com/showthread.php?t=2010312
[Nexus 5 General] RedBlueGreen:
Can everyone please include what country they are from? Would be much appreciated
[Nexus 5 General] davidquesada:
Ordered on 8, got the shipping notice yesterday being delivered tomorrow

US
[Nexus 5 General] RedBlueGreen:
Just got an email saying mine has been shipped.

Ordered replacement on the 7th

Emailed on the 12th.

I'm from London.