The one with quadcore and 1gb RAM
Mcu 2.91
Gesendet von meinem SM-G900F mit Tapatalk
Mcu 2.91
Gesendet von meinem SM-G900F mit Tapatalk
I suppose there are dozens or hundrets of different devices with these specifications (like a car with 4 wheels and 6 cylinders). Follow the link ro L5.1.1.Quadcore, then ...800x480 and that's it.The one with quadcore and 1gb RAM
Mcu 2.91
Ha ha, this warning is written for a long time. Some people mistakenly put the firmware MTCD - MTCB. The result was a brick.Is there any solution for the laggy lollipop? Sometimes it takes a very long time to open Waze and than another app. Sometimes it gives a blackscreen too. :/
What is that? On the carjoying site:
Android 5.1.1 Lollipop car Head Unit Audio stereo upgrade for Joying
Note: Please do NOT upgrade ROM from Malaysk on forum.xda-developers.com or other brand. Because it is a serious issue, it will broken head unit and dead(WIFI doesn't work, head unit die). If you updated you do NOT update your lollipop anymore and will lost warranty. See this video https://youtu.be/pGCROGRV1Mo , it is NOT really android 5.1.1 lollipop verion.
I guess some can not understand you have 3 or more threads dealing with units and software.Ha ha, this warning is written for a long time. Some people mistakenly put the firmware MTCD - MTCB. The result was a brick.Who understands android - restored the device. Others were sent back to the seller.
Do you have an OBD Bluetooth device enabled?I have the Eonon unit, which is an rk3188 - 800x480 - KLD6 head unit. This came with KitKat 4.4.4 and I recently upgraded to the Malaysk 5.1.1 ROM (update_5_1_1_FUSE_800X480_RK3188_02_MAL_02_07_2016_MTCB). Everything is great, with 2 exceptions, both happen on boot. When the unit first boots up, the splash screen (in my case, a Chevy logo) shows up like normal. After about 20 seconds, it goes to the launcher (home) screen for about 5 seconds and then flips back to the Chevy logo splash screen for about another 10 to 15 seconds. Second, and this may be related to the first issue, is that my last app no longer auto-launches after reboot. Most of the time this is the MTCradio app, but in 4.4.4 any app that was being used when the unit shut down would automatically start the next time it booted up. Has anyone else seen this and/or know how to fix?
Thanks!
I do have an OBDII bluetooth device enabled. I'll check the keymap version in factory settings. Is there a specific one I should be looking for or trial and error? Thanks!Do you have an OBD Bluetooth device enabled?
Change the keymap version in factory settings, one of them should get your last app to reopen.
After seeing what hans109h said, I tried changing the keymap. I tried all 10 and still had the issue. Since he mentioned something about the OBDII, I tried disabling that (removing the device from my paired devices) and it now works. It's kind of a nuisance to have to repair the OBDII bluetooth adapter every time I want to use it, but it's something I can deal with. Anyone know if there is workaround for the OBDII issue causing the last app to not launch properly on boot and making the HU crash?I had the same issue. The unit is crashing after trying to start the last active app. Thats why you see your car logo twice. I was not able to solve this and tried another ROM
Gesendet von meinem Mi-4c mit Tapatalk
I also can't find where to turn off the screen saver. I set the audio timeout to never, but it didn't shut it off. I'm also running Nova launcher and I've deleted all but the Next launcher. Can anyone help?I'm still not able to find it...were you able to find it on your unit?
No problem. Everything is trial and error with these. On some keymap versions my Wi-Fi wouldn't turn on, but the majority were the same. Some would result in previous apps opening on boot, some wouldn't, but with an obd device there is a crash that causes the boot logo.After seeing what hans109h said, I tried changing the keymap. I tried all 10 and still had the issue. Since he mentioned something about the OBDII, I tried disabling that (removing the device from my paired devices) and it now works. It's kind of a nuisance to have to repair the OBDII bluetooth adapter every time I want to use it, but it's something I can deal with. Anyone know if there is workaround for the OBDII issue causing the last app to not launch properly on boot and making the HU crash?
Thanks again hans and pathfinder!
Did you have all speakers connected?Found another issue with bluetooth. My phone audio doesn't come through. If I play music on my phone and it is paired to my HU, it will come through the car speakers without issue. If I make a phone call, the audio does not come through the car speakers. I'm assuming this might be another keymap option change, but before going through that, I wanted to see if anyone experienced the same.