Yes, I used search but I didn't find any thread concerning those numbers in su permissions. Can somebody explain how to understand those? I usually see e.g. 777, 775, 666 without knowing what they mean
It's easy, you have 3 numbers every number correspond to an user
You have in this order owner, group, all.
Exemple:
if the permission is 765:
Owner = 7
7 in dec = 111 in binary
rwx
111
the file is readable, writable and executable by the owner
Group = 6
6 in dec = 110 in binary
rwx
110
the file is readable, writable and not executable by the group (owning the file)
all = 5
5 in dec = 101 in binary
rwx
101
the file is readable, not writable and executable by all
bensabin said:
It's easy, you have 3 numbers every number correspond to an user
You have in this order owner, group, all.
Exemple:
if the permission is 765:
Owner = 7
7 in dec = 111 in binary
rwx
111
the file is readable, writable and executable by the owner
Group = 6
6 in dec = 110 in binary
rwx
110
the file is readable, writable and not executable by the group (owning the file)
all = 5
5 in dec = 101 in binary
rwx
101
the file is readable, not writable and executable by all
Click to expand...
Click to collapse
binary??? How do I turn dec to binary and vice versa?
bensabin said:
It's easy, you have 3 numbers every number correspond to an user
You have in this order owner, group, all.
Exemple:
if the permission is 765:
Owner = 7
7 in dec = 111 in binary
rwx
111
the file is readable, writable and executable by the owner
Group = 6
6 in dec = 110 in binary
rwx
110
the file is readable, writable and not executable by the group (owning the file)
all = 5
5 in dec = 101 in binary
rwx
101
the file is readable, not writable and executable by all
Click to expand...
Click to collapse
Oh I got it
Thnx
Well in fact, to be precise it's Octal and not decimal, but the explanation is the same.
For those interested, Amazon FireTV JTAG pinout is very close to the standard 20-pin ARM JTAG. See atached image for the actual pinout. If anybody has an OpenOCD config file for QUalcomm Krait 300 (SnapDragon 600), please share. Rooting can be done by bypassing a couple of checks in the bootloader.
Huh. Question. Is it snapdragon 600 you want or S4 pro. I dug pretty deeply before I got the box to figure exactly what processor is in there. Amazon gives: snapdragon 8064, krait 300, 1.7 GHz with adreno 320. I couldn't actually find a direct match for those specs in Qualcomm info, but the only thing that matched those specifications was the S4 pro, the same thing in the Nexus 7. Not to derail what you started, just want to be sure you're seeking the correct thing.
from my N5
Edit: let me clarify a bit. Amazon says it's the 8064. I went to qualcomm's site and that wasn't listed anywhere. So through deductive reasoning: CPU speed and the adreno 320 match the S4 pro which is also in the N7 2013. I haven't actually looked what xda says it has, but that's how I came to the S4 pro.
DroidIt! said:
Huh. Question. Is it snapdragon 600 you want or S4 pro. I dug pretty deeply before I got the box to figure exactly what processor is in there. Amazon gives: snapdragon 8064, krait 300, 1.7 GHz with adreno 320. I couldn't actually find a direct match for those specs in Qualcomm info, but the only thing that matched those specifications was the S4 pro, the same thing in the Nexus 7. Not to derail what you started, just want to be sure you're seeking the correct thing.
from my N5
Edit: let me clarify a bit. Amazon says it's the 8064. I went to qualcomm's site and that wasn't listed anywhere. So through deductive reasoning: CPU speed and the adreno 320 match the S4 pro which is also in the N7 2013. I haven't actually looked what xda says it has, but that's how I came to the S4 pro.
Click to expand...
Click to collapse
Being curious, I did some reading. I'm pretty sure it's a S4 Pro as well. 600 uses LPDDR3, has higher clock speed 1.7 vs 1.9GHz, and has wireless AC.
http://forum.xda-developers.com/nexus-4/help/snapdragon-600-vs-snapdragon-s4-pro-t2157201
http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
Luxferro said:
Being curious, I did some reading. I'm pretty sure it's a S4 Pro as well. 600 uses LPDDR3, has higher clock speed 1.7 vs 1.9GHz, and has wireless AC.
http://forum.xda-developers.com/nexus-4/help/snapdragon-600-vs-snapdragon-s4-pro-t2157201
http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
Click to expand...
Click to collapse
Yeah they didn't match up to me. I see xda just says 1.7 ghz, etc and not the 600. I'm thinking S4 Pro too. Good to get a confirmation though. :good:
DroidIt! said:
Yeah they didn't match up to me. I see xda just says 1.7 ghz, etc and not the 600. I'm thinking S4 Pro too. Good to get a confirmation though. :good:
Click to expand...
Click to collapse
The 600 was mentioned in some specs on the web, but it may have been a guess.
Actual JTAG device IDs:
4BA00477 (dap)
2071E0E1(cpu) <- googling this one yields nothing
Luxferro said:
Being curious, I did some reading. I'm pretty sure it's a S4 Pro as well. 600 uses LPDDR3, has higher clock speed 1.7 vs 1.9GHz, and has wireless AC.
http://forum.xda-developers.com/nexus-4/help/snapdragon-600-vs-snapdragon-s4-pro-t2157201
http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
Click to expand...
Click to collapse
the original apq8064 was dubbed the 'S4 Pro' (before the new naming scheme kicked in). Later variants (apq8064t, apq8064ab, etc) are dubbed 'snapdragon 600'. The newer variants have newer krait and newer revision of a320 (gpu), clock bumps, etc.. but basically tweaks of the original.
Determined said:
For those interested, Amazon FireTV JTAG pinout is very close to the standard 20-pin ARM JTAG. See atached image for the actual pinout. If anybody has an OpenOCD config file for QUalcomm Krait 300 (SnapDragon 600), please share. Rooting can be done by bypassing a couple of checks in the bootloader.
Click to expand...
Click to collapse
I've got a third FireTV hooked up to my riffbox now, but having issues. If I can get a successful read and write, I'll post a dump with a hacked bootloader to run unsigned images.
Issue I'm as is im not getting any response from RTCK. Fuses indicate that jtag was not disabled, and this isnt my strong point.
jcase said:
If I can get a successful read and write, I'll post a dump with a hacked bootloader to run unsigned images.
Click to expand...
Click to collapse
No need to pull that dump, it is provided in the OTA (emmc_appsboot.mbn). There is a procedure (located at 0x88F01144 in OTA 51.1.0.1) that checks unlock code, if you force it to return 1, you will be able to boot anything as well as run "oem unlock" and other restricted commands.
Determined said:
No need to pull that dump, it is provided in the OTA (emmc_appsboot.mbn). There is a procedure (located at 0x88F01144 in OTA 51.1.0.1) that checks unlock code, if you force it to return 1, you can boot anything as well as run "oem unlock" and other restricted commands.
Click to expand...
Click to collapse
Not what I was referring to, sorry for my bad wording.
I have already rooted and unlocked mine, but I an unable to release the root at this point (will shortly, waiting on Amazn not confirm a patch is done for the root exploit). I was trying to say I would release a riffbox flashable binary, with a bootloader hack allowing booting of custom images.
Booting unsigned recovery with modified res images:
I can't get a response over jtag, will put more effort into it this week.
emmc_appsboot.mbn itself can not be alternated, sbl3 validates it before continuing with boot.
jcase said:
emmc_appsboot.mbn itself can not be alternated, sbl3 validates it before continuing with boot.
Click to expand...
Click to collapse
Hah! If you step through it using a jtag and skip the checks it won't actually need any changes.
Determined said:
Hah! If you step through it using a jtag and skip the checks it won't actually need any changes.
Click to expand...
Click to collapse
Hah? Stepping through it is impractical for most uses. For the few of us that have one sitting on our desk? Sure ok, for those that have it in their entertainment center? Not practical at all.
If you are going to jtag it, might as well hack it proper once, and not worry about having to step through it each boot.
If you choose to jtag and step through it, have it return a value of being unlocked will result in androidboot.unlocked_kernel=true being passed to cmdline, and /sbin/adbd will not drop root when that exists. Would be a easy-ish root through jtag without actually flashing anything.
jcase said:
If you are going to jtag it, might as well hack it proper once, and not worry about having to step through it each boot.
Click to expand...
Click to collapse
That is your [much appreciated] thunder. I don't have time to generate public-friendly hacks anymore.
Determined said:
That is your [much appreciated] thunder. I don't have time to generate public-friendly hacks anymore.
Click to expand...
Click to collapse
Thunder is over, I'm done after I provide a few promised ones come Blackhat (including this one). Too much of time sink, and the public factor of the amusement has long gone.
If you have gtalk/hangouts give me a shout to the address in my signature.
There is also a serial debug port.
Are the pins known which is which?
{ParanoiA} said:
Are the pins known which is which?
Click to expand...
Click to collapse
I'll try and verify tomorrow
Sent from my HTC One_M8 using XDA Premium 4 mobile app
iNT0XiC8D said:
There is also a serial debug port.
Click to expand...
Click to collapse
Nothing to see there, just kernel messages:
Code:
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk: current version is lk_rel_3.0.1_02272014
[10] platform_init()
[10] target_init(): platform_id 109
[10] Its BUELLER. revision 3
[70] display_init(),target_id=7337.
[70] hdmi_msm_panel_init: default format=4
[2730] splash_screen_mmc :235, 67
[2750] Config HDMI PANEL.
[2750] Turn on HDMI PANEL.
[2760] EDID: no DTD or non-DTD data present
[2760] EDID: no DTD or non-DTD data present
[2760] hdmi_edid_get_audio_data: No adb found
[2770] hdmi_audio_playback: 48KHz not supported by TV
[2770] hdmi_msm_audio_acr_setup: video format 0 not supported
[2780] aboot_init: calling idme_initialize
[2780] Idme version is 2.0 and set related function to V2.0
[2790] IDME INFO: checking for new items to add (stored items:12 specified items:12)
[2790] serial num from idme: XXXXXXXXXXXXXXXXXX
[2800] Reboot -- restart_reason=427810811 (0x197fdffb)
[2800] aboot_init: IDME - device boot up info
[2810] idme items number:12
[2810] name: board_id, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2820] name: serial, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2830] name: mac_addr, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2830] name: bt_mac_addr, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2840] name: productid, size: 32, exportable: 1, permission: 292, data= 00000000000000000000000000000000
[2850] name: productid2, size: 32, exportable: 1, permission: 292, data= 00000000000000000000000000000000
[2860] name: bootmode, size: 4, exportable: 1, permission: 292, data= 1
[2860] name: postmode, size: 4, exportable: 1, permission: 292, data= 2
[2870] name: bootcount, size: 8, exportable: 1, permission: 292, data= 32
[2880] name: eth_mac_addr, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2890] bootcount = 33
[3080] aboot_init: Boot linux from MMC
[3090] boot_into_recovery=0 idme_bootmode=1 (NORMAL)
[3090] use_signed_kernel=1, is_unlocked=0, is_tampered=0.
[3100] Loading boot image (6344704): start
[3340] Loading boot image (6344704): done
[3340] Authenticating boot image (6344704): start
[3350] Attempting to enable ce3_src_clk before setting its rate.[3360] TZ channel swith returned 0
[5070] TZ channel swith returned 0
[5070] Authenticating boot image: done return value = 1
[5090] cmdline = 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2'
[5100] Power on reason 1
[5100] Its bueller again 3.
[5100] cmdline_length=170, n=172, n1=45
[5110] IDME: idme atag init (export to kernel), atag_size=514
[5110] name: board_id, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5120] name: serial, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5130] name: mac_addr, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5140] name: bt_mac_addr, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5140] name: productid, size: 32, exportable: 1, permission: 292, data: 00000000000000000000000000000000
[5150] name: productid2, size: 32, exportable: 1, permission: 292, data: 00000000000000000000000000000000
[5160] name: bootmode, size: 4, exportable: 1, permission: 292, data: 1
[5170] name: postmode, size: 4, exportable: 1, permission: 292, data: 2
[5180] name: bootcount, size: 8, exportable: 1, permission: 292, data: 33
[5180] name: eth_mac_addr, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5190] The atag idme items number:11
booting linux @ 0x80208000, ramdisk @ 0x82200000 (368957)
No JTAG Debug
Connecting to JTAG with OpenOCD needs a few changes in the cortex_a.c source to enable support for Cortex-A15. If you actually make those changes and play with debug registers, you will discover that DBGEN and SPIDEN signals/fuses are disabled, so debug mode is not accessible.
I have not yet tried flashing.
Determined said:
Connecting to JTAG with OpenOCD needs a few changes in the cortex_a.c source to enable support for Cortex-A15. If you actually make those changes and play with debug registers, you will discover that DBGEN and SPIDEN signals/fuses are disabled, so debug mode is not accessible.
I have not yet tried flashing.
Click to expand...
Click to collapse
ohh, openocd? I'm listening..
I have a number of snapdragon devices that I'd love to use jtag with.. but no windows machine for the riffbox sw.. openocd would be awesome
I spent a bit trying today, I never could get a response from RTCK at all
I'm trying to compile the kernel but either I'm doing something wrong or LG forgot to add a few files. So I contacted LG and they actually responded saying they'll contact the devs to see when they can distribute the fix. When that happens I'll compile it and see if I can add a few lower frequencies because 598mhz min is a battery hog and 200mhz min will probably be more battery-friendly. For now I've added lagfree because it's arguably the best governor and all the other ones that came with the kernel blob (like "balanced") I haven't played with adding I/O schedulers yet, but I will once LG write back. Don't expect much of this because this is my first kernel and I barely have any idea what I am doing other than copy-pasting into the right place because I understand file context and syntax.
Thumbs up, even if I don't use the H420.
Tomo123 said:
Thumbs up, even if I don't use the H420.
Click to expand...
Click to collapse
Don't worry, I'm sure the crazy Russians over at 4pda will unlock the bootloader :good:
TheFagulousFag said:
Don't worry, I'm sure the crazy Russians over at 4pda will unlock the bootloader :good:
Click to expand...
Click to collapse
If you are talking about H420's bootloader, it's already been unlocked. As for the H440N, the guy who unlocked the H420's bootloader says that H440N should use a method similar to Bump. He says aboot can't be patched, sth like that.
Fobos531 said:
If you are talking about H420's bootloader, it's already been unlocked. As for the H440N, the guy who unlocked the H420's bootloader says that H440N should use a method similar to Bump. He says aboot can't be patched, sth like that.
Click to expand...
Click to collapse
If it uses bump can't you use openbump, or did lg patch that?
TheFagulousFag said:
If it uses bump can't you use openbump, or did lg patch that?
Click to expand...
Click to collapse
I don't know, I haven't tried it yet. I'll give it a try and report.
---------- Post added at 05:33 PM ---------- Previous post was at 05:16 PM ----------
Fobos531 said:
I don't know, I haven't tried it yet. I'll give it a try and report.
Click to expand...
Click to collapse
Before I do anything, can I do this?
dump aboot partition ---> use open bump on aboot.img --> trasnfer it back on the device and see if it works. Do I risk my device getting bricked or what? I also saw an abootbak partition.
Well, it would make sense to ask the original Bump dev about the possibility for porting this to H440N. Just send him the aboot.
Fobos531 said:
I don't know, I haven't tried it yet. I'll give it a try and report.
---------- Post added at 05:33 PM ---------- Previous post was at 05:16 PM ----------
Before I do anything, can I do this?
dump aboot partition ---> use open bump on aboot.img --> trasnfer it back on the device and see if it works. Do I risk my device getting bricked or what? I also saw an abootbak partition.
Click to expand...
Click to collapse
Try to bump the recovery instead, just don't forget to make a backup copy.
TheFagulousFag said:
Try to bump the recovery instead, just don't forget to make a backup copy.
Click to expand...
Click to collapse
Bump was tried on our device long ago, but it didnt work.
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
Tomo123 said:
Well, it would make sense to ask the original Bump dev about the possibility for porting this to H440N. Just send him the aboot.
Click to expand...
Click to collapse
Bump as a project is dead if Im right. It surely wont work, because LG made changes in LP bootloader in comparison to KitKat so Bump wont work. Take a thorough look at this thread: http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Btw. I have issues registrating on 4pda.ru so I cant yet ask the guy who patched the H420 bootloader why our cant be patched through IDA.
Serious issues.
LG sent me an email saying they fixed it and it was an error in the txt file. Following the instructions, I decided to make a fully untouched stock kernel to see if it would compile. When I run the last command which programs and packs the kernel "make zImage" it errors after literally 4 lines and stops. I decided to ignore errors and forced it. It still fails. I logged the command and sent it to LG. Hopefully they will fix this, I am now even more eager to compile this.
Can someone post all the list of cpu governors, cpu frequencies and default cpu settings for the H420? Maybe I can tweak those to some better values.
Tomo123 said:
Can someone post all the list of cpu governors, cpu frequencies and default cpu settings for the H420? Maybe I can tweak those to some better values.
Click to expand...
Click to collapse
Only hotplug is modiefiable. If you want I could give you the source files.
I would not mind taking a look at those.
Keep in mind it is C code. I'll send you a pm with the files zipped when I get home.
Overclock already defined?
Looking at mtk_cpufreq.c has some interesting stuff, like defined frequencies.
Code:
#define DVFS_F0_1 (1690000) // KHz
#define DVFS_F0_2 (1599000) // KHz
#define DVFS_F0_3 (1495000) // KHz
#define DVFS_F0_4 (1391000) // KHz
#define DVFS_F0 (1300000) // KHz
#define DVFS_F1 (1196000) // KHz
#define DVFS_F1_1 (1092000) // KHz
#define DVFS_F2 (1040000) // KHz
#define DVFS_F2_1 (1001000) // KHz
#define DVFS_F3 ( 747500) // KHz
#define DVFS_F4 ( 598000) // KHz
#if defined(HQA_LV_1_09V)
#define DVFS_V0 (1200) // mV
#define DVFS_V1 (1150) // mV
#define DVFS_V2 (1090) // mV
#define DVFS_V3 (1090) // mV
#elif defined(HQA_NV_1_15V)
#define DVFS_V0 (1260) // mV
#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV /*Not used */
#elif defined(HQA_HV_1_21V)
#define DVFS_V0 (1320) // mV
#define DVFS_V1 (1210) // mV
#define DVFS_V2 (1150) // mV /*Not used */
#define DVFS_V3 (1050) // mV /*Not used */
#else /* Normal case */
#define DVFS_V0 (1250) // mV
#define DVFS_V1 (1200) // mV
#ifdef CPUFREQ_SDIO_TRANSFER
#define DVFS_V2_0 (1185) // mV
#endif
#define DVFS_V2 (1150) // mV
#ifdef MT_DVFS_LOW_VOLTAGE_SUPPORT
#define DVFS_V3 (1050) // mV
#endif
#endif
Even though I'm a complete noob at kernel compiling, this seems easy enough for me to try and get it to work at 1.69ghz, which seems a bit overkill actually :laugh:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any modification that you will make from this subject is at your own risk neither I nor the forum we do for the partial or total damage of your equipment.
XDA:DevDB Information
GEFORCE QUALCOMM PROJECT, Tool/Utility for all devices (see above for details)
Contributors
kaiiori
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-11-11
Created 2017-11-11
Last Updated 2017-11-11
additional note
Some files, directories may not be available on your device according to it you will have to search oh add the required.
to work better it is necessary to have a PC for more convenience and to have installed some file editor in this case Notepad ++ oh whichever is your preference
Qualcomm snapdragon processor in 64-bit versions
Xperia device
big.LITTLE HMP (2 clusters)
Sowfware Android 5.x.x 6.x.x 7.x.x 8.x.x
installed busybox
to know if your processor is compatible with big.LITTLE and know the architecture I recommend you install the CPU-Z application I attached picture about the required information
It is required to make the copy of the following files that are in the following directory /system/etc respectively import them to your pc
It requires knowing the frequencies of each nucleus that your processor handles and you can do it this way with an android terminal and using the following command
Reference information
Code:
freq cpu0
400000 691200 806400 1017600 1190400 1305600 1382400 1401600
freq cpu4
400000 883200 940800 998400 1056000 1113600 1190400 1248000 1305600 1382400 1612800 1747200 1804800
freq gpu
266666667 300000000 366670000 432000000 480000000 550000000 600000000
now with notepad ++ open the file thermal-engine.conf and locate the next parameter
Note
There may only be one or more parameters like the ones I show them, they must all have the same configuration as the first one
Code:
[emmc_therm__0.DEFAULT]
[emmc_therm__1.DEFAULT]
[emmc_therm__2.DEFAULT]
[msm_therm.DEFAULT]
we find this or something similar
Code:
[emmc_therm__0.DEFAULT]
algo_type monitor
sensor case_therm
sampling 1000
[color=red]thresholds[/color] 48000 48700 49000 49800 50000 50500 50800 50900
[color=red]thresholds_clr[/color] 46000 48000 48700 49000 49800 50000 50500 50800
[color=red]actions[/color] cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam cluster0+cluster1+hotplug_4+hotplug_5+gpu+s_backlight+battery+s_cam
[color=red]action_info[/color] 1401600+1248000+0+0+600000000+255+0+0 1401600+1248000+0+0+600000000+202+0+0 1401600+1248000+0+0+600000000+202+2+0 1401600+1248000+0+0+600000000+162+2+0 1401600+883200+1+0+600000000+162+3+0 1401600+400000+1+1+600000000+162+3+0 1382400+400000+1+1+600000000+162+3+0 1382400+400000+1+1+600000000+130+3+0
We will have to modify the parameters that frame in red color and change them by the following parameters
increases the battery charge
Code:
thresholds 42500 43500 44400 45500 46800 48300 49000 50300 51100 52300 53900 55400 57400 58400 59400
thresholds_clr 41000 42500 43500 44400 45500 46800 48300 49000 50300 51100 52300 53900 55400 57400 58400
Reference table
for now we will focus on the following parameters
in the frequency of CPU 0 the maximum frequency of the core will always be used as shown in the table and in the last frequency use an intermediate frequency
Code:
1401600
1401600
1401600
1401600
1401600
1401600
1401600
1401600
1401600
1401600
1401600
1401600
1324800
in the frequency of CPU 4 the maximum frequency will always be used and in a descending way, the last minimum frequency is not always used
Code:
1804800
1747200
1612800
1382400
1305600
1305600
1248000
1190400
1056000
1056000
998400
940800
883200
400000
400000
400000
the maximum frequency will always be used in the GPU frequency, the last minimum frequency is not always used
Code:
600000000
600000000
600000000
600000000
600000000
600000000
600000000
600000000
600000000
600000000
600000000
300000000
300000000
300000000
300000000
300000000
FPS
Code:
672000 (68fps)
614400 (62fps)
364800 (37fps)
staying in this way
Code:
1401600+1804800+0+0+0+0+600000000+255+1+100000+0
1401600+1747200+0+0+0+0+600000000+255+1+100000+0
1401600+1612800+0+0+0+0+600000000+219+3+100000+0
1401600+1382400+0+0+0+1+600000000+171+3+100000+0
1401600+1305600+0+0+0+1+600000000+141+5+100000+0
1401600+1305600+0+0+1+1+600000000+115+7+003600+0
1401600+1248000+0+0+1+1+600000000+95+9+003600+0
1401600+1190400+0+0+1+1+600000000+95+10+003600+0
1401600+1056000+0+0+1+1+600000000+78+11+001800+0
1401600+1056000+0+1+1+1+600000000+46+13+001800+0
1401600+998400+0+1+1+1+600000000+46+13+001800+6
1401600+940800+1+1+1+1+300000000+46+13+001800+6
1324800+883200+1+1+1+1+300000000+46+13+001800+6
672000+400000+1+1+1+1+300000000+46+13+001800+6
614400+400000+1+1+1+1+300000000+36+14+001800+6
364800+400000+1+1+1+1+300000000+26+14+001800+6
for each frequency table you must match with actions I will give you an example
Code:
actions
cluster0+cluster1+hotplug_4+hotplug_5+hotplug_6+hotplug_7+gpu+s_backlight+battery+s_cam_ltb_tim+s_cam
action_info
1401600+1804800+0+0+0+0+600000000+255+1+100000+0
save changes
Optimization of frequencies and boost
Necessary files
init.sony.cpu_parameter.sh
init.sony.cpu_parameter_gov.sh
If you do not have any of these files you can add it in the init.qcom.post_boot.sh file as follows
Code:
# Override with SOMC tuning parameters for governor
/system/bin/sh /system/etc/init.sony.cpu_parameter_gov.sh
# Override with SOMC tuning parameters for scheduler and others
/system/bin/sh /system/etc/init.sony.cpu_parameter.sh
I have attached my settings that I currently have on my device and it is a reference guide for you
File init.sony.cpu_parameter.sh
Code:
# set cpu_boost parameters
echo "0:1305600 1:1305600 2:1382400 3:1382400 4:1401600 5:1401600" > /sys/module/cpu_boost/parameters/input_boost_freq
echo "40" > /sys/module/cpu_boost/parameters/boost_ms
echo "60" > /sys/module/cpu_boost/parameters/input_boost_ms
echo "1017600" > /sys/module/cpu_boost/parameters/sync_threshold
File init.sony.cpu_parameter_gov.sh
Code:
# set (super) packing parameters
echo 1017600 > /sys/devices/system/cpu/cpu0/sched_mostly_idle_freq
echo 40 > /sys/devices/system/cpu/cpu0/sched_mostly_idle_load
echo 1017600 > /sys/devices/system/cpu/cpu1/sched_mostly_idle_freq
echo 40 > /sys/devices/system/cpu/cpu1/sched_mostly_idle_load
echo 1017600 > /sys/devices/system/cpu/cpu2/sched_mostly_idle_freq
echo 40 > /sys/devices/system/cpu/cpu2/sched_mostly_idle_load
echo 1017600 > /sys/devices/system/cpu/cpu3/sched_mostly_idle_freq
echo 40 > /sys/devices/system/cpu/cpu3/sched_mostly_idle_load
echo 1056000 > /sys/devices/system/cpu/cpu4/sched_mostly_idle_freq
echo 40 > /sys/devices/system/cpu/cpu4/sched_mostly_idle_load
echo 1056000 > /sys/devices/system/cpu/cpu5/sched_mostly_idle_freq
echo 40 > /sys/devices/system/cpu/cpu5/sched_mostly_idle_load
save changes and transfer the files to your device and move them, apply permissions and restart and enjoy your games
1.- Do you think it could work if my android device is not 64bit?
R.- I do not know if it works or not to get rid of that doubt should do the tutorial and know if it works
2.- my device is different from the requirements I think it could work?
R.- you must apply the tutorial and thus clarify your doubt
3.- I have several thermal-engine.conf files as I know what file it is?
R.- the same configuration must be applied to all
4.- with this configuration can I play without lag?
R.- if you correctly apply the configuration you can play without any lag
5.- I have playstore system optimizing applications believe that some conflict is created when playing
R.- could cause lag
6.- I have optimizer packages in support init.d should I uninstall it?
R.- yes
7.- I have a custom ROM I think it could work its configuration on my device
R.- must prove and thus clarified his doubt
8.- I am a developer and I would like to share your configuration in my projects could I do it?
R.- Of course if you just add this link to this topic
reserved
reserved
Can you help me booster my fps to 60?
Snapdragon 630 Moto x4
Can you show us with video ?
can I apply this on snapdragon 212?