It seems that your lognotworking/dmesg is identical with logworking/dmesg.
And make sure apk upgrade -a is run. The latest kernel is 6.6 and yours is 5.17, which is not supported any more.
okay, i just understood that the apk upgrade -a fails on an error, but AFTER doing a very long system modification (i guess its upgrade packages) and then come back to the old kernel.
how could i fix it?
thank youg530fzupgrade2 it work better for qualcomm's cell chip, but the battery icon is still wrong : it's now full red/empty (with discharging even on USB charger) as on previous version it was full of charge (white).
notice that the common user didnt know "apk fix" tool ;)
@lm2lm2, I don't understand if you've made a fresh pmOS installation to g530fz or made an upgrade from an old instalation you've made in past.
@wonderfulShrineMaidenOfParadise, I'm not sure if his still ongoing issues depend on installation could be not fresh (but maybe due to a broken upgrade) and if a new pmOS installation could be solve everything or if it's not needed (especially if he has not experience with that)
Even if the patch from linux kernel mailing list has not yet been merged into upstream, it should be already included in linux-postmarketos-msm8916 kernel fork (!4520 (merged) shows it's currently 6.6).
I read: "Note: For SM-G530FZ (and maybe other variants), make sure you are on a recent firmware version that can boot aarch64 kernels. If lk2nd says ARM64 - unavailable or you're unsure, flash the latest (Android 5) stock firmware with Odin or Heimdall.". So, are you running aarch64 (64-bit) lk2nd kernel release or armv7 (32-bit) lk2nd kernel release?
It seems you can load aarch64 kernels. to be sure, in pmOS, check: uname -m (in linux, I use this command to get kernel arch).
Your lk2nd seems stuck at 0.12.2 version. @wonderfulShrineMaidenOfParadise, grandprime seems supported since 0.12.0, is needed to upgrade to 0.15.0 for some reasons?
apk search linux-postmarketos-msm8916 <= give no results
Sorry, I've made a mistake. Check: apk search linux-postmarketos-qcom-msm8916.
grandprime seems supported since 0.12.0, is needed to upgrade to 0.15.0 for some reasons?
With official linux-postmarketos-qcom-msm8916, no. It's fine with old lk2nd >=0.12.0.
@lm2lm2 @cristian_ci About charger and battery, in fact it's a device tree bug in official linux-postmarketos-qcom-msm8916. It's hard to review the patches but I will try my best to send it to upstream mailing lists directly so it might get applied before 2030.
TL;DR There is nothing you can or need to do for now, unless you feel like to try my postmarketOS fork, fumOS.
Sorry for confusing. I thought that I have made it clear. You cannot do anything for it without fixing the kernel device tree, and I cannot provide any more helps in this thread.
@wonderfulShrineMaidenOfParadise, it seems upstream patch has been accepted upstream and also initial device tree for grandprime (g530fz) has landed into torvalds tree. I guess this is not a blocker anymore but likely it needs waiting for v6.9. Am I wrong?
Note that !4835 renames the device from samsung-gprimeltexx to samsung-grandprimelte, and the support for former one, samsung-gprimeltexx will be deprecated.
I was already talking about that new battery issue:
but the battery icon is still wrong : it's now full red/empty (with discharging even on USB charger) as on previous version it was full of charge (white).
Due to what you previously said, it appeared as this new issue is related to device tree and the changes you made. If you mean, instead, that this new issue is due to device naming (as for 4835), I didn't know. If lm2lm2 says that the new issue disappears after applying 4835, then lm2lm2's battery issue is definitively solved. So, let's wait that 4835 is merged and for lm2lm2's feedback.
P.S. since this is just an issue and not a MR, single threads cannot be closed.
Nothing will be fixed in !4835 by the way, I am sorry but I have NOT claimed to fix anything yet, so try not to expect anything, untill there is a clear statement announced.
The battery/charger/PMIC/whatever is a new issue, which deserves a new issue thread opened, rather than sticking here. That's how GitLab is used.
I would like to help, and solve your issues, but if you don't need any help, please reject the invitation. Ignoring would cause more misunderstanding. Hope that I don't need to repeat this for 5th time.
@lm2lm2, if you're still interested to that and when you've time, please close this issue (2539) and open a new issue related to the new battery issue or consider joining #msm8916:postmarketos.org chat (as explained above) to get more details.