yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] guap:
thanks, upgrading mcu now.

- fully rooted

- backed up original recovery

- flashed twrp

- backed up whole rom

- upgraded v40 mcu

- flashed tuatara & regular boot yayyyyy :good:

also... I'm going to flash again twrp but, just saying, ho the f*** I'm supposed to use twrp CWM without any key? :eek::D

finally upgrading to xdauto after this step :)
[Android Head-Units] coyttl:
.. Touchscreen? :D

(I honestly can't remember if TWRP on this supports touch yet. I thought it did!)
[Android Head-Units] deeznutz1977:
Twrp is fully touch gui
[Android Head-Units] toologic:
You can try next scheme. Connect AB to HU as usual way and connect AB to headrest screen via HDMI-AV converter like this

I tested this circuit. it works. But i have very old version car-monitor (480px) and not use it now.
[Android Head-Units] guap:
yes, you're right... I obviously intended CWM :silly: too much recovery for today. Currently using TWRP

1st issue: cannot save apn in xdauto 1.1.6c
[Android Head-Units] pfarley11:
Hi All,

I just wanted to check in again on this. Does anyone have any thoughts on what might be causing the problem I'm having using FFT with xdauto? It will load the .img file fine.(xdAuto-1.1.6c.img), but no matter what I do (whether replacing the boot screen or not), when I select 'confirm modification', it starts to process indefinitely. (I haven't waited more than eight hours, but I assume it shouldn't take that long(?))

Any thoughts? Am I labeling the save file wrong?("update" (update.img)) Or, might I be doing something else wrong? Or, is there an issue with using FFT for xdauto that I haven't heard about?

Thanks again!

Patrick
[Android Head-Units] guap:
cannot fugure it out either... FFT and replacing boot image is a no go for me actually

my huawei e3131 works once reset default apn's, but it's a bit unstable... :confused: 3g coverage appears and disappears. Not a vodafone problem, my phone is 10cm far :)

also, the rom is absolutely amazing, fast and stable for now :good: great work!
[Android Head-Units] deeznutz1977:
Cwm is touch also swipe down for down. Up for up. Left for accept and right for back
[Android Head-Units] DiGiTY:
The dual Bluetooth radio/adapter thing... is it a feature of any head unit with the RK3188 chip or just this Newsmy model?
[Android Head-Units] Bokomaru:
I haven't had any of the other android head units, but I'm pretty certain this is a specific feature of the Newsmy hardware
[Android Head-Units] fifife:
I have just installed this hub

HooToo® 7-Port USB 3.0 Hub, 2 Smart Charging Ports (12V/5A Power Adapter, USB 3.0 Cable, VIA VL812-B2 Chipset)

it has a 12v input and seems to work very well. I have a WD 500g drive and logi web cam (to give me OK Google mic) connected to the AB through it. It gives me a couple of charging posts for phones as well. No more cables hanging out the lighter socket in the car. Just cut the wire from the provided power supply and put it behing a 5A fuse and job done.
[Android Head-Units] f(x):
I used to run into problem with the non-standard image folder on older (pre 116C) rom. Since It has been fixed with 116C rom, i have no problem replacing the logo or boot animation using FFT. Maybe try clear your window temp folder and run FFT as administrator? sometimes turn off antivirus might help as well.
[Android Head-Units] pfarley11:
I'll give it a try. How long should it take to process when saving, by the way? (I assume I'm giving it enough time, but just in case . . .)

Thanks!
[Android Head-Units] guap:
with 1.1.6c FFT works again. The point is: why use fft and rkbatchtool after that?

- flashed tuatara via rkbatchtool -> logo/anim changed

- flashed xdAuto 1.1.6c via twrp -> logo changed

so, not only the anim (/system/media) but even the logo is zip flashable. [MENTION=2190016]Zaphod-Beeblebrox[/MENTION] any hint about that? Zip are way more comfortable :)

I noticed that even twrp, before teamwin splashscreen, has its own "Amplified" logo"

On xdAuto rom itself: love the navbar, but can you pin to center the clock when removing buttons?
[Android Head-Units] f(x):
it depends on how fast your computer is. i have a decent computer and it didn't take more than 5min to finish. If it takes more than half hour, i would say there is something wrong with your computer's setup, either too slow or running out of memory, hard disk space, or some window component is not up-to-date etc.... Do you have access to another computer and try it there?
[Android Head-Units] pfarley11:
I'll do that. I just tried emptying temps and running as admin. It's still doing the same.

I'll borrow a computer and try again.

Thanks
[Android Head-Units] sn2k:
I have found the misstage, but is a bit specialy: The xdauto-1.1.6.c.img have added a boot image with FactoryToolV4.4, and when i flash this and start Supersu become a error message, the message update binary not come.

When i flash the orginal xdauto-1.1.6.c.img all work fine.

Give there an other methode to change the bootlogo?

[MENTION=2190016]Zaphod-Beeblebrox[/MENTION]: Thanks a lot.
[Android Head-Units] guap:
bootlogo should be in boot.img. Unfortunately it doesnt appear to be in a standard ext or cramfs format... Any hint?

Bugs an issues so far:

- smartdial doesnt work -> ExDialer installed, need a way to bind it to phone button in navbar

- usb modem huawei 3131 doesnt work, got signal but no data coverage -> inspecting about AT commands for "modem only" mode -> no luck, got coverage but no 3g :|

- usb modem alcatel OneTouch X215S works out of the box

Attached Link for my vw logo bootanimation.zip for 5261 owners and/or vw fans

Installation:

- rename the one in /system/media

- copy new animation to /system/media

- test with "adb shell bootanimation" (ctrl+C to stop) BEFORE restarting (it works for me but I assume no responsabilities, so, check by yourself)

- optional: delete old bootanimation and reboot

https://dl.dropboxusercontent.com/u/7403995/Newsmy/bootanimation.zip

enjoy ;)
[Android Head-Units] Juktas:
I believe there's a post on proper powering of the Android unit, but I can't find it right now. My home PC is still USB 2.0. Should this have enough power to flash the Android box? I can hit the Switch button in RKBatch and the box turns green, but if I try to do a Restore operation it fails. I'm guessing I'll have to wait for my DC adapter to show up next week to flash Tuatara and xdAuto? I've already verified drivers are installed, tried using the Release_DriverAssitant driver install tool, and tried RKBatch with both SUPPORTLOWUSB=TRUE and SUPPORTLOWUSB= in RKBatch's config.ini.

TIA . . .

Andy
[Android Head-Units] ElfinJNoty:
I've had pretty good experience with this on an old tablet as well as on my lg g2 before lollipop, and an old evo 4g lol

I think its worth taking a look at the scripts to get an idea of what Exit_Only does to increase speed and performance. I know the entropy helps a bunch on non-art KitKat. Dnsmasq should also increase data speeds receiving.

http://xdaforums.com/showthread.php?t=2411161[ /URL]

OKJ :thumbup:
[Android Head-Units] Bokomaru:
The only time I didn't have enough power when plugged in via USB was when I also had the HDMI hooked up. You should be able to flash the ROMs with only the USB hooked up.
[Android Head-Units] guap:
flashed many times via usb only, no problems so far. Maybe a faulty cable/connector?
[Android Head-Units] guap:
totally agree. If someone is interested he can try by himself :) Same as xposed framework (works like a charm btw ;) )
[Android Head-Units] Juel-DK:
Known bugs on my HU with xdAuto 1.1.6C.

1. Audio ducking dont Work on streaming apps ONLY in the Radio app when iI use Here og Maps

2. VLC still have the low audio problem after some hibernations. The fix is to go into the radio and out Again, then the volume on VLC is correct.

Other than that, no issues here :)
[Android Head-Units] guap:
no problem of sort with mxplayer, maybe it's a vlc issue? It's still a bit young on android...

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

There is a way to customize the navbar icons?
[Android Head-Units] -=Jeff=-:
Juel-Dk, I see you are using HERE maps.. are you able to access the settings on HERE with xdAuto 1.1.6c?
[Android Head-Units] guap:
found a nice app: "PowerToggles" https://play.google.com/store/apps/details?id=com.painless.pc&rdid=com.painless.pc

it adds 1 (or 2) quicktoggles row directly in notification area. Bonus: you can add your own app to the bar, so I added the second bt icon for handsfree app :o

screen attached

Unfortunately cant find any xposed modules to add customizable buttons to navbar :)
[Android Head-Units] Juel-DK:
Yes no problem at all :)
[Android Head-Units] kommando:
Need some advice, got my NU5002 yesterday and its installed in the car, I have changed the MCU to ver 41 with no issues and then using an external SD card update.img installed Xdauto 1.1.6c, this boots fine but the memory is screwed, only 1G or ram, no internal SD (NAND memory) but the internal is accessible. TWRP cannot install a img file as it needs access to the internal SD card. Can get into recovery but selecting Tuatara 1.1.4 update.img fails when it tries to access the internal SD.
[Android Head-Units] guap:
there are some issues upgrading from stock to xdauto. Flash tuatara via rktool and then via recovery flash xdauto in zip format.

About ram... Maybe there are other versions? Ram should be decetcted correctly in any case...
[Android Head-Units] kommando:
Can't get it to flash, I see it in device manager on the laptop as Andriod ADB interface and the driver shows as Fuzhou Rockchip Electronics Co., Ltd. but I cannot get the rockchip batchtool to see it to connect. Never like to use Windows to connect to android, pile of poo.
[Android Head-Units] guap:
did you followed wiki instructions about rkdriverassistant and rktool usb settings?

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001#Update_ROM

section "Update via Computer with RK Batch Tool"
[Android Head-Units] kommando:
Yes those are the instructions, the RKtools never connects as squares are all grey but Windows sees it and has the driver as being Fuzhou Rockchip Electronics Co., Ltd. Will try another reboot.
[Android Head-Units] guap:
try to change usb port if you have more than 2... On most laptop the left usb port group are on hub and the single right is direct to the chipset
[Android Head-Units] ElfinJNoty:
Also make sure you are holding down the reset button when you plug in USB host to the computer as this launches the android box into the download mode for rkbatchtool
[Android Head-Units] kommando:
Well thats two Win 8.1 laptops and a Win 7 desktop and all exactly the same, windows device manager has them showing and with a rockchip driver but the RKtools program stays grey. The XP one is too slow and flaky to risk any connection.

---------- Post added at 06:13 PM ---------- Previous post was at 06:03 PM ----------

It was the button, I thought you had to press once you are ready, it has to be pressed before you connect. Flashing now, thanks to all.
[Android Head-Units] guap:
a mistery :eek:... I never pressed ANY button. But I'm connected to the HU too
[Android Head-Units] Zaphod-Beeblebrox:
If you boot the Android Box normally, you should be in ADB mode (different driver set - don't load the Rockchip drivers to this 'device'). You'll want to fix this particular driver set up as having ADB access is handy for debugging, pushing updates, etc.

In RKBatchtool, while in ADB Mode, the box will show as Green. Pressing 'Switch' will cause the box to reboot into bootloader mode (where the Rockchip drivers should then be loaded), and it will show up as pink in the RKBatchtool.

Recap:

Green = ADB mode (and recovery)

Pink = Bootloader.

the common 'adb reboot bootloader' works here too .
[Android Head-Units] kommando:
Not here, memory is restored and a reboot followed by a flash to XDA and all working other than a blank settings screen in Here so can't get the offline maps to go to the external SD card or set the speed warnings to realistic. XDA looks very good and the sound is much improved once Viper is going.
[Android Head-Units] Juktas:
Thanks guys. I had the ADB drivers installed correctly for the 1st step, but had installed the ADB rather than the RKBatch drivers when it was in bootloader mode. All appears to be well now. :)
[Android Head-Units] danny131313:
Wiring Harness

Is the wiring harness a standard type or is it specific to the Carpad, I know one end is an ISO but what is the other end which connects into the HU?

(I think I may have screwed my current harness up - too much soldering and chopping!:eek: )
[Android Head-Units] Bokomaru:
Luckily you should have another one. There should have been one with an ISO end and another one that either has no connectors or some car specific connectors.
[Android Head-Units] Kevinkuensken:
[MENTION=2190016]Zaphod-Beeblebrox[/MENTION]

can you make a helper apk for the Navigation icon for igo Primo?
[Android Head-Units] guap:
package name needed. I'm going to do an helper for ExDialer... Or waiting some news about smartdial with stock dialer
[Android Head-Units] Zaphod-Beeblebrox:
I'm not going to be making anymore helpers. The source code for the ones I made is on our github. Some basic steps to create more was posted a few pages back (and I think copied into the wiki). It's time for other people to step up and start making these as needed for random apps. I don't have the time to keep up with it.

ExDialer *should* work without a helper. Pretty sure I tested it.
[Android Head-Units] leonkernan:
In what way is smartdial not working?

I've only tested with Exdialer and the Android standard phone app and both call out through the stock app. There might be another intent that smartdial uses that we need to handle.
[Android Head-Units] Kevinkuensken:
Hello,

