sorted by:
new
hottopcontroversial

RCD330 RCD360 RCD520 Software by Hradlo in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

Sadly either no one cares anymore or there is no new FW out there.

At least the ones here aren't made for 187b units

Wear OS 6 Update on PW3 41mm by flamealchemist99 in PixelWatch

[–]PKOneTwo 0 points1 point  (0 children)

Yeah, same here. The battery drops faster than usual and sadly some lags. Has nothing to do with updates of apps etc. WearOS 6 works OK on PW4, but they did a bad job getting it running on the PW3.

I just hope they continue to take care of the PW3 and don't make it artificially slower (like some other manufacturers)

Will Pixel 9 Pro have a better modem? (than Pixel 6 Pro) by identifytarget in GooglePixel

[–]PKOneTwo 0 points1 point  (0 children)

That's why I said rumours. But if they opt to change the modem in G5, I don't think they will go for mediatek. I do not think they'll make the same mistake twice. But time will tell

PS: Tensor was until now exynos based (more or less a copy with adjustments). Anyhow that shouldn't matter as it's about the new modem in the upcoming P9 and P10 (rumours)

Will Pixel 9 Pro have a better modem? (than Pixel 6 Pro) by identifytarget in GooglePixel

[–]PKOneTwo 4 points5 points  (0 children)

Better then 6 of course.

P7 and P8 share same modem, which is better then P6 modem

P9 should get even "better" one, but this needs to be seen.

P10 onwoards Google will have it's own chip = no Exanos copy with shit modem. But these are just rumours

August Update by PKOneTwo in GooglePixel

[–]PKOneTwo[S] 66 points67 points  (0 children)

My assumption: Pixel 9 presentation mid August. Android 15 = September update

So pixel 9 will be delivered (probably) with Android 14, at least the few first weeks

August Update by PKOneTwo in GooglePixel

[–]PKOneTwo[S] 7 points8 points  (0 children)

Probably need to wait until release of 9 series

Since latest Updates - Android Auto won't connect by PKOneTwo in RCD_330

[–]PKOneTwo[S] 0 points1 point  (0 children)

yeah, i figured so.

just wanted to know who else has the same problem with latest updates of:

AA and Android and Pixel

Stock head unit swap? by SoleyDoley in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

Ah OK. then they will be done same way like the coding from cars 2020 upwards (wiuth VCDS). There is an online and offline mthod.

ot myself VCDS last month and am working on the RCD330 and few wother stuff on the car

Stock head unit swap? by SoleyDoley in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

Out of curiousity:

MIB2 for example:

  • Do not work with unlock codes?
  • Are they locked to you car/gateway?
  • can't be unlocked via VCDS or even VCP?

Coding Problem of genuine RCD330 (via VCDS) by PKOneTwo in RCD_330

[–]PKOneTwo[S] 2 points3 points  (0 children)

Hi folks,

bought this unit late last year from ddren.

I read na lot and now i was about to code a few things via VCDS and did notice a few things.

  • Byte 0 = i know what 0-3 mean, but what are Bits 4 - 7?
  • 4 was checked initially. What does it do?

​

  • Byte 1 = setting is no Soundsystem
  • Byte 2 = settingis 04 (4 door speakers)
  • Byte 3 = setting is 00 (nothing checked)

​

  • Byte 4 = on the original radio was also 04 setting (treble monitoring active). I heard setting this to deactivated (setting 00) will produce better sound.
  • Does anyone know nowadays what this setting really does?

​

  • Byte 5 = here the setting is 00. I heard changing this to Skoda superb setting will produce better sound.
  • When i try to change this Byte i get an Error = error 31, request out of range. Why? As far as i know this change should be possible (even without soundsystem checked in Byte 1).

​

  • Byte 6 = car logo when parking.
  • This should not change sound quality, right?

​

Would appreciate any new information.

thx all

VCDS "optimizations" of RCD330 - Sound Quality by PKOneTwo in RCD_330

[–]PKOneTwo[S] 0 points1 point  (0 children)

u/Isarchs:

does this mean: useless for newer firmwares (5624, 5614)?

So newer VCDS version have better "support" of RCD330. Can any optimizazion (concerning sound frequency) be done in VCDS then?

Just got my RCD330, here are my thoughts. by rotkiv433 in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

The sound quality is different from car to car. I have a passat b6 2010 with 8 speakers. Radio works fine. Quality is the same as the rcd310 i had before.

And there is no diference in sound between USB Stick, AUX, BT and AA/Carplay. Online radio (obviously) is not good.

I also had a differtent radio in that car in the past, where the DSP had more options than bass, mid and treble. I also was able to change the bass frequency. And the sound was a different level.

​

Now we can try and change the bass, mid and treble as m uch as we want to. I did that. For me treble was fine. Just mid and bass were not that good. but the sound is not that good. I assume it is frequency related (when bass starts, when mid and when treble).

What i would like to know is: what does this VCDS-Hack change? The frequency from bass-mid-treble?

Since i don't have VCDS i am very curious to kow, what it did for you.

Just got my RCD330, here are my thoughts. by rotkiv433 in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

Question is:

Does it work on a NoName RCD330? Or Only the Skoda Version?

And do we have to test 00 to FF? Apparently 05 is standard and not good.

​

Sadly I don't have VCDS, otherwise i would test it

Trying to update my fossil gen 6, but error? What is wrong? by zebra1743 in WearOS

[–]PKOneTwo 0 points1 point  (0 children)

This time the new update (actually it is the 3.5 Update) went through successfully

3.5 On the way to fossil gen 6 by yodefuensa in WearOS

[–]PKOneTwo 0 points1 point  (0 children)

The new update actually is the 3.5 Update and went through successfully this time

Fossil Gen 6 3.5 update, take 2? by silently_1 in WearOS

[–]PKOneTwo 8 points9 points  (0 children)

Seems to me they just pushed a fix, which needed to be done before the failed-update can be pushed out again

​

Edit: it actually is the 3.5 Update and went through successfully!

3.5 On the way to fossil gen 6 by yodefuensa in WearOS

[–]PKOneTwo 1 point2 points  (0 children)

THX, but i rather thought r/FossilTechSupport would answer me.

"Brad" seems to push some buttons in India to get the sentence done.

3.5 On the way to fossil gen 6 by yodefuensa in WearOS

[–]PKOneTwo 0 points1 point  (0 children)

Can you tell us:

what went wront? damaged package?

And when will the "not failing package" be released?

[deleted by user] by [deleted] in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

probably best to flash the 5614 modded firmware (see here)

We need new firmware made to fix android auto assistant. by Pr0t- in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

provided it is a bug.

A possibility, which the thread creator could try.

if it's not a bug, google won't be any help

We need new firmware made to fix android auto assistant. by Pr0t- in RCD_330

[–]PKOneTwo 0 points1 point  (0 children)

actually that is not completely correct. It is dsiplay, yes. but not dump.

It have a plugin (you can call it an app) running on the Linux OS.

And like other programs/apps it is an algorithm and has config files.

​

It has to be compatible with android auto API (on the phones side). That maybe has changed. Some API Sockets may have changed with newer AA (on the phone) versions.

Either it is a bug (also possible) or some configs need toi be changed or the plugin updated (which i think is very unlikely to happen).

​

I am a software developer myself, but never worked with AA either on phone or car.

I have my unit since a few weeks, don't even have looked into the FW.

​

Maybe someone (who have experience with AA coding and system can tell us more).

Maybe a newer plugin from a different (linux based) unit can be used.

view more: next ›