yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] donaldta:
If you press the "Step 2 button" you don't need to do cat command. Either one or the other both is unnecessary.

You would select the normal method. Btw, did you delete the /data/local/build.prop file or did you skip that too? And what was the exact syntax of the error?

It sounds like it is showing you the rear cam or aux input without an actual video device connected.

---------- Post added at 02:12 PM ---------- Previous post was at 01:59 PM ----------

Btw, the su binary ( /system/xbin/su ) is different from the SuperSU app. The SuperSU app manages the permissions for su access, while the su binary actually facilitates the change. Yes, the su binary is contained within the APK along with the java code for SuperSU app but they are two separate but interdependent mechanisms. You can grab the current su binary from the APK by unzipping it. It will be contained in \arm directory of the archive. You can manually update it by re-mounting the system file system read-write and overwriting the old binary with the new as root.
[Android Head-Units] pgarrity18:
Is there any way to make PowerAMP default to play once the app is opened. Small issue, but every time I open the app it starts off "paused" and having the fat sausage fingers that I do, it is difficult to hit that play button, and I often hit the "repeat" button by accident. It would be née if the app just started playing music right away.
[Android Head-Units] chris.r.r:
I can confirm that the media keys work when the back button is pressed within the radio app. But what I then get is another issue: When I'm listening to music in Poweramp and press the "Next" panel button, it switches correctly to the next song. Interestingly, after approximately 4 seconds there is quiet "Pop" on the speakers and music in Poweramp stops. It seems as the muted radio app in the background grabs back the audio from Poweramp. I hope you guys understand what I'm trying to say... ;)

I tried each of the three audio routing options in Audio settings ("3rd party app priority", "system app priority" as well as "intelligent routing"), but no difference - music in Poweramp constantly stops when I press one of the media panel buttons. I've never read about the routing options in this thread, can you guys confirm that it's available on the generic AN21-U unit?

I'm on .62 because my VW unit still refuses to install updates from this thread. Could it be that my issue is version-dependent?

same for me... who needs seeking to the next station, when there are stored stations/favorites? very annoying...

Good hint, I'll give that a try tomorrow.

BTW, I've already made some significant progress in modding the system apps to give them a modern, flat Jelly Bean look - so I can confirm that changing the skin of the apps is relatively easy possible. I'll post some pictures later this week.
[Android Head-Units] TOMMYX2:
after my Carunit is bootet i start my Radarapp and Poweramp automtic with the app called TASKER.

Automatic play when open Power Amp Tutorial:

1.Install application called Llama.:good:

https://play.google.com/store/apps/details?id=com.kebab.Llama

2.create a task:

- when active application is Poweramp -> Player=Play

3.and second task:

- when application Poweramp is closed or in background -> Player=Stop

Just try a different theme for Poweramp,there are some nice looking Themes with the play button in the middle
[Android Head-Units] goolac:
Ok this afternoon on my way to lunch i did the .70 update from .62 and everything seems fine...All of my apps are still loaded and working and the play store remained loaded and it works. The quad-pane is a cool but not customizable...No Problem I just swiped over to the previous screen and put my favorites and widgets there.
[Android Head-Units] jakejm79:
Simple enough with tasker, set a profile for when poweramp is loaded to trigger a tasker for media control pause/play toggle (you might want to issue a pause command first, sometimes the toggle wont work if the pause state is unknown).
[Android Head-Units] pgarrity18:
works like a charm thanks so much!!
[Android Head-Units] Lexsus1983:
I need to ask for .23?
[Android Head-Units] NickNoltePop:
2.6.70

He Guys!

Yesterday i updated from .68 to .70 and i recognized that the Radio doesnt save the channels if you turn the unit off.

And GPS doesnt work yet.

Does anyone have the same "Probs"?
[Android Head-Units] Drakey83:
Sorry if its been asked.

I made it to page 13 trying to find an answer to my question and the search tool is useless in this case so I decided to give up and just ask. Does this unit restrict you in anyway while you are driving or is everything available? The reason I ask is because my current JVC unit had some VERY stupid restrictions like not being able to access the navigation features on the fly or make a call via bluetooth unless I was in park. I was able to get around this by having it installed in such a way that my nav system always thought that my car was in park but my question is, is this necessary on this unit?
[Android Head-Units] KID52:
Sorry, I'm not sure I understand what you are asking for?

