The real joke here is they have something to hide for us with the stockrom-drivers, so they have another team that have to develop the drivers from scratch.
@fingus
it is my opinion that you are giving too much credit to Sony
one french politician (Michel Rocard) said once:
“Toujours préférer l’hypothèse de la connerie à celle du complot. La connerie est courante. Le complot exige un esprit rare.”
which i try to translate as
“Always prefer the hypothesis of stupidity to the one of conspiracy. Stupidity is common, Conspiracy needs a rare mind”
My understanding is that at least on some models, Sony’s alpha-team (their camera department) does the drivers for the camera to add their “secret sauce” to it, and the AOSP team have to come up with their own more generic solution. In the past there was also a theory about these improvements needing a secret key to use, and the key would be destroyed unrecoverably when you unlock the bootloader, leading to lesser image quality, even if you flash the stock Android back.
I also heard this non-recoverable key for superior cam output somewhere
It could very well be the thing they want to hide is licenced, and they don´t have permission to share it, per agreement. I would guess it is something like that. But, it is a guess. We can’t know when it is hidden. I expect it is nothing nefarious, but as we can’t know for sure, we should still assume it is.
Sony Xperia XCompact Wifi hotspot can be fixed by this link:
I got the fix working only by downloading rpm file and installing the fix locally (EDIT2).
Actually Sony have much bigger fails with their own software.Fail can always happen,more important is to fix them.
Thank you for the reply, but I think creating the image of these models will not cost lot, just recompile with the right variable. While it may help debugging as more people will install it and give their feedbacks.
I can confirm now, that there are cases where switching mobile connection off/on doesn’t do it. There was even the need of a reboot, because nothing worked (flight-mode on/off, android-support off/on, restart network services) to recover mobile connectivity.
I had the impression that this was the case only, when I used mobile hotspot in combination with GPS and some android app using the GPS for navigation. With this ‘setup’ there are events when android crashes completely after some time (but not always, which makes it quite tedious to reproduce) and mobile connectivity doesn’t come back (sometimes not even for sailfish itself) until you reboot the device.
Hanlon’s Razor: Never atttribute to malice that which is adequately explained by stupidity
Sonic Stage, anyone?
Me too, on a Xa2 dual (H4113). After upgrade is stuck on Sony’s logo. Flashing from scratch also leads to Sony’s logo. Flashing 4.4 works, upgrade to 4.5 works, upgrade to 4.6 no. Perhaps an encryption issue?
I’ve tried recovery->check filesystem and flashing after revert to Android with Emma. With 4.6 it’s not working.
I already use the beta on my Xperia 10 V. To be honest: I’d love to have Sfos 5.0 as soon as possible as licensed version (including Android App support) even if that one comes without camera support. Camera is secondary for me. The system itself already is my daily driver in its current beta, but I still need my old (mobile network broken) 10 II for my needed android apps. I use the 10V as hotspot for network access.
If I had Android support I would only need one device to carry around…
Has anyone heard something about when a licensed version for Xperia 10 V is coming? I really like to get sailfish, but with the beta I had no chance to install android applications. And for me this is necessary
Nobody in the community and probably Jolla also as they wait for Sony blob.
I’m not so worried about Android apps, I haven’t really missed any, and most of the time (eg. Banking apps, Youtube, etc) you can just use the website.
That said, there’s been a few times I’ve wanted to use the camera and haven’t been able to. Hoping Sony pull their fingers out soon. In the meantime I’ll have to just stick a cheap point & shoot in the glove box.
I’ll just piggyback off this to ask a question, however, as its been a long time since I’ve used SFOS: Is there any way to set an upper limit on battery charging? My phone has never spent so much time above 80%, and just charging it in the morning is not an option as it charges so slowly on SFOS. I need to work out how to limit it to 80% overnight…
Under Settings -> Battery -> Charging mode
(the last option, don’t know the exact option names in English or other languages) and change that so you can set the upper limit for the phone to stop charging.
Thanks, but for some reason that option is missing on the 10 IV. Is this a bug, or intentional? Is there a workaround?
I’ll also note I tried to use BatteryBuddy, and woke up to a phone that hadn’t charged at all, which was not ideal.
I actually had a look at this w.r.t. Battery Buddy as soon as I had flashed my X10V, and I couldn’t suitable files to control the charging. It looks like controlling the charger operation just isn’t currently exposed to userspace - that seems to be the reason why it’s missing from Settings as well. That’s all I could figure out from “outside” anyway.