[Version: v4b] SEX1 Android Kernel - XPERIA X1 Android Development

This is the bug fixed version of the “v4a” kernel that should work for all Android distributions for Kovsky (Xperia X1).
Change log:
+ Upgraded to GIT commit e83e7c3fccf8423bd0cf489f852f830ca6e80259
+ Kernel debugging and certain associated options for OS compatibility
Release Notes:
I’m providing two versions of “v4b” for regular and advanced users. At this time the only difference is the keyboard and buttons driver either being build inside the kernel (regular version) or outside in the modules (advanced version). In future versions there may be additional differences, but they will be detailed in my release notes.
Keyboard and buttons modules HOW-TO has been explained in other threads, if you’re thinking to yourself that you have no idea what I’m talking about I suggest sticking to the “regular version”.
Known Issues:
You will require the November 29 3D driver found at this thread: http://forum.xda-developers.com/showthread.php?t=852937. If you don’t install this your device will function completely normal outside of 3D games and applications. IMPORTANT NOTE: don’t install the gralloc driver as it will cause the screen driver to eventually lockup (otherwise known as SoD).
The camera has been fixed in the kernel source code, but the libraries in Android have no support for it. It’s not an easy fix, and it’s not going to be fixed anytime soon so support has not been built into the kernel.
Keyboard and buttons will eventually fail, this isn’t new but using a method posted in this forum for reloading the drivers (advanced version only) works!
The battery driver is very accurate up until about 50% left being reported in Android. After which it becomes somewhat unstable, reports incorrectly and may force shutdown (softly) your device. My best suggestion; consider 40-50% left as 0.
Smart feedback is appreciated.

thanks alot i will tested and back with feedback soon

are android camera libraries particular to each device or can we use libraries from other devices?

Here is the guide for advanced kernel, which 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. Extract autostart.sh from the included archive and place it to your SD card
2. Install android like normal.
Until step 9, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. If you don't have it in your release, install "Terminal Emulator" from market
4. Launch "Terminal Emulator". Soft keyboard should pop up.
5. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
6. Type "mkdir /data/opt" and press Enter.
7. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
8. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
9. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
10. Go into the market and search for "Autostart (Root)". Install that application
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading, otherwise you can close this page.
11. Install application "GScript Lite" from market.
12. Open GScript Lite.
13. Press left softkey (menu) and select "Add Script".
14. Type any name, like "Fix Keyboard".
15. Tick "Needs SU?" and press "Load File".
16. Type this into bottom window:
Code:
#!/bin/sh
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko
17. Press save.
18. Return to the homescreen
19. Hold your thumb to get "Add to home screen" menu.
20. 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.
For the kernel, first impressions are OK. Testing with release "Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010]" release + nov29 3D driver. Artefacts still present when turning device on. I will report more after testing it out a bit more.

Camera Libraries
CowMix said:
are android camera libraries particular to each device or can we use libraries from other devices?
Click to expand...
Click to collapse
HTC Touch Diamond Camera library is pefect.
http://gitorious.org/~jbruneaux/linux-on-qualcomm-s-msm/linux-msm-home-work
http://www.youtube.com/watch?v=vhz0sPjT2UA

Im testing it now on CM6.1 Barebone with 3D drivers and autostart.sh
Wifi works
GSM works
fps2d: 28FPS
Neocore-no sound: not tested
Camera is not working
3G works
Bluetooth not tested
GPS works
Notification leds work with charge state (when start android attached charger)

i cant use this kernel..
when run haret, it comes error and then boot to WM back..
it said "can't mount fs......"
help me..
is it something wrong??
im using CM6.1

are you using windows 7 OR vista ?
if use this OS , you need to remove SD card and use card reader then recopy the kernel files , use v4b advnaced with autostart.sh
regards

im using ubuntu 10 and win xp..
i try to port it same as i port the other kernel..
but the other kernel work and not getting error when running haret,but with this one i got error..
thanks for quick reply..

