yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] PaulGiz:
Listen to this very good advice. I am a firm believer of the "clean install". Because I use ROMCleaner, I can do a full wipe, flash a ROM and restore my phone in a few minutes. So, that's what I do. You'd be surprised at how much residual junk you have laying around from multiple ROM/Kernel/Mod flashes. I guess you don't need to do it every time, but after a while it's a good idea.

One other thing for you (OK, we) flashaholics. It can't hurt to back up your SD, reformat/partition, and then just restore what you need every now and then. Again, bits and pieces of unresolved and unused files, fragmentation etc. make your SD inefficient. Clean it up once in a while, your phone will run better, and you're less likely to have mysterious and untrackable little glitches.

P.
[HTC Sensation] hinxnz:
Thanks for your answer :) I must of done something wrong elsewhere because when I excluded those modules when I re-flashed a repacked version of 009b3 I had a wifi error.
[HTC Sensation] Dijkstra88:
Using b3 for 4 hours now. So far no lag. Thanks to Faux Hinx and Yank for making this possible :D

Send from my HTC Sensation Z710e with Tapatalk
[HTC Sensation] jyo1:
Not sure how, but I'm getting smoother performance with faux's default 9b1 than with the aroma for 9b3 (with default settings) :rolleyes:
[HTC Sensation] Yank555:
Try slightly higher inactive max / two phase, I sete the defaults a little lower in Aroma to save a littel juice.

But just one question, did you remove the 99z_kernel in init.d when flashing default 009b1 ? Else you still run the "Aroma" settings.

JP.
[HTC Sensation] XaQi 101:
009b3 is running great on my phone, not encounter any lag since flash it. For know it about 7 hour of usage. I uv -100 and enable hardswap.
[HTC Sensation] haifish9999:
I've tried v1.82- aroma in yesterday and everything worked gread. One little thing: battery life drain a little more( everything setting in Aroma from you only max frequency and UV something else). Waiting for a few day to look something better.( follow Your advice from Venom threard).
[HTC Sensation] Hawke84:
playing around with faux beta 9v3 im still getting some laggy performance when working through sense. no where near as bad as it was and my memory is being managed better, never dips below 100mb free but its not quite as smooth as the beta 8 that everyone loves was.

im on viperS sense 4.0 stock LMK values for now. i'll do some more testing with different lmk values but the venom tweaks app makes that hard.

what would be helpful from a log point of view with this, logcat the most useful?
[HTC Sensation] ajay83:
Hey Guys.

I've been testing the 009b3 since last night. My settings are as follows

ACTIVE MAX--------------------1512MHZ

INACTIVE MAX-----------------972MHZ

PHASE2--------------------------864MHZ

MAX SCREEN OFF----------594MHZ

NO UNDERVOLT

GPU--------------------------------STOCK

NO HARDSWAP OR ZRAM

LMK VALUES-----------------STOCK

SWEEP2WAKE WITH BACKLIGHT ENABLED

I/O SCHEDULER----------------CFQ

I've abused it as much as I could and my RAM isn't going below 130-120mb which is good. I think it's around 85% as good as 008b8v6 which Yank re-did with the new aroma settings a couple nights ago. Very rarely is there a slight lag here and there. Some times a few seconds too many going from say homescreen to settings or pulling up all the apps. Otherwise very very good. Something I would still keep as a daily driver.
[HTC Sensation] chrisrj28:
Is there a yank version of 009b3 coming? Don't read anything about it
[HTC Sensation] DeactivatedProtocolDroid:
If I'm not mistaken you can flash 009b3 then flash an older version of Yank's but select script only on the Aroma.

I'm currently playing with 009b3 with stock Sensation settings except -150 UV on Member's MIUI. Surprised that it's running smoothly so far. I'll try it on Elegancia Sense 4 later.
[HTC Sensation] Yank555:
I intended to wait for faux's next beta, the hack in 009b2 will be reverted as far as I know, and will align at that occasion.

Let's see when faux finds the time to work on the kernel.

I have my sources ready with just the fix added in 009b3 ready, could compile them, but I have to replace my HDD tonight, so I won't get to that I think, except if copying my data is faster than I believe :D

JP.

---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------

That won't work, the script would try to set GPU OC to 300MHz which faux's version does not have as a valide frq. and will revert to 320MHz.

The frequencies for GPU OC are compiled into the kernel, and the top freq. is 320 for faux's kernel, and I lower it to 300 in my version.

Or in other words, the difference is Aroma

and

the kernel (zImage).

JP.
[HTC Sensation] Zirias:
Thanks for the clarification! It wasn't THAT hard figuring out what I had to do, but I guess for ppl without deeper linux/unix knowledge, it could be challenging. In my opinion, just adding a directory that is widely known for its purpose in case it isn't already there won't ever do any harm.

This is indeed a problem. Just a thought: It might be more reliable to detect whether there already IS a mechanism in place for executing init.d scripts rather than detecting the system and making assumptions -- just like in web development, it's more reliable to detect the features present in the user agent rather than assuming something based on its name. But then, I have no idea whether there is a reliable way to detect init.d execution mechanisms in place. I'll try to have a closer look on this soon...
[HTC Sensation] jyo1:
Thanks Yank.. Will try that. And yes, I did remove the 99z file. Good habit as a result of reading this forum :)
[HTC Sensation] klothius:
There is a way to check for init.d support, but it will prolong the installing time, by how much I don't know, probably not much, but there is a way.

In the process of unpacking the current boot.img (to replace the current zImage with a new one), you get not only zImage, but also a ramdisk image.

You can then unpack that image into some tmpfs (like in /tmp that is already created for purposes of packing/unpacking during the normal installation). Then you could check for execution lines for either init.d or init.post_boot.sh script in init.rc and init.pyramid.rc and if find init.d, stop there, if you don't but you do find execution line for init.post_boot.sh, then search in that file for init.d execution. If even that doesn't work out, and you find a line for execution of init.qcom.post_boot.sh, then check in there...it's a lot of checks, but there are a lot of ways devs execute init.d scripts.

Although many roms execute init.d scripts through init.post_boot.sh, some still do it via the old way as in execution from init.rc/init.pyramid.rc.

I'm not familiar with the interworks of the Aroma installer, and my exams start soon so i cannot afford to spend time on learning that now, but I'm positive yank will figure it out :)
[HTC Sensation] Yank555:
Sounds fair enough, in case I don't add it to the next Aroma, please do give me a gentle reminding slap ;)

The thing is, the way I do it, isn't actually the way

I

do it, I just use the way mike does it for ARHD.

Detecting is very very tricky. init.d being present means not much. Parsing init.post_boot.sh is, to say the least really not easy, as it would require to parse shell code and understand what it does (if there is a case expression, would that evaluate to true or false ...), not to keen going down that road.

Then there is the more commun init.d support, out of the ramdisk. Detecting that is even harder, it would require :

1) dumping the boot partition to a file

2) decompressing the boot image (file)

3) once decompressed, you'd have amongst other things a compressed ramdisk that would need decompressing again

4) once decompressed, you'd find the filesystem structure of your system's "/" (root) filesystem (that is what the ramdisk actually is btw.)

5) In there you'de need to start looking for a logic of execution of startup files (can be shell scripts, can be rc files...) to try to figure out if init.d is handled from within there

Hmm ... that's a even heavier than just parsing one shell script (init.post_boot.sh), I'm afraid :(

I think that in essence the way it's done by mike for ARHD is the best way at hand, I'd rather have gone the other way around and done it from the ramdisk, but I guess he does have his reasons to not do it, reasons I actually never wondered what those might be, but rather accepted this as a given fact, which is eventually is.

So using any of the properties un build.prop to determin whether to start init.d scripts from within there is the best way.

Especially for a ROM like the stock ROM which as it seems comes with neither init.d support, and adding it to init.post_boot.sh is quite easy, adding it to the ramdisk, well you've seen what had to be done to take the boot image apart. Adding init.d support there would require modding the ramdisk (plus adding busybox, need to execute many commands in init.d scripts), recompressing the ramdisk, rebuilding a new boot image and then flashing it to the correct internal memory partition.

A lot of work and a deep intrusion in your system...

JP.

---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------

True (our posts just overlapped ;)). The only thing I'm not so easily keen on doing is this :

Suppose there is no reference to init.d in the ramdisk, but I find a reference to init.post_boot.sh. A simple "grep init.d init.post_boot.sh" won't do, as it may be within a conditional clause (if or case), so how to tell what the condition would evaluate to ?? :(

Will think about it, but as of now, all I can think of is to at least create the init.d folder, it'd be a start, an easy one I agree :D

JP.
[HTC Sensation] Zirias:
Yep, I see what you mean. In a situation, where every ROM dev uses a different approach in a compressed fs image while stock rom doesn't support it at all, it's probably not worth the effort. So I'd suggest to just add init.d directory in case it was missing, together with some instructions for the average user to install a) busybox and b) some flashable zip replacing init.post_boot.sh in case it doesn't work as expected.

BTW, kernel 009b3 seems fine for me after ~7 hours ... just some lag starting up the music app (using bfq on an SD card with lots of mp3s). But then, as I read here, the heavy lag issues were only seen on Sense 4 ROMs, right?
[HTC Sensation] radiohitec:
For me the same, 8U works here better, only the memory is better (138 and more on agressive setting) on the 9v3, working with Android Revolution HD 6.7.2 XE ROM
[HTC Sensation] Yank555:
Mostly yes, since Sense 4 is a memory hog :rolleyes: Consider trying cfq rather than bfq ...

JP.

---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------

008u or 008b8 ?? Becuase 008u is 3.0.41 without the fix...

JP.
[HTC Sensation] klothius:
Well you don't have to do the checks with a bash script, you can just extract the ramdisk with bash (as recovery supports gzip -- at least EXT recovery does) and write up some small C program for checking existance of execution line (or just if there's a mention of init.d/init.qcom/init.post_boot as there won't be any other reasons for them to be mentioned in file except for execution of them), then call a function with parameters forwarded to the file we're checking, see if there is execution line for init.d in that file and write 1 or 0 for confirmation/denial of existance in some external file in /tmp (either by opening a file in program or starting the program with program > file), but do it only when it's done checking everything so to be left with only one number. If you get a confirmation while checking, skip rest of the checks. Then you just use the file to see if there is init.d support or not and continue from that. Of course all of it could be done within bash, a bit more code, but it could be done.

When I'm done with exams in a week and a half, maybe 2 weeks, I'll see what and how exactly can be done and pm you if you want :)
[HTC Sensation] Yank555:
That'd be great ;)

Where I keep seeing the difficulty is if we end up init.d being probably handled by init.post_boot.sh, how do you check if init.d is handled within a conditional clause (like if rom=arhd then execute init.d).

And good luck with your exams ! :D

JP.

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium
[HTC Sensation] 69gm:
Thank you all for your input! Some good stuff there!

@hinxnz, no it's not physically related as far as I can tell because when I use my nandroid to go back all is responsive again.

@piimp, thanks! I was thinking that when flashing a new kernel, that kernel's settings would take over. It doesn't? :confused:

@Yank, once again you are a wealth of knowledge. I had assumed that there was something built into the kernel or installer that would remove all traces of the previous kernel. Was I wrong? At any rate, I am currently in the process of redoing my phone. Just superwiped and now doing clean install of ROM. After that I will flash 9b3. After that I will restore data from my nandroid backup. Is this correct? Any time I'm switching kernels I have to go through this process? Logically it sounds like the cleanest but I always thought, besides reset scripts, you just had to flash a new kernel over the previous one. Oh well, hoping for the best!

@PaulGiz, thanks to you too! Yes I'm trying it out from scratch, pretty much. And I hear ya' about the SD card. Did it recently. As you say, it's incredible the amount of stuff that gets leftover!

I'll give it a whirl and report back later! Thanks all!!! :good::good::good:
[HTC Sensation] acesabe:
009b1 without z99 ran fine all day for me, might try b3 later.

For gathering info in the init.d process, bootchart might be useful, if anyone has the time/patients to service it all up, which probably includes enabling it in the kernel etc...Android bootchart article here: http://elinux.org/Using_Bootchart_on_Android
[HTC Sensation] Yank555:
If you superwipe, then you'd need rather a titanium backup of you apps. You can try to do an advanced restore of the nandroid and just restore /data, but that would be somewhat odd and missing the point I think...

In Aroma faux and I take care of the leftovers from other kernels we know of, might not be 100% I'm afraid, and changes with time.

Also, settings that are overridden by apps will always 'win', the script is executed once at boot, and that's it, whatever changes are applied later will be active, and there's not much that can be done against that.

JP.

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium

---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------

Can you post the result of this in a terminal :

ls -l /system/e5c/init.d

I find it strange the the config script would be messing up anything !?

Thx, JP.

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium
[HTC Sensation] klothius:
Well it could be made with a bit of pointer moving up and checking if there's a clause after we find a line for executing init.d from within *post_boot.sh, but I don't see it being important as no one in their right mind would put a clause that has no way of returning true unless someone just copies over someone elses file in which case it's easy to pinpoint exact rom and pm a dev with info on that. I might be wrong on this, as I can't say I've looked through a lot of roms and their files as I'm using my own version, but if I am, I'll find a way for that to work too :)

And thanks, I'll need it :D
[HTC Sensation] Hawke84:
Random reboot on version 9 beta 3 while texting and installing apps. No last_kmsg file that normal?
[HTC Sensation] Yank555:
Since we need to remove a few things from thag file, we had to add a case clause thag does handles the init.d for aehd and elegancia, but not others, since the kernel need to be installable on several ROMs.

I'm ready to be impressed by you on this, again, since finding the double code in the source was quite impressing ;)

JP.

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium

---------- Post added at 09:55 PM ---------- Previous post was at 09:54 PM ----------

No /proc/last_kmsg !?

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium
[HTC Sensation] klothius:
It might prove usefull to rom/kernel devs, but it's not worth it here and again I'm not even sure that init is the same in htcs rom and aosp as you'll need a source of the init file to add it which we only have from aosp.
[HTC Sensation] malybru:
Hi,

Try Lumberjack from the market.

Great for last ksmg and logcats .

:)
[HTC Sensation] djgboy:
009b3 kernel with the ram hack works good for me no lagg
[HTC Sensation] acesabe:
just 93zipalign and 99complete are in there (obvs. e5c was meant to be etc!).

I'm not saying the config script is messing anything up, just that plain 009b1 works fine without the 99z script....Lets have a go at the latest Aroma version with conservative choice of options (maybe no bfq as you don't recommend it ((why is it on offer??!)) ) and see how we get on...
[HTC Sensation] Yank555:
bfq was added by faux upon request on a different kernel thread, to keep stuff consistent, he also added it here.
[HTC Sensation] piimp:
They do, but u have to change the governor to whichever you want, intellidemand in this case...when I was switching around from Sebastian to faux, sys tuner would say ondemand, (which is what I use on seb), although now its using faux's ondemand. So I changed it to intellidemand...hope that makes sense

Sent by my feau gee
[HTC Sensation] Yank555:
Many of Aroma will stick, everything governor specific, but other will be overwritte by Viper, like LMK settings ... their tweaks apps runs way later in the boot process than my script, and the last always wins here !

If the governor doesn't stick, that is very strange, then there are leftovers !!

It should be intellidemand. Except if Viper tweaks also mess with governor ??

JP.
[HTC Sensation] piimp:
I don't use viper so I don't know about that...but you are saying once you install faux it should automatically set it to intellidemand without you changing it, regardless of previous kernel?

Sent by my feau gee
[HTC Sensation] Yank555:
Aroma version certainly. Faux's version, not too certain, since I can't recall what files come exactly with it... and where your ROM sets governors.

JP.
[HTC Sensation] Zirias:
I had cfq with the 008u kernel, but that's probably a bad comparison ... cfq also runs on my desktop (some years ago with self-compiled con kolivas kernels [he's the man], but now just with stock debian). I just thought from the description of bfq that it would be the more sensible thing to do. But sure, i'll try out cfq here again ... maybe it's the old engineer's wisdom: simple solutions are better :)

And concerning installation (AROMA) -- I just think there might be some users who (like me) want to trust the original manufacturer's ROM and still want to use a different kernel and who (unlike me) don't have much *nix experience. So I promise to (re)search for an appropriate solution soon ... but maybe others are faster, it's really impressive reading this thread how quick some ppl solve problems :)
[HTC Sensation] ammenRA:
Just flashed the latest faux. The first setup without the swap mod, I got lags when i turned the phone from portrait to landscape. I let the kernel to settle in. Erased the post boot and his friends, flashed the 2nd time with swap mod, the lags are gone.
[HTC Sensation] PaulGiz:
It's been a full day now, b9v3. Using hardswap, aggressive memory mgt., mostly stock (Faux) settings, 1.51 clock, 320GPU.

I have to say I quite pleased. No lags, no restarts, and phone is quite snappy.

Recommended!

P.
[HTC Sensation] 69gm:
Okay latest report!

So as Yank suspected, after Superwiping and restoring nandroid data, the phone was still laggy. So decided to do a true Superwipe and start from scratch. Took a while to get everything back to how I had it but now faux has NO LAG! Well okay there is a small lag. It is when my phone is "sleeping" and I get a small lag when I wake it. Of course it doesn't help that I use the photo album for my lockscreen, but I've always done that with minimal, if at all, lag when using the stock (Bricked) kernel. Once my phone wakes, though, it is nice and smooth! I can't say it's significantly smoother than I had it before but it's only been the first day so I'll give it a few days to settle in. It's definitely not worse anymore though! Yayy! :victory:

So there definitely was "something" clogging things up that would keep faux from running although I'm still not sure what.

Oh FYI, I used all the defaults except I chose Yank'd default for screen off freq and I didn't overclock my GPU since I've had heat issues playing games.

Yank, yes the governor definitely did NOT change to intellidemand originally even when using AROMA. Somehow something kept it from changing so something to look into? :confused: After my complete nuking of my phone, the governor readily switched from Bricked's badass to faux's intellidemand.

I will continue to report if something happens, but for now, running pretty nicely!

Thanks all for your input, especially Yank for suggesting going nuclear on my phone. If you're having similar problems, I would recommend it. It takes longer to get your phone going, but you'll feel "cleaner" once it's done!
[HTC Sensation] kairanz:
Strange, after flashing 008b8 v6 over bricked, my governor change to intellidemand. Wait 5 min after boot and check it. My freq is on 1566 after boot altough i set to 1180 in aroma, but after 5 min it change to 1180. Or did you have boot setting in system tuner? If yes then maybe that was causing the governor not change

Edit. Nvm i think i didn't read your whole post, so you didn't have any problems right?

Thanks yank and faux and everyone involved with this kernel development. You guys are awesome, especially you master yank! Thanks for your kindness to share all the knowledges to all of us. Remember me who ask you many question in your hardswap thread?haha. Many thanks sir :beer:
[HTC Sensation] Hawke84:
The file just doesn't exist
[HTC Sensation] faux123:
By the way, beta 4 is available at the bat cave. Have fun!
[HTC Sensation] Yank555:
Hi,

Here's the AROMA installer version :

I could not test this flashers due to lack of time...

Remember, Nandroid is your friend, always backup your system before flashing !!

Enjoy, JP.
[HTC Sensation] 69gm:
Hi Yank,

Just wondering if this is 9b1, and I'm on 9b3, should I be flashing 9b4 which is 9b1? :confused::eek:

And since I'll be going from faux to faux, I shouldn't be experiencing the problems that used to plague me, right?

Any ideas on the sluggishness from screen off? Do I need to increase the freq? I used your default...which I believe was 432? I know in Bricked the default was 486. Is this the cause? Can I change that via System Tuner or better to reflash (especially if I decide to do 9b4). I know sooooo many questions! Sorry about that! :o
[HTC Sensation] Yank555:
009b2 and b3 were just to validate which of those changes were the right ones, as announced previously, that is done now, 009b4 is the way to go ! ;)

JP.

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium

---------- Post added at 09:04 AM ---------- Previous post was at 08:51 AM ----------

Try using a higher screen off freq ;)

JP.

Sent from my custom ARHD 2.1.1 / Yank555.lu kernel v1.1 (Linux 3.0.42) powered Samsung Galaxy S3 using xda premium
[HTC Sensation] 69gm:
You read my mind Yank! That's exactly what I was going to ask! And since I'm going from faux to faux I shouldn't have the problems that plagued me before, right?