yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
Partial solution: goto Settings, search "answering", click on answering and ending calls and select answer with home key and/or the command "answer". Done.

Not good enough? Other potential fixes:

Goto stock recovery and delete cache and dalvik and reboot phone.

-or-

Factory reset.

-or-

Open Dialer, dial *#2663# (You most likely don't need the S-Pen to dial but using S-pen may help for those that mistakenly flashed the wrong custom recovery and need this to restore touch.), then update the touch FW by pressing "TSP FW update (General)". It's harmless to restore if not needed but maybe it helps. Maybe just a refresh after update is needed?

None of these will void the warranty but you may consider backing up with KIES or Helium before factory reset. No root alternatives. There's also Drive, Samsung and Google backup and restore but not so data app friendly on restore.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] kingsosa:
not part neither will recovery mode will download mode I installed twr then I installed the rom hd car and after I get only the blue screen update failed tells me to do it with smart switch even with smart switch does not recognize me the s / n
[Android Themes] The Hard Gamer:
Hi guys , this is my first post and here i present batman bootanimation for devices of resolution:) 720*1280 this has been posted once before but this version is modified with sound!!!

Just take backup of your stock animation and audio from /system/media and replace with these both..

Comment if you have any problems or if you feel it is good...

Hope you all like it.....

Links..

Sound-

Uploadex.com/vysgtykdgr0b

Animation-

uploadex.com/j46zlw5xxrws
[Android Themes] The Hard Gamer:
I tried it.......it is best bootanimation ever batman fans must try it
[Android Themes] LuxRed:
I tried on my mobile. Its working perfect. Thanks.

:laugh:
[G3 Android Development] chuyennho184:
I've bumped TWRP F400 Variants compatible with Aroma Installer.

Download TWRP:

https://drive.google.com/file/d/0B4FoLWZ0e4kmbTZYcWxBYXM2WTA/view

- Instruction to use: Go to Google Play to install Flashify. Use Flashify to install TWRP.

Second method:

TO F400 VARIANTS USER:

If flash twrp with flashify have a issue on boot. Please, change flash twrp with adb commands like that:

Preparetion:

- The device has root access.

- Enabled usb debugging.

-

Download TWRP original:

https://twrp.me/Devices. Type f400k in search frame & download it.

- Change name downloaded file to recovery.img

**

Tool to bump twrp:

Choose match for your windows.

- Windows 32bit: https://drive.google.com/file/d/0B4FoLWZ0e4kmVlNfNVNYcUg1MWc/view

- Windows 64bit: https://drive.google.com/file/d/0B4FoLWZ0e4kmVlNfNVNYcUg1MWc/view

**

Instrution to bump twrp:

- Extract tool bump to desktop.

- Drag & drop recovery.img to bump.exe (bump.exe is a tool bump twrp & in it folder same name)

- Look below picture to see how to do it

- After bumped file. change name recovery.img again & copy to internal storage.

And now, use adb command to install twrp:

1. Connect your device with pc. Make sure installed LG driver before.

2. adb shell --> enter

3. su --> enter

4. dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery --> enter

5. dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery --> enter

6. exit --> enter

7. exit --> enter

8. adb reboot recovery --> enter (your device will boot into twrp)
[G3 Android Development] smartphone_lg:
Like nhé...

Gửi từ LGLS990 của tôi bằng cách sử dụng Tapatalk
[G3 Android Development] daveaus:
Has anyone with f400k flashed this?

Is it possible that a new version of TWRP would enable us to access recovery via key presses or is that something else?

Thanks!
[G3 Android Development] chuyennho184:
You can easily access twrp with hard buttons or quick reboot app.
[G3 Android Development] daveaus:
No button combination works on the f400k. We are forced to use a app which means if the device can't boot we can't get into recovery.
[G3 Android Development] chuyennho184:
I've tested on my device before make a thread. You should to try several times to access twrp with hard buttons. I alway to boot into twrp via hard buttons to test rom.
[G3 Android Development] daveaus:
Do you have f400k? It is different to the F400S

Which buttons are you pressing. Thanks!
[G3 Android Development] chuyennho184:
Twrp v3 is use for f400 variants. Access twrp by hard buttons is the same for f400 variants.

Hold volumn "-" + power. When you see LG logo, release 2 these buttons, press volumn "-" + volumn "+". You device will going to factory reset. Choose yes 2 times to enter twrp.
[G3 Android Development] noypitoits:
[MENTION=2756494]chuyennho184[/MENTION] thank you for making this worked on our f400. the official version gives me error. (F400L)

