Guest MCZQ Posted January 1, 2012 Report Share Posted January 1, 2012 (edited) Has anyone had any lucking building an OC kernel that supports Wifi? Thanks, Adam Hello, Yes I have had luck. Today I built the sources from Tom's git repo, enabled SmartAassV2 and overclocking. Seems stable at 1017mhz. For wifi, I followed this http://forum.xda-dev...04&postcount=34 and this allowed the old (stock?) wifi module (dhd.ko) to load up ignoring vermagic errors. I was unable to get the newly compiled dhd.ko from Tom's source to load. To confirm I have overclocking + wifi on my T-Mobile Vivacity. Edited January 1, 2012 by MCZQ Link to comment Share on other sites More sharing options...
Guest raverrr Posted January 1, 2012 Report Share Posted January 1, 2012 Hello, Yes I have had luck. Today I built the sources from Tom's git repo, enabled SmartAassV2 and overclocking. Seems stable at 1017mhz. For wifi, I followed this http://forum.xda-dev...04&postcount=34 and this allowed the old (stock?) wifi module (dhd.ko) to load up ignoring vermagic errors. I was unable to get the newly compiled dhd.ko from Tom's source to load. To confirm I have overclocking + wifi on my T-Mobile Vivacity. good news :) is the front facing camera supported? Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted January 1, 2012 Report Share Posted January 1, 2012 Hello, Yes I have had luck. Today I built the sources from Tom's git repo, enabled SmartAassV2 and overclocking. Seems stable at 1017mhz. For wifi, I followed this http://forum.xda-dev...04&postcount=34 and this allowed the old (stock?) wifi module (dhd.ko) to load up ignoring vermagic errors. I was unable to get the newly compiled dhd.ko from Tom's source to load. To confirm I have overclocking + wifi on my T-Mobile Vivacity. Proof? Link to comment Share on other sites More sharing options...
Guest MCZQ Posted January 1, 2012 Report Share Posted January 1, 2012 (edited) good news :) is the front facing camera supported? Edit: Nope front camera busted. Proof? Edited January 1, 2012 by MCZQ Link to comment Share on other sites More sharing options...
Guest Russ_uk Posted January 1, 2012 Report Share Posted January 1, 2012 Nice Screenshots MCZQ! What are your Quadrant results looking like since the OC? Link to comment Share on other sites More sharing options...
Guest MCZQ Posted January 1, 2012 Report Share Posted January 1, 2012 Nice Screenshots MCZQ! What are your Quadrant results looking like since the OC? The scores do not mean much to me, care to comment? 1032stock kernel 1367OC to 1017mhz. Link to comment Share on other sites More sharing options...
Guest Dop3KinG Posted January 1, 2012 Report Share Posted January 1, 2012 Hello, Yes I have had luck. Today I built the sources from Tom's git repo, enabled SmartAassV2 and overclocking. Seems stable at 1017mhz. For wifi, I followed this http://forum.xda-dev...04&postcount=34 and this allowed the old (stock?) wifi module (dhd.ko) to load up ignoring vermagic errors. I was unable to get the newly compiled dhd.ko from Tom's source to load. To confirm I have overclocking + wifi on my T-Mobile Vivacity. Could you please post link to kernel i'd love to try it out Link to comment Share on other sites More sharing options...
Guest MCZQ Posted January 1, 2012 Report Share Posted January 1, 2012 Could you please post link to kernel i'd love to try it out Ok here you go. http://www.megaupload.com/?d=PBLUEHNY Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted January 1, 2012 Report Share Posted January 1, 2012 Hello, Yes I have had luck. Today I built the sources from Tom's git repo, enabled SmartAassV2 and overclocking. Seems stable at 1017mhz. For wifi, I followed this http://forum.xda-dev...04&postcount=34 and this allowed the old (stock?) wifi module (dhd.ko) to load up ignoring vermagic errors. I was unable to get the newly compiled dhd.ko from Tom's source to load. To confirm I have overclocking + wifi on my T-Mobile Vivacity. Any chance of porting a kernel for the SFII? Link to comment Share on other sites More sharing options...
Guest Dop3KinG Posted January 1, 2012 Report Share Posted January 1, 2012 Ok here you go. http://www.megaupload.com/?d=PBLUEHNY Many Thanks :D Link to comment Share on other sites More sharing options...
Guest Simon O Posted January 2, 2012 Report Share Posted January 2, 2012 Any chance of porting a kernel for the SFII? Vivacity and SF2 will be able to use the same kernel. Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted January 2, 2012 Report Share Posted January 2, 2012 (edited) Vivacity and SF2 will be able to use the same kernel. Nope, I tried it on my SFII to see what would happen and I was getting the same problem with the tracking (i.e. getting wrong key presses while using the keyboard) so I flashed the stock orange kernel again but obviously the overclock was gone. Edited January 2, 2012 by PsYcHoKiLLa Link to comment Share on other sites More sharing options...
Guest MCZQ Posted January 2, 2012 Report Share Posted January 2, 2012 The code seems missing for the front camera + the Sanfrancisco II touchscreen as it differs from the Vivacity. Stock kernel seems to have the option to work with both devices. So ZTE are holding out on us? :( Link to comment Share on other sites More sharing options...
Guest jasonleeds Posted January 2, 2012 Report Share Posted January 2, 2012 are these the same ones as these? goo.gl/6Xm8W been poking about the zte site and found these..not sure if theyre the same ones. Link to comment Share on other sites More sharing options...
Guest MCZQ Posted January 11, 2012 Report Share Posted January 11, 2012 (edited) are these the same ones as these? goo.gl/6Xm8W been poking about the zte site and found these..not sure if theyre the same ones. Same as the stuff linked in the first post here. Which ls also missing front camera (OVM7690?) and the dual touchscreen support (CONFIG_TOUCHSCREEN_MXT224_P736V?). Has anyone tried emailing them? I will give it a shot. Edited January 11, 2012 by MCZQ Link to comment Share on other sites More sharing options...
Guest bunnygirl222 Posted January 23, 2012 Report Share Posted January 23, 2012 Ok here you go. http://www.megaupload.com/?d=PBLUEHNY Would anyone be able to upload this to a new file host? :unsure: Link to comment Share on other sites More sharing options...
Guest Fuzzra Posted February 11, 2012 Report Share Posted February 11, 2012 (edited) The touchscreen issue with the SFII got on my nerves a bit, so I took it upon myself to attemp to pull the right configuration from a running kernel. After some learning and quite a lot of swearing I seem to have found some workable config numbers. To get things working we need to look in drivers/input/touchscreen for atmel_config.c and add this directly between #elif defined(CONFIG_MACH_BLADE2) and .version = 0x16, #if defined(CONFIG_TOUCHSCREEN_MXT224_P736V) .version = 0x16, .source = 1, .abs_x_min = 0, .abs_x_max = 479, .abs_y_min = 0, .abs_y_max = 799, .abs_pressure_min = 0, .abs_pressure_max = 255, .abs_width_min = 0, .abs_width_max = 15, .gpio_irq = 29, .power = atmel_platform_power, .config_T7[0] = 50, .config_T7[1] = 12, .config_T7[2] = 25, .config_T8[0] = 6, .config_T8[1] = 5, .config_T8[2] = 10, .config_T8[3] = 10, .config_T8[4] = 0, .config_T8[5] = 0, .config_T8[6] = 255, .config_T8[7] = 1, .config_T8[8] = 0, .config_T8[9] = 0, .config_T9[0] = 131, .config_T9[1] = 0, .config_T9[2] = 2, .config_T9[3] = 14, .config_T9[4] = 9, .config_T9[5] = 0, .config_T9[6] = 16, .config_T9[7] = 70, .config_T9[8] = 3, .config_T9[9] = 1, .config_T9[10] = 10, .config_T9[11] = 10, .config_T9[12] = 32, .config_T9[13] = 32, .config_T9[14] = 2, .config_T9[15] = 10, .config_T9[16] = 30, .config_T9[17] = 30, .config_T9[18] = 31, .config_T9[19] = 3, .config_T9[20] = 223, .config_T9[21] = 1, .config_T9[22] = 15, .config_T9[23] = 13, .config_T9[24] = 25, .config_T9[25] = 23, .config_T9[26] = 208, .config_T9[27] = 63, .config_T9[28] = 208, .config_T9[29] = 90, .config_T9[30] = 15, .config_T9[31] = 0, .config_T15[0] = 0, .config_T15[1] = 0, .config_T15[2] = 0, .config_T15[3] = 0, .config_T15[4] = 0, .config_T15[5] = 0, .config_T15[6] = 0, .config_T15[7] = 0, .config_T15[8] = 0, .config_T18[0] = 0, .config_T18[1] = 0, .config_T19[0] = 0, .config_T19[1] = 0, .config_T19[2] = 0, .config_T19[3] = 0, .config_T19[4] = 0, .config_T19[5] = 0, .config_T19[6] = 0, .config_T19[7] = 0, .config_T19[8] = 0, .config_T19[9] = 0, .config_T19[10] = 0, .config_T19[11] = 0, .config_T20[0] = 25, .config_T20[1] = 1, .config_T20[2] = 1, .config_T20[3] = 1, .config_T20[4] = 1, .config_T20[5] = 0, .config_T20[6] = 0, .config_T20[7] = 0, .config_T20[8] = 0, .config_T20[9] = 0, .config_T20[10] = 0, .config_T20[11] = 0, .config_T22[0] = 13, .config_T22[1] = 0, .config_T22[2] = 0, .config_T22[3] = 25, .config_T22[4] = 0, .config_T22[5] = 231, .config_T22[6] = 255, .config_T22[7] = 8, .config_T22[8] = 25, .config_T22[9] = 0, .config_T22[10] = 1, .config_T22[11] = 0, .config_T22[12] = 17, .config_T22[13] = 31, .config_T22[14] = 57, .config_T22[15] = 65, .config_T22[16] = 8, .config_T23[0] = 0, .config_T23[1] = 0, .config_T23[2] = 0, .config_T23[3] = 0, .config_T23[4] = 0, .config_T23[5] = 0, .config_T23[6] = 0, .config_T23[7] = 0, .config_T23[8] = 0, .config_T23[9] = 0, .config_T23[10] = 0, .config_T23[11] = 0, .config_T23[12] = 0, .config_T24[0] = 0, .config_T24[1] = 0, .config_T24[2] = 0, .config_T24[3] = 0, .config_T24[4] = 0, .config_T24[5] = 0, .config_T24[6] = 0, .config_T24[7] = 0, .config_T24[8] = 0, .config_T24[9] = 0, .config_T24[10] = 0, .config_T24[11] = 0, .config_T24[12] = 0, .config_T24[13] = 0, .config_T24[14] = 0, .config_T24[15] = 0, .config_T24[16] = 0, .config_T24[17] = 0, .config_T24[18] = 0, .config_T25[0] = 0, .config_T25[1] = 0, .config_T25[2] = 0, .config_T25[3] = 0, .config_T25[4] = 0, .config_T25[5] = 0, .config_T25[5] = 0, .config_T25[6] = 0, .config_T25[7] = 0, .config_T25[8] = 0, .config_T25[9] = 0, .config_T27[0] = 0, .config_T27[1] = 0, .config_T27[2] = 0, .config_T27[3] = 0, .config_T27[4] = 0, .config_T27[5] = 0, .config_T27[6] = 0, .config_T28[0] = 0, .config_T28[1] = 0, .config_T28[2] = 2, .config_T28[3] = 16, .config_T28[4] = 16, .config_T28[5] = 0, .object_crc[0] = 0, .object_crc[1] = 32, .object_crc[2] = 16, .cable_config[0] = 10, .cable_config[1] = 32, .cable_config[2] = 32, .cable_config[3] = 117, .GCAF_level[0] = 4, .GCAF_level[1] = 16, .GCAF_level[2] = 0, .GCAF_level[3] = 0, .filter_level[0] = 100, .filter_level[1] = 100, .filter_level[2] = 100, .filter_level[3] = 100, .display_width = 1024, /* display width in pixel */ .display_height = 1024, /* display height in pixel */ #else Then pop a #endif above /*ZTE_TS_ZFJ_20110425 end*/ To give us the P763V touchscreen option we also need to shove something in Kbuild in the same directory. Above config TOUCHSCREEN_CYTTSP_I2C insert: config TOUCHSCREEN_MXT224_P736V bool "P736V Touchscreen" depends on TOUCHSCREEN_MXT224 default n help Say Y here if you have a P736V / Orange San Francisco II. Now I think I'm going to sit in a darkened room and re-evaluate my life choices. :P *Edited To add nicer numbers and a boot image to play with If you've been dying to play with an overclockable kernel for the SFII and don't mind losing the front camera, here you go. Obviously I take no responsibility if it causes nether hells to open in your kitchen or gives your aunt shingles. Edited February 12, 2012 by Fuzzra Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 11, 2012 Report Share Posted February 11, 2012 The touchscreen issue with the SFII got on my nerves a bit, so I took it upon myself to attemp to pull the right configuration from a running kernel. After some learning and quite a lot of swearing I seem to have found some workable config numbers. To get things working we need to look in drivers/input/touchscreen for atmel_config.c and add this directly between #elif defined(CONFIG_MACH_BLADE2) and .version = 0x16, #if defined(CONFIG_TOUCHSCREEN_MXT224_P736V) .version = 0x16, .source = 1, .abs_x_min = 0, .abs_x_max = 479, .abs_y_min = 0, .abs_y_max = 799, .abs_pressure_min = 0, .abs_pressure_max = 255, .abs_width_min = 0, .abs_width_max = 15, .gpio_irq = 29, .power = atmel_platform_power, .config_T7[0] = 0x32, .config_T7[1] = 12, .config_T7[2] = 25, .config_T8[0] = 6, .config_T8[1] = 5, .config_T8[2] = 10, .config_T8[3] = 10, .config_T8[4] = 0, .config_T8[5] = 0, .config_T8[6] = 10, .config_T8[7] = 6, .config_T8[8] = 0, .config_T8[9] = 0, .config_T9[0] = 0x83, .config_T9[1] = 0, .config_T9[2] = 2, .config_T9[3] = 14, .config_T9[4] = 9, .config_T9[5] = 0, .config_T9[6] = 16, .config_T9[7] = 45, .config_T9[8] = 3, //.config_T9[9] = 6, .config_T9[9] = 1, .config_T9[10] = 10, .config_T9[11] = 6, .config_T9[12] = 6, .config_T9[13] = 0x0, .config_T9[14] = 2, .config_T9[15] = 10, .config_T9[16] = 30, .config_T9[17] = 30, .config_T9[18] = 0x1f, .config_T9[19] = 3, .config_T9[20] = 0xdf, .config_T9[21] = 1, //.config_T9[18] = 0x40, //.config_T9[19] = 0x01, //.config_T9[20] = 0xdf, //.config_T9[21] = 0x01, //.config_T9[18] = 223, //.config_T9[19] = 1, //.config_T9[20] = 31, //.config_T9[21] = 3, .config_T9[22] = 15, .config_T9[23] = 13, .config_T9[24] = 25, .config_T9[25] = 23, .config_T9[26] = 208, .config_T9[27] = 63, .config_T9[28] = 15, .config_T9[29] = 90, .config_T9[30] = 15, .config_T9[31] = 5, .config_T15[0] = 0, .config_T15[1] = 0, .config_T15[2] = 0, .config_T15[3] = 0, .config_T15[4] = 0, .config_T15[5] = 0, .config_T15[6] = 0, .config_T15[7] = 0, .config_T15[8] = 0, .config_T18[0] = 0, .config_T18[1] = 0, .config_T19[0] = 0, .config_T19[1] = 0, .config_T19[2] = 0, .config_T19[3] = 0, .config_T19[4] = 0, .config_T19[5] = 0, .config_T19[6] = 0, .config_T19[7] = 0, .config_T19[8] = 0, .config_T19[9] = 0, .config_T19[10] = 0, .config_T19[11] = 0, .config_T20[0] = 25, .config_T20[1] = 1, .config_T20[2] = 1, .config_T20[3] = 1, .config_T20[4] = 1, .config_T20[5] = 0, .config_T20[6] = 0, .config_T20[7] = 0, .config_T20[8] = 0, .config_T20[9] = 0, .config_T20[10] = 0, .config_T20[11] = 0, .config_T22[0] = 0x0d, .config_T22[1] = 0, .config_T22[2] = 0, .config_T22[3] = 0x19, .config_T22[4] = 0x0, .config_T22[5] = 0xE7, .config_T22[6] = 0xFF, .config_T22[7] = 8, .config_T22[8] = 25, .config_T22[9] = 0, .config_T22[10] = 1, .config_T22[11] = 0, .config_T22[12] = 17, .config_T22[13] = 31, .config_T22[14] = 57, .config_T22[15] = 65, .config_T22[16] = 8, .config_T23[0] = 0, .config_T23[1] = 0, .config_T23[2] = 0, .config_T23[3] = 0, .config_T23[4] = 0, .config_T23[5] = 0, .config_T23[6] = 0, .config_T23[7] = 0, .config_T23[8] = 0, .config_T23[9] = 0, .config_T23[10] = 0, .config_T23[11] = 0, .config_T23[12] = 0, .config_T24[0] = 0, .config_T24[1] = 0, .config_T24[2] = 0, .config_T24[3] = 0, .config_T24[4] = 0, .config_T24[5] = 0, .config_T24[6] = 0, .config_T24[7] = 0, .config_T24[8] = 0, .config_T24[9] = 0, .config_T24[10] = 0, .config_T24[11] = 0, .config_T24[12] = 0, .config_T24[13] = 0, .config_T24[14] = 0, .config_T24[15] = 0, .config_T24[16] = 0, .config_T24[17] = 0, .config_T24[18] = 0, .config_T25[0] = 0, .config_T25[1] = 0, .config_T25[2] = 0, .config_T25[3] = 0, .config_T25[4] = 0, .config_T25[5] = 0, .config_T25[5] = 0, .config_T25[6] = 0, .config_T25[7] = 0, .config_T25[8] = 0, .config_T25[9] = 0, .config_T27[0] = 0, .config_T27[1] = 1, .config_T27[2] = 0, .config_T27[3] = 0, .config_T27[4] = 0, .config_T27[5] = 0, .config_T27[6] = 0, .config_T28[0] = 0, .config_T28[1] = 0, .config_T28[2] = 2, .config_T28[3] = 16, .config_T28[4] = 16, .config_T28[5] = 0, .object_crc[0] = 70, .object_crc[1] = 0, .object_crc[2] = 10, /*.cable_config[0] = config_T9[7], .cable_config[1] = config_T22[8], .cable_config[2] = config_T28[3], .cable_config[3] = config_T28[4],*/ .cable_config[0] = 10, .cable_config[1] = 32, .cable_config[2] = 32, .cable_config[3] = 117, .GCAF_level[0] = 4, .GCAF_level[1] = 16, .GCAF_level[2] = 0, .GCAF_level[3] = 0, .filter_level[0] = 100, .filter_level[1] = 100, .filter_level[2] = 100, .filter_level[3] = 100, .display_width = 1024, /* display width in pixel */ .display_height = 1024, /* display height in pixel */ #else To give us the P763V touchscreen option we also need to shove something in Kbuild in the same directory. Above config TOUCHSCREEN_CYTTSP_I2C insert: config TOUCHSCREEN_MXT224_P736V bool "P736V Touchscreen" depends on TOUCHSCREEN_MXT224 default n help Say Y here if you have a P736V / Orange San Francisco II. Now I think I'm going to sit in a darkened room and re-evaluate my life choices. :P Is it not possible to just replace the affected files from the San Fran kernel to the Vivacity Kernel? Link to comment Share on other sites More sharing options...
Guest Fuzzra Posted February 11, 2012 Report Share Posted February 11, 2012 (edited) I suppose you could graunch it in somehow, but I don't really see the point. You only need that config if you're building from source for a SFII to do silly things like overclock. Since I have the SFII and wanted to play with the kernel from TomGiordanos repository, getting a touchscreen which wouldn't make me want to smoke crack seemed like the place to start. I should add that it seems to break wifi for some mysterious reason. Nothing's ever easy. :/ *Edit* Don't worry too much about the wifi. I'd absent mindedly done something silly with my .config Edited February 11, 2012 by Fuzzra Link to comment Share on other sites More sharing options...
Guest MCZQ Posted February 13, 2012 Report Share Posted February 13, 2012 Great work on getting that sorted! Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 14, 2012 Report Share Posted February 14, 2012 "Silly things like overclock" is what I think a lot of people want :) Although I'm sure I read somewhere that the CPU in the Blade2 is just an overclocked version of the one from the original Blade? Link to comment Share on other sites More sharing options...
Guest Russ_uk Posted February 14, 2012 Report Share Posted February 14, 2012 (edited) Although I'm sure I read somewhere that the CPU in the Blade2 is just an overclocked version of the one from the original Blade? Think you could be right... Blade: Qualcomm MSM7227 600 MHz (Released 2009) Blade 2: Qualcomm MSM7227T 800 MHz (The 'T' stands for Turbo) (Released 2010) The rest of the specs are absolutely identical: Embedded 320MHz DSP (GSM, GPRS/EGPRS Multislot Class 12, EDGE, UMTS Release 6, 7.2 Mbps HSDPA, HSUPA 5.76 Mbps, MBMS baseband), 400MHz modem processor, Adreno 200, OpenGL ES 2.0, OpenGL ES 1.1, OpenVG 1.1, EGL 1.3, Direct3D Mobile, SVGT 1.2, DirectDraw. Edited February 14, 2012 by Russ_uk Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 15, 2012 Report Share Posted February 15, 2012 (edited) If you've been dying to play with an overclockable kernel for the SFII and don't mind losing the front camera, here you go.<br style=color: rgb(75, 75, 75); font-family: Verdana, Tahoma, Arial, 'Trebuchet MS', sans-serif, Georgia, Courier, 'Times New Roman', serif; font-size: 13px; line-height: 19px; background-color: rgb(249, 250, 251); ">Obviously I take no responsibility if it causes nether hells to open in your kitchen or gives your aunt shingles. How do we install this, Clockwork or using the update device? Or is it supposed to be inserted into a rom replacing the resident boot.img? Also, as discussed above the CPU on the crescent seems to be an already overclocked version of the original Blade CPU, so has anyone who has overclocked the Vivacity had problems? EDIT: Never mind, I got it flashed using the nandroid backup/advanced restore under clockwork recovery. Had to mess with the md5 file though to get it to allow me to restore just the boot.img. I can now overclock to 920MHz, I've set it to ondemand though of course and I've still got SetCPU set to underclock to minimum values when the screen is off, gives me mega battery life. For anyone else wanting to try, I used this md5 checker to get the md5 value of the replacement boot.img (you have to, of course, rename the file you download to boot.img and replace the one in the backup folder) then I just edited the md5 file in the backup folder (using notepad++) and replaced the value for boot.img. Clockwork recovery then let me use the advanced restore to just restore that boot.img (since the md5 value was now correct, it passed the check) and then I restarted SetCPU now reports my max speed at 1.3GHz...I'm not going up that far though of course, don't want to change my phone into a firecracker The keyboard seems to work fine too, thanks Fuzzra Edited February 15, 2012 by PsYcHoKiLLa Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 15, 2012 Report Share Posted February 15, 2012 (edited) UPDATE: Had to go back to the stock kernel, my phone's battery went flat overnight from a full charge, even though I had SetCPU set to underclock down to minimum when the screen is off. Edited February 15, 2012 by PsYcHoKiLLa Link to comment Share on other sites More sharing options...
Guest Fuzzra Posted February 15, 2012 Report Share Posted February 15, 2012 That's odd. I've had no problems with battery life myself, but I've left the governor as SmartassV2 as set as default when I built the kernel. Possibly an app hanging around and demanding lots of processor time during the night? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now