Related
If possible could the choice under applications > development that allowed us to check having the screen not sleep while charging be added to a rom?
I know some said it was removed because many complained about the option, but I'm sure many miss it too.
I'd love to have it back for Pandora, SiriusXM and other apps without having to do the work around by setting the sleep time to 30 minutes or so.
Is it possible or is source code needed first?
Thanks in advance for any input!
Sent from my Super Clean 2.7.1 Froyo - Voodoo - Fascinate!
Just use SwitchWidgets, there is a widget to keep the screen on.
Or Widgetsoid. Works great with SC2.8
I have a feeling you'll see it back there soon
DEVELOPMENT DISCONTINUED
Disclaimer:
You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!
_motley kernel:
Current version features:
OC support (overclock) - frequencies: 1.200, 1.400, 1.504, or 1.600Ghz (recommend 1.4 or 1.5GHz). Default clock speed is [email protected]
UV support (under-volting)
I/O schedulers: optimized deadline (default) and noop
Governors: optimized interactive, on demand, conservative, and performance
vfp, vfp3, vfpv3d16, thumb, thumbee, swp, fastmult, edsp, half
USB charging enabled
JRCU implemented - RCU for SMP with a single CPU garbage collector
Auto-group scheduling
Built in cifs, NTFS, Xbox controller, tun, PS3, joystick, mouse support
Encryption features CONFIG_DM_CRYPT, CONFIG_BLK_DEV_CRYPTOLOOP, and CONFIG_KEYS
Stock hardware/software is all working with no known issues (Camera, GPS, WiFi, sound, headphones, sensors, market, video/youtube etc.)
Prerequisites:
ROM must be based on the stock Galaxy Tab 8.9 with TouchWiz (stock and Overcome ROMs have been tested)
ROM must be rooted and have CWM installed.
Make sure you backup your boot.img so you can flash your stock kernel back. You should have a full CWM backup anyhow.
An app like SetCPU if you want to overclock(OC) or under volt (UV). I recommend only overclocking up to 1.4 or 1.5 GHz. Try 1.4 GHz first and see if it works for your tab.
Make sure you download the correct version for WiFi or 3G (3G only supported on Android 3.2).
Make sure you download the correct version for Android 3.1 or 3.2.
Android Honeycomb 3.2
Version v2d for Android HC 3.2
Add "autogroup" scheduling (for some background see: http://www.linuxfordevices.com)
Add support for LUKS and other file encryption utilities (CONFIG_BLK_DEV_CRYPTOLOOP=y and CONFIG_KEYS=y). Ext2 formatted loop devices should work now, but still no luck FAT12 8.3 volumes. Let me know how it works! (thanks ZeroPDA)
Misc merges\bug fixes from Nvidia repo (tegra\video\hdmi fixes, ext4 memory leak fix, interactive gov div\0 fix etc.)
v2d (7310 WiFi) View attachment motley_v2d.zip MD5 640af1d30eff11124f17b7fcb4c6201e
v2d (7300 3G) View attachment motley_v2d_3G.zip MD5 640af1d30eff11124f17b7fcb4c6201e
Version v2c for Android HC 3.2
WiFi only feature addition - added CONFIG_IP_ADVANCED_ROUTER=y to properly support Cisco VPN (VPNC Widget). This was not required for 3G as it already has this kernel feature. Thanks to questionmark for providing the info and testing the change for us.
UV bug fix - v2a introduced a UV issue where it was no longer subtracting the UV values even though they were set properly in sysfs by SetCPU etc. Thanks to Crashdown12 for reporting.
Important - I recommend removing the option to set UV on boot before installing this new version, just in case you were down to unstable voltages.
v2c (7310 WiFi) View attachment motley_v2c.zip MD5 cbfdee00b5ce514bef88e4230f7d0694
v2c (7300 3G) View attachment motley_v2c_3G.zip MD5 bce4881b2716f410b2903f96fe347271
Version v2b for Android HC 3.2
USB charging is now enabled like the GT10.1 (thanks pershoot, stefansaraev). See the following for usage: how-to (thanks dpakrr)
Performance: implemented JRCU, an RCU for SMP with a single CPU garbage collector so that each and every CPU doesn't periodically participate in RCU garbage collection. This is popular in the Android kernel space since dual CPUs have come about (thanks Joe Korty).
Performance: added optimized deadline i/o scheduler which is now the default since it is great for SSD (thanks morfic)
Added switch to turn off TouchWiz at the kernel level (not really relevant until someone tries to build a vanilla ROM)(thanks pershoot)
v2b (7310 WiFi) View attachment motley_v2b.zip MD5 3446574b2024897e41bad69f7c699aca
v2b (7300 3G) View attachment motley_v2b_3G.zip MD5 d299579a1de0d1469bfcb99ed6afc1d4
Version v2a for Android HC 3.2
Same features as v1i kernel, but now works for HC 3.2
Now a version for P7300 3G
v2a (7310 WiFi) View attachment motley_2a.zip MD5 59bfb8b8f213517676e06b6d69f35080
v2a (7300 3G) View attachment motley_2a_3G.zip- MD5 b5b6ab4f3dffe29dce5a83f32dd7eba6
Android Honeycomb 3.1
Version 1.0i changes (current for Android 3.1):
Governor default changed to OnDemand, but only so we can properly set back to the preferred interactive governor on boot using SetCPU and other tools (let me know!).
I/O schedulers: NOOP now the default (minor read/write improvements), CFQ still available, Deadline removed for now.
Starting voltages increased for 1.504 GHz and above due to some instability issues reported. I recommend you UV 25mV or so if you already achieved stability as it was increased by 50mV. Higher than 1.5GHz is still experimental and not recommended. I have been able to run at 1.6GHz for the first time in this build.
v1i - View attachment motley_v1i.zip - MD5 ea77e46967aa4c917e8dd8c429dca724 (current for Android 3.1)
Version 1.0h changes (beta 1):
Touchscreen lag fixed. Firmware downgrades prevented within Melfas touchscreen driver.
UV bug fix, no known issues.
Governor fixes, SetCPU seems to set properly on boot now (edit: still some issues setting on boot depending on SetCPU configuration)
Version 1.0g changes (alpha 2):
Overclock to 1.504GHz+ (only 1.5 is stable, over is experimental only)
UV (undervolt) support (experimental, still in testing)
NTFS and Xbox now built-in. No longer need to mess with loading modules.
Applied some upstream kernel patches.
Version 1.0c (alpha 1/first release):
Based on Samsung open source kernel from opensource.samsung.com
Overclock to 1.2GHz or 1.4GHz (a future version will likely be able to clock to 1.504Ghz)
Installation Instructions
Backup with CWM
Put the zip on your sdcard
Flash zip file from CWM
Install SetCPU and use to set governor to "interactive" and desired OC frequency (recommend 1.4 to start). The default governor has been set to On Demand on purpose even though it is not the recommended governor to use in SetCPU. Setting the recommended interactive governor will help SetCPU trigger the instructions to sysfs causing it to take hold. Sometimes it is finicky and a reboot can help once you have the interactive governor set with your desired frequency.
Optional: if you need or want to restore your original kernel, restore ONLY your boot.img from the CWM advanced recovery option.
Thanks go to:
pershoot for all his hard work on the 10.1 kernel. I used his kernel as a working guide and used his delivery method (Anykernel)
alterbridge86\Overcome for CWM.
Koush for the Anykernel delivery method.
Samsung for releasing the source like they should
Tiamat team, RichardTrip\roggin and NVidia for their open source git repositories.
All the testers!
Let me know if I forgot somebody!
Git repository:
https://github.com/motley-git
FAQ
Q: What is a kernel and why would I need it? How is it different from a ROM?
A: The kernel is the lower level of the operating system, or the engine so to speak. It is a bridge between applications and the actual data processing done at the hardware level. The Android OS utilizes a custom Linux kernel. The stock kernel provided by Samsung limits the CPU clock speed (i.e. CPU frequency) and other functionality that the upper level operating system can request (like mounting NTFS hard disks, undervolting, encrption, using certain joystick controllers, mounting network shares etc.).
A kernel is different from a custom ROM. A ROM is a customized version of the Android Honeycomb OS and will also come with a kernel. Most ROMs will come with the stock kernel, they should designate which kernel they use. In other words, most ROMs provide a customized version of the upper level of the operating system including base services and applications.
Q: What do I have to wipe before I flash?
A: For kernel only flashes, like this one, you don't have to wipe anything.
Q: What does the zip file do when I flash?
A: When the zip is applied in CWM, it does the following things using Koush's AnyKernel method:
Unpacks your boot.img from into a temp folder (into ramdisk and zImage components)
Replaces your zImage, i.e. the kernel binary
Updates the ramdisk default.prop (sets ro.secure=0 for adb root shell and removes init.p3.rc lines that set frequencies and governor during boot)
Repacks the new boot image and flashes back to /dev/block/mmcblk0p3
Updates two kernel modules in the stock location /lib/modules
Q: Will I lose any customizations to my ramdisk provided by a custom ROM?
A: No, your should not due to the use of the AnyKernel method described above.
Q: Will other overclocking apps besides SetCPU work OK?
A: Yes, they should work, but just keep in mind that not all apps are able to under-volt. I will typically be using SetCPU for all my testing, so keep this in mind if you have problems.
Q: Will overclocking use more battery?
A: Yes, higher voltages equals more current draw (I=VR). It will depend upon your setup and individual usage scenarios to how much runtime you will lose.
Using the interactive governor, your tablet will scale down to lower frequencies when the highest clock speed is not necessary. At the lower frequencies, the tablet will not use more power than it does stock.
Q: What OC frequencies are safe?
A: From research thus far, 1.5GHz is the top end for every day use stablity for most tablets. However, due factory tolerances 1.5GHz still may not be stable for everyone. You may need to use 1.4GHz or even 1.2GHz. Many choose to run 1.4GHz since it still gives a great performance bump over stock, but less heat is generated, and it will chew up a little less battery.
Q: I set my OC frequency to X, but I don't think it is working. How do I test to know that it is working?
A: For 1.4-1.5GHz using the interactive governor, you should be able to see a Linpack score between 70-87 depending on what else is running on the tablet.
The ad-free version of Linpack is better because the ads can lower your scores unless you hit test at the right time when the ad is already loaded. If you keep hitting test at 1.5Ghz, your consistent higher scores should be around 78-85.
Verify the clock speed by using Linpack scores
Verify in SetCPU that the different clock speeds are being used periodically, most particularly the highest clock speed.
It is kind of finicky sometimes until you get it set right and sometimes after a new version is installed it will get finicky. After you get it set right, then it stays put on reboot and you should have any issues from there. I am still wondering if there isn't something I can do about it to force it honor any changes SetCPU requests to sysfs no matter what. This is the reason why I eventually set the default governor to On Demand and then suggest that you configure it to be Interactive in SetCPU (the recommended governor). This seemed to help trigger the proper acceptance from SetCPU on boot. Pershoot (the 10.1 kernel guru) suggested that it might be falling to conservative at the default frequency like when it goes to sleep, but not coming back. However,when it goes to sleep and I turn it back on, it always goes back to my 1.5GHz just fine. And when it's set and happy, it never has this issue on boot either. Maybe a second boot is all that it takes, but I would sure like to pin it down and understand it better. Let me know if anyone has any ideas.
If your Linpack scores suggest OC is not working, I recommend that you do the following:
Uncheck the SetCPU setting to "set on boot" for OC and UV settings. Don't set this for boot until you are sure you are good to go with your clock speed and UV settings.
Upgrade to the latest kernel version for your tablet if you haven't already (Choose, HC 3.1 or HC 3.2, then 7300 3G or 7310 WiFi)
Boot up and use SetCPU to set your desired OC frequency AND then setp to use the "interactive" governor.
Verify your linpack scores to make sure they are higher than stock (~50-55). See above reference scores and notes about ads slowing down the scores.
Q: How do I setup under-volting (UV)? What values should I use for each frequency?
A: Not all tablets are created equal at the factory. What works on anothers tablet may not work on yours.
Uncheck the SetCPU setting to "set on boot" for UV settings. Don't set this for boot until you are sure you are good to go with your modified UV settings.
Once the clock speed is verified (see previous question), run some bench marks (Linpack, AnTuTu, and Quadrant are good) and do some multiple-tab browsing sessions to make sure your tablet is stable. Watch some vids or whatever you like to do, this is the key.
If you are stable, step down your voltage at the highest clock speed by -25mV. Repeat the benchmarks and usage scenarios. If it fails (locks the tab), hold down the power key until it reboots and step back up +10mV and repeat until it is stable.
Repeat the UV calibration for the next lower clock speed and so forth. I don't typically mess with anything below GHz since those are stock values.
Q: So, what OC and UV settings do you use?
A: I typically run @1.5GHz -50mV and leave the rest of the frequencies as-is. For my usage, I don't find the CPU spending a lot of time anywhere else besides 216, 312, 1000, and 1504. Every other frequency is typically less than 1% of time in state. If folks can UV further and keep it stable, that is great. I don't worry about battery too much since I am mostly around the house and don't mind charging every 2-3 days.
Q: I noticed that the stock tablet does charge using a normal PC USB port. The tab say discharging with a red x but it seems to be charging. So do I really need to use the usb charging script?
A: I grabbed this fix from the 10.1 kernel base. I was wondering the same thing when I went forward with the code change.
Here is what I know so far. The change in the kernel allows the tablet to properly report the charging state properly back to the OS. After the fix, the USB charging seems to be much faster, but it may just be the reporting mechanism. Before, it would take forever to trickle up 1%. Now it really seems be a viable charging source, but still slower than plugging in to the wall of course. I have not however done any tests to prove this, but I think the mod is definitely worthwhile. Samsung should have done it like this stock, but I think they did not want to deal with support calls to troubleshoot charging via USB as it is not as fast and reliable.
That said, the option is there and folks have a choice on whether to activate it or not. Others, please report back on your experience on this topic.
Any chance this would work on the 3g version?
Great! Can't wait to try it. Any reason it might not work with the overcome ROM?
EDIT: Just tried and it worked with Overcome 1.0.0. Noticeable improvement in landscape mode, buttery smooth in portrait.
Any chance we can undervolt the kernel?
Also, did you apply any optimizations (VFP3/FP/gcc-O etc.)
What is meant by "PS3" support?
KitF said:
What is meant by "PS3" support?
Click to expand...
Click to collapse
I assume it's support for the PS3 Dualshock 3 (which uses Bluetooth)
Hurrian said:
I assume it's support for the PS3 Dualshock 3 (which uses Bluetooth)
Click to expand...
Click to collapse
I highly doubt that. Maybe it supports it over USB.
+1 on this feature added to OC... I feel the stock ROM is too slow...
Hello mr. Motley!
awesome works, applied it to my 8.9" it works really neat both in 1.2 ghz and 1.4 ghz!
thumbs up from denmark!
---------- Post added at 12:52 PM ---------- Previous post was at 12:44 PM ----------
Hello!
haha my antutu benchmark (using overcome 1.2)
1ghz : 4900
1.2ghz: 5607
1.4ghz: 6590
woooom
---------- Post added at 01:24 PM ---------- Previous post was at 12:52 PM ----------
Hi,
at 1.4 ghz - the lockscreen seems to have some issues (it has a 10/15 sec freeze before unlocking)
+1 for the 3G version! Will this one work?
Also, +1 on the PS3 controller support. (Why wouldn't it be able to support Bluetooth? I figured it may be easier that way anyhow. Tell you what though, if it does work, I'm buying a PS3 controller! (I've never had the desire to own a PS3))
Jade Eyed Wolf said:
+1 for the 3G version! Will this one work?
Also, +1 on the PS3 controller support. (Why wouldn't it be able to support Bluetooth? I figured it may be easier that way anyhow. Tell you what though, if it does work, I'm buying a PS3 controller! (I've never had the desire to own a PS3))
Click to expand...
Click to collapse
Because ps3 uses a proprietary bluetooth protocol.
Android 3.1 has built in USB controller support, so ps3 controller should work over USB. If Samsung hasn't messed something up.
Def a long delay on wake up otherwise everything is running fine, thanks!
Def looking forward to a faster OC, would be nice to be able to test up to 1.7 like the Tiamat kernel. A GPU overclock option would be welcome too. Let me know if you need any testers.
Sixaxis app works fine on the 8.9, I use my controller via Bluetooth with my tab just fine. Guess it is good to know there is USB support, too.
alishankiti said:
Any chance this would work on the 3g version?
Click to expand...
Click to collapse
Sorry, but I don't think it has the right kernel options at the moment. Samsung has a separate source download for the GT-P7300 and I have not studied it to see if it is the same source. It may be possible to easily make it happen by using a different configdef to setup the kernel. We'll see about adding support in the future, however I don't have 3G (or even a 3G dongle) to give it a try so others would need to test it. Some of the 10.1 guys might be able to help determine whether this is a mountain or mole hill. If it is the latter, I am happy to give it a try at some point.
CanEpia said:
Great! Can't wait to try it. Any reason it might not work with the overcome ROM?
EDIT: Just tried and it worked with Overcome 1.0.0. Noticeable improvement in landscape mode, buttery smooth in portrait.
Click to expand...
Click to collapse
Thanks for the update, you may be the second person to run this kernel
Hurrian said:
Any chance we can undervolt the kernel?
Also, did you apply any optimizations (VFP3/FP/gcc-O etc.)
Click to expand...
Click to collapse
Yes, voltage control is definitely high on the list after all hardware and annoying glitches are addressed.
vfp and vfp3 are baked in already. I believe they were in the stock kernel already. As far as compiler optimization, I haven't done much playing with that. I tried to use the code sourcery toolchains, but I could never get the damn kernel to boot. I am currently using the Android NDK to compile. I even had to back off a version on these toolchains because it broke WiFi without any other coding changes. It's a very sensitive beast. If anyone has any known and proven compiler optimization for Tegra2 and ARM toolchains, I am happy to give it a try. I know that the toolchains are what do most of the magic for our CPU, so we would have to stick to whatever is supported in the toolchains.
KitF said:
What is meant by "PS3" support?
Click to expand...
Click to collapse
This is for supported the PlayStation 3 controller via USB (kernel option CONFIG_HID_SONY). Kernel option CONFIG_INPUT_JOYDEV is also built-in for supporting other generic joystick devices. I am not an avid gamer, so you guys will need to help out with the testing with this stuff.
All is well @1.4 on Overcome 1.2
Sent from my GT-P7310 using Tapatalk
randomb said:
Hello mr. Motley!
awesome works, applied it to my 8.9" it works really neat both in 1.2 ghz and 1.4 ghz!
thumbs up from denmark!
---------- Post added at 12:52 PM ---------- Previous post was at 12:44 PM ----------
Hello!
haha my antutu benchmark (using overcome 1.2)
1ghz : 4900
1.2ghz: 5607
1.4ghz: 6590
woooom
---------- Post added at 01:24 PM ---------- Previous post was at 12:52 PM ----------
Hi,
at 1.4 ghz - the lockscreen seems to have some issues (it has a 10/15 sec freeze before unlocking)
Click to expand...
Click to collapse
Thanks for testing from Denmark Good thing I posted it last night before bed!
Your lockscreen seems to be much worse than I am experiencing. I get the same 2-3 sec behavior no matter what my cpu speed is. Not sure this why this is different for you. Even if my lockscreen is turned "off", I still get the 3 sec delay on wake. I like a good sleep, but this is a bit more like a drunken coma.
poolguy said:
All is well @1.4 on Overcome 1.2
Sent from my GT-P7310 using Tapatalk
Click to expand...
Click to collapse
Good to hear poolguy, thanks.
Kernel is running nicely, as stated earlier it is about a 2-3 second wait time on the lock screen. The only issue I had is that the CPU was pinned at 1 ghz, this issue was solved by switching governors and then back to interactive. Now scaling nicely. Thanks for this.
Sent from my GT-P7310 using Tapatalk
Looking for some advice as I am still pretty noob-ish. I apologize in advance if this thread is out-of-bounds in any way; every search for answers that I've conducted always seem to beat-around my questions. Any advice will be thanked ASAP, even if you can shoot me a url to the advice I need that would be awesome. If it appears that I'm on top of things that would be great to know as well. Thanks in advance!
I'm running CM7.1.0 Encore Signed emmc with Tiamat v4.1.0 kernel; using Ram Manager Pro for optimization in lieu of task killers, Nook Tweaks for CPU stepping and voltage management, "Antivirus Free" for virus protection, "Battery Calibration" to monitor/obtain max charge (~4200 mV), and "Set DNS" for faster web-based loading. I've also disabled Android Cell-Standby Services through ADB and removed useless apps such as camera and voice apps using Root Explorer. My biggest questions are as follows:
1. Am I running the best kernel for speed and battery saving?
2. What are good voltage settings for better battery conservation (currently on default voltage settings)?
3. Is there really a need for a virus protection, and if so is there something better than what I have?
4. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
5. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
I keep telling myself that I'm probably good to go, but I want to be certain that I've been as thorough as I can be. If anyone does something differently with great results please feel free to advise! As I said before, any advice or even just urls that help with my questions will be thanked. Can't wait to discuss this more!
vessamj said:
Looking for some advice as I am still pretty noob-ish. I apologize in advance if this thread is out-of-bounds in any way; every search for answers that I've conducted always seem to beat-around my questions. Any advice will be thanked ASAP, even if you can shoot me a url to the advice I need that would be awesome. If it appears that I'm on top of things that would be great to know as well. Thanks in advance!
I'm running CM7.1.0 Encore Signed emmc with Tiamat v4.1.0 kernel; using Ram Manager Pro for optimization in lieu of task killers, Nook Tweaks for CPU stepping and voltage management, "Antivirus Free" for virus protection, "Battery Calibration" to monitor/obtain max charge (~4200 mV), and "Set DNS" for faster web-based loading. I've also disabled Android Cell-Standby Services through ADB and removed useless apps such as camera and voice apps using Root Explorer. My biggest questions are as follows:
1. Am I running the best kernel for speed and battery saving?
2. What are good voltage settings for better battery conservation (currently on default voltage settings)?
3. Is there really a need for a virus protection, and if so is there something better than what I have?
4. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
5. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
I keep telling myself that I'm probably good to go, but I want to be certain that I've been as thorough as I can be. If anyone does something differently with great results please feel free to advise! As I said before, any advice or even just urls that help with my questions will be thanked. Can't wait to discuss this more!
Click to expand...
Click to collapse
Sounds like a good setup. You may experience market issues by removing cell service and camera, some apps may not show up. My question is how did you get tiamat's kernel to run on the nook?
bdcrim said:
Sounds like a good setup. You may experience market issues by removing cell service and camera, some apps may not show up. My question is how did you get tiamat's kernel to run on the nook?
Click to expand...
Click to collapse
I'd like to know that as well......
I used Tiamat's latest Evo NON SBC Kernel ( http://tiamat-dev.com/tiamat_evo/ ). After downloading I installed the zip through Clockwork (after wiping both caches) in boot-recovery and I'm guessing it's working fine... what issues have there been with Tiamat's before?
-XDA Premium on CM7 Nook Color
vessamj said:
I used Tiamat's latest Evo NON SBC Kernel ( http://tiamat-dev.com/tiamat_evo/ ). After downloading I installed the zip through Clockwork (after wiping both caches) in boot-recovery and I'm guessing it's working fine... what issues have there been with Tiamat's before?
-XDA Premium on CM7 Nook Color
Click to expand...
Click to collapse
No issues reported, because the only kernels around this forum are Barnes and Noble source. Let us know how the battery life is. Not to question your integrity, but did it stick, showed up in settings, about tablet?
That's a great point. It didn't stick. All seemed well when I installed it but I guess the long pause on the next reboot was from the system restoring the last kernel I had. After looking around some more I came to realize that in order to have control of CPU stepping with Nook Tweaks you must have Dalingrin's 2.6.29 OC Kernel 09/01/11 (http://coachz.inetpro.org/~dalingrin/nook/kernels/090111/) or later. So that's fixed.
Meanwhile my battery is only good enough that I have to charge it at the end of every day under normal use, sometimes earlier.
After that, my list of questions fall to:
1. What are good Nook Tweaks voltage settings for better battery conservation (currently on default voltage settings)?
2. Is there really a need for a virus protection, and if so is there something better than what I have?
3. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
4. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
-XDA Premium on CM7 Nook Color
vessamj said:
That's a great point. It didn't stick. All seemed well when I installed it but I guess the long pause on the next reboot was from the system restoring the last kernel I had. After looking around some more I came to realize that in order to have control of CPU stepping with Nook Tweaks you must have Dalingrin's 2.6.29 OC Kernel 09/01/11 (http://coachz.inetpro.org/~dalingrin/nook/kernels/090111/) or later. So that's fixed.
Meanwhile my battery is only good enough that I have to charge it at the end of every day under normal use, sometimes earlier.
After that, my list of questions fall to:
1. What are good Nook Tweaks voltage settings for better battery conservation (currently on default voltage settings)?
2. Is there really a need for a virus protection, and if so is there something better than what I have?
3. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
4. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
-XDA Premium on CM7 Nook Color
Click to expand...
Click to collapse
Sounds like your battery drains about normal. I lose around 12 to 15% per hour, always have. I have tweaked the voltage some, but did not see much of a result. There is is no need for virus protection that I am aware of. I have not seen a single thread on that issue (I have been around this forum for a year)
I can't advise on any DNS settings. You may want to play with the voltage some and see if that makes any difference on battery life. By the way, there is an updated kernel in the development forum in MiRaGe's kang build. Look for it in the OP. Also his build, for me, is the fastest and most responsive that I have used. Good luck.
bdcrim said:
Sounds like your battery drains about normal. I lose around 12 to 15% per hour, always have. I have tweaked the voltage some, but did not see much of a result. There is is no need for virus protection that I am aware of. I have not seen a single thread on that issue (I have been around this forum for a year)
I can't advise on any DNS settings. You may want to play with the voltage some and see if that makes any difference on battery life. By the way, there is an updated kernel in the development forum in MiRaGe's kang build. Look for it in the OP. Also his build, for me, is the fastest and most responsive that I have used. Good luck.
Click to expand...
Click to collapse
Thanks for the advice... I'll look up the kernel and see how it goes.
1) There's some voltage stuff listed here
2) I don't use any, it seems to me like most malware is centred around phones anyway. I just use Droidwall to block internet access for anything shady-lookin'. LBE lets you block more permissions, or CM7 will too, but with no SIM, no mobile data, no GPS, there is just not as much to be concerned about on the nook . Basically, being aware of what Permissions are, and checking them, should keep you safer than relying on a faceless, profit-motivated company.
www.theregister.co.uk/2011/11/21/mobile_security_dust_up/
4) If you're interested, Tasker can be used to under/overclock any app. So, your flashy game will run at 1200, your simple text reader at 800, and so on.
selection16 said:
1) There's some voltage stuff listed here
2) I don't use any, it seems to me like most malware is centred around phones anyway. I just use Droidwall to block internet access for anything shady-lookin'. LBE lets you block more permissions, or CM7 will too, but with no SIM, no mobile data, no GPS, there is just not as much to be concerned about on the nook . Basically, being aware of what Permissions are, and checking them, should keep you safer than relying on a faceless, profit-motivated company.
www.theregister.co.uk/2011/11/21/mobile_security_dust_up/
4) If you're interested, Tasker can be used to under/overclock any app. So, your flashy game will run at 1200, your simple text reader at 800, and so on.
Click to expand...
Click to collapse
Thanks! I'm definitely gonna purchase Tasker now, as I've been looking at it for a while... and I'll check out the voltage and the security links for sure.
selection16 said:
1) There's some voltage stuff listed here
2) I don't use any, it seems to me like most malware is centred around phones anyway. I just use Droidwall to block internet access for anything shady-lookin'. LBE lets you block more permissions, or CM7 will too, but with no SIM, no mobile data, no GPS, there is just not as much to be concerned about on the nook . Basically, being aware of what Permissions are, and checking them, should keep you safer than relying on a faceless, profit-motivated company.
www.theregister.co.uk/2011/11/21/mobile_security_dust_up/
4) If you're interested, Tasker can be used to under/overclock any app. So, your flashy game will run at 1200, your simple text reader at 800, and so on.
Click to expand...
Click to collapse
Would you be willing to share a profile for 4) as this is exactly what i am trying to do with no luck thus far. Thank you.
gsutton said:
Would you be willing to share a profile for 4) as this is exactly what i am trying to do with no luck thus far. Thank you.
Click to expand...
Click to collapse
This is where I got the info;
http://tasker.wikidot.com/cpu-profiles-governor-frequency-control
Hello.
I've got a stock Android 3.2.1 (A501 4.066.29 COM GEN1) rooted with Stock/HV/Taboonay V3.7 for HC 3.2 16-10 - 1.64Ghz/UV control kernel.
The question is:
how to set cpufreq parameters (governor, max_freq,..) WITHOUT using 3rd party apps so that the parameters were restored after reboot.
Thank you for reading this.
Either the kernel needs to support init.d scripts or a service needs to execute on boot.
That kernel doesn't support init.d and Voltage Control has a startup service.
CuriousTech said:
Either the kernel needs to support init.d scripts or a service needs to execute on boot.
That kernel doesn't support init.d and Voltage Control has a startup service.
Click to expand...
Click to collapse
Forgive my ignorance but I can't put to use your answer.
I don't get where is Voltage Control and what I have to do.
Get Voltage Control from the market, make adjustments, save as boot. You'll be given the option to save as init.d script or startup service.
Well.. I tested it. Odd app.
First of all it can see only one core. It's funny. After reboot cpu0 works in conservative mode, max_freq 1.4 GHz and cpu1 in ondemand mode, 1.0 GHz.
I tried to edit init.d script and add the 2nd core but after reboot cpu worked with the default kernel values - script didn't work at all.
Moreover Voltage Control shows voltages turned upside down - the less cpu frequency the bigger voltage values. I fear to use this app
Download setcpu or antutu cpu master it recognizes dualcore , has the boot option
More education would be advised To you PLEASE DONT BREAK YOUR TABLET
Please do not take this the wrong way..
it does sound like you do not know what your doing.. I suggest you read more about over clocking./under voltage of a TEGRA 2 DEVICE.. That will get you more understanding about what you need to do. And maybe even help you decide if you really want to do this or not.. There is alot of resources online about this subject. I have tried custom kernel with set cpu.. I use it on my 650 mhz phone. clock it to 768. but it has a huge battry issue when running at that speed.Not to mention It would be dangerous to leave it on my purse with something running might be a fire bug.. GOOD LUCK .
Basically lower voltage at higher frequencies keeps the CPU stable. Leaving it linear would increase temperature exponentially.
Script Manager can run scripts on startup but I don't know how you could disable them if they keep it from starting up.
I didn't know about VC and dual core though. My bad.
ef1x said:
Download setcpu or antutu cpu master it recognizes dualcore , has the boot option
Click to expand...
Click to collapse
Thank you.
I tried all cpu related apps from the Market that I was able to try. Now I want to try to get along without them.
erica_renee said:
Please do not take this the wrong way..
it does sound like you do not know what your doing.. I suggest you read more about over clocking./under voltage of a TEGRA 2 DEVICE.. That will get you more understanding about what you need to do. And maybe even help you decide if you really want to do this or not.. There is alot of resources online about this subject. I have tried custom kernel with set cpu.. I use it on my 650 mhz phone. clock it to 768. but it has a huge battry issue when running at that speed.Not to mention It would be dangerous to leave it on my purse with something running might be a fire bug.. GOOD LUCK .
Click to expand...
Click to collapse
Thank you Erica
I don't understand? You want something that does the same thing but you don't want to know it's there?
I found one app called System Tuner that lets you adjust CPU frequencies individually. I don't know why though.
CuriousTech said:
Script Manager can run scripts on startup but I don't know how you could disable them if they keep it from starting up.
Click to expand...
Click to collapse
Thank you but it looks too bulky for such a small task. And I still don't want to use 3rd party apps
CuriousTech said:
I don't understand? You want something that does the same thing but you don't want to know it's there?
I found one app called System Tuner that lets you adjust CPU frequencies individually. I don't know why though.
Click to expand...
Click to collapse
Actually I don't like how these apps work. And I thought that setting up a few parameters would't be difficult. It seems I was wrong.
Yep. Code has to execute to do stuff, otherwise that stuff doesn't get done.
System Tuner Pro allows voltage adjustments on overclock settings. If you're interested. Also, has a lot of packages integrated into one (task manager, app freezer, etc). They have a free version in the Market if you're interested. It's nice to have several apps, in one nice package.
Moscow Desire
Thank you but I actually don't need it anymore
I have rolled back to the stock kernel because of constant "sleep of death" issue.
huck_d said:
Moscow Desire
Thank you but I actually don't need it anymore
I have rolled back to the stock kernel because of constant "sleep of death" issue.
Click to expand...
Click to collapse
It's because the 3.7 kernel you used, is really not compatible with the a501. The ultra-low voltage causes "screen freeze" and the "sleep of death" when under 3g only. It's a known issue with the 501 and 3.6 and 3.7 kernels also. I would reccommend RTrips 3.4+. Probably his best for for a501.
I ship it with my own Alexandra II and III rom. No issues with it, and none ever reported.
Had I noticed when I woke this morning, you had an a501, I could have given this advice. Sorry, didn't have enough coffee
---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------
Moscow Desire said:
It's because the 3.7 kernel you used, is really not compatible with the a501. The ultra-low voltage causes "screen freeze" and the "sleep of death" when under 3g only. It's a known issue with the 501 and 3.6 and 3.7 kernels also. I would reccommend RTrips 3.4+. Probably his best for for a501.
I ship it with my own Alexandra II and III rom. No issues with it, and none ever reported.
Had I noticed when I woke this morning, you had an a501, I could have given this advice. Sorry, didn't have enough coffee
Click to expand...
Click to collapse
The problem, is that a lot of dev's, don't have a501's, only a500's. So they really can't test a lot on it. And sometimes, the issue doesn't happen for 2 or 3 days. Sometimes less. I'm going to experiment a little this weekend, with some of the newer kernels, and mess with the voltage's and see if I can get it stabilized where it doesn't freeze on 3g only.
Moscow Desire ,
Thanks for clearing it up and the advise. I'll try either 3.4 kernel or your ROM.
huck_d said:
Moscow Desire ,
Thanks for clearing it up and the advise. I'll try either 3.4 kernel or your ROM.
Click to expand...
Click to collapse
If you go to RichardTrips kernel thread, you will see a link to his older kernels.
You will find the 3.4 listed on his server. I think you just need to flash it, although I usually dump Dalvak cache.
Alex II is an easy install. Alex III (3.2.1) is a little more ... interesting to install, but not difficult. If you run into an issue, post it in my thread. Everybody else has got it installed, so I think you'll have no issues either.
It's the only "certified" 3.2.1 for the Acer a501 that I know if. Not that the other roms are bad, because they really are good, but, the 3.2.1 they advertise, are from system dumps after running an update, or adding missing files to a 500 rom. The TMPL is an Acer release.
Like the title says, I was just wondering if there was a way to change the default CPU speed on boot permanently? I know I can use SetCPU, but sometimes that hasn't held through a boot and I had to set the speed manually. So, I was hoping there was just some script somewhere I would have to change. But then I got to wondering, would that be possible from my phone? Would I have to build my own kernel? Or would I just be able to decompile the rom in dsixda's kitchen to change a kernel script? Any help is greatly appreciated!
I use ROM Toolbox. It has a ton of stuff including CPU Control and CPU Profiles (like to make it 691MHz max when the screen is off). And you get a lot of other stuff with ROM Toolbox. But you could say the CPU part is like Set CPU. Don't really know if this answered your question. Hope I helped though.
I'm pretty sure CM7 has a built in CPU setting feature in its Cyanogenmod Settings -> Performance menu. It gives you the option to set on boot as well. I've never played around with it so I'm not sure if it'll give you the same problems you're describing now, but it's worth a shot if you don't want the separate app.
Is your phone rooted?
Sent from my Black Ice'd Glacier using XDA App
c707h3j said:
I'm pretty sure CM7 has a built in CPU setting feature in its Cyanogenmod Settings -> Performance menu. It gives you the option to set on boot as well. I've never played around with it so I'm not sure if it'll give you the same problems you're describing now, but it's worth a shot if you don't want the separate app.
Click to expand...
Click to collapse
I think I remember this too.
--sent from my glacier.