yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] ElfinJNoty:
I know it has been asked but have not gotten an answer on previous inquiries.....

Is there a mod/app/xposed module that would allow us to INCREASE that maximum brightness for the screen?

I see that antiglare screen protectors as an option, but feel there could/should be a way to modify the default lux values, and allow for a brighter screen during bright daytime conditions.

Just seemed appropriate to ask again since the discussion is about display brightness adjuatments
[Android Head-Units] Bokomaru:
Of the tests I've done I think we are at the max brightness the MCU will allow now. It is possible that MCU code changes could allow this to go higher or maybe a hardware modification.
[Android Head-Units] wacko37:
Guys thanks so much for all the replies, and sorry for the late response.

Anyhow this was one of the easiest Tasker profiles i have ever had to setup. I have exported my profiles and attached here. Makes no sense why the unit goes to sleep.

Again i am eager for your replies. Thanks
[Android Head-Units] -=Jeff=-:
Yep same response

checked tonight, does not work with 1.1.6c blank settings

[IMG="screenshot"]https://lh3.googleusercontent.com/-WtwTRF5sdfU/VYlDuc86p8I/AAAAAAAAHQE/hiExthLT8ek/s912/HERE-settings.png[/IMG]

Thinking of reinstalling and installing again, wonder if something is corrupt or not correct
[Android Head-Units] jpsandiego:
a few questions

Hey guys,

Sorry if this has been covered, but read over 500 pages and couldn't find answers.

1)is there a way to change the radio region to USA?

2)is there a way to update boot logo and animation using fw factory tool without killing root? I was able to swap them successfully but after installing the 6c rom, root was gone. Tried it twice with same results. It worked with tatura's rom.

3)automotive navbar shortcut gives me zaphod error. Anyone else have this?

4)wondering the correct voltage of the dc adapter needed to power the android box when out of the vehicle. I have seen it mentioned here as 5vdc and then again as 12vdc. Has anybody confirmed which is correct?

Nu3001-02 running xdauto 6c

Thanks for the help
[Android Head-Units] kommando:
Ref the Here settings blank screen I have been playing around with settings, eg changing the font size, turning the soft android buttons on and off etc and cannot get the settings screen to display any settings. For offline maps I tried Navmii but that looks very 3rd rate with the car going off road all the time and sometimes the car showing as being in reverse.
[Android Head-Units] -=Jeff=-:
one thing I found is that on my Nexus 7, with HERE the settings only work in portrait.. if I am in landscape mode and I press settings it makes the screen portrait.. Maybe that is where the issue is?

since the map screen in HERE work in both landscape and portrait?
[Android Head-Units] Bokomaru:
Factory 1.1.9 posted

Just noticed that Factory 1.1.9 was posted here http://pan.baidu.com/s/1eQq67Zk

Don't think we had seen any 1.1.8 either so I posted the release notes included for those as well. Looks like they finally decided to switch the partition sizing. I'm still downloading so I can't check, but hopefully the order/sizing lines up with what we are doing with xdAuto.

V1.1.8

1. Modify the FM interface.

2. Modify the Bluetooth interface.

3. Solve reversing radar screen radar distance show abnormalities.

4. Addressing Bluetooth phone number redial phonebook problem unresponsive.

5. Added 2.5GB user data software for the built-in 16GB EMMC car machine over.

If the previous user's documents update_v1.1.8_2.5G user data.img burning tool to burn, you can not be upgraded.

V1.1.9

1. Increase the dvr drive. (This has nothing to do with the current user)

2. resolved TF card inserted can not recognize the bug.

Note:

1.update_v1.1.9_2.5G user data.img for large user data partition, if the previous user data partition (System Settings - Storage - Internal storage capacity shown) is not the size of 2.5GB, you need to use to burn recorded programming tools.

2. Before upgrading the user needs to modify the file name update.img, otherwise the system can not recognize the upgrade file.
[Android Head-Units] kommando:
On my Jiayu S3 with a 5.5 screen Here settings is fine in portrait but will not go to landscape at all on any screen including map, auto rotate is on. I will load some auto/force rotate apps and see if one gets the screen to appear, only needs to appear once.

The auto rotate apps did not work either, they had no effect on the screen at all, I was hoping by forcing portrait the screen would rotate by 90 degrees but even reverse rotation did not work.
[Android Head-Units] Zaphod-Beeblebrox:
Storage changes look to be for a 16gb version?? Wonder if there is a new AB version coming out?

I'm curious about FM interface changes. Going to be out of town for a few days. Maybe some enterprising soul will flash the 1.1.9 and take some screenshots?
[Android Head-Units] Bokomaru:
You're right, I overlooked that. I wonder if the v3.3 board is going to have 16GB by default. There were some previous comments in the kernel about specific GPIO needed for v3.3 board.

This just illustrates why the rockchip image flashes are bad. Now they will always have to release multiple version per release, when if they used the standard OTA packaging one release could handle multiple hardware versions.
[Android Head-Units] nichos:
I just received my unit and I wanted to clarify something in the wiki. I want to flash xdauto, do I need to update the MCU or anything first? Can I just follow the rock flash directions, install clockwork and put xdauto in the SD card and go from there?

Thanks in advance.
[Android Head-Units] Juktas:
It's recommended that you flash Tuatara's image first, and then flash the xdAuto image. People have had problems going straight from factory to xdAuto. I used RKBatch to flash xdAuto, and didn't experience problems.

You can update the MCU whenever you'd like.
[Android Head-Units] guap:
2) bump for bootlogo... rkbatchtools lead to missing root when used with xdauto.

bootanimation.zip can be replaced simply with root access, is located on /system/media

3) please be more specific... Which error? What are you trying to do?

4) 12v, 1A at least, more if you are planning to use a 3g dongle. My box was powered 12v directly for 3 days without any issues. Also, your car system is 12v and HU powers android box via 12v. The android box itself downvolts the "firewire" and optional power supply input to 5v to operate ('cause this is his nominal voltage and thus it can operate via 5v usb). However, I'm taking NO responsabilities :D

You are not forced to update MCU before flashing xdauto but it's strongly suggested because latest xdauto has a HU setting app that can take advantages of all new options managed by latest MCU.

so correct steps whould be:

- start stock

- update mcu (when hooked to HU!)

- flash tuatara via rkbatchtools

- upgrade to xdauto using the provided recovery

followed this procedure on 2 different units, no problem at all :good:
[Android Head-Units] Bokomaru:
Is this still an issue? After fixing the filesystem issues, I haven't been able to reproduce a failure at all.

Edit: If anyone is still having this issue, send me a copy of their /cache/recovery/log to investigate
[Android Head-Units] jpsandiego:
Thanks for the response, makes sense. As for clarification to number 3, when i click the automotive " OBD" shortcut for torque in the lower menu, it produces an error and will not open anything. It works if I click the app shortcut.

Any ideas on the radio region?
[Android Head-Units] guap:
did you installed torque helper? :angel: apk located in zaphod's repository

no info about radio region, barely don't use radio at all :)
[Android Head-Units] jpsandiego:
Yeah, i used the helper to no avail. This is not a big deal to me so I can live with that. Loving this rom so far!
[Android Head-Units] Bokomaru:
Installed 1.1.9 on my test setup. The radio looks a bit nicer but I don't see anything major, was kind of expecting a place where RDS data would eventually go. One thing I noticed that I'm not sure was there before is a Radio widget that lets you start/stop the radio and it shows the station. Touching the widget anywhere other than the play/pause button opens up the radio app.

MCU config app has a checkbox for RGB-Camera now.

"Set the Standby" is just on/off again and no configurable time

Edit: wow, didn't realize how blurry those pics are but good enough to get the idea
[Android Head-Units] Juktas:
Maybe not - I didn't see that it was fixed, so went with the intermediate Tuatara process that I found. I didn't try going straight to xdAuto, so can't say for sure.
[Android Head-Units] Duck Dodgers:
One thing I've just discovered (after plugging in the AB to my ancient laptop) is that the AB is not receiving power when using USB 3 male to USB 3 male cable when plugged into USB port on AB and laptop USB ports (all of them). I know AB is only USB 2..........and so is my laptop!

Now when I connect the USB 3 cable to any port on the laptop, then plug the other end into the female USB 2 to mini USB male adapter(that came with the AB), then plug into the mini USB OTG port on the AB - powers fine.

Just need to install JDK, etc now to get the box seen and root it!
[Android Head-Units] kwalsh24:
Is the radio app in full English now or are all the menus still in Chinese ?
[Android Head-Units] nestortoledo:
Bluetooth interfaces is changed too acording to changelog.

Can you post photo also?

Enviado desde mi LG-H815 mediante Tapatalk
[Android Head-Units] guap:
sorry, cannot reproduce this behaviour :|

same here. And not a big deal after all regarding the boologo thing: with fft every update will results in a factory reset (if I'm correctly reading the wiki), thinking about changing bootlogo via fft it's a no go anyway imho

no need of whole jdk, install minimal adb and fastboot http://xdaforums.com/showthread.php?t=2317790

for power, the ab receives power ONLY from mini usb port afaik, it can't be usb3 related.
[Android Head-Units] supremekizzle:
Nevermind
[Android Head-Units] leonkernan:
There were hints at changes in the last code leak.

I haven't seen how they changed the look but i'm guessing mainly cosmetic rather than functional changes, similar to the radio app.
[Android Head-Units] Bokomaru:
Looked all cosmetic to me. Parts of it look nicer than it used to, but I'd guess it's mostly all superficial.
[Android Head-Units] f(x):
here are some screenshots of v1.19 or is it v1.20???
[Android Head-Units] leonkernan:
Thanks, as expected it's mainly cosmetic.

Looks like they are trying to match the default setup of the other Chinese headunits a bit more with those ugly widgets.
[Android Head-Units] supremekizzle:
OK. A few things.

1. Is there a way to launch the radio app in the background so I have music right away like a real head unit? Ideally, I could have music play from my phone right away, but since I have to go into the Bluetooth app before the nav buttons work to press play it kinda blows that plan out of the water.

2. Speaking of the nav buttons, how can I change their defaults? They somehow auto assigned themselves and I want to change their functions.

3. Those pictures of the new software actually look nice. I might move to that as it seems more optimized than XDAuto does. The phone app for instance launches as if I'm on a phone in portrait and the dial pad is unusable because it's so scrunched up.

4. The screen dims when the headlights turn on, but to go dimmer I have to go in and adjust the brightness slider to dim it to night usable levels. Why isn't there an option to go all the way dim in the 'update settings'? 2 part dimming seems super flawed.

These are the few issues I've experienced.
[Android Head-Units] leonkernan:
You probably shouldn't be using the Google Phone dialer on XDauto. It's almost completely untested.

The Google built in dialer adds itself as a consequence of us setting we have phone support. The Kitkat version doesn't support landscape mode though which is why it looks odd.

The phone in those screenshots is the Bonovo Bluetooth app, which is also what our Bluetooth app is based on.

Until we add contact lookup support to that (the new one probably doesn't have that either) something like Exdialer would be a good alternative.
[Android Head-Units] Duck Dodgers:
+1 for ex dialer
[Android Head-Units] Zaphod-Beeblebrox:
Tasker is your friend. Learn how to use it.

All of the intent buttons operate on standard Android default intent practices. If you've set an app as default, and want to change it, just go to the app in settings -> apps and 'Clear defaults'. Then when you hit the intent button again it will ask you which one to set as default.

Brightness level when when Illum line is set is set in the MCU update settings app.
[Android Head-Units] supremekizzle:
That's what's odd. I went in to clear the defaults of apps that were set and when I got into the settings the 'clear defaults' was greyed out. Something must be amiss. I'll reinstall XDAuto and see if that clears up the issue.

I know how to set the lights-on brightness in the update settings app. What's annoying is that I have it set all the way down for when the lights are on. So I turn lights on, screen dims to the low setting I had set. However, if you go to the brightness slider in the notification window, you can adjust it down even further. It'd be nice to go down to this absolute minimum initially when turning on headlights. Shouldn't be a problem with tasker, right? Nope. The box and MCU don't talk to each other so setting tasks like 'MCU brightness minimum-> set Android brightness minimum doesn't work. Same with a Bluetooth solution. Since the box doesn't sleep right away but the MCU does, a nice tasker event to play music through phone by pressing the Bluetooth play button on the HU would be 'screen on-> trigger play' at this point the play button would be 'pressed'. My phone, seeing the head unit as a Bluetooth device, would register the play and launch Google play music on my phone and start playing. This is useful for situations like when I'm driving along... Doo dee doo dee doo... Whoops I need gas. Shutting off the car stops music on my phone via a stop intent. But since the box never went off, when I start my car again there's no way for the box to know to send out a play command again to resume music. But it would if it registered MCU screen on. And guess what...... I could just hit the play button in the nav bar to restart the music. Lol no. I have to first go into bonovo Bluetooth app before the nav button even works :laugh:
[Android Head-Units] f(x):
Quick tip for you. If you want your reverse camera to turn on whenever you want, you can connect your camera's +12V to V.CON 12V (Brown wire), reverse signal to HU's reverse-input (Orange wire). That is it, you don't need anything additional switch or diode. Backup camera will turn on when reverse or when you open up Backdraft app.
[Android Head-Units] Zaphod-Beeblebrox:
Don't use tasker to trigger on screen events. Use 'BT Near' events. I use tasker to auto connect BT to my phone (Tether) anytime the phone is 'near'. works nearly flawlessly.
[Android Head-Units] supremekizzle:
Isn't the camera always receiving power then? It shouldn't matter for most, but my camera has LEDs....

If i wanted a similar set up I could attach reverse light bulb 12v to the camera so it comes in when selecting reverse, but also have the V. 12 Cont. Also going to the camera but stopping at a toggle switch. That way I could flip it on. As a bonus I could branch off the toggle switch a 12 constant wire that goes to the reverse in wire on the HU. That way it also automatically launches backdraft. Sound legit?
[Android Head-Units] f(x):
no. the V.CON 12V will only have power when Backdraft is turn on, or car in Reverse. As soon as you close backdraft or out of reverse, power will cut off to V.CON by default.
[Android Head-Units] supremekizzle:
Crap. I wish I knew that. So car in reverse sends 12v to head unit via reverse wire, then V. 12 Cont. Sends out 12v to the camera? No reverse light power needed? Looks like I have some rewiring to do...
[Android Head-Units] f(x):
Yeah..that is correct. :)
[Android Head-Units] Duck Dodgers:
Cheers f(x)

Not ventured down the install of camera route yet. Was wanting to get the setup of HU/AB 1st. I'm going down the wireless transmitter/receiver route so need to wire it up the the reversing light. I think the receiver has a black and red cables plus the yellow connector for the adapter on the head unit. The HU adapter has the V.CON and REVERSE wired together on a connector so I'm assuming that the wireless receiver will need the red and black wires on the same connector to put the 2 together?

I'm hoping to get the dual Fakra radio antenna adapter fitted this week or next. I'll take some pics of the setup as probably easier to see what I mean!
[Android Head-Units] kommando:
Never tried a cordless reversing camera but the posts I have seen of people trying them is that the lag and picture breakup problems make them next to worthless hence why I use a corded one.
[Android Head-Units] -=Jeff=-:
I am using this Camera:

http://www.amazon.com/gp/product/B00EHD8J6S?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00

amazed by the picture quality
[Android Head-Units] guap:
widgets are very ugly but I like bt/radio/phone app
[Android Head-Units] blacklistedcard:
That eq in the radio application. Does it actually work. Or it is a picture?
[Android Head-Units] Bokomaru:
Just a picture
[Android Head-Units] briangig:
I've read all I can read, but I don't see anyone else having these three issues.

I am running xdAuto-1.1.6c on my NU3001, loving it so far, great work everyone involved. I have two audio related issues. It seems the Radio app volume never stays the same, and almost has a mind of its own. One example, if I use the Radio, then switch to say...Play Music, and then after some time, go back to the Radio, the volume on the Radio will be super low. If I adjust the dedicated Radio volume from within the Radio app itself, it will all of a sudden shoots up as soon as I touch the volume slider. Its like the audio from the Radio was ducked? I also had it randomly shoot to 100% when I first flashed it and was messing around with it in the driveway (and almost crapped my pants), trying to avoid this again.

Next issue, when I use Viper4Android, I lose turn by turn voice prompts from Google Maps (the music playing simply ducks, and I get no voice). I haven't been able to find anyone on Google with this issue.

And the final third issue, that I don't think it software related, cause I was experiencing it on Tutara's ROM and on MCU 3x, my screen doesn't always auto-power on when I start my car. Now that I can enable extended standby, I am noticing this more and more. Happens maybe 40-50% of the time. I simply press the power button, and everything comes up fine, but I am curious what the cause could be. I am thinking about moving up to the 8" screen, and if the issues persisted (no power button), I would be SOL I think.
[Android Head-Units] Bokomaru:
I've noticed some similiar issues on my test rig (with NU3001), but I never have had time to dig into it. I suspect it's a timing issue where the android box is sending the command to power on the screen too early.
[Android Head-Units] kommando:
On the 8" you tap the screen to get it back on, it happened to me a few times on my NU5002. So no need to not get the 8" because of this fault.
[Android Head-Units] x5nder:
With regards to the xdAuto navbar, is there any way to get support for GoneMad Music Player (GMMP)? For those of us with a large music collection it's actually a better choice than PowerAmp...
[Android Head-Units] supremekizzle:
Anyone else having issues with getting the time to stick on reboot? My time resets every time the box powers down.
[Android Head-Units] ElfinJNoty:
Scroll back and read through the past 20 or so pages and you'll find Instructions where to find one of the "helper" .apk's and how to modify it to work for your app of choice
[Android Head-Units] x5nder:
Ah, thanks, found it. Unfortunately I have zero experience with Git or compiling APK's :(
[Android Head-Units] leonkernan:
You aren't alone on this one, it's still happening for me too.

I found the radio volume on 0 today for no reason at all. I intend to figure out why soon.
[Android Head-Units] Juktas:
Zeroed radio volume is happening to me as well. Hopefully we can figure that out soon!
[Android Head-Units] guap:
After a few days investigating on bootlogo, I discovered a stupid workaround to update it without reflashing with rktools (which will result in destructive update) using temp files of FirmwareFactoryTools (FFT from now)

- assuming you're running latest xdauto: flahed tuatara via rktools and then updated via recovery with xdauto .zip

MAKE A BACKUP!!!

1- create your logo (1024x600, ppm ascii format, more info HERE thanks to [MENTION=5612737]toologic[/MENTION] )

2- open your running xdauto in .img version with FFT

3- load your logo and confirm modifications, save your new .img and close FFT

4- delete FFT temp files

5- open FFT and load YOUR .img

6- check the path $yourFFTinstalldir\Temp\Android\Image\boot.img and push it via adb or move it anyway you like to external_sd

7- erase /boot on your device (maybe not needed, just in case) - adb shell dd if=/dev/zero of=/dev/block/platform/emmc/by-name/boot bs=4096

7- flash your boot.img - adb shell dd if=/mnt/external_sd/boot.img of=/dev/block/platform/emmc/by-name/boot bs=4096

8- reboot and enjoy your new logo :)

Note that bootlogo is embedded in kernel, you have to repeat this procedure for every update AND with CONSISTENT components: if you are on xdAuto 1.1.6c you will need 1.1.6c .img to obtain a functional boot.img

Currently I'm trying to figure out how to work directly on boot.img bypassing FFT
[Android Head-Units] Bokomaru:
That seems like a lot of effort when you could just build your own kernel or complete rom easily, then you can track the updates and rebuild whenever a significant change has been made.
[Android Head-Units] guap:
less effort then building a whole development environment for a custom logo imho ;) I have no idea about compiling a rom from a source
[Android Head-Units] Bokomaru:
No better time than now to learn. We can always use more people to work on the rom
[Android Head-Units] Duck Dodgers:
I too have had this issue (NU5261) - I am still on stock ROM and MCU v40 - I've also noticed that if I've been using exdialer or another "offline app", when ignition is off, HU goes off. If I'm playing internet radio app (using wifi dongle) a message saying "off" appears but HU stays on. Doesn't come back on automatically if ignition turned on (have to touch the screen). Is this something to do with the ACC cable at the back?

I need to turn off the Canbus pop ups. Door open is showing wrong side and air con changes are getting on my nerves!!!
[Android Head-Units] leonkernan:
Attached is a sample of what i'm working on at the moment. This is the Bluetooth settings page, with a hint of Bonovo's updated look applied.

Turns out Bonovo found Bluetooth pairing too hard, so they just didn't do it. It's always been up to your phone to handle the connection which is why people have been having problems.

Last night I got very basic pairing working and as you can see in the screenshot, it's happy to have multiple devices paired. As expected only one can be active at the same time.

Hopefully i'll get this cleaned up over the weekend along with the new separated Bluetooth music player.
[Android Head-Units] kwalsh24:
Awesome. Maybe this is why my Sirius bt radio has the issues it has syncing to the radio...
[Android Head-Units] supremekizzle:
You rock. Do you mean that in the newer versions of their firmware you can't connect your phone to the HU? Or what do you mean by Bonovo finding Bluetooth pairing too hard and not doing it?
[Android Head-Units] guap:
I was scared about an answer like this... Basically 'cause I have no time and if decide to start learning I'm going to spend a lot of time :D Can You link me an actual tutorial with a kitchen working on our rom?

absolutely amazing :good: