Sony Xperia 10 (kirin)
-
@hengyedev Good time of day.
I have a Sony I4113 does not work cellular connection.
How do I fix this? -
This post is deleted! -
@zentrr my cellular works with this modification:
by ssh or directly on your terminal
change your filesystem permission withsudo mount -o remount,rw /
modify with vi le file /etc/ofono/ril_subscription.conf by
sudo vi /etc/ofono/ril_subscription.conf
[Settings] #EmptyConfig=false #Identity=radio:radio #3GLTEHandover=true #SetRadioCapability=auto SetRadioCapability=off emptyPinQuery=false radioPowerCycle=false confirmRadioPowerOn=false useDataProfiles=true [ril_0] transport=binder:name=slot1 name=slot1 [ril_1] transport=binder:name=slot2 name=slot2
and main.conf
sudo vi /etc/ofono/main.conf
[ModemManager] AutoSelectDataSim=always
and reboot and phone
-
@golliath51 main.conf had a bug, in the latest rootfs this change should not be necessary anymore
-
After having tested twice, when I do above operation my bluetooth indicator disappears and I can't active my bluetooth.
Anyone have any idea of link between these conf files and bluetooth? Or how to reactivate my bluetooth. -
I have been playing around with the port on the I3223 and it is working pretty good! A few things I am still trying to get working, like access the phone with adb when booted into ubuntu-touch. It might be related to the other issue I'm looking into, that charging isn't working either. If you plug in the phone while off, it doesn't show a charge screen and instead just reboots. If you plug in the phone while on, it doesn't indicate that it is charging.
Also I found that the mod from golliath51 is also necessary for single sim 10 Plus models to use cellular, just omit the slot2 parts. -
@golliath51 To enable bluetooth:
sduo restart bluebinder
-
@hengyedev it's works, thank you.
Do you have tested the bluetooth with headphone or car bluetooth. Because the sound works but the commands doenst work (next, vol+/-, play or ||)?
And you can add gps works in your port, i use all day. But the gps init is slow. May be the agps data doesnt work. -
@golliath51 Commands don't work for me neither. GPS is probably because there is no carrier acceleration in ubuntu touch.
-
@hengyedev some MMS doesnt work and i can add only by files folder but no picture or camera folder. May be change the permitions?
-
@hengyedev i have receive an update of UT by OTA. Have you tested? Is it works? How i install this update, in telegram he talk to UT recovery but it doenst work for me.
-
I seem to be having quite a different experience with the build than is stated at the start of this thread. So rather than making a million different posts, I have instead compiled a similar status list. I hope this can help the developer(s) to improve this port of Ubuntu Touch.
I am running a I3113 model in Britain (if that makes any difference). These results are only from a couple of days of running the OS.
Working
• Actors: Manual brightness
• Camera: Photo
• Camera: Switch between back and front camera
• Endurance: Battery lifetime > 24h from 100%
• GPU: Boot into UI
• Lights
• Misc: Battery percentage
• Misc: Offline charging
• Misc: Online charging
• Misc: Shutdown / Reboot
• Network: Flight mode
• Network: WiFi
• Sensors: Rotation
• Sensors: Touchscreen
• Sound: Earphones
• Sound: Loudspeaker
• Sound: Microphone
• Sound: Volume control
• TorchUntested
• Endurance: No reboot needed for 1 week
• GPU: Hardware video decoding
• Misc: Reset to factory defaults
• Misc: RTC time is used after reboot
• Misc: SD card detection and access - only for devices that support it
• Network: Hotspot
• Sensors: GPSNot Working
• Actors: Vibration
• Battery charging indicator
• Camera: Video
• Cellular: Carrier info, signal strength
• Cellular: Data connection
• Cellular: Incoming, outgoing calls
• Cellular: MMS in, out
• Cellular: PIN unlock
• Cellular: SMS in, out
• Cellular: Change audio routings
• Cellular: Voice in calls
• Network: Bluetooth
• Sensors: Automatic brightness
• Sensors: Fingerprint reader
• Battery indicator when charging
• Libertine
• USB: MTP accessIt can't seem to detect my SIM card (which is working, as I have tested the SIM in other phones). Could anyone help me to get the phone to recognise the SIM card, I'm not actually sure how to get to SIM settings, and only know that it doesn't detect it from the Phone app.
I hope this information helps!
-
@adlinux try goliath51's config change to get SIM working.
-
@golliath51 there's no android9 recovery for this device currently.
-
@hengyedev Thanks, I'll give it a go!
I do have another question though: When I followed the initial installation guide you posted (it was very useful by the way, thank you) you said to flash the latest flashable artefacts. I chose to flash the one numbered as #1012205941 as it is the latest one that is just labelled 'flashable'.
However, there do appear to be more recent versions. I just wanted to ask what some of the terms used mean.
The latest version as of today is #1033922516, which is labelled as 'devel-flashable_mermaid'. I assume 'devel' is short for 'development', but what are you referring to when you say 'mermaid'? Or 'pioneer'? Which I have seen in other builds?
-
@adlinux In file deviceinfo_{version} you can check to what belongs. I have I4113 (dual sim). For Xperia 10 flash devel-flashable ( https://gitlab.com/ubports/community-ports/android9/sony-xperia-10/sony-kirin/-/jobs/1033922508/artifacts/download)
For cellular and bluetooth to work you need to apply mentoined above modifications.
-
Hello.
I would like to have ubuntu touch on my Sony Xperia 10 (I4113). But my first attempt was not successful. After rebooting there was only Sony logo on the screen and the device does not accept any button touch. Fortunately, I had another attempt. I was successful with flashing back Android 9 on the phone. So, I decided ask for an assistance here. Could anyone explaine to me where I made any mistake?
My process: 1. Downloading I4113_StoreFront_1319-3402_53.0.A.6.92_R1A from XperiFirm 2. Flashing ROM by newflaher. (I use newflasher, because Flastool had warn message: No partition delivery included“) 3. Unlocking bootloader (following steps on Sony websites) 4. Downloading latest artifacts devel-flashable_mermaid 5. Formating user data (fastboot format:ext4 userdata) 6. Going to TWRP (fastboot boot twrp.img) 7. Choosing the A slot 8. Flashing Ubuntu (fastboot flash boot_a boot.img and fastboot flash system_a system.img) 9. Rebooting (fastboot reboot)
and there was only Sony logo on the screen as I wrote before.
Do I have wrong Android 9 ROM? Is it necessary to delete all .ta files from Android ROM when I use newflasher (as I saw on youtube where someone showed how to fix „No partition delivery included“ error on Flashtool. He deleted all .ta files and used newflasher)? Or do I have an error on any command? Or Do I miss something else?
-
@becherekmg It seems that removing .ta files helps. Now ubuntu starts running. But when I want to select my native language, the screen stucks at grey color. I suppose I did not flash ubuntu correctly. Which mode is necessary? For boot.img fastboot mode I suppose. But for system.img? I used fastboot mode too, because flash mode ends with error (command not authenticated), but fastboot mode has 5 steps only whereas flash mode has 24 steps
-
@becherekmg Please look on my comment above. Check deviceinfo_{version} file. Will tell you what artifacts use. I your case download devel-flashable. You are flashing wrong and thats why u see gray screen.
kirin - Xperia 10
mermaid - Xperia 10 Plus
pioneer - Xperia XA2 -
@akikyo Thanks. That's it. I have flashed ubuntu successfully now