yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] syedfaraz5:
Hello everyone,

i am using this stock rom on S7 edge i am not sure which version of s7 edge is this mobile as the back glass is changed and this rom is installed and this rom is very laggy on s7 edge so any recommendations on which stock rom should i use to speed up my phone and to make it work lag free.

also i want to know

every time i search for a stock rom i find XAA,XAS AIO, and BST versions , what is the difference between them ?

thanks.
[Mogul, XV6800 General] 3boos:
I had a problem with my Mogul, so I sent it to repair, meanwhile I switched back to my old phone Samsung SPH-A940 or sometimes it is called MM-940, I know it is not a Windows Mobile phone, but back in the days I had purchased like more than 20 games and applications that runs on the the phone which I think runs on Java, my question is:

Is there any way to extract these games so I can try them on my Mogul when I get it back? Or there is no need to bother they will not work!

I downloaded the driver from Samsung web site and I do not see the phone or any indication that it is connected to my PC except the sound of a new hardware being connected and disconnected!!!

I tried to send them using blue tooth but the phone does not give me the option of doing that!!

I am guessing that they might work sice the mogul has Java installed!!

any ideas?
[T-Mobile LG G3] Canthovan:
I attempted a downgrade to an older version of twrp via twrp in recovery mode. Not sure what I did wrong. Now my LineageOS hangs at the LG logo at startup. When I try to access TWRP using recovery mode, the LG logo flashes on and off (loops). I cannot access the LineageOS to enable debugging, OEM unlock, MTP USB mode, etc...

From a Windows XP SP3 desktop:

I can manually put my D851 into Download mode and can get from Download mode to firmware update mode when connected to a Windows XP computer. The Windows XP computer sees the phone as new hardware ("LGE Android Net MTP") device when connected in Firmware Update mode. In Firmware Update mode, I cannot properly access the phone using the LG PC Suite, ADB/fastboot tools, etc...

I have tried installing various versions of the LG United USB drivers. Originally, the driver installs failed citing "Windows MTP driver" not found and advising me to install Windows Media Format Update. After learning Windows Media player contained the Windows MTP driver, I installed Win Media Player 11. Now the LG United driver install fails but without mentioning missing Windows MTP driver or Windows Media Format 11 runtime updates. I have tried installing the USB drivers using LG PC Suite but it too fails when reinstalling the driver. LG PC Suite cannot connect to my phone. . Ihave tried to install the LGMobile Support Tool (ie. LGMobile Phone Software Update Tool), but the install seems to hang.

I feel that if I could just get a computer to communicate properly with the phone while in Firmware Update mode, I should be able to restore my phone. Does anyone have any ideas on other things I might try?

Thank you
[T-Mobile LG G3] IssacZachary:
I got stuck in that same boot loop as you. There's a thread that claims that the D851 is unbrickable: https://xdaforums.com/tmobile-lg-g3/help/lg-g3-d851-unbrick-qualcomm-9008-t3430221 But I was also unable to get it to work on my laptop. I think some computers may have a hard time using the drivers correctly and maybe trying another computer is your best bet.

But personally, I ended up sending mine to a J-Tag service on eBay and paying some $30 to get the thing completely reset.
[OnePlus 7 Pro Questions & Answers] besimply:
Hello,

I had now the Open Beta of Android 10 running since yesterday morning. I updated from stabile to OB1 with the image from oneplus 7 pro. Today after I used Android Car the phone changed randomly settings. So I tried to restart the phone but I came only to this error message:

QUALCOMM CrashDump Mode
————————————————

Fatal exception
die
PC at:arm_smmu_context_fault+0x910/0x918

The phone stays in this error screen. Does someone know how to exit this screen?

Thank you,

bs
[OnePlus 7 Pro Questions & Answers] Krsmqn:
Have you tried a hard reset? Hold power and volume up till it boots
[OnePlus 7 Pro Questions & Answers] besimply:
Awesome hint it works now again, thank you Krsmqn. Do you know how I can See what was the reason for that issue?
[OnePlus 7 Pro Questions & Answers] Krsmqn:
Happy to help. And honestly, I have no idea where to start.
[MTCD Android Head Units General] Forester_Diesel_CVT:
Hello,

i own a Forester MY17 Diesel CVT and bought a Dasaita Max6 PX6 4/64GB Headunit.

