yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 Android Development] astearon:
WOW

Can't wait for sp3dev to port the 2.6.35 ! That would truly rule!

On a side note there is something you guys missed out in the kernel. Since the optical trackpad does not work why can't the led that helps it track be turned off? It can be seen on all the time when the front panel is lit. i think that would help battery saving a little bit more.
[XPERIA X1 Android Development] pirlano:
i think Alexander (sp3dev) will release 2.6.35 once it's fully working :)

now you can build new kernel but it lacks many features, it's not really usable for now :)
[XPERIA X1 Android Development] stefanACM:
I just wanna ask for one REALLY IMPORTANT THING !!!

Why i can't download anything form MARKET over WiFi, WiFi keep crashing every secund :| and some process crashing too

Thanks :D
[XPERIA X1 Android Development] cyberdesigner.net:
uhm? not in my case... for me its working... not as fast as it should, but it works.

please try it again on a complete fresh install. it should work!
[XPERIA X1 Android Development] matejdro:
So, then what is the advantage of buttons in modules?
[XPERIA X1 Android Development] seandean:
Unfortunately, there was none.

I was hoping that having them as modules would allow them to be re-loaded (and re-activated) after the button functionality failed. I don’t think anyone reported this method to be a success, so keeping them as modules just created more “my keyboard doesn’t work!” posts even after I clearly wrote what was needed to have it activated after boot.
[XPERIA X1 Android Development] mkbm:
Hi,

I have tested to reload it after the keys stopped working. First I had to remove the loaded modules and after that reload them.

After that the keys started working again. I have made a script that did that automatically. But after that the keys stopped working in a shorter period so that I have to reload them very often.

Right now I have stopped to run Android because I need my phone for work and with every build I had freezes or reboots.
[XPERIA X1 Android Development] stefanACM:
I have that problem on every BUILD from XDANDROID to NEOPEEK...every build...

On some builds its crashing more on some less, but WiFi modul is really crashy...

@SeanDeen

Can you tell me more about that Wirelles problem ??? When i try to download anything from MARKET, WiFi icon disappear from STATUS BAR and MARKET download instantly paused and after 4-5 sec. its continue, download 10-15kb, and again....

Why ??? Can you try to solve that... That is biggest problem i think for now
[XPERIA X1 Android Development] viper.:
First of all you will need to turn on your wifi in winmo. If that doesnt work than you should try this...

Make a fresh install of android (that means :deleting everything that is "connected" to android). Next, use the v3a kernel with superfroyo or frg83 and everything should work fine.
[XPERIA X1 Android Development] stefanACM:
You are SeanDean ?

Anyway

WiFi work!!! New kernels dont need to turn on WiFi on Windows Mobile...

Anyway if you read my post, you must understand that i did formating my memory card a lot of time... And that problem i have from first 2.2 build, for me this is not problem an old data because I am computer engineer and definitely i must know about parititioning and formating an memory :|

Of course i waiting from smart answer from SeanDean or SP3DEV ;)
[XPERIA X1 Android Development] Rubik.Orange:
v3c kernel with Neopeek CM 6.0 and 6.1 is wifi working. But frg83 isn't work. I think frg83 is the problem
[XPERIA X1 Android Development] man_genius91:
hye..

when were camera will work on android?

i'm just wondering to know..
[XPERIA X1 Android Development] Pete Rask:
Preview is working! but ask the devs, they probably have a more qualified answer regarding how much work there's left to get it fully functioning.

http://www.youtube.com/watch?v=vhz0sPjT2UA
[XPERIA X1 Android Development] man_genius91:
wow..nice job..

hope it can be release really soon..

love their work!
[XPERIA X1 Android Development] seandean:
New Kernel - v4a

I have new kernel and modules package to release, as well as an updated autostart.sh for those looking for even more speed. This is version “v4a” which has some minor bug fixes but really focuses more on optimization. When JIT is enabled in Android you can expect Linpack scores around 4.3 and Neocore FPS around 17. This is the fastest kernel for Kovsky released to date.

Change log:

+ Upgraded to GIT commit b8f2cdcc344c2ac3ea8bb424b10a2018463a703d

+ HW3D and FB ported in from 2.6.35 source code

+ Minor feature and compiler setting tweaks, more available memory (now at 200548kB)

+ Updated highest “overclocked” speed to 614.4MHz which I’ve deemed stable (this is obviously subjective – previously 595.2MHz)

- Kernel debugging and certain associated options (CONFIG_DEBUG_KERNEL)

SetCPU notes:

I have found that the “Sampling Rate” is extremely important for 3D graphics, and has little to no effect on anything else. One example is having it set at 5000 which gave me a 13.2 FPS in Neocore, while set at 250000 (my recommended value) allowed for 17.3 FPS.

HW3D notes:

Due to the upgrade in HW3D all distributions (as of writing) due not have 100% compatibility and will cause the screen to flicker when trying to use this functionality. The fix (until built into distributions) is to download the November 29 3D driver and carefully follow instructions from here: http://xdaforums.com/showthread.php?t=852937.

Known issues:

The front-facing button issue has not been fixed, eventually these buttons will stop working for you so be prepared. The camera is not functional, nor does it have the “preview only” ability. WIFI and 3G work, but your setup may require additional steps (e.g. turning WIFI on before booting into Android).

Testing and your “constructive” feedback are appreciated.
[XPERIA X1 Android Development] Devaster:
with latest kernel i had keys not working when i connect a usb cable ....
[XPERIA X1 Android Development] yaana:
Hi seandean, i'm a new user and great thanks to your brilliant works! Would it be possible to release a new kernel with keyboard driver built as modules (as in v3a & v3b)? I found it helps resolve the keypad dying problem. Here's how i tried it (tested on v3b+superfroyo):

1. Install Gscript Lite

2. Add a new script

#!/bin/sh

echo "Restart Kovsky keyboard and buttons"
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko

3. Create a desktop shortcut to the script

4. When keypad dies, just run the script, and keypad will live again!

CAUTION: DO NOT try the script when keypad is ok, it will probably reboot your phone!
[XPERIA X1 Android Development] sjkoon:
Problem!

Error

"Process system is not responding."

CM6.0, CM6.1, SuperFroyo

all same error
[XPERIA X1 Android Development] seandean:
Yes, I will build v4a with both of those as modules tomorrow. The only reason I changed it back was due to less advanced users just not following instructions.

Perhaps going forward I can build two versions, with and without those as modules until we solve the issue in the source code.
[XPERIA X1 Android Development] seandean:
I have attached v4a with those two drivers taken out of the kernel, built as modules and placed inside the attached modules package.

I have also attached the modified autostart.sh for this setup.
[XPERIA X1 Android Development] ddutchie:
seandean do we still need to implement the 3d driver from this thread

3d driver for testing with gralloc.
[XPERIA X1 Android Development] matejdro:
Backing up my apps to wipe and reinstall this new kernel. Will report soon.
[XPERIA X1 Android Development] seandean:
Yes,

Until these drivers are updated by distribution managers they will have to be loaded manually, or you can just overwrite whatever version of the file you had previously. They are still working on perfecting the driver in that thread so I would consider this a moving target – it will eventually change again.
[XPERIA X1 Android Development] matejdro:
New kernel it's not working for me. After boot logo i got "Process is not responding: system". No matter if i press Force Close or Wait, window will close and i will get black screen with mouse cursor in left top corner.

Release is freshly installed CM6 Barebone. Same release worked great with v3c.
[XPERIA X1 Android Development] seandean:
I’ve been doing all my testing this time around using Neopeek’s CM6.1-Barebone.

Can you give that a try?
[XPERIA X1 Android Development] saobang3886:
try with Neopeek’s CM6.1-Barebone, V4A, 3D driver, first time run good, now I will test every thing ^^!
[XPERIA X1 Android Development] Pete Rask:
Battery consumption is defenitely hugely improved!

