yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] jeffc83:
I got my car back last night and I'm also not happy with the unit. Gmaps froze and was the only app running...after restarting it, then it was fine. I uninstalled a launcher, downloaded another then it rebooted. Since it's unstable, I might wipe it but before that, I'm switching my runtime to ART as DALVIK is outdated and slow.

If this keeps up, I'm just going to buy an OEM 10" screen from eBay and send this back. I knew it was outdated from the beginning but the specs are "usable" in many ways and this crashing is NOT related to hardware specs. We'll figure it out.

---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------

So far this damn thing bootloops after switching to ART (5 times, waited 25 minutes) Think I'll need avin to reset or this might have to go back as it's a friggin Android feature. Not like this is hacking here. What a joke.
[Android Head-Units] CleanKM:
I do not have any issues with the play store and August update. Have you reached out to AVIN?
[Android Head-Units] CleanKM:
Did you try the latest August update? Mine so far has been pretty stable as long as I let it fully boot up (takes about 1:40 min). I also disabled a bunch of misc system services that I wasn't using. Mind positing your MCU and AppVer?
[Android Head-Units] jeffc83:
I'd love to but nothing works and it doesn't boot now. (waited 33 minutes before giving up) I insert the SD Card with the update and nothing (same bootloop). Mine might be bricked all over switching to ART. Not a happy camper.

This is the time issue but at this point, I'm not sure if I even want to go any further with this:/ This code needs to be edited ---> persist.sys.timezone=Asia/Shanghai

I'll try again at lunch but it's looking bleak...I suppose I wouldn't be as upset if the iDrive side was perfect but that stretched, cut off screen irritates me along with the ambient lighting issues.
[Android Head-Units] CleanKM:
Doubt it matters, but i've done all my updates with USB instead of SD card. Do we know if there is a way to boot to a recovery on this thing? I know i can do it from a running unit then reboot (rooted) to recovery, but do you think there is a key combo to do this? Does it have a little reset button on the back (i didnt even look)? Where in the process is the bootloop occuring? Sorry buddy, dont give up on me yet! This is why we are in XDA instead of bimmerfest :silly:
[Android Head-Units] jeffc83:
Yeah about that USB plug...it fell back into the center console as I didn't give it enough slack so from day 1, I have not had that option. (my fault on that lol) I emailed Tommy about the reset as I don't see any buttons; haven't heard back yet but I only emailed about 2 hours ago.

It's pretty straight forward in terms of how it loops and now I cannot get to the android screen at all! Took pics (see below) and it went from BMW logo to black then to BMW logo then black (30 second to a minute delay in between so it is trying to do something) I hadn't frozen any apps so I know it isn't that. It would be nice if it would recognize the update on the SD Card but no go. My next approach without Avin is to just let it sit. I'll let it idle for no longer than an hour but I'll try it. Have this feeling that I will not get a response and if I do, it'll probably be "run the update" that I cannot run lol.

Pics that were originally going to be included in a small tutorial for others -> https://1drv.ms/f/s!AkHKmnTUFIO1g5I5QF-HDFb1dLMCZA

Thanks; not giving up yet but it's sure in hell discouraging that I have used the unit for about 20-30 minutes and troubleshot the rest:eek:

EDIT: Can get to the Android screen ONLY because my NAV button is re-routed. Yep, same loop but I only had 10 minutes total to test. (15 min break)

---------- Post added at 05:37 PM ---------- Previous post was at 05:05 PM ----------

Now I am getting ticked. Take a look at this for LESS MONEY! We did get jacked....

https://avinusa.com/volkswagen-8-android-6-0-marshmallow-gps-navigation-system.html
[Android Head-Units] CleanKM:
Yeah, the only thing is that they have a whole double din in order to fit more robust guts into the system instead of an LCD panel in which they are trying to keep uniform to the OEM style. Given the space and size, i think they did a good job incorporating the hardware in it. However, i would have rather had the actual guts of the system be another box that could be tucked away in the dash to allow for beefier hardware and combat the heat issues instead of an all-in-one unit.

Maybe they will read all of our feedback on bimmerfest and here and send us a Rev 2 model since we are basically beta testers for their hardware. :rolleyes: wishful thinking....

Even the E46, because of the double din, gets a beefier hardware package... https://avinusa.com/bmw-3-series-e46-m3-9-android-6-0-navigation-system.html
[Android Head-Units] jeffc83:
Found a reset button; top left corner on the back using a paper clip. Haven't had time to do anything but press once then wait and it still loops. I also see a hole in the front on the left bottom corner but I don't think it's a button so I didn't stick anything in there lol.
[Android Head-Units] CleanKM:
Yikes about the warranty.

