• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [LINARO] AWEstruck v1.04 12/14/14 | [3.4.107] v1.05b6 5/30/15

I'm under the impression that flashing kernels over each other is a bad idea if they're not the same size. I'm having awkward problems that are occurring after I have flashed multiple kernels one over the other. At first i started with RBs which worked excellent until I tried to flash back to it after flashing a couple of Spocks, ...now it sticks to whatever Max frequency I have it set to and I'm on Smartass v2 and everything worked successfully until I did multiple flashes. Is it possible that some code gets left behind in the boot partition and screws with things?
 
DsyMnapTic said:
I'm under the impression that flashing kernels over each other is a bad idea if they're not the same size. I'm having awkward problems that are occurring after I have flashed multiple kernels one over the other. At first i started with RBs which worked excellent until I tried to flash back to it after flashing a couple of Spocks, ...now it sticks to whatever Max frequency I have it set to and I'm on Smartass v2 and everything worked successfully until I did multiple flashes. Is it possible that some code gets left behind in the boot partition and screws with things?
Click to expand...
U need to force stop and clear app data of whatever app ur using for control
 
brittnearl said:
U need to force stop and clear app data of whatever app ur using for control
Click to expand...

Ahhh, that makes sense. I didn't do that.

Right on, thanks. I've been using android tuner, it's great. Should I usually keep MP decision on or off?...I've been reading a lot about you guys discussing it and yet i don't know whether it's better to have on or off.
 
DsyMnapTic said:
Ahhh, that makes sense. I didn't do that.

Right on, thanks. I've been using android tuner, it's great. Should I usually keep MP decision on or off?...I've been reading a lot about you guys discussing it and yet i don't know whether it's better to have on or off.
Click to expand...
My personal preference is off, as i have disabled it in my rom, spocks kernel enables it kernel side for oc stability reasons and is not controllable, i feel u loose some performance and gain batt life on and the opposite is true off, although i havent seen much difference in batt personally
 
brittnearl said:
My personal preference is off, as i have disabled it in my rom, spocks kernel enables it kernel side for oc stability reasons and is not controllable, i feel u loose some performance and gain batt life on and the opposite is true off, although i havent seen much difference in batt personally
Click to expand...

The kernel side mpdecision is controllable through android tuner or trickster mod, hence my recommendations in op. So is the thermal control.
 
spock1104 said:
The kernel side mpdecision is controllable through android tuner or trickster mod, hence my recommendations in op. So is the thermal control.
Click to expand...

Any chance you could add smartAssV2 governor to your kernel. I think i like it the best and I usually get great battery from it. It appears to be the only governor not working properly on RBs kernel
 
DsyMnapTic said:
Any chance you could add smartAssV2 governor to your kernel. I think i like it the best and I usually get great battery from it. It appears to be the only governor not working properly on RBs kernel
Click to expand...

I can look into it after I'm done with the Wi-Fi rework. I just don't want to go bloating the kernel with a lot of governors.
 
Has anyone been clean flashing the latest betas to give better reference?
For example (different phone, same principle):
Recently I was having issues with my GNex on Dirty V so I flashed Fancy over it not thinking any issue would arise since it installed a new ramdisk (I believe were still on the same as before, but hear me out) I started having problems all over the place. To fix it I dirty flashed my ROM and the kernel on top of it in TWRP together and it resolved the problems.
Just a thought...
 
dragonhart6505 said:
Has anyone been clean flashing the latest betas to give better reference?
For example (different phone, same principle):
Recently I was having issues with my GNex on Dirty V so I flashed Fancy over it not thinking any issue would arise since it installed a new ramdisk (I believe were still on the same as before, but hear me out) I started having problems all over the place. To fix it I dirty flashed my ROM and the kernel on top of it in TWRP together and it resolved the problems.
Just a thought...
Click to expand...

Even I test with "dirty" flashes. I'm not really sure what you'd wipe for kernel only updates anyways. Everything I read says it isn't necessary. It's a good thought though and maybe cache words are worth a shot with the WiFi update.
 
spock1104 said:
Even I test with "dirty" flashes. I'm not really sure what you'd wipe for kernel only updates anyways. Everything I read says it isn't necessary. It's a good thought though and maybe cache words are worth a shot with the WiFi update.
Click to expand...

I'm not saying wipe anything. Just flash a ROM that will reinstall the /system and boot.img and have the kernel qued up next in TWRP. This will restore the original kernel and system, leaving data intact so nothing is lost. Moonshine would be best for this. Just don't forget to wipe dalvik/cache before reboot
 
dragonhart6505 said:
I'm not saying wipe anything. Just flash a ROM that will reinstall the /system and boot.img and have the kernel qued up next in TWRP. This will restore the original kernel and system, leaving data intact so nothing is lost. Moonshine would be best for this. Just don't forget to wipe dalvik/cache before reboot
Click to expand...

Good idea for some, but I can't, I'm still stock! :eek:
 
dragonhart6505 said:
Has anyone been clean flashing the latest betas to give better reference?
For example (different phone, same principle):
Recently I was having issues with my GNex on Dirty V so I flashed Fancy over it not thinking any issue would arise since it installed a new ramdisk (I believe were still on the same as before, but hear me out) I started having problems all over the place. To fix it I dirty flashed my ROM and the kernel on top of it in TWRP together and it resolved the problems.
Just a thought...
Click to expand...
When flashing a kernel the whole partition is written to hence "boot.img" only thing that should need done is control app force stopped and data wiped
 
brittnearl said:
When flashing a kernel the whole partition is written to hence "boot.img" only thing that should need done is control app force stopped and data wiped
Click to expand...

In the case of my GNex the kernels have a different ramdisk and Fancy is built with anykernel2 (to be universal for all 3 versions of the phone), so they suggested flashing from a dirty ROM. Like I said, it was just a thought as I know were on the same ramdisk as before so this doesn't "technically" apply in our case. But since he is rebuilding/reworking the features I thought it would at least be a good idea to see if anything changes with this method
Food for thought, argue it if you want...
 
brittnearl said:
When flashing a kernel the whole partition is written to hence "boot.img" only thing that should need done is control app force stopped and data wiped
Click to expand...

How is the whole partition written when kernels are obviously of different sizes? And no other partition acts like that. Also how come there was a format boot option in a prior recovery, i know i used it. Also in another recovery, I think Philz, it would format boot every time you flash a kernel. Personally if all the other partition need formatting before flashing items, then why wouldn't the boot? I think we need a format boot option in recovery.
 
DsyMnapTic said:
How is the whole partition written when kernels are obviously of different sizes? And no other partition acts like that. Also how come there was a format boot option in a prior recovery, i know i used it. Also in another recovery, I think Philz, it would format boot every time you flash a kernel. Personally if all the other partition need formatting before flashing items, then why wouldn't the boot? I think we need a format boot option in recovery.
Click to expand...

Such an option does exist in TWRP for other devices. GS4 I believe, as well as Nexus (I know I keep bringing that one up...) Just needs to be implemented
 
DsyMnapTic said:
How is the whole partition written when kernels are obviously of different sizes? And no other partition acts like that. Also how come there was a format boot option in a prior recovery, i know i used it. Also in another recovery, I think Philz, it would format boot every time you flash a kernel. Personally if all the other partition need formatting before flashing items, then why wouldn't the boot? I think we need a format boot option in recovery.
Click to expand...

Boot is a ramdisk image, there's no file system to format. It's inherently overwritten every time you flash.
 
spock1104 said:
Boot is a ramdisk image, there's no file system to format. It's inherently overwritten every time you flash.
Click to expand...

Then why is the option present? I've used it before on the Awe, I swear broski....it has happened, lol.

Ps: not questioning your expertise, as obviously you are a Jedi master, but this padiwan wants to know:D
 
Can I manually to format boot with the terminal in TWRP? I just wanna see something, because Smartass seemed to be working differently when I first flashed the RB kernel clean. It was the very first kernel I ever flashed on my new awe and worked fine...now after flashing multiple kernels over one another things are working differently....Yes I already did the whole force close and data wipe with Android Tuner and I have the same results...To me this only signifies that dirty flashing kernels is what's causing problems. I've even done entire restores of my stock rooted Rom and still have problems with the kernel working exactly how it did the first initial time I ever flashed one on this phone.
 
Right...So now I have proof that clearing data and force closing Android Tuner does nothing. I did that and completely uninstalled the app and settings are sticking from a different side regardless of apps priorities. I stand firm on the idea of needing to format boot.

Is anyone on philz recovery? I can't remember if the format boot option was in that one or a previous version of TWRP and I'm kinda leery about flashing another recovery over this one anyway. I don't want another Encryption Unsuccessful problem.
 
DsyMnapTic said:
Right...So now I have proof that clearing data and force closing Android Tuner does nothing. I did that and completely uninstalled the app and settings are sticking from a different side regardless of apps priorities. I stand firm on the idea of needing to format boot.

Is anyone on philz recovery? I can't remember if the format boot option was in that one or a previous version of TWRP and I'm kinda leery about flashing another recovery over this one anyway. I don't want another Encryption Unsuccessful problem.
Click to expand...

If you ever hit save in android tuner it'll write a file for itself that it can pick up on again, I think.
 
You must log in or register to reply here.
Back
Top Bottom