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
Related
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...
HybridRom Concept EditioN
New Z1:
I decided to buy a secondhand Z1, so now I can continue developing. As school is starting again soon I will not be able to do a lot. I will do what I can.
Description:
We all got used to the idea that most stable ROM is a Stock one.
This ROM will prove you otherwise.
This ROM was previously only available for the Xperia ZU, but thanks to @Doom Slayer's new development group it will start spreading to other Xperia devices. Some apps might not be the newest, but they are very stable. Our main priority is making the ROM compatible with other Xperia devices before updating every app. Today we have decided to release the first open beta for the Xperia Z1. There is only one problem we know of so far, which is an issue regarding the rear-facing camera. Sometimes the camera saves corrupt photo's. Video recording, front-facing camera, Snapchat, taking WhatsApp photo's etc. work just fine.
Feel free report bugs and help us squatting them .
Main Futures:
Very fast and responsive ROM based on Z3 aosp concept and GPE libs with amazing battery life and memory management.
Perfect combination of Sony and Google apps.
No bloatware, no adds.
Only 400 megabytes.
Optional modifications.
Installation options:
Feel free to install the rom the way you want to:
Are you an advanced user who'd like to experiment with their phone?
Feel free to install our mod for theme support and kernel for advanced futures.
Change log:
Kernel 24-aug
128kHz and 24bit audio
Fixed fauxsound
V2.0.1:
Fixed zip file
V2:
Updated Sony and Google apps
Removed:Browser,Google Now,Gmail,Viper,Video(support implemented in Album) and some other bloatware.
Fixed Sony Sound Enhancements
Fixed Write To SD Card (I hope so)
Added new weather widget
Bugs:
Flashlight (probably camera related)
Autorotation
Some people might have 5ghz wifi connection problem
Wifi may disconnect during screen off no matter the settings. (This is android problem, not my rom)
The rear-facing camera sometimes saves corrupt photo's
Installation Instruction:
Make sure that your Bootloader is Unlocked.
Boot in TWRP.
Wipe system,data,and both caches.
Flash the ROM.
Reboot device.
Prepare to be amazed.
Mods and fixes, but don't install these kernels on your Z1!
Credits:
@Jozinek for Z3 AOSP Concept
@ATMOSF3AR Z Ultra PSD
XDA:DevDB Information
HybridRom Concept EditioN, ROM for the Sony Xperia Z1
Contributors
aquaboy11, Doom Slayer
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Z3 AOSP Concept, Stock and GPE
Version Information
Status: Beta
Current Beta Version: 2.0.1
Beta Release Date: 2016-07-26
Created 2016-07-26
Last Updated 2016-08-24
Reserved
This post can be removed as I jus figured out how to reserve posts using DevDB .
Since ZU and Z1 have similar hardware, I can provide some support as well. @aquaboy11, thank for opening a thread, let's make a cabdy out of that ROM.
A person who will find a way to fix camera will become a member of out dev team.
Also, if you have experience with kernels, then you can try to make a defconfig for my own kernel, which will allow me to bring a kernel as well, kernel with fauxsound, dt2w and etc.
I don't have Z1 on my own unfortunately.
Doom Slayer said:
Since ZU and Z1 have similar hardware, I can provide some support as well. @aquaboy11, thank for opening a thread, let's make a cabdy out of that ROM.
A person who will find a way to fix camera will become a member of out dev team.
Also, if you have experience with kernels, then you can try to make a defconfig for my own kernel, which will allow me to bring a kernel as well, kernel with fauxsound, dt2w and etc.
I don't have Z1 on my own unfortunately.
Click to expand...
Click to collapse
Glad to see that new devs are arriving to our device. But for the dt2w feature on kernel, it's not possible for z1 because of a deepsleep's bug.(i don't think it's possible to correct it).
Nice. I hope it comes to our Z1 Compact
FotoMichi said:
Nice. I hope it comes to our Z1 Compact
Click to expand...
Click to collapse
It's a next device in the to-do list
FotoMichi said:
Nice. I hope it comes to our Z1 Compact
Click to expand...
Click to collapse
I might give it a shot , I'll see what I can do!
Hello, this ROM for which the Xperia version is compatible?
For all codename "honami": Xperia Z1 C6902, C6903, C6906, C6943 ??
Thank you
pickmod said:
Hello, this ROM for which the Xperia version is compatible?
For all codename "honami": Xperia Z1 C6902, C6903, C6906, C6943 ??
Thank you
Click to expand...
Click to collapse
C6903 for now, I don't have testers for the others, but I do think I could build it. Send me a pm if you are wanting to test it.
Error while trying to flash the ROM. Error 6 in TWRP.
Also can't fastboot the files inside the zip.
Downloaded this file 3 times already. Am I doing something wrong?
aquaboy11 said:
C6903 for now, I don't have testers for the others, but I do think I could build it. Send me a pm if you are wanting to test it.
Click to expand...
Click to collapse
Count me in as your tester..
Impossible to install for me too. I have E : Error executing updater binary in zip ' /external_sd/hybrid_concept....
nemesisexsp said:
Error while trying to flash the ROM. Error 6 in TWRP.
Also can't fastboot the files inside the zip.
Downloaded this file 3 times already. Am I doing something wrong?
Click to expand...
Click to collapse
benplay said:
Impossible to install for me too. I have E : Error executing updater binary in zip ' /external_sd/hybrid_concept....
Click to expand...
Click to collapse
This should be fixed now.
aquaboy11 said:
This should be fixed now.
Click to expand...
Click to collapse
Nice non it's fixed and aller works smoothly, but how can we change dpi? Can we flash universal path? I don't underground the système ui thing you said on Xperia zu post#2
benplay64 said:
Nice non it's fixed and aller works smoothly, but how can we change dpi? Can we flash universal path? I don't underground the système ui thing you said on Xperia zu post#2
Click to expand...
Click to collapse
To change the doing you need to edit the build.prop. Open it up with any build.prop editing app and look for ro.sf.lcd_density, just typing lcd in search should be enough. Adjust the dpi to your liking, save and reboot.
For the universal path, I think you should be able to just flash it. If it doesn't work, then just reflash the rom and you'll be good to go. Be sure to tell us if it doesn't work.
aquaboy11 said:
To change the doing you need to edit the build.prop. Open it up with any build.prop editing app and look for ro.sf.lcd_density, just typing lcd in search should be enough. Adjust the dpi to your liking, save and reboot.
For the universal path, I think you should be able to just flash it. If it doesn't work, then just reflash the rom and you'll be good to go. Be sure to tell us if it doesn't work.
Click to expand...
Click to collapse
Downloading and will flash on a moment. Will let you know how it goes...
Edit:all is working like a charm! Applied a whole layers theme (prime), no bootloops or any other issues... PexoCam is not working though, will try some more cam mods and report wonderful job guys! Thank you so much!
Okay so I don't think I will try advanced path because inside there is a zu system ui.apk so it will probably not work. But I saw that substratum have just been put to Google play store. Can we use it or it needs to add pluggins in the rom?
benplay64 said:
Okay so I don't think I will try advanced path because inside there is a zu system ui.apk so it will probably not work. But I saw that substratum have just been put to Google play store. Can we use it or it needs to add pluggins in the rom?
Click to expand...
Click to collapse
I tried it a while ago and it does not seem to work. The app FCs when trying to open a theme.
benplay64 said:
Okay so I don't think I will try advanced path because inside there is a zu system ui.apk so it will probably not work. But I saw that substratum have just been put to Google play store. Can we use it or it needs to add pluggins in the rom?
Click to expand...
Click to collapse
It will work.
UI is actually from Z3 and it's working on Ultra.
Why it won't work with on Z1?
Only thing is changed is dpi, which can be done in build.prop.
Btw if u applying themes, apply framework for Android M!
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~!
Disclaimer:
* You flash this ROM at your own risk and responsibility.
* This ROM is provided without ANY WARRANTY WHATSOEVER, not even the warranty that it works.
* None of the developers of this ROM will be held accountable for any damages, complaints or anything.
Hello! I have stopped all android related work year ago, last month I decided to try @SuperLamic device trees from Z1 forum, but I wasn't abble to boot CM kernel and I decided to use stock kernel and try boot it, done. Had some touch screen isues and some more but after some days of working on it finally made kernel fully functional. I have contacted SuperLamic and got his permission and want to share build backported from his Z1 but its a bit diferent because I'm using different kernel -
patched stock kernel, here is build and changelog , almost fully working! I have opened this thread mainly bacause I want to try help SuperLamic and hope we get clear rom on booth devices. I will share working stock kernel on git hope at a weekend! At a weekend I will solder uart on my seccond z1c and dump bootloop log and provide it to SuperLamic since he was unable to debug an CVE clean kernel which have bootloop because of his broken Z1, hope we switch soon to that kernel on booth devices. One more diferencie my build is selinux enforce, I will try to make a diff file and provide patch for Z1 guys. Curently done this using my PoC which curenly have updated selinux stufs, but I will need to decompile booth sepolicy and make an diff file which we can use to easy implement into Z1 and Z1C device tree.
If you need twrp:
- read this https://forum.xda-developers.com/showpost.php?p=73586527&postcount=169
Credits which I need to put on this is:
1. ofcorse full credits goes to @SuperLamic since I have used his device tree from Z1
2. special thanks to guys who worked on camera libshims: tomascus, nailyk, rcstar6696, xkeita, special thanks to @tomascus guy who worked with me 1 year ago when we got stock kernel working on nougat and done some initial work to stock camera hals, just to remind you this is a thread https://forum.xda-developers.com/crossdevice-dev/sony/discussion-development-custom-rom-t3479108
Kernel source code:
- https://github.com/SuperLamic/android_kernel_sony_msm8974 branch cm-14.1
If you notice any bug please report, need to know to be able to make list of bugs and asign fixing priority!
munjeni said:
If you notice any bug please report, need to know to be able to make list of bugs and asign fixing priority!
Click to expand...
Click to collapse
Here's what I found -
* default screen dpi = 480. Not a problem to change, but it's pretty funny looking
* 'mtp host has stopped' message, whenever certain activity chooser functions are called on. Doesn't cause any problems, just press 'ok' and it goes away.
I forgot to change dpi to 320, next build will get that change. About mtp host stopped working, solution (temporary) is to disable mtp app in setting so it will no more cause those popups, I didn't noticed anything aftected by disabling that app, have no idea what is usage of these app. When I get more free time will look into source code to get idea whats going on with that app. Thanks for reporting!
I'm curently on stock rom since my battery is almost dead, need replacement battery Anybody recommend me an good battery for z1c?
Hi @mujenii!!
You did it!!¡
Congratulations!?!!
Sent from my Nexus 7 2013 WiFi using XDA-Developers Legacy app
Hi mate, thanks! I just spent some days on it but I can't say I did it, guys from z1 forum is responsible for our almost stable and great rom!
That Full stock camera hal means that the camera will be as good as in stock sony roms ? It would be dream come true since camera is huge thing for me on this phone
MozkoZrout said:
That Full stock camera hal means that the camera will be as good as in stock sony roms ? It would be dream come true since camera is huge thing for me on this phone
Click to expand...
Click to collapse
Yes man camera is almost the same, in my opinion better than stock one! Fast response and fast focus
Some screen shoots
munjeni said:
Yes man camera is almost the same, in my opinion better than stock one! Fast response and fast focus
Click to expand...
Click to collapse
Wow awesome i need to try it than, you shall be praised as god if you really made this possible
Hello,sorry for my blindness)) but where is the link to the download? throw off me please..
AreusShow said:
Hello,sorry for my blindness)) but where is the link to the download? throw off me please..
Click to expand...
Click to collapse
Post 1... 'build and changelog'
levone1 said:
Post 1... 'build and attachments'
Click to expand...
Click to collapse
Fanks
Thank you for the great job! Gonna flash it today and report!! :good::good:
Hello @munjeni , is Real Recovery required for this rom?
cam not working
i instal this rom>cam not work
AreusShow said:
i instal this rom>cam not work
Click to expand...
Click to collapse
Make sure to full wipe, (data, caches, and system). Rom and camera working fine.
AreusShow said:
i instal this rom>cam not work
Click to expand...
Click to collapse
heorung said:
Hello @munjeni , is Real Recovery required for this rom?
Click to expand...
Click to collapse
Read carefully my site instructions and chance for bad installation is minimal. I'm on our rom for about 3 days, apsolutly my favorite rom! Camera apsolutly work!
If somebody need wallpapper and the same look like my screenshoots use walpapper from http://orig00.deviantart.net/d43e/f...llpaper_red_034_by_charlie_henson-daa22ts.png and weather from
https://play.google.com/store/apps/details?id=mobi.lockdown.weather
I just can't wait anymore
Deemooo said:
I just can't wait anymore
Click to expand...
Click to collapse
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
sorry, i don't understand the system domain, i just a normal xperia user, just want to use native android likes los,dotos,rr etc. I'm sorry i can't help you, All i can do is wait, that's some sad.
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
Yes I see xperia merge fix in sources actually for kernel sources issue compile . I will create custom kernel for start . lineage later
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
I guess we can create repo vendor and extract proprietary blobs from stock vendor...
I tested phh gsi lineage and its fully stable guy - in bonus green tint is fixed -
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Kyrimeas said:
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Click to expand...
Click to collapse
for now no . I run actually gsi phh in daily use for stability . for sources I still work on it I have worked for compile kernel xperia https://github.com/Aarqw12/kernel_PDX213/commits/aosp/LA.UM.9.12.r1 but no luck actually its bootlop only for unknow reason.
Kyrimeas said:
Are you also building recovery?
Click to expand...
Click to collapse
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
zpk787 said:
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
Click to expand...
Click to collapse
for stability build-in is very recommanded
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
no need vendor image, need only flash oem.img xperia give really everything . lena sodp is no completly done for now , new features need to be implemented team sodp work on it. I guess just wait more
now xperia 10 III is officially added to open-source programm
Xperia 10 III added to Sony's Open Devices program - Sony Developer World
developer.sony.com
software binary released now we can compile rom
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
yeah，i also think we can have roms in the furture，im waiting
Kyrimeas said:
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
Click to expand...
Click to collapse
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
You can check "e foundation" GSI. It's ungoogled phones
ada12 said:
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
Click to expand...
Click to collapse
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
xinniethewuflooh said:
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
Click to expand...
Click to collapse
GSI is no a custom rom its a Generic System image , its update only /system ( os framework ) and use blobs,drivers from your /vendor , GSI is universal and run in all devices treble .
They are no custom rom available in public actually for this devices , source for custom rom is availlable but unstable in use ( sound only in headset , ril bug ... )
actually if you want run lineage or other custom android os use PHH GSI , or wait for custom rom ( NO ETA ).