Eonon GA5151F - GPS Not Locking After Malaysk ROM Install - MTCB Android Head Units Q&A

@Malaysk Sorry to ping you on here mate but really need some help.
I flashed my Eonon GA5151F Mazda 3 android headunit with the Malaysk ROM and its all installed correctly.
The only issue I'm having now is the GPS isn't locking on. It can find sats in the sky (up to 12) then drops down to 1 for a few seconds then back up but never comes up that it has fixed / locked on.
Any suggestions I would be truly greatful!
Some specs just in case:
Screen res: 800X480
RK3188

I have the exact same problem with my kld unit - MCU 2.30
The Malaysk rom refuses to lock satellites
I then installed the latest stock KLD rom - and it also fails to lock them. I wonder is this related to the the latest we android core - rather than malaysk's specific rom?
Sent from my Nexus 10 using Tapatalk

Did yours lock on before you flashed the rom?
Mine worked fine and only changed the ROM so can only assume it's the ROM version perhaps.
Have you tried an older Rom version at all?

I had the same with my KGL - went back to the latest KGL rom and its been fine for about three months now.

It was locking fine before the update. I've gone back to the older factory firmware now and it's still not locking picked up loads of satellites but they all stay red
Sent from my Nexus 10 using Tapatalk
---------- Post added at 07:55 PM ---------- Previous post was at 07:23 PM ----------
Ok - went back to a much earlier stock rom now (22052015) and after 30 mins driving it finally locked. Hopefully it stays!

Update : no joy - today it's refusing to lock satellites again. Anyone have any idea why?
Sent from my Nexus 10 using Tapatalk

Ok well this is weird. I installed the APK that comes with the Malaysk ROM called "GPS Test" and my GPS is now locking on and working.

In frustration, I pulled out the unit - disconnected the GPS antenna - and reconnected. Everything now works. Go figure. Must have worked loose
Sent from my Nexus 10 using Tapatalk

Make sure to set the timezone correctly as well, I think this makes a difference.

Related

Compass,magnetometer doesn't work!