can i change the Android Boy permanently to Galaxy S 5?Give it a cabel or adapter from Firewire to microusb?
[Android Head-Units] guap:
you're right :) my mistake to not say "always" at the first launch

expected behaviour in dialer: start typing letters and contacts appears

real behaviour: start typing, only numbers shown :)

a rapid question: is the e firewire 400 cable standard?!?!? Why it's labeled "to host" and "to android box" at each connector?
[Android Head-Units] leonkernan:
Ok, I got confused. I thought you were talking about a different dialer app that wasn't working with our phone setup.
[Android Head-Units] Kevinkuensken:
Can i use screen mirror via Bluetooth or wifi?or must i buy a cable?i have a Galaxy s5
[Android Head-Units] Bokomaru:
If you are asking if you can use a Galaxy S5 instead of the Newsmy Carpad Android box then the answer is no. This is a specialized piece of hardware that is setup for this setup only.

---------- Post added at 08:18 AM ---------- Previous post was at 08:12 AM ----------

The only difference is that the "To Host" end has a right angle connector to make it easier when connected to the back of the head unit when installed in a car.
[Android Head-Units] guap:
thanks, I've already check with a tester. Since I've ordered a longer cable i was a bit scared :D

a little issue: after I launch the bt bonovo app, both music and phone button doesn't launch poweramp or exdialer but the bov app itself
[Android Head-Units] danny131313:
Thanks Bokomaru, it didn't occur that I could use that. Is it possible to remove the pins from the small HU end? Looks very small but I guess the pins must come out somehow. Will do some googling!
[Android Head-Units] Bokomaru:
I think you would likely be better off just starting over completely
[Android Head-Units] JeepAndroid:
So I accidentally pushed the FireWire cord in the wrong way round and damaged the male FireWire things on the head unit.

Since then the head unit gets no sound and really really bad flickering image from the android box!

Looking to see if summer will sell me a new head unit separately!
[Android Head-Units] kommando:
I would be buying a socket (check first as there will be different types)

http://www.ebay.co.uk/itm/6-Pin-Pol...749?pt=LH_DefaultDomain_3&hash=item418a13c555

and talking nicely to my old school TV repair guy.
[Android Head-Units] Zaphod-Beeblebrox:
I'm pretty sure I've explained how the intent buttons work before, but let's go over this in detail.

The intent buttons are semi-smart, and entirely dumb all at the same time. Rather that setting up some complicated app/list tool, I decided to rely on the intent system the way Android was designed. I also threw in a few tweaks to make it 'smart'.

It doesn't matter which button we are talking about (Music, Phone, Auto, etc), they all operate in the same way, with only the Intent used to generate the app list as the difference.

On Key Down (the moment you press the key, but have not released it yet)
Retrieve a list of all running apps, Retrieve a list of apps that match the Intent.
Loop through the list and find the first Target App that is currently running (if any).

OnLongpress (this is a time thing. Long press occurs when you hold the button longer than the 'timeout' period)
Ignore initial search and launch the Activity Chooser with the target intent.
This will show a list of all apps that match the intent and allow you to choose one.

OnKeyUp (if before the longpress timeout)
If a running target was found in Keydown, then bring that app to front.
If not, Launch the target intent.
If you've never launched this intent before, Android will present the chooser screen and allow you to select 'just once, or always'.
If you've set an 'always' app, then this is the app that is launched.

So what does all this mean? Well, it allows you to have multiple apps for each target, allows you to set a 'default' (through the use of Android's 'Always' open option), but also allows easy access to the other apps without having to change your defaults.

So if Radio is my default Music app (and it is). But I want to listen to poweramp for a while, I just longpress the music button and start poweramp. Now, I can continue to use Android in anyway I want to. No matter what app I'm in, when I press the Music button, my code sees that Poweramp is the most recent 'Music App' in memory, and goes back to PowerAmp rather than launching the Radio. Next time I reboot, Radio is still the default. If I want to switch back to Radio without rebooting, just longpress Music, switch back to Radio and it is now the most recent Music App in the process stack.

So that is why when you launch the BT app, the other buttons 'no longer work'. They do actually work, exactly as intended :)

The complication with the current BT App, is that it is registered as both a MUSIC app, and a PHONE app. We are working towards separating those apps, but you can currently thank Bonovo for wrapping them up into one package.
[Android Head-Units] leonkernan:
Oh yes, thanks very much Bonovo... :D

Still working on this, trying lots of ideas offline but its slow going at the moment.

It's the middle of winter here so running back and forward to the garage to test changes isn't very appealing right now.
[Android Head-Units] guap:
thank for the explaination. I read all pages but I missed some points, it was a bit tricky realize all dificulties before having HU on my hands.

I whould rather prefer multiple customizable buttons, so everyone can decide to link a button to his preferred standard apps or apps used sometimes.. But I remember you were facing some problems implementing aokp navbar system, so I'll live happy with bonovo oddity :D

PS any hint on bootimage logo customization? It's in boot.img? How can I access it without rktool? No luck with unzip, cramfs mounting...
[Android Head-Units] kommando:
On my NU5002 in Here the settings screen is blank, so cannot set speed warning thresholds or change the default map storage to external SD, so I raised a support ticket and the reply was.

Hello John,

Thanks for reaching out.

Our application does not support the Android head unit at the moment.

We apologize for an inconvenience.
[Android Head-Units] Juel-DK:
Ok :( no issues with xdAuto 1.1.6c and nu5261 :)
[Android Head-Units] kommando:
xdAuto 1.1.6c and NU5002 with issues :o (with Here that is, everything else is fine, just downloading a map and will see if that forces the settings screen to wake up)

Well downloading a map made no difference other than reducing the internal memory ;)
[Android Head-Units] -=Jeff=-:
I still need to test HERE with the NU3001.. I cannot access the Setting page ( always is blank)

'

But that was with 1.1.6b2 I need to try 1.1.6c. I sure hope it works..

------

you know what would be a nice thing on this unit.. When the illumination is wired and you turn on the lights, it dims the screen, I think right now you need to dim it with the Settings app for the unit (where the RGB LED settings are). I need the unit as bright as possible during the day, but not so much at night
[Android Head-Units] Bokomaru:
That is the 'Car Light Backlight' setting in the MCU Config app. I suppose it should be renamed 'Screen brightness when lights on'.
[Android Head-Units] wacko37:
Bit off topic but still in regards to screen brightness.

I'm using tasker to adjust the screen brightness based on the time of day. Problem is that tasker puts the unit in sleep mode after its adjustment, so i then need to swipe the screen to wake up the unit.

Wouldn't really bother me but it kills sound etc.

I tried using an input key after the adjustment but to no avail.

Any help is much appreciated. Thanks
[Android Head-Units] -=Jeff=-:
What does your tasker task look like?

I could do that for mine.. I would only have 2 times to base it off of for me to keep it simple
[Android Head-Units] usafle:
What Jeff said, you need to copy/paste/export what your tasker looks like so we can figure out what's going "wrong". I thought about doing this with tasker also, just keep forgetting about it. But, every time I manually raise and lower the brightness; I curse at myself for not doing it. LoL

The "illumination wire + setting in MCU" still doesn't lower the brightness to minimum values.

Try this for tasker:

Start Tasker and tap the + button on the bottom o the main screen to create a new profile. Give it a descriptive name, such as "Brightness Down" for example.

Choose the "Time" context on the presented menu.

For the "From:" option select the time of day you wish to have brightness lowered.

Un-check the "To:" option, and tap the green "Accept" button.

On the "Task Selection" dialog tap the "New Task" button and name it "Lower Screen Brightness" and tap the "Accept" button.

Tap the "+" button to add an action, select "Display" category, select the "Auto Brightness" action, select the "Off" option on the "Set" drop-down, and press the green "Accept" button.

Tap the "+" button to add another action, select "Display" category, elect the "Display Brightness" action, set the desirable low level (20 being the lowest recommended setting), ensure that both "Ignore Current Level" and "Immediate Effect" options are checked, and tap the green "Accept" button.

Tap the green "Accept" button on the "Task Edit / ..." screen.

On the main screen tap the "Brightness Down" profile once, then tap on its wrench button, and select the "Clone" option.
Tap the newly-cloned profile, tap its wrench button, select the "Rename" option and name it "Brightness Up".

Tap on the clock icon, select the "Edit" option, change the "From:" time to the time of day when you'd like brightness increased, and tap the green "Accept" button.

Now tap on the task itself, select "Rename" option, name it "Increase Screen Brightness", and tap the green "Accept" button.

Tap the task again, and select the "Edit" option.

Tap on the "Display Brightness" action, set the Level to a higher setting, and tap the green "Accept" button.

Tap the green "Accept" button on the "Task Edit / ..." screen.

Ensure that on the main screen, the button on bottom-right reads "On", and exit the Tasker app.