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
I recently got the xperia X, which is an awesome device, and this is good news! Thanks a lot. Developers, please!
Does flashing those ROMS means that they are turned into Nexus?
I assume we will loose the camera software and also the radio?
ykphuah said:
Does flashing those ROMS means that they are turned into Nexus?
Click to expand...
Click to collapse
No
ykphuah said:
Does flashing those ROMS means that they are turned into Nexus?
Click to expand...
Click to collapse
Yes. It turn your phone into 6p. Including your camera quality.
K
Thx
Bye.
Lol, I am sensing a lot of sarcasm here.
I have used Nexus before, and I have used HTC devices that are flashed to AOSP.
So can I confirm that we loose the camera software and also the FM radio if we flash this AOSP? I don't have a better way to describe this other than "make it a nexus".
ykphuah said:
Lol, I am sensing a lot of sarcasm here.
I have used Nexus before, and I have used HTC devices that are flashed to AOSP.
So can I confirm that we loose the camera software and also the FM radio if we flash this AOSP? I don't have a better way to describe this other than "make it a nexus".
Click to expand...
Click to collapse
Forgive me if I am wrong, but last time I used the sony open devices firmware on my previous xperia, we kept the camera quality just with the AOSP app.
@jerpelea when following the commands here, and following them exactly step-by-step based on the guide, I get the following:
[ 4% 2253/50550] host C++: llvm-tblge.../utils/TableGen/CodeGenDAGPatterns.cpp
ninja: build stopped: subcommand failed.
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (03:57 (mm:ss)) ####
Click to expand...
Click to collapse
Anyone else tried to follow the steps?
FYI, FreeXperia has released an experimental Nougat build for the X (suzu), which can be downloaded here.
I presume you can flash it onto your device by using fastboot.
iH8Ecchi said:
FYI, FreeXperia has released an experimental Nougat build for the X (suzu), which can be downloaded here.
I presume you can flash it onto your device by using fastboot.
Click to expand...
Click to collapse
Yeah they're found here and the last one was a week ago.
My reason for posting was I was trying to build myself
jerdog said:
@jerpelea when following the commands here, and following them exactly step-by-step based on the guide, I get the following:
Anyone else tried to follow the steps?
Click to expand...
Click to collapse
since it is a ninja error i suppose that you are on the wrong ubuntu version
please post a full log on the pastebin and pm me
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
jerpelea said:
Now you can build the latest Android with the latest 4.4 kernel
Click to expand...
Click to collapse
Will we see any official ota update from sony with this kernel?
The Open Devices and Official SW are built from different code base which means that the answer is NO
Regards
J
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
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
Related
Before to start flashing
This is an UNOFFICIAL version of CM12.1, so this means that have bugs that i hope to fix soon. So use it carefully at your own risk. The most important thing to say, after flash this ROM,is ....
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Installation Guideline
Install the lastest version of TWRP (it's in uploading state and have an important update in fstab file)
Power down your phone and go in recovery mode.
Copy the ROM file in your sdcard
Make a wipe data/factory reset
Install the zip you copied
Wipe cache
Reboot
What works
First Boot
Audio
RIL
SDCARD
Tethering
LEDS
Touchpad now works
Bluetooth (partial: pairing not works)
Some else i'm testing
Light and proximity sensors, Accelerometer, Gyroscope and Magnetic sensors
What not works
Camera
GPS
NFC
SMS
Anything else i will find and fix
Screenshots and Video
In the top of the pace, section Screenshots.
Download
M4 Aqua ProjectMarshmallow Official Site
Uploading in this moment. You will see a post on my site!
Installation
Be sure to have my TWRP installed on your device. If you don't have it go to my site and download it (see download section).
Download and copy the ROM and GAPPS in the root of your SD
Boot in TWRP
Wipe your data (wipe data/factory reset in TWRP)
Install the ROM (Install... in TWRP)
Install GAPPS (see more information in the following GAPPS Section)
Reboot
GAPPS
You can download your GAPPS here. Be sure to download the ARM64 version for 5.1. The pico version is the minimal one (save more space).
Bug Channel
Please report any bug and issues here!
http://projectmarshmallow.altervista.org/bug-channel/
Both the ROM and the new RECOVERY will be uploaded on my site. Stay in touch!
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia M4 Aqua
Contributors
tonystark88
Source Code: https://github.com/projectmarshmallow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Alpha
Created 2015-12-12
Last Updated 2016-04-30
Thanks for the rom, but where is the download? All I see is the download page for TWRP
Still uploading. I will advice you when finishs. Anyway its a testing ROM...not for daily use.
Does this has any problem with battery draining more than the stock rom? because this problem existed in my old ? z1 and i can't find anything related to the camera, so am asking if is it working? and any chance of porting z4 camera framework so we can use superior auto in this rom? Thanks in advance
I think is a bit premature make these kind of discussions now. When i'll make this rome stable (now it's a test build, have some reboot problems probaby lrelated to thermanager config) we can face more problems. But don't worry, any problem/idea will be faced at right time.
Awesome! Thank for your work!
Thanks for excellent work! Hope some major bugs could be fixed asap [emoji481]
Sent from my E2312 using Tapatalk
put more SS please...
WiFi not working???About Sound too??
And This is Android M or Android LP???
CyanogenMod 12 is based on android 5.x so that means this rom is lollipop
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Great news. Thanks God for You.Good Luck and we will wait for results
Wysłane z mojego E2303 przy użyciu Tapatalka
tonystark88 said:
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Click to expand...
Click to collapse
If you can force enable adb and upload the rom I'm sure that we can send you logcats to find the problems. Also, could you upload the new TWRP that is mentioned in the OP?
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
boylush said:
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
Click to expand...
Click to collapse
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
tonystark88 said:
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
Click to expand...
Click to collapse
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
It's the temp .config file generated when u build the kernel. I renamed it and used because differently from the asp defconfig is formatted well.
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
I see no problem here especially since Sony hasn't exactly released the kernel code. There is no reason to be so distrustful. Heck he hasn't even released the rom yet so what are you complaining about. Please don't take offense. He is just trying to further this community
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
Supports developers, do not lock their work
I don't understand this mentality of 'Let the dev work and do his thing' and saying that he should be given space to himself to work and build CM12 for The M4 Aqua. As it stands, you all don't know what Open Source Means. The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua. I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
I don't like these kinds of reasoning about me and about my work only because in two months other people aren't been able to boot nothing, also a recovery. This is the last time i will respond to you because this is a DEV topic, and here will be DEV things.
Furrydaus said:
The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua.
Click to expand...
Click to collapse
I repeat this thing again, all my sources are public. Just see the first page of this topic. And also, all sources are open on sonyxperiadev and are a intellectual property of Sony. All the LOCAL modifications are on my github page, in the commit area. Just click and see.
Furrydaus said:
I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
Click to expand...
Click to collapse
And i'm happy for the Sony XPERIA SP, this means people work together. In the case of Sony M4 Aqua i just saw topics that bumps out after i started to develop, also if only the recovery, for this device. No one sent me a message for say, "Tony let's work together".
Furrydaus said:
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Click to expand...
Click to collapse
I'm not stressed, i feel great thanks And again no one ROM violates the GPL license. Simply because there isn't yet on the site and will not be until will complete boot correctly. And about the request, i responded yet. I have to repeat that i used the same kernel published by sonyxperiadev site WITHOUT MODIFICATIONS ?
Furrydaus said:
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
Click to expand...
Click to collapse
Probably in the ROMS world this sentence is true. But i'm a graduated ICT Engeneer and i worked in past in Android. Maybe i know a little bit of devel things, and i say "a little bit" because i know i can do it, and i not let you and others to offend me without know who i am.
CONCLUSION
Without me, the unexperienced, this device today has a working recovery and i hope for ALL THIS COMMUNITY a working CM12.1 . And i repeat again this thing: THE SOURCES ARE PUBLIC ON MY GITHUB AND ON THE SONYXPERIADEV GITHUB. I'm not blocking the work of anyone and i will be happy if someone else will make the rom work better and efficiently than mine. I will learn where i failed from the other devs commits, like i always did.
I hope is more clear my point of view now to avoid future noisy discussions.
CyanogenMod 13 for the Sony Xperia XA Dual Sim
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the F3112 and the F3116
Code:
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
@Deepflex for his P9000 github repository used as base for sources.
@zacharias.maladroit for his CM13 guide for Z5 and who have heavily inspired me for this guide
-The Sonyxperiadev team for releasing their kernel sources to the public.
-The entire CyanogenMod team.
-All Xda contributors for their guides and HowTo.
-The Google searchbar
Known Issues
-Camera not working
-Video not working
-No Sim
-Screen not wake up after screen off.
-No sound
-"Security" settings not working
-"More... " settings not working
-NFC not working
-GPS (not tested)
-Full brightness
-And probably more...
Guides/Instructions
For now I will not explain how to flash because my Rom is in very beta stage and I need help for debugging,
it mean it's not user friendly and only skilled users will know how to flash it,
As soon as the rom will be stable I will update this part of the guide.
I will just say it's like any other CM Rom flashing.
Downloads
CyanogenMod Recovery https://mega.nz/#!EoJXyK6R!ORe1tBtn2LhkFsOIs0grhOo_jFDsYKT1wJKGGBJhBsA
ROM
Initial release: https://mega.nz/#!gx50yZZL!i1qL_Ab9_LubJCmuYefnazW4ddn_r5Z-a-8FXmKTsDg
Questions and bug reporting
The following questions will be ignored
- Inappropriate questions
- Requests for other devices
-Forced orders, EX. : "PLS FIX!!!!!!"
-ETA's
-Often repeated questions or requests usually by the same user
-Requests that are out of CM
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
Source Code can be obtained from:
https://github.com/CyanogenMod
https://github.com/rrvuhpg
Kernel Source code can be obtained from: http://developer.sonymobile.com/downloads/xperia-open-source-archives/
I gladly accept any developers that are willing to contribute to this project! Please PM @rrvuhpg if you are interested in joining this project!
You can join my XA/Ultra channel on Telegram for dev questions: telegram.me/rrvuhpg_XA
ROM OS Version: 6.0.1 Marshmallow
ROM Firmware Required: 33.2.B.3.81 Recommended
Based On: CyanogenMod
Version Information
Status: Initial release
cool !! nice work.. if u can do the same on F3111 please !
first time i get sony and i use stock firmware ..with other brands i use custom rom
Nice! I've been waiting for this!
I'm learning C and JAVA myself, but guess it would take a long time before I can actually develop something!
Until then, I count on you! Thanks!
ObtuseFox said:
Nice! I've been waiting for this!
I'm learning C and JAVA myself, but guess it would take a long time before I can actually develop something!
Until then, I count on you! Thanks!
Click to expand...
Click to collapse
You know porting roms have nothing to make with pure developpment. More with analyse of codes and importations of libraries, etc... You won't really code a whole page
I am so happy to see this here
My old LG D295 just died and i pull the trigger for XA F3111 and i hope everything is going well with the port
Stersound said:
I am so happy to see this here
My old LG D295 just died and i pull the trigger for XA F3111 and i hope everything is going well with the port
Click to expand...
Click to collapse
It's on the good way, I'm waiting for my new computer to continue, my actual take 11 hours to build :silly: As soon as the "ril" (telephony features) will work I will release an update, for now I can enter pin code but sim stay locked
All other features are working or unstable, only NFC is not working. For XA single sim you will have to wait a little more.
Cyanogen means losing Bluetooth aptX.
saintsimon said:
Cyanogen means losing Bluetooth aptX.
Click to expand...
Click to collapse
Sir i believe this is not correct
Stersound said:
Sir i believe this is not correct
Click to expand...
Click to collapse
Well: aptX means licence fees. Does Cyanogen pay them?
I need facts, no beliefs. Cyanogen is not known for aptX support.
Or is there a file like "libbt-aptX-ARM-x.x.x.so" in the /system/lib/ folder? If not, your belief is unsubstantiated.
Can we expect CM 14 ? instead?
are you going to build a rom like cm or aosp for the xa ultra?
sexxualization said:
are you going to build a rom like cm or aosp for the xa ultra?
Click to expand...
Click to collapse
Probably no, I don't have an unlocked Ultra to work on it. As long as we don't know why Ultra devices can brick when flashing with Flashtool it will stay with locked bootloader.
rrvuhpg said:
Probably no, I don't have an unlocked Ultra to work on it. As long as we don't know why Ultra devices can brick when flashing with Flashtool it will stay with locked bootloader.
Click to expand...
Click to collapse
well i own an unlocked xa ultra with twrp recovery to help you try the rom out
sexxualization said:
well i own an unlocked xa ultra with twrp recovery to help you try the rom out
Click to expand...
Click to collapse
Thank you for your help but I need the device in my hands for many reasons (dump, debugging, reverse engineering, ...).
As you know XA and Ultra are not intended to have custom roms and I have to make my own sources, it mean a lot of work. Ultra is not a simple copy/paste of the XA system
saintsimon said:
Well: aptX means licence fees. Does Cyanogen pay them?
I need facts, no beliefs. Cyanogen is not known for aptX support.
Or is there a file like "libbt-aptX-ARM-x.x.x.so" in the /system/lib/ folder? If not, your belief is unsubstantiated.
Click to expand...
Click to collapse
Apt-x is a feature supported in vanilla android already.
Then it's true you should have the loading library (which isn't all that secret btw) but for some reason, it's reported to work nevertheless on Xperia S.
Regardless, I don't see why you couldn't just include stock libbt-aptX-ARM-4.2.2.so in android_vendor/proprietary (or android_device/prebuilt, Idk)
EDIT: https://review.lineageos.org/#/c/158337
Is there any chance this ROM will work on the f3111?
jolpool said:
Is there any chance this ROM will work on the f3111?
Click to expand...
Click to collapse
I think this project is kind of dead already since were no activities happening.
Jhayzt said:
I think this project is kind of dead already since were no activities happening.
Click to expand...
Click to collapse
As you know CM is dead and Lineage OS just launched. Other thing, Nougat for XA and Ultra will come soon and I know that users will ask for Rom based on it. We can say CM13 project is dead but new Lineage OS project will come for XA
rrvuhpg said:
As you know CM is dead and Lineage OS just launched. Other thing, Nougat for XA and Ultra will come soon and I know that users will ask for Rom based on it. We can say CM13 project is dead but new Lineage OS project will come for XA
Click to expand...
Click to collapse
Really looking forward for lineage OS for XA.
Please update this rom asap. Really need your help, i hate this stock version. The touch screen is very annoying. I can't touch the edge of the screen. Please help us
I am a newbie to android development and want to clear out my some confusion about compiling ROM as I am compiling ROM for first time. Your assistance will be appreciated.
Q1. Well. I run the repo sync command and at last, after 100% fetching project done , I got an error as " error: .repo/repo/: contains uncommitted changes"
What does it means? why it occurs and how to fix it ?
Q2. What is local_manifest ? I am compiling for a unsupported device (Micromax Q370), so do I have to create a local manifest by myself ? If yes, then how ?
Q3. What is device tree ? How to make it ?
Hire to extract device specific codes from my device using adb ?
Q4.
Q5.
Q6. How to choose a target ? What target means ? Is it my device (Micromax Bolt Q370) ? or something else ?
Can someone explain these guides reffered in android.com ? =
" Choose which target to build with lunch. The exact configuration can be passed as an argument. For example, the following command:
$ lunch aosp_arm-eng
refers to a complete build for the emulator, with all debugging enabled.
If run with no arguments lunch will prompt you to choose a target from the menu.
(When I type lunch, terminal prompt me to install" sudo apt install python-lunch") "
I am compiling CM13 for my device Micromax Q370, its not an emulator, so what I have to type instead of $ lunch aosp_arm-eng ? What are BUILDTYPES anyway ?
And what lunch does ?
Q7. What will happen if I type
$ make -j4
Will it start compiling the ROM ?
Well. These are my confusion. I know these are very nooby question but I am new to android development without any prior programming language knowledge and want to learn it. I hope someone will help me out. Thank you for reading my thread. Waiting for your help. Have a good day.
Q.4 and Q.5 are removed as I understood what those things are.
@sudharshankakoty I'm pretty much sure that you've MTK chipset based device. I tried to search online but the chip isn't mentioned anywhere. Download CPU Z nd post the screenshots here from all of the tabs. I'm afraid that if it's MTK based then you cannot do any further development except to port the roms. Only if there are roms for that chipset.
Has.007 said:
@sudharshankakoty I'm pretty much sure that you've MTK chipset based device. I tried to search online but the chip isn't mentioned anywhere. Download CPU Z nd post the screenshots here from all of the tabs. I'm afraid that if it's MTK based then you cannot do any further development except to port the roms. Only if there are roms for that chipset.
Click to expand...
Click to collapse
Nope, I am at Spreadtrum Chipset. My device details are here https://www.dropbox.com/s/pwpgo7muawmekwf/Device Details.zip?dl=0
Well, I got a lollipop rom of same chipset and android version, and I tried replacing the system/lib folder from base to port rom with setting the correct mount points of my device in updater-script .
But when I tried to flash, it says error executing updater binary in zip (TWRP)
Sudarshankakoty said:
Nope, I am at Spreadtrum Chipset. My device details are here https://www.dropbox.com/s/pwpgo7muawmekwf/Device Details.zip?dl=0
Well, I got a lollipop rom of same chipset and android version, and I tried replacing the system/lib folder from base to port rom with setting the correct mount points of my device in updater-script .
But when I tried to flash, it says error executing updater binary in zip (TWRP)
Click to expand...
Click to collapse
Okay so I checked the details. The problem is that you can't build the ROMs for this device. As far as I know Spreadtrum doesn't release the souce code. What status error did you get? 7? Give me the link of TWRP built for your device nd also the ROM you're trying to port.
Has.007 said:
Okay so I checked the details. The problem is that you can't build the ROMs for this device. As far as I know Spreadtrum doesn't release the souce code. What status error did you get? 7? Give me the link of TWRP built for your device nd also the ROM you're trying to port.
Click to expand...
Click to collapse
TWRP for my device : https://drive.google.com/file/d/0B377TLFOgWdsTExNTFIza1BCckE/view?usp=docslist_api
ROM trying to port : https://drive.google.com/file/d/0B6a7A5E8IzscdjNSRzRBSWZLZzg/view?usp=drivesdk
Sudarshankakoty said:
TWRP for my device : https://drive.google.com/file/d/0B377TLFOgWdsTExNTFIza1BCckE/view?usp=docslist_api
ROM trying to port : https://drive.google.com/file/d/0B6a7A5E8IzscdjNSRzRBSWZLZzg/view?usp=drivesdk
Click to expand...
Click to collapse
Error while flashing ROM : when I tried to flash, it says error executing updater binary in zip (TWRP)
Mount points of my device attached here.
@sudharshankakoty Sorry for replying, missed your notification. I want the source pages for this TWRP nd the ROM so I could see the details. Here is a guide to build device tree I haven't seen this video but it might help you:
https://www.youtube.com/watch?v=Uw_caMHZRC4
About the error, probably it is because of the mount points or the asserts.
Has.007 said:
@sudharshankakoty Sorry for replying, missed your notification. I want the source pages for this TWRP nd the ROM so I could see the details. Here is a guide to build device tree I haven't seen this video but it might help you:
About the error, probably it is because of the mount points or the asserts.
Click to expand...
Click to collapse
Well, somehow, I could managed to extract the device tree from boot.img file. But the problem is I am unable to make the recovery image, getting an make error... ********************************************************** Kernel source found, but no configuration was defined Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file *********************************
Sudarshankakoty said:
Well, somehow, I could managed to extract the device tree from boot.img file. But the problem is I am unable to make the recovery image, getting an make error... ********************************************************** Kernel source found, but no configuration was defined Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file *********************************
Click to expand...
Click to collapse
You can try to get help from @doesntexits He developed for Speadtrum device so he might be able to help you.
Has.007 said:
You can try to get help from @doesntexits He developed for Speadtrum device so he might be able to help you.
Click to expand...
Click to collapse
None of the CyanogenMod he developed is for sc7731 chipset
Sudarshankakoty said:
None of the CyanogenMod he developed is for sc7731 chipset
Click to expand...
Click to collapse
That's right but it is for sc device so it would be easy for him to at least have a kickstart. You even might be able to build tree by using his sources. Obviously it needs a lot of experience.
Has.007 said:
That's right but it is for sc device so it would be easy for him to at least have a kickstart. You even might be able to build tree by using his sources. Obviously it needs a lot of experience.
Click to expand...
Click to collapse
Ya. That's right, well I own my device tree, I need kernel sources actually. OK, let's contact him and will ask for some assistance. ☺
Has.007 said:
That's right but it is for sc device so it would be easy for him to at least have a kickstart. You even might be able to build tree by using his sources. Obviously it needs a lot of experience.
Click to expand...
Click to collapse
I am currently running a custom Android 5.1 ROM with almost stable state, by porting myself. It includes many features including CM Theme Chooser/Engine. Only bug is Auto-Rotation is not working. I am using stock boot.img so I need to port the kernel for this. Occasionally after porting the kernel, and flashing through TWRP, Touch was not working so I went to stock boot.img and running till now like this.
I want to learn rather than getting things done. ,:silly:
[Black is my happy colour]
Sailfish OS 4.4.0.72 for Sony Xperia 1 and 5
These release notes cover Sailfish OS 4.4.0.72 for the following devices:
Sony Xperia 1 (J8110, J9110)
Sony Xperia 5 (J8210, J9210)
Intro
This port has been updated last to the latest release of Sailfish OS 4.4.0.72 in addition to that several adaptation bugs discovered in the testing of the first release have been fixed.
Also several documentation updates or buildinfrastructure changes have been made.
Updates to these project components are now tracking in the main bug tracking repository SailfishOS-SonyXperia/bugs/releases.
The highlights in this release are:
[prjconf] Fix pattern dependencies. Fixes SailfishOS-SonyXperia/bugs#55, fixes SailfishOS-SonyXperia/bugs#59
[patterns] Require ngfd >= 1.4 instead of ngfd-plugin-native-vibrator. Fixes SailfishOS-SonyXperia/bugs#69
[configs] Keep dual sim configs on J9210/Xperia 5, remove on J8110. Fixes SailfishOS-SonyXperia/bugs#51
[kickstart] Fix @DEVICES@ name for Xperia 5/J9210 in flash-on-windows. Resolves SailfishOS-SonyXperia/bugs#50
Thanks to all who have provided testing, reported bugs or have contributed otherwise.
FunctionalityThe devices have the same functionality level as the Xperia 10 II port made by Jolla,
except in areas such as VoLTE where public packages are missing or in relation to Sailfish X features which are (currently) unavailable.
Known issues
SailfishOS-SonyXperia/bugs#33
Because of a missing package inside the adaptation-common repository Windows binaries for flashing are missing inside the zip archive. To workaround that issue have added another zip file that includes these files as "droid-flashingtools.zip" to this release.
SailfishOS-SonyXperia/bugs#37
The launcher icons on the Xperia 1 are to small because there's no bigger graphics-theme size than 2.0.
ProjectThe Github project that contains this port and all other ports from this project can be found here:
Sailfish OS Community ports for Sony Xperia devices
Sailfish OS comunity ports for Sony Xperia devices - Sailfish OS Community ports for Sony Xperia devices
github.com
Project UpdatesAs explained above there’s now a separate changelog for project wide updates which can be found down below:
Release Project Update 02-12-2022 · SailfishOS-SonyXperia/bugs
Intro The changelog describes all the project wide changes, such as for example documentation updates or build infrastructure changes. In case an adaptation issue arose from wrong build configurati...
github.com
The changelog file about the project updates can be found down below:
project_changelog.md
About
The goal of this project is to port additional Sony devices on top of Jolla's existing adaptations while staying as close as possible to the existing ports and contributing back to the upstream where possible.
Most of the changes from Jolla ports are adopted in both directions since the issues that one port has usually apply to the sister device of the same generation (e.g. Xperia 10 II -> Xperia 1/5).
This is the reason why changes from Jolla’s port end up in the changelog for these port,
in many cases because they also affect the specific port but not always.
Where possible changes that were done for this port go back to the _Mer-Hybris_ repositories such as the kernel or droid repositories.
The project is open for anyone that wishes to port additional Sony devices to Sailfish OS. Feel free to suggest new features, provide bug reports or to contribute.
SourcesAny sources specific to this port can be found inside the project linked above. The device repositories are named after the devices board name for example in this case kumano.
All our sources are included inside the project linked above.
All other sources are taken unpatched from upstream which is either Sony-AOSP or SailfishOS/mer-hybris.
If changes are needed inside upstream repositories these are submitted to the upstream repositories.
This GPL includes components such as the kernel or libhybris.
On pressure of XDA I add the direct link to the kernel repository, however the exact ref used during build
can be found inside the droid-hal repository, which in the case of the Xperia 1 for example, droid-hal-kumano.
Sources for this board
https://github.com/mer-hybris/android_kernel_sony_msm/tree/hybris-sony-aosp/LA.UM.7.1.r1
https://github.com/SailfishOS-SonyXperia/droid-hal-sony-kumano
Report bugs
Bugs can be opened in the bug repository linked below:
GitHub - SailfishOS-SonyXperia/bugs: Empty repository that is used as a bugtracker
Empty repository that is used as a bugtracker. Contribute to SailfishOS-SonyXperia/bugs development by creating an account on GitHub.
github.com
Download
Release 4.4.0.72+git1 · SailfishOS-SonyXperia/droid-hal-version-sony-kumano
Sailfish OS 4.4.0.72 for Sony Xperia 1 and 5 These release notes cover Sailfish OS 4.4.0.72 for the following devices: Sony Xperia 1 (J8110, J9110) Sony Xperia 5 (J8210, J9210) Intro This port ha...
github.com
Flashing
To install Sailfish OS on your device please follow the install instructs in the flashing-readme.txt file included in the archive or read the offical flashing instructions for either the Xperia 10 II or Xperia 10 III:
Sailfish X Installation Instructions - Jolla
jolla.com
Just make sure to download the software binaries for your device instead of the ones mentioned in the instructions:
Software binaries for AOSP Android 10.0 – Kernel 4.14 – Kumano (latest) - Sony Developer World
developer.sony.com
Changeloghttps://github.com/SailfishOS-SonyX.../releases/download/4.4.0.72+git1/Changelog.md
Great job, thanks for making the port! Does it have Android app support? If it does I'll definitely give it a try, I saw on the SailfishOS official website that only the paid version can run Android apps...
Edit: I see why now, because of the very very long term support that you get, it's like 7 years of updates for a bit of money, that's pretty good.
just try to use on my device.
its first time for me using Sailfish OS.
but.
when i turn off the phone, and try to turn it on, it asks for the security code, after i enter the security code, it just loading in quite a long time,
then, simcard and wifi didnt works.
I can confirm, that neither data connection nor WiFi works.
Without any data such as logs I can't help you. Please create a bug in the bugtracker.
Please also make sure that you flash the version that matches your device.
Please follow this article to fetch logs:
https://jolla.zendesk.com/hc/en-us/articles/360013910599-Collecting-basic-logs-from-a-Sailfish-device
You can also try to flash the new images, I will add tomorrow.
I updated the release archives today:
Package ngfd as `CUSTOM_’ FFMemless vibration effects require newer version than packaged in SailfishOS 4.4.0.
Fix issue in ssu-vendor-data package that made the address of the adaptation repository invalid. [BUG] address of adaptation repo is invalid #49
I've installed Sailfish and its working fine. But i dont find access to install android apps. Is there a way to install APKs?
Thaodan said:
Without any data such as logs I can't help you. Please create a bug in the bugtracker.
Please also make sure that you flash the version that matches your device.
Please follow this article to fetch logs.
You can also try to flash the new images, I will add tomorrow.
Click to expand...
Click to collapse
First of all, many thanks for your reply - very appreciated!
Yes, I've downloaded and flashed the appropriate version (J9210, Xperia 5, DualSim). As I've bought this device as a new one about 2 years ago, I've used it that time, and it worked. The bootloader was already opened; it was rooted, because of some rooting apps.
Therefore, it was not necessary to check, if data connection, wifi, gps, camera and so on works, because it worked.
I flashed sailfish os (with the latest software binaries, Android 10, Kernel 4.14 - as in the op described [the extracted .img I've placed in the same folder as your firmware, of course]) via Linux Mint.
The device boots up flawlessly, the screen is responding without any problem, and also the intro worked.
But I can't activate wifi. I can push the button, and it responses, but it don't activates wifi. Also, my sim card won't be recognized, therefore there's no chance to enter the sim pin.
So there's a few questions:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Or is it necessary to buy a Yolla licence? No problem, I would pay for it, but the Xperia 5 isn't listed yet on your homepage...
Thanks in advance for your kind reply!
P.S.: Yes, I've tried it 4 times (went back to the latest Sony fw), and the last time I've flashed the latest Sony fw even on slot a and b before flashing Sailfish OS again (the latest [1.06] for the Xperia 5 Dual Sim variant), but unfortunately every time with the aforementioned result...
Klaus N. said:
First of all, many thanks for your reply - very appreciated!
Yes, I've downloaded and flashed the appropriate version (J9210, Xperia 5, DualSim). As I've bought this device as a new one about 2 years ago, I've used it that time, and it worked. The bootloader was already opened; it was rooted, because of some rooting apps.
Click to expand...
Click to collapse
Did you download the version for the J9210? Please check the file name of the archive.
Klaus N. said:
Therefore, it was not necessary to check, if data connection, wifi, gps, camera and so on works, because it worked.
I flashed sailfish os (with the latest software binaries, Android 10, Kernel 4.14 - as in the op described [the extracted .img I've placed in the same folder as your firmware, of course]) via Linux Mint.
Click to expand...
Click to collapse
Extracted the .img? You should extract the .zip archive, then run ./flash.sh to flash Sailfish OS to the device.
Klaus N. said:
The device boots up flawlessly, the screen is responding without any problem, and also the intro worked.
But I can't activate wifi. I can push the button, and it responses, but it don't activates wifi. Also, my sim card won't be recognized, therefore there's no chance to enter the sim pin.
So there's a few questions:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Click to expand...
Click to collapse
Sorry I forgot to post the link, please look again.
Klaus N. said:
Or is it necessary to buy a Yolla licence? No problem, I would pay for it, but the Xperia 5 isn't listed yet on your homepage...
Thanks in advance for your kind reply!
Click to expand...
Click to collapse
Not you don't need to buy a license, the device isn't support by Sailfish X (it is not available so far for community ports).
Klaus N. said:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Click to expand...
Click to collapse
@Thaodan
Thanks for providing the link!
Here's the basic-logs-2022-09-24-1031.tar from my device.
Thank's in advance!
In addition, the answers (sorry, almost forgot) to your questions:
Yes, I've downloaded the Sailfish_OS-Sailfish-SonyXperia-4.4.0.68-j9210-1.0.0.6.zip and the software binaries provided in your op.
I've only extracted the zip, but not the .img, ofc. Then I put the Software Binaries.img into the same folder as the firmware and run ./flash.sh
@Thaodan
As there's one month left in the meanwhile, I only wanted to ask, if there's some progress regarding the J9210!? Is this the wanted logs, do you need some other, or has this project stopped?
Klaus N. said:
@Thaodan
As there's one month left in the meanwhile, I only wanted to ask, if there's some progress regarding the J9210!? Is this the wanted logs, do you need some other, or has this project stopped?
Click to expand...
Click to collapse
I checked and didn't found anything obvious in your logs. I didn't had time to check your device further before my vacation.
I didn't mention it here but please open a bug report, a forum or specificly this forum thread isn't the best place to talk about issues.
My J9210 runs fine.
Thaodan said:
I checked and didn't found anything obvious in your logs. I didn't had time to check your device further before my vacation.
I didn't mention it here but please open a bug report, a forum or specificly this forum thread isn't the best place to talk about issues.
My J9210 runs fine.
Click to expand...
Click to collapse
First of all, thank you very much for your reply!
Ok, so I'll give it one more try: I will set it up with the latest Sony stock fw, put my sim-card into it and test/use everything - as described...
I'll report back!
I just checked my test phone everything works so far.
Please check if it doesn't work that you flash the latest stock version that is close to this one: 55.0.A.11.25.
Thaodan said:
I just checked my test phone everything works so far.
Please check if it doesn't work that you flash the latest stock version that is close to this one: 55.0.A.11.25.
Click to expand...
Click to collapse
The Xperia 5 firmware I've flashed is the J9210_Customized EU_55.2.A.4.332-R13C one. I'll flash it again and give SF OS another try. Perhaps it failed because my Xperia 5 was rooted and debloated; I also had AFWall+, the Xposed framework and XPrivacyLUA installed. I don't know...
Right after flashing the aforementioned fw I will test GPS, mobile data, wifi and so on, and will keep everything turned on before flashing SF OS - maybe it will work?
@Thaodan
One further question: Have you installed Sailfish OS via Windows or Linux? I did it with Linux Mint...
Klaus N. said:
The Xperia 5 firmware I've flashed is the J9210_Customized EU_55.2.A.4.332-R13C one. I'll flash it again and give SF OS another try. Perhaps it failed because my Xperia 5 was rooted and debloated; I also had AFWall+, the Xposed framework and XPrivacyLUA installed. I don't know...
Right after flashing the aforementioned fw I will test GPS, mobile data, wifi and so on, and will keep everything turned on before flashing SF OS - maybe it will work?
Click to expand...
Click to collapse
have you tried?
I want to try it again, but it's a shame if it's without a simcard or wifi.
Well, now I've flashed the J9210_Customized EU_55.2.A.4.332-R13C fw, played around with data connection, wifi, bluetooth, camera, and everything worked.
Then I tried to install SF OS via Windows 10 64 bit, but there must be a mistake inside the script. I definitely own a Xperia 5 dual-sim (J9210)!!!!!!! But: Please have a look into the attached pic...
Then I tried to flash SF OS running Linux Mint (latest stable release); the flash ran through without any error, but again: No WiFi, no data connection.
I'm about to give up!!!
One note:
I've flashed so many devices, mostly LineageOS, but also Ubuntu Touch, and never had any problem like that - unfortunately, it's annoying...
Klaus N. said:
Well, now I've flashed the J9210_Customized EU_55.2.A.4.332-R13C fw, played around with data connection, wifi, bluetooth, camera, and everything worked.
Then I tried to install SF OS via Windows 10 64 bit, but there must be a mistake inside the script. I definitely own a Xperia 5 dual-sim (J9210)!!!!!!! But: Please have a look into the attached pic...
Then I tried to flash SF OS running Linux Mint (latest stable release); the flash ran through without any error, but again: No WiFi, no data connection.
I'm about to give up!!!
One note:
I've flashed so many devices, mostly LineageOS, but also Ubuntu Touch, and never had any problem like that - unfortunately, it's annoying...
Click to expand...
Click to collapse
Isually use Linux to flash but also should have checked the Windows flash script.
Please edit the batch script you called and replace j9210 with J9210.
I just fixed the issue but for now just change the flash script for Windows:
[BUG] Device is invalid in windows flashing script for Xperia 5/j9210 · Issue #50 · SailfishOS-SonyXperia/bugs
The @[email protected] in the kickstart script is written as j9210 but it should be J9210.
github.com
Thaodan said:
Isually use Linux to flash but also should have checked the Windows flash script.
Please edit the batch script you called and replace j9210 with J9210.
I just fixed the issue but for now just change the flash script for Windows:
[BUG] Device is invalid in windows flashing script for Xperia 5/j9210 · Issue #50 · SailfishOS-SonyXperia/bugs
The @[email protected] in the kickstart script is written as j9210 but it should be J9210.
github.com
Click to expand...
Click to collapse
Thank you very much for the response - and your efforts, ofc!
Finally: It works
I had not to flash the latest firmware (doesn't work), but a rollback to the J9210_Customized EU_1320-0801_55.1.A.9.52_R10B fw before flashing Sailfish OS did the trick!
We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 | Developer World
developer.sony.com
Many thanks! I was wondering if you could help me with the following two issues:
Can't find binaries SW_binaries_for_Xperia*.zip (for Xperia 1 III Android 13) for step 7 "Flash vendor image to your device".
(Never mind, I read you said elsewhere to use the Generic Android 12 Vendor Image.)
Also DSU loader crashes when trying to load Android 13 experimental or any other GSI through "Developer options".
KillSkill said:
Many thanks! I was wondering if you could help me with the following two issues:
Can't find binaries SW_binaries_for_Xperia*.zip (for Xperia 1 III Android 13) for step 7 "Flash vendor image to your device".
(Never mind, I read you said elsewhere to use the Generic Android 12 Vendor Image.)
Also DSU loader crashes when trying to load Android 13 experimental or any other GSI through "Developer options".
Click to expand...
Click to collapse
At this stage the Android 13 release is tested only on a full build according to the build intructions
jerpelea said:
At this stage the Android 13 release is tested only on a full build according to the build intructions
Click to expand...
Click to collapse
And everything actually works? That has not been the case in the past with SODP code.
thatguy222 said:
And everything actually works? That has not been the case in the past with SODP code.
Click to expand...
Click to collapse
It depends on what the expectations are. The basic functionality is already working
jerpelea said:
It depends on what the expectations are. The basic functionality is already working
Click to expand...
Click to collapse
Define basic functionality...like texting, data and phone calls???
what is the use of all these instructions if there are no developers who have made and supported at least a normal firmware based on android 12