yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Zaphod-Beeblebrox:
There are a multitude of car-dock front end apps/UI's on the play store . Any of these could be used to quickly derive a car-centric UI.

The real power in this particular unit is the existence of source. We will be able to build custom widget/UI's for many MCU based functions, re-write and/or tweak the radio app, etc.

It may have been an accident that the source was obtained, and quite likely somebody will get fired over it, but hopefully someone in the Newsmy organization will see this as a positive event as we make their device much better than they ever could :)
[Android Head-Units] easyguy:
Simple solution first, is your HU in USB ADB mode? Plugs into a different USB port, see if that will work. Restart your laptop. many other reasons on why it is not seeing it.

When a screen flashes and flickers, that sounds like a short somewhere with loose cables. Was it flickering at the shop?
[Android Head-Units] usafle:
The screen doesn't flicker all the time. It does it sporadically. And, yes it was doing it on initial install at the shop. As soon as it was powered on it started to flick.

I only have two USB ports but they are both on the same usb hub so switching ports won't do anything. I'll restart the computer but it picks it up under device manager.

Got the device to show up on Rockchip. Got the following error when trying to flash/RESTORE Red's .img file:

"This Operation didn't do because of not supporting!"

So, now I'm not sure what the problem is. Guess I'll have to wait for someone to type out idiot proof directions on how to flash / upgrade these things.

On a positive side;

I was successful in obtaining ROOT and getting SuperSU to work. Installed AdAway ad blocking software, got ES File Explorer to use ROOT functions and I might try to install Xposed Framework.
[Android Head-Units] easyguy:
Does the device shows up in PINK color?, you will have to hit "switch" it will then turn "green" then you can hit "restore".
[Android Head-Units] renedis:
I had that problem to.

Please try to change the following on your Windows computer in the batch tool folder:

Now: as for the config.ini modification, I found on minixforums a post by user Snurb that does the trick. You open config.ini (located in the same folder where the .exe file is) and look for this line:

LOGFLAG=TRUE

#SUPPORTLOWUSB=TRUE时,扫描支持full speed usb设备，默认只支持high speed usb设备

SUPPORTLOWUSB=

This you change into:

LOGFLAG=TRUE

#SUPPORTLOWUSB=TRUE时,扫描支持full speed usb设备，默认只支持high speed usb设备

SUPPORTLOWUSB=TRUE

FULLSPEEDUSB=TRUE

Save & close.

Then you start Rockbatch Tool and all of a sudden, I had a green flashing light… ready to flash the new firmware!
[Android Head-Units] Zaphod-Beeblebrox:
Summer has replied to me regarding the 8" tiggo version. She advises it is indeed the same as the 7" universal here, except for the obvious screen size difference. They will sell to me (with a set of universal wires/harness) for $355.00, plus $103.52 shipping to the US.

Guess I'm taking the plunge.

I hate you people :)
[Android Head-Units] renedis:
@ Zaphod-beeblebrox: haha, hope it will work out in your car!

@ others: I've noticed that there was a new kernel.tar.gz of 4th of november.

I downloaded this and uploaded it to my ftp. You can find it in the folder "kernel"

Usually the downloads go slow but i've found out that my (internationally) compony has a straight line to china. Downloading files from baidu from my workplace goes a nice 1000 KB/sec to 2000 KB/sec :)
[Android Head-Units] stops91:
Is there still FM radio function on that rom?

@ ALL - Does someone here have a 2011+ Kia maybe?
[Android Head-Units] renedis:
Yes

I do not have a Kia, but any car that supports a double din should work. If you have a car with steering wheel control that works "resistive" and not via canbus then that is supported to.
[Android Head-Units] Dream Reality Syndrome:
You should document the process of how you customize the fit in your vehicle!
[Android Head-Units] Zaphod-Beeblebrox:
I will try, but the last thing I want is for everyone to see how dirty I let my truck get :)
[Android Head-Units] DragonFlye:
I have a Kia Rio 2012
[Android Head-Units] stops91:
Me too! :eek:

Do you have the unit installed?
[Android Head-Units] red13dotnet:
Quick status update

I ripped apart a machine and cobbled together a build server.

I've been spending the last several days winding through the twisted build config they are using. so far I can compile a full update from source and it flashes, boots the kernel and tries to start android, but android never finishes loading. Keeps looping on a dying audioflinger service / camera service. Not quite there but getting there.

I'll keep you guys updated as any progress is made and believe me, you will hear about it the first time i flash a working system built totally from source.

Thats all for now, keep me posted on anything you guys run into / any annoyances or gotchas you might like addressed once this is running and ready for changes.

---------- Post added at 11:19 AM ---------- Previous post was at 11:17 AM ----------

Yes, Amplified 1.0.9v1.0 does include FM radio, untouched from stock 1.0.9 ROM
[Android Head-Units] Zaphod-Beeblebrox:
I haven't had time to pull down and look at any of the source.. But is there by chance any MCU source in there? I can't tell you how awesome that would be :)
[Android Head-Units] usafle:
Took a video of the screen flickering issue I'm having. Maybe someone can offer up some advice?

You can watch it here: Newsmy HU: http://youtu.be/nycUiRpnWoc

Thanks.
[Android Head-Units] easyguy:
Contact newsmy and see if they can ship you a new data cable between the android and the HU. Forward the video LINK to Summer, she can show it to her engineer team and they might figure it out.

The flickering looks like it only happens when you go into setting?...the video was too short to even determines where and how it is activated.

---------- Post added at 09:18 PM ---------- Previous post was at 09:14 PM ----------

LOL you ended up buying a more expensive unit.

When it arrives, please take pictures/videos so we can see what it looks like.

We might need you do do some measurements too.
[Android Head-Units] usafle:
And here I thought 30 seconds was too long of a video?

I can guarantee that the flickering happens when I go into settings. I can reproduce it 100% of the time by doing that. Other times it will just flicker at random times. When it flickers, it also causes a "static" sound from whatever audio is playing at the time. That's why I had music playing when I was doing it but, after watching the video, you can't hear it.

Does anyone elses brightness setting actually work? I shot that in the video as well. It was DAMN bright driving into work this morning at 0500. I know it's hooked up properly because the VOL and other backlight keys turn on when I turn on/off my headlights.

_______________________

Just flashed Red's custom ROM. About to go plug the "brain" back in and see whats-what.

It's nerve wracking not being able to "see" the unit. I've never 'blind flashed' anything before. Just plugging it in and hitting some buttons without actually seeing the boot screen , etc..etc... it just doesn't feel right. lol

I need to get like a HDMI cable so I can plug this thing into the TV so I can watch it.
[Android Head-Units] Bokomaru:
Does this tool work with the official factory image from Newsmy?
[Android Head-Units] zanix:
Yes, it does
[Android Head-Units] horn34:
Suggestions for the fastest way to get audio running after startup? I have Tasker set to launch PowerAmp at bootup, but it's still over 30 seconds after starting the car before I hear audio. Many times I'm 1/2 or 1/3 of the way to my destination.

What are you guys using to get music running quickly?
[Android Head-Units] Bokomaru:
If you're that close, just walk with some headphones :)

You could increase the standby time so the android box stays on for as long as you think you need, then it would only be the first start up in the morning that was slow.

At the bottom of my todo list is to see what can get trimmed off the bootup time. I'm sure some seconds can be saved, but I suspect it will be difficult to get less than 22ish.

If we had access to the MCU code, in theory, the MCU could cause the android box to startup when illumination power (headlights) is present. So if you hit your unlock button which flashes your lights it might start the bootup.
[Android Head-Units] kwalsh24:
Quick question, I didn't see this covered sorry if it has but is there any way to flash the xdauto releases without having to reinstall apps? I'm currently on b2 and want to either go to b3 or alpha4 now seeing how b2 has been stable now for a week.
[Android Head-Units] Bokomaru:
If you flash through recovery with the zip it SHOULD keep your apps and settings. As always, I recommend backing up with something like Titanium Backup to be sure.
[Android Head-Units] larsomen:
well i just got a message from customs, i need to pay 155 euro's if i want the radio....
[Android Head-Units] runemail:
I have tried to flash adauto b3 from stock several times from different computers with RKbatch tool, but it hangs on bootanimation. I see the the new bootlogo, but the dots just keep spinning forever. What am I missing?

Do I need a spesific MCU version to install b3 (I am on v37)?

Is it not possible to flash from stock directly?
[Android Head-Units] Zaphod-Beeblebrox:
I have to agree, if you are half-way there in 30 seconds, it's a pretty short drive :) But do make sure you have set the standby time in the MCU settings app. I think it now defaults to 'none' which requires a full reboot every time you start the car. The box draws very little power, so you can set the stand-by to several hours (maybe even a day or more if you feel comfortable with your car/battery). The 'wake' time in this mode is only a couple of seconds. Much faster than full reboot.

This has been something that [MENTION=4173803]Bokomaru[/MENTION] has been investigating and believes he's finally found. Look for the full fix in the final b4. However, if you want to flash b3, or my b4-alpha, just flash Tuatara's ROM first. The problem has to do with the resizing of partitions and using TWRP as a recovery. Since Tuatara's ROM doesn't flash CWM until AFTER the initial RKflashtool process, it was still using the rockchip recovery for that step. Since xdAuto completely replaces recovery with TRWP, any little issue with script/partition processing was messing with the flash process.
[Android Head-Units] runemail:
This has been something that [MENTION=4173803]Bokomaru[/MENTION] has been investigating and believes he's finally found. Look for the full fix in the final b4. However, if you want to flash b3, or my b4-alpha, just flash Tuatara's ROM first. The problem has to do with the resizing of partitions and using TWRP as a recovery. Since Tuatara's ROM doesn't flash CWM until AFTER the initial RKflashtool process, it was still using the rockchip recovery for that step. Since xdAuto completely replaces recovery with TRWP, any little issue with script/partition processing was messing with the flash process.[/QUOTE]

Ok thanks for enlightening me. I know better than to ask for eta, so ill just wait it out and test b4 when it drops.

Added the info to the wiki
[Android Head-Units] leonkernan:
Is that something that's changed recently in github? Because I can't seem to build a working copy tonight.

Every build i've tried has stuck on the boot animation.

Heres the log, i've even flashed a new build image with RKBatchtool with the same issue.

I made sure to do a make clobber before that build as well.

The last part keeps repeating over and over for as long as you leave it running.

Log at pastebin
[Android Head-Units] Bokomaru:
Please attach the logs as a file or use something like pastebin. The change went in yesterday, I'll have to check to make sure I didn't leave something out on my local copy.
[Android Head-Units] blacklistedcard:
+1. Boot loop
[Android Head-Units] Bokomaru:
Sigh. Well I was hoping to work around yet another android oddity, but I'll have to go about it another way. For some reason they made make_ext4 only able to work on devices > 8MB without passing the length on the command line. So I decided to switch to ext2 for /metadata (which I doubt anyone is using at all, but maybe in the future). I didn't want to increase the size of the partition, because it's just not necessary for it to be that big.

I'll switch it back to ext4 and change make_ext4 so it'll work with it.
[Android Head-Units] danny6869:
Good call.
[Android Head-Units] leonkernan:
Sorry about the log, it was after midnight and I ended up putting it up and going straight to bed. I've moved it to pastebin now.

That would also explain why TWRP also started erroring on /manifest as well.

I flashed back to turata to get a working box again, will give it another try shortly.
[Android Head-Units] Bokomaru:
I had to fork another repository and make a change in there, I just completed this a few minutes ago. Now I'm doing a complete rebuild to make sure no other issues popped up due to the new repo.
[Android Head-Units] vip-25:
Thanks friend

I got This app from stock rom :)
[Android Head-Units] BonOeil:
How did you that ?

Wow 500 pages now :cool:
[Android Head-Units] blacklistedcard:
Did the new build install fine?
[Android Head-Units] Bokomaru:
xdAuto ROM 1.1.6b4

Looks like we've got a stable build here. The overclocking and governor are back to defaults, so some people experiencing crashes should have better results (Zaphod was having an issue with one of his boxes crashing and this helped). If you want to overclock or adjust the governor, at least test the base out to make sure it is stable for you before making adjustments.

As always let us know about any issues.

rkBatchTool flashable Image

Recovery flashable zip

1.1.6b4: May 29th 2015

Change default governor to be 'interactive' by default

Allow ROM to be flashed with rkBatchTool from factory ROM

User selectable NavBar buttons

- Return of Volume Up/Down buttons to Navbar

