[KERNEL]Netarchy Nexus for NS + NS4G (22-Oct-2011) Testing: 1.4.1
- Thread starter netarchy
- Start date
- Status
I've created the script also... in system/etc/init.d/ with the name deep-idle_on.sh
and the script is running fine if i run it manually! but at boot it won't run...any idea why?
The permissions are also set properly...
a litle help would be nice
casca said:I've created the script also... in system/etc/init.d/ with the name deep-idle_on.sh
and the script is running fine if i run it manually! but at boot it won't run...any idea why?
The permissions are also set properly...
a litle help would be nice
Depending on your kernel, processing of /etc/init.d scripts may not have been enabled. This is the case in lean roms like Blandroid and Bugless Pete's (at least for the NS). In these cases, try installing Netarchy's kernel for stock roms after doing whatever backups/restores you need to.
At least for me, this led to an /init.rc that has init.d processing turned on.
Hope this helps,
- chris
thank you for your help!
well, I'm running latest oxygen + netarchy "universal" kernel 1.4.1 CFS
I'm assuming it has the scripts enabled right?Is there a way to check for it or manually enabling it?
tks once again
casca said:
Well a good way to check is to try to add a new script and see if it runs
To make absolutely sure, you could add a line to an existing init script that has side effects like:touch /sdcard/inittest
After a reboot, if the file inittest isnt on your sdcard, your init scripts probably aren't being run.
I found that the kernel for stock roms takes care of enabling this support. It may be a better option than hacking your init.rc yourself. As long as you do a backup first it should take about 10 minutes to try.
- chris
thank you for the idea mate!
well, I have simply added at the end of a "99complete" file that exists in /etc/init.d , that already had some commands in it, the line
echo "1" > /sys/class/misc/deepidle/enabled;
and... it works
that was easy...lol didn't occur that...if they are part of the rom and the rom is working... I'll simply add what I need on the existing files, no need for .sh script files (i think lol)
Thank you for all your help!
well, I have simply added at the end of a "99complete" file that exists in /etc/init.d , that already had some commands in it, the line
echo "1" > /sys/class/misc/deepidle/enabled;
and... it works
that was easy...lol didn't occur that...if they are part of the rom and the rom is working... I'll simply add what I need on the existing files, no need for .sh script files (i think lol)
Thank you for all your help!
Last edited:
Yes undervolting can cause reboots. Also the custom rom.
Sent from my Nexus S using XDA Premium App
It is anything 2.3.4 or newer, hence the 2.3.4+ mentioned. Basically, all recently updated roms *should* work, unless you are Ezekeel and sticking with CM 7.0.3 which is 2.3.3 and would require an older kernel.
Sent from my Nexus S
Can't enable deepidle by going through the /sys/class/misc/deepidle and editing the file. It causes Root Explorer to force-close.
First, regarding Root Explorer, did you mount in r/w mode?
If you want to avoid Root Explorer, try either the long winded init script method below or install (https://market.android.com/details?id=mobi.cyann.nstools):
Push something like what's below as a text file to /etc/init.d/. I called mine 96deepidle. You do have to go in as root and change the permissions to at least 750. I also matched the owner:group the those of the other files in init.d. To push a file to the phone using adb, use
Code:
adb push localfile remotefile
Code:
#!/system/bin/sh
#96deepidle
echo 1 > /sys/class/misc/deepidle/enabled- Push the below text as a file to /etc/init.d/
- Either use a terminal emulator on the phone or use adb shell to get to a shell
- Make sure you are root. If the prompt is $, you aren't root. If it's #, then you are root. You can also use the command whoami to determine your user.
- cd into /etc/init.d
- Run
Code:
chmod 750 96deepidle - Run
orCode:
chown root:shell 96deepidleCode:chgrp shell 96deepidle - Reboot
- Return to a shell as before
- Run
Code:
cat /sys/class/misc/deepidle/enabled - If that returns 1, you are all set, if it returns 0, something went wrong
Last edited:
More explanation than I needed, but thanks, I'll try using an init.d script to enable deepidle, assuming it doesn't cause any problems while trying it out.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
143Netarchy Nexus represents my foray into the world of kernel development for the Nexus S, having previously been working on kernel builds for the Evo 4g.
*Standard Disclaimer: All packaged builds are provided with no guarantees as to their safety. By flashing, you assume any and all potential risks that running a custom kernel might entail.*
*A note to overclockers: If your phone is unstable when running an overclock speed, your particular phone probably can't handle that overclock and you should choose a lower clock.*
All kernel builds mirrored HERE.
*It is generally a good idea to wipe Cache and Dalvik-Cache when flashing a new kernel build to avoid certain problems usually related to Dalvik-Cache*
Downloads:
Experimental Version: 1.4.1 (These are testing builds that are more likely to have issues)
2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.4.1-cfs (For stock 2.3.4 or higher roms)
Netarchy Nexus - 1.4.1-cfs-universal (Universal for non-stock 2.3.4 or higher roms)
BFS BUILDS:
Netarchy Nexus - 1.4.1-bfs (For stock 2.3.4 or higher roms)
Netarchy Nexus - 1.4.1-bfs-universal (Universal for non-stock 2.3.4 or higher roms)
"Stable" Version: 1.3.7
2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.3.7-cfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
BFS BUILDS:
Netarchy Nexus - 1.3.7-bfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-bfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)23Code:Changelog: Revision 1.4.1: - Updated Ezekeel's Touchkey Dimmer to version 3.0 bugfix 4 - Integrated Ezekeel's Deep Idle mod, current to bugfix 5 - 45,333 rabid naked bunnies were harmed during the making of this kernel Revision 1.4.0: - Revert a patch that caused random reboots in certain usage situations - Added Ezekeel's backlight dimmer sysfs interface (See instructions in second post on how to use) Revision 1.3.9: - Return to Deadline as default IO scheduler, using BFQ v2 could cause bugged encounters such as a never ending boot - Applied kernel tweaks from the recent 2.3.5 OTA (mostly relevant for sprint users) Revision 1.3.8: - BFQ updated to BFQv2-r1 - Some build options that may have contributed to random reboots have been modified Revision 1.3.7: - Voodoo Sound driver updated to v10 - Testing out tiny rcu - Touchscreen tweaks are no longer applied by default on boot. Users can still custom tweak touchscreen settings if desired by editing /system/etc/init.d/98touchscreen and rebooting as before. Revision 1.3.6: - Wifi driver changes, rolled back some code that was causing problems - Added Cyaniris' touchscreen tweaks back in the form of a user customizable sysfs interface (courtesy of work by Cyaniris). Users can set custom values by editing /system/etc/init.d/98touchscreen , followed by a reboot for the changes to take effect. Currently the default values are set, users that find the defaults not optimal might want to try some suggested settings by Cyaniris of 35 for touchthr, and 20 for noisethr. - Corrected a bug that would have caused reboots and/or other assorted badness when having the phone sleep at a frequency other than 800mhz (Confession: I was an idiot and forgot to move over this fix from my 2.3.3 kernel trees when making the new kernel trees for 2.3.4, woops!) Revision 1.3.5: - Wifi driver updates, bugfixes - JHash3 Added - Cpu cache clearing fixes - New compiler toolchain for builds, using gcc 4.5.2 - Interactive governor adjustments - IO scheduler set to Deadline, seems to have a nice balance in performance Revision 1.3.4: - Remove touchscreen adjustments for now, they were causing problems on some phones. Touchscreen tweaks will be revisited for a future build - Add auto group process scheduler for CFS builds Revision 1.3.3: - Touchscreen adjustments that may improve touch response - Update Voodoo Sound driver to version 9 Revision 1.3.2: - Update BFS builds to BFS404 - Add Simple IO Scheduler and set as default Revision 1.3.1: - Smartass screen-off speed adjusted to address unresponsive programs during screen-off - Smartass adjustments to improve responsiveness - SLQB slab allocator added to help optimize memory allocation performance - Some build configuration changes that may improve overall feel - Ondemand governor up threshold adjusted to improve battery usage while still maintaining responsiveness Revision 1.3.0.12: - Adjustments to smartass to improve performance (there is probably still room for improvement) - Default I/O Scheduler set to CFQ (previously BFQ), this may prove to be more stable in certain situations - Some adjustments made to the CFS scheduler that may result in a better overall feel to CFS builds Revision 1.3.0.11: - Added Smartass Governor (Not enabled by default, use setcpu or CM's cpu performance settings to change if you want to try it out) - Raised voltage cap to 1600mV for crazy people that want to turn their phone into a reactor ;D - Set config options in 2.3.4 kernel builds that should enable NS4G compatibility for our newly arriving sprint friends. Welcome to club nexus ;D Revision 1.3.0.10: - Update kernel base to 2.6.35.13 - Excessive stuttering in apps such as Gun Bros should be resolved or significantly improved; some problems with memory handling were introduced in 2.6.35.12 and are resolved in .13 Revision 1.3.0.9: - The cause of super-lag has been found (Big thanks to twitch153 for helping me test) - Introducing Universal builds! These universal builds are designed to be flashed on any non-stock rom of the series marked (ie; Universal 2.3.3) - Misc other tweaks to the kernel config that may result in an even smoother overall experience Revision 1.3.0.8a: - Fix issue preventing USB debugging (and adb), and sdcard space from working Revision 1.3.0.8: - Updated to support the 2.3.4 rom update - Lots of updates from upstream, including components needed to support the forthcoming nexus s 4g (yes that means that I will be supporting the ns4g) - Back to the 2.6.35.12 kernel base, the sdcard tweak has been scaled back as it appears to have been causing excess lag - BLN work for i9023 models from akent included (not tested), i9023 users may find they can now use BLN Revision 1.3.0.7: - Revert back to 2.6.35.11 base until I can track down the cause of ridiculous lag in the .12 base (Not that .11 was a bad performer by any means ;D) - BFS builds updated to BFS401 - BFS users should find that they have regained their bootanimation Revision 1.3.0.6: - Voodoo driver updated to v8 - Custom voltage sysfs interface has changed, the method used in 1.3.0.4 and 1.3.0.5 is not compatible. See the guide in the 2nd post for details on the new method. Revision 1.3.0.5: - Raised max voltage cap by 50 mV for people who want to try raising the voltage a little bit on 1.4ghz - More tweaks to try and address instances of "super-lag" Revision 1.3.0.4: - Corrected a bug that could cause a slightly higher voltage to be used at certain speeds (resulting in slightly faster battery drain) - Added a sysfs interface for manipulating voltage levels at various speeds, see 2nd post for details (read: this allows the possibility of custom under/over volting in realtime) - Used a different build configuration that may address the occasional "super-lag" that appeared in 1.3.0.3 Revision 1.3.0.3: - Update kernel base from 2.6.35.11 to 2.6.35.12 - Updated BFS version from BFS 363 to BFS 400 (BFS builds only) - Raised default read-ahead value from 128 to 2048 (read: sd speed tweak built-in, scripts not necessary) Revision 1.3.0.2: - Updated Voodoo Sound driver to version 7 - Fixed a bug that made the sysfs file "scaling_available_freqs" not exist Programs that must read this file for discovering/controlling available cpu speeds can now do so. (This also means that CM7 users can set their cpu speeds from the cyanogenmod performance settings instead of having to use SetCPU) Revision 1.3.0.1: - Add initial BLN support (Currently only functional on SAMOLED models [i9020]) Download the BLN control app from the market to use BLN functionality Revision 1.3.0.0: - More adjustments to the default colours to try and de-smurf the previous adjusted defaults while still avoiding "Yellow tint shock" - Voodoo sound updates (see github commit if you want more details) - Fixed a bug that caused boot times to take significantly longer than necessary Revision 1.2.9: - Voodoo Sound v5 driver update - Adjust default colours to avoid the initial "Yellow tint shock" Revision 1.2.8: - Voodoo Color gamma fix Revision 1.2.7: - Voodoo Color driver updates/fixes Revision 1.2.6: - Bring panel code up to date with official kernel - Update Voodoo Color driver to v2 - Release initial cm7 2.3.3 compatible builds Revision 1.2.5: - Add 2.3.3 compatible builds - Incorporate many updates from the newer 2.3.3 kernel sources, including wifi driver updates, touchscreen updates, drivers for future SLCD nexus-s variants, and more (far too many bugfixes and updates to list, review the commit list on my github if you want details) - Ext4 tweak should be working again in stock builds Revision 1.2.4: - Add NFS modules - Make TUN built-in rather than modular (this may address issues some have had loading the driver) - Add Voodoo Color Revision 1.2.3: - Update kernel base to 2.6.35.11 - Removed the ~56fps cap - Conservative governor tweaked to perform better for users that choose to use it - Greater rom compatiblity, particularly with roms that use specialized init scripts Revision 1.2.2: - 1.3ghz and 1.4ghz added to the frequency table for overclockers - Default cpu speed on boot is 1000mhz, use a tool such as SetCPU to overclock (No doubt I'll get some flack for this, but it's a very bad idea to boot into the max possible overclock when not all phones can tolerate it, so I consider it a necessary evil) - Interactive Governor added, use a tool such as SetCPU to change to it if you want to try it out (Probably needs a bit of tuning to avoid annihilating battery, we shall see) - CFS and BFS variants are now available - Infused with the power of 1000 rabid naked bunnies Revision 1.2.1: - Ext4 hack should be working properly now Revision 1.2: - Fixed a condition where limiting max speed to 1000 would result in potential underclocking to 800 (Thanks DebauchedSloth) - Set hi-res timer to 1000hz - Gave a little more power to the cpu at 1.2ghz, this may help those having trouble running at 1.2 be more stable - Integrated ext4 hack into the ramdisk builds (ext4 hack is not technically a kernel issue but worth pointing out) Revision 1.1: - 1.2ghz overclock *really* works now -Thanks for the help Morfic- - Cpu policy fix to avoid crashes with SetCPU and screen off profiles (Courtesy of work by coolbho3000) Revision 1.0: - Initial release - Add BFS scheduler - Add 1.2ghz overclock - Add BFQ - Add Voodoo Sound driver - Add CIFS support - Add TUN support - Update kernel base to 2.6.35.10
Custom Under/Over volting 101:
Code:**As of 1.3.0.6 the method of custom voltage control has changed, read carefully!** It is now possible for users to define custom levels of under/over volting via a new interface in sysfs. The interface file in sysfs can be found at /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table By default, the custom values are all zeroed out, so a ` cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ` will show: 1400mhz: 1450 mV 1300mhz: 1400 mV 1200mhz: 1350 mV 1000mhz: 1250 mV 800mhz: 1200 mV 400mhz: 1050 mV 200mhz: 950 mV 100mhz: 950 mV Modification of voltages is possible by echoing a string of 8 values to the sysfs interface via the console, where the order of values goes left to right from highest frequency affected to lowest. To adjust the mV for a particular higher or lower than the default, echo values divisible by 5 like in the following example from an adb shell (this is JUST an example, not guaranteed working values ;D): ` echo "1500 1400 1325 1275 1200 1050 900 850" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ` Which has the following effect when examining UV_mV_table: 1400mhz: 1500 mV 1300mhz: 1400 mV 1200mhz: 1325 mV 1000mhz: 1275 mV 800mhz: 1200 mV 400mhz: 1050 mV 200mhz: 900 mV 100mhz: 850 mV Rom developers, you can conceivably create custom scripts to apply various under/over volt settings For reference, these are the default voltages: Default Frequency Voltage Table: 1400mhz: 1450 mV 1300mhz: 1400 mV 1200mhz: 1350 mV 1000mhz: 1250 mV 800mhz: 1200 mV 400mhz: 1050 mV 200mhz: 950 mV 100mhz: 950 mV Additionally, there is currently a safety cap of 1600mV for max voltage, setting a value higher than 1600mV will currently not have an effect greater than 1600mV. (Read: You can set a value higher than 1600, but it will get dropped to 1600 behind the scenes) This can be altered for future builds if I get feedback asking for it.
Backlight Dimmer:
FAQ:
Code:Q: I'm getting a "Device or Kernel version not supported" error in Voodoo Control Plus! A:The error is referring to the generic modules that voodoo control plus comes with to support kernels that don't already have voodoo built-in (such as a completely stock kernel). You can safely ignore this error, as voodoo is already built into the kernel. Q: I'm getting SOD's (Sleep of Death) when undervolting! A: You are probably undervolting too far Q: OMG I'm getting a black screen (no boot animation) when booting a 2.3.3-based rom! A: This tends to happen mostly on BFS builds, though it *can* occur on cfs builds (and even on the stock kernel). The exact cause of this glitch is not known at this time, however, it is purely cosmetic. You will notice that the bottom buttons are lit, and if you were to run adb logcat, you will see that the phone is active. The phone is actually booting, just be patient. Q: What are BFS and CFS? A: They are task schedulers (they determine what processes get cpu time, how much, etc). CFS (Completely Fair Scheduler) is the default scheduler in the official mainline kernel. It's a tried, tested, stable scheduler. BFS (Brain **** Scheduler) is a third party scheduler written by Con Kolivas that must be patched into the kernel, and replaces the CFS scheduler. It tends to be faster in certain tasks, and is usually pretty stable, but sometimes there can be performance quirks.97Edit: Proton now lives in its own thread - http://forum.xda-developers.com/showthread.php?t=1091382
Please use it instead of this thread for app related posts.
Here it is! Proton Voltage Control for Nexus S phones running a supported version of Netarchy kernels (1.3.0.6 and up)
Download here: http://download.jonathongrigg.com/apps/ProtonVoltageControl.apk
Or a mirror here (in case my server goes down under load...): http://dl.dropbox.com/u/9751350/ProtonVoltageControl.apk
Edit: 0.1.1 fixes no space issue, download here: http://download.jonathongrigg.com/apps/ProtonVoltageControl-011.apk
[Mirror] http://dl.dropbox.com/u/9751350/proton/ProtonVoltageControl-011.apk
Usage
Enter in the string of 8 voltages into the text box, then press apply (and optionally 'set on boot').
- It is easier to press one of the 3 voltages buttons to give you a base to work on
- The suggested voltages is a -25mV reduction across the board, similar to what is used in Ogdobber's Sabai Dee kernel I believe
- 'Save on Boot' creates an init.d script called proton_voltage_control with your entered values, so don't be alarmed if you see an extra init.d script
A better UI and more improvements are coming, but this is a fully working, stable UV app!
Enjoy!
