yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kaween:
I can tell you with 100% certainty that signal strength is not the problem.

I live 2 km away from the FM transmitter station of the official Belgian Radio service. No way the signal isn't strong enough. On top of that, of all my android devices with a FM chip only the AN21 has issues with this, and only the AN21 has this specific issue of not showing the decoded string if it isn't long enough on many radio stations over here.

There are exceptions : one or two radio stations will show a shorter RadioText+ code, and those stations are far weaker and are regional radio stations. The signal from those stations is far weaker, yet they never fail. "Hit FM" for example.

Another proof is that a certain Belgian radio station had issues with RadioText+ for a while, and started sending out only a solid string "Q is good for you". The AN21 always showed that string. Some weeks later, the radio station got their Radiotext+ back in order and the static "Q is good for you" which SCROLLS on units that show this string in a correct manner. The AN21 can't do scrolling (no doubt because it decodes the RadioText+ buffer incorrectly), so it showed the string as a static message.

Some days ago, the radio station got their RadioText issue fixed, and the static message was replaced by ye-normal-artist+song string. Well, the AN21 simply refuses to show any of that info now, UNLESS the RadioText+ string again is so long that it forces the string to display again. My wife's WinCE-based unit decodes this info flawlessly while parked in a underground parking lot. The AN21 can't when it litterally sits under the FM transmitter tower. (no joke).

Based upon this behavior, there's no doubt in my mind the issue is not caused by signal strength (or lack of) nor by a problem with the 6624 itself, but pure in the software that has to decode and display the RadioText+ string.
[Android Head-Units] digitaldr:
I've had it with this unit. It seems to need constant tinkering to keep it functioning properly & is definitely not wife friendly! Anyway I've ordered a JVC headunit - couldn't afford afford a touchscreen one but at least it will be reliable. Probably my biggest gripe with the anu21 is the terrible fm reception. I've seen a number of references to a cold solder joint in the copper braid to the tuner being responsible for this. Is this easily identifiable and fixable as I'd like to sort it out before I sell it?
[Android Head-Units] kaween:
I've returned to the 2.8.8 version on all units, and that one has never given any issues regarding RDS name or problems regarding station names.

---------- Post added at 02:50 PM ---------- Previous post was at 02:47 PM ----------

On the AN21's I've seen from the inside, there's no copper braid. That issue is typical for Huifei units. I understand it's no help to you, but I must say the FM reception of my AN21 is very much the same as the factory installed unit. Unless your car uses a powered antenna with build-in amp and something went wrong there, the AN21 should not produce a worse FM reception than any normal unit would.
[Android Head-Units] digitaldr:
Thanks I guess I just got a bad unit :(
[Android Head-Units] chris.r.r:
Could you please share the 2.8.8 radio apk, I haven't found it on the Yandex repo. I would like to try the 2.8.8 apk on the 2.8.3 system.
[Android Head-Units] safkafin:
I've got a "bad" unit too. I've tried several MCU versions and I've found out that some of them has better quality on radio. Too bad is that I haven't found version which would have all working and good radio receiving quality.. I do not recommend upgrading MCU..
[Android Head-Units] kaween:
Can be found as attachment on post #6466 .

---------- Post added at 05:07 PM ---------- Previous post was at 05:01 PM ----------

... as I've been saying for .... a long time now.

Only do an mcu update if

A) you have a backup of your current version

B) seriously, be sure to have a backup

C) .... did I mention you need to have access to a backup of your current version. :)

.... and if you current version is posing serious problems. I've NOT experimented too much with different MCU's after I retreived a correct working one, but yes, difference in radio quality can indeed be caused by the mcu, though I would not expect a serious improvement over the stock version the unit came with (unless some Chinese seller really botched up of course).
[Android Head-Units] chammerbeck:
Yeah, I could use the app. My "saves" are only the system updates and nothing useful there to install.

THANKS! :)
[Android Head-Units] safkafin:
Yeah. I know.. Always have the backups. :silly:

Problem is that these **** boxes comes with MCU versions which has very bad radio quality already when they leave from factory. Significant improvement with some MCU updates but downsides like loosing volume knob functionality and other surprize features.. :mad:

I've given up and use only netradio like TuneIn.. That works well.
[Android Head-Units] Josh22222:
Thank you, Rocket player does the job.

How do I change the default music player, assuming that it can be done. When I start the car if I have been using rocket player, it plays music as well as the default player, bit strange having 2 songs playing at once.
[Android Head-Units] apersaud500:
Stuck at Android Boot Logo

Hi,

I updated to android-4.1-2.7.29 but get the unauthorized ui message so I tried reverting to a previous working os but now its stuck at android logo animation. Can someone please help? thanks. :confused:
[Android Head-Units] kaween:
The default music player is called "com.tw.music_41e.apk". In the past, I tried to rename RP to this name in the hope it would take over playback when choosing the default player button, but this failed. Maybe it does work with Poweramp, I'm not sure. You could always try. Maybe somebody else has experimented with this already and can chime in ?

As for preventing the "heck 2 media players at the same time", you could use Lama to kill off the standard music player (which Lama will simply call "music player") using Root persmissions, and launch Poweramp instead. I've tried this myself once, and I know this does work. At the same time, you can let Lama issue a "play" command to Poweramp as Poweramp has the oddity of not starting playback automatically at launch. Launching Poweramp from a previous condition WILL show the last track that Poweramp played previously to deactivation, but it will simply PAUSE the track instead of resume it. Lama can solve that for you.

BUT, before you dive into Lama, have you tried the "return button trick" ?

Basically, enter the radio app. Longpress the "back" button (not the physical button, I mean the odd return thing which is found on the down-right corner). Shut down the unit. Now try your music problem again. It should not start 2 players at the same time now.

---------- Post added at 12:26 AM ---------- Previous post was at 12:19 AM ----------

Hmm. Hard reset (reset pin hole for 3 seconds) with a sdcard with a previous working firmware on it maybe ?

