Related
Hi guys,
I think the subject says it all...
I have a Diamond which suffers from serious GPS lag (not fix!). This means that when I'm driving, my car is always up to 50m ahead of what TomTom or IGO tells me that I am...
I'm thinking about changing my device as nobody seems to know the cause of this...
So, I wonder if Rapheal has the same issue or not...
HastaSSSS
Here's what i tested for you on the way to work...
Using TomTom6 (6.032), driving at 30mph, using the tip if the blue arrow as my position (same as i always used on TytnII) i would say my car was no more than 5m behind were i should be. No issue going down the right road or turn.
Same situation as johnk1973. No 50 meters lag, but aprox. 5 meters.
Same problem here on Raphael, TT7 is 50 meters behind. Will test it tonight if it also occurs with TT6.
Same here with tt7 and igo8....
Now this is going to get complicated....
I had Diamond before and NEVER experienced GPS lag.
I tried almost every official and cooked ROM and had no problems with GPS.
Recently I switched to Raphael....
And guess what... GPS lag !
I used my Diamond and Raphael in identical conditions, with the same app (iGO 8).
I'll try to test it more.
I'll post if I find anything useful to you.
Cheers,
Sh*t...that means Raphael is a "no go" for me...
Unless we solve the problem...whatever it might be...
Please keep on posting your findings about this issue...I like very much Diamond and Diamond Pro....but I'm not willing to have a device without 100% functionality...
HastaSSSS
I have a Touch Pro with iGo8 installed. I realised this "50m lag" on my business trip this Monday but I thought it was due to the speed of the car (I was driving very fast for the most of the time). Now I see the problem might be a little more complicated.
On the other hand the 50m is not so bad - I never had a wrong turn, the acoustic signalization of iGo8 is very good. Nevertheless, I would be glad if this could be fixed...
And another thing - I'm not sure if you are aware of the charging problem while using GPS. My Touch Pro actually stopped charging because of overheating and was running only on the battery. So be aware of this fact too.
But this is a different issue, I'm sure there is a thread for this.
I dont have the problem with TT6.
I second this issue, both with TT7 and IGO8 (haven't tried it with another one yet)
Guys I had GPS lag on TT7 when I fist used it (Only tried it for 5min) it was awful. Mainly everytime I turned a corner whilst driving.
Then I did the following changes:
\start\settings\system\external GPS -> Set GPS Program port COM4; Hardware NONE; Access Manage GPS automatically.
Hit ok, wait 10 secs, switch off the device and then soft reset.
Now go to TT7 change the GPS prefences, to use bluetooth device and selected COM4.
No my GPS is perfect now, no problems at all. Have tried it with two different ROMs and no problems.
I have TT7 installed on the main memory and the maps on an Sandisk 8GB Class 4 SDHC card.
Radio ROM is 1.02.25.19 if that helps? and AGPS is turned on a up-to-date.
BTW it was exactly the same when using google maps.
Did you also try it by just setting tomtom gps to bluetooth? I'll give that a shot anyway before going into the register... tnx for the tip
Please keep in mind that you'll get an update of your past position only once per second. This means: The faster your velocity the more inexact the position will be, because the distance you'll pass in this second becomes longer and longer:
@30kmph: ~8m
@50kmph: ~14m
@80kmph: ~22m
@100kmph: ~27m
@130kmph: ~36m
Additionally there is the inaccuracy which comes with GPS: In good times you may have ~10m divergence on average. But with weaker signal (which one may have driving in a city) it will become even more. So keep in mind that GPS will tell you, where you've been one second ago (plus the divergence).
By the time I get my Diamond Pro, I'll collate this at the same time with my X500, which has a build in Sirf3 receiver.
I am having a slightly different issue with my TP using iGuidance 4. Although the unit aquires a signal faster than any other device I have used in the past, it seems to lag or freeze as I drive. It will not update the time, speed or position unless I press a button or something on the screen. There is another thread on XDA (I think in the Diamond or Kaiser sections) that claims to have solved this issue, but the fix doesn't work on my Touch Pro (in fact it completely freezes my iGuidance requiring a soft reset).
Hi,
I'm using Ndrive and TomTom 7.
on NDrive I don't have any problem, it's fast.
on TomTom is slow..
I thing the problem is on TomTom using this GPS of Raphael.
WizP said:
Guys I had GPS lag on TT7 when I fist used it (Only tried it for 5min) it was awful. Mainly everytime I turned a corner whilst driving.
Then I did the following changes:
\start\settings\system\external GPS -> Set GPS Program port COM4; Hardware NONE; Access Manage GPS automatically.
Hit ok, wait 10 secs, switch off the device and then soft reset.
Now go to TT7 change the GPS prefences, to use bluetooth device and selected COM4.
No my GPS is perfect now, no problems at all. Have tried it with two different ROMs and no problems.
I have TT7 installed on the main memory and the maps on an Sandisk 8GB Class 4 SDHC card.
Radio ROM is 1.02.25.19 if that helps? and AGPS is turned on a up-to-date.
BTW it was exactly the same when using google maps.
Click to expand...
Click to collapse
these settings are the settings that are preset. Hence nothing changed. the lag on the diamond is bad but this is awful.
WizP said:
Guys I had GPS lag on TT7 when I fist used it (Only tried it for 5min) it was awful. Mainly everytime I turned a corner whilst driving.
Then I did the following changes:
\start\settings\system\external GPS -> Set GPS Program port COM4; Hardware NONE; Access Manage GPS automatically.
Hit ok, wait 10 secs, switch off the device and then soft reset.
Now go to TT7 change the GPS prefences, to use bluetooth device and selected COM4.
No my GPS is perfect now, no problems at all. Have tried it with two different ROMs and no problems.
I have TT7 installed on the main memory and the maps on an Sandisk 8GB Class 4 SDHC card.
Radio ROM is 1.02.25.19 if that helps? and AGPS is turned on a up-to-date.
BTW it was exactly the same when using google maps.
Click to expand...
Click to collapse
these settings are the settings that are preset. Hence nothing changed. the lag on the diamond is bad but this is awful.
Using Igo8 very intensively with my TP, no lag at all. Compared it this morning with my VW passat stock nav system, and again, i notice no lag.
I have the settings in the posts above, and have very little lag. I am using QuickGPS instead of AGPS, but all else is the same. My main probklem is how long it takes to get a lock (much longer than on my old Kaiser), but since installing DCS's ROM and doing a hard reset immediately after that does seem to have improved - I often get a lock from cold within a minute now..
Rowan
I believe the reason that some people are getting horrible GPS lag while others get nothing has to do with the Radio ROM versions that came installed with the device. Most custom ROMS don't update the Radio ROM. It's 12am and I'm posting this from my TP, so I'll just tell you that the Radio thread is stickied in the Raphael ROM dev forum.
EDIT: http://forum.xda-developers.com/showthread.php?t=439566
A lot of people have problems with the TouchPro GPS especially for pedestrian use...
From stock the TP GPS is quite unsable in car especially with TomTom 7 and totally unusable for pedestrian use.
After 2 weeks of reading and testing tweaks, here are the results of my tests and the applied tweaks to enhance the GPS performance
A. With Advanced config 3.2 http://www.touchxperience.com/fr/ou...ads/9-advanced-configuration-tool-32-cab.html
1. disable A-GPS
2. disable GPS logging
3. logfile name must be empty
4. old logfile name must be empty
5. maximum size of logfile must be 0
6 delete the files : \windows\GPSLogFile.txt and \windows\GPSLogFileBack.txt
7. it seems that if TomTom is installed on a fast microSD decrease the lag(have to test to be sure)
With those changes car usage will be quite perfect
B. Then edit registry with TotalCommander http://ghisler.fileburst.com/ce/tcmdpocketarm.cab
Under: HKLM\SYSTEM\CurrentControlSet\GPS Intermediate Driver\
- Drivers\GpsOneDevice\PollInterval -> 100 (default is 1000)
- Drivers\InputBufferSize -> 512 (default is 4096)
- Drivers\OutputBufferSize -> 512 (default is 4096)
- Drivers\SleepOnNoData -> 100 (default is 1000)
- Multiplexer\MaxBufferSize -> 512 (by default not present, you have to create it)
Tests to be done with buffers at 256...seems to be a little better
Tests to be done with other PollInterval value...seems to "drain" battery
With those tweaks pedestrian usage will be much better but not perfect...I explain.
You have to walk for a least 250m in order to have a reposition with mouvement on the map (before that, speed is always 0km/h) and then if you continue to walk there is quite no lag...and the speed reflect reality
...BUT if you stops you have to walk again for a least 250m in order to have a reposition with mouvement on the map and then if you continue to walk there is quite no lag...
Very strange indeed...
I hope this will help people...please test and feedback.
PS : tests were done with
TomTom_Navigator_7.450.9028_R3_VGA_black_edition
GoogleMaps 2.2.0.16 -- http://www.google.be/gmm/GoogleMaps.CAB
GPSTuner 5.4 -- http://www.gpstuner.com/download/GPSTuner_v5.CAB
I noticed GPS problems yesterday with Route66. Havent have time to test GPS lot before, just checked that it can find satellites and really works with Route66.
First while driving, Route66 got fix to satellite pretty quickly, but drop it then after couple seconds. Then couple secods of lag, again found satellites, couple seconds ok, drops again. This keeps going over no matter what, moving or staying stopped.
I then did soft-reset, no help. Then tried Google Maps with GPS, that worked no prob. After using Google Maps I returned to Route66 and strangely satellite fix was ok...
This might be just random satellite fix problem, but strange enough
Taajuus said:
I noticed GPS problems yesterday with Route66. Havent have time to test GPS lot before, just checked that it can find satellites and really works with Route66.
First while driving, Route66 got fix to satellite pretty quickly, but drop it then after couple seconds. Then couple secods of lag, again found satellites, couple seconds ok, drops again. This keeps going over no matter what, moving or staying stopped.
I then did soft-reset, no help. Then tried Google Maps with GPS, that worked no prob. After using Google Maps I returned to Route66 and strangely satellite fix was ok...
This might be just random satellite fix problem, but strange enough
Click to expand...
Click to collapse
Many of us have/had that issue so I can confirm you Its a device issue, not a satellite situation. The registry tweaks minimize that problem but I hope HTC solves the problem in his next driver/radio rom/... and the users hasnt to tweak their devices (95% of the users probably will never read this forum and they dont know how to "tweak" their devices
Thanks for sharing. I 'll check it.
Thank you!
I applied all the patches, my TP still doesn't want to find the sattelites...
F.....g hell!!! I tried anything,and morning I've got a fix with 5 satellites in 20secs,so it looks nice(yesterday evening I did the tweaks). But after 4 hours it can see 1-2 satellites,sometimes 3,very rarely 4 under blue sky. So 2 hours of my travelling from city-to-city I didn't get a fix! Co do pici s tym je!!??(sorry for slovak lng,but I cannot speak it english,because so wrong words english language doesn't have). I bought an useless technology and HTC is rolling on the floor laughing,how the customer is stupid. F..k them all with their technologies. Another thing is wifi...no comment is better. I will maybe buy an crazy Eten with Sirf3 and HTC with their stupid Qualcomm can go to hell. For what are all the technologies here,when they are working <20% of time? I am so angry on HTC,so when my kind of device will appear,I will immediately sell the Raph.
Flippy_TK said:
I applied all the patches, my TP still doesn't want to find the sattelites...
Click to expand...
Click to collapse
Same here... Don't know what else to do...
I believe I will never be able to use the GPS...
Ain't that a shame
Cheers.
But I don't get it, it used to work the first days...
Flippy_TK said:
I applied all the patches, my TP still doesn't want to find the sattelites...
Click to expand...
Click to collapse
i can confirm
Kevlar-Source said:
Same here... Don't know what else to do...
I believe I will never be able to use the GPS...
Ain't that a shame
Cheers.
Click to expand...
Click to collapse
for such an expensive device it is...
For those how have still problems
1. Hard reset
2. Applied the tweaks
3. Download last QuickGPS
4. Install TomTom
5. Have a little more patience...
Gook luck.
omega01 said:
For those how have still problems
1. Hard reset
2. Applied the tweaks
3. Download last QuickGPS
4. Install TomTom
5. Have a little more patience...
Gook luck.
Click to expand...
Click to collapse
Did all that and the bloody phone is still not getting a fix on satellites...
I am confused in other way...
Why it does lock the satellites in 30seconds and it sees 8 sats.and few hours after it has problem with seeing 3 of them at the same place with same weather conditions? I believe,that tomorrow(when I will not needed to have the fix,anyway I will try it) will fix the satellites ASAP. Do the Raphael have a status-sensor,that knows,if I need it right now or not? That's my opinion,while it doesn't work,when I need it and works when I testing it...
I will s..t on whole GPS technology and I will trust the plain maps as before(unfortunately,that costs me some money/energy that I spend for that).
Totally amazing
This is just amazing. Thank you!
Now I get a fix in 10-15 seconds. Earlier it took several minutes... totally amazing...
omega01 said:
For those how have still problems
1. Hard reset
2. Applied the tweaks
3. Download last QuickGPS
4. Install TomTom
5. Have a little more patience...
Gook luck.
Click to expand...
Click to collapse
tried this also and been driving around for almost an hour without results is that enough patience?
hmm, my gps was working normally, applied these patches and nothing changed..still working normally (no lags etc.)
Applied all the patches except one (I kept A-GPS on), and after testing with iGo it's working like a charm. With the latest QuickGPS data downloaded, it can still take - seconds to get a fix, but the positioning is accurate (no more 100-200m lag), the devices sees 4-6 satellites in the Belgian sky, and the navigation is finally usable on the Touch Pro. I'll make regular checks in the coming days and I'll report the results. Thanks for the tweaks!
With A-GPS enabled the GPS works great. I had it in my pocket with GPS tuner running while running in a forrest and he didn't lose my position and no lag. The problem: with A-GPS enabled TT7 loses the fix every second. Like 1 sec there is a fix, next there is not. And it keeps doing that. When I disable A-GPS it takes way longer to get a fix with TT7 but it holds the fix.
Tip: driving around makes it harder for the gps to get a fix.
gps problem
hi, i recently bought htc touch pro & i am facing problem to download gps on my phone could someone help me regarding this matter step by step.
thankx
Can somebody tell me how do i get this install in my htc hd2 plz, step by step guide..
CrazyM0f0 said:
Can somebody tell me how do i get this install in my htc hd2 plz, step by step guide..
Click to expand...
Click to collapse
Do a search - it's all here already, you just have to look
thank you
very very beatiful
iGO primo™ v1.2 (9.2.1.178658) (Feb 9 2011) HTC HD2 version
very very beautiful
Reboot issues
Has anyone been able to sort out the reboot issues?
I have it working in landscape now problems. Except when it is in the actual navigation mode, it reboots the phone.
If there is no nav, just the map, no problem.
Thanks for your help guys.
Reboot issue with iGo on HD2
I had the irritating problem of freezing when starting ANY navigation software. And to be more exact, when the software achieves a satellite fix!!
I noticed that the lower part of the phone warms up everytime, and it helped to extend the duration of navigation software by putting it against the air condition of the car. But this was not enough, because iGo worked only for 5 minutes at best, after which I had to pull the battery and WAIT for a couple of minutes before inserting it again and restart the phone.
It's really hot in Egypt at this time of the year. So, this meant that the HD2 is permanently and completely crippled when it comes to GPS software.
So, I moved to SD android, which had the same problem. The phone also froze when it connected to to GPRS on Android after some time (about 5 minutes without cooling).
The next logic step was flashing a NAND android, hoping that the probelm was in WM6.5.3 itself. Surprisingly, the Android NAND had the same problem!!!
I finally discovered the ultimate solution; UNDER-CLOCK your CPU! since then I could use CoPilot on android for as long as I want.
Now, I'm moving back to WM and going to under-clock the CPU to see if this will work.
please let me know if this helps you..
BTW, I noticed that this restart issues with GPS software was somewhat common with HD2 esp in hot weather, but I think this is the first time somebody (that'll be me!!) comes out with a solution. So, I'm really looking to replicate it and test it.
tmfarid said:
It's really hot in Egypt at this time of the year. So, this meant that the HD2 is permanently and completely crippled when it comes to GPS software.
Click to expand...
Click to collapse
I used hd2 (wm 6.5.5)+TomTom last summer in Sardinia (not as hot as Egypt .. but driving hours under the sun in a car with black leather interior is quiet the same ) and never had any lags or device over heating.
maybe iGo for WM is buggy
I have never had those issues.
I have been using TomTom for over 12 months, I switched to iGo and it was perfect. I then run iGo Primo and it also works with maps on only.
When I use the voice navigation, thats when it reboots. This tells me it's not an overheating issue, but a config or voices problem.
Other people using it in Italy don't have the problem. I assume I need to find other English voice files.
igo8 without bug on winmo
hi,
personally i am using this version ( Nav N Go iGo8 Revision 3
V 8.3.4.102680 - August 13 2009 )
you can download it from
david2131.com
or from google torrents search
the size is about 44mb without maps
i use it for one year and it has no bug for me and its not slow.
N.B : format your sd card (1 or 2 gb) and install IGO8 on it before installing anything, its very important to do this step for a 100% success.
you don't have to install nothing, it's just copy paste, and works like charm.
tmfarid said:
I had the irritating problem of freezing when starting ANY navigation software. And to be more exact, when the software achieves a satellite fix!!
I noticed that the lower part of the phone warms up everytime, and it helped to extend the duration of navigation software by putting it against the air condition of the car. But this was not enough, because iGo worked only for 5 minutes at best, after which I had to pull the battery and WAIT for a couple of minutes before inserting it again and restart the phone.
It's really hot in Egypt at this time of the year. So, this meant that the HD2 is permanently and completely crippled when it comes to GPS software.
So, I moved to SD android, which had the same problem. The phone also froze when it connected to to GPRS on Android after some time (about 5 minutes without cooling).
The next logic step was flashing a NAND android, hoping that the probelm was in WM6.5.3 itself. Surprisingly, the Android NAND had the same problem!!!
I finally discovered the ultimate solution; UNDER-CLOCK your CPU! since then I could use CoPilot on android for as long as I want.
Now, I'm moving back to WM and going to under-clock the CPU to see if this will work.
please let me know if this helps you..
BTW, I noticed that this restart issues with GPS software was somewhat common with HD2 esp in hot weather, but I think this is the first time somebody (that'll be me!!) comes out with a solution. So, I'm really looking to replicate it and test it.
Click to expand...
Click to collapse
I had a same problem and do the tricks same as you do.
At first time for about week or two under clock do the job, but after some time situation goes worse and worse. After problem with GPS, there were problems with WIFI and Youtube clips, after that situation came little bit worse because i didn't even make a call without restart or freeze.
And at all times lower part of phone goes warmer and warmer. I bring it to service and they told me that they know for that bug for HTC HD2 and it`s a usual problem. They changed mother board and now phone work like a charm without this problems and it`s a cold always.
Hi, I have an px5 xtrons and a problem with the clock on Android 8 (stock and malaysk rom) When I restart the car the unit have the old time of shutdown. (Unit connected to battery and no problem with android 6) Canbus is set on my model car and I have this problem, but if I set canbus model to none the clock works ok. I try to change canbus box but same issue. Anyone have a solution? Thanks
edit: even with the last malaysk android 6 rom same problem. Is it possible to solve putting downgrade version of clock app?
AlexRuhl said:
Hi, I have an px5 xtrons and a problem with the clock on Android 8 (stock and malaysk rom) When I restart the car the unit have the old time of shutdown. (Unit connected to battery and no problem with android 6) Canbus is set on my model car and I have this problem, but if I set canbus model to none the clock works ok. I try to change canbus box but same issue. Anyone have a solution? Thanks
edit: even with the last malaysk android 6 rom same problem. Is it possible to solve putting downgrade version of clock app?
Click to expand...
Click to collapse
I've had the same issue for probably the past year or so when I first started playing with custom roms. I'm pretty sure it happened after doing an MCU update. I have GS PX3 MTCD running hal9 rom. I've tried disabling network time etc but no difference.
When booting the headunit the time appears to be correct, then it changes to the wrong time, then after a few mins when either GPS or wifi has got a connection it corrects itself. I haven't tried changing the canbus model in factory settings as it's already correct.
I've found that the Clock app from Google works. All other including the stock clock keeps the shutoff time.
same problem here after upgrading Xtrons PX5 unit to Android 8.... it seems that somethings changed in CAN-Bus communication. Where bevore the car could write the correct time into the HU it's not possible anymore and the wrong (stucked) time get written into the Dashboard. The time will not synced when the HU is in standby (fastboot)... but will synced within 1 minute if i make a full boot.
dud89 said:
I've found that the Clock app from Google works. All other including the stock clock keeps the shutoff time.
Click to expand...
Click to collapse
hi, can you explain in more detail haw you managed to make clock work with google clock app?
i have installed it but no changes. the clock still shows old shutdown time
Hi I'm having the same issue with my xtrons head unit. Did anybody figure out a fix for this?
Hello,
I have the same problem. I have tried to add clock app to the whitelist, (mtce-utils) but It doesn't work. The canbuis I don't know is working correctly, Torque applicacion can not detect ODB unit and I can not view any value.
I set the clock to get the time from GPS only and I ve never had a problem.
typos1 said:
I set the clock to get the time from GPS only and I ve never had a problem.
Click to expand...
Click to collapse
Yes, but it only works if you have GPS connection (outdoor). If you are into garage there is no GPS udpate.
I have XTRON PX5 unit with Malaysk 8.0 and I have set the following things on whitelist:
com.android.settings
com.android.providers.settings
com.microtek.hctwidget
com.android.deskclock
com.cyanogenmod.lockclock
I have used mtce-utils ehitelist and Graser Daisata Xposed modules and none of them works.
I have connected the unit to the battery to avoid losing memory.
What can be the problem?
Thanks!
Same problem here :|
Android 6.0 clock also not working
As of 11/30/2018 after doing an MCU update 2.83 for Android 6.0, my clock also stopped syncing with the car's when turning it back on. It also display the last time right before the car was turned off.
Turning on/off GPS update or network update or setting the clock manually makes no difference and does not fix issue. Hope to see a solution to this.
If you revert back to the original MCU version, does the clock start working normally again? I'm assuming it would... I would just revert back to the original MCU version and be done with it. Unless, of course, there is some specific fix in the newer MCU that you needed?
greygoose82 said:
As of 11/30/2018 after doing an MCU update 2.83 for Android 6.0, my clock also stopped syncing with the car's when turning it back on. It also display the last time right before the car was turned off.
Turning on/off GPS update or network update or setting the clock manually makes no difference and does not fix issue. Hope to see a solution to this.
Click to expand...
Click to collapse
Did you export you MCU config before updating the MCU ?
I don't mind reverting back to the original MCU version I had but the problem I had with that one was my audio kept going back to sounding like mono instead of stereo each time I started the car. When I played video or music sound would only come out on my right door speakers. I kept having to do a factory reset each time to get it to come out at both sides.
I haven't browsed through the forum enough to see if anyone else experienced similar issues or if there were fixes for this.
greygoose82 said:
I don't mind reverting back to the original MCU version I had but the problem I had with that one was my audio kept going back to sounding like mono instead of stereo each time I started the car. When I played video or music sound would only come out on my right door speakers. I kept having to do a factory reset each time to get it to come out at both sides.
I haven't browsed through the forum enough to see if anyone else experienced similar issues or if there were fixes for this.
Click to expand...
Click to collapse
You could try the latest MCU, they may have sorted it out, you dont say what unit you have.
You could also try updating to Ore, it may also be fixed in the latest ROM.
Thanks I'll have to give it a try. My unit is the HA 2150 V600 with the px5 chip.
HI did anybody manage to sort the clock issue out on the headunits thanks
I have been having this same issue for a long time and hoping to find a fix for it.
I have tried the Google Clock app, that did not work.
I have updated my MCU from Ver 1.81 to 2.65 to 2.75 and now on 3.0.1. None of these MCU versions fix this issue.
I have also tried the V2.75_sp and no change (Did not think this would help with this issue, but tried it anyways)
On each of the MCU versions above, I have tired multiple roms (Stock, Malyask and Hal9K) and no luck fixing the problem.
The only time I have been able for this to work is if I have wifi enabled and connected to a Hotspot and Network time sync selected in the settings/Date&Time. With this configuration the time sync works everytime.
Now when the time does not Sync and if I open the GPS Plus app, the time displayed in the app is correct. So based on this, the only thing I can think of is that somehow the time from GPS is not being pushed to the clock app.
Guys I think I found the solution, at least it works in my case. What happens actually is that the unit is set to autosleep and not to shut it down. So when the unit goes to sleep, everything freezes including the clock time. When you put back the key contact, the unit goes back to live and all the apps start again from the moment when they went to sleep.
The solution which seems to work in my case, is to set the unit to shut down after I turn off the engine. Of course, it takes around a minute to turn on back when I put the contact key, but because the whole unit has been shut down, when it starts again it checks also the time clock and it syncs with either the GPS time or with the network provider time zone (depends what you have set). In my case I use the GPS time zone and with this workaround everything works well now.
It's not so much the MCU updates but the actual system update. Going backwards to the 20171214 system update will get the clock working fine again and should work with the most recent MCU update (my instance). With this version I didn't have to bother with changing the auto sleep or shutdown settings since it's an inconvenience to wait for a full minute for the unit to boot up. Also did not have to change GPS or network time sync either. I turn the key ON and the clock just works right away.
So I've recently "upgraded" my car from a Opel Zafira 2009 to a 2015 Volkswagen Golf 7 Variant(stationwagon).
In the VW there's an infotainment system, not a NAVI but still classified as MIB 1 I've figured out.
I've done a ton of searching and it seems to still be an issue with certain cars infotainment systems, I have no issues what so ever connecting my Lenovo tablet to the car and playing Spotify through that. But since there's no phone feature it's kind of not what I'm after.
I've contemplated just getting a used *insert random other brand here* and just use that until the issue is solved, but since I've done quite a bit of reading on this I see that this has been an issue since late Android 10 versions of Oxygen OS and still persists on 11...
Has anyone here found a workaround for this? Is the issue still ongoing if I use a custom rom and most important, is there a stock camera to flash on custom roms?
Needless to say, it's annoying as heck and yes I've actually done every bit of troubleshooting there is. I even reset the infotainment, removed power from it and put it back... The whole shabang so to say...
It's a bug with OnePlus and no matter what settings I use in "developer alternatives" it still keeps randomly disconnecting, sometimes after a few seconds and sometimes it's a minute and a half.
Things I've tried:
- Removed the pairing on both devices
- Removed fuses related to infotainment on car, waited 2 min and tried again
- Unplugged the infotainment from the glove compartment, waited 2 min and connected it again
- Deleted data/cache on the bluetooth app within android
- Tested another device(Lenovo tab) that worked fine.
- Hard reboot of the infotainment(10 sec power button hold)
- Rebooted the phone(obviously)
- Reset system settings on the infotainment
- Asked a VW dealer, they had no idea and wanted me to bring in the car
- Searched numerous VW forums for any updates(has to be done by a dealership I've figured and since it's working with another unit not relevant).
- Every bluetooth setting combination related to bluetooth in developer settings.
- Probably alot more, but it's been a few days now.
Note to self, the Lenovo tab is actually running android 8, so I might have to get a Android 11 device to test with as well.
This is the only community I trust when it comes to custom roms and that kind of stuff tbh, so if anyone has experienced anything similar or found a workaround, feel free to post...
Thanks in advance for any reply. If you experience this as well feel free to says so, maybe it can all be submitted to OnePlus(not that I think they would care) or something...
I've attached a video displaying the issue as well.