[APP] NSTools v1.16 for managing various Ezekeel's MOD and tweaks

FadeFx · May 14, 2012 at 7:32 PM

se7enthson said:
Thanks. Without any negative Character? Means charging in car and pc USB ports? It does not affect the charging with original Samsung Chargingdevice?

Actually i think it wont charge faster on PC USB port as that only delivers 500ma. However if u use a USB wall charger in some cases it is detected as Pc USB port and thus enable slow charging mode despite the charger could deliver more power. In this case enabling fast charge helps u charge faster as it will be forced to AC mode. But sideeffect is that fast charge will disable USB data transfer.

------------------------------
tapatalked from Galaxy S

loonieryan · May 16, 2012

I'm on the 2012-05-15 nightly build of CM9 and I've encountered a bug with NSTool 1.16. I have it set to use init.d script to set on boot but the 99nstools script inside the /etc/init.d folder is 0 bytes and completely empty.

Any ideas? Here is my logcat:

Code:

D/NSTools.SettingsManager( 8263): write to init.d script
D/NSTools.SysCommand( 8263): mount -o remount,rw /dev/block/platform/s3c-sdhci.0/by-name/system /system
D/NSTools.SysCommand( 8263): echo a > /etc/init.d/99nstools
D/NSTools.SysCommand( 8263): chmod 0777 /etc/init.d/99nstools
D/NSTools.SysCommand( 8263):
D/su      ( 9675): 10103 mobi.cyann.nstools executing 0 /system/bin/sh using shell /system/bin/sh : sh
E/NSTools.SettingsManager( 8263):
E/NSTools.SettingsManager( 8263): java.io.IOException: write failed: ENOSPC (No space left on device)
E/NSTools.SettingsManager( 8263):       at libcore.io.IoBridge.write(IoBridge.java:452)
E/NSTools.SettingsManager( 8263):       at java.io.FileOutputStream.write(FileOutputStream.java:187)
E/NSTools.SettingsManager( 8263):       at java.io.OutputStreamWriter.flushBytes(OutputStreamWriter.java:167)
E/NSTools.SettingsManager( 8263):       at java.io.OutputStreamWriter.close(OutputStreamWriter.java:140)
E/NSTools.SettingsManager( 8263):       at mobi.cyann.nstools.SettingsManager.saveToInitd(SettingsManager.java:483)
E/NSTools.SettingsManager( 8263):       at mobi.cyann.nstools.MainActivity.onDestroy(MainActivity.java:187)
E/NSTools.SettingsManager( 8263):       at android.app.Activity.performDestroy(Activity.java:4629)
E/NSTools.SettingsManager( 8263):       at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1079)
E/NSTools.SettingsManager( 8263):       at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3222)
E/NSTools.SettingsManager( 8263):       at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3253)
E/NSTools.SettingsManager( 8263):       at android.app.ActivityThread.access$1200(ActivityThread.java:132)
E/NSTools.SettingsManager( 8263):       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1190)
E/NSTools.SettingsManager( 8263):       at android.os.Handler.dispatchMessage(Handler.java:99)
E/NSTools.SettingsManager( 8263):       at android.os.Looper.loop(Looper.java:137)
E/NSTools.SettingsManager( 8263):       at android.app.ActivityThread.main(ActivityThread.java:4575)
E/NSTools.SettingsManager( 8263):       at java.lang.reflect.Method.invokeNative(Native Method)
E/NSTools.SettingsManager( 8263):       at java.lang.reflect.Method.invoke(Method.java:511)
E/NSTools.SettingsManager( 8263):       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/NSTools.SettingsManager( 8263):       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/NSTools.SettingsManager( 8263):       at dalvik.system.NativeStart.main(Native Method)
E/NSTools.SettingsManager( 8263): Caused by: libcore.io.ErrnoException: write failed: ENOSPC (No space left on device)
E/NSTools.SettingsManager( 8263):       at libcore.io.Posix.writeBytes(Native Method)
E/NSTools.SettingsManager( 8263):       at libcore.io.Posix.write(Posix.java:178)
E/NSTools.SettingsManager( 8263):       at libcore.io.BlockGuardOs.write(BlockGuardOs.java:191)
E/NSTools.SettingsManager( 8263):       at libcore.io.IoBridge.write(IoBridge.java:447)
E/NSTools.SettingsManager( 8263):       ... 19 more
D/NSTools.SysCommand( 8263): mount -o remount,ro /dev/block/platform/s3c-sdhci.0/by-name/system /system

loonieryan · May 20, 2012 at 4:42 AM

Version 1.16 has the Fast Charging option but does not write anything for that into the init.d script so the option selection just resets upon reboot.

Any chance to get a bug fix for that?

arifhn · May 21, 2012 at 4:15 AM

loonieryan said:
I'm on the 2012-05-15 nightly build of CM9 and I've encountered a bug with NSTool 1.16. I have it set to use init.d script to set on boot but the 99nstools script inside the /etc/init.d folder is 0 bytes and completely empty.

Any ideas? Here is my logcat:

write failed: ENOSPC (No space left on device)

it seems your system partition is full, can you try to create/copy a file into /system with other app (root explorer)

loonieryan said:
Version 1.16 has the Fast Charging option but does not write anything for that into the init.d script so the option selection just resets upon reboot.

Any chance to get a bug fix for that?

it is intended behaviour, do you think it is good to enable fast charge every time?
i think you only need it when charging... because when fast charge is enable the data transfer (via usb) is disabled.

RootTheMachine · May 21, 2012 at 10:14 PM

Hey arifhn, I know I bugged you about this a few months back, but I'm still having the same issue. Whenever I save a setting in NStools, restoring it or choosing either boot option will automatically set the CPU max to the highest possible setting (at time of restore), and that gets pretty inconvenient when it's set at boot. I've been going around this the past few months by quickly changing the CPU setting as fast as possible after restoring, but it's not safe enough to set at boot.

I am willing to provide whatever further details you might need. This is on CM9 nightly with Glitch kernel, but it behaves the same way on other ROMs and kernels. Running latest version of NStools, and have had issue since 1.16 came out

arifhn · May 22, 2012 at 2:57 AM

korockinout13 said:
Hey arifhn, I know I bugged you about this a few months back, but I'm still having the same issue. Whenever I save a setting in NStools, restoring it or choosing either boot option will automatically set the CPU max to the highest possible setting (at time of restore), and that gets pretty inconvenient when it's set at boot. I've been going around this the past few months by quickly changing the CPU setting as fast as possible after restoring, but it's not safe enough to set at boot.

I am willing to provide whatever further details you might need. This is on CM9 nightly with Glitch kernel, but it behaves the same way on other ROMs and kernels. Running latest version of NStools, and have had issue since 1.16 came out

Hi.
If I'm not wrong, you are using live oc. Am I right?
When you use live oc, the cpu freq table also changed. It makes the code that setting cpu min/max value being complicated. I am trying to find another way to set that one.

RootTheMachine · May 22, 2012 at 3:20 AM

arifhn said:
Hi.
If I'm not wrong, you are using live oc. Am I right?
When you use live oc, the cpu freq table also changed. It makes the code that setting cpu min/max value being complicated. I am trying to find another way to set that one.

Yessir, using liveOC. Thanks, just making sure you knew.

reference.phone · May 23, 2012 at 8:01 PM

Hi arifhn

http://forum.xda-developers.com/showthread.php?t=1669134

You are the only one that can solve this situation, IMO.

(NSTools can support both)

arifhn · May 24, 2012 at 5:07 AM

reference.phone said:
Hi arifhn

http://forum.xda-developers.com/showthread.php?t=1669134

You are the only one that can solve this situation, IMO.

(NSTools can support both)

but that will not solve the problem, the fragmentation still there.

punkeroso · May 26, 2012 at 11:13 AM

Dismiss missed call

Hi,
I'm using the stock rom with the Air Kernel and your app is a must have.
I'm having an issue with NSTools regarding missed calls and BLN.
I'm not able to dismiss the notification.
I've tried swiping the notification left or right, tapping on the notification, none seems to make the blink stops.
The only way to dismiss the notification is disable an re-enable the backlight notification in NSTools.
Can you give me some hints?
Thanks

nexusphone · Dec 5, 2011 358 49 0

Hi arifhn

http://forum.xda-developers.com/showthread.php?t=1628477

the feature to lock/unlock the bootloader without the forced data-wipe

possible on NSTools for NS?

http://plus.google.com/101637761999487954252/posts/VwgcPER2dzd

obsanity · May 29, 2012 at 6:56 PM

Arifhn,
What location do you store the saved settings? Some of the governor settings degradation is not fine enough so when pressing + it jumps over the setting I want. I figured if I know the location of the file you save the settings to, I can just manually edit the file. Assuming you store it in clear text.

arifhn · May 31, 2012 at 8:10 AM

nexusphone said:
Hi arifhn

http://forum.xda-developers.com/showthread.php?t=1628477

the feature to lock/unlock the bootloader without the forced data-wipe

possible on NSTools for NS?

http://plus.google.com/101637761999487954252/posts/VwgcPER2dzd

i think, its a different tool

obsanity said:
Arifhn,
What location do you store the saved settings? Some of the governor settings degradation is not fine enough so when pressing + it jumps over the setting I want. I figured if I know the location of the file you save the settings to, I can just manually edit the file. Assuming you store it in clear text.

/data/data/mobi.cyann.nstools/mobi_cyann_nstools_preferences.xml
it stored in xml format, but i don't recommend to edit the file directly

obsanity · Jun 2, 2012 at 5:31 PM

arifhn said:
/data/data/mobi.cyann.nstools/mobi_cyann_nstools_preferences.xml
it stored in xml format, but i don't recommend to edit the file directly

Actually I just wanted the custom settings which I found in the settings folder. I made my edits and loaded the profile and it worked. Thanks!

nexus.prime · Jun 6, 2012 at 1:36 PM

Hi arifhn

You seem busy these days in real life.

GN CMPlus and Air kernel users are waiting for the support of NSTools

Thanks, dev

arifhn · Jun 10, 2012 at 1:34 PM

nexus.prime said:
Hi arifhn

You seem busy these days in real life.

GN CMPlus and Air kernel users are waiting for the support of NSTools

Thanks, dev

I'm sorry, a bit busy

Be patient, pls wait for ver 2.0

Sent from my Crespo using XDA

Sc4ryB3ar · Jun 11, 2012 at 2:31 PM

Has anyone else experienced conflicts and random reboots running nstools and romtoolbox pr?

Sent from my Nexus S 4G using Tapatalk 2

JokerAce · Jun 12, 2012 at 11:57 AM

Love this tool. Thanks OP

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

nexus.prime said:
Hi arifhn

You seem busy these days in real life.

GN CMPlus and Air kernel users are waiting for the support of NSTools

Thanks, dev

Does it not support Air Kernel? I am using it and it is working.

xtrezpasor · Jun 13, 2012 at 5:20 AM

How do I get it to undervolt? Even after unchecking the box it never shows me any options...

Sent from my SPH-D700 using xda premium

arifhn · Jun 15, 2012 at 2:49 AM

JokerAce said:
Love this tool. Thanks OP

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

Does it not support Air Kernel? I am using it and it is working.

yes its working for nexus s. i tought he talk about galaxy nexus

xtrezpasor said:
How do I get it to undervolt? Even after unchecking the box it never shows me any options...

Sent from my SPH-D700 using xda premium

you must use kernel with custom voltage mod or uv_mv_table

[APP] NSTools v1.16 for managing various Ezekeel's MOD and tweaks

Senior Member

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Retired Recognized Developer