I was looking at the mt_cpufreq.c file in the leaked kernel source for the MTK 6589 SoC (the one running at 1.2 GHz), at https://github.com/varunchitre15/MT...atek/platform/mt6589/kernel/core/mt_cpufreq.c
I noticed there were frequency settings above 1209 MHz defined there. The highest one, DVFS_F0_0 goes above 1.7 GHz.
The code that seems to define the maximum frequency starts on line 1573 of that file. It relies on the returned value of PTP_get_ptp_level to define it. Since PTP_get_ptp_level is just a external header on that file, I needed to search the git repo to find its definition. Turns out it is in this file mt_ptp.c. Pay special attention to line 1018 and below: https://github.com/varunchitre15/MT...ek/platform/mt6589/kernel/core/mt_ptp.c#L1018
There's this interesting bit:
Code:
#if defined(MTK_FORCE_CPU_89T)
return 3; // 1.5GHz
#else
By returning 3, this function tells the frequency scaling driver that the CPU can go up to a 1.5 GHz clock.
I think I read the 6589T also has a higher GPU clock, and it can handle 2 GB of RAM with no problems. I'm not saying that the difference between the 6589 and the 6589T is just a kernel config, in fact, the chip most likely got a new revision. This source code leaked before there was any talk of a turbo revision of the 6589, so I think it's safe to assume that on newer code trees there may be fixes for the 2 GB of RAM and a higher GPU clock.
But I wonder, if the 6589 (not T) is able to go up to 1.5 GHz or even 1.7 GHz. It would be good if someone could compile that kernel with some modifications to make it think it will be running on a 6589T (adding a #define MTK_FORCE_CPU_89T should be enough) and see if it works fine. Since that source code came from a Acer model, maybe it would be easier to start tests on that device (because we can be sure the source is 100% compatible). I think it may run, but it may heat a lot or it may drive the voltage of the CPU up to a point where the phone's PCB is not prepared to deliver, causing damage (maybe the T revision chip fixes this).
have you done any more digging or testing on this?
Just noticed that Jiayu have released a MTK6589T version of the G3S for only $5 extra - could it be just a simple software unlock?
thanks
My guess is that it really is only a kernel setting considering that the Jiayu G3S comes with both chips within 2 weeks. Besides this is a really easy way for mediatek to sell a wide range of SoC's (just varying the voltages/clockspeeds). The main thing I wonder if this also controls the clockspeed of the GPU, since that clock is different as well, considering the MKT6589 and MKT6589T.
http://www.ini3e.com/thread-2610-1-1.html
This chinese article confirms that the only difference is clock speed.
It would be really good if someone who can already compile custom kernels for any MT6589 phone, could make that little modification and check the results - worst case scenario, the chip would get too hot and break forever... but since it seems to have a lot of temperature monitoring in place, I don't think that would happen.
I could do it myself, but I'm not going to download 8 GB of Android source, on my limited home connection, just to apply the MT6589 patches available on GitHub, which probably wouldn't work out-of-the-box since they are for a Acer phone and mine's a Zopo 910.
Bothering people at Zopo to do it is out of question, since they are interested in selling the Zopo C2 which comes with this "turbo" kernel config.
As for the GPU clock, on this kernel source there doesn't seem to be anything controlling that based on the MTK_FORCE_CPU_89T define. But this may be just because this is an old source tree - the one they have been distributing for their clients more recently, for the 6589T, may already have the changes for the GPU clock.
The ideal situation would be to have a kernel which can allow all the possible CPU and GPU frequencies, and these would be controlled and limited on the userspace.
It would be awesome ! Please devs, do something for us
is there anyone working on this
kartikoli said:
is there anyone working on this
Click to expand...
Click to collapse
I looked at it shortly, and noticed a lot of stuff is missing to compile it.
But why not look at it yourself?
Start by git cloning the cm10.1 tree and compile for a device that is supported, to get an idea of how it works.
People who manage to compile the source, please post, because from there we can come close to building CM10.1.
The sources on that Github are meant to be merged with the JB source tree, you're aware of that when you say it's missing things, right?
Here are sources for another MTK 6589 device:
http://forum.xda-developers.com/showpost.php?p=43650399&postcount=10
gbl08ma said:
The sources on that Github are meant to be merged with the JB source tree, you're aware of that when you say it's missing things, right?
Here are sources for another MTK 6589 device:
http://forum.xda-developers.com/showpost.php?p=43650399&postcount=10
Click to expand...
Click to collapse
this group is working on a Cyanogenmod for mtk6589 devices...http://forum.xda-developers.com/showthread.php?p=41345830
http://wikogeek.com/ (Select CINK 5) complete kernel source (800 Mb compressed) with build scripts.
gowtham121 said:
http://wikogeek.com/ (Select CINK 5) complete kernel source (800 Mb compressed) with build scripts.
Click to expand...
Click to collapse
The Cink Five is a French MTK 6589 (not T) phone. Specs identical to my ZP910 except for the screen (higher resolution). Also, on Wiko Mobile's website they claim it supports USB OTG, which would be interesting to implement on other MTK phones.
Now downloading the sources (let's hope the connection doesn't fail, and that I don't spend all of the quota for this month... sigh).
EDIT:
I am now compiling this kernel tree, which is the most complete I've ever seen. Funny thing, this one doesn't have the 89T part I mentioned on the OP.
Ideas from http://forum.xda-developers.com/showpost.php?p=43861751&postcount=64 are proving to be useful when compiling this 6589 kernel (mainly the kalOidComplete errors thing).
Of course I'll never be able to get this kernel to boot on my Zopo, as I'd have to guess all of the kernel config including things like GPIOs... but getting a binary will at least be fun.
And in case you never looked into a Mediatek code tree, this thing is a horrible mess (something common to most OEMs and SoC manufacturers, anyway). And this is just the kernel... I don't even imagine how it would be if it also had the preloader, lk, etc. sources...
BTW, I just got a "**** Successfully built kernel ****" message, but then it says "Cannot open file /arch/arm/boot/zImage". Will have to investigate.
EDIT2: I managed to compile a kernel from the Cink Five source tree.
Interesting aspects:
This kernel source is more incomplete when it comes to CPU freq scaling than the one from the Acer Liquid E2 available on Github (and which is missing many of the scripts needed for compilation). For example, it doesn't know of any speeds above 1209 MHz. The source tree on GitHub is effectively more recent.
This kind of saddens me. It means that at some point, Mediatek wrote the code thinking the CPU wouldn't go over 1.2 GHz. Then they may have added the 89T-specific code later, only when they developed a physically different die that effectively allows for higher clocks. And so 6589 and 6589T may have more differences than just a kernel config.
You can see that new DVFS configurations were added to the source code at some point.
From mt_cpufreq.c @ Cink Five source tree (presumably before):
Code:
#define DVFS_F1 (1209000) // KHz
#define DVFS_F2 ( 988000) // KHz
#define DVFS_F3 ( 754000) // KHz
#define DVFS_F4 ( 497250) // KHz
#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV
#define DVFS_V4 ( 950) // mV
From mt_cpufreq.c @ Acer Liquid E2 source tree (presumably after):
Code:
#define DVFS_F0_0 (1703000) // KHz
#define DVFS_F0_1 (1599000) // KHz
#define DVFS_F0_2 (1508000) // KHz
#define DVFS_F0_3 (1404000) // KHz
#define DVFS_F0_4 (1300000) // KHz
#define DVFS_F1 (1209000) // KHz
#define DVFS_F2 ( 988000) // KHz
#define DVFS_F3 ( 754000) // KHz
#define DVFS_F4 ( 497250) // KHz
#define DVFS_V0 (1250) // mV
#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV
#define DVFS_V4 ( 950) // mV
This is just a very small part of the differences between the two code trees.
But even if the 6589 can't overclock, the 6589T apparently support a speed of 1.7 GHz (DVFS_F0_0)... unless they added that just for testing purposes.
All we now need is someone with a Cink Five to join this forum...Hopefully someone will be willing to test your kernel..
Anyone out there with a Cink Five???
Apparently the Cink Five is targeted at the French market, so probably one will have better luck asking in a French Android forum.
Any French speakers here?
Hi I'm a Wiko cink five user from France. I can give a try but I need stability. If you think it's stable enough, no problem, I can test it.
Thank you for your work !
frans0023 said:
Hi I'm a Wiko cink five user from France. I can give a try but I need stability. If you think it's stable enough, no problem, I can test it.
Thank you for your work !
Click to expand...
Click to collapse
To be honest, I think it wouldn't even boot, let alone be stable...
But if you can make a backup of the existing boot.img, then flash my one, and don't mind spending a hour or so without the phone, you could revert to the original boot.img if mine didn't work.
I don't know if Wiko released any updates for the Cink Five or if you have one installed, but that would make it easier to get the current boot.img for backup.
gbl08ma said:
To be honest, I think it wouldn't even boot, let alone be stable...
But if you can make a backup of the existing boot.img, then flash my one, and don't mind spending a hour or so without the phone, you could revert to the original boot.img if mine didn't work.
I don't know if Wiko released any updates for the Cink Five or if you have one installed, but that would make it easier to get the current boot.img for backup.
Click to expand...
Click to collapse
No problem for me, send me the file and I will give a try. Just tell me what I have to check, maybe you want the logcat ?
Only boot.img is written when you flash a kernel ?
If it's only that, I could boot on recovery (twrp) and backup the file with "adb pull", then push yours ?
I have to sleep, good night
Envoyé depuis mon CINK FIVE avec Tapatalk
Actually, boot.img is the name of the file on the computer, to be updated with SP Flash tools. I don't know if Wink ever released an update to be flashed this way (but since you have TWRP, probably you have used it).
On the phone (or with recovery), I know a kernel can be flashed with a update.zip.
Right now I don't even know how to create a boot.img file, I only have the zImage. I'm trying to get a way to repack my boot.img so that I can try it on my Zopo...
And then I'll have to solve the problem of the kernel modules (these may be harder to restore since they are in the system partition I think)...
Also:
Is it just me, or the Cink Five is the same as the Fly IQ451? Turns out the zImage I compiled was with the config for the s9201b board, which is the IQ451.
From the pictures of the case, it seems to be the same... but, with Chinese phones, the case means little.
The source tree came configured to use the tinno89_jb config but I changed it because I couldn't compile with it.
Aw yeah, you atleast tried to compile the kernel Let's hope the CINK Five guy can test your kernel (P.S: A engineering build please, so that I can access Thermal settings in MTK Tools)
gowtham121 said:
Aw yeah, you atleast tried to compile the kernel Let's hope the CINK Five guy can test your kernel (P.S: A engineering build please, so that I can access Thermal settings in MTK Tools)
Click to expand...
Click to collapse
I think you guys still haven't understood very well that my kernel most likely won't even get to the Android boot logo (I bet it will stop in the early kernel boot stages with some kernel panic).
Furthermore I need a boot.img for the Cink Five so I can put my zImage in there. Otherwise it will never be compatible.
Also, I think the build type is set on the Android building process. I can only build a kernel. I don't have a good enough internet connection to download the Android source, and my computer with 8 GB of RAM lacks the necessary 16 GB (!!!) for compiling.
hello, I'm French but I use a translator so excuse me errors in grammar or spelling.
I have a phone that is: Nura 2 (orange)
Here the data (links to photos). I wish rooter my laptop, I tried Kingroot, root Genius, One Click One, be it PC or APK.
I am addressing you because you are in my opinion professionals Android.
Thank you for your help, I am open to offers.
I can't post after 10 posts so i was copy :
GENERAL INFORMATION
MANUFACTURER
Orange
MODEL
Nura 2
SOFTWARE INFORMATION
ANDROID VERSION NAME
LOLLIPOP
ANDROID VERSION CODE
5.0.2
ID
LRX22G
BUILD NUMBER
LRX22G release-keys
Seth33320 said:
hello, I'm French but I use a translator so excuse me errors in grammar or spelling.
I have a phone that is: Nura 2 (orange)
Here the data (links to photos). I wish rooter my laptop, I tried Kingroot, root Genius, One Click One, be it PC or APK.
I am addressing you because you are in my opinion professionals Android.
Thank you for your help, I am open to offers.
I can't post after 10 posts so i was copy :
GENERAL INFORMATION
MANUFACTURER
Orange
MODEL
Nura 2
PRODUCT
Nura_2
HARDWARE INFORMATION
BOARD
msm8916
HARDWARE
qcom
CPU_ABI
arm64-v8a
CPU_ABI2
ADVANCED CPU INFO
abi: arm64-v8a
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5
processor : 6
processor : 7
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Qualcomm Technologies, Inc MSM8939
STORAGE
External storage : 2,899MB / 11,301MB
OTHER INFO
Finger print : orange/Nura_2/m823_orange:5.0.2/LRX22G/v3CA4-0:user/release-keys
Host : 50492-2600
Tags : release-keys
SOFTWARE INFORMATION
ANDROID VERSION NAME
LOLLIPOP
ANDROID VERSION CODE
5.0.2
API LEVEL
21
BOOTLOADER
L3CA4040BU00
ID
LRX22G
BUILD NUMBER
LRX22G release-keys
NO OF INSTALLED APPS
242
Click to expand...
Click to collapse
Greetings,
Thanks for using XDA Assist. First, do not ever provide your IMEI in open forum or to any untrusted individual. That is very sensitive information. I have removed it from your post.
Regarding your question, please ask that here:
Android Q&A, Help & Troubleshooting
You'll receive expert advice there. Good luck!
Thanks
The_Merovingian said:
Greetings,
Thanks for using XDA Assist. First, do not ever provide your IMEI in open forum or to any untrusted individual. That is very sensitive information. I have removed it from your post.
Regarding your question, please ask that here:
Android Q&A, Help & Troubleshooting
You'll receive expert advice there. Good luck!
Click to expand...
Click to collapse
thank you for responding and letting me know that was IMEI sensitive information. I did not know. Although I have not received any proposal root, I am satisfied with this site and customer service. Happy new year (with a little bit late ^^)
I want to compile android for a new device with that setup:
Code:
PLATFORM
OS Android 7.0 (Nougat)
Chipset Qualcomm MSM8940 Snapdragon 435
CPU Octa-core 1.4 GHz Cortex-A53
GPU Adreno 505
What compiler / env vars I should use?
Do I have emulator that I can config for that setup?
Thanks.
roman.mandeleil said:
I want to compile android for a new device with that setup:
Code:
PLATFORM
OSAndroid 7.0 (Nougat)
ChipsetQualcomm MSM8940 Snapdragon 435
CPUOcta-core 1.4 GHz Cortex-A53
GPUAdreno 505
What compiler / env vars I should use?
Do I have emulator that I can config for that setup?
Thanks.
Click to expand...
Click to collapse
https://source.android.com/source/initializing
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
https://source.android.com/source/initializing
Click to expand...
Click to collapse
Thanks for the reply. I know that page but cant find there
the concrete differences in conifgs between different
chipset?
roman.mandeleil said:
Thanks for the reply. I know that page but cant find there
the concrete differences in conifgs between different
chipset?
Click to expand...
Click to collapse
What do you mean "configs between different chipset"? Setting up the environment is a universal thing, the differences should come when you sync repo to download your device's source code. Sync the correct source and you're ready to go, as far as I know.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hey im looking for help here i have a project and need help because im stuck. And this community is the best. So here goes.....
The project is this:
I want to install kali linux (preferably net hunter) on this tablet that i got from a friend who just got out of prison and had zero use for it i know this tablet sucks more than a hoover but i cannot bring myself to toss out good working devices so i want to put this to use for penetration testing and improving my android to android otg/adb/flashing/rooting skill set. It's not often you get a burner to play with lol....and who can beat free?
Now i've used linux deploy but no matter what version of linux i deploy/install (debian fedora kali ubuntu) I seem to always get the same results........ FATAL kernel to old.......so ive turned to the experts for help because i'm not familiar with installing linux ( windows user) so i wanted to take this opportunity to get into the linux world.......so some info about the system i'm currently running.....
First this tablet is fully rooted with the exception of the bootloader i have not been able to get the bootloader unlocked so i still have a stock recovery....and it blows id much rather have twrp..
Second here is the systems info and I hope someone can guide me to a rootFS that i can install using linux deploy or any other way i can run linux ontop of android that will actually start I have both vnc viewer and No Machine installed but because i cannot get linux to fully install I cannot use them lol......
So anyways any help would be greatly appriciated and THANKS A MILLION IN ADVANCE EVERYONE!!!!
********************************System ********************************
Android 4.2.2 / Jelly Bean MR1 / API 17
Baseband Version:
Build Number: JP5JDQ48.worker.20171109.075727
Build Fingerprint: JPay/jp5s/jp5s:4.2.2/JP5JDQ48/worker.20171109.075727:user/release-keys
Linux Kernel Version: 3.0.36+
Http User Agent: Dalvik/1.6.0 (Linux; U; Android 4.2.2; JP5s Inmate Media Device Build/JP5JDQ48)
********************************HARDWARE ********************************
Model: JP5s Inmate Media Device
Manufacturer: JPay Inc.
Board: jp5s
Device: jp5s
Product: jp5s
CPU Cores: 4
CPU Bit: 32-Bit
CPU Model: RK30board
Memory: Total 1.0 GB, Avail 457.62 MB
Storage: Total 27.34 GB, Avail 8.53 GB
Resolution: 1024 * 600 px / 160 dp
Screen Size: 5.8" * 3.6" / 6.8 Inches
******************************** SCREEN ********************************
Density: 160 dp / mdpi / 1.0x
Exact Density: 177.2093 * 168.89351 dp
Resolution: 1024 * 600 px
Available Resolution: 1024 * 552 px
Screen Size: 5.8" * 3.6" / 6.8 Inches
******************************** VIRTUAL MACHINE ********************************
Dalvik
VM Version: 1.6.0
Java Home: /system
Class Path: .
Boot Class Path: /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/tigerclient.jar
******************************** CPU ********************************
ABIs: armeabi-v7a, armeabi
CPU Cores: 4
CPU Bit: 32-Bit
CPU Model: RK30board
I'm sorry but I had to close this thread and to remove related posts. With reference to rule no. 9 of the XDA Forum Rules we do not allow discussions about jailbreaking or unlocking of Jpay tablets.
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
Regards
Oswald Boelcke
Senior Moderator