hey did anyone manage to get the keys work with these kernels (KERNELS WITH KEYPAD DRIVERS AS MODULES) in any CWM build?
I try to load it using terminal like before but its not working
even the Gscript method is not working anymore, is there any other solution than restarting the device with KERNELS WITHOUT KEYPAD DRIVERS AS MODULES after each freez, the freez mostly happen after pressing the right option in the keypad or using setCPU
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
saobang3886 said:
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
Click to expand...
Click to collapse
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
kerfooly said:
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
Click to expand...
Click to collapse
OPP!
First, you should boot with kernel without modules keyboard, it easy to setting in first time. try setting all thing who make that build recommend!
Second, in stall Autostart and gScript app. copy autostart.sh to root of your sdcard. open terminal, remove old modules and copy autostart.sh to /data/opt like this post http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2
Then open restart keyboard script in your computer, open Gscipt in your phone, add new script, tip name is restart keyboard. Script like the file you open in computer!
after that, restart to window mobile, copy kernel with keyboard as module to your boot folder, replace old file, then reboot and it will work!
Well, after setting up all the scripts for loading and reloading of the kernel modules and then removing all kernel-modules of the old kernel (that without the drivers als module), you have to reboot your device. As part of the boot process, the new kernel modules are copied from the tar.gz-file, without deleting the old modules, this step will be skipped from the boot script.
So.
1. prepare all scripts
2. remove the old modules
3. boot the new 'KEYBOAD-AS-MODULES' kernel with it's module-archtive in place
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory ... the works quite nice and is much cooler that trying to press vol-down in the right moment ... i renamed it then to no_recovery.txt ... makes getting to recovery quite relaxed ...
Ciao
Kurt
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
hopsakee said:
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
Click to expand...
Click to collapse
Yep, here's the code from the init script that's in rootfs.img:
if [ -f /sdcard/npkboot/recovery.txt ]; then
so ... have fun with Android on your X1 .
Ciao
Klaus
Kurt Krummbein said:
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory
Click to expand...
Click to collapse
Ik works. I start into CWM. But the volume buttons still don't respond, and I need those to navigate through CWM.
Anyone a solution other than switching back to standard kernel without seperate modules?
when I type "sh /data/opt/autostart.sh" and press Enter, I get this error:
"insmod: can't read '/lib/modiles/microp-ksc.ko': no such file or directory
insmod: can't read '/lib/modiles/microp-keypad.ko': no such file or directory"
Can you help me?.
Where is kovsky keyboard modules????
I using ygge kernels with HoneyComb Froyo V.3
Related
Simply it's the best rom combination to be the most stable rom i have ever used and now am using it daily with no problems :-
(you may find it difficult but i swear u will be very happy with the results just give it a try)
Download rom:-
http://www.multiupload.com/T589I4WUX9
__________________________________________
Installation ...
1- Create (ext2) partation on your card ...
like in this video....
http://www.neopeek.com/viewtopic.php?f=16&t=146
2- Copy contents from the rar file to SD card ...
3- Open folder npkinstall and run install.exe
4- After restart open haret.exe normaly ...
5- download better keyboard from attachements and put it in ur androidapps folder in sd card
__________________________________________
you must do this to make ur button work and to be able to restart it by one press
open terminal emulator then type the following :-(press enter when u write the letters in each line)
Code:
su
mkdir /data/opt
cp /sdcard/autostart.sh /data/opt
chmod 755 /data/opt/autostart.sh
Then install autostart.apk (found in the rom source folder)
When your buttons stop functioning, you have to run a script from GScript that reinstalls the modules so they work once more. Perform these steps:
Install GScript.apk
Open GScript Lite and press <menu> button, then <add script>
Press the <Load file> button.
The script you need is located autmatically and is called "XPEROID Gscript Button restarter script.sh"
Select it and then in the new screen press <Save>
You can now return to your homescreen and add a shortcut to the script so you can reset your buttons easily. To do this do the following:
Press <menu> and then <add> to add widgets.
Select <shortcut> from the list and then locate and select <GScript Lite>
Then select the "XPEROID Gscript Button restarter script" and you now have a shortcut on your homescreen to reset your buttons.
_________________________________________________
thanks to "needo" for pure froyo rom main topic address
http://forum.xda-developers.com/showthread.php?t=941059
thanks to Duckly for the "keyboard as a module kernel" main topic address
http://forum.xda-developers.com/showthread.php?t=978309
thanks to tiad8 for the 3d files main topic address
http://forum.xda-developers.com/showthread.php?t=852937
note guys it's just a collective topic to make it easy for the noobs and am one of them don't be angry coz i got ur work and edited it a lil bit,,,
__________________________________________________
u can find the apps needed for keyboard restarting in androidapps folder
__________________________________________________
this allows u to get :-
Battery Life ( woooooooow so nice)
Bluetooth ( u can accept items efficiently i havent tried to send)
Wifi (nice but not so fast)
Baclight Control
Landscape Support
Phone ( WHEN u accept a call and u find no sound from the ear speaker just press the speaker button two times after u answer ur call)
Browser ( nice )
3D (playing angry birds lite so smoooooooooth)
working 3.5mm jack
SMS
_________________________________________________
Keyboard not working
Hi
I formated the SD-Card, went trough the installation as described, but when it comes to add my Googleaccount I have no way to enter any data since there seams no Softkeyboard installed and also the Hardwarekeyboard does not work.
Any information, how I can proceed?
Regards
agadir9866
unfortunately the buttons dont work after installing
semiran said:
unfortunately the buttons dont work after installing
Click to expand...
Click to collapse
read first post!!!
It seems like you forgot to say that some keyboard application should be downloaded and placed on SD card before taping a script code that you have posted in Emulator, because at the time of first run there is no possibility to tape anything at all (HW keyboard doesn't work without running the script, but the script itself cannot be run without it) Anyway it is useless because there is no way to run Edit command within Gscript, because... HW keys don't work!
Please, correct your first post keeping in mind that HW keys don't work without some doing.
Anyway, it could be a really good thing, it runs so smooth!
so i should copy
Better KB.apk
Ginger KB.apk
Smart KB.apk
SwiftKey KB.apk
to the root of the sd card first before i run haret is that correct?
Here is the guide wich allows you to wake keyboard with 1 click instead of rebooting the device. Guide is for freshly installed android (so no just updating the kernel).
1. Move autostart.sh from the included Folder and place it to your SD card
2. Install android like normal.
Until step 8, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. Launch "Terminal Emulator". Soft keyboard should pop up.
4. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
5. Type "mkdir /data/opt" and press Enter.
6. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
7. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
8. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
9.Install application "autostart.apk"
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading ...
10. Install application "GScript Lite".
11. Open GScript Lite.
12. Press left softkey (menu) and select "Add Script".
13. Load (XPEROID Gscript Button restarter script.sh)
14. Press save.
15. Return to the homescreen
16. Hold your thumb to get "Add to home screen" menu.
17. Select Shortcuts --> GScript Lite --> Script that you just created.
And now, each time your keyboard or front keys stops working, simply press camera key and tap on that icon you've just created
P.S.: this is not my work, i have just adapted what users seandean and yaana created. All credits go to them.
ON screen soft keyboard not present?
I can notate that screen keyboard is not present/installed?
And for the keyboard you can connect the phone through adb shell navigate to /sdcard/ and do the next:
chmod 775 autostart.sh
sh autostart.sh
Then you can do the configuration above ;-)
Hi , everything sounds good.
I am going to install / try directly when i am free of work
Most steps are normal steps when installing Android on X1.
However i do not understand what is meant by:
"open terminal emulator then type the following". Could someone explain how to do this (open terminal emulator)?
Is this done when having booted in Android? And if yes, how can i do this
Many MANY thanks in advance.
Willp ost results when i have had the time to test tonight
EDIT: ok tried it....looks VERY smooth, however i cna not get terminal emulator to do naything..
The peeps above are right... no soft Keyboard is present.
Any easy solution to this? (asume i have to install a soft kb first i gues...think i will give that a try.
Well i got this version up and running .
I just installed a software tobo myself and then i went through all the steps required.
Have not yet had much time to check the possibilities and speed.
but first impressions are good
(before this one i had the honeycomb V2 Android running. this one "feels" better.
Wifi: still unstable (on/off at random, like in every build i installed)
Speed: looks VERY good
Battery: hard to say, going to see how long he will be up today.
Charging: Still have to connect in winmo in order to be able to load
Software: Market etc. running very good.
Going to test upcoming time and report in
Hi
I formated the SD-Card, went trough the installation as described, but when it comes to add my Googleaccount I have no way to enter any data since there seams no Softkeyboard installed and also the Hardwarekeyboard does not work.
Any information, how I can proceed?
Regards
agadir9866
Click to expand...
Click to collapse
well sth have gone wrong i thought there is a software keyboard in the rom
ok u can find the app in the 1st post attachement
u have to download the SW keyboard and put it in androidapps folder in ur sd card
for the hardware butons u have to do all the steps accurately
u didn't do this steps
you must do this to make ur button work and to be able to restart it by one press
open terminal emulator then type the following :-(press enter when u write the letters in each line)
Code:
su
mkdir /data/opt
cp /sdcard/autostart.sh /data/opt
chmod 755 /data/opt/autostart.sh
Then install autostart.apk (found in the rom source folder)
When your buttons stop functioning, you have to run a script from GScript that reinstalls the modules so they work once more. Perform these steps:
Install GScript.apk
Open GScript Lite and press <menu> button, then <add script>
Press the <Load file> button.
The script you need is located autmatically and is called "XPEROID Gscript Button restarter script.sh"
Select it and then in the new screen press <Save>
You can now return to your homescreen and add a shortcut to the script so you can reset your buttons easily. To do this do the following:
Press <menu> and then <add> to add widgets.
Select <shortcut> from the list and then locate and select <GScript Lite>
Then select the "XPEROID Gscript Button restarter script" and you now have a shortcut on your homescreen to reset your buttons.
Click to expand...
Click to collapse
____________________
It seems like you forgot to say that some keyboard application should be downloaded and placed on SD card before taping a script code that you have posted in Emulator, because at the time of first run there is no possibility to tape anything at all (HW keyboard doesn't work without running the script, but the script itself cannot be run without it) Anyway it is useless because there is no way to run Edit command within Gscript, because... HW keys don't work!
Please, correct your first post keeping in mind that HW keys don't work without some doing.
Anyway, it could be a really good thing, it runs so smooth!
Click to expand...
Click to collapse
thx dude i edited it
Well i got this version up and running .
I just installed a software tobo myself and then i went through all the steps required.
Have not yet had much time to check the possibilities and speed.
but first impressions are good
(before this one i had the honeycomb V2 Android running. this one "feels" better.
Wifi: still unstable (on/off at random, like in every build i installed)
Speed: looks VERY good
Battery: hard to say, going to see how long he will be up today.
Charging: Still have to connect in winmo in order to be able to load
Software: Market etc. running very good.
Going to test upcoming time and report in
Click to expand...
Click to collapse
thx dude waiting ur feedback
so i should copy
Better KB.apk
Ginger KB.apk
Smart KB.apk
SwiftKey KB.apk
to the root of the sd card first before i run haret is that correct?
Click to expand...
Click to collapse
just copy the kb in attachements to ur androidapps folder in ur sd card
anyone else has trouble with automatic reboots and freezes of this stable rom... :S
had this installed and tried it today, but it rebooted over 10 times already!
Yes, launcherpro doesn't really works properly?
proces android.process.acore
Click to expand...
Click to collapse
and the phone reboots like every 5 min...
anyone else has trouble with automatic reboots and freezes of this stable rom... :S
had this installed and tried it today, but it rebooted over 10 times already!
Click to expand...
Click to collapse
Yes, launcherpro doesn't really works properly?
proces android.process.acore
and the phone reboots like every 5 min...
Click to expand...
Click to collapse
well guys i swear am using this build without any problems it's so smoooth
i haven't experienced this problem so plz make sure u obeyed the instructions and u made the ext2 partition
bob 4ever said:
well guys i swear am using this build without any problems it's so smoooth
i haven't experienced this problem so plz make sure u obeyed the instructions and u made the ext2 partition
Click to expand...
Click to collapse
I really followed the instructions as in the first post, I also made the ext2 partition, so I don't know
plz give it a 2nd try and tell me
Ok, installing again as we speak.. but thats only because it has dutch language support
(ok, ok, ánd because of full launcherpro version
ánd beautifull widgets (even while i dont use the widgets)
but it would be so much perfect if...
- keyboard would be installed on start (since no soft-keyboard is installed by default)
- kernel will be updated to last (Duckly's Kernel [3-9-2011]) (it also contains changelog = No Sleep Of Death)
- maby overclock to 650 Mhz (or is it already overclocked?
- betterterminal ssh would be fixed, or deleted, because both times i installed it didnt work..
(java.io.IOException: Unexpected http status code 404 Expected 200)
Jhonnie's own graphic request:
- auto-install startupcleaner would be banished,
it has a hideous icon in top! Juch! (and it can't uninstall it )
- bootanimation.zip will be changed to gingerbread's one
- why it got the fancy transitions between screens? fast, but may be to kinky.....
(can i disable the transitions in android install??)
Q's:
1.can some1 tell me how i do install drivers for ADB/debug usb?
2.does the android setup (first boot) always crash?
3.if you add autostart to AndroidApps, does it really autostart keyboard drivers,
or is this a one-time install android ever..?
If you are looking for how to get back to stock Bell, go HERE.
Disclaimer: I have not tested this on anything but my phone. This is a development section of a hacking website. Make backups. Know what you are doing.
Credits:
Brut.all for apktool
edgan for 2nd-init
designgears for aroot inspiration.
xda for being a source of info.
Requirements:
Windows 7 or Ubuntu 10.10+ (10.10 and 11.04 tested)
Java installed. (For applymods, it uses apktool)
Running Phone, not in recovery mode, etc.
Tips:
Don't factory reset please if something goes wrong, it just erases your personal settings, it doesn't write to the system partition. It also deletes your data partition, making it harder to get back to stock.
Early usb mode, turn your phone on while holding down the lower volume button, when it says fastboot, release and press volume down repeatedly until it says early usb enumeration, then press up volume. It takes 30 seconds or so before adb is ready.
Version 9:
Download it here.
What's new:
Added support for 2nd-int (WIP, tested on stock Bell only)
shsu updated to allow a super user to become a super user, acts like sh in that case.
fixed linux install_recovery.sh and uninstall_recovery.sh scripts to use shsu instead of remaining using su. Ditto with ApplyMods.sh
Boot animation now smaller, using jpegs instead of png files, no difference in appearance.
Version 8:
Download it here.
What's new:
Added full phone backup and full restore phone options to the menu. It will download a backup if there is none found.
root script more universal, tries psneuter first, then gingerbreak.
Early usb recovery updated, now uses a tmpfs for system, also mounts /sdcard and /sdcard-ext.
Deodexed French 2.1.1 files incorporated.
Misc fixes
Version 7:
What's new:
New Menu script for windows and linux in the top folder, double click Menu and enter options.
ApplyMods and other scripts updated to use /data/local/tmp/system, this means I can update system.tar.gz and add folders to be copied into system.
Early USB enumeration recovery option. (experimental but useful as is)
Fixed bugs in windows scripts. Can't get user input from bat file while in a parenthesis block apparently.
Bloat backed up to sdcard now
root and unroot scripts updated with more prompts for rebooting phone.
Version 6:
What's new:
Support for Telstra 1.4.2.
ApplyMods can create signed update.zips now, Create_update.bat updated. both using basic ready made scripts in main bin folder instead of creating them on the fly, CR LF issues.
Updated root and unroot scripts, more fool proofing, has to be Bell stock firmware (psneuter doesn't work on telstra).
Includes basic boot animation, and mod for Bell apn on telstra firmware. (Have to reset to default under access point names in settings.)
transparent status bar, yellow tinted white for text color, matches front buttons somewhat.
Version 5.1:
Features:
Works under Linux and Windows 7
Includes root and no ads scripts
Patch system for applying modifications.
What's new:
New scripts for doing mods, fixes issues with patch 9 images.
Updated root and unroot scripts, more fool proofing.
New RestoreSystemPartition script
Custom apktool for more [hopefully] bug free installations.
How to use:
Extract archive, keeping folder structure intact.
run a command prompt/terminal (There is a link to one in the windows folder)
run root.bat or root.sh from the linux or windows folders, depending on which one you are using.
Turn the phone off after that is done and turn it back on again.
The rest of the scripts shouldn't be run with psneuter affecting the phone.
run ApplyMods.bat (.sh) [OPTIONAL] This applies webtop hack and translucent status bar, translucent notification drop down, etc. Select update system.tar.gz.
run install_bell_deodex.bat or .sh
System image of stock Bell.
Mirror of above
Cheers!
Very nice! Looks good!
Will try this when I get home
Sent from my Motorola Olympus
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Sent from my MB860 using XDA Premium App
cool, i'll try this tomorrow when i don't still have a ****load to do and only 5 hours to sleep
nice to see a Bell dev here!
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Atrices, just so you know
NFHimself said:
Hi,
(What is the plural of Atrix?)
Click to expand...
Click to collapse
Can I run this on my mac? Sorry relatively new to adb
Sent from my Motorola Olympus
you could run it on a mac, just had to edit the script a bit.
Hi,
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
Click to expand...
Click to collapse
I wouldn't try theming with ATT files, I would take what was done to them and apply them myself to the deodexed files here. There may or may not be differences that are not obvious. I am never really sure if there is any benefit to this stuff, it's fun to do, about it.
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Click to expand...
Click to collapse
The soft_brick.bat script is specific to the folders I am using for transferring data to /system/app and /system/framework. It tries to get root via psneuter, mounts system read write, deletes dalvik-cache files, and tries to copy the files already on the phone to the right folders. It could be that just one file caused the phone to crash mid copy and copying it again will fix things. This avoids trying to do a usb data transfer of all the files which you don't have time to do otherwise. I was also thinking that install-recovery.sh would be a good place to do this, (and then clobber it later with the init.d hack) but I couldn't find setprop and I wasn't in need enough to select a file to use as a semaphore.
Can I run this on my mac? Sorry relatively new to adb
Click to expand...
Click to collapse
It would be easier to do it all from a sh script really, and that would likely be more compatible with a Mac.
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Click to expand...
Click to collapse
Thanks!
Cheers!
maledyris said:
Atrices, just so you know
Click to expand...
Click to collapse
Thanks, a lot, really, 10 chars..
How do I recover from a softbrick from this? Thanks.
Before anything is done, all the files are extracted to /data/local/tmp/app and /data/local/tmp/framework. If you run into problems put the phone into fastboot/early usb enumeration mode (see here) and run soft_brick.bat (.sh for linux)
Quote:
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
This is the message I get when i run the batch file.
This is of course when invoking Early USB Enumeration.
Wait for the count down to finish ...
'TIMEOUT' is not recognized as an internal or external command,
operable program or batch file.
clearing Dalvik cache..
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or director
y
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directo
ry
reinstalling apps
cp: cannot stat '/data/local/tmp/app/*': No such file or directory
reinstalling framework..
cp: cannot stat '/data/local/tmp/framework/*': No such file or directory
done.
The timeout message means you are running a version of windows without timeout, see adeo thread.
The lines for rm just mean there are no files to delete in the Dalvik-cache, which is normal, you should see that the second time around.
The cp lines are saying that there are no files in /data/local/tmp/app (/framework).
So, that's unusual, in order to get soft bricked using my script you would to have copied files from /data/local/tmp to /system, and if you are bricked would be unable to delete the files afterword.
sequence:
cd /system
cp /data/local/tmp/app/* app/
sync
reboot now
**brick**
So, how are the /data/local/tmp/app files being deleted?
No clue. I'm not sure what to do here? Is my phone permanently bricked? Any other way to recover from this? The one thing that could have gone wrong is I tried installing from my behind my works firewall. Maybe I could not download the proper files.
No, you are soft bricked, you only made a change (that I know of) in system files.
Were you rooted before you tried this?
If you copy the soft_brick.bat files and change the last line to be adb.exe shell ls -R /data/local/tmp, what do you get?
Basically, it sounds like to need to get the files copied over to data/local/tmp, how they are missing/inaccessible is odd. So, create a script to copy the files over bit by bit, might take a while but it should be able to be done.
EDIT:
Do this:
from command prompt:
adb.exe shell ./data/local/tmp/psneuter
wait a few seconds
type this:
adb shell ls -l -R /data/local/tmp
if psneuter fails, it isn't in /data/local/tmp, which is also odd.
I was rooted before this. So I should attempt all these commands while Early USB Enumeration right? That doesn't give me much time Lol.
OK, here's the output.
C:\bell_deodex>adb.exe shell ./data/local/tmp/psneuter
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
property service neutered.
killing adbd. (should restart in a second or two)
C:\bell_deodex>adb shell ls -l -R /data/local/tmp
/data/local/tmp:
-rwxr-xr-x root root 585731 2011-01-09 02:02 psneuter
-rw-r--r-- mot_tcmd mot_tcmd 4 2011-03-30 21:00 ap_tcmd.pid
C:\bell_deodex>^A
And sorry to be a pain. How would I create the script? What are the files that need to be copied? Are they included in your script?
Hi Guys,
This is driving me crazy. A lot of people, who are too lazy to search. Well, here you go.
Allright, you brought your Xperia X1 with android. Now, there is a problem. Once in a while, the keyboard does not respond, only action is a reboot. HELP?
Allright, lets get started.
Download this package:
http://www.mediafire.com/?cp1o1glxjo145pu
Install a android of your choice(just normally).
Unpack, and copy all (yes, all) contents to you SD card.
Move the turbo or Monster kernal to the NKBoot Map, click yes to replace any excisting files.
On your computer, open up the readme, and read it carefully.
After step 4(after you entered 'su') type this:
rm /lib/modules* -rf
That will remove your current modules, and at the next boot, they will be replaced.
Reboot, and proceed with step 5 and the rest. Follow the guide excactly, then you're good!
Have a nice evening!
Not Test, But Thanks You !!!! I Need
sorry to say but when i folled your guide to just after step 4 when typing the -rf
it says cannot remove read only file system
is that normal?
thanks
yes it is. just reboot after the error, then the new modules will install!
Just thinking ... a dev might know it this is possible ...
Hm, perhaps, best solution at the moment would be, to run the unload-load-script when the phone is waking up from sleep mode. So, when keypad is lost, the user can send to sleep with the power button an immediately switch it on again ... and additionally, the script can run when a call comes in ... don't know if these events can get picked up and the event-handlers can be changed, just thinking ...
Ciao
Klaus
Kurt Krummbein said:
Hm, perhaps, best solution at the moment would be, to run the unload-load-script when the phone is waking up from sleep mode. So, when keypad is lost, the user can send to sleep with the power button an immediately switch it on again ... and additionally, the script can run when a call comes in ... don't know if these events can get picked up and the event-handlers can be changed, just thinking ...
Ciao
Klaus
Click to expand...
Click to collapse
Don't know if this could be a good option. Because I have had some freezes when runing the script. And sometimes the screen changes it orientation.
thomskipsp said:
After step 4(after you entered 'su') type this:
rm /lib/modules* -rf
Click to expand...
Click to collapse
casualt said:
sorry to say but when i folled your guide to just after step 4 when typing the -rf
it says cannot remove read only file system
is that normal?
thanks
Click to expand...
Click to collapse
Shouldn't it be?:
After step 4(after you entered 'su') type this:
rm /lib/modules/* -rf
mind the /
Anyway, I tried both ways, and rm /lib/modules/* -rf seems to work, but I can't load back into CWM if I install a kernel with seperate keyboard modules. I think I mess up the exact order of installing normal, removing modules, replacing kernel, restarting. Hope this will work
http://forum.xda-developers.com/showthread.php?t=1072387
Yes. I can restart keyboard after freeze. Although with eggy monster kernel, my screen is rotated 90degrees after that.
No. I can't get back into CWM, after I switched to a kernel with seperate modules.
The original kernels of Honeycomb v3 both worked.
I tried the kernels with seperate modules of this post and i tried the ygge kernels.
Can this be solved? No. But apparently, there is a workaround http://forum.xda-developers.com/showthread.php?t=1072387.
when I type "sh /data/opt/autostart.sh" and press Enter, I get this error:
"insmod: can't read '/lib/modiles/microp-ksc.ko': no such file or directory
insmod: can't read '/lib/modiles/microp-keypad.ko': no such file or directory"
Can you help me?.
Where is kovsky keyboard modules????
I using ygge kernels with HoneyComb Froyo V.3
PS: sorry I used the same post in several threads
I have to open a new thread here because I can't still post in the android section, by the way I've tried to follow the instruction found in this post for solve the keyboard freezing problem but I when I launch the script it says that he can't find the 2 files it have to launch, and opening the folder by the terminal or by my ubuntu I can't found the 2 files
/lib/modules/microp-ksc.ko
/lib/modules/microp-keypad.ko
anyone knows why?
a member wrote on the same post that he had the same problem, so he have deleted some files and have run the new kernel...how can I launch the device with another kernel?
thank you
Hi,
answer is easy (well, for those who looked behind the scenes), at boot, the system checks if the kernel-modules on the sdcard are different from the installed in /lib/modules ... and due to the fact that the kernel version is the same (just with the keypad drivers optional as modules), the unpacking of the tar.gz-archive is skipped.
You have two options now, use the 'Terminal Emulator' and do a:
su
rm /lib/modules/*
and reboot your phone, or copy the two modules from the tar.gz in ubuntu.
Ciao
Kurt
I have tried the first before opening this thread without any result, now I'm retrying
ehm...now the script runs...but I can't use the onscreen keyboard and everytime I enter an app the screen rotates...is it normal?
and if I press camera button it doesn't return to the home
Hm, rotating the screen is not normal ... just if he thinks you pulled out the 'real' keyboad.
I think, the camera button of Honeycomb froyo is prepared for camera usage ;-).
Hm, perhaps, best solution at the moment would be, to run the unload-load-script when the phone is waking up from sleep mode. So, when keypad is lost, the user can send to sleep with the power button an immediately switch it on again ... and additionally, the script can run when a call comes in ... don't know if these events can get picked up and the event-handlers can be changed, just thinking ...
Ciao
Klaus
This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread
dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?
hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them
thats amazing, will try it as soon as possible
SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx
Work work work, thank you bro .
uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.
I tried it, it's working. Thanks for the mod
I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.