Develop Bugs

How to Speed up your Hero - My Way

Well i already tried speeding up my HERO by following the steps from another thread here in the forum and it just didn't work for me.
So Heres what i Tried and it just seems to work out for me! And its very simple too.​
THIS IS VERY IMPORTANT: DOWNLOAD "OVERCLOCKWIDGET" FROM THE MARKET AND SET THE MIN MHZ TO (128000) AND MAX TO (528000) MHZ. THIS SHOULD HELP KEEP THINGS RUNNING SMOOTH.
^^^^Also from the settings of "OverClock Widget" you can set the MHZ Frequencies while the screen if off to the a low but not so low Frequencies in order to save battery!
So if your like me and like to have a lot of widgets on your phone then Using Task manager to kill certain apps might just do the trick....
First of all never end applications such as
com.htc.socialnetwork.provider
com.htc.provder.weather
HTC media uploader
Touch input
HTC Location Service​
and more! They do not have an icon if your using "advance task Manager" All other apps are good to end such as music,peep,market, Messages,Mail, Google Mail, and of course Browser which uses a lot of memory.
Give it a try and let me know how it goes...​
Heres the link to a video i made to show the performance of my HTC Hero!
Not the best quality.
http://www.youtube.com/watch?v=R3BrCmWXwhQ
Click to expand...
Click to collapse

Thats the way i do it to.
But i also noticed, that some widgets uses more battery than others. After i removed quick calender and digital clock, i got better battery performance. That might also have some effects on the processing power

I tried this...
This afternoon and so far this morning the Hero is far more responsive after I wake it up (which was when it was at its most laggy).
I can now immediately slide around the home screens. Before I had to wait a few seconds or suffer ignored screen swipes.
I was not using the Stocks app or widget but it was set to auto update so set it to never update.
Maybe its a process that runs regardless of whether you use the app or widget ??

Know what I think might work? An app that reboots the phone.
User selects frequency of reboot (daily? every 2 days? every week?)
User selects time of reboot (12 midnight? 3 am?)
User defines Countdown period (15 seconds? 30 seconds? 1 minute?)
At the user-defined time, the app will run itself, and prompt the user "Reboot Now?". A countdown timer will start.
User can select 'Later', 'In 10 minutes', or if there is no interaction/input, when countdown reaches 0, the app will reboot the phone automatically.
This way, users will always wake up to a 'fresh' phone. What do you guys think?

Rebooting the device won't make it faster. On the contrary you have to start every apps for the first time so it takes more time.
You'd better leave it on and turn to airplane mode when you don't need it.

piflechien said:
Rebooting the device won't make it faster. On the contrary you have to start every apps for the first time so it takes more time.
You'd better leave it on and turn to airplane mode when you don't need it.
Click to expand...
Click to collapse
Tell that to my phone. It's back to it's zippy self after a reboot, and only slows down after I run Maps, Browser, Google Talk, Market and HTC Mail

joemax said:
I tried this...
This afternoon and so far this morning the Hero is far more responsive after I wake it up (which was when it was at its most laggy).
I can now immediately slide around the home screens. Before I had to wait a few seconds or suffer ignored screen swipes.
I was not using the Stocks app or widget but it was set to auto update so set it to never update.
Maybe its a process that runs regardless of whether you use the app or widget ??
Click to expand...
Click to collapse
Well im glad to know it works not only for me but for other people Too!

minogue said:
Well i already tried speeding up my HERO by following the steps from another thread here in the forum and it just didn't work for me.
So Heres what i Tried and it just seems to work out for me! And its very simple too.
So if your like me and like to have a lot of widgets on your phone then Using Task manager to kill certain apps might just do the trick....
First of all never end applications such as
com.htc.socialnetworl.provider
com.htc.provder.weather
HTC media uploader
Touch input and more! They do not have an icon if your using "advance task Manager" All other apps are good to end such as music,peep, market and of course Browser which uses a lot of ram.....
Give it a try and let me know how it goes...
Click to expand...
Click to collapse
Could you be more detailed about what process must be excluded from closing?
com.htc.socialnetworl.provider
com.htc.provder.weather
HTC media uploader
Touch input
...
...
THX!

@Asci
Thread updated with latest Info!

I think clock should also be spared of killing, as if I recall correctly, something bad could happen to set alarms (not setting off, volume too low etc.)!

Hi guys, need some help.
i've just rooted my Hero thanks to this article http://forum.xda-developers.com/showthread.php?t=543571 and Quick Boot (which needs root) now works perfectly.
After i've installed overclockwidget i cannot start it as it gives me an error "Star-up error - cannot start Overclockwidget (need Root)".
Any ideas?
thanks in advance.

Surely increasing the CPU speed will also increase battery drain ?
Its also likely to lead to instability and additional heat (Hero gets hot enough when working hard).
Personally I would be wary of doing this.

I have no real issues with battery drainage after tweaking the processor speed; lasts about the same as it would w/out the tweaks.
I do see some minor performance improvements, but on the flip-side, the phone can also get sluggish at times upon waking it up from sleep.

I'm confused, my hero runs at 528 stock o_o

seshmaru said:
I'm confused, my hero runs at 528 stock o_o
Click to expand...
Click to collapse
wrong.. the proccesor was underclocked just like with the HTC Magic and the T-mobile G1

minogue said:
wrong.. the proccesor was underclocked just like with the HTC Magic and the T-mobile G1
Click to expand...
Click to collapse
wrong, mine runs at 528 MHz, and I haven't overclocked it

I can confirm that mine shows 526 (the widget number) as well out of the box. And changing the settings doesn't appear to do anything. It's always returning to 480Mhz - 528Mhz when I restart the app / widget. I've tried this both with SetCPU and OverClock Widget.
The Hero (at least some Heroes) seems to be immune to fiddling with the cpu. And I am sure I'm rooted, because I enabled paid apps in Android Market with MarketEnabler and that's working.
MarketEnabler didn't work out of the box tho - because it had a script that relied on Grep and Grep isn't installed, so I had to empty the AndroidMarket cache by hand from the terminal... Maybe there's something similar preventing fiddling with the cpu speeds?

Overclocking XDAndroid Rhodium

So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks

You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.

devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.

Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...

Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.

devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.

Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.

I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.

so nothing on the OC for 2.1 yet?
bump

I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.

on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying

O.S.K. byebye command is msmvkeyb_toggle=off

OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.

[Q] [REQ] Gsiff_Daemon Runaway causing severe battery drain, possible fixes?

This is a formal request for any developer capable of doing so, to take a look at this problem.
There is a growing number of users noticing a severe battery drain and hot phone at times, caused by the runaway process; (gsiff_daemon)
The threads discussing this as of now are scattered and unorganized, and with the number of users experiencing this problem, it would be excellent to have one central thread for everyone to work together on this.
Here's what we know so far:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
It is not carrier specific, At&t, Tmobile, and Verizon users have all confirmed this problem.
The only reliable way to rid of this at this time, is a reboot, although some have had luck ending the gsiff_daemon process, or renaming the file, although this requires further testing.
Here are a few threads that have been started on the issue, with some good reading:
http://forum.xda-developers.com/showthread.php?p=30074303#post30074303
http://forum.xda-developers.com/showthread.php?t=1800812&page=3
Anyone capable of looking into this, and know what they are looking at enough to determine the cause, will be eternally thanked, and i will personally donate a case of beer(or soda) to whoever fixes it.
Thanks!

is this Gsiff_Daemon issue only for rooted users? I just got it too...after rooting...I never had this issue since june 30, since I've had the phone

I just renamed the file.. problem went away. it doesn't run anymore.. and haven't had any negative effects that I can tell....

do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?

Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app

tjb433 said:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
Click to expand...
Click to collapse
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.

themadproducer said:
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.
Click to expand...
Click to collapse
isn'ttthere a period before bak?