During installation i noticed that the delivered USB-Adapter is wrong - it's for the older Forester without Starlink System.

.........i had to cut the red&black wire on the single USB harness because the USB ports of the car are now powerd by the car not by the unit.

If you don't do that it causes an short circuit and the unit will not boot!!

After that everthing runs fine.........

........until i drive a while - then the rear cam stopped working - only the black screen with the yellow sign.

You all know that - or not??

I had a lot of emails with Dasaita about that problem, but that was wasted time (sorry Bryce & Iris).

Now i had a few days off and time to fiddle around with the unit.

I figured out that before the rear cam is not working you get the black screen with sign when you only mirror the front cam!!??

So it's a calculating issue and that is caused by temperature!

I disassembled the PX6 board and its heatsink and noticed there is a termal pad between but without pressure marks on it.

......so the gap is to big!!

I lowered the "feets" of the headsink and put a good (12W) termal paste between.

Then i installed an aluminium headsink also with termal paste.

.......that gave me some more minutes but was not solving the problem at all.

So next i installed a fan and wired it to ACC & GND.

.........now everything works fine no matter how long you drive!

I orderd an other fan with only 10db, hope then everything is quiet!

Sorry - i can't show you pics, because i'm a new member and not able to add links!!

Best regards
[MTCD Android Head Units General] Forester_Diesel_CVT:
........now pics added!!

Best regards
[MTCD Android Head Units General] ciccimatt:
Great job!
[MTCD Android Head Units General] Forester_Diesel_CVT:
Hello,

today the new fan arrived!

Now all is installed like i wanted it to be......

The fan i ordered.......

.......installed and wired.......

.......and at last the cover!

It works great!!

You have to put your ear direct on the unit to hear the fan - but still very quiet.

When you sit in the car only the fan running you can't hear almost nothing - i love it!

Best regards
[MTCD Android Head Units General] Kambrium:
Probably a stupid question, I know, but how did you manage do get a hole into the metal coverage?
[MTCD Android Head Units General] ~zATBz~:
I have the same unit in my car. :cool: Installed it a few days back. So it's fairly new but working good with no modifications.

For a backup camera. I retained the factory installed one "Mitsubishi" And it seems to be working great with no issues so far. Other then I need to be able to adjust the grid lines that are being produced by the headunits software. :laugh:
[MTCD Android Head Units General] Forester_Diesel_CVT:
Hello,

...i drilled four 10mm holes in the corners, saw it out with a jigsaw and the little rest with a file by hand.

Best regards
[MTCD Android Head Units General] Forester_Diesel_CVT:
Hello,

......i think it depends to the dashboard and how the heatingsystem is installed.

And the system updates do the rest - the stock system did not caused so much heat, every update it's getting worse....

Best regards
[MTCD Android Head Units General] chrispitude:
Nice work!

Did you communicate the root cause back to Dasaita so they can address it in future software/hardware revisions?
[MTCD Android Head Units General] ~zATBz~:
This makes sense. Hotter location would equate to more problems. My unit is installed just below the air conditioning vents. Will be interesting to see what happens in the winter time when hot air comes through the vents vs cold.
[MTCD Android Head Units General] simplyshrey:
How did you manage to reprogram the grid lines cos I installed the same unit on my Mitsubishi, but grid lines are missing .
[MTCD Android Head Units General] marchnz:
Cabin temp will be about the same at a guess.
[MTCD Android Head Units General] Forester_Diesel_CVT:
....yes, but not under the dashboard!

The air can not circulate under the dashboard, that's the reason why my passive heatsink didn't worked!

The Subaru HU has a fan too - think they did the same conclusion.

Now with the fan i drove 400Km highway today at 29°C outsidetemp and soc & gpu are at 35°C.

On normal days without AC they are about 30°C.

Fan is always running!

Best regards
[MTCD Android Head Units General] ~zATBz~:
I'm actually still working on grid lines. :) the newest rom gives you 4 options for grid lines inside settings/car settings/extra settings/show grid ruler. The lines work but I'd like to customize them and make them perfect. They are just a picture file. Figure I'll make a custom lines. Once I get some time.
[MTCD Android Head Units General] Forester_Diesel_CVT:
Hello,

......take a look - standing one hour in trafficjam on highway at 29°C outsidetemp.

DAB+, Navigation, Blockada, CPU-Z and Netflix running

Best regards
[MTCD Android Head Units General] New guy 123:
Great job! I might try this. Stupid question. Should the fan blow down on the chip/heat sink or draw air up away from it, thanks
[MTCD Android Head Units General] Forester_Diesel_CVT:
Hello,

.......the fan blows to the heatsink.

Between the fan and cover i have a gap about 1mm to prevent noise,

best regards
[MTCD Android Head Units General] trulu:
Hello, did you install the heatsink or is it came from the factory?
[MTCD Android Head Units General] marchnz:
All that matters is airflow.
[MTCD Android Head Units General] Lprx:
Did you screw the fan into the heat sink?
[MTCD Android Head Units General] danimop:
I have the same question. It is not clear from the pictures where it is screwed into.
[MTCD Android Head Units General] ata7676:
i have problems with freez can you help me? i need a update but i can not find everything
[MTCD Android Head Units General] schariwari:
He everybody.

I´ve bought an Dasaita Max 6 1Din Device.

I am in trouble about the reverse cam.

Witch yellow chinch plug is the right.

I used the Cam Vin and the Canbus Reverse Wire is connectedwith the Radio "Back" wire.

Nothing happend while switch gear to reverse.

I used my gauge to confirm the 12V+ while switch to reverse . 12v on Camera/and on the "Back" wire

If I change the Chinch to FCam and start the app on the Radio.. everything is fine. Best camera picture quality.

Is there a hidden Menu to activate switching to Cam Vin if there is 12v on the "back" wire ???

THX for every help.
[MTCD Android Head Units General] ode_joy:
There os the Factory Settings, which has the option for Reverse Câmera.

Try to confirm if it is marked. :)

Enviado do meu Nokia 6.1 através do Tapatalk
[MTCD Android Head Units General] dafunky:
Thank you for the feedback. I plan to screw a spare copper heatsink with a silent fan. I think I'll remove the top metal cover, so that the head unit get fresh air.
[MTCD Android Head Units General] cflaviu:
Hi there,

I recently noticed my PX6 unit doesn't see any of the front / rear cameras. With all wires connected the f-cam app shows the orange triangle (no signal) for both front and back cameras. The same happens if I give a 12v signal to the reverse (pink) wire.

I never got to install the backup camera in my car but I did bench tests with a power source and had the cameras working when I first got the unit. Now, a few months later, the cameras simply don't work

I tested with 2 different cameras and also with a DVD player and none worked.

I even opened the unit and checked the motherboard to see if there is a fried circuit or IC...and saw nothing. The video inputs lead to a IC labeled "FMS6502" and the signal gets to it through a 75ohm resistor and a capacitor which both look okay.

What can it be?

Please give me your opinions on this as it drives me crazy !

Thank you!
[Essential Phone Questions & Answers] thetrickster213:
Last night, I downloaded the Android 10 full factory image file from the Essential Developer portal, extracted it (with platform-tools up to date in the same folder), and flashed it to my Essential. When I turned on the phone, and after it booted up, a random QR code was shown on the screen, and Bluetooth kept stopping over and over again. I then proceeded to downgrade to Pie and update to A10 via side-loading an OTA. The QR code randomly appearing as well as the Bluetooth issues seemed to be resolved. Anyone know what that could have been? Maybe a corrupt modem flash? Let me know if you had the same experience. Thank you.
[Essential Phone Questions & Answers] mruno:
what system image were you running prior to the upgrade to 10?
[Essential Phone Questions & Answers] ktmom:
Any chance this has to do with the new Android 10 feature where you can generate a QR code with the credentials of your Wi-Fi network?
[Essential Phone Questions & Answers] IronRoo:
That would be my bet
[Google Pixel 3 XL Guides, News, & Discussion] BigOkie:
So the 3A and 3A XL aren't affected? I have 10 on mine now after sideloading the OTA last night and aside from the 20 minute reboot cycle, I've seen no problems as of yet.
[Google Pixel 3 XL Guides, News, & Discussion] nikhilnangia:
No idea about the other models. I've just posted the ones that I could find on forums, including mind (3XL).

There is something in common here for everyone that we seem to be missing. In the interest of getting to the root of it, I am posting my pre-android 10 update configuration:

Pixel 3XL, hardware model MP1.0

Rooted with magisk 19.3

Recovery: TWRP

Kernel: Kirisakura Kernel v3.4.5

Magisk modules installed: youtube vanced, busybox, energized, systemless hosts, zRAM/ SWAP manager to enable zram

Apart from this, I had naptime installed working in root mode

And tweaked a few kernel settings: color settings, changed scheduler for graphics, zram compression algorithm and I/O scheduler.

Anyone else facing this problem see something in common?
[Google Pixel 3 XL Guides, News, & Discussion] i42o:
That is sooooo weird... I've never seen that on my phone
[Google Pixel 3 XL Guides, News, & Discussion] alpinista82:
I would rather say this is related to the bootloader that after flashing beta 6 doesn't get downgraded when returning to an older beta version or even Pie. Since only a part of the users is affected I would guess that a specific hardware revision doesn't play nice with Android 10. As I am not affected I can't do further testing and you should take what I wrote above as an educated guess ;).
[Google Pixel 3 XL Guides, News, & Discussion] nikhilnangia:
Thanks for the ideas! I can confirm that the hardware version is not the problem since some others with the same hardware version as myself (MP1.0 - which can be checked on About Phone->Hardware) do NOT face this issue.

As far as the bootloader goes, that's certainly plausible. [MENTION=1615926]ultimatepichu[/MENTION] and [MENTION=4695495]FcukBloat[/MENTION] has any of you tried this? i.e change the bootloader version to an older version and flash 10?
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
the first thing in flash-all is to send the bootloader to the phone . But even if the bootloader is not downgraded, then I should get sensor problem in Pie as well right?

But no, I didn't try what you said.
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
After majorly screwing up my first attempt to jump from Pie to 10, I finally made it, and sure enough, I am a victim of this bug as well.

On an unrelated note, for the Magisk users out there, attached is the patched boot.img across 4 RAR archives for the Pixel 3 XL 10.0.0 (QP1A.190711.020, Sep 2019) image to save you some time making one yourself.

The SHA-256 hash for the image contained across the archives is:

dbdc828777fd8b734986998d0732c1c4e3e565fc66499c310f3a23c85abe383b
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
Just listening... can't figure this one out too...in the GSI build I found a Qualcomm driver for sensors for Crosshatch, but I don't know how to flash it, downloaded the bin and Qualcomm installer but afraid to go thru it might kill my phone. I do an average a day of flashing, my phone might get crazy???

---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------

Me and FCUCKBloat has been discussing this since beta 6 came out. All my sensors used to work on beta 5, with kernels and TWRP installed, but after I tried flashing custom ROM and eventually beta6 came out flashed it thru fastboot, regular update and so on, sensors won't worked anymore. So, I decided to go back to beta 5 but sadly sensors don't worked anymore, when it used to worked before.:crying:
[Google Pixel 3 XL Guides, News, & Discussion] saxmydix:
This happened to me since Pie. And Google seem doesn't do anything about it.

httpss://support.google.com/pixelphone/thread/3086868?hl=en
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
installed the GSI BUILD 10 from google and all sensors are working, flash it came from Bootleggers ROM. The only thing I can't find is the gesture Nav, maybe someone can help me activate it, so far all the sensors, dark mode are working.
[Google Pixel 3 XL Guides, News, & Discussion] FcukBloat:
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!

tia :o
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
yup

---------- Post added at 01:55 AM ---------- Previous post was at 01:54 AM ----------

copy your storage first on a computer

---------- Post added at 02:07 AM ---------- Previous post was at 01:55 AM ----------

well flashing to official 10, sensors stop working again...what the, i will try to factory reset
[Google Pixel 3 XL Guides, News, & Discussion] FcukBloat:
would like to try to replace the system and vbmeta images in stock Q with the ones in the

GSI package, but in GSI we have a single system.img file while in stock Q there are two (system.img and system_other.img) so don't know how I could do :(

alternatively I could try just fastboot flashing system and vbmeta images from stock Q, but again I wouldn't know how to manage the two system images... :silly:

---------- Post added at 08:30 AM ---------- Previous post was at 08:11 AM ----------

@imna357 I can't erase system and install GSI system image, I go in bootloader (fastboot mode) and i can flash vbmeta image, but when I try to erase or flash system image, it says this must be done in fastbootD...

>fastboot flash system system.img

Invalid sparse file format at header magic

Sending sparse 'system_a' 1/9 (261528 KB) OKAY [ 6.370s]

Writing 'system_a' FAILED (remote: 'Partition should be flashed in fastbootd')

fastboot: error: Command failed

:silly::confused:
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
this thing happened to me last night, if you can't erase the system it will not go thru, but after flashing bootleggers then let it settle with magisk, reboot to bootloader, it worked

---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------

were you on pie rooted?

---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------

ok, your on Q, will not work, last night I was on Q it did not work, need to be on PIE...sorry busy flashing my phone back to bootleggers, will try the TREBLE ROM tomorrow
[Google Pixel 3 XL Guides, News, & Discussion] billyt1:
I came from pie rooted avb and encryption disabled an took the ota when booting it said it was corrupted had to factory reset booted and worked fine all sensors any way except the mobile data sucks worse but I'm on Google Fi in East Tennessee. Also there's 2 builds for Android 10 on the dev site maybe try both builds and worst case scenario go back to pie and disable avb and encryption then set phone up then try taking the ota.

To disable avb and encryption boot to twrp then advance wipe,format data then sideload this zip and flash then reboot.

https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
[Google Pixel 3 XL Guides, News, & Discussion] saxmydix:
Damn, thats a good news. Would be great if anyone using blueline without the problem share their persist.img.
[Google Pixel 3 XL Guides, News, & Discussion] alpinista82:
I don't know for sure, but the defunct sensors issue should be completely unrelated to possible issues resulting from a dirty flash.
[Google Pixel 3 XL Guides, News, & Discussion] FcukBloat:
guys you are awesome! thanks to all who contributed, you did very than Google staff lol :)

will this work for blueline as well? or blueline need a different image?

ps. so knowing the solution you can guess what broke things for us? just out of curiosity!
[Google Pixel 3 XL Guides, News, & Discussion] bggold:
I updated my original post with instructions with the link to the persist file.
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Yeah that's what it sounds like to me as well. Especially if the issue is limited to the persist folder. Perhaps [MENTION=5437072]bggold[/MENTION] said it that way to discourage people who don't have backups from trying to dirty flash a downgrade to Pie?
[Google Pixel 3 XL Guides, News, & Discussion] bggold:
Actually I was following the original instructions that stated clean flash. I am willing to try a dirty flash from Pie to 10 a little later for those that want to wait. Please reply if interested so I do not waste any time.

I will first need to flash 10 again to see if the sensors break again to be sure we get a valid test.

Thanks

---------- Post added at 11:11 AM ---------- Previous post was at 11:10 AM ----------

ALL sensors are working.
[Google Pixel 3 XL Guides, News, & Discussion] santod040:
https://xdaforums.com/showpost.php?p=80194778&postcount=46

0_0
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Don't worry about trying the dirty flash. I am currently restoring my Pie TWRP backup and will try it myself. I will post the results when I am done.

---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------

Too many posts to keep track of! Thank you very much.
[Google Pixel 3 XL Guides, News, & Discussion] slothdabski:
I now have sensor after flashing the persist.img!!!!

Can't test active edge on aosp tho

Have gapps working now

Default Launcher3 widget is fugly
[Google Pixel 3 XL Guides, News, & Discussion] apag96:
Here's what worked for me. I was on Android 10 (Pixel 3 XL) with broken sensors

1) Open root shell

2) dd if=/dev/block/sdf2 of=/sdcard/persist_backup.img

3) Download image from post #110 in this thread

4) dd if=/sdcard/persist.img of=/dev/block/sdf2

5) Reboot device

I didn't have to flash back to 9 get this to work
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
After flashing the persist.img file, I cannot boot in to either the OS or recovery. Doing a reflash. Since persist seems to, well, persist, I expect that after the second flash is done, I will be able to boot without issues.

---------- Post added at 02:58 PM ---------- Previous post was at 02:48 PM ----------

I can confirm that dirty flashing from Pie to 10 works!

Restore TWRP backup of Android Pie

Root with Magisk

Boot TWRP and flash zip

Flash 10 (clean flash not necessary)

Boot to TWRP

Download persist.img and copy to phone

dd if=WhereverTheFileIsOnYourComputer/persist.img of=/dev/block/bootdevice/by-name/persist

Flash 10 again (this step may not be necessary for you, but for some reason I was bootlooping after the persist.img flash until doing this)

If you want root on 10, reboot to the bootloader and flash the magisk_patched.img file that I shared on the first page of this thread

Reboot, and your sensors should be working!