yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] DragonFlye:
Me too, but....Any chance of a video running ZB's ROM? A picture says more than a thousand words. I'de like to see the differences between Stock, Tuatara's and ZB's ROM. Things like boottime, (full)immerse mode etc.

Using Tuatara's atm and things running smooth (thx Tuatara!), so I'm reluctant to try another.
[Android Head-Units] ElfinJNoty:
I've been using Tuatara's 1.4.3

As of last night, I am getting no sound output from any of the apps on the android box. Dunno what happened, but I've checked all settings everywhere(settings/sound, made sure volumes were all up, made sure screen presses sound was on, checked the MCU app, trust me.... All settings have been checked)

Only way I can get sound is to connect the Bluetooth app, and play through that(after enabling BT audio) from my phone

Guess I'm going to install this new build and give it a go. Since I recently installed the hu, I was worried I had messed something up with wiring, but all was working and IS working when using the hu as a BT receiver. Sound plays fine and V4A controls all the eq stuff.

If the box is plugged in in the house, audio routes to the TV(HDMI) fine.

But no apps(Pandora, Google Play, Spotify, both music apps that come with the ROM) will send out any sound. And no keypress sound either. I did hear a few notifications make noise, but then stopped again.

Granted, I do have xposed installed... And could have easily messed something up somewhere I guess. Oh well, not even going to backup anything. Just gunna start fresh :banghead:
[Android Head-Units] leonkernan:
Mine did that once or twice early on. Completely powering off the headunit (I actually disconnected mine from the car) caused it to come back and it hasn't had the same issue again yet...
[Android Head-Units] ElfinJNoty:
yeah i brought it in the house and connected to my tv and it was all working fine, but owuld not put out sound still in the car.

i actually used the android setting/backup&restore/factory reset

it left anything i modified in system/apps alone, so the "blacked out" apps i was using(black themed google play, google now app, and youtube) stayed themed and that was a plus

one less thing to go back and install

kinda sucks i lost the config i had, as it was running great and was starting to get to a point of making a backup in recovery. but not so far along that i cant fairly easily go back in and reinstall everything.

has anybody tried pairing a bluetooth headset to the android box, and using that for voice commands? i have an old motorolla bt earpiece ive got laying around, i just put it on the charger to give it a whirl. i know i was able to use it with my phone for voice input....

last thing(for now)..... my pc is not detecting the android box correctly anymore. and since the headunit is now installed in my car, i realized i was missing one thing since the first time i flashed a rom using rkbatchtool. I dont have a firewire connection going from the pc to the box anymore. i dont have a spare firewire cable.... so here is the question

is a firewire connection needed for the rkbatchtool to recognise the android box connected? i tried watching the video again a few times to see the process. but my icon for devices is pink and not turning green. i also notices that the android box is seen and installs the drivers for RockChipUSBdevice(which comes up twice) but there is still a device named CarPad-II-S which does not install any driver automatically as the other two did. i tried pointing the device to the path of the drivers in the rockchip folder, selected the appropiate driver, but it wont install. always shows as carpad-II-s. and remains undetected by batchtool

i'm going to try and use the reboot app to reboot into download mode, and give the newest test.rom a try
[Android Head-Units] leonkernan:
I've just been doing some looking thorough the Newsmy official forum and there is a mention of a V39 MCU that some people have had access to. Only change i've seen mentioned so far is the obvious one:

V39 <1> correction external box Android hosts video chip initialization error

Doesn't seem to have been released to everyone yet but if i find a download link i'll let everyone know.

Newsmy forum address:

http://www.newsmy-car.com/bbs/forum.php
[Android Head-Units] trusky77:
I explain what I do. Wear laptop to the car and light it. Usb cable to connect my laptop (only the end you connect the laptop). In the Box Android squeezed the little button and connect the Firewire cable (You have to turn on the green LED) Loose Button and very quickly connect the USB cable to the android box. With this as you would well connected to pc Android Rkbatch box to use. If you do not fast and as I say, possibly do not work, because to me it happened to me once. Sorry for my english ... (I use google translator)
[Android Head-Units] Zaphod-Beeblebrox:
Your MCU 'mode' has likely gotten stuck. This is not an issue with the android side of things. If you browse through the MCU handling code what you'll find is that the HU has several audio 'paths'. And the Android box is only one of them. The Radio, Aux, AVIN, and Bluetooth Audio paths are all controlled on the MCU and those streams never make it to the android box. The MCU mixes those streams, along with the android audio output before going to the speaker. The Android box only has the ability to turn these paths on/off, and set volumes.

My suggestion is to try and re-flash the MCU firmware. and do a full power/down reboot as mentioned above.

---------- Post added at 05:49 AM ---------- Previous post was at 05:46 AM ----------

Like most android devices ,there are at least two modes and drivers needed. if RKBatchtool is showing up Pink, then you've likely gotten the ADB driver working. When the device boots into 'normal' mode, RKBatchtool shows pink. You can hit the 'switch' button in RKBatchtool to reboot the device into bootloader mode, or you can even do it with ADB from the command line:

adb reboot bootloader

Once in bootloader mode, you'll need to make sure to install the proper drivers.
[Android Head-Units] trusky77:
When turned on and connected, if in pink, pressing the little button would switch to boot mode? If so is much easier than what I have explained above.
[Android Head-Units] bockywocky:
Did somebody try a 32GB HC I Class 10 SDCard on the androidbox?

Is this readable?
[Android Head-Units] nestortoledo:
I have this 2 mini sdcards i get for my gopro

http://www.amazon.es/gp/product/B00FQOXI3G?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s01

http://www.amazon.es/gp/product/B00AJS9EGY?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00

And both works fine on NU3001 (with correct microsd to sd adapter)
[Android Head-Units] Zaphod-Beeblebrox:
Pretty sure this is the one I currently have installed: http://www.amazon.com/gp/product/B00B7ID99I/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1

Seems to be working fine.
[Android Head-Units] [Bob]:
Subwoofer

What would be the best way to wire a subwoofer to this unit ? Low or high ? Someone said low works good with amplified subwoofer but also some people reported that the low lines are noisy.

Also, I don't know ( and didn't find ) where I should wire the + on the subwoofer. Does it go to the battery ?

I have a small under the seat Blaupunkt active subwoofer with integrated crossover.

Thanks ! :)
[Android Head-Units] bockywocky:
Thank you guys !

I am going to order one
[Android Head-Units] alaninsitges:
High is never the best way to go unless you're connecting to an unpowered speaker. The noise in the line outs won't be an issue with your sub because it filters out frequencies in the range that the noise occurs.
[Android Head-Units] alaninsitges:
OK having spent some more time with this ROM I gotta say you did a great job. It's fast and smooth and pretty much trouble free. If the navbar had a more Android-Auto-ey design I might be tempted to skip Auto Mate and just use this. The buttons are well thought-out and work great, though I think if I didn't have the physical volume buttons having to essentially push a button every time I want to push a button would be a huge PITA. I like the new volume position and size.

I did run into one problem: when running in immersive mode, GPM takes up the entire screen but the area where the nav bar used to be is covered up by a translucent rectangle and doesn't respond to touches.

Another bonus: the annoying audio stuttering that I (and others) have experienced with Tuatara's ROM have disappeared.
[Android Head-Units] alaninsitges:
At this point I really don't think it's anything anyone has done with these ROMs. In fact if others weren't having the same problem I would probably just say I'm crazy and try to find another solution. I have some free time tomorrow and I'm going to make a video of the problem and see if anyone else thinks of something I haven't.
[Android Head-Units] B-Hard:
Does anybody know which adapter i need for my Mazda 6 2008 with bose.

Here are pictures of my current connection.

Thanks!
[Android Head-Units] B-Hard:
But whats that for an adapter?

