yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Questions & Answers] petiolarissean:
Try service disabler its free

---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------

Have you tried customs roms and is it still doing it?
[Google Pixel XL Questions & Answers] thetrangdam:
Yes I did and it persists.:crying:
[Google Pixel XL Questions & Answers] nabbed:
You flash stock firmware, roms etc and reset, and problem persists? Have you considered that there's no feasible way to remedy this? As in, your phone has defective hardware?

Otherwise, it would have to be a phone hacked by CIA with custom hardware that is impervious to resets and firmware flashes.

Think about it...
[Google Pixel XL Questions & Answers] petiolarissean:
Contact google and there pretty easy going and will go out of there way replace phone.Ive went threw 5 pixel and every time they have jump threw hoops to make me happy.Phone returned 3-5 days every time.
[Google Pixel XL Questions & Answers] spezi77:
Maybe it's malware!?

Read this: https://www.google.de/amp/s/amp.reddit.com/r/Moto_Z/comments/5ox4ab/constant_wakelock/
[Google Pixel XL Questions & Answers] thetrangdam:
That could probably right.

At first, my device kept showing a persistent notification "USB Supplying Power to attached device",

And I could not charge my device unless I reboot (then it will appear again later).

I googled & figured some people had the same problem and got it solved by cleaning the charging port

on the phone so I did the same.

It stills show up time after time, but now I can choose to "charge this device" from the popup & charge fine.

But the kernel wakelock, which I believe belongs to usb otg or something like that, still keeps my device awake 100% of the time, and drain the battery.

Appreciate your help.

Unfortunately, I live in a country where Google isn't available, and purchased this device from private vendor,

so there's no way I can RMA this now.

Maybe not.

It happens no matter what rom, kernel I'm on.

Since I had the persistent "USB Supplying Power to attached device" time after time,

it's likely that wakelock thinks I'm plugging something into the usb port all the time,

and keeps my devices awake.

I've cleaned the port with tooth pick, some alcohol & air duster but the wakelock hasn't gone away.
[Google Pixel XL Questions & Answers] liam_davenport:
Caused by USB I've seen before in BBS thread, I think it's due to a poor USB port on the device contact Google to see your options
[Google Pixel XL Questions & Answers] :
I agree [MENTION=5823687]liam_davenport[/MENTION]. I did a little digging through some xda threads and people claimed they had that wakelock if they plugged their phone in wrong, do to the USB port being sloppy. There is also something in our device tree called "tcpm logging" that is related to that number, doing a little research now to see what it is/does.
[Google Pixel XL Questions & Answers] petiolarissean:
let me talk to my cousin,he works at google.Let me throw problem at him
[Google Pixel XL Questions & Answers] fiverings:
I've only heard of this problem with people running Android P preview2. It seems using the finger unlock on back of phone, some people tap it when the screen begings to dim and taping fingerprint brightens screen. But what I was thinking, that doing that even without preview2 might cause similar effect.

So you could try disabling that feature might help. It seems that their connected somehow.
[Google Pixel XL Questions & Answers] nabbed:
Didn't he say Android 8.1, stock? He flashed it many times?
[Moto Z2 Force  Questions & Answers] platinumlayer:
Hi, i got a Moto Z2 Force running Android 7.1.1, but, after a OTA, everytime i open the camera, a message box saying "the camera stoped work" appears. I've tried to come back to Nougat, but through fastboot isn't possible to downgrade. Anyone can help me? I'm from Brazil, sorry for my bad english.
[Honor 9  Themes, Apps, and Mods] ACOJO5920:
Or do you think it'll be possible soon?
[Honor 9  Themes, Apps, and Mods] fiskcz:
Why?

The camera application of Honor 10 is very similar to Honor 9. What if it has the same function? It depends on Camera API2 support.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Gradu2012:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: [url]http://xda.tv/post76580944[/URL]
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Gradu2012:
When accessing the link http://xda.tv/post76580944, i am redirected to this thread.
[LG V30 Questions & Answers] CHH2:
Looking to see if anyone else has had BT issues in the past week-ish? I'll get some cutting out of the audio. It seems to happen no matter which app I'm streaming from or what device I'm streaming to. Also, I'm not sure if it is related but I've noticed some weirdness with my Fitbit Syncing too since roughly about the same time. (Some of the data is making it across to my phone because another app gives me credit for the steps taken but none of the info shows up in the Fitbit app and I can't get the time on the tracker to update. May 12th seems to be the last official sync.)

