yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Siafall:
@d5aqoep @badabing2003 try this link
[Google Pixel 7 Pro] roirraW "edor" ehT:
I confirm that link still only gives the v34.0.0 zip. Besides the same version number in the filename, I've checked the hash of the zip file, and it's the same as the 34.0.0 that was released on February 10th.

I have Aignes Website-Watcher set to let me know when the direct link below leads to an updated file:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

(https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip also gives a 404 error)

Thanks for the heads-up about the possible impending release, though. Hopefully it actually fixes all the issues everyone had with using 34.0.0 once it is made available.
[Google Pixel 7 Pro] Schroeder09:
The march update is Monday, right? Isn't this a quarterly release with some big big fixes and feature drops planned? I read on Android authority or some other outlet that the update was going to include a fix for the flashing and green screens many have reported.

Can we still just flash the update with platform tools 33? That worked fine for the February update. I don't wanna deal with update issues. That's always a bad day when those happen.
[Google Pixel 7 Pro] badabing2003:
Thanks, but just like @roirraW "edor" ehT I still get 34.0.0
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, the March firmware should be out this Monday, and it should be the Android 13 QPR 2 Final.

We probably won't know that for sure until it comes out, and someone tries to use 33.0.3 with it. The 34.0.0 Platform Tools hadn't come out yet when the February Stable firmware was released.

It can be hit or miss. Sometimes an old version works fine, and other times changes they've implemented in the firmware require the new Platform Tools to flash.

I'm usually busy, so I often don't flash the new firmware for several days. I also wait to hear if some root modifications I use need updated to use with it - which is more often the case with QPR FInals. So I'll be waiting to hear what others report. :)
[Google Pixel 7 Pro] bird333:
I have run into a problem. When I plug in my phone it detects as a "Pixel 7 Pro" not an "Android Composite ADB Interface". Ok so I select Pixel 7 and still update drivers. Ok now it does show as an "Android Composite ADB Interface". So I do the 'adb reboot bootloader' command and it takes me to fastboot, but now it's disconnected from the USB and I can't update the drivers to the "Android Bootloader Interface". Help!
[Google Pixel 7 Pro] cmh714:
maybe try setting your Default USB Configuration to No Data Transfer....just a guess to try...GL!
[Google Pixel 7 Pro] simplepinoi177:
When the P7P is in bootloader/fastboot mode, it will be identified as "Android Bootloader Interface" now instead of "Android Composite ADB Interface". So I'm thinking either you may be overlooking it as it is titled different, it is somewhat hidden for some reason, or it's coming up as something else (possibly "unknown device" or mis-identified as another device because it's using another driver) and you need to update/change the driver so it will load up as "Android Bootloader Interface". But try running fastboot devices to see if the USB is truly "disconnected" or if fastboot can still make commands (or it might call on the Bootloader Interface driver)...
[Google Pixel 7 Pro] bird333:
Thanks for the replies guys. I don't know what the deal was but it was not showing up. I entered fastboot manually by holding down and the power button.

1. Open Device manager

2. Turn phone off if necessary

3. Hold down volume and power button

4. After in fastboot mode plug in USB cable

5. The phone was detected as Pixel 7 in 'Other Devices' with an exclamation point.

6. Update the USB drivers and now it was identified as "Android Bootloader Interface"

Then I was able to enter the command to unlock the bootloader. It seems rebooting to fastboot from adb was not letting the usb detect the phone again for some reason.

EDIT: It was the damn Oneplus USB cable I was using. It wouldn't allow the phone to be detected while in bootloader/fastboot mode. I changed to a Samsung cable and it worked. WOW.
[Google Pixel 7 Pro] simplepinoi177:
i knew it had to be the Pixel 7 identified as something else vs. all of a sudden your computer not detecting it while detecting it for ADB...! I always hate when devices randomly get relegated to the "Other Devices" or identified as "unknown device"!:mad:

And then when it's something as "silly" as the cord?!?!? There are still cases where using a USB-A suddenly is best -- I've seen the same issue and reasoning all the way back to the Pixel 2! I would have thought something like that would've been worked out by now; especially considering how more prevalent and established USB-C is now (ports, various spec'ed cables, etc.)

