yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Questions & Answers] bkeaver:
Really and truly the size isn't that much different to be concerned with. As for battery I was running qhd at 120 and was still getting around 4 to 5 hours on screen time which imo isn't bad considering the resolution and refresh rate. If you went down to fhd at 120Hz I'd get like 5 to 6 and if I ran it at 60Hz I'd get 6+ depending on which resolution.
[OnePlus 8 Questions & Answers] marvi0:
I used both, its safe for me to say in terms of performance, battery life and screen refresh, I didn't notice any difference. What did it for me though is the size, the 8 regular is definitely more comfortable to hold and I have big hands. Also the £200 difference couldn't be justified!
[OnePlus 8 Questions & Answers] Nickinfinity:
Did u get to test the camera? Also what do you think about the display quality of both the devices in real life.
[OnePlus 8 Questions & Answers] Droid4200:
Is the 8 pro the only with wireless charging? I like that feature because its less wear and tear on the USB plug, every wireless charging phone I had always kept a tighter USB connection , berter when using for data transfer. all phones I have had without wireless charging eventually end up getting less stable / lose USB connections. Motorola use to have a lot of wireless charging phones then they stopped adding them.

The reason I'm asking is I'm thinking about buying one, I didn't notice a finger print scanner or expandable micro SD card slot when I skimmed over the specs. Are these missing?

Thanks
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Mazinhobsb:
Unfortunately the display of my Mi 9t Pro cracked at the top and the screen ended up getting all dark, anyway ..

Due to the high value of the Amoled display of this device here in Brazil, I saw some reports that the display of the Redmi Note 8 is for the Mi 9t Pro, working perfectly, including the digital one on the screen, the only obstacle being an noch part that would be "camera" included on the Note 8 screen. Has anybody ever seen reports about it and can tell me if this adaptation really works?I thank you all!Sorry for the english, I'm using google translator.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Robbo.5000:
AliExpress has sellers that have TFT LCD displays, which are much cheaper than AMOLED, specifically for this phone.

This seller has both options.

https://a.aliexpress.com/_dY5C2E9
[Touch Diamond, MDA Compact IV ROM Development] pcharouz:
I am so confused with so many hard spl's I dont know which one to use... and they dont even match the rom #

what are you guys using?

EDIT:

IF you have a 1.40, mark	HardSPL_Olinex137_Unsigned for unsigned and HardSPL_OliNex138_Signed for signed
[Touch Diamond, MDA Compact IV ROM Development] saveferris:
Good question, I have no idea.

I'm uisng olinex's unsigned SPL, which lets me Flash my Diamond with any unsigned and/or signed ROM.
[Touch Diamond, MDA Compact IV ROM Development] oldhouse:
I am using 1.40 which is not listed in the poll.
[Touch Diamond, MDA Compact IV ROM Development] funnysurf:
I also :rolleyes:
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
I think most people use 1.40.OliNex, and quite some use 1.30.OliNex, so add them to the poll ;)
[Touch Diamond, MDA Compact IV ROM Development] MrDerrickC:
1.40 here as well.
[Touch Diamond, MDA Compact IV ROM Development] live3:
me to 1.40 by olinex!!
[Touch Diamond, MDA Compact IV ROM Development] GPSSlovakia:
I am using Olinex 1.40.
[Touch Diamond, MDA Compact IV ROM Development] oscahie:
1.40 Olinex
[Touch Diamond, MDA Compact IV ROM Development] papimuzo:
1.40 olinex, why not in the poll?
[Touch Diamond, MDA Compact IV ROM Development] pcharouz:
I cant seem to find 1.40 olinex, can someone post a link? anyway, just pick other...
[Touch Diamond, MDA Compact IV ROM Development] mickeymouse:
here also 1.40 olinex
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
don't be joking. :) 1.40.OliNex should not be dismissed as "other" as it is the most common hardspl version.

here it is: http://xdaforums.com/showthread.php?t=400950

also 1.30.OliNex is here: http://xdaforums.com/showthread.php?t=400402

now you can add them to the poll :P
[Touch Diamond, MDA Compact IV ROM Development] Confucious:
Of course it is!

Olipro = Very Good

cmonex = Very Good

The OliNex is greater than the sum of the parts :)
[Touch Diamond, MDA Compact IV ROM Development] htckaiseruser:
So its clear, almost everyone uses the Olinex 1.40.

Shame on the guy who made this poll, forgetting the most important one:eek:
[Touch Diamond, MDA Compact IV ROM Development] demacus:
And another one using 1.40 Olinex.