An extra $20 for the time it saves isn't bad though.

Unfortunately that does seem typical of a lot of sellers in China / Hong Kong. Not wanting to stereotype too much, as some sellers like Peter Chan provide excellent after-sales support, but from my own experience, the majority of sellers will maybe send you a couple messages very quickly, even a software or firmware update, then as soon as you tell them that hasn't worked, they ignore you. I've had this happen numerous times with various products and values.

Which rooting steps did you follow? The video and Wiki are outdated, I've been meaning to update both, however the written instructions on the main post are up to date and shouldn't cause any issues.

Interesting observations, my unit is out of the car so I'm not able to test all things that easily. I did have some speakers connected but I installed them in the car. Guess I need to find the originals and test hook them up.

Yes, with good reason as explained on the main post.

Post #345
[Android Head-Units] donaldta:
I hate to tell you this but that feature required by law in a lot of places which is why

every

head unit will have that feature. However in most cases, this feature can be bypassed by simply grounding a wire or not connecting it at all. In other case, you might need to use a special ASIC to spoof the signal or disable a setting in the software. Try looking up "JVC Parking Brake Detection".

To address your question, "yes", but it can be easily bypassed by not connecting the parking brake detection wire or disable the setting in software. Additionally, you could have saved yourself 13 pages of reading by watching the YouTube video @ 9:47 in the initial post of the first page. But, I guess you wouldn't know what's feature was used for.
[Android Head-Units] sciallo:
Eh, that didn't last too long... It's supposed to be available another 17 hours, but they already took it off the market... I was waiting to see if the manufacturer or my seller could provide a better deal... If anyone finds another let me know...
[Android Head-Units] goolac:
From what I know of the .68 debacle, you need to get your hands on .23, factory reset then update to .23 then you can go to .70. Although after a little more investigating, I would go from .23 to .62 then to .70 and that should be the cleanest path with all the apps working correctly.
[Android Head-Units] Mancubus99:
Well it appears that I've been struck by the GPS bug. The strange thing is that I'm on version 62, just upgraded from 60 where I had a perfectly working GPS. I don't know If the problem is directly related to the upgrade since I didn't test it immediately afterwards but I went to use the GPS this morning and it's not seeing any satellites. It's as though I don't have an antenna installed. Any suggestions? Can I get the downgrade file from 23 to use in case of a last resort?
[Android Head-Units] pgarrity18:
I have tablet talk installed on both my phone and the AN-21U but I cannot get them to connect via bluetooth. I follow the instructions but the AN-21U does not "see" the phone. Anyone else have this issue? I am on firmware .70 connecting to a verizon galaxy note II.

---------- Post added at 11:05 AM ---------- Previous post was at 11:00 AM ----------

After factory reset I do not have those folders. Is there any way you could upload all of those apk's? I think it would be very helpful to many of us who lost the default apps.
[Android Head-Units] sciallo:
The bluetooth on the unit is not visible by android, it's merely a "headphone" type connection for phome and music streaming. You do want to connect your phone to it if you want to use tablet talk to answer/initiate calls and be able to talk through the car sound system, but it does NOT handle tablet talk connection. You need to use wifi for that until we can find a suitable kernel source to try to compile BT dongle modules for an external bluetooth dongle. If you plan on using your phone as a wifi access point, the wifi connection in tablet talk's newer versions works over that connection too, there is a checkbox in the settings.
[Android Head-Units] pgarrity18:
So how would I set up the "headphone" type connection? I am confused. Does tablet talk work without a wifi hotspot? I only want to receive/initiate calls and hopefully get batter contact sync. I have no desire to text.
[Android Head-Units] donaldta:
Let me see if I can explain it a bit better. The Bluetooth Module in a AN-21U is connectected directly to a MCU board which handles a lot of low level events that Android does not. Amongst this is Bluetooth pairing for smartphones. Instead of being a direct connection into Android board, it runs sound channels as if it was a headset with a microphone to the Android OS. That is why you have to pair your phone using the phone app and not the normal settings app. This allows you to accept/make calls and listen to music on with the MCU and the phone but it prevents you from using Bluetooth with Android outside of that capacity.

