yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 7 Questions & Answers] vejvik:
I tried everything

also unlocked the bootloader and tried other rom

fix is not a problem, but the signal is still weak (large inaccuracy), with most satellites up to 20snr

a month ago there was no problem, I suspect the gps antenna, but I do not recall any phone crash, etc.

unfortunately I find nowhere manual, video, where the antenna and how to fix it
[Xiaomi Redmi Note 7 Questions & Answers] lmp007:
try to change the region, restart your smartphone and check for any improvement in the gps signal.
[Xiaomi Redmi Note 7 Questions & Answers] vejvik:
I tried everything, fix is no problem, I catch 12 sometimes more satellites (in open area), but all with low signal. Just go under the edge of the tree, and the signal is very weak and very inaccurate.
[MX Player] DimeDrl:
I just started up mx player to watch a few videos on my Sony TV with android TV and the app is not usable after the last update.

The app is now locked into portrait orientation and the directions inputs for navigation won't respond. The cursor is stuck on the button that used to be the settings menu, but with that menu gone, I can't access it to make any changes. It has basically become unusable with a remote.

I managed to find a workaround, but its not a permanent solution. I have a bluetooth keyboard with touchpad I can pair to my tv, so I was able to access the settings menu by starting a video. There was no way to change the list rotation or re-enable remote control inputs. But after exiting the video, the settings menu button reappeared and remote control navigation re-enabled. Restarting the app also reset the orientation detection to landscape.

I'm not sure why all this worked, but it seems to have made MX Player functional on Android TV again.
[MX Player] The_Madhatter:
The same issue applies to Android tablets. Had to roll back to the previous version.
[MX Player] daromar:
At Mi TV Box the same, mx Player pro opens in portrait mode.

Wysłane z mojego MI PAD 4 przy użyciu Tapatalka
[MX Player] MXPlayer:
We are sorry to bring you this inconveniences. We have already released a quick fix for the same. However, due to the Google Play Policy changes, it may take several days to review the updates. Meanwhile, request you to install the latest build from our website (http://apps.mxplayer.in/download) and it may fix your issues.
[MX Player] oursgentil:
Since last update (1.15.4), MX player Pro was not usable on my Sony Android TV

I have installed from your website site 1.15.5

Cool, the app is now in good orientation

Arggggg, the doesn't find any videos !!
[MX Player] Jules63:
For me even the latest download offered above has the player now fixed in portrait mode when not playing a video. :(

This does not work well for android TV.
[E 2015 Q&A, Help & Troubleshooting] Sonicfann:
Hi guys I'm having a problem where on Android 7+ I have no sound please help me as soon as you can
[E 2015 Q&A, Help & Troubleshooting] riyan65:
Is the call volume is low, or no sound is coming out from speaker???
[E 2015 Q&A, Help & Troubleshooting] Sonicfann:
There's no sound from the speaker and the call volume doesn't work either
[E 2015 Q&A, Help & Troubleshooting] riyan65:
Is it works if you use head phone???
[E 2015 Q&A, Help & Troubleshooting] Sonicfann:
Well my headphone jack is broken but my Bluetooth earbuds work so yea
[E 2015 Q&A, Help & Troubleshooting] riyan65:
Then it should be Hardware problem, try hitting back of speak, something it works, if not you need to replace the speaker.
[E 2015 Q&A, Help & Troubleshooting] Sonicfann:
I think it's a software issue because games won't start they crash after the splash screen and the mic crashes Google Assistant and sound recorder
[E 2015 Q&A, Help & Troubleshooting] riyan65:
Try flashing other custom ROM. Maybe it will solve your problem.
[E 2015 Q&A, Help & Troubleshooting] Sonicfann:
No you Don't get it it's on EVERY custom rom above 6.0.1 also I tried what you said it didn't work

(Crdroid 5.1 was the one that caused the prob btw)
[E 2015 Q&A, Help & Troubleshooting] kanaan360:
Had this issue on my e 2015,I downloaded one of those speaker tester apps, and once I got to a high enough MHz sound,the speaker started working

https://play.google.com/store/apps/details?id=com.blackflame.internalspeakertester
[Tilt, TyTN II, MDA Vario III General] thentertaina:
iits really hard tto press soome keys on itt? heelp?
[Tilt, TyTN II, MDA Vario III General] grizzley:
Do a hhardd reesset. Thhen, press harrder or liift weeightss so thaat you dont feeeel liiike yoou aree pressing soo hardd on yyour keyboaard. If thhat dooseen''t woork, get annn iPhoone.
[Tilt, TyTN II, MDA Vario III General] kareeem:
Wth? It's a hardware problem, not a software--and if it was a joke, not funny. At the OP, if it's less than a year old, get a warranty replacement if it's really bad at 1800-801-1101.
[Tilt, TyTN II, MDA Vario III General] grizzley:
Just wondering, but I think your advise is almost as bad as mine since you have no idea what ROM it is or anything else. I mean, is it a brand new phone? Stock ROM?

Is it a hardware issue? There are plenty of keyboard issues out there that ARE software related..... NOT HARDWARE!!!!!!!!!!

Who knows? To me, it sounds like a flashed ROM that has a simple keyboard issue that a CAB would fix.... but, who knows since the OP dosen't bother with giving any info other than iii hhaaave a kkeey issssuueee.
[Tilt, TyTN II, MDA Vario III General] kareeem:
Are you kidding me? He said it was HARD TO PRESS SOME KEYS meaning when he presses a key, he has to press it hard rather than the regular force needed. I have NO idea how that could be software related. Also, i take it that he means the slide-out keyboard, not the on-screen one.
[Tilt, TyTN II, MDA Vario III General] livefastdiefun87:
Guys quit the arguing.

@ OP can you provide more info so we can hopefully fix the issue
[Tilt, TyTN II, MDA Vario III General] P1Tater:
Well said. Stop the bickering.

@ the OP

Please provide more information. However, I feel as though it is going to be a hardware problem, maybe. But who knows, stranger things have happened.
[Tilt, TyTN II, MDA Vario III General] ChumleyEX:
thats the funniest thing I've read on this site.

woot Taters a mod and he's swinging axes around, watch out.
[Samsung Galaxy Watch] thanito:
So I have a galaxy watch active 2 and a huawei p20 pro as a daily phone. I noticed though that the watch dies not notify you when phone alarms go off. I have clock notifications enabled, yet no alarms ringing on the watch. I know that the watch itself has separate alarms, however I suppose that the phone alarm should also notify you on the clock. Is it only me? Is it a Samsung - huawei clock compatibility issue?

Cheers

Thanos
[Samsung Galaxy Watch] anych:
I have the same problem with P30. Unfortunately, I was writing here, but no one answered me.

What I managed to find is that the problem has it with no Samsung devices, but nowhere read a solution. Samsung does not want to cooperate because they does not answer when the question is not about their product.
[Samsung Galaxy Watch] vojopd:
Different apps, ofc it doesnt work.
[Samsung Galaxy Watch] thanito:
Yes, but since you have the option to set notifications on for clock alarm app, it should notify you through the watch, the se way it does for every other app. I am not saying that when you set your alarm on the phone to also have it in your alarm app of the watch, since they are indeed different apps,yet the notification should be active..
[Samsung Galaxy Watch] dersie:
It seem that Android Alarm Clock app do not send notification to connected watch. Just send on WearOS Watch.
[Samsung Galaxy Watch] Petr Monty:
GW SM-R800, Samsung S8.

Everything works fine. If I set an alarm on my phone, it will also appear on my watch.
[Samsung Galaxy Watch] anych:
The problem is with other brands, with Samsung phone work fine.
[Samsung Galaxy Watch] thanito:
Yeah that's what I imagine as well. Not cool though..
[Samsung Galaxy Watch] Lada333:
It does send a notification of your alarms. You need to understand though that when your alarm goes off on your phone, it doesn't show a "notification," like any other apps, it works a bit differently. If you have any means of dnd turned on while you're sleeping, clearly you're not gonna see/feel the notification coming through.

Take like 5 minutes and clone your alarms from your phone to your watch.

Samsung also likes money, they much rather you have a Samsung phone too :D

You could also use some third party alarm app, like Sleep as Android which sets off an alarm both on your phone and your smart wearable (if you so desire).
[Samsung Galaxy Watch] thanito:
You are right, but if I clone the alarms then I will have to switch off twice the same alarms each time they trigger, once on the watch and once on the phone, fir each of the alarms, a bit counterintuitive don't you think?
[Samsung Galaxy Watch] Lada333:
It'll be sure to wake you up ;)

Also, you might wanna install a Samsung Clock apk, see if the integration with the watch works any better
[Samsung Galaxy Watch] TBBTNut:
I have the same issue with my Galaxy S10+ and my Galaxy Watch Active (SM-R500) since I changed from the Samsung Clock app to Google's own one.

Yes I can set alarms directly from my watch, and I usually wake up to them but I work shifts so often have to get up at 4am for work at 5:30.
[Chromebooks] vladone97:
Is there any way to root the Android subsystem on FydeOS? I'm new to Chromium OS and I don't know all the ins and outs. I do know, however, that there's this way to root Android on Chrome OS. Does it also work on FydeOS? If not, is there any other relatively simple way to root?

I tried to run sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions $(( $(rootdev -s | sed -r 's/.*(.)$/\1/') - 1)), but I got a message saying that I don't have developer firmware.
[Android Q&A, Help & Troubleshooting] anasDaw:
Hi, when i want to add multi-user feature on my phone using build prop (fw.max_users = 3fw.show_multiuserui = 1) when the first reboot, it doesn't work, and these words disappear from buildprop as nothing happened, is there a solution?

SM-G610F

BLACK BIRD ROM V5.1"pie

MAGISK
[OnePlus 6 Questions & Answers] CassieTheGeek:
after updating to pie some of my apps (Google photos, xda labs, edxposed manager) can't save files. other apps (like Chrome) can save files without issue. I've checked and all of them have storage permissions on.

I've tried uninstalling magisk and edxposed and neither helped.

I'm not sure what else to do other than a factory reset, which I'd like to avoid.

if I can't get this fixed can I downgrade back to oreo?
[OnePlus 6 Questions & Answers] brashmadcap:
You have to wipe data in TWRP

That's how I've solved this same problem
[OnePlus 6 Questions & Answers] CassieTheGeek:
i did that and now i keep rebooting to twrp :/

edit: fixed that by restoring a backup (i'm an idiot and forgot to turn off passcode) but i'm still having issues
[Google Pixel 4 XL Questions & Answers] graffixnyc:
I'm coming from the Pixel 3 (not XL) and just got my 4XL today. I noticed my 4xl's display is not as saturated as my pixel 3's. Anyone else coming from the Pixel 3 notice it as well? I know the smaller pixel 3 had an LG panel and the 4 XL has a Samsung panel so I'm sure that's why but looking at them side by side, my 4 XL's colors look more washed out. It also doesn't seem as bright as my pixel 3's
[Google Pixel 4 XL Questions & Answers] autobot7957:
Yes! I noticed and also slow motion have so much grains not pretty clear.
[Google Pixel 4 XL Questions & Answers] Demolition49:
The screen is great on my 4XL, I've had all generations of the pixel phones (XL variants), the only real disappointing screen for me was the 2XL. If you are getting noise or grain on your images, that is probably due to low light situations which is to be somewhat expected. The 4XL has a very decent panel, the only thing it might lack is a bit of extra brightness.
[Google Pixel 4 XL Questions & Answers] EeZeEpEe:
Are both phone's colors set to the same option? Natural, Boosted, or Adaptive?
[HTC Vox] scypax:
hi!

i'm new to this forum and i managed to boot windows 1.01 with the help of pocket DosBox.however,i can't get anything else to see but the background colour.

also i managed to get commander keen 1-6 installed and working(although newest versions crash after some time)

alley cat which works extremely well(not at all wondering myself because it's a low resource game)

i couldn't run duke nukem1 it says:

"dos/16m error:[15]protected mode available only with 386 or 286"

borland pascal 7.0 doesn't work also (why????) it says:

invalid opcode at 125d 0de6 f200 00c6 ....and so on

has anybody tryied anything like this on his vox?

i forgot to say that i use dr.gonzo's guava rom flashed after i got sick and tired of orange's romanian rom...
[HTC Vox] secosan:
sounds fun, can you post some donwload links?
[HTC Vox] scypax:
sure here they are:

dosbox for smartphone:http://www.pocketdos.com/

windows 1.01 and other oldies to be found here:http://www.vetusware.com/download/Windows 1.01/?id=3642

you will need to extract the image with win image ;copy it in a folder and access it via pocket dos

doom:http://www.olddoom.com/home.htm

borland pascal:http://darkbyte.evonet.ro/pascal.html

windows 3.1 and windows 95 will follow in my tests
[HTC Vox] ifxbr:
Forget about it. PocketDOS emulates the XT systems with VGA display. I ran it on my QTEK 9100 and I could run MS-DOS 6.22 and Windows 3.0

Windows 95 requires 32 bits systems and it does not run on PocketDOS.
[HTC Vox] scypax:
then what other dos emulators are there to suport win 95?
[HTC Vox] secosan:
thank you scypax
[HTC Vox] scypax:
you're welcome.if you have any questions post them here
[Xiaomi Redmi Note 7 Questions & Answers] mbwf:
Hello :)

I'm new to Xiaomi. Please would someone explain the purpose or meaning of the 10-digit hex string which is appended to the end of the filename for a Xiaomi OTA zip or stock firmware, for example (in red):

http://bigota.d.miui.com/V11.0.5.0...._global-V10.3.13.0.PFHINXM-V11.0.5.0.PFHINXM-c65aedb356-9.0.zip

Thank you so much. Have a lovely weekend.
[OnePlus 6 Questions & Answers] s3nn4:
I don't know why but after installing the last beta+magisk some fonts are bugged as hell and i can't get it to work

[IMG="Scuffed font"]https://prnt.sc/po9jjw[/IMG]

, any hints?
[OnePlus 6 Questions & Answers] Azhar_Fahry:
are u on modded font before u upgrade to beta ?

are u on magisk ? if yes, try to use this magisk mod https://xdaforums.com/oneplus-6/themes/mod-pixel-2-sans-font-t3797613 maybe it could help. thx
[OnePlus 6 Questions & Answers] s3nn4:
Well, that actually worked, thanks a lot dude!
[OnePlus 6 Questions & Answers] Azhar_Fahry:
no problem dude. glad to heart that.
[OnePlus 6T  Questions & Answers] SkyLukewalker:
Phone: A6010

OOS: 9.0.17

TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6

Magisk: Magisk-v19.3

PC OS: Manjaro Linux with Android SDK tools

Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)

If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.

I've tried the following steps to troubleshoot:

1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img

adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery

adb sideload Magisk-v19.3.zip

Result: stuck at "bootloader unlocked" warning screen & enters bootloader

2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.

3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.

4. Rebooted into bootloader

fastboot boot twrp-3.3.1-8-fajita.img

copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img

reboot into Recovery & adb sideload Magisk-v19.4.zip

Same result as before, stuck at warning screen and then into bootloader.

5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.

The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.

Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.

At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.

Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.
[OnePlus 6T  Questions & Answers] SkyLukewalker:
Thank you for the reply.

At this point, I'm kinda resigned to losing all data, so i did a backup this morning. However, I need my phone to be functional over this weekend, and will do as you have suggested on Monday after another backup.

Will start with the Format Data in TWRP method first, since i'm running Linux and have to setup a VM with USB passthrough to run Win7 and Msm.

Just to confirm, since i'm already running 9.0.17, is it okay simply to use MsmDownloadTool v4.0.59 if it comes to that? Thanks in advance.

On a sidenote, since data loss is inevitable, once it's confirmed that the phone boots up correctly with root and stock OOS, it may just be worth moving to LOS16 thereafter.
[OnePlus 6T  Questions & Answers] SkyLukewalker:
I had time today, and tried Format Data. Didn't work. Installing Magisk landed the phone in the same error screen.

So the Win7 VM was fired up and the instructions for Msm were followed. The phone is recognized and the drivers were successfully installed, showing up as Qualcomm HS-USB QDLoader 9008 (COM3)

However, when MsmDownloadTool V4.0.59 -- 9.0.16 was launched and Start was pressed, the operation times out with the message "Sahara Communication Failed. Please try again after power off phone."

This is despite powering off using the normal method within OOS itself, or powering off from within TWRP.

Not sure how to proceed. Please help?
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
Could be an issue with the VM. I'd also try to change USB Port or try another Cable.
[OnePlus 6T  Questions & Answers] elSkelet:
Why are you using TWRP from OP6 so old too? Here for OP6T there is newer https://github.com/engstk/android_device_oneplus_fajita/releases/tag/v9.101
[OnePlus 6T  Questions & Answers] SkyLukewalker:
I have updated to the latest TWRP as you have mentioned. The issue still persists when Magisk is installed. Once again, Magisk had to be uninstalled before the phone would boot up properly.

I tried with 2 different USB ports today. Tomorrow i will reboot the VM, remove the driver, let it re-discover and install the driver from MS (i installed a pre-downloaded driver today) and try again. The cable is the original one that came with the phone, and another one will need to be purchased if the efforts fail. Hopefully it is just the VM acting funny.
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
No that won't be necessary. As the drivers can't be downloaded from MS. Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. Also, I'd look into getting a Windows Laptop if it doesn't work. As MSM is known to have issues with VM.
[OnePlus 6T  Questions & Answers] SkyLukewalker:
Yes, i have twrp-3.3.1-x_blu_spark_v9.101_op6t currently installed without Magisk. Will do as you have said tomorrow, since i have also downloaded the full 9.0.17 OOS zip file.

Since budget is very tight at the moment, i will look into borrowing a Windows PC/laptop for awhile to use Msm if the other methods don't work.
[OnePlus 6T  Questions & Answers] xRogerxC:
Wait, wouldn't flashing back to 9.0.17 lock your bootloader? Then you can't enable OEM unlocking, which means you can't unlock the bootloader. You would need to flash MSM 9.0.11 to enable OEM unlocking, then unlock the bootloader before proceeding further. I'm no expert, just thought I'd mention it. Best of luck!!
[OnePlus 6T  Questions & Answers] SkyLukewalker:
Didn't seem to be an issue, worked correctly and the bootloader remained unlocked.

This worked, and now the phone is booted up into the system WITH Magisk 19.4 installed. Thank you very much! I didn't have to use Msm.

The steps for anyone else facing the same issue that i did:

Reboot into Recovery. This can be done via long-press power button in System and pressing Recovery if TWRP is already installed, or adb reboot bootloader to reboot into the bootloader, and fastboot boot recoveryImage_Filename.img (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.img)

Enter password/pattern to unlock

Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip (in my case, it was OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905.zip)

Back

ADB Sideload -> adb sideload TWRPzipFile_Filename.zip (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.zip)

Back -> Back Arrow

Reboot -> Recovery, and wait for phone to reboot into Recovery

Enter password/pattern to unlock

Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip

Back

ADB Sideload -> adb sideload TWRPzipFile_Filename.zip

Back -> Back Arrow

Wipe -> Format Data -> type "yes" and click the blue tick "Enter" key on keyboard.

Back Arrow to Main Screen -> Reboot -> Recovery, and wait for phone to reboot into Recovery

Enter password/pattern to unlock

Advanced -> ADB Sideload -> adb sideload MagiskInstaller.zip (in my case, it was Magisk-v19.4.zip)

Back -> Back Arrow

Reboot -> Power Off to completely power down.

Long-press power button to boot the phone. The issue of being stuck at the bootloader unlocked warning screen was gone. The phone booted into System with Magisk Root installed and working.

Later today, I will install LOS16 with Magisk and report back on how that went. Once again, much gratitude and appreciation to Mannan Qamar for the solution!
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
Glad to know it worked. MSM should be a last resort but most people use it as a first option to Nuke their phone. And if you want help on installing ROMs, don't hesitate to ask.
[OnePlus 6T  Questions & Answers] SkyLukewalker:
LOS16 was installed successfully with Magisk and i spent nearly 7 hours setting up the phone since opbackup could not be seen by OnePlus Switch, and i had to do everything manually.

Suddenly the screen started flashing all sorts of colours. I rebooted, and the same problem came back, i.e. stuck at the warning screen.

So, i used the instructions you provided and got OOS 9.0.17 booted back up with Magisk 19.4. However, when i try to connect to the phone via USB, even with debugging enabled, the internal storage cannot be read. Says "enable MTP." This is also happening in TWRP even after disabling and re-enabling MTP.

How do i get the phone to see the internal storage again? Please help.