yashsingh1/xdaforums huggingface dataset:
[LeEco Le Max 2 Guides, News, & Discussion] oneNight1:
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.

Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?

We do not have the specification of the QDCM xml file that the tool generates.

It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.

I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.

Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.

I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).

I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.

That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?

Thanks
[LeEco Le Max 2 Guides, News, & Discussion] ThE_MarD:
Heyyo, it's definitely a formatting error. XML standard has open and close brackets.

For example, the OnePlus 5T

https://github.com/TheMuppets/propr...b_data_samsung_s6e3fc1_cmd_mode_dsi_panel.xml

Or the Xiaomi Mi5 (Gemini)

https://github.com/TheMuppets/propr...calib_data_sharp_fhd_cmd_incell_dsi_panel.xml

As for viewing the files on your phone? Yes you would need root and a root file explorer.

Magisk, SuperSU, KingRoot or such all work for root but some versions of EUI ROM have issues.

For root enabled file browser? Amaze works... Amazing. Just get it from the Play store and then in settings enable root explorer.

For uninstalling root please Google the uninstall method to whichever root method you use as they are all different.
[LeEco Le Max 2 Guides, News, & Discussion] oneNight1:
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)

How they had formatted their tags was valid xml.

<Calib_Data />

is just an element with nothing in it, the same thing as:

<Calib_Data> </Calib_Data>

However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it :)

Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.

It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.

Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://xdaforums.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).

How can i find out which of the 3 display types my device is using? (Preferrably via adb).

I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S

It's also weird how those xml files have been hand tampered with!

Thanks!
[LeEco Le Max 2 Guides, News, & Discussion] sergio151179:
Write this in the terminal.

cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info | grep panel_name
[LeEco Le Max 2 Guides, News, & Discussion] oneNight1:
Thanks Sergio, so my device is running:

le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt

Hmm it seems that SmallEUI ( https://xdaforums.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.

I am pretty sure that I have root properly, supersu seems to be installed.

For some reason though, if i try and get ADB to get root, it says:

adbd cannot run as root in production builds

I don't have a folder named configs, only one called "config" and it is completely empty.

Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?

I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?

Thanks
[LeEco Le Max 2 Guides, News, & Discussion] giaur:
You should notice this does not work, garbage screen is there even with this fix applied. I have it all the time on latest Lineage 15.1.
[LeEco Le Max 2 Guides, News, & Discussion] oneNight1:
Okay I checked in

system/etc

and I do have the files. They are formatted as

<Calib_Data />

too.

Why does your github page say that they should be in

config/qcdm

???

Anyway, I flashed your zip to see if it would make a difference but it didn't help with the black crush sadly.

Although maybe modifying the calibration data would - but of course we would need to understand the format.

I checked my TWRP backup image (you can just browse them with 7zip) and they have the same empty tag too.
[LeEco Le Max 2 Guides, News, & Discussion] oneNight1:
I can confirm that after installing your edited xml files, the colour mode settings no longer work on my device.

So it looks like in the case of our devices it was meant to be an empty tag after all. Strange if it's different to other devices. Mind you, considering the contents of the le x2 sharp and truly xml files are identical, i would be surprised if they did any proper calibration anyway.

Interestingly, the sharp file without the le x2 suffix is different - is that one ever used by any device? I'm guessing maybe it was just a sample one that sharp supplied to le eco for their screen hardware? Problem is, I have the Truly screen so that doesn't really help.

Either way, in their original form, it seems like these files are used. So if we could workout the binary calibration format then colour calibration for all phones supporting qdcm could be possible..

That's a project far bigger than just this device though.
[Miscellaneous Android Development] kushal7111:
Not working properly pls fix it
[8525, TyTN, MDA Vario II, JasJam General] toucam:
I dropped my phone yesterday and now there's no sound at all. The phone feels solid, it seems nothing has fallen off or disconnected inside. I thought it was a software problem and did a hard reset but still no sound. Has anyone any ideas? Is there a guide to dismantle Hermes somewhere that I can have a look at?

Cheers.
[8525, TyTN, MDA Vario II, JasJam General] XtreMe_G:
there's a link in the wiki, and i swear i've seen a youtube video
[8525, TyTN, MDA Vario II, JasJam General] toucam:
Cheers,

Googled and found it from a Russian website.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
You only needed to search here. All the info you need is on this site. There is detailed instruction concerning both front and rear speakers. Of course you have not said which speaker is concerned. Both can be dislodged in a fall and both are easily fixed if you have dismantling skills. The rear speaker is a piece of cake as it only requires the the push in connector to be re-seated. The front speaker requires a major dismantle and requires the spring contacts to be pulled out a little to restore good contact with the M/board.

I will return with more links for you.

Mike
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Speaker Front/Rear Pics/Links/Guidance etc:

Front Speaker(Ear piece) These spring contacts can bend if the phone gets a knock and lose contact with the board.

Read these threads:

http://xdaforums.com/showthread.php?t=288728&highlight=speaker

http://xdaforums.com/showthread.php?t=283490

Rear Speaker

Note (Rear Speaker) the white push in connector with red/black wires. (This can become loose)

Read this thread:

http://xdaforums.com/showthread.php?t=317870

Mike
[8525, TyTN, MDA Vario II, JasJam General] toucam:
Thank you so much, it worked beautifully, it was the rear speaker, the connector was loose.
[8525, TyTN, MDA Vario II, JasJam General] duracool:
worked for me

i had the same problem with my 8525. after i dropped it i just removed the back and re-seated the rear speaker wire and it worked fine. thanks for the post.
[8525, TyTN, MDA Vario II, JasJam General] Raptor567:
amazing...

I was totally freaked out when my sound stopped after i dropped my phone...

Luckily i was able to pick up a torx set for less than $6 and pop the sucker open, didn't even have to remove the back faceplate all the way to snap the sound cable back in...

Couldn't of done it without this thread....
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Happy Days!:)
​

Mike​
[Amazfit] epareja:
Hello, I have an Amazfit pace original with 1.3.6d firmware.

When I get out running with my earphones on and listening to onboard music, I don't hear notifications each kilometer. It just vibrates and shows the time and pace in the screen.

The Lap alert in the configuration is on.

What should I do?
[Amazfit] s2k7:
+1 for official Pacefictor 1.2.49k.
[Amazfit] le_lutin:
Pacificator 1.2.48 is the most recent version that the voice prompt is working for me.
[Amazfit] epareja:
Thank you for your answer.. Should I brick the watch with this firmware (i suppose yes) and if I do that can I update the watch later with stock versions?

Thank you
[Amazfit] Sungem:
Hi, Did you try the Firmware? Does it work on your A. Stratos?

I am still looking for the Voice alert feature for my watch. :(
[Amazfit] lfom:
StratosFied ROM lists English voices as working, and it is for Stratos.

For Pace only, there is AmazeROM.
[Amazfit] Sungem:
Thank you. I have tried to PUSH the folder and files downloaded, but failed as I supposed that it was still not correct way. So complicated! :)
[Amazfit] lfom:
You can try this one-click installation for StratosFied 2.0.28.0 by [MENTION=9246567]ingraynieris[/MENTION] (I haven't tried it tho, as I do not have Stratos):

https://mega.nz/#!nxVDQKgJ!5rmUrPOCBrvpZjGynmrgK7YaI-pdb28-OURbTFNXDsA

Or try StratOS, it looks much easier to install, but I am not sure if it has English voice alerts:

https://nicolasagliano.com/stratos-3-1/
[Xperia Play Q&A, Help & Troubleshooting] pWEN:
I have an Xperia Play that I got off eBay (I know, I know, personal project - I do have another working one). Reported issue was that it wouldn't boot, but after messing with it, I found that it would 1/10 times if I pull the battery for a few seconds before trying. I was even able to flash a stock firmware again. However, the majority of the time, it won't boot into OS, fastboot, OR flash mode.

Here's why: QHSUSB_DLOAD

From my research, this basically means the bootloader is corrupt or somehow otherwise malfunctioning. When connected to a computer, it resolves to "Qualcomm HS-USB QDLoader 9008 (COM3)" or whatever COM port it lands on, and it does this in fastboot and flash mode. Except for those rare instances where it acts like a normal phone.

I've spent most of the past couple of days digging around in forums, Google, and the Wayback Machine, trying to find a solution. Unfortunately, beyond trying a different computer and reinstalling drivers (both of which I have), the only solutions given are to use Omnius or s1tool/s2tool. They both seem to require payment for unlocking phones, which I don't need, but as far as I can tell should work fine for repairing the s1 boot, which I think is what I need to do. I've been following different guides that all say to remove the battery, connect the test points, and plug in the USB, but I can't get Omnius or the s-tools to work.

Is there any hope for this device? Can anyone who has gone through this before offer some suggestions? Alternatively, is there maybe a way I can just deal with the problem while still being able to use the phone without needing to pull the battery a bunch of times? The Xperia Play is still a great portable gaming system, so I'm hoping we'll be able to figure something out, as I know many other people are starting to acquire these from eBay and try to get them working, and may also run into this issue.
[Xperia Play Q&A, Help & Troubleshooting] Logos Ascetic:
#metoo

I'm also having the same issue.

found this thread [Q] [Hardbricked]Xperia Play lifeless

And this one [How-to] Repair Damaged Bootloader + Trim Area [Red Led][Unknown Device]

And finally, I found this thread in the Xperia SP forum [Guide]Zeus Flash Or qhsusb_dload Solved!!!!!

And also this thread S1 boot download driver.

Some of these fixes and threads are old/outdated, so I dont know what will work Ive already started to use some of the tips last night. I have found out that my phone does get detected as "Qualcomm HS-USB QDloader 9008" but that's as far as Ive gotten. Please read the threads and tell me what you find out, or try that works
[Xperia Play Q&A, Help & Troubleshooting] pWEN:
I've already been through those threads, and several more like them. The immediate answer is to contact Alejandrissimo, but they've been MIA for years now. I shot them an email the other day, but I don't expect to hear back.

Things I've tried:

Xperia Companion (PC Companion) - doesn't recognize device

SEUS (Sony Ericsson Updater Service) - discontinued, can't connect to servers

S1tool testpoint method - doesn't recognize that a device is connected

Omnius - doesn't recognize that a device is connected

Flashing stock the one time I could get it to boot into flashmode

It looks like this method stands a good chance of working, but it requires an "APPSW .sin_file_set" file, which I haven't been able to acquire for the Xperia Play. From Googling around, it seems that's the blob file that gets downloaded when you get an OTA update or when using XperiFirm (which no longer gives Xperia Play as an option), but all I can find are recompiled *.ftf files. Those files do contain a bunch of *.sin files, but comparing the contents to what you find in a *.sin_file_set file, is too different; the latter has a different folder structure and a bunch of XML files that provide information to the phone. I'm not sure exactly just how necessary that structure is and I couldn't find a guide on recreating a *.sin_file_set file, just how to decrypt one to convert to FTF.

If you click that link to the tutorial for that process, you can download a *.sin_file_set for a different model of phone to see what it should look like.

Of course now I just stumbled on a guide to convert FTF back... I will have to try that.

EDIT: Okay, I grabbed the s1tool from that link and disabled my antivirus before using it. Did the testpoint procedure as described, and got this error:

That might be because the bootloader is still locked. If I can get it to let me into fastboot, I may be able to change that.

EDIT 2: Got it into fastboot, verified the bootloader is locked. Ran the unlock command, but it failed. Tried doing it through s1boot and got the same error as before. Guessing there isn't anything else I can do at this point.

EDIT 3: Forgot to mention the process I tried before was with an FTF, since I discovered S1tool will use those after all (I used the version from that website I linked to). I still need to recompile a sin_file_set version and try that. In the meantime, I did actually receive a response back from Alejandrissimo, so we'll see where that goes and I'll report back.
[Tasker Tips & Tricks] clinto69:
Guys,

Can anyone please help me. I want to use Tasker to do the following.

1. On connection to WiFi

2. Open Google Play Services

3. Force Stop

4. Return to homescreen

Its a long story about why I want to do this so wont go into it. But there is a reason.

Can anyone please help?

Thanks
[Tasker Tips & Tricks] #Henkate:
EDIT:

Sorry, haven't read the reason part >.<
[Tasker Tips & Tricks] clinto69:
I absolutely want it to restart itself! Like I say there is a reason I want/need to do this. Currently I am manually doing this every time the head unit connects to the wifi hotspot. I just want to automate it.

Thank you
[Tasker Tips & Tricks] ktmom:
Use the AutoInput plugin or use a run shell with the command "input tap 270 230". The 270 230 are the x,y coordinates of the tap location.

You'll just have to "tap" your way to what you want.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Essential Phone Guides, News, & Discussion] maverickmarc:
Reverting to Nougat form the 8.1 beta using Linux mint, full step by step available somewhere? About to take a hammer to this phone. ADB and fastboot just won't find the phone, I've tried over and over again.... Anyone?
[Essential Phone Guides, News, & Discussion] bjs339:
Have you seen this thread?:

https://xdaforums.com/essential-phone/help/adb-devices-phone-linux-t3733504

Also this post:

https://xdaforums.com/essential-phone/help/adb-devices-phone-linux-t3733504

You need to give your user account permissions on the device. I did it by creating a group in Linux and granting permissions to that group, although I think you can grant them directly to the user.
[Essential Phone Guides, News, & Discussion] avd:
Sudo fastboot ....
[Essential Phone Guides, News, & Discussion] Bad_MOFO_33:
update your android rules in /etc/udev/rules.d

# Clone this repository

git clone https://github.com/M0Rf30/android-udev-rules.git

cd android-udev-rules

# Copy rules file

sudo cp -v 51-android.rules /etc/udev/rules.d/51-android.rules

# OR create a sym-link to the rules file - choose this option if you'd like to update your udev rules using git.

sudo ln -sf 51-android.rules /etc/udev/rules.d/51-android.rules

# Change file permissions

sudo chmod a+r /etc/udev/rules.d/51-android.rules

# Restart UDEV

sudo udevadm control --reload-rules

sudo service udev restart

# Restart the ADB server

adb kill-server

# Replug your Android device and verify that USB debugging is enabled in developer options

adb devices

# You should now see your device
[Essential Phone Guides, News, & Discussion] UN5EEN:
Pulling the following error in terminal.

chmod: cannot access '/etc/udev/rules.d/51-android.rules': Too many levels of symbolic links
[Essential Phone Guides, News, & Discussion] mobileman88:
note the "OR"

# Copy rules file

sudo cp -v 51-android.rules /etc/udev/rules.d/51-android.rules

# OR create a sym-link to the rules file - choose this option if you'd like to update your udev rules using git.

sudo ln -sf 51-android.rules /etc/udev/rules.d/51-android.rules

Personally I'd do the sudo cp instead of the sudo ln

It's up to you. did not run the commands but symlinking a file back to itself will respond with this.
[Essential Phone Guides, News, & Discussion] Bad_MOFO_33:
to make it a little easier

$ sudo curl --create-dirs -L -o /etc/udev/rules.d/51-android.rules -O -L https://github.com/M0Rf30/android-udev-rules

$ sudo chmod a+r /etc/udev/rules.d/51-android.rules

$ sudo service udev restart
[Galaxy S6 Q&A, Help & Troubleshooting] LYudhistira:
Hello guys.. i want to ask, is Device Maintenance has screen resolution changer right now ?

Cause i change my resolution to 720p HD.

But when i want to change it back to FHD or QHD there is no display on setting..

Can somebody help me with this bug ?

Thanks

I'm using SM-G920F Stock ROM

Device Maintenance version 1.5.10.21
[Barnes & Noble Nook Tablet] fddm:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
[Barnes & Noble Nook Tablet] nmyshkin:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
[Barnes & Noble Nook Tablet] fddm:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
[Barnes & Noble Nook Tablet] secretwolf98:
Does this work on 16GB only or does this include 8GB version?
[Barnes & Noble Nook Tablet] fddm:
It should work on both, they run the same ROMs, only requirement is Lollipop+.

Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
[Barnes & Noble Nook Tablet] nmyshkin:
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same :(

BTW, there were no error messages I detected as the Magisk zip installed.
[Barnes & Noble Nook Tablet] fddm:
If you can, these three things might help to catch the problem:

TWRP log from after flashing Magisk(advanced->copy log)

A TWRP backup of your boot partition after flashing Magisk

A link to the ROM you tested
[Barnes & Noble Nook Tablet] nmyshkin:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip

Let me know if there's anything else I can do.
[Barnes & Noble Nook Tablet] fddm:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
[Barnes & Noble Nook Tablet] nmyshkin:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
[Barnes & Noble Nook Tablet] fddm:
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!

Edit: problem found, fix incoming
[Barnes & Noble Nook Tablet] fddm:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!