yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
Ok i was wrong. It does work.

I was not sure if i remembered correctly so i tried again.

The thing is... there is no difference between fastboot boot and fastboot flash methods. While in TWRP, it will give enough privileges to set the persist, which i checked and yes... data persist IS there and getprop there returns the prop correctly. But you see... the funny thing is... there are other props that doesn't return in normal boot. So i thought that maybe what i remembered from mi A1 was that, although it did not return the prop with getprop, it would return with camera 2 api probe apk.

And yeah... it says LEVEL_3

So this is my current getprop

adb shell getprop | grep persist

[persist.activate_mbn.enabled]: [false]

[persist.backup.ntpServer]: ["0.pool.ntp.org"]

[persist.bokeh.switch.lux]: [290]

[persist.bt.a2dp.aac_disable]: [true]

[persist.chg.max_volt_mv]: [9000]

[persist.cne.feature]: [1]

[persist.data.df.agg.dl_pkt]: [10]

[persist.data.df.agg.dl_size]: [4096]

So no persist.camera... but in camera2prob apk (attached)

So i will give a test with arnova (yeah people said it doesn't work ok but... just to see if hdr+ works).

But basically goes like...

get twrp.img

fastboot oem unlock stuff... that will wipe your device... i tried the holding vol. down stuff... it did unlock, but i was stuck in bootloop... so i let it wipe...

fastboot boot twrp.img

adb shell... and setprop there

reboot system... getprop here won't return it enabled but check with the camera 2 api probe apk
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
It does work without rooting... but it requires the OEM and wipe stuff

And yeah... the quality is quite different...

I just tested the HDR stock vs HDR+ to check if it is working. So i am attaching both photos just as a quick test (forgive me for the terrible photos).
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
Dude, not sure if you read last reply... but fastboot boot works... in case you wanna try
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] minnuss:
I used that version of TWRP for fastboot boot and did not get the adb connection, that is the last version of TWRP for our device.

With the earlier version I couldn't boot, I was always in bootloop.

Why I did not get adb connection is a mystery for me.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
Hmm... well i was able to boot both sep and oct updates...

adb was enabled when normal boot right? I mean also the notification about allow this computer and stuff... right?

Have you tried to kill adb server, plug out and plug the usb again?

In the usb connection event, it will check which kind of connection it is, and check some permissions, just in case your pc might be doing something...

But what happens when you send adb devices command? Does it detect correctly? or just empty?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] minnuss:
Adb devices was empty

I did try to disconnect usb cable, nothing...

But I did not try to kill adb server...maybe that would work. :eek:

Of course, in windows everything worked fine, with all permissions.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
Well... i saw sometimes windows closing the port when the phone booted, like changing ports or stuff like that.

If adb is not showing the devices then you sorta need to find out what is killing your connection...

go for a unplug kill adb replug...

device manager in windows should show some device in usb connection... try to "refresh" the drivers there... like reselecting the adb driver or something
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Nebrassy:
If you just boot TWRP, it may not be able to decrypt data, and some other stuff might not work

I used setprop in terminal emulator to enable camera2, and it shows up with getprop, it won't show up in twrp because what that command modifies is in /data and not the actual build.prop

And regarding your previous post, there's the following partitions:

Bluetooth_a

Bluetooth_b

devcfg_a

devcfg_b

dsp_a

dsp_b

modem_a

modem_b

xbl_a

xbl_b

pmic_a

pmic_b

rpm_a

rpm_b

tz_a

tz_b

hyp_a

hyp_b

keymaster_a

keymaster_b

cmnlib64_a

cmnlib64_b

cmnlib_a

cmnlib_b

abl_a

abl_b

boot_a

boot_b

system_a

system_b

vendor_a

vendor_b

userdata

mdtp_a

mdtp_b

splash

mdtpsecapp_a

mdtpsecapp_b

storsec

So it's more complicated than you described, treble support doesn't have anything to do with A/B support( Known as Seamless update), the purpose of it is to vastly reduce downtime (Recovery is no longer needed), and so if the installation fails, it just boots back to the previous slot

The reason why it doesn't flash on A when you're on A is because it can't flash over itself while it's running, and also in the case that the update fails it doesn't brick your phone

devices that doesn't support seamless update download the ota to cache then reboot to recovery to install it from there

devices that support it downloads to data and once finished it installs it to the inactive slot (there is no cache or recovery partition)
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
True facts... treble and AB concepts are different... treble are basically to separate google from OEM... AB is just to make stuff easier for OEM update the phones, without taking too long and without putting their hands on googles framework.... (too much)...

about the "more complicated" it's not actually related to all images... for example... you gave us an example of QCT phone... this images will be loaded before even the boot goes up... so...

dsp_a

dsp_b

modem_a

modem_b

you won't be touching those for example... usually modem are images compiled with QCT signature... so... yeah... not touch

abl_a

abl_b

here you have (i believe) primary bootloader... (aboot) also you won't be touching these...

and neither QCT images like...

xbl_a

xbl_b

tz_a

tz_b

hyp_a

hyp_b

rpm_a

rpm_b

devcfg_a

devcfg_b

mdtp_a

mdtp_b

mdtpsecapp_a

mdtpsecapp_b

so let's go directly where we can actually not brick the phone (hard brick i mean)... which will be past the moment that your secondary bootloader chooses which boot partition to boot into...

for example

Bluetooth_a

Bluetooth_b

boot_a

boot_b

system_a

system_b

vendor_a

vendor_b

userdata

I believe that BT has only bluetooth config (not a required partition actually... so this might be for some other reasons)

storsec

not sure what this is used for... likely to be related to security :p

splash

If it is a image... it's likely to have an image in hex or something to store some booting image... probably because there is no file support at this moment.. so i would say it's probably the static image that shows up when booting...

So we ended up basically with...

boot_a

boot_b

system_a

system_b

vendor_a

vendor_b

userdata

there are a lot about the booting process here...

newandroidbook.com/Articles/aboot.html

anyway... there are other stuff like image validation in server side... doesn't concern us now...

about the TWRP not decrypt data... that is not true... before booting into TWRP it requests the PIN... so... just as in android boot... it can decrypt the data partition... also... i checked data partition while in TWRP... everything is there... meaning.. not encrypted...

and while in TWRP it does show with getprop... so no issue in here...

But let's say you bricked your device... i saw that in Mi forum... some mi a1 team member showed there are shorts pin so you can boot into emergency recovery... which means.. your device is safe... all we need is to have guts to open the device... and download all the drivers from QCT... and QFIL.. and bla bla bla... too painful but we can unbrick... well... if mi a2 has this short pins... (which i believe it does) we are safe...
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Nebrassy:
Vendor is mainly for drivers and other stuff from the manufacturer (such as Qualcomm, not Xiaomi)

The images I listed are the ones that A2 has, you can modify all of them, not sure if there are more

splash is indeed the splash android one image in addition to the image shown on fastboot

taken from official TWRP instructions

"Note: Xiaomi's implementation of the keymaster may prevent decrypt from working using the fastboot boot images. Decrypt should work after installing TWRP."
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
Vendor should be from manufacturer... not that manufacturers actually follow some rule... but they now will be putting stuff in ODM partition... if it shows up eventually...

hmm bizarre... fastboot boot image actually managed to do quite fine...

BTW... i found this video showing the test points for emergency dl...

youtube.com/watch?v=ypDU78c4w_Y
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] italomlp:
So, I have 3 doubts:

1 - After all, if I fastboot boot twrp, and try to setprop, and reboot to Android, I'll have camera2api activated? Or is better to flash twrp to do it?

2 - If I have to flash twrp, it can lead errors when I update OTA sometime later? Will the inactive partition (the one that TWRP was flashed) be erased in favor of the updated rom?

3 - In any case, when updated OTA, I have to make all this things again? Or camera2api continues there?

Thanks for the attention.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] AsItLies:
Those are good questions.

1 - The consensus seems to be that 'fastboot boot twrp' works for some people but not for others... I know, How Is That POssible? I think I know, but haven't gotten the chance to test my theory yet. TO answer your question, I'd recommend flashing it to the inactive partition.

2 - No, it won't lead to errors if you flash it, here's why: When you flash it (to the inactive partition), the next is to fastboot reboot WHILE holding Vol UP, then twrp recovery comes up and you do the 'set prop' commands. Then, in twrp, set the other partition active and then select reboot. Once rebooted, go back to fastboot and flash your previous version boot.img to that inactive boot partition (that's what you flashed over with twrp, now you're just setting it back the way it was).

3) No, when an OTA happens you will have to re do nothing. Cam2api will still be working. The confusion around this is because people don't understand (and don't bother to research) what 'setprop persist' does. Suffice it to say, it does not write anything to 'system', it writes to 'data'. That's why you continue to get OTA's and why it 'persists' (there's only one Data partition, it doesn't change with OTA).

you're welcome
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
About data partition not being updated it's not because it has only one. Data was never updated as it contains basically apps data. While google or OEM could update them, they cannot make a diff between old data and new data. What basically created the OTA package is more or less a diff between the old version and newer version. So having one partition is still updatable via cache or data update method. It will basically depend on how the OEM will decide to make the update system.

I agree with everything... But i still think that flashing is just too much as we are able to easily boot with fastboot.

I think the reason that you think that it might not work for some is that you think while fastboot boot would give you a encrypted data and would not allow you to write the prop correctly with setprop right? If that's so... I agree with you... One thing that i started doing.. since fastboot oem unlock wiped my data... And i was in rush... I skipped all the google account and pin fingerprint config. While in twrp i did see once data with scrambled info... The last time i tried (without setting any security anymore) i saw everything ok... so this could be something maybe...
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] AsItLies:
Ahhhh? I have no idea what point yer trying to make? Sounds to me like yer making a bunch of assumptions about what I mean... and they are totally inaccurate.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
Dude these are not assumptions... I'm stating...
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] italomlp:
Hmm... Thanks for the replies! I think I'll try without flashing TWRP, and fastboot boot twrp right after unlock bootloader, to avoid the encrypted data. If I got it, come back to say which way I used.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Forhad777:
It's working on October update?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
yeah i actually enabled it in october update
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] ricardohnn:
So after the latest update, i can guarantee some stuff that i wanted to confirm.

I saw many people saying about having the bootloader unlocked would not get updates, i always remembered with the mi A1 having updates even with the bootloader unlocked, wanted to confirm with this new update.

So yeah, no issues with the unlocked bootloader, it updated smoothly... hdr+ untouched, obviously...
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] lepi:
Is this working on the Official Pie ROM?

Just installed yesterday.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Sagar Sritighor:
hi im using mi a2. and using this. i have unlocked with this apps. but i cant root my device with this. please help me
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Appar khandelwal:
I read today this on searching in google to enable camera2api without root in mia2..

I'm in feb update (india).

I downloaded these patch boot file & trying to go in fastboot mode..

But when i connect my phone to laptop (windows 7), there is connecting sound i heard ..

I enabled already oem unlocking option & usb debugging in phone through tapping 7 times & all ..

But when after inserting commands in adb & entered , it's saying waiting for device..

& Nothing is shown in screen in mi a2 , other than fastboot bunny..

Can anyone help me what's going on wrong here ?

Link of that site :

https://www.the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/

The *** is putted by xda automatically in link..

In actual in place of *** it is 'the custom Android' (without space)
[LG V40 Real Life Review] Mike26037:
Been loving mine so far! Have had it for about a week.
[LG V40 Real Life Review] tube517:
Just got mine on Monday. Fantastic phone. Still keeping my V20.

Need to experiment more w/the camera.

Display is very sharp.

Love the quad dac and still using my 128 gb sd card.
[LG V40 Real Life Review] rfarrah:
Had mine for a couple weeks now. Came from an LG G6 and I'm really liking this phone so far. Not one complaint.
[LG V40 Real Life Review] treesap:
Wait... You have Asian leopards?!
[LG V40 Real Life Review] mikekoz:
I have had mine since the 20th and these are my thoughts so far! I am coming from a new iPhone 8+, and still have my three year old LG V10.

The good?

1. The screen is beautiful! I would have preferred if they made it a bit wider where it was 18:10, but I will get used to it. Most large phones seem to be made this way now.

2. The phone is very fast and fluid like a new phone should be

3. It does have a lot of garbageware on it out of the box, but most if it I was able to uninstall. This is pretty much unavoidable if you want an Android device unless you get a Pixel.

4. I got it for half price!! ;p)

5. My wildlife photos I have on my SD card look great! I have not tried the camera yet, but rarely use my phone as a camera. I also have not listened to any of my music on it, but if it is anything like my V10, it will be great!

The bad?

1. Not that I would fill it up, but after three years the onboard storage is still 64GB? Should have been 256GB. I know it will take a 2TB microsd card when they are available, but if you install a ton of apps, this storage is better to have on the phone. Again, I would not fill it, I am just a bit surprised at this.

2. I wanted a glass protector on it, but I have yet to see one that gets good reviews. Maybe this is because it is so new. I bought an Otterbox for it and I cannot believe they left off the protective screen. I may take the screen off my V10 case and see if I can get it on the V40 one.

3. It does not have a replaceable battery. If you register the phone with LG within 90 days after you but it, they will extend your warranty for another year. The built in batteries are a bad design in my opinion.

Anyhow, I am just glad to be off of the Iphone and back on an Android device!
[LG V40 Real Life Review] SaintlySins:
Been away a while, sorry for delayed reply.

Yes, but don't think it's like Wild Kingdom here ... they're cross-bred to be domesticated (mostly). They're a bit smaller than Savannah's, yet just as exotic looking and way less maintenance. More 'house-cat-ish'. Quite affectionate, one even plays fetch ... for h o u r s if you've the time and patience to keep throwing the ball.
[LG V40 Real Life Review] wing_addict_usa:
Incredible phone. Not sure why they moved the power button though. I came from v20.
[LG V40 Real Life Review] rfarrah:
Agreed! I liked it on the back with the fingerprint sensor.
[LG V40 Real Life Review] Medevac1:
After ownership of LG's Leon, G4 and the V20 I went with the Samsung Galaxy Note 8/9 when it came time to upgrade. I had good experiences with all of my LG phones but when they dropped all of the features that made them stand apart from the herd (swappable batteries, IR blaster, etc.) It was time to part ways. I had no interest in LG all through the various V30 releases and the G7 ThinQ. The V40 caught my attention with all the features it brought to the table but at nearly a grand asking price it was pretty much a nonstarter. But when I ran across an offer for a new in the box for $400 USD. it was an offer I could not refuse. This device is feature packed, functional and fun. It's like a V20 on steroids. I do a lot photography and this phone's camera and video capabilities add a layer of creativity not to be found on any other device. It replaced my still very much alive and kicking V20 as my daily driver and it does everything I ask of it from navigation to hands free phone calls and does it all well.
[LG V40 Real Life Review] sas007:
Don’t think there is a lot of overall love looking at this LG v40 thread..nobody seems to visit it or answer questions etc..maybe not a very popular device me thinks..and I just purchased one..dooh
[LG V40 Real Life Review] Medevac1:
Don't despair my friend. You purchased a great device. The action is over on the LG V40 Reddit or Android Central forums.
[LG V40 Real Life Review] sas007:
Thanks will head over and take a look..cheers.
[LG V40 Real Life Review] sas007:
Had my LG V40 a week or so now and boy..I LOVE IT!!!
[LG V40 Real Life Review] Medevac1:
Cheers!
[LG V40 Real Life Review] sas007:
Now I have the proper UK stock of the LG V40 instead of the bloody Hong Kong version I love it even more...
[JASJAR, XDA Exec, MDA Pro ROM Development] orp-adm:
hi@all

my mda pro with win mob 6 always shows a message: "\windows\wcshlp.exe can not be found"

i looked for the file but couldnt find it. can sb. upload it please?

thx
[JASJAR, XDA Exec, MDA Pro ROM Development] ajie:
I Think Bad Uninstall...

Please Cek \Windows\StartUp\wcshlp.Ink ===>>> Delete This File Or Backup This File and Then Save to Another Directory. My Be My Document.

(U can Explorer with Resco Explorer)
[JASJAR, XDA Exec, MDA Pro ROM Development] orp-adm:
this file doesnt exist. the message shows up not only after booting but always when turning it on.
[JASJAR, XDA Exec, MDA Pro ROM Development] ajie:
please Try Again...Use Resco explorer. Setting Resco explorer with Custom setting.

