Xperia 10 II bugs

i’m on 4.1 with x10ii
i only this week retired my xperia x

1 Like

The Xperia 10 II dual sim has a bug where the sim 1 tray can accept and make calls but cannot accept data. For example, can make calls, but can’t recieve or send emails. The data does not work.

I cannot confirm this. Do you have SIM in both places? I have only one SIM in the dual SIM, but the first one works fine for mobile and calls.

Just one sim. The other slot is used by an SD card.
The weird situation is that the sim on the sim 2 position works very well.

Is in the sim 1 tray that the data connection does not work.

I remember a similar problem with the Jolla C or the XA2 in the early days, but I don’t know if they have been solved.

So, they may solve it for the next update.

Finally a got a solution through shortcuts menu. The data convection was disabled. And I could only enable by shortcuts menu. Even though if I disable sim 2 , I lose data connection on sim 1.
The bug is that through configuration app it is impossible to enable data, and only through the shortcuts menu. And the second bug I can see is that if you disable sim 2 you lose data connection on sim 1

It takes a good while after the apparent installation for things to settle down. It could also take a reboot or two for it to function properly. (Cloudy undocumented memories.)

This bug occurs when you install an Android application (usually Here we go) before you install Android support. Fixing is easy: remove all Android applications then install them again. You might need to remove Android support, too.

2 Likes

I can confirm those very two issues happening for me as well.
I’m on 4.2.0.21

Most peculiar. How could we check the wifi country setting? I mean, there’s the usual Linux commands for it, but does it count for SoC’s in phones?

Edit: The access point also should have a country setting :slight_smile:

When I check which cores are running (e.g. with htop), it always shows all 8 cores are on. This is despite the fact that the load average is usually quite low (around 3), so it definitely doesn’t need this horsepower. My old XA2 Plus didn’t do this, and also my wife’s 10 does not. Obviously, battery life isn’t great this way.

I have reflashed SFOS to make sure it’s not something I installed. I just got this phone yesterday (a “new” secondhand device for me). Only thing I did was to update with pkcon and install htop to check.

I do see this in the log repeatedly, not sure if it’s relevant:

[  584.833648] Freezing user space processes ... (elapsed 0.034 seconds) done.
[  584.868188] OOM killer disabled.
[  584.868191] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
[  584.872202] Suspending console(s) (use no_console_suspend to debug)
[  584.905923] Disabling non-boot CPUs ...
[  584.908398] CPU1: shutdown
[  584.913637] CPU2: shutdown
[  584.919027] CPU3: shutdown
[  584.923651] CPU4: shutdown
[  584.927523] CPU5: shutdown
[  584.931427] CPU6: shutdown
[  584.935013] CPU7: shutdown
[  584.938707] suspend ns:     584938696744	suspend cycles:      23409443172
[  584.938696] resume cycles:      23411635310
[  584.939621] Enabling non-boot CPUs ...
[  584.941739]  cache: parent cpu1 should not be sleeping
[  584.942400] CPU1 is up
[  584.943925]  cache: parent cpu2 should not be sleeping
[  584.944621] CPU2 is up
[  584.946204]  cache: parent cpu3 should not be sleeping
[  584.946905] CPU3 is up
[  584.948153] arch_timer: CPU4: Trapping CNTVCT access
[  584.948669]  cache: parent cpu4 should not be sleeping
[  584.949371] CPU4 is up
[  584.950125] arch_timer: CPU5: Trapping CNTVCT access
[  584.950479]  cache: parent cpu5 should not be sleeping
[  584.951024] CPU5 is up
[  584.951835] arch_timer: CPU6: Trapping CNTVCT access
[  584.952149]  cache: parent cpu6 should not be sleeping
[  584.952794] CPU6 is up
[  584.953513] arch_timer: CPU7: Trapping CNTVCT access
[  584.953842]  cache: parent cpu7 should not be sleeping
[  584.954995] CPU7 is up
[  584.995623] OOM killer enabled.
[  584.995627] Restarting tasks ... done.
[  585.016702] PM: PM: suspend exit 2022-09-17 18:29:54.113981794 UTC
[  585.016706] PM: suspend exit
[  585.065376] ## mmc1: mmc_gpio_set_uim2_en: gpio=101 value=1

Is this just me, or is on-demand core activation for this device broken? I’m running 4.4.0.68

3 Likes

Hi

another issue on Xperia 10 II dual sim.
I am on 4.4.0.72. For some reason (error while trying to install opengapps on the android container) I had to reflash. After that, no compas, no accelerometer, no steps counter etc.

Has anyone

  • Met that issue ?
  • has any idea how to resolve ?
    would reinstalling Android then reflashing help ?

Regards
Dominique

If you reflash your device, there won’t be any extra apps on your device. Flashing.your device means installing a vanilla image containing only the preinstalled apps.

So: No bug.

IIRC step counter isn’t implemented in SFOS side, but compass for sure is, and accelerometer should work too.

Do the sensors work in CSD tool? Click five time the value of Settings > About Device > Build to open it.

1 Like

After three years since Sony Xperia 10 II debuted in the Sony’s Open Devices program, Sailfish OS works well on this beautyful piece of hardware, IMHO,

However, some issues are still bothering the user experience but workaorounds are available and therefore is supposed a solution too in the future. I suggest to read this post:

I hope this helps, R-

Stop promoting your thread all over the place.

7 Likes

Please, keep low the tones. I have simple informed those are interested in the topic. If you have objections about the workarouds that I have proposed and how to improve them or find a solution, I will be happy to read your contribution.

Got this bug

Xperia10II-DualSIM lipstick[5758]: [D] :50 - Failed to obtai
n Foreca token. HTTP error code: 0
Jun 13 20:20:30 Xperia10II-DualSIM lipstick[5758]: [D] onStatusChanged:107 -
WeatherForecastModel - could not obtain forecast weather data Espoo 1006601
58
Jun 13 20:20:31

how can this be fixed?it appears to happen very often, and battery life has decreased too.

Seems to be again the case today