I responded to a post in the Tmo Oreo thread that I'm not really sure that it is related to the Oreo update. I did the update right when the OTA came out then went on a road trip. It didn't happen the first couple of days. I initially thought it was thermal cut out since I was driving a lot at the time and it was pretty hot out. But it still happened when I was driving at night when it was cooler. Then I was thinking it might be my car's BT but it's also happening as I sit here at my desk connected to a pair of BT headphones that were also reliable before my trip.

So it's looking like some sort of update did it but I'm at a loss as to which one so I thought I'd see if anyone else was having the same issues. Although, after a little looking around, I think the Fitbit stuff may just be Fitbit's issue.
[LG V30 Questions & Answers] R800x_user:
This was one of the reasons the Oreo update was halted.
[LG V30 Questions & Answers] CHH2:
As I said, this doesn't seem to be Oreo related. Just as oddly as it started, it has stopped. So it doesn't seem to be related to any visible front end update, OS or app. Looks like it is somewhere in a background update. (And I don't have any my apps set to auto update.)
[LG V30 Questions & Answers] Wolfsbane58:
FWIW, the only communication update that I can recollect at this point in time that is causing a ton of problems for mobile device users is the Bluetooth 5 that came out with Oreo 8.0. It is a bonifide mess. The version that came out with Oreo 8.1 was supposed to fix these issues, but I don't know that this actually happened. For the most part, manufacturer updates that are released for devices, such as BT Headphones, will try to incorporate a workaround or fixaround for the deficiencies in the underlying software, such as Bluetooth. But there is only so much that a manufacturer can do to circumvent the fundamental issues in an application such as Bluetooth. After all the promises and hype, the basic consensus is that Bluetooth 5 practical improvements are basically in range and some bandwidth. But it is also pretty well accepted, by now, that Bluetooth 5 is largely a mess right now, and not only for headphones, but pretty much about everything that you try to pair your phone to.
[Zenfone 2 Laser Q&A, Help & Troubleshooting] oldyjoe:
Hi There.

Maybe a newbie problèm but in order to unlock bootloader and Root my device, can't install the twrp.img file on cmd i can reboot on fastboot mode but fastboot boot twrp-......IMG still getting me no such a file...

I've checked and reinstalled drivers by autorised unsigned drivers,when i look on my Android adb device all seems good..

Any ideas?
[Zenfone 2 Laser Q&A, Help & Troubleshooting] Pratik Dalui:
Fastboot boot twrp.img enter see your phone load in to twrp mode .. then restart using twrp . After boot . Agin go fastboot mode and type fastboot flash recovery twrp .img (u can drag this file also if u want or manualy typing as u wish) . Enter and wait few sec. Its finish. Then type fastboot reboot (remembar before hiting entar tap volume down switch then hit entar). Now u feel viberet and see twrp logo . Then go wipe advanced wipe tik the ASDF swipe to conform. And then restart ur phone.... congarts u have succesfully install twrp ... enjoy .:D
[Zenfone 2 Laser Q&A, Help & Troubleshooting] oldyjoe:
THX it s more clear i ll try and let u know;)
[Zenfone 2 Laser Q&A, Help & Troubleshooting] Laltu_k:
First of all download the app TWRP from play store . Then download the latest version of twrp from there .

Then you have to unlock your bootloader by using the app unlock device tool . After unlocking the bootloader go to developer option and enable USB debugging . After that connect your laptop or PC to your mobile . An option will come on your screen to allow debugging to the device . Allow it permanently . Then open adb (I hope you have installed it otherwise download and install it Just google it download adb ) After installing open C drive and then go to adb . Then open command prompt there by pressing cntrl shift and right click . there will be an option to open command prompt there . After opening just type adb devices there in the command prompt it will show your device serial no. Then move the twrp file from your mobile to PC and to adb folder . Then rename it to recovery .