Its not relly described in the wiki :(

I really dont know if my car has canbus or not, also there is not much information on the internet except the SWC Adapter which i've found here:

https://www.ultramall.de/shop/artikel/UM8538.php
[Android Head-Units] Bokomaru:
TWRP

I've got TWRP working on here. Need to do some further testing and then I'll upload a recovery.img and submit the changes to the github repository
[Android Head-Units] NU5002S:
Jeff: That looks really good and clean. I'm glad the install is low to the ground so people behind you don't watch your screen :p

Anyone have word on MCU v39? Does the changes seem to fix the reboot issue when turning off the car (from MCU V37)?
[Android Head-Units] Bokomaru:
Until someone modifies the BonovoMCU app to send the timeout over to the MCU it will likely always just power down. I would have thought that they would have set the default value at what it was before instead of 0.
[Android Head-Units] NU5002S:
Why did the BonovoMCU app break its timeout value? I noticed that the Upgrade application changed to a newer interface, but I didn't know it was also the cause of the timeout breaking.

If that's the case, when do you expect the fix to be implemented ? Would it be on Tautara 1.5.5ish?
[Android Head-Units] Zaphod-Beeblebrox:
Built from source I presume? Looking forward to seeing the submission/changes.

One thing we need to test is if we can still do update via SDCard on the unit. I don't know if TWRP or CWM supports the flashing script used by the RKupdate process.

As far as source builds, we are still on MCU 1.0.9. The MCU updates are massive, and making it very difficult to port up. Without that source, we will be relying on Bonovo to fix their own code. I don't know if anyone has tested this with 1.1.5. I quickly abandoned 1.1.5 due to the 160dpi change.
[Android Head-Units] Bokomaru:
Yep from source. Just combining parts from random places would have been easier, but I prefer to do things the right way.

I've never looked into the sdcard update, I'll have to take a peek at what the original was doing. Any idea what the process is? From the wiki it sounds like something on the rom notices the update.img on the sdcard and asks to reboot into recovery and then the rkimage.cpp code does the update.

Will definitely take some modification to make that work. Presumably it would be a good thing to make it happen since not everyone will want to hook the android box up to update.
[Android Head-Units] ElfinJNoty:
After reading up on my car and looking at what it would take to get my camera wired up for always on with ignition, and having to get a reverse signal from the fuse box since my car doesn't have one wired towards the head unit..... Went to a local shop to have them install and wire the rear can and what not

---------- Post added at 05:26 PM ---------- Previous post was at 05:18 PM ----------

Car is a 2006 Mercury Mariner, basically a Ford Escape with a nicer trim. I also asked them to look at the three remaining wires from my car harness(which I cut) that weren't going to anything on the HU. I noticed I couldn't get the radio app to not fc anytime I tried to open the radio app. So I was worried I had missed something(all I did was plug in the radio antenna to the unit but not working)

Think it is going to cost me about $130, and they are gunna try to fix the radio as part of it. Of course I already have the rear gate disassembled and all the dash dissassemlbed as I arrived. Lol. I did most of the labor for em but probably messed some things up as well along the way.

I'm much better with android than I am with car stereos apparently lol.

But these guys have never seen a HU like this, and are pretty impressed with the digital EQ alone(viper4android of course)

Then I've got the android box all xposed out so certain apps go auto full screen, and whatever other ui tweaks I've done. They are asking me where they can order one for them to play with and perhaps do a bulk order and install some haha. I feel like news my owes me a sales commission if these guys do a bulk order of 30+ like they are suggesting lol
[Android Head-Units] Black6spdZ:
awesome! not that the update.img method is hard, but a good recovery makes it easier for even the inexperienced types to do backups and test new roms that they would ordinarily let the others do for them. The more people that buy this radio the better for all. The AN-21U unit is still going pretty strong despite its closed source. Maybe more of them will jump ship as I did.. I see the real potential in this unit.
[Android Head-Units] Zaphod-Beeblebrox:
Excellent. Even if we don't get the auto update working right, having a good recovery means we can distribute via flashable zip instead. It's a little more 'manual' than the other method, but still very doable without removing the box.

Did you test touch operations on TWRP through the headunit? I actually had TWRP building and booting on my AOKP runs, but I didn't have the FSTAB built properly, so it couldn't see the SDcard. However, I was only doing bench tests with mouse & keyboard connected, never tested with full touch.
[Android Head-Units] Bokomaru:
Yep, working on the HU in the house with the internal and external sd.

Though once I finally install the unit I might have to consider getting another unit just for testing/development.
[Android Head-Units] ElfinJNoty:
I am a big fan of twrp being built for the device and hope you will surely share once you have put it through appropriate testing. Twrp will let you mount a USB drive over otg, so could potentially store everything except media for hu use onto an external USB for safe keeping.
[Android Head-Units] Summer-Newsmy:
1.1.5 did not complete,please do not use it
[Android Head-Units] Bokomaru:
Summer,

Please consider making the android apps source available so we can merge and improve on it.
[Android Head-Units] ElfinJNoty:
Yes Summer,

Please allow us to work with you on app development by providing source code for MCU and Newsmy specific apps
[Android Head-Units] blacklistedcard:
Nice..
[Android Head-Units] slicky803:
Hello,

Anybody know if there will be an upgrade to Lollipop with this model? Hoping to use it in conjunction with my phone for Android Auto. Didn't see any discussion in the FAQ or anywhere else on this possibility. If not, I suppose I'll have to wait a few months until they start producing units that DO include the requisite upgrades. Thanks!
[Android Head-Units] Summer-Newsmy:
Hello everyone,

Where you found MCUV38? I just now know this version. One of our customer install NU3001,works fine,then update to MCU38,then the screen completely black,now have to return back to fix.

Please do not update MCU!!!

If your headunit has problems,please contact with summer first.

Best Regard

Summer
[Android Head-Units] Bokomaru:
I successfully updated via a zip file from my TWRP install tonight.

USB storage isn't showing up in TWRP so I still need to dig into that a bit more, but the USB isn't showing up in the normal AOSP build so it's probably a kernel thing and not necessarily anything related to the TWRP build. Though I did have to change a define to point to the right usb area.

Always a heart stopping moment when rebooting on something new when you aren't sure if you can recover from a complete brick.
[Android Head-Units] ElfinJNoty:
Good to know testing is showing good results. Keep cracking at the mount points... Please keep us updated

Thanks for your work
[Android Head-Units] nestortoledo:
Summer, most of the updates for system and mcu we use, ia posted by users or developers of newsmy on your forum. and shared via baidu.

Instead of this, i think will be better to get a site or a forum, where we can find oficial and finished roms and with corresponding changelogs.

Will be better for us and for newsmy to have all stored and organized on same site/page/forum
[Android Head-Units] ElfinJNoty:
So I'm on the tuatara 1.4.3 ROM and my radio app FC's every time I launch it. Have MCU 37 installed

All else is working fine, just the built in radio app not working at all

I know there is another version of the .apk that I thought I read had been modified? Can someone point me in the right direction for this? And weather or not I will possibly have better success with the alternative radio.apk versus the one packaged with tuatara's ROM?

And could there be something not wired correctly on my unit that is causing the alp to crask? I have just an old "ford" 2006 Mercury Mariner, and only radio antenna is plugged into the unit, nothing else is connected to the unit in regards to radio(so maybe I miss something?)

Thanks in advance
[Android Head-Units] nestortoledo:
Have you changed the dpi ON YOUR SYSTEM?
[Android Head-Units] Zaphod-Beeblebrox:
Glad to have you helping/working on this. But fear not, the RK3188 is about as brickproof as any other device out there. As long as you can get the unit into bootloader mode (and there is a small reset pin beside the DC power point that assures that you can always get into bootloader mode) then you can flash via RKbatchtool and recover.

I'm not saying the truly determined might not figure away to brick it, but it's pretty hard to do :)

Crashing radio would almost 100% not have anything to do with hardware. The app will run when not even connected to the MCU (So no Radio hardware to interface!). First guess would be nestortoledo's question. If you've changed to any DPI less than 213, you'll probably crash as Bonovo didn't provide proper resources for all DPI's (It's crashing on a Nullpointer error for a button resource that doesn't exist in the layout at that DPI).

My modded radio apk will have the same issue, as I didn't fix their resources in that version (I'm working on a complete UI overhaul, but not ready for distribution yet).

If you really want to run at a lower DPI, you could probably extract the radio from 1.1.5 and use it. Bonovo made the switch to 160dpi with that version, so the radio should work.
[Android Head-Units] ElfinJNoty:
I think I am using whatever tuatara has set as default.

I can use xposed/AppSettings module to define DPI.... If need be. What DPI is "stock" for stock radio.apk?
[Android Head-Units] Zaphod-Beeblebrox:
Summer, our users have found that if you plug in an external HDMI monitor along with the Headunit, you can still boot up and flash an older MCU to recover. Unit does not need to be sent back, although the logistics of plugging in an HDMI monitor with everything still installed in the vehicle might be tough.

---------- Post added at 06:12 AM ---------- Previous post was at 06:10 AM ----------

Stock for anything pre-1.1.5 is 240dpi.

