yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] p64imp:
Hey guys,

Do any of you have issues with the google play store consistently blocking you?

Seems nearly ever reboot i have to go back in, delete my google account, clear cache for the play store, and re-add my google account before i can download apps again. I keep getting a rpc:s-3 error.

Any way to prevent this from happening? I figured a way around it clearly, but i dont want to have to re-register my account every time i need to access the app store for updates or a new download.

Also, why is it that a good deal of apps say they arent compatible with my head unit? Clearly they support android 4.1, but some of them either dont show up on the play market (poweramp trial, subsonic, and google earth for 3 examples) and when i google them and get the direct link to find them on the play store they prohibit installation.

I've been able to get around that as well by searching out the apk installers directly, but i shouldnt have to do that!
[Android Head-Units] Fariborzkhan:
3G Modem

Hi everybody

I try many some 3G modem but non of them does not work with that I asked the Seller on ebay she said just WCDMA modem is compatible with this , I bought TP-Link MA-260 but still doesn't work with that :(

can you help me how can I solve this problem

regards

Fred
[Android Head-Units] donaldta:
This is because the fingerprint of the device is not blessed by Google. Therefore there's going to be a lot of filters and methods which will prevent you from finding or installing directly from Google Play without spoofing another device. The biggest hurdle is when a developer marks their app as copy protected in the APK's AndroidManifest.xml file. One way around it is to use Market Helper which will help you get past most filters when spoofing as another device. If you are still unable to find the device then use, AppBrain in tandem with Market Helper and you can find and install just about 99% of the apps from Google Play.

An alternative for non-paid apps is to just sideload it from another Android device.
[Android Head-Units] donaldta:
Excellent. I'm glad it all worked out as planned. You're welcome for any advice that I managed to contribute. Glad to help.

Technically, the double din unit falls within both the American and Internal standards. The double din standard specifies the body of the radio as it fits into the cavity behind the dash not the opening for the screen or controls. The "issue" with this unit is that the face plate requires a slightly larger opening than what the older original dash kits provide. In fact, if you check eBay some of the dash kits specify this issue.

So, it is a little misleading to say it is an oversized double din radio. The face plate just uses more of the width and height of the body of the radio to fit the larger display than the older radios. Otherwise, if it was an oversized double din unit then you would need to expand the opening to fit the body of the radio inside the console. As opposed to increasing the increasing the aperture of the frame that fits over it.
[Android Head-Units] booba5185:
Alight, so I have everything setup to where the home button opens Car Home Ultra as a Launcher, Poweramp launches on startup, and all that. I can't get Poweramp to play on startup, I've followed all directions on Llama and it doesn't work. I've installed it, gone to the events tab, added a new event that says when the current app is power amp send media play (android 3.0+) and nothing happens. I've tried send media pause (android 3.0+) before play, no change. I'm tried send media play\pause, no dice. What am I doing wrong?
[Android Head-Units] donaldta:
You're not doing anything wrong. The problem is that stock radio app has an OnKey receiver which is intercepting media keys and blocking other apps from acting on them even when it is not in focus. I think you maybe able to install Autorun Manager to disable the receiver that is intercepting it. Otherwise, you'll need to make sure the radio app is closed before launching any of the media related key events.
[Android Head-Units] booba5185:
I believe I got it to work with Tasker and the action box for it. Is there a way to fix the problem where Poweramp pauses itself? for example, a song is playing in Poweramp, I leave Poweramp (while song is still playing) and do something else, I go back to Poweramp (song still playing), when Poweramp comes back up, the song is paused automatically...any fix?

I installed Autorun Manager and Radio or Music is not running or even listed, What could be intercepting the media keys?
[Android Head-Units] donaldta:
Are you looking at the advance mode? or basic?
[Android Head-Units] booba5185:
Advanced, but will this help me keep Poweramp from pausing itself?
[Android Head-Units] donaldta:
I don't know. This is more for the radio's listeners. Did you enable "show system entries"? If I remember correctly, radio is a system app.
[Android Head-Units] jakejm79:
How do you have the task for playing poweramp setup, is it tied to an 'on boot' profile or an 'on poweramp launch' profile?
[Android Head-Units] donaldta:
Haha. Well, the latter would account for pausing PowerAmp whenever it is brought into focus if there wasn't any flow control. I guess that's why there is a Tasker Is Music Playing Plugin.
[Android Head-Units] booba5185:
New problem, I lost root (superuser needed an update) so I tried to root is again, and after I hit temp root and restarted, I can do nothing. Poweramp eventually starts up, but I can't do anything. I'm trying a system update off a microsd right now to see if maybe it'll do a factory reset. and let me back in.

