Database Develop

[PRJ][OS]Linux and Android on SE Xperia X1

This thread is here for information and discussion about the Linux kernel (and Linux based userspaces like Ångström distribution or google android.
If you have no clue what this is all about, click the above links and read a bit about it.
The xperia(kovsky) research information vital to porting the linux kernel is available at htc-linux.org
The kovsky is very similar to raphael, diamond and the other htc phones that are based on the QCT msm7xxxA chip. This is why the raphael/diamond development kernel code from the htc-linux project runs well on it.
Kovsky has its own machine type in the htc-msm-2.6.27 (see link above) branch now.

im kinda excited about this! if linux (& android) is able to run on the X1 smoothly, I'm definitely donating!

New thread = very good news.
If you need someone for testing then let me know.
I would be willing to donate as well.
Keep working hard everyone!

somehow i feel like setting up an X1 android version for it. since im more the "script" guy im rather useless for u if it comes to kernel development ^^
how stable and functional is the kernel so far?
and especialy, is the Wifi running allready?

hey decordes,
there is the question where to get the [email protected] files 0.8 and 1.0... (i have them. but dont know if i may provide these files while they are not from my self!)
a simple yes or no and they are available for the next years or not
--
cyberdesigner.net

achmed20 said:
how stable and functional is the kernel so far?
and especialy, is the Wifi running allready?
Click to expand...
Click to collapse
afaik the wifi doesnt work. only usb0 which is laggy. (but works! you could ssh to the x1 per default.)
i am a little bit bussy at the moment (have to provide some sap-python-mysql-interface for productive use.)
but if i get spare time i will take a closer look at wifi...
--
cyberdesigner.net

kk thx.
as long i can use ssh, i'm all set up i guess
time for some android theory

NSRocket said:
Ooops (forgot to strike key), yes I mean TNETW12511.
Click to expand...
Click to collapse
isnt that the same wifichip as the kaiser has?
but why is wifi needed to boot android?

Reversedhex said:
isnt that the same wifichip as the kaiser has?
but why is wifi needed to boot android?
Click to expand...
Click to collapse
I don't know many things on Kaiser device but if you read somewhere that it use a TI 1251 WLAN then... yes, it's the same.
I don't understand why do you correlate wifi and android booting
We're talking about this wifi chip just because it isn't supported in the linux-htc-kovsky package at the moment.

NSRocket said:
I don't know many things on Kaiser device but if you read somewhere that it use a TI 1251 WLAN then... yes, it's the same.
I don't understand why do you correlate wifi and android booting
We're talking about this wifi chip just because it isn't supported in the linux-htc-kovsky package at the moment.
Click to expand...
Click to collapse
i was reading a combination of things,
-wifi not working and usb0 laggy.
-log readout over usb0
so i thought maybe for the log or something, nevermind
---------------------------------------------------------
wifi not working on kaiser either so we cannot take the driver from there, but i dont think wifi has high priority...
http://www.androidonhtc.com/kaiser:port_status

NSRocket said:
I don't know many things on Kaiser device but if you read somewhere that it use a TI 1251 WLAN then... yes, it's the same.
I don't understand why do you correlate wifi and android booting
We're talking about this wifi chip just because it isn't supported in the linux-htc-kovsky package at the moment.
Click to expand...
Click to collapse
its not related. i jsut read that the USB connection was kind of laggy so once i set up a working wifi connection i can continue working with SSH over wifi. that was the only reason.

ah... ok i think this was my intention.
most of the time i am waiting for usb0 to get any response! i cant read on the display them self... so the next needed feature for _me_ was to get a stable/responsible connection (like wifi
achmed20: you got it!
--
cyberdesigner.net

Hi,
very nice project. Maybe i could help out a bit
At least i may help testing and do some hardware discoveries, because i'm not a good kernel hacker.
Anyway i'm used to digg the kernel source and all the other stuff.
There are some questions though:
Those are introduced in the git repository of Mariusz "Aiv" Dalewski. Among other changes, it has the fully working xperia keyboard.
Click to expand...
Click to collapse
Is the git already accessible?
Maybe someone could create a patch to get started more easily
afaik the wifi doesnt work. only usb0 which is laggy. (but works! you could ssh to the x1 per default.)
Click to expand...
Click to collapse
What's the exact state of USB connection right now?
Does it work on Raphael?
Concerning debugging:
Anything known about JTAG on Kovksy?
As you might know i'm addicted to this interface
Best regards,
scholbert

scholbert said:
Hi,
very nice project. Maybe i could help out a bit
At least i may help testing and do some hardware discoveries, because i'm not a good kernel hacker.
Anyway i'm used to digg the kernel source and all the other stuff.
There are some questions though:
Is the git already accessible?
Maybe someone could create a patch to get started more easily
What's the exact state of USB connection right now?
Does it work on Raphael?
Concerning debugging:
Anything known about JTAG on Kovksy?
As you might know i'm addicted to this interface
Best regards,
scholbert
Click to expand...
Click to collapse
http://www.htc-linux.org/wiki/index.php?title=Kernel#Kernel_for_QCT_MSM7xxxA_based_devices
The aiv code is htc-msm-2.6.27 branch plus xperia changes. I think he doesn't want to make it available publicly yet. I'm waiting for it too so I can push it to linuxtogo. You can pull the htc-msm-2.6.27 either way.
usbnet is same driver as used for raphael.
drivers/usb/msm_usb
For jtag, I think you need to wire it to the board manually.
For the raphael you can get a serial connection by making a cable that plugs in the usb port. Ask dreamkill about it. I don't know if it is wired the same way in xperia.
Hope this makes sense I have horrbile hangover

http://www.phonewreck.com/wiki/index.php?title=Sony_Ericsson_XPERIA_X1
So what has to be done is get the linux drivers for al these hardware components and compile them to a kernel to make it fully working?
that probably ist going to be easy
---------------------------------------------------------
btw about wifi cant the driver from g1 be extracted?
same hardware G1/X1
-Power Management PMIC: Qualcomm PM7540
-WLAN Texas Instruments WL1251B/WL1251FE
-UMTS: 2100MHz avago ACPM-7381
-USB SMSC USB3316

Hi dcordes,
thanks for your reply.
http://www.htc-linux.org/wiki/index.php?title=Kernel#Kernel_for_QCT_MSM7xxxA_based_devices
The aiv code is htc-msm-2.6.27 branch plus xperia changes. I think he doesn't want to make it available publicly yet. I'm waiting for it too so I can push it to linuxtogo. You can pull the htc-msm-2.6.27 either way.
Click to expand...
Click to collapse
Yeah did that already.
Unfortunately right now i got no X1 for testing. Should arive the next days i suppose
usbnet is same driver as used for raphael.
drivers/usb/msm_usb
Click to expand...
Click to collapse
O.K., i see so we will also use the config for raphael, i suppose..
For jtag, I think you need to wire it to the board manually.
Click to expand...
Click to collapse
Sure, that's essential
I just wanted to know if there's anyone apart from Sony and HTC engineers who got some info about these testpoints ?
For the raphael you can get a serial connection by making a cable that plugs in the usb port. Ask dreamkill about it. I don't know if it is wired the same way in xperia.
Click to expand...
Click to collapse
That's cool!
Hope this makes sense I have horrbile hangover
Click to expand...
Click to collapse
Does make sense to me
BTW anyone tried this patch to get WIFI support on X1?
http://linuxtogo.org/~lgorris/diffs/git-diff_htc-msm-2.6.27_add-ti1251.diff
Best regards,
scholbert

BTW anyone tried this patch to get WIFI support on X1?
http://linuxtogo.org/~lgorris/diffs/git-diff_htc-msm-2.6.27_add-ti1251.diff
Click to expand...
Click to collapse
Have to quote myself
The patch applies fine but after having a short glimpse, this one has been extracted from the SDK. No proper Kconfigs or Makefiles
So i don't think this huge patch is intended to go into kernel tree again.
AFAIK, there's also a lot of stuff for userland inside.
Insider may know more about it!
Perhaps for WIFI on the X1 it's better to start with a more clean driver.
You make have a look here:
http://osdir.com/ml/linux-wireless/2009-02/msg00390.html
I will try to integrate the patch to current 2.6.27-msm.
There's work to do of course, e.g. SDIO support and PM.
Best regards,
scholbert

I have no idea what you guys are saying.
But Android on the Xperia is f*****g awesome!
could any1 just quickly recap how close we are on a ROM with Android?

D4113R said:
I have no idea what you guys are saying.
But Android on the Xperia is f*****g awesome!
could any1 just quickly recap how close we are on a ROM with Android?
Click to expand...
Click to collapse
though i understand just a little, id like to qoute myself on this
So what has to be done is get the linux drivers for al these hardware components and compile them to a kernel to make it fully working?
that probably ist going to be easy
Click to expand...
Click to collapse

yes with htcraphael_defconfig xperia boots.
I will ask some people about 7xxxA jtag pins and let you know if I have any information.
scholbert said:
Have to quote myself
The patch applies fine but after having a short glimpse, this one has been extracted from the SDK. No proper Kconfigs or Makefiles
So i don't think this huge patch is intended to go into kernel tree again.
AFAIK, there's also a lot of stuff for userland inside.
Insider may know more about it!
Click to expand...
Click to collapse
Right, It copies some revision (see date of file upload) of the android git ti1251. It should enable you to build the kernel module.
lgorris=dcordes
scholbert said:
Perhaps for WIFI on the X1 it's better to start with a more clean driver.
You make have a look here:
http://osdir.com/ml/linux-wireless/2009-02/msg00390.html
Click to expand...
Click to collapse
It's no big secret the 10M google ti1251 driver is crap and it might really be better to use that wl12xx as soon as they have the SDIO.
scholbert said:
I will try to integrate the patch to current 2.6.27-msm.
There's work to do of course, e.g. SDIO support and PM.
Click to expand...
Click to collapse
That will be nice. Let me know when you tried.

the hd has compass hardaware? There are people that say yes

hi
I'm very surprised because tuxhero said yesterday that the blackstone has compass harware:
http://forum.xda-developers.com/showpost.php?p=4304713&postcount=833

bad link... you cant link it with dots: )

Not sure but some sources say that we have it.

daguerrotipo said:
hi
I'm very surprised because tuxhero said yesterday that the blackstone has compass harware:
http://forum.xda-developers.com/show...&postcount=833
Click to expand...
Click to collapse
Your link does not work

Fallen Spartan said:
Your link does not work
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4304713&postcount=833

tuxhero said:
Not sure but some sources say that we have it.
Click to expand...
Click to collapse
"1. Today i came to know that our Blackstone has Compass Hardware too and we have code for it too."
Seems to me that you were sure?

Moony1987 said:
"1. Today i came to know that our Blackstone has Compass Hardware too and we have code for it too."
Seems to me that you were sure?
Click to expand...
Click to collapse
Ya but not tested it to be so sure

tuxhero said:
Ya but not tested it to be so sure
Click to expand...
Click to collapse
Ahh righto

I think we do have.
Thats the shame 'bout HTC (besides da poor quality of hard- and software): they setup ONE hardware and make 5 PDAs with slighty changed details. they were never interested in making good hardware.. everytime they took something away the previous model had... now, they do have android and are able to clone nearly the same device just with another OS.
in commercial aspects, this makes sense.... but as consumer I can only think of it as a pain in the neck. my old universal has a high res display, a 3,5mm audioconnector, a well made keyboard and a fast cpu... years ago... a shame it is the size of a brick .

If someone would mad it possible to use the Compass HW with WinMo i would gladly set a bounty of 50$.
Goal would be a little App to proof that it ist working plus the sourcecode for other Devs.
Does anyone join in?

its probably another 'tv out' scenario...
basically the chipset has the tech but other required hardware / software is not present hence the features can never be used.
why on earth HTC cripple devices like this is boggling.....if the HD had been released with TV-out (which the qualcomm chipset supports) & a hw compass (to be confimed) it would have levelled the competition.....
i am sure their marketing strategy has good reasons for not doing...but as said earlier from the consumers point of view its a pain in the butt...especially considering some of us are locked in 24 month contracts.!! so wont be purchasing other handsets even if we wanted too.
lets hope some clever devs find a way to unlock these features!! (if possible)

purec0de said:
its probably another 'tv out' scenario...
basically the chipset has the tech but other required hardware / software is not present hence the features can never be used.
why on earth HTC cripple devices like this is boggling.....if the HD had been released with TV-out (which the qualcomm chipset supports) & a hw compass (to be confimed) it would have levelled the competition.....
i am sure their marketing strategy has good reasons for not doing...but as said earlier from the consumers point of view its a pain in the butt...especially considering some of us are locked in 24 month contracts.!! so wont be purchasing other handsets even if we wanted too.
lets hope some clever devs find a way to unlock these features!! (if possible)
Click to expand...
Click to collapse
I disagree your argumentation:
Developers here wrote drivers to implement TMC and RDS into the features of the Blackstone. HTC hasn´t done it yet.
HTC seems to leave possible feature unused. Maybe to save time for their developers.
The old topic of a missing video driver is another example for that.

Draque:the_Plaque said:
If someone would mad it possible to use the Compass HW with WinMo i would gladly set a bounty of 50$.
Goal would be a little App to proof that it ist working plus the sourcecode for other Devs.
Does anyone join in?
Click to expand...
Click to collapse
50$ from me for unlocking the feature + another 100$ if anyone makes it work with Google Maps + another 100$ if someone makes an augmented reality app like Wikitude (Android).
Only if it's done before the release of the HTC Leo

It's a AK8976A chip

well i would chip in $50 as well .. if it worked !!

KlausFindus said:
It's a AK8976A chip
Click to expand...
Click to collapse
is the same that dream phone?
Byes

haha, did anyone think that they mite have released the phone in haste, or maybe they did it on purpose to allow the release of the HD pro to include such features, along with a 128GB internal memory (i wish).

ghosty_uk said:
haha, did anyone think that they mite have released the phone in haste, or maybe they did it on purpose to allow the release of the HD pro to include such features, along with a 128GB internal memory (i wish).
Click to expand...
Click to collapse
Sometimes happen... It's true that more with anothers brands (apple), I can remember Ipod touch, iphone, wifi in the macs....
may be this time no but is possible.
Byes

I've read the same thread from Tuxhero and I have to see it before I believe it. The only thing we've got is a blanket statement that he has read it somewhere. Someone else created slight confusion on this site before with similar statements.
Not saying that he's lying (in fact, I hope he's right), a source would help. Until then, I'm not getting my hopes up.

Im guessin they didnt include alot of features cause when the phone was released whoever ws going to buy it would buy it anyway, and when competitors (Iphone3gs) release phones with features like the compass thing etc , htc can easily release newer phones with the same features ... sort of like having it ready on earlier models so when they need to release it they can quickly!
My guess

[DEV][UPDATE: 2-10-11][Optimus One multitouch fixes]

This thread has gone on a different approach on resolving this, so I'll be setting aside my old post (I wont be deleting them for some reasons). Everything under the hash army (###) in this single post is about getting the Spica stuff on the O1. We moved to focusing on the O1's ts driver itself.
Other note: Fixes are independent. Choose whichever works for you. A universal fix may come in the future though (Tell me if this post still confuses you. I'll edit ASAP)
Multitouch axis inversion fix (First release: Feb 6, 2011): Forum member waleedq came up with a workaround that inverts the inversion. This seems very straightforward, and it works. Please note, however, that this is a workaround and not a fix. As always, do a backup.
Stuff you should know:
- Most of us who tried it (inc. me), lost our OC.
- mik_os' touchscreen lag fix is here. Tested it with Android Status while touching the screen.
- Axis inversion is still a problem. Check video 2.
Videos: http://forum.xda-developers.com/showpost.php?p=11178060&postcount=67
Link to the download link: http://forum.xda-developers.com/showpost.php?p=11166426&postcount=47
waleedq's source: https://github.com/waleedq/ThunderG-Kernel/blob/thunderg_oc/drivers/input/touchscreen/mcs6000_ts.c
Faster readout fix (First release: Feb 8, 2011) : Der_Caveman released for testing a kernel with some delay fix (modified from stock kernel). Apparent goals were to make touchscreen input readouts faster. Also, useless and non-working functions that doesn't work were removed. No CPU spike (somewhere around 30%cpu use when touching screen)
UPD: v3 is based on drellisdee's kernel source, so yes, it's OCable.
Link to download link: http://forum.xda-developers.com/showpost.php?p=11195243&postcount=84
Link to download link(v3): http://forum.xda-developers.com/showpost.php?p=11221504&postcount=126 or a forum upload http://forum.xda-developers.com/showpost.php?p=11230915&postcount=137
Changes and stuff: http://forum.xda-developers.com/showpost.php?p=11206827&postcount=91
Touchscreen optimization + axis inversion workaround(First release: Feb 10, 2011):Der_Caveman and waleedq's work combined by Sippolo.
Link to download link + source + details: http://forum.xda-developers.com/showpost.php?p=11256797&postcount=198
Link to download link + source + details (v1.1): http://forum.xda-developers.com/showpost.php?p=11270721&postcount=237
#########################################################
Okay, so I just recently found out that the Galaxy Spica (was supposed to choose it over the O1 --') -unofficially- supports multitouch.
A link to the driver's was PMed to me by adi4motion:
https://github.com/Gabriel-LG/i5700-multitouch-kernel
Anyway, is it possible that we could implement their method on our drivers? I understand that there might be some hardware differences between the two. I'm just trying my luck
Lastly, for sample videos, check YouTube. I have to say that the performance with those drivers really are impressive (well, I saw the axis invert once)

https://github.com/Gabriel-LG/i5700-multitouch-kernel/tree/master/drivers/input/touchscreen
I didn't find any melfas drivers in there- so I doubt that the Galaxy Spica has a melfas touchscreen controller in it.

But it's possible that we could write a driver based on those, right?

only kpbotbot can do tht and i hope he does

What about O1 brother the LG Chic? Does it have the same issues?
Sent from my LG-P500

ccdreadcc said:
only kpbotbot can do tht and i hope he does
Click to expand...
Click to collapse
Sorry, can't code. But I assure you, I'm trying my best not to just leech (And I'm still figuring out how to compile FroYo to learn how ROMs get born)
N3mesis said:
What about O1 brother the LG Chic? Does it have the same issues?
Click to expand...
Click to collapse
There may be a guy here in the forum that has the Chic. Maybe he can test out the inversion issues (If you're reading this and you have the Chic, please test if the axis inverts using a tool like touch test xD)

kpbotbot said:
But it's possible that we could write a driver based on those, right?
Click to expand...
Click to collapse
In the O1 a melfas MCS6000 touchscreen controller reads the capacitive touchscreen. The controller itself got a proprietary firmware in it (don't know if its from melfas or LG)- you can find that somewhere in the system folder (melfas.bin(?)). Then there is the LG kernel driver which "interacts" with the melfas controller ic- it also has the ability to flash the melfas controller.
So if there is a problem in the MCS6000 firmware- we're most likely screwed, because lack of datasheets.
Furthermore I want to know how android gets the multitouch data. Maybe the android interface itself is not that multitouch friendly?
The easiest way would have been that each finger represents a "mouse event", but I doubt that this way was chosen...

I see. Is it possible to decompile that .bin somehow? I know, that question might sound stupid xD
I too did a search for melfas related stuff including source codes and the like. The only stuff I found was about Samsung phones having the same touch screen.
Let's just hope (for now that we cant do anything about it) that LG -at least- releases an improved version of their drivers for their 2.3 update

Update: The Chic has the same problem :/
http://forum.xda-developers.com/showpost.php?p=11014035&postcount=5

Maybe the axis inversion is somehow also android related.
Multitouch is something new for linux.

Der_Caveman said:
Maybe the axis inversion is somehow also android related.
Multitouch is something new for linux.
Click to expand...
Click to collapse
I think is just the crappy touch controller that's installed on our device; It can't spot more than 2 touches, and has got axis inversion. So I don't think there's so much to do with drivers

kite86 said:
I think is just the crappy touch controller that's installed on our device; It can't spot more than 2 touches, and has got axis inversion. So I don't think there's so much to do with drivers
Click to expand...
Click to collapse
LG only implemented "two fingers"- one can read that in LG's sources.
Again: axis inversion could also be android related (if android only requests coordinates without "finger assignments" bugs are preassigned).

I don't really care whether it would accept more than 2 presses That would be awesome for people doing extreme gaming with the phone, but with normal use it's awkward to use 3 fingers.
I bet the axis inversion issue is very much fixable. We just don't know how yet. But considering the fact that the Spica has less of this as a problem, we might fix it a bit, or completely fix it.
This is just my opinion though. I saw some guy explain multitouch with an illustration.

Wow, I have found this:
http://www.mjmwired.net/kernel/Documentation/input/multi-touch-protocol.txt
Just had to open my eyes
Let's see...

kpbotbot said:
I bet the axis inversion issue is very much fixable. We just don't know how yet. But considering the fact that the Spica has less of this as a problem, we might fix it a bit, or completely fix it.
Click to expand...
Click to collapse
You are 100% sure that the Spica does not have "the axis inversion bug"?

Der_Caveman said:
You are 100% sure that the Spica does not have "the axis inversion bug"?
Click to expand...
Click to collapse
I'm 100% sure.

I talked to a guy who used to own the phone. He said the drivers perform well.
I didn't say that there really was no inversion. It happens less (inverted once on the video I watched)

kpbotbot said:
I talked to a guy who used to own the phone. He said the drivers perform well.
I didn't say that there really was no inversion. It happens less (inverted once on the video I watched)
Click to expand...
Click to collapse
Ok, then I would say there is hope.

Der_Caveman said:
Ok, then I would say there is hope.
Click to expand...
Click to collapse
I sure do prey that someone will take this project and fix the driver or write it from scrath. As i can see the code is not that long
our driver
https://github.com/mik9/ThunderG-Kernel/blob/master/drivers/input/touchscreen/mcs6000_ts.c
spica's driver
https://github.com/Gabriel-LG/i5700...4461c4a3d4e2be0b5f4b1a94b451604c6541f1#diff-0

I have 2 months of doing absolutely nothing at home (stopped this sem. doctor said i have to rest. and yes, I have a life xD), so I might be able to understand a bit of the code. It really isn't that complex, but my lack of programming knowledge hinders me from modifying the code.
However, I sure do hope that someone figures this out

[DEVELOPMENT - SENSOR HAL] for Xperia™ phones available open source

Hi,
In this thread Johan Abramsson. Sony Ericsson Developer Program, will look for feedback and questions regarding Sensor HAL sources just published as Open Source.
http://developer.sonyericsson.com/wp/2012/02/14/sensor-hal-for-xperia-phones-available-as-open-source/
/Kalle
Karl-Johan Dahlström - KalleD
Sony Ericsson Developer Program

That's why I prefer SE..

Nice to hear that

Great job SE ... I'm sure our developers will find this helpful.

Does this mean that the Devs have finally better access to the camera-sensor and thus can optimize it?

NeoCream said:
Does this mean that the Devs have finally better access to the camera-sensor and thus can optimize it?
Click to expand...
Click to collapse
No, these are libraries for accelerometer-, proximity-, pressure- and gyro-sensors, as far as I can tell.

DerEineDa said:
No, these are libraries for accelerometer-, proximity-, pressure- and gyro-sensors, as far as I can tell.
Click to expand...
Click to collapse
Yes, accelerometer/gyroscope/compass/magnetometer

This is great news, and this is just one of the many reasons I love Sony (Ericsson).

does that mean that our touch screen will finally be fixed by some nice developer that is willing to do it?

There is nothing wrong with our touchscreen
Its for sensors like accelerometer and stuff on custom roms like CM7 - CM9 by J (FXP) or any Rom that's built from source
If people don't want to use precompiled ones from SE Rom then this will be useful
Regards

yeah there is nothing wrong with the touch screen
Sent from my LT18i using Tapatalk

waynekirby said:
There is nothing wrong with our touchscreen
Its for sensors like accelerometer and stuff on custom roms like CM7 - CM9 by J (FXP) or any Rom that's built from source
If people don't want to use precompiled ones from SE Rom then this will be useful
Regards
Click to expand...
Click to collapse
hootnath said:
yeah there is nothing wrong with the touch screen
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
There is actually if you ever tried to type very fast the touchscreen on the arc and arc S will read it as you sliding your finger from the 1st touch point to the 2nd touch point

I don't think that Sony would see this as a problem though unfortunately, and personally I blame it on the SEMC keyboard...

waynekirby said:
I don't think that Sony would see this as a problem though unfortunately, and personally I blame it on the SEMC keyboard...
Click to expand...
Click to collapse
Its the problem of using new touch screen technology. All keyboards have that problem. For what I heard Sony embedded apps have somehow fixed the problem. Not really sure
Sent from my LT15i using xda premium

touch screen is fixed so please dont spam here

thanks for this release
accelerator akm907x sensor was not included in package !

I've been a pretty loyal Samsung guy until recently, but... If Sony keeps this up, my next device will probably be a Sony. It's either that or the next Nexus.

Voice activation

The Snapdragon 800 has on Chip Voice activation, how I can active it?
I was saw a Video on the Qualcomms Website the people call: Hey Snapdragon and the phone turn on and say Hello Master?
Sony deactivate the function on the Software or I make some wrong?
Sent from awesome Z1

Nice Option, I never know something like that it's possible with Z1. I am curious too if we can get this option to work.

Here : http://www.qualcomm.com/snapdragon/processors/800
Scroll down to Technology that listens you.
Tomorrow I will ask the Sony support.
Sent from awesome Z1

It's not implemented yet. Has nothing to do with Sony. It's a new feature in KK

jamespmi said:
It's not implemented yet. Has nothing to do with Sony. It's a new feature in KK
Click to expand...
Click to collapse
What a shame. Are you sure?

eclyptos said:
What a shame. Are you sure?
Click to expand...
Click to collapse
A shame? A pity maybe as no implemented before 4.4
Very sure. The first KK phone introducing it was N5 with the Google Experience Launcher.
There are apps simulating this, but as a system cheat I rather think a battery drainer...

jamespmi said:
A shame? A pity maybe as no implemented before 4.4
Very sure. The first KK phone introducing it was N5 with the Google Experience Launcher.
There are apps simulating this, but as a system cheat I rather think a battery drainer...
Click to expand...
Click to collapse
Then is a software related? That mean we will get ti soon, maybe.

The Voice Activation is Hardware Features from S800.
It is exist on Chip but locked by Sony.
Look my link scroll down.
Sent from awesome Z1

Nemeziz 56th said:
The Voice Activation is Hardware Features from S800.
It is exist on Chip but locked by Sony.
Look my link scroll down.
Sent from awesome Z1
Click to expand...
Click to collapse
Ok, so the Chip have the ability to use that feature but is locked by Sony. I hope it will can be unlocked but I doubt.

Guys it's not Sony related. It's a feature introduced in KitKat. We are still on 4.3. Stop begging Sony for each and everything. Just njoy the rest of the beautiful device. There is a lot of stuff coming soon, step by step. Think about holding a device in hands witch will smoothly be able to handle all the features they introduce even in one year while other phones just give up due missing specs...
Sent from my C6903 using xda app-developers app

This disinformation in this thread is amazing. Then is not locked but is System related and is implemented in KitKat, if so we will get that feature.

Update Google Search to 3.2.16.1006154 and the Experience Launcher to 0.10.1.920880 and you are in the game...
Probably you don't even need the Experience Launcher but I can't understand people not using it as the tight Google Now integration is just awesome...