System Specs
Baseband Version
FM_Base_18B_W21.12.3|sc9873A_modem|03-24-21 03:14:08
MARLIN3E_TRUNK_W21.13.3|uwe5623_marlin3E_usbhub|03-31-21 01:19:48
Build Number
QP1A.190711.020 release-keys
System Info
App 1280x720 2021-11-10 09:57:06
CPU Info
CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version
2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
Bluetooth Version
BLINK_2161_RELEASE/2021:09:14:19:38:05_blink
Hi there, trying to figure out why no sound is made from the head unit OR the phone when connected through bluetooth.....Not running Android Auto (disabled app).
Is there something simple I'm missing? 1st dive into these android head units, Any help is greatly appreciated.
Thank you!
Mekede or Winca or ???
****added hwinfo pics
Only solution I've found is to disable Sounds option in bluetooth access on the phone AUDIO and MESSAGE ACCESS. This at least allows the phone to make it's notification sounds while connected to head unit.....phone calls still get routed to head unit.
Doesn't seem there's any working method to have a notification on screen/with sound with this head unit....for now this will do
Update......it appears setting the unit's bluetooth Version to AVRCP 1.6 (in developer options) allows for app notifications to sound through the head unit.....No on screen toast etc, but I'm happy with the notification alerting audibly
Added info/pics
What unit is this?
What can i do/what can't i do?
Can/how can i root it ?
I've been reading but it is all just a blur of info to me at this point......anyone care to help clear the clouds for me??
Thank you in advice!
Trying to answer a bit of your questions, as notifications via Bluetooth are also a grey area for me.
Your unit has a fyt manufacturer id of 116. That id is used by YIN, NaviFly , Mekede , Prelingcar, Runningway, NIDYGR, Hengcheng, COHO and a number of unbranded units/resellers (and the list grows almost daily on aliexpress). Pick the one you like , but actually it doesn't make a difference. A Mekede firmware (last one 14 March 2023) will do fine.
What notifications do you want?
WhatsApp -> Register your unit under your phone, and it will receive notifications as well. @Clandaries wrote a post about that. See here.
Use the paid version of Tapatalk on your unit and do the same. It can relay multiple notifications.
About rooting: Why do you want to do that? What do you think it will bring?
"What can I do? What can't I do?" Wow! This is really a very broad question which can result in thousands of answers. Tell us what you want. That gives us the option to give you more specific answers.
surfer63 said:
Trying to answer a bit of your questions, as notifications via Bluetooth are also a grey area for me.
Your unit has a fyt manufacturer id of 116. That id is used by YIN, NaviFly , Mekede , Prelingcar, Runningway, NIDYGR, Hengcheng, COHO and a number of unbranded units/resellers (and the list grows almost daily on aliexpress). Pick the one you like , but actually it doesn't make a difference. A Mekede firmware (last one 14 March 2023) will do fine.
What notifications do you want?
WhatsApp -> Register your unit under your phone, and it will receive notifications as well. @Clandaries wrote a post about that. See here.
Use the paid version of Tapatalk on your unit and do the same. It can relay multiple notifications.
About rooting: Why do you want to do that? What do you think it will bring?
"What can I do? What can't I do?" Wow! This is really a very broad question which can result in thousands of answers. Tell us what you want. That gives us the option to give you more specific answers.
Click to expand...
Click to collapse
Thank you for clearing up some questions i had! It really helps me out. As to notifications, mainly it'd be nice to receive sms messages w/pop up on screen (not required, but it would be convenient)
Root, well honestly I'd like to use viper, i see that it's mentioned that it doesn't "work", that's something I'd like to play with (again not a necessity but i use viper on my phone and it makes a huge difference on vs off.
I think however most of what I'd like to do is run through different firmwares , for instance (not sure if available) but I'd like to try different firmwares with different camera apps, for instance current firmware has a Front Camera app....but nothing to manually view the rear cam....i believe, could be wrong, that some firmwares might even have a camera dvr app built in .....features like that which are missing....i tried a 3rd party dvr app from playstore but they all seem tailored to using cellphone cameras so its hit or miss as to if the apps even recognize the cameras......
Had one app that recognized front camera and it would record, but even switching to reverse would stop the recording and not resume.
Most of what I'd like to do may just be out of range of potential for these units....I'm really trying to feel out the limits and expectations.
Thank you 1000 times !!!
I appreciate you taking your time to answer my posts and helping to educate me on these devices.
I'll be reading back and forth through these post until i feel comfortable enough to start tinkering (and grab a factory firmware in case i mess up )
louforgiveno said:
Root, well honestly I'd like to use viper, i see that it's mentioned that it doesn't "work", that's something I'd like to play with (again not a necessity but i use viper on my phone and it makes a huge difference on vs off.
Click to expand...
Click to collapse
Viper might work nicely on a phone without DSP.
However, all these units come with a highly modifiable DSP nowadays. You don't need Viper (from my point of view).
And indeed, to prevent usage of Viper, you can now only use it when rooted.
Related
First of all, let me say that not only am I new to android, I am also new to smartphones in general. So when - in your amusing video, which I quite enjoyed watching - you say 'noob'...I mean NOOB!
I have Googled this problem extensively and have posted this question on 5 other android support forums over the last month or so, and although it seems (from my research) many people have this or a similar issue, no-one has come up with a solution. A forum memer from one of those websites has now suggested I post this here. I have, before posting, searched this site also for a solution, but it appears that although some have a similar problem, there has not yet been a solution found, or the advice given hasn't worked in my case.
So here's hoping somebody here can help with this irritating and inconvenient issue:
Device: Samsung Galaxy Ace
Carrier: Virgin Mobile
Country / Language: UK/English
OS / Browser / build number: Android Gingerbread 2.3.3
I am having the problem where I have set custom ringtones for some of my contacts, but they are not always being played as they are assigned.
I have all of my ringtones in an folder on my sd card (/sdcard/ringtones, having moved them from /sdcard/media/audio/ringtones to see if this solved the issue. It didn't)). I have a custom ringtone (mp3) set as the default ringtone and a couple of other custom ringtones set for a few of my contacts. However, when I receive a call the phone does not play the correct custom ringtone for that caller but instead plays the custom ringtone assigned to the previous person that called. If the caller is also the previous person to have called me, then it will play the correct ringtone, as they are the previous caller. (If that makes sense??)
To reproduce: Basically I install some mp3s onto my SD card. I go into my contacts, choose a contact, then click 'edit'. I then set the desired ringtone as the custom ringtone for that contact and click 'save'. When that contact rings, instead of the assigned ringtone, my phone plays the ringtone of the person who called me before that. When the next person rings, it plays the ringtone it should have played for the last contact. And so on. When I check the details for that contact, it confirms the ringtone I had chosen is still selected for that contact, it just doesn't play that one, but the one of the previous caller.
In addition to posting on Android help forums, I have also reported this bug to Samsung, although I'm not convinced it is a Samsung problem as clearly (according to my research) it is happening across the board with several other makes of Android phones. However, the reply I received from Samsung was:
"Thank you for contacting Samsung. As of yet, Google has not developed a fix for this fault so we may have to have the phone taken in by one of our engineers without any real guarantee it will be resolved. We could set this up for you but you may have to wait 28 days for the phone to be returned to you."
I am sorry, but I think it is unreasonable to be expected to give my phone up for a month, with no guarantee the issue will be sorted, just to be able to use a facility Samsung state is already available on the phone when it is clearly not.
I am inclined to believe this is an Android problem, and therefore would really appreciate any advice/a fix/solution anyone on here may be able to offer.
Thank you.
This problem - or lack of a solution - is really annoying me now as no-one seems to have a fix for it. I have over the last month posted on 6 forums: Android Central, Android Forums, Android Community, Google Android Support, OHA Project Issues and XDA developers. In total the post has had over 2500 views but NO solution!
I have also submitted the issue to Samsung - they don't know how to fix it either!
Have I got the only unfixable problem ever to affect an android phone??!!
I just don't understand why the developers of both the phone and the operating system can't solve a problem in their own product!
PLEASE, can anyone help?
"Have I got the only unfixable problem ever to affect an android phone??!!"
Looks like it
Thanks for all the interest. Not.
Well. I was advised to post this question on here by a couple of other Android forums, as they said you guys love trying to find solutions to this kind of thing.
But not even any interest or replies or even acknowledgement, least of all any suggestions.
Guess those Android forums just got it wrong.....
It might be true that Samsung can't do much to fix this, it's clearly a software problem and maybe it has not been fixed by Google (or maybe it has been fixed and you don't have the OS version that has the fix, i.e. Gingerbread 2.3.6/2.3.7)
I'm sorry to see that nobody replied to this yet, but the reason might be simply because nobody really knows how to fix (if possible) this problem. Again, this is a software problem and Samsung doesn't have much to do here, so you could try and flash a newer OFFICIAL rom for your Ace, as custom roms might have some other bugs. (You could try with CyanogenMod maybe?)
I hope you can find a way to make it work good luck.
Device: Samsung Galaxy Ace
Carrier: Orange Romania
OS: Android Gingerbread 2.3.3
I too have had a similar problem: when a normal contact calls it uses default ringtone... when a custom ringtone contact calls after that, the same default ringtone is used... if the custom contact calls again the custom ringtone is used.
Possible solution:
Put all ringtones in SDcard/Media/Audio/Ringtones
Go to Contact -> Edit -> Ringtone -> select Sound -> browse SDcard/Media/Audio/Ringtones and select your custom .mp3 file -> Save Contact
Test to see if it works and then reboot and see if it still works.
Please reply or press Thanks button to let me know how it turned out
ybres said:
Device: Samsung Galaxy Ace
Carrier: Orange Romania
OS: Android Gingerbread 2.3.3
I too have had a similar problem: when a normal contact calls it uses default ringtone... when a custom ringtone contact calls after that, the same default ringtone is used... if the custom contact calls again the custom ringtone is used.
Possible solution:
Put all ringtones in SDcard/Media/Audio/Ringtones
Go to Contact -> Edit -> Ringtone -> select Sound -> browse SDcard/Media/Audio/Ringtones and select your custom .mp3 file -> Save Contact
Test to see if it works and then reboot and see if it still works.
Please reply or press Thanks button to let me know how it turned out
Click to expand...
Click to collapse
Thanks, but I had already tried this in the beginning, but no luck
I'm sorry to hear that... That exact method helped me. It may still have a glitch every week or so but it doesn't happen very often.
unbelievable, looks like there is truly no solution.. screw everything that Android has to offer if something as trivial as this can't be fixed.
Hello,
I have a TC55 from Motorola Solutions (i.e. the enterprise division that does not belong to Google). It is a rugged phone with a big battery (4400 mAh), but certainly not the sleekest design. Not sure if there is much interest in this kind of device, and I am certainly no developer - but in case anyone is investigating the TC55, here are two things I found so far:
It does not come with any Google apps: no Maps, no Gmail, no Play store and so on.
It is easily rooted with Framaroot using the Gandalf exploit.
(I cannot post this info into the Framaroot thread due to my low post count).
Anyway, maybe this helps someone. I will be happy to try to answer any questions about the TC55, but keep in mind I am no pro and I am not keen in messing around in its internals much more than I have done already.
Elanguescence said:
Hello,
I have a TC55 from Motorola Solutions (i.e. the enterprise division that does not belong to Google). It is a rugged phone with a big battery (4400 mAh), but certainly not the sleekest design. Not sure if there is much interest in this kind of device, and I am certainly no developer - but in case anyone is investigating the TC55, here are two things I found so far:
It does not come with any Google apps: no Maps, no Gmail, no Play store and so on.
It is easily rooted with Framaroot using the Gandalf exploit.
(I cannot post this info into the Framaroot thread due to my low post count).
Anyway, maybe this helps someone. I will be happy to try to answer any questions about the TC55, but keep in mind I am no pro and I am not keen in messing around in its internals much more than I have done already.
Click to expand...
Click to collapse
I heard my company is planning to go with these soon for entry level supervisors such as myself. I'm trying to figure out exactly what it is. All the specs and brochures from Motorola keep calling it a mobile computer in a smartphone "form factor" but never actually call it a phone. I didn't see anything in any of the specs to lead me to believe for sure that it was a phone or if it was just an Android computer in a smartphone form factor.
Anyway, I just wanted to confirm, that, you're certain this is a phone, correct?
Thanks.
- Byron
bfollowell said:
Anyway, I just wanted to confirm, that, you're certain this is a phone, correct?
Click to expand...
Click to collapse
Yes, definitely. You can call and get called, and you can send and receive SMS. It also supports wired headsets, and it is supposed to work with Bluetooth headsets, though I do not have any to test.
Elanguescence said:
Yes, definitely. You can call and get called, and you can send and receive SMS. It also supports wired headsets, and it is supposed to work with Bluetooth headsets, though I do not have any to test.
Click to expand...
Click to collapse
Thanks for the info but it looks like mine is going to be crippled.
Sort of a let-down really. Yes, it "can" be a phone. Or without a sim card it can be a really powerful Android based mobile computer. That's what it is going to be for most of us. Only a few supervisors with area management approval are going to get units with the phone features working. Still cool. Just not as cool as I'd thought it was going to be.
- Byron
bfollowell said:
Thanks for the info but it looks like mine is going to be crippled.
Click to expand...
Click to collapse
I see, sorry to hear that. It sounds weird to me to do that, but then again I have no clue about this type of work.
Maybe the crippling could be worked around or undone by people with good Android knowledge - but I suppose it might not be the best idea to go against company policy.
Elanguescence said:
I see, sorry to hear that. It sounds weird to me to do that, but then again I have no clue about this type of work.
Maybe the crippling could be worked around or undone by people with good Android knowledge - but I suppose it might not be the best idea to go against company policy.
Click to expand...
Click to collapse
I don't think they're doing anything all that special to cripple it. They just won't all have sim cards or a cell plan. Pretty much as simple as that.
I won't be doing anything to circumvent that though or rooting it or anything like that. It's not like it's a gift and it belongs to me or anything. After almost 22 years, I've kind of grown to like my job and getting a paycheck every two weeks.I'd kind of like to keep it for another 15 or 20 years. Who knows, maybe my manager will decide that I need cell service with mine.
I work for a large automaker in the U.S. We have over 2.8 million square feet under roof. Personally, I can be anywhere on in the plant, on the roof, in pits & sub-basements underneath or anywhere on or near the 50 acre plant site at any given time. A lot of what I need to do on a daily basis is through our intranet portal. They're putting in something like 500 new wi-fi repeaters/extenders all around the plant as well. They're purchasing these for over 300 first line supervisors at my site alone. I'm pretty sure they're doing this corporate-wide so I hate to think what they're spending on these things as a corporation. I'm sure it would bankrupt many small nations! In addition to giving us portal access away from the desk, these are meant to replace our aging industrial radio system. As expensive as these are, they're still much cheaper than $1.5 to $2k per person for a radio that has no other built-in functionality and these do seem pretty ruggedized.
Still a shame about the phone functionality though.
- Byron
Can you see what browser it comes with? Can you install (untrusted) APKs directly without rooting it?
FYI, in case anyone's wondering, there is a version with Google apps on the way (if it isn't already orderable).
Sent from my Moto X
tfnico said:
Can you see what browser it comes with? Can you install (untrusted) APKs directly without rooting it?
Click to expand...
Click to collapse
Browser is a standard one, which comes with other devices. Name is Browser.apk and version is 1.0.9
It's possible to install unsigned APK's without rooting.
google account
Hi,
I got stucked with trying to get google calendars from my google account to TC55.
I found one solution to setup google account as a corporate one, but it's not available anymore due to change in google policy.
I can setup google mail via email account, but that doesn't bring me my calendars to the device.
I tried to install gapps but without success.
Is there any other way?
Thanks.
Motorola work on google apps for TC55.There is in beta.
Elanguescence said:
... here are two things I found so far:
It does not come with any Google apps: no Maps, no Gmail, no Play store and so on.
It is easily rooted with Framaroot using the Gandalf exploit.
(I cannot post this info into the Framaroot thread due to my low post count).
Anyway, maybe this helps someone. I will be happy to try to answer any questions about the TC55, but keep in mind I am no pro and I am not keen in messing around in its internals much more than I have done already.
Click to expand...
Click to collapse
Obviously u rooted, can u install gapps in it?
RjCode said:
Obviously u rooted, can u install gapps in it?
Click to expand...
Click to collapse
No idea, I haven't tried. As far as I understand gapps are usually installed via flashing a zip from recovery, and the stock recovery of the TC55 does not have that option, it only allows reflashing a whole image, if I understand it correctly. Either way, I have come to appreciate the open source alternatives and do not want to get Google on my phone, so I will not try, sorry.
However, going by this thread over at the Motorola support forum, it seems it won't take long until there is official gapps support:
https://developer.motorolasolutions.com/thread/4989
Motorola has now released a TC55-firmware with Google apps. Here are the release notes:
https://atgsupportcentral.motorolasolutions.com/content/emb/docs/ReleaseNotes/Release%20Notes%20-%20%20TC55_RevAPlus_GMS_01%2074G_v10.htm
According to the support email they sent me, to get the actual release you need to perform the following arcane ritual:
Resolution Type is : Software Download
Resolution Id is : 95562
Resolution Title is : TC55 Update Image v1.74 with GMS (Google Mobile Service) Release Note & Factory Reset & Enterprise Enabler package
restrictedSW :
T55N0JGMVRUEN17400.zip 321 MB TC55 OS Recovery Update package
T55N0JGMVAUEN17400.apf 321 MB TC55 OS update package file for deployment using MSP
If you require access to OS files for TC55 1.74 GMS then call the local Support Desk and provide following information:
a. Site ID
b. Serial #(s)
c. Phone #
d. Customer name (First and Last)
e. E-mail address
Click to expand...
Click to collapse
Don't ask me what the local support desk number is, or the site ID, or why they have to make this so complicated.
Hi Elanguescence,
I think I screwed up my tc55 by enabling the multiuser function without first creating the white list. Now all the users (with admin rights) does not have access to all the programs, including Applock Administrator and Multiuser administrator.
To cut things short, do you know of a way to reset the device? I don't mind setting it to factory default and start over. I've googled it and some said to launch Rapid Deployment and scan a barcode from there... but my Rapid Deployment just says "Service Not Ready, Please Wait" and get stuck there.
Any help appreciated. Thank you.
Any TC55 users here? Should be getting my unit w/ GMS soon... How do you guys like it?
Is the bootloader locked?
Sent from my Moto X
Hey!
I want to Buy one TC55 for me. Normally i hate Android and the Google stuff on the Phone but some Motorola Salesman told me there is a version with out.
Now i use an Sybian Device. That mean i am "offline" the hole time and when i need Internet the Phone connect the the Internet.
So how about that phone can i work "offline" to?
I will also use an VPN Tunnel to block on my backend all Connnection i dont want. Does all Data trough this VPN Tunnel ?
How about the Barcode Scanning does it work good?
I know for 2D i need to use the Cam but how works it when i am in some other Application?
Nobody?
Ok. I just bought a TC55 from a Friend and I was wondering if someone would post the update to get GSM and the Factory Reset packages. I went to the page and it requires all the information posted above before. Mine is rooted, but i am trying to install GAPS but the recovery is the basic and cannot. I manually installed Google Play and the Google Play Services but Google Play services keep crashing and the Play Store will not connect, any ideas ?
the are 2 versions one with google s... service and the other without.
So i belive you have the first?
(Can i ask you some question about that phone?)
Joying got in contact with me and asked me if I would wanted to test one of their new PX5 2GB models on Android version 8.
I decided that I wanted to do so, so I received for some 28 euros a Joying JY-VO130P2.
So what is it:
8" screen 2DIN unit for VW/Skoda/Seat/Audi
ARM Cortex based ARM V8, 1 processor 8 A53 cores (4 running at 1.5 GHz, 4 "low energy" running at 1.2 GHz)
FYT based SOM
2GB internal memory (RAM)
32GB storage (ROM)
Android version 8.0.0
particularities: DVD-player
I made a video review of it which you can find here:https://youtu.be/MH1snfDIU5A
The Good:
seems minimally faster than the Sofia 3GR
FYT/syu software the same as on Sofia 3GR.
Android 8.0.0, longer support
Android 8 supports split-screen functionality out of the box.
Improved radio reception (but needs to be tested over longer period)
Improved sound quality (I think, but I forgot to mention in the review)
The bad:
Too high temperatures of the cpu
No user configuration of buttons
FYT/syu software the same as on Sofia 3GR (I mean that some "weird" things are still there on the PX5 as well)
FYT/syu applications (radio, bt, music player, etc.) do not support split screen (and it is so simple to enable this)
No Android 8 Automotive integration
Chinese translations could be improved using on-line tooling like weblate.org or crowdin.com (or others) by using the user community.
The really bad:
Too high temperatures of the cpu. It really needs better cooling.
Update Sun 13 May 2018:
There is indeed an issue with the WiFi on this new Version 8.0.0 model. I already mentioned in my video review that it did not auto-connect to my WiFi networks.
- When fully rebooting the unit, it connects automatically to my home WiFi. No issue at all.
- When coming from deep-sleep, WiFi is either switched off ór WiFi is still on, but it doesn't connect automatically to my WiFi networks.
See update Fri 18 May
And maybe some explanation: I mentioned in the review that it is very simple to alter the AndroidManifest.xml to allow resizing the app and make it function in split-screen. So why didn't I do that myself?
The Joying apps are signed. Some parts can be easily changed without touching the signing, but the AndroidManifest.xml is part of that signing as it also contains the security options the application needs. Off course I do not have the Joying signature so I can't recompile the app with the same signature while the AndroidManifest.xml is obviously changed. That is exactly how it should work or any hacker could get access.
FYT/syu should change this.
Update Mon 14 May:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Update Tue 15 May:
The Google Assistant with spoken searches does not work.
When trying to use the voice search function (clicking the microphone in the search bar), It shows very shortly the 'Speak now' indicator before it turns into an error message that mentions "No internet connection". I checked very carefully and my internet connection is fine. I tried with 2 home WiFi networks and via hot-spot on my phone. All internet connections work fine, but Google search still gives this error message.
Update Fri 18 May:
See post #44
Update Wed 23 May (test of Android auto):
See post #54
Update Sunday 10 June:
See post #77
- OK Google solved.
Update Tuesday 12 June:
Some update about the BT app erasing your Google contacts: Joying is now working full steam on it. Another user made a nice video on youtube about it
Thanks a lot for your great review video!
Huh, 17 minutes... but it's definitely worth watching it fully till the end.
You spent a huge amount of effort and Joying still took 28 EUR from you? They should be ashamed!
So, the Joying Intel Sofia users (like me) will loose your support now? You state at the end of the video that you plan to continue using it in your car.
Interesting review, it addresses many of the questions I had regarding the new Joying PX5 units. Thanks!
Now as @realzoulou mentions above, I hope we won't lose you on the SOFiA platform! Your work on JET and on XSofiaTweaker is central to the success of those units.
I spend a day thinking whether I wanted to spend that money, because I really didn't. Finally I did agree because I thought: "then I have a spare unit for 28 euros".
Like I mentioned: the user layer software (the apks) is the same on the Sofia and the PX5. I already decompiled it in both apktool and jadx.
I can continue the XSofiaTweaker the same way for the PX5 as for the Sofia. Same for the JET apk with some small internal changes (if Sofia then, else ..)
I already made a nokill main server (=sofia server on Sofia) using the exact same steps as on the Sofia (and as explained by @realzoulou) and I replaced the radio mod.
Android 8 for this device is that new that there is no firmware to download yet.
I don't think rooting is a problem, but I'm not going to do/try that without firmware that allows me to reflash. Same for Xposed.
I will program the option to user-select the delay time for double/triple tap today (for Sofia), or at least early next week. However, I think XSofiaTweaker is now almost ready.
I think no new developments will come out for Android 6, so no further developments are necessary either for JET. Mods can easily be added as I simply upload them and use an xml to configure installation. Upload it, add a line to the xml, simply recompile: done.
I like to tinker, but I'm also a simple user that doesn't need that much. Especially when (or more probably: if) Joying/FYT/syu will make more hardware buttons and steering wheel buttons user configurable, there is even less need for special apps. (And I think I forgot to mention that GPS speed indication is correct on this units, but that should actually not be necessary to mention: it should simply work)
I just read on this forum Yesterday that on the standard Joying when you press the Navi button, the assigned (Navi) app will be started. If you press the button again, the previous app will be brought to front. Pressing it again the Navi app will be brought to front again. Etcetera. I did not even know that, but it is very handy. Of course that no longer works in the XSofiaTweaker (or in Gustdens mods).
Only that little overheating barbecue inside is worrying me.
https://www.joyingauto.eu/blog/category/update-firmware/
https://www.youtube.com/watch?v=AXQ4tsXO0Y0
@surfer63 what do u think? it will fit?
RoNeReR said:
https://www.joyingauto.eu/blog/category/update-firmware/
https://www.youtube.com/watch?v=AXQ4tsXO0Y0
@surfer63 what do u think? it will fit?
Click to expand...
Click to collapse
No it is not suitable. The 2GB-RAM/16GB-ROM and 4GB-RAM/32GB-ROM models are NOT FYT based and NOT compatible with the 2GB-RAM/32GB-ROM models.
The version I have is a FYT based 2GB-RAM/32GB-ROM version. There is no Android version 8 firmware for it yet.
Update Sun 13 May 2018
There is indeed an issue with the WiFi on this new Version 8.0.0 model. I already mentioned in my video review that it did not auto-connect to my WiFi networks.
- When fully rebooting the unit, it connects automatically to my home WiFi. No issue at all.
- When coming from deep-sleep, WiFi is either switched off ór WiFi is still on, but it doesn't connect automatically to my WiFi networks.
And maybe some explanation: I mentioned in the review that it is very simple to alter the AndroidManifest.xml to allow resizing the app and make it function in split-screen. So why didn't I do that myself?
The Joying apps are signed. Some parts can be easily changed without touching the signing, but the AndroidManifest.xml is part of that signing as it also contains the security options the application needs. Off course I do not have the Joying signature so I can't recompile the app with the same signature while the AndroidManifest.xml is obviously changed. That is exactly how it should work or any hacker could get access.
FYT/syu should change this.
(also added to first post)
There's a 4gb version now on the joying website that is FYT based...
Probably will pick one of these up as a spare, at least the SoM, if anything to test or generate a rom, and get Xposed working on this!
Once root is ahcieved, the manifests can be changed, the program only needs to be granted root, and it'll work fine.
Questions:
Did you look at the clock speed? Is it variable? What governor is used?
What is the three lines present in the system bar do?
Did you open the unit? Haven't found any photos of the interior of the new units yet.
gtxaspec said:
What is the three lines present in the system bar do?
Click to expand...
Click to collapse
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
carter.w.jason said:
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
Click to expand...
Click to collapse
You have the fyt model right?
gtxaspec said:
You have the fyt model right?
Click to expand...
Click to collapse
Correct
carter.w.jason said:
Correct
Click to expand...
Click to collapse
Are you able to get us some pictures of the internals?
@gtxaspec
Nice looks like a drop in replacement for the 6021...
---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------
carter.w.jason said:
Should be just the Menu icon, 3 dots.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
Testing Unit on Standby!
My PX5 is just sitting here, doing nothing. Will help test anything.
Click to expand...
Click to collapse
You have the 6.0 os installed? Want to try a custom ROM ( if I can figure it out). You can reflash stock if needed.
gtxaspec said:
Nice looks like a drop in replacement for the 6021...
---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------
You have the 6.0 os installed? Want to try a custom ROM ( if I can figure it out). You can reflash stock if needed.
Click to expand...
Click to collapse
Yes, should be 6.0, what ever is stock. I'm down to try a custom ROM. I've felt like this is the better unit, if it could be tamed.
Update Mon 14 May
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
surfer63 said:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Click to expand...
Click to collapse
That's a bug in the SYU dialer app, it never went away. The solution is to use Xposed app settings to deny contacts write permissions. Ouch.
gtxaspec said:
Did you look at the clock speed? Is it variable? What governor is used?
Click to expand...
Click to collapse
Overlooked this one. Will check tonight. It is variable from 216 MHz to 1.51GHz, but I will look at the specifics tonight.
surfer63 said:
Update Mon 14 May:
There used to be a bug in the older ROMs that where you gave the BT access to your contacts, it would erase all your contacts.
Well, 8.0 also erases all your contacts!
This issue annoys me highly as it is so old and it still isn't solved.
Click to expand...
Click to collapse
I have this bug on the 7.0 Android as well - this annoys the **** out of me!
Zeze21 said:
I have this bug on the 7.0 Android as well - this annoys the **** out of me!
Click to expand...
Click to collapse
I reported this bug immediately to Joying, like I did last year and like other users did as well: users from the XDA forum as well as the previous carjoying forum.
Joying reacted really surprised on my mail.
That surprised me again a lot (with some other emotions as well).
Hi guys, i'm a little confused and between 2 minds on my joying headunit. I've been running the android 10 unit for quite some time now (https://www.joyingauto.com/joying-9...-android-10-0-car-autoradio-ips-1280x720.html) and generally really like the spec, features and responsiveness. However there seems to be a lot of different ways of using it. And i can't quite decide what would be the 'best' way.
1. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and either fitting a 4G data sim
2. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and using my phone as a wifi hotspot and tethering the internet to it to keep everything running natively.
3. I can use Android Auto and mirror my phones apps to the headunit and use it that way.
Just looking for opinions and discussion around how peope are using there's and why? I use mine in configuration 2 above.
As a side note, i'd love to install a custom rom onto the unit rather than use joying's image but can imaging a 100 things would break and that i'd potentially brick the unit by just attempting it. Even their update process seems to be a blog post that says "Here's some links, if you not sure what to use, email us and we'll advise." But i don't trust that i'd get much support with a bricked or dodgy update. Thouhts?
I do 1 and 3 on mine, but with CarPplay.
Reason being: CarPlay nav is more "on the road friendly" in that the UI is designed to be used while moving.
Native functionality is good when I want the unit to do the stuff while I just BlueTooth sound from a different device.
My one issue is that if I have data turned on and enable CarPlay, my phone uses the head unit as a hotspot which isn't ideal.
thestraycat said:
Hi guys, i'm a little confused and between 2 minds on my joying headunit. I've been running the android 10 unit for quite some time now (https://www.joyingauto.com/joying-9...-android-10-0-car-autoradio-ips-1280x720.html) and generally really like the spec, features and responsiveness. However there seems to be a lot of different ways of using it. And i can't quite decide what would be the 'best' way.
1. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and either fitting a 4G data sim
2. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and using my phone as a wifi hotspot and tethering the internet to it to keep everything running natively.
3. I can use Android Auto and mirror my phones apps to the headunit and use it that way.
Just looking for opinions and discussion around how peope are using there's and why? I use mine in configuration 2 above.
As a side note, i'd love to install a custom rom onto the unit rather than use joying's image but can imaging a 100 things would break and that i'd potentially brick the unit by just attempting it. Even their update process seems to be a blog post that says "Here's some links, if you not sure what to use, email us and we'll advise." But i don't trust that i'd get much support with a bricked or dodgy update. Thouhts?
Click to expand...
Click to collapse
I believe you mean FYT UIS7862 based unit. Joying is a made up brand.
3. Pseudo Android Auto- reality is it is a hack that will eventually frustrate as google and phone manufacturer release updates. These units are NOT Android Auto.
Re. Custom ROMs. None exist and are not needed.
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Nope but is it an FYT based headunit - post Android system information including MCU version to understand what variant the unit might be and what bluetooth your device has.
FYI - Bluetooth is not standard in these units.
marchnz said:
Nope but is it an FYT based headunit
Click to expand...
Click to collapse
One that I'll insult tomorrow is, yes.
Edit: I'm also "installing" it tomorrow.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
I don't have any bluetooth issue with mine after the aug update. (finally)
spludgey said:
One that I'll insult tomorrow is, yes.
Edit: I'm also "installing" it tomorrow.
Click to expand...
Click to collapse
Oh that poster had no intention of helping you, they just couldn't wait to tell you that you had posted in the wrong forum.
As for bluetooth implimentation, other than changing the variable in config.txt's sys.fyt.bluetooth_type= entry. They may not be any more you can do.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
Not sure what exact function you are missing, but I used this one to install my OBD scanner (Vlinker) that the head unit would not connect to.
Bluetooth Finder, Scanner Pair - Apps on Google Play
Find and pair your bt device. Find your headset, smart band or earphone easily
play.google.com
ludditefornow said:
Oh that poster had no intention of helping you, they just couldn't wait to tell you that you had posted in the wrong forum.
As for bluetooth implimentation, other than changing the variable in config.txt's sys.fyt.bluetooth_type= entry. They may not be any more you can do.
Click to expand...
Click to collapse
No one could establish the unit to be FYT based on this post.
without that info recommending a configuration setting which is applicable only to FYT based units is just as useless. I request you stop making assumptions about my posts as you might be lacking prerequisite knowledge.
Knowing what the unit is, is everything. A cursory read thorough MTCD forums show just how misunderstood it is, and without my posts and reporting to moderators the forums quickly fill up with out of topic posts and the real development falling off.
If every new post started with, my unit is "ANDROID SYSTEM INFORMATION + MCU version" then those that actually know could recommend and not enter a tool like guessing game.
Would be great if you begun assisting too, if not, not a problem and if you don't like a post the report button is always available to you.
This is my last post on the matter with you.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
For a hands-free bluetooth dialing app that works with FYT 7862 head units, I recommend the free "Voice Call Dialer" by ArtostoLab, which is available on the Google Play store. It allows you to say the name of the person in your contacts list that you want to call on your cell phone over the Bluetooth connection, and it confirms the contact's name by displaying it as it counts down from 3 seconds (you can configure this value) before it initiates the Bluetooth phone call.
Previously I used the Google Assistant to make calls, but when I upgraded my old PX5 to the Joying 7862 10.5 inch 1280x720 head unit I found that the only way I could get Google Assistant to make call using my voice was by setting the "Smallest Width" DPI value in the "Developers options" to a value of 596 or less, and using an older dialing app called "GVC Callhandlert 4 Joying" which is described here:
Joying forward dial requests from Google Voice
By replacing the old GVC dialing app with the Voice Call Dialer, I am now able to set my screen to full resolution, with the "Smallest Width" DPI value set to 720 DPI. I am not able to make a voice call _directly_ from Google Assistant, but I can tell Google Assistant "Voice Dialing", and then I can just say the name of the person I want it to call.
Edit: I had a typo in the open command, and the word "open" is optional.