so we can't fix those broken symlinks? we just leave it like that then?
It's not that you can't fix those broken symlinks but why would you want to? Would you get any extra benefit from fixing each and every single one of them by hand? Do you know how udev works exactly? Has there been any proven cases of fixed broken symlinks being useful? Did you lose functionality from your device just because those links were broken?
These are in /dev/.udev directory not /dev/udev directory (note the period mark before the wrods udev, hence hidden directory). Apart from that I'm guessing most of the broken symlinks normally link to sysfs and other parts of devpts.
I would not go about fixing these broken symlinks as udev marked them as failed, etc and fixing them may cause your device to bootloop or do things you wouldn't expect.
i finally found out which program that cause this many broken symlinks on my device...it is Backupmenu....
i know this cause after i re-flash my device,there is no broken smylinks in /dev/.udev so after each apps/program i install i check the folder to make sure which apps/programs causing the broken symlinks....backupmenu is the last thing i install so the broken symlinks appears after normal reboot (i don't open backupmenu on reboot)...
to anyone who have backupmenu on their device please confirm if there is some broken symlinks on /dev/.udev directory....
well i've noticed when i open the QCPUFrequency my CPU temperature is unknown and i see one of the broken symlink is temp so maybe that has something to do with my cpu temperature being unknown?