eyecon82 said:
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).

78c10 said:
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).
Click to expand...
Click to collapse
I am using rooted stock rom
This is only an issue with touchwiz, so you won't see it on cm10
Sent from my SPH-L710 using xda app-developers app

eyecon82 said:
isn'ttthere a period before bak?
Click to expand...
Click to collapse
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.

themadproducer said:
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.
Click to expand...
Click to collapse
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though

eyecon82 said:
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though
Click to expand...
Click to collapse
Eyecon82...really...don't worry about the period. It's irrelevant.
So long is the file is renamed, it wont be triggered/found by whatever normally triggers/finds it.

http://pastebin.com/siAGdxp4
It looks like it's sending gyroscope and accelerometer data to the locapi, (location application interface) and there's some reference to sns there as well.
So, why would a location app need accelerometer data? Or maybe the question is why would someone who's getting my location data need my accelerometer data, too? What's in it for Samsung that they would bother developing it and roll it out? Why wasn't it there in June?
Ok, having a little fun speculating, but perhaps blackboxing for car accidents? Your phone log is the first thing they check and see if you were texting, or whatever, right before impact. Oh, wait, if they have a location-accessing app, they don't need your locally stored log. Nah, probably something technical with the compass....

Janis;34345281It looks like it's sending gyroscope and accelerometer data to the locapi said:
Yes, I don't have any evidence to support this other than what just happened on my phone. I was out for about a 15 minute walk and I got back. Phone was hot and i noticed a severe drop in battery. I remember reading that Goog Now tabulates how far you walked/jogged monthly or something. Maybe this process is capturing that motion/data for it? Just my speculation. No evidence. I think I'll try renaming the file as I dont really GAF about how far Goog thinks I've walked.
Click to expand...
Click to collapse

I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file

harryshepard said:
I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file
Click to expand...
Click to collapse
You sure it's gsiff_daemon that's causing the issue? Have you renaming qosmgr in system/bin?
Sent from my SGH-I747 using Tapatalk 2

Sorry, didn't have reply notification. Yes I am sure. I Google'd it after seeing it using 30% of my battery with about 50s use. I will try renaming qosmgr but how do you diagnose which process is actually doing it? This time battery doesn't specifically say gsiff_daemon but not sure if that's where I saw it before.
I have attached my battery use screenshot. Game and screen a the top, fair enough. But 13 hours on battery and 75% drained, 6% of which is 7 seconds of the gpsd process. It's a little odd
Sent from my GT-I9300 using xda app-developers app

fix yet ? mines doing same

gsiff_daemon
Mine has been doing the same ever since the kitkat update.
I am running an unrooted EE note 3 (n9005) in the UK.
Gsiff_daemon is constantly my top battery drainer according to the battery app (35% - 47%).
I have not been able to find any consistent method to either activate this rogue app or to get rid of it.
Is there any solution without rooting it as I understand that renaming it should do the trick?

+1 from me about this problem.
Uprooted, up to date Note 3.
No solution so far, will try turning off WiFi when screen off and auto rotation... Let's see...
Hopefully it'll be fixed soon or in next version. It's a shame, though, my Windows phone pals are teasing me!
Best regards,
Doncho

Better governor to prioritize performance rather than power save

Hi,
I have a rooted sm-p600. I have been finding ways to speed up my tablet and reduce (if not totally eliminate) the lag.
First, I installed wanam xposed module and enabled/disabled the "touchwiz DVFS" option and "Enable boost mode" option. I don't know if it makes any difference and I'm not totally sure either what that option is for. So if anyone could tell me if I should enable/disable it, that'll be great,
Second, I tried to use an overclocking app, "no-frills cpu" and "cpu tuner". I know that I actually have to have a custom kernel which enables overclocking but I really didn't need to overclock my tablet, I just basically want to keep my min and max frequencies to 1.9 so that means, it won't try to underclock my cputo save battery (which the kernel is doing by default). It works great and it DID eliminate the lag and the tablet was so snappy. But there's one glitch. If I lock the tablet, it fails to wake up. And I had to do a forced reboot. But there's one thing I've noticed and this may be of help to someone who is trying to figure out how to eliminate the known lag issue in the note 10.1 (2014). It only hangs if the tablet is not charging. Meaning, if I set the max and min frequencies to 1.9ghz, it hangs (once locked) if the tablet is not plugged into the charger. If I plug it into the charger, even if I lock it and unlock it several times, it doesn't hang.
So, anybody got any clue as to how to resolve this issue? Or has anyone come up with a better kernel for this tablet?

Try setting the min to 1.3 ghz see what that does or try using flux to set min Max and memory read times to 3072 or whatever the value is I forget. Play around with the settings and I'm sure you will find a better more stable experience. I don't know how having two quad cores affects the performance maybe that's why you getting the black screen and no wake on battery. It might have to tick over the lower quad first before it kicks in the main one. Might be taxing the battery to much clocking straight to 1.9. Hope this helps let me know how you get on

Qbm said:
Try setting the min to 1.3 ghz see what that does or try using flux to set min Max and memory read times to 3072 or whatever the value is I forget. Play around with the settings and I'm sure you will find a better more stable experience. I don't know how having two quad cores affects the performance maybe that's why you getting the black screen and no wake on battery. It might have to tick over the lower quad first before it kicks in the main one. Might be taxing the battery to much clocking straight to 1.9. Hope this helps let me know how you get on
Click to expand...
Click to collapse
Which overclocking app are you referring to? I would assume you're talking about "cpu tuner" as the other app I've mentioned in my initial pose which is "no-frills cpu control" doesn't have any other settings besides the min and max frequency.
GOOD NEWS though! I got cpu tuner to work! I did lower the min frequency to 1.8ghz and kept max at 1.9ghz. Actually, there are only 3 selectable values for both fields, it's 250mhz, 1.8ghz and 1.9ghz. I gave 1.8ghz a try, locked the tablet, it froze, then I restarted it. The settings were reapplied when I logged back in, then after that it never froze again even after I've locked it a few times. The performance is excellent! I tried running multiple apps on pen window. I've never seen it perform this well since I bought this tablet! Let's see if it works well in a few days.

draftbeer89 said:
Which overclocking app are you referring to? I would assume you're talking about "cpu tuner" as the other app I've mentioned in my initial pose which is "no-frills cpu control" doesn't have any other settings besides the min and max frequency.
GOOD NEWS though! I got cpu tuner to work! I did lower the min frequency to 1.8ghz and kept max at 1.9ghz. Actually, there are only 3 selectable values for both fields, it's 250mhz, 1.8ghz and 1.9ghz. I gave 1.8ghz a try, locked the tablet, it froze, then I restarted it. The settings were reapplied when I logged back in, then after that it never froze again even after I've locked it a few times. The performance is excellent! I tried running multiple apps on pen window. I've never seen it perform this well since I bought this tablet! Let's see if it works well in a few days.
Click to expand...
Click to collapse
Battery life will be horrible!
Στάλθηκε από το SM-P600 μου χρησιμοποιώντας Tapatalk 2

steveman29 said:
Battery life will be horrible!
Στάλθηκε από το SM-P600 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Yeah best to try flux123 kernal app on the playstore you can set a lot more in there. Works like a treat on my s4. Set it to 1.3 and 1.9. I'll post some more settings to try later. All I've got is nova launcher and disabled as much blout that I don't use. Not yet rooted on my tablet but just doing them two simple things makes a ton of difference. As you rooted you could use root uninstaller to remove touchwiz and other stupid startup processes. I did it last week on my tab 8.0 got rid of 12 pointless processes now that flys wouldn't even think it was the tablet. Can't wait for a oc kernel and decent rom for the note 10.1 will come into its own then. To bad Samsung killed it with all there unneeded rubbish .

Qbm said:
Yeah best to try flux123 kernal app on the playstore you can set a lot more in there. Works like a treat on my s4. Set it to 1.3 and 1.9. I'll post some more settings to try later. All I've got is nova launcher and disabled as much blout that I don't use. Not yet rooted on my tablet but just doing them two simple things makes a ton of difference. As you rooted you could use root uninstaller to remove touchwiz and other stupid startup processes. I did it last week on my tab 8.0 got rid of 12 pointless processes now that flys wouldn't even think it was the tablet. Can't wait for a oc kernel and decent rom for the note 10.1 will come into its own then. To bad Samsung killed it with all there unneeded rubbish .
Click to expand...
Click to collapse
At this point, I don't really mind the slight degrading of the battery life, I just want the tablet to be snappier.
By the way, I installed faux123, but it seems that I cannot change the settings. Like when I try to drag the min frequency slider to 1.3ghz, it slides back to 250mhz. Also, all of the other settings I set revert back to the original settings after I reboot. I have enabled the "set on boot" options on all screens, but they all just revert back to original settings on reboot. Am I missing something?

draftbeer89 said:
At this point, I don't really mind the slight degrading of the battery life, I just want the tablet to be snappier.
By the way, I installed faux123, but it seems that I cannot change the settings. Like when I try to drag the min frequency slider to 1.3ghz, it slides back to 250mhz. Also, all of the other settings I set revert back to the original settings after I reboot. I have enabled the "set on boot" options on all screens, but they all just revert back to original settings on reboot. Am I missing something?
Click to expand...
Click to collapse
Just came back to check for anymore help I could give and the best thing I can advice is clean rom. Fly's with nova launcher but still haven't got any kernals to take advantage of flux yet which sucks abit but trust me you won't be disappointed by clean rom if you haven't already got it on your tab don't waste another second

Stock Oreo - CPU not scaling

This morning my Pixel C felt slow and sluggish.
Rebooted and removed recently installed apps but no difference.
Installed a CPU monitoring app and see that the CPU stays at 204Mhz even under load.
Any ideas before I try a full wipe?

Full reset seems to have fixed though notice cpu maxes at 1326
This right?

I'm not sure most CPU monitors know what to do with the X1, I know CPU-Z doesn't recognize it beyond a general "Nvidia Tegra" chip. What app are you using?

I switched from AOSP for acbit but yesterday had the same issue. Tablet felt slow and sluggish.
CPU monitor app showed CPU not scaling.
Went back to stock Oreo and still "feels" slow.
Geekbench4 says single core 926 and multi 2561
This is wrong?

My Pixel C performance is strange still the OREO update. I know this going to sound weird but when in splitscreen, the app on the left in landscape or on the top in portrait is lagging a lot. Scrolling, page swiping, etc.. takes a distinct longer time than expected. The app in the other half of the screen is acting normally.
Could this be related to the same issue?
With the pixel C now discontinued, Google is unlikely to fix a bug, especially if nobody reports it.. Bit of a worry, what to do?

I'm facing this issue as well. Already wiped cache and did factory reset, with no results.
It's now a very fancy digital picture frame.

There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat

Vartom said:
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Click to expand...
Click to collapse
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L

laurentbon said:
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
Click to expand...
Click to collapse
At the moment I'm using the kernel I've modified, and I have no problem with scrolling on the left side of the screen in split screen mode.
you can try it.

Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.

MrPhilo said:
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
Click to expand...
Click to collapse
For what? if the frequency control and so works normally

Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156

AlfreGarcia98 said:
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
Click to expand...
Click to collapse
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you

liam_davenport said:
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
Click to expand...
Click to collapse
I dont know why, but the blue buttons are unclickable for me, so I cant create the issue.

Bringing back from dead.
So if you use Kernel Auditor to turn off some of the cores when this is occurring, the clock speed goes up for the primary core. It's as if they set a total limit, then divide by total core count. When battery charge is above 67%, you get the full max speed. No reboot or anything, just charge it up and you unlock the speed again. I suspect the Oreo kernels have bad throttling algorithm for this CPU.

My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.