Related
Hi everybody!
Normally I was using OxySlim ROM and had no poblems with it at all.
Yesterday I tried to flash CM13 with Nano-Gapps. Everything worked
and I configured 4 fingers for fingerprint unlock. After some more
configuration and app installations I tried to unlock with my fingerprint
and my phone freezed completely. I rebootet with long press of On/Off button
and retried, but it freezed again.
Then I restored my OxySlim Nandroid backup and even there my phone freezes now
with every fingerprint unlock attempt. I tried the "[Guide] OnePlus 2 Home Button Dead Solutions", but no change. (Sadly I have no *#808#-menu with OxySlim)
My homebutton and all other buttons are working well, but phone freezes with every fp-unlock attempt.
Find some logs attached. Fingerprint messages are tagged with "FingerPrintLogUtil".
Thank you for your help!
hello.. i faced the same issues wen i switched to cm 13 from OOS.. fp sensor would not work even wen i tried on different roms like crdroid and bliss pop.. also after d first reboot on every rom, d dialer app would force close..
den i read somewhere about d new modem.. i looked for it and flashed it, after factory reset and clearing cache.. den i installed d cm 13 again wid mini gapps.. not facing a single issue after dat and d fon works flawlessly now..
so u might consider flashing dat new modem, if u havnt already..
here's d link:
https://androidfilehost.com/?fid=24407100847293158
Thanks for your answer @meetg22 !
Which CM13 are you using? CM13 from @Seraph08 ?
Because I read here that Seraphs cm13 requires old Modem? I would give it a try but
since getting back the old modem seems not so easy I would stick to the old one until I'm sure to do the right thing.
yes @obermeier i am using Seraph's cm 13..
also i visited the link that you mentioned... i can see that there it is written to flash d new modem for seraph's rom if coming from oos.. please confirm again
obermeier said:
Thanks for your answer @meetg22 !
Which CM13 are you using? CM13 from @Seraph08 ?
Because I read here that Seraphs cm13 requires old Modem? I would give it a try but
since getting back the old modem seems not so easy I would stick to the old one until I'm sure to do the right thing.
Click to expand...
Click to collapse
meetg22 said:
yes @obermeier i am using Seraph's cm 13..
also i visited the link that you mentioned... i can see that there it is written to flash d new modem for seraph's rom if coming from oos.. please confirm again
Click to expand...
Click to collapse
Seraph's build will work on both modems. I confirmed again.
if you read carefully you'll know what I said.
1. Which modem/firmware should I flash before I install this ROM?
This is question raised by many people who have security settings crash or bootloop. So I wanted to write upon this in two ways.
If you are coming from Leaked H2OS Marshmallow ROM then,
First, you need to flash the revert2lollipop zip from here How to revert back to Lollipop by Yash98 if not your device will be in boot loop.
Below are the ROMs you can flash directlywhen you come from Leaked H2OS MM or Based ROMs after flashing revert2lollipop zip.
ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 __Seraph08
[ROM][6.0.1][UNOFFICIAL] Blissrom __benschhold
[ROM][6.0.1][UNOFFICIAL] crDroid __taker18
[ROM][6.0.1][UNOFFICIAL] Temasek CM 13 __benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 __taker18
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x __regalstreak
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 __Trafalgar Square
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project [email protected]
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for __Raja.M
Click to expand...
Click to collapse
If you are coming from OxygenOS/HydrogenOS Lollipop ROM then,
I installed O2OS every time for testing I changed ROM, it really is a hectic task.
Below are the ROMs you can flash directlywhen you come from OxygenOS
[ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 __Seraph08
Click to expand...
Click to collapse
Install *new*modem from https://androidfilehost.com/?w=files&flid=49404 for below ROMs
[ROM][6.0.1][UNOFFICIAL] Blissrom __benschhold
[ROM][6.0.1][UNOFFICIAL] crDroid __taker18
[ROM][6.0.1][UNOFFICIAL] Temasek CM 13 __benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 __taker18
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x __regalstreak
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 __Trafalgar Square
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project [email protected]
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for __Raja.M
Click to expand...
Click to collapse
I tried it with new modem, no improvement.
But you are right, Seraphs CM13 build works with both modems.
I can confirm that.
I was then trying krishnas solution mentioned here.
But, I can only give you one suggestion. Try installing OxygenOS, check your fingerprint from 808 menu and then flash CM13. This will make your fingerprint unlock normal again.
Click to expand...
Click to collapse
Thank you very much @krishna442, that worked! Even without clean install of CM13. I just flashed my nandroid backup again.
obermeier said:
I tried it with new modem, no improvement.
But you are right, Seraphs CM13 build works with both modems.
I can confirm that.
I was then trying krishnas solution mentioned here.
Thank you very much @krishna442, that worked! Even without clean install of CM13. I just flashed my nandroid backup again.
Click to expand...
Click to collapse
:highfive:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
+1
ajeteja said:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
Click to expand...
Click to collapse
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
NZedPred said:
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Click to expand...
Click to collapse
Yes I was on soak test. Pls help Moto g5s plus
@NZedPred Can you pls help? I am also facing the same issue.
#shubham Bane/- said:
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Yes I was on soak test. Pls help Moto g5s plus
Click to expand...
Click to collapse
kiranbala003 said:
@NZedPred Can you pls help? I am also facing the same issue.
Click to expand...
Click to collapse
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
@NZedPred thanks man. It worked
kiranbala003 said:
@NZedPred thanks man. It worked
Click to expand...
Click to collapse
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
ugander1989 said:
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
Click to expand...
Click to collapse
Step by step instructions are in my post above... Do you have a more specific question?
Does this work with moto G5s plus [sanders]
Will the above method work with moto g5s plus sanders
sarath6622 said:
Will the above method work with moto g5s plus sanders
Click to expand...
Click to collapse
Yes, if you did the same thing, i.e. flashed stock Oreo and then went to an Oreo custom rom, then yes the same approach will work. I have a flashable build and persist fix for sanders here:
https://www.androidfilehost.com/?w=files&flid=280579
Clean flash/Dirty flash?
@NZedPred I am facing the same problem. I own the Indian Moto G5 Plus (retin)
Here's what I did -
1. I unlocked my bootloader
2. I updated to Oreo (soak test) using the OTA capture.
2. I somehow rooted my phone after flashing TWRP.
3. Just after I flashed TWRP i.e. before rooting, I took a complete backup including the persist and EFS partitions.
4. After rooting, I clean installed MSM-Xtended ROM (8.1.0)
5. Everything is fine, but the fingerprint feature doesn't work/appear anywhere. Even the gesture support is gone.
What do I need to do?
If I follow your steps mentioned above i.e. flashing the persist-fix first, flashing the Nougat ROM you provided and then flashing any custom ROM, how should I proceed?
I am really confused whether I should clean flash (Wipe Data, System, Cache) after every step or dirty flash everything.
Please guide me.
Before you go back to custom ROM from stock Oreo ROM you have to flash stock nouget ROM if not fingerprint , NFC will not work.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
@sinchan_nohara
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
U wrongly flashed firmware, try Oreo custom rom
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
dhinesh_cool said:
U wrongly flashed firmware, try Oreo custom rom
Click to expand...
Click to collapse
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
navinsingh said:
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
Click to expand...
Click to collapse
ask in telegram grp
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Prince parth said:
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Click to expand...
Click to collapse
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash moun kernel in different ROMs to check whether it works or not?
ImSSin said:
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash mourn kernel in different ROMs to check whether it works or not?
Click to expand...
Click to collapse
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine??
Prince parth said:
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine
Click to expand...
Click to collapse
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
ImSSin said:
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
Click to expand...
Click to collapse
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Prince parth said:
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Click to expand...
Click to collapse
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Don't need to flash stock ROM I'm on Resurrection Remix treble ROM and for flashing I followed steps stated in forum.. it's work for me no bootloops.
First fastboot flash userdata userdata.img and then boot into Twrp and flash ROM zip that's all.
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Userdata.img is not necessary, just install the rom and format data(must) then reboot
Thnx for the help guys but after spending hours flashing different ROMs, TWRPs and kernels, I finally found the solution for the touch screen bug.
eXtreme kernel is the only kernel that was able to fix the screen completely. Its working in all of the custom ROMs (tried on LOS15.1 & 16, RR, LR Oreo and pie, etc.)
The stock versions of francokernel, void kernel are able to fix the touch screen but it breaks WiFi so they are not a complete fix.
And btw stock versions of Franco,extreme,void kernels work on the stock ROM.
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
yasars said:
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
Click to expand...
Click to collapse
have you tried flashing the extreme kernel?
extreme kernel v11 not working only V8 working for me.
What about you guys??
only with kernal 4.9 based custom roms, i have touch issues as described in here. and yeah i had screen replacement too.
now i can't flash any new pie roms as they all are based on 4.9 kernals and i can't find the old pie roms based on 3.18(link dead)..right now on los15.1
:crying::crying::crying::crying::crying::crying::crying:
Same problem here
ImSSin said:
have you tried flashing the extreme kernel?
Click to expand...
Click to collapse
ImSSin
Were you able to solve this problem? Can you put the link to download the kernel?
I flashed soak Oreo test 3 and Lost Imei so I moved to Custom Rom Cosmic Os New Build and Lost FP
same thing Happened in Bootlleger ROm
Lost FP means - In start we have to make one google account and it asks for Fingerprint security but In my case It direcly Finish the setup after Config of Google account
So I can't use FP Gestures and FP Security
All things are working fine Including Volte and Other Stuff
just Facing this
PS- FP is working in Stocks only
I heard no one Facing this issue ,I am Not Blaming the Devs Just Requesting the Solution! :good::good:
The solution is in the oreo thread. Read the first two posts.
ıllıllı shiv ıllıllı:
Just some info ..
As some people flashed stock Oreo and when they moved to custom ROMs fingerprint doesn't work for them.
I also moved to stock Oreo and wanted to come back to custom ROMs. As we know (or maybe not) to move to custom ROMs, we have to flash stock nougat first , and for this you have to download a 1.3gb file.
What I found -
Modem from stock Oreo is breaking fingerprint. Other partitions have no role in it.
So if you want to move to custom ROMs , just flashing the nougat modem will work, you don't have to flash the whole ROM.
Nougat modem files zip (100mb only)
https://drive.google.com/file/d/1VIYwHHcz2lIqPcsWHIv-mmzKnAPlkWp7/view?usp=drivesdk
You will see error in twrp when flashing this, ignore it. You don't have to flash again the Whole Rom You can do this even After Installing/Using the Rom if you are Facing the Issue.
If you are Flashing the Whole Rom again Then 1st Flash ROm, THis zip,Gapps,etc...
I don't know the username of dev who gave me this,So I can't Tag him
All Credit goes to him.
Hello everyone!
So I'm having this weird issue where the camera/flashlight all of a sudden stopped working one day (didn't make any device changes) but it had happened occasionally and all I needed to do was clear dalvik/cache and it would be fine regardless of Lineage version. Now that solution no longer works. I just flashed both stock Nougat and Oreo firmwares to see if it was a hardware issue and the camera works perfectly fine. It's just on Lineage that it all of a sudden won't work (tried clean installs of 14, 15.1, 16 and now 17) and none of them have a working camera so I wanted to get you guys' input on what it could be.
Basically tl;dr
Lineage = camera/flashlight not working
Stock nougat/oreo = camera works perfectly
iTzFeRReTTi said:
Hello everyone!
So I'm having this weird issue where the camera/flashlight all of a sudden stopped working one day (didn't make any device changes) but it had happened occasionally and all I needed to do was clear dalvik/cache and it would be fine regardless of Lineage version. Now that solution no longer works. I just flashed both stock Nougat and Oreo firmwares to see if it was a hardware issue and the camera works perfectly fine. It's just on Lineage that it all of a sudden won't work (tried clean installs of 14, 15.1, 16 and now 17) and none of them have a working camera so I wanted to get you guys' input on what it could be.
Basically tl;dr
Lineage = camera/flashlight not working
Stock nougat/oreo = camera works perfectly
Click to expand...
Click to collapse
Ask in the specific Los thread, theirs numerous camera issue discussions
Sent from my LG-H910 using XDA Labs