• 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 think the heat issue is due to memory use because I noticed that when it gets too hot, I use task manager via rom toolbox and kill all. Immediately replug my charger and it works instantly. Phone also cools off within 10 seconds or so of killing tasks. I set app process background limits to 4, seems to have helped a lot. Nice work btw! Pretty smooth. ;-)
 
brittnearl said:
Agreed lots of obsolete code from previous devices eg: lock screen, also theres code for sim eg: network controller, so probably incomplete or obsolete kernel source
Click to expand...

I mentioned this stuff when I was building AWEsome in irc. It just seemed weird to me that any of this stuff was put in there. Like 4g code in xml's. Its not even a 4g capable device?! I was told to let it as is, but if taken out it may reduce the rom size dramatically
 
I can see leaving it while trying to get things working, but once it works then removing bloat is a worthy cause.
 
dragonhart6505 said:
I mentioned this stuff when I was building AWEsome in irc. It just seemed weird to me that any of this stuff was put in there. Like 4g code in xml's. Its not even a 4g capable device?! I was told to let it as is, but if taken out it may reduce the rom size dramatically
Click to expand...

I believe it's because ZTE is a mass manufacturer of inexpensive handsets and probably used the same device tree for as many devices as they could get booting. Its cost effective and they don't have to care about firmware updates or maintenance updates because they can say..."what do you want for 59.95?" Sadly that's my take on it.
 
starkraving said:
I believe it's because ZTE is a mass manufacturer of inexpensive handsets and probably used the same device tree for as many devices as they could get booting. Its cost effective and they don't have to care about firmware updates or maintenance updates because they can say..."what do you want for 59.95?" Sadly that's my take on it.
Click to expand...

Pretty much this.
Looks like its up to us to clean it up
 
I got the prima driver to fully compile but I think I did something seriously wrong. The module is 38MB in size!
 
spock1104 said:
I got the prima driver to fully compile but I think I did something seriously wrong. The module is 38MB in size!
Click to expand...
Nope, unless I was doing something entirely wrong as well! I have no idea why it builds that large, but it does. I tried with MANY versions of the prima driver, all to the same extent.

Edit: However, it SHOULDN'T be that large, since the stock module is only a few mb. :/
 
cooldudezach said:
Nope, unless I was doing something entirely wrong as well! I have no idea why it builds that large, but it does. I tried with MANY versions of the prima driver, all to the same extent.

Edit: However, it SHOULDN'T be that large, since the stock module is only a few mb. :/
Click to expand...

I figured out the size issue last night, have to disable debug options in the defconfig or else it will debug statement all the things! Unfortunately this came after I replaced the wcnss driver with the one from the 8x30 common kernel, which didn't want to load. The cm11 nexus 4 driver did load when I tried it Saturday, so I'll give that another try tonight now that I understand the prima module better.
 
spock1104 said:
I figured out the size issue last night, have to disable debug options in the defconfig or else it will debug statement all the things! Unfortunately this came after I replaced the wcnss driver with the one from the 8x30 common kernel, which didn't want to load. The cm11 nexus 4 driver did load when I tried it Saturday, so I'll give that another try tonight now that I understand the prima module better.
Click to expand...
Wait, you DID?!? Please share what needs to be disabled to keep the filesize down. :)
 
Latest result:

Code: 
<4>[05-20 03:02:43.477] [0][2785: insmod]wlan: module is from the staging direct
ory, the quality is unknown, you have been warned.
<6>[05-20 03:02:43.527] [0][2785: insmod]wlan: loading driver v3.2.2.17
<3>[05-20 03:02:43.527] [0][2785: insmod]wlan: [2785:E :HDD] hdd_apply_cfg_ini:
Reg Parameter BtAmpPreferredChannel < allowed Minimum [0 < 1]. Enforcing Default
= 1
<3>[05-20 03:02:43.527] [1][2785: insmod]wlan: [2785:E :CTL] WCTS_OpenTransport:
 smd_named_open_on_edge failed with status -19
<2>[05-20 03:02:43.527] [1][2785: insmod]wlan: [2785:F :CTL] WDI_Init: Failed to
 open WCTS transport
<3>[05-20 03:02:43.527] [1][2785: insmod]wlan: [2785:E :WDA] WDI Init failed
<3>[05-20 03:02:43.527] [1][2785: insmod]wlan: [2785:F :VOS] vos_open: Failed to
 open WDA module
<2>[05-20 03:02:43.527] [1][2785: insmod]VOS ASSERT in vos_open Line 339
<4>[05-20 03:02:43.527] [1][2785: insmod]------------[ cut here ]------------
<4>[05-20 03:02:43.537] [1][2785: insmod]WARNING: at drivers/staging/prima/CORE/
VOSS/src/vos_api.c:339 vos_open+0x3cc/0x524 [wlan]()
<4>[05-20 03:02:43.537] [1][2785: insmod]Modules linked in: wlan(C+)
<4>[05-20 03:02:43.537] [1][2785: insmod][<c0017148>] (unwind_backtrace+0x0/0x13
8) from [<c0093258>] (warn_slowpath_null+0x38/0xa8)
<4>[05-20 03:02:43.537] [1][2785: insmod][<c0093258>] (warn_slowpath_null+0x38/0
xa8) from [<bf14caf0>] (vos_open+0x3cc/0x524 [wlan])
<4>[05-20 03:02:43.537] [1][2785: insmod][<bf14caf0>] (vos_open+0x3cc/0x524 [wla
n]) from [<bf0387b4>] (hdd_wlan_startup+0x880/0x1224 [wlan])
<4>[05-20 03:02:43.537] [1][2785: insmod][<bf0387b4>] (hdd_wlan_startup+0x880/0x
1224 [wlan]) from [<bf2f70cc>] (hdd_module_init+0xcc/0x21c [wlan])
<4>[05-20 03:02:43.537] [1][2785: insmod][<bf2f70cc>] (hdd_module_init+0xcc/0x21
c [wlan]) from [<c0008938>] (do_one_initcall+0x10c/0x170)
<4>[05-20 03:02:43.537] [1][2785: insmod][<c0008938>] (do_one_initcall+0x10c/0x1
70) from [<c00e7760>] (sys_init_module+0x980/0x1698)
<4>[05-20 03:02:43.537] [1][2785: insmod][<c00e7760>] (sys_init_module+0x980/0x1
698) from [<c000f860>] (ret_fast_syscall+0x0/0x30)
<4>[05-20 03:02:43.537] [1][2785: insmod]---[ end trace da227214a82491c0 ]---
<3>[05-20 03:02:43.537] [1][2785: insmod]wlan: [2785:F :HDD] hdd_wlan_startup: v
os_open failed
<3>[05-20 03:02:43.537] [1][2785: insmod]wlan: [2785:F :HDD] hdd_driver_init: WL
AN Driver Initialization failed
<3>[05-20 03:02:43.537] [1][2785: insmod]wlan: driver load failure
 
cooldudezach said:
Wait, you DID?!? Please share what needs to be disabled to keep the filesize down. :)
Click to expand...

This will come with the driver commit once I have it working, but in nex_defconfig disable any option that contains "DEBUG." These really shouldn't be on anyways unless trying to troubleshoot specific issues.
 
OP updated with the new version.

I had to add back most of the debug, my phone went into a reboot loop. IE someone didn't pay attention to their IFDEFs while adding code. I'll have to disable debug one by one until I find what caused the loop. I at least removed the debug that mattered to the module size.


To get 3G working in 1.01, update PRL and profile, and reboot.
 
spock1104 said:
OP updated with the new version.

I had to add back most of the debug, my phone went into a reboot loop. IE someone didn't pay attention to their IFDEFs while adding code. I'll have to disable debug one by one until I find what caused the loop. I at least removed the debug that mattered to the module size.


To get 3G working in 1.01, update PRL and profile, and reboot.
Click to expand...

To return to stock are stock modules needed for wifi??
 
brittnearl said:
I could do that was just curious thanks
Click to expand...

That would be great. You'll need to grab /system/lib/modules/prima/prima_wlan.ko and the contents of /system/etc/firmware/wlan/prima/, and of course the stock boot.img

During the install I don't remove any files so nothing else should need replacing.
 
brittnearl said:
So far kernel working great :) auto wifi connect works as well
Click to expand...

Thanks! I somehow broke my phone last night so that when I turned on WiFi my 3G gave out. I reflashed and it seems to be working fine now. I'm correcting the mistakes you found in 1.01 and updating the OP with 1.01a.
 
I'd like to add in undervolting next, if anyone knows of any compatible examples I can follow I'd be much appreciative.

I'd also like recommendations for CPU governors and I/O governors, I don't want to go adding too many.
 
spock1104 said:
I'd also like recommendations for CPU governors and I/O governors, I don't want to go adding too many.
Click to expand...

Interactivex, smartass/v2, wheatley cpu govs would be great.

Fiops is a MUST for i/o. Best gov ive used on every phone ive had recently.

As for similar kernels, check out the SIII/Nexus. I know the CPU is different, but ive noticed quite a few similarities in the git's so maybe you'd have some luck there.

Would absolutely adore a Dirty-V kernel for the awe!

Also if your planning on o/c'ing the GPU id recommend starting out VERY lightly until your sure you know where you can make it stable. In previous attempts by cdz/rb we got it to go well at around 415mhz. Anything higher and it killed performance all around. May have just been code error and this was very early on, but just a suggestion
 
You must log in or register to reply here.
Back
Top Bottom