all f400 variants can access recovery via hard buttons as the op stated. ( just to clarify things)

volume down +power when you see the LG logo immidiately released both then as fast as you can press volume down + up make sure you are pressing borh button on the edge ( away from power button) then follow the op's instructions.

[MENTION=2756494]chuyennho184[/MENTION]

I have successfully flashed 3 roms already including fulmics 3.5 & restored couple of back ups to test this. & its working. But with these 3 roms. I cant get my phone to reboot. If I press reboot on the power menu the phone turns off & I have to pull the battery out to turn it on again. Can you confirm this? Is this a twrp bug? Never encountered this on twrp 2.8.6
[G3 Android Development] daveaus:
This button combo doesn't work on the f400k.

See here: http://xdaforums.com/lg-g3/help/boot-to-recovery-t2964143/post65227472#post65227472
[G3 Android Development] chuyennho184:
On twrp 2.8.7.0, I have still same issue.
[G3 Android Development] noypitoits:
If this button combo works for F400s & F400L but not on F400k:confused: sorry bro I have nothing to say thats all I know.
[G3 Android Development] teokjisoo:
[MENTION=2756494]chuyennho184[/MENTION]

I'm using f400k MM stock rom (30d).

I have rooted temporary by using kingroot and flash your recovery via flashify.

But when I try to reboot to recovery, it shows

========================

Boot verification Failed

-cause MISMATCH_SIG_LEN

========================

Is there anything that I am missing?

Thanks for your reply.
[G3 Android Development] vineet381:
I am getting the same error on boot,boot verification failed.

---------- Post added at 01:14 PM ---------- Previous post was at 01:14 PM ----------

Currently on twrp 2.8.7
[G3 Android Development] chuyennho184:
I think your device lose root access when reboot with kingroot.
[G3 Android Development] chuyennho184:
It's weird while F400S & F400L can easily access TWRP successfully. Only F400K have issue.
[G3 Android Development] chuyennho184:
TO F400K USER:

If flash twrp with flashify have a issue on boot. Please, change flash twrp with adb commands like that:

Preparetion:

- The device has root access.

- Enabled usb debugging.

-

Download TWRP original:

https://twrp.me/Devices. Type f400k in search frame & download it.

- Change name downloaded file to recovery.img

**

Tool to bump twrp:

Choose match for your windows.

- Windows 32bit: https://drive.google.com/file/d/0B4FoLWZ0e4kmVlNfNVNYcUg1MWc/view

- Windows 64bit: https://drive.google.com/file/d/0B4FoLWZ0e4kmVlNfNVNYcUg1MWc/view

**

Instrution to bump twrp:

- Extract tool bump to desktop.

- Drag & drop recovery.img to bump.exe (bump.exe is a tool bump twrp & in it folder same name)

- Look below picture to see how to do it

- After bumped file. change name recovery.img again & copy to internal storage.

And now, use adb command to install twrp:

1. Connect your device with pc. Make sure installed LG driver before.

2. adb shell --> enter

3. su --> enter

4. dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery --> enter

5. dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery --> enter

6. exit --> enter

7. exit --> enter

8. adb reboot recovery --> enter (your device will boot into twrp)
[G3 Android Development] chuyennho184:
[MENTION=4277630]vineet381[/MENTION] & [MENTION=7277867]teokjisoo[/MENTION]: Use adb command to install twrp v3. Look above my post.
[G3 Android Development] helijia21:
how to use

how to use this on a unrooter LG F400S (with stock romV30C)
[G3 Android Development] chuyennho184:
Read my instruction to install twrp.
[G3 Android Development] vineet381:
Thank you buddy, let me try this,will report back tje result. Thanks for taking time to post this.
[G3 Android Development] chuyennho184:
I want to know how's result about install twrp by adb commands. Please tell me.
[G3 Android Development] teokjisoo:
Thanks for your advice.

