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!
Related
Dear All
Ever heard or read of/about PDroid? Ever thought about securing your data, addresses, locations and SIM information from being (mis-) used by downloaded apps, games and other things?
Time to read about...
PDroid is a ROM-hooked privacy protection of your personal information & data. It let's you set per-app access rights to your private informations. No more hidden address ore phone-book misuse or GPS-based advertisement "enhancement".
Read more about PDroid/OpenPDroid: http://forum.xda-developers.com/showthread.php?t=2098156
What is this thread about?
This shall be a pure SERVICE thread to all users and friends of Android that care about their privacy.
We (users & friends of xda-developers, PDroid & AutoPatcher) help you patching your ROM so that you can use your apps and games under privacy protection.
Patching these ROMs provides some hurdles and hooks - some of us are very experienced and built & installed an environment to enable "simple patching". Many users stand back from this effort and have few experience with command-based or GUI-based patching - these are the addressees that we want to enable to have ALSO privacy protection on their tablets and smartphones.
Especially when you're not a very frequent "ROM-hopper"
What IS this service?
You drop us a link & we patch & upload this patch - that's it.
Please grant us some time, the response time depends on the supporters - and they all spend their free time for this.
(Please thank the helpers and providers by hitting the Thanks button!) ... maybe also rating the thread?
How to USE the service?
You install your ROM and post us the download link. You'll get back an upload with the patch. Usually you can simply flash it to your device, you should not have any problem, installing it "over" your installation. Even no data loss.
To set the rights for each app and get a warning if rights are changed, install "PDroid Manager" from App Store and launch it.
Nevertheless - make sure to have a backup
- of your (unpatched) ROM install
- of your data & installation
before your first trial.
Further Information:
OpenPDroid / PDroid information: http://forum.xda-developers.com/showthread.php?t=2098156
PDroid Manager - the access rights managing software: https://play.google.com/store/apps/details?id=net.digitalfeed.pdroidalternative
AutoPatcher - the tool if you also want to start patching...: http://forum.xda-developers.com/showthread.php?t=1719408
We'll elaborate this thread and post more and more and add links and further information - subscribe it to get familiar with PDroid!
One last notice: these patches do NOT induct any backdoor, trojan nor any other virus ar any advertisement to your device - rather enable you to set rights to achieve the opposite.
Special thanks to all contributors here, to the PDroid and OpenPDroid Team and especially to mateorod and his AutoPatcher's team.
With kind regards from Switzerland - Chris
Please thank the helpers and providers of patches by hitting the Thanks button!
How to install / proceed with my patch?
Flashing ROMs or ROM updates is unfortunately quite device-dependent.
Please make sure you have a copy of your flashed (unpatched) ROM to restore
Please make sure you backed up all of your data
A GENERIC guidance could be the following steps: How to update your installation to the PDroid-enabled one:
Download [yourROM] (unpatched version)
Download the attached patch-update from the appropriate post - the answer of one of the "helpers" (hit THANKS! )
Put both on your SD-Card
Enter Recovery of your device
(If not yet installed) Install (ZIP from SD-Card) the full fletched non-patched [yourROM] (usually no need to re-boot after that, simply go on with...)
Make sure you installed the appropriate GApps
Install (ZIP from SD-Card) the patched update from this thread's answer post "over it"
IF you changed a major Android version (e.g. 4.2.2 -> 4.3), perform a full wipe
Reboot the device
Go to Play Store and download "PDroid Manager" and start it to configure your privacy settings per every single App - You're done.
After you set up the permissions, you don't need the Android's (very limited; since 4.2.2) privacy protection anymore - deactivate it
Greetz - Chris
#3 - reserved
Req: Patch for cm-10.2-20130918-NIGHTLY-p3100.zip
EXAMPLE of a Request:
Hi
can you patch CM 10.2. Nightly as per 2013-09-18 for P3100 device for me?
Device details:
Manufacturer: Samsung
Device: GT 2 7.0 P3100
ROM's download link: http://www.get.cm/get/jenkins/41935/cm-10.2-20130918-NIGHTLY-p3100.zip
Christoph21x said:
EXAMPLE of a Request:
Hi
can you patch CM 10.2. Nightly as per 2013-09-18 for P3100 device for me?
Device details:
Manufacturer: Samsung
Device: GT 2 7.0 P3100
ROM's download link: http://www.get.cm/get/jenkins/41935/cm-10.2-20130918-NIGHTLY-p3100.zip
Click to expand...
Click to collapse
EXAMPLE Answer:
Hi pls find attached the patch
Nice idea, hopefully it'll get approved and added to the development threads op.
I might join in by writing a short explanation about VM's and how to use the patcher there (since I was doing it this way until a few weeks back, where I got (nearly) rid of win)
Being on Linux actually makes the whole thing a hell of a lot easier.
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
Here it is!
IRKONIK said:
Nice idea, hopefully it'll get approved and added to the development threads op.
I might join in by writing a short explanation about VM's and how to use the patcher there (since I was doing it this way until a few weeks back, where I got (nearly) rid of win)
Being on Linux actually makes the whole thing a hell of a lot easier.
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
Click to expand...
Click to collapse
THANKS, IRKONIK!
You know, PDroid is a great service protecting us, the work of the developers is great - including mateorod and others who're working all day and night, as it seems.
And if we can, we should try to make this protection available also (and especially!?) to all non- or semi-enthousiastic users that do not neededly flash ROMs frequently..
Thanks for your support - highly appreciated!
Greetz - Chris
GT-N7000, Krueger CM10.2
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
ralphm2004 said:
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
Click to expand...
Click to collapse
Hi ralph
You posted in the wrong thread - patch DEVELOPMENT is under http://forum.xda-developers.com/showthread.php?t=1719408 who add support for non-patchable ROMs, we just build it for users...
greetz - Chris
Christoph21x said:
Hi ralph
You posted in the wrong thread - patch DEVELOPMENT is under http://forum.xda-developers.com/showthread.php?t=1719408 who add support for non-patchable ROMs, we just build it for users...
greetz - Chris
Click to expand...
Click to collapse
Hi Chris,
thanks for the information, i misunderstood the sense of this thread.
As a junior member i can't post in development-threads. Can someone please post it there?
I posted a link, so you'll be fine (hopefully)
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
ralphm2004 said:
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
Click to expand...
Click to collapse
Thanks for the thread, Christophe!
I can add support, but I need the rom's source code. You will have to ask the dev for a link to their github page. But then I can add support.
mateorod said:
Thanks for the thread, Christophe!
I can add support, but I need the rom's source code. You will have to ask the dev for a link to their github page. But then I can add support.
Click to expand...
Click to collapse
hi mateorod,
i cant post to that thread to. there doesn't seem to be a link to the right source.
but with v3.1.78 the patch has worked.
i try to contact bangsti and ask for the source, maybe it is helpful for the future.
ralphm2004
--- edit ---
got the information from bangsti:
Is the CM10.2 Source and crdroid Source.
github.com/cristianomatos
github.com/CyanogenMod
Krueger is a Mix from this Sourcen.
Well, I said it, so here it is (yeah, I deliver )
How to use the Auto-Patcher on Linux (debian based (!!)) in a virtual machine.
This "tutorial" does not take you by your hand. No, I DEMAND :silly: that you do stuff by yourself. It helps you! (Trust me. The easy way is not always the best)
First of all: You need a virtual machine with your favorite distro. (I like Mint Cinnamon)
How this step works? Well, google/youtube it. There is so much info about it, there is no need in writing another tutorial. Especially when other people have done it waaaay better
So, you have linux running. What now?
Second step: Getting all the stuff the patcher relies on.
Code:
sudo apt-get update
Code:
sudo apt-get install git git-core cpio patch unzip tar openjdk-7-jdk openjdk-7-jre
Third step: Getting all the files from github and build the patcher
Code:
git clone https://github.com/mateor/auto-patcher
Code:
cd auto-patcher
Code:
./batch.sh
Fourth step: Copy the rom you want to have patched into the auto-patcher folder.
Code:
./auto_patcher rom.zip
!! With this method, the patcher will use the rom detector and will build OpenPDroid patches. If you DO NOT want them, read the first page of the dev-thread. !!
Fifth step: Getting the files "out of" the VM.
- Easy way: Upload it into the/your cloud.
- Nearly as easy way: Use some filehost. (Since the files are about 6MB big, it's not even a hassle). Fast filehost: zippyshare
When your files finished the uploading, just use the link to the file in a qr-code generator, scan it with your device and download it. Easy!
Sixth step: BEFORE you flash the file, check the md5sum (in the VM and on your device!) how-to
If they match, you are good to go. Don't forget to make a nandroid backup! It's not needed, but hey, better safe than sorry!
I hope this helps If something is missing, tell me!
Cheers! :highfive:
PS: Due to lack of time, this "tutorial" is as short as possible and might lack a few explanations. (Hopefully not steps)
PPS: The only "tip" I have: use the tab-key for auto-complete So instead of writing "auto-patcher" just type "au" and then press tab. Saves you lots of time.
Edit1: Props to Mateorod and everybody over at the dev thread!
PDroid Patches for Samsung Galaxy Tab, HTC Desire & Desire S
Dear All
please find below some already PDroid-patched ROM links
Samsung Galaxy Tab 2 7.0 P3100, P3110 & P3113 (JB 4.3 Nightly & JB 4.2.2 CM 10.1.3 RELEASE)
[PDROID][GT-P31XX][2013-09-21][JB][4.3/4.2.2]PDroid: CM 10.2 Nightly & CM10.1.3 Rel. - see http://forum.xda-developers.com/showthread.php?t=2357514
HTC Desire
[ROM][Sept03][CM10.1] Chromium ROM | Build 10 | bravo - see http://forum.xda-developers.com/showthread.php?p=45441296#post45441296
[ROM/4.2.2] [June 03 2013] VJ CM10.1 | Jelly Bean 4.2.2 - v6.3 Stock/Sense/Data++ - see http://forum.xda-developers.com/showthread.php?p=43710438#post43710438
HTC Desire S
[ROM][08 AUG 13][4.2.2][UNOFFICIAL] CyanogenMod 10.1 - see http://forum.xda-developers.com/showthread.php?p=45441957#post45441957
With kind regards - Chris
http://pio-masaki.com/?dir=DroidDNA/Carbon
I'm in need of the 2nd from the bottom
9/22 for CDMA.
Awesome
Æaa°\,,/
takota6 said:
http://pio-masaki.com/?dir=DroidDNA/Carbon
I'm in need of the 2nd from the bottom
9/22 for CDMA.
Awesome
Æaa°\,,/
Click to expand...
Click to collapse
Since you did not specify which patch you want, you get OpenPDroid. All zip's are zipped with md5sum-files and the patch log.
Download link
Yeah I know, MEGA is pretty ****ty (down- and upstreams are crap) BUT it's more stable than other services.
Cheers!
PS: Please report back, if it works, and if it does, hit the thanks button, so a) I know and b) the thread doesn't get spammed. If something does not work as expected, please post a logcat in the dev thread, so it can get fixed.
Thank you
Well it didn't work, not with your doing but rather the Dev that built didn't put some vendor tree and so everyone is not able to boot that build.. I'll post back when I'm sure there a good build up.. Thanks
Æaa°\,,/
I'm back.. Heres a stable crAosp/ Cyanogen open pdroid please
http://forum.xda-developers.com/showthread.php?t=2417275
Direct Iink
http://www.mediafire.com/?6hblh4leblfc0lh
Thanks
Æaa°\,,/
Here's your patch takota6
takota6 said:
I'm back.. Heres a stable crAosp/ Cyanogen open pdroid please
http://forum.xda-developers.com/showthread.php?t=2417275
Direct Iink
http://www.mediafire.com/?6hblh4leblfc0lh
Thanks
Æaa°\,,/
Click to expand...
Click to collapse
Hi takota6!
Thanks for this clarification.
Please find attached the update file (patch) you need.
To restore to original (if you want to) you may use the attached "restore" file.
Kind regards from Switzerland - Chris
Introduction:So I see you have found my Android M Preview ROM thread. So... You all might of seen this. It's Sony announcing that it's AOSP open line of Xperia devices can now build Android M and is showing devs how to build it. Apparently things aren't exactly that way. Google created under it's source code, an alpha branch for the upcoming Android M, what that branch contains is mostly Android Lollipop code and some Android M stuff. This branch will evolve to become Android M, but at it's current state, the ROM is in between Android lollipop and M (kind of a weird mix of a sort that's why the build number is 5.1.51 and the easter egg is the one of lollipop). I will however provide weekly (hopefully) builds of Android M as it becomes more M than L. Keep in mind that the current release of the ROM (as of 25-6-2015) does not contain the new API's (for devs that are interested). You can see Sony's official explanation here. If you are still interested though in checking out the current state of Android M be my guest though keep in mind that in it's current state it is FAR from a daily driver (modem and camera are the most major of bugs currently) and most if not all of the cool features on Android M developer preview for the Nexus line probably are not currently included (as on 25-6-15).
Warning
This works only on UNLOCKED BOOTLOADERS. Keep in mind that the ROM was built for the D6603 I don't know if it will work with any other variant of the Z3. In addition flashing this might erase recovery on some devices. Also I take no responsibility of whatever may happen by using this ROM.
Downloads (please read the Introduction if you haven't, its important )Kernel
System
Userdata
Installation:1. Backup EVERYTHING (Your SD card included. This ROM has proven to be unpredictable as of storage on some handsets).
2. Download the Kernel, System and Userdata images
3. Get yourself a working ADB/Fastboot installation (more on that on the kernel page)
4. Flash the kernel as described on it's page (Steps 1-7)
5. While still in fastboot mode enter these commands in the command prompt:
Code:
fastboot flash system (directory of system image)
fastboot flash userdata (direcotry of userdata image)
6. Reboot your device and wait for it to start up
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
Erases all storage (internal and external) on some handsets
Screenshots:
Here you go.
Credits:
The rest of team Pear Crew
akateha
My Family & Friends
Sony and it's AOSP project
XDA
Google
Changelog:
----- Build I -----
Initial release.
Synced the latest android-m-preview branch
Most Android M features completely missing, ROM is like a hybrid of Lollipop&M
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
I can't believe what you just posted
Hahaha @Griffiths_Anna why so?
@CedArctic
it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
@Gustavo RD78
Actually I haven't, even Sony states that Camera & Modem are guaranteed broken. Even if the modem was fixed (which I believe it will in the next few weeks) the ROM still needs a lot of work for all the other bugs. Although about the baseband, I think M requires a special version of the baseband because even when you flash the official M preview over the Nexus 5, you have to flash a new baseband that is compatible with Android M. I am currently away from my Z3 but if someone tries it out and confirms it working I would gladly add it to the main thread.
Wow, that was fast, need i say more??
@corpsegrinder62 Actually, considering the announcement date it is fast. I dualbooted my PC with linux just 36 hours ago, downloaded the sources and compiled... XD
Gustavo RD78 said:
@CedArctic
it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
Click to expand...
Click to collapse
Some modem components are stored on /system and not included for legal reasons in Sony's AOSP binary releases. https://github.com/SuperBenevolent/aosp-vendor-qcom-proprietary
At least with L-MR1, the ONLY things missing for modem to work are the blobs above. Dunno about M, I'm not bothering to mess with it until official M release.
Woaw, nice to see android m being worked on even though it's in its early stages.
Is that my build you are running?
Installed a few minutes ago. Thank you for compiling the source code.
Am I wrong or can´t I flash GApps?
Edit: Also I cannot use any storage. Not internal and not sd card
@Silveryard Yeah there are like lots of bugs... I hope some will be solved in the future. Storage is definetely one of them. I never tried to flash gapps though
It´s because some .apk files (like the play framework) cannot be installed with adb install command and require a custom recovery kernel or root or root for writing permissions in "system"
I don´t know much about compiling a system image but is it possible to place the gapps files into the right folder right before compiling everything in one file? This would help much and would make this preview much more usable in daily life.
Thank you! I'll be trying this on my D6653.
Made an installation video.
How To: Flash Android M Alpha for Xperia Z3: https://youtu.be/rJgYnqv3ZPM
Good news
CedArctic said:
@Silveryard Yeah there are like lots of bugs... I hope some will be solved in the future. Storage is definetely one of them. I never tried to flash gapps though
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...v-android-m-apps-framework-deodexing-t3166000
@squabbi Cool bro @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide
CedArctic said:
@squabbi Cool bro @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide
Click to expand...
Click to collapse
What? I'm not sure what your talking about
Just to repeat, those are the actual M preview apps and I "fixed" them so that you can add them to your rom
@Aaahh you posted a quote of me about storage and I said now that I think I know that the issue is in the storage-list.xml in the framework. I will include your apps in the next build, but for now I am focusing on a different project until M becomes more stable...
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.
Announcing Sailfish for the Sony Xperia Z3 Compact!
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone.
Special thanks to:
rss351 and locusf for the collaborative effort in porting SailfishOS to the Z3 compact
Everyone from the SailfishOS team/community, sledges and mal- in particular.
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Known issues:
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Sensors dont work (auto-adjust brightness, etcetera)
The Jolla account/store functionality is not enabled. This is being worked on by Jolla. In the meantime: use openrepo's warehouse (see bottom of this post)
What works:
Booting, basic usage of the OS itself (browsing, etc)
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi (both 2,4 and 5 GHz)
Power management seems to work fine (not tested much though)
Looking around and getting a feel for SailfishOS
Using your phone to develop and debug SailfishOS apps.
Installation guide/checklist:
Insert default warranty void message here. Your warranty is now void
Make a backup (just to be sure)
Depending on what you need from your phone, this may not be a rom suitable for daily driving with. But installation is non-destructive to your existing rom, so if you're curious, give SailfishOS a try
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an official Sailfish OS build, and the Xperia Z3c is not a Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, this thread is perfectly fine for that.
BEWARE: this image is NOT optimized for security. The phone boots in development mode by default. There is a root shell on telnet port 2323. This is not secure and will give anyone who wants it remote access to your phone. When the port matures this will be fixed.
The Sailfish OS image does not provide recovery, and since the Xperia Z3c does not have a recovery partition, you need a bootimage with recovery on it to flash cm/stock/sailfishos upgrade. I highly recommend using Nut's Xperia files for this. Use the boot.img from your Cyanogenmod installation.
The Sailfish OS image is based on a recent version of Cyanogenmod 12.1, so update your Cyanogenmod installation while you are at it. Use cm-12.1-20160523-NIGHTLY-z3c.zip if you encounter issues with other versions. Using another rom is not guaranteed to work, even if this rom is based on Cyanogenmod.
You can find the required zip in this Mega folder: https://mega.nz/#F!ucoRnDjD!WAHNWgxLQX5SK1Vdu8MRWw
Use your favorite recovery (but not CM's recovery since that checks for signatures, which this image does not have) to flash the zip.
If you want to return to Cyanogenmod, extract boot.img from your cm-12 zip and flash that with fastboot. Alternatively you can restore a previous backup. There is no need to re-flash Cyanogenmod because it was not removed by installing SailfishOS. You can remove the /data/.stowaways/sailfishos/ folder afterwards to reclaim disk space.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Contributing
If you think this is awesome, and want to help fix the issues currently open: come by in #sailfishos-porters on irc.freenode.net!
Sources
You can find all used source code (may not be up-to-date to the latest image, but all key components are there) here: https://github.com/xperiasailors/
Installing OpenRepos warehouse
OpenRepos warehouse is like what F-Droid is versus Google's Play store. An unofficial, community-driven repository of open source apps.
Go to settings->developer options and set a password. Then open a terminal or connect over ssh to your phone (ssh [email protected]_of_phone).
Download the latest version of the warehouse app from here: https://openrepos.net/content/basil/warehouse-sailfishos
When you are asked to terminate packagekit anywhere in the steps below, answer yes.
Code:
$ devel-su
# zypper rr adaptation0
# zypper in <location_of_rpm_you_downloaded>
After this Warehouse app will be in your app launcher.
Impressive work! :good:
Sent from my Sony Xperia Z3 Compact using XDA Labs
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
mrrflagg said:
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
Click to expand...
Click to collapse
Probably, yes.
SailfishOS uses libhybris for hardware communication, which in turn uses the existing Cyanogenmod installation for drivers and proprietary blobs. But hybris is compiled against a certain Cyanogenmod version, so using other roms as a base might fail.
I've updated the TS and put the exact CM version I used in there, that should work fine.
There are any news? The project is in development?
Alexander3273 said:
There are any news? The project is in development?
Click to expand...
Click to collapse
No news, I don't spend much time on this port, every now and then I fiddle around with it an evening.
I'm currently trying to get AOSP based Sailfish port because Cyanogenmod for Z3c seems unmaintained, but progress is very slow.
Thank you for the info. Do you know when a version (sailfish port) comes out?
Hello! Thanks for your work. May i know the progress ?
it would be great to see a real "european" OS coming out of the dust...
i hate the thought that any company from the other side of the atlantic are wheels in the monster of patriot act...
@maikoool Any news about new build or something?
Yes, look here:
https://nokius.net/SFOS/scorpion/PreAlpha/
But still no Cam, no BT, No Sensors and No video playback
AFAIK is the 'scorpion' the Z3 Tablet compact, so not the Z3 compact. The base images will probably be the same.
I've recently rolled a build using AOSP 5.1 from the Sony Xperia developer pages, but my Z3c has developed an issue where the top and bottom of the screen don't function, so I cannot test properly.
Aries is device name, right? What's scorpion ?
kskarthik said:
Aries is device name, right? What's scorpion ?
Click to expand...
Click to collapse
Aries = Z3 compact, Scorpion = Z3 Tablet compact
I'm waiting eagerly to see SFOS on aries Do you know anything about our device support on jolla's list ?
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 - Sony Developer World
developer.sony.com
The one downside is Ubuntu...I would be down to start building roms...but the problem is I'm on windows 11...and prefer it...
Ainz_Ooal_Gown said:
The one downside is Ubuntu...I would be down to start building roms...but the problem is I'm on windows 11...and prefer it...
Click to expand...
Click to collapse
WSL?
unicastbg said:
WSL?
Click to expand...
Click to collapse
WSL??
What is Windows Subsystem for Linux
Learn about the Windows Subsystem for Linux, including the different versions and ways you can use them.
docs.microsoft.com
Code:
sudo apt-get purge ...
The instructions aren't off to a good start.
kevinmcmurtrie said:
Code:
sudo apt-get purge ...
The instructions aren't off to a good start.
Click to expand...
Click to collapse
To be blunt as a rock, you should be doing this on a clean install or inside a container anyways. I'm surprised Sony is not providing us with one.
UsernameNotRecognized said:
To be blunt as a rock, you should be doing this on a clean install or inside a container anyways. I'm surprised Sony is not providing us with one.
Click to expand...
Click to collapse
That's clear from step 1, but not necessary if Sony had created the build correctly. Modern build environments may coexist without issues.
Even apt-get is rather outdated.
kevinmcmurtrie said:
That's clear from step 1, but not necessary if Sony had created the build correctly. Modern build environments may coexist without issues.
Even apt-get is rather outdated.
Click to expand...
Click to collapse
The Guides are copy-paste since quite a time now. You basically just need to change the Tag each time You want to sync the Code. Anyways, sudo apt install works well on Ubuntu while some Parts cant be installed and need to be corrected like zlib1g-dev:i386 which is zlib1g-dev. WSL2 works fine on My W11 install. Just give this a go:
GitHub - bostrot/wsl2-distro-manager: A GUI to quickly manage your WSL2 instances
A GUI to quickly manage your WSL2 instances. Contribute to bostrot/wsl2-distro-manager development by creating an account on GitHub.
github.com
You will like it if You want to keep Windows...
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
Sakuma_Eitarou said:
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
Click to expand...
Click to collapse
There are many people involved working on it. It takes times and they need help with logs and testing since there are many supported devices. I am working myself on it with A13 and its a pain in the a** right now... Many small issues and missing stuff here and there. We are also talking about bugs like no Mobile Data + No Wifi and non working Cameras and such... It's a great Project but lacks Users and support...
Miustone said:
There are many people involved working on it. It takes times and they need help with logs and testing since there are many supported devices. I am working myself on it with A13 and its a pain in the a** right now... Many small issues and missing stuff here and there. We are also talking about bugs like no Mobile Data + No Wifi and non working Cameras and such... It's a great Project but lacks Users and support...
Click to expand...
Click to collapse
certainly lacks people and support because the community is too small due to the high cost and unpopularity of the phone. To begin with, I would like to see a completely completed firmware like this https://sourceforge.net/projects/ancientrom/files/gsi/V6.4/ and only then firmware based on a13
maybe one day there will be one fully working ROM with a fully programmable assistant button and a working Sony camera. as well as all the advantages of custom ROM
Sakuma_Eitarou said:
maybe one day there will be one fully working ROM with a fully programmable assistant button and a working Sony camera. as well as all the advantages of custom ROM
Click to expand...
Click to collapse
I can surely tease, there is Something comming this Year. Android 13 2019-2022 Xperias
Miustone said:
I can surely tease, there is Something comming this Year. Android 13 2019-2022 Xperias
Click to expand...
Click to collapse
in general, it doesn't matter, because official Google builds are 5 years behind amateur builds like crdroid and other teams. In my opinion, Android 12-13 looks gray, boring, not beautiful, sad, no transparency effects, colored notification icons. It feels like there are some idiots at Google who can't come up with anything worthwhile, or at least standardize what is already available in custom ROM. For example, it annoys me that the usual aosp assembly is empty, there you can't even adjust the height of swipes of control gestures
Miustone said:
The Guides are copy-paste since quite a time now. You basically just need to change the Tag each time You want to sync the Code. Anyways, sudo apt install works well on Ubuntu while some Parts cant be installed and need to be corrected like zlib1g-dev:i386 which is zlib1g-dev. WSL2 works fine on My W11 install. Just give this a go:
GitHub - bostrot/wsl2-distro-manager: A GUI to quickly manage your WSL2 instances
A GUI to quickly manage your WSL2 instances. Contribute to bostrot/wsl2-distro-manager development by creating an account on GitHub.
github.com
You will like it if You want to keep Windows...
Click to expand...
Click to collapse
would you want to update the aosp build guide as a how to do for xda?
i would certainly be interested in stock aosp build.
"Now you are ready to build AOSP images that can be flashed to a device. To do this, you have to point out your specific device and then start building the images."
this my current blocker. how would i point out the specific device? as i understand the command in the given step ( step5 ) it requires a source. that source is not specified in the builöd instructions or i didn't find them