• 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

HOG1 said:
I had 2 reboots with the 1.04 kernel. 1.35GHz - 162 GHz Wheatley. Gpu was at 400. One reboot earlier and one a few minutes ago.
Click to expand...
Can u get a last kmsg??? Did u clear data of ur kernel control app??? Me and starkraving have yet to have a reboot
 
I can't get a boot AT ALL on KitKat with KK beta kernel. Nothing but black screen.... Only tried to boot with PAC Rom so far. Anyone else?

I boot all other kernels fine on respective android OS versions, Lol:p


UPDATE: Got it to boot with AOKP, but boot up was weird and long and fragmented.... also apparently the KK kernel needs WiFi modules..... something about PAC ROM I think breaks root for me, which may be what's causing kernel problems with the KK kernel on that ROM.... Just speculating
 
DsyMnapTic said:
I can't get a boot AT ALL on KitKat with KK beta kernel. Nothing but black screen.... Only tried to boot with PAC Rom so far. Anyone else?

I boot all other kernels fine on respective android OS versions, Lol:p


UPDATE: Got it to boot with AOKP, but boot up was weird and long and fragmented.... also apparently the KK kernel needs WiFi modules..... something about PAC ROM I think breaks root for me, which may be what's causing kernel problems with the KK kernel on that ROM.... Just speculating
Click to expand...

No, the ramdisks are too different for it to work. Like I said previously, I can only guarantee it will work with CM11 until I can get an anykernel updater working. Phenom's boot.img has a block size that the usual tool doesn't like and I'm trying to find a workaround.

The challenge here is the way the system is set up. Boot.img contains a ramdisk, a kernel, and the kernel boot command. My releases so far are preassembled boot images. Anykernel deconstructs the image, replaces the kernel, and reconstructs, so that the kernel is inserted into any ROM.

There's a long weekend coming up, hopefully I get some time for this.

Anyone wanna help develop? :p
 
spock1104 said:
No, the ramdisks are too different for it to work. Like I said previously, I can only guarantee it will work with CM11 until I can get an anykernel updater working. Phenom's boot.img has a block size that the usual tool doesn't like and I'm trying to find a workaround.

The challenge here is the way the system is set up. Boot.img contains a ramdisk, a kernel, and the kernel boot command. My releases so far are preassembled boot images. Anykernel deconstructs the image, replaces the kernel, and reconstructs, so that the kernel is inserted into any ROM.

There's a long weekend coming up, hopefully I get some time for this.

Anyone wanna help develop? :p
Click to expand...

Oooohhhh, lol...... sorry dude, this is too much to take in and remember, lol I do remember you saying that now.... I just did a mad flash of three different ROMs with kernels trying to make sure to do everything right and remember what problems I was having, ...... okay cool thanks for clearing that up :rolleyes::D
 
Had another shut down today. When I boot back up there are no kernel error messages in Android Tuner Pro. It's not rebooting, it's shutting down.
 
HOG1 said:
Had another shut down today. When I boot back up there are no kernel error messages in Android Tuner Pro. It's not rebooting, it's shutting down.
Click to expand...

Make sure you're selecting last reboot in android tuner, otherwise grab /proc/last_kmsg
 
spock1104 said:
Make sure you're selecting last reboot in android tuner, otherwise grab /proc/last_kmsg
Click to expand...

I've done proc/last kmsg all three times, all it says is error loading message.
The 1.03 runs perfect for now. I wish I could get you the details on the shutdown to help things along though.
 
HOG1 said:
I've done proc/last kmsg all three times, all it says is error loading message.
The 1.03 runs perfect for now. I wish I could get you the details on the shutdown to help things along though.
Click to expand...

Believe me, I'd like to help too. There's the possibility that you had a bad download or flash. For the heck of it, check the MD5 on your 1.04 download and check if it matches what dev-host lists.
 
I'm lovin the kernel Spock, but the only problem I'm having is that thermal control won't stay on.
 
JHell said:
Just flashed the Awestruck_jb and SMASHED the HTC one x on quadrant standard
Click to expand...
This is my bench with my stock kernel and obviously my "L" Awe rom :cool:

ab3cfdc5b9cc199837ce43a69040463c.jpg
 
brittnearl said:
This is my bench with my stock kernel and obviously my "L" Awe rom :cool:

ab3cfdc5b9cc199837ce43a69040463c.jpg
Click to expand...

Hmmm, wow so you stomped it in memory.... way to go :rolleyes:



... which is probably because (according to specs) it has no SD card capabilities.

Don't get me wrong, it's still an awesome phone for the price, but if your entire bar was green all the way up to 5,000... you'd have a great I/O, but that's about it and you'd still have a higher score than a lot of other phones that were better in all actuality.
 
Worth posting here too.

I finally wrapped my head around how the frequencies are getting set, and rbheromax and I have been setting them incorrectly (curses jimsmith80!). In the frequency table there's a PLL specifier and a hex value. The hex value is a multiplier, and the PLL is the base frequency. HFPLL 2 is 13500Hz and HFPLL 1 is 27000Hz. To calculate the frequency you'll need to convert the hex multiplier to decimal. For example, the 1188000Hz clock is set by HFPLL1*0x2C, or 27000*44. So the max clock in AWEstruck is really 1620000 and the max clock in rbheromax's kernel is really 1728000.

Here's an accurate table we can use to correct our values https://github.com/Grarak/grakernel-msm8930/blob/grakernel/arch/arm/mach-msm/acpuclock-8930ab.c

AWEstruck clocks are accurate up to 1.512GHz. 1.674GHz is really 1.566GHz, and 1.728GHz is really 1.62GHz. Corrections to be made soon, and OC table expanded.
 
im looking into it now...
i got stuck, my kernel boots on powersave gov and lowest freq is 81 mhz :(
it seems to be SLOWLY booting and no errors in logcat, 10 mins now, i think i should pull battery and make a new build smh
 
Still trying to fix up the GPU OC code. I have it overclocking at this point, but going over 400MHz causes the display to stutter. I suspect the bus isn't scaling properly.
 
I smoothed out the GPU OC a bit, looks like I can't get it "perfect" or at least on my phone. I also corrected the CPU OC table. GPU is now booting at 533MHz though, so I need to work that out before I release. GPU OC may not be worth it :confused:
 
spock1104 said:
I smoothed out the GPU OC a bit, looks like I can't get it "perfect" or at least on my phone. I also corrected the CPU OC table. GPU is now booting at 533MHz though, so I need to work that out before I release. GPU OC may not be worth it :confused:
Click to expand...

I would bag the GPU oc and just focus on CPU.
 
You must log in or register to reply here.
Back
Top Bottom