Edit no luck, same result. Now what do I do?
[Android Head-Units] donaldta:
Remember the "ro.kernel.qemu=1" line in the /data/local.prop that temporarily provides escalated privileges will cause to system to run very sluggishly. Even to a point it will seem unresponsive, especially if there are a lot of apps loading at boot. So, you just have to be patient enough to have the ability to delete it or at least the line within the file.
[Android Head-Units] booba5185:
It finally began to respond, but most everything is black. Any message window that pops up is black, and most any program is black. I can get into setting and read everything normally, but when I goto perform a factory reset is asks me for a code which I know is 7980, but the keyboard app that comes up is blacked out so I can't see anything to type in the code. this is irritating, thanks you so much for the help BTW!

I figured it out, just followed the rooting instructions from step 1, lol.
[Android Head-Units] zzzody:
it's possible to upgrade into ... ?

Guys, tell me whether it's possible to upgrade in the latest firmware from here (2.6.70) in

vvvvvv.aliexpress.com/item/Capacitive-Touchscreen-Android-car-gps-dvd-player-for-Nissan-X-Trail-Qashqai-Paladin-Livina-Note-3G/750420954.html :confused:

FREESCALE I.MX535D Cortex A9 Dual Core 1GHz

Ram: DDR3 1G Ram

iNand Momery: 8G

Android 4.1
[Android Head-Units] donaldta:
Double check with CPU / RAM / DEVICE Identifier to see if it acutally has a Freescale I.MX535D because that is actually a Cortex-A8 single processor not a dual core A9. If you have the Mstar786 CPU which is a Cortex-A9 and your your screenshots are the same then you can use the 2.6.70 updates.
[Android Head-Units] zzzody:
Thanx.

I told to saller about the possibility of an error in the unit description, and he insists that exactly A9 dual processor, but the name of the chip not tested.

Is there any hope in the new firmware (heard about .72 version) that will work normal BT dongle and can possibility connect them with BT ELM327 ?
[Android Head-Units] donaldta:
Well, the processor is probably the easiest way to actually differentiate between certain models. So, until you get it or get a confirmation about the actual processor then we won't know for sure.

Well, there is only one ODB2 Bluetooth adapter, "Landu" that is compatible with the AN-21U varients. They'll have to perform physical changes to hardware to allow it which is why it has to be purchased at the same time. At this point it is unknown whether or not it will work with any other software, other than the one it comes with "B-Scan".

If you're looking for an ODB2 adapter, you're much better of getting an USB ODB2 adapter. It was much better reading throughput than a Bluetooth adapter. Usually around 2x the speed. USB ODB2 adapters are also powered by the USB Host, whereas the BT ODB2 are powered by the ODB bus. Often this can mean that the BT adapter to continue to draw power even while the unit is off. Where as the USB ODB2 adapter will shutdown along with the head unit.
[Android Head-Units] ThePapabear:
This might explain my Bluetooth issues that I've at both units I installed. If I remember right, my Bluetooth worked fine but no more since selecting an other mcu in the units settings, latest after updating to .62.

I will try to go back to .60_2 which was installed, when the unit was delivered and try the mcu's that are in there.

I will report the result.
[Android Head-Units] Mancubus99:
Hi there. I have the same problem where the home button defaults to the stock launcher. I'm curious, what did you do to resolve this?
[Android Head-Units] zzzody:
Than (u shown) BT ODB2 adapter is exclusive and pricey.

I can connect by a USB wire OBD2 comfortable (My ODB2 connector is in the glove compartment). ODB2 ELM USB plug'n'play with Android 4.1 (no requires additional Android software or drivers) ? Torque will immediately work ?

How about WiFi ODB2 ? Difficult in the network settings (Ad-Hoc, ESSID, ...) ?
[Android Head-Units] Niclas.s:
Thanks a lot!

Pressing the resore button did the trick. Now my unit works fine again.

Auto audio switch works and hopfully google play works again. I will try later today.

---------- Post added at 12:08 PM ---------- Previous post was at 12:00 PM ----------