Come on guy, add it to the poll.
[Touch Diamond, MDA Compact IV ROM Development] pcharouz:
um.. its says "	HardSPL_Olinex137_Unsigned" in the link u gave me.. and I have that listed....

edit: sorry, I dont think you can edit the poll
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
lol, you haven't fully read that post then... 1.37 in the update notes. the main post talks about 1.40.OliNex, read it all.
[Touch Diamond, MDA Compact IV ROM Development] pcharouz:
well it doesnt actually say 1.40.... :D but I now noticed that when I enter the bootloader on my diamond it says it... :)

sorry for the confusion
[Touch Diamond, MDA Compact IV ROM Development] sumitescp:
Anyone using the dollypro version? lololol

btw i am using 1.37 olinex unsigned (voted)
[Android Head-Units] Majster25:
Hi,I need an update file software version? " KC1E0110-P01-1.1.4.3.1 - BLINK161 - 20200104 - N3" ?

I would like to update my radio.

I have a problem I installed the latest version

KC1E0104-PA1-1.1.4.3.1_20190929_181347

but the radio freezes on the welcome screen

RADIO INFORMATION :

Android 9.0

4gb + 64Gb

Hardware : RK3399

KERNEL VERSION :LINUX4.4.167+

OS VERSION : KC1E0110-P01.1.1.4.3.1-BLINK161-20200104-N3

MCU VERSION: STM32-20200103-11-KC6-33
[Android Head-Units] MrSchlumpf:
may an update help?

https://xdaforums.com/t/px6-rk3399-stm32-android-10-head-unit-user-q-a.4423601/#post-86674103
[Huawei MatePad Pro Questions & Answers] stoot:
Hi,

Can we install windows 10 on Huawei MatePad Pro and still using the stylus and all other features?

I think this is a decent alternative since G play services are not supported on this device!!
[Huawei MatePad Pro Questions & Answers] lazycow:
Windows 10 does not have the necessary hardware support, and Huawei devices no longer allow replacement of the system software. So even if someone could hack together a version of Windows for ARM that would sort of work, the tablet would refuse to install or boot it.
[Huawei MatePad Pro Questions & Answers] Guigs2109:
good luck
[Android Q&A, Help & Troubleshooting] Muadib11815:
Hello everybody... Umidigi Power 3 Compass/Gyroscope problem. The Umidigi Power 3 Compass/Gyroscope points all directions with any navigation or gyroscope app. I use google maps and skywiew. Thanks in advance

p.d. everything else is fine, I have version 1.1. I need compass for driving in my work, it is important

Thanks in advance
[Android Q&A, Help & Troubleshooting] Apipote:
A disaster around here too. All software is horror. Full of bugs. We will have to wait for the promised update at the end of this month. You are lucky if everything else is fine.

Regards
[Android General] VB6backtester:
Hello, I'm proud to show you the last version of my app GPS-locator-OSMaps. The first version implement a radar style screen to track a position, or to choose a position on a GPX file.

The last version show you Open Street Maps with your gpx track and actual position. You can Zoom, dezoom, swipe and point on maps to select a new nav location.

The altitudes are represented with the colors (blue deepest, and red hightest points).

Tested on Amazfit Stratos 2, Pace...

[IMG="carto maps app"]https://github.com/gege13007/Amazfit-Stratos-GPS-locator/blob/master/6-carto2.jpg[/IMG]

Details and APK are on https://github.com/gege13007/Amazfit-Stratos-GPS-locator
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] der-seemann:
Hi,

my phone stopt charging properly, maybe s.o. can help me fit it.

Stock Android, Magisk, debloated.

Since a frew days is shows a yellow triangle wehn charging with phone turned off. When powered on, someties it is charging very slow,then again it shows that it it not charging at all.

I tried different cables and chargers.

I cleaned the USB port.

I cleaded the cache.

nothing seems to work.

here is a dump of "dmesg | grep bat" maybe s.o. can find a hint whats the problem.

the first one I took with TWRP, where it is slowly charging, the second with normal stock android, were it is only sometimes showing charging symbol and not really charing at all.
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] HoldMySoul69:
It's charging with usb, at least phone thinks you are connected to usb. I recommend reflashing phones FW(Firmware) and charge it without any mods, root or anything.
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] der-seemann:
It seams that the usb port is broken. Maybe I'll give it a try to resolder it...
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] MaDaLiNoSt:
Reflash stock kernel. On logs it says 2500mw but this phone is rated for 1.5A for charging.
[Upgrading, Modifying and Unlocking] mievalt:
I'm trying to change the Qwerty to Qwertz and already had some results... Read the Thread and maybe you can help to finalize this...!!!

