yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] hksaaa:
Hello, whats the diffrence between double din and single din ( not talking about size)

for example

Newest Joying 7 Inch Double Din Car Stereo Apple CarPlay Radio Android 10

SKU: JY-UQ128N4GShip From: Chinese WarehouseCPU: UIS7862 12nm Dual ARM Cortex-A75 + Six ARM A55Ram: LPDDR4 4GB Rom:EMMC 64GBSupport Bluetooth, WiFi, DVR, OBD2, Back-Up Camera

www.joyingauto.com

Joying Newest CarPlay 7" Single Din 4GB+64GB Android 10.0 Car Media Player

SKU: JY-UQS03N4GShip From: Chinese WarehouseCPU: UIS7862 12nm Dual ARM Cortex-A75 + Six ARM A55Ram: LPDDR4 4GB Rom:EMMC 64GBSupport Bluetooth, WiFi, DVR, OBD2, Back-Up Camera

www.joyingauto.com

everything seems the same, i guess double din have better cooling for cpu?

are both of this unit use uis7862 cpu? is just says CPU: Octa Core 1.8GHz. 64-bit high-performance processor and support is not answering me, so if someone could help!

Thanks
[FYT Android Head Units] surfer63:
They are exactly the same. Cooling doesn't matter in this case. Just ask Joying which will fit your car better.

If I had the choice I would always go for the single-din unit if your car is not so big, as that means that the space behind your dashboard will not be too big either. With a few accessories it is really difficult to put everything in the dashboard.

Note that both units are 1024x600. For a 7" that is sufficient, but if you also have the choice for 1280x720 and you can afoord it, I would select that one.
[FYT Android Head Units] hksaaa:
Thanks for the answer, can you give me link for 1280x720 one? my size needs to be 7inch
[FYT Android Head Units] surfer63:
I don't know if there is one. I suggested to look for it (if you have ..). You have now selected Universal ones. Is your car type not supported?
[FYT Android Head Units] hksaaa:
i drive an old honda civic from 97 that have double din ( found picture on google as example) so thats why im using universal one, it dosent exist for my car, and there is no 7inch 1280x720 one on Joying site, but i dont know if there is some more decent brand that i could check?
[FYT Android Head Units] surfer63:
No there is not, but there is this one.

And you can search on Aliexpress.
[FYT Android Head Units] hksaaa:
thats for newer honda, it's not possible to find for my car since its old and thats ok since universal exist
[Mogul, XV6800 ROM Development] kflipproductions:
So the wheel on my 6800 is broken which means i can no longer silence calls. I use a dialer skin which only gives me the options to Answer or Ignore. I've tried setting 'Mute' and 'Volume Down' to a button, but no luck. anyone have any ideas on how i can silence my calls? or how to edit the softkeys so one is 'Answer' then the other is 'Silent' first then 'Ignore'?
[Mogul, XV6800 ROM Development] kflipproductions:
bump. anyone? 48 views and no one's got anything?
[Mogul, XV6800 ROM Development] dwizzy130:
When getting a call, scroll up or down with the side scroll wheel to silence it.

dwizzy130
[Mogul, XV6800 ROM Development] kflipproductions:
yeah......:confused:
[Mogul, XV6800 ROM Development] Scott:
Hmmm... Not sure this will work but maybe worth a shot. There is a program out there called AE Buttons Plus. It lets you assign nearly any function to any soft key or iteration of the same soft key (ex: press once vs press twice vs press three times vs long hold). It allowed me to do things like soft reset my phone if I held the end key for three seconds. It was cool but did sort hog more memory than I liked, maybe 1.5 megs of RAM.

Just a thought off the top of my head. Here is the link:

http://ae.inc.ru/aebplus.php
[Mogul, XV6800 ROM Development] kflipproductions:
cool thanks ill check it out. i might just get it replaced. i think the USB port is about to go
[Google Pixel 6 Pro] roirraW "edor" ehT:
New including my solution without wiping:

Old:

TL;DR:

​

Back to the details you may or may not want to know...

This is the corruption screen in question, it precedes the normal bootloader unlocked screen, but in this case, it always requires a manual press of the power button to proceed:

The g.co/ABH link takes you to Understand warning about operating system safety. It's not very helpful in my opinion as it doesn't tell a way to fix the issue without a full wipe. Below are the contents of the page:

Spoiler content hidden.

As you can see below, after flashing (but without wiping) I'm able to boot as normal (only tested with the stock February kernel, rooted with Magisk 24.1), with the only exception being the third screenshot from the top-left, about corruption, and requiring manually pressing the power button to get past the screen.

View attachment 5532145View attachment 5532147View attachment 5532149View attachment 5532151View attachment 5532153View attachment 5532155View attachment 5532159View attachment 5532157View attachment 5532159View attachment 5532181​
[Google Pixel 6 Pro] roirraW "edor" ehT:
In case I need this post #2.
[Google Pixel 6 Pro] roirraW "edor" ehT:
In case I need this post #3.
[Google Pixel 6 Pro] roirraW "edor" ehT:
In case I need this post #4. (Last one of these)
[Google Pixel 6 Pro] smurfmeat:
It happened to me once when I sideloaded January's OTA and a full wipe with the Android Flash Tool worked, manually flashing via adb did not. However, I got that corrupt boot screen when flashing February's update via AFT. It was worse trying to fix the problem this go-around because I wiped the phone multiple times via AFT with various options (wiped, disable verity, even relocked the bootloader and returned to stock). It finally stuck but I'm not sure what I did.

I tried all the suggestions on XDA and around the Internet but nothing helped. Closest thing I could figure out was maybe one of the boot slots had had encryption and the other didn't so the update failed? It sucked, because now I'm hesitant to flash any kernels or even a patched magisk image because that damn corrupt boot screen appears way too easily.
[Google Pixel 6 Pro] V0latyle:
Had this come up once on my wife's 5a.

This means there is dm-verity corruption:

Boot Flow | Android Open Source Project

source.android.com

Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.
[Google Pixel 6 Pro] Lughnasadh:
Copied and pasted (for the most part) from another post of mine:

"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."

See documentation below (which shows the warning sign in red but with the same message).

Boot Flow | Android Open Source Project

source.android.com

Verifying Boot | Android Open Source Project

source.android.com

EDIT: And Ninja'd by 1 minute by @V0latyle 😋
[Google Pixel 6 Pro] V0latyle:
Beat you to it, thanks for the additional explanation
[Google Pixel 6 Pro] Lughnasadh:
I edited my post to reflect your Ninja prowess 😅
[Google Pixel 6 Pro] shiftr182:
It happened to me back in December when I first got my P6P and was rooting it. I couldn't get it to boot though. I tried using the repair tool, but it wouldnt find my device. I tried manual flashing via adb, but it would fail. I was about to send it back to google when I figured I would try to switch boot partitions and that fixed it.
[Google Pixel 6 Pro] Nekromantik:
dunno how I got this message as I only got it after flashing a custom kernel which dev said includes the magisk version that does not veed verity disabled.

i hope in march ota when I flash that it will go back to previous boot slot it dont say that.

I will probably do a full wipe and flash when I get some time as the message is annoying as it adds delay to boot
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thank you! Sideloading just now didn't fix it for me. I tried it while I was already on the February full firmware.

Spoiler content hidden.

I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.

Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!

Thank you! I appreciate the details and the additional link to relevant information.
[Google Pixel 6 Pro] V0latyle:
Well, this is how things went wrong on my wife's Pixel 5a:

Restored boot image in Magisk, installed OTA. Rebooted. Successful boot, no root (because she rebooted it before I had a chance to install to inactive slot)

Switched active slot to the "old" slot. Bootlooped.

Dirty flashed January factory image on old slot. Verity EIO corrupt warning. Bootlooped.

Dirty flashed January factory image to both slots. Bootlooped, Rescue Party data corrupt warning.

Downloaded and dirty flashed February factory image to both slots. Bootlooped, Rescue Party.

Sideloaded the February OTA to the "new" slot. Successful boot. Attempted to live boot previously patched image, I believe January patched with 23017. Rescue Party.

Patched February boot image in Magisk Stable 24, rebooted to bootloader and live booted. Successful. Performed Direct Install in Magisk, and rebooted. Successful boot with root.

There is something to do with the OTA mechanism that will bork everything if you try to mess with it. I do know that if it doesn't successfully boot the updated slot, it will mark that slot "unsuccessful" and won't try to boot it again, and will then revert to the old slot. I don't know why it didn't just boot the old slot in my case.

Going forward, at least until we figure out the problem with automatic OTAs, the safest method of update is either dirty flashing the factory image (can use Android Flash Tool as well), or sideloading the OTA.
[Google Pixel 6 Pro] Alekos:
I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.

Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.

Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the 'device is corrupt' message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.

Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.

searching for 'corrupt' on reddit's GooglePixel sub shows this problem was mostly prevalent from November-December, Pixels 4-6.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Interesting experience. Thank you for sharing the details.

I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.

I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.

😂 LOL!!

Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.

My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!
[Google Pixel 6 Pro] Alekos:
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.

Also, your message is completely different than the one I saw. Mine looked like the attachment.

edit--

And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.

edit--#2--

shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!

edit --#3-- fixed link, woops thanks @roirraW "edor" ehT
[Google Pixel 6 Pro] roirraW "edor" ehT:
Very interesting. Maybe there's a slight difference in the cause or some other detail we don't know yet, since the problem on mine wasn't preceded by wired or wireless headphones being used. Very interesting! Your link "this" became garbled. Here's the fixed link. this
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's quite alright, not your fault. I've only recently started fooling with safe mode so it's still a slight surprise to me each time, but I think it won't stay a surprise for much longer. 🤣

You're welcome!
[Google Pixel 6 Pro] Guyinlaca:
I had this error after a non-wipe upgrade, coupled with bootloops. I had everything backed up so I did a complete factory image install and re-rooted. The phone runs like new again and all rooting conflicts are resolved.
[Xiaomi Mi 11] captain2k20:
View attachment 5532187

Hello since the update Android 12 I can not send pictures on telegram
[Xiaomi Mi 11] feng.zh.cfo:
Yes,same problem.
[Xiaomi Mi 11] Pho3nX:
Use Telegram X instead Telegram or do a factory reset from settings > security for fix storage issue
[Xiaomi Mi 11] Marrurk86:
A factory reset right after a fresh install fix all storage issues with A12. Not only telegram.
[Xiaomi Mi 11] Pho3nX:
It's for this reason i have write "or", he have choice to just install Telegram X if he want just fix his Telegram problem without all wipe "or" he can can do a factory reset for fix storage issue. :)
[Xiaomi Mi 11] 4r44444:
Factory reset or you will have the storage problems in every other apps too.

Factory reset inside android fixes the problem.
[Xiaomi Mi 11] alirahimianb:
Hi/ I have problem with enable Topics in a group in telegram, but In general, this option is not available for me on mobile and Telegram desktop, what should I do?
[Samsung Galaxy S20 FE Guides, News, & Discussion] lovesroni81:
How to use galaxy s20 fe duel sim slots, how do I access sim manager
[Samsung Galaxy S20 FE Guides, News, & Discussion] brianmolko1981:
Insert one sim in Slot 1 and another sim in Slot 2.
[Samsung Galaxy S20 FE Guides, News, & Discussion] lovesroni81:
I did that now what
[Samsung Galaxy S20 FE Guides, News, & Discussion] brianmolko1981:
Settings, Connectivity and there is SIM-Card Settings
[Google Pixel 6 Pro] jrg67:
I just got an update through the playstore of the latest version of Messages and now under Advanced settings, there is a blank menu option with a toggle that is on. It can be turned off but not sure what this is. I am not enrolled in beta for Messages. Anyone else see this? Could it be Google prepping for the iPhone reactions toggle?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Interesting. Could be, I'll ask my sister to text me directly at my real cell number (since I usually have her send to my Google Voice #). Tested it just now with my sister texting me; it's not the iPhone reactions fix for me yet. My Advanced page looks a little different from yours but could be related to other settings I have chosen. I'm on AT&T with a factory unlocked P6P. My Messages version # is 20220118_00_RC01.phone_dynamic. I'm on the February firmware.
[Google Pixel 6 Pro] jrg67:
Realized I forgot to include the version I'm on. Here's another screenshot
[Google Pixel 6 Pro] Deleted member 739586:
In my German app, this toggle is used for enabling the reception of service broadcast messages.
[Google Pixel 6 Pro] jrg67:
I have Verizon service with an unlocked P6P if that makes any difference.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm on the same version. My Messages version # is 20220118_00_RC01.phone_dynamic.

I'm on AT&T with a factory unlocked P6P.

I'm on the February firmware.
[Google Pixel 6 Pro] jrg67:
I am also on the Feb firmware. Must be something with VZW service adding those extra MMS settings in that I have.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, could be. My sister reacted to a text for me but I still got the "Laughed at..." blah blah blah. :D
[Google Pixel 6 Pro] jrg67:
Haha 😂 well I guess that's not it then.
[Google Pixel 6 Pro] cmh714:
That blank on mine says: Show iPhone reactions as emoji........having said that I am on the Beta....
[Google Pixel 6 Pro] therock3181:
I too have it and I'm in Canada. Disabling black theme didn't show either what is this.
[Google Pixel 6 Pro] cmh714:
most likely its what I wrote above your post....it shows on the beta
[Google Pixel 6 Pro] fuadhdmini:
View attachment 5532267
[Google Pixel 6 Pro] jrg67:
I just got another update but it's still blank. Version moved up to RC03
[Google Pixel 6 Pro] roirraW "edor" ehT:
Sounds like "Release Candidate 3" to me.
[Google Pixel 6 Pro] jrg67:
You'd think that would be the logical naming convention IF I were enrolled in beta. However, since I'm not and on the stable channel, you'd think "release candidates" wouldn't be what Google is pushing lol. Either their naming convention sucks or they literally have 2 beta channels. One where you know you're in beta and the other is the secret one to get wider testing via billions of unknowing users 🥸
[Google Pixel 6 Pro] Lughnasadh:
Think you are right. I'm on the latest beta 20220203_01_RC00

View attachment 5532313
[Google Pixel 6 Pro] foobar66:
Same here (language set to Dutch). 20220121_02_RC03.phone_dynamic version.
[Google Pixel 6 Pro] randylahey786:
Omg, why is this happening I'm noticing it now on my phone and it is the Worst!
[Google Pixel 6 Pro] Az Biker:
I'm on same version as OP and I neither have a blank space nor "show iPhone reactions as emojis"...

Interesting...
[Google Pixel 6 Pro] bobby janow:
Another well designed rollout from the folks at Google. You can't make this stuff up.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It wouldn't surprise me if the actual working iOS reaction option text will merely appear by a server-side switch.
[Google Pixel 6 Pro] Lughnasadh:
Good point. So many things are these days.
[Google Pixel 6 Pro] :
Me neither...
[Google Pixel 6 Pro] RetroTech07:
I didn't know this was happening with the iOS emoji switch. I'm so annoyed always seeing someone react to my messages and I get a dumb text about it, but thankfully now it'll show up as an actual reaction. Can't wait for this to be released.
[Google Pixel 6 Pro] RetroTech07:
I downloaded the beta and had a friend react to a message. It works perfectly lol so happy for this!

My only wish is being able to react to other users messages, and not having to use "chat features" in this app to do so.
[Google Pixel 6 Pro] jrg67:
Just an update on this.. that blank option is gone from my advanced settings menu. No new update or anything.
[Google Pixel 6 Pro] prohibido_por_la_ley:
Get over yourself.
[Google Pixel 6 Pro] bobby janow:
Did that years ago but thanks for your concern. You sound like a really nice person. Good luck to you. You're blocked.
[Google Pixel 6 Pro] RetroTech07:
Why can't folks play nice here? Smh
[Google Pixel 6 Pro] bobby janow:
Most often we do even in disagreement.. But once in a while folks just get a wild hair up their.. and then it all goes to crap. I just find it easier to block those that get like that rather than start a flame war..
[Google Pixel 6 Pro] RetroTech07:
So, the app now has two distinct menu options, although most settings are still accessible over in the top right. We now get a hamburger menu off to the left where you can access device pairing, theme, and inbox type.

The top right now allows us to switch accounts and access previous settings, but I've noticed we can now "pinch to zoom" on a conversation to make text easier to read, and get "reminder" notifications similar to Gmail, where the app will nudge you to reply to a message if it's over an hour.
[Google Pixel 6 Pro] erktheerk:
Could be a dev mistake. Could be random. Having transferred A LOT of data back and forth over the internet since the late 80s. 1.5TB just today on my home connection. My 2￠ is a reminder to check your files. If there is a hash provided, use it. If the file is critical go looking for one. I can't even count the amount of times I've verified and it didn't match. All it takes is a single bit to flip and ruin your whole day/week.
[Google Pixel 6 Pro] RetroTech07:
Has anyone gotten the actual stable public release s/w with iOS reactions yet? I keep reading it's rolling out and that US English users will get it first, but with each new Messages release, nothing has shown up.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I haven't.
[Google Pixel 6 Pro] cmh714:
I use Beta and have the iphone emojis and no blank spaces in my Advanced menu....
[Google Pixel 6 Pro] RetroTech07:
I was using beta as well, but stopped because I just want a stable release at this point. The Contact app was updated with new features and new menu, so I'm assuming messages is around the corner. I just wish they'd speed it up lol.
[Redmi Note 10 Pro] polyfrog99:
Hi guys,

I've unlocked my Note 10 Pro, and was trying to flash MIUI global 12.5.9 with XiaomiMiTool. However the tool got stuck half way and left me soft bricked.

It also throws an error trying to recover me from soft brick.

I have access to stock recovery and fastboot at the least. I've tried using the Mi flash tool, but it tells me 'Couldn't find flash script' or 'can not found file flash_all.bat'

And to be fair, there is not flash_all.bat inside the ROM folder. Am I missing something? Is there an easier way of doing this? At this point I just want to get any kind of ROM back on the phone. Help!
[Redmi Note 10 Pro] polyfrog99:
Hi all, I found what was stopping the Mi flash tool from working - I was using a recovery ROM instead of a fastboot rom. However, I've now got a new issue - even the latest ROM is giving me a "Antirollback check error" and won't start flashing. I'm trying to flash 12.5.9 global - how do I get around this??
[Redmi Note 10 Pro] polyfrog99:
Ok I got around this, if anyone has this issue what you have to do is edit the flash_all.bat file and take out all the top lines before the flash commands that check your version etc.
[Redmi Note 10 Pro] Supermatt01:
Use the newer update script in the old ROM folder
[General Questions and Answers] Chris de Savigny:
I am trying to instal a car DVR on PX Malaysk Rom but this is not working

anyone have any suggestions

the APK is installing OK but nothing happens when I try to open app

the app is XCDVR1 2.8.10 google store

Is it something to to with the stock Video apk that is in the Rom?

seems to work ok when connected to phone or tablet

Please help me
[General Questions and Answers] PocoF3:
Hello everyone,

I'm using gboard, however as this is too low at the bottom, it's difficult to type. Is there any way to lift this keyboard? Like this:

^I don't need another keyboard or a bigger layout.
[General Questions and Answers] Teddy Lo:
You have Settings button so press on that and adjust the way you like it....
[General Questions and Answers] PocoF3:
Up