Anybody using SetCPU

Odieman · 01-05-2012, 06:06 PM

If so, what settings are you using, and how's it working for you?

Kboland · 01-05-2012, 07:54 PM

Are you using it, and if so is it working? I'd be very interested in even getting the little guy to clock to 1ghz, and more than willing to trade the loss in battery life for even a slight increase in performance. Because as far as I can tell, for a device with almost identical stats to the Nook Color, it doesn't even come close to the same user experience.

jefftheworld · 01-06-2012, 01:01 AM

Changing clock speed with setCPU would require kernel support. You'd have to compile a kernel with CPU frequency scaling. It shouldn't be all too hard, since Freescale (the CPU vendor) has a lot of documentation on compiling Linux kernels for the i.MX line, but you'd need some Linux know-how.

mr_nobody · 01-06-2012, 08:32 AM

At one point I was looking at using CIFS for something on the vox only to find the kernel did not support it. So, it looks like there are probably a few useful things that could go in a custom kernel. Although presumably the more features you add, there is a hit somewhere in terms of memory/processor usage?

KoboJW · 01-06-2012, 11:51 AM

As far as I know, the CPU is already running at max frequency supported by this particular version...

hpulley · 01-06-2012, 12:02 PM

Freescale advertises 800MHz max but reports of overclocking to 1-1.2GHz have been reported.

mr_nobody · 01-06-2012, 12:04 PM

Overclocking is certainly the one thing which will void your warranty, I imagine.

hpulley · 01-06-2012, 12:50 PM

It is an interesting question and unless they are going to look at the kernel code of each returned unit it will be hard to know if thermal failure was caused by overclocking.

Odieman · 01-06-2012, 02:20 PM

The kernel of the vox does not allow for overclocking, however I was using it to set a more efficient CPU ramping, because reading is not that taxing, and if you can de ramp the processor to a lower clock speed then that (theoretically) will get you better battery life. If it also allows you to ramp up the processor more efficiently when you need more oomph, it should smooth out performance for more demanding apps.

jefftheworld · 01-07-2012, 01:05 AM

Quote:

Originally Posted by KoboJW

As far as I know, the CPU is already running at max frequency supported by this particular version...

I know for a fact that this CPU will go to 1Gz and remain stable and relatively cool. Although long-term heat degradation does come into play.

However, it obviously voids your warranty to do it and messing with overclocking is not something you should do unless you're experienced with that sort of thing. Unless you happen to know the thermal failure point of this particular i.MX chip and have the tools to monitor it's temperature, probably best not to do it for now.

hieronymos · 01-07-2012, 01:20 AM

Rather important is the question If the GPU will ever work correctly.

01-05-2012, 06:06 PM	#1
Odieman Enthusiast Posts: 27 Karma: 10 Join Date: Oct 2011 Device: Kobo vox	Anybody using SetCPU If so, what settings are you using, and how's it working for you?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Development SetCPU for Edge	javese	enTourage eDGe	8	09-04-2012 01:11 AM
Setcpu and the PE	bunodosoma	enTourage eDGe	10	08-03-2011 08:56 PM

01-05-2012, 07:54 PM	#2
Kboland Zealot Posts: 115 Karma: 201864 Join Date: Jan 2012 Location: Sudbury, ON Device: Kobo Vox, iPod Touch, Samsung Galaxy Nexus	Are you using it, and if so is it working? I'd be very interested in even getting the little guy to clock to 1ghz, and more than willing to trade the loss in battery life for even a slight increase in performance. Because as far as I can tell, for a device with almost identical stats to the Nook Color, it doesn't even come close to the same user experience.

01-06-2012, 01:01 AM	#3
jefftheworld Groupie Posts: 190 Karma: 157090 Join Date: Nov 2011 Device: Kobo, Kobo Vox	Changing clock speed with setCPU would require kernel support. You'd have to compile a kernel with CPU frequency scaling. It shouldn't be all too hard, since Freescale (the CPU vendor) has a lot of documentation on compiling Linux kernels for the i.MX line, but you'd need some Linux know-how.

01-06-2012, 08:32 AM	#4
mr_nobody Evangelist Posts: 440 Karma: 26671 Join Date: Nov 2011 Device: kobo mini, nexus 7 (2012), kobo vox	At one point I was looking at using CIFS for something on the vox only to find the kernel did not support it. So, it looks like there are probably a few useful things that could go in a custom kernel. Although presumably the more features you add, there is a hit somewhere in terms of memory/processor usage?

01-06-2012, 11:51 AM	#5
KoboJW UX Lead, Kobo Vox Posts: 113 Karma: 199002 Join Date: Oct 2011 Device: Boxes of Voxes	As far as I know, the CPU is already running at max frequency supported by this particular version...

01-06-2012, 12:02 PM	#6
hpulley Addict Posts: 288 Karma: 29760 Join Date: Nov 2011 Location: Ontario, Canada Device: Kobo Vox, Playbook32	Freescale advertises 800MHz max but reports of overclocking to 1-1.2GHz have been reported.

01-06-2012, 12:04 PM	#7
mr_nobody Evangelist Posts: 440 Karma: 26671 Join Date: Nov 2011 Device: kobo mini, nexus 7 (2012), kobo vox	Overclocking is certainly the one thing which will void your warranty, I imagine.

01-06-2012, 12:50 PM	#8
hpulley Addict Posts: 288 Karma: 29760 Join Date: Nov 2011 Location: Ontario, Canada Device: Kobo Vox, Playbook32	It is an interesting question and unless they are going to look at the kernel code of each returned unit it will be hard to know if thermal failure was caused by overclocking.

01-06-2012, 02:20 PM	#9
Odieman Enthusiast Posts: 27 Karma: 10 Join Date: Oct 2011 Device: Kobo vox	The kernel of the vox does not allow for overclocking, however I was using it to set a more efficient CPU ramping, because reading is not that taxing, and if you can de ramp the processor to a lower clock speed then that (theoretically) will get you better battery life. If it also allows you to ramp up the processor more efficiently when you need more oomph, it should smooth out performance for more demanding apps.

01-07-2012, 01:20 AM	#11
hieronymos Groupie Posts: 186 Karma: 45172 Join Date: Nov 2011 Device: Kobo Vox	Rather important is the question If the GPU will ever work correctly.