yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] raymond_bqg:
Move .xml file to /system/etc/permissions.

Set permissions to rw -r -r

Reboot!

If u can't download the XML file then download from

https://drive.google.com/open?id=0B4...3NrYUd2akxzT2s
[General Questions and Answers] jaimejdv:
Hi, I found this file already on my folder. I believe that you were maybe trying to help me with Oxygen OS and the USB host issue in drivedroid.......? Thank you, but I am not on Oxygen anymore, I am using PureCM and I am trying to find an option to enable OTG on it.
[Galaxy S6 Q&A, Help & Troubleshooting] Friel74:
Hopefully someone can help. I've a Samsung Glaxy G925F here which has been completely wiped, it's got nothing on it. It can't even boot up. The only thing on it is TWRP recovery. How would I go about getting the phone up and running again? I've tried flashing the stock ROM on to it, but get an error saying "Could not find 'META-INF/com/google/android/update-binary'".

Any help would be appreciated.
[Galaxy S6 Q&A, Help & Troubleshooting] brenner650:
Tried flashing matching pit, and than fw through Odin?

Or Smart Switch emergency initialization with phone sn?
[Moto G4 Plus Questions & Answers] kishan_meena:
moto g4 plust Volte supported phone,then why i am not able to make a video call using jio4gvoice app or without app
[Nexus 6P Q&A, Help & Troubleshooting] esmith13:
I am trying to figure out a way to still adjust the non-BT media volume slider (music note symbol in volume panel) while actively connected to bluetooth. The only media setting I have access to is the BT-volume slider (BT logo in volume panel).

I understand in general that when connected to BT all media playback goes to BT and therefore I shouldn't need access to the non-BT media slider but when I use Waze in my car I intentionally keep it set to use the phone speakers for Waze audio while Bluetooth handles phone calls for me. The issue comes in when my non-BT media volume was set low (maybe I was playing a game on my phone at work...) and I jump in the car after. I forget to turn my non-BT volume up before starting my car and now if I need to use Waze the volume is stuck on a low volume since I can only adjust the BT volume once in the car.

I know I can disable bluetooth, fix the volume and reconnect to the car but that's a pain in the a** to deal with (I do it now).

Bottom line, is there any way to make BOTH media sliders accessible at the same time? I was browsing thru the xposed module database and couldn't find anything useful so I thought I'd ask here. I'm using a stock/rooted Nexus 6P currently on MM but will want a solution for Nougat as well, eventually.

Thank you in advance for any help!
[Nexus 6P Q&A, Help & Troubleshooting] gjkrisa:
I believe with nougat you can change them individually when I have my headphones on I get all of the sliders but not every time

I can hit the arrow on the right though to bring it down.
[Nexus 6P Q&A, Help & Troubleshooting] esmith13:
That is how it always works. The problem only occurs with Bluetooth. When a bluetooth connection is made the bluetooth volume slider REPLACES the normal media slider. Their are still only three sliders (using your picture as an example). The middle one (music note) changes to the bluetooth one. I want to be able to access all four when there is a bluetooth connection.
[Nexus 6P Q&A, Help & Troubleshooting] gorman42:
It's a little nightmare of mine when trying to automate stuff through Tasker. I searched a little bit and didn't find anything.
[Windows Mobile Development and Hacking General] alex_time:
Hi to everybody.

Do you know if it possible through a registry update, to not allow data connection if the xda is in roaming?!

Hope that someone has an answer or a glue!! I really need it guys, belive me!
[Windows Mobile Development and Hacking General] ai6908:
Try Modoca no data (search for a cab file), it does not exactly disable data when roaming, but allows you to turn data connection off and on...
[Windows Mobile Development and Hacking General] alex_time:
Thanks for the replay, but this not useful for me, I mean, I can turn data off and on simply changing the data connection on settings. Maybe this cab is faster than open everytime Start->Settings->Connections->Connections->Advanced->Select Network, but I always need data connection because of push email service, and turn of it only on roaming because of traffic cost under roaming. Any other ideas?
[Nexus 5X Q&A, Help & Troubleshooting] eatsleep:
I have Xiaomi's USB c to micro USB adapter: Amazon link

I am trying to connect flash drive with micro USB connector but the nexus 5X won't detect it. The USB flash drive: link
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
You need a USB Type-C OTG cable.
[Android General] DarkAlpha.Sete:
delete this
[Nexus 6 Q&A, Help & Troubleshooting] Lim_Dul:
Hello there!

I’m currently the newest Nougat image (7.0.0 NBD90Z). Before flashing to this version I was on the latest marshmallow image (6.0.1 MOB31H). Initially I dirty-flashed the image, keeping the data partition intact.

However, after I tried to root the phone with SuperSU 3.78 SR1 via TWRP recovery I got into a bootloop. After restoring stock again, I backed up my data partition (nandroid backup) and did a clean flash. On the clean ROM rooting works just fine - when I tried restoring my data partition after root was up the phone got into a bootloop again.

I repeated my experiments with SuperSU 3.78 (non-SR) and 3.76 - same results.

It seems the phone gets stuck quite late into the booting process since it is detected by my PC and listed under adb (as offline, mind you).

I don't even know how to begin to analyze or debug this problem since rooting and even dirty-flashing between major versions has been working for me since Nexus 4 / KiteKat times.

Letting go of all my userdata (at least entirely) is not an option.

Any ideas or directions how I could proceed into tracking down the problem?
[G4 Q&A, Help & Troubleshooting] improvius:
I'm trying to troubleshoot a friend's phone. It keeps playing a voice that says "Verizon wireless" whenever a call comes in, regardless of the ringtone selected. I think it plays the voice at other times, too. I couldn't find anything in settings.
[ZenFone 2 Q&A, Help & Troubleshooting] brunomcf:
Hey guys!

I had rooted my phone a couple of days ago to use an app it needed routed access.

I totally forgot about not doing official updates, and after doing this update it just got stuck on a endless bootloop.

Even after I unrooted it.

Can I unbrick without loosing all my data? What process should I follow?

Thx guys :)
[ZenFone 2 Q&A, Help & Troubleshooting] Dzin4a:
Was in the same situation, fixed mine by following this guide on asus forum

for the record: fastboot flash fastboot droidboot.img failed

https://www.asus.com/zentalk/thread-39487-1-1.html

I downloaded his `rooted` system that matched my previous update version (Z00A_WW_2.20.40.196), also get adb and fastboot elsewhere as his post is old.

Check if your computer can see the phone via adb when it is in boot loop, if yes then you can back up all the data with

adb pull ./ C:\pathoncomputer\
[ZenFone 2 Q&A, Help & Troubleshooting] brunomcf:
Thanks for your answer. Where could i get an updated Adb and Fastboot for this device?
[ZenFone 2 Q&A, Help & Troubleshooting] Dzin4a:
There is massive list of resources on zenfone 2 xda forum.

http://xdaforums.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596/page1
[Xiaomi Mi 5 Questions & Answers] dhrubaz:
Recently i Bought a mi5 but it is installed xiaomi.eu stable version. But i want to get back in official. Even i do not know if my device bootloader is locked or unlocked. What to do? :(
[Xiaomi Mi 5 Questions & Answers] chiragkrishna:
connect your phone in fastboot mode(VOL DOWN & POWER) and type

fastboot oem device-info

you should get

C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.060s

if "Device unlocked: true", then download what ever rom you want and install it

else unlock it..
[Xiaomi Mi 5 Questions & Answers] dhrubaz:
Adb is required? Where to get for mi5 bro?
[Xiaomi Mi 5 Questions & Answers] gm007:
Get minimal fastboot and adb from here http://en.miui.com/thread-112662-1-1.html
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
My nexus 6 had been auto update/upgrade from android 6.x to android nougat 7 a few week ago.

So, after reboot my nexus can't boot to home screen.

It still alway occur error message something like this.

" unfortunately setting has stopped " infinity loop. ( can't access to home screen ) ( It's alway show the dark screen )

and i try to enter the recovery mode.

##########

1. If your device is on, turn it off.

2. Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.

3. Press the Volume down button until you highlight "Recovery mode."

##########

Nothing happen , I can't access the menu recovery mode ( Still in the dark screen )

I hv try so many times , many days.

Please help / suggest me how can't i recovery my nexus 6.

Thank you very much in advance.

Please help.

Note
[Nexus 6 Q&A, Help & Troubleshooting] holeindalip:
Are you bootloader unlocked?
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
You mean root ?

No, my nexus hv not been root.

My nexus still very original.
[Nexus 6 Q&A, Help & Troubleshooting] holeindalip:
No mean as in bootloader unlocked and can flash factory images
[Nexus 6 Q&A, Help & Troubleshooting] dahawthorne:
pratchaya, when you start your N6, do you see at the bottom of the screen a picture of a padlock with the lock open on one side?
[Nexus 6 Q&A, Help & Troubleshooting] pr0ndigy:
1. Go here, https://developers.google.com/android/nexus/images

2. Download this, https://dl.google.com/dl/android/aosp/shamu-nbd90z-factory-92e7bb05.zip

3. Power off phone, hold down power+volume down, boot into bootloader

4. Extract contents of zip to your computer

5. Flash fresh install of Android on your phone

Actually do this instead now that i've thought about it.

1. Go here, http://www.wugfresh.com/nrt/

2. Download the latest version of Nexus Root Toolkit (v2.1.9 as of writing this)

3. Install onto your PC

4. Use NRT to Flash Stock + Unroot

I use NRT all the time when wanting to flash beta images from Google. Never had an issue with it.
[Nexus 6 Q&A, Help & Troubleshooting] holeindalip:
That's what I was gonna tell him, but it won't work if his bootloader is locked, or if he could just flash the recovery through fastboot and side load the OTA from there
[Nexus 6 Q&A, Help & Troubleshooting] pr0ndigy:
Maybe i don't know this just because my bootloader has been unlocked since the day i got my phone.

But i would imagine that google's STOCK image would be flashable, even with a locked bootloader...

But if it's not, then that sucks.

But NRT has the option to Root+Recovery from the fastboot/bootloader...But once again, not sure if you need to be bootloader unlocked before that will work.

I guess you have nothing to lose trying and seeing what happens.
[Nexus 6 Q&A, Help & Troubleshooting] biggiesmalls657:
If he holds down the three button salute, it will take him to the bootloader where he can run fastboot OEM unlock to unlock his device then flash just as long he has unlockable in developers settings checked.
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
Hi, I don't know about bootloader lock or unlock.

But I'm a normal user , just use my nexus as normal user ( original from factory + update + upgrade + reset sometime ).

Is this mean bootloader lock ? sir.
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
Hi, I can't see any picture except these photos.
[Nexus 6 Q&A, Help & Troubleshooting] dahawthorne:
Well, that's puzzling. I've just restarted my N6 to be sure of my facts, and there is clearly a screen before the four dancing icons you show in your first picture. The very first thing that the phone shows on boot is a pure black screen with "Google" in big white letters in the centre, with (on my unlocked phone) the picture of an unlocked padlock at the bottom.

Are you saying that you don't see this?

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

And while we wait for the answer to the question above, please try this:

- Power off the Nexus 6 completely.

- Next, press and hold Volume Down, Volume Up and Power simultaneously – don’t release the buttons until Fastboot Mode menu appears.

Note that this is not what you've already tried - this should get you into Bootloader mode, whereas you described the Recovery procedure in your first post. Does this procedure get you any screen? If so, please describe what you see.

(Further edit: just noticed that biggiesmalls657 suggested this on the first page, but I think that pratchaya appears too inexperienced to know what you suggested).
[Nexus 6 Q&A, Help & Troubleshooting] holeindalip:
You guys are incorrect

This isn't possible unless the ROM starts and he can check OEM unlock in the developer options

And he can flash the OTA file with a locked bootloader but he has to have a working recovery
[Nexus 6 Q&A, Help & Troubleshooting] pr0ndigy:
Have you tried a Hard Factory Reset?

https://www.youtube.com/watch?v=0nDLvy8F5qk
[Nexus 6 Q&A, Help & Troubleshooting] biggiesmalls657:
I just said that!

Edit: Did you notice force closes before all this happened? Lots of force closes when doing a factory data reset sometimes means it's hardware with the internal storage. If you can't boot into Android to check OEM unlock button and fastboot doesn't allow you to flash while locked then I am not sure then.

---------- Post added at 05:47 AM ---------- Previous post was at 05:41 AM ----------

The stock recovery is crappy as it's rough to get in unless you try lots of combos.

---------- Post added at 05:51 AM ---------- Previous post was at 05:47 AM ----------

What if he were to select the factory mode in the bootloader menu? I know that trying to access the stock recovery is a pain sometimes. OP what do you see when you select Recovery Mode?
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
I hv tried this at 1st day but it nothing happen.
[Nexus 6 Q&A, Help & Troubleshooting] dahawthorne:
So you're reading only the last post and ignoring earlier possibly helpful questions...? Ok...
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
I'm trying to do every suggestions.

I'm trying to do

Method #1

1. Go here, https://developers.google.com/android/nexus/images

2. Download this, https://dl.google.com/dl/android/aos...y-92e7bb05.zip

3. Power off phone, hold down power+volume down, boot into bootloader

4. Extract contents of zip to your computer

5. Flash fresh install of Android on your phone

Method #2

1. Go here, http://www.wugfresh.com/nrt/

2. Download the latest version of Nexus Root Toolkit (v2.1.9 as of writing this)

3. Install onto your PC

4. Use NRT to Flash Stock + Unroot

And will tell/ask you after got result.
[Nexus 6 Q&A, Help & Troubleshooting] dahawthorne:
And still ignoring my post... http://xdaforums.com/showpost.php?p=69115384&postcount=12
[Nexus 6 Q&A, Help & Troubleshooting] pratchaya:
Hi,

I hv already try this method . but nothing happen on my nexus .

( press and hold Volume Down, Volume Up and Power simultaneously more than 20 min. and nothing show , still dark screen )

Actually I try this method at day one that my nexus dead.
[Sony Cross-Device General] SuperLamic:
Hello,

this thread is only for development discussion regarding development of android for msm8974. If you have anything useful, it's the right place, however, it's not for non-dev things.

Current state of cam:

working, though, still low quality. Will be fixed on v6. (and no videocam)

if you wanna have live chat, you can join an IRC

http://webchat.freenode.net/?channels=#freexperia
[Sony Cross-Device General] SuperLamic:
placeholder
[Sony Cross-Device General] munjeni:
Ok. Seems I have wasted time with camera :( I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
[Sony Cross-Device General] rcstar6696:
So now i will explain all a little bit more

It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too

All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them

We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs

Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat

So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.

I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam

So keep it up and help to fix the things :)

If you need some help or some more infos you can write me via pm or hangouts
[Sony Cross-Device General] SuperLamic:
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
[Sony Cross-Device General] rcstar6696:
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
[Sony Cross-Device General] munjeni:
I don't know but I will try in next few days when I get more free time for installing sotck rom
[Sony Cross-Device General] munjeni:
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!

That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master

Please don't post misinformation if you are not 100% sure!
[Sony Cross-Device General] mkdmc:
Camera.msm8974 is an useless lib on stock rom

Camera.qcom is Sony camera hal.

I had found out it few months ago.
[Sony Cross-Device General] rcstar6696:
If you read it again you will see that i talk about drm verity not drm keys :eek::eek:

Test it if you want we had cm13 booting on 3.4 and it was only possible with display patches audio patches where only needed to fix some small sound issues

Chirayu desai one of the cm maintainer can confirm this.

Selinux is correct this needs to be rewritten and mmap too but i wanted to write it understandable for all guys not only for devs

The other thing about the camera hal is an info from alin but if you say he isnt correct then you will be right :good:

It could be possible that the cam will start without but not with all Features

Do what you want but i'm quite sure that you don't get a fully working cam :)
[Sony Cross-Device General] munjeni:
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality can be noticed. I will definitelly go to 3.10 kernel till after camera gets working
[Sony Cross-Device General] munjeni:
Thats what I thinking now too! Did you tested, whats happening when camera.msm8974.so gets removed, is camera working? I need confirmation on rom 4.6.1.A.236 ! Which I found camera.qcom.so uses chocobal and excal blobs, camera.msm8974.so uses nothing from that.
[Sony Cross-Device General] munjeni:
Did you try to grep that file? For example

strings camera.msm8974.so | grep drm

You can see null results about drm
[Sony Cross-Device General] nailyk:
Hi

thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.

Obliviously it doesn't change anything to camera facts.

About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.

I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.

About the camera, i doubt it is related to TA partition.

I just made a test with:

z3 stock .575 locked bootloader

z3 stock .200 unlocked bootloader

z3 cm-12.1

Camera on both stock z3 are working the same way.

I need to make the same test with both stock device on the same rom version now.
[Sony Cross-Device General] rcstar6696:
Drm verity are not the same as drm keys :p the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices

You can look into hammerhead source and you see some commits about drm verity too but hammerheads cam libs are not included in the verity

I have castor and sirius

---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------

Hey yes i was only talking about stock not about thr cm kernel

When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
[Sony Cross-Device General] munjeni:
Where you found that info? Any log about it?
[Sony Cross-Device General] rcstar6696:
Ask alin Jerpelea or chirayu deasi all infos i give too you are from them

For drm verity just use google :/
[Sony Cross-Device General] munjeni:
I'm oticed frezings and some strange things using that msm8994 display hal, but on my buld I have used codeaurora LA.BR.1.3.6_rb1.3 branch for display, camera and some things in media, I can confirm that display things fly, its soo smoth, video soo smooth, screen power off/on smooth... if you want to try here is it http://munjeni.myiphost.com/mynougat.tar.gz , don't forget to build kernel with script buildkernel.sh since it will install kernel headers from 1.3.3 and will build 1.3.3. kernel too. I have told jerpelea about it but no reaply about LA.BR.1.3.6
[Sony Cross-Device General] nailyk:
Really? :) My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!