UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi,
Not much to write. I've made automatic install script to enable init.d support
on Sony Tablet - like root-tool. Thanks to DooMLord for init.d support addon.
Requirements:
root
adb
(optional) 'rescue backdoor', via decreasing value of 'ro.sony.build.incremental'
in build.prop - to be able to reflash device if you mess something
br
condi
Good job and well done.
It will be very helpful for "no specialists"
What you mean obicom? hope you were not looking at me there.
No, not to you ... ;-)
But I guess it is helpful for all to reduce the manual effort and make the procedure more secure.
Okkkk, could somebody post results?
Do I need to do the access rights changes or the auto-install also includes the steps as well?
Great Work condi !
i have used it et any problem
zaynal said:
Do I need to do the access rights changes or the auto-install also includes the steps as well?
Click to expand...
Click to collapse
just run script, all included, fully automatic
Meelouw said:
Great Work condi !
i have used it et any problem
Click to expand...
Click to collapse
Great to hear that Thanks for posting results
condi said:
Hi,
Not much to write. I've made automatic install script to enable init.d support
on Sony Tablet - like root-tool. Thanks to DooMLord for init.d support addon.
Requirements:
root
adb
(optional) 'rescue backdoor', via decreasing value of 'ro.sony.build.incremental'
in build.prop - to be able to reflash device if you mess something
br
condi
Click to expand...
Click to collapse
Worked perfect no issues. Thanks Condi!
aside from mounting SD card as internal, what can we do presently with this i.e. what scripts are available?
wintermute000 said:
aside from mounting SD card as internal, what can we do presently with this i.e. what scripts are available?
Click to expand...
Click to collapse
i second this question.
By the way, will this automatically mount my external SD card to internal or will I have to do that manually? I just got my tablet rooted so I have not try anything yet.
Take a look in this thread ...
http://forum.xda-developers.com/showthread.php?t=1490116
scripts
What scripts are out there for this?
Condi's AllInOne Tool ....here in same section
http://forum.xda-developers.com/showthread.php?t=1515720
Hi Condi my SONY tab s 114 is stuck on SONY logo can you please help how to get my tab back thanks and good work
Related
Hi People... It's my first post, so please be gentle!
Thanks to this board I now have a fully rooted X10i - everything went smooth except for having 64bit java, but found answers to everything here, so props to all you lot.
I've got all the usual suspects installed on a rooted phone (root explorer, set cpu, cachemate, root manager etc) - all working fine.
But... the one that interests me the most is Autostart. 3 questions:
1) I've added a busybox command to automatically mount the filesystem as rw and that works great. - Is that super dangerous to do?
2) I saw some others that have installed autostart have added a command to use swapon /sdcard - when I try that I get "unsupported" - I'm guessing that is because we don't have custom ROM yet, and the generic kernel does not support swap?
3) Can anyone suggest any other good uses of an autostart script?
Thanks peeps, and peace out...
Check this out
adamsweeting said:
Hi People... It's my first post, so please be gentle!
Thanks to this board I now have a fully rooted X10i - everything went smooth except for having 64bit java, but found answers to everything here, so props to all you lot.
I've got all the usual suspects installed on a rooted phone (root explorer, set cpu, cachemate, root manager etc) - all working fine.
But... the one that interests me the most is Autostart. 3 questions:
1) I've added a busybox command to automatically mount the filesystem as rw and that works great. - Is that super dangerous to do?
2) I saw some others that have installed autostart have added a command to use swapon /sdcard - when I try that I get "unsupported" - I'm guessing that is because we don't have custom ROM yet, and the generic kernel does not support swap?
3) Can anyone suggest any other good uses of an autostart script?
Thanks peeps, and peace out...
Click to expand...
Click to collapse
1. Mounting /system as rw automatically... hmmm... sounds useful, but is it? I don't know about dangerous, but take a look at this:
http://forum.xda-developers.com/showthread.php?t=712951
2. Don't know and didn't try. But, sounds interesting... will look into it. I was more inclined to first create an ext3 filesystem on the sdcard and move stuff around from the /data filesystem on to there...
3. Well once we get a working custom ROM, we can use groh_kun's splboot loader to boot into it.
First of all I am taking no credit for any of this. All I did was combine other people's work and edit scripts to make this tool that I believe works best on my phone. Plus HULU WORKS!!!
Dev's who's material was used:
panamaniac - Perma-Temp Root + HULU FIX
eugene373 - (TOOL) Perma-Temp Root with *R/W* & Stable!
Almighty1 - [Fix] Hulu working + Flash.apk April 22
coolbho3000 - [MOD] EVO 3D Overclocked to 1.8GHz!
agrabren - [GUIDE] Fre3vo / Fre3dom Official Thread
What I Did: I just combined (TOOL) Perma-Temp Root with *R/W* & Stable! with Perma-Temp Root + HULU FIX and [MOD] EVO 3D Overclocked to 1.8GHz!.
What it does: Basically what the title says. It will temporarily root you device, overclock it to 1.8Ghz and swap out the current flash player for one that will allow you to use Hulu on your device.
AFTER DOWNLOADING, FOLLOW THE BASIC INSTRUCTIONS
BASIC INSTRUCTIONS
1. Plug your phone into your PC and select Charge only
2. Make sure HTC Sync is not running
3. Enable USB debugging by going to Menu>Settings>Applications>Development and checking USB Debugging
4. Unzip the folder titled "Unzip This.zip"
5. Open the file titled "Perm-Temp Root with RW + Overclock + Hulu Fix"
6. Run (Double click) the .bat file of your choice.
NOTE: YOU WILL NEED TO HAVE ROOT FIRST BEFORE YOU RUN HULU FIX OR OVERCLOCK
I am not personally responsible for any damage that may occur to you or your phone. Hopefully you are responsible enough to try and not break things and if you do not to cry all about it. That being said, If you are having problems with anything please describe in detail what you did and I will do my best to try and help.
DOWNLOAD
If you have NOT taken the OTA Update:
Pre OTA DOWNLOAD
Hulu app
I thought I would share this link with everyone. I downloaded the hulu app and it looks good. The only thing is that auto rotate was disabled and I couldn't figure out how to go full screen.
http://forum.xda-developers.com/showthread.php?t=782169
Hulu Plus +
HULU PLUS+ is soon to come. You can download the app and try it out it looks pretty clean. It won't allow you to watch content because our devices are currently not supported but it looks pretty koo.
http://forum.xda-developers.com/showthread.php?t=1136634
macramentonate said:
First of all I am taking no credit for any of this. All I did was combine other people's work and edit scripts to make this tool that I believe works best on my phone. Plus HULU WORKS!!!
Dev's who's material was used:
panamaniac - Perma-Temp Root + HULU FIX
eugene373 - (TOOL) Perma-Temp Root with *R/W* & Stable!
Almighty1 - [Fix] Hulu working + Flash.apk April 22
coolbho3000 - [MOD] EVO 3D Overclocked to 1.8GHz!
agrabren - [GUIDE] Fre3vo / Fre3dom Official Thread
What I Did: I just combined (TOOL) Perma-Temp Root with *R/W* & Stable! with Perma-Temp Root + HULU FIX and [MOD] EVO 3D Overclocked to 1.8GHz!.
What it does: Basically what the title says. It will temporarily root you device, overclock it to 1.8Ghz and swap out the current flash player for one that will allow you to use Hulu on your device.
AFTER DOWNLOADING, FOLLOW THE BASIC INSTRUCTIONS
BASIC INSTRUCTIONS
1. Plug your phone into your PC
2. Make sure HTC Sync is not running
3. Enable USB debugging by going to Menu>Settings>Applications>Development and checking USB Debugging
4. Unzip the folder titled "Unzip This.zip"
5. Open the file titled "Perm-Temp Root with RW + Overclock + Hulu Fix"
6. Run (Double click) the .bat file
I am not personally responsible for any damage that may occur to you or your phone. Hopefully you are responsible enough to try and not break things and if you do not to cry all about it. That being said, If you are having problems with anything please describe in detail what you did and I will do my best to try and help.
DOWNLOAD
Click to expand...
Click to collapse
Not working, missing something?
urcboss07 said:
Not working, missing something?
Click to expand...
Click to collapse
Which part is not working? Did you get an error message or something? Unable to download? Please explain.
AdbWinApi.dll is in the wrong place with zip extract. put all files in the tools folder and it works
ok everything runs through fine ... only problem is is doesn't grant root access. no apps can get root.
mallman said:
ok everything runs through fine ... only problem is is doesn't grant root access. no apps can get root.
Click to expand...
Click to collapse
Were you able to overclock in SetCPU?
Working?
Can anyone confirm this as working?
macramentonate said:
Can anyone confirm this as working?
Click to expand...
Click to collapse
I've been wanting to do a data reset because I lost ability to connect to wifi a few days ago. I'll try it out. That way everything is scratch except my 32g card
knightwolf123 said:
I've been wanting to do a data reset because I lost ability to connect to wifi a few days ago. I'll try it out. That way everything is scratch except my 32g card
Click to expand...
Click to collapse
That would be great. Thank you. When you unzip the folder it should look like the file that I've attached here.
I might be a noob, but I don't understand how anyone is able to change setcpu when it tries to OC the phone before SU permissions. Unless the winrar I have is corrupt and it's skipping it,
havent tried it yet (charging phone) plus im currently reformatting my 4G with MikG for the wifey and redoing my 3D after i get it charged up.
however.
i noticed you have only one overclock (do you need befor and after OTA?)
and only one script to root (no root and reroot. which doesnt really matter because if the file is already there it will skip it in theory)
Onethirtytwo said:
I might be a noob, but I don't understand how anyone is able to change setcpu when it tries to OC the phone before SU permissions. Unless the winrar I have is corrupt and it's skipping it,
Click to expand...
Click to collapse
personally what i do (maybe overkill) is keep the .apk for setcpu on sd card and when i know i am going to do a full reboot (not fast reboot) i uninstall setcpu, reboot, reroot, then install setcpu and do my profiles.
again this may be overkill but..... it works for me EVERY TIME ! (and i was using panam script till now)
macramentonate said:
Were you able to overclock in SetCPU?
Click to expand...
Click to collapse
No... Like I said I didn't even have root with this. No apps had root and I tried multiple times rebooting each. Regular prema team works fine
Sent from my PG86100 using XDA Premium App
macramentonate said:
That would be great. Thank you. When you unzip the folder it should look like the file that I've attached here.
Click to expand...
Click to collapse
It does but that doesn't work. Have to put those files in tools folder and run from there. That's the only way it would run for me
Sent from my PG86100 using XDA Premium App
knightwolf123 said:
personally what i do (maybe overkill) is keep the .apk for setcpu on sd card and when i know i am going to do a full reboot (not fast reboot) i uninstall setcpu, reboot, reroot, then install setcpu and do my profiles.
again this may be overkill but..... it works for me EVERY TIME ! (and i was using panam script till now)
Click to expand...
Click to collapse
I simply have no root. Not setcpu not nothin so it doesn't matter what order
Sent from my PG86100 using XDA Premium App
If i may....
I attached to file and it should work now... i just moved the files around so that everything lines out with your script.
here's the link:
Download
Let me know if it works... Cheers!
OP Updated
mallman said:
AdbWinApi.dll is in the wrong place with zip extract. put all files in the tools folder and it works
Click to expand...
Click to collapse
First of all thank you for testing this out. I discovered why it wasn't working and have updated the Original Post accordingly. You were correct regarding the .dll files being in the wrong place but just moved the other files to the wrong location. Why it wasn't working on yours or others Windows machines had to do with the environmental variables. On my PC I have adb configured in my PATH. This was allowing adb to run with the .dll files in my android-sdk-windows folder. If you don't have adb in your PATH than it never would have worked the way that it was set up. I believe I have corrected this and it should be working 100%. Please give it another try and let me know if there's any problems.
Great thank you! This should work for everybody now. I've updated the OP.
Can someone please confirm as working?
Information and Modules description
I was in the need to add some missing kernel modules to my Xperia Mini Pro sk17i with v4.0.2.A.0.58, but I could only find modules compiled form ICS sources, so I decided to build them myself.
All modules have been compiled from official sony Xperia v4.0.2.A.0.58 kernel sources, using Android NDK r5, and they should be fine with any GB based Xperia 2011 device (with that kernel version at least).
This is the list of modules, with some interesting programs using them:
fuse.ko: Cryptonite (used to create encrypted EncFS or Truecrypt volumes, adds support to mount drives so that are visibile to the whole Android system. Note: Cryptonite is not currently able to load the module automatically, you need to load it from Terminal Emulator..se more below)
usb-storage.ko, nls_utf8.ko, ntfs.ko (compiled with write support, currently untested): USB OTG Helper (used to mount external USB drives with USB On The Go cables).
cifs.ko, slow-work.ko, md4.ko: CifsManager (used to mount network shares)
ext4.ko, jbd2.ko: if you wish to use the EXT4 filesystem
tun.ko: needed by VPN clients, like OpenVPN or DroidVPN
Installation Instructions
Attached to this post you will find a ZIP that can be used along with CWM Recovery to install the modules in system.
Download the module, put it inside you SD card, reboot your phone in CWM (which you can install with the Xperia CWM Auto-Installer) and select install zip from sdcard, and browsed to the ZIP. Reboot your phone when install finishes.
Loading Modules
No module is automatically loaded at system startup: this saves your memory and battery (some of those modules are known to drain your battery if always loaded).
To manually load a module you have to open the Android Terminal Emulator and tap:
Code:
su
insmod /system/lib/modules/MODULENAME.ko
where MODULENAME is the name of the module you want to load.
Other useful commands:
Code:
lsmod
to see currently running commands
Code:
rmmod MODULENAME.ko
to unload a module.
If you wish to manually load a module at phone startup you should use init.rd or any other method (?) to run custom scripts at startup.
Load Order
Some modules need to be loaded in a specific order:
slow-work.ko must be loaded before cisf.ko
jbd2.ko must be loaded before ext4.ko
Other Firmware Versions
I've released the same package for other firmware versions, click on the firmware version to go to the specific thread:
ICS v4.1.B.0.587 Kernel Modules package by zxp
Changes
v2 - 2012.07.19
===========
- customized, built and added slow-work.ko, which is needed to load cifs.ko
- added jbd2.ko, which is needed to load ext4.ko
v1 - 2012.07.12
===========
- First release
Thanks for this..
Fuse, and the rest as required, are automatically loaded as required by USB OTG Helper if found in /system/lib/modules.
shardul_seth said:
Thanks for this..
Fuse, and the rest as required, are automatically loaded as required by USB OTG Helper if found in /system/lib/modules.
Click to expand...
Click to collapse
Yes, the same applies to CifsManager, even if it requires some fiddling in options, while your USB OTG Helper does it automagically...by the way, it would be really nice of you if you could add the same auto-load code to Cryptonite, which is open source somewhat related to your work! :good:
zxp said:
Yes, the same applies to CifsManager, even if it requires some fiddling in options, while your USB OTG Helper does it automagically...by the way, it would be really nice of you if you could add the same auto-load code to Cryptonite, which is open source somewhat related to your work! :good:
Click to expand...
Click to collapse
I have my own encryption script, and I am happy with it.. So no fiddling with cryptonite for me
Updated both install and uninstall packages to fix cifs.ko and ext4.ko that couldn't be loaded because of missing dependencies (slow-work.ko and jbd2.ko).
You can find the updated zips in the first post.
where i can find the ext4.ko module for Xperia 2011 ICS?, i can't find it nowhere, can you help me with it?
sorry for my bad english
lightdesiny said:
where i can find the ext4.ko module for Xperia 2011 ICS?, i can't find it nowhere, can you help me with it?
sorry for my bad english
Click to expand...
Click to collapse
I don't know where to find it, I don't have upgraded to ICS yet, sorry.
If you are sure that no one have released it I may build a package similar to this one once I upgrade to ICS, in the coming weeks. Keep an eye on this forum :cyclops:
hi when I type the cod say me that not found that I istall it with recovery please help me
my phone xperia ray
my rome is 2.3.4 - 4.0.2.A.0.58 GB
hadics1 said:
hi when I type the cod say me that not found that I istall it with recovery please help me
my phone xperia ray
my rome is 2.3.4 - 4.0.2.A.0.58 GB
Click to expand...
Click to collapse
Don't complain if none will answer you.
hadics1 said:
hi when I type the cod say me that not found that I istall it with recovery please help me
my phone xperia ray
my rome is 2.3.4 - 4.0.2.A.0.58 GB
Click to expand...
Click to collapse
Can you please explain your problem better?
I can't understand your post.
zxp said:
lightdesiny said:
where i can find the ext4.ko module for Xperia 2011 ICS?, i can't find it nowhere, can you help me with it?
sorry for my bad english
Click to expand...
Click to collapse
I don't know where to find it, I don't have upgraded to ICS yet, sorry.
If you are sure that no one have released it I may build a package similar to this one once I upgrade to ICS, in the coming weeks. Keep an eye on this forum :cyclops:
Click to expand...
Click to collapse
I've just released the same package as this for Xperia ICS v4.1.B.0.587, you can now use ext4 on the latest ICS firmware
This is great
Sent from my WT19i
mount nfs share works with busybox - but won't with cifsmanager
Hello folks,
as this is my first post here, i'd like to thank all of the contributors for the excellent Guides and Howtos on this platform. Based on the instructions in this forums i was able to root my Xperia Mini Pro sk17i and greatly expand my devices applicability. Thanks to all of you!
Sorry, that the post got that long - hope that someone is still so kind to read and answer to it. I just wanted to be as precise as possible in the desription of my problem.
And here it comes. As the title of my post already implies, my ultimate goal is to mount nfs shares of my NAS and Router in my private network as user-friendly and simple as possible.
So far, I tried the following to achieve this goal:
Install busybox to generally expand linux capabilities of the device
install the Android Terminal emulator also from Google play
as previuosly mentioned, the device is rooted and Super user capabilities are set
created a mount-point for the nfs share
installed cifsmanager for mounting/unmounting with one click later
I tried to manually mount the share in the terminal. Without busybox i had no luck, but actually that was not sursprising at all. With busybox however, it worked instantly - what indeed surprised me, because this thread here implied somehow the kernel, as is, wasn't even capable to do it without additional modules. I could easily browse the share with ES file manager etc. and make use of my shares. So far, so great. :good:
But opening a terminal, get super user rights and mount manually by typing the whole sequence of
Code:
busybox mount -o nolock,vers=3 -t nfs 192.xxx.xxx.x.x:/my/nfs/share /mnt/MyLocalFolder
is not what you'd call simple or user-friendly at all.
So i aimed to improve the mount procedure with cifsmanager, but I always fail. And do no not understand what i am doing wrong. Initially i tried it without further kernel modules, encouraged by the success i had with busybox. But i always got a "Invalid argument" reply.
During the troubleshooting I stumbled upon this post, and thx to zxp's files, i managed to add the kernel modules to my /system/lib/modules folder (and yes, I have the exact same original/stock GB kernel version they are intended for).
But still no luck - even after i added slow-work.ko to the list of modules loaded by cifsmanager in the properties (placed before cifs.ko as it was suggested by another thread found somewhere in the forum). The info tab states the modules are loaded, but i still receive the same crooked "Invalid argument" message. What the heck am I doing wrong?
Seems to me there is some sort of general syntax issue - here is what info I give the app:
Share: 192.xxx.xxx.x.x:/my/nfs/share
Mount Point: /mnt/MyLocalFolder (tested with and without the mount point prefix in properties)
User: guest (default - without it, it wont work,app description states it will be ignored for nfs shares anyway)
Pwd: left empty
Options:nolock, vers=3 (tested with and without these - but where generally considered essential in some threads + my shares are nfs_v3)
Does somebody have an idea what is going wrong and might point me in some useful direction?
Thanks and Cheers to you all,
Nix
Use script manager and create a script!
Nixblicker said:
Hello folks,
as this is my first post here, i'd like to thank all of the contributors for the excellent Guides and Howtos on this platform. Based on the instructions in this forums i was able to root my Xperia Mini Pro sk17i and greatly expand my devices applicability. Thanks to all of you!
Sorry, that the post got that long - hope that someone is still so kind to read and answer to it. I just wanted to be as precise as possible in the desription of my problem.
And here it comes. As the title of my post already implies, my ultimate goal is to mount nfs shares of my NAS and Router in my private network as user-friendly and simple as possible.
So far, I tried the following to achieve this goal:
Install busybox to generally expand linux capabilities of the device
install the Android Terminal emulator also from Google play
as previuosly mentioned, the device is rooted and Super user capabilities are set
created a mount-point for the nfs share
installed cifsmanager for mounting/unmounting with one click later
I tried to manually mount the share in the terminal. Without busybox i had no luck, but actually that was not sursprising at all. With busybox however, it worked instantly - what indeed surprised me, because this thread here implied somehow the kernel, as is, wasn't even capable to do it without additional modules. I could easily browse the share with ES file manager etc. and make use of my shares. So far, so great. :good:
But opening a terminal, get super user rights and mount manually by typing the whole sequence of
Code:
busybox mount -o nolock,vers=3 -t nfs 192.xxx.xxx.x.x:/my/nfs/share /mnt/MyLocalFolder
is not what you'd call simple or user-friendly at all.
So i aimed to improve the mount procedure with cifsmanager, but I always fail. And do no not understand what i am doing wrong. Initially i tried it without further kernel modules, encouraged by the success i had with busybox. But i always got a "Invalid argument" reply.
During the troubleshooting I stumbled upon this post, and thx to zxp's files, i managed to add the kernel modules to my /system/lib/modules folder (and yes, I have the exact same original/stock GB kernel version they are intended for).
But still no luck - even after i added slow-work.ko to the list of modules loaded by cifsmanager in the properties (placed before cifs.ko as it was suggested by another thread found somewhere in the forum). The info tab states the modules are loaded, but i still receive the same crooked "Invalid argument" message. What the heck am I doing wrong?
Seems to me there is some sort of general syntax issue - here is what info I give the app:
Share: 192.xxx.xxx.x.x:/my/nfs/share
Mount Point: /mnt/MyLocalFolder (tested with and without the mount point prefix in properties)
User: guest (default - without it, it wont work,app description states it will be ignored for nfs shares anyway)
Pwd: left empty
Options:nolock, vers=3 (tested with and without these - but where generally considered essential in some threads + my shares are nfs_v3)
Does somebody have an idea what is going wrong and might point me in some useful direction?
Thanks and Cheers to you all,
Nix
Click to expand...
Click to collapse
that works, but...
Well, yeah - that was an option. I already did, and it works with the busybx mount as stated.
But i would have to write another to mount another share, unmount them, and one to prevent ES file manager to somehow occupy the mount to make it busy before unmounting etc.
I hoped that cifsmanager would smooth and ease the mounting/unmounting.
Thank you for your suggestion, anyway!
Cheers, Nix
shardul_seth said:
Use script manager and create a script!
Click to expand...
Click to collapse
SleekAI kernel for the LG G Pad 8.3 V510 (GPE)
Updated 1-22-2015 CURRENT Sleekai8.1
Both kernels updated to Fsync off (again) and a couple of small changes to code. Also changed the versions to match numerically.
Also added a new 88sleektweaks file for init.d that has preset values for voltage control undervolting, See second post for instructions and zip file. Use Trickstermod if you want fsync on.
Both Lollipop And Kitkat Versions
(Lollipop version also works with CyanogenMod12)
Features:
Flash Through Recovery!
Interactive Governer as default
Row IO Scheduler as default
Wheatley Governer added as option (Lollipop only)
Knock_on enabled by default (Lollipop) or with
My app in the third post down (KitKat)
Sweep2Sleep enabled as an option
LCD screen control using Trickster Mod
Compiled using Linaro Toolchain cortex a15-4.9.3
o3 Compile optimizations
init.d support (zip align, etc...)
Faux Sound Control added
USB Fast Charge added
Frandom replacing Urandom
Fsync On/Off using Trickstermod
Tethering for bluetooth and usb
Exfat support for sdcards
User Space Voltage Control TricksterMod to change
Five new IO schedulers for Lollipop! Trickstermod to change
And more!
The kernel source and Commits that show the changes used for sleekai can be found here: Github
Prerequisites
Unlocked bootloader
Root
Install Busybox for init.d support
TricksterMod is recommended for changing settings
How does this work?
Start by making a backup of your boot in recovery, then:
Flash the latest version in Recovery . Proceed to the downloads below, download to your tablet, reboot into recovery and install the zip --That simple!
if you want to build your own kernel start to finish with complete instructions, you can follow my guide for rolling your own kernel HERE
Please hit "Thanks" to show your support!
DOWNLOAD HERE:
ATTACHED FILES
TO USE INIT.D SUPPORT ON YOUR DEVICE
Busybox must be installed for the init.d support file to work! (in the playstore)
You will need to add a folder named init.d to /system/etc/ in order to use this support
One example is to have your apps zip aligned on boot.
Another is to use my 88sleektweaks script to save battery
This includes undervolting values that you can adjust as neccesary, and a few WiFi tweaks.
Unzip the file to reveal the zip-align script. Then:
Copy the script to your /system/etc/init.d folder, change the permissions if needed, and reboot. Thats it!
You can tell you have it right by looking in /data for the zip align db files after you reboot.
You should change your permissions on any file in init.d to rwx r-x r-x (755)
Sleektoggle - For Knock_on and Sweep2Sleep
I made a small application using tasker that will enable Knock-on and Sweep2Sleep on devices using the kitkat kernel.
Knock-on is enabled by default in my Lollipop kernel - no app required.
The application works as a toggle, and will need to be "enabled" after every boot to use these features.
This is for your protection, as knock-on will freeze your device if enabled before or during boot.
This keeps you from having to enable these manually by adjusting the files yourself.
The knock-on feature should work on ANY 510 device, as it is native to the device.
To use:
Download and install the apk.
Put the icon from your apps somewhere on your home screen
after boot/reboot, press the icon, allow root privilages, and you are done!
You should only need to enable root the first time.
To use the features:
Simply knock twice in the center of the screen to wake up your device from standby
To put it to sleep, swipe from right to left on the lower portion of your screen.
Pressing the icon a second time does not disable the features. Restarting your device does!
Glad to see some dev on this device finally. Will flash it tonight and report if i have any issues.
edru said:
Glad to see some dev on this device finally. Will flash it tonight and report if i have any issues.
Click to expand...
Click to collapse
Excellent! You can expect the first reboot to be slow, as well as the first opening of some apk's as the kernel repopulates the files. Let me know!
A lone V510 dev emerges!!! Thank you!
Sent from my LG-V510 using Tapatalk
-Updated kernel for ability to pull the .config from the device, and shorter idle time before sleep.(battery saver). With this comes an updated name change to sleekai2.
--Update--
Kernel recompiled using the latest Linaro toolchain 4.9.3
Gamma corrected on the tablet with no further optimization needed
And the latest Antutu benchmark for the 510 with the latest Lollipop kernel: 31,526 See attachments.
going to give this a go right now.
---------- Post added at 01:57 PM ---------- Previous post was at 01:49 PM ----------
Gamma looks GREAT!
nice job sir. Thank you.
Just flashed on my V510. Thank you so much for your hard work!
Anyway to mod the gamma fix onto other roms (v500) via adb or something?
this is awesome! It feels like a brand new device!
Hi Sleekmason,
I tried your kernel by booting it but not doing the permanent flash to the tablet and something that I noticed is that when I am booted using your kernel I can't see or use my sdcard1 (external sd). When I boot off the normal stock kernel the sdcard1 is available again. I tried 2x and same result each time. Am I having bad luck and others can see their external sd card? The extra 64GB of storage is critical for me so even though I would like to try more your kernel and the improvements you have made I can't without the external SD card working. Please let me know if you know a solution. I don't know if this makes any difference but I have done the platform.xml change to be able to write on the external SD, that is the only change to the stock GPE Rom besides rooting. Thank you
schalmers said:
Hi Sleekmason,
I tried your kernel by booting it but not doing the permanent flash to the tablet and something that I noticed is that when I am booted using your kernel I can't see or use my sdcard1 (external sd). When I boot off the normal stock kernel the sdcard1 is available again. I tried 2x and same result each time. Am I having bad luck and others can see their external sd card? The extra 64GB of storage is critical for me so even though I would like to try more your kernel and the improvements you have made I can't without the external SD card working. Please let me know if you know a solution. I don't know if this makes any difference but I have done the platform.xml change to be able to write on the external SD, that is the only change to the stock GPE Rom besides rooting. Thank you
Click to expand...
Click to collapse
huh, I don't have this problem myself using es file explorer, or in my settings tab under storage.
There should be nothing in the configuration to cause the problem you report.
I have however, heard that there were issues with some of the 64 gig cards. Have you tried removing the card and reinserting? I suppose it would be possible that it needs a new initial read after changing kernels. Please let me know.
Also what file system is the card?
What are you trying to read it from?
kdog350 said:
this is awesome! It feels like a brand new device!
Click to expand...
Click to collapse
Excellent! Glad to hear it!
general_z said:
Anyway to mod the gamma fix onto other roms (v500) via adb or something?
Click to expand...
Click to collapse
Check out "How to roll your own kernel" in my signature. There is somebody who is going to try to make a kernel for the 500. Unfortunately, without the device I cannot take the chance of making a mistake and ruining someone's day. Hopefully they will succeed!
-Update-
Kernel Added
Changelog 22 Feb 14
general setup-perf-changed to sleekai3
compiled with -o2 for optimization of code/better battery life, maybe.
general setup-kernel log buffer size changed to 14
Note* sleekai3 is pretty much the same thing as sleekai2 except the specific use of the optimize flag for the gcc compiler. Does it really change anything? Don't know yet. Wouldn't worry about changing unless you just can't resist. If I see noticable battery savings I'll let ya know. Of course, changing is easy too . . ..
sleekmason said:
Check out "How to roll your own kernel" in my signature. There is somebody who is going to try to make a kernel for the 500. Unfortunately, without the device I cannot take the chance of making a mistake and ruining someone's day. Hopefully they will succeed!
Click to expand...
Click to collapse
How thoughtful of you. In what file(s) is the gamma fix or where is the changelog that shows it?
I'm thinking that It may be quite easy to just to mod another kernel for the v500 and put it in (like dyn.Kernel v3).
sleekmason said:
huh, I don't have this problem myself using es file explorer, or in my settings tab under storage.
There should be nothing in the configuration to cause the problem you report.
I have however, heard that there were issues with some of the 64 gig cards. Have you tried removing the card and reinserting? I suppose it would be possible that it needs a new initial read after changing kernels. Please let me know.
Also what file system is the card?
What are you trying to read it from?
Click to expand...
Click to collapse
Hi Sleekmason, thank you for responding.
I tried again this time with your new v3 kernel and I get the same results. The card is a Sandisk 64GB formated as exfat. I can read it no problem when booted on stock kernel and in W7. From the tablet I check the sd card from ES FileExplorer and from the settings Storage. When I removed and re-inserted the SD card while booted on your kernel I get the option to "Mount SD" but it does not seem that it can complete the mounting.
Have you modified your platform.xml file (under system/etc/permissions) to allow writing to the SD card?
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
add line : <group gid="media_rw" />
Without that change I could not write to the SD card but only read from it on the stock kernel / rom.
Are you able to read and write to your SD card with your kernel?
schalmers said:
Hi Sleekmason, thank you for responding.
I tried again this time with your new v3 kernel and I get the same results. The card is a Sandisk 64GB formated as exfat. I can read it no problem when booted on stock kernel and in W7. From the tablet I check the sd card from ES FileExplorer and from the settings Storage. When I removed and re-inserted the SD card while booted on your kernel I get the option to "Mount SD" but it does not seem that it can complete the mounting.
Have you modified your platform.xml file (under system/etc/permissions) to allow writing to the SD card?
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
add line : <group gid="media_rw" />
Without that change I could not write to the SD card but only read from it on the stock kernel / rom.
Are you able to read and write to your SD card with your kernel?
Click to expand...
Click to collapse
Yes, I did the fix as well. The sleekai3 is only the optimized sleekai2 (using flag -o2), so there really is not much difference.
SO, here we go, I looked up problems with the 64 bit card as I remembered reading something about them in a samsung forum. What I found this time I searched was here: http://forum.archosfans.com/viewtopic.php?f=84&t=66346 and here in our own forum: http://forum.xda-developers.com/showthread.php?t=2575043
Basically what "they" say is that the Sandisk 64 bit cards have issues with exfat. The solution is to format in fat32. you lose a gig or two with the different format, but it works. The above link also suggests ext4 as an option, but it will not work on our device, neither will ext2. At least not mine!
Long story short is to copy your files to your computer, reformat to fat32 and put them back!
The longer story is of more interest to me. As sleekai3 is based off the original kernel source for the 510, and because I have made no changes to areas that should/could effect the reading of your card, WHY does the stock kernel you have allow it? (yes, I switched it and am assuming it is unreadable by every kernel for the sake of argument.)
This is entirely a permissions issue as far as I know. frustrating. One thing I cannot do with my card is download a file, say a zip file, to my external sd card. I can copy it after it's downloaded, I can use link2sd with no problem, everything shows up well. This indicates the need for root access by Dolphin Browser.
I had thought to edit the fstab file and simply add "users" to the options but that doesn't work. I also tried many variations of the fix in the /permissions/platform.xml as well.
I'm going to have to study permissions for the device and see what I can do to fix it for everybody if I can. I'm afraid that adding the card to root could allow for an exploit. maybe.
Anyway, reformat to fat32 and let me know how it goes! regards, sleekmason
A special thanks to @HypoTurtle for all of the basic info that I compiled here. :good:
Many of us get a little disgusted with the extreme palm sensitivity of the touch pad when we are using Remix OS for PC with a touchscreen or mouse. You can disable the touch pad or other devices by following these steps:
NOTE: YOU MUST HAVE ROOT and system must be R/W enabled if you wish to modify the file /system/etc/excluded-input-devices.xml
In order to make the system R/W you need to go here: http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
After that then refer to the attached PDF file for instructions on modifying the system.
Issues
I have root .. per Root Checker and I am SuperSU .. I am able to pull up and edit the file BUT I am unable to save it and get an unable to save error message.
dalton_daley said:
I have root .. per Root Checker and I am SuperSU .. I am able to pull up and edit the file BUT I am unable to save it and get an unable to save error message.
Click to expand...
Click to collapse
I made this before Jide locked down the system file. In order to make the system r/w you need to go here http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Then you can use my method.
Ahhh ... I was thinking something was up .. AWESOMENESS!!!!! TSYM
dalton_daley said:
Ahhh ... I was thinking something was up .. AWESOMENESS!!!!! TSYM
Click to expand...
Click to collapse
OP updated
not working my usb mouse
I do this thing on prime os and it done well my touchpad is disabled. and my first restart my usb mouse is worked. but next time not work at all.
please help me to use my usb mouse.