4% in 8 hours using Neopeeks X1-cm6-28112010 Full with prerelease of v4a, as sharp one doesn't seem to work on CM6. Refer to here.

2% in 8 hours using Neopeeks X1-barebone-cm61a from (11102010 I believe) with v4a from here!

Anyone else getting these numbers?!

Thanx a million Seandean!!
[XPERIA X1 Android Development] saobang3886:
I use X1-barebone-cm61a with V4A, battery about 1% a hour, but when it drop down to 49%, the phone shutdown, I reboot to win mobile and battery show 10% ^^! now i will try with full battery and review how long it shutdown ^^!
[XPERIA X1 Android Development] yaana:
Installed v4a (moduled) in superfroyo, no luck, "Process system is not responding."

So I tried other releases from neopeek:

[Sony X1 only][Barebone][CM6.1][26-11-2010 Kernel update package]-------------------------->OK, with minor glithces(screen scrambles after wake-up)

Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010] (barebone)-------------------------->no luck, "Process system is not responding."

Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010] (full)-------------------------->no luck, "Process system is not responding."

All tests are with new 3D driver installed.
[XPERIA X1 Android Development] matejdro:
I would, but i don't like that release since it's missing a browser.

Any other CM build that works with new kernel?
[XPERIA X1 Android Development] seandean:
Thanks, I’ve issued the following warning to Neopeek build users;

“Early end-user reports are saying this kernel works only on the CM6.1-Barebone Android build. This was also the Android build I conducted all my testing.”

It would be nice if someone using non-Neopeek builds could test this out and report back.
[XPERIA X1 Android Development] Pete Rask:
I've also noticed that above 50% battery meter seems pretty accurate. When dropped to 50% and below the battery itself seems to decrease faster then the meter actually tells.

My readings were done over night (no calls and other incoming/outgoing stuff during these 8 hours) and the 4% I got is measured between 81>77% and the 2% is between 58>56%.
[XPERIA X1 Android Development] codexc:
hello im testing the new kernel with 3D driver and autostart on CM6.1 Barebone

i don't get error message but the system freezing sometime and need restart

note : I set setcpu at ondemond

any think to make system more stable ? i don't think the new version is bad

thanks
[XPERIA X1 Android Development] chester0:
Try to disable mobile data in settings - wireless -mobile

i can confirm this
[XPERIA X1 Android Development] matejdro:
So, what releases works with this kernel except CM6.1Barebone?
[XPERIA X1 Android Development] seandean:
The “process system is not responding” issue is being caused by the removal of CONFIG_SCHED_DEBUG which places a file called “/proc/sched_debug” in the system. I don’t think its affecting users on Neopeek CM6.1 (which I’m using) but it’s certainly doing so with Neopeek CM6.0 and FRG83 builds. I can’t really comment on the differences between the builds besides the obvious CM stuff.

Unrelated fixes have been committed to the source tree, along with possible camera support (I haven’t completely reviewed the commits so don’t quote me on this). I won’t be able to build and test anything until at least Thursday this week, but when I do it will include all the changes done.

I will also re-enable kernel and scheduler debugging so we don’t get the above error anymore, but you need to realize this isn’t necessarily a kernel issue at all as this is not required for Android. Since it does prevent a high percentage of users from using this kernel I will put it back in at the cost of some kilobytes of memory and processing cycles.

My timeline for the next release (v5a; if camera support works OR v4b; if it doesn’t and becomes a bug fix build instead) is between Thursday afternoon and Friday night this week.

I’m probably going to also start a dedicated thread here on XDA, this thread is starting to become very “end-user support” and it should really be more focused on kernel development - I realize this is partially my fault.
[XPERIA X1 Android Development] codexc:
Thanks for hard work ! mr seandean

we are waiting for you ;)
[XPERIA X1 Android Development] mkbm:
@seandean: can you tell me from which GIT you are building?

I have tried the GIT from sp3dev which was posted in this thread. But I always get an error that some files are missing.
[XPERIA X1 Android Development] matejdro:
+1

I always felt that there are too many offtopic stuff going on in this thread, which is primarily intended for developers to meet here.

(and yes, i know that i'm also creating offtopic :))
[XPERIA X1 Android Development] mkbm:
@seandean:

I have now build my first kernel from the sp3dev with some modifications.

But I still have one question. Which option/entry is for the hardware buttons?

I want to add it as module like you have done. But if I look under Keyboard I can not find the right option which I have to compile as module.

Can you give me a hint please?
[XPERIA X1 Android Development] seandean:
You will need to make sure the following is set;

CONFIG_KEYBOARD_MICROP_KEYPAD=m

CONFIG_SENSORS_MICROP_KSC=m
[XPERIA X1 Android Development] codexc:
@seandean

hello bro, any new news about the v4b ?
[XPERIA X1 Android Development] codexc:
[Version: v4b] SEX1 Android Kernel updated from 8 minutes ago

seandean : First post updated to reflect new information: new version.

Version: v4b
[XPERIA X1 Android Development] the_icebear:
Sp3devs kernel from the 5th of november works very well for me, but misses the cifs module, where can i get the sources for this version to compile the cifs module ?
[XPERIA X1 Android Development] yaana:
Tested v4b(moduled) with superfroyo for a few days, works ok! and the UI is somewhat smoother(maybe?)

problems:

1. free memory is 184mb, v3b is 199mb+ (remember,not sure)

2. screen scrambles after wake-up

3. battery meter inaccurate
[XPERIA X1 Android Development] jerpelea:
i think that we shoul also look for corect epson initialization

for now inmage is upside down and android is patched to display corectly

all for wrong initialization ;)

lets find the right sequence
[XPERIA X1 Android Development] sp3dev:
You should be using the word (that is, w) mode to access it. Or use i2cdump
[XPERIA X1 Android Development] vdelf:
some progress on microp-klt:

i stumbled upon this chat log, and as user xperia states, version is at 0x07 on my phone. Version is 0787, that matches WiMo-Logs.

I run some tests and i got the following results:

-writing 0xff 0xff to 0x11 activates the four LEDs in display border

-wrting 0xff 0xff to 0x20 activates the four LEDs in display border

-writing 0x00 0x00 to 0x20 deactivates LEDs

-writing 0xff 0xff to 0x14 activates keypad backlight at full brightness

-writing 0x00 0xff to 0x14 deactivates keypad backlight

-writing 0xff 0xff to 0x13 made keypad backlight flash once and stay on very dimm

-writing 0x00 0xff to 0x13 deactivates keypad backlight

-writing 0x00 0x00 to 0x12 deactivates LCD backlight

-writing 0xff 0xff to 0x12 activates LCD backlight full brightness

I played around a bit with LCD brightness, but it is either on or off :confused:

And be warned: Dont change KLT_ID_LCD_BRIGHTNESS to 0x12, because that will make android turn off LCD backlight during boot. I had to reset because nothing was seen on the display :o
[XPERIA X1 Android Development] :
vdelf this could be "the big step" in the android dev for xperia. really impressed with you

thanks for all that work
[XPERIA X1 Android Development] jerpelea:
reclaim some ram 17mb

in board-htckovsky.c

mi->bank[1].node = PHYS_TO_NID(mi->bank[1].start);

mi->bank[1].size = (128-51)*1024*1024;

mi->bank[1].node = PHYS_TO_NID(mi->bank[1].start);

mi->bank[1].size = (128-34)*1024*1024;

in pmem.c

pmem_setting.pmem_start=MSM_EBIN_BASE+128*1024*1024-51*1024*1024;

CALC_PMEM(pmem_adsp, pmem, 16*1024*1024);//16MB

CALC_PMEM(pmem_camera, fb, 1024*1024);//1MB

become

pmem_setting.pmem_start=MSM_EBIN_BASE+128*1024*1024-34*1024*1024;

CALC_PMEM(pmem_adsp, pmem, 0);//16MB

CALC_PMEM(pmem_camera, fb, 0);//1MB

thanks phhusson for the ideea
[XPERIA X1 Android Development] jerpelea:
Set sleep idle time to 20ms instead of 2s

in defconfig

CONFIG_MSM7X00A_IDLE_SLEEP_MIN_TIME=200000000

becomes

CONFIG_MSM7X00A_IDLE_SLEEP_MIN_TIME=2000000

thanks phhusson

seems that this breaks ts !
[XPERIA X1 Android Development] drlucky:
Great news ... works for me, too. My phone starts up and the microp-driver is identified as described during boot.

Now I think we need to change the code and include some kovsky-specific IDs to make a progress ... vdelf has already found some IDs, the "xperia" guy from the irc log states that the LED_STATES is at another ID (will try this out now).

:D
[XPERIA X1 Android Development] drlucky:
Just one question - how do you run these tests? Compile a special kernel with these tests included, or do you have a special command in android to run these? I'm currently compiling a kernel, upload to mobile, restart phone ... takes ages and id getting on my nerves :o
[XPERIA X1 Android Development] sanjayecb:
ya that is the same problem with me
[XPERIA X1 Android Development] angusmcb:
We can fiddle about if you have shell access to the phone by using debugfs to read and write the registers we are talking about: see micropklt_dbg_init for examples.
[XPERIA X1 Android Development] drlucky:
OK, I see. found the kernel sources and some documentation about debugfs - but I cannot mount the debugfs filesystem (as root using the terminal app):

mount -t debugfs /sys/kernel/debugfs

> mount: cannot read /etc/fstab: No such file or directory.

Can you give me another hint on howto enable this (I'm quite sure DEBUGFS is compiled in the kernel). If I have this running, I can use "cat" with input/output redirection to read/write to these debugfs functions, correct? Just like I can change some kernel options using the /proc or /sys filesystem?
[XPERIA X1 Android Development] sanjayecb:
you have to be root

make a new directory in /mnt/<xda or whatever>

then try mounting

use mount -o loop debugfs /sys/kernel/debugfs
[XPERIA X1 Android Development] angusmcb:
traditionally we would mount debugfs with

mount -t debugfs none /sys/kernel/debug

read & write with cat & echo from the shell

make sure you wrap your reads & writes in mutex on &data->lock in the driver
[XPERIA X1 Android Development] sanjayecb:
i was unaware about this i thought of this to be rootfs
[XPERIA X1 Android Development] drlucky:
Thanks a lot ... just forgot to include the "none", so linux was trying to get the mount information from /etc/fstab. Everything works fine now.

Next step: get dropbear working, so I can connect using ssh from my PC (where I know all keys ... keyboard layout is still such a pain on a german hardware keyboard ... hehe)
[XPERIA X1 Android Development] vdelf:
some more progress:

LCD backlight is controlled by writing two bytes to adress 0x12

First byte deactivates (0x00 - 0x7F) or activates (0x80 - 0xff) the backlight

Second byte controls brightness in 256 steps (0x00 - 0xff)

Full Backlight controll is getting close :D
[XPERIA X1 Android Development] _Sensible:
@vdelf,

Awesome find man! :D
[XPERIA X1 Android Development] drlucky:
Hooray! Nearly there!

But when I'm correct, this is a completely different behaviour than the current microp-code in the kernel? They are using an LED_STATE, or am I missing something? Does that mean we need to change big chunks of code in there or replace it with some kovsky-microp.c? If you need help, let me know ... :)
[XPERIA X1 Android Development] vdelf:
I used exactly that way, too :o

But a few moments ago, i also got android adb working, thanks to Musse_1 and this thread. It works very well on the fatsal-build.

These steps did the trick for me:

-in WinMo set USB-connection to ActiveSync and deactivate the speed option (i never tried with that option on)

-in WinMo connect the phone, it will be detected. You dont need ActiveSync installed

-in WinMo put the "echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch"-line into the conf-file. To be sure use an editor that can handle linux-linefeeds

-while connected run haret to start android. during boot the phone is detected as smartphone, install the android adb driver from sdk

-in android, check the debug-options in settings -> applications
[XPERIA X1 Android Development] vdelf:
There is already some machine-depended lcd-backlight code in micropklt_led_brightness_set:

// lcd-backlight lets us do varied brightness
if ( idx==5+8 /*&& brightness>0*/) {
//microp version ?
if(machine_is_htcrhodium()) {
buffer[0] = MICROP_KLT_ID_LCD_BRIGHTNESS2;
//Scale from 0 to 9
buffer[1] = (brightness*9)/255;

printk(KERN_INFO MODULE_NAME ": Setting %s brightness2 to: %d/10\n",
led_cdev->name, buffer[1]);
micropklt_write(client, buffer, 2);
//msleep(1);
} else {
buffer[0] = MICROP_KLT_ID_LCD_BRIGHTNESS;
buffer[1] = brightness/2 & 0xf0;

printk(KERN_INFO MODULE_NAME ": Setting %s brightness to: 0x%02x\n",
led_cdev->name, buffer[1]);
micropklt_write(client, buffer, 2);
//msleep(1);
}
}

Adding some kovsky-lines isnt a problem. Android even calls this already. Sadly it always uses brightness zero :( Dont know why...
[XPERIA X1 Android Development] sp3dev:
so, the patch for headset inversion is pushed to mainline. have a look at the latest commits. just add the jack_inverted = 1 to h2w platform data in kovs. also, here's a small patch for usb

diff -ruN ../htc/linux-msm/arch/arm/mach-msm//board-htckovsky.c ./arch/arm/mach-msm//board-htckovsky.c
--- ../htc/linux-msm/arch/arm/mach-msm//board-htckovsky.c	2010-03-28 20:53:21.000000000 +0400
+++ ./arch/arm/mach-msm//board-htckovsky.c	2010-04-26 00:33:26.000000000 +0400
@@ -47,6 +47,9 @@
#include <mach/gpio.h>
#include <mach/io.h>
#include <linux/delay.h>

#include <linux/microp-keypad.h>

@@ -77,22 +80,33 @@
.dev = { .platform_data = &raphael_keypad_data, },
};

-
-static int usb_phy_init_seq_raph100[] = {
+static int usb_phy_init_seq_kovs100[] = {
0x40, 0x31, /* Leave this pair out for USB Host Mode */
0x1D, 0x0D,
0x1D, 0x10,
-1
};

static void usb_phy_reset(void)
{
+ gpio_set_value(0x69, 1);
gpio_set_value(0x64, 0);
-	mdelay(1);
+	mdelay(3);
gpio_set_value(0x64, 1);
mdelay(3);
}

+static void usb_phy_down(void) {
+	gpio_set_value(0x64, 0);
+	gpio_set_value(0x69, 0);
+}
static struct i2c_board_info i2c_devices[] = {
{
// LED & Backlight controller
@@ -286,8 +352,7 @@
// Device pdata overrides
msm_device_htc_hw.dev.platform_data = &msm_htc_hw_pdata;
msm_device_htc_battery.dev.platform_data = &msm_battery_pdata;
-	msm_add_usb_devices(usb_phy_reset, NULL, usb_phy_init_seq_raph100);
-
+	msm_add_usb_devices(usb_phy_reset, usb_phy_down, usb_phy_seq_kovs);
#ifdef CONFIG_SERIAL_MSM_HS
msm_device_uart_dm2.dev.platform_data = &msm_uart_dm2_pdata;
#endif
[XPERIA X1 Android Development] angusmcb:
Quick hack kernel to test

This kernel should switch the backlight off and on with the display and have working wifi (wifi doesn't hang the phone for me when switching off). Display takes a little while to turn on after pressing the power button.

I deleted data.img & cache folder on sdcard to test.
[XPERIA X1 Android Development] jerpelea:
tested

backlight works

wifi craches ok switch off

will you push this on git?

also i see that you dont have memory patch;)