Usage is also very nice for energy and display stats.
1 Like
When I connect the 10III via bluetooth wit my car then only the bt mac address is shown only and not the device name.
Can sombody else confirm that behaviour?
1 Like
I have a Xperia 10 III and I can correctly connect to my car (and also the name is shown correctly). Maybe this is specific to your car?
It’s a known issue; you’ll have to change the name of the device, and it shows up correctly until you reboot the device. Hopefully it will be fixed in the next release.
3 Likes
Does somebody has any idea why sailfish-home LUKS partition has this on 10III?
# /usr/sbin/cryptsetup luksDump /dev/mapper/sailfish-home
LUKS header information for /dev/mapper/sailfish-home
Version: 1
Cipher name: aes
Cipher mode: xts-plain64
Hash spec: sha256
Payload offset: 4112 <<<<<<<<<<<<<<<<<<<<
...
I’ve checked on my 10, it has the usual 4096 offset. But LUKS on it was set up 2 years ago, so…
What are these 8 KB of additional data on 10III on 4.4?
Maybe it’s related to that
Phone doesn’t keep bluetooth settings
It affects me similarly:
The first pairing went well, except that the name of the BT device (mobile) did not appear identical in the car, it wrote a sequence of character pairs similar to the MAC. After disconnecting the mobile phone and turning off the BT, the mobile phone did not connect automatically for the second time (“pair automatically” was specified during pairing). I had to re-pair with my cell phone in the car.
Xperia 10 III, Mazda 3
1 Like
Hi everyone, a question for those who have already installed OS on Xperia 10 III: how fast the stock browser is? Is everything is really “butter smooth” like Jolla says? Of course, it’s surely quicker in loading pages, but what about scrolling experience?
Nobody talking about whether overall scrolling really improved. Say, opening and scrolling this forum or some heavy news websites like Washington Post, etc. On my Xperia 10 II scrolling pages in default browser is always super laggy, maybe somehow on Xperia 10 III it’s better? It’s doubtful… but anyway?
I haven’t seen any problems with scrolling on the 10 III in the week or so that I have been running Sailfish 4.4 on it. Compared to my XA2 its a lot faster.
Well, of course that depends on what one is considering an issue. That’s what I usually see on my 10 II: Video on Google Drive
I’m probably not the best reporter coming from jolla C, but it does feel buttery smooth
Browser on 10mk1 sucked, I almost always preferred to use Android’s Firefox.
On 10mk3 I haven’t even installed it yet. Not sure I ever will.
4 Likes
Wow, is it that good? The thing is, if it’s really working so well, it should be a serious reason to choose xperia 10 III over anything else. Could you possibly provide a video of scrolling? (as there are no other sources on internet anyway)
1 Like
I can confirm that, too. So far I can’t send “SMS” with the Xperia 10 III, which worked before with an Moto G9 play.
Hi, I observe that the accumulator decreases very fast with “Android Support” activated:
- during 16,5 h from 100% to 50% with “Android support” and WLAN activ
- during 7,5 h from 50% to 45% with “Android support” and WLAN deactivated.
Furthermore I don’t get push-notifactions from Android-mails (installed by Aurora Store).
Regards
WLAN truly is a power hog, especially with crowded airways. The same holds true to crowded 4G areas, too.
Android support in itself doesn’t use battery that much, but the apps with background services do. In my experience, just having WhatsApp installed and not even opened makes the battery deplete a whole lot faster…
2 Likes
I can confirm that. The following 8 hours I activated only WLAN and used Android support only several minutes:
the accumulators decreased in 8 h from 50% to 19% → that is a factor 6 times faster than with WLAN deactivated.
I hope that the next software-update brings a significant improvement in this issue.
Idea:
Before that phone I used a Moto G 9 play which has a very nice feature:
If you put down the phone face down (display on the table) → “do not disturb”-mode is automatically activated. When you pick it up later, it is at once in the normal state again.
For the Xperia 10 III would a similar behavior be very useful :
If you put down the phone face down, the flight mode should be activated automatically. When picking up it should be deactivated. (If you lay down the phone face up, nothing should be done.)
→ This would save a lot of power without tapping the settings on the phone!
2 Likes
Yes, the browser is very much improved. I used to avoid the native browser like the plague and open everything in Firefox. On 10iii I’m actually choosing the SFOS browser over FF when I want a better experience. (Doesn’t count security or privacy issues tho).
It has been three weeks and honestly, this is my favorite phone since the N9. And that is saying a lot because IMO the N9 was the greatest phone of all time. (And I’ve tried a lot of alternatives!)
14 Likes
Could anyone using a 10iii please post the content of /vendor/etc/gps.conf or upload the file?
Thanks.
$ cat /vendor/etc/gps.conf
# XTRA_SERVER_QUERY (1=on, 0=off)
# If XTRA_SERVER_QUERY is on, the XTRA_SERVERs listed
# below will be ignored, and instead the servers will
# be queried from the modem.
XTRA_SERVER_QUERY=0
# XTRA_SERVERs below are used only if XTRA_SERVER_QUERY
# is off.
XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra2.bin
XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra2.bin
XTRA_SERVER_3=http://xtrapath3.izatcloud.net/xtra2.bin
# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0
# NTP Server
# NTP_SERVER=time.gpsonextra.net
# Asia
# NTP_SERVER=asia.pool.ntp.org
# Europe
# NTP_SERVER=europe.pool.ntp.org
# North America
# NTP_SERVER=north-america.pool.ntp.org
NTP_SERVER = time.google.com
# If NTP_SERVER is commented NTP_SERVER=time.izatcloud.net is used
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
# If DEBUG_LEVEL is commented, Android's logging levels will be used
DEBUG_LEVEL = 1
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# GPS Capabilities bit mask
# SCHEDULING = 0x01
# MSB = 0x02
# MSA = 0x04
# ON_DEMAND_TIME = 0x10
# GEOFENCE = 0x20
# default = ON_DEMAND_TIME | MSA | MSB | SCHEDULING | GEOFENCE
CAPABILITIES=0x37
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000
################################
##### AGPS server settings #####
################################
# Bitmask of slots that are available
# for write/install to, where 1s indicate writable,
# and the default value is 0 where no slots
# are writable. For example, AGPS_CERT_WRITABLE_MASK
# of b1000001010 makes 3 slots available
# and the remaining 7 slots unwritable.
# AGPS_CERT_WRITABLE_MASK=0
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.sonyericsson.com
SUPL_PORT=7275
################################
# EXTRA SETTINGS
################################
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=0
# Mark if it is a SGLTE target (1=SGLTE, 0=nonSGLTE)
SGLTE_TARGET=0
##################################################
# Select technology for LPPe Control Plane
##################################################
# 0x1: DBH for LPPe CP
# 0x2: WLAN AP Measurements for LPPe CP
LPPE_CP_TECHNOLOGY = 0
##################################################
# Select technology for LPPe User Plane
##################################################
# 0x1: DBH for LPPe UP
# 0x2: WLAN AP Measurements for LPPe UP
LPPE_UP_TECHNOLOGY = 0
##################################################
# AGPS_CONFIG_INJECT
##################################################
# enable/disable injection of AGPS configurations:
# SUPL_VER
# SUPL_HOST
# SUPL_PORT
# SUPL_MODE
# SUPL_ES
# C2K_HOST
# C2K_PORT
# LPP_PROFILE
# A_GLONASS_POS_PROTOCOL_SELECT
# USE_EMERGENCY_PDN_FOR_EMERGENCY_SUPL
# GPS_LOCK
# 0: disable
# 1: enable
AGPS_CONFIG_INJECT = 1
# AP Coarse Timestamp Uncertainty
##################################################
# default : 10
# or as per clock uncertainty of product
AP_TIMESTAMP_UNCERTAINTY = 10
#####################################
#DR_SYNC Pulse Availability
#####################################
# 0 : DR_SYNC pulse not available (default)
# 1 : DR_SYNC pulse available
DR_SYNC_ENABLED = 0
#####################################
#PPS Device name
#####################################
PPS_DEVICENAME = /dev/pps0
#####################################
#AP Clock Accuracy
#####################################
AP_CLOCK_PPM = 100
#####################################
#MAX ms difference to detect missing pulse
#####################################
MISSING_PULSE_TIME_DELTA = 900
#####################################
#Propagation time uncertainty
#####################################
PROPAGATION_TIME_UNCERTAINTY = 1
2 Likes
Thanks you very much!