Temp fix to allow make otapackage to build flashable zips

Adjust DPI in BonovoMCU Backlight page so OK button fits on screen

Allow Volume Up/Down/Mute keycodes to adjust MCU volume
[Android Head-Units] leonkernan:
Yep, worked for me.
[Android Head-Units] Zaphod-Beeblebrox:
A quick note about the selectable NavBar. These settings/options are in Settings / User Interface. The first time you flash this (or my Alpha), your navbar is going to look kind of like a stock Android phone layout (back/home/recents). You must go into the settings and set your buttons up. It does not default to the layout that I was using previously.

Also, I updated the PowerAmp & Torque Helpers on the repo to use the proper icons and text. No changes in functionality, but if you don't want to see windows icons, you can download the latest and re-install.

http://xfer.aokp.co/?developer=zaphod&folder=nu3001
[Android Head-Units] tacopicante123:
Nice work! Just a quick question.. Going from Tuatara's build to this, and wondered if there are any benefits or changes to this rom. Could someone post pics of what this looks like?
[Android Head-Units] Zaphod-Beeblebrox:
One little note/oddity about the helper apps. Due to the nature of the way the intent buttons work (ie, launching default app unless another app is already active) the helper has to stay in memory once it launches its target. It's a very small app, and I am excluding it from the Recents view, so there is no problem in this. The oddity comes in if you try to exit torque or poweramp after launching it from the intent button.

When you exit Torque, it brings up the last app in the stack. Which if you just launched from the navbar, is the helper app. Guess what the helper app does when it resumes :) It relaunches Torque.

So the way to close torque or poweramp in this case is to just go home, or launch the app from the home/screen, drawer, notification, etc. Just anything that puts *something* in between the app and it's helper in the stack.

I don't see this as a big issue as most people will leave these apps running once launched, but I wanted you to know what was happening if you saw it.
[Android Head-Units] -=Jeff=-:
I seem to recall an issue where power amp or Apollo doesn't "stop/Pause" with key off. has this been adjusted in the b4?

I will update from b3 as i like what everyone is doing with this ROM... THANKS!!!!!
[Android Head-Units] kingamra:
Using ex dialer (actually I tried almost every dialer in market ) getting error:

Phone function is disabled because the bluetooth server is disconnect or bluetooth is powered off

Currently can dial thru phone itself and bluetooth works (audio) nothjng on screen tho...

If I attempt to dial using native bt app I get an error:

The hpf of bluetooth is disconnect

Ideas?

Running b3 at the moment
[Android Head-Units] blacklistedcard:
Latest sync with GIT. Linaro Build with overclocking and Performance Governor

https://www.dropbox.com/s/8ouut47brwjri1b/rk3188-ota-eng.root(3).zip?dl=0
[Android Head-Units] kwalsh24:
Just flashed from b2 to b4 via recovery successfully with zero app loss! Thanks for all the work!

Just in case some are wondering, playback pause when the radio is off isn't functioning. Then again that could be an issue with p

Playerpro. I tried power amp in the past and just couldn't get use to the library interface lol.
[Android Head-Units] nFKT:
Any chance of getting a flashable zip of just your kernel? :)
[Android Head-Units] kingamra:
Just Uninstalled dialers.. wiped app cache.. rebooted phone and box... now it works...
[Android Head-Units] leonkernan:
I've just sent a pull request across for some work on the Bluetooth Handsfree app so I thought i'd better show what changes i'm proposing.

(Apologies for the poor photos, my good phone was handling the call)

The first screen changed is when a phone call comes in:

[IMG="Call ringing"]http://i.imgur.com/avtnLTZ.jpg[/IMG]

There are no more number dialing buttons on the ringing screens. I've tried to adjust the layout to better suit answering a call while driving.

Secondly, when in a call the following screen appears:

[IMG="In a call"]http://i.imgur.com/3F7zxzE.jpg[/IMG]

So far you can end the call or press the white button to show the dialing buttons. This allows for those phone menus (press 1 for x, press 2 for y).

If you use the dialing buttons screen, the back button is in the top left corner to return to the call.

I haven't made any changes to the dialing screen yet. You still get the buttons to type in a number and call it.

One of my next plans is to handle call waiting and holding and resuming calls.

I'm still learning my way through all this so please let me know if there is anything that's not working or i've done incorrectly and i'll sort it out.
[Android Head-Units] supremekizzle:
Any way to use this head unit as a lo jack of sorts since it has a GPS unit? I suppose in order to do so a 3g dongle would be needed to be able to remotely see where it is? Or does a locater app work without internet connection? Thanks.
[Android Head-Units] nFKT:
FYI this will not flash when coming from b4.
[Android Head-Units] Kevinkuensken:
Hey,

on b4 Viper4 Android not work.Anyone else this Problem?
[Android Head-Units] Surgent:
Worked for me mate :)

This whole ROM is starting to feel verrryy nice. Just need to decide on a UI and it'll almost be time to put in the car.

Big thanks to all those involved thus far.
[Android Head-Units] kwalsh24:
Hmm so what's the main differences between xdauto & the GIT linaro build? Minus the overclocking ability...?
[Android Head-Units] leonkernan:
I was hoping to be able to show contact photos working in the Bluetooth app tonight but they are still giving me a bit of grief.

When they work they come up in a box to the left of the name and call timer. Hopefully if I sleep on it the fix will come to me.

I did get the microphone mute button going though. This disables your microphone when it's turned on so the other party can't hear you.

The screenshot shows my name because I called myself from my home phone to my mobile.

[IMG="Handsfree incall screen"]http://i.imgur.com/jKoxH45.png[/IMG]
[Android Head-Units] Zaphod-Beeblebrox:
While you are working on this, a couple of things to keep in mind.

1) Thanks!! I am happy to see more and more people get involved in the coding side of this.

2) The BT Music and BT Phone apps need to be separated. Because they share a package name, my intent based navbar buttons get a little confused when trying to switch between music & phone. ie, open BT Phone, then press the music button on navbar - it does nothing. It thinks the BT app is a music app (which it is), so it stays there.

3) the JNI/mcu functions need to be relocated from the various bonovo 'apps' and centralized in the bonovoHandle app. I started to work a bit on this last night, and just didn't have the energy for it :) I think the basic discussion that Bokomaru and I had on this is to centralize all of the MCU control at bonovoHandle, and use intents/broadcasts to control the I/O.

---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------

Theoretically:

http://www.xda-developers.com/impro...-custom-linaro-gcc-cross-compiler-toolchains/

But it's a pretty hotly debated topic amongst Android Devs.
[Android Head-Units] leonkernan:
For sure, I haven't touched the music or settings side at all yet. It would certainly make more sense to split this thing up. The Bluetooth pairing and settings should probably live in the settings app.

I'd almost be tempted to start from scratch with a basic new A2DP app rater than try to split out and reuse the existing code. There aren't a lot of BT commands required for that to work.

The phone UI should handle that pretty well. It's already designed around talking to the Bluetooth Service in that way for the most part and i'm trying to keep it that way.

My eyes glazed over at the lower level code so far. Learning Android's little quirks is enough for me right now, let alone trying to remember how to code in native code. :)
[Android Head-Units] jkchr1s:
My head unit should be on Tuesday, I can't wait! :)

I just uploaded new build of Spotirius to github: https://github.com/jkchr1s/spotirius-android

APK is attached to post.

This app syncs satellite radio playlists to Spotify playlists so we can still listen to our favorite stations on our head unit. :D

Added:

* Rewrote using Retrofit, no longer blocks UI thread

* Notification panel now shows the sync progress

* Checks for duplicates against Spotify playlist instead of sqlite cache

* Much faster syncing

To sync, launch app, log in to Spotify, click menu button, add channels you want. Then click menu, Sync to sync. Enjoy!
[Android Head-Units] bas-r:
Hey, Does anybody experience the following?

I cannot see anything in the Nokia Here maps Settings page. It's completely blank and I cannot set anything.

I'm on stock 1.1.5, tried 1.1.1, 1.1.3. It used to work, but after a screw up from my side I did a factory reset yesterday and since that moment I cannot change any setting in Nokia Here maps. I've cleared cache, deleted and reinstalled the app, but nothing.
[Android Head-Units] blacklistedcard:
Sure it will.... I just did it. Unless your box can't handle it.

---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------

I still have to sit down and figure out creating a zip file with only the kernel. You can just flash the whole thing. Settings don't get wiped.