Related
Hiya everyone,
I've ported Dumfuq's overclocking patches from 2.6.29 to 2.6.32.21! This applies to those of us using the stock HTC OTA and allows the use of programs like SetCPU. This kernel was built from the source code from http://developer.htc.com and the kernel config is an identical copy of the one included in the latest Froyo OTA (my leak).
My current method of providing this is as an update.zip... just put this on your SDcard, boot into Clockwork, and flash it. If it kills your kittens, do not blame me.
Also, reminder: flashing this zip alone is not enough to overclock your device. Afterward, use a program (from the Market) such as SetCPU to overclock your device.
Download: http://www.multiupload.com/2XEWYRL62U
Change Log:
- Revision 2
Fix Wifi issues (as well as any other kernel module loading issues).
Add support for CPUfreq governers 'interactive' and 'smartass'.
Change the default governer from 'ondemand' to 'interactive' - this dramatically improves redraw performance and other user-interface responsiveness.
To change to the Smartass governer use something like SetCPU.
Include the MSM KGSL TLB performance tweak changes that are present in CM's kernel repository. You may or may not notice any video performance improvement, but it provides a possibility of improvement.
Fixed the kernel version string to properly read '2.6.32.21' not '2.6.32.17' - the first version wasn't .17, it was .21.
Please remember to disable the HTC Perflock in SetCPU by pressing the Menu key (while in SetCPU) and selecting 'Perflock Disabler'.
Happy? Donate.
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
What is the max frequency of this kernel? And does it include smartass governer?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
agentg1001 said:
What is the max frequency of this kernel? And does it include smartass governer?
Click to expand...
Click to collapse
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
nbetcher said:
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
Click to expand...
Click to collapse
I have made the changes, however I decided to NOT disable HTC Perflock through the kernel config, so please make sure to disable it (via SetCPU) first before trying to overclock or change your governer. New version uploaded, see OP.
Could you also include some higher frequencies? (Preferibly up to 960)? That would be great because my phone is stable up to 921. Also compcache enabled (like drowning child's kernel) would be awesome.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I'm not sure why but my slide didn't like this kernel
http://pastebin.com/hVgG467j
Thank the devs for nandroid!
My slide not working with this kernel too (
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly. Besides, according to that logcat your problems aren't related to the kernel... Android is unable to mount any of the MTD partitions (/system, /cache, /data, etc).
Please let me know more about what you're running.
Also, I'll be working on making a separate version of this that has OC enabled up to 960MHz, but 960MHz is very dangerous... 800MHz+ is even asking for trouble despite our processor's normal clockrate being 800MHz (T-Mobile downclocked it to 600MHz out-of-the-box).
I'll look into Compcache as well.
im IN.
good job, will try after work. gj
how long does it take to boot the first time?
been stuck at the white MT3GS boot screen for a few minutes now.
running CM7 RC4
EDIT: oops, did not know this is only for the leaked froyo update
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Sefy said:
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Click to expand...
Click to collapse
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
pettigrew95 said:
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
Click to expand...
Click to collapse
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Sefy said:
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Click to expand...
Click to collapse
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
nbetcher said:
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
Click to expand...
Click to collapse
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Sefy said:
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Click to expand...
Click to collapse
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
EDIT: in hind-sight this all seems to not really answer your question and only further supports the need for a better answer to you, but hopefully you'll find some clarity.
nbetcher said:
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
Click to expand...
Click to collapse
Everyday you learn something new! thanks for being the teacher!
nbetcher said:
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly.
Click to expand...
Click to collapse
Well now I feel a bit sheepish, I guess that's what I get for not reading closely enough, I'm running CM7 RC4, sorry about that.
Does anyone happen to have a copy of this kernel laying around somewhere? Megaupload is long gone unfortunately
I'm presently working on the answers to another question I asked recently regarding cifs. I got some great technical advice but it seems that I must do some work with the kernel in my vegan ginger tab to understand all the info I received. I was sent a link to Pershoot's kernel page http://droidbasement.com/db-blog/ and I went there but I do not understand what I am seeing. I see that there is a numbering system 2.6.32.39 and I can guess that UV means undervolted and that OC means overclocked. The rest ??? Which one works with gingerbread ??? Also, reading the posts in the kernel page on XDA, there seems to be a lot of experimentation going on with voltages and governors, etc to try and squeeze the max out of the g-tab. That's great but I'm not ready to play in that league yet. I want a basic, stable kernel that I can learn to load modules with. I don't want to be worrying about adjusting other things at the moment. How, can I determine which is the correct kernel for my vegan ginger? Actually the one that came with the ROM is working fine (2.6.32.36) but I need to have the zip file to look at the information inside to understand the answers to my original questions about loading cifs module. Any kernel wizards out there that can give me some basics on the labeling system?
My guess would be the one with....(Gingerbread)........after it....
Its not that hard to read.......
ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
roguey said:
My guess would be the one with....(Gingerbread)........after it....
Its not that hard to read.......
ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
Click to expand...
Click to collapse
Of course its not that hard to read if you know what you are reading!
"ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
cm_2632.39 - kernel version (derived from cyanogen mod I presume)
gb - yup gingerbread
oc - overclocked - probably
uv - undervolted - another good guess
xtra - well he explains what is in that
vfp - no clue
fp - also no clue
043011 - yeah the date !!!
now there is all this reference to replacing the boot loader - which, based upon all the furor about the last viewsonic release might be a problem - or not. Do I need a new bootloader or is this just standard with kernels. I've flashed a few and never seen that before - but I was using clemsyn's. Will it mess up my clockworkmod?
Then it also looks like I have to install an app to manage the overclocking. Do I want to overclock? Should I overclock? Hmmm not working on that issue at the moment so I don't want to start a recursive thread in my mind investigating overclocking. Perhaps I shouldn't be using pershoot kernels at all if I want something less experimental. All I wanted really was to have cifs work. Clemsyn? Well cifs is built in but it didn't seem to work well with gingerbread rom. How to tell what works with what rom? Trying not to make a brick here. Anyway - I'm rambling but hopefully someone see the point. How do you find the information you need to make a decision? So far the only way I can see is to post questions like this, receive snarky answers and an occasional helping hand. Well if that's what it takes - bring it on because sooner or later I'm going to find out what I need to know to keep pushing forward with my g-tab.
There is a learning curve to anything, and Linux kernels are no different. First, don't over think it! It is sufficient to get the right kernel for whatever you are running. For us gtab folks that would be gtab, then either froyo or gingerbread as the major version, then either the original 1.1 or the new 1.2 bootloader. Combine all that and you will know which pershoot ron will work for you.
As to the overclocking, by default if you do nothing, the pershoot kernel will slightly underclock, so it will always work on any hardware. You can follow the directions to start pushing the overclock speed and see hot it works for you. Try 1200 for a few days, and if all goes well push it up to 1400
Ha-ha-ha Sorry I'm an INTJ - I ALWAYS overthink. Learning curves are my curse! That said - identifying the kernel makes more sense. I'm not sure I know how to determine what bootloader it is for - I prefer to stick with the old one for now. Is it something obvious that I just haven't seen? For example:
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip which bootloader???
Then there is the question of "In order for UMS (USB mount) to work on Gingerbread, this must be reverted:
https://github.com/CyanogenMod/android_device_harmony/commit/f51f9e2a1037b4e3fb1a" What does REVERTED mean?
Good news on the overclocking - I can just leave it alone and it will work and then when I'm ready I can try the overclocking. Is this usually true with kernels that have been undevolted or overclocked that the default settings are more or less normal and you have to actually tweak them to use the OC or UV? I know nothing is carved in stone but would that be "the norm" for most developers?
enigma0456 said:
Ha-ha-ha Sorry I'm an INTJ - I ALWAYS overthink. Learning curves are my curse! That said - identifying the kernel makes more sense. I'm not sure I know how to determine what bootloader it is for - I prefer to stick with the old one for now. Is it something obvious that I just haven't seen? For example:
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip which bootloader???
Then there is the question of "In order for UMS (USB mount) to work on Gingerbread, this must be reverted:
https://github.com/CyanogenMod/android_device_harmony/commit/f51f9e2a1037b4e3fb1a" What does REVERTED mean?
Good news on the overclocking - I can just leave it alone and it will work and then when I'm ready I can try the overclocking. Is this usually true with kernels that have been undevolted or overclocked that the default settings are more or less normal and you have to actually tweak them to use the OC or UV? I know nothing is carved in stone but would that be "the norm" for most developers?
Click to expand...
Click to collapse
You have to check out his blog page - it should clearly identify if a kernel is for the old or new boot loader. The vast majority are for the old boot loader, so if it's not mentioned at all, it's for the old one.
You can ignore the USB revert thing - that's not an instruction for you, it's what he did for gingerbread.
The way overclocking is implemented (at least in pershoot's case), you need to change something on your gtab to set the min/max clock. By default, on pershoot's kernel, the max will be just under 1Ghz, so doing nothing you get that. The undervolting is fixed in the kernel, you can't change it. Likewise the "steps" the cpu clock can take from min to max is fixed in the kernel and isn't changeable.
The other kernel (1.5ghz OC) I know nothing about, since I've never used it nor looked into it.
It's even easier than you are still trying to make it
There is only one bootloader for the Gtablet that supports "other" kernels and that is the one that is currently shipping and currently "officially the latest". There is a "newer" bootloader for the 1.2 system based stuff (3991 and above stock images...which were up for a day and then pulled for unknown reason) and there are zero replacement kernels for that bootloader.
If you read it says..
"Malata Zpad [New Bootloader] "
Click to expand...
Click to collapse
and no where does it mention new or old bootloader and Gtablet together.
So for Gingerbread based Viewsonic Gtablets you would want this one.
ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
Download: boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
Click to expand...
Click to collapse
If you need extra filesystem or other support (CIFS, NTFS, etc..) you need the proper module from the lib file..
lib-2632.39_gb.tar.gz (kernel modules)
Download: lib-2632.39_gb.tar.gz
Click to expand...
Click to collapse
which you would open and extract the module you need and push it to your device however you want....ADB or Root Explorer, etc...
Pull the one you want from lib-2632.39.tar.gz (winrar can open this),
adb remount
adb push MODULE.ko /system/lib/modules/2.6.32.39-cyanogenmod/
adb shell chmod 644 /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
adb shell insmod /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
Note:
You can download gscript lite from the Market, and put the insmod line in there, and tap when you want to insert it and use its functionality.
Click to expand...
Click to collapse
if you want to use overclocking, download SetCPU or use the CPU settings in VEGAN-Ginger.
Overclocking-
How-To:
-Install the latest SetCPU (2.11a is current) from the market and/or XDA (http://forum.xda-developers.com/showthread.php?t=505419)
-Select auto
-If using CM7, then you can use the included CPU Settings within CyanogenMod Settings.
Note:
If you were using SetCPU prior, with ‘custom’ and this kernel set, please go to device selection and select auto. Please delete the custom setcpu file on your filesystem:
adb shell rm /data/local/setcpu
Note2:
Be aware, that if you leave it pinned to max, hammering it, it will get warm/warmer then your used to at 1GHZ, pinned.
It is advised not to select any of the 2 governor’s listed (but, at the very least, not performance).
It is advised to keep your min value at 216.
Click to expand...
Click to collapse
You don't need to worry about this statement
In order for UMS (USB mount) to work on Gingerbread, this must be reverted:
https://github.com/CyanogenMod/android_device_harmony/commit/f51f9e2a1037b4e3fb1a
Click to expand...
Click to collapse
If you are on a ROM based off the CyanogenMod source tree which VEGAn-Ginger is.
enigma0456 said:
vfp - no clue
fp - also no clue
Click to expand...
Click to collapse
FYI, vfp_fp = Vector Floating Point
Many Thanks
OK - all these postings have given me answers and ideas and things to try - now I'll go back into my cave for awhile, try them and digest the results. Thank you all for being so supportive - I really appreciate the time you have spent detailing your answers. I'm sure that others that find these posts will as well.
Hey guys just a quick question, i recently flashed the LOL rom with an updated kernel that has the smartass governor, what file / line do i change so that this is the default governor without the use of any app like setCPU?
note. that in the system_available_governors file smartass is listed, and thus can be set by setCPU without problems.... what im trying to do is avoid to have to run setCPU in the background to set smartass on bootup (default is interactive)
i have tried setting the system_governor to smart ass and setting it to read only but it ends up getting changed back to interactive somehow.
i have tried setting in the 05cpuclock file smartass instead of interactive to no avail... so it seems as if during the bootup process something after those scripts are referenced / executed another one is setting the cpu governor... question is where?!??!
Ginger LOL has script for overclocking so don't have to use any apk for overclocking... go to terminal and type su cpuclock and follow instructions on sceen
nd4spdbh said:
Hey guys just a quick question, i recently flashed the LOL rom with an updated kernel that has the smartass governor, what file / line do i change so that this is the default governor without the use of any app like setCPU?
Click to expand...
Click to collapse
By recompiling the kernel with CONFIG_CPU_FREQ_DEFAULT_GOV_SMARTASS=y
kubas87 said:
Ginger LOL has script for overclocking so don't have to use any apk for overclocking... go to terminal and type su cpuclock and follow instructions on sceen
Click to expand...
Click to collapse
LOL != GingerLOL
dr.notor said:
By recompiling the kernel with CONFIG_CPU_FREQ_GOV_SMARTASS=y
LOL != GingerLOL
Click to expand...
Click to collapse
ya... not using any of the GB roms... they all seem to have their problems... on the 2.2.2 froyo LOL rom.
i actually figured it out. the text editor i was using on my comp was messing with the file encoding so when i did edit the 05cpuclock init.d script it was never able to execute.... so editing the original script in eclipse proved to solved the problem.
Hi everybody,
I installed a cool ROM on my phone but one if its features included dimming the haptic buttons on my phones. I liked them bright before when I had stock. Is there any mod I could flash to help fix the dim haptic buttons. They're a little too dim for me but the Rom is way better than stock.
Thanks
Sent from my PG86100 using XDA App
Hiya Buddy said:
Hi everybody,
I installed a cool ROM on my phone but one if its features included dimming the haptic buttons on my phones. I liked them bright before when I had stock. Is there any mod I could flash to help fix the dim haptic buttons. They're a little too dim for me but the Rom is way better than stock.
Thanks
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
It depends on whether the dim setting was done in the kernel itself or not. Go check this:
/sytem/etc/init.d/ <- open the various scripts in there and look for a reference to this:
/sys/devices/platform/leds-pm8058/leds/button-backlight/currents
if there IS a script in there, it *might* have the currents set to 2 or 5 or something. The stock brightness is 20, so you could either change the value you find in the script to 20, or whatever you like, OR delete the script altogether.
if there is NOT a script in there, the setting is probably built into the kernel, so the only way around it would be to ask the ROM or kernel dev to remove it or allow an option to change it. You could also flash a different kernel that does NOT have the setting built in.
Thanks I can find the init.d folder and its contents but I don't think that script you mentioned is there. I'll post a screenshot of the init.d folder. If you're right about it being built in to the kernel would you know what kernel I would need to flash in order to do this???
P.S. Not sure if I should PM the dev who created the ROM or try to post in the rom's forum. Unfortunately, I need to get my post count up to post in that forum seeing as I'm still considered a noob.
P.S.S. I forgot to mention the rom's name. Its called Olympus Trinity XE Prime and its by theAndroidOsX (something along the lines of that...forgot how to spell it...)
Thanks again for your help!
Hiya Buddy said:
Thanks I can find the init.d folder and its contents but I don't think that script you mentioned is there. I'll post a screenshot of the init.d folder. If you're right about it being built in to the kernel would you know what kernel I would need to flash in order to do this???
P.S. Not sure if I should PM the dev who created the ROM or try to post in the rom's forum. Unfortunately, I need to get my post count up to post in that forum seeing as I'm still considered a noob.
P.S.S. I forgot to mention the rom's name. Its called Olympus Trinity XE Prime and its by theAndroidOsX (something along the lines of that...forgot how to spell it...)
Thanks again for your help!
Click to expand...
Click to collapse
Hey bro, try flashing this, and see if it works. It will add a script to your init.d folder (50NormalLed) that *should* set your LEDs to full power whenever you reboot your phone.
Let me know if it works
If you have root explorer you can also just go to sys/devices/platform/leds-pm8058/leds/button-backlight/ long press 'currents,' select 'Open in text editor,' and change the variable to 20. Hit menu and select: 'save changes.' Only thing is that every time you reboot your phone you have to redo this process
@Bamba1260 tried flashing the zip. Its in the init.d folder but the haptic keys still have the same low brightness. Any other suggestions???
Hiya Buddy said:
@Bamba1260 tried flashing the zip. Its in the init.d folder but the haptic keys still have the same low brightness. Any other suggestions???
Click to expand...
Click to collapse
ask the ROM dev if he built the dim leds INTO the kernel, if so, ask him to make you a zip that disallows this, so you can set your own brightness. Or try a kernel without the lights hacked, if there are any.
Thanks, looks like I have to PM the dev of the ROM. I figured I wasn't flashing right since I have H.BOOT 1.5 and S-ON so I tried it through fastboot. That didn't work either, thanks for trying to help me though.
Hiya Buddy said:
Thanks, looks like I have to PM the dev of the ROM. I figured I wasn't flashing right since I have H.BOOT 1.5 and S-ON so I tried it through fastboot. That didn't work either, thanks for trying to help me though.
Click to expand...
Click to collapse
Hmm... il Duce is probably on to something with it being in the kernel then lol. I thought a script would override that, but apparently not.
Good luck with the dev, I hope you figure something out
Woah a long time lol
The ROM was olympus trinity/titan. I loved that rom, but the only issue I had were the dim haptic keys. I think they were built into chad's kernels, so not sure of how to fix that other than flashing a diff kernel that doesnt dim the haptic keys.
I just got this new galaxy tab and it's really cool, but it's very laggy and I ready have a custom rom on it I'm not sure which one it is tho...
can somebody tell me how I can speed it up
flash galaxytask 14 and use an alternative launcher if you want.
carinlynchin said:
I just got this new galaxy tab and it's really cool, but it's very laggy and I ready have a custom rom on it I'm not sure which one it is tho...
can somebody tell me how I can speed it up
Click to expand...
Click to collapse
The best way for anyone to help you get to where you want to be is for us to know for sure where exactly you are
I agree your best bet is to switch to Task 14 and if that happens to be your custom ROM already there are more steps to help you get rid of the lag than just the ROM.
If you can't figure which custom ROM you're on, it would be best, IMHO, to start by going to the development section and Task 14 thread.
Hope this helps.
Sent from my GT-P7510 using XDA Premium HD app
i just realized i have galaxy task, but not sure of the version....how can i check?
also, what else could i do to get rid of the lag?
settings, about
flash pershoot's kernel if you dont already have it and overclock to 1.2 or 1.4 Ghz
install another launcher
It says
galaxy task 14 slim
And kernel says 2.6.36.3 [email protected] #1
So how do I do all that stuff...can someone give me a quick step by step?
I just downloaded CPU master and set it to on demand but the maximum it goes is 1000.....and so far I haven't noticed Any speed improvements
You need pershoot's kernel in the dev section.
carinlynchin said:
I just downloaded CPU master and set it to on demand but the maximum it goes is 1000.....and so far I haven't noticed Any speed improvements
Click to expand...
Click to collapse
Get yourself ADW launcher
Sent from my GT-P7510 using Tapatalk
ADW Launcher helped with laggy tab for me in the beginning
you should give it a try and once you are familair with your tab and rom then use tasks rom and other kernel
I'd there a free way to get the launcher ?
GO Launcher
That's awesome....but I still haven't noticed much of a speedup...I thought I already had Pershore kernel since I have the numbers of my kernel as 2.6.36.3....but I'll look in Dev part
carinlynchin said:
That's awesome....but I still haven't noticed much of a speedup...I thought I already had Pershore kernel since I have the numbers of my kernel as 2.6.36.3....but I'll look in Dev part
Click to expand...
Click to collapse
Use kang ics rom. Task is the fastest honey comb rom, if that's slow to you, ics is the only solution
Check whether urs is wifi or 3g model. Don't flash the wrong one.
Ray1 said:
Use kang ics rom. Task is the fastest honey comb rom, if that's slow to you, ics is the only solution
Check whether urs is wifi or 3g model. Don't flash the wrong one.
Click to expand...
Click to collapse
but I thought ICS made the camera not work...did they fix those bugs??
Nope but it isn't laggy.
lol...ok.... how about just doing the kernel then...i have downloaded it but don't understand pershoot's lingo....
"To install kernel modules:
Use Winrar (windows) or tar with the z option and unpack lib-2636.4.tar.gz
Push any module you desire to /data/local/modules (this is created by the update.zip)
Then, insmod it (you can do this via adb, in a gscript, or on the device in terminal."
I have unzipped it and have the lib folder and more stuff inside...how where do I put it? I can't find the data/local/modules...only data folder and then only .com stuff is in there
I tried running update.zip...from recovery mode but installation was aborted because it coudln't find the file or directory....where can I get it? looks like this update.zip is supposed to create the needed folders
ok...now i have just created those folders and added themodules but I can't insmod them through the adb shell..I can't even see them in the folder I put them in...only the 2.6.36.4-cyanogenmod+ but that wont "insmod"
carinlynchin said:
ok...now i have just created those folders and added themodules but I can't insmod them through the adb shell..I can't even see them in the folder I put them in...only the 2.6.36.4-cyanogenmod+ but that wont "insmod"
Click to expand...
Click to collapse
Flash the kernel using cwm.
Sent from my GT-P7510 using XDA Premium HD app