I wonder if you have to press it in then start car or something to enable recovery. Something along those lines. If it's completely bricked and you can't return it, then cracking it open might be able to provide additional options there? I'd be interested to see the actual guts of the system when disassembled. Potentially a header that you can tap into?
[Android Head-Units] jeffc83:
Thanks...I tried that, pressing POWER/MUTE on iDrive, Menu and the reset then 15 seconds on the button. (in combos and alone) There MUST be a way to get recovery to come up or reset it completely.

It'll be an expensive lesson for sure but the more I research, the less confidence I have that this will work out as these issues has been going on for over 5 years now with various units they have released! (releasing outdated products then no support) AVIN EUROPE pulled out too in January (was an official partner) but I'd rather not bash the company further and say who and why.

I appreciate the recommendation but if I am disconnecting the screen, I will be smashing (literally too) the unit open to get my "lost" SD cards out and would then have some more fun with the hammer. It may sound stupid but I would much rather smash the crap out of it if i have to take it out. I'm almost certain that I can fix it using ADB but am just not taking that route as it requires disassembly. Very frustrating to say the least.

My plan for tonight is to pop this image onto an SD card (again) and put it into the slot. I will hold the reset THEN start the car to see if that does it. I know you can boot to an SDCard and can also update using an SDCard.
[Android Head-Units] CleanKM:
Well can you take detailed pictures of the smashed unit so i can see what the guts looks like even though they've been hammered? :D Sorry to hear you're not having any luck.
[Android Head-Units] jeffc83:
LMAO, thanks for the laugh:D If I do take it out of the car and smash it, I will grab pics of the "guts" prior to it's demise THEN after so you can see how much I LOVED this unit;) (my excuse not to "hammer it out of the car" is that I don't want to ruin a 128GB and a 64GB SD Card haha) I truly don't want to remove the screen and smash it plus I somehow still have an ounce of confidence this little reset button has a "magical combo" to get this update to run. If I can get past that, I'm back to new. There just HAS to be a way and all joking aside, I "hope" Tommy at Avin helps me figure it out but I honestly expect nothing but the "try this and try that", which we have lol.

I'm probably more pissed because less than 5 minutes before this started looping, I was taking pics of my screens to show you guys the launchers I have tried:/
[Android Head-Units] swa0000:
[MENTION=2463417]gt2009[/MENTION]

Thx a lot for your "digging" :)

Yes, you are right

Therefore i'm developing right now my own Launcher .

The main Car-Keys are "shipped" by three simple Broadcast- Receivers.

The "EventCenter"- Service is catching the CAN-Bus and pushing these broadcasts.

Inside this Service, there is a simple SerialPort - Handling to the CAN-BUS UART. (115k / ttyS0)

(BTW : they used a terrible & chaotic chinese code-style)
[Android Head-Units] gt2009:
This is the worst code I've seen .. if I coded like this, I'd be fired from my job :D
[Android Head-Units] swa0000:
:)

Are you still "searching" in this code or was it only to puplish an answer ?

If you are also involved in this , let us share the news ....

