Related
I was thinking about installing SetCPU but I have heard stories of it not working very well on the Captivate. Does anyone use this, and if so what kind of battery life improvement are you seeing? Post config settings too please!
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
kenjindomini said:
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
Click to expand...
Click to collapse
Thanks for these, I was looking for a some decent settings. Mine were close to that to start, but I had no idea what I was doing, haha
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
CPU throttles itself. Any effects of setCPU is placebo effect
Err if you set the clocks yourself, you can produce a difference depending on what it's catered towards. I'm sure if I set the max clock to 200 (assuming the app works) for all situations there will be a difference.
Does the stock ROM have a perflock like the EVO that we need to disable?
Also, does the stock ROM automatically underclock at times, or???
I've now verified after clearing user data, the stock firmware already sets the conservative governor and allows it the full range of frequencies supported by the CPU. Only benefit from SetCPU should be profiles - reduce max clock when hot or low battery, that sort of thing.
Sent from my Samsung Captivate
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Default Profile: 800 MHz
Profiles:
Temp > 46 C -- 400 Max 100 Min Conservative
Battery < 40 -- 400 Max 100 Min Conservative
Screen Off -- 400 Max 100 Min Conservative
This now gives my phone life of about 2 days with moderate use (1 hour calls, 1 hour browsing and another 30-45 mins of using apps that need screen on like games, etc)
brandonb81 said:
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Click to expand...
Click to collapse
One thing u got to keep in mind, CPU scales up when woken from low speeds (like when u set for 200 n this takes a second or two). After some R&D i realized 400 MHz when sleeping is optimal with hardly noticeable lag.
Unhelpful said:
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
Click to expand...
Click to collapse
well, i have tried playing heavy games like asphalt 5, dungeon hunter, assasin's creed... these all games seemed to work with no lag even at 400 MHz when my battery was less than 40. Most apps I have or used or saw were very comfortable even at 400 MHz. But with multiple apps open, sometimes there was lag, so i set the max at 800 MHz, instead of 1 GHz.
Also, I set my connection to EDGE from 3G. This helped reduce phone from getting heated up with long calls.
I tried using this app myself but uninstalled it after a week. While I'm sure there was some underlying cause, it made my phone never wake up from sleep mode when it turned off.
Honestly thou, I know several android phone owners with s lot of phones That didn't see any real change in their battery life as s result. And based on my experiences, I'd say stay away from it.
Just my 2 cents thou
Sent from my SAMSUNG-SGH-I897 using XDA App
It seems the CPU scaling is not set properly with the kernel that cause the phone runs warm and decrease battery life. Checked with CPU Spy and I noticed it often idles around 1134~1026MHz, instead of all the way down to 384MHz.
What you need:
1. Download any CPU control apps, like AnTuTu CPU Master, No-frills CPU Control, CPU Tuner...etc...
2. ROOT!
3. Set the minimum frequency to 384MHz. Leave all other parameters unchanged.
4. Check Apply on boot.
Now check with CPU Spy again you'll see your CPU idles at 384MHz and your phone is running cooler.
Yeah seems the kernel needs to be tweaked a little. It will most likely be patched by .1
Sent from my Nexus 7 using Tapatalk 2
the phone goes in standby, but the cpu stands over 1000Mhz instead of scaling at the bottom?
Mine already goes down to 384mhz without intervention of any CPU apps. At this very moment my CPU is at 1% and clocked at 384mhz.
I don't think doing this will have any effect on battery life or heat.
OverTheBelow said:
Mine already goes down to 384mhz without intervention of any CPU apps. At this very moment my CPU is at 1% and clocked at 384mhz.
I don't think doing this will have any effect on battery life or heat.
Click to expand...
Click to collapse
Mine aswell. Clocks down to 384 Mhz when doing nothing.
Thermal throttling is NOT supposed to throttle to minimum, its not a rollercoaster. It would lag terribly intermittently. Perhaps the threshold needs to be brought up, but the throttling clocks seems about right. Something else that could be done and help a lot is adjust the voltages.
Edit : sorry I misread your post.
OverTheBelow said:
Mine already goes down to 384mhz without intervention of any CPU apps. At this very moment my CPU is at 1% and clocked at 384mhz.
I don't think doing this will have any effect on battery life or heat.
Click to expand...
Click to collapse
Mine does go down to 384MHz. But my point is the CPU does not go down to 384MHz when it should be.
From CPU Spy it seems like when idling the CPU half time stays on 1134MHz and half time goes down to 384MHz.
After the tweaking the CPU goes down to 384MHz all the time, and does NOT affect smoothness or fluency of the system.
richteralan said:
Mine does go down to 384MHz. But my point is the CPU does not go down to 384MHz when it should be.
From CPU Spy it seems like when idling the CPU half time stays on 1134MHz and half time goes down to 384MHz.
After the tweaking the CPU goes down to 384MHz all the time, and does NOT affect smoothness or fluency of the system.
Click to expand...
Click to collapse
Mine oscillates between 1 and 1.5 Ghz while in use, and goes down to 384 when lightly used or when WifFi is on (Wifi prevents my phone from entering Deep Sleep). The rest of the time, it's in Deep Sleep.
384 is the minimum? Damn, I remember when 384 was the maximum.
Sent from my Nexus 7 using xda app-developers app
Hehe, time goes on and we need more power xD
Q&A for [KERNEL][D5803&D5833] AndroPlusKernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][D5803&D5833] AndroPlusKernel. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Very nice kernel, fast and smooth - great work and port.
Anyone knows if it's possible to use any third party kernel app to boost the headset volume?
Working
Hi this is my first post, infact I joined so I could report my findings.
I would just like to confirm so far that V5 working on my Z3C using the .93 firmware. I didn't need to wipe cache/dalvik/data partitions either.
For purposes of settings configuration, I'll be using TricksterMod
For stress testing purposes I'll be using Stability Test 2.7
Overclocking
Overclocking seems to work, I'll stress test and report back with the results.
I was wrong, it is unstable when overclocking and stress testing, with the phone force rebooting 1-5 seconds in to the stability test which loaded all 4 cores. Tried 2899Mhz and 2880Mhz (were both unstable and didn't try 2.72, 2.75, 2.57 either - I might try stability testing them.) Was completely stable at 2.47GHz, and it actually stuck there, no throttling in place! I stopped the stress test when the CPU temp was around 77-80C as my hand was getting burnt! The battery temp reached about 46C. It took 10 mins of stress testing for this to be reached. When the stock kernel was in place it would begin throttling after about 1-20 seconds under full load. First 2.2GHz, then 2 then 1.7 then 1.5 and eventually 1.25 after about 2-4mins.
I couldn't do a single core test though. I suspect as most games use single core or dual cores it wouldn't get overly hot.
My opinion is that fast clocked phones should be marketed with 2 speeds. The highest it'll reach under a boost mode (turbo for Intel's i5 and i7 series), and a slower speed that it'll average out at under thermal pressure. The Z3Cs would be turbo: 2.5GHz and normal: 1.5GHz.
Governors
These are quick tests I'm performing here to provide a quick look at responsiveness and potential unnecessary CPU jump ups.
Wheatley - most of the time it's hovering at top speed when approx CPU usage is 9%, it'll occasionally hunt down to 300Mhz but then right back up to 2899MHz. This one is speedy though. Governor tunables available.
Lagfree - idles at 300MHz - 960MHz then hunts up to 2.2-2.9Ghz when needed and turns on the second core. It seems to slow back down to idle. This one seems to have fast scrolling, sliding notifications pane quickly). No governor tunables.
SmartassV2 - idles at 300Mhz, speeds up to 422-960 on core 0, and turns on core 1 at 1.2-1.5GHz for a few seconds under fast scrolling and notification pane opening. Seems quite responsive. Probably good for battery life hopefully with the responsiveness of Interactive. No governor tunables.
Lionheart - Idles at 960 MHz for a few seconds then slows down to 300MHz with the odd increase to 729MHz. Core 0 and Core 1 reaches 1.26GHz under scrolling, notification pane opening. As fast as the others. Governor tunables available.
Hotplugging
Intelliplug appears to work better than MP-Decision - now only one core is on during idle, instead of 2.
MP-Decision was disabled to avoid conflicts.
Undervolting
I've only undervolted 300MHz to 675MHz from 775MHz as of writing this post.
Tried quickly undervolting in trickstermod by setting them all about -75mV, stability tested it, appears stable. I'll tweak the voltages a bit better when I do a scaling stability test.
Issues I've experienced
Sound Control is the only thing so far that causes a reboot. However music still plays over the speakers and headphones. Equaliser works too.
Upon rebooting, the CPU top speed will set itself to 2.2GHz, despite being set higher and saved at a higher speed in Trickstermod. Certainly trivial though.
Strange thing I've noticed: On the undervolt part I've noticed that there is a freq called 3033MHz, but no 2899MHz freq. Just an observation.
Misc
Force Fast Charge confirmed working! Before flashing new kernel charge went up 5% in about half an hour. It's now up another 5% in a matter of 5-10mins. This is when plugged to my PC.
Vibrator strength - set to 20 from 31, much quieter on table and can still feel it.
I'd like to say a huge thank you to DooMLoRD and AndroPlus for developing this stable kernel. Now my Z3C is worth the £28 a month I'm paying for again. Since this silly lad decided to bork the camera, Bravia functionality etc by rooting it on the first day. I'll report back and edit the post with my findings.
Max won't go beyond 2.266 GHz, Min won't change.
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
pjmanalo said:
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
Click to expand...
Click to collapse
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
DBCJoey said:
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
Click to expand...
Click to collapse
Thanks! That did the trick!
Odd that my usual app for the job across 4 other phones - SetCPU - doesn't work on what should essentially be the same job. [emoji55]
Please make sound_control drivers work so its possible to boost headphone volume on the Xperia Z3 Compact... Thanks
Nice work, a lot of updates I like it!
Is it possible to add a change log?
Thanks!
kernel for d5803 with the .93 but not .105
i search a kernel for the d5803 with the last .93 french version of phone
.5.77
Works great! Thanks a lot
Link for Z3C_D5803_AndroPlusKernel_v10.zip is dead
Pls upload in another location.
Yay sound control is working, thank you so much you're the best!
How to make this?
Hi AndroPlus,
I'm trying to figure out how one would go about building this boot.img that you've created.
What platform and compiler are you using?
Where are you getting sources the for the kernel? This file?
c9af6fc647060fb85dd646798453ec8f 23.0.A.2.105.tar.bz2
How do you construct boot.img from zImage + recovery?
Sorry if these are dumb questions.
Edit: never mind, I figured this out.
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/ contains most of the information I needed.
The arm version of gcc that ships with Ubuntu 14.04 worked fine - arm-none-eabi-gcc (4.8.2-14ubuntu1+6) - no need to track down any mystery binaries. I did have to make several modifications to the kernel source to get it to build. Interestingly, some of the cpufreq stuff contained code that was incorrect. Someone at Samsung needs to go look up what "sequence point" means.
The hardest part was figuring out how to turn the zImage + ramdisk into something I could boot.
This: https://github.com/sonyxperiadev/mkqcdtbootimg was the correct tool to use - again, no need to track down any mystery mkbootimg or dtbTool binaries.
Hope this is helpful to someone. As someone new to Xperia dev, I found most of the information out there worse than useless.
I can't use my vr gear for more that 10 minutes before the overheating message appears on the phone.
Has anyone found a fix for this?
I wouldn't do the cooling fan mod on the gear, too much hassle.
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
jedisurfer said:
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
Click to expand...
Click to collapse
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Rayan said:
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Click to expand...
Click to collapse
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
jedisurfer said:
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
Click to expand...
Click to collapse
Funny I just did the same thing to my a10 7870k rig. Lowered vcore and over clocked gpu. Runs much better those a10s don't need 1.45 volts lol. I'm not sure if I could do that to my s6 tho as I'm nervous to root because of jump program.
Sent from my SM-G920T using Tapatalk
I have this tabled for a long time, but as i rarely used it i didn't bother with it much. From day one back in 2014 the tablet was sluggish and laggy, today is just unbearable even for browsing. So i have decided to take a look of what can i do.
I have installed the latest (10.26.2019) LineageOS-14.1-Deathly with gapps nano.
I have installed CPU Throttling Test from the play store and start testing to see what's going on. I saw that the CPU Throttle instantly (like in 10-15 sec max) from 1900mhz to 600mhz, and this is where the sluggishness comes from, the CPU is constantly throttled no matter that you are just looking at a simple web page.
I started playing with the Deathly Adiutor and under-voltage the cpu, set the max to 1400mhz and this is where it is stable as it is. At 1400mhz constant 100% CPU stress the CPU temps are around 90c (at 95 the cpu starts throttling). Anything above 1400mhz even with under voltages CPU results in throttling within 1-2 min, but even like that at 1400mhz and GPU set to be always used and at minimum of 480mhz (with setting in dev options to always use gpu for 2d composition) the performance was really much much better then the stock settings.
I have continued to play with it and noticed that if i apply pressure with my fingers on the back panel just below the camera where is the most hottest, the temps are dropping 10-15C, so i have opened it and i saw the issue.
The issue is that the metal shield radiators does not make a good contact with the thermal pad on the back panel, and thus can't dissipate the heat well. This may variety from user to user as some back panels will make better or worse contact, but its far from ideal.
Its good that i have some spare thermal pads around and i have applied them, and the result is perfect, drop in 12-17Cfrom stock setup under continues stress.
As a final result i have managed to bump the CPU from 1400mhz to 1600mhz with 1087mV voltage and at max 84C (down from around 90 at 1400mhz) at constant 100% CPU stress. The performance gains are around 100 to 150% (At around 42-47k GIPS up from 20-25k GIPS stock in CPU Throttling test). Additionally i have to say, its extremely easy to open the back cover panel.
Furthermore, i made an video to see how it runs and the settings i use.
https://youtu.be/_UJdjPDQB00
I'm attaching before and after the mod photos.
Quick followup, i have run 3D Mark benchmark and PCmark, see the screenshots below. Managed to achieve the world fastest Tab S, enjoy
Awesome.. I followed ur recommendations and set 1087mv at 1600mhz and its fasttttt
rihui said:
Awesome.. I followed ur recommendations and set 1087mv at 1600mhz and its fasttttt
Click to expand...
Click to collapse
Thanks mate. I'm glad it helps According to 3DMark, the performance now is slightly better then Galaxy Tab A 2019, it really bring new life to this tablet and its ready to rock another couple of years
how's your battery life with minimum CPU speed at 1600
Screen on & Standby time?
rihui said:
how's your battery life with minimum CPU speed at 1600
Screen on & Standby time?
Click to expand...
Click to collapse
Its not the minimum CPU frequency that gives you the performance boost, its the maximum frequency limit at 1600mhz down from 1900mhz, as i explained, to gain the performance, you need to avoid CPU from overheating and throttle down itself to the ground. That's why the max frequency with the thermal pads and improved thermals is 300mhz below the stock 1900mhz, and without the pads my max stable frequency were 1400mhz (500mhz below stock).
The minimum frequency will only smooth out initial animations and things like that, but don't have much of an impact on the overall performance. With that said, increasing the minimum frequency ofc will eat more battery and you don't need it, you can safely set it to 650mhz (as low as it allows) and depending on your kernel governor policy should have the same or better battery life. As i said, the main gainer is preventing the CPU from overheating at 1900mhz and throttle down to 650mhz where it sits most of the time with stock settings.
In fact if you limit your max frequency to 1400 or 1600mhz depending on your stable thermal results, and set minimum to 650mhz, you will see the performance gain AND significantly increased battery life due to that CPU does not go to 1900mhz and does not eat that much power and voltage. You really need to fine tune it depending on your needs, but at stock CPU throttling down to 650mhz and staying there is an manufacturer (Samsung) failure, and if i were discovered this when i bought it, i would wanted refund, as they advertise 1900mhz CPU which almost never works at that frequency.
I tested this method on other tablets and phones, and while it happens on other devices to throttle down after 5-7 mins (not after 15 sec), i have never seen to throttle more then down to 80% of the advertised frequency, but the Tab S goes almost immediately down to 35% where it stays and cripple the device. Its really really bad engineering from Samsung.
Going to try this.
Thanks
A lot better .
What thickness of thermal pad should I buy? Probably will buy from Amazon unless I need to make a trip to Microcenter. Thanks for this suggestion @nauvho
osutx427 said:
What thickness of thermal pad should I buy? Probably will buy from Amazon unless I need to make a trip to Microcenter. Thanks for this suggestion @nauvho
Click to expand...
Click to collapse
Well as you can see on the picture, the CPU bed already has one black pad by Samsung by default which is around 0.2/0.3mm i think, but it does not make contact, so i put on the CPU radiator 1mm pad and on the other radiators i put 0.5mm to equalize in case my pad is too thick. Your guide should be how easy is to close the back-plate, if you need too much force you may need thinner. So i guess you can take 0.3, 0.5 and 1mm pads.
effing A
Wow
Applied the same settings that you show in the video and WOW! It's like a new tablet. I didn't even put thermal pads.
joelcool69 said:
Applied the same settings that you show in the video and WOW! It's like a new tablet. I didn't even put thermal pads.
Click to expand...
Click to collapse
nice
just rooted t800 with MM + trw + SU.
added some thermal pads like in the pics.
installed Deathly Adiutor ....which said that doesn't like the kernel..and doesn't let to change the cpu max speed, and the voltage page doesn't even exist
installed Kernel Adiutor from playstore with which I can lower the freq, and for 1600 it works 1-2min at 27-28000GIPS then starts to throttle
louis_alphons said:
just rooted t800 with MM + trw + SU.
added some thermal pads like in the pics.
installed Deathly Adiutor ....which said that doesn't like the kernel..and doesn't let to change the cpu max speed, and the voltage page doesn't even exist
installed Kernel Adiutor from playstore with which I can lower the freq, and for 1600 it works 1-2min at 27-28000GIPS then starts to throttle
Click to expand...
Click to collapse
Why are you using MM? Also, did you noticed that center pad is thicker and side ones are tinnier? what are your CPU temps? Also probably due to MM, but I'm getting around 42gpis (average) at 1.6, but you should really check your pads placement, thickness and temps, put the CPU under load note the temps before throttling down.
nauvho said:
Why are you using MM? Also, did you noticed that center pad is thicker and side ones are tinnier? what are your CPU temps? Also probably due to MM, but I'm getting around 42gpis (average) at 1.6, but you should really check your pads placement, thickness and temps, put the CPU under load note the temps before throttling down.
Click to expand...
Click to collapse
I'm using MM since I don't know if it worth to upgrade; does this LineageOS work well...all features (cam, scanner, soud etc) works with it?
used 1mm pad over the cpu... 0.5 otherwise (china made); also removed the small factory pad and placed another pad patch there; the back cover heats well and I assume that the heat doesn't have where to go.
since it's not throttling at 1600MHZ (almost 100%, take a look at the pic)...from where to get more than 28GIPS?
louis_alphons said:
I'm using MM since I don't know if it worth to upgrade; does this LineageOS work well...all features (cam, scanner, soud etc) works with it?
used 1mm pad over the cpu... 0.5 otherwise (china made); also removed the small factory pad and placed another pad patch there; the back cover heats well and I assume that the heat doesn't have where to go.
since it's not throttling at 1600MHZ (almost 100%, take a look at the pic)...from where to get more than 28GIPS?
Click to expand...
Click to collapse
I don't think removing the stock black pad were a good idea, I did not removed mine, my pad is next to it. Also CPU throttle app is not reliable to monitor cpu temp (at least for me) , you should do it by starting the throttle test and then switch to deathly auditor and monitor the temp and clock there or other app like CPUz or Aida. Look at the video how I monitored the temp. The CPU will start throttle at 93-95c so your temp of 81 cannot be accurate if it throttle. Didn't you said that you throttle at 1.6 in your previous post?
Regarding the performance I think it might be eigher app difference between mm and 7.1 or due to MM itself. And yes everything is working perfectly for me with lineage, camera, fingerprint, everything is fine and it is mile better then MM imo.
installed 7.1
pcmark 4330 with your mods.
so the thermal pads doesn't matter on MM.
from my testings on 7.1 the boost in pcmark comes form setting max freq 1600 + undervoltage (3000->3500), and another boost...by setting the lower freq to 1600 (3500->4300)
louis_alphons said:
installed 7.1
pcmark 4330 with your mods.
so the thermal pads doesn't matter on MM.
from my testings on 7.1 the boost in pcmark comes form setting max freq 1600 + undervoltage (3000->3500), and another boost...by setting the lower freq to 1600 (3500->4300)
Click to expand...
Click to collapse
Nice.
About the pads, they matter only if the CPU temp under load drops when you apply pressure with fingers on the back cover as i explained in my first post, but idk if this apply to all tablets or just mine. The boost comes from not throttling the CPU down and being stable at maximum possible frequency. The CPU can go up to 1900mhz and beyond (2.1 by spec), but the cooling is not enough for that frequencies.
I think that adding an 0.5-1mm copper heat pipe thru radiators or copper heat pads similar to flagship phones might push it to 1.9, will order some someday and try it.
now it will be interesting ?% it's the termal mod in this boost, which means, performing the test in PCMARK only with steps 1+2:
1. LineageOS-14.1-Deathly
2. Deathly Adiutor (which requires step 1) + CPU max freq 1600 + undervoltage at that freq + CPU min freq 1600
3. Thermal pads added inside the box.
Since I started with thermal pads...I can say that in MM it doesn't matter.
-after upgrade to 7.1 as I said..PC...MArk around 3000 (thermal pads mounted)
-after setting max freq 1600 + undervoltage I got a boost in PCMark to 3600
-in addition, with min freq 1600...got another boost..to 4300; in this turbo state..the battery drains quickly, but the interface it's fast like the wind.
PCMark doesn't use CPU at 100%, it counts also how fast cand do certain short tasks...and this matters because if CPU it's in it's low power states..it loose time to rise its freq and do the calc at full power.
louis_alphons said:
now it will be interesting ?% it's the termal mod in this boost, which means, performing the test in PCMARK only with steps 1+2:
1. LineageOS-14.1-Deathly
2. Deathly Adiutor (which requires step 1) + CPU max freq 1600 + undervoltage at that freq + CPU min freq 1600
3. Thermal pads added inside the box.
Since I started with thermal pads...I can say that in MM it doesn't matter.
-after upgrade to 7.1 as I said..PC...MArk around 3000 (thermal pads mounted)
-after setting max freq 1600 + undervoltage I got a boost in PCMark to 3600
-in addition, with min freq 1600...got another boost..to 4300; in this turbo state..the battery drains quickly, but the interface it's fast like the wind.
PCMark doesn't use CPU at 100%, it counts also how fast cand do certain short tasks...and this matters because if CPU it's in it's low power states..it loose time to rise its freq and do the calc at full power.
Click to expand...
Click to collapse
Thermal mode does matter alot, CPU thermals is everything, the lower temps are, the higher frequency you can push the CPU, more frequency = more performance. As i said, without the thermal pads i could not get 1.6ghz to be stable, only 1.4 were stable-ish.
In stock rom, CPU governor and states are set according to the temps with the stock cooling. But if you don't change settings it wont change much. However Samsung engineers did a terrible job with those default settings, so as i explained in my first post only doing the software changes had dramatic impact on the performance because you get the CPU stable even at 1.4, but the thermal mod push it further to 1.6
The true performance benchmark is the 3DMARK (my screenshots 3 and 4 for score "ice storm unlimited" test and "Sling Shot" test) this will push your CPU and GPU to the max, PCMark is more about daily use performance and also can be used to measure battery performance between different settings.
Yes leaving CPU with minimum of 1.6 will drain battery more quickly naturally, is using more power, i leave mine at 1.2 as minimum, but minimum speed should not matter much in benchmarks if you are using the same as mine CPU governor. CPU governor basically tells the CPU how to behave, like how quickly to rise the frequency, for how long and etc.