I have been a fan of DJ Steve's ROMs and his dev skills. But right now I am running a deodexed 351 that is otherwise stock, in portrait mode. haha
I love his ability to compile ROMs and Kernels and such, but I really want just the kernel that supports overclocking.
I can get any of the kernels to work from 1.91
no vol, no ppt
no vol, ppt
vol and ppt
vol and no ppt
I even add the proper dhd.ko file for the modules folder and correct the permissions and even the reset.ko file too.
But no matter what I do, I can't get the kernel to work AND wifi to work. It seems like either or for a stock rom. Either you have a plain kernel with no overclocking, or you can use the kernel with no wifi working.
Does anyone know of:
1: If there are other files I should be bringing over from the rom to make the kernel and wifi work together
or
2: What specifically I can edit to allow the stock kernel to allow overclocking?
Sorry for the long post.
Thanks for the help in advance.
OK. I guess no one out there knows either.
What I have been doing so far to achieve overclocking is create a .txt file (according to the instructions on setcpu.com) and put that at the root of my sdcard and have setcpu do the rest.
I would prefer to use the kernel method so I can add the volboost and/or ppt tweaks in 1.91.
I will wait patiently for your guidence.
Maybe try this
http://forum.xda-developers.com/showpost.php?p=14679059&postcount=135
Ok I figured out which one will work.
http://forum.xda-developers.com/showthread.php?t=1113256
Ok go to Simple Streak's thread.
1. Download the .zip for version 1.2
2. copy the files in /system/lib/modules to your /system/lib/modules
3. fix permissions, they should be 644, which are rw-r--r--
4. boot into fastboot, and flash his boot.img
Thank you Spidla for a kernel I can use that supports overclocking, that I dont have to use the entire ROM and most importantly, my wifi works.
rsalib said:
Ok I figured out which one will work.
http://forum.xda-developers.com/showthread.php?t=1113256
Ok go to Simple Streak's thread.
1. Download the .zip for version 1.2
2. copy the files in /system/lib/modules to your /system/lib/modules
3. fix permissions, they should be 644, which are rw-r--r--
4. boot into fastboot, and flash his boot.img
Thank you Spidla for a kernel I can use that supports overclocking, that I dont have to use the entire ROM and most importantly, my wifi works.
Click to expand...
Click to collapse
I am interested in this, can you explan the procedure in more detail, copy files from what rom to what rom and how to fix permissions?
thanks
Related
Found this thread on the HTC Hero section for it's open GL will this work for our wildfire?
http://forum.xda-developers.com/showthread.php?t=899801
Yea I flashed it, noticed an improvement in playing angry birds...i think.
Sent from my HTC Wildfire using XDA App
Will it work on cm7 nightlies kevin?
Sent from my HTC Wildfire using XDA App
Yeah
Sent from my HTC Wildfire using XDA App
Yes it works with just about every ROM, but, in my view, I can't see any benefit. (I dont play Angry Birds, and, the rest of the games and LWP's don't show any benefit).
How do you do this?
Just flash it like a rom?
Well, that's what I initially did. Flash the ZIP in Post #49 in that thread. But, on reading that complete thread, I guess you have to edit the build.prop file in /system (Using Root Explorer / ADB Push Pull).
However, this is where I cant get it to work. WHenever I add the 2 lines in Root Explorer and Save Changes, the phone reboots. If I use ADB, even after pushing, when I check the same file using build.prop, no changes are visible, (The opengles.version automatically reverts back to 65536 and the line which enabled hardware acceleration of the UI is gone) and, ASI only shows OpenGL 1.0 due to this
Well, I have no idea what I am doing wrong, will try it out again and see..
I'm a newb with this.
Could someone possibly make a bit more explained guide?
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Updated: (ADB Commands Copy - Pasted from another post by kevin2516. Thanks mate )
*Make sure ADB is installed on your system and it is working. There are many guides available to install ADB, so I wont be going into that.
*Start Command Prompt (cmd), Browse to your "Tools" folder into your SDK
*Use the ADB Pull Command adb pull /system/build.prop
*This will now be saved to your tools folder. Edit is using Wordpad / Notepad++ (Not Notepad) as follows:
*Locate a line which starts with dalvik. (The first one, there are 3 of them)
Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save it.
* Push it back to System using the ADB Push Command: adb push build.prop /system/build.prop
* Reboot ADB using the adb reboot command
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
bgx said:
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
Well, I took your flashable ZIP, removed the build.prop it contained, and replaced it with the build.prop of CM7 Nightly 2. Then, I tried flashing it, still no change.
Now, I have no idea whether I am 'allowed' to change flashable ZIP's like that or not, but, from what it is looking like, I am still unable to get this working on CM7NB2. I'll probably try making a flashable ZIP from scratch later as I get time.
bgx said:
I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
If it's simple enough, it would be nice if you could tell how to do a flashable zip (or yourself make a one suitable for CM6/7 ). I just want to test these libraries on CM7, any help is appreciated
Don't expect nothing special, I'm not a dev!
3xeno said:
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Then, locate a line which starts with dalvik. (The first one, there are 3 of them)
* Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save and Exit
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
Click to expand...
Click to collapse
But it's not working for CM7?
Where can i find FLashable zip? I don't understand where is post #48
Even if i find, i have read, that it's not working? Or working?
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
3xeno said:
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
Click to expand...
Click to collapse
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
vilks said:
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
Click to expand...
Click to collapse
Which is exactly what I said in the CM7 thread. No one here has till date, found verifiable gains, with using OpenGL on the Wildfire. Everyone reports the same thing, that there is no or absolutely negligible (Which I think is just a mind thing) change in gaming / intensive applications performance.
If you are looking for ROM's wit inbuilt OpenGLES Support, WildPuzzle has a flashable ZIP, and DS and DK Roms provides it inbuilt in its latest version. For the others, the manual method has to be followed.
Hello,
Can someone tell if it's wise to upgrade my Tytung R13 Kernel to R14 or Dorimanx kernel?
I like to have a better battery life.
How do I have to upgrade to a "better" Kernel without losing all my apps and settings?
Hope someone can provide me some answers.
Greetings Matthieu.
Put the Dorimax kernel zip file in the root of your SD.
switch your phone off
switch it on again holding down the power button until the menu comes up
select install zip from SD
navigate to the Dorimax zip and install that.
then reboot your phone!
(if you're using NAND Android!)
I use r14 with Tytung's Gingerbread ROM. Tried several earlier versions of Dorimax's kernel and had terrible luck with them. Lost app linkages mainly and Titanium Backup even though I was using the correct zip file created by a forum user on Tytung's thread. Going to the hidden phone menu I switched my phone to use GSM only and this reduced the battery drain from WCDMA preferred which is the default.
What ROM do you use? The original Tytung kernel thread and included file is for Tytung's ROM. For compatibility, somebody has suggested to replace the initrd.gz file with the one in your ROM before flashing.
You can try Tytung 14. It is good and stable. If you like to do some adventure and something exciting but a little dangerous, try Dorimanx. Dorimanx is a crazy developer. The speed of kernel and ROM updates is high. I will recommend to try Dorimanx kernel v3.3 and 4.1. Both of them work on my Typhoon ROM.
Hello,
Thanks for the answers. I use the NexusHD2 Gingerbread V3.2a rom with Tytungs R13 kernel.
I read something about the initrd.gz file. Do I have to do something with that file before upgrading to Tytungs R14 or is there a complete zipfile and can I install it just as mentioned in the second post without losing anything? Is the batterylife better with R14 or Dorimanx 4.1 instead of R13?
I am just a beginner and want to extend the usage of my HD2.
Thanks.
Greetings Matthieu.
Go to the kernel thread by Tytung http://forum.xda-developers.com/showthread.php?t=1258110. The kernel is just all you need.
The ROM you use is his work, too. Nothing have to be changed before flashing. Just do it. Have fun.
I am not sure if battery life if better in R14. You can try it. Flashing the kernel you will not lose anything. If you want to do some cleansing work, just wipe cache, Dalvik cache (in advanced setting), and fix permission. Do not wipe system/factory reset.
Thanks!! I hit the thanksbutton for you...
Is it also possible to just put a dorimanx 4.1 zipfile on my sd card and install it without doing extra actions (like installing extra files)? I am a noob with this so....
Greetings Matthieu.
Yes, in Dorimanx v4.1 the initrd.gz files from CM/MIUI/ICS are incl. in the kernel. While flashing you can choose your system. Though the file you are looking for, initrd.gz, is located in your ROM's .ZIP. just open it en you will find the file under /boot, extract initrd.gz en extract the Dorimanx .ZIP and place initrd.gz in the initrd-custom directrory. Last but not least you need to select all the exctracted files from the Dorimanx .zip (incl the initrd-custom folder with your custom initrd.gz) and make a new .ZIP!
Correct me if i'm wrong!? =P
can I flash Dorimanx kernal to sense roms?
Hi, I'm trying various kernels on my rom.
Therefore I'd like to backup my existing kernel.
I know TWRP can easily do this.
However for information I'd like to know manual adb method, or terminal commands.
Or is there a Zip file which I can run to automate the process
why not just keep the kernel zip file in your storage?
as a hobby, i test kernels, trinity kernel to be exact. i probably have 20-30 kernels in my storage at all times. when im want to run my favorite again, i just reflash it. i cant imagine why id want to back up a kernel.
http://forum.xda-developers.com/showthread.php?p=44680433&highlight=keyboard#post44680433
Slimbean 3.1 build is very functional for GT540 - thanks. I do not know if the Cyanogenmod 10 build is affected by the problem described in above post as well. But here is
GT540_Slimbean_Build1_kbd_fix.zip
Simply use ClockWorkMod (CWM) and install this zip AFTER Slimbean 3.1 was installed.
It will fix the "soft keyboard not showing up" problem, since the kernel is built without atcmd_virtual_kbd.
Also, CIFS and TUN are compiled into kernel (not as module, but statically linked in).
For more information see the contents of directory README/ within the zip file, which contains everything you need to reproduce what I've done.
Thanks for hitting thanks.
Cheers
cmuelle8
ps: Thanks to miroslav_mm for having been so thoughtful to include /proc/config.gz option. You'd think this is standard among open developers, but unfortunately it is not. I've seen tons of kernels without config.gz compiled in, which is a pain..
EDIT: You do NOT need to wipe cache/data to apply this, as it just exchanges boot.img, nothing else. If you lack CWM on the phone you can also extract the contained boot.img and push it with fastboot. This alternative method is documented in this forum, search for fastboot and boot.img ..
I have been playing around with kernels (for nexus 5), to add some features to the stock kernel. But I have problem with Samsung. I am trying to build a flashable custom kernel for Samsung S7 edge (G935F). .Steps I followed to create the boot.img are:
Get the stock source code (Samsung openSource)
Modify the kernel (just add/remove some TCP features)
Build the kernel (as per the kernel READ.ME, with aarch64-linux-android-4.9 toolchain)
-->created Image, with no loadable modules (*.ko)
Unpack the boot.img from the stock kernel (abootimg -x )
Create new boot.img replacing the original zImage with the custom kernel Image (abootimg --create . . . )
Make tar.md5 file of the custom boot.img for Odin3
Pushed the custom kernel using Odin3, but it fails to boot ("kernel not enforcing seadnroid"). I have tried using TWRP (install from zip), but it just does bootloop. Can anyone see what I am doing wrong? Am I missing something? I have read most of the "Build kernel from source" dev-threads but have not found a solution for this, nor am I allowed to post my questions there as I am just a junior member.
I would highly appreciate any help, as I have already invested some days with no avail
mdh-labs said:
I have been playing around with kernels (for nexus 5), to add some features to the stock kernel. But I have problem with Samsung. I am trying to build a flashable custom kernel for Samsung S7 edge (G935F). .Steps I followed to create the boot.img are:
Get the stock source code (Samsung openSource)
Modify the kernel (just add/remove some TCP features)
Build the kernel (as per the kernel READ.ME, with aarch64-linux-android-4.9 toolchain)
-->created Image, with no loadable modules (*.ko)
Unpack the boot.img from the stock kernel (abootimg -x )
Create new boot.img replacing the original zImage with the custom kernel Image (abootimg --create . . . )
Make tar.md5 file of the custom boot.img for Odin3
Pushed the custom kernel using Odin3, but it fails to boot ("kernel not enforcing seadnroid"). I have tried using TWRP (install from zip), but it just does bootloop. Can anyone see what I am doing wrong? Am I missing something? I have read most of the "Build kernel from source" dev-threads but have not found a solution for this, nor am I allowed to post my questions there as I am just a junior member.
I would highly appreciate any help, as I have already invested some days with no avail
Click to expand...
Click to collapse
I dont want to tell you something you have already read, if you have been through the Dev forums, But on the off chance:
Have you removed the Fingerprint reader?
The Kernel will fail to boot with it enabled, Unless you know the workaround (EchoTeam)
dave7802 said:
I dont want to tell you something you have already read, if you have been through the Dev forums, But on the off chance:
Have you removed the Fingerprint reader?
The Kernel will fail to boot with it enabled, Unless you know the workaround (EchoTeam)
Click to expand...
Click to collapse
Hmm ... Fingerprint reader? No, I have not removed anything. I was thinking that since I am not adding anything that was not already in the stock kernel source, I do not need to do any modifications. How can I remove this reader?
Here are the temporary solutions.
Way A:
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Way B: (If you want to completely disable (or bypass) TEE)
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Replace /system/lib64/hw/gatekeeper.exynos8890.so,/system/lib64/hw/keystore.exynos8890.so with these i uploaded.
Both of them will make your FP Sensor not working.
(Lock Screen will work)
But,at least,you get a stable custom kernel.
Click to expand...
Click to collapse
http://forum.xda-developers.com/s7-...m-g935f-fd-t3361460/post66762787#post66762787
Thank @Jesse Chan He also fixed the fingerprint too.
dave7802 said:
http://forum.xda-developers.com/s7-...m-g935f-fd-t3361460/post66762787#post66762787
Thank @Jesse Chan He also fixed the fingerprint too.
Click to expand...
Click to collapse
Thanks a lot, I will try that. I have already seen his custom kernel (would love to ask something on his thread but . . . )
mdh-labs said:
Thanks a lot, I will try that. I have already seen his custom kernel (would love to ask something on his thread but . . . )
Click to expand...
Click to collapse
I saw someone mention me.
Well, you must disable all TIMA-related configs as well as KNOX_KAP to get kernel boot.
And then, if you want to get a stable kernel with FP, you must apply my FP fix.(could be found in my Kernel's flashable zip)
Jesse Chan said:
I saw someone mention me.
Well, you must disable all TIMA-related configs as well as KNOX_KAP to get kernel boot.
And then, if you want to get a stable kernel with FP, you must apply my FP fix.(could be found in my Kernel's flashable zip)
Click to expand...
Click to collapse
I appreciate that you have had the time to look at my question. I've tried the tricks you suggested but my kernel still cannot boot. Modified the .config file (with menuconfig):
disabled
# CONFIG_KNOX_KAP is not set
# CONFIG_TIMA is not set
# CONFIG_TIMA_LKMAUTH is not set
not in config anymore
-CONFIG_TIMA_LOG=y
-CONFIG_TIMA_RKP=y
Then built a custom boot.img as mentioned in my question and added the META and mcRegistry folders from your flashable zip file to create a zip file out of the three.
I have also tried by removing the libbauth* files from system/lib/ and system/lib64 directories?
One more thing, does it matter whether I get just an Image file or zImage from kernel build (I get only Image and .gz of it)?