You are welcome ( i'm still searching some implemented features)
[Android Head-Units] lguodon:
After successful development, remember to share！
[Android Head-Units] Gillou_4ever:
thanks
[Android Head-Units] Gillou_4ever:
Does someone got the last firmware update .img ?

I have the 20180523-XXXXX in my last unit bought but got the 20180315-XXXXX in another car.

Thanks !
[Android Head-Units] rub94:
hi ... avin send me this

https://drive.google.com/file/d/1HpxuxTrMk7yvnYFwmp3U2YCdjsNlcVhe/view?usp=sharing

is the june apdate ..

Envoyé de mon SM-G935F en utilisant Tapatalk
[Android Head-Units] kalinkamaen:
Is the 8.8 inch units same firmware as this one? Thinking about 7.1 android with 2 gb ram 32 gb rom version.
[Android Head-Units] rub94:
this one is for 4.4.2 1gb ...

Envoyé de mon SM-G935F en utilisant Tapatalk
[Android Head-Units] skynet77:
For which unit? Android 4.4 and 1GB RAM or something else?
[Android Head-Units] Gillou_4ever:
Merci beaucoup c'est sympa ;)
[Android Head-Units] aclearersky:
Anyone have any idea what is changed in the June version
[Android Head-Units] mjosua007:
[MENTION=8556982]CleanKM[/MENTION] [MENTION=2463417]gt2009[/MENTION] Hi guys, you two seem to be the most knowledgeable in this thread and I was hoping you guys could shed some light in helping me fix an issue. I have an e60 8.8" unit with 4.4 that I got from Aliexpress and it's been flawless since first boot up. However it seems I got one of those units that was loaded with like 7gigs of Chinese maps and I deleted all those but somehow the system still thought storage was nearly full so it wasn't allowing me to install any more apps due to insufficient storage so stupid me decided it was a good idea to force stop and clear the data and cache for the "settings.apk" which ended up breaking my Menu button functionality which takes me to the home interface.

---------- Post added at 12:46 PM ---------- Previous post was at 12:46 PM ----------

Nor the physical menu button or the actual touch button in the upper left hand corner worked so I decided to do a factory reset from within the unit and luckily everything was back to normal :cool: Except everything I had installed was gone including root access (which was expected). Problem is I had Xposed framework already installed and everything was wiped from the android side but as you may know xposed was not. I ran the Xposed installer again and I got this message https://ibb.co/mxCRce I hit install again inside the app and then rebooted. Unit booted up to main menu and would reboot itself after 30 secs. So in those 30 secs I was in, I hit uninstalled in the xposed app and left it alone but I can't seem to get xposed running Again? Do you guys know a fix to this? I can't completely uninstall xposed by flashing the zip Uninstaller as we don't have any custom recovery for our units. Here's also a pic of my xposed log. (I also upgraded to the 2018 0410 update) but I'm not sure if it'd conflict with that in any way. https://ibb.co/hd9xYK
[Android Head-Units] CleanKM:
To be honest, I'd just cut my losses and start from scratch on everything. Seems like you booger'd it up pretty good. I've been there.

Follow these instructions and use the tool that is provided below if that's the route you want to take.
[Android Head-Units] mjosua007:
Thanks man! I will give it a try. Do you happen to know if the June update img file uploaded on this thread a few days ago by [MENTION=1498761]rub94[/MENTION] would work fine with the 4.4 CCC for e60 with 8.8"??

I don't see why not but I'd rather ask the ones who know first.

---------- Post added at 03:00 AM ---------- Previous post was at 02:46 AM ----------

Btw guys, feel free to check out my custom Boot animation that I achieved on my e60 4.4 1gb unit.

[youtube]vTY59_0kz5Q[/youtube]

i think it makes the boot up waiting time that much more interesting and fun. And gives it that oem feel. :cool:

I'd be willing to share my boot file and the instructions on how to do this but I take no responsibility for any issues that this may cause... (As many of you have expressed, boot up times can vary.) Not sure depending on what, but mine takes approximately 30 secs and I specifically made this custom Boot animation to cover for the exact 30 secs that it takes for mine to boot up. You'd also need root access.

[MENTION=8556982]CleanKM[/MENTION] P.s This was taken when my xposed was actually working :/ I've yet to figure that out.
[Android Head-Units] CleanKM:
I do not know if it would or wouldn't work on yours to be honest. I planned on giving it a whirl on mine but am leaning towards the mentality of if it's not broke then don't fix it. But it's killing me to know what the extra 10 MB brings to the table compared to the march/April one.
[Android Head-Units] mjosua007:
[MENTION=8556982]CleanKM[/MENTION] Just tried the latest Avin June update on my e60 I figured since the screen res are exactly the same I'd give it a try and worked like a charm even got my xposed back! Fxxk yeah!!

I think there was something about that other img file i got from an Aliexpress seller just wasn't compatible with xposed.

Thanks!!
[Android Head-Units] CleanKM:
Glad it worked out for you! Did you do just regular update method or the SD card method? Any differeneces in this rom?
[Android Head-Units] mjosua007:
Honestly I tried to follow the instructions you gave me and I'm almost 100% sure it's my SD card but I got an "MBR" error and I'm sure it would've worked if I had another SD card but I didn't so I just did the simpler method that I was told to do by the seller which is just copy and paste the img file on the SD card and let the system prompt me to do an update and it worked just fine.

As for the rom itself, I felt absolutely no difference in performance or stability at all. That's probably why the 10mb difference in size lol. I'm guessing just minor bug fixes or something.

If I was you I'd probably not worry about it if yours working fine like you said earlier. I'm definitely just about done messing with mine.
[Android Head-Units] teletype:
Hi everyone, I just got the gen2 7.1.1 Avin unit today. I figured I'd get it powered up indoors before installing it in the car. First order of business: root. I didn't see that anyone had done this yet for the gen2 so figured I'd share. Turns out it wasn't very difficult, you can just su from an adb shell. Since we have no USB debugging access, here is the method I used:

Connect to wireless network.

Open a local (non-root) shell on the device. Any terminal app will do, I used JuiceSSH.

Run setprop service.adb.tcp.port 5555 in the local shell to enable ADB over TCP.

Run ifconfig wlan0 in the local shell and note the device's IP

Enable Developer Options menu, then either enable USB debugging or disable/re-enable it to restart adbd

On a PC with adb tools enabled, run adb connect 1.2.3.4:5555, replacing 1.2.3.4 with your device's IP

On the PC, run adb shell to get a shell on your Avin device. From there, run su to become root.

Result:

px3:/ $ su
px3:/ # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc)

While this will give you root access, I wouldn't call the device "rooted" yet. Next goal is to get SuperSU or hopefully Magisk working. I want to figure out how to recover if I bootloop or soft-brick it before messing around too much more. It does look like the USB is OTG, does anyone know if it's possible to get this into device mode for either Android recovery or Rockchip maskrom mode?
[Android Head-Units] mantrajt:
It could be nice to see how performance is in this version. As gen 1 sucks is so many ways that it has become so frustrating to use that I almost don't use any of it's features.

I use my phone for Google maps or waze because Avin GPS is soooo unpredictable (bad). Bluetooth connection is awful so I use BMW instead of Avin. And everything is slow as hell, opening apps, input lag, etc

Because I'd Android version there is no way to run Android Auto. .

And I could continue talking about this.

Please give as your feedback
[Android Head-Units] swa0000:
Just a small note : I don't know about the 7.1 but i'm developing my own launcher with the 4.4 over ADB (rooted / Wifi)

USB Debugging : Maybe they used the same password to get into the developer Options : "7101"
[Android Head-Units] nomorebigideas:
[MENTION=6727112]teletype[/MENTION]

I've got a 7.1 AliExpress unit - I think they're all the same and purchased wholesale from China and just rebranded.

I haven't got an SDCard slot but I've got a 2 X USB via a cable. Mine is soft bricked - wrong firmware. Can't get any response from the USB. Tried to solder a deconstructed USB cable with pins to the Android board (as per another PX3 thread) but as the board is a different readout it doesn't work.

Long story short - don't brick it. Or if you do - and fix it - let me know how and I'll shout you a drink!
[Android Head-Units] onizuka007:
Nice, I tried it last weekend as well to use USB debugging. Didn't find a way to activate USB device mode. Then tried via adb over wifi, but didn't succeed because my wifi hotspot had a problem to find the unit.

To get into revovery mode just open a local (non-root) shell on the device

Run reboot recovery

Problem is you can't actually navigate in recovery menu due to lack of hardware volume / power buttons.

A Bimmerpost forum user mentioned he was told to remove a resistor to get into USB device mode:

- OTG recovery. Alice told me to open the unit and remove the resistant at USB_OTG on the Android SOM.

hxxps://f30.bimmerpost.com/forums/showthread.php?p=23387558&highlight=root#post23387558

How do you get it powered up indoors before installing it in the car? Do you connect 12v power to the harness?
[Android Head-Units] cederron:
This wont work on a bricked device
[Android Head-Units] onizuka007:
yes, your right. On a bricked device it won't work.

So we first need to find a way to recover the device in case it is bricked. As far as i know the bimmerpost user sent back his Android SOM to get it flashed.
[Android Head-Units] teletype:
Yeah, I was able to get into recovery and also unable to navigate. TWRP recovery would be very helpful here. That's good info about the OTG resistor, I peeked inside briefly but didn't notice that. Hopefully it won't come to that!

After reading back in the thread a bit it sounds like a few people have un-bricked using a bootable SD, so I'm exploring this avenue first. I haven't got it to boot from SD yet but I did try a Radxa SD image which caused it not to boot, so it's probably able to boot from the SD slot. I haven't seen a recent update.img for this unit yet. The first thing I did after getting root was to dd images of all the mmc partitions, so hopefully I can use those to build one. I've only worked with RK chips using rkflashtool before (got a Meural Canvas art frame into maskrom mode to root it) so there's a bit of a learning curve still.

Yes, to power on I connected a small 12V 1A power supply to the harness. I had a spare quadlock plug to wire into so I didn't have to cut the Avin harness.
[Android Head-Units] onizuka007:
Here you can find recent images (px3.img). Latest is 20180801

hxxps://drive.google.com/drive/folders/1mWtI61GU8GReGQ-PjwcjBjFXM34EGaoE

This is for the 2GB RAM Android 7.1.1 units! (Thanks CleanKM)
[Android Head-Units] CleanKM:
To clarify so that people dont end up bricking their units: This is for the 2Gb RAM Android 7 units.

Correct?
[Android Head-Units] bill_viper:
URGENT!! BMW F20 Gen.2 Android 4.4 KitKat

Guys please help me, it's three days now that an automatic Google Play Services update f*cked up my BMW F20 Gen.2 4.4 KitKat screen.

I'm in Greece, and I've bought the device from eBay. Also, I've paid AVINUSA for support package.

They sent me some new image_force files to update the device. Ok, I can boot it up with this method, and after I install the latest August update.

Although, when I'm connecting to Play Store (or running any apps that need updated Google Play Services such as Sygic) I get an never ending loop error that Google Play Services crashed. The device auto updates the services to latest 12.8.74 (attaching 2 videos).

I'm really desperate, I don't know what else to do, what Services version I should install.

I have tried the following versions from apkmirror:

com.google.android.gms_13.2.75_(000300-209029382)-13275000_minAPI14(armeabi-v7a)(nodpi)_apkmirror.com

com.google.android.gms_13.2.75_(000302-209029382)-13275001_minAPI14(armeabi-v7a)(160dpi)_apkmirror.com

com.google.android.gms_13.2.76_(000302-209662548)-13276001_minAPI14(armeabi-v7a)(160dpi)_apkmirror.com

com.google.android.gms_12.5.27_(000302-192236476)-12527001_minAPI14(armeabi-v7a)(160dpi)_apkmirror.com

com.google.android.gms_12.8.72_(000302-202717283)-12872001_minAPI14(armeabi-v7a)(160dpi)_apkmirror.com

com.google.android.gms_12.6.88_(000302-197970725)-12688001_minAPI14(armeabi-v7a)(160dpi)_apkmirror.com

And the latest 13.2.77 version. None worked.

Tried many more noDPI versions but none worked.

The bad thing is that I need 15-20 minutes - every time that Services won't work - to flash first the image_force and then the latest image.

Please, please, help me!!!

And 2 videos of the error:

https://www.dropbox.com/s/n06piveeqijgczl/20180824_073343.mp4?dl=0

https://www.dropbox.com/s/44rzf053j31kk90/20180823_132625.mp4?dl=0
[Android Head-Units] bill_viper:
Guys any help please? Anyone knows the correct version of Play Store Services to download it from apkmirror and then install it?

Can't use at all my screen now. :(
[Android Head-Units] swa0000:
Bill :

Did you tried following : ?

a) a complete Factory reset

b) put the image-file on the sd and reboot .

c) After reboot - remove sd card (or image-file on it)

c) Be sure that wait for a while, until Google updates the system (see the new icon of Playstore app)

Reboot the system and disable automatic update in the playstore app directly
[Android Head-Units] bill_viper:
Thanks for the answer my friend.

Yes, I did factory reset like 40 times these 3 days now.

Although I won't go online with the screen so that the services won't be updated, when I'm trying to use a navigation app needs the latest Google Play Services (I get a message for this).

I still don't connect my Play Store account, I have put some Play Services apks from apkmirror.com in my USB stick, and with the file explorer I install every one of it to try which one will work. But no luck at all.

I have spent 15-20 hours in the car these days trying and getting errors.
[Android Head-Units] swa0000:
Just do it once i explaind it above, use the playstore account and let the system download/choose the right versions.

(no apkmirror stuff !)

P.S. I'm developing on this device and did this procedure very often - all was fine.
[Android Head-Units] bill_viper:
Yes, that's the way I did it and got this error.

When the system alone downloads the right version (I have post a screenshot above, it's the 12.8.74 version), I get the error in the video.

Bootloops all the time that Google Play Services have crashed.
[Android Head-Units] onizuka007:
Which android update version do you have?

I had the same problem with Google Play Services crashing using android update 20180801. Factory reseted a few times, didn't help.

I flashed android version 20180703 and factory reseted again. Now Google Play Services updates and works again. :)