If that doesn't fix it, maybe the "help at bootloop" will : "Place the update files on your MicroSD card (see "Firmware Updates" section). Then turn the unit on whilst holding down the volume knob and home button. This should start the update process." (quote from first page)
[Android Head-Units] apersaud500:
Hard reset did not work :( or installing from sd card via home and volume knob does not work.
[Android Head-Units] majB:
[MENTION=4736782]kaween[/MENTION] I graped the radio.apk from version 2.9.3_20150112.

I uploaded it here.

I made a screenshot of the radio. Some times I have two lines (in white) one above and one under. These RDS lines are static. It take time to appear when I change the station. It is also dependent of how powerful the signal is.

I hope the picture and the file will help!
[Android Head-Units] majB:
error
[Android Head-Units] kaween:
Thanks for this, gives me something to tinker with. But from your discription, it is probably the same base apk with a different skin.

I suspect the main problem is that most European stations are shifting towards RadioText+, which is the actually (in terms of type of signal and transmission system) identical to RadioText, but several bytes of the string have gotten a new function. The longer I observe the AN21's behavior, the more I'm convinced the issue is in the the incorrect interpretation of the RadioText+ syntax.

The layout looks very much like a variation of the original APK (presets on the left), but with a larger font type for the RadioText.

Question : where you able to compare the AN's behavior to another Android device (phone or something) with an FM chip on the same stations ?

And did you get your reverse cam problem sorted out ?

PS : LOL. I forgot you're running a high res screen. :) As a result, I got 65% or something of your radio app on my screen. :) But it was an interesting test : it also helped me do a little test to exclude "signal quality" as main culprit in my situation. I KNOW there's a radio program each week which will send out a static message during the broadcast. I parked my car outside and tuned into this radio station. Sure enough, I got the static message I expected. Then I went to my basement, fired up my spare/repaired AN21 which has only a piece of wire as antenna (it receives 3 or 4 stations that way instead of the 20+ stations I receive in my car, so no question the reception is bad). Well, both showed the same static line.

The proves this problem is NOT related to signal strength, but resides pure in the way the RadioText+ info is interpreted by the AN21's radio apk. Now I just need to find an seller who's willing to listen to this issue and can be pursuaded to solve this. If anyone knows a seller who could be pursuaded into looking into this, let me know. I'm sure we'd all benifit from it.
[Android Head-Units] majB:
Yes, sorry about that, I forgot to mention it in my post. I did compair it to my phone radio, the radio program as in the picture BNR has a text scrolling under the name of the station. Tuning the car radio and the phone radio to the same station at the same time. The car radio did not show the text. So you are right about it.

About the reverse cam. Connecting it to 12+ did not make any difference, the cam view will only show when I turn the ignition on and disappear when I start the engine.

I got frustrated and tried various combinations of wires until I toasted the cam :(

I have orderd a new one today, hopefully I can get it to work, :I

I forgot to mention also that the socket have another yellow RCA female (yellow color als as cam in) with label text D90- and chinese text which I couldnt translate. connecting the cam to it does nothing ?? Any ideas?
[Android Head-Units] kaween:
Euh, it's not a good idea to start "trying various combinations" blindly. Disaster may strike. :eek: And certainly not without something like a multimeter at hand : you wouldn't be the first one who fries his headunit doing stuff like that.

When you receive the new cam, just hook it up like "supposed to" and see if THAT at least still works (in other words, you have picture without engine running, you loose picture with engine on) so at least we know THAT part of the system still works. I still need to know if your unit shows a simple BLACK screen when reversing with engine on, or if it shows you a "no video signal" message while doing so : that may indicate what's going on. There might even be a problem with your harness : I've read something comparable to your issue once on this forum, and the solution there was to cut one of the wires of the harness, but no further details were given in that topic.

Be sure to contact Audiosources about this issue before continuing blind tests. I wouldn't be surprised at all if they'll say something like "oh but on car X you have to cut wire Y or bridge Wire Z". AND you could wave a little flag about the Radiotext issue too of course. :angel: That D90- cinch could be anything : from a front Cam/aux connection (which most AN21's designs do support .... and would be logical for a yellow female cinch) to a subwoofer or whatever. Not a good idea to just "hook it up and see what happens".
[Android Head-Units] hashman:
I had same problem as you... it turned out the problem was that I was pulling power to the reverse camera from my reverse lights.... that did not power it correctly

when the car is on and ignition off - the voltage is around 12v, when you turn ignition on; it boosts up to around 14v... thats normal for a car and the camera should work with that.

However, my camera did not like the power from the reverse light, so solution for me was to pull a wire direct from fuse box to a relay switch (2$ shipped on fleabay) and use the relay switch to turn the camera on when power comes to the reverse light.... the camera is now powered direct from fusebox.
[Android Head-Units] kaween:
Interesting input, yet strange.

For a good understanding : Ignition itself doesn't boost anything. What happens is once your engine is started and the alternator/charger circuit kicks in, the board voltage wll rise from the normal battery-level (approx 12.6 V for a load-free car battery in good condition) to +/- 13.8V in order to charge the cars' battery. So unless he pulled the power from the "wrong side of the bulb" (after the bulb instead of before) there's no way he should be suffering from a too-low voltage level when the engine runs. But that wouldn't account for the fact the cam works when his engine doesn't run. I wonder if he's not having an issue with a bad ground connection or similar, as ground problems can cause really spooky issues in car electronics.

Best thing he can do is indeed take a multimeter and meassure exactly what kind of voltage is put on the camera when it fails functionality, which could also help indentify a bad ground.
[Android Head-Units] majB:
It is interesting about the cam not liking the change of voltage. It is a pity that my cam is dead now and I can not test this theory.

I did test the voltages with the a multimeter before installing the cam, the 12+ and ground came from the reverse light directly, I did a very neat installation and with a good isolation. The reverse light keeps on when I start the engine (unlike your fathers Ford Kaween ;)). But I am a short-tempered (kort lontje) sometimes if things don’t work they way I like, so took my revenge from the cam.

When the car starts, the voltage kicks to more than 12 volt and stay higher than 12v, maybe the cam did not like it. I had a such suspicion, because everything was working until starting the engine. The other theory maybe is something to do with the canbus.

I have ordered a new cam and the testing will go on. (so, this hobby keeps you busy, isn't it)
[Android Head-Units] aroel1:
My case is different, no image shown when rear cam signal connected to "rear camera in" yellow female but it does display when conncted to "aux video in". Do you know why?

One more question, when I reverse the car, the rear cam video will show on the screen right away ,no need to turn on any so called rear cam app,right?
[Android Head-Units] kaween:
If you wanted to do that (controlling Reverse cam image over an app), you can't. The Reverse Cam port completly hardware-controlled, afaik android can't even access it.

But I'm having a hard time understanding your question.

First you write : "no image shown when rear cam signal connected to "rear camera in" yellow female "

Then you write : "when I reverse the car, the rear cam video will show on the screen right away"

Or do mean to say : you EXPECT it to work that way, but it doesn't ? You do know your car will need to detect the change of gears into reverse, which it does by looking at the status of your "reverse" cable which you probably will have to connect to your reverse light, OR if you know where, you can connect it to the reverse status line of your MCH (the controlbox in a car which is responsibe for status of lights, fans, directional lights ect ect).

So, when you put the car in reverse, what do you see ? Nothing ? Black Screen ? Black screen with a "no video" message ? Just the Android background ?
[Android Head-Units] aroel1:
Thanks Kaween for replying me so fast.

Actually I have wireless rear cam installed before , also I have a wirless receiver from my old car. Now I just simply connect wireless receiver to "rear camera" wire to expect to see the rear image right away once I reverse my car( wireless cam+wireless receiver worked very well like this way in my old car). However, It is not working with my new head unit. so I changed the connection to aux camera in, Now I can see the image after I turn on iAUX app ( without iAUX app, I can see nothing even though I reverse my car). I read previous post with similar issues like me, someone suggest to connect "reversing "wire to +12V, I did not try it yet. Anyone tried this?

One more question, is there any solution to make Torque Pro work with OBDII bluetooth adapter? my Torque always find my iPhone as pair. I knew this unit limit the connection to other device in order to make more money. I search this thread, but no clue.:(
[Android Head-Units] kharnm:
Hi all,

I've bought an Android untit with the 1024x600 display.

I've a major problem, I've just installed Chrome, Waze, Sygic (maps not installed) and Poweramp (music on microSD) and I can't update my apps "insufficient space" ... but I've 2 x 32Go microSD card and more than 4/5Go on the internal memory.

For infomartion it's a BMW E39 version.

Here is some pictures.

Thanks !
[Android Head-Units] aroel1:
Thanks a Lot, [MENTION=4736782]kaween[/MENTION]. Your reply clear all my confusion about this Unit. In order to make My rear cam work, I have to find reverse wire from dash. I can not image to get the reverse power from the end to my unit: totally mission impossible for me now.

for OBD, do you have any suggestion for good Bluetooth dongle for OBDII communication? I had bought OBDII BT adapter already it worked well with my Torque Pro on my Android Tablet. if there is one BT dongle working with my OBDII adapter, can I just simply insert to USB port and run one BT management app on my Unit?
[Android Head-Units] Vee63b:
I just had this same issue. What I did was this:

1: Use FX File Explorer copied all the files from the RO internal sdcard to my 32gb extsd.

2: In settings > General > Extra Settings (pw: 123456)

-Switch SD 1 and 2 = Close

-Switch sdcard = Open

Reboot

3: Verify internal and extsd swapped in File Explorer.

4: Use "Storage Partitions" from play store to find the mmcblk0p_ that belongs to the RO sdcard:

-Menu > Advanced > Internal storage

5: (You must be rooted) Using Android Terminal Emulator

i. Format the internal SD card with these 2 commands:

- su

- /system/bin/newfs_msdos -F 32 -O android /dev/block/mmcblk0p_

ii. Mount it. Go to storage in the menu and on the bottom of the list click, mount sdcard.

6: Swap internal and external SD cards back if you wish; undo step 2 and perform step 1 again.

Hope this helps anyone that has the same issue. Sorry if I confused anyone anywhere in this guide. I've been sitting in my car looking like a lunatic since 11pm trying to fix this issue; current time is 2:50am. PM me if you have questions, or just quote me in a post.
[Android Head-Units] Shadow128:
Hi there,

yesterday I got a "Ewaygps EW842P" which should be similar to the "AN-21 U" in this thread.

On first starting it looks quite good, only the fan is a little bit loud. But I think built-in-car it should be not so loud.

But the first (and presumable not the last) questions to that drive.

In my device I've MCU Version 4.3.5-13-10-2501;System version 2.7.35;DVD Version 2.13.14-1200xh

I've seen that there are newer firmware versions. In this thread (first post) there is System Version 2.7.29 and in the wiki System version 2.8.6.

And in the file repository also some MCU firmware files, but there are all older than mine version.

- Can I update that system without problems to 2.8.6? Or only to 2.7.29?

- Is the MCU firmware included in the system update?

- If I root that device now and update afterwards, is the root still alive? Or should I root that device after update?

Is it possible to install a CWM to backup my existing rom?

Thanks for your help,

Shadow128
[Android Head-Units] balaes:
My unit is similar with this :

http://www.jewellet.com/Android-Hyundai-Elantra1-DVD/Android-Hyundai-Elantra1-Navigation

only difference what i observe it is Android version :

i have Android 4.2 and this is 4.4

It is possible to upgrade our units winth Android 4.4 ?
[Android Head-Units] chris.r.r:
I have a similar issue in 2.8.3: When I start Sygic, my sdcard is sometimes remounted as R/O which prevents the app from startup.

I solved it that way that I run a script on Sygic startup to remount the sd as read/write (requires root):

mount -o remount,rw /mnt/sdcard

That works for me.
[Android Head-Units] kaween:
That unit has nothing to do with ours. It's a Rockchip design. So, no.

---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------

I'd suggest updating to 2.8.8 instead. I've been running for quite some time, and it's stable and nearly flawless.

On mine with 2.8.8 installed en Baidu root, the root is permanent and is not lost after reboot.

You do NOT have to change your mcu after installing a new system. ONLY change mcu when you encouter issues, otherwise : leave it alone. It will NOT be automatically upgraded when you upgrade the system and upgrading the mcu requires a sepparate user action, but many system updates do indeed come with an MCU update file. But as said : do not change MCU unless you encouter issues.

AFAIK, it is not possible to install CWM.

Quiter fans do exist. I've put a Scythe 12V 40x40mm in my unit, it is completly silent.
[Android Head-Units] Shadow128:
That sounds great, thanks for your help.

But.... :D

Where do I find that 2.8.8 firmware?

In the first post and the wiki I can only find till 2.8.6?!
[Android Head-Units] kaween:
Seek and Ye shall find. :silly:

But as I'm not that mean : https://yadi.sk/d/7gb5oWwvcZXDn
[Android Head-Units] TheSSJ:
I always have to laugh when reading some of your funny answers :D

The permroot is done by replacing the 2.8.8 with an older kernel version if I am not mistaken...the newer ones seem to disable root again, right?

Bummer that the update files are encrypted :( But to be honest I think it is a simple XOR encryption - not to sound racist, but the chinese people seem to be a bit minimalistic in this context (I really don't want to offend any chinese people with my statement).