Actually I have seen your post at lgviet (http://lgviet.com/forum/threads/twrp-recovery-v3-0-0-all-variants.53475/) and when I tried it, it also didn't work for me.

Maybe king root (or temporary root) is the cause of the trouble because your recovery works perfectly on lollipop stock rom which is permanently rooted.

Thanks again, [MENTION=2756494]chuyennho184[/MENTION].
[G3 Android Development] vineet381:
Que- After I drag and drop recovery.img, do I need to rename it again and then copy this file to my internal storage on phone?
[G3 Android Development] chuyennho184:
After bumped twrp, your recovery file have changed name. So, change name to recovery.img to flash with adb commands.
[G3 Android Development] nice.guy:
not sure about other variant, but i can confirm that using hard button to get into recovery mode does not work on f400l. which is why i am extremely careful when i switch rom so I dont get stuck in bootloop. it'd be great if this version of twrp fix that.
[G3 Android Development] chuyennho184:
Not to hard to access twrp by hard buttons. You should try several times. Before I have same issue like you but now don't have a problem like that.
[G3 Android Development] captsingh787:
Hi. Can you please help me to root F400K stock 6.0
[G3 Android Development] chuyennho184:
With F400 model, can't directly root on stock rom v6.
[G3 Android Development] captsingh787:
Help
[X2 Q&A, Help & Troubleshooting] skmrom:
hi i'am using cm11 on my nokia x2ds and i have flashed it with cwm recovery :) and after sometime i want to move apps to sdcard so i tried xposed installer and xinternalsd but it didn't work for me so i flashed disable_internal_cm-11-20151121-UNOFFICIAL-ara.zip and it worked :D:D

then i checked my phone status and my phone name was nokia ara but i know why but after some time my phone has changed to [Sony ara] also apps and games think my phone is [sony ara] please help me

links [i flashed this]

cmw6.0.5.1.zip

NokiaX2_modem_flashable.zip

pa_gapps-modular-micro-4.4.4-20150308-signed.zip

cm-11-20150915-UNOFFICIAL-ara.zip

i want to make my phone nokia ara again or nokia x2 ara please HELP I want to know how to fix this or if that was a bug

also apps crash randomly :eek: i need help for that too

thanks
[X2 Q&A, Help & Troubleshooting] yasat nokiax2:
Hello [MENTION=7272281]skmrom[/MENTION], just open build.prop in system folder and search for word Sony. Then change it to Nokia. Probably it will be at ro.product.manufacturer=Nokia. But you check other lines also.
[X2 Q&A, Help & Troubleshooting] SimonVN:
It's caused by Nokia X Manager.

Nokia X Manager change some information in build.prop to Sony to fix Facebook app (fix notifications).
[LG G5 Themes, Apps, and Mods] abella0:
According to a Geekbench benchmark, the LG G5 will be powered by a Snapdragon 820 processor and coupled with 4GB of RAM.
[LG G5 Themes, Apps, and Mods] shaneel1491:
Single core: 2248

Multi core: 5061

https://browser.primatelabs.com/geekbench3/5216058
[LG G5 Themes, Apps, and Mods] KennyG123:
Placeholders are not allowed

Benchmarks cannot be discussed for a device not yet released

Please make a new thread on release day

Thread closed
[Micromax Canvas Nitro A310/A311] 9888:
Hey, developers plz. make a 6.0.1 cm for our buddy MMX A310.

:fingers-crossed:
[Micromax Canvas Nitro A310/A311] juned.khatri31:
Coming soon bro
[Micromax Canvas Nitro A310/A311] 9888:
when it is comeing also send the date:)
[Micromax Canvas Nitro A310/A311] Sher1234:
Developers for cm13 mt6592 are currently building it (as per my information & its highly unstable so wait for developers to post there stable build)

Its difficult to to tell you the exact time or date when the ROM will be developed or say becomes stable for use
[Micromax Canvas Nitro A310/A311] 9888:
ok but plz be fast to built
[Micromax Canvas Nitro A310/A311] karan6606:
me too waiting for android 6.
[Micromax Canvas Nitro A310/A311] 9888:
Ok
[Micromax Canvas Nitro A310/A311] Nack cool:
Me too waiting......
[Micromax Canvas Nitro A310/A311] girijad40:
Me too waiting guys.....
[Micromax Canvas Nitro A310/A311] rahult2838:
I think its taking some more time to port m for a310
[Micromax Canvas Nitro A310/A311] 9888:
Any update
[Micromax Canvas Nitro A310/A311] rahult2838:
Under building process
[LG G Flex 2] wtang:
Is anybody here using Google Voice on their Flex 2? I have this issue where outgoing calls made through Google Voice are recorded in the stock phone app's call log as some random number, not the number I just dialed. I did a little a little research, and Google Voice apparently routes all outgoing voice calls through a "gateway" or "access" number. That must be the random number that's showing in my call log. But this was never a problem on all the Android phones I've owned (and I've had many) and all the different ROMs I've flashed over the years. For example, Google Voice shows the actual numbers I dialed on my previous LG G2, Samsung Galaxy S4, LG G Pro, Nexus 4, etc.