Then switch off your mobile and open fastboot mode by pressing power button and volume up button . then go to the command prompt you have opened before . type there fastboot devices . it will show your device serial no. Then type Fastboot flash recovery recovery. Img then wait for some time after the processing gets over in there . then switch off the mobile by removing battery and switch on to recovery mode by pressing power button and volume down button . Congrats twrp has been installed successfully in your device . You will see twrp window. If this works then thumbs up
[Honor 6X Guides, News, & Discussion] Siddk:
Who have unlocked their bootloader and want to update to latest version but dont want to lock bootloader by flashing full rom use following guide

*TWRP Required*

1.Download FullOTA-MF:good:) or OTA-MF(not working:confused:) (Use Firmware Finder).

2.Put all 3 files you want to flash in a separate folder on phone or sdcard

update.zip

rename other 2 file to

update_full_BLN-L22_channel_in.zip ---------> update_all_hw.zip

update_data_full_public.zip ---------> update_data_public.zip

3.Put HuRUpdater zip in same folder. thanks to [MENTION=3975929]zxz0O0[/MENTION]

download HuRUpdater from[url]https://xdaforums.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279[/URL]

4.reboot to twrp and install HuRupdater.zip

5.follow instructions on screen

Note:your bootloader remain unlocked only stock recovery get restore:cool:

keep all 4 files in same folder

I have successfully update from BLN-L22C675 B360 To B364 without bootloader relocking

OTA package test is pending please update if it works

B364 Files

1.[url]http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v137653/f1/full/update.zip[/URL]

2.[url]http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v137653/f1/full/BLN-L22_channel_in/update_full_BLN-L22_channel_in.zip[/URL]

3.[url]http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v137653/f1/full/public/update_data_full_public.zip[/URL]
[Honor 6X Guides, News, & Discussion] Jax:
Thanks man,we need guide like this
[Honor 6X Guides, News, & Discussion] Jugabrat:
Thanks bro...very useful tool..

Tell me one thing, can I use it downgrade ?

Like In honor 6x,can I install b360 if I'm on b365
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ghpranav:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/

Finally the wait is over. Project Treble is finally here for Tissot, but unofficial obviously :P . Before I proceed any further, I would like to quote [MENTION=7675024]theandroidguy[/MENTION]'s explanation about Project Treble.

​

So now that you know what's Project Treble, let's try to understand how we achieved Treble in our beloved Tissot.

Project Treble for Tissot?

Most of the unofficial Treble support for other devices was due to the presence of any unused extra partition, like cust partition in many Xiaomi devices, which developers used it to mount that unused partition as vendor partition. But Tissot doesn't have any such unused extra partition. Luckily [MENTION=1844875]CosmicDan[/MENTION] came up with a perfect guide to repartition our huge system_a & system_b to vendor_a & vendor_b. Which allows us to enjoy Project Treble & seemless updates (A/B partition) at the same time. So all we had to do was move all the device specific stuff to vendor partition, & clean the system partition. Hence making it possible to use GSIs (Generic System Images). Benefit :) .

(Fun Fact: Tissot is the first-ever A/B device to get unofficial Treble support)

How to get Treble on my Tissot?

• Repartition your Tissot device to create vendor_a & vendor_b partitions, using CosmicDan's guide.

• Reboot to custom TWRP provided by CosmicDan, & wipe system & vendor on both slots.

• Check what slot you are in. I will assume A for the sake of these instructions.

• Install RR-Treble build & custom TWRP installer zip from TWRP. (Prior permission has been taken from [MENTION=7210959]mountaser halak[/MENTION] to upload an experimental build of RR)

• Reboot recovery

• Make sure the active slot is B (if you started in A). If not, you need to reboot to fastboot and do

fastboot —set-active=b

then reboot to recovery again.

• After making sure active slot is B (if you started in A), wipe data. Install Magisk & GApps (optional).

• Reboot to phone & enjoy a Trebelized ROM ;) .

• Now you can flash any GSI from fastboot.

Links Section

•Repartition guide & TWRP

•RR Treble Build - 20190522

•Treble devices development

•Device Tree

•Kernel Source

•Proprietary Vendor

Credits:

• [MENTION=5393309]ghpranav[/MENTION]

• [MENTION=1844875]CosmicDan[/MENTION]

• [MENTION=1915408]phhusson[/MENTION]

• [MENTION=5120185]flex1911[/MENTION]

