Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Once exit back to the main screen, it won't relaunch #129

Closed
waynesi opened this issue Apr 21, 2018 · 20 comments · Fixed by #134
Closed

Once exit back to the main screen, it won't relaunch #129

waynesi opened this issue Apr 21, 2018 · 20 comments · Fixed by #134

Comments

@waynesi
Copy link

waynesi commented Apr 21, 2018 •
edited
Loading

Hi,

I'm using v1.08 installed via the All in One Tweak. The AA launches fine 100% when the car starts. However, if I quit the app to the main screen, I can no longer relaunch the AA from the Applications. I got the following errors shown on the screen. I don't know how to extra the log, so took some
img_1582
img_1583
img_1584

Please help. Thanks.

Also great appreciation to your wonderful work.
@Trevelopment
Copy link
Collaborator

Trevelopment commented Apr 22, 2018 •
edited
Loading

the only part of the log we need to see is the last lines all the way at the bottom... you didnt quite make it there

@waynesi
Copy link
Author

waynesi commented Apr 22, 2018

Hi,
Sorry, my bad! I've redone the photos. The pictures are attached in the order from bottom scrolling to the top.

The exact symptom was, the AA started fine to begin with. Then I used the Exit to Mazda Connect menu item or Home hardware button to quit to the home screen. After I relaunch the AA from the Applications menu, I got this copyright screen with blank log area and then the screen went black after 1 or 2 seconds. Although the screen stayed black, the Okay Google voice command was responding, but I couldn't use Open Google Maps voice command to force the screen to refresh. Press the Home hardware button again, I was given the copyright screen. Quite often the log area was blank. I had to tap on screen or quit to Home Screen and relaunch AA to get something there.

A few screens at the bottom of the log are shown below. For full log please download from https://www.dropbox.com/s/9gmxctoqc81vujb/MazdaAA.zip

img_1595
img_1596
img_1597
img_1598

@waynesi
Copy link
Author

waynesi commented Apr 22, 2018

I'm guessing the issue is probably because the memory allocation failure on the takeVideoFocus call.

For your information, the AA is the only major tweak I installed. I don't have StatusBarTweaks and Speedometer tweaks installed anymore. I never installed the VideoPlayer and CastScreenReceiver.

I DO have Swapfile tweak installed and the swapfile is stored on a cheap thumb drive.

@waynesi
Copy link
Author

waynesi commented Apr 22, 2018

Another thing is, sometimes I noticed in the log which said Something bad happened ...

img_1617

Not sure if it has anything to do with the issue.

@rolanie3
Copy link

rolanie3 commented Apr 23, 2018 via email

@waynesi
Copy link
Author

waynesi commented Apr 23, 2018

I believe it is because of the memory allocation failure. I have the built-in SATNAV (SD card). I took it out and boom everything started working smoothly. I could switch out and back in, and the music play was no more jerky. I uninstalled and reinstalled the swapfile and put back the SATNAV SD card, and everything seems still working. I will give it a road test tomorrow morning and report back.

@rolanie3 I did my tests before seeing your post, but still much appreciate your advice. I'm wondering, since everything is working now with the swapfile, did the swapfile previously fail because I removed the USB drive from time to time? I understand I'm not supposed to remove it when the system is running, but I was told to only insert the USB drive after the system boots to install the tweaks and I had to remove the USB drive after the installation but before the system reboots. I was hoping the system will still try to mount the swapfile every time after boot even if it failed to do so previously. Maybe I was wrong thinking in that way? Is there a safe procedure to install tweaks after installing the swapfile tweak? Use two USB drives?

@mishan
Copy link

mishan commented Apr 23, 2018 via email

@waynesi
Copy link
Author

waynesi commented Apr 23, 2018

@mishan I'm following the FAQ on the https://mazdatweaks.com/faq/ When do I need the to use the SwapFile Tweak? If you use a navigation SD card and/or use the Video Player app or Android Auto often, you want to be using the swapfile.

In my case, I have the SATNav SD card and I use AA a lot. Ideally I don't ever want to switch out of AA because it almost gives me everything a modem infotainment system should. But I do want to check my trip data, e.g. the coolant temperature and battery level and most importantly my trip MPG, and unfortunately the ODB2AA is no longer working. So I have to switch out to check Speedometer. Also I want to keep my SATNav SD card in the slot, just in case my Android run out of battery after long journey; we all know how weak those USB ports are when charging a phone!

Anyway, I couldn't wait for tomorrow, so just finished a drive around home. With the swapfile reinstalled, I managed to switch between AA, Speedometer and built-in SATNav constantly; 99% of time worked. I did get a "Can't find (or connect, can't remember) the headunit process" error once though and I had to reboot the infotainment system, but couldn't remember what I did to trigger this error. I think my issue was caused by the swapfile which was probably somehow broken, because uninstalling the reinstalling the swapfile was the only thing I did, other than removing the SATNav card and putting it back.

I will try again tomorrow on my longer journey to work and report back. Hopefully we can close this issue after!

@mishan
Copy link

mishan commented Apr 24, 2018 via email

@waynesi
Copy link
Author

waynesi commented Apr 24, 2018

Just finished my commute to work and constantly switching between AA, Speedometer and built-in SATNav was flawless. No reboot needed at all this time. So I reckon this issue can be closed.

The only issue remaining is the audio was very very jerky. I played music on Spotify. When the Spotify was on focus in AA, the audio was smooth. But as soon as I switched to Google Maps on AA, the audio became broken and unbearable, including the voice guide for navigation. I though it might be the interruption from the built-in SATNav, but even after I turned off all the warnings wherever I could, the audio was still broken. Not sure if it is the swapfile on a slow thumb drive.

BTW, I saw on the youtube video that after launching AA, one needs to press Fav + Music to focus the audio channel? I never needed to do so and saw no difference even after doing that. Do we need to do that?

@mishan Thanks I will give it a try.

@waynesi
Copy link
Author

waynesi commented Apr 24, 2018

As @mishan suggested, I uninstalled swapfile and gave it a try. I still could switch between all the apps as afore-described. I have to say I'm very surprised as I expected to see the old issue getting back; but no, still worked. Now I have no idea why I got the initial issue. Maybe the swapfile was in use but the file itself was corrupted?

Anyway, the audio stream was still broken badly. I can only guess maybe it's the process priority? When Spotify is on screen in AA the audio is fine; the audio from the built-in SATNav running at the background is always fine, but it can't explain why the voice guide from Google Maps or Waze is always broken even when those apps are shown in AA. I also noticed, when I stopped playing the music, the music audio still continued for quite a few seconds so long that I often wondered if I did press the pause button. Not sure if it's common to everyone. Anyway, at the end I had to decide to remove the factory SATNav card to fix the audio issue. I would love to know if any other factory SATNav owners have same problem or not.

Earlier I mentioned I also got the "Can't connect to the headunit process" error. I don't know if anyone has the same problem with their Mazda, but every time I start the engine, the screen turns black and then resumes displaying again as if the computer lost power for a couple of seconds. Occasionally I got this "Can't connect" error after this "reboot" if I had AA running before starting the engine. Anyone has the same problem?

@waynesi
Copy link
Author

waynesi commented Apr 24, 2018

Another thought on the jerky audio stream issue...Since all the video and audio data are streamed via the USB connection, then when the audio player is shown on screen, the screen is fairly static and thus the video data consumption is much smaller and thus the audio has bigger bandwidth, so good playback. The factory SATNav's audio never needs to go through the USB bandwidth, so always good playback. But when the Google Maps or Waze is in use, the screen is more dynamic and thus more video bandwidth and not much room for the audio stream for both the music and the voice guide. This theory seems can explain everything very well, and can also explain the question I raised in other issue for better resolution - maybe the built-in USB is just not fast enough? Maybe the WIFI connection is the cure? Still would love to know if anyone else has the same issue with audio though.

@Trevelopment
Copy link
Collaborator

Have you tried using a better USB cable? If you are using a crappy cable you will have a crappy connection.

@waynesi
Copy link
Author

waynesi commented Apr 25, 2018

Hi @Trevelopment Thanks for your advice. Although my cable is not a gold plated one, I won't call it crappy. It's the supplied one in the box. My previous comment on USB bandwidth was a guessing; after all the same cable works fine as long as the factory SATNav card is not inserted. I will try to source a better cable, but it may take time for me to report back.

@Trevelopment
Copy link
Collaborator

I just suggest that because just using a better cable is a very common solution to this issue and works for most but so is removing the SATNav card because that is definitely what is giving you memory errors. It is probably the reason that the headunit process crashes when you turn off the car too and why your audio starts to get jerky after a while. Remember that SD has slower I/O speed than USB and much, much slower than internal storage and just think of how much information that navigation software is processing at any given time from all the detailed info that is on the card.

@waynesi
Copy link
Author

waynesi commented Apr 26, 2018

Thanks a lot for your suggestion @Trevelopment . I shall find a good cable and give it a try. Thanks.

@waynesi
Copy link
Author

waynesi commented Apr 27, 2018

Borrowed a gold plated, but unfortunately didn't help at all. Same problem. And I noticed, as soon as the car is stationary, everything is good. So I reckon, maybe tracking the moving car with the factory SATNav along with decoding the AA video stream are too much to the infotainment computer hardware,

@melvin100
Copy link

@waynesi hello.. did you find any solution bro???

@waynesi
Copy link
Author

waynesi commented Jun 7, 2018

Hi @melvin100 for the initial issue, i.e. failing to relaunch after quit, I reflashed the AA and it worked since then. I'm no longer using the SwapFile BTW. The jerky audio stream issue was still there and I could only resolve the issue by removing the SATNav SD card. Oh, one more thing, as I mentioned in my earlier post, the system always seems lost power for a sec when the engine starts. If AA is started before that, there are good chances the process can't be found and only a reboot can help. So I always manually launch the AA after starting the engine.

@melvin100
Copy link

@waynesi i changed the USB cable. Now sometimes AA is coming and sometimes not.

@Trevelopment Trevelopment mentioned this issue Jan 14, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WiFi support, config file, & version info Trevelopment/headunit
5 participants
@mishan @waynesi @Trevelopment @rolanie3 @melvin100