Hi all! I had my Nexus since New Year and I'm so pleased with it. The last 2 weeks have I just noticed that my compass doesn't work anymore. I have checked several calibration apps but nothing works(twisting it around it's axis etc) . I then tried "advanced tools" application. Here could I see that my phone got zero signals from the compass and the magnetometer! I have switched from stock to m5 just to see if it was software related but the problem is the same. It is like the sensors is out... So my question to you all: Is it any way (through root for example) that I can force reset the sensors or is maybe service next?
Skickat från min Galaxy Nexus via Tapatalk 2
Did you flash any custom ROMs at any point?
I got a fresh Sprint Nexus. Compass worked fine. Flashed some custom ROMs, and compass didn't work with any of them. Next step recommended by CM9 folks is to revert to full stock to see if it works again to troubleshoot, but I won't have time for a while to do this.
As noted elsewhere in other posts, compass just doesn't work. It's not just N/S being reversed, it just goes haywire with any tilting, etc. Calibrating doesn't work from Compass or GPS Status.
That's the thing. I was on stock when I noticed the problem, that was why I switched to M5. But the compass is totally still for me. It doesn't move at all. It's totally non functional..
Skickat från min Galaxy Nexus via Tapatalk 2
Try to calibrate the compass. I am on AOKP and compass is also not working proberly. After calibration it does. Here is how to do it (I'm not a native speaker, try to explain it):
Start an app which is activating and using the compass. Stand free and hold the Nexus parallel to the floor facing the screen to the ceiling. Draw an 8 several times with the phone keep this orientation. Then, hold the phone upright to the floor facing the screen to your face and draw an 8 serveral times, again.
Salem24 said:
Try to calibrate the compass. I am on AOKP and compass is also not working proberly. After calibration it does. Here is how to do it (I'm not a native speaker, try to explain it):
Start an app which is activating and using the compass. Stand free and hold the Nexus parallel to the floor facing the screen to the ceiling. Draw an 8 several times with the phone keep this orientation. Then, hold the phone upright to the floor facing the screen to your face and draw an 8 serveral times, again.
Click to expand...
Click to collapse
Did exactly that with Compass app and GPS Status. Neither works.
Anyone have any progress with fixing this?
This is posted in the Sprint Nexus CM9 thread, might provide some information. Same compass problems happened with other CM9-based ROMs I've tried in the past.
I popped into the [CM9] IRC channel a little while ago and talked about how the compass was broken. It was suggested that I do a complete flash back to stock and report back. Trying to document as best as I can:
1. Complete flash back to stock under "[ACS] Return to stock" thread in this forum, used the first big link for FC12 Stock .tar (md5: 638d9b052b45396be345727ec0eedd64), which curiously is linked to "http://www.shabbypenguin.com/ACS/devices/Samsung/Sprint/GNexus/Stock/FC12/code_i9250xxsph-l700fd01.tar" and not *fd12.tar, like the mirror links to.
2. First reboot, downloaded Catch.com's Compass, compass works.
3. Baseband version lists as L700.05 V.FD01 / L700.FD02. I had previously flashed "toroplus_full_radios-FD02" a while ago.
4. Used Galaxy Nexus ToolKit v6.1, did option 7 for "all in one," though bootloader was already unlocked. Powered off, powered on, compass still works.
5. Copied over backed up zips, etc, flashed "toroplus_full_radios-FD02," rebooted. Compass still works. For kicks, updated to latest Google Maps, and Compass still works, GPS locks, location is correct. Baseband version lists L700.05 V.FD02 / L700.FD02.
6. Wiped system/cache/Dalvik & did factory reset. Flashed latest CM9 nightly (20120509-NIGHTLY-toroplus), GApps (20120429-signed), rebooted. AAAAND compass is broken again, as before.
Hope this gives you guys some information for a fix.

Icecoldsandwich 8.4 and 8.5

I've been using 8.4 since release as it is so far the only version that has allowed my GPS to work for more than 2 minutes. 8.3 and now 8.5 both get a lock in seconds but then loose lock and search until I turn GPS off and on again or restart the app using GPS. I have fastfix installed and working but only 8.4 will work. My question is can anyone tell me a radio that works with 8.5 and the soon to be released 8.6? I'm also getting the 1-2 second silence on 8.4 when a call connects so really would like to update ASAP.
Many thanks to anyone who can help out,
James
rytterbomb said:
I've been using 8.4 since release as it is so far the only version that has allowed my GPS to work for more than 2 minutes. 8.3 and now 8.5 both get a lock in seconds but then loose lock and search until I turn GPS off and on again or restart the app using GPS. I have fastfix installed and working but only 8.4 will work. My question is can anyone tell me a radio that works with 8.5 and the soon to be released 8.6? I'm also getting the 1-2 second silence on 8.4 when a call connects so really would like to update ASAP.
Many thanks to anyone who can help out,
James
Click to expand...
Click to collapse
If your on at&t try the new radio that just came out (.11) I also tried radio (.19) which seemed pretty good to me. But radios are based on your region not on rom.
Reinaldo33897 said:
If your on at&t try the new radio that just came out (.11) I also tried radio (.19) which seemed pretty good to me. But radios are based on your region not on rom.
Click to expand...
Click to collapse
I'm over in the UK and on T-Mobile, I'm currently using 26.14.04.28_M Maybe just testing a few out is the way forward...
Thanks for your reply
Update:
Just installed 26.16.04.09 radio and reflashed 8.5, I get lock within 2 seconds and permanent loss (searching) after about 2 minutes. back to 8.4 I go...
I've now tried:
26.13.04.19_M
26.14.04.28_M
26.16.04.09
26.09.04.11_M2 (now current as signal + GPS seemed to be quicker and better than the other radios)
With all the above on 8.5 GPS would lock then slowly start drawing a larger and larger blue circle around my position in Google Navigation until searching appeared and stayed. It seems like the ROM is the issue to to me, some way it handle the data passed to it? In 8.4 the indication of lock (the circle with the dot in the center) appears to have lost the sat lock, but the software is able to continue giving a near perfect lock of it's global position. In 8.5 I notice the software gives up around the same time that the phone starts to indicate it has lost lock. Could that be the issue? 8.4 ignores the instruction that GPS is lost and 8.5 goes along with the data passed to it? Sounds odd but it seems that is what is going on...
Does anyone else get this? or do I just give up and get a new phone...

Volume wheel stops working

My volume wheel only works for the first 15 minutes or so then and then it stops working until I reboot the unit.
Any idea ? Software or hardware fix ?
A few have the same issues. Myself included. For me it was software related. Out of interest what navigation do you use.
Sent from my SM-G920F using Tapatalk
I agree, since a software reboot fixes it I'm guessing it a software. Did you find a fix ?
I'm using Waze
Waze was my culprit. Try an alternative as an experiment.
Sent from my SM-G920F using Tapatalk
Unfortunately, Waze is the reason why I bought the head unit. Although I'll try to see if that's the problem and if so ask Waze if they can fix it
Thanks
Some others have went back to an older version of Waze. The last one before the change in material design.
Some others with same problem have discounted Waze so it's a bit of a lottery.
Sent from my SM-G920F using Tapatalk
Just noticed I have the same problem as well (volume knob stops working after a few minutes, reboot fixes it for a bit, repeat). I don't know when it started as I've always just used the steering wheel controls for volume.
Kicker is that I don't use Waze nor have it installed.
Using latest (Apr 23 2016 RK3066 800x400, latest JY MCU) Malaysk ROM, basic JY headunit.
@gk66 - since you last wrote your post, have you had the problem occur again despite using the older version of Waze?
I don't use an older version. Ditched Waze completely. Use Google maps. Problem hasn't resurfaced yet.
Sent from my SM-G920F using Tapatalk
gk66 said:
I don't use an older version. Ditched Waze completely. Use Google maps. Problem hasn't resurfaced yet.
Click to expand...
Click to collapse
Ah, I should learn to read. Thanks for the info though!
I haven't done extensive testing but Waze seems to be the culprit in my case too.
Muting waze also works. I've set it to "alert only" and it's much better but still stops from time to time.
When Waze talks it lower or mute media volume, my guess is that Waze does it wrong or uses an old API, I've had problem even on my phone where media volume would stay low or stop altogether.
I'll make a bug report and hopefully they can fix it
Caddish said:
I haven't done extensive testing but Waze seems to be the culprit in my case too.
Muting waze also works. I've set it to "alert only" and it's much better but still stops from time to time.
When Waze talks it lower or mute media volume, my guess is that Waze does it wrong or uses an old API, I've had problem even on my phone where media volume would stay low or stop altogether.
I'll make a bug report and hopefully they can fix it
Click to expand...
Click to collapse
Thanks for that. Glad you've found the culprit.
Sent from my SM-G920F using Tapatalk
Waze is not the only cause, also this happens with pc radio with the latest malaysk firmware for rk3188
Nobody said it was the only culprit. Why not start a thread to identify all the culprits
Sent from my SM-G920F using Tapatalk
I'm having the same issue. Radio works fine until I launch waze, within ten minutes the knobs don't work anymore.
Since everybody is having sporadic issues, I'm actually testing out if the audio mixing you can set in Settings->GPS has anything to do with it. I always had it set to mixing, and I now put it to switch. Tomorrow I'll know more after a round trip to work.
No waze here, yet I have the same issue. Happens out of the blue, even when just running the original radio apk and no navigation at all. The SWC keeps working. Functionality returns after a reboot or a jump to the hardware settings. As the SWC always functions I don't mind TOO much but it a bit sloppy.
Tried changing the GPS settings today. Whatever I did, nothing helped, not even putting a random app that doesn't produce sound as my navigation app.
Which MCU do you all have? Mine is JY/Joyous...
Waze is not the culprit, it just happens more often when using it. Bluetooth calls (interrupting your current audio) often break it. Other apps switching audio break it too.
It is most likely some bug in the firmware related to switching the audio input.
There is no solution found yet.
---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------
SilverViper2k said:
Since everybody is having sporadic issues, I'm actually testing out if the audio mixing you can set in Settings->GPS has anything to do with it. I always had it set to mixing, and I now put it to switch. Tomorrow I'll know more after a round trip to work.
Click to expand...
Click to collapse
Mine is set to Mixing 5. I haven't tried to switch yet.
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
SilverViper2k said:
Which MCU do you all have? Mine is JY/Joyous...
Click to expand...
Click to collapse
KLD2, RK3188 SD. Came with KLD2 v2.77 firmware, now running v2.81. Both have the issue. I haven't tried flashing older firmware
I tried using tomtom as my main GPS application, same issue, so it's definitely not Waze specific. Friday I'll drive without using any GPS app and see if it still fails.
Next time as soon as I notice it failed, I'll check system log for any errors or exceptions, perhaps something stands out.
I do know that the turning of the knobs is logged in the log even after they failed and don't change volume. One of the xposed modules that shows the buttons pressed and such does not recognize turning of the knobs after they have failed...
SilverViper2k said:
I do know that the turning of the knobs is logged in the log even after they failed and don't change volume. One of the xposed modules that shows the buttons pressed and such does not recognize turning of the knobs after they have failed...
Click to expand...
Click to collapse
Hmmm. The system log still gets the volume knobs turning but not the app? That could mean the firmware is ok and the bug is somewhere in the Android audio?
shtirlitz111 said:
Hmmm. The system log still gets the volume knobs turning but not the app? That could mean the firmware is ok and the bug is somewhere in the Android audio?
Click to expand...
Click to collapse
Yeah that's why I started playing around the GPS settings...
Any idea which app/service is responsible for handling the volume knobs?

Fulmics ROM 6.1 Bluetooth issue

Hi,
I have installed Fulmics ROM 6.1 and I have issues on bluetooth (i remember that i had already this issue in stock rom 6.0):
when connected to radio car or BT headset or Heart Rate Wristband , the BT turns off randomly on phone and i have to turn it on again on phone...
The frequency of this issue is random: sometimes it doesn't turn off, sometimes after 5 min, 15 min, or more.
i have tried to reflash modem 21c and 21a, same issue...
If somebody have an idea...
Thanks (sorry for my english...)
LG G3 D855
Did you delete the system before flashing rom in twrp
Sent from my iPhone using Tapatalk
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
I used yhis rom for a long time and m still using the latest 6.1 there are no issues at all with anything
Sent from my iPhone using Tapatalk
acft83 said:
Hi,
I have installed Fulmics ROM 6.1 and I have issues on bluetooth (i remember that i had already this issue in stock rom 6.0):
when connected to radio car or BT headset or Heart Rate Wristband , the BT turns off randomly on phone and i have to turn it on again on phone...
The frequency of this issue is random: sometimes it doesn't turn off, sometimes after 5 min, 15 min, or more.
i have tried to reflash modem 21c and 21a, same issue...
If somebody have an idea...
Thanks (sorry for my english...)
LG G3 D855
Click to expand...
Click to collapse
I'm also having a problem with bluetooth on the 6.0 rom. And this is a feature that I always use to listen to music so I really would like to find a solution.

PX5 freeze

Hi,
I have a PX5 RK3368 car radio with MCU MCTE_HLA_V2.80b_2 (recently updated from MCTD_HLA_V2.47_1). When I use the pre-installed app for Bluetooth A2DP (bluetooth music), after a while the radio freezes completely, continuing to play music, but no longer responding to touch commands (the screen is completely freezed, even the information it shows). I have to reboot the radio to use it. I've noticed that sometimes it happens with Chrome, too. Is there a solution to the problem?
Thanks
maicol07 said:
Hi,
I have a PX5 RK3368 car radio with MCU MCTE_HLA_V2.80b_2 (recently updated from MCTD_HLA_V2.47_1). When I use the pre-installed app for Bluetooth A2DP (bluetooth music), after a while the radio freezes completely, continuing to play music, but no longer responding to touch commands (the screen is completely freezed, even the information it shows). I have to reboot the radio to use it. I've noticed that sometimes it happens with Chrome, too. Is there a solution to the problem?
Thanks
Click to expand...
Click to collapse
I have the same problem on my xtrons 10.1 using the play store or Google chrome seems to cause this for me. My MCU is GS version 3.40. I get random black screen boot up errors as well.
Sent from my SM-A705MN using Tapatalk
@bamaredwingsfan try to change the ROM to one custom (like Hal9k's one). This seems to have solved the issue
maicol07 said:
@bamaredwingsfan try to change the ROM to one custom (like Hal9k's one). This seems to have solved the issue
Click to expand...
Click to collapse
That's what I'm about to try later today. What specific brand radio do you have? Also when you installed the update did you do it from recovery, or just load up the update zip and plug in to the radio and do it that way
Sent from my SM-A705MN using Tapatalk
maicol07 said:
@bamaredwingsfan try to change the ROM to one custom (like Hal9k's one). This seems to have solved the issue
Click to expand...
Click to collapse
Well, I installed the update and it seems to have fixed all my problems. Only wished I'd installed it on day one
Sent from my SM-A705MN using Tapatalk

Categories

Resources