Database Info

Tutorial ROKCHIP2918 ADB UBUNTU LINUX AND ROOT

1-Preparing the environment.
sudo add-apt-repository ppa: nilarimogard/webupd8
sudo apt-get update
sudo apt-get install-android-tools-tools adb-fastboot android
Those three commands install ADB TOOLS, for Ubuntu 12.04 and earlier versions.
2-Each manufacturer has its ID development.
This, in principle, we can solve in a simple way Ubuntu. We need to add a line in the file / etc / udev / rules.d.
The line to add to the file depends on the manufacturer and model of the device. We can find the Vendor ID and Product ID of the device running (after having connected to USB, of course):
$ lsusb
This will be returned
*
Bus 002 Device 021: ID 2207:0000
(This is an example of what we can give back, by brand and manufacturer)
This indicates that the Vendor ID is "2207" and the Product ID is "0000".
3-Let's do it step by step:
Enable USB debugging and unknown sources on the Android.
Go to Settings -> Security and check the Unknown sources checkbox, then go to Options and development USB debugging enabled.
Connects via USB to Ubuntu Android.
Create / edit a file in / etc / udev / rules.d called 51-android.rules:
$ sudo gedit / etc/udev/rules.d/51-android.rules
Add the following line and save it
SUBSYSTEMS == "usb", ATTRS {idVendor} == "....", MODE = "0666", GROUP = "plugdev"
***IMPORTANT: Place the idVendor ATTRS {idVendor} == "HERE"***
4-Restart udev
$ sudo restart udev
At this point adb and should recognize our device, but it is not. This is because the version of adb included in the Android SDK does not "understand" our Vendor ID (not a salesman "officially recognized").
To fix this do the following:
Create / edit a file in $ HOME / .android called adb_usb.ini:
$ gedit $ HOME / .android / adb_usb.ini
Add the following content and save it
# ANDROID 3RD PARTY USB VENDOR ID LIST - DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0 × 2207
************************************************** *****************************
At this point gave me a problem, which was solved in a way a little strange. The following file $ gedit $ HOME / .android / adb_usb.ini
has to look like:
# ANDROID 3RD PARTY USB VENDOR ID LIST - DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0 × 2207
# ANDROID 3RD PARTY USB VENDOR ID LIST - DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0 × 2207
It was the way it worked for me and found the tablet.
************************************************** *******************************
5-At this point adb and should recognize our device:
$ adb devices
List of devices attached
0123456789ABCDEF device
Although sometimes you need to stop and start the adb server:
$ adb kill-server
$ adb start-server
************************************************** *********************************
Or maybe we should use this other method to stop the deamon
************************************************** *********************************
Reinitiate the 'deamon', as follows:
$ sudo stop udevd
It is likely that in the process of detention remains in standby, so the terminal will show nothing after entering the command.
Do not panic, simply: Restart our machine.
After restarting our team, we will ensure that our tablet has enabled debug mode, for that we can address
Settings >> Applications >> Development
And check the option 'USB debugging'
Once marked, we connect our tablet via cable / USB, open a terminal command:
$ adb devices
Automatically our deamon 'udevd' ripped, since previously we had stopped. And if all goes well, it should show you a list of connected devices, with their ID's.
6-Now that our team recognizes our device we root him:
Superuser unloaded tool (ICS compatible version and with our platform ARM, MIPS, ROKCHIP, ALLWINNER, etc.) and extract the application "Superuser.apk" and binary "your" in, for example, / tmp.
Su and Superuser installed:
$. / adb remount
$. / adb push / tmp / su / system / bin / su
2568 KB / s (22364 bytes in 0.008s)
$. / adb push / tmp / su / system / xbin / su
2843 KB / s (22364 bytes in 0.007s)
$. / Adb push / tmp / Superuser.apk / system / app / Superuser.apk
4593 KB / s (843503 bytes in 0.179s)
$. / adb shell chown 0.0 / system / xbin / su
$. / adb shell chmod 6775 / system / xbin / su
$. / adb shell chown 0.0 / system / bin / su
$. / adb shell chmod 6775 / system / bin / su
$. / adb remount
remount succeeded
$. / adb reboot
We hope to restart the tablet and go!
Sources:
http://rubensa.wordpress.com/2012/05/21/energy-sistem-i828-hd-ics-4-0-3-rooting/
http://www.htcmania.com/showthread.php?t=469742

