Using performance cpu governor

pico · 02-12-2011, 20:24

Using the performance cpu governor on the D3 seems to make it more responsive in my so far limited testing using it. This will most likely kill battery life, but here is how I did it.

1) Turn on USB debugging

2) Root the device using z4root.

3) Install android SDK on your PC

4) Use <sdk-install-dir>/platform-tools/adb to get shell access on the device.
ADB did not recognize the device until I put the manufacture ID in adb_usb.ini

Code:

echo "0x0e21" > ~/.android/adb_usb.ini

5)

Code:

./adb shell
$ su /bin/sh
# echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# exit
$ exit

The D3 uses ondemand by default.

4DThinker · 02-12-2011, 20:45

Since you know more about android than most of us will, Pico, could you look into adding the android market to it? Right now that one flaw is a far more serious omission than leaving out gapless playback. Your CPU experimentation is greatly appreciated as well. The D3 will never win a showdown against the iPod Touch until its UI is equally responsive.

Headcased · 02-13-2011, 10:38

well done ive been in the mits of getting root access to it too
seems u beat me to it

market is all its missing a very big pain finding apps hoping there not infested

makes sense to underclock the cpu to save battery

also strange why it did not use 2.2 out of the box

also have you noticed the ear piece at the top

seems to use this soc
TCC93xx
http://www.telechips.com/

make sense too considering the full hd branding

also the gpu details
GPU offers up to 20M polygon 3D graphic with OpenGL ES2.0

so it dose seem indeed this is a clock scaling issue

pico · 02-14-2011, 04:17

I think it uses TCC8900, only from digging around in software though.

adrianv04 · 02-14-2011, 05:15

pico,

I've used XP, Windows 7, and Ubuntu systems to install the Android SDK and everything.

I've rooted my D3 using z4root.

I got the Google USB Drivers to install the Android ADB Interface for my D3, and modified adb_usb.ini to include Cowon's vendor code (Windows XP-only).

Now, with everything supposedly configured appropriately, ADB is just not recognizing my device. I've rebooted, restarted the adb server, reconnected the D3 multiple times, reinstalled the drivers, etc. With every combination, every "adb" command (shell, usb, devices, etc.) returns "error: device not found".

Is there anything else besides the few steps you outlined that I'm missing? Definitely have just researched Android development for the past few hours just to make sure everything was correct, and I'm not seeing any reason (under Windows XP, Windows 7, and Ubuntu) why ADB doesn't recognize my D3 under any O/S I've tried.

Any help is greatly appreciated - I would love to set the cpu profile to performance to see if there's a difference in everyday use.

-Adrian

pico · 02-14-2011, 05:49

Quote:

Originally Posted by adrianv04

pico,

I've used XP, Windows 7, and Ubuntu systems to install the Android SDK and everything.

I've rooted my D3 using z4root.

I got the Google USB Drivers to install the Android ADB Interface for my D3, and modified adb_usb.ini to include Cowon's vendor code (Windows XP-only).

Now, with everything supposedly configured appropriately, ADB is just not recognizing my device. I've rebooted, restarted the adb server, reconnected the D3 multiple times, reinstalled the drivers, etc. With every combination, every "adb" command (shell, usb, devices, etc.) returns "error: device not found".

Is there anything else besides the few steps you outlined that I'm missing? Definitely have just researched Android development for the past few hours just to make sure everything was correct, and I'm not seeing any reason (under Windows XP, Windows 7, and Ubuntu) why ADB doesn't recognize my D3 under any O/S I've tried.

Any help is greatly appreciated - I would love to set the cpu profile to performance to see if there's a difference in everyday use.

-Adrian

The key to getting adb to recognize the D3 for me was adding the manufacture ID to adb_usb.ini

I did it on Linux, so I suggest you try again in Ubuntu.

You can confirm the ID by running dmesg just after you plug in the D3.

Code:

dmesg
..
usb 1-3: new high speed USB device using ehci_hcd and address 4
usb 1-3: New USB device found, idVendor=0e21, idProduct=1060
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3: Product: COWON D3
usb 1-3: Manufacturer: COWON
usb 1-3: SerialNumber: COWON D3

The page here suggests you have to add it to udev in Ubuntu, and gives you an example of how. You will need to reboot after adding the udev file, just so you know.

But I believe you will have to add it to adb_usb.ini still (in your home dir .android) because I doubt the SDK yet supports Cowon's vendor ID.

See here for previous discussion on this with mobile phone vendors.

Good luck

adrianv04 · 02-14-2011, 05:59

Quote:

Originally Posted by adrianv04

pico,

I've used XP, Windows 7, and Ubuntu systems to install the Android SDK and everything.

I've rooted my D3 using z4root.

I got the Google USB Drivers to install the Android ADB Interface for my D3, and modified adb_usb.ini to include Cowon's vendor code (Windows XP-only).

Now, with everything supposedly configured appropriately, ADB is just not recognizing my device. I've rebooted, restarted the adb server, reconnected the D3 multiple times, reinstalled the drivers, etc. With every combination, every "adb" command (shell, usb, devices, etc.) returns "error: device not found".

Is there anything else besides the few steps you outlined that I'm missing? Definitely have just researched Android development for the past few hours just to make sure everything was correct, and I'm not seeing any reason (under Windows XP, Windows 7, and Ubuntu) why ADB doesn't recognize my D3 under any O/S I've tried.

Any help is greatly appreciated - I would love to set the cpu profile to performance to see if there's a difference in everyday use.

-Adrian

I spoke too soon. Got it working in Windows 7. For anyone else that may run into issues - Make sure your "android_winusb.inf" file has the following lines under the "Google.[NTx86|NTamd64]" section:

Code:

;Cowon D3
%SingleAdbInterface%        = USB_Install, USB\VID_0E21&PID_1060
%CompositeAdbInterface%     = USB_Install, USB\VID_0E21&PID_1060&MI_01
;

This matches the driver to your device (make sure to modify "adb_usb.ini" file with the 0x0e21 Cowon vendor code, too).

Now, I can finally go to bed - thankfully, I took the day off!

pico, thanks for the suggestion for the CPU, let's see how much this makes a difference!

EDIT: Forgot to mention, it wasn't working before because I had only specified "USB\VID_0E21&PID_1060" for both SingleAdbInterface and CompositeAdbInterface. Throughout my experimenting, I completely forgot to go back and fix these variables.

adrianv04 · 02-14-2011, 17:39

For what it's worth, you can tell that it's a bit more responsive after a day of use, but enough to enhance overall performance? Not too much, but it's still a good thing.

If anything it got me playing around with this enough to pop Pandora on it and dig around the underlying OS. Seems like the D3 is pretty good under the hood, just needs a little help with some optimization that hopefully Cowon can provide.

I love this device, and although it was a bit pricey, I really can tell the difference between the audio quality on the D3 versus my S9, so I'm sticking with it. Playing around with Android is an added bonus, but Cowon really shines when making music sound good.

Ryogo · 02-20-2011, 13:51

Using market on D3 is not such a big deal I think.
What you need -
GoogleFramework.apk
Vending.apk
for Android 2.1, you can find this stuff over XDA freely.
Install GoogleFramework.apk, then Vending.apk and finally set up an account in Settings->Accounts & Sync.
Just keep in mind - you need an apks for Android 2.1 / HDPI.

---

Also, about performance CPU governor - warning, this thing kills your battery. This governor is designed so your CPU will always be clocked to the maximum speed. Normally android is used with ondemand governor which clocks your CPU up if needed and keeps it as low, as can be in other situations (when screen is turned off, etc).

NiceFluffy · 02-22-2011, 15:37

Quote:

Originally Posted by Ryogo

Install GoogleFramework.apk, then Vending.apk and finally set up an account in Settings->Accounts & Sync.

Has any tried this yet? I was unable to install the framework apk.

Ryogo · 02-25-2011, 05:36

EDIT:
done some research. Since there is android 2.1, apks to be installed
GoogleApps.apk
GoogleCheckin.apk
gtalkservice.apk
SetupWizard.apk
Vending.apk

Also, if you manage to install those market won't work anyway because build.prop must also be modified to deceive market that you have another device (with legally enabled market support).

So, no market until root/custom recovery.

roebeet · 03-04-2011, 17:12

Quote:

Originally Posted by pico

Using the performance cpu governor on the D3 seems to make it more responsive in my so far limited testing using it. This will most likely kill battery life, but here is how I did it.

1) Turn on USB debugging

2) Root the device using z4root.

3) Install android SDK on your PC

4) Use <sdk-install-dir>/platform-tools/adb to get shell access on the device.
ADB did not recognize the device until I put the manufacture ID in adb_usb.ini

Code:

echo "0x0e21" > ~/.android/adb_usb.ini

5)

Code:

./adb shell
$ su /bin/sh
# echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# exit
$ exit

The D3 uses ondemand by default.

Worked for me - thanks! (Ubuntu user)

02-12-2011, 20:24	#1
pico Member Join Date: Feb 2011 Posts: 36	Using performance cpu governor Using the performance cpu governor on the D3 seems to make it more responsive in my so far limited testing using it. This will most likely kill battery life, but here is how I did it. 1) Turn on USB debugging 2) Root the device using z4root. 3) Install android SDK on your PC 4) Use <sdk-install-dir>/platform-tools/adb to get shell access on the device. ADB did not recognize the device until I put the manufacture ID in adb_usb.ini Code: echo "0x0e21" > ~/.android/adb_usb.ini 5) Code: ./adb shell $ su /bin/sh # echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor # exit $ exit The D3 uses ondemand by default.

02-14-2011, 05:15	#5
adrianv04 Junior Member Join Date: Dec 2009 Posts: 27	ADB is not recognizing my D3 pico, I've used XP, Windows 7, and Ubuntu systems to install the Android SDK and everything. I've rooted my D3 using z4root. I got the Google USB Drivers to install the Android ADB Interface for my D3, and modified adb_usb.ini to include Cowon's vendor code (Windows XP-only). Now, with everything supposedly configured appropriately, ADB is just not recognizing my device. I've rebooted, restarted the adb server, reconnected the D3 multiple times, reinstalled the drivers, etc. With every combination, every "adb" command (shell, usb, devices, etc.) returns "error: device not found". Is there anything else besides the few steps you outlined that I'm missing? Definitely have just researched Android development for the past few hours just to make sure everything was correct, and I'm not seeing any reason (under Windows XP, Windows 7, and Ubuntu) why ADB doesn't recognize my D3 under any O/S I've tried. Any help is greatly appreciated - I would love to set the cpu profile to performance to see if there's a difference in everyday use. -Adrian

02-25-2011, 05:36	#11
Ryogo Junior Member Join Date: Mar 2009 Posts: 3	EDIT: done some research. Since there is android 2.1, apks to be installed GoogleApps.apk GoogleCheckin.apk gtalkservice.apk SetupWizard.apk Vending.apk Also, if you manage to install those market won't work anyway because build.prop must also be modified to deceive market that you have another device (with legally enabled market support). So, no market until root/custom recovery. Last edited by Ryogo; 02-25-2011 at 06:44..

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

02-12-2011, 20:45	#2
4DThinker Senior Member Join Date: Mar 2009 Posts: 588	Since you know more about android than most of us will, Pico, could you look into adding the android market to it? Right now that one flaw is a far more serious omission than leaving out gapless playback. Your CPU experimentation is greatly appreciated as well. The D3 will never win a showdown against the iPod Touch until its UI is equally responsive.

02-13-2011, 10:38	#3
Headcased You Know When You've Been Headcased Join Date: Mar 2009 Location: Goggleth Cymru Posts: 272	well done ive been in the mits of getting root access to it too seems u beat me to it market is all its missing a very big pain finding apps hoping there not infested makes sense to underclock the cpu to save battery also strange why it did not use 2.2 out of the box also have you noticed the ear piece at the top seems to use this soc TCC93xx http://www.telechips.com/ make sense too considering the full hd branding also the gpu details GPU offers up to 20M polygon 3D graphic with OpenGL ES2.0 so it dose seem indeed this is a clock scaling issue

02-14-2011, 04:17	#4
pico Member Join Date: Feb 2011 Posts: 36	I think it uses TCC8900, only from digging around in software though.

02-14-2011, 17:39	#8
adrianv04 Junior Member Join Date: Dec 2009 Posts: 27	For what it's worth, you can tell that it's a bit more responsive after a day of use, but enough to enhance overall performance? Not too much, but it's still a good thing. If anything it got me playing around with this enough to pop Pandora on it and dig around the underlying OS. Seems like the D3 is pretty good under the hood, just needs a little help with some optimization that hopefully Cowon can provide. I love this device, and although it was a bit pricey, I really can tell the difference between the audio quality on the D3 versus my S9, so I'm sticking with it. Playing around with Android is an added bonus, but Cowon really shines when making music sound good.

02-20-2011, 13:51	#9
Ryogo Junior Member Join Date: Mar 2009 Posts: 3	Using market on D3 is not such a big deal I think. What you need - GoogleFramework.apk Vending.apk for Android 2.1, you can find this stuff over XDA freely. Install GoogleFramework.apk, then Vending.apk and finally set up an account in Settings->Accounts & Sync. Just keep in mind - you need an apks for Android 2.1 / HDPI. --- Also, about performance CPU governor - warning, this thing kills your battery. This governor is designed so your CPU will always be clocked to the maximum speed. Normally android is used with ondemand governor which clocks your CPU up if needed and keeps it as low, as can be in other situations (when screen is turned off, etc).