Endrom

joined 1 year ago
[–] Endrom@lemmy.ml 1 points 6 months ago

We don't block capable devices, the problem is that not all VoLTE configurations work. Without testing device we can't know if it will work with our network and usually brands with biggest market share send their prototypes and try to fix what is possible from their side and we from our side.

[–] Endrom@lemmy.ml 1 points 6 months ago (2 children)

From my experience working for mobile carrier (not USA), I would recommend to contact your carrier to know if they support VoLTE for all capable devices or only for specific brands.

[–] Endrom@lemmy.ml 2 points 1 year ago

I use total commander and x-plore. I would use only TC but sometimes i can't overwrite files, while x-plore can overwrite most of the time. I would not recommend x-plore becouse it has ads (with adaway i don't see) and is not opensource (i think).

[–] Endrom@lemmy.ml 2 points 1 year ago

Never liked it on pc, but I have it on phone and love the ability to have 2 dirs open at the same time.

[–] Endrom@lemmy.ml 1 points 1 year ago (1 children)

I have old backup from swift. I tried uninstalling magisk but nothing chanchged.

 

I updated magisk and now my phone is stuck in bootloop. I have backup of internal storage but I need to back up few apps. I tried adb but i get message "Now unlock your device and confirm the backup operation...". Currently I am trying twrp backup for data. does anyone know a tool or command to get apps with their data?

Phone: Poco X3 NFC

OS : xiaomi.eu miui 14

[–] Endrom@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

It probably happened when I was messing with SSDs. I wanted a smaller one to be root and a bigger one as home.

Edit: Kind of happy that i managed to break something and fix it.

[–] Endrom@lemmy.ml 2 points 1 year ago (3 children)

I managed to find a problem and fix it. The problem was that /etc/kernel/cmd had the wrong UUID. Thanks for giving advice about initrd and bootloader reconfiguring, might not have found a solution without it.

[–] Endrom@lemmy.ml 1 points 1 year ago

I think I found what changes root UUID. When I used dracut-rebuild all entrie UUIDs changed to the wrong one. Now I have to find how to stop that.

[–] Endrom@lemmy.ml 2 points 1 year ago (2 children)

I used gparted, blkid, checked fstab and by-uuid dir and no partition or drive had that UUID.

[–] Endrom@lemmy.ml 0 points 1 year ago

Will have a look.

[–] Endrom@lemmy.ml 1 points 1 year ago (4 children)

I used arch-chroot. I mounted efi to efi dir with mount and used mount -o subvol=@subvolname to sub vol dir. Just incase i will reinstall nvidia drivers when booted normally. I will read about initrd. Thanks for all the info.

 

I suddenly got the same problem in /efi/loader/entries all conf files reverted to previous uuid (first post ). To change uuid I just edited all conf files with the correct uuid for root.

I don't know if manually changing was correct or if I should use some sort command.

Bootctl status

UUID in status is wrong.

I have no idea what is reverting UUID back to the wrong one after updating system.

I could just reinstall but if possible I would like to try to fix this and learn.

Edit: Problem was that in /etc/kernel/cmdline had wrong UUID. Changed it to correct one and dracut-rebuild uses correct UUID.

 

I am getting "A start job is running for /dev/disk/by-uuid/8469fa80-.... No limit"

It started after system update. During update there was conflict with nvidia and nvidia-dkms. Nvidia-dkms was removed.

From live iso I looked at dev/disk/by-uuid and my fstab but there is nothing with uuid "8469fa80..."

My os is endevouros. And file system is btrfs.

Blkid also didnt show anything with that uuid.

Edit: I also tried from live iso to install nvidia-dkms and uninstall nvidia but nothing changed.

view more: next ›