We got root on the one xL. So, my question is How about this over clocking going on here? So I finally rooted, got a ROM, flashed a kernel.. Then bought SETCPU and turned it up to 1.9ghz. This seemed to work right well, but then I discovered a tool from chainfire and found that it wasn't sticking. So I was told about and edited this thermald.conf file.
But I wanna know, what temp was it that caused this to occur, and what I have just changed?
I've overclocked 3 phones now (8125/fuze/inspire) but none were this nice (dual core for example.) and this one gets warm. But I cannot tell how warm? And now I've even changed something and don't even know what. And it was related to warm.
Tl;dr how hard is are you Pushin yer phone?
The change:
sampling 5000
[pa_therm0]
sampling 5000
thresholds 70 80 90
thresholds_clr 65 75 85
actions none none none
action_info 0 0 0
[tsens_tz_sensor0]
sampling 1000
thresholds 50 65 75 80 99 102 105
thresholds_clr 40 62 72 77 96 99 102
actions cpu cpu cpu cpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu+shutdown
action_info 1809000 1242000 1134000 918000 594000+255+0+0+0+200000000 384000+30+1+3+1+27000000 384000+30+1+3+1+27000000+5000
[tsens_tz_sensor1]
sampling 1000
thresholds 75
thresholds_clr 72
actions none
action_info 0
[tsens_tz_sensor2]
sampling 1000
thresholds 100
thresholds_clr 80
actions none
action_info 0
[tsens_tz_sensor3]
sampling 1000
thresholds 75 78 81 84 87 90
thresholds_clr 72 75 78 81 84 87
actions cpu cpu cpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu+shutdown
action_info 1242000 1134000 918000 594000+255+0+0+0+200000000 384000+30+1+3+1+27000000 384000+30+1+3+1+27000000+5000
[tsens_tz_sensor4]
sampling 1000
thresholds 50 65 80 86
thresholds_clr 40 62 77 84
actions gpu gpu gpu gpu
action_info 400000000 300000000 200000000 27000000
Please!
Move on to the One XL forum, please.
This is the forum for the One X with quadcore Tegra 3 CPU so we can't tell you which temperatures are ok for the dualcore S4 CPU in your device
Sent from my HTC One X using xda app-developers app
Related
OK, so I'm testing out custom auto brightness settings to share with everyone to help improve battery life, its definitely a wip and I need testers to help find the perfect balance of darkness vs being able to see the screen clearly
Auto brightness settings can be found in "settings>display>custom backlight settings>edit other levels" in many custom roms just make sure screen dim level is set to 1 and use custom is checked
OK, so far I have the following settings which seem OK though might be a little dark, please test and report back
Only change values in the "screen" column
5
7
10
13
17
20
24
25
30
40
50
60
65
70
85
95
115
135
165
255
(Last value is just to ensure max brightness in very strong light)
Good to see someone already started this thread. I have some settings I collected from xda and android forums that have been working well so far for my needs...
Window Length: 5 seconds
Reset Threshold: 400Lux
Sample Interval: 2sec
Screen Dim Level: 5
Allow Light Decrease : Yes
Lower Upper Screen
0 199 10
200 399 20
400 599 25
600 799 30
800 999 40
1000 1249 50
1250 1499 60
1500 1999 70
2000 2999 80
3000 3999 90
4000 5999 100
6000 9999 125
10000 ∞ 255
If anyone can tweak these and get better results by all means do share!
retareq said:
Good to see someone already started this thread. I have some settings I collected from xda and android forums that have been working well so far for my needs...
Window Length: 5 seconds
Reset Threshold: 400Lux
Sample Interval: 2sec
Screen Dim Level: 5
Allow Light Decrease : Yes
Lower Upper Screen
0 199 10
200 399 20
400 599 25
600 799 30
800 999 40
1000 1249 50
1250 1499 60
1500 1999 70
2000 2999 80
3000 3999 90
4000 5999 100
6000 9999 125
10000 ∞ 255
If anyone can tweak these and get better results by all means do share!
Click to expand...
Click to collapse
Hi, i just tried these values, and for me its way to dark. I think that the display of the galaxy looks realy bad, if the value is under 1/4 of max.
retareq said:
Good to see someone already started this thread. I have some settings I collected from xda and android forums that have been working well so far for my needs...
Window Length: 5 seconds
Reset Threshold: 400Lux
Sample Interval: 2sec
Screen Dim Level: 5
Allow Light Decrease : Yes
Lower Upper Screen
0 199 10
200 399 20
400 599 25
600 799 30
800 999 40
1000 1249 50
1250 1499 60
1500 1999 70
2000 2999 80
3000 3999 90
4000 5999 100
6000 9999 125
10000 ∞ 255
If anyone can tweak these and get better results by all means do share!
Click to expand...
Click to collapse
I think most slots should be raised by 5-10 for best visibility but I would suggest adding a slot or 2 at the beginning of it for best low light (mainly nighttime) settings
beama said:
Hi, i just tried these values, and for me its way to dark. I think that the display of the galaxy looks realy bad, if the value is under 1/4 of max.
Click to expand...
Click to collapse
Did you try my values? I think its a little easier to tweak some different light levels just to your liking, also the only thing that really doesn't look all that great are dark backgrounds on the home screen and launcher background but by raising some of the brightness levels by 5 or so at a time, its easily correctable... this is mainly to be a baseline guide since the stock values are wayyy to high in most cases
Fyi, before doing this I considered 2.5 hours on extended battery good, now I easily get 3+ even 4 hours on screen time with overclocking (1344 MHz) and interactive governor
I get 4 hours easy. I agree its a bit dark but I have no idea on what to modify because I don't really understand how its set up. To the guys who tried it already can you post your modified values that might be brighter ?
retareq said:
I get 4 hours easy. I agree its a bit dark but I have no idea on what to modify because I don't really understand how its set up. To the guys who tried it already can you post your modified values that might be brighter ?
Click to expand...
Click to collapse
Just try upping the values in the "screen" column by 5-10...even with increasing by 10 its still far lower than stock (stock setting has 50 as lowest value when even 15-25 should be plenty bright
To determine what level you are currently on look at the very top for filtered/raw values and see which level they fit between the first 2 columns (lower and upper)
Ok I tried metalspring way and this is what I have now :
Window Length: 10 seconds
Reset Threshold: 400Lux
Sample Interval: 10 seconds
Screen Dim Level: 10
Allow Light Decrease : Yes
Lower Upper Screen
0 199 20
200 399 25
400 599 35
600 799 45
800 999 55
1000 1249 65
1250 1499 75
1500 1999 85
2000 2999 95
3000 3999 105
4000 5999 115
6000 9999 125
10000 ∞ 255
Oh I also have the color calibrated from franco kernel app using the values suggested in app so I'm REALLY liking this now. No gradient banding or grain, looks sweeet.
updated: after todays field test I modified the values to allow for gradual dimming as much as possible. I will keep tweaking and posting results here.
Hi, how can I get gradual change like stock does? More values? Less? I hate the pop high/low u get with this
Sent from my Galaxy Nexus
does it happen to anyone else that changing the number of levels/steps for custom auto brightness from the stock 20 to anything less causes the screen go go MAX (255) brightness?
miguel.b said:
does it happen to anyone else that changing the number of levels/steps for custom auto brightness from the stock 20 to anything less causes the screen go go MAX (255) brightness?
Click to expand...
Click to collapse
Not to bring back this thread, but this is the exact issue that has shown up in CM10 ROMs and reported by quite a few users. If you use any number of levels other than 20, brightness is locked to 255 no matter what your thresholds or sensor is registering. Have you found any workaround or fix for this?
AuraspeeD said:
Not to bring back this thread, but this is the exact issue that has shown up in CM10 ROMs and reported by quite a few users. If you use any number of levels other than 20, brightness is locked to 255 no matter what your thresholds or sensor is registering. Have you found any workaround or fix for this?
Click to expand...
Click to collapse
I really thought I was the only one. I have NOT found a work around unfortunately. Rather, I've just stayed with the stock steps/levels all the while. the behaviour is still present, and I've not found any other resource or posts on the issue.
I have brought this up in another thread over at rootzwiki and others have chimed in. Perhaps I'll create a brand new thread to acknowledge it (as opposed to responding to relevant threads already created) since it doesn't appear to be getting traction in finding a solution.
Sent from my Galaxy Nexus using xda premium
Hi guys!
I got my SXS on 24 December and i try to play games (etc. Dead Space NFS Most Wanted) but my phone gets a bit hot (not very, but its a bit uncomfortable for my hands) but the bigger problem is: it drops the CPU clocks to 805 (?) MHz and its make games unplayable. All stock on my phone and I try to play nonpirate games. The worst is, sometimes the games pause automatically.
The phone do that too when I start playing. (So thats isn't hot and still lags, and pauses...)
Any suggestions?
only pauses, lags, and heats? man you are lucky..
my xperia ion is nowhere better. after 1st time playing dead space, it doesn't get hot or get lags. it simply rage quit and not letting me play every time i start the game.. all stock no pirate as well.
btw, xperia ion will be my last android phone, yes, no more android, but still other sony devices. i so hate the way android works, even though you can really enjoy the customization and apps integration, but seriously nothing else. i have lost all the faith on android and sony mobile. i don't wanna struggle just to get something i want to work. i want something reliable, and that's definitely not android.
asdf2222 said:
Hi guys!
I got my SXS on 24 December and i try to play games (etc. Dead Space NFS Most Wanted) but my phone gets a bit hot (not very, but its a bit uncomfortable for my hands) but the bigger problem is: it drops the CPU clocks to 805 (?) MHz and its make games unplayable. All stock on my phone and I try to play nonpirate games. The worst is, sometimes the games pause automatically.
The phone do that too when I start playing. (So thats isn't hot and still lags, and pauses...)
Any suggestions?
Click to expand...
Click to collapse
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Also, check you're on the latest firmware
Sent from my Jellybean Xperia S
Welcome to the forum. Please post all your questions here in Q&A in future.
Thanks
AvRS
Ben36 said:
Also, check you're on the latest firmware
Sent from my Jellybean Xperia S
Click to expand...
Click to collapse
Yeah im on the latest firmware, and i tried older firmwares too.
monivan said:
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Click to expand...
Click to collapse
May this will help, I changed this values i will test soon!
(sry for my english)
0000alex0000 said:
only pauses, lags, and heats? man you are lucky..
my xperia ion is nowhere better. after 1st time playing dead space, it doesn't get hot or get lags. it simply rage quit and not letting me play every time i start the game.. all stock no pirate as well.
Click to expand...
Click to collapse
I didnt had those problems on stock or by now. I play a lot on my Ion and everything runs great.
monivan said:
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Click to expand...
Click to collapse
I dont know but i changed the values and the game is auto pause... :S sry for my english :crying:
monivan said:
Go to system/etc and find thermal-send.conf
Edit with root explorer!
you'll see these lines:
[MSM_THERM]
sampling 10000
thresholds 49 52 55 58 70
thresholds_clr 45 50 53 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Change to:
[MSM_THERM]
sampling 10000
thresholds 49 52 65 58 70
thresholds_clr 45 50 63 56 68
actions lcd lcd cpu lcd shutdown
action_info 192 128 810000 64 0
Reboot your phone will no longer lag during heavy game! Before if u reach 53 degree u'll lose performance. Now It will not clocked down until 63 Degree.
Thank me, if I deserved it.
Send from my stupid lt26i
Click to expand...
Click to collapse
will this work on Samsung galaxy music duos ? iam facing the same problem-i mean Auto pausing of games and also force stop sometimes..if this dont work then please post some working method for the device if any..
I'm over clocked at 1.89ghz with about 29-30° C temperature. Clock varies from 384 mhz to max clock speed. What's a good temperature for it to be at with both general and gaming use? Last thing I want to do is overheat or something, but it doesn't seem to get hot at all.
Sent from my Nexus 7
The app I used gave false reading. Cpu temperature is in between 40-50° C. Idk what's too hot when it comes to these, but I know PCs get a lot hotter.
Sent from my Nexus 7
40-50 is pretty cool. I don't know how warm these newer devices usually run, but I used to see a lot higher temps than that on my single core Galaxy S. I believe the N7 has thermal throttling, if it gets to XX degrees it will scale back the CPU, and if it keeps heating up will shut down at a specific temperature to prevent damage.
Sent from my Nexus 5 using xda premium
95Z28 said:
believe the N7 has thermal throttling, if it gets to XX degrees it will scale back the CPU, and if it keeps heating up will shut down at a specific temperature to prevent damage.
Click to expand...
Click to collapse
Correct.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Just found it in trickster, once it reached 80° it will throttle down, and I'm a whiles off of that. Thanks.
Sent from my Nexus 7
[tsens_tz_sensor7]
sampling 1000
thresholds 70 90 95 100 105 110 115 120
thresholds_clr 67 85 90 95 100 105 110 115
actions cpu+battery cpu+battery cpu+battery cpu+battery cpu+battery cpu+battery cpu+battery shutdown
action_info 1512000+0 1188000+0 810000+1 648000+1 540000+2 487000+2 384000+3 5000
Hello everyone,
recently im having serious battery problems (random reboots with battery logo, 20-30% battery decrement).
Can someone attach a log made with CurrentWidget of a normal usage (normally 1 charge cycle from 100 to 20 for example)?
Basically i'm noticing that when the phone is absorbing significant amounts of current is becomes unstable
Example of a shutdown situation (need to charge in order to boot properly, green text)
Code:
Date Time mA % volt temp
08/11/2016 07:44:00 -63 78 3,588 23,7
[COLOR="Red"]08/11/2016 07:45:37 -1154 78 3,588 23,7[/COLOR]
08/11/2016 07:46:37 -43 78 3,588 23,7
[COLOR="Orange"]08/11/2016 07:47:39 -204 78 3,588 23,7[/COLOR]
08/11/2016 07:49:22 -166 78 3,588 23,7
08/11/2016 07:50:22 -172 78 3,588 23,7
0[COLOR="Red"]8/11/2016 07:51:55 -654 77 3,709 20,5[/COLOR]
[COLOR="SeaGreen"]08/11/2016 08:12:04 140 63 4,084 26,5[/COLOR]
08/11/2016 08:13:29 480 66 4,357 25,5
08/11/2016 08:14:29 444 67 4,355 25
Unusual drop in voltages (i'm assuming this happens since i waked up my phone after waking up myself)
Code:
Date Time mA % volt temp
08/11/2016 07:07:27 -51 83 4,062 16
[COLOR="red"]08/11/2016 07:08:28 -47 83 4,062 16
08/11/2016 07:09:28 -54 82 3,696 19[/COLOR]
08/11/2016 07:10:28 -47 82 3,696 19
Moreover when in TWRP 3.0.2 i can't see the battery value on top right corner! Can someone confirm he can?
Hi
I have been working on google pixel 2xl in my research and I wanna understand the contents of the thermal-engine.conf file (I mean what each subroutine written there is doing)
many phones start throttling when the temperature of the cores exceeds some threshold, although in google pixel 2xl and according to what I understood from thermal-engine.conf file
it is rather based on a sensor called bd_therm2 as shown in the first subroutine in the thermal-engine.conf file
"[SKIN-MID-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 38000
set_point_clr 37000
device_max_limit 1804800
time_constant 0"
but this is not the only subroutine there and there are others and I do not understand what each subroutine is doing
although based on my experiments when bd_therm2 sensor exceeds 38 throttling starts
I appreciate if somebody directs me to some reference that explains these contents
The file contents are as follows (sorry my first time on that forum and I did not know how to attach it)
[SKIN-MID-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 38000
set_point_clr 37000
device_max_limit 1804800
time_constant 0
[SKIN-MID-LOW-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 40000
set_point_clr 39000
device_max_limit 1497600
time_constant 0
[SKIN-LOW-FLOOR2]
algo_type ss
sampling 2000
sensor bd_therm2
device cluster1
set_point 45000
set_point_clr 44000
device_max_limit 1190400
time_constant 0
[HOT-SKIN-VIRTUAL2]
algo_type virtual
trip_sensor bd_therm2
sensors tsens_tz_sensor13 tsens_tz_sensor0
list_cnt 2
weights 1 -1
set_point 39000
set_point_clr 36000
sampling 1000
math 0
[VIRTUAL-SS-GPU-SKIN2]
algo_type ss
sensor HOT-SKIN-VIRTUAL2
device gpu
sampling 2000
set_point 7000
set_point_clr 2000
device_max_limit 414000000
[SKIN-MONITOR2]
algo_type monitor
sampling 2000
sensor bd_therm2
thresholds 48000 50000 52000
thresholds_clr 47000 49000 51000
actions cluster0+cluster1+gpu cluster0+cluster1+gpu cluster0+cluster1+gpu
action_info 1094400+1190400+414000000 883200+902400+342000000 300000+300000+257000000
[BATTERY-MONITOR2]
algo_type monitor
sampling 2000
sensor bd_therm2
thresholds 50000
thresholds_clr 48000
actions battery
action_info 3
[SKIN-SHUTDOWN2]
algo_type monitor
sampling 1000
sensor bd_therm2
thresholds 54000
thresholds_clr 53000
actions shutdown
action_info 1
[SKIN-MID-FLOOR]
algo_type ss
sampling 2000
sensor bd_therm
device cluster1
set_point 49000
set_point_clr 48000
device_max_limit 1804800
time_constant 0
[SKIN-LOW-FLOOR]
algo_type ss
sampling 2000
sensor bd_therm
device cluster1
set_point 51000
set_point_clr 50000
device_max_limit 1190400
time_constant 0
[HOT-SKIN-VIRTUAL]
algo_type virtual
trip_sensor bd_therm
sensors tsens_tz_sensor13 tsens_tz_sensor0
list_cnt 2
weights 1 -1
set_point 39000
set_point_clr 36000
sampling 1000
math 0
[VIRTUAL-SS-GPU-SKIN]
algo_type ss
sensor HOT-SKIN-VIRTUAL
device gpu
sampling 2000
set_point 7000
set_point_clr 2000
device_max_limit 414000000
[SKIN-MONITOR]
algo_type monitor
sampling 2000
sensor bd_therm
thresholds 58000 60000 64000
thresholds_clr 57000 59000 63000
actions cluster0+cluster1+gpu cluster0+cluster1+gpu cluster0+cluster1+gpu
action_info 1094400+1190400+414000000 883200+902400+342000000 300000+300000+257000000
[SKIN-SHUTDOWN]
algo_type monitor
sampling 1000
sensor bd_therm
thresholds 66000
thresholds_clr 65000
actions shutdown
action_info 1