yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] smit_pathak1:
Whyred have 636 processor. i overclock it with kangarooX kernel.

I also tried many roms like you did.

so just find one with high ranks. you can find it on Xda front page. just install that rom.

install kangarooX or kirks kernel.

Manage your ram via nox cleaner and/or sd maid

Apply L speed boosters performance mode.

Apply GL tool settings. play on medium graphics, high fps. and you are good to go on vince/whyred or any device with 4gb/6gb ram.

I tried GL tools on a 2 gb ram device, applied potato graphics settings and i played it fair. so i think it should work for you too.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] Andrio:
Okay thanks will try.
[Xperia SP Q&A, Help & Troubleshooting] magc880826:
I installed 4.1 stock jb rom for my c5303 and can't find any gapps. How to install google apps for the 4.1 stock rom. Please help.
[LG G7 ThinQ  Questions & Answers] Obscenic:
On or around Dec 5 (the day I install the just-released Pie update G710AWM20c_00_1025) my earpiece speaker stopped working. Or seemed to, until I was in a very quiet room and realized that it could be heard VERY faintly - almost as if coming from the back of the phone near the top (if you put your ear to the back you can hear the caller). The volume control was up of course. It's still not working and here's the checklist of things I've done:

None of these changed the behavior

- Tried multiple apps

- Tried to clear cache, but this phone does have a recovery menu except to reformat - but I did the "smart clean/optimize phone"

- Booted in safe mode

- Restored to factory

- Restored to factory again

- Restored to factory again

- Flashed the rom from before the update

- Replaced the earpiece speaker (!!!)

- Inspected the speaker grill for any blockage - it was completely clear

The problem persists. I'm at my wits end, so any thoughts - snarky or not - will be greatly appreciated!
[LG G7 ThinQ  Questions & Answers] allinkiran:
Can you check with some other sim card? The same thing was happening on my phone but only on the 3g sim card while the 4g volte sim calls were perfectly loud and clea(dual sim variant). Fixed the issue by getting a replacement for the 3g sim card.
[LG G7 ThinQ  Questions & Answers] thenotonly:
Speaker holes may be clogged up with dust. Check it carefully. Had the same issue took a small needle and cleaned the holes and the problem was sorted outside.
[LG G7 ThinQ  Questions & Answers] Obscenic:
Holy ****, that was it. When I looked from the inside (when it was apart) they looked clear, I could see daylight through them. I blew some air through them anyway... With a few pokes of a needle into some invisible dirt, full sound is restored. I feel like an idiot, but at least I can use my phone as a phone!

Thank you!
[Galaxy Note 4 Q&A, Help & Troubleshooting] Xyspade:
TL;DR: Specifically looking for a Note 4 that satisfies the following:

- GSM Unlocked 4G LTE and works in the US*

- Has an unlocked bootloader (is rootable, custom ROM-able, etc.)

- Is exempt from, or at least has the fewest reported instances of, the infamous eMMC failure, if possible

*I don't have much knowledge on carrier frequency bands - if it does calls, SMS, and 4G LTE data at reasonable speeds for a 6 year old phone (can stream a video at 480p), that's fine

I have a N910A (the AT&T one) and it's by far and wide the best phone I've ever had. It has an unparalleled set of hardware features that no phone on the market today has beat (IR, S-Pen, user-removable battery, user-servicable internal electronics to an extent, 16MP camera with focus, stabilization and 1080p60 recording, SD card slot, and headphone jack, all in one package). But sadly it fell victim to the eMMC issue earlier this year. So far the cardboard fix combined with wakelock has kept it usable, but it still runs slow, overheats, and randomly freezes doing simple tasks.

However I refuse to give up on the 4 just yet. I have a bunch of spare batteries, plus all my chargers are still micro USB, and the phone still does everything I need it to and more; had it not been for the eMMC issue it would still be going strong.

I'm leaning toward either the N910T (Snapdragon, T-Mobile) for its great software modding potential, or the N910C (Exynos) because I've heard the Exynos one may be less prone to the eMMC failure (?) and has better performance (?), but this is speculation. Plus the Exynos one is more expensive and harder to find. I had thought about just getting a motherboard of one of those two models to put in my AT&T shell, but with that comes the hassles of possibly needing to swap the cameras too, coming across other incompatibilities like carrier frequencies, and worst of all getting one with a bad ESN.

If I'm right that N910T or N910C is the way to go, I'm hoping for some input to steer me in the right direction by addressing a few questions I have that I couldn't find clear answers to:

1. Is it true that the Exynos one isn't prone to eMMC failures, or is every Note 4 susceptible all the same? If the latter is true that pretty much confirms I would go for N910T.

2. Is the Exynos version more or less equivalent to the Snapdragon one in terms of usability when used in the US?

3. Does one or the other have greater custom ROM support?

4. Would I run into any other issues using the Exynos one in the US that the T-Mobile one wouldn't have?

Any input is appreciated, but please be aware I'm really looking for input based on my question. If you're only here to recommend a new phone outside of the Note series, it will take some hard convincing :p

My carrier is TracFone. Let me know if you need any more info. Thanks for your help!
[Galaxy Note 4 Q&A, Help & Troubleshooting] doubledragon5:
It's hard to say really, but what you need to know first is.. Which carriers had the most eMMC failure, then go from there.. If your here in the states, then either ATT again, or T-Mobile. I have had 3 Note4 1 with Verizon, and 2 Sprint.. Neither one had failures.. I sold the one from Verizon when I went back to Sprint.. The first Sprint I had for less than 6 months, as I got bored, and wanted something new.. But with the phones being locked down, and me not happy with phones I have had including my Pixel 3a Xl which is being kept in it's box only as a spare.. I went back to this phone, because of root, removable battery, S-pen, really decent camera that came in the custom rom etc. And believe it or not, with a little tweaking, it is just as smooth as my Pixel.
[Galaxy Note 4 Q&A, Help & Troubleshooting] iceepyon:
Seeing as you live in the US. It would be more beneficial for you to get a US variant of the Note 4. As both the international variants won't receive LTE from US Cell Providers with the exception of T-Mobile, I believe
[LG G8X ThinQ Themes, Apps, and Mods] sev7en:
Hello dears,

I was looking for news on our G8x and I found an interesting contest did by LG about the V50s about the best wallpaper dual-screen. The contest is terminated by not the way to make it!

You can find the instruction (ok it is Korean...) and the PSD file for templating here: https://blog.naver.com/grafolio/221667944038

Cheers,
[LG G8X ThinQ Themes, Apps, and Mods] BB0401:
I still do not understand how to make.
[LG G8X ThinQ Themes, Apps, and Mods] JonnyTrulove:
Nice find. Thank you for sharing!

Lg is so bad about making resources like this available to consumers in the US...
[LG G8X ThinQ Themes, Apps, and Mods] EmirSc:
Will try it out tomorrow
[LG G8X ThinQ Themes, Apps, and Mods] twospirits:
I was able to translate that page using google translate and sort of figured it out. I downloaded that LG G8X photoshop template and made a version for my V60.

I then downloaded a nice wallpaper from here, split the image, added a black space to the bottom of it (so my text icons stick out) and inserted them into my phone.

I then applied each image to each screen.

I don't think it turned out bad. image here

I think the hard part is trying to find an image.
[LG G8X ThinQ Themes, Apps, and Mods] nileHUN:
//OFF (launcher)

what kind of launcher are you using?
[LG G8X ThinQ Themes, Apps, and Mods] twospirits:
I'm using Nova launcher. But I assume you are wondering how I got the folders to be just names. I use TextIconCreator version 4.7.1 (last updated in 2012) which I carry over to each phone I upgrade to. It doesn't seem to be on the play store anymore. But Simple Text-Text Icon Creator does the same thing I believe and that is still available in the play store.
[LG G8X ThinQ Themes, Apps, and Mods] Specter597:
@sev7en Thanks for sharing the link and getting us started!

I was inspired so I may dump some L/R wallpapers here once in a while.

View attachment 5202621 View attachment 5202635
[Tilt, TyTN II, MDA Vario III General] erraticfun:
Hi guys, this is just a tip for WMWifiRouter users, that use kaiser alot in home with wireless conections like me, we all know that the phone gets to hot and turns off, and the battery dosnt even charge, so i come up with this very easy solution, problably there is better ones but this one was good to me and i made it in 10 minutes or so..

Material:

-A tape;

-A cooler (i took one from a old computer, 12v ,11A actually was the right size for the tape);

-Glue;

-4 screws;

So i stuck the tape to the cooler, be sure the cooler is at the right side, then i added 4 screws under the cooler so the cooler dosnt touch the table, and it throws more air to the mobile, and i pluged it to the computer, so every time i turn my computer on it turns the cooler on also.

You can charge the battery as long as you wish because it will be allways cold, and the kaiser can stay on as long as you need it to be on, you will see in the fotos below that the led is allways green.

And that´s it, problably some of you will think this maybe some stupid idea but it helped me with the problem and it tooked me 10 minutes to solve it, not expensive and very easy to make.

greets to all comunity :D

And sorry for my bad english lol :P
[Tilt, TyTN II, MDA Vario III General] raiisak:
Haha! Nice one! I enjoyed that :) Lets see: tape *check* (...)
[Tilt, TyTN II, MDA Vario III General] amkaos:
it is funny looking.. real smart and i like it.. but funny. good idea
[Tilt, TyTN II, MDA Vario III General] erraticfun:
nice that someone liked it :D
[Tilt, TyTN II, MDA Vario III General] NuShrike:
Yes, the Kaiser is using the Pentium4 of Qualcomm processors.

Good idea - I try to hold it up to the car's A/C usually while traveling for the same reasons with Navizon heating things up.
[Tilt, TyTN II, MDA Vario III General] erraticfun:
Did anyone have more ideas? maybe more sofisticated...
[Tilt, TyTN II, MDA Vario III General] strikeone:
very nice work - it looks quite nice and practical.
[Tilt, TyTN II, MDA Vario III General] mech_supernova:
you coulc also try something like this http://www.coolitsystems.com/index.php?option=com_content&task=view&id=43&Itemid=133
[Tilt, TyTN II, MDA Vario III General] erraticfun:
Looks nice, only bad thing is must pay for it :S

mine looks cheaper lol
[Tilt, TyTN II, MDA Vario III General] gregxdoom:
Hahaha!

Ghetto fabulous!
[Xiaomi Mi Pad 4 Plus Guides, News, & Discussion] tom.android:
Info.

+CN version (not global) --no pre-installed gapps, GMS

+WiFi +Bluetooth not fixed yet (Only Mobile Data working)

Download: A-Only Device

https://sourceforge.net/projects/oemgsis/files/ZUI/ZUI-Aonly-10-20191207-ErfanGSI.img.7z/download

=========================

TWRP : https://mega.nz/#!sHoXlaDK!ZIfuRrtl7IGsruGMIWDrbvudKgxcYdiEd-6iQS2YFNg

Step

1. flash latest Firmware https://mega.nz/#!QDplSYab!mrB5f8875...kq3anZCipLWzqo

2. flash Vendor https://mega.nz/#!ECAG1aIS!OuGf9eVoi...bu9AwR95MSlO-g

3. flash GSI as System Image

4. flash "Permissiver_v5.zip" https://mega.nz/#!0fplDaJR!OhqcQzIoA...w1cTokJMJEGD0E

5. flash allzygotefix2.zip https://mega.nz/#!xXpViC4Y!UsRgGMYNt...s-9xrZrPu5QCP8

6.Reboot

===================

set English Language. (see pic)

======================

ExLite Gapps (normal edition)

https://xdaforums.com/android/software/gapps-exlitegapps-android-10-t3984039

***Face data will be active after installed ExliteGapps.

=====================
[OnePlus 7T Questions & Answers] YrrchSebor:
My phone keeps waking up, not to the ambient display but to the OG lock screen, it happens within 10 to 20 seconds after turning the screen off, and keeps happening over and over again. I guess it must be a third party app because it doesn't happen in safe mode, so my question is, is there an app I can use to determine the culprit? I don't see any option to disable third-party apps, only uninstall them, which is highly inconvenient, to keep uninstalling apps to see if they are keeping the phone awake, then having to reinstall them if they don't seem to be the culprit.

Is anybody else having this problem?
[OnePlus 7T Questions & Answers] YrrchSebor:
I got lucky on a Google search and learned that it was the Ring app! Apparently there's been a little bug where it turns the screen on even when it's not supposed to give you a notification.
[OnePlus X General] emilianoheyns:
I have a new TWRP on my OPX, but I don't really know what to change in the rawprogram0.xml file.
[OnePlus X General] emilianoheyns:
I have no problems with having an unlocked bootloader -- I thought this device had one already. Yesterday it was running TWRP3.0.2-1 and LOS Marshmellow, I just screwed it up trying to upgrade it to an unofficial LOS16. It would first bootloop constantly, then I tried QDL, and now it doesn't even seem to turn on; I can hold the power button for a full minute but the screen remains black, and there's no vibration as I'm used to. It does show up in QDL mode; I tried the procedure as per point 3, using twrp-3.0.2-1 as the recovery image. QDL says:

HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ image: 13 offset: 0x0 length: 0x50
READ image: 13 offset: 0x50 length: 0x1000
READ image: 13 offset: 0x1050 length: 0x1000
READ image: 13 offset: 0x2050 length: 0x1000
READ image: 13 offset: 0x3050 length: 0x1000
READ image: 13 offset: 0x4050 length: 0x1000
READ image: 13 offset: 0x5050 length: 0x1000
READ image: 13 offset: 0x6050 length: 0x1000
READ image: 13 offset: 0x7050 length: 0x1000
READ image: 13 offset: 0x8050 length: 0x1000
READ image: 13 offset: 0x9050 length: 0x1000
READ image: 13 offset: 0xa050 length: 0x1000
READ image: 13 offset: 0xb050 length: 0x1000
READ image: 13 offset: 0xc050 length: 0x1000
READ image: 13 offset: 0xd050 length: 0x1000
READ image: 13 offset: 0xe050 length: 0x1000
READ image: 13 offset: 0xf050 length: 0x1000
READ image: 13 offset: 0x10050 length: 0x1000
READ image: 13 offset: 0x11050 length: 0x1000
READ image: 13 offset: 0x12050 length: 0x1000
READ image: 13 offset: 0x13050 length: 0x1000
READ image: 13 offset: 0x14050 length: 0x890
END OF IMAGE image: 13 status: 0
DONE status: 0
qdl: failed to read: Connection timed out
LOG: Host's payload to target size is too large
LOG: logbuf@0xF8023A78 fh@0xF80208E0
LOG: logbuf@0xF8023A78 fh@0xF80208E0
LOG: logbuf@0xF8023A78 fh@0xF80208E0
LOG: start 1409024, num 31680
LOG: Finished sector address 1440704
[PROGRAM] flashed "recovery" successfully at 3960kB/s
no boot partition found

but the OPX still won't boot.
[OnePlus X General] SebiderSushi:
Is your bootloader actually unlocked?

The OnePlus X ships with a locked bootloader that prevents flashing files to the device using fastboot.

The usual steps to modify the OnePlus X and installing custom ROMs are:

- Unlock the bootloader by running "fastboot oem unlock" on a desktop PC while the phone is connected in fastboot mode.

- Flash TWRP by running "fastboot flash recovery TWRP.img" on a desktop PC while the phone is connected in fastboot mode.

Pressing the volume up button while turning on the device normally puts it into fastboot mode and "Fasboot Mode" will be displayed in the middle of the screen along with the oneplus logo.

Unlocking only works with the original OnePlus recovery and if the option "Allow OEM unlocking" is checked in the developer settings. Unlocking requires wiping all userdata.

Did you never do this yourself with your OnePlus X? Did you get this device as a used phone from someone else who already unlocked the bootloader?

What do you mean by "bootloop constantly"? Could you not boot the recovery?

Are you saying you already ran QDL with the unmodified files from the UnBrick tool?

If you really had TWRP 3.0.2-1 running before all your problems started, then doing so initially soft-bricked your device to begin with, as i outlined in footnote [1] of my original post.

I am not sure of the precise timeline and order of your descriptions. I currently assume that you're saying:

1. Had a working device with ROM: "LineageOS 13.0" Recovery: "TWRP version 3.0.2-1" Firmware: Unknown

2. Flashed some "lineage-16.0-unofficial.zip" in TWRP

3. When rebooting, "bootloops" appeared [How did that look? What was affected - just ROM or recovery as well?]

4. Run QDL with the unmodified files from the UnBrick tool that is linked in my original post

5. Phone does not react to button presses except when putting into EDL mode

6. Run QDL with recovery only as described in Point 3 of my follow up post, with the image file of TWRP version 3.0.2-1, QDL repoted success

7. Still not booting [What exactly does this mean? Still no reaction to button presses? Dees the phone vibrate and bring up the OnePlus logo?]
[OnePlus X General] BolitaBolita:
I've followed the mentioned steps and Im still stuck on linux logo..

I desesperately need help, bought a bricked second hand Oneplus X which I know nothing of in terms of past actions but previous owner
[OnePlus X General] SebiderSushi:
If you did not modify any files from the unbrick tool by Naman Bhalla and qdl ran through sucessfully, it should have flashed a compatible combination of bootloader and stock recovery so you should be able to reboot to that one.

If this is not the case, you can also go with flashing just a TWRP image. Since there are really just two possible versions of the bootloader (at least in regards to booting compatibility) this should succeed after the second try at most. If not, it means that some other stuff might be broken as well.

As i wrote in my OP, for the OnePlus X any TWRP v3.0.2-0 or older is compatible with the "old bootloader" (Lollipop) and any TWRP v3.0.2-1 or newer is compatible with the "new bootloader" (Marshmallow).

What you basically want to achieve is to just get any recovery booting (be it Stock, TWRP, orangefox or any other useful recovery). From that point, it is fairly easy to get anywhere else on the OnePlus X.

As for other things that can break:

Most of the partitions in your device can be restored to an intact state by flashing an official OxygenOS zip (https://www.oneplus.com/support/softwareupgrade). There are some other ways but this is the safe and easy method.

Only a few partitions cannot be restored once tampered, since they are unique to the specific device. If this happens to be the case, then it can be fairly hard to fix. If the previous owner had unlocked the devices bootloader and flashed some stuff on it, you should ask them whether they might have some TWRP backups around, namely of the partitions "Persist" and "EFS".
[OnePlus X General] SebiderSushi:
Now what exactly do you even mean when you say "Bricked"?

If you can boot into recovery, then your device is usually not bricked, but even if, it is usually not in a state where using a flashing tool and risking to **** up the device for good has any real advantage over solving whatever problem in the recovery.

As long as your device doesn't have any hardware errors (broken storage) then the official OnePlus Recovery should almost always be able to install the official OxygenOS.

Under what terms did you even buy this device? How did the previous owner describe the state of the device and its defects if they mentioned them?

You are using windows, so how did you even end up in this thread?
[OnePlus X General] emilianoheyns:
Sorry for the delay -- I thought I had set up notifications and didn't want to push on the point until you had time, but I did not receive a notification for this.

I had a LineageOS running on the OPX before I screwed up an upgrade of LOS. I had TWRP on the phone. The bootloader must be unlocked then yes?

broadly, that is what I had done before, but right now I don't even get the fastboot logo.

Right, but I had passed that station before, as it was running LOS.

No, I did all this myself, but screwed up the update to a non-official LOS.

I could not, no, but now I'm not even getting the fastboot logo

Correct, yes.

Initially I could get to recovery, I tried to upgrade to the latest TWRP for the OPX, when I tried to restart that to recovery, it would just vibrate and reboot continuously

Currently, the screen stays black, and I can hold volume up or power for 20 seconds with no reaction (no vibrate, no logo)
[OnePlus X General] SebiderSushi:
After that, you can also boot back into fastboot mode and the run

fastboot oem device-info

from your computer to check if your devices bootloader is currently unlocked or not. If it is not, this is a perfect chance to unlock it, since you already got the official recovery installed and probably no user data to take care of anyway.
[OnePlus X General] emilianoheyns:
Hi, thanks for getting back to me. The problem I'm facing currently is that the OPX currently seems unresponsive -- the screen stays black, and no vibration, seemingly regardless of what button combination I use or how long I keep it on the charger. Any idea what key combo is most likely to bring it up in a state that QDL would see it?

I have fetched a fresh copy of OPX_UnBrick_Mini_By_Naman_Bhalla; I'm sorry to have to ask again, but I should then copy over prog_emmc_firehose_8974.mbn, rawprogram0.xml and patch0.xml unchanged, and run `/path/to/qdl_source_code/qdl prog_emmc_firehose_8974.mbn rawprogram0.xml patch0.xml`? I think I'd prefer to get it back to a booting state to then figure out what I can safely flash on it.

---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------

I should note, if I connect the charger, the red charging light comes on for a second, maybe two, end then goes out again. It does not come back on unless I plug in again, even if I let it charge overnight.
[OnePlus X General] SebiderSushi:
In my case the usual route to enter EDL mode worked fine - that is, disconnect your OnePlus X from any power source for a few seconds, then press and hold the Volume Up button and after a few seconds reconnect it to your PC where you run qdl, then release the button and execute qdl.

If you want to flash the default confuguration of the unbrick tool you must open your terminal window in the folder you extracted from the download (or cd to it). This is because the files that are flashed to the device are in this folder as you caj see and they are being referenced with relative paths / their filenames from within "rawprogram0.xml".
[OnePlus X General] emilianoheyns:
Ah well, it must have died somewhere along the way then. When I do that, even after having it on the charger, nothing shows up in dmesg. Thanks in any case!