Great! Does it actually work? Can you discover any BT devices in AAS?
Is it worth running sfos as a daily on Nagara yet? Or should I wait? I’m mostly concerned with audio, I had to give up on getting xNext ported over to android and just flat out remove all the dolby nonsense because documentation on the dac solution is next to non-existent.
Nagara Port is the best port I’ve ever used before. I use Xperia 1 IV as my main device. There were no problems with the sound. I hear the other person well and clearly, and the other person hears me well. The phone lasts for at least two days on a single battery charge. Sometimes it can get very hot when using AAS applications.
Thank you all for excellent work.
1 Like
Definitely YES. I’ve been daily driving it for several months already and it looks like the best SFOS experience I’ve ever had. I intend to keep using it as my daily driver as long as possible (i.e. until it breaks or something like that). The port itself is totally stable and fully functional, but in addition to that the 1 IV and 5 IV are the fastest devices SFOS has ever been ported to, considerably more powerful than even the latest JP2. I can’t recall having any problems with sound, it is clear and of good quality, both calls and media playback. What I don’t like about it is that the 1 IV is quite hungry for power when browsing the web or streaming videos (it’s not unusual for it to momentarily draw even up to 1.5-2 Amps in such case), especially on mobile data connection (on WiFi it seems to eat noticeably less), but on the other hand on standby/idle it is actually the most power eficient of all my SFOS devices - when idling it often consumes less than 0.5% of battery per hour.
Warmly recommended!
5 Likes
I had no more reboots so far since I updated to 5.1.0.11. It has been 2 weeks now (taking photos).
I had random missing touchscreen when waking-up and unlocking from finger print (with normal reaction time).
The situation was bad while I had disabled the double-tap to wake-up feature.
I still have variable delays to wake-up now using double-tap (even worse than before : 5 to 10s) but far less missing touchscreen after that.
Might be an hardware problem on my official Sony-compliant replaced screen device.
Anyway I’m very happy with this snappy port, and photo quality is good with those high-end devices.
power
This is normal on the stock android OS. Sony’s approach to consumption is quite aggressive, to the point of delayed notifications and such. It ramps up incredibly quickly in use, though. The consumption at heavy operation is quite high, which may well have been the motivation for the offset.
Assuming part of the sony open devices source is used here, this might be an explanation.
Also, I might as well ask here since I didn’t get a response on IRC. Are there any other non-gesture launchers around for SFOS? Dyspraxia makes it kinda hard to get the vagueries of gestures right, and it’s an unpleasant user experience for me. I much prefer buttons, so much so that I’ve stuck with a specific launcher layout for almost two decades now. Is it feasible to replicate at least the buttons and application drawer on SF, as pictured below?
1 Like
There isnt any patch to my knowledge to replicate such a layout with buttons, no.
SfOS is inherently a gestures OS.
There isn’t even the concept of alternative “launchers”.
I would have imagined that less precise swipe gestures would be easier than hitting buttons - especially tiny ones like in your screenshot.
But please, one topic per topic.
Nice to hear! I did not have “camera on, turn screen off” problems either.
But I still encountered zoom problems sometimes, and camera did froze on taking pictures, but only for a short(er) time and it didnt bring the system down. So it is better, but not gone for good.