As i wrote before. Orginal MCU for your unit is: MCU 4.2.6.1-7-10-6501 for 2.6.70

I have the same unit. The supplier has maild me the MCU. But i dont think i got everything from them. file size only 64.12k

I'm a noob at this but if someone like to have a look at the files i got, i share a dropbox link to files.

_https://www.dropbox.com/sh/9hjvim0gzfkinot/7PdrBh-RS8_
[Android Head-Units] pakidermo5000:
Great !!! Could please make a review when you get it ?

May I ask you which unit did you get ? I have been asked 350$ + 65$ shipping for Audi versions of the unit. 4% extra with Paypal.

Since it seems to be a different unit from AN-21 U, I suggest to start a new dedicated thread. I really do not know how to do it, could anyone do it please?

In the mean time I got more info that adds to the one above:

CPU: RK3066 1.6GHz Cortex A9 Dual-core

Storage memory: Samsung DDR3 1GB

Radio receptor: PHILIPS 6624

It includes DSP sound

Wifi adaptor of type IEEE802.11B/g/n compatible WLAN

I also got a video. The quality is, being generous, poor. But at least, it is a video. I will upload it tonight. It has been recorded upsidedown ... I will try to transform it somehow.
[Android Head-Units] blankers:
This is the same unit I am buying, but for the audi.

http://www.alibaba.com/product-detail/HuiFei-KGL-7683G-Car-Navigation-with_1653847511.html

As I said, I am paying $260 +$60 shipping. I am dealing with a guy named keylo Luo and he is very quick responding to emails.

I will review the unit once it arrives....
[Android Head-Units] p64imp:
just curious, what are the benefits to upgrading the unit to the latest firmware?
[Android Head-Units] PsychoMcSatan:
64k is the corect size for an MCU. So I tried that one and while the dials work correctly (with volume on US passenger side), I still couldn't get my bluetooth to work. As I think I posted before, my phone connects to "CAR" when the radio is booted up, but the bluetooth app doesn't seem to see that connection. I hadn't looked into the models selection yet. Perhaps changing something there will enable bluetooth?

I've already emailed my seller to see if they can offer suggestions.

Hmmm... I'm wondering if a system restore would clear out the old bluetooth settings. Has anyone here chosen that "Factory Reset" option successfully? What exactly are you left with once it's "restored"?
[Android Head-Units] donaldta:
Yes

It depends on the unit.
[Android Head-Units] p64imp:
hey guys,

i searched over 35 pages of this forum just trying to get the name of the app you all use to dump the system information from the HU with zero luck. If i remembered the name of the app i'd know how to search for it...

Anyone able to provide me the name of this app so i can download it and get the details of what my HU is running?

Thanks much!
[Android Head-Units] donaldta:
Android System Info and CPU / RAM / DEVICE Identifier are pretty much the two apps we used to verify the specifics.

]Next time try using "system info" in the search this thread tool on the right.
[Android Head-Units] zzzody:
Can u help me find an differents between this USB ODB2 adapter:

vvvvvv.aliexpress.com/item/Factory-Price-2014-New-100-Vgate-USB-ELM327-OBD2-OBDII-ELM-327-V1-5-Auto-Diagnostic/1637233664.html

and this one:

vvvvvvv.aliexpress.com/item/Wholesales-OBD-OBDII-scanner-ELM-327-car-diagnostic-interface-scan-tool-ELM327-USB-supports-all-OBD/1594345839.html

:confused:

Which one is more compatible and popular?
[Android Head-Units] donaldta:
Neither, both are craptacular clones. Post #635, Post 1262, Post #1667, Post #1923, etc...
[Android Head-Units] ThePapabear:
With this MCU the volume knob is mirrored and there is no color app (in the third try after using some other MCU´s there was an Color App, but BT is broken again...).

Tried to install FW 2.60.-2 brought back Bluetooth, but i lost it again after rooting the device. Using some other MCU´s it is coming back sometimes, but it went away, after trying to use the above mentioned MCU (the attempt which keept Color App).

I will now try .70 if it changes anything and go back to .60-2 if it does not work like all the other ones. A little confusing is, that .60-2 brings not one MCU that works correctly. One changes Volume and Channel knob, but they don´t work correct, the other two both knobs dont work.