[Tut] Fast Change Kernel Paramteres

This is a very simple guide for build a script that manipulates the kernel parameters. Using SManager we will add it on us home or dock.
No specific skills are required, only patient.
What You Need:
- Root Permissions
- a customizable kernel
- SManager & SMWidgets
- Busybox
------------------------------------------------
1) First make your personal script for manipulating the kernel parameters.
Make a new file without extension on your computer and open it with a text editor
a) write this two line (IMPORTANT !!!)
#!/system/bin/sh
busybox mount -o remount,rw /system
the first line is the standard initialization of a sh script in Linux-Unix system. The second line allows the writing of the file system.
b) Now add the code. All the kernel parameters are text file located in the /sys/ folder. Is possible to edit such parameters writing
echo NEWVALUE > / PATH / OF / THE / DESTINATION / PARAMETER
for example, for changing the minimum frequency
# CPU Min Freq
echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
In sh scripts the line with # symbol won't be execute, so you can write whatever you wants.
c) The most important parameters are located in:
# CPU Min Freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
# CPU Max Freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# CPU Governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# IO Scheduler (ALL THIS PARAMETERS MUST BE CHANGED FOR THE SCHEDULER)
/sys/block/mmcblk0/queue/scheduler
/sys/block/mmcblk0boot0/queue/scheduler
/sys/block/mmcblk0boot1/queue/scheduler
/sys/block/mtdblock0/queue/scheduler
I attached a simple script in this form here. You can found other parameters here, or A complete documentation of a kernel linux here. Other scripts and information about the Android kernel can be found here, here. A complete documentation of a kernel linux is here
BE CAREFUL WITH EDITING KERNEL PARAMETERS. ALWAYS READ THE DOCUMENTATION OF YOUR KERNEL AND CHECK THE PARAMETERS
d) Add this line at the end of the file for remount the system folder as read-able only
busybox mount -o remount,ro /system
now your script is done.
You can check and control the parameters by typing on the terminal or via ADB
cat / PATH / OF / THE / PARAMETER / YOU / ARE / CHECKING
------------------------------------------------
2) push the file on your phone. Set executable permission of file with an explorer or with chmod comand. Now open SManager, navigate to the path of the script and add it on its database. You can check it and test if everything works fine.
------------------------------------------------
3) the last step consists to add the shortcut of the script your home. With the most advanced launcher you can change the icon and the name and personalize it.
------------------------------------------------
4) optional: after the execution of the script with SWmanager the terminal will be open. To automatically return on the home you must add at the end of the script a line with the activity of your launcher related to the home button (this is a method I found, if someone has a better idea please tell me )
For Nova Launcher the code is:
am start -a android.intent.action.MAIN -n com.teslacoilsw.launcher/com.android.launcher2.Launcher
The method is used to found this activity was:
a) Open an app, and then return the to the home by pusching the central button
b) With the terminal emulator, or via adb, launch the logcat command
c) look for the last activity related to your launcher
d) replace the part after the -n with the string you have found
------------------------------------------------
All is done, if you have questions or some advice please contact me.
...The english will improve during my android experience :angel:

busybox ls --color and many other commands "Working"

have you got bored of your one Text colored terminal ?
when you look at the results you always are confused ?
well .. you came into the right thread
I'm here today to show you how to make every busybox command fully functional
I was trying to make this command work but no success
Code:
#ls --color=always
then i ended up making busybox fully functional
Note: you must have rooted device and custom recovery and SDK tools " incase you don't have adb.rar "and your phone developer mode and USB debugging checked .
go to your SDK tools press sheft and right mouse click and open cmd here
________________________________________________________________________
now .. lets get to it shall we ?
1 - reboot into recovery and connect your device in your PC
2 - type in these commands in your PC command prompt you opened in order :
Code:
# adb shell
# mount system
# cp /system/bin/sh /sdcard/Download/sh
#adb reboot
3 - reboot your device
4 - download this busybox app and start it
jrummy.busybox.installer
5 - you'll see in the app's INSTALLER icon a location /system/xbin
change it to /system/bin
6 - open app's settings "upper right corner beside the three dot's" and check all what's in the installer settings
7 - press back and click install " your phone will boot into recovery and install the busybox "
8 - after finishing the process your device will reboot normally but wait a minute !!! SU is not working anymore :crying:
9 - reboot your device again into recovery !! " I'll try to fix it for you "
10 - type in these commands in order :
Code:
#adb shell
#mount system
#cp /sdcard/Download/sh /system/bin/sh
#chmod 755 /system/bin/sh
#adb reboot
and we are done
look at the attachment below this is how your terminal will look like and error free