Goes to show it's always good to check these minor things out; that although minor, they can be the root cause...!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I guess it's going to be one of those firmware limbo days. Might be an update today or sometime, who knows.
[Google Pixel 7 Pro] Lughnasadh:
Sir, I am too old to do the limbo anymore 🤷‍♂️🙃
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! Well, live and let live!

Spoiler content hidden.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Oddly, even though:

Pixel Update Bulletins | Android Open Source Project

source.android.com

doesn't show the March 2023 Pixel Update Bulletin, websites have revealed that it is available here:

Android Security Bulletin—March 2023 | Android Open Source Project

source.android.com

Still no hint of the actual firmware, however.
[Google Pixel 7 Pro] Ghisy:
Someone at Google fell asleep and forgot to push the button to upload the factory images it seems! 😅

I'm in no hurry though, I'm traveling so I won't update until this weekend probably.
[Google Pixel 7 Pro] thereason00:
Hey there.. My P7P shows as a Nexus 6P in Google One and in Find My Device, etc. but I've checked my ro.build.fingerprint via SetEdit and it's a cheetah (P7P) fingerprint. What did you actually do to get your device being recognized as a P7P again? I didn't see in any of these messages what was actually done to get it back to reporting as a P7P. Thanks!
[Google Pixel 7 Pro] badabing2003:
What Magisk modules are you using?
[Google Pixel 7 Pro] thereason00:
Shamiko, Systemless Hosts, Zygisk - LSPosed, and Universal SafetyNet Fix 2.4.0 MOD 1.2 by Displax.

I just installed that version of USNF yesterday to see if it would fix it, but it didn't. Before that I was using the regular kdrag0n USNF 2.4.0. When the phone just came out I tried all the USNF's that were coming out before the intial Displax MOD one that worked came out, so I don't know if that would have anything to do with it. I also might've tried stuff with Magisk Hide Props Config but would've reverted everything before I uninstalled it, I just can't remember if I did use it with this phone or just my last one at this point.

I also factory reset it and relocked the bootloader like a month ago for a couple days, but have since unlocked and re-rooted it, and I definitely have only had those 4 modules above installed since then, no MHPC. So I'm kind of at a loss here.

I normally wouldn't really care, but I now have two Play Store apps that are saying that they're no longer compatible with my device and I think it's because the Play Store thinks I have a Nexus 6P and the apps have discontinued support for devices that old or something. So I assume this is going to start happening to more apps as time goes on. So I'd like to avoid that :)
[Google Pixel 7 Pro] badabing2003:
What LSPosed modules are you using?

What have you set in Magisk Denylist

What have you set in Shamiko?
[Google Pixel 7 Pro] thereason00:
Hide Mock Locations is the only LSposed module installed.

I'm not aware of any settings I can change/set in Shamiko, I've just installed/enabled it in Magisk manager (v0.6).

I have 86 apps in my Magisk Denylist, are you looking for anything in particular? Most are bank/financial/smart home/social media apps, which I assume are inconsequential, but I'll list all the Google apps that I have checked. If you really want the whole list let me know and I'll type it out.

Google News, Google One, Google Opinion Rewards, Google Play Games, Google Play Protect Service, Google Play Services, Google Play Store, Google Podcasts, Google Services Framework, Google Wallet, GPay, Home
[Google Pixel 7 Pro] LLStarks:
I've become skeptical of Shamiko and switched to Magisk Delta hiding. Neither are open source or easy to audit.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Note that it can take some time after uninstalling one USNF, or installing another USNF for Google to change what it recognizes your phone as. So be wary of changing too much too often.

I don't remember if it also helped speed things up by wiping the Play Services and/or Store's cache and data, then rebooting.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google finally adds the Pixel 7, 7 Pro, and Pixel 6a to its ARCore support list

Google's latest update to its ARCore support list plays Pixel catch-up

www.androidpolice.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
[sarcasm]I love it when Google changes the "updated" date on their webpages, when nothing has changed other than that date.[/sarcasm]

At least five of their Android-related webpages now say:

But that's the only thing that changed. I've seen this on their webpages many times over the past year since I started monitoring more closely. That includes yesterday, when at least some were updated to say the 6th without any other change, so it doesn't even necessarily indicate an impending true update.
[Google Pixel 7 Pro] Ghisy:
What's funny (not really though) is that Samsung actually updated their flagship phones already!

Maybe Google discovered a last minute bug with the Pixel builds? Otherwise, I don't know why there would be a delay. 🤷‍♂️
[Google Pixel 7 Pro] LLStarks:
Going to be funny if we get another developer preview tomorrow before a stable release again.
[Sony Xperia XZ1 Compact Questions & Answers] strianugraha:
View attachment 5729479

Is there any fix to make yellow all these emoji?

Device Sony xperia xz1 compact docomo
[Sony Xperia XZ1 Compact Questions & Answers] Unreal_Hawkzz:
Without root:

Try installing official custom fonts for ur device...if not try installing custom text fonts/custom emoji font...custom emoji font should work...

With root:

Flash emoji magisk module n custom font module.

What you are facing is docomo emojis..(docomo variant of xperia ) i am facing same with docomo galaxy s8+
[Redmi Note 8 Questions & Answers] XSilverTH:
hi

so my rn8t doesnt turn on (i dont know if its a softbreak or hard break).

its unlocked i have pbrp on it and this happend after i tried to install a miui13 port for ginkgo on it

it turns on and immediately turns off. this happens in normal boot, recovery and bootloader.

i have no idea how to edl and would really prefer if i dont have to open the phones back for it

is there anyway to fix it without edl? if there isnt how do i fix it with flashing edl
[Redmi Note 8 Questions & Answers] XSilverTH:
bump
[Google Pixel 5a] norazi:
Hi guys, I bought a used 5a and am seeing a snapdragon logo (red/white circle) flash briefly at boot up right before the normal Google G splash screen and was wondering if this was normal for the 5a.

I have already tried flashing the lastest OTA (zip via ADB) and kernel (boot img) via fastboot after unlocking the bootloader just in case. I am worried about any potential malware and want the phone as factory stock as possible.
[Android Head-Units] Stefanek33:
Hi.

I'm quite new in this adventure (LOL)

I have a Belsee android 10 head unit connected to my sound system in a car with DSP and aftermarket amps and speakers (Mazda 6 2017)

a couple of things annoy me and I would like to ask how can I improve the android to work better? Which app I should install it?

Also, have a problem. Sometimes it freezes and has to restart it.

When I turn on the HU the original software is frozen for a while before he kicks on! Is there a way to fix this glitch?

Also what annoys me very much is when I switch off from the android to the normal Original Mazda mod screen Aux music stop playing. Is there something to avoid this?

Also I there anything to have a volume control panel where I can see how much I'm increasing volume? My system is quite loud and I have set the volume to not go above to prevent clipping or distortion and just wanna be safe. Unfortunately, I have to switch to the original OEM from android, the music stops, and then adjust the volume to see what level I am.

Also as the original OEM use a bose amp and now is obviously replaced with aftermarket amps i can't figure out why is my radio and CD/DVD player quieter then AUX output..Anyone knows, please?

I would really appreciate it if someone can give me the best tips and apps to improve the HU.

Thank you!!!
[Android Head-Units] eddotykc:
I also have a belsee android unit (on my mazda 3) with aftermarket subs, tweeters and connected to Bose system that has both the Mazda connect & Android o/s. I have experienced similar problems as you - sometimes the original mazda system takes forever to complete it's boot-up. I did upgrade to Mazda connect firmware 74 and that DID help (system responds faster and voice commands function much better) but it has some issues sometimes with the backup camera for some reason As far as the volume issue, i've found that if i don't use steering wheel control for volume but the knob on the center console i get a visual representation of volume from both sides.

You might check to see if your Bose Co-pilot and Centerpoint are disabled. I've found this levels out the volume a little better.

Do you have problems switching between the two o/s's - ie it's easy to get back to the mazda system by touching console favorites button or using the CarUI icon but going back to Android by swiping right hand side of screen doesn't work many times??????

I've also found that sometimes the Driver (left) side of audio on AUX cuts out as if it's not there and reserved for the voice warnings that occur and doesn't come back until restarted.

Does DSP work for you? I can touch the icon for it, it won't launch for me. Also radio is only available on Mazda side and app not there on android side.
[Android Head-Units] Stefanek33:
Hi.Thanks for your reply. I haven't hope anyone will answer!

I would like to update the firmware but I don't know how..Also, I was reading you can jump straight from android 10 to android 12 but i don't know how to.

I have still a problem with the reversing camera sometimes..

There is absolutely poor communication with the Chinese..Their English is like hello. connect to the original radio then ok?... So what the hell that means?!!!!

Also, does the volume button piss me off? Is there a way somehow with some app to get the volume from the OEM screen to transfer to the android?

Also, I have an issue checking the android for clipping by oscilloscope..My focal tweeters sound harsh and sparkling when I increase the volume...I don't know if there has to be a balance between the volume of OEM to volume on AU|X?I ws reading somewhere someone checks the original OEM for clipping and it says there is no clipping on full volume..I have to test it..The problem is I don't know whether to check the voltage from HU before the pre amp or after..I bought an adapter from amazon which on one end is a wire to strip in and another side is RCA female output when I'm running 8 wires into the DSP Focal and then to each amp.

About DSP in android ..Do not use this..Its a crap..I tested with a scope. It's clipping like hell and producing a lot of distortion.

But my main issue is the correct voltage output from HU because if you set the voltage in DSP software on a computer wrongly you by sending to the amps digital clipping....

About the Radio in android, i have only FM which i don't know why because i purchase DAB and install it..Also the DAB is very weak..it may be because of interference from somewhere..

I have as well the problem with the left door speaker cutting of few times..
[Android Head-Units] eddotykc:
Would love to move from android 10 to 12 - have you found firmware file to do it?

I actually changed out the back-up camera for a third party model that i can choose from six different views and it works great with both the mazda connect and android.

On the distortion issue, have you checked all the wiring behind glove compartment and heat unit to make sure there isn't a wire exposed potentially causing the distortion. I had a problem on the rca going to an under-seat sub sounding like crap until i wrapped the left and right as they came out of the PAC AOEM line-out converter and ensured it ran opposite of power/ground wiring.
[Android Head-Units] Stefanek33:
I’m not using PAC.you don’t have to because if you measure the output voltage from hu is only between 0.6-0.8v before the factory preamp .after that is 2.4V so I bought on Amazon just adapter which on one end plug wires and other end rca. Then they run in to the dsp. But what really make my piss of is the volume on radio which is very quiet.I try your tactics without result.I don’t know if the Bose amp increase the volume or… other things have you manage to do the big 3 upgrade?at the moment I have 155amp alternator and second battery at the back xs power 3400 .the thing is I can’t connect alternator to battery as it causing charging eloop malfunkcion.it has to be done somehow to pass the sensor but haven’t figure out test.any idea?also charging screen not ready for I start stop -battery .when I disconnect second battery then fine full ready. It’s the upgrade issue alt to battery or alt? If where can I get bigger one ?
[Android Head-Units] mjs8rkis:
Good Morning!

I have a 2017 Mazda 6 with Bose system and amp & just installed a Belsee android 10 with dual capability to use my factory infotainment + android. Is this the same one ya’ll have? Im also a novice when it comes to all of this so I’m working with a local car stereo shop to figure it all out. 1) We’re either of ya’ll able to plug in the center control knob? Factory system and original screen both had 4pin plugs, but Android has a proprietary plug with 4pin to plug into original infotainment system, so there are no more 4pin ports. 2) when I plug in the RCA cables I get a background static that doesn’t go away — constantly on once the system boots (and is there when I’m on the OEM and Android). Android side base volume is low and I have to crank volume way up to hear. 3) when using wireless Apple car play on Android side and making calls, the receiver gets a horrible immediate echo of their voice. Not sure of the fix for volume and echo, just thought I’d throw it out here if any of you or those on the forum have similar problems or a solution. Thanks!
[Android Head-Units] mjs8rkis:
Hello stefanek33! Yes, I did buy from Belsee and have been dealing with Rambo since June troubleshooting the issue. It has been very frustrating and I’ve come to the conclusion in my novice mind that the systems are crap. You confirmed it with your professional work on it! I had to look for something because my factory screen crapped out on me — it was going to be $1500 to replace and was backordered by Mazda with unknown stock date so I went looking and found Belsee. Screen size is great but that’s about it. At this point since the factory works, I’m just going to use the thing for the 10.1” screen and get one of those car link adaptors that does the same (android apps, wireless CarPlay) but run it through the factory part and completely ignore the Belsee android (attached the install document and a picture of the split screen android/factory system). All I need to do is figure out how to plug in the center command knob and they plan will work (I think lol).