There is only one other device that works as a bluetooth connection and that's the special Landu ODB2 adapter with B-Scan software. I believe the manufacturer has a special arrangement which allows them to communicate through proprietary connections though the MCU. However since this is a non-standard connection, no other third-party developer has been able to use it.
[Android Head-Units] pgarrity18:
So tablet talk does not work at all unless connected via wifi/mobile hotspot? Is that correct?
[Android Head-Units] donaldta:
Yep.
[Android Head-Units] TOMMYX2:
I have since yesterday, the problem that I no longer hear the sound at power amp, tune in and all other 3th party apps:(.

I must first start a original Systemapp Music or Video so I can hear the sound of Poweramp.

The original Music or Video app must be run with a break in the background so that I can hear again my Music with Poweramp.

if i leave the original Music app with the back button,I hear no more sound in poweramp:confused:

I've also changed the priority in the sound settings, but without success

need help i dont want to make a System 'Restore,thx:angel:
[Android Head-Units] sciallo:
Wiki pages

Dedicated AN-21 U Wiki page Was born... Subpages coming still needs more, but it's a good step forward.
[Android Head-Units] donaldta:
That is how it works according to video.
[Android Head-Units] AMRivkin:
"how does the sound behave when you use it not set as default navi app?" - no sound. I don't know why.

"Specifically, if you have another android music player playing music, what happens when the navigation gives you directions?" - mixed. After I launched the app (and it failed to start) music music became quieter and if I will open app again (from all application) it will work well. All sounds will interfere with radio.
[Android Head-Units] sciallo:
I found that having the disk app as the last "native" app opened (without a disk in the drive) was doing the trick perfectly for me. It would boot to desktop and keep the audio working as it's supposed to.
[Android Head-Units] AMRivkin:
No effect at all.

Here is my log. Hope ypu can tell me how to fix this.

Also I found that I can install apps on build-in sdcard. How to install on my new sdcard? Device mounted it as extsd folder. (it is also in /mnt/usb/mmcblk1p1).

And I wanted to try updating to .70. How can I make a full backup of my system?

Regards,

Andrey
[Android Head-Units] sciallo:
Seems like that app tries to take over the audio in android. When you launch it with the Navi button (or if it's associated as the navigation app) it's audio is routed through it's own input channel of the MCU. When you tried this, did you disassociate the app as navigation (ar associated some other app as the navigation app). Radio, BT, Disk and other "native apps" like those are handled by the MCU so your navigation app will have no control over their sound, but it should over other android apps.
[Android Head-Units] AMRivkin:
YandexNavi works in both cases.

1) It is not assigned as navi. Launch from apps. Works well, but no sound.

2) It is assigned as navi. Can't launch it from navi button. Can launch from apps. Works great. Sounds are mixed.
[Android Head-Units] sciallo:
1 is kind of interesting... Do other android apps such as pandora or google music have sound in that case?

I guess you'll need to run it as point 2. Maybe you could ask the developer of the app if sound is handled a different way than other android apps, he might give you some insights
[Android Head-Units] TOMMYX2:
ok great thanks,i try your method ;)

but what I do not understand why poweramp else has always worked and now suddenly no longer

and why producers make their device worse if they do not want 3th party apps for media?

For what is priority option in the sound Settings Menue?
[Android Head-Units] djblaze852002:
ADW Launcher EX?

Has anyone had any luck setting ADW launcher as their default launcher? I cannot get the unit to recognize and keep the setting after rebooting it. I am currently using nova launcher because of this issue. Do I need to somehow disable the stock launcher?

Does anyone else have any recommendations for a launcher??
[Android Head-Units] fcortes626:
so it turns out they didnt mail me the "program update" they emailed it to me but there is nothing in my email so i have to wait for them to resend it. Im thinking its going to be the same .70 update the manufacturer sent me. As for Ben he doesnt answer my messages anymore and always appears offline to me. Same thing with Allison also from qqchat and they wont give me a direct contact for the engineers because they dont speak english.
[Android Head-Units] tdt038:
Maybe because now celebrate Chinese New Year until February 10, and nobody works.
[Android Head-Units] fcortes626:
According to google Chinese New Years is January 31. On Allisons status on qqchat it says holiday from Jan 25 - Feb 10. Its Jan 21 and i messaged them last week.
[Android Head-Units] donaldta:
You should be able to disable any package by using "pm disable {package.name}" as root with "adb shell" or a terminal app. But, you have to make sure there's an alternate launcher in place otherwise you'll end up with a bootloop and have to reload firmware to get out of it.
[Android Head-Units] djblaze852002:
I was hoping someone had tried it... I was unsure if disabling the stock launcher will force the system to automatically recognize and launch ADW (since it is already not recognizing that is has been set as default). I will try disabling and hope it doesnt boot loop on me tomorrow.