• #TeamOreo

• Also thanks to all my haters for always having time to point out my mistakes immediately, & helping me to learn more :D

Please refer to 2nd & 3rd post for FAQ, Vendor images & more.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ghpranav:
Reserved

F.A.Q:

(Readme first!)

1. What's the use main use of Project Treble for an advanced user?

A: GSIs. One system image for all Treble enabled devices.

2. Will I be able to use already existing custom ROMs after repartitioning?

A: Depends. If you shrink your system partition to create vendor partition, then nope, you'll not be able to flash the existing custom ROMs anymore. But if you shrink your data partition (will erase all data, including internal storage), then you'll be able to use the existing ROMs, & also the trebelized RR.

3. Can I use custom kernels?

A: Nope. Unless the maintainer releases a Treble compatible version of their custom kernel, you won't be able to use any custom kernels as they don't mount our newly created vendor partition properly.

4. Can I flash XYZ GSI?

A: Yes, you can flash any A/B ARM64 GSI.

5. What's "Unable to mount '/vendor' (Invalid argument)" error in TWRP?

A: It means that you haven't repartitioned your device to Treble compatibility yet. Please repartition first, before proceeding.

6. Bootloop! Plox haalp!!!

A: Get logs. Or it never happened.

Vendor Images:

I'll try to maintain up-to-date vendor images here.

• Vendor - 20180521

• Vendor - 20180522

• Vendor - 20180523

• Vendor - 20180614

• Vendor - 20180705

• Vendor - 20190522

Treble patched boot images:

Based on Flex's Kernel. Source code link is given in 1st post.

• Boot Image - 20180522

• Boot Image - 20180523

• Boot Image - 20180614

• Boot Image - 20180705

• Boot Image - 20190522
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ghpranav:
Reserved #2

What's working:

• Everything

• Selinux is enforcing

What's broken:

• You tell me ;)

Changelog:

[LIST]
[*]2019-05-22:
[LIST]
[*] Fixed OEM bootloop issue
[*] Fixed internal hardware error at first boot
[*] Fixed Dirac giving problems
[*] Enabled KCAL control
[/LIST]

[*]2019-05-21:
[LIST]
[*] First public release of 4.9 Pie vendor
[*] Updated to latest Flex's trees & kernel
[*] Removed jank in some use cases
[*] Updated GPS blobs & config
[*] Optimised Auto Brightness
[*] Cleaner Dirac implementation into vendor
[*] Add audioshpere effect engine
[*] Improved performance
[*] Reduced boot time
[*] Added Boeffla wakelock blocker driver
[*] Added KCAL calibration support
[*] Added Sound Control
[*] Lot of under the hood kernel changes for better performance & battery life
[/LIST]
[*]2018-07-05:
[LIST]
[*] Fixed signal fluctuations. Feel Stock like signal bar stability. (April modem recommended)
[*] Fixed MIUI offline charging animation in GSIs
[*] Fixed Battery Drain
[*] Slightly faster & smoother boot animation
[*] Various fixes for better stability
[*] Merged changes from latest Void Kernel
[*] Kernel upstream to 3.18.114
[*] Lineage & RR upstream
[/LIST]
[*]2018-06-14:
[LIST]
[*] Resurrection Remix upstream to v6.1.0
[*] Added Lineage Trust
[*] Selinux enforcing
[*] Fixed USB Tethering
[*] Fixed random crash of Bluetooth MAC address on reboot
[*] Switch to less hacky way of getting camera to work on GSIs
[*] Reduced screen retention problem
[*] Reduced hissing sound on earphones (needs more feedback)
[*] Added ExFAT support & enabled NTFS
[*] Probable fix for FM on GSIs
[*] Added Joystick support
[*] Update GCam
[*] Merged changes from latest Void kernel
[*] Kernel upstream to 3.18.113
[/LIST]
[*]2018-05-23:
[LIST]
[*] Fixed camera
[*] Fixed Bluetooth MAC address issue
[*] Kernel upstreamed to 3.18.109
[/LIST]
[*]2018-05-22:
[LIST]
[*] Fixed booting issues
[*] Fixed WiFi MAC address issue
[/LIST]
[*]2018-05-21:
[LIST]
[*] Initial Release
[/LIST]
[/LIST]
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] abhinavgupta371:
Awesome +1
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] theandroidguy:
[MENTION=5393309]ghpranav[/MENTION] a big congratulations to you and to the entire team behind this huge success.......thumbs up
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] mountaser halak:
nice work buddy !

#TeamOreo_did_it _first
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] euricoalex:
Nice work i will test weekend

Enviado de meu Mi A1 usando o Tapatalk
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] AndroZeek:
great work. you are actively working for tissot
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] moonsmart00712345:
Congratulations on such a great development.

Waiting for full-fledged treble ROM development.;)
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] KeroNyu:
Great work!. Is it possible to flash a Android P GSI? Would love to test it on my phone. :)
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] theandroidguy:
Not released yet
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ghpranav:
Android P GSI is not yet out. Once it comes out, yeah sure, you can go ahead & test it.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Userbaban:
how about converting your RR into a official Treble supported rom ?!! :p:p
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] murtaza1326:
just curious isnt moded magisk (treble supported) is needed for treble?

i asked bcz my secondary device needed it.

thanks
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Ahmed Al-Sayed:
It is still an experimental build ..... If everything goes well with this build, he might release the next official rr builds with treble support
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] akshaygalaxystarmod:
Congratulations To you all

Cheers
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Maximaro:
So to #2 then i need to wait for Treblized Roms that the original way used of smaller system Partition.

So far i need to wait for out coming Rom´s.

One Qestion: Are the Rom builds specific for one Device or for all device´s that have Trebel?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] jack404:
u seems didnt read the whole OP carefully :)

and yes GSI is one for all treble device
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] KeroNyu:
Thanks for answering.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] emin93:
Yeah great work! :D :good:
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] CosmicDan:
Wait.

I thought you meant non-Treble RR.

No you can not "sidegrade" from a completely different ROM! Never could, never will.

You are changing ROM's - you will need to factory reset like always.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] joeyhuab:
So...

non-treble RR to Treble RR = Dirty Flash

Non-treble LOS to Treble LOS = Dirty Flash

Non-treble PE to Treble GSI = Clean flash.

Got it. Thanks!
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] CosmicDan:
Generally, yes. Same AOSP fork = dirty flash possible. Treble change doesn't really matter, that's all abstracted away. Sometimes you will need to clean flash for an update though if there was a major change, but it seems rare these days.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Blackheart151:
Yes
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] deveshgupta69:
Should I update Vendor Only for DotOS gsi? or The boot Img also? and in what order
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Blackheart151:
Both vendor and boot IMG. Don't forget to flash twrp after boot IMG, any order is fine..
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Ayush061:
Can i use any treble rom in mi a1....... Other than RR?

Like LOS treble rom? Directly flashing it....... After vendor any boot img provided by uh?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] CosmicDan:
No you cannot use any boot IMG. That's the kernel.

You can use other GSI's.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Ayush061:
Means...... I use ur boot.img nd vendor for mia1 and any gsi? A/B one arm-64 is this correct?

Also if i shrink my data partition for vendor can i flash any custom rom whether its non treble or treble rom without any converting partition to stock one?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] SomratMJX:
Not sure about the first question!

But regarding second one, YES! You can use any ROM (even stock with OTA) regardless treble/non-treble if you treblize by shrinking data!
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] N1ck474:
OTAs Will be Broken with Treble partitions.

Tested yesterday, installation problem.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] dback31:
Just quickly tested it yesterday before going to bed (so maybe I missed something).

In the latest treble RR (from the OP) cellular network and voLTE worked fine, but in every other GSI I'm connected with my network operator but I don't have mobile data and I can't see if I'm connected to 2g, 3g or 4g. VoLTE obv also doesn't work.

All GSI's were flashed along with the boot.img and vendor.img from the 23rd.

I'm back to stock nougat for now since I don't know how I can take a log for this particular issue.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] SomratMJX:
Nope! I was the first person ever to test it! And OTA worked!

You just need to clean flash and lock Stock using fastboot!
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] N1ck474:
I've done It, full reinstall of stock firmware, can't update to May patch, repartitioned to stock (removed vendor_a and _b), reinstalled again and May update just worked fine.

With Treble partitions you will receive an installation problem.

Mi A1 32GB userdata installation.