FORUMS
Remove All Ads from XDA

[Review] Joying PX5 2GB+32GB on Android version 8.0.0

1,602 posts
Thanks Meter: 643
 
Post Reply Email Thread
14th May 2018, 06:13 PM |#21  
surfer63's Avatar
OP Senior Member
Flag Zwolle
Thanks Meter: 643
 
Donate to Me
More
Quote:
Originally Posted by gtxaspec

Did you look at the clock speed? Is it variable? What governor is used?

Maybe not for @gtxaspec, but for the others who would like to know.
I slightly touched on the PX5 cpu/cores in the review. The PX5 has 8 cores: 4 "low energy" cores and 4 "performance" cores, listening respectively to policy0 and policy4.
Standard frequency is 1.2GHz, the performance cores can go up to 1.51GHz. The cores of the PX5 are scaled up/down per set of 4 cores, the policy0 and policy4 set (whereas the Sofia 3GR cores where adapted per core).

So what I did:
Code:
cd /sys/devices/system/cpu/cpufreq

cat policy0/scaling_available_governors
conservative ondemand userspace powersave interactive performance
cat policy0/scaling_governor  
interactive
cat policy0/scaling_available_frequencies
216000 408000 600000 816000 1008000 1200000


cat policy4/scaling_available_governors
conservative ondemand userspace powersave interactive performance 
cat policy4/scaling_governor  
interactive
cat policy4/scaling_available_frequencies 
216000 408000 600000 816000 1008000 1200000 1296000 1416000 1512000


px5:/sys/devices/system/cpu/cpufreq/policy0 # ls -l
total 0
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 affected_cpus
-r-------- 1 root   root   4096 2018-05-14 18:35 cpuinfo_cur_freq
-r--r--r-- 1 root   root   4096 2018-05-14 17:20 cpuinfo_max_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 cpuinfo_min_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 cpuinfo_transition_latency
drwxr-xr-x 2 root   root      0 2013-01-18 09:50 interactive
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 related_cpus
-r--r--r-- 1 root   root   4096 2013-01-18 09:50 scaling_available_frequencies
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 scaling_available_governors
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 scaling_cur_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 scaling_driver
-rw-rw-r-- 1 system system 4096 2013-01-18 09:50 scaling_governor
-rw-rw---- 1 system system 4096 2013-01-18 09:50 scaling_max_freq
-rw-rw---- 1 system system 4096 2018-05-14 17:20 scaling_min_freq
-rw-rw-r-- 1 system system 4096 2013-01-18 09:50 scaling_setspeed
drwxr-xr-x 2 root   root      0 2013-01-18 09:50 stats


px5:/sys/devices/system/cpu/cpufreq/policy4 # ls -l
total 0
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 affected_cpus
-r-------- 1 root   root   4096 2018-05-14 18:35 cpuinfo_cur_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 cpuinfo_max_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 cpuinfo_min_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 cpuinfo_transition_latency
drwxr-xr-x 2 root   root      0 2013-01-18 09:50 interactive
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 related_cpus
-r--r--r-- 1 root   root   4096 2013-01-18 09:50 scaling_available_frequencies
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 scaling_available_governors
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 scaling_cur_freq
-r--r--r-- 1 root   root   4096 2018-05-14 18:35 scaling_driver
-rw-rw-r-- 1 system system 4096 2013-01-18 09:50 scaling_governor
-rw-rw-r-- 1 system system 4096 2013-01-18 09:50 scaling_max_freq
-rw-rw-r-- 1 system system 4096 2018-05-14 17:20 scaling_min_freq
-rw-rw-r-- 1 system system 4096 2013-01-18 09:50 scaling_setspeed
drwxr-xr-x 2 root   root      0 2013-01-18 09:50 stats

cd stats
px5:/sys/devices/system/cpu/cpufreq/policy4/stats # ls -l
total 0
-r--r--r-- 1 root root 4096 2018-05-14 18:35 time_in_state
-r--r--r-- 1 root root 4096 2018-05-14 18:35 total_trans

cat time_in_state       
216000 3715
408000 4840
600000 10192
816000 50199
1008000 54206
1200000 23718
1296000 1673
1416000 1257
1512000 5376
From the stats (the last block), you can see that most time was spent in the 816 MHz and 1008 MHz frequency, and hardly any time in the highest frequencies. I think that this was due to throttling due to the overheating cpu.

Edit: I already have csv files containing
Code:
"YYYY-MM-DD hh:mm:ss","AvgTemp","LowFreqCoresTemp","HighFreqCoresTemp","LowFreqCoresFreq","HighFreqCoresFreq"
but for reading out the frequencies I need root access (like in the JET apk on Sofia). As I did not root my unit yet, I need to do that via adb.
I'm not going to take my laptop with me during a drive. Set the unit as hot-spot, connect over adb on the laptop and let a rooted shell run during the trip.

Currently I use a shell script for that, that measures every 10 seconds.:
Code:
#!/system/bin/bash
sleep_time=10

mdate=$(date +%Y%m%d-%H%M%S)
file_name=/sdcard/px5temp_$mdate.csv

echo '"YYYY-MM-DD hh:mm:ss","AvgTemp","LowFreqCoresTemp","HighFreqCoresTemp","LowFreqCoresFreq","HighFreqCoresFreq"' > $file_name
while true; do
avgtemp=$(cat /sys/rockchip_thermal/temp)
date_time=$(date +%Y-%m-%d:%H:%M:%S)
lfct=$(cat /sys/devices/virtual/thermal/thermal_zone0/temp)
hfct=$(cat /sys/devices/virtual/thermal/thermal_zone1/temp)
lfcf=$(cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq)
hfcf=$(cat /sys/devices/system/cpu/cpufreq/policy4/cpuinfo_cur_freq)

echo $avgtemp $date_time
avgtemp=${avgtemp#current cpu_temp:}
echo "\"${date_time}\",\"${avgtemp}\",\"${lfct}\",\"${hfct}\",\"${lfcf}\",\"${hfcf}\"" >> $file_name
sleep $sleep_time
done
 
 
14th May 2018, 07:52 PM |#22  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
Quote:
Originally Posted by surfer63

Maybe not for @gtxaspec, but for the others who would like to know.
I slightly touched on the PX5 cpu/cores in the review. The PX5 has 8 cores: 4 "low energy" cores and 4 "performance" cores, listening respectively to policy0 and policy4.
Standard frequency is 1.2GHz, the performance cores can go up to 1.51GHz. The cores of the PX5 are scaled up/down per set of 4 cores, the policy0 and policy4 set (whereas the Sofia 3GR cores where adapted per core).

So what I did:


From the stats (the last block), you can see that most time was spent in the 816 MHz and 1008 MHz frequency, and hardly any time in the highest frequencies. I think that this was due to throttling due to the overheating cpu.

Edit: I already have csv files containing

but for reading out the frequencies I need root access (like in the JET apk on Sofia). As I did not root my unit yet, I need to do that via adb.
I'm not going to take my laptop with me during a drive. Set the unit as hot-spot, connect over adb on the laptop and let a rooted shell run during the trip.

Currently I use a shell script for that, that measures every 10 seconds.:

Awesome information...I wonder what the temps are running 100% at 1.5 (and how great the system runs).... =D

Are you able to do a dump of all partitions except data and cache?

I'm going to ask @carter.w.jason to do the same and compare to see if there are any bootloader differences between 6 and 8...if they don't release an upgrade I may be able to...
14th May 2018, 09:52 PM |#23  
surfer63's Avatar
OP Senior Member
Flag Zwolle
Thanks Meter: 643
 
Donate to Me
More
Quote:
Originally Posted by gtxaspec

Awesome information...I wonder what the temps are running 100% at 1.5 (and how great the system runs).... =D

Are you able to do a dump of all partitions except data and cache?

I'm going to ask @carter.w.jason to do the same and compare to see if there are any bootloader differences between 6 and 8...if they don't release an upgrade I may be able to...

I already made dd partition images from boot, kernel, recovery and system to examine them. I'm uploading now. See here: https://drive.google.com/open?id=1Af..._HmS_ZjbIv0KF1
system.img.tgz might be uploaded at 23:15. It is now 22:48 (see posting time). It is (compressed) 744,4MB. boot, kernel and recovery are already uploaded.
Edit: System image upload went wrong. Now 23:00 here (see "last edited" time below post). Will take at least to 23:45. Otherwise wait till I let you know.

I will do the rest tomorrow

Below are the partitions on the Joying PX5 Android 8 (Joying PX5 6 might be the same, but otherwise the command below is possible info for @carter.w.jason)
Code:
 ls -l /dev/block/platform/ff0f0000.dwmmc/by-name/ > mapping_blocks2partitions.txt

total 0
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 backup -> /dev/block/mmcblk2p8
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 boot -> /dev/block/mmcblk2p6
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 cache -> /dev/block/mmcblk2p10
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 frp -> /dev/block/mmcblk2p15
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 kernel -> /dev/block/mmcblk2p5
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 logo -> /dev/block/mmcblk2p17
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 metadata -> /dev/block/mmcblk2p12
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 misc -> /dev/block/mmcblk2p3
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 oem -> /dev/block/mmcblk2p14
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 recovery -> /dev/block/mmcblk2p7
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 resource -> /dev/block/mmcblk2p4
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 security -> /dev/block/mmcblk2p9
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 sqloem -> /dev/block/mmcblk2p16
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 system -> /dev/block/mmcblk2p11
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 trust -> /dev/block/mmcblk2p2
lrwxrwxrwx 1 root root 20 2013-01-18 09:50 uboot -> /dev/block/mmcblk2p1
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 userdata -> /dev/block/mmcblk2p18
lrwxrwxrwx 1 root root 21 2013-01-18 09:50 vendor -> /dev/block/mmcblk2p13
The Following User Says Thank You to surfer63 For This Useful Post: [ View ] Gift surfer63 Ad-Free
15th May 2018, 04:41 AM |#24  
Senior Member
Thanks Meter: 21
 
More
Code:
lock/platform/ff0f0000.rksdmmc/by-name/                                       <
lrwxrwxrwx root     root              2013-01-21 02:50 backup -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-01-21 02:50 baseparamer -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2013-01-21 02:50 boot -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2013-01-21 02:50 cache -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2013-01-21 02:50 kernel -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-01-21 02:50 kpanic -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-01-21 02:50 logo -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2013-01-21 02:50 metadata -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2013-01-21 02:50 misc -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-01-21 02:50 radical_update -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2013-01-21 02:50 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-01-21 02:50 resource -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-01-21 02:50 sqloem -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2013-01-21 02:50 system -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-01-21 02:50 trust -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-01-21 02:50 uboot -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-01-21 02:50 userdata -> /dev/block/mmcblk0p17
root@px5:/ #
The Following User Says Thank You to carter.w.jason For This Useful Post: [ View ] Gift carter.w.jason Ad-Free
15th May 2018, 07:43 AM |#26  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
@surfer63 / @carter.w.jason,

does google assistant work on your units with 8 and 6.0.1 respectively? are ya'll able to test?
15th May 2018, 07:51 AM |#27  
surfer63's Avatar
OP Senior Member
Flag Zwolle
Thanks Meter: 643
 
Donate to Me
More
Quote:
Originally Posted by gtxaspec

@surfer63 / @carter.w.jason,

does google assistant work on your units with 8 and 6.0.1 respectively? are ya'll able to test?

No, it does not. Completely forgot to mention that in the review.
It constantly complains that it can't connect to the network.
15th May 2018, 07:52 AM |#28  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
Quote:
Originally Posted by surfer63

No, it does not. Completely forgot to mention that in the review.
It constantly complains that it can't connect to the network.


Ahh...ok that's different than the problem on Intel....hmm. probably due to outdated g apps.
15th May 2018, 10:20 AM |#29  
surfer63's Avatar
OP Senior Member
Flag Zwolle
Thanks Meter: 643
 
Donate to Me
More
With regard to the overheating:

I now have a unit with a DVD/CD-player. (The reason? My wife drives most kilometers in the car and she hates searching in the media-player. She simply wants to slide in an (mp3/flac) CD and afterwards push the eject button. I did not anticipate that for my previous unit, but I really want to keep my wife happy )
I opened the unit Yesterday evening and the DVD-player almost completely covers the total area, only leaving 5-6 millimeters on the sides and about 4-5 millimeter on the back. It is also thicker then I expected, which does not leave much room for heat dissipation from the standard sink, or for building in a heat-sink and fan.
I wanted to install a bigger slow-running fan on 12V, but there was simply no space for it, so I removed the 3x3cm 5V USB fan from my Sofia unit and installed that one, but still had great difficulties installing it, but finally succeeded. There was no room to place a heat-sink. Then I had to reinstall/build in the DVD-player again above the fan. I did not replace the cover.
Tomorrow I have to drive 1½ hours. Lets see what the temperature does.

Anyway, users without DVD/CD-player will have the same space as in the Sofia 3GR units. That should already give some more "ventilation" space for a standard, un-modded unit, and all the room for placing a heat-sink and fan.
15th May 2018, 02:37 PM |#30  
Senior Member
Hamburg, Germany
Thanks Meter: 13
 
More
Maybe you can convince Joying to release the source code for their apps next time. Seems the hardware is still OK (except for the fying pan), but the software just doesn't et any better:
- RDS doesn't work to spec
- The Wifi error (I have the same error you described on my Joying Sofie head unit)
- the Bluetooth idiosyncracies
- The awfull dialer
- The Google assistent
etc
etc
Just imagine what the experts here could do to fix all this, probably within a few days. The take the S/W to new levels.
15th May 2018, 03:05 PM |#31  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
Quote:
Originally Posted by tbd@immigrantsong.de

Maybe you can convince Joying to release the source code for their apps next time. Seems the hardware is still OK (except for the fying pan), but the software just doesn't et any better:
- RDS doesn't work to spec
- The Wifi error (I have the same error you described on my Joying Sofie head unit)
- the Bluetooth idiosyncracies
- The awfull dialer
- The Google assistent
etc
etc
Just imagine what the experts here could do to fix all this, probably within a few days. The take the S/W to new levels.

Joyojg doesn't even have the source, they are customers of the ODM manufafyurer, FYT. We should be able to get a custom ROM going soon.
The Following User Says Thank You to gtxaspec For This Useful Post: [ View ] Gift gtxaspec Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes