-
Status as of 2022-08-18:
- Actors
- Manual Brightness: Works
- Torchlight: Works
- Notification Led: Works
- Vibration: Works
- Camera
- Flashlight: Works
- Photo: Works
- Video: Works but A/V desync, https://gitlab.com/ubports/development/core/qtubuntu-camera/-/issues/22
- Switching Camera: Works
- Cellular
- Carrier Info: Works
- Data Connection: Works
- Calls: Works
- DualSim: Works but only sim 1 can 3G/4G
- MMS: Not tested
- SIM card pin unlock: Not tested
- SMS: Works
- Audio Routings: Works
- Voice Call: Works
- Volume Control: Works
- Endurance
- Battery Lifetime Test: Can idle more than 24 hours with one sim
- No Reboot Test: Been working on it rather actively, have not had a chance to not reboot it for more than 7 days
- GPU
- UI Boots: Works
- Video Acceleration: Works
- Misc
- Anbox Patches: Anbox started crashing with a recent mir change, otherwise does not spawn windows after app launch
- Apparmor Patches: Applied
- Battery Percentage: Works
- Offline Charging: Works
- Online Charging: Works
- Recovery Image: Ready
- Factory Reset: Works
- RtcTime: Works
- SDCard: Works
- Shutdown: Works
- Wireless Charging: Works
- Wireless External Monitor: No idea how to use that with ubports
- Waydroid: No official halium 11 support from Waydroid currently
- Network
- Bluetooth: Works, sound devices might require fiddling with pactl however
- Flight Mode: Works
- Hotspot: Works
- NFC: Not tested
- WIFI: Works
- Sensors
- Auto Brightness: Works
- Fingerprint Sensor: Works on viper sensor, egis sensor not tested
- GPS: Works
- Proximity: Works
- Rotation: Works
- Touchscreen: Works
- Sound
- Earphones: Works
- Loud Speaker: Works
- Microphone: Works
- Volume Control: Works
- USB
- MTP: Works
- ADB: Works
- Wired External Monitor: Not supported by hardware
- Actors
-
I installed and updated ut using your instructions and it mostly works as a charm, if it's important for testing I can reflash your image without the updates just let me know. Tbh I'm pretty much a newbie but I can at least help with testing
-
@katharinechui I have been using the S7 (herolte) in parallell with my work phone. I have a twin SIM. Here is what I have noticed about the cellular functionality.
SIM card pin unlock works consistently.
MMS works, but not consistently. Occasionally, I have received this message:
"Could not fetch the MMS message. Maybe the MMS settings are incorrect or cellular data is off?"
It is possible that cellular data was in fact off in one case, but even though it is now on and I have also rebooted the phone since, the 'download' button in the same message is inactive. It is also worth noting that I have successfully received several MMS messages from the same phone number since this. (Not sure if any of these might possibly be the original ones that triggered the error message?)Another thing I have noticed is that if I leave the phone on overnight, something happens to the cellular connection. In this situation I have tried twice to call the same person. It looks as though the call is going through at first, but then it is suddenly cut off. At this point I have not heard any tone signaling that the phone is ringing at the other end. Also, the other party has confirmed that their phone rang, so something still worked. When they called back, though, the call did not go through on this device, but only on the other one (with the twin SIM) which runs Android.
After rebooting the phone, things were back to normal.
I will continue trying it out and post anything more info or other issues I come across.
All in all a very impressive port! Good work!
-
@katharinechui I have now confirmed that I can connect my device to my car via bluetooth without any additional steps. Receiving a call seemed to work well also. The sound was a bit choppy at first, but this might have been caused by the caller being in a place where the cellular reception was not ideal.
-
@aribk If you come across logs for call issues after long idling, please add them here
https://gitlab.com/ubports/porting/community-ports/android11/samsung-galaxy-s7/samsung-exynos8890/-/issues/2
(pulse, ofono, halium rild, or any logs you think related)For mms, please add logs here if possible
https://gitlab.com/ubports/porting/community-ports/android11/samsung-galaxy-s7/samsung-exynos8890/-/issues/1
(ofono, halium rild, or any logs you think related) -
Hi @katharinechui if everything works as i hope i might get my hand on a 7edge and am interested installing UT on it, hows the progress on the device and what prerequisite do i need to get it started once i get my hand on one… not sure if there is a snapdragon and exynox versions do i need to focus on one variant if available? Thank you and keep up the great work.
-
@a-sinner here is your answer :
@katharinechui said in Samsung Galaxy S7/S7 Edge (exynos:herolte/hero2lte) call for testing:
Hi, I am a Galaxy S7 exynos owner and I have been working on a halium 11 based port for both the exynos S7 and S7 Edge.
-
@keneda join forces with @katharinechui if you haven’t yet and build it together would be great to see it working on a newer port …
-
https://github.com/Kethen/waydroid_build/releases
for those who wish to attempt waydroid, here are some instructions and system.img vendor.img for h11
note that memory might be a bit tight until the next OTA which enables zram
-
Thanks @katharinechui , amazing work! I will definitely try back home in few weeks, I have two devices and hope than one will be using
/dev/sefp0.Side question: I also tried it with @aribk a while ago without much success, our port was based an Halium7/LineageOS 14 and I spent hours trying to find an issue in the image format: the camera was able to do A/B/C vs the format expected by the camera app being X/Y/Z. Did you encountered such thing? I still wonder what was the solution
-
@oliv I have no idea what is A/B/C and X/Y/Z, I didn't have to investigate much into the camera because it pretty much just worked with the LineageOS blobs from https://github.com/8890q/proprietary_vendor_samsung/tree/lineage-18.1, except https://gitlab.com/ubports/development/core/qtubuntu-camera/-/issues/22 but that seems to be related to how UT starts audio and video recording instead
camera also just works on waydroid
-
Hi,
first of all thank you for your work, seems a difficult task for being only you working on this port.
I'm an owner of galaxy exynos too, only that mine is hero2lte, I would like to help in the development of this, if you need help with testing specific things I'm really interested. Although I'm some kind of a newbie regarding Android stuff, but hey this isn't Android but Linux!, despite that I'm also a Linux poweruser (they call it like this
) and I think I can do at least something. Anyway... I'm more than willing to help, just please let me know.Cheers
P.S. forgive my english, is not my native language
-
Hi,
I'm a galaxy S7 Edge (Exynos) user. I recentlyported it toinstallled Ubuntu 20.04 on it. I can assist you if something needs to be tested in the s7 edge variant. -
I'm considering getting a S7 or S7 Edge as a second UT phone (it checks a lot of boxes for me). Is there any advantage/disadvantage selecting the S7E over a regular S7 (or vice versa)?
-
@ubuntumale The s7e screen is slightly better (in my view) but both are much the same. They are both prone to screenburn, but that probably stems from usage and being so popular as a phone (I see a lot of second hand ones).
If you get one make sure screenburn is limited, the screen doesn't go black randomly (internal issue that requires disassembly to fully repair) and the battery is good - UT is a battery drainer on a lot of devices and a badly used battery will make it worse.
-
I have installed 20.04 on my new old herolte device. I might find some time if I can help testing some thing. Experienced Linux/Python user. I would be interested in wireless screen.
-
@aribk said in Samsung Galaxy S7/S7 Edge (exynos:herolte/hero2lte) call for testing:
"Could not fetch the MMS message. Maybe the MMS settings are incorrect or cellular data is off?"
I am having this problem on my recently install Ubuntu Touch, on my fairphone 4. Is there a fix for this yet?
-
I know this is old, but I'm available for testing!
-
A couple of things:
There seem to be a sequence of adding/removing fingerprints that leaves the unlock screen funky, so no pin entry keyboard is shown. I don't know how to unlock my phone now. Fingerprint unlock seems to work 'for a while' and then does not. It is a phone for playing, so I'll end up resetting it again. I'll try a usb keyboard before resetting.The latest ota upgrade left the phone on the Samsung banner screen. I re-installed from zero to recover it (recovery mode worked, so other strategies might have worked)
-
K Keneda moved this topic from Devices on