I'm sorry about this post
apparently I was kinda mistaken
I think what happens that lead to this is
when you write down the applet's name in terminal the device start to search inside bin file first .. if the applet was not found in bin .
the device will start to search on xbin file and maybe the whole storage for that command
so .. since there are some applets in bin are the same one in busybox and I was able to locate them "took me like an hour to do so"
and these applets are :
Code:
[COLOR="blue"]blkid
brctl
cat
chmod
chown
clear
cmp
cp
date
dd
df
dmesg
du
grep
gzip
hd
id
ifconfig
insmod
ionice
ip
kill
ln
ls
lsmod
lsof
mkdir
mke2fs
mknod
mkswap
mount
mv
netstat
nohup
ping
ping6
printenv
ps
readlink
reboot
renice
rm
rmdir
rmmod
route
sh
sleep
swapoff
swapon
sync
top
touch
tune2fs
umount
uptime[/COLOR]
there are a lot of difference in results between the factory applets and the busybox applets
if you want to see the difference install busybox in /system/xbin and in terminal type one of these applets above like this :
for busybox applets result :
Code:
busybox [I][COLOR="blue"]applet[/COLOR][/I]
for system applets result :
Code:
[I][COLOR="Blue"]applet[/COLOR][/I]
it might not be a new thing but for me it is
I just wanted to share that info for the ones who doesn't know
Edit : there is also one applet in system/xbin which is " nc "
thanks .

Android Auto working on 7.1.x ROMs

Hello,
Android Auto would not work with any of the 7.1.x ROMs: head unit screen remained black with occasional green macroblocks. The solution is to disable two video encoders, which appear not to create streams compatible with Android Auto.
Using adb root:
Code:
adb root
adb remount
adb shell mv /system/lib/omx/libOMX.SEC.AVC.Encoder.so /system/lib/omx/libOMX.SEC.AVC.Encoder.so.bak
adb shell mv /system/lib/omx/libOMX.SEC.M4V.Encoder.so /system/lib/omx/libOMX.SEC.M4V.Encoder.so.bak
adb shell sync
Using Android shell:
Code:
su
mount -oremount,rw /system
mv /system/lib/omx/libOMX.SEC.AVC.Encoder.so /system/lib/omx/libOMX.SEC.AVC.Encoder.so.bak
mv /system/lib/omx/libOMX.SEC.M4V.Encoder.so /system/lib/omx/libOMX.SEC.M4V.Encoder.so.bak
sync
I suggest a reboot thereafter.
BR,
Jerome.

Changing CPU Governor with ADB?

Would this work without root? And if so, could I set it to powersave and expect the result to stick after a reboot?
How to change CPU frequency
you can change the CPU frequency on your android device regardless of what your CPU governor is. You will be actually changing the governor to one that only takes userspace input in determining frequency.
The first step is to make sure you have the userspace governor available on your device..
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
interactive ondemand userspace powersave performance
we have the userspace governor on my Nexus 4, you should see it on any other Android device as well since it’s an old and simple governor.
Next we will set our governor to be userspace.
[email protected]:/ # echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
usersapce
It is set now. If the governor isn’t set then scaling_governor will return something else.
Now it’s just a matter of determining what frequencies are available and setting them.
[email protected]:/ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
384000 486000 594000 702000 810000 918000 1026000 1134000 1242000 1350000 1458000 1512000
For Locking CPU Frequecy at a particular level:
By using below mentioned ADB Command we can lock CPU Frequency
adb shell "echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq"
adb shell "echo userspace > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq"
adb shell "echo userspace > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq"
adb shell "echo userspace > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq"
adb shell "echo 1600000 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq"
If you are interested in how long your system spent in what state, check out the file
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
To have frequency on Android, just read these special files
in /sys directory
#cat "/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq"
#cat "/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq"
#cat "/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq"