Yes, I do exactly as you write... bu my 7zip sw (x64 version, latest) doesn't show among the compression options, as first choice in the list, as your picture "0 - Nessuna" instead as first choice I have "Memorizzazione" (see my picture).
Most likely it was the zip file or txt file that is somehow kind of corrupted.
So for two of us, it doesn't work with the latest FW. Any special trick to get it working? What is the brand of your phone?
I agree with everything you write...if you don't do it right when make a final zip, it will be corrupted afterwards.
I have S21
Also used in the past 7zip 64 bits latest version so don't know why you have different options in names?
Mine is also S8 but I can't get wireless to work. Same setup as you, but different outcome. i.e only wired AA.
Hi,
Thankyou So much! i'll try as soon as.Hi all, if anybody would like to test a very early alpha version of NavRadio(basic), they can find it here:
Download NavRadio BASIC for QF01
it's incomplete, full of bugs, it surely crash here and there but still usable.
I have enabled Google Crashlytics to help me debug all the crash and ANR so more people use it and more i'll fix it.
The full version will come when the free version will run smootly.
Enjoy
NOTES:
- Autoscan is done by MCU and it's fixed to 18 stations. Anyway you can use Autoseek function to find more stations or add new ones to the existing ones.
- The first frequency at startup need to be fixed.
- Sometimes you can hear the sound muting for a second, it's because the ROCO service think that navradio is a player and not a radio. I'll look for a fix later on..
what was the temperature in the car? What firmware are you currently on? did you update? no drop during idle ?
Temp in car was like 22 C because of Air conditionner running . I’m on the latest firmware 0508. I didn’t pay enough attention about the idle because i was a bit late driving to work so..
Didn’t worked for me.. I’ve downgraded to the same version but still overheating.. what is the normal temperature of the unit ? I mean when listening to radio or using CarPlay ?
Guys, there was a problem with the release that make the app to not start.Hi all, if anybody would like to test a very early alpha version of NavRadio(basic), they can find it here:
Download NavRadio BASIC for QF01 FIXED
it's incomplete, full of bugs, it surely crash here and there but still usable.
I have enabled Google Crashlytics to help me debug all the crash and ANR so more people use it and more i'll fix it.
The full version will come when the free version will run smootly.
Enjoy
NOTES:
- Autoscan is done by MCU and it's fixed to 18 stations. Anyway you can use Autoseek function to find more stations or add new ones to the existing ones.
- The first frequency at startup need to be fixed.
- Sometimes you can hear the sound muting for a second, it's because the ROCO service think that navradio is a player and not a radio. I'll look for a fix later on..
You have to remap buttons in the settings!
thank you, I will try when i am at home!You have to remap buttons in the settings!
Go to settings, enter 8888 then you will find a menu there where you can add functions to buttons.
I am working now but I will take pictures when I arrive home if you want.
Did you get the Wireless AA work btw?
It worked well to me before the update but now it only works wired via CarLetter.
Yes, i'm sure i was talked about it here, and also Aanton measured it and if I remember it was 1,6mm gap
forum.xda-developers.com
forum.xda-developers.com
Both mic (interior and exterior) are in the same line, so if you have both, they interferr,
it depends on which thermopad you buy. the higher thermo conductivity, the pad are harder. So if you want 2mm thick, then buy no higher than 6W/mK. But IMO 1,8mm is ok.
In my opinion there's absolutely NO advantage to use AA/CarPlay if you have 4G SIM with good signal coverage. You only get hotter HU being moooore busy running AA/CarPlay wich will also runs slower and also draining your phone battery for no reason.
Now i'm waiting for cc3 2k, so when it comes, i'll say some more, compare to s8 unit which i use since february
Of course, MANY problems also arise from poor writing of the latest firmware and MCUs released by developers.
The port is 9876. ( I've found that inside the build.prop)Just by trying a bunch of different codes and looking for patterns. Starting by looking at the codes we already knew I discovered they are all a repeating sequence of digits that are adjacent to each other on the keypad. Once you find a pattern there’s usually another code that uses the same pattern somewhere else on the keypad. If you actually type in the codes and look at the physical pattern they make you’ll see what I mean. For example 114477 is just the digits in the left column of the keypad going down. 336699 is the same pattern in the right column. And then some codes are just variations on top of that, like doing a code in reverse (which we already knew) as well as adding 00 to the end of some. This is how I discovered all the codes. Once I’d find one code Id try that same pattern in all places and variations. Simple as that! I’m sure there’s more patterns yet to be discovered so try different ideas out and see what you can find. With many people using these strategies I’m sure we can discover more! I may have even missed a few using the patterns of ones I found.