I’m interested in your suggested fix, but I’m not sure what you mean about the red wire. What is the tau? Do you have a picture example of the wire? I’m sorry — you’re dealing with a complete noob / novice to troubleshooting electronics. Happy holidays!!!
[Android Head-Units] mjs8rkis:
TAU = Tuner Amplifier Unit. Google is my friend. I’m getting smarter at this by the day! Lol. It’s one thing to work through good quality products that have diagrams and such … but having to pull teeth to get back one to two liners in broken English is very frustrating. Even more so when they say these units are “plug and play” lol
[Android Head-Units] Stefanek33:
you should recieve this wire ..then connect it and run the rcaback to the unit and connect it in to the AUx in..The central knob i havent got any wires i just use the factory wire from the Radio and connected to the Android ..It mus fit try...Central knob connect to the original location...I was bit strugling too as later i figure out from the Original OEM you have to dismount the metal Unit and fit the android unit on it..Of course Mr Rambo didnt provide scrwews so i have to use my one...When you instal the Android on the metal OEM part then just run the blue wire from the Android and connect to the Metal Unit and you should be okay..
[Android Head-Units] mjs8rkis:
Ah yes, received that connector and ran it through to the Aux in on the Android. I have the static and the low volume and echo on Bluetooth/CarPlay calling still.

For the center control knob, I have this power/4pin connector (attached pic), and I can connect it to the factory, but then the Android blue cable that connect from Android head unit to that 4pin port won’t connect. Will I still get the factory system to show? I’ll need to extend the cable though to get it to plug into the factory since it won’t reach.

Thanks!
[Android Head-Units] Stefanek33:
The blu cable has nothing to do with the central consol .blue wire from android the second end connect to the metal part of oem.
[Android Head-Units] mjs8rkis:
That’s right. But if I leave blue connected to the metal part of OEM, I have no other place to plug the center console plug. All Rambo told me was to unplug the blue and see what happens lol
[Android Head-Units] Stefanek33:
I connect the central console back to the OEM metal bracket..I think in my one the 4 pins are positioned on the left back side..How is it look like your metal Bracket from back..Can you make some pic.?
[Android Head-Units] mjs8rkis:
I was able to get the center knob to work! I kept the blue 4 pin cable, but apparently in a previous install the guy helping me ran a separate 8pin cable that didn’t connect to anything, so I found the correct 8pin that is connected to the power cable and it all works. Now I just need to try and solve the echo and static issue. I think if I go the way you did and completely replace the Bose system, it would work — though might end up with the same issue you have. Happy New Year!
[Android Head-Units] Stefanek33:
How is working aux for you?You have to plug the silly 3.5mm jack in to the aux slot then switch to the Aux on the OEM..When you increase the volume on aux did you hear static noise with or without starting the engine?Please let me know!Its very important!
[Android Head-Units] mjs8rkis:
So I plugged red/white RCA connector to the R/W RCA inputs on the android. I immediately began hearing static at low to zero volume. I did not have the 24 pin adapter cable even connected to the right door radio plug. I also did not have the 35mm jack in the aux slot. So I had the static then, and the after, when I plugged the adapter in and the 35mm in the aux slot, static was still there, but my volume was very low. Turning up the volume made static even worse. I heard the static both without and with the engine started.

Thought it interesting that static started immediately when plugging the RCA male to the RCA inputs on the android and didn’t even have the 24 pin adapter connected.
[Android Head-Units] Stefanek33:
Make some short video and upload on vimeo ..We have to do something with it as Rambo wasnt really honest with as.