Greatings Mievalt!
[Upgrading, Modifying and Unlocking] guisof:
Hey

How did ou do ?

I'm trying to get a AZERTY for myself (French !)

Let's provide the info so that I can cook a AZERTY ROM

Thxs in advance
[Upgrading, Modifying and Unlocking] mievalt:
First of all it seems that there is a problem with touchscreen and mouse I'm trying to fix that but no promises.

You have to replace all files of the zylonite_keypad_Us.dll including the S001, S002 etc. files.

Do the same with the consHID.dll files.

My Keyboard layout is now qwertz but as I said there are still problems with the touchscreen and mouse. But I think we are quite close...
[Upgrading, Modifying and Unlocking] guisof:
I need to replace these files by the same ones from a French ROM I assume ?
[Upgrading, Modifying and Unlocking] mievalt:
Yes thats correct!!!
[Upgrading, Modifying and Unlocking] mievalt:
It is very curious...

I've managed to change the qwerty keyboard layout to qwertz, and first the touchscreen works fine, but when use the mouse button for the first time I can only use the touchscreen to click where the cursor is...??? Sounds as stupid as it is???!!! It seems that the "old" German Rom I use doesn't really come along with the new mouse driver that can hold the tap....

Does anyone know a solution or can assist??? The zylonite_keypad_Us.dll seems to be Samsung-made. Maybe someone with more experiences can say if it is possible to change some parts of the file and which!!!!

What I will try tomorrow is to use a ROM that doesn't have the new mouse driver... Maybe I get some results!!!
[Upgrading, Modifying and Unlocking] Realhawk1969:
Hi. i have the same problem, i update with an Italian ROM (I live in Ticino). I have understand that i have to replace the zylonite_keypad_Us.dll but what ist the right file that i have to update ? And where can i find it ? Grazie.
[Upgrading, Modifying and Unlocking] mievalt:
I tried several things... and found out that its all about these three files:

zylonite_keypad_Us.dll

conshid.dll

compime.dll

with all there S00x files.

But by just replacing them your touchscreen and mouse screw up....

I'm trying for days now but can't fix this problem... EFN meant we need other Language MUIs, so replaced some but also no results...
[Google Pixel 3 Guides, News, & Discussion] MatthewOffical:
Hi!

Can you pull out from Android Q Beta 2 the "framework-res" and "framework" APK files? I need the bolder Battery Icon because I want to create a Battery changer magisk module.

Thanks!
[Android Q&A, Help & Troubleshooting] Da Luce:
I have a Note 8 and can't figure out how to change fonts in Android apps such as Wikipedia and Chrome. I have changed the font to Samsung Sans in the system settings, but this doesn't apply to apps, only the system font.

Please help, the stock Roboto font is a hideous abomination. Thank you.
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
If your phone is rooted changing font on a per-app basis can be done by means of Xposed Module called Fonter.
[General Questions and Answers] Alvin50:
At last, it happened! (My fault, indeed).

I was upgrading my J5-2017 from LineageOS16 to Lineage17.1

I erased all, reinstalled an Oreo official ROM (J530FXXS5BSE3_J530FITV5BSC1_ITV) by Odin,

got developer status, installed TWRP J530F_TWRP_3.2.1.0.tar by Odin, RMM-state bypass by Corsicanu

updated to TWRP TWRP-3.3.1-j5y17lte.tar, reinstalled RMM-state bypass and no-verity-opt-encrypt-6.0.zip.

Then Magisk-v18.1.zip from sdcard, updated to Magisk-v20.0.zip, same from sdcard.

All run flawlessly, and I were to install the new LOS, when I observed an install note of Hacker812c that outlined

the necessity to upgrade the bootloader ad modem using Android 9 files. My stupidity made me install the whole Pie,

thinking I could well downgrade and reinstall Oreo. So I installed J530FXXU6CSK9_J530FITV6CSL1_ITV.

Despite having gained access to developer's bootlock control, when I tried to install TWRP, Pie said it wouldn't allow

unofficial system changes, and aborted the operation. While, subsequently I tried to reflash the former Oreo, it denied,

