[Il_Simo]

Hello, I bought this XTRONS 10.25"
android

It seems works fine but I hame some problem wit navi gps.
I installed HERE and downloaded maps for offline use but I don't have any audio.

Please help me to fix this issue.
But I have some issues:
I installed Here maps, Maps.me, Sygic, but I haven't any vocal indications, just google maps specks throught a small speacker

Do you know if I can personalized right side (android) of the screen???

thanks a lot

[RedErik]

Originally Posted by Il_Simo

Do you know if I can personalized right side (android) of the screen???

You cannot personalise this screen. It's governed by the MCU and we cannot modify it.

[Il_Simo]

any suggestions about Here or sygic doesn't speak??

[RedErik]

Originally Posted by Il_Simo

any suggestions about Here or sygic doesn't speak??

No, sorry.

[FrederikD]

Originally Posted by RedErik

Boot animations and splash images

Universal boot animations along with splash images for 1280x480 and 1920x720 units.

Boot logos:
Android 9 and 10 use splash.img and the tool is linked in the first post.
Android 11 uses imagefv.elf unfortunately due to the nature of these files we do not have the tool to create them.
Android 12 uses imagefv.bmp and everyone can make it using widely available tools.

How to install on SD425/450/625/662/665:
1. Create OEM folder in the root directory of your SD card/USB stick
2. Copy both bootanimation.zip and boot logo (splash.img, imagefv.elf or imagefv.bmp) to the OEM folder
3. Plug in to your Android unit
4. Wait for confirmation of successful installation
5. Reboot and enjoy

How to remove boot animation from SD425/450/625/662/665 unit:
1. Create OEM folder in the root directory of your SD card/USB stick
2. Create an empty bootanimation_clear.zip file and move it to the OEM folder
3. Plug in to your Android unit and wait


Thanks to VincentZ4 for providing installation instructions for PX6 units and 3bl for providing additional steps in case you encounter any isses.

How to install on PX6:

Splash image / Boot logo
- Create 1280x480 image
- Save image as logo.bmp
- Create OEM folder on your USB drive
- Copy logo.bmp to the OEM folder
- Turn the device off
- Wait 15 sec
- Plug the USB in
- Let the system start
- Reboot

Bootanimation.zip
On PX6, you will need to run ADB on your PC/laptopt
There are 4 steps to follow:

STEP 1: create bootanimation.zip
bootanimation.zip is a set of files as described here: https://android.googlesource.com/pla...tion/FORMAT.md

One thing to know, in the desc.txt, the last txt line is empty :
-- beginning of file --
1280 480 25
p 1 0 part0
p 0 0 part1

-- end of file --

Step 2: enable ADB WiFi
- connect the HU and computer to the same WiFi network
- go to Developer Settings: -> enable USB debug.
- install Terminal Emulator on your HU
- run HU Terminal Emulator and enter following commands:

setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot

After the reboot launch Terminal Emulator on your HU and enter:

ifconfig wlan0

this will show the current IP address of the HU


Then continue on your PC:

adb connect xxx.xxx.x.x:5555

(IP address from the previous step)

adb root
adb disable-verity
adb reboot

After reboot check the IP address again (just to be sure)
Then continue on your PC:

adb connect xxx.xxx.x.x:5555

(IP address from the previous step)

adb root
adb remount

Put the bootanimation.zip in the root of your USB.
Move USB stick to your Android unit
Then continue on your PC:

adb shell cp /storage/usb_storage/bootanimation.zip /system/media
adb shell cp /storage/usb_storage/bootanimation.zip /data/local
adb shell chmod 644 /system/media/bootanimation.zip
adb shell chmod 644 /data/local/bootanimation.zip
adb shell chmod 755 /system/media
adb reboot

If you get "Read-only" message when you try to copy, that means something wasn't done correctly in one of the previous steps.
You may need to reconnect after each "adb root" command.
You should see the animation now !


NBT boot animation - demo video




NBT EVO boot animation - demo video




NBT M boot animation - demo video




Universal 1 boot animation - demo video
Splash image thanks to mbonus




Universal 2 boot animation - demo video





Ask me for custom made boot animation with your exact car and welcome text - see my work on YouTube

Hi, my name is Frederik from belgium. I have a BMW 3 F31 with android 10.25 PX6.

I wanted to have a moving animation so I downloaded it from this link. (NBT boot animation)
Splash file + the zip file under and made an OEM folder on the USB.
I inserted the USB in the android and did nothing for the rest.
Now I get a fuzzy screen when I am in the original part of the screen. Android still seem to work completely.
I tried a factory reset in the android menu but this did not work.
How to solve this please? What could be the problem?
Did my main connection with the original menu crash?
Need to fix asap because I need to sell the car..

Screen error when in original menu:

[RedErik]

Originally Posted by FrederikD

Hi, my name is Frederik from belgium. I have a BMW 3 F31 with android 10.25 PX6.

Hi

Originally Posted by FrederikD

I wanted to have a moving animation so I downloaded it from this link. (NBT boot animation)
Splash file + the zip file under and made an OEM folder on the USB.
I inserted the USB in the android and did nothing for the rest.

It's because you didn't actually read the post. What you were trying to do was to install animation and splash using method that works only on Snapdragon devices. Yours isn't as you said yourself it's a PX6. So in effect you did nothing. You just plugged in a USB drive with some files on it - could've been any files at that point, makes no difference.

Originally Posted by FrederikD

Now I get a fuzzy screen when I am in the original part of the screen. Android still seem to work completely.
I tried a factory reset in the android menu but this did not work.
How to solve this please? What could be the problem?
Did my main connection with the original menu crash?
Need to fix asap because I need to sell the car..

What you did is completely unrelated to your issue. It's either incorrect OEM screen setting, wiring issue or corrupted MCU.

[Basti600]

Originally Posted by RedErik

For those who want to get rid off the "Phone is starting..." message after each boot, here is the tool do that. This is system overlay and works exactly the same as KswOverlay theming.

As before you will need a laptop that is connected over WiFi to your HU and follow instructions on the screen.

What exactly does the tool do?

Is the info not displayed and the screen remains black? Do I have to set an image instead? Is this completely disappeared and am I already in the user menu at the time of the actual info display?

Where can I find detailed installation instructions? Couldn't find anything about how to do this with the laptop

Best regards & thank you very much for your patience.

[RedErik]

Originally Posted by Basti600

What exactly does the tool do?

Is the info not displayed and the screen remains black? Do I have to set an image instead? Is this completely disappeared and am I already in the user menu at the time of the actual info display?

Where can I find detailed installation instructions? Couldn't find anything about how to do this with the laptop

Best regards & thank you very much for your patience.

It replaces the "Phone is starting..." text with a blank text, that's all it does.

How did you manage to miss the guide on how to install it? It's in the first post here, both as a link (KswOverlay) under Tools and as a few point writeup under TL;DR.

[Robert AMG]

does anyone with A10 v3.9.4 successfully delete the phone is starting message? cause mine don't want to be deleted and the androidoverlay pushed the file with no errors, on my older version it went good.

[RedErik]

Originally Posted by Robert AMG

does anyone with A10 v3.9.4 successfully delete the phone is starting message? cause mine don't want to be deleted and the androidoverlay pushed the file with no errors, on my older version it went good.

I will have to check to see if there were any changes made with 3.9.4 that would affect that. I will get back to you on that.

EDIT: both versions have identical frameworks, so I can't see any reason why my overlay wouldn't work.

[Mike8040]

Hello there,

awesome thread even though I might not get much out of it since I was reading my device with the 8259L is not supported customizing the themes. It has the ID7 theme installed stock so I thought it could work. Yesterday I got a new firmware by Xonrich for the device.
Can somebody tell if the ID7 theme customization may work with my newer firmware?




Also what is strange is that even the flowUX synesthesia launcher and the Drive Controller app are shown as incompatible with my device. I can install all other know launchers but those two that interest me and I would pay for it won't allow me to install.

[Robert AMG]

Originally Posted by RedErik

I will have to check to see if there were any changes made with 3.9.4 that would affect that. I will get back to you on that.

EDIT: both versions have identical frameworks, so I can't see any reason why my overlay wouldn't work.

Thanks for your reply, what should i check now?

[RedErik]

Originally Posted by Mike8040

Hello there,

awesome thread even though I might not get much out of it since I was reading my device with the 8259L is not supported customizing the themes. It has the ID7 theme installed stock so I thought it could work. Yesterday I got a new firmware by Xonrich for the device.
Can somebody tell if the ID7 theme customization may work with my newer firmware?




Also what is strange is that even the flowUX synesthesia launcher and the Drive Controller app are shown as incompatible with my device. I can install all other know launchers but those two that interest me and I would pay for it won't allow me to install.

Themes available here are not universal. They are only compatible with Snapdragon units running KSW firmware. This means that if a theme was made for app X you cannot install it for app Y and hope it will work. Your MTK unit has a completely different launcher than Snapdragon units. And before you ask, no, you cannot change to KSW firmware as each vendor makes their firmware specific to the hardware it is running on.

As for the FlowUX, I cannot comment on that - it's not my app. What I can comment on however is the Drive Keyboard which is mine. It has been tested with 8259L devices and it's running just fine on them. What version of Android are you running on that unit?

[RedErik]

Originally Posted by Robert AMG

Thanks for your reply, what should i check now?

To sure to be honest. System logs? I don't have device that is capable of running 3.9.4 so I cannot test it myself.

[Mike8040]

Originally Posted by RedErik

Themes available here are not universal. They are only compatible with Snapdragon units running KSW firmware. This means that if a theme was made for app X you cannot install it for app Y and hope it will work. Your MTK unit has a completely different launcher than Snapdragon units. And before you ask, no, you cannot change to KSW firmware as each vendor makes their firmware specific to the hardware it is running on.

Thanks for your reply. I'm aware that the firmware is a big deal for compatibility on those devices. It was just a hope that the new firmware may be compatible since my unit uses the same ID7 skin stock.

Originally Posted by RedErik

As for the FlowUX, I cannot comment on that - it's not my app. What I can comment on however is the Drive Keyboard which is mine. It has been tested with 8259L devices and it's running just fine on them. What version of Android are you running on that unit?

Yes already wrote you an email since I would like to buy the Drive keyboard app but I can not through Playstore restrictions saying it is not comaptible. Even my new Realme 9 Pro+ is not compatible. I thought since my Android TV box is eligible to download it, to download the apk from my Android box once it is installed and sideload on my HU.
The HU was sold as Android 11. The Android settings say it is 10. So it must be 9 then

[RedErik]

Originally Posted by Mike8040

Yes already wrote you an email since I would like to buy the Drive keyboard app but I can not through Playstore restrictions saying it is not comaptible. Even my new Realme 9 Pro+ is not compatible. I thought since my Android TV box is eligible to download it, to download the apk from my Android box once it is installed and sideload on my HU.
The HU was sold as Android 11. The Android settings say it is 10. So it must be 9 then

I didn't get any email from you, well I don't think I did anyways.
What you're proposing to do will not work. If you download my app on your TV, extract the apk and try to sideload it on your headunit, the license verification will fail.

[Mike8040]

You are correct. The email was stuck in the outbox. Issues with Emclient...
Anyway. If I buy the app with my main Gmail account I should have the license for my account (in other words I use the same Google account on all devices) or is it bind to the device? How else can I download it? You already confirmed the 8259L is working with the app so it must be some Playstore bullshit then.

[RedErik]

Originally Posted by Mike8040

You are correct. The email was stuck in the outbox. Issues with Emclient...
Anyway. If I buy the app with my main Gmail account I should have the license for my account (in other words I use the same Google account on all devices) or is it bind to the device? How else can I download it? You already confirmed the 8259L is working with the app so it must be some Playstore bullshit then.

Well I cannot reveal how it works behind the scenes - that my license verification mechanism. But I can tell you this much: you cannot sideload the app, it has to be installed through the Play Store.

I have just checked and there are no restrictions on any device in Google's catalogue. My only requirement is a big screen (tablet size) and API level 27 (Android 8.1) and higher.

[Mike8040]

Yeah, well than we are out of luck I guess. There is no country restriction I guess otherwise I would not see/find it in the store. The weirdest things of all of it, is the Android TV box is the oldest device with Android 8 and the other two Android devices I own that are not "compatible" are Android 10 and 13.
Does the Android DPI setting play a role for the requirement check? I switched it to 440p for the 8259 head unit.
Can I not just send you the 4 bucks and you send me the app? Guess I do not get auto updates then?

[RedErik]

Originally Posted by Mike8040

Yeah, well than we are out of luck I guess. There is no country restriction I guess otherwise I would not see/find it in the store. The weirdest things of all of it, is the Android TV box is the oldest device with Android 8 and the other two Android devices I own that are not "compatible" are Android 10 and 13.
Does the Android DPI setting play a role for the requirement check? I switched it to 440p for the 8259 head unit.
Can I not just send you the 4 bucks and you send me the app? Guess I do not get auto updates then?

Just got your email.
The DPI setting does play a role, so possibly that's the issue here. If I disabled that requirement, the app will suddenly become compatible with all mobile phones, which clearly isn't, but people would still install it. The UI wasn't designed to scale to mobile phones and you cannot navigate the keyboard without the iDrvie knob. It would crash on every phone flooding my Play Console and Firebase crash reports. Some might even leave low star rating and negative feedback because of that. I have to think what to do with it.

[Il_Simo]

has anyone some template to create a idrive 8 theme?

[rodriguezstyle]

...