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, 04:32 AM |#11  
Senior Member
Thanks Meter: 21
 
More
Quote:
Originally Posted by gtxaspec

You have the fyt model right?

Correct
 
 
14th May 2018, 04:32 AM |#12  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
Quote:
Originally Posted by carter.w.jason

Correct

Are you able to get us some pictures of the internals?
14th May 2018, 04:50 AM |#13  
Senior Member
Thanks Meter: 21
 
More
@gtxaspec
Attached Thumbnails
Click image for larger version

Name:	IMG_0011.jpg
Views:	370
Size:	273.4 KB
ID:	4500628   Click image for larger version

Name:	IMG_0012.jpg
Views:	378
Size:	269.4 KB
ID:	4500629   Click image for larger version

Name:	IMG_0013.jpg
Views:	380
Size:	274.2 KB
ID:	4500630  
The Following User Says Thank You to carter.w.jason For This Useful Post: [ View ] Gift carter.w.jason Ad-Free
14th May 2018, 05:51 AM |#14  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
Nice looks like a drop in replacement for the 6021...

---------- Post added at 05:51 AM ---------- Previous post was at 05:14 AM ----------

Quote:
Originally Posted by carter.w.jason

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.


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.
14th May 2018, 06:35 AM |#15  
Senior Member
Thanks Meter: 21
 
More
Quote:
Originally Posted by gtxaspec

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.

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.
The Following User Says Thank You to carter.w.jason For This Useful Post: [ View ] Gift carter.w.jason Ad-Free
14th May 2018, 08:34 AM |#16  
surfer63's Avatar
OP Senior Member
Flag Zwolle
Thanks Meter: 643
 
Donate to Me
More
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.
14th May 2018, 08:37 AM |#17  
gtxaspec's Avatar
Senior Member
Thanks Meter: 484
 
Donate to Me
More
Quote:
Originally Posted by surfer63

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.

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.
14th May 2018, 08:42 AM |#18  
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?

Overlooked this one. Will check tonight. It is variable from 216 MHz to 1.51GHz, but I will look at the specifics tonight.
The Following User Says Thank You to surfer63 For This Useful Post: [ View ] Gift surfer63 Ad-Free
14th May 2018, 02:42 PM |#19  
Member
Flag Munich
Thanks Meter: 3
 
More
Quote:
Originally Posted by surfer63

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.

I have this bug on the 7.0 Android as well - this annoys the **** out of me!
14th May 2018, 03:41 PM |#20  
surfer63's Avatar
OP Senior Member
Flag Zwolle
Thanks Meter: 643
 
Donate to Me
More
Quote:
Originally Posted by Zeze21

I have this bug on the 7.0 Android as well - this annoys the **** out of me!

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).
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
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