Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Now you can build the latest Android with the latest 4.4 kernel
Thanks for all the hard work and keeping the resources easily accessible and up-to-date. I will be using them for sure .
Thank you for providing these resources and keeping up development for the devices they support. I notice that the dynamic resolution switch in the extended settings doesn't work on android 8.0 or 8.1. Are there any plans to add support for this back in at any point?
Sepo190 said:
Thank you for providing these resources and keeping up development for the devices they support. I notice that the dynamic resolution switch in the extended settings doesn't work on android 8.0 or 8.1. Are there any plans to add support for this back in at any point?
Click to expand...
Click to collapse
we are working on the issue
Regards
J
It says here that we can change the display to native 4K at 60hz or 1080 at 120hz with your AOSP https://androplus.org/Entry/4577/
The previous comment says it's not working in 8.0 or 8.1, but I don't see an open issue about it in your bug tracker. Was it fixed?
If it wasn't available for 8.0 and 8.1, what version is it available on?
I hope los and rr now.
gaijin1% said:
It says here that we can change the display to native 4K at 60hz or 1080 at 120hz with your AOSP https://androplus.org/Entry/4577/
The previous comment says it's not working in 8.0 or 8.1, but I don't see an open issue about it in your bug tracker. Was it fixed?
If it wasn't available for 8.0 and 8.1, what version is it available on?
Click to expand...
Click to collapse
Just to be sure, I opened an issue in the bug tracker for it.
@jerpelea, if you would like the issue to be closed, I'll happily close it.
iArvee said:
Just to be sure, I opened an issue in the bug tracker for it.
@jerpelea, if you would like the issue to be closed, I'll happily close it.
Click to expand...
Click to collapse
we are working on it
please leave it open
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
jerpelea said:
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
Click to expand...
Click to collapse
Is there a changelog or something like that? I had issues with these binaries and AOSP builds from last week. A few days later I noticed a commit that mentioned these new binaries, but after that the "Fingerprint" setting is gone, so I'm now using a build of 08-03-2018 with the V10 binaries.
To be honest, I haven't tried a factory reset nor flashing userdata.img, so when I get home I'll update the repo, build a new version and do a full reset.
@jerpelea why Sony remove the FM radio feature on all modern Xperia phones? Why??? The hardware capability is there. Why you cripple the phone on purpose?
Can you please give a logical explanation about this issue?
When will Sony give me back this feature?
And why Sony block the Displayport alt mode? Again you cripple the phone on purpose.
And why I cannot root my phone without losing DRM keys? How to backup my DRM keys??? Please tell me.
I am waiting for answers but my patience is slowly running out.
Thanks Sony for being so user friendly.
If Sony don't fix these issues soon I will never buy Sony products ever again and I sell my Xperia's, my Playstations, my Walkmans, my Sony TV's and all my other Sony products. And I tell all the people that I know to do the same.
It's your choice Sony.
lebigmac said:
@jerpelea why Sony remove the FM radio feature on all modern Xperia phones? Why??? The hardware capability is there. Why you cripple the phone on purpose?
Can you please give a logical explanation about this issue?
When will Sony give me back this feature?
And why Sony block the Displayport alt mode? Again you cripple the phone on purpose.
I am waiting but my patience is slowly fading away.
And why I cannot root my phone without losing DRM keys? How to backup my DRM keys??? Please tell me.
Thanks Sony for being so user friendly.
If Sony don't fix these issues soon I will never buy Sony products ever again and I sell my Xperia's, my Playstations, my Walkmans, my Sony TV's and all my other Sony products. And I tell all the people that I know to do the same.
It's your choice Sony.
Click to expand...
Click to collapse
Nice try but Sony will ignore it like every other vendor.
Moarten said:
Is there a changelog or something like that? I had issues with these binaries and AOSP builds from last week. A few days later I noticed a commit that mentioned these new binaries, but after that the "Fingerprint" setting is gone, so I'm now using a build of 08-03-2018 with the V10 binaries.
To be honest, I haven't tried a factory reset nor flashing userdata.img, so when I get home I'll update the repo, build a new version and do a full reset.
Click to expand...
Click to collapse
the fingerprint has been fixed and now it is working as it should (stability issues are fixed)
please update your device with the latest Sony Sw before flashing AOSP
Regards
J
Bitti09 said:
Nice try but Sony will ignore it like every other vendor.
Click to expand...
Click to collapse
No. Some manufacturers actually care about their users. Not all smartphone manufacturers cripple the phone on purpose the way Sony does it.
lebigmac said:
@jerpelea why Sony remove the FM radio feature on all modern Xperia phones? Why??? The hardware capability is there. Why you cripple the phone on purpose?
Can you please give a logical explanation about this issue?
When will Sony give me back this feature?
And why Sony block the Displayport alt mode? Again you cripple the phone on purpose.
And why I cannot root my phone without losing DRM keys? How to backup my DRM keys??? Please tell me.
I am waiting for answers but my patience is slowly running out.
Thanks Sony for being so user friendly.
If Sony don't fix these issues soon I will never buy Sony products ever again and I sell my Xperia's, my Playstations, my Walkmans, my Sony TV's and all my other Sony products. And I tell all the people that I know to do the same.
It's your choice Sony.
Click to expand...
Click to collapse
Unfortunately I can't answer those questions since I am just a developer
Regards
J
jerpelea said:
the fingerprint has been fixed and now it is working as it should (stability issues are fixed)
please update your device with the latest Sony Sw before flashing AOSP
Regards
J
Click to expand...
Click to collapse
Great, thanks. I've returned to the stock roms now, but will try AOSP again soon.
jerpelea... Remeber well from the early FXP Times back on My SONY Devices. Can't wait to try out XODP after Years without SONY Devices. Thanks a lot for still contributing that much to the Xperias! True Hero!
i think you should support dual sim cards,i flash aosp for g8142 but it cant use 2 sim cards
loukky said:
i think you should support dual sim cards,i flash aosp for g8142 but it cant use 2 sim cards
Click to expand...
Click to collapse
I am using a XA2 Dual sim with Android 8.1 and it works fine
Regards
Alin
Related
How to make Bluetooth permanently discoverable for Android 2.3.4 Gingerbread.
I am using Stock Xperia Pro GB .69 with root access.
I'm not sure about GB but on ICS and JB there is a visibility timeout setting in a bluetooth settings screen. Go there and push a menu button.
Not possible due to security reasons.
Someguyfromhell said:
Not possible due to security reasons.
Click to expand...
Click to collapse
Is there any tweek available?
chiragvagh said:
Is there any tweek available?
Click to expand...
Click to collapse
None that developers know. It has never been requested or needed by anyone.
Someguyfromhell said:
None that developers know. It has never been requested or needed by anyone.
Click to expand...
Click to collapse
Is there any update!!!!!!!!!!!!!!!!!!.
Micromax A27 phone is having android 2.3.6 and its having bluetooth visibility timeout infinite or discoverable always.
How that is possible with adroid 2.3.X
Please help
chiragvagh said:
Is there any update!!!!!!!!!!!!!!!!!!.
Micromax A27 phone is having android 2.3.6 and its having bluetooth visibility timeout infinite or discoverable always.
How that is possible with adroid 2.3.X
Please help
Click to expand...
Click to collapse
Just because one phone manufacturer added it to its firmware, does not mean it is available on all phones.
Sony phones do not have such feature and most likely it will not be added due to security reasons.
Come on, you do not want someone to be hacking your phone via Bluetooth without your knowledge, do you?
Someguyfromhell said:
Just because one phone manufacturer added it to its firmware, does not mean it is available on all phones.
Sony phones do not have such feature and most likely it will not be added due to security reasons.
Come on, you do not want someone to be hacking your phone via Bluetooth without your knowledge, do you?
Click to expand...
Click to collapse
What are security reasons, It is already available in ICS and JB. Is there no security? And there is option to switch off the Bluetooth, so when needed I can switch off that, no need to make mobile discovery off.
If you don't know the solution, then stop giving this type of answers.
chiragvagh said:
What are security reasons, It is already available in ICS and JB. Is there no security? And there is option to switch off the Bluetooth, so when needed I can switch off that, no need to make mobile discovery off.
If you don't know the solution, then stop giving this type of answers.
Click to expand...
Click to collapse
Well a noob can hack to your or my phone via bluetooth,it's very easy,one click,and how many times did you forgot to turn it off???I was looking for something like this once,but when my friend got hacked i stopped...Thats the security and i don't think that Stock ICS has a turn visibility on for perment.Bit i'm sure its impossible to get it on GB...
Sent from my LT15i using xda premium
chiragvagh said:
If you don't know the solution, then stop giving this type of answers.
Click to expand...
Click to collapse
The thing is, that there is currently no solution for Sony or Sony Ericsson phones.
Sony Music App version 9.3.11 (with Walkman Logo)
That you can install like any other Normal app for any device running Android 4.2 and above. Root or No Root.
I have just made only one change that is removing the restrictions for compatible devices and unlocked it for all devices, there might be some bug for certain features that might not be supported on every device, but it works. I will update more apps that we all can use, even for unrooted devices. just don't ask for ETA's I am not that much in development actively.
Enjoy.
Download here
Although there is another thread for this app here which I saw just after creating this post and a better one than mine. So I will port and post some other apps that works on our devices.
You can also try these apps that I posted on other thread here. works on unrooted devices as well.
Is ClearAudio+ available ?
gougous3 said:
Is ClearAudio+ available ?
Click to expand...
Click to collapse
+1 and sound enhancements? is that available too?
What is the point of walkman without sony's sound enhancement..
*no offense bro..
Thanks for sharing.
gougous3 said:
Is ClearAudio+ available ?
Click to expand...
Click to collapse
No, for un-rooted device apart from sony.
for rooted users, that is possible for any device, but can't guarantee, until I or someone else tests it on Mi A1.
harshu0101 said:
+1 and sound enhancements? is that available too?
Click to expand...
Click to collapse
Without Root, not available for anyone apart from Sony. Need build.prop edits as well as other things on the system partition for it to work for the port.
babalizm said:
What is the point of walkman without sony's sound enhancement..
*no offense bro..
Click to expand...
Click to collapse
None taken and as much as I love to have all the options open for an android device, I have to keep this device unrooted.(I have 6 other devices in my home and all of them are rooted except this one), so for now, it's my 1 percent to the A1 community.
Good
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
AOSP and LOS roms should be okay.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
@auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
This causes a bootloop on P DP1.
iaTa said:
This causes a bootloop on P DP1.
Click to expand...
Click to collapse
Thanks for the report.
can anyone confirm this?
In the meantime i removed the p tag from the thread title.
Could be That there are additional changes in p that make this libs unusable and only workable on 8.1.
Unfortunately there is afaik no complete source for p yet. So I can’t compile them specifically for p.
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
jbarcus81 said:
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
Click to expand...
Click to collapse
Same with me on google fotos!
Glad it’s fixed for you.
Freak07 said:
Same with me on google fotos!
Glad it’s fixed for you.
Click to expand...
Click to collapse
Also fixed for me, thanks for solving this problem!
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Prey521 said:
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
Click to expand...
Click to collapse
sixohtew said:
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Click to expand...
Click to collapse
I also thought at first I didn’t have this issue at all.
But once I triggered it accidentally I experienced it many times. Maybe I just learnt what to look for.
Another fun thing is. A friend of mine also got the pixel XL 2 and I could reproduce it right away on his locked phone which is stock 8.1.
I can also trigger it on my pixel C tablet.
ReapinDevil said:
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
Click to expand...
Click to collapse
Either try flashing it in recovery or use the latest magisk?
Freak07 said:
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
@auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
Click to expand...
Click to collapse
The mention for the last dev didn't work for some reason, so:
@auras76
mistermojorizin said:
The mention for the last dev didn't work for some reason, so:
@auras76
Click to expand...
Click to collapse
Thanks in the quote from your post of my post it worked tough
Freak07 said:
Thanks in the quote from your post of my post it worked tough
Click to expand...
Click to collapse
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the quote.
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
What app did you use for that test?
I've experienced lack of touch response quite often. It's weird and seemingly random. I just flashed this on 8.1 with magisk. I don't have any results yet, but based on what everyone else is saying, this is a solid fix. Thanks for your work!
Do we have to worry about removing this in the future if google updates fix the issue too? Will this being on the system cause conflicts and issues?
mistermojorizin said:
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the Autor.
Click to expand...
Click to collapse
That’s just xda bring xda.
I had this problem a few times when updating the OP for a new release. Sometimes the OP won’t update at all...
otonieru said:
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
Click to expand...
Click to collapse
Glad it works out for you!
Enjoy your phone
Hey, just a discussion. A50 comes with android 9.0 pie. And Treble Check app In Playstore shows A only option. So its supported. But anyone tried it yet?
Pls let me know as I dont want to risk my phone.
Someone try installing pixel experience from of this project.
Pratham Gajjar said:
Hey, just a discussion. A50 comes with android 9.0 pie. And Treble Check app In Playstore shows A only option. So its supported. But anyone tried it yet?
Pls let me know as I dont want to risk my phone.
Someone try installing pixel experience from of this project.
Click to expand...
Click to collapse
Hey mate,
Treble with Samsung is always a bit icky in my experience. Personally, don't try it yet.
The A50 has a Pie vendor, and yes, it does have Treble. Every phone shipped with an OS past 8.0 will have it. I had this convo on Telegram, I say it's best to wait, or if you're curious, try one of phh's GSI's. Pixel Experience would best work on the A50 with it's own device tree, which as far as this has been posted, isn't available. It's a waiting game.
As I say to a lot of people, if you bought a new Samsung to enjoy AOSP, you bought the wrong phone.
Yeah you're right. But I like stock android. I would've installed it but I'm scared it won't support the in display fingerprint and face unlock and various things.
Pratham Gajjar said:
Yeah you're right. But I like stock android. I would've installed it but I'm scared it won't support the in display fingerprint and face unlock and various things.
Click to expand...
Click to collapse
I understand, and I do too. For in display fingerprint to work, you'll need the tree and a rom that can support it. Face unlock, iris unlock and others are lost due to lack of Google support.
Xperia 10 III is now officially supported by Sailfish OS: https://blog.jolla.com/xperia-10-iii/
From Wikipedia:
Sailfish OS is a Linux-based operating system based on free software, and open source projects such as Mer as well as including a closed source UI. The project is being developed by the Finnish company Jolla.
Click to expand...
Click to collapse
Anyone in here tried it yet?
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
According to its readme file, Newflasher runs on Linux too: https://github.com/munjeni/newflasher
So I think it should be possible to flash an Android 11-based firmware from here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/ using this tool. But I never used it (neither on Windows nor on Linux) so I can't say for sure whether that works.
As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?
As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?
Click to expand...
Click to collapse
Ha! Yes I did do all the required steps. I found an Android 11-based build on the Sailfish forums which worked, after doing it twice with Newflasher. Once this was done the OEM unlock command did its thing without a hiccup. Sailfish OS is now running nicely on the 10 III - hopefully Jolla are able to provide some more complete instructions for those who have managed to upgrade themselves into a documentation loop!
I've been using the X10III with Sailfish for several days now, and the experience is quite smooth. There is no green tint visible, but the "color space" gets really smashed and mangled in low light + low brightness situations... I think it's more or less the same bug. The best way to describe is that the dark areas of the screen are rendered with 8-bit color palette and way too high brightness. I created a bug report for it over at Sailfish OS Forum for those who wish to keep an eye on that.
There are three known issues: Camera API doesn't support the three back cameras (Camera2 API does support it, so it's very fixable), the indicator led is way too green (driver issue), and issues with noise cancellation during phone calls (seems to be fixed in git).
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
direc85 said:
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
I have a hard time understanding why it is necessary to repair a thing that is not broken?
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
And in general, calling is the least used feature of the phone lately.
ksuuk said:
I have a hard time understanding why it is necessary to repair a thing that is not broken?
Click to expand...
Click to collapse
What exactly are you referring to? 3G, the OS in the device, or something else..?
ksuuk said:
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
Click to expand...
Click to collapse
Why shouldn't I use what I already paid for?
But yes, phone calls are getting rarer; for me it's something between daily and weekly. But still, it's the official method to be reached, supported by pretty much every device, so why not just use it instead of apps.
Also, if I wanted to use only apps to talk with my friends, I'd have five chat apps installed, some of them analyzing me, and all of them draining my battery. No thanks...
But let's get back to topic. Does anyone know how to solve the color banding issue on AOSP?
direc85 said:
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.
Aranornen said:
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.
Click to expand...
Click to collapse
I can't say anything about features built into the OS (as I've never used it), but I was able to find two 3rd party apps which let you limit the maximum battery charge level:
Battery Buddy | OpenRepos.net — Community Repository System
openrepos.net
takimata / harbour-battery-charging-control · GitLab
SailfishOS application which allows to stop battery charging at user-defined levels.
gitlab.com
Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
hi can you help me o i have an Xperia 5 phone running sailfish os same as your Xperia 10 mark 3 i cant buy license to run apk app you can extract aliendalvik file can you give it to me, i will keep it from sharing to anyone, because it is the source of life jolla , i will transfer you a small amount of money, i come to sailfish os full of passion but not enough money , hope you can help, thank you very much