[Sony] Xperia Open Devices Project

jerpelea · Aug 14, 2015

Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.

For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.

If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel

Project git
https://github.com/sonyxperiadev/

jerpelea · Sep 7, 2015 at 10:13 AM

Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/

Happy cooking

DHGE · Sep 12, 2015

SGP712 comilation of 28.0.A.7.251 fails

@jerpelea

Code:

  CC      drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
  pdata->stylus_support = (u16)val;
       ^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
    if (pdata->stylus_support &&
             ^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
    if (pdata->stylus_support &&
             ^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2

I will revert your stylus (really?) patches to version .31

Or please update a declaration struct maxim_sti_pdata at the proper location.

EDIT: I added

Code:

u32       stylus_support;

to 28.0.A.7.251/kernel/include/linux/maxim_sti.h

EDIT2:
I flashed the DE 28.0.A.7.251 - works.

I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.

I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop

EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58

dl12345 · Sep 12, 2015

DHGE said:
@jerpelea

Code:

CC drivers/input/touchscreen/maxim_sti.o drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt': drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support' pdata->stylus_support = (u16)val; ^ drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg': drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support' if (pdata->stylus_support && ^ drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support' if (pdata->stylus_support && ^ scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1 scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed make[2]: *** [drivers/input/touchscreen] Error 2 scripts/Makefile.build:455: recipe for target 'drivers/input' failed make[1]: *** [drivers/input] Error 2 Makefile:815: recipe for target 'drivers' failed make: *** [drivers] Error 2

I will revert your stylus (really?) patches to version .31

Or please update a declaration struct maxim_sti_pdata at the proper location.

EDIT: I added

Code:

u32 stylus_support;

to 28.0.A.7.251/kernel/include/linux/maxim_sti.h

EDIT2:
I flashed the DE 28.0.A.7.251 - works.

I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.

I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop

EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58

28.0.A.8.251 compiles and boots first time for me on Z3+. EDIT: seems to perform better too, with Antutu benchmark score going up from 47,800 to ~53,000

DHGE · Sep 12, 2015 at 3:51 PM

28.0.A.8.251 compiles and boots first time for me on Z3+

I hope they tested the source on this device.

Maybe they do not test all kitakami devices e.g. SGP712

dl12345 · Sep 12, 2015 at 4:07 PM

DHGE said:
I hope they tested the source on this device.

Maybe they do not test all kitakami devices e.g. SGP712

Seems ok for now. I'm running it at the moment on a custom rom that has xposed installed and it's so far stable. This is the kernel in the current firmware, so I'm sure it's been tested.

jerpelea · Sep 14, 2015 at 10:11 AM

AOSP uses a different kernel source
https://github.com/sonyxperiadev/kernel

DHGE · Sep 14, 2015

please clarify

@jerpelea

All I write on compiling applies to my SGP712.

AOSP uses a different kernel source

Than what?

The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:

@kholkkholk on 29 May input: TS: Add Maxim SmartTouch Imager driver

I think that is OK for karin_windy.

I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...

I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).

Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.

btw: # CONFIG_DM_VERITY is not set

jerpelea · Sep 21, 2015 at 9:34 AM

Hi

i have recompiled the kernel
https://github.com/sonyxperiadev/kernel

i have tested karin_windy here with same V11 archive and flashed all 3 partitions

i have touch screen and device working fine

br
J

DHGE said:
@jerpelea

All I write on compiling applies to my SGP712.

Than what?

The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:

I think that is OK for karin_windy.

I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...

I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).

Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.

btw: # CONFIG_DM_VERITY is not set

DHGE · Sep 21, 2015 at 10:10 AM

Thanks @jerpelea for the update!

I am mostly interested in the stagefright patches.
I do not find them in my repo synced AOSP tree.

The (compiled) patches are in ROM 28.0.A.8.251 though and last week I finally managed to get this rooted and running on my karin_windy.

I will try AOSP again if I have more time.

belrik · Oct 5, 2015 at 11:17 AM

How is the AOSP source for the Z4, does it build yet? Looks like things are building towards a TWRP/AOSP release.

Sent from my SGP712 using Tapatalk

HotBlack77 · Jul 17, 2010 40 9 0

Is there a news on a ASOP build for the Z4?

Sent from my SGP771 using Tapatalk

streilu · Nov 15, 2015 at 2:10 PM

FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?

HotBlack77 · Jul 17, 2010 40 9 0

streilu said:
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?

FreeXperia has "karin windy" builds too.

Look here: http://fxpblog.co/aosp/aosp-5-1/ and choose the first of the 2 possible mirror providers (different sets of files are offered at each), scroll to the buttom and the latest ASOP for the Z4 is there. I have yet to try and install it as the download consistently fails and then forces me to wait for 24 hours.

jerpelea · Nov 18, 2015 at 11:37 AM

http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/

enjoy
J

HotBlack77 · Jul 17, 2010 40 9 0

Is anybody able to download any of the ASOP builds from http://fxpblog.co/ ?
Could they be mirrored, at a more "normal" file host?

streilu · Nov 23, 2015 at 11:30 AM

I can upload it later today to your preferred hoster if you tell me.

HotBlack77 · Jul 17, 2010 40 9 0

streilu said:
I can upload it later today to your preferred hoster if you tell me.

How about https://www.androidfilehost.com/ that would seem appropriate. But frankly any host which does not force you to pay for downloads.

streilu · Nov 23, 2015

Got no dev account on AFH, sorry.

Hope this is ok: https://mega.nz/#!aEZlnZJS
@HotBlack77 please tell me how AOSP feels on the Z4 tab. I'm unsure about the BL unlock thing.

Gesendet von meinem SGP712 mit Tapatalk

jerpelea · Dec 2, 2015 at 12:59 PM

Hi all

We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

Enjoy
J

[Sony] Xperia Open Devices Project

Senior Recognized Developer

Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Recognized Developer

Senior Member

Senior Recognized Developer

Senior Member

Senior Member

Member

Senior Member

Member

Senior Recognized Developer

Member

Senior Member

Member

Senior Member

Senior Recognized Developer