claiming its bootloader was out of date. The preload flag was set, rmm, also. As I tried to power off, it went in an emergency state, saying "An error has occurred while updating the device software. Use Emergency Recovery function in the Smart Switch PC software.", refusing to power off whatever I did. I also tried Smart Switch, but it didn't see the device, neither in a newer nor in an older version that seemed allow to select the phone model, giving a "device unrecognized" or a "device unsupported" message.

The device stays on, and not to miss its battery, I hold it plugged, is it right, ot is it better to let battery drain-off?

That's all... sigh! :crying: :crying:

Does anybody have some viable suggestion?

Best regards
[General Questions and Answers] Alvin50:
Pfui!

I succeeded in debricking my J5-2017!

Not by intelligence, but merely by desperation...

I decided to let it discharge to zero, but after some hour, when the battery was around 50% (I discovered it later),

I began to furiously test all possible combinations of the various buttons, that were unrensponsible in the usual way.

Pushing both Vol- and PWR appeared to switch the device off only momentarily, and all normal manoeuvres to put the

device in recovery mode failed sistematically. But I tried to gain vantage in the instant in which the screen gone black,

trying and retrying with no real reason, to push Vol-, Home and PWR as for recovery mode, varying the timing of pushing

the buttons. At last I obtained to enter in the Odin download enabling screen, but it suddendly disappeared. After another

lot of trials, I was pretty sure of what follows:

1) Hold down both Vol- and PWR for 7- 10 sec. until the screen goes black, then immediately

2)slip from Vol- to Vol+, release PWR, hold Home down.

The display would present the screen to choose between Continue to download (Vol+) or reboot (Vol-)

DON'T PUSH them, but PWR instead. The screen "don't power off until downloading complete" would come up

allowing to install THE SAME ORIGINAL ROM (Pie) that were corrupted.

NOTE: KG state: PRENORMAL

FRP LOCK: OFF

OEM LOCK: OFF

Then, when the system is installed, it's impossible to disable Google Protect and, in the developer's options

the bootloader unlock is missing. I suppose it's because of the Prenormal.
[General Questions and Answers] Droidriven:
When you flashed the Pie firmware, that probably locked your bootloader, making it impossible for you to flash or use TWRP or Magisk.

You will have to flash the updated firmware, you should be able to flash it via Odin while the device is booted into the "encountered an issue" screen.

If flashing the Pie firmware locked your bootloader, you will not be able to use TWRP or Magisk unless you find a way to unlock the bootloader. You may just have to leave the device continuously for 1 week without powering off or rebooting during that week. Then look in your settings to see if the OEM unlock setting appears.
[General Questions and Answers] Alvin50:
I hope you're right... For I have read that the "quarantine week" applies for RMM lock but is useless for KG lock...

Well, we'll know it for sure the next week. Thank you for your reply, anyway.
[General Questions and Answers] Alvin50:
I succeeded in reverting KG state from Prenormal into Checking using the suggestion of a video on YT.

My starting ambient is Galaxy J530F with installed Pie standard ROM J530FXXU6CSK9_J530FITV6CSL1_ITV, Italian version.

The procedure had been the following:

Connect to a WiFi network

I use my laptop as hotspot with two little command scripts to be executed as Admin. [my OS is Win7-64]

filename "hotspot wifi-start.bat":

NETSH WLAN set hostednetwork mode=allow ssid=YourWiFi Name key=YourPassPhrase

NETSH WLAN start hostednetwork

filename "hotspot wifi-stop.bat":

NETSH WLAN stop hostednetwork

the main internet connection of the PC shall be made available to LAN users, and consequently also to WLAN.

Go to developer's options and enable "stay active" and "system automatic update".

Go to Settings -> general settings -> set date and hour and choose 2019, January,1st.

Go to Settings -> "software updating" and disable "wifi automatic download"

Tick on the upper row "Download and install manually"

It will appear a screen saying "registering device" and, after a while, "checking for updates".

After some other minutes it would display the screen "your software is up to date".

Would you not see "checking for updates" or "your software is up to date", rule your action looking at download transfer rate. If you don't see traffic for some other minute, exit, shut off, and restart

Now, looking to your developer's settings, you'd see the OEM unlock slider visible and selectable. Set it on, then power off.

Push together Vol-, Home, PWR and then Vol+ to select Odin download mode, and you'd see that KG status is reverted from Prenormal to Checking...

YABBADABBADUUU!! :victory::victory::cool:

The weird thing is that, despite the automatic time update expressly set off, the phone date & time updated correctly at present values... GOOGLE POWER... At-Tention! Present Arms! ;)

Now the problem is how to avoid failing again in the same "blackhole" while installing Magisk, TWRP or other non official but very useful software... Pie security appears to be a nasty beast, and in my land we say that, "once one had been burned with hot water, he also fears the cold one"...

Some hint?
[General Questions and Answers] Droidriven:
I don't know, I dealt with the same issues on a J3727 many months ago, I got the status to switch to "checking" and I enabled the OEM unlock setting, but I still couldn't get TWRP or Magisk to work. I chased the issue for weeks attacking from every angle that I thought was even remotely possible and also had some of my colleagues working on it with me, we never made any progress.

Also, there is a default option in Windows 7 that creates a hotspot, you should not need to run any scripts to enable hotspot.

https://www.groovypost.com/howto/turn-windows-7-laptop-wireless-hotspot/
[General Questions and Answers] Alvin50:
Thank you for your information.

In the past I used .bat files very often, and so it comes staightforward to me. Moreover I see that the hotspot facility has been removed in recent win releases, so maybe it' s easier to use those .bat files if one doesn't want to waste time looking for some freeware that makes this job.

I also heard about near impossibility to root Pie phones, but on the other hand there are people claiming they did it. I'll take some more time to google around, let's hope I stumble on something viable. I made other posts in ananjaser thread, let's hope some developer can reply affirmatively.
[General Questions and Answers] Droidriven:
Rooting Pie is very device specific, some can, some can't. It really comes down to the flagship brands and models, such as Samsung S devices, the J series devices don't really get any support from "real" developers, it's usually just some members finding a way to root and maybe getting lucky building a TWRP for the device.

The Pixel devices(other than the Verizon model) are rootable.

OnePlus devices are rootable.

As for Samsung devices these days, you're lucky if you find a way to root without TWRP or even root via TWRP/Magisk. Typically, the carrier branded versions lock the bootloader and do not allow OEM unlock, it is usually the models from the various MVNO subsidiary networks, not the main networks that allow OEM unlocking.

Except for in my case, my carrier is StraightTalk and they have their devices locked down pretty tight and can't be modified.
[General Questions and Answers] Alvin50:
At last I succeded in routing Pie.

After a lot of trials that ended into infinite loop or altering KG status, I have come back to my old solution https://xdaforums.com/showpost.php?p=80223502&postcount=82

The only TWRP I found working is that, though I have to beware that, if you, during recovery, allow the screen lock to start, you fail into a nightmare of misworking of the touch screen that gets quite crazy, changing all setting randomly at light speed until you succeed in powering it off. Once installed it, using it with the above cares, also install all stuff to root in the same post. It works on Pie too.

Kind regards
[General Questions and Answers] Henri.P:
I don't understand why you should create a hotspot with your computer. I will still test your method step by step ;)

edit: Thanks it works!
[General Questions and Answers] Alvin50:
The story repeats itself...

This time it happened while I was updating to Gonic LOS17.1 a newly bought J5.

Instead of stopping its upgrades to 6CSK9 version, a firmware lock and its consequent upgrade caused me to go to 8CTK1 baseband. Apparently working, I then sadly discovered that it disallows navigation, at least I think it's its fault.

So now I need to revert to CSK9 baseband, but all efforts I did of loading either the whole ROM or BL and CS only via Odin failed. I'm presently on Gonic LOS17.1 with OrangeFox recovery, all working well except for navigation.

Can someone please address me to a way to revert BL and modem to former CSK9?

I'm wondering of some "brute force" substitution or tampering as plain Odin method seems not to work in this case. Maybe something that involves Android kitchen?

What I fear more is that I saw a newer security patch of january,5 2021 that might get things better screwed up...😭😭
[Thinkpad Tablet General] MDCore:
Hi. The google drive RAR files expect a password. What's the password?
[Thinkpad Tablet General] gubbe:
It's "https://firmware247.com" without quotations.
[Thinkpad Tablet General] banlee36:
Thanks, that's working for me
[Thinkpad Tablet General] chribbio:
Hi,

I followedall the steps, but after entering fastboot, at step 10, when I type the line "fastboot flash osloader efilinux-user.efi" I receive the message "FAIL(flash_cmds error!).

What am I doing wrong?

Thank you for your help.
[Thinkpad Tablet General] chribbio:
I finally made it.

However, so far the tablet is almost unusable: although there is internet connection it is impossible to download OTA updates, Google Play does not connect, the pre-installed browsers (both Chrome and UC Browser) do not go beyond the google search page.

Any suggestion?