Open Resco explorer>Menu>General>Browser> Please Uncek to All>Done

and then..Menu> Find> So type this Tex wcshlp

Thanks..
[JASJAR, XDA Exec, MDA Pro ROM Development] orp-adm:
used resco explorer. neither the exe nor the lnk does exist.
[General Topics] Deuce Nitro:
I need a checklist app that will allow me to assign multiple categories to checklist items. (I've been a ListPro user for years, but their workaround for doing this - multiple checkbox items in lieu of a category field - is crap.)

Does anyone know of a checklist app that can do this?
[General Topics] Deuce Nitro:
For now I've created a text field for tags and I'm using that. Works pretty well.
[Touch Dual, MDA Touch Plus General] disflipissofresh:
where can i get a htc niki - 20 key ?? can you guys like give me a site to where i can buy it from?? thnxs..
[Touch Dual, MDA Touch Plus General] eyecrispy:
try ebay. that's where i got mine.
[Touch Dual, MDA Touch Plus General] disflipissofresh:
yes i found one =]. im bouts to get it soon. so there will be a new htc niki user coming..
[Samsung Galaxy Note 9 Questions & Answers] Hendriksie:
Hi,

I'm having a strange issue with audio over Bluetooth when Mobile Hotspot is on and I was wondering if there is anyone who can help me out.

When my Mobile Hotspot is on and I'm listening music in my car over Bluetooth there is sometimes a random stutter in my audio.

The stutter (no audio for small amount of time) only lasts ~300ms but it totally random. Sometimes there are a few stutters in a few minutes of time, but sometimes it can also a just one stutter within 15 minutes.

I've got a dashcam in my car that I want to have connected to the internet when I'm driving, so that's why I'm using my Mobile Hotspot in my car.

The data flow is as follows (simultaneously):

4G connection => Deezer music app => Bluetooth => audio.

Dashcam => Mobile Hotspot => 4G Connection.

I've got a feeling that the stutter is happening when some network activity is happening over the Mobile Hotspot, but I'm not sure.

When I disable my Mobile Hotspot the stutters are gone.

Your help is appreciated!

Edit:

After more testing it has nothing to do with the Mobile Hotspot, but with Bluetooth in general. Especially when receiving a notification while streaming audio over Bluetooth gives me stutter.

I have the 8GB Exynos (512GB) edition
[Samsung Galaxy Note 9 Questions & Answers] traffas:
I'm getting the random Bluetooth hiccup without hotspot enabled.
[Samsung Galaxy Note 9 Questions & Answers] a2fast:
Also me even when I connect one Bluetooth device
[Samsung Galaxy Note 9 Questions & Answers] Hendriksie:
Hm, yesterday was the first time since this phone releases that my Bluetooth connection also sometimes stutters, even without the Mobile Hotspot enabled. It's a lot less than having Mobile Hotspot enabled but it still happened.

Very weird, my Bluetooth connection also stuttered on my previous phone, the Samsung Note 3. Only on the stock rom though, when I used LineageOS the stutters were gone.
[Samsung Galaxy Note 9 Questions & Answers] nathlynn22:
I was getting audio stutter over Bluetooth with music and notifications causing problems. My phone is being sent back Monday though.
[Samsung Galaxy Note 9 Questions & Answers] beta546:
From the op I was maybe thinking some crossover signal interference, but with a number of you saying the same and now I've just tried my Bluetooth ear buds and they stutter a little too, I guess it's a more general issue. I doubt it's a hardware problem as Bluetooth isn't exactly a new thing, I can't see Samsung using shoddy radios. I assume software as stuttering seems worse with screen off, maybe some power saving feature misbehaving, or background processes not getting priority, I don't know. Hopefully an update fixes it.

Are any of you on custom ROMs and experiencing it?

I'm going to flash one as soon as my memory card arrives, I thought woohoo 128 GB, no need to buy yet another card for another device, then read all the development forums that say in the process you need to format data haha, so a card is needed after all ? But once I'm done I'll test Bluetooth again.