Guest PsYcHoKiLLa Posted February 15, 2012 Report Share Posted February 15, 2012 What is this Smartass you speak of and where might one get it? Link to comment Share on other sites More sharing options...
Guest Fuzzra Posted February 15, 2012 Report Share Posted February 15, 2012 It's one of the CPU governors built in to the kernel. Just like ondemand. It should be right at the top of the governor list in SetCPU. Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 15, 2012 Report Share Posted February 15, 2012 (edited) Ah right, just reinstalled the boot and chosen SmartAss, I'll see how it gets on, thanks. Edited February 16, 2012 by PsYcHoKiLLa Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 16, 2012 Report Share Posted February 16, 2012 UPDATE : Seems fine now, I think I sorted out what was killing the battery, I installed ftpdroid, great program for transferring files to your phone, try it if you haven't already. I had it set up to run as a service in the background though, I've changed it to run only when I choose to run it. So, I now have the O/C kernel and also the Signal Boost app which Fuzzra solved (Great work fella!) and the battery seems to be working OK and discharging slowly, I'm using the SmartAssV2 governor and also using SetCPU to ramp down the phone to it's lowest speed (122MHz to 245MHz) when the screen is off. Thanks again Fuzzra for both these massive improvements to our phones!! :) Link to comment Share on other sites More sharing options...
Guest Russ_uk Posted February 17, 2012 Report Share Posted February 17, 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. Can you (or anyone) post a link to the over clocked kernel for the TMV (with wifi working - not bothered about the front camera not working) Thanks in advance if anyone can help. Link to comment Share on other sites More sharing options...
Guest MCZQ Posted February 17, 2012 Report Share Posted February 17, 2012 (edited) Can you (or anyone) post a link to the over clocked kernel for the TMV (with wifi working - not bothered about the front camera not working) Thanks in advance if anyone can help. Hi Russ. Later today I will be posting a ported Skate ROM (ICE ARMOR II) based on CM7 which wifi and OC for our Tmobile Vivacitys, if your willing to test thatd be great :) Edited February 17, 2012 by MCZQ Link to comment Share on other sites More sharing options...
Guest Russ_uk Posted February 18, 2012 Report Share Posted February 18, 2012 (edited) Thanks for the reply MCZQ.. Not a problem, I'd be happy to do some testing. I'd would also be appreciated if you could post the O/C kernel independently. Thanks Edited February 18, 2012 by Russ_uk Link to comment Share on other sites More sharing options...
Guest MCZQ Posted February 18, 2012 Report Share Posted February 18, 2012 Thanks for the reply MCZQ.. Not a problem, I'd be happy to do some testing. I'd would also be appreciated if you could post the O/C kernel independently. Thanks Slight (Major!) delay in me posting the CM7 ROM in the meantime heres the OC kernel just flash from recovery http://www.mediafire.com/?7crbxa3cbs2am1y (Just for T-Mobile vivacity) Link to comment Share on other sites More sharing options...
Guest Russ_uk Posted February 19, 2012 Report Share Posted February 19, 2012 Slight (Major!) delay in me posting the CM7 ROM in the meantime heres the OC kernel just flash from recovery http://www.mediafire...7crbxa3cbs2am1y (Just for T-Mobile vivacity) Many thanks MCQZ :) Link to comment Share on other sites More sharing options...
Guest Titas Posted February 20, 2012 Report Share Posted February 20, 2012 Slight (Major!) delay in me posting the CM7 ROM in the meantime heres the OC kernel just flash from recovery http://www.mediafire...7crbxa3cbs2am1y (Just for T-Mobile vivacity) Great to see you're working on this - I'm just itching to get CM on my Crescent/TMV (loved it on my Blade). Trying to be patient but I spend half my time checking this site for news lol. N'way, really appreciate your work - I hope the "major" delay is not too serious!! Link to comment Share on other sites More sharing options...
Guest Titas Posted February 21, 2012 Report Share Posted February 21, 2012 Slight (Major!) delay in me posting the CM7 ROM in the meantime heres the OC kernel just flash from recovery http://www.mediafire...7crbxa3cbs2am1y (Just for T-Mobile vivacity) ICE ARMOR III.update: Tue, Feb 21, 2012 This is a freshly compiled CM7 ROM for the ZTE Skate / OMC. It is built from the latest CM repo sync and has all the latest features. Link to comment Share on other sites More sharing options...
Guest Russ_uk Posted February 24, 2012 Report Share Posted February 24, 2012 ICE ARMOR III.update: Tue, Feb 21, 2012 This is a freshly compiled CM7 ROM for the ZTE Skate / OMC. It is built from the latest CM repo sync and has all the latest features. Where ? Am I Missing something? Link to comment Share on other sites More sharing options...
Guest Titas Posted February 24, 2012 Report Share Posted February 24, 2012 Where ? Am I Missing something? This is a CM7 ROM for Skate - the post is quoted from that forum. It's relevance here was that MCZQ had requested the source code so that it could be ported to the Crescent. He has said he has hit a major problem with that & recently the developer has posted "ZTE Crescent I do not think." so I'm not too optimistic about it now. Shame really as it seems to be a very fast, stable with innovative features. Link to comment Share on other sites More sharing options...
Guest PsYcHoKiLLa Posted February 24, 2012 Report Share Posted February 24, 2012 This is a CM7 ROM for Skate - the post is quoted from that forum. It's relevance here was that MCZQ had requested the source code so that it could be ported to the Crescent. He has said he has hit a major problem with that & recently the developer has posted "ZTE Crescent I do not think." so I'm not too optimistic about it now. Shame really as it seems to be a very fast, stable with innovative features. Not a very open source attitude to be honest. Link to comment Share on other sites More sharing options...
Guest Cuvillier Posted April 5, 2014 Report Share Posted April 5, 2014 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. *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. can you upload the file to another host please as the link does not work thank you to the link as soon as possible 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