Looking in Model Choose, there is none. Slowly getting really weird....
[Android Head-Units] Niclas.s:
Well i have added two pictures in my dropbox, notice my blutooth works (galaxy s3 conected). Have a look at my face plate. Do you have exactly the same face plate?

Radio freq wheel on left. Volume wheel to right.

A9 Mstar786 dual core. (there is a few units that looks the same but with Freescale MX535 dual core prossesor)

If you have, it probbably works with .70
[Android Head-Units] donaldta:
That is incorrect. There is no such thing as a Freescale M535 dual core processor. This processor is a single core Cortex-A8 processor according to Freescale's i.MX535 Multimedia Applications Processor page. You're probably referring to the inaccurate listings on eBay, AliBaba, AliExpress, etc where the reseller has erroneously reused the context for different units. The head units with the Freescale iM535 processors with the user interface that resembles the AN-21U is referenced in the Ouku Unbranded thread.
[Android Head-Units] p64imp:
Is it possible for the manufacturer to dupe the processor to appear like its an A9 cortex when its actually a freescale m535? I.E. the settings info showing M9 hardware built in.

I know i purchased a jump drive off ebay once where the seller listed it as a 64gb, but what showed up was a 16gb incorrectly partitioned to mount and show as a 64gb with a faulty partition, but once a bit above 16gb was written to the drive the file system table fell to pieces, causing full corruption to the drive (quite a dirty trick). That little scam cost me 6 months of paypal disputes and $16 in shipping fees back to tokyo.

I'd speculate that a shady manufacturer could also stoop to such dirty pool as a improper branding of a cpu to make it appear to be one thing in the system menu, and actually be another...
[Android Head-Units] PsychoMcSatan:
I'm thinking that I'll be trying a "Factory Reset" when I get home tonight. It seems that various apps from my previous FW are still around after moving to .70 so I'm wondering if bluetooth is perhaps confused by old code still accessing it.
[Android Head-Units] ThePapabear:
Yes, it is the same unit. Same Faceplate and the A9 dual core and it came with the same colored buttons on the menu, your picture shows (2.60-2) which are different to the 4 squares at .70.

I could kick myself in the ass, because i had 2 chances to safe the MCU`s, that came original with the unit and i missed both because i even didn´t think about it. So i can´t go back to where this started for me.

I tried so many things now, i could not even remember, what i tried exactly. In the moment, i´m at .70 with an .2101 MCU where the two knobs are not working, but everything else including Bluetooth is working fine. Color App works, as i reinstalled it from my safed one. It did not came with this MCU.

That´s not a big problem in my case, because i have the Steering Wheel Controls, but this is not a possible way for my friend, who has none of them.

If i remember right, at 2.60-2 Bluetooth worked too at the first time, but it messed up at a point i can´t remember clearly. I don´t know if i just rooted the unit again, or did an MCU update too. But i am shure, Bluetooth and Kobs worked, but Knobs where mirrored, so i tried another one, lost Bluetooth and could not bring it back. So i went to .70 and tried another 2 hours with any MCU of the ones, i have now on my SD-Card (í´m shure, i missed some. It´s late and too cold in the car...).

I tried a Factory Reset too, but after over half an hour with nothing going on i shut down the unit. After restarting it, all 3rd Party Software was gone but bluetooth did not work. Then i installed 2.60-2 and Bluetooth was working (Menue Buttons stayed the same, as in 2.62, but background an apps changed). Knobs where not working as expected so i tried an other MCU and rooted the unit again. After that (in combination, or simply after rooting i can´t remember) i tried a view MCU´s, got no luck and went to 2.70. But i think i will give 2.60-2 another chance, since Knobs where working at it, even mirrored is better than nothing.
[Android Head-Units] pakidermo5000:
New and dedicated thread for HuiFei unit Android 4.2.2

I finally managed to open a dedicated thread for the HuiFei unit.

I have added the basic specifications, and the video review of the unit.

You can find the thread here: http://xdaforums.com/showthread.php?p=50602899

and the video review here: https://vimeo.com/87512794
[Android Head-Units] donaldta:
Well, I wouldn't go as far to say it is impossible but it is very, highly improbable. Disguising a single core processor into appearing to work as a dual core processor would be a significant feat onto itself. It is not something that is as easily accomplished by using a disk editor to spoof the capacity of external media. Heck, I did that as a kid with 5.25" floppy disks.
[Android Head-Units] PsychoMcSatan:
Factory reset didn't seem to change much for me either. However, I was able to recreate the 2.60-2 Bluetooth revival. It seems that on first boot after upgrading to 2.60-2, I go into the bluetooth app and my phone is already there. Weird thing is that the setup page for the bluetooth has the old device name and old password. Everything works fine, but on next reboot I get the "Android is upgrading" or whatever and when I go into the bluetooth app, my phone is no longer listed. In the setup page, there's a new device name (CarKit something or other) and the password is different.

But my phone is still connecting with the old devicename and password! Unfortunately, the radio's bluetooth app doesn't see this connection.

The MCU that seems to be working for me (other than bluetooth) is 4.2.5-8-10-E501 which was given to me by Papabear. Where did you find that one? (thanks by the way).

When I have a chance tomorrow, I think I'll try installing 2.60-2 again, but on first boot when I still have control of bluetooth, I'll try resetting the devicename and password to overwrite that original one that is stuck in the background somewhere. Actually, perhaps those details are written into the MCU because I notice that my phone connects almost right away when booting up. So yeah, I'll see if I can rewrite that entry somehow.

---------- Post added at 08:56 PM ---------- Previous post was at 08:29 PM ----------

Actually after double-checking, this MCU ( 4.2.6.1-7-10-6501) causes my volume control to be backwards. I don't think bluetooth was working either. I have the same unit that is in your picture, though I can't see the dial labels. My volume is on the right side, under the BT button.
[Android Head-Units] Niclas.s:
Ok, strange if it doesen't work if you have the same unit. My volyme is on the right side, under the BT button.

I have never change the MCU or firmware. They are orginal from factory.

But when my unit act little wired, i pushed the reset button. After that it seams to work fine again. But still having some problem to download apps from Play.
[Android Head-Units] p64imp:
Hey guys,

just wanted to check back on this item to see if anyone else is experiencing this issue, and has a possible fix. It is REALLY annoying!!! :

Do any of you have issues with the google play store consistently blocking you?

Seems nearly ever reboot i have to go back in, delete my google account, clear cache for the play store, and re-add my google account before i can download apps again. I keep getting a rpc:s-3 error.

Any way to prevent this from happening? I figured a way around it clearly, but i dont want to have to re-register my account every time i need to access the app store for updates or a new download.
[Android Head-Units] veletron:
http://android.stackexchange.com/qu...ading-application-from-the-play-store-rpc-s-3 <-- worked for me

Also, Play Store wont let you get latest version of play services, but its poss to sideload latest (install on another device and use APK share). com.google.android.gms.apk is what you need to sideload IIRC. Its also poss to fudge the identity on the AN-21 via an app (search this thread, its there somewhere).

Another quick tip (prob also found on here somewhere!). If search in google play on the device wont show you the app that you know is there - then google its name on the device and open the url with the play store app, then you get to install it.

Since sideloading latest google play services I have not had any issues with stuff not showing, and the AN-21 started showing up on my PC too (something it had failed to do beforehand).

Nigel
[Android Head-Units] donaldta:
I am curious, does this symptom trigger by package updates? or even specific package updates? or does it also trigger from new app downloads?
[Android Head-Units] PsychoMcSatan:
Is there a way to dump the contents of the MCU? I didn't have a copy of the MCU that came installed on my unit.

In any case, I tried the 4.1.0-1-10-2101 MCU and that finally got my bluetooth working consistently, but no knob functionality at all. However, I went into the "Model choose" section and now saw six choices. Basically two each for 3 cars (vw, camry, and something else) and the only difference between each of those pairs was one listed "BC6" among other, identical things, and the other did not.

I chose one with "BC6" and the knobs started working, albeit backwards. I chose the vw one, but I'm guessing the car model only affects CANBUS stuff if you have one.

So long story short, my guess is that the "BC6" in a model description refers to dial functionality. Perhaps Button Control? But BC6 seems to be be backwards (turning clockwise decreases volume so not a huge deal) though I'm wondering if anyone is running a firmware that lists a model with BC5 or BC7 or something?

The one MCU that I have tested where the dials work correctly was 4.2.5-8-10-E501, however there were no models listed in the "Model choose" section, and unfortunately bluetooth doesn't work with that one.

Anyway, Papabear, this should get your friend's unit without SWC at least usable again.