Why not restore them if they exist? You go out of your way to back them up, and then don't restore them? If there were files, you're not restoring them on uninstall. That's a change.
I also see you never addressed one key point of what I was saying. Your description (both here and in the deb) says you're creating cgroups for the desktop and for apps, when in fact you're doing neither. They only cgroup you're making is for bash and shell scripts using bash. The desktop and user apps are already in a cgroup, created by Nokia as part of the kernel compile. Can you please address why you're lying about what you're doing?
The kernel already does that if there's a lockup, even if you default it to something else. If you load a profile as default, and the system reboots twice in the span of a couple minutes, the kernel automatically rejects loading the default config and uses the built-in Nokia-based values (250-600, high-voltage). That's been in there since Titan's kernels, well before KP. The fact that you don't know this, shows how little you know about this whole process.
Again, you show you have no idea what you're talking about. A missing default kernel profile will never cause a reboot loop. A missing module or kernel file may, but a profile never will. It will simply stick with the built-in Nokia defaults if the profile it's instructed to read is not present, or is corrupt in some way.
Nokia, as part of the phone app, triggers the phone app to get real-time priority, and locks the kernel at a set speed (600 as I recall). At that speed, the phone app takes about 60% of the CPU and allows enough background time for apps to continue to function if needed. I made plenty of calls using the stock 250-600 kernel and noticed no quality issues. If you're seeing issues, it's probably because you're either running something highly CPU intensive in the background, or because you've installed a speedpatch that's screwing around with cgroups and letting shell scripts take higher priority than they should!
Also, you again show ignorance on your own scripts. In the postinst for batterypatch, you check for version 42, 47, and 48 of KP, and copy the config settings from /opt/dbus-scripts/ to /usr/share/kernel-power-settings. The config files put in place for those kernels is: call: 750-850 non-call:250-805 sleep:125-600 (all with SR2 set) For all other kernels, the files used are call: 720-850 non-call:250-805 sleep:125-600 (all with SR1 & 2 set!)
Also, for all but 42, 47, and 48, you're enabling SR1, another problem. You do know that with K49 (and 43, 44, 45, & 46) that SR1 is not always stable, right? The patch to handle that is slated for K50, and only those doing kernel testing have a version of K49 that might be recent enough to allow this in a stable way. Did you know SR1 is also never stable for 125Mhz, since Nokia never enabled it and never setup the e-fuse stuff for that? Yet you tinker with it.
The biggest issues are the crazy (7X0-850) overclocking, use of SR1, and use of unstable 125Mhz. If you took those issues out, it wouldn't be all that bad. But those alone, yet alone staked with other mods, make the whole deck of cards wobbly.
maybe mohammad is karam evil twin..dont know and dont care...just want a solution to get rid of these patches efectively without reflash...
ps Karam: you need to sort out your Karma. Single figures makes you look like a proper shady character!