yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Super-Android:
Ok guys, guess we need to look into this scenario, I was on stable version 2 --- Flashed both the test version -- Phone worked normally.

For test, Installed Faux kernel -- Then tried and installed test version 2.3 and 2.5 .... Stuck in boot up.. Splash screen...

Again installed stable version 2 (Non - Aroma) --- Test builds working.....

Just thinkign what about the people coming from Faux?

Ganeshp tried ur work around too.. Didnt work..
[HTC Sensation] :
Oh, I've chosen the wrong every time :D
[HTC Sensation] axetilen:
flash this and then reflash the kernel

https://dl.dropbox.com/u/47039397/MODs/Powerful Kernel Reset - MOD Remover.zip

---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------

OK. I'm missing something

Now, I'm back and downloading 2.5 now :)
[HTC Sensation] Super-Android:
I really dont knw whats wrong with my phone, None of the test build seems to be booting up now.... Even after i flashed reset mod.... But Stable version 2 is working fine...!! Previously worked, after installing other kernel, not working,,, any work around?
[HTC Sensation] axetilen:
hey hey

I have the same problem :(

Phone stucks at HTC splash screen and ... down .......!!!!!!!

pacha, please fix this
[HTC Sensation] ganeshp:
mostly might be the changes in the init.qcom.post_boot.sh (you can ignore vold.fstab and vold.fstab.auto)

EDIT: test version doesnt have this file ..so they must use stable v2 version ones

check the differences between the stable v2 ,kernel re-setter mod and faux kernel
[HTC Sensation] axetilen:
I'm using the stable v2 init.qcom.post_boot.sh and remove all the scripts but still not work

However, there are 2 people who have problems => users, the number would increase on many devices :(

stable v2 with the same settings boot up perfectly but test 2.5 can't not :(, the same with 2.3
[HTC Sensation] Super-Android:
Meanwhile, trying to figure out wt is wrong with test version..

I would like to tell that Antutu benchmark score with stable version 2 is 6124... !!
[HTC Sensation] XxXPachaXxX:
Now i post the stable3...but how to clean the init.d folder? what are the most used scripts names from faux and others?
[HTC Sensation] realsis:
Just downloaded 2.5 :D

sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, mugen battery. please press thanks if I helped in anyway. :)
[HTC Sensation] axetilen:
faux: 99z_kernel

Bricked: 89badass

mods from me and iba21: 69force

I have Powerful Kernel reset which has a script to clean up all these leftovers

EDITTED:

Pacha, you can add these scripts to the updater-script: ===> I think they are helpful for having a clean kernel and we can reduce the number of people who have problems

delete("/system/etc/init.d/69force");
delete("/system/etc/init.d/89badass");
delete("/system/etc/init.d/99z_kernel");
delete("/system/etc/init.d/31gpu_scaling");
delete("/system/etc/init.d/30cpu_scaling");
delete("/system/etc/init.d/32vdd_levels");
delete("/system/etc/init.d/33zram_swap");
delete("/system/etc/init.d/50faux");
delete("/system/etc/init.d/21uv");
delete("/system/etc/init.d/99vsync");
delete("/system/etc/init.d/91s2w");
ui_print("Deleting 69force...");
ui_print("Deleting 89badass...");
ui_print("Deleting 99z_kernel...");
ui_print("Deleting 31gpu_scaling...");
ui_print("Deleting 30cpu_scaling...");
ui_print("Deleting 32vdd_levels...");
ui_print("Deleting 33zram_swap...");
ui_print("Deleting 50faux...");
ui_print("Deleting 21uv...");
ui_print("Deleting 91s2w...");
[HTC Sensation] ganeshp:
the kernel resetter has some extra files ..which are not there in v2 stable .. init.post_boot.sh and thermald.conf which v2 stable doesnt posses ..may be that's what causing the issue

also from faux if you flash test zips then the zips wont work for sure as they are not complete ..thay dont have lot of required files that are needed in /system partition (the test zips work only over the v2 stable as far as i understood)

go with the standard version just like v2 stable (keep all what are required) ..why bother about cleaning the left overs from other kernles??? the aroma version can deal with that :) (just my opinion :D)
[HTC Sensation] topjohnwu:
But the link isn't working...
[HTC Sensation] ganeshp:
he is saying im about to post it ...he hasn't posted yet!!!! ..he need to update his updater-script of the zip file ...:)

hold your horses for couple more minutes :D
[HTC Sensation] topjohnwu:
Oh, thanks a lot maybe I'm a bit too hurry.
[HTC Sensation] XxXPachaXxX:
ADDED stable3
[HTC Sensation] axetilen:
it can't be?

thermald.conf is a required file to config thermald

in the v2 kernel, we can see there are thermald and mpdecision and thermald will load the configuration from that thermald.conf

init.post_boot.sh and init.qcon.post_boot.sh cant cause any problem because it took them from super-android which comes from stock kernel and there is no setting that affect the activity of the kernel

EDITTED:

download stable v3 and it doesnot boot up too :(
[HTC Sensation] XxXPachaXxX:
thermald.conf isn't required and init.post_boot.sh isn't a qualcomm's script so this is the major cause of problems.
[HTC Sensation] ganeshp:
i kinda guess about the thermal.conf file

but i didnt see anything else that should obstruct the kernel ..weird

so over kernel-resetter the v3 is not booting up ?

let me try that too

seems not required based on pacha's explanation
[HTC Sensation] axetilen:
Now, my phone seems to stuck at HTC plashscreen forever...

what do I have to do? Just flash the kernel and don't flash anything else :(

v2 works normally
[HTC Sensation] gen129:
stable 3: cpu1 does not go to sleep after reboot until echo 0 > /sys/.../cpu1/online

then mpdecision make his work fine.
[HTC Sensation] ganeshp:
remove the thermald.conf and init.post_boot.sh and then flash v3 and see
[HTC Sensation] axetilen:
pacha included a script to delete these things so I don't have to

but I'll try to remove them

editted:

What is happenning to me???

Phone still not boot up after deleting init.post_boot.sh and thermald.conf
[HTC Sensation] ninjabadger:
Everything working correctly here with v3.

CPUs going on and off as expected.
[HTC Sensation] Sharpi1:
Now iam Confused, for some ppl v3 worked for some not. What should I Do :D
[HTC Sensation] gen129:
Is stable3 removes /etc/init.post_boot.sh?!! It makes /etc/init.d scripts inaccessible on ARHD :(
[HTC Sensation] axetilen:
You can flash

and report of you see the error

or perhaps the problem comes from ViperS?
[HTC Sensation] ganeshp:
its simple ..if you are currently running v2 then simply flash this and it should work

if you are on another kernel ..then for safe keep ..backup the current the /system partition (advance backup---for safekeep) then flash the v3

if not booting up which i highly doubt it ..restore the system and then flash back the earlier kernel :)
[HTC Sensation] spiderio:
REPORT...

Now I have good news

the aroma version 2.53 is good, no keep awake

my phone goes to deep sleep...

no battery drain indicator

i have installing Watchdog Task Manager lite

no probs so far...

Only there's Alert Tabs ...

Android system using 58%
[HTC Sensation] ganeshp:
ahh yes ARHD has this requirement right ...hmm backup the original one and then after flashing the kernel try to restore it
[HTC Sensation] gen129:
Never mind - I can solve my problems by myself, but what is for othes ARHD users?
[HTC Sensation] ganeshp:
pacha has to decide that ..

because having that init.post_boot.sh file from other kernels is affecting this kernel (for some)

and not having that init.post_boot.sh in case of ARHD rom will cause problems to the rom

so im lost !!!
[HTC Sensation] topjohnwu:
The v3 kernel is working on me (using the vipers 1.3.5) without doing anything expect flashing the zip.

BTW, I found out that maybe the v3 is based on bricked kernel (in hardware info cpu info says bricked 1566x2)
[HTC Sensation] sundin_13:
Great work, it's really fast. Everything is working fine on my Sensation, but I can't mount CIFS drives. Can you help me to resolve this problem? Is CIFS supported in the kernel? I'm using ARHD 6.7.2 Thanks, and keep up the good work!
[HTC Sensation] gen129:
I'd suggest to overwrite this file with absolute minimum as

runparts /etc/init.d

or something about this.
[HTC Sensation] Super-Android:
I am really confused.... V3 is still not working... M beating my head out on this,,,,, M running on version 2, It worked.. But version 3 stucked at splash screen...!!! :crying:
[HTC Sensation] gen129:
Have ran init.qcom.post_boot.sh manually. Is it expected behaivor? Where are all theese files gone?

app_40@android:/etc # sh init.qcom.post_boot.sh

init.qcom.post_boot.sh[75]: cannot create /sys/module/rpm_resources/enable_low_power/rpm_cpu: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu0/power_collapse/suspend_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu1/power_collapse/suspend_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu0/standalone_power_collapse/suspend_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu1/standalone_power_collapse/suspend_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu0/power_collapse/idle_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu1/power_collapse/idle_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu0/standalone_power_collapse/idle_enabled: No such file or directory

init.qcom.post_boot.sh[75]: cannot create /sys/module/pm_8660/modes/cpu1/standalone_power_collapse/idle_enabled: No such file or directory

mount: Device or resource busy

Unable to chmod /sys/devices/platform/rs300100a7.65536/force_sync: No such file or directory

Unable to chmod /sys/devices/platform/rs300100a7.65536/sync_sts: No such file or directory
[HTC Sensation] Gramzz:
I have the same problem with v3, my phone stuck on splash screen and restart all time.
[HTC Sensation] axetilen:
we have the same problem :(

HTC splashscreen, always
[HTC Sensation] ganeshp:
wow that's some number ..need to identify the culprit then ..but im not sure where exactly we have to start
[HTC Sensation] axetilen:
1 user reported that About Phone is Bricked --> ???

I think there is a problem related to boot.img
[HTC Sensation] ganeshp:
in my cases its pachas only ...he might have bad flash or flashing aborted initially itself

EDIT:hardware info indeed says bricked :)
[HTC Sensation] ninjabadger:
His phone isn't bricked. He was referring to system info looking like bricked kernel.

I.e 1566mhz x2 bricked
[HTC Sensation] sjknight413:
Working fine here, flashed over ViperS 1.3.5 + SebastianFM 1.5.2.

About phone does indeed say bricked, which is strange because there is nothing related to it in init.qcom.post-boot.sh. possibly something from bricked in the boot.img?
[HTC Sensation] axetilen:
ViperS 1.3.5 + SebastianFM 1.5.2???

Are you using sebastian kernel?
[HTC Sensation] sjknight413:
I was, but I flashed stable 3 over the top and it worked fine.
[HTC Sensation] gen129:
Just notice:

PydX stable2 and stable3 does not go to deep sleep - cpu0 is always on. Seb 1.5.2 - does go to deep sleep after ~1 min screen off.

No Zram, no custom init.d scripts. init.post_boot.sh minimalistic - from axitilen Seb kernel mod.
[HTC Sensation] flamechamp:
same problem again :'(
[HTC Sensation] saigon66:
Just flashed . It seems so far so good!

Verstuurd van mijn HTC Sensation Z710e met Tapatalk
[HTC Sensation] csheppard93:
Just flashed v3 over v2 and now I'm stuck in a boot loop
[HTC Sensation] realsis:
Flashed stable 3 over 2.5 running newest version of viper Rom .

All is well and running perfectly! No problems whatsoever!

sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, mugen battery. please press thanks if I helped in anyway. :)
[HTC Sensation] caxio:
+1 come back to v2 and my sensation works i have checked md5 and match whit is write on devhost my rom is Viper 1.3.5
[HTC Sensation] sjknight413:
Do any of those in a bootloop have any undervolting set? Because I can tell you now this kernel reeeeeally doesn't like being undervolted!
[HTC Sensation] paoloc67:
Just flashed v3 over v2 and now I'm stuck in a boot loop
[HTC Sensation] csheppard93:
Didn't set any undervolt. All I did was flash the zip and reboot. stable2 works fine but stable3 stays at splash screen then reboots over and over
[HTC Sensation] erraggy:
I too don't use any undervolting and after flashing stable v3 over stable v2, I was stuck in non-stop boot loops. Restored my nandroid that I backed up just before so I'm back on v2 until a fix is found.
[HTC Sensation] sjknight413:
That's really strange.

Well as I said I was on sebFMs 1.5.2 kernel before I flashed v3 so if you are on v2 it might be worth flashing to sebFM then booting, then flashing v3 and see if it works.

If you flash sebFMs kernel from v2 though be sure to delete init.qcom.post-boot.sh first as it doesn't contain one.

So, v2 - delete init.post-boot - flash sebFM - boot - go to recovery and flash v3 - boot.

See if that works :)
[HTC Sensation] axetilen:
not work for me

I usually switch between sb and pyd :(

This problem is not small. There should be a stable v4 with a fix
[HTC Sensation] gen129:
Stable1 is working fine and going to deep sleep as expected. So I'll stay on it waiting fo fix.
[HTC Sensation] 69gm:
Well, so far after flashing ver. 3 from ver. 2 all seems well. I'll pass judgement on it later after it's had time to settle into my phone. Initial thoughts are that it feels a little sluggish compared to ver. 2.

I do wonder why it says it's a "Bricked" kernel. I thought Pacha was basing off of Sebastian?

Pacha, care to weigh in?
[HTC Sensation] XxXPachaXxX:
I don't know...in this case we can keep init.post_boot.sh...Tomorrow i will update the installation zip to make it more compatible for all.

It's an error. This string is writed in a cpu file. I taked some code from show-p to add cmdline. Will be corrected in the next version.

I've noticed that some peoples haven't problems and some peoples have a lot of problems. I will work on compatibility.

But i need more infos. The users that have problems in boot up what rom are using?

I noticed that with viperS, if in cpu tab you check the set on boot setting, u will get boot loops

The ARHD users have to keep the init.post_boot.sh, so Tomorrow i will correct the zip.

Users that have sleep state problems, it's caused by a script in aroma installer. Use my zip only for now!

Other users that have problems, report me with detailed info (rom, previous kernels, all!)
[HTC Sensation] sjknight413:
I had set on boot checked in the cpu tab when I flashed v3 and it booted fine just to let you know :)
[HTC Sensation] emanuele252:
I guys. I'm interested to this kernel, but I would an information: how many core are used in this kernel? One or two?

Inviato dal mio HTC Sensation Z710e con Tapatalk 2
[HTC Sensation] 69gm:
Thanks Pacha! Appreciate all your hard work in perfecting your kernel!

So far Elegancia seems to work okay with your kernel...
[HTC Sensation] erraggy:
Experiencing Reboots on v2

After the boot loops from flashing v3 over v2, I restored my backup that was made just before that flash. Now I'm having reboots :crying: so I'm planning on doing a full wipe install of ViperS v1.3.5 and then after configuring the ROM and flashing the AIO Mod (in my sig), I'll flash the stable v3 and see if I find more success.

Here is the /proc/last_kmsg from my last reboot: http://dl.dropbox.com/u/147192/last_kmsg.PYD-X_v2.txt

The meat of the last_kmsg may be this block here:

[ 7809.889617] increase_vdd: vdd_sc (cpu1) increase failed (-5)
[ 7809.956329] lowmem: select 31178 (cargps.provider), adj 15, size 4612, to kill
[ 7809.956512] lowmem: select 31226 (com.htc.bgp), adj 15, size 5741, to kill
[ 7809.956726] lowmem: select 31264 (settings:remote), adj 15, size 10566, to kill
[ 7809.956939] lowmem: send sigkill to 31264 (settings:remote), adj 15, size 10566
[ 7810.066375] lowmem: deathpending end 31264 (settings:remote)
[ 7810.358306] Unable to handle kernel paging request at virtual address b8b56cd8
[ 7810.358367] pgd = c0004000
[ 7810.358398] [b8b56cd8] *pgd=00000000
[ 7810.358459] Internal error: Oops: 5 [#1] PREEMPT SMP
[ 7810.358489] Modules linked in: bcmdhd kineto_gan
[ 7810.358581] CPU: 1 Not tainted (3.0.16-PydX-stable2 #18)
[ 7810.358642] PC is at __cpufreq_driver_target+0x24/0x60
[ 7810.358703] LR is at dbs_refresh_callback+0x64/0x158
[ 7810.358764] pc : [<c0439494>] lr : [<c043c064>] psr: a0000113
[ 7810.358795] sp : ccdf3f18 ip : 00000000 fp : c6aeb050
[ 7810.358825] r10: c0924980 r9 : c6aeb050 r8 : c1519c98
[ 7810.358886] r7 : 014df000 r6 : c003ac88 r5 : c1519c88 r4 : c0923f98
[ 7810.358947] r3 : fe08cb50 r2 : 00000000 r1 : 000c5c10 r0 : c33f8c00
[ 7810.359008] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 7810.359069] Control: 10c57c7d Table: 48c0406a DAC: 00000015
[HTC Sensation] deepsaha007:
phone is not booting after installing Stable 3 , although stable 2 works fine...

After installing Stable 3 , the phone just reboots after the startup splash screen .. It isn't even showing the boot animation

Previously i had Stable2 but removed it using kernel remover then tried to flash the Stable3 and its stuck...more details are on my sig..

Moreover after installing this Stable3 , if i try to install any other kernel or Stable 2 it also gets same problem..So i have to restore nand backup.. :/
[HTC Sensation] csheppard93:
Ok I got rid of the bootloops and being stuck at splash screen and now have stable 3 flashed and working nicely. I reflashed viper 1.3.5 without wiping and without exiting recovery flashed stable 3 and everything is working.
[HTC Sensation] deepsaha007:
Thanks for the solution but i think this is not appropriate solution for this issue.. I think this kernel removes some boot related file so its gets stuck in loop.. I hope dev will fix it asap
[HTC Sensation] csheppard93:
If it removes a boot related file wouldn't it delete it by flashing it wouldn't boot for anyone? Maybe some mods are the issue, since reflashing Rom removes all mods its able to boot.
[HTC Sensation] erraggy:
ViperS 1.3.5 + Venom AIO + PYD-X Stable V3 = boot loops

I just completed the following steps:

a full-wipe install of ViperS v1.3.5

Complete setup after 1st boot

Restored user apps (no system apps / no settings) from Titanium

Setup all of my accounts

Performed a nandroid backup

Flashed Venom All In One Mod v21 by jerrytan93

Performed another nandroid backup

Flashed PYD-X Stable V3

Could not get past the HTC splash screen without boot looping (never got to the boot animation).

This is as clean as I can do. Nothing else was flashed at all. The list above fully covers all of the modification I performed. I have since restored my backup from step #7 above and my next attempt will be flashing Stable v2.
[HTC Sensation] csheppard93:
Try reflashing viper1.3.5 without wipe and don't reboot, while still in recovery flash stable 3 then the all in one mod. Reboot and see if it boots
[HTC Sensation] erraggy:
That's a negative :crying:

Did just as you suggested and found my sensie in boot loops once again. I'm going to give v2 a shot. At least that booted. I'm really not sure what is the issue behind the boot loops.

Update: I successfully installed v2 and booted fine after restoring my backup that was made previous to flashing v3.
[HTC Sensation] ganeshp:
The last kmsg you have given earlier.. Is an issue of kernel itself... Paging error.. Hopefully pacha solves it :)
[HTC Sensation] axetilen:
I will stay with this error and wait for the next version without trying to fix

I will report of it causes the same problem again

I will remove init.post_boot.sh in the next aroma version

I'm using vipers but I don't check Apply on boot -> still get bootloops

hope you can fix this problem soon and we can use the great kernel :)

sebastian kernel with all the same configurations is laggy
[HTC Sensation] XxXPachaXxX:
It's so strange that for some users it works and for Others not...
[HTC Sensation] ninjabadger:
I deleted the 69force and 21uv scripts before flashing v3 and everything worked fine.

Did the guys having issues do this?
[HTC Sensation] axetilen:
no. I don't have these files before flashing

already deleted
[HTC Sensation] Gramzz:
I have the same problem with bootloop. I've got Vipers 1.3.5. I tried flash v2 PYD-X kernel before flash v3 - didnt help so i tried flashed bricked v1.36 - didnt help. i tried wipe dalvik cache and without wipe, i tried with kernel reset and without -NOTHING help me...

this is very strange i flashed a lot of kernels and never had problem like this one.

Pacha help us:) And thank You for your hard work - v2 its awesome.
[HTC Sensation] yazzabo:
I' M on viper 1.3.5 and i was on stable v2 with aroma...i use powerful kernel reset and i flash v3...all goes as it should!
[HTC Sensation] jkolner:
Very strange...

Im running ViperS 1.3.5 and Stabel v2 Kernel. Yesterday i flashed v3 but got bootloop every time. Re dovnloaded but with same result. Today i tried to flash v3 over v2 again and it works just fine ;)
[HTC Sensation] Nekromantik:
Im waiting for aroma version of stable 3. :)
[HTC Sensation] axetilen:
Sorry, now this kernel has problems with my device and some other users, so I can't test and make the AROMA for this :(

I'm wating for a newer version which is 100% compatible with all devices
[HTC Sensation] XxXPachaXxX:
What's your rom?
[HTC Sensation] axetilen:
It's all in my signature

It's vipers but I don't check Apply on boot, neither system tuner
[HTC Sensation] Nekromantik:
Im on Viper S too so wont flash 3 if there are issues.
[HTC Sensation] topjohnwu:
Well I'm on vipers too but no problems, very smooth. I flashed the v3 over the v2 aroma, and get no issues.
[HTC Sensation] XxXPachaXxX:
Mmm....very strange...can U wipe data and start the rom and see...it's possible to have a problem with data...or take a logcat when the phone reeboots
[HTC Sensation] axetilen:
I can't generate the logcat because it stucks at HTC splashscreen

abd always said device not found

I'll try to backup and do it later

editted

After Formatting data -> reflash v3 and it still gets bootloops
[HTC Sensation] Stephen:
Weird I went from 2.5 test to 3.0 stable on vipers rom and it worked fine for me!!!!
[HTC Sensation] haifish9999:
I just flashed stables v3.0 and worked fine for me,got no bootlop and very smoothness.Try to use some hour and report back if got issue.( I went from SB to stables v3).
[HTC Sensation] pekaka:
real nice kernel,thanks,try v3
[HTC Sensation] axetilen:
how can I generate logs for this kernel???

It stucks at HTC and can't reach ViperS bootanimation => not enough for adb to find the device

or maybe, I'll try to flash Bricked kernel and then flash v3 over

I seem to me that this problem is quite similar to -100mV or something like that undervolting. Some chips can handle and the other ones are not
[HTC Sensation] XxXPachaXxX:
If you can't get boot animation you can't use adb. Your problem is during kernel load, nothing to do. It's not the data partition, it's the ramdisk or other low level things.

I getted a same problem, but my phone stuks at bootanimation. I think the ramdisk is corrupted now, probably because you and i have flashed too many kernels (test kernels, stable builds, a lot.)

So you can do only one thing, reflash viperS and then flash the latest kernel. Wait some minutes, i'm uploading the new version. I will do a clean intall on my phone.
[HTC Sensation] topjohnwu:
Keep up the great work!! Using this kernel makes my phone fly!!
[HTC Sensation] XxXPachaXxX:
Added stable3.1 version!
[HTC Sensation] axetilen:
still not work :(

the only way is to fullwipe vipers
[HTC Sensation] Super-Android:
Thanks for the upload, but m afraid still no help, the phone is stucking in the splash screen same as before...!! :confused: :confused:

Version 2 is working...!!
[HTC Sensation] XxXPachaXxX:
No more problems for me...do you get bootanimation?