• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Help] Kernel Testers

its not exactly perfect......lololol
okay, its set to clock that way, to ensure I was actually reaching those speeds. I'll add in governors. Running the build since when I posted it yesterday (battery at 100%) and its just now getting to 33%.
Which governors would you guys like to see?
I would say wait for a KitKat release (so I can test it out, because all I'm doing is setting SELinux mode and putting the kernel with the ramdisk from cm11 which may or may not work....) i.e. SlimKat Paranoid CM11 Carbon etc.
 
rbheromax said:
its not exactly perfect......lololol
okay, its set to clock that way, to ensure I was actually reaching those speeds. I'll add in governors. Running the build since when I posted it yesterday (battery at 100%) and its just now getting to 33%.
Which governors would you guys like to see?
I would say wait for a KitKat release (so I can test it out, because all I'm doing is setting SELinux mode and putting the kernel with the ramdisk from cm11 which may or may not work....) i.e. SlimKat Paranoid CM11 Carbon etc.
Click to expand...

Yeah, but it'll get there. I think you're off to a great start. The stability test looked very promising, especially the battery temps, which was my biggest concern, other than maybe a boot loop, but that's easy to fix. Could you throw in some of the standards, like smartassV2, Wheatley, and interactive? Personally I tend to default to interactive when its available. I really think its amazing that you can even get this phone to 2.1Ghz, pretty epic if you ask me. That's what, about a 90% OC? I remember there was trouble just getting to 1.8 awhile back.

Edit: Its a %78.47 OC. woke up enough to do the math. Niceness!
 
modhatter6811 said:
Yeah, but it'll get there. I think you're off to a great start. The stability test looked very promising, especially the battery temps, which was my biggest concern, other than maybe a boot loop, but that's easy to fix. Could you throw in some of the standards, like smartassV2, Wheatley, and interactive? Personally I tend to default to interactive when its available. I really think its amazing that you can even get this phone to 2.1Ghz, pretty epic if you ask me. That's what, about a 90% OC? I remember there was trouble just getting to 1.8 awhile back.

Edit: Its a %78.47 OC. woke up enough to do the math. Niceness!
Click to expand...

I'll add those in.


devs (or anyone willing to help) please stop by #zte8930 on freenode. That way we can test with all types of chips (good and bad) and make it compatible for everyone
 
JHell said:
2.1 GHz would b sweet for this phone. Oc the graphics and this would b a pocket laptop
Click to expand...
Working on GPU oc. Hard part is, I'm working on a 85 kbps connection so just cherry picking commits isn't as instant as it sounds. I'm going to probably have to manually apply the commits by looking at the diff for all the commits made. I also want to increase screen sensitivity. Is the screen both resistive and capacitive????
 
JHell said:
2.1 GHz would b sweet for this phone. Oc the graphics and this would b a pocket laptop
Click to expand...
Just a small question but y push limits?? I feel we should concentrate on stability :) yes i like oc too but y not stop at a realistic oc of 1.5 cpu and 500 gpu with no mp decision and stock default speeds... Its like putting a turbo on a stock engine... Yes it will run good but not for ever
 
I can agree with that. A 2.1 is awesome, and I think its fantastic that this phone can be pushed so hard, but it wouldn't be very practical for an everyday basis. It would mean needing a new phone a whole lot earlier. Personally, I'd love to test the GPU @500, wait a sec, can't we also force GPU rendering? (that could make for some fun testing :D)
 
@rbheromax I'd love to give this kernel a try, but I came a bit late to the party and both of the download links have expired. Could you reupload them and update the OP when you get a chance? Thanks!>
 
SpotComms said:
@rbheromax I'd love to give this kernel a try, but I came a bit late to the party and both of the download links have expired. Could you reupload them and update the OP when you get a chance? Thanks!>
Click to expand...

I'll have a trial period for an updated version today, I found some problems in the kernel source I need to fix up
 
shell@android:/sdcard # lsmod
zcache 33129 0 [permanent], Live 0x00000000 (C)
zram 9924 0 - Live 0x00000000 (C)
zsmalloc 6877 2 zcache,zram, Live 0x00000000 (C)
wlan 2546359 0 - Live 0x00000000 (C)
shell@android:/sdcard #

zram had problems this morning, seems to insmod fine now, anyone know how to configure this properly? (on the OS side, because that's not really my thing)
 
rbheromax said:
shell@android:/sdcard # lsmod
zcache 33129 0 [permanent], Live 0x00000000 (C)
zram 9924 0 - Live 0x00000000 (C)
zsmalloc 6877 2 zcache,zram, Live 0x00000000 (C)
wlan 2546359 0 - Live 0x00000000 (C)
shell@android:/sdcard #

zram had problems this morning, seems to insmod fine now, anyone know how to configure this properly? (on the OS side, because that's not really my thing)
Click to expand...

Why can't you do it in the ramdisk
 
rbheromax said:
insmod is fine. I did that thru init scripting but I mean there is another part to zram that needs to be configured system side
Click to expand...

I think what you're referring to is setting the threshold values for the framework config.xml. which would be this.

<!-- Device configuration setting the /proc/sys/vm/extra_free_kbytes tunable in the kernel (if it exists). A high value will increase the amount of memory that the kernel tries to keep free, reducing allocation time and causing the lowmemorykiller to kill earlier. A low value allows more memory to be used by processes but may cause more allocations to block waiting on disk I/O or lowmemorykiller. Overrides the default value chosen by ActivityManager based on screen size. 0 prevents keeping any extra memory over what the kernel keeps by default. -1 keeps the default. -->
<integer name="config_extraFreeKbytesAbsolute">-1</integer>

<!-- Device configuration adjusting the /proc/sys/vm/extra_free_kbytes tunable in the kernel (if it exists). 0 uses the default value chosen by ActivityManager. A positive value will increase the amount of memory that the kernel tries to keep free, reducing allocation time and causing the lowmemorykiller to kill earlier. A negative value allows more memory to be used by processes but may cause more allocations to block waiting on disk I/O or lowmemorykiller. Directly added to the default value chosen by ActivityManager based on screen size. -->
<integer name="config_extraFreeKbytesAdjust">0</integer>

If not my next guess, would be to look at fstab, and make sure this line is present. /dev/block/zram0 none swap defaults zramsize=<size in bytes>,swapprio=<swap partition priority> Note, that swapprio might not be needed, I'm not sure if we have more than one swap. If not it, then it isn't needed. I'm guessing you have fstab nailed down already though. You have much more experience then I do, I'm sure of it.
 
modhatter6811 said:
I think what you're referring to is setting the threshold values for the framework config.xml. which would be this.

<!-- Device configuration setting the /proc/sys/vm/extra_free_kbytes tunable in the kernel (if it exists). A high value will increase the amount of memory that the kernel tries to keep free, reducing allocation time and causing the lowmemorykiller to kill earlier. A low value allows more memory to be used by processes but may cause more allocations to block waiting on disk I/O or lowmemorykiller. Overrides the default value chosen by ActivityManager based on screen size. 0 prevents keeping any extra memory over what the kernel keeps by default. -1 keeps the default. -->
<integer name="config_extraFreeKbytesAbsolute">-1</integer>

<!-- Device configuration adjusting the /proc/sys/vm/extra_free_kbytes tunable in the kernel (if it exists). 0 uses the default value chosen by ActivityManager. A positive value will increase the amount of memory that the kernel tries to keep free, reducing allocation time and causing the lowmemorykiller to kill earlier. A negative value allows more memory to be used by processes but may cause more allocations to block waiting on disk I/O or lowmemorykiller. Directly added to the default value chosen by ActivityManager based on screen size. -->
<integer name="config_extraFreeKbytesAdjust">0</integer>

If not my next guess, would be to look at fstab, and make sure this line is present. /dev/block/zram0 none swap defaults zramsize=<size in bytes>,swapprio=<swap partition priority> Note, that swapprio might not be needed, I'm not sure if we have more than one swap. If not it, then it isn't needed. I'm guessing you have fstab nailed down already though. You have much more experience then I do, I'm sure of it.
Click to expand...

That's only for KitKat. He's need it for jellybean
 
You must log in or register to reply here.
Back
Top Bottom