yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note5] Psypeke:
A few updates ago, the handwriting keyboard appeared às the default keyboard. I know how to switch to the typing keyboard, but it is only temporary. Every time I start to search in the browser, the handwriting keyboard is the default.

The handwriting keyboard also lags for about a minute...sometimes longer...and I can't click to change to the typing keyboard. I also can't write on the handwriting keyboard because it freezes up.

Can someone help me permanently put the typing keyboard as default? Thanks.
[Android Head-Units] surfer63:
Hi,

Like you might have seen in "my" other thread "[Review] Joying PX5 2GB+32GB on Android version 8.0.0", I worked on rooting the Joying Android version 8.0.0 PX5-A53 Rockchip units. (Do not confuse this with rooting the Sofia 3GR Intel units)

I have now released my scripts for Linux/Unix like and for Windows. You can find these scripts on my github releases section.

It comes with an instruction. Read it carefully and if unclear let me know.

I also updated the rooting page of my website.

My signature under my posts also reflects the "new status".

Note that the current rooting method uses the "setenforce 0" method to root your unit. That is deprecated since Android 4.2 as it is less safe. Until now I (and many others) did not find a way to root our Chinese head units in the "safe way" (using setenforce 1). I will do my best to get the safe method working on our units (some day)!

Note: I do have a FYT unit, but the scripts should actually work on any PX5 Android 8.0.0 unit. The scripts "might" work on PX5 Android version 6.0.1 units, but you better use the official rooting methods in those cases. (Besides: Android 6.0.1 on the PX5 units is a "dead end").

========

I'm also working on Xposed on the PX5. The first attempts resulted in a not working Xposed. Upon uninstall I boot-looped my unit needing a fresh flash. At least I could test my root script one more time ;). I will continue on that.

I'm also working hard on my JET apk: A complete rewrite (multiple screens, tab based approach) and making it suitable for the PX5 as well. Some images are already showing up on my website
[Android Head-Units] surfer63:
reserved
[Android Head-Units] walkin123:
Hey Surfer,

When I run the Extra Tools app it tells me my unit is not a sofia or px5 unit. What information does it check?

If this helps any:

CPU: ARM Cortex-A53 eight-core 2+32 GB PX5; CPU: PowerVR G6110

Build: PX5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20180605.100502 test-keys

MCU: 2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160

System: APP2018-06-05 03:04:18

--Tully
[Android Head-Units] steef84:
Tried this script on Joying 2GB 32GB Android 6.01 unit. ADBoverwifi enabled. Script cannot connect to unit. Laptop and HU on same 2.4GHz network. After reboot no Superuser app apears appearantly. Joying Extra apps still says semi-rooted then. Too bad Joying has no 8.0 rom for this unit for now :(

C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>copy_install.bat 192.168.8.104
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
Reboot your Head Unit NOW!
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>
[Android Head-Units] surfer63:
That version 50 was theoretically configured for PX5 as at that time I did not have a PX5 yet. I based it on the way how the Sofias were configured. The check is now correct in the version I'm working on.

It still contains some bugs due to the massive rewrite and the new PX5 parts. You have to wait till that one is ready.
[Android Head-Units] walkin123:
Just let me know and Ill happily test it for you.
[Android Head-Units] surfer63:
Did you reboot your unit in advance?

And how often did you try? Sometimes you need multiple tries.

And how did you enable the adb over tcpip? Do you have a terminal app? If so could you give the command "getprop persist.adb.tcp.port". It should return 5555.

Furthermore: I am already in discussion with Joying as I think the PX5 wifi is not good.

As I was not certain whether it was my unit only or also on other units, I did not extensively communicate about it in this forum. I think quality control is not so good at Joying. Both users of Sofias and PX5s are complaining about terrible WiFi reception. The WiFi antenna needs to be soldered onto the board and I think the "assembling teams" have good and bad solderers.

Anyway: It only works for me when I take my phone and laptop into the car and use my phones hotspot. Downloading of apps over my home WiFi does work, but is extremely slow, much slower than my previous Sofia.

(Installation of apps from the Play Store is much faster though than on the Sofia).
[Android Head-Units] surfer63:
Give me a couple of more days. Almost there, but I have again a busy week in front of me.

Sorry to say, but at this time it takes perhaps more time to react on test reports than it takes me to test myself.
[Android Head-Units] wanb1i:
I tried this on my PX5 4x32 Oreo. The unit rooted just fine, then I was notified to update the SU Binary, so I did. Now I'm stuck on the Android Boot screen. Tried resetting 3 times, no joy. I tried re-running the root script and I get the exact same as above, it's not completing the boot to where adb will work.

Please Help! I have a very long trip on Wednesday, would be nice to have a stereo and maps...
[Android Head-Units] surfer63:
Sorry. That is something I do have to add. Do NOT try to update the su binary. It was the same in all previous methods so I really forgot to mention that now. The only thing you can currently do is reflash the unit with a fresh firmware. I will immediately update the pages and the instruction.
[Android Head-Units] wanb1i:
Ok, I'm downloading the 6/5/18 firmware. I really didn't want to upgrade this unit because everything was working with the stock FW it came with. oh well, the joys of modding android!

I'm going to wait until you have this done before I mess with it again.

Do I have to update the OEM & MCU as well? Never done that before SCARY!!

UPDATE:

I have it working again, now I need to set it back up.
[Android Head-Units] Orphlo:
PX5 Android Version 8.0.0 incompatible

Believe a user above expressed a similar issue where apk gives an incorrect analysis of system saying "This is NOT a Joying Sofia 3GR Intel-" which is true "-or a Joying PX5 unit!". Either they sent me the wrong unit (joking, I got the right unit) or the apk needs a little bit of tweaking ;)

I'd just like to know when your newer script arrives as your last release was over two months ago. I just want to remove Launcher3 since Joying firmware apparently doesn't allow a persistent default launcher; it changes back to Launcher3.

Have a JY-UO135N4
[Android Head-Units] surfer63:
There are great running apps more than 2 years old :). It doesn't mean a project is dead. Besides: I have a very interesting, busy life outside Joying.

Switching a launcher has nothing to do with my JET apk. If you want to switch the launcher you should do that from the Settings from the Apps part, where you define the standard apps. It is mentioned as "boot screen" app or something like that.

So not the Joying launcher changer as that only gives you the option for the Joying launchers.
[Android Head-Units] Orphlo:
Re:

Yup good to hear, and I'd certainly hope there wasn't someone who lived their life in a car. Anyway, yes what you're talking about is the 'Default Apps' section in settings. Normally the default home launcher option will allow you to change the default launcher, however the Joying unit will reset your choice each time it is rebooted. I don't know why it is, and the limited ability of Joying's "Launcher3" home screen is unfortunate, so it seems the only way to fix this is to remove Launcher3 completely and disable it which can only be done with root access, something I can't seem to get.

So ultimately It'd be great to see an update so I can get it done through your method, otherwise if there are any other methods feel free to let me know :good:
[Android Head-Units] surfer63:
I said "you should do that from the Settings from the Apps part", NOT from Joyings launcher settings.
[Android Head-Units] Orphlo:
Re:

No I got what you said, it's just that the Launcher app actually redirects you there. The Launcher app I'm using is Nova, and in Nova settings the option to set as default home app opens up settings to that location
[Android Head-Units] horuscurcino:
I was able to root my Joying JY-UOS01P4 unit (32GB+4GB PX5) OREO (NOT MTCD/E!) by modding some files and running your root package. I did the following manually because im not able to inject the mod to the main file yet:

1. downloaded the latest firmware update from joying website

2. extracted its contents and i put "service.adb.tcp.port=5555" on last line of the config.txt file

3. flashed this slightly modified firmware

4. Installed ADB over WIFI enabler "AoW_v1.1.apk" ( https://xdaforums.com/showpost.php?p=71616884&postcount=273 ) and made it happen

5. Connected to the router and followed your instructions. ROOTED !

Altough i was not able to use your great Joying Tools app (says my unit is not a Joying product) and was not able to use Viper4Android. By using root explorers seems some folders and files are write-protected even with root rights acquired by your method.

Thanks for your job !

Horus
[Android Head-Units] surfer63:
Nice your rooted it. JET version 50 was a "theoretical" approach to the PX5. The to be released version 51 will support the PX5.
[Android Head-Units] horuscurcino:
Great. I will wait for this release!

Thank you, Horus
[Android Head-Units] reckert:
I downloaded JET 51, and was able to root fairly easily. My only hiccups running the scripts were because I was using a work laptop that seems to stop once in a while, which caused timeouts on adb But I re ran the scripts a few times and was ultimately successful.

Edit: I also had a few issues because the Joying WiFi MAC address changed. This used up all of the DHCP Leases/ IP Addresses from my hotspot, so I had to restart the hotspot after a few reboots.
[Android Head-Units] looxonline:
Tried to root using the JET 51 APK. Could not get my unit to accept an add connection on 5555. My unit is not a Joying but it is an FYT 6026 SoM based unit made by Witson. WiFi and GPS modules are both based on the SoM so I guessed that whatever command enables the adb on the Joying ROM will most likely do the same on my ROM.

All I get is a "connection refused" error when I try to make the adb connection. I know that there is some degree of communication with the HU because when I enter the incorrect IP I get a timeout error after a long time.

So I figured that maybe I needed to try a different way of enabling adb over WiFi. Used the AoW_V1.1 apk and it also came back saying that adb was enabled but same error when I tried to connect.

Anyone have any ideas before I go and solder up a USB A male to male cable?
[Android Head-Units] surfer63:
Did you check if the port 5555 is really active. My JET apk should do and then mention that, but to be honest: I did test it, but I did not test this particular function in the latest development builds on my PX5 before release.

So please go into a terminal and do a "getprop persist.adb.tcp.port"

it should come back with 5555.

If it is correct, but keeps failing: please contact Joying. My WiFi on the PX5 is pretty ****ty. If I need to do these kind of things I really have to take my mobile with me and set it to hot spot to use that WiFi, and then connect my laptop to the same hot spot.

My previous Sofia had no issues with Wifi when standing on the driveway. This PX5 has.
[Android Head-Units] looxonline:
I'm guessing that you have checked the soldering of the pig-tail to the FYT SoM? My WiFi seems fine. Running using a blade antenna connected to the SMA which then follows the pig-tail to the SoM. Within the car I'm running everything off a mobile hotspot but I can still see networks up to 50m away. It may also be a bad RF layout on some of the earlier FYT boards that they have since fixed.

P.S. I'll give your suggestion a go on Wednesday evening when I will have a chance again. Thanks for the tip.
[Android Head-Units] wanb1i:
Google Voice from Speech key

I rooted and used the JET app on my PX5. Then installed the No Kill mod. Set the SW Speech (or Push to talk) key to speech in the SW app, but when I push it, it just opens a Google Web Page and doesn't listen unless I tap the Mic icon on the screen. I even went through the setup for Google Assistant, but it doesn't listen until I press the Mic Icon. Is this the way it's programmed? It didn't behave like this on the Sofia core. :confused:

Ideally, I would like to be able to set my speech key to enable Google assistant to listen and only to listen when I press the key, like it did with the Sofia core. I'd prefer NOT to have Google constantly listening in the car.

Any Help would be appreciated.;)
[Android Head-Units] looxonline:
So I managed to get it to work today. I don't know if I'm just such a noob that this is obvious but I had to go into the developer options and flick a toggle switch that has no label attached to it but is located as the very first option. I'm guessing that it enables all of the developer options. After I did that I then enabled USB debugging for good measure. Tried ADB again after that and it worked. It may be worthwhile adding this as a required step if there are other noobs out there like me.
[Android Head-Units] surfer63:
Maybe, but I didn't do that. If I don't count you and myself, I can't imagine the other 77 would not mention it, if it was neccessary to do your steps.
[Android Head-Units] looxonline:
True. I'm guessing that the ROM that WITSON put on my unit is slightly different to the Joying ROM even though both are FYT 6026 based. Thanks nevertheless for the script.
[Android Head-Units] wanb1i:
I agree Surfer, I didn't have to do that either.
[Android Head-Units] Squirley709:
Will this work on a JY-UO134N4PX5S unit? I'm having a hard time finding info on it.
[Android Head-Units] surfer63:
The ..PX5S units are QD units, not FYT units. So it is different from the hardware I tested on.

From rooting point of view it shouldn't matter at all, but I can't guarantee anything.

You could try. If it fails, either nothing happens or you might need to reflash your unit again with a fresh ROM.

But please note that you will not be able to use the JET apk to add mods to your system. The XSofiaTweaker will not work either as that Xposed module is based on FYT software. I think I have made it compatible for the FYT version 8 units, but it was way too hot the past 3 days to test it.
[Android Head-Units] Squirley709:
Thanks for the answer. So overall there isn't much I can do with this unit? I am still kind of new to all this and really just want root and viper4android.
[Android Head-Units] surfer63:
Rooting shouldn't be a problem using my script (but no guarantees).

I can't get viper4android to work on my (FYT) unit. I tried 3 different installation methods, described here and on several other sites. They all require the unit to be rooted in permissive mode (, which I have as I still can't get it to enforcing mode). Not a working version up till now. I must admit that as such I don't care much about viper4android, so it is low-prio. It is more that I'm just curious why it is so extremely hard to set it up on Android 8.
[Android Head-Units] Squirley709:
Poking around I found this thread: https://xdaforums.com/android-auto/...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724. Is this even possible on joying? It does have a rockchip.
[Android Head-Units] surfer63:
It is a rockchip but the hardware is different. The Malaysk rom is for MTCD units. You have a QD based unit.

Most Joying units are FYT based.

All different hardware builders.
[Android Head-Units] Squirley709:
I understand, thanks for being patient with me. Is there any custom ROMs available for the QD based joying or am I just gonna have to wait for it? I am afraid of the stock rom because I had terrible experiences with Xtrons stock units until I rooted and put Malaysk's rom on it. I suppose all I need is root and I can do whatever I want from there. I mean, is Joying overall a better experience than Xtrons?
[Android Head-Units] surfer63:
Sorry to say, but the QD units by Joying are a dead end. They were temporarily sold by Joying but all new version 8.0 units are again FYT units.

I'm afraid there are not too much users with QD units, and I'm almost sure no custom rom will be developed for it.

Take a look at Joyings blog page for a new rom for your unit: https://www.joyingauto.com/blog/category/updated-files-released/

Try my root script. If it works you have your unit rooted. If not you can flash a new rom from Joyings blog page.
[Android Head-Units] Squirley709:
Any suggestions on 10.1 Joying units? I want one I can root and custom rom.
[Android Head-Units] Squirley709:
Thanks for all your help and patience Surfer, I ended up trading the unit for a JY-UOS02P4. From what I found the JY-UOS02P4 will be able to do everything I want AND I'll be a able to use your services fully on it. Correct me if I'm wrong, but your JET will work 100% with this P4 unit.
[Android Head-Units] surfer63:
Yes, it will. Be it that the PX5 is slightly different and therefore the JET apk has less options.

But that may come if other, new wishes come up for the PX5.

The PX5 can easily be rooted.

Then the JET apk can be used and from JET you can also install Xposed (new not yet released JET v52). With the current rooting method hat is so much easier on the PX5 than on the Sofia.
[Android Head-Units] wanb1i:
USB-CP?

Can anyone tell me what USB-CP is? I'm looking at a new Joying PX5 unit (JY-TO151N4PX5S https://www.joyingauto.com/toyota-r...ia-player-support-subwoofer-video-output.html) that has what appears to be 3 USB ports, one of which is designated as USB-CP. A Google search wasn't helpful...:confused:
[Android Head-Units] looxonline:
I would assume that they mean USB - Car Play... there is only ever one port on a unit that supports carplay functionality.
[Android Head-Units] surfer63:
Note that this is a QD unit, not a FYT unit.

Probably no customization in the future. No fast-boot. And I think: no future.

I have no idea about the USB/CP.
[Android Head-Units] wanb1i:
WOW! ?

I had no idea it wasn't an FYT unit, I thought all Joying PX5 units were FYT!

Thanks Surfer for letting me know this. Will your rooting script work on this unit?

This unit is to replace the dying Sofia (5009) unit in my wife's car, so probably won't need much more than root.
[Android Head-Units] surfer63:
I'm almost sure it will work on the QD PX5 as well, as my script is derived from other completely non-Joying units.

But I did not receive any feedback yet from any user who might have tried it.
[Android Head-Units] wanb1i:
I'm a little dismayed that this is not an FYT unit, as I have upgraded my older 6021 Sofia to a PX5 6026 SOM and I'm quite happy with it and looking forward to some mods.:D

But since it's for my wife's Rav4 and it has the Factory look, I think I'm still going to get it for her. When I get it, I'll use your script to root it and let you know how it goes. It almost HAS to be better than the 5009 unit she has now that the screen works sometimes and not others!:crying:

Honestly, my biggest concern is keeping it cool. The design is quite different and there appears to be no room for a heatsink or a fan, maybe I can attach a small fan or 2 to the vents on the back and at least suck out the hot air?:rolleyes:

I decided not to get the QD unit, so I won't be able to test the rooting script for you. ?
[Android Head-Units] hapb:
I got the joying jy-uo135p4 awhile back and am considering getting root access on it. I just got a question about updates, will I still be able to install firmware updates? I'm familiar with other devices, but still quite new to android head units.
[Android Head-Units] surfer63:
Yes, you are. That makes no difference, but after every firmware update you need to root your unit again.
[Android Head-Units] hapb:
Thanks for the quick reply. I'll probably give it a shot next week. Will update with a success story or back here for help lol.
[Android Head-Units] twokidsandaphone:
Deleted - already answered.
[Android Head-Units] tweakmax2:
Can roughly tell me what the purpose of rooting vs stock?
[Android Head-Units] hapb:
Attempted to get root access today and ran in to an issue within the first couple of steps.

I've installed The Joying extra tools v54, and after enable adb over wifi and hitting the top left menu button I am presented with a blank white blank screen. Unable to get the ip address from here. I should also note going in to the Info tab with the about, credit, and help tab also are blank white screens.

Follow up:

Decided to go in to router to find ip address of HU. Went a head to run script with follow results.

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

connected to 192.168.0.53:5555

restarting adbd as root

connected to 192.168.0.53:5555

144 KB/s (108496 bytes in 0.734s)

Not sure if install is finished or has stalled.
[Android Head-Units] looxonline:
Reboot the unit. I've seen it get to this point before and not produce the final message but still work. If SU is on the unit after the reboot you are good.
[Android Head-Units] surfer63:
This is really weird, but if I run it on my phone I get the same. I will have a look at it.

W.r.t. the rooting. The adb-over-wifi connection can be really flaky, especially on these PX5 units. You sometimes need to try a couple of times.
[Android Head-Units] looxonline:
I had exactly the same thing happen with my unit. I had to go to the advanced WiFi menu to get my IP or use the router admin page. Strangely enough after the root the menu was there and has never disappeared since.
[Android Head-Units] hapb:
I already have tried multiple times, and again as i'm typing this reply lol. Looks like i'm getting the same results being stalled running the script. I'll wait a bit to see if the issue can be figured out.

I am unable to finish the rooting process. Once I can, it'll be smooth sailings from there.
[Android Head-Units] looxonline:
Go into your developer menu (3368), enable the top software switch (it should be un-labelled) then enable USB debugging then reboot the unit and try again. Also try this APK (https://xdaforums.com/showpost.php?p=71616884&postcount=273) to enable ADB over WiFi. I also had problems but a combination of these steps made it work.
[Android Head-Units] hapb:
I got it! The script finally finished running after the 6th or 7th attempt today and now have root access.

Have already installed xposed and xfytweaker, although haven't had much time to play around with it yet.

Are there any must have mods/tweaks/options?
[Android Head-Units] surfer63:
I really, really have no idea apart from the fact that the online thunkable environment recently has been updated. I use a "style" (actually it is different in thunkable) to specify the colors. That does work if you open the menu from the Mods, Enhance or Other (sub)screen, but not from the first System subscreen.

Even if I "manually" hard-code the colors it doesn't work.

Next to that is the tabview/menubar itself. The System/Mods/Enhance/Other buttons are "borderless" material design buttons, but they are now clearly visible as buttons with a frame around it.