Related
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...
About Team Pear Crew:
Hey there! We are a team of android fanboys who love customization! We love to build ROMs, MODs, Kernels and tweaks. We have are addicted to flashing our Android handsets. We started out as a porting team who flooded the forums of the Desire HD/ARC/Neo/Play/... forums with ROMs. Now we moved to building and modifying source code for other devices. One of our handsets is the Xperia Z3 and we intend to build more ROMs for it in the future as well as provide weekly builds of our existing projects. If you love our work and care to support us in getting some better equipment to further advance our work, you can give us a small donation. Without further to do, I present to you the SlimLP ROM.
About Slim ROMs:
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
Features:
-Layers 2.1 Support
- SlimNavbar
- SlimPIE
- SlimRecents
- SlimHeadsup
- Chamber of secrets
- Privacy guard
- Expanded desktop
- Global menu
- Many more
Disclaimer: We (team Pear Crew) and the Slim Team take no responsibility to whatever harm may be done by the use of this software.
Screenshots: Here you go
Installation Instructions:
- Download SlimLP and the specific Gapps linked.
- Boot into recovery.
- Perform a full backup.
- Perform a complete wip (system, data, dalvik, cache)
- Reboot phone.
- Once phone is booted and set up, enable developer options and then enable USB debugging, then go to System ->Security and temporarily enable Root Access for ADB and Apps.
- Connect your phone to your computer
- Download TWRP from here. And place it in your Internal Storage (not inside a folder)
- Start up cmd at your adb/fastboot installation directory (search XDA for: Minimal ADB/Fastboot or else install Android SDK) and type
Code:
adb shell
and hit enter.
- Then type
Code:
su
and hit enter. Grant root access on your phone if prompted (you normally shouldn't)
- Copy and paste this into the cmd:
Code:
dd if=/sdcard/z3fotatwrpv4.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and hit enter.
- Close cmd and enjoy. Your phone is now running the latest SlimLP and has TWRP by LeonidasTurk installed. It is important to install the recovery, as the one that SlimLP installs is unusable at the current state.
Downloads:
SlimLP - Build I
Google Apps NOTE: It's important to install these specific Gapps as some other Gapps packages might cause issues with the ROM.
Bugs: You tell me , even the camera key works (not in the lockscreen though).
Credits:
Team Pear Crew
Luna
Irene F.
akateha
PhilipoZ-DaPreZident
Pcnoic
Axilleas T.
My family
Google
Sony
CyanogenMod
XDA Community
Slim ROMs
Slim ROMs links: >slimroms.net >Official downloads >Changelogs >FAQ >Kernel Sources of official devices >Google+ >Twitter >Facebook >Forums
Reserved
Great:fingers-crossed:
what do u mean "even the camera key works". thats not the same as drm keys i guess? do this work on LB, or do we need UB?
@sewb XD no I didn't mean software DRM keys. I meant the actual camera button on the side of the Z3, you can use it to launch the camera app Have a nice day man
@th0ngpham Thanks
CedArctic said:
@sewb XD no I didn't mean software DRM keys. I meant the actual camera button on the side of the Z3, you can use it to launch the camera app Have a nice day man
@th0ngpham Thanks
Click to expand...
Click to collapse
yeah thats what i thought. does that button not work on other roms?
@sewb Oddly in other ROMs, that button only works to shoot photos within the camera app, in SlimLP the button works to launch the app, not shoot photos... weird stuff...
OK. Thanks. How does Dolby audio, viper and xposed work on this one? Anyone tried?
Sent from my Xperia Z3 using Tapatalk
Locked or unlocked bootloader?
@sewb haven't tried it yet.
@gregysk Unlocked
ive used this now since yesterday and it seems really nice. but its a couple of things i wonder. is it possible to get a option to only have battery in text and no icon in status bar? and also im mising doubletap setting in nav bar, can only get singel and long tap now?
Sent from my Xperia Z3 using Tapatalk
@sewb I think you can get these mods through third party solutions such as Xposed or the 3Minit Battery mod. As for the double tap, I think you can enable it with Kernel Tuner. This ROM is currently being developed by team Slim. I assume they will be added in the future...
ok. im gonna try xposed, but cant do that until monday. gonna try 3minit, thanks
Sent from my Xperia Z3 using Tapatalk
Looks great! Finally AOSP with Cam key :victory:
What about the other Features?
What is Layer 2.1, Chamber of secrets and Global Menu?
Will test later...:fingers-crossed: Thanks!
@sewb No problem man
@Miustone Hahaha OK, Layers 2.1 is an addition to the android framework like xposed but is integrated into the code. So you can install themes (like CyanogenMod) and other mods (you need the Layers Manager by Bitsyko first, search it on the Play Store) I suggest trying the Elixium UI Layer theme (check it out on Play Store). Chambers of secrets is a Harry Potter reference, that is how team Slim calls the developer options . As for Global Menu I have no idea XD. Have a nice day man
Is the fisheye camera bug still present? This is literally the only thing that keeps me stock and locked at the moment
@sgiannouris No the camera bug isn't present on SlimLP (and I think pretty much any AOSP ROM). (An exeis kanena problhma apla steile mhnuma )
CedArctic said:
@sgiannouris No the camera bug isn't present on SlimLP (and I think pretty much any AOSP ROM). (An exeis kanena problhma apla steile mhnuma )
Click to expand...
Click to collapse
Wait what? So what you're saying is that aosp roms has fixed the fisheye problem. Do we finally have shinano drivers for our camera or are they still the same as xperia z1. So if you take a picture of something with a straight line like a TV, it does not get bended? This has been the only bug that has been kept me away from custom ROMs other than stock sony based.
Oh and does the camera key work to launch the camera app while the screen is off?
My last question, does auto brightness work? (it ha been a problem in cm12.1)
So fisheye bug is fixed for all aosp and is this the only aosp rom out for our phones
If it's really fixed, I'd be super happy. Can anyone confirm?
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 ?
FIRST OF:
You warranty is now void dont point at me if Broken or ill laugh at youbla bla you already know it
THIS IS NOT MY ROM! ALL CREDITS TO MAKING IT, GO TO THE AOSPA TEAM!!! I JUST EDITED TIME VALUES TO THE YEAR 2020
So i found (and "restored") this old paranoid Android 8.1 build...a lot of features missing like Theme manager but with built in Substrat um support? Everything Working
OEM image Version 17 for Android 8.1 Loire required
Rom download:
https://drive.google.com/file/d/1C6iliMInY5pH9mVwPiKUdzc1VFSNnvSe/view?usp=drivesdk
You can get that image Here:https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-4-loire/
Known bugs: Reinstall needed if navbar turned off and on
You dont tell me
Because I can't fix it
Gapps not included but found Here:https://opengapps.org
Special thanks to: Paranoid Android Team for making this Rom
And Me for " restoring" it I guess
Some random said:
FIRST OF:
You warranty is now void dont point at me if Broken or ill laugh at youbla bla you already know it
THIS IS NOT MY ROM! ALL CREDITS TO MAKING IT, GO TO THE AOSPA TEAM!!! I JUST EDITED TIME VALUES TO THE YEAR 2020
So i found (and "restored") this old paranoid Android 8.1 build...a lot of features missing like Theme manager but with built in Substrat um support? Everything Wirkung and OEM image Version 17 for Android 8.1 Loire required
Rom download:
https://drive.google.com/file/d/1C6iliMInY5pH9mVwPiKUdzc1VFSNnvSe/view?usp=drivesdk
You can get that image Here:https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-4-loire/
Known bugs: Reinstall needed if navbar turned off and on
You dont tell me
Gapps not included but found Here: Opengapps.org
Special thanks to: Paranoid Android Team for making this Rom?
Me for " restoring" it???
I really dont know
Click to expand...
Click to collapse
Wow someone actually thanked this!
Oh and by The way this Rom is rootable and should Have full xposed support too
For those who aren't clear, this guy changed the build date of AOSPA 8.1.0 to 2020, so that it could be installed over latest stock firmware. The build on AOSPA website was throwing errors while flashing, because it was built before .118 firmware.
Personally i'm not using this one (still waiting for PA9 stable) but i can see this coming in handy. Good work.
Yeah wasnt really hard or something just needed some converters and thats it
Hi, I want to try Paranoid Android on my Xperia X but neither the official image on aospa official site neither this version worked for me. The rom is correctly flashed on my device but after the sony logo image I have a black screen with the error message "Your device has failed verification and will not work properly." and then it shuts down.
I flashed the ODM oem.img v17 for Android 8.1 before flashing the AOSPA zip.
Do you know how to solve this problem?
DaNi95 said:
Hi, I want to try Paranoid Android on my Xperia X but neither the official image on aospa official site neither this version worked for me. The rom is correctly flashed on my device but after the sony logo image I have a black screen with the error message "Your device has failed verification and will not work properly." and then it shuts down.
I flashed the ODM oem.img v17 for Android 8.1 before flashing the AOSPA zip.
Do you know how to solve this problem?
Click to expand...
Click to collapse
Hey!
Currently my Xperia X is broken...
But try reflashing the latest stock Oreo before using this
DISCLAIMER
This rom is usable BUT it's just a old development build with a patch applied
There are a lot of bugs
If you find one please report it to me
I'm going to put that bug into OP
Some random said:
Hey!
Currently my Xperia X is broken...
But try reflashing the latest stock Oreo before using this
DISCLAIMER
This rom is usable BUT it's just a old development build with a patch applied
There are a lot of bugs
If you find one please report it to me
I'm going to put that bug into OP
Click to expand...
Click to collapse
I've tried flashing AOSPA after reflashing the stock Oreo and my Xperia X got stuck on Sony logo. I didn't flash the ODM oem image after reflashing stock Oreo
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!