FORUMS
Remove All Ads from XDA

[Avin USA] BMW F-Series

49 posts
Thanks Meter: 9
 
By CleanKM, Member on 15th September 2017, 08:55 PM
Post Reply Email Thread
Howdy,

We are migrating over from BimmerPost over to XDA because the Original Thread has evolved from just the DIY install into more of a modification of the Unit itself. The unit we are talking about is This One In Particular, however it has similarities of other units that are in the F Series BMWs (jmoney99 on BimmerPost has one in the X3).

I hope that we can engage the whole Android Community better here on XDA while talking with other folks who have this unit on BimmerPost.

Avin has released a GEN2 unit with a different hardware format in connectors, but the specifications seem to be the same. The software ROMs and MCU also seem to work without issues on the GEN2. Until stated otherwise, you can assume software is identical.

Specifications:
  • AVIN Model: BMWF30A-1025
  • Device: rkpx3
  • Device Model: rkpx3
  • Manufacturer: rockchip
  • Brand: rockchip
  • Hardware: rk30board
  • ID: KTU84Q

The unit runs Android 4.4.4, 1GB Ram, 1.6 Ghz Quad Core CPU. So far, this is what we know is possible with it:
  • Rootable through KingRoot
  • KingRoot can be removed by SuperSume
  • SuperSu works fine
  • Rootable Applications are able to be installed and work properly

These are the following versions that are currently on record being released from AVIN (Updating breaks Root):
  • 20170711-Ver1.0.0.0001_foreign_a (Rootable) - MD5 (update.img) = 66a55552d6746e62b08783af7253af94
  • 20170823-Ver1.0.0.0001_foreign_A (Rootable) - MD5 (update.img) = 1d7eff1957827f68a025b5a4928f7295
  • 20170913-Ver1.0.0.0001_foreign_A (Unknown Rootable) - MD5 (update.img) = d27bef19b6e361350b5b9217cba6d41b
  • 201710XX-Ver1.0.0.0001_foreign_A (Unknown Rootable) - MD5 (update.img) = 7c5d98e63c7511ed8acbace071ca2b46
  • 201711XX-Ver1.0.0.0001_foreign_A (Unknown Rootable) - MD5 (update.img) = fe9ae7a54ae7ae4cb2b90224f79ffcf0

Latest MCU Update:
MD5 (update.nbd) = 988aa693c8e3922a5b250fc9b1693c4e

ROMs/.img's are able to be unpacked by proprietary RockChip Factory Tool v.5

Overriding system 24 hour clock to force 12 hour format is possible, but requires shell scripting and either modification of system startup files or third party program. See post HERE

__________________________________________________ ___________________________
DO NOT SWITCH TO ART IN DEV SETTINGS AS IT CAN CAUSE A BOOTLOOP
__________________________________________________ ___________________________

build.prop dump (from August ROM):
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84Q
ro.build.display.id=rkpx3-eng 4.4.4 KTU84Q eng.zxw.20161219.165857 test-keys
ro.build.version.incremental=eng.zxw.20161219.165857
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=2016年 12月 19日 星期一 16:59:21 CST
ro.build.date.utc=1482137961
ro.build.type=eng
ro.build.user=zxw
ro.build.host=zxw-ubuntu
ro.build.tags=test-keys
ro.product.model=rkpx3
ro.product.brand=rockchip
ro.product.name=rkpx3
ro.product.device=rkpx3
ro.product.board=rk30sdk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=rockchip
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=rkpx3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rkpx3
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=rkpx3-eng 4.4.4 KTU84Q eng.zxw.20161219.165857 test-keys
ro.build.fingerprint=rockchip/rkpx3/rkpx3:4.4.4/KTU84Q/eng.zxw.20161219.165857:eng/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/rockchip/rkpx3/system.prop
#
#
# system.prop
#

#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libril-rk29-dataonly.so
rild.libargs=-d /dev/ttyACM0
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true

#NFC
debug.nfc.fw_download=false
debug.nfc.se=false