matejdro said:
Here is the guide for advanced kernel, which 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. Extract autostart.sh from the included archive and place it to your SD card
2. Install android like normal.
Until step 9, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. If you don't have it in your release, install "Terminal Emulator" from market
4. Launch "Terminal Emulator". Soft keyboard should pop up.
5. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
6. Type "mkdir /data/opt" and press Enter.
7. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
8. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
9. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
10. Go into the market and search for "Autostart (Root)". Install that application
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading, otherwise you can close this page.
11. Install application "GScript Lite" from market.
12. Open GScript Lite.
13. Press left softkey (menu) and select "Add Script".
14. Type any name, like "Fix Keyboard".
15. Tick "Needs SU?" and press "Load File".
16. Type this into bottom window:
Code:
#!/bin/sh
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko
17. Press save.
18. Return to the homescreen
19. Hold your thumb to get "Add to home screen" menu.
20. 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.
For the kernel, first impressions are OK. Testing with release "Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010]" release + nov29 3D driver. Artefacts still present when turning device on. I will report more after testing it out a bit more.
Click to expand...
Click to collapse
you can skip the steps 14 to 16 by downloading the attached file and pressing load file when you are in the new script page. so instead of typing all those comands you can just load this file and save it.

I have tried that, but for some reason it showed me blank screen instead of script file browser.

matejdro said:
I have tried that, but for some reason it showed me blank screen instead of script file browser.
Click to expand...
Click to collapse
it works for me most of the times but it sometimes restart the device maybe typing it out is the best way

im testing the android right now and it is a good one but i got one problem.
when i unlock my screen i got a rare screen sometimes whit green dots and sometimes whit stripes. anyone knows how to fix that?

xorium said:
im testing the android right now and it is a good one but i got one problem.
when i unlock my screen i got a rare screen sometimes whit green dots and sometimes whit stripes. anyone knows how to fix that?
Click to expand...
Click to collapse
its a known issue no it hasnt been fixed yet this problem started from v4a

kerfooly said:
its a known issue no it hasnt been fixed yet this problem started from v4a
Click to expand...
Click to collapse
okey tanks for the info

how van i connect from in android to my pc for data exchange between my sd card?
when i plug it in my computer says that i dont have the driver?

Hi!
I have been testing Android and various Kernels for a while. And I have got no good answer to a question I have. I cant get bluetooth headset to work. Cant pair them. The answer I got is that its not fixed and that it is kernel issue. Bluetooth seems to work but not to connect pheriperals.
Is there a plan for this to work or is it a thing for the future?
Its the one thing before it can actually be used for day to day work. Lotus Traveler is now released for Android so sync should work.

today i got a isseu i runned android from yesterday evening until this afternoon that my buttons dont work again. only the camera button. how can i fix this? or is it retyping the codes again?

Here working very good on CM6.1
During boot there is a line containing something like:
[KOVSKY]: is ac online == 0
or (if charger is plugged in)
[KOVSKY]: is ac online == 1
Maybe it is possible to set this parameter to be '1' at boot? So the charger would work either it is connected or not while runnig 'haret.exe'

why its not going to work for me!!!!!?????????
why it is so hard to port????
its say cannot mount partition,cannot mount fs....bla...bla...bla...
HELP ME PLEASE WITH THIS V4B KERNEL..
IM STUCK AT HARET AND THEN BOOT TO WINMO BACK..
TRYING 10000000000000 TIMES TO PORT IT..

Related

HOWTO run ANDROID on X1

