@rdl85 said in MMS issues:
@aircooled OK, so you still think it is all in the APN settings? How did you figure out your data was restarting everytime you try and send an MMS? I'd be curious to watch for that on my 3a as well.
At the time the data indicator would actually go dark and then light back up after the failed message appeared. It doesn't seems to happen since the last update.
@rdl85 If it wasn't working in europe I would agree. Also when I try and send an MMS I can watch the data connection reset.
First off I'd like to thank all the developers for the hard work that they've put in to the project.
As an avid supporter of all things FOSS I'd like to say that one of the biggest problems facing wide spread use of UT is the stability on more modern devices. With that said, is there any progress on the issues facing North American users on Halium 9 devices (MMS, network connectivity...)? I for one, long for the day that I can ditch my Nexus 5 and use my Pixel 3a as a daily driver.
Thanks
@rdl85 Thanks. This looks pretty similar to what I've got running here. Now if only someone from europe would post theirs.
@standupmobile I'm getting pretty reliable 4G reception on my phone.
@freefrog They should be similar. Typically android will only have one for both MMS and internet but this doesn't seem to be working on the 3a right now. You can however just make one APN entry for each and just use the same info in both.
@something_wrong I had a similar problem. I flashed android again using the "flash" link and checking force flash all partitions and wipe device in the options (click the pencil icon). That worked for me.
@rdl85 Well that's something. Can you post up your gprs file for me?
@fredldotme
Hey Alfred. If you get the chance I know you're using a 3a.
As this seems to be a problem for us Canadian and American users only, I thought I'd try and troubleshoot as best I can. If someone in europe with working MMS could post up their APN contents from /var/lib/ofono/<id> /gprs , I think it might be a good starting point.
I'm having the same issues. Did you ever get this fixed?
I cannot add any APNs and changing the ones that are there just make the connection flaky. I'm more than willing to put the time in to help fix this if anyone has any ideas where to start.
@dvs said in Mobile stuck at penguin boot image:
After installing UBTouch-jasmine_sprout-05-11-2020 using twrp, I am getting attached image and it is not responding. adb commands not working either.
I don't know about the A2 specifically but for all my devices you need to be running stock Android before installing. I'm guessing since you mentioned TWRP that you are not.
@captaincook Oh apple! I cannot help you there. Sorry. But if you do find a solution be sure to post back here for the next guy looking. You might want the change the title of the post to "Apple email setup" as well.
Good luck
@captaincook said in Email Account Setup:
Dekko2, doesnt work.
What do you mean Dekko2 doesn't work? It works great for me.
@rdl85 Hello, I'm also in Canada (on Fido) and have also had issues with APN settings on the 3a. As far as I can tell the Halium 9 devices seem to have issues with LTE or "Internet and MMS" APN settings. My Nexus 5, which has worked almost flawlessly for over a year only has one APN (Internet and MMS).
My guess is that when registering on the network the phone is not receiving a compatible APN. What I did was to change the seperate MMS and internet APNs and filled them with the same information copied from the one working on my nexus 5.
You can try using the settings from here:
https://www.publicmobile.ca/en/qc/get-help/articles/set-up-data-on-an-android-phone
Fill any fields that you can and change both APNs. Enable them both. Reboot. And let me know if it works.
@darkcoder221 No, sorry. The port is currently in need of some work as the last bootable image failed to wake for phone calls. I am currently unable to put any time into fixing this.
@Lakotaubp I'm actually working on that port, I'm just looking for some help with this problem. If you want to move this to porting that's cool but I don't think I'm going to get much help if this is moved to OT.
I'm running a port on my BLOX2 (one of the many garlic clones) and I'm having an issue where the phone won't sleep. The sleep process gets interrupted constantly and the logs fill up with these messages:
[12099.452698] PM: suspend entry 2020-06-07 04:27:20.935169074 UTC
[12099.458513] PM: Syncing filesystems ... done.
[12099.545409] PM: Preparing system for mem sleep
[12099.712654] Freezing user space processes ...
[12099.726900] PM: Wakeup pending, aborting suspend
[12099.730790] last active wakeup source: eventpoll
[12099.736731] Freezing of tasks aborted after 0.019 seconds
[12099.742112] Restarting tasks ... done.
[12099.759822] cpufreq: Frequency violation fixed for CPU0
[12099.764502] PM: suspend exit 2020-06-07 04:27:21.246965219 UTC
[12099.769904] PM: suspend entry 2020-06-07 04:27:21.252363240 UTC
[12099.775833] PM: Syncing filesystems ... done.
[12099.798209] PM: Preparing system for mem sleep
[12099.966815] Freezing user space processes ... (elapsed 0.012 seconds) done.
[12099.984618] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
[12099.994866] PM: Entering mem sleep
[12099.998247] Suspending console(s) (use no_console_suspend to debug)
[12100.048247] PM: suspend of devices complete after 41.729 msecs
[12100.051479] PM: late suspend of devices complete after 3.219 msecs
[12100.056582] PM: noirq suspend of devices complete after 5.086 msecs
[12100.056597] Disabling non-boot CPUs ...
[12100.103558] Suspended for 0.000 seconds
[12100.103692] Enabling non-boot CPUs ...
[12100.105135] CPU1 is up
[12100.106655] CPU2 is up
[12100.108147] CPU3 is up
[12100.113115] CPU4 is up
[12100.116031] CPU5 is up
[12100.119277] CPU6 is up
[12100.122826] CPU7 is up
[12100.124685] PM: noirq resume of devices complete after 1.607 msecs
[12100.127612] PM: early resume of devices complete after 1.765 msecs
[12100.128949] [04:27:21.775055] [00000039F290EA54] [VosRX] wlan: [E :WDI] WDTS_RxPacketDump RX Data frame is BC
[12100.128968] [04:27:21.775076] [00000039F290EBEE] [VosRX] wlan: [E :WDI] WDTS_RxPacketDump: Data subtype:0 SA:70:4f:57:29:e3:d5 DA:ff:ff:ff:ff:ff:ff
[12100.129037] [04:27:21.775124] [00000039F290EF7F] [VosRX] wlan: [E :HDD] hdd_log_ip_addr: src addr 192:168:1:76
[12100.129050] [04:27:21.775159] [00000039F290F223] [VosRX] wlan: [E :HDD] hdd_log_ip_addr: dst addr 192:168:1:255
[12100.140158] PM: resume of devices complete after 12.535 msecs
[12100.250333] PM: Finishing wakeup.
[12100.253641] Restarting tasks ... done.
[12100.278073] cpufreq: Frequency violation fixed for CPU0
[12100.283431] cpufreq: Frequency violation fixed for CPU4
[12100.287755] PM: suspend exit 2020-06-07 04:27:21.933865740 UTC
Does anyone have any ideas what might be causing this? The battery actually seems to drain quicker this way then when actually using it.
This works as desired on my garlic device (no regressions). Issue #1045 occurs after the hang up of the Bluetooth headset, which I guess is not surprising to anyone.
Hopefully I'll get a chance to try this out on my N5 since I'm having issues with my headset on that device.