Going to try and make this short and adequately detailed:
I've not worked on or directly tampered with ROMs for about 2 years (though I did with individual apps) now and when I felt like working an OxygenOS optimized & stripped 'base ROM' (with GApps, Swiftkey etc. properly exterminated from the ROM) to allow other devs (and myself) to make ROMs on top of (lack of OOS based ROMs makes me sad, even if CM is seen by most as superior). I have figured out a problem which has never occurred to me before in any of my devices or the experience I had a while ago.
I find that when I pull /system from the stock or modified stock OxygenOS ROM that WLAN/WiFi modules aren't being properly pulled for me. This is true for me both if I am pulling with the OS properly booted and functioning or if I am pulling when being and recovery.
This is a problem because I have to add them manually each time around I pull /system from my device to the dump which simply is inconvenient and wastes time for me.
Of course my other alternative is to take a nandroid and extract from nandroid but I don't know how to decompress backups made with TWRP 2.8+ with Windows (normally I'd run a unixlike system for work but I had to temporarily move Arch off my USB drive which I needed for an OS installation onto another system). (The ext4 backups don't open in the tools I traditionally used.)
(In case you are asking, I am running adbd as root in order to do the operations, I won't forget that after such a while.)
Oh and by the way, the ROM base itself otherwise once the missing libs are added runs fine, I've tested it already. I've still to zipalign my apps and optimize the images (JPGs & PNGs) inside the system apps as well as add some of my battery optimisations into the ROM (w/ default kernel config --> I'm shipping Boeffla w/ its config app given all other kernels are dead ATM, also shipping the SD810 tweaks). SuperSU, busybox and other common tools are obviously already integrated. In fact I'm posting from it right now though I'm in a rush typing this up because the frustration I had (trying to figure out why WLAN wasn't initially working and then not figuring out why the modules weren't pulling) has now reduced me to 4h of sleep :/.
Sent from my ONE A2003 using Tapatalk
I've not worked on or directly tampered with ROMs for about 2 years (though I did with individual apps) now and when I felt like working an OxygenOS optimized & stripped 'base ROM' (with GApps, Swiftkey etc. properly exterminated from the ROM) to allow other devs (and myself) to make ROMs on top of (lack of OOS based ROMs makes me sad, even if CM is seen by most as superior). I have figured out a problem which has never occurred to me before in any of my devices or the experience I had a while ago.
I find that when I pull /system from the stock or modified stock OxygenOS ROM that WLAN/WiFi modules aren't being properly pulled for me. This is true for me both if I am pulling with the OS properly booted and functioning or if I am pulling when being and recovery.
This is a problem because I have to add them manually each time around I pull /system from my device to the dump which simply is inconvenient and wastes time for me.
Of course my other alternative is to take a nandroid and extract from nandroid but I don't know how to decompress backups made with TWRP 2.8+ with Windows (normally I'd run a unixlike system for work but I had to temporarily move Arch off my USB drive which I needed for an OS installation onto another system). (The ext4 backups don't open in the tools I traditionally used.)
(In case you are asking, I am running adbd as root in order to do the operations, I won't forget that after such a while.)
Oh and by the way, the ROM base itself otherwise once the missing libs are added runs fine, I've tested it already. I've still to zipalign my apps and optimize the images (JPGs & PNGs) inside the system apps as well as add some of my battery optimisations into the ROM (w/ default kernel config --> I'm shipping Boeffla w/ its config app given all other kernels are dead ATM, also shipping the SD810 tweaks). SuperSU, busybox and other common tools are obviously already integrated. In fact I'm posting from it right now though I'm in a rush typing this up because the frustration I had (trying to figure out why WLAN wasn't initially working and then not figuring out why the modules weren't pulling) has now reduced me to 4h of sleep :/.
Sent from my ONE A2003 using Tapatalk
from xda-developers http://ift.tt/1YfnEJo
via IFTTT
No comments:
Post a Comment