This thread puts all the necessary steps together for sucessfully run the Android-release from THIS thread on the X1. Since many seem to have problems with that this may become handy
So lets get started!
What you need:
- latest XPEROID-release, fatsal-xperoid-20100221.7z, get it here
- 7zip to extract it, get it here
- sd-card, using fat32-filesystem with 500MB free space
What you need to do with it:
1. Extract fatsal-xperoid-20100221.7z on your computer. This will give you the following files:
- calibration, wlan-firmware
- haret.exe, runs the linux-kernel and android
- initrd.gz, initial ramdisk, needed for linux to boot (phase one)
- modules-2.6.27-00888-g339bdfc-dirty.tar.gz, linux- and android-driver for wlan
- rootfs.img, contains files needed for linux to continue boot (phase two)
- STARTUP.TXT, contains the parameter for haret.exe and boot-options for linux-kernel
- system.sqsh, contains all android system files
- zImage, contains the linux-kernel
- conf/*.user.conf, configuration files for android
- AndroidApps/*.apk, applications for android, installed during boot
2. Delete all the *.apk-files from the AndroidApps-directory. They are not needed for running android. You should keep the directory, just delete all files in it.
3. Download some essential android apps here, you will get essential_apps.zip. Extract it and put the apk-files into the AndroidApps/ folder.
4. go to conf/ and delete eclair.user.conf, then rename eclair.user.conf~ to eclair.user.conf. That will disable the swapfile.
5. open startup.txt and remove the mem-option mem=102M. This was suggested by hotlein here. That will increase the memory from 102m to 182M and improve android speed alot.
6. Copy all files and directories to the root of your sd-card. Do not create any directory, just copy them to the blank sd-card.
7. Put the sd-card in your phone if not already done. On the X1 open the sd-card and run haret.exe. You will get alot text running across the screen. During the boot-process, one file is created.
- data.img (256M). This file contains all the files normaly stored on the android-phone. Your settings, Applications, media, etc. You can always delete this file to reset android. It will be recreated.
First boot takes a while to complete, so be patient. Finally you should get the android welcome screen. Follow the on-screen-instructions and you are done!
Changing some settings
- IMPORTANT: Disable GPS in settings -> location & security -> Use GPS satellites, because it will hang the device!
- Turn off locks screen when holding red call button. Spare parts -> End button behaviour -> Nothing. That will simplify the shutdown procedure. Credits go to Reversedhex: Post
Now let's stop android
1. Press and hold the end-call-key. The phone starts to vibrate like crazy, ignore that.
2. After a few seconds a menu pops up. Dont release the button yet, keep holding it! If you changed end button behaviour, you can release it now.
3. Press down on the digi-pad. You may press it three times to go to the shutdown-option.
4. Now you can release the end-call-key. If you do not hold it, you will end up in the android lock screen.
5. Select shutdown option and confirm. Then android shuts down.
If you try another kernel-image (that is replacing zImage), the system may lock up during shutdown. Then you have to soft-reset your phone. But you should always try to shut android down.
Now you can update the linux-kernel:
1. Download the kernel-image, get the latest here. That gives you zImage_kovsky_20100325.zip.
2. Extract zImage_kovsky_20100325.zip to get zImage. This is the linux kernel.
3. Copy zImage to the root of your sd-card. You should always back up your existing zImage so you can go back.
4. Download wlan-modules, as they must match the kernel-image, get them from here. That gives you wlan-modules_20100325.zip.
5. Extract wlan-modules_20100325.zip to get modules-2.6.27-01006-ga30aafa-dirty.tar.gz. This archive contains the wlan modules. Do not extract this. Simply put this on the root of your sd-card. On android startup this file will be extracted on the modules copied for you.
As suggestet by angusmcb (post), i used for the latest kernel the latest cross-compiler.
Latest kernel from xdadev-repos with backlight control and correct battery readout, get it here. The archive also contains matching wlan-modules.
Troubleshooting
Q. Android will not boot
A1. check if all needed files are present
A2. check if you have enough free space on card. Android creates two big files during first boot, so you will need at least 384M free space.
A3. you can try to delete data.img and swapfile to reset android. This helps if you messed up settings in android.
Q. Wlan wont start
A1. check if file calibration on sd-card-root
A2. check if file modules-*.tar.gz matches kernel-image
A3. you may try to enable wlan in windows mobile before running haret.exe
Q. How to stop android from using data connection
A. go to settings -> wireless & networks -> mobile networks -> access point names and delete all apn-settings
Q. Android-screen is upside-down
A. Slide out keyboard -> android switches to landscape. Then slide keyboard in -> android switches to correct portrait.
Q. I have no ringtones
A1. Put the ringtones in the MEDIA\AUDIO\ringtones folder (post, post for folder structure)
A2. Take a look at this post. Some characters make the android media scanner crash.
Q. I can not enter pipe-symbol. Where to find keymaping
A1. Press function key, followed by shift key, followed by commer key (right hand side of space bar) (linuxtux post)
A2. For keymapping in general take a look here. That is the default android keymapping.
Q. I want live wallpapers
A. Here you go. But be prepared for performance loss.
Q. I can not send SMS
A. Check this post by jimipoh. It might help.
Done for today
reserved for future updates
also reserved for future updates
and this, too
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
What the F?
♥♥♥
Good luck~♥
Muo said:
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
Click to expand...
Click to collapse
This thread is mainly about how to get android working. I am trying to speed android up by partitioning the sdcard as fatsal mentioned. If it works there will be a HOWTO for that, too.
Until then i will continue to work the linux-kernel for X1-android until it is done (or i loose my X1, too )
This is pretty consize. I hope it sums up all the main points of fatsal thread on android
With zImage_kovsky_20100313.zip system always lock up during shutdown
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
No no no! Your doing it wrong!! D:<
gbajzelj said:
i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
Unfortunately, due to certain hardware limitations of the X2, boot time of the X1 kernel on the X2 can take a little longer. About 1.2 seconds after the sun explodes and extinguishes all life on Earth 4 billion years in the future, is a good estimate.
Sorry
vdelf, will you be committing regularly to gitorious? Or do you have a scratch repo for messing around with?
vdelf said:
also reserved for future updates
Click to expand...
Click to collapse
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
i had the bin/sh error too , first time.
when simply retrying -> it booted up to the "exploding X".
however, that screen froze on me.
i seem to get more progress though than with the material from the original threads.
the material from this topic has gotten me further than ever before. as i speak i'm booting a fresh one with the new kernel (from the start). it's upside down, but i hope this one works 'out of the box'.
persistence is paramount, as time passes the chance on reaching satisfaction approaches 1. how this satisfaction is achieved is up to you; may it be through running XPEROID, purchasing an android phone or simply giving up.
I managed to get it back to the "exploding X" screen (using the first file, not the kernel update).
It seems to be stuck in the X screen though, it's looping (and stalling a little) for 20 minutes now. Last time I soft-resetted the phone after about 10 minutes of X-screen, and it mangled my sd card (meaning I had start from scratch). There is no text (or error message for that matter), so I don't know what is going on.
Is anyone familiar with this?
EDIT:
I paused my attempts for now. Same result over and over. I'm not able to find anything on this in the original thread (or possibly when I read every single post I might find something), search reveals nothing to me.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
You have to use a version of haret that supports your phone. As X1 and X2 have not identical hardware (or do they?) someone has to code X2-support to haret. Until then it will not work.
In startup.txt there is this line
Code:
set mtype 2006
This is for kovsky X1. For X2 there has to be a different value, but dont ask me about that
dawen said:
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
Click to expand...
Click to collapse
It seems that your sd-card has no partition. If you use linux, you can check this very easy. On windows, you can try to reformat the card.
You can also try another card.
Woudnt it be possbile/smarter to put the android on your xperia's internal memory (when you have 300+mb free?) or woudnt there be any diffrence in speed?
can you install apps from the market
or do you have to manually do it (pasting the apk to the sd)
?

(25/3)Best and most stable rom ever[ext2][daily-use]

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..?

[Q] solving keybord freeze on honeycomb froyo v3

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

[ROM][ICS][AOSP] Lenovo Ideapad K1

This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning
So from now on we will be able to flash future updates through recovery without wiping everything?
So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.
That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.
Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.
me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...
That's great. thanks for share.
Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.
Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?
I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.
I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.
Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
several more freezes. obviously not depending on any special app..
erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie
Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!
Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1
Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423
For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!
Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423
After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?
Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?
Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible
Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.
hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch
Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!
riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.
mediafire link is dead (twrp) - please, reupload it!
Thanks so much for this, it worked perfectly! So great to have my watch back!
Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.

Categories

Resources