Related
if cm11 out i will buy one
Sent from my Moto G using Tapatalk
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Riyal said:
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Click to expand...
Click to collapse
Not CM11, but still very exciting =)
TheQwertiest said:
Not CM11, but still very exciting =)
Click to expand...
Click to collapse
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Riyal said:
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Click to expand...
Click to collapse
We wait for CM11!
Xperia V, T doesn't have official 4.4 ROM too, but they have CM11.
Also, I think it's possibile developing CM11 or other CM11 based (KitKat) AOSP ROM.
Unfortunatelly I can't develop it...
I just will use it :fingers-crossed:
u guyz are lucky...u have munjeni wid u now. just be patient.. his hardwork brought cm11 novathor devices... which were abondoned on ics.
two reason i see z1compact as my next phone is that i dont like large phones and master munjeni has z1c also...
We can use CM11 from Z1 since Z1 CM11 on Z1C is working but there is no display available since CM kernel on MSM8974 need some changes related to the Z1C display Bad news is we can not use stock kernel since gralloc, copybit ..etc is not working than. I started working on CM kernel but hmmm CM kernel and stock kernel is a lot diferent so hard work is needed If we get CM kernel working we will get CM11 working with no big modifications
Edit:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded https://github.com/CyanogenMod/android_kernel_sony_msm8974 branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Can't wait to try CM
kernel config from boot.img
munjeni said:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded{removed} branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Click to expand...
Click to collapse
Hello,
I am not sure if this is helpfull, but I'll give it a try: You are right - there is absolut no difference between the two kernel configurations, beside that one line. Since there are already nightlies available for the Z1(honami) I thought there might some helpfull informations inside that nightly. Of course there was a boot.img inside the nightly and I found that script to extract the kernel.config from that boot.img. Using the extract-ikconfig from my xperia z(yuga) kernel located in ./kernel/sony/apq8064/scripts/extract-ikconfig.
If the extracted config is reliable, there are indeed many differences.
I attached the extracted config. Maybe you remove the Lines starting with # and the blank lines for a better compare.
Let me know if I can help in some way.
Kind Regards
I don't know whats going on or why CM kernel is working on Z1 and not on Z1C but I think these fails on Z1C is related to the baseband and bootloader? Just asking, DO NOT FLASH THEM!!!
And another thing is maybe dtbs is a thing related to the fail since I can see some things in dmesg related to the pingpong command in mdss_mdp_intf_cmd.
Error log -> http://pastebin.com/9zgcWd4a
Thanks to the developers who are trying to make CM11 working on this phone. I will buy this phone if CM11 is available
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Riyal said:
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Click to expand...
Click to collapse
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Nope, doesn't seem to boot :/
munjeni said:
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Click to expand...
Click to collapse
Yeah but I just relocked my bootloader yesterday. I won't be unlocking it till I get more time in development.
crytic said:
Nope, doesn't seem to boot :/
Click to expand...
Click to collapse
Weird then... The patch I applied to port z1 kernel to z1 compact made a fully working stock kernel. But when I applied it to CM kernel it doesn't even boot. Can you by chance get a copy of /proc/last_kmesg and upload it somewhere or here?
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6nuname -r
uname -r
3.4.0cyanogenmod-g77098c0-dirty
~ # ←[6n
Click to expand...
Click to collapse
munjeni said:
Click to expand...
Click to collapse
Woot! There it goes Now I don't have to port CM haha!
Sweet, with or without display?
crytic said:
Sweet, with or without display?
Click to expand...
Click to collapse
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
munjeni said:
Click to expand...
Click to collapse
munjeni said:
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
Click to expand...
Click to collapse
git bisect to the rescue Well, if you need any help, just drop me a line!
Hello Everyone!!
So here is a new ROM I compiled yesterday, it does have a lot of features and it is called SONIC OPEN KANG PROJECT
I didn't open a new thread for it because I'm not gonna be updating it unless many users encourage me to do so...
Anyway I thought I should share it with you guys, for who ever wanna test it
Here is this ROM's features:
http://sonic-developers.com/?page_id=160
Also here is a quick review for the ROM:
And for more info visit their website:
http://sonic-developers.com
Download Link:
I've started uploading my files to androidfilehost.com , hoping you like it more than Dev-host
SOKP-MS-04-KK444-KTU84Q-20140726-amami.zip
Here are my screenhots as well:
Hello Guys,
Since our lovely Z1C is relatively new, it doesn't have many CM based ROMs, so I thought why not porting some
from the closest phone to ours (which is obviously Xperia Z1).
So I'll be presenting five ports for five ROMs as mentioned in the title, but I'm gonna start with a simple guide for how to port the ROM yourselves
All you have to do to port a CM11 based ROM from Z1 is:
Download the Z1 ROM and extract it wherever you want
Open META-INF\com\google\android\updater-script with any text editor and remove first five lines (assert)
Download This for old builds, and This for new builds, then unzip it
Copy and replace "boot.img" from the previous zip to your Z1 ROM
Copy and replace "modules" folder to system\lib\modules in your Z1 ROM
Open system/build.prop with any text editor and change this value:
Code:
# Graphics
ro.sf.lcd_density=480
to become:
Code:
# Graphics
ro.sf.lcd_density=320
that is it, although there are optional things you may do before compressing the ported ROM:
In system/build.prop search for honami and replace them with amami
And then search for C6903 and replace them with D5503
Also you may wonna add "Compact" here:
ro.product.model=Xperia Z1 Compact
Click to expand...
Click to collapse
You may also open META-INF\com\android\metadata and do the same replaces
Resign the ROM.zip after compressing it
Important Notes:
DO THIS ON YOUR OWN RISK
You must be running KK ROM before flashing these ROMs down below
This method won't work on Slimkat, although you can grab it from Here
All bugs in these ROMs are related to the original ROM not issues caused by posting
Fell free to report any bugs you face though, and I'll enlist them in known issues
PacMan ROM and MoKee ROM are officially supported, so there is no need to port them
Instructions for all ROMs down below:
Copy the zip to your device
Reboot into recovery
Backup of your system (optional)
Do a factory reset and format [/system]
Flash the Zip
XenonHD & BeanStalk
:::The XenonHD ROM:::
This was built in (2014-04-02) [Build 5]
It contains CM11 FXP312 Kernel
Zip is resigned
Screenshots:
Download link:
update-XenonHD-04-02-14-signed-amami.zip - 238.44 MB
New build's port can be found here: (Not tested by me)
http://forum.xda-developers.com/showthread.php?p=53365536
For more info and screenshots, visit the Original Thread
:::The BeanStalk ROM:::
This was built in (2014-03-11) [Build 3]
It contains It contains CM11 FXP312 Kernel
It has random reboot bug
Zip is resigned
Screenshots:
Download link:
BeanStalk-4.4.255-20140311-amami.zip - 251.39 MB
For more info and screenshots, visit the Original Thread
:::Gapps:::
GApps Standard 4.4.2 (10/5)
Removes AOSP Camera and AOSP Gallery and Replaces it with the Google variants
Removes AOSP Launcher2/Launcher 3 and CM Trebuchet and Replaces it with Google Now Launcher
Adds Google Search aka Google Now
All necessary syncing apks and libs
GApps Minimal 4.4.2 (10/5)
~20 MB
Playstore
Syncing apks and libs, etc.
Google Camera 4.4.2 (16/1)
Automatically removes AOSP Camera/Gallery and adds Google Camera/Gallery
FaceLock 4.4.2 (10/5)
Adds Face unlock
GenieWidget 4.4.2 (10/5)
Adds stock news and weather widget
AOSP Calendar Sync 4.4.2 (16/1)
Adds syncing ability for AOSP Calendar (not in Core or Standard packages)
AOSP Browser Sync 4.4.2 (16/1)
Adds syncing ability for AOSP Browser (not in Core or Standard packages)
This was copied and pasted from Original Thread (you can find more Gapps mirrors here)
Personally I prefer [and have tested] the minimal Gapps package, it is the best
Great work!
I wonder if you would do Slimrom also, it is a mainstream ROM with many innovations that other ROMs have copied.
[edit] Duh I just read your comment about slimkat. That'll learn me to read OPs properly...
wow, this looks good, i think ill try MoKee, just one question, is everything working ?
Just flash rom and some gapps ?
juried said:
Great work!
I wonder if you would do Slimrom also, it is a mainstream ROM with many innovations that other ROMs have copied.
[edit] Duh I just read your comment about slimkat. That'll learn me to read OPs properly...
Click to expand...
Click to collapse
actually, just today; @akshaybz has opened a thread for slimkat (not ported, compiled) here:
[ROM][4.4.2][KOT49H] SlimKat - Amami [Build 4][Alpha][UNOFFICIAL]
Enjoy
xhizors said:
wow, this looks good, i think ill try MoKee, just one question, is everything working ?
Just flash rom and some gapps ?
Click to expand...
Click to collapse
Well I didn't test everything, but the ROM was flawless, wifi is OK
Yes just flash rom and some gapps, try it and give a nice feedback
Might be a dumb question, but will updating them through the rom settings mess anything up?
RevokOne said:
Might be a dumb question, but will updating them through the rom settings mess anything up?
Click to expand...
Click to collapse
I don't expect updates to appear in the ROM's settings, but if they do,
yes updating that way should mess up a lot, it should make a bootloop.
anyway if you see an update for the ROM you're using, just tell me and I'll port the new release right away
omarainea said:
I don't expect updates to appear in the ROM's settings, but if they do,
yes updating that way should mess up a lot, it should make a bootloop.
anyway if you see an update for the ROM you're using, just tell me and I'll port the new release right away
Click to expand...
Click to collapse
I been building ROMs on linux trying and testing build from source..Im new to it and the device has been a long time HTC user. So guess all are from Z1 with afew changes you posted similar to the stock port way. I built a few roms so apart from the one I'm supporting. Carbon and PAC ROM has shown
Sent from my Xperia Z1 Compact using Tapatalk
Thread Updated
Ported MoKee 2014-03-31 Release
Ported Carbon 2014-04-01 (Build 2)
Also updated kernel in OP and in these two builds to 3.4.0 CM11 gb37510f From FXP313
I think I'll be updating the thread every week from now on, until these ROMs get a compiled version
Enjoy
How are the cameras qualities on these roms?
---
Sendt fra LG G Pad
slonn said:
How are the cameras qualities on these roms?
---
Sendt fra LG G Pad
Click to expand...
Click to collapse
Exactly like in CM11.0
omarainea said:
Exactly like in CM11.0
Click to expand...
Click to collapse
And how exactly is the quality in CM11, I can't seem to find a definitive answer in either CM thread?
Any updates on the roms btw?
Cheers! :good:
Thread Updated
e2zippo said:
And how exactly is the quality in CM11, I can't seem to find a definitive answer in either CM thread?
Click to expand...
Click to collapse
I don't know how to describe its quality, I think the best way to know is by trying
e2zippo said:
Any updates on the roms btw?
Click to expand...
Click to collapse
Yeah it's been a week, so here are the Updates of this week:
Updated Carbon ROM to build 4 (2014-04-09)
Updated MoKee ROM to build 2014-04-04 (its kernel was updated to FXP314)
Added XenonHD ROM latest release build 5 [2014-04-02] (download link in second post)
it is very customizable (can't describe it enough)
you can check more info about it in its main thread
about the kernel update, it seems like FXP team have messed up thier kernel a little
so when I tried it on Carbon and XenonHD I got some sort of bootloop,
but it worked fine on MoKee, so MoKee is the only ROM that has FXP314 kernel,
I don't recommended anyone to use it for porting so I didn't upload it
omarainea said:
about the kernel update, it seems like FXP team have messed up thier kernel a little
so when I tried it on Carbon and XenonHD I got some sort of bootloop,
but it worked fine on MoKee, so MoKee is the only ROM that has FXP314 kernel,
I don't recommended anyone to use it for porting so I didn't upload it
Click to expand...
Click to collapse
Actually the problem is not much with the latest kernel, but rather with the ROMs:
Recently there was a huge changeset merged in CM tree, among other things it took in kernel a lot of CAF code\blobs from 4.4 Sony sources, and Xperia CM ROM was rebased on this CAF kernel.
It means, that the ROMs based on CM must be rebuild using latest sources, otherwise they'll have a bootloop with the new CAF kernel =)
TheQwertiest said:
Actually the problem is not much with the latest kernel, but rather with the ROMs:
Recently there was a huge changeset merged in CM tree, among other things it took in kernel a lot of CAF code\blobs from 4.4 Sony sources, and Xperia CM ROM was rebased on this CAF kernel.
It means, that the ROMs based on CM must be rebuild using latest sources, otherwise they'll have a bootloop with the new CAF kernel =)
Click to expand...
Click to collapse
Huh, Thanks for the info bro,
seems like I should read more very now and then to know this kind of stuff.
Thread Updated
Added Paranoid Android ROM
This was built in (2014-04-15)
It contains CM11 20140410-Nightly kernel
Updated MoKee ROM
This was built in (2014-04-14)
The ROM was deodexed (original ROM was odexed)
It contains CM11 20140410-Nightly kernel
hi, should i have a unlock bootloader for test this roms? i can´t unlock it
canteo said:
hi, should i have a unlock bootloader for test this roms? i can´t unlock it
Click to expand...
Click to collapse
unfortunately yes, if you want to flash a custom kernel, you have to have an unlocked bootloader (and that is required to flash custom ROM)
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
I am looking for the CM12.1 20150813 build, if anyone has it. CyanogenMod Downloads only keeps the 5 latest builds.
If anyone redirects me to Bonoboo's post, I need the actual build zip, for other purposes. (And yes, it's for Enfriar Z5).
elmkzgirxp said:
I am looking for the CM12.1 20150813 build, if anyone has it. CyanogenMod Downloads only keeps the 5 latest builds.
If anyone redirects me to Bonoboo's post, I need the actual build zip, for other purposes. (And yes, it's for Enfriar Z5).
Click to expand...
Click to collapse
You can find that in Xperia M android development> Enfriar Z5 Rom thread :good::good:
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 ).