#add Rockchip properties here
ro.rksdk.version=RK30_ANDROID$(PLATFORM_VERSION)-SDK-v1.00.00 \
ro.rk.screenoff_time=-1
ro.rk.screenshot_enable=true
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com
ro.rk.install_non_market_apps=true
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.sf.hwrotation=0
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=false
ro.rk.systembar.tabletUI=false
wifi.interface=wlan0
ro.tether.denied=false
sys.resolution.changed=false
ro.default.size=100
persist.sys.timezone=Asia/Shanghai
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.factory.tool=0
ro.kernel.android.checkjni=0
#set default lcd density to Rockchip tablet
ro.sf.lcd_density=160
ro.adb.secure =0
ro.telephony.default_network=9

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.sf.lcdc_composer=0
debug.hwui.render_dirty_regions=false
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ril.function.dataonly=1
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rk.bt_enable=true
ro.factory.hasUMS=false
persist.sys.usb.config=mtp,adb
ro.factory.hasGPS=false
ro.kernel.android.gps=ttyS0
ro.factory.storage_suppntfs=true
ro.factory.without_battery=true
ro.product.version=1.0.0
ro.product.ota.host=www.rockchip.com:2300
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.android.checkjni=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

UPDATED: CarType.xml from October Update Package:
Code:
<?xml version="1.0" encoding="utf-8"?>
<cartype>
   <model>
         <id>1</id>
         <name>1.F1X F2X F3X F4X(2013-2017)6.5inch</name>
   </model>
   <model>
         <id>2</id>
         <name>2.E60(2005-2010)6.5inch</name>
   </model>
   <model>
         <id>3</id>
         <name>3.E60(2005-2010)8.8inch</name>
   </model>
   <model>
         <id>4</id>
         <name>4.F1X(2011-2012)6.5inch</name>
   </model>
   <model>
         <id>5</id>
         <name>5.F1X F2X F3X F4X(2011-2012)6.5inch-full</name>
   </model>
   <model>
         <id>6</id>
         <name>6.F1X(2011-2012)10.25inch</name>
   </model>
   <model>
         <id>7</id>
         <name>7.F1X F2X F3X F4X(2013-2017)6.5inch-full</name>
   </model>
   <model>
         <id>8</id>
         <name>8.F02(2009-2015)10.25inch</name>
   </model>
   <model>
         <id>9</id>
         <name>9.F1X F2X F3X F4X(2013-2017)8.8/10.25inch</name>
   </model>
   <model>
         <id>10</id>
         <name>10.F1X(2011-2012)6.5inch-ADJ</name>
   </model>
   <model>
         <id>11</id>
         <name>11.F1X(2011-2012CIC)6.5inch</name>
   </model>
   <model>
         <id>12</id>
         <name>12.F1X(2011-2012CIC)6.5inch-full</name>
   </model>
   <model>
         <id>13</id>
         <name>13.G30(2018)8.8/10.25inch</name>
   </model>
   <model>
         <id>14</id>
         <name>14.E60(2004-2010)8.8inch</name>
   </model>
   <model>
         <id>15</id>
         <name>15.E65(2005)8.8inch</name>
   </model>
</cartype>
UPDATE: factory.xml from October Update Package:
Code:
<?xml version="1.0" encoding="utf-8"?>
<factorys>

        <factory>
          <!-- all:common:普通客户;high-grade:优质客户; -->
          <client>ALS</client>

          <!-- BMW_NBT:宝马NBT;  AUDI_A4L:奥迪A4L;  BWM_EVO:宝马EVO; AUDI_Q5_1024x600:奥迪Q5_1024x600分辨率; BWM_EVO_UI2:宝马EVO新款 -->
          <UI>BWM_EVO_UI2</UI>

        <!-- DVD模块类型: 0:关闭  1: DVD软件1 2:DVD软件2(HLA)  -->
          <DVD_type>0</DVD_type>

          <!-- A4L主页左边Logo: 0:不显示 1:A4L1(默认) 2:A4L2 3:A4L3 4:Q5 5:客户专用 -->
          <A4L_Logo_Left>1</A4L_Logo_Left>
          
          <!-- A4L主页右边Logo: 0:不显示 1:显示AUDI LOGO 和 高德导航信息 2:仅显示 AUDI LOGO  -->
          <A4L_Logo_Right>1</A4L_Logo_Right>
          
          <!-- 奥迪主界面是否要滚动特效:0:否  1:是  -->
          <Audio_Main_Scroll>1</Audio_Main_Scroll>
          
          <!-- EVO主界面选择 0:公版  1:主界面第一页和第二页交换  -->
          <EVO_Main_Interface_Select>0</EVO_Main_Interface_Select>





          <!-- 工厂设置密码(4位数) -->
          <password>1314</password>
         
          <!-- AUX功能开关 (0关闭, 1打开)-->
          <AUX_enable>0</AUX_enable>
         
          <!-- DTV功能开关 (0关闭, 1打开)-->
          <DTV_enable>0</DTV_enable>   
                    
          
          <!-- DVR模块类型: 0:关闭  1: CVBS DVR  2:USB DVR(使用USB才可以设置下面的DVRApk_packageName,否则无法自定义) -->
          <DVR_type>0</DVR_type>
          
          <!-- USB DVR APK包名: 默认:凯富隆  (DVR模块类型为USB DVR时有效)-->
          <DVRApk_packageName>com.anwensoft.cardvr</DVRApk_packageName>
          
          <!-- GooglePlay: 0:关闭  1:打开   -->
          <GooglePlay>0</GooglePlay>

          <!-- 蓝牙开关: 0: 后装蓝牙 1: 前装蓝牙 注:协议这样 -->
          <BT_type>0</BT_type>

          <!-- 蓝牙模块: 0:文强BC5  1:文强BC6  -->
          <BT_module>1</BT_module>

          <!-- 第三方APK软件安装: 0:允许  1:禁止  注:协议如此 -->
          <APK_install>0</APK_install>

          <!-- 宝马原车CD主机设置: 1:阿尔派  2:哈曼  注:协议使用的是1,2 -->
          <BMW_CD>1</BMW_CD>
          
          <!-- AUX切换方式: 0:自动  1:手动   -->
          <CarAux_operate>0</CarAux_operate>
          
          <!-- 功放选择: 0:原车功放  1:外置功放盒   -->
          <AMP_type>0</AMP_type>
          
          <!-- 原车显示: 0:关(老款宝马X1)  1:开   -->
          <CarDisplay>1</CarDisplay>
         
          <!-- 同行者语音唤醒词: -->
          <TXZ_wakeup>你好小微</TXZ_wakeup>

	  <!-- CCC_IDrive类型选择 0:IDrive_A  1:IDrive_B   -->
          <CCC_IDrive>0</CCC_IDrive>
   
          <!-- EVO主界面选中图标是否放大 0:不放大  1:放大   -->
          <EVO_main_interface_select_zoom>0</EVO_main_interface_select_zoom>
          
        </factory>
</factorys>
Update: mapApkLst.txt from October update:
Code:
com.baidu.baidumaps
com.baidu.BaiduMap
com.baidu.navi.hd
com.mxnavi
com.mxnavi.naviapp
com.autonavi
com.cld
cld.navi.mainframe
cld.navi.c3588.mainframe
cld.navi.c2739.mainframe
cld.navi.c3551.mainframe
cld.navi.k3618.mainframe
cld.navi
com.kingwaytek
com.papago.M11General
com.papago.s1OBU
com.papago
com.loco
com.sygic.aura
com.txznet.txz
com.google.android.apps.maps
com.mireo.magnav
com.mireo.dontpanic.android.incyclone
com.waze
com.sogou.map.android.maps
com.tencent.map
com.mapbar.android.mapbarmap
com.mapbar.android.carnavi
com.nng.igoprimo.javaclient
com.nng.igo.primong.hun10th
com.navngo.igo.javaclient
com.basarsoft.igo.javaclient
com.basarsoft.igonextgen.javaclient
com.mapswithme.maps.pro
com.here.app.maps
ru.yandex.yandexnavi
Attached Thumbnails
Click image for larger version

Name:	Firmware update instrution.jpg
Views:	1464
Size:	47.8 KB
ID:	4361783  
The Following 2 Users Say Thank You to CleanKM For This Useful Post: [ View ] Gift CleanKM Ad-Free
 
 
15th September 2017, 09:20 PM |#2  
Thanks for starting this here. (same member name for me at Bimmerforums) I'll start with the original link - http://f30.bimmerpost.com/forums/sho...374452&page=19

--------------------------------

Found a few launchers that might work better:

https://play.google.com/store/apps/d...rwebguru&hl=en

https://play.google.com/store/apps/d...ncher.motorcar

https://play.google.com/store/apps/d...es.carlauncher

