Develop Bugs

SONY LT26i Kernel 3.4.0 for any JB based on stock

SONY XPERIA S.
Kernel 3.4.0+1.0.21100 by SONY.
CPU msm8260 192~1.728Mhz.
GPU Adreno 220 - 2D 160~266Mhz - 3D 200~320Mhz.
TWRP Recovery 2.8.7.0.
Support for recovery in FOTAkernel.
Support for run-parts in /system/etc/init.d/.
Support for IPtables.
Swap.
How to Flash Kernel:
0 - Download file and unzip.
1 - Unlock Boot Loader.
2 - Power off Phone.
3 - Start Flash Tools.
4 - Hold Vol+ while plug the USB cable, on led blue light, release the Vol+.
5 - on Flash Tools Start the Flash in Fast Boot Mode to Flash Kernel.
XDA:DevDB Information
[email protected], Kernel for the Sony Xperia S
Contributors
Rafael.Baugis
Source Code: https://github.com/RafaelBaugis/Kernel-nozomi
Kernel Special Features: OverClock, init.d, TWRP Recovery, IPtables, Swap
Version Information
Status: Stable
Created 2014-04-11
Last Updated 2015-11-08

Last Kernel: kernel-20151107.elf.zip

Hey,hey.. Please see Xperia ION users.
Thanks you.

Is like the ASK from doomlords? But with the new (And also better) Cwm by crazy_doz, right? it looks, pretty good, i'm gonna test it

Bem vindo amigo!
Welcome friend!

So much time passed since that time when you made my day by resurrecting that freaking ace
I'm pleased you come back

What are the other features of this kernel?

Nice MAN
Waiting u to upload it !!
Rafael.Baugis
Click to expand...
Click to collapse
Code:
Rafael.Baugis

amraasar said:
Nice MAN
Waiting u to upload it !!
Code:
Rafael.Baugis
Click to expand...
Click to collapse
Download link is working?

Rafael.Baugis said:
Download link is working?
Click to expand...
Click to collapse
Are you refering to the 2nd post link : https://docs.google.com/file/d/0B2xJmiwfYDFyUUFnZnhmQXozOG8/edit
Then yes, i can see 2 files and download them.

This is kernel from Sony stock rom? What rom? And what telephone?
Wysłane z mojego LT26i przy użyciu Tapatalka

@Rafael.Baugis, what r the special features of your kernel? can u include it at OP. or no new and its just like doomkernel?

slink722 said:
@Rafael.Baugis, what r the special features of your kernel? can u include it at OP. or no new and its just like doomkernel?
Click to expand...
Click to collapse
I start dev and now have a small features.

I was on DoomLord V6 Kernel and flashed this one, didn't really noticed anything (bad or good) just that the cpu is oc to 1.7ghz by default.
Looking forward for next features, thanks for still doing some dev on XS.

Glad....we've got a new kernel developer...
Umm...can you Import the features from this kernel...It's a really awesome kernel...!!
http://forum.xda-developers.com/showthread.php?t=1867265
And the undervolting feature too...^_^

GPL licencing
@Rafael.Baugis
Im quite sure its a part of forum rules last time i checked but you have to link source code in the thread
Mentioned here
http://forum.xda-developers.com/showthread.php?t=2310958

Envious_Data said:
@Rafael.Baugis
Im quite sure its a part of forum rules last time i checked but you have to link source code in the thread
Mentioned here
http://forum.xda-developers.com/showthread.php?t=2310958
Click to expand...
Click to collapse
Not forum rules. XDA is a proprietary as it gets and has no ties with FSF . Its the General Public Licence that its in fact the reason why you have to link source code. You are not allowed to modify that licence, you are allowed to distribute as long as the same licence is carried over and the source is made available. Since the Android system started as GPL, everything based after it will and must be GPL.

Have any source code?

o2xygen said:
Not forum rules. XDA is a proprietary as it gets and has no ties with FSF . Its the General Public Licence that its in fact the reason why you have to link source code. You are not allowed to modify that licence, you are allowed to distribute as long as the same licence is carried over and the source is made available. Since the Android system started as GPL, everything based after it will and must be GPL.
Click to expand...
Click to collapse
Source changes inside the .zip file

help needed
@Rafael.Baugis
hey hii i just wanna know, if u could develop a kernel for xperia ion LT28h based on the new Xperia Z2 4.4.2 stock rom
we r waiting to port the base stock rom (4.4.2) on our xperia ion
it would be my pleasure along with all the other xperia ion users for ur kind n generous help
thanks

[LOLLIPOP] Xperia AOSP Project

hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
PS.
in case latest software does not appear just press "all Services"
flash latest software available and on top new loader

Custom ROM We Want! (Xperia T3 D5102)

jerpelea said:
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
Click to expand...
Click to collapse
Good news for T3 devices!

All we need now is cwm/twrp recovery and the show may begin!!
great lollipot binaries... so android 5.0 will finally come to T3 ;p

updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

How do we set up?

Berkant Ayhan Karabudak said:
How do we set up?
Click to expand...
Click to collapse
if you read the guide you will see

jerpelea said:
if you read the guide you will see
Click to expand...
Click to collapse
I am in turkey. My english is not so good.

Do you make installation guides?

AOSP 5.0.2 is published
http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/

http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/
- updated L build guide published
- new blob zip
- wifi is built into kernel
- media is built from source now
- NFC built from source
- audio built from source
- GPS built from source
enjoy
J

Error in sony.xml
<project path="device/sony/kernel" name="kernel" groups="device" remote="sony" revision="aosp/LNX.LA.3.5.2.2-03010-8x74.0 " />
Click to expand...
Click to collapse
You have a space after 8x74.0 and the "

jerpelea said:
hi all
we have included this device in open devices project
...
feel free to fork, build, fix and push back
Click to expand...
Click to collapse
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.

lalotche said:
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.
Click to expand...
Click to collapse
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J

build guide has been updated for easy reading
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
br
J

jerpelea said:
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J
Click to expand...
Click to collapse
That sounds better.
I have not enough time to make it seriously and full time but I've got a few ideas to try and of course - I'm going to check new aosps and new GServ. releases.
As Google services are essential for android functionality until I get it stable I won't try to build more complex set.
Sent from my D5103 using XDA Free mobile app hurray

First shot.
So. It was little trouble for google made geek.
After a few hours of hard fight (I mean hard googling) I've got rooted system and gaps working.
I decided to root it to easier play with system apps. I did not want to hack source tree as well.
Curious - make_ext4fs changes file privileges (I've needed to add some stuff into system.img).
I had to add some lines to init.rc to correct it.
There are some minor issues appearing in dmesg - could live with that.
And the one major problem - internal speaker is dumb.
Ear phones works right, but speaker is necessary - this is my only phone
l

custom rom for sony T3 D5102
please port custom rom for sony xperia T3 D5102:good::good::good::good:

So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
I'm considering install an AOSP ROM because I love pure android but I guess I'll give a try to Sony's one until this ROM is perfectly stable.
Have nice day!
Enviado desde mi XT1032 mediante Tapatalk

gbueno6 said:
So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
Click to expand...
Click to collapse
Yes. It looks, that everything else for D5103 is ok.
I checked headphones, microphone, gps and wi-fi.
I did not check bt, nfc and others (accelerator?) but nobody reported its faults.
For me speaker is necessary but if you like I've got even rooted 5.0.2 with gaps (git 2015-02-15).
l

Android M Developer Preview for Xperia Z1 [July-04]

Introduction
Hello,
Recently Sony released their source binaries for the Android M Developer Preview, so I decided to build and share it . Keep in mind this is a Developer Preview. It's just to give an idea of how the new Android M looks like. Both the camera and modem aren't included by Sony, so you can't use those.
Click to expand...
Click to collapse
Not included
Modem
Camera
Click to expand...
Click to collapse
Installation instructions
Make a back-up and store it outside of your phone.
Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable.
In the terminal on your computer type the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
Now when you disconnect your device from the computer and start it, it will be running AOSP.
Click to expand...
Click to collapse
XDA:DevDB Information
AOSP M, ROM for the Sony Xperia Z1
Contributors
aquaboy11
Source Code:
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/list-of-devices-and-resources/
https://android.googlesource.com/platform/manifest/+/android-m-preview
https://github.com/sonyxperiadev/
ROM OS Version: Android M
ROM Firmware Required: C6903
Based On: AOSP
Version Information
Status: Testing
Created 2015-06-26
Last Updated 2015-07-04

good for trying how M looks but hope some one will come with a patch to make modem work... I tried to build it too.. but reposync will take for ever

jos_031 said:
good for trying how M looks but hope some one will come with a patch to make modem work... I tried to build it too.. but reposync will take for ever
Click to expand...
Click to collapse
I don't think anyone wants to port the modem and camera to a Developer Preview. We will have to wait for Sony to do that.

Think the modem is intentionally disabled from the article i read, interesting that its using the 3.4 kernel though, i would have thought 4.x or at least a newer 3.x.. Did not spot a link to the sources(?), i really like the way Sony Ericsson has managed these projects ( the Z series), not only will it benefit us in the future when they eventually deprecate the project, but actually including the community and promoting development rather then hampering it by all means possible, reason enough for me to recommend the series, me like :>

threader said:
Think the modem is intentionally disabled from the article i read, interesting that its using the 3.4 kernel though, i would have thought 4.x or at least a newer 3.x.. Did not spot a link to the sources(?), i really like the way Sony Ericsson has managed these projects ( the Z series), not only will it benefit us in the future when they eventually deprecate the project, but actually including the community and promoting development rather then hampering it by all means possible, reason enough for me to recommend the series, me like :>
Click to expand...
Click to collapse
Oops, I forgot to include the sources . Will add them now .

I tested it, and think it's only more buggy lollipop, which sony/google called "m". Any new features like multiwidow from m preview, API 22 (from 5.1), old lockscreen, lollipop easter egg, and strange android version 5.1.51
Bluetooth sharing gives FC. When Sony give us a full working clear aosp ?
Wysłane z mojego Xperia Z1 przy użyciu Tapatalka

It's not Sony's fault. Google hasn't made the new APIs open source yet. They have just given build instructions for the aosp M preview branch.
I wouldn't recommend using this, as there's absolutely no difference from Lollipop as far as I've seen.

aquaboy11 said:
Oops, I forgot to include the sources . Will add them now .
Click to expand...
Click to collapse
Read trough the build guide.
It's supposed to use the 3.10 kernel. I'm having all sorts of problems with this kernel though, i havent gotten it booting on the device yet.. .Just says missing dtb no matter what i do .. even creating the zImage-dtb trough config or manually results in fastboot saying no dtb...
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/AU_LINUX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067" />

threader said:
Read trough the build guide.
It's supposed to use the 3.10 kernel. I'm having all sorts of problems with this kernel though, i havent gotten it booting on the device yet.. .Just says missing dtb no matter what i do .. even creating the zImage-dtb trough config or manually results in fastboot saying no dtb...
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/AU_LINUX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067" />
Click to expand...
Click to collapse
You can try to put the kernel sources into a build environment, i.e., any cm based rom, do build envelope, launch your device, then do mka bootimage and see what happens. But generally, this development has been nothing short of grossly pathetic. Linux now has fully working 4.x kernels. I don't necessarily blame developers primarily, as the main culprits are Sony and Google. However, oems are not more cooperative with linux developers than with android devs, yet linux is ages ahead not only in terms of kernels, os, but also in creating open source firmware...

optimumpro said:
You can try to put the kernel sources into a build environment, i.e., any cm based rom, do build envelope, launch your device, then do mka bootimage and see what happens. But generally, this development has been nothing short of grossly pathetic. Linux now has fully working 4.x kernels. I don't necessarily blame developers primarily, as the main culprits are Sony and Google. However, oems are not more cooperative with linux developers than with android devs, yet linux is ages ahead not only in terms of kernels, os, but also in creating open source firmware...
Click to expand...
Click to collapse
True, replacing the kernel directory and running a script to remake the headers from that kernel used to build android is the way to port android to a new kernel. I'm not building a rom atm though, i'm building the kernel only (bellow). I suspect the 3.10 kernel and newer require an updated bootloader.. However, in what way updating this would affect my ability to boot 4.4.4 i do not know, so im a bit weary.
Code:
ARCH=arm CROSS_COMPILE="$home"/dev/sdk/linaro-gcc-4.9-abe-gnueabihf/bin/arm-none-linux-gnueabihf- make -j8
dtbTool -o dt-0.img -s 2048 -p/scripts/dtc/ arch/arm/boot/ ( changed arch/arm/boot/ to arch/arm/boot/dtb in later kernels)
mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x37 ehci-hcd.park=3 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y vmalloc=400M" --base 0x00000000 --kernel "$home"/dev/nix/xperia/xperia-c6903-z1-source-final-4.4.4-0/arch/arm/boot/zImage --ramdisk "$home"/nix/xperia/boot-xperia-c6903-z1-sony-kernel-0/157/kernel_S1-SW-LIVE-6732-PID1-0005-MMC.elf.ramdisk --ramdisk_offset 0x02000000 -o boot-0.img --dt dt-0.img --tags_offset 0x01E00000
Also spotted this (Recovery mode now available for a range of unlocked Xperia devices) http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/ , however, my device (thankfully) runs Customized NCB_1276-9897 ( scandinavia ), so i dont know how well it would take to a UK rom, which has been updated.
As i mentioned before elsewhere, porting to a newer kernel ought be relatively easy, 4.1 would be a natural choice, its LTS and i suspect Android M or so will probably land there..

threader said:
True, replacing the kernel directory and running a script to remake the headers from that kernel used to build android is the way to port android to a new kernel. I'm not building a rom atm though, i'm building the kernel only (bellow).
Click to expand...
Click to collapse
I know you are not building a rom, but my point is it is much better to compile a kernel in a native (to your device) environment with all the tools already there. You also have your native ramdisk, as opposed to some generic one. I have built quite a few kernels using this method and it has yet to fail once...

True, as it stands now, the way im assembling the boot.img it's incompatible with certain installers for Multibot, using the method you described would avoid that entirely.
Spotted the nexus 5 and 7 are on 4.2.2 for android m. I guess 3.10 is just a step.

no links?

OptidroidPlus said:
no links?
Click to expand...
Click to collapse
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?

drakonizer said:
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
Click to expand...
Click to collapse
give me links please? i am new in xda.. thanks

drakonizer said:
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
Click to expand...
Click to collapse
No, it's still a buggy Lollipop version. The update just includes the latest commits and changes made to the project.

OptidroidPlus said:
give me links please? i am new in xda.. thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=10518#downloads

Thanks!!

Android M Preview 2 is coming ? http://www.droid-life.com/2015/07/09/android-m-developer-preview-2-now-available/
Sent from my Xperia Z1 using Tapatalk

danny19901 said:
Android M Preview 2 is coming ? http://www.droid-life.com/2015/07/09/android-m-developer-preview-2-now-available/
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
I doubt Google is going to update AOSP sources...one can only hope. @aquaboy11 Could you post a changelog of any noticeable difference when you update your builds? Thanks...

[Sony] Xperia Open Devices Project

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.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues

Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J

jerpelea said:
Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J
Click to expand...
Click to collapse
Is the xa going to be included in the open devices project or excluded due to being a mediatek powered Xperia.
Sent from my Xperia XA using XDA Labs

aidy.lucas said:
Is the xa going to be included in the open devices project or excluded due to being a mediatek powered Xperia.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
For the moment we don't support MTK
Regards
J

jerpelea said:
Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J
Click to expand...
Click to collapse
Are you going to add X performance / XZ to open device program?
There are no vendor binaries for them on open devices page.

millosr said:
Are you going to add X performance / XZ to open device program?
There are no vendor binaries for them on open devices page.
Click to expand...
Click to collapse
It's a work in progress.

Vendor binaries already released for X Performance on jan 10.
The experimental 7.1 build is working fine (as documented, no front facing camera, fingerprint reader, etc).
It is takes ~5 hours to build on 4 core, 16GB memory vps (Softlayer) and requires lot of disk space (near 106GB repo, source and build output)

Are you going to add the xperia e4 to the open device list?

We have moved to a new address!
https://developer.sony.com/develop/open-devices/

Now you can build the latest Android with the latest 4.4 kernel

Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates

For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J

What is this?

All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues

on disabling dm-verity & FBE
jerpelea said:
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
Click to expand...
Click to collapse
Hello, Alin,
thanks for your continuous support,
could you instruct the community on how exactly to disable those 2 functions prior to building an AOSP?
With kind regards,
thank you for your time.
UPD #1: as per https://stackoverflow.com/a/45968174 need to comment out the line (PRODUCT_SYSTEM_VERITY_PARTITION) in ${SOURCE_TREE_ROOT}/device/sony/tone/platform.mk
UPD #2: seems like installing a Magisk module does not change the encryption behaviour Maybe shoud check with TWRP on this.

Android Wear 2.0 for SmartWatch 3 port progress Thread & Creation of OSS project

Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire

I need that so much any ETA ?
By the way keep up the good work !

Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs

Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk

great!!! thanks

Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:

thankx you great hard work and good luck my friend

I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.

drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire

but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?

xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.

@PDesire :
You're the man...keep up a good work ???

Hey @PDesire , any news? I'm sooooo hyped!!!

Thank bro I hope

Thanks for this!

So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire

PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???

Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app

Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...

Thank you very much, hope you will finish it without problems~!