---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------

Has anyone tried this Xposed Module?

http://xdaforums.com/showthread.php?t=2414467

I would love to be able to store my Google Music on the external SD! However, I am still experiencing intermittent problems with the songs continuously playing. Sometimes it will never skip to the next track (music playback error), or other times it will take a long time and sometimes play a next track... I would like to get Google Music working flawlessly on this unit. Can anyone else comment on their overall experience with google music and continuous playback? I just want to know if I am alone in this conundrum.
[Android Head-Units] tdt038:
According to google this feature of android 4.1 related to licensing and fixed in 4.2. Some paid apps dont autostart after reboot. Try to install the launcher from standalone apk, not from Google Play.
[Android Head-Units] sciallo:
Same boat, I've been trying to ask him if he can get me a replacement board, I saw him online two nights in a row, the first night all I got was "I told engineer" (don't know what the engineer would have to do with cost of spare parts...) got ignored since... Kind of sucks to be $570 in the hole and nothing to show for... I'm thankful it was still on my desk and I still have the crappy stock radio in the car...
[Android Head-Units] fcortes626:
If that update doesnt work im going to tell them to either pay the sipping costs or ill escalate the claim and let ebay decide. I might even tell them i will give them a bad rating and that might make them pay for it.:mad:
[Android Head-Units] wjv144:
questions about my newly receive unit

Hi all,

a few days back I received my new unit and right from the start I feel very happy that I bought it.

My unit was shipped with 2.6.70 firmware, which includes the "color" app to change the LED colors. Seller also included Igo (installed) and Sygic (stored in internal memory)

Lucky for me, there was a 3.5mm jack to plug an external mic into!

Rooting was a breeze, using Wondekin's root app!

My questions:

- I only have the "music" widget. The others ("Radio", "Navi" and "Disc") are missing. Any suggestion how to obtain those?

- The unit has built in TV, but I don't know if it is analogue or digital. Would like to know, before I buy an antenna. How can I check this?

Thanks for pointng me in the right direction!
[Android Head-Units] pgarrity18:
I installed .68 complete and it killed my gps. Then I did a factory reset, upgraded to .70, still no gps. Then I tried a reset and .62 and still no gps. But let me clarify, sometimes when I reboot, and I go to the gps checker app it works, but not every time. Other times it works and then 20 minutes later no signal. I cannot figure out what triggers the drop in signal, but I do know it was working fine before I upgraded to .68.

Without gps this unit is useless to me. I am not sure what to do next. If I have to reset and reinstall everything again, I would like it to be my last time. The worst thing is that it appears to work, so I reinstall all my apps and customize it. Then next time I turn it on, no signal. Then repeat with a new firmware. Doesn't seem to be getting me anywhere.

Have we solved this problem yet? There is a lot posted about it, but I assume we have not.
[Android Head-Units] kschumake83:
You need to flash .23. The GPS comes back but never touch .68 again, that's what breaks it. .23 was buggy and ended up bricking a few units along wit MCU updates so all links have been removed so people don't randomly flash it. Send a pm to the original poster and he will get you a link to the file.
[Android Head-Units] donaldta:
Great news! I hope it works out.
[Android Head-Units] KID52:
That sounds like progress, thank you for your efforts :)

And also a thank you to [MENTION=531561]WonderEkin[/MENTION].
[Android Head-Units] KID52:
You need the app installed on both your phone and the "tablet" anyway, so that is definitely a possibility. Although I probably won't try it again for a while, it's not high on my priority list as I don't really use my phone when driving, and certainly shouldn't be sending texts :)

The main thing that annoys me about the default app is the completely useless way it displays contacts, it needs some sort of search function.
[Android Head-Units] sciallo:
Another example why root would be nice :) I had it installed on the ouku, market was fixed... You might have to sideload it but I'm afraid it will still check for license verification...

:fingers-crossed:
[Android Head-Units] JohnnyTightlips:
Awesome, hope this works. I have been following this thread and just waiting for some root. This device looks great but I can't get past how locked down it is. The potential is great so if this works I will likely be making a purchase.
[Android Head-Units] KID52:
That was one of my concerns, hence why I haven't really bothered to try it. I did have a look for a "try before you buy" version, but did not find much worth while.
[Android Head-Units] kmtk:
Been watching this thread closely for a while, thought I'd contribute.

Found another 4.0 head unit that the manufacturer informed me is rooted and has an unlocked bootloader.

in-dash[dot]net/buy_en/index.php?route=product/product&path=1&product_id=63

I'm still holding out on buying to see if someone can get this AN-21 U unit rooted. The major difference between it and the unit I linked is the AN-21 is powered by an A9.
[Android Head-Units] WonderEkin:
Here's the modded file

V1.0

https://drive.google.com/file/d/0BwKObTKUOwAqRFBtTVVwM0JOU0k/edit?usp=sharing

V1.1

https://drive.google.com/file/d/0BwKObTKUOwAqWkFZTDJUbUxLeU0/edit?usp=sharing

V1.2

https://drive.google.com/file/d/0BwKObTKUOwAqeE13b1NTdnFTd2c/edit?usp=sharing

V1.3

https://drive.google.com/file/d/0BwKObTKUOwAqOWN5cUdXZnNjejg/edit?usp=sharing

Two things will do in the apk

1) Enable the ADB

2) Append "ro.kernel.qemu=1" into /data/local.prop, so the adb instance should get root access
[Android Head-Units] KID52:
Just installed this, opened up, pressed the button, and error saying app has stopped :(

I don't know what version of the firmware the SettingsProvider.apk is from that you received, perhaps you could compare it to this one? This is from firmware version 2.6.60-2.

SettingsProvider.apk

framework-res.apk
[Android Head-Units] sciallo:
I wish they showed some screenshots of the interface... Kind of interesting, I wonder if it's a variant of the S150... (they're starting to get some 4.0 going on those...) see this thread ...or it's yet a whole different one...
[Android Head-Units] WonderEkin:
try this one, changed some code

https://drive.google.com/file/d/0BwKObTKUOwAqRFBtTVVwM0JOU0k/edit?usp=sharing
[Android Head-Units] KID52:
It worked! :)

USB debugging now enabled according to the menu option.

Haven't tested anything with it yet but it's looking very promising!

Thanks again.

Only one slight issue I'm having. Upon reboot the unit is SLOW, it's lagging really bad, as if it has a 100MHz CPU. Any ideas about that?
[Android Head-Units] WonderEkin:
ro.kernel.qemu=1 may slow the device, you should root you device in adb shell and retrieve the ro.kernel.qemu back to 0
[Android Head-Units] KID52:
Okay, thanks.

I'm assuming the best way to go about this is via WiFi as there is no USB connection to use.

Can't seem to be able to get adbd started on the device to be able to connect via WiFi though.
[Android Head-Units] WonderEkin:
Try this, add adb wifi

https://drive.google.com/file/d/0BwKObTKUOwAqYndhSlItV0dia2M/edit?usp=sharing
[Android Head-Units] KID52:
Am I right in thinking all I need to do is run this app, reboot, and then I can connect to adb via WiFi?

Think I am missing something here as I just can't get it to work.
[Android Head-Units] WonderEkin:
no, you will lost adb wifi after reboot, just click it when you need it.
[Android Head-Units] KID52:
Okay, tried again, but adb still says unable to connect. I know IP of the device is correct, and I can ping it fine. Assuming port is 5555?
[Android Head-Units] WonderEkin:
yes, port 5555

try again

https://drive.google.com/file/d/0BwKObTKUOwAqWkFZTDJUbUxLeU0/edit?usp=sharing
[Android Head-Units] KID52:
Still not able to connect :(

Is there anything I can do to help determine where the problem lies? I wouldn't really know where to begin to look though...
[Android Head-Units] :
Can you provide a link where you have bought your unit?

Can you upload some photos of the 3,5mm jack?