If anyone can confirm this is also happening on their LG Flex 2, then I'll know it's not just me.
[LG G Flex 2] epofhouston:
Mine showed the corrected # on both side. I'm on H950 5.1.1. Maybe you can update your google voice app.
[LG G Flex 2] jgolf:
That's the way it works on iPhones. I've never seen the Google Voice "hidden routing" number show up in the native call log on any android phone I've used. (That hidden routing number in Google Voice parlance is sometimes referenced as the "grandcentral" number which was the company that Google Voice bought when it started). If you notice, your "grandcentral" number actually shows up in the background (you can of see it in small numbers in your Google Voice app for a half second) when dialing a call from your Google Voice App.

Is it happening for calls you're making from even your Contacts, or just unknown numbers that you dial manually? (Not that I'd have anything to add or offer, but I"m just curious). Are you running stock, or are you modded in any way? (Again, I'm just curious).

I actually prefer the way Apple does it so you can see the number in your call log. It's handy to have. It's a static number that doesn't change for your Google contact. You can save it and dial it directly from any phone -- even without data or making a landline call -- and the call shows up on the other end that you're calling from your Google Voice number.
[LG G Flex 2] wtang:
I'm already on the newest version of the Google Voice app. I'm on a LS996 running 5.1.1, but I'm firmware version ZV6. I believe the newest 5.1.1 stock firmware is ZV9. I wonder if upgrading to ZV9 will fix the problem What 5.1.1 firmware version are you on?
[LG G Flex 2] epofhouston:
I'm on 11x.
[LG G Flex 2] wtang:
I see the Google routing phone number in my call log for all the outgoing calls I make. It doesn't matter if I dial someone from my Contacts or I manually dial the number. Also, I'm not sure what you mean by "dialing a call from your Google Voice App". I'm dialing by tapping on names in my Contacts app, or by tapping out numbers in the stock Phone app. I only open the Google Voice app to look at text messages or listen to recorded voicemail messages.

I'm using a Sprint LS996 and running the stock 5.1.1 firmware version ZV6. No mods. If Google Voice is working on your Flex 2 and showing the real outgoing numbers in your call log, may I ask if you're running a Sprint LS996 or an AT&T H950? Maybe it's just an issue in the stock LS996 ROM. Like I said, I never had this issue in any of the other Android phones I've owned.

I'm not sure why you say it's preferable that Apple shows the Google routing number instead of the actual number dialed. Why would you want to see phone numbers you don't recognize in your call history log? Why would you want or need to save that routing number and dial it directly? If you already have that person's real phone number, what is the advantage of having another strange number for that same person?
[LG G Flex 2] jgolf:
Oh yeah, I messed up on the part of "dialing from my GV App." Sorry about that. I was confused about where I see that grandcentral number when I make a phone call. I thought I only saw it if I initiated a call from the GV app, and even when I do that it just goes to the native dialer and I see it every time.

This is what I meant: On my phone, when I make a call, whether from contacts are just using the regular dialer, the top line shows my contact and/or the number I'm calling; the second line reads "call forwarding is enabled" the third line in blue reads "CALLING VIA GOOGLE VOICE" (that line is capped on my phone) and then the grandcentral number.

I'm using the AT&T H950. Did you by chance disable call forwarding? I remember when I had sprint it didn't play nice with Google Voice. Integrating voice mail (I can't remember exactly what the problem) but it was something like call forwarding didn't work very well with Sprint (and its MVNO's) and Google Voice.

As to your last question why I prefer seeing the grandcentral number in the call log is for personal and nostalgic reasons, and I probably shouldn't have even mentioned it because the whole thing is pretty much moot and pointless now, but I might as well briefly explain. In the early days of Google Voice, which wasn't that long ago, smartphones and cheap data weren't ubiquitous and a lot of us were using dumb phones. It wasn't easy using dumb phones with Google Voice, especially texting, because that unknown number or the grandcentral number was confusing as heck to both you and the person you were texting. If you could find out what number Google Voice was routing to your contact (without using the GV app like on a dumb phone) then it made texting easier.

Now someone is probably going to jump in, or they are thinking, it was easy to text with Google Voice on a dumb phone, because there were easy workarounds like just starting the text from your computer. True, but if you wanted to initiate the text, and you didn't have access to a computer or data, it was convenient to have that grandcentral number saved in your contacts. It was always kind of hard finding that grandcentral number. Even on Android phones you have to take a screenshot, so I kind of liked having that number in the call log and being able to see it. In a way, that's really the number your calling anyway, at least that's the way I look at it.

Anyway, it doesn't really matter now since we use smartphones and have near universal cell and cheap data plans.

---------- Post added at 04:17 PM ---------- Previous post was at 03:51 PM ----------

I should just explain why I asked that question too. I was just curious to know if there was any differentiation between unknown manually dialed numbers and saved contact numbers. I wouldn't have been able to offer any insight if in fact there was a difference between the two. I was simply curious. In my experience the Google Voice App, and routing calls through Google Voice on a mobile device, always works better for numbers you've called before with that device. I think the info gets cached in the phone's Google Voice app once used.
[LG G Flex 2] Wallstreetkid212:
if your going to use google voice you should use hangouts it's a much better experience You can make and receive calls, send and receive text messages,MMS and listen to your voicemails even if you don't have a active phone service all just using WIFI download the hangout dialer from the playstore If you want to use the stock dialer app on your device but have your Google Voice number appear on caller ID, keep the original Google Voice app and select the use Google Voice to make all calls in the settings Additionally, you set the Hangouts Dialer app as your default dialer, which will display your Google Voice number on Caller ID.
[LG G Flex 2] epofhouston:
Google is removing texts feature from Hangouts soon
[LG G Flex 2] Wallstreetkid212:
I've been using hangouts since being integrated with Google Voice that's just a rumor going around since november that they would drop SMS features but I doubt it I'm in the latest version 7.0 i still send and receive text messages just fine
[LG G Flex 2] wtang:
Just an update for everyone. I flashed back to unrooted stock ZV6, then I applied the ZV7, ZV8, and ZV9 OTA updates. Now that I'm on ZV9, which is the latest stock Sprint ROM, I decided to test Google Voice again. Well, the call history log in the stock phone dialer still shows the Google Voice routing number, not the actual number I dialed. I guess something is different (better) in the AT&T firmware that fixes this Google Voice issue because folks here using the AT&T H950 don't have the issue.
[Moto G 2015 Q&A, Help & Troubleshooting] Tenório95:
Moderator Edit:

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).

Moto G — XT1544- Brickado - Bootloader Bloqueado - Desbloqueio OEM desativado - Depuração USB desativado

Fala galera...

Estou com um Moto G 2015 nas seguintes condições ...

Estava na versão 6.0 e tentei voltar para a 5.0 via adb e o celular deu brick.

Brickado

Android 6-0

Bootloader Bloqueado

Desbloqueio OEM desativado

Depuração USB desativado

Ao ligar o aparelho ele vai direto para a tela de Fastboot e quando seleciono START a tela pisca (aparece rapidamente o logo da Motorola como se fosse carregar o sistema) mas quase que instantaneamente volta para a tela de fastboot.

Tentei desbloquear o bootloader novamente mas sem sucesso

Tentei flashear a ROM KitKat mas sem sucesso

Alguem tem alguma dica ou sugestao ou quem sabe a solução para este problema? :confuso: :chorando:
[Moto G 2015 Q&A, Help & Troubleshooting] walter0157:
Depuração tem q esta ativa

---------- Post added at 11:56 AM ---------- Previous post was at 11:56 AM ----------

Nesse link VC baixa os drivers atualizados

---------- Post added at 11:56 AM ---------- Previous post was at 11:56 AM ----------

Baixa o arquivo

---------- Post added at 11:57 AM ---------- Previous post was at 11:56 AM ----------

Executa , apenas ler ele e vai saber oq fazer brother !

---------- Post added at 11:57 AM ---------- Previous post was at 11:57 AM ----------

http://xdaforums.com/devdb/project/?id=1314#downloads
[Moto G 2015 Q&A, Help & Troubleshooting] Tenório95:
O aparelho nem liga mano, como é que vou ativar a depuração???

​

Mas brother, o celular nem liga, como é que vou ativar a depuração?
[Moto G 2015 Q&A, Help & Troubleshooting] walter0157:
oq houve antes dele buga e n liga?
[Moto G 2015 Q&A, Help & Troubleshooting] Tenório95:
Tentei fazer um downgrade pro 5.1, mas esqueci de desbloquear o bootloader e ativar a depuração usb. Fiz o procedimento via adb, alguns comandos deu falha, esperei o celular reiniciar mas ele só desligou, tento ligar ele normal e ele não liga. Só liga em fasboot.:(
[Moto G 2015 Q&A, Help & Troubleshooting] dantas.:
Olá alguém pode me ajudar? meu Moto G3 (XT1544) apresenta na tela de fastboot a informação que deveria ser Locked, está como Engeneering. E isso não me permite desbloquear o bootloader, pois no processo da erro quando eu vou colocar o código que a Motorola fornece para desbloquear.

Já tentei quase tudo da Internet e não consegui.

Alguém pode me ajudar.?