If you've not changed it, then something else is the issue. Again, this is a software issue, not hardware. Try clearing data on the BonovoRadio.apk app. Other than that, you'll need to learn how to get a logcat and look at the errors when you launch the app. If you want, you can post the log to pastebin (do not post long text entries here - post them to pastebin and provide a link). Just be sure to review and scrub any personal info from the logs before you post.
[Android Head-Units] ElfinJNoty:
http://pastebin.com/HE1Lg6Zj
[Android Head-Units] Zaphod-Beeblebrox:
That doesn't have the stuff we are looking for. Clear the log. Start the radio, and then look again.

you'll be looking for things related to BonovoRadio.apk and/or com.example.radio.
[Android Head-Units] spoks:
BTW on my unit your modified radio apk do not stop when other media (poweramp) starts. Or I am missing something?
[Android Head-Units] Zaphod-Beeblebrox:
Actually, it does stop. There was a leftover notification that I didn't clear, so it still shows in your notification tray, but it has successfully stopped (you don't hear two streams, right?)

I've since fixed that, and the version that is in my test ROMs behaves a little better.
[Android Head-Units] NU5002S:
I am MCU V37 and I want to go to MCU v34 or so because of the error with black screen. Are you saying I am required to have an external HDMI monitor connected before the "Update Setting" application will actually see the MCU Update v34 (lesser version) file? I have update file in the right location, but the app doesn't currently see any updates in the car.

If that is the case, I don't have any HDMI monitors but I do have a TV in my house. I need to purchase the right power adapter for this Newsmy carpad unit. Can someone please link me the correct power adapter?

Side question: Besides the DPI screwing up the apps, what else is wrong with the DPI change? Is there a reason that Newsmy wanted to change the DPI in the first place?
[Android Head-Units] spoks:
I do hear two streams. I am on Tuataras rom.
[Android Head-Units] Zaphod-Beeblebrox:
160 DPI is the 'natural' setting for our displays based on Google's definitions. We discussed this in this thread before, and I was a proponent of moving to 160dpi as it would give more screen real estate, and detail to some apps.

By setting the DPI to 240, it basically tricks Android into making everything a little bigger (it's a contrary notion, but higher DPI makes things bigger on screen, lower DPI makes them smaller - it's a scaling attribute). Once I actually tried 160 dpi (via 1.1.5), I found most controls too small to be comfortable while driving. While we could adjust many of the system components to compensate, even controls within apps such as Waze, Google Play, etc were just not comfortable.
[Android Head-Units] Summer-Newsmy:
Please only use the MCU file from summer. Because we will check first them provide to you.
[Android Head-Units] Zaphod-Beeblebrox:
Then you either aren't using my Radio, or you didn't properly install it (which means you aren't actually using it :)).

Mine definitely stops playing when another source requests audio focus. I believe you mentioned PowerAmp, which I often use, and it behaves as intended.
[Android Head-Units] Summer-Newsmy:
Thanks for let us know this.

---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------

How about we update the news on WIKI? Because I found that I can change wiki.

---------- Post added at 09:21 PM ---------- Previous post was at 09:15 PM ----------

Still did not got nod. If I am boss, I will certainly agree with this.
[Android Head-Units] spoks:
Well .. there is no Help>About :D to see version number.

I installed it as update of stock one. No errors occurred. While getting Waze announcements, sound reduces. So, it is your apk. I tried specially PowerAmp because you mentioned it before :)

Will check it again later on road to home.
[Android Head-Units] Zaphod-Beeblebrox:
The proper way to install is this is to delete (or rename) the BonovoRadio.apk and copy mine into /system/app. You would then need to change the permissions to 644 (R/W, R, R). Installing as an update evidently doesn't work :)
[Android Head-Units] spoks:
Then why Waze anouncements lovers radio volume? On stock radio Waze does not affect the sound volume.

But OK, I will put it in "proper"way. :)