Trying at least one over the weekend myself as there is practically no use for the stock launcher after removing the Stock Browser, Altered AVIN Music App and Altered AVIN Video Apps. (crashes HOME launcher when selecting now)

Too simplified for me but this might work well for others: https://play.google.com/store/apps/d...nus.launchertv

SetCPU works (with root) to change governors - set to INTERACTIVE by default
The Following 2 Users Say Thank You to jeffc83 For This Useful Post: [ View ] Gift jeffc83 Ad-Free
15th September 2017, 09:24 PM |#3  
OP Member
Thanks Meter: 9
 
More
Quote:
Originally Posted by jeffc83

SetCPU works (with root) to change governors - set to INTERACTIVE by default

Thanks for coming over bud.

Have you experienced any issues with the governors thus far, besides a potential overheating that you mentioned back in F30post?
15th September 2017, 09:29 PM |#4  
Quote:
Originally Posted by CleanKM

Thanks for coming over bud.

Have you experienced any issues with the governors thus far, besides a potential overheating that you mentioned back in F30post?

No issues to report with any of them and I did see a performance boost when set to PERFORMANCE since it keeps it maxed out all the time. My next step is to set it on boot to: OnDemand -> Min CPU 450mhz and Max CPU 1200. I also want to try and UNDERCLOCK it to see if that helps any. I would then go back to Interactive -> Min CPU 125mhz and Max 1000. On the commute home, I am planning on trying one new launcher and setting that CPU to option 1.
15th September 2017, 09:45 PM |#5  
Junior Member
Thanks Meter: 1
 
More
Interested in how the new launcher's work. Also if there is a way to intercept the CAN bus buttons.
16th September 2017, 05:21 AM |#6  
I installed AG Launcher and this was a pic while driving. Since then, I have customized it to launch what the hell I want lol. I'll grab more pics tomorrow and might even try another!

https://1drv.ms/i/s!AkHKmnTUFIO1g5E7iZgHVqcobfpZfA
The Following User Says Thank You to jeffc83 For This Useful Post: [ View ] Gift jeffc83 Ad-Free
16th September 2017, 06:08 AM |#7  
Junior Member
Thanks Meter: 2
 
More
Coming over from BimmerPost as well to talk about Android specific topics. How do you physically connect to the screen to start root? Did you guys use a laptop to do that?
16th September 2017, 06:03 PM |#8  
OP Member
Thanks Meter: 9
 
More
Quote:
Originally Posted by daxtor

Coming over from BimmerPost as well to talk about Android specific topics. How do you physically connect to the screen to start root? Did you guys use a laptop to do that?



No laptop needed for this unit. KingRoot is able to root it through its app. Then use SuperSume to remove KingRoot since it's bloated with adware.


Sent from my iPhone using Tapatalk Pro
The Following User Says Thank You to CleanKM For This Useful Post: [ View ] Gift CleanKM Ad-Free
17th September 2017, 02:56 AM |#9  
OP Member
Thanks Meter: 9
 
More
Was warm today and the Android aide of the unit just **** the bed. Said no signal on the screen after using it for about a minute. Luckily the OEM side was fine. Not a happy camper.

Once I got to my destination and started car again, everything seemed to work fine.


Sent from my iPhone using Tapatalk Pro
17th September 2017, 10:23 AM |#10  
Junior Member
Thanks Meter: 2
 
More
My screen died completely today: it got stuck with the BMW logo and won't boot up properly. I contacted Avin nd was given a newer ROM dated August and instruction to reflash it using the SD card. I am now able to use it again. Let's see how long it will stay running this time and hope the new ROM is more stable.
17th September 2017, 10:32 AM |#11  
Firefly1337's Avatar
Senior Member
Flag Heidelberg
Thanks Meter: 96
 
More
Also check out this thread: https://forum.xda-developers.com/and...a-nav-t3489042

I stumbled upon this and was very interested. Even more when you guys started rooting it. Not trying to be rude, but unfortunately this just seems to be old, outdated and slow consumer grade hardware.
Another question I'm asking myself: Where is the difference between one of these random chinese headunits and this avinusa model? Seems to me they are just reselling for a higher price.

I was really excited for this to work because I have the old CHAMP2 headunit but seeing the thread linked above the aspect ratio is completely off.
Anyway, I basically just wanted to give you guys the link to the thread and wish you the best of luck to make something useful out of this
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes