yashsingh1/xdaforums huggingface dataset:
[HTC Amaze 4G] MentalDeath:
Was using EKF but then I just opted to do it manually to see if it worked and it did :S
[HTC Amaze 4G] Fahnix:
Nice! Glad to hear it worked out for you. :)

Sent from my FastAmaze :)
[HTC Amaze 4G] faux123:
Amaze kernel 008 Beta 7 is out! (paul@ubuntu #16 is the correct version for this)

http://www.multiupload.com/TXXQ444D38

Going back to use EKF again. Make sure you use a PC to do this. SDIO Interface is what Amaze uses to talk to the Modem. So here's Amaze's hardware architecture:

MSM8660 ==> MMC ==> WiFi Module (WiFi is treated as an MMC card)

. ==> SDIO ==> Cell Modem (Cell Modem is treated as an SD card)

{ build 7 }

re-enabled CPU OC

Updated USB, OTG, VIDC, Camera and DMA drivers from Telus Kernel source.

{ build 6 }

disabled CPU overclocking

{ build 5 }

sdio: Handle graceful shutdown

sdio: fix MCI_CLK corruption

driver/vibrator: reduce debug message spam to dmesg log

{ build 4 }

Added JRCU (thanks to Joe Korty!)

Patched MMC lock up issue

Removed additional Panasonic Gyro Log Spams

Patched RPC and SMD drivers

Enabled Performance Lock Screen Off settings
[HTC Amaze 4G] fcpelayo:
wow your faster than a bullet lol so 1. all you did was re enable the OC? and if yes 2. will I save more battery with beta6. 3. Do you want us to even continue to test beta 6 out for you or jump over to beta 7 and test that out instead?
[HTC Amaze 4G] terahybrid:
beta 4 was working good for me,

beta 5 freezes my screen once in a while in games and web also noticed my batt drained faster, I keep getting a report bug to htc as well

I will update to beta 7 now

is there a way to turn the key lights to auto or off on command

could this be the rouge app? I did not know but HTC gallery schedules to check for perfect pics and you can disable the schedule in it, even scanned created a folder named perfect pics and copied some of my pics to it that I have never taken with this phone.
[HTC Amaze 4G] Totòòò:
the key lights are to auto.
[HTC Amaze 4G] ickedmel:
Just to let you know with beta 6 I had no restarts.
[HTC Amaze 4G] fcpelayo:
crash on beta 5

Im not sure if this is useful to you as this is my first time posting a crash. So if its not then cool at least now i know how to pull last kmsg and upload it for next time. and if its good i hope its useful. file should be attached. this was on beta5 never touched OC so i assume its at 1.7 no UV using bp2.1 with baseband .07d
[HTC Amaze 4G] terahybrid:
thank you, my bad for not explaining I was wondering if we can turn the key lights off in command line/terminal then back to auto whenever we want.

how can htc miss the bleeding lights in r&d seriously :eek:
[HTC Amaze 4G] heyodee:
yes, you can. search /sys for backlight
[HTC Amaze 4G] ickedmel:
Faux on beta 7 default speed is set to about 1ghz that's what you intended I take it?
[HTC Amaze 4G] ickedmel:
Hmm I'm using ROM 2.1.0 bullet proof. Speeds will not stick, keeps dropping to 1.13 ghz.
[HTC Amaze 4G] faux123:
That's seemed to be a ROM issue. I am running on stock and I am experiencing no such issues. Everything is behaving as it should.
[HTC Amaze 4G] eliasadrian:
I know you have a ton of phones and work, but would it be helpful to run your phone on BulletProof or some other custom ROM to test your kernels? Either way, thanks!
[HTC Amaze 4G] faux123:
I debug kernels not Roms. If I use a custom ROM, it would make it difficult for me to troubleshoot my kernels. I need a stable Rom as a baseline and stock Rom is the most stable one.

So, in short no.
[HTC Amaze 4G] xboarder56:
Your problem not fauxes or mine
[HTC Amaze 4G] eliasadrian:
Fair enough, haha. Makes sense, too. Thanks man.
[HTC Amaze 4G] gaww:
I am on Bulletproof 2.1.0 and original .008. Have not had reboots and bootloops in days since i last flashed. Also, have not had any of the other issues others are having. I am also using system tuner, and speeds and screen off-profiles stick OK (voltages do for awhile).

For those have all the other misc. issues, I would recommend adding a wipe of the /system partition to you preflashing full wipe routine, as some of these issues my be noise carried over from previous flashes.

Question on flashing:

I have been using the EKF without issues, but you recommend flashing connected to computer, which I assume means flashing manually, so I am wondering what am I missing here?
[HTC Amaze 4G] seansk:
its not the rom nor the kernel, if you're using fauxclock, the speeds do not stick...try using system tuner app from the market instead...I had the same problem!! :)

https://market.android.com/details?id=ccc71.pmw&hl=en
[HTC Amaze 4G] ickedmel:
Yea I use system tuner app. The o/c speeds are sticking today not sure why it wasn't sticking last night, but thank you guys for the help.
[HTC Amaze 4G] hiazn:
Easy kernel flasher, ie ekf is connected to the computer.... You're missing the definitions..haha ;)
[HTC Amaze 4G] gaww:
Lol - guess so - was thinking of binary's tool - THAT is the easy one.

Plus, last time I flashed faux kernel (original .008) it was set up that way, so while my reference to ekf was off - the question remains. It flashes the kernel, so why connect to the computer?
[HTC Amaze 4G] aj_2423:
U have to connect to the computer and use ekf to flash beta 7 and the few betas before it. It is no longet set up to where you can flash it through CWM

sent from my Bulletproof Amaze w/faux .008 kernel
[HTC Amaze 4G] gaww:
Ok - that now makes sense (except it worked ok before - unless the newer beta's were not able to be flashed that way?).
[HTC Amaze 4G] aj_2423:
Exactly, beginning somewhere around beta 5 i believe. He switched back to EKF because for some reason it wasnt working for some people the other way. Pretty much, too much confusion and it for sure works using ekf so saves some trouble

sent from my Bulletproof Amaze w/faux .008 kernel
[HTC Amaze 4G] terahybrid:
Now the only problem I'm getting is wifi doesn't reconnect after waking the phone

Everything else seems ok so far my beta 5 issues are gone

edit: it gets stuck like this see pic
[HTC Amaze 4G] Fahnix:
Went into a bootloop after attempting to manually refresh facebook. Only other bootloop I have had with this kernel/rom combo is when I initially opened System Tuner. After rebooting everything was fine until now.

FastAmaze v1.1

2.6.35.13-g52e85af

paul@ubuntu #14 (I dont remember which kernel I stuck with. I think this is beta 5?)

Is this the right place to be posting these?

Should I include more info?

Thanks!
[HTC Amaze 4G] fcpelayo:
008 beta 7

UV -12.5 using system tuner

OC max
[HTC Amaze 4G] faux123:
Amaze kernel 008 Beta 8 is out! (paul@ubuntu #17 is the correct version for this)

http://www.multiupload.com/5ABPIP7VRR

Going back to use EKF again. Make sure you use a PC to do this. SDIO Interface is what Amaze uses to talk to the Modem. So here's Amaze's hardware architecture:

MSM8660 ==> MMC ==> WiFi Module (WiFi is treated as an MMC card)

. ==> SDIO ==> Cell Modem (Cell Modem is treated as an SD card)

{ build 8 }

disabled DeviceMapper Cache

restored original scheduler load calculation timing

{ build 7 }

re-enabled CPU OC

Updated USB, OTG, VIDC, Camera and DMA drivers from Telus Kernel source.

{ build 6 }

disabled CPU overclocking

{ build 5 }

sdio: Handle graceful shutdown

sdio: fix MCI_CLK corruption

driver/vibrator: reduce debug message spam to dmesg log

{ build 4 }

Added JRCU (thanks to Joe Korty!)

Patched MMC lock up issue

Removed additional Panasonic Gyro Log Spams

Patched RPC and SMD drivers

Enabled Performance Lock Screen Off settings
[HTC Amaze 4G] xologist:
awesome thanks
[HTC Amaze 4G] garveygibbs:
not being able to connect to hidden wifi networks, is it a rom thing or a kernel thing
[HTC Amaze 4G] hiazn:
8b8 #17 + bulletproof 2.2.0

:( Hopefully it's not kernel :) or Rom.

Clk 1.62ghz, btooth on, WiFi on, reading through xda app at the time.
[HTC Amaze 4G] Binary100100:
Here's one for #16.

Not sure which one it is... I lost count.

Clocked to 1.5Ghz, using wifi, bluetooh enabled but not in use, rebooted while charging on the dock.
[HTC Amaze 4G] kkholidaze:
Or search for screen filter on the market. Clean, simple, easy ;-)
[HTC Amaze 4G] faux123:
[22455.228610] binder: release 28001:28007 transaction 1964804 in, still active

[22455.228702] binder: send failed reply for transaction 1964804 to 28122:28272

[22455.229526] binder: send failed reply for transaction 1964817 to 28162:28182

[22455.229648] binder: send failed reply for transaction 1964820 to 28162:28244

[22455.229801] binder: send failed reply for transaction 1964830 to 28310:28310

[22455.229984] binder: send failed reply for transaction 1964833 to 28154:28154

[22455.230075] binder: send failed reply for transaction 1964839 to 28160:28160

[22455.230228] binder: send failed reply for transaction 1964840 to 28122:28208

[22455.230411] binder: send failed reply for transaction 1964841 to 28162:28224

[22455.230502] binder: release proc 28001, transaction 1964834, not freed

[22455.230686] binder: release proc 28001, transaction 1964835, not freed

[22455.230777] binder: release proc 28001, transaction 1964842, not freed

[22455.246402] binder: 28162:28182 transaction failed 29189(7), size 148-0

[22455.284641] binder: 28122:28272 transaction failed 29189(7), size 88-4

[22455.289310] binder: 28122:28321 transaction failed 29189(7), size 256-0

[22455.641634] binder: 28160:28160 transaction failed 29189(7), size 68-0

[22455.842683] binder: 28160:28160 transaction failed 29189(7), size 100-4

[22455.844515] binder: 28160:28160 transaction failed 29189(7), size 112-0

[22455.901613] binder: release 28160:28191 transaction 1964762 in, still active

[22455.901796] binder: send failed reply for transaction 1964762 to 28101:28305

[22455.903200] binder: 28101:28305 transaction failed 29189(7), size 80-4

[22456.028474] binder: 28162:28244 transaction failed 29189(7), size 84-0

[22456.519868] alarm_release: clear alarm, pending 0

[22456.519959] alarm_release: clear alarm, pending 0

[22456.520112] alarm_release: clear alarm, pending 0

[22456.966767] CPU1: msm_pm_power_collapse: change clock rate (old rate = 384000)

[22457.297486] [LS][CM3628] lightsensor_release

[22458.544495] request_suspend_state: wakeup (0->0) at 22458085168270 (2012-01-15 22:33:53.985491479 UTC)

[22458.555023] [NFC] pn544_dev_read wait_event_interruptible breaked ret=-512

[22458.582733] init: untracked pid 27919 exited

[22458.583130] init: untracked pid 28194 exited

[22458.584473] init: untracked pid 28310 exited

[22458.589203] init: untracked pid 28087 exited

[22458.591522] init: untracked pid 28172 exited

[22458.596069] init: untracked pid 28154 exited

[22458.596558] init: untracked pid 28166 exited

[22458.600250] [AUD] audio_acdb: acdb_release: ref count 0!

[22458.600403] [AUD] q6adm: adm_memory_unmap_regions

[22458.602112] init: untracked pid 28096 exited

[22458.607849] init: untracked pid 27918 exited

[22458.608704] init: untracked pid 28274 exited

Binary100100, I am not sure what to say, but I do notice that in many of your logs, you have lots of errors relating to untracked pid xxx exiting... What ROM are you using? I am now suspecting the ROM more than the kernel... I have not experienced any crash or boot loops myself with 100% stock ROM :(
[HTC Amaze 4G] faux123:
No idea why yours rebooted :(

[ 256.182644] emergency_remount bootloader (LINUX_REBOOT_CMD_RESTART2).

[ 256.182919] rmt_storage_client_shutdown: calling rmt_storage_force_sync... Client:rs300100a7

[ 256.191402] Emergency Sync complete

[ 256.191524] (pid 7) request emergency remount

[ 256.272854] [WLAN] currBss_HandleTriggerEvent(). eventID=0

[ 256.272976] [WLAN] currBSS_lowRssiThrCrossed

[ 256.273128] [WLAN] currBSS_reportRoamingEvent: trigger [6]

[ 256.331173] call alarm, type 2, func alarm_triggered+0x0/0xa8, 275869000000 (s 275869000000)

[ 256.483669] EXT4-fs (mmcblk0p29): re-mounted. Opts: (null)

[ 256.654871] [RMT] sdio_smem_cb: Received event 0

[ 256.655023] [RMT] Read done

[ 256.710474] EXT4-fs (mmcblk0p31): re-mounted. Opts: (null)

[ 256.728632] [RMT] rmt_storage_event_write_iovec_cb: write iovec callback received

[ 256.728723] [RMT] handle = 1

[ 256.728815] [RMT] sec_addr = 0, data_addr = 49717000, num_sec = 1503

[ 256.728906] [RMT] sec_addr = 1503, data_addr = 497d2e00, num_sec = 1

[ 256.729059] [RMT] iovec transfer count = 2

[ 256.729059]

[ 256.729242] [RMT] handle_rmt_storage_call: Sending result=0x0

[ 256.731928] [RMT] rmt_storage_ioctl: get shared memory parameters ioctl

[ 256.732111] [RMT] rmt_storage_ioctl: wait for request ioctl

[ 256.934228] EXT4-fs (mmcblk0p30): re-mounted. Opts: (null)

[ 256.934656] [RMT] rmt_storage_ioctl: send status ioctl

[ 256.934808] [RMT] rmt_storage_ioctl:	handle=1 err_code=0 data=0x20d2aac

[ 256.937189] rmt_storage_ioctl:rmc->msm_final_call=0, rmc->mdm_final_call=0

[ 256.937402] rmt_storage_client_shutdown: Wait for final MDM efs_sync: OK (rc = 925)

[ 256.937982] [BATT][tps65200] TPS65200 shutdown

[ 256.938959] Initiating msm_sdio_al_shutdown...

[ 256.939050] [SDAL_24]: msm_sdio_al_shutdown: Set the state to MODEM_RESTART for card 1

[ 256.939325] [SDAL_24]: msm_sdio_al_shutdown: Set the state to MODEM_RESTART for card 4

[ 256.940088] [SDAL_24]: msm_sdio_al_shutdown: sdio_release_irq for card 1

[ 256.946283] [USBDIAG] diag: sdio remove called

[ 256.948663] msm_sdio_al_shutdown complete.

[ 256.948785] charm_modem_shutdown: setting AP2MDM_STATUS low for a graceful restart (4)

[ 256.949213] adbd(parent:init): Restarting system with command 'bootloader'.

[ 256.949304] arch_reset: Going down for restart now.

[ 256.949487] arch_reset: mode 104

[ 256.949579] arch_reset: restart command `bootloader'.

[ 256.949762] from arch_reset

[ 256.949853] wait_rmt_final_call_back: Modem is not up, skip efs_sync

[ 256.949945] back arch_reset

It seemed so normal and ordinary, then BAM! requested reset :( So it's not a crash but a requested reset from PID 7 :(
[HTC Amaze 4G] Binary100100:
I'm using the latest Bulletproof. He included your kernel with his rom.

I guess I can always flash the stock kernel. For some reason I don't get any reboots with that. Strange because your kernel is pretty much stock anyway. Curious as to whats causing it. I'm starting to think it might have something to do with my dock or the dockmode app.
[HTC Amaze 4G] dj tray:
I'm loving the battery life with the new kernel.... F
[HTC Amaze 4G] govindar77:
Hey Binary,

Are you sure the kernel included in the ROM (BP2.2.0) is #16, which is beta 7? I could swear that it was beta 6 (#15). I say that because I had to flash #16 manually.

In the post with attachment you say you are on #16 but also that X included it in the ROM.

I know you are in a bad mood, but I'm just trying to help, 'cos I'm on the same ROM and kernel with no crashes. Of course, I'm not using the dock, so your speculation that it could be the dock or the dock app is quite possibly the reason for your crashes.

Cheers.
[HTC Amaze 4G] aj_2423:
Did u download it the first time he uploaded it or the 2nd time after he fixed something. The first on included beta 6 the second one included beta 7 because it was released in between the first and second upload.

sent from my Bulletproof Amaze w/faux .008 kernel
[HTC Amaze 4G] terahybrid:
found it thanks not by that name thou

even better awesome thanks

----------------------------------

only beta 5 has giving me problems but not reboots I'm on quicksense 3.0.0 rom, I used super wipe instead of CW wipe I dont think that makes a difference thou.
[HTC Amaze 4G] fcpelayo:
bp 2.2

faux 008 beta 8

no modification to oc or uv just installed it and ran it all day today and had this reboot.
[HTC Amaze 4G] Totòòò:
bp 2.2

paul #16

was trying to install rom manager when phone froze and rebooted..View attachment last_kmsg.rar
[HTC Amaze 4G] eliasadrian:
Had my first two reboots on BP 2.2.0 and Faux kernel 16, but I think it's cuz the app aDownloader. Here are the pastebin's, the first one was too big for pastebin so I deleted part of the beginning.

http://pastebin.com/uM0xWUCu

http://pastebin.com/SDTvsBjA
[HTC Amaze 4G] faux123:
1st one:

[ 1544.630437] Watchdog bark! Now = 1544.630407

[ 1544.630620] Watchdog last pet at 1535.480025

[ 1544.630926] msm_watchdog_suspend

[ 1544.631261]

[ 1544.631261]

[ 1544.631261] [htc_watchdog_top_stat] Start to dump:

[ 1544.635259] CPU Usage PID Name

[ 1544.635625] 72% 1383 .DroiDownloader

[ 1544.635808] 5% 917 com.htc.bg

[ 1544.635992] 3% 607 tiwlan_wq

[ 1544.636297] 0% 301 system_server

[ 1544.636480] 0% 123 emmc-qd

2nd one:

[ 634.962556] Watchdog bark! Now = 634.962526

[ 634.962861] Watchdog last pet at 626.554510

[ 634.963136] msm_watchdog_suspend

[ 634.963868]

[ 634.963899]

[ 634.963899] [htc_watchdog_top_stat] Start to dump:

[ 634.969911] CPU Usage PID Name

[ 634.970216] 85% 1353 .DroiDownloader

[ 634.970735] 4% 1880 re.rootexplorer

[ 634.971009] 2% 604 tiwlan_wq

[ 634.971284] 1% 301 system_server

[ 634.971803] 0% 77 kgsl-3d0/0

BOTH were caused by app hanging (.droiDownloader)
[HTC Amaze 4G] eliasadrian:
Thanks, that's what I assumed. But it's weird my whole phone restarts, I've never had a phone that just up and restarts cuz a bad app...bummer.
[HTC Amaze 4G] Totòòò:
I wonder if members know this kernel works with other 3.0 sense roms as well...would be interesting to know how it performs on those other roms...
[HTC Amaze 4G] gypsy214:
had anybody had this problem. im using the lates kernel and i have this problem even with oldest kernels, when ur phone dies, you plug it in, the red led turns on but flashes you leave it plug for several minutes but when you try to turn it on it wont. it just stayed there, well i have this and i have to use my friends amazed battery and when he puts mine in his phone it turns on with battery that you had charged
[HTC Amaze 4G] faux123:
Give this latest beta a serious try...
[HTC Amaze 4G] seansk:
I have stock rom rooted, no issues!!
[HTC Amaze 4G] aj_2423:
Yes. Just unplug the phone, wait a minute, then hold down the power button until it turns on
[HTC Amaze 4G] heyjoe66:
i'm guessing, the problem mite be in init.d scripts related to /proc/sys and sysctl.

like these:

echo "0" > /proc/sys/kernel/panic_on_oops
echo "0" > /proc/sys/kernel/tainted

echo "1" > /proc/sys/vm/laptop_mode
echo "0" > /proc/sys/vm/swappiness
echo "1000" > /proc/sys/vm/vfs_cache_pressure
echo "4096" > /proc/sys/vm/min_free_kbytes

such scripts included in every custom rom, but not in stock of-course.

i've already disabled mine one, but it'll take some time to test. it can run a whole day or even more before getting bootloop
[HTC Amaze 4G] gaww:
You may be on to something there. I do not use either, and have had no problems with faux kernels and BulletProff.
[HTC Amaze 4G] Binary100100:
Had another reboot but it wasn't doing anything at all.

http://pastebin.com/fubD68eX
[HTC Amaze 4G] Totòòò:
Hows baytery life btw?
[HTC Amaze 4G] xboarder56:
Faux just to teat something I'm gonna remove all init.ds from my Rom to see if that would change anything
[HTC Amaze 4G] terahybrid:
quick sense 3.0.0 here no problems

Yeah I had that with every custom ROM except stock, only works if you shutdown from the ROM
[HTC Amaze 4G] seansk:
I downclock back to 1.5 using system tuner, 1.7 is not needed for me. battery life is decent, 24 hours with light usage, about 10 hours with moderate usage and 5 hours with heavy usage :)
[HTC Amaze 4G] Totòòò:
thanks for the statistics provided. life battery is better with custom rom then
[HTC Amaze 4G] terahybrid:
same here and I agree. haven't done light usage but moderate about 10~12 hrs here, heavy about 5~6 hrs, those numbers are till I get %5 batt.

-------------------------------

my wifi not waking up in standby is fixed now in b8 thanks.
[HTC Amaze 4G] bmbrad:
Had a bootloop when I tried to watch a video online.

no undervolt

1.7-3

bp 2.2

8.7b kernal
[HTC Amaze 4G] heyjoe66:
in continue of topic,

spent hours of heavy gaming with charger plugged on, phone got crazy hot, but no bootloops so far

running almost stock rom and 008b7

but i'm still intending to find out, what particular tweak is causing troubles
[HTC Amaze 4G] faux123:
help pressure htcdev... I believe our kernel source is 1 version behind. I forgot the OTA package included a new kernel image but the kernel source was for the original phone release...

https://twitter.com/#!/faux123/status/159064571892604928

Beta bump below:
[HTC Amaze 4G] MentalDeath:
I don't think they care that much.. HTC is dropping the ball
[HTC Amaze 4G] seansk:
Yes in fact it is, I've been telling xboarder this and he knows about it as well I told him to change the original boot.img he provided for stock roms, its one behind!!! and messes with wifi, bluetooth and g-d knows what else!!!... the latest update has a new kernel!!! HTC needs to release this info wth!!!! seems like the only way to get it is to seek employment with HTC then release all these codes and sources blackmarket :p
[HTC Amaze 4G] saulcho009:
Yet Another last_kmsg

Another bootloop on 008b8 with BulletProof 2.2.1

I had the same experience HTC is currently giving us with my last phone, the Motorola Cliq. Motorola completely dropped the ball on us delaying our eclair update for months. By the time they released it, we already got Froyo running lol. Let's hope HTC will stop sitting and start walking.
[HTC Amaze 4G] :
I've loaded X's stock rooted rom 1.43 version to test the near stock theory that others seem to point to.

I've had bootloops on BeastMod and Senseless in the past trying this kernel. I'm happy to say that my device has now worked flawlessly for a whole day - which is longer than it has ever gone with this kernel and without a bootloop.

I re-enabled init.d and am running LoopySmoothness without any issues. There are no other scripts in the init.d folder.

I'm running the very latest faux beta kernel.
[HTC Amaze 4G] MentalDeath:
What radios are you guys running because I haven't gotten any bootloops on beta 7 (I think that's what it says in my sig). And I've used GPS, Data, wifi, wifi hotspot but no bluetooth and every thing is going very well and I have OC'd to max and UV'd quite a bit.
[HTC Amaze 4G] xboarder56:
Faux got another one stock rooted your kernel

http://pastebin.com/XCMQ4JMa
[HTC Amaze 4G] chrischoi:
\

Using b7, I haven't had the random bootloops. It was when I was watching Netflix, I think it's from overheating. No OC, just 1.512. I just didn't experience the random one's where they would happen in the middle of the night. Each beta is getting better and better.
[HTC Amaze 4G] saulcho009:
Here it is mine, maybe I should crop it and use it as my sig. I get bootloops
[HTC Amaze 4G] frodoboy:
I am using X's stock kernel with 2.2.1 and same radio as yours. I have absolutely no FCs or bootloops on that setup yet some have constant BLs and FCs with that one. I still don't get why some would have constant problems with either kernel and some don't have any problems at all. Maybe we should just get some testing going on different phones with absolutely the same exact apps running...basically stock bulletproof...and Faux's kernels for a few days and track what apps we use and then compare who is crashing and who isn't. This has got to be frustrating as hell to X and Faux!
[HTC Amaze 4G] brolic925t:
How do yu get the min values to stick?! THIS IS SO ANNOYING having to open fauxclock or systemtuner every 5 mins -_____-. Help please. It happens on both
[HTC Amaze 4G] heyjoe66:
oh yeah, this cpu is possessed
[HTC Amaze 4G] frodoboy:
Try SetCPU. Make sure you give it SuperUser permissions. Just choose your min and max (I also check On Demand) and then check "set on boot." Restart and see what happens. It should stick.

Edit: Also check to make sure you don't have more than one CPU oc app setting on boot. That could confuse things. Only run one app to overclock. Uncheck any others that might offer that option.
[HTC Amaze 4G] MentalDeath:
Odd I am running the same one but on BP 2.2.0. What are your setting OC/UV? Might be apps causing crashes then.
[HTC Amaze 4G] jjlean:
Ok. No bootloops on stock Rom for days. Used qik for video calls and boom bootloops

Fyi version with bulletproof