Jump to content

Modified kernel (EXT4,TUN,CIFS) UVOC 1113 MHz


Recommended Posts

Guest Richard Trip
Posted (edited)

Just something to test (tested and working on my own device with MCR3 ):

Kernel 2.6.29 bravo:

  • patched Undervolted and Overclocked 1113 MHz (you need setcpu.txt on sdcard)
  • EXT4
  • tunnel module (automaticaly loaded on boot) NEW version without reboot bug!
  • cifs module

Apply with recovery console.

MCR version : http://android.modaco.com/index.php?act=at...st&id=55899

Stock rom version: http://android.modaco.com/index.php?act=at...st&id=55711

If you need other modules let me know.

setcpu.txt

MCR_uvoc_V7_signed.zip

Edited by Richard Trip
Guest squrl
Posted

For us noobs, can you shortly explain the benefits of these modifications?

Thanks.

Guest Richard Trip
Posted
For us noobs, can you shortly explain the benefits of these modifications?

Thanks.

Ext4 is a newer/better filesystem (you can use it with apps2sd). Tun.ko is for openvpn and vpnc users.

Compcache is memory compression (use google if you want to know more about it)

Guest squrl
Posted
Ext4 is a newer/better filesystem (you can use it with apps2sd). Tun.ko is for openvpn and vpnc users.

Compcache is memory compression (use google if you want to know more about it)

Thanks, compcache looks promising. But form what I've read, I'm not sure if it'll be of any use for users that don't run heavy multitasking.

Guest furniel
Posted
anyone else tried this?

Yes, I tried and everything works good on MCR r2.

Guest arielext
Posted

I put it on the phone, wroks ok with R2 but dunno if compcache is actually working.

Only checked it with meminfo which says /proc/ramzswap does not exist

Guest Richard Trip
Posted
Richard! Can you help out over here: http://forum.xda-developers.com/showthread.php?t=681733 ?

Dev seems to have problems compiling his kernel, he actually does not have a Desire :)

Thanks!

Already looked into that. Have no problem compiling his patch, but i didn't get any overclock with setcpu. If you hear of any succes let me know and i patch the bfs kernel with it.

Guest Richard Trip
Posted

See my first post for a BFS enabled kernel. (dropped compcache).

Guest furniel
Posted (edited)

Thanks. setcpu works fine. Is it possible to involve all 576 ram, because at present time it is only 398?

Edited by furniel
Guest Richard Trip
Posted
Thanks. setcpu works fine. Is it possible to involve all 576 ram, because at present time it is only 398?

Maybe this is normal. Even the nexus with 21 mb extra "KANGMEM" hack has 416mb.

Guest Rdy2Go
Posted

Flashed successfully using recovery console.

My rom is "Pays-ROM Desire with Sense v1.5 A2SD Dalvik2SD (RockSolid)" from xda-developers.

Works excellent. Live wallpapers seem to be more fluent, especially Nexus One neural network wallpaper.

Guest cTrox
Posted

Nice, I want to flash it onto my desire with CM 5.0.6.

But I want to take a full backup of my ROM first. How can I run nandroid backup with the desire?

Guest Kali-
Posted
Nice, I want to flash it onto my desire with CM 5.0.6.

But I want to take a full backup of my ROM first. How can I run nandroid backup with the desire?

on the same recovery menu for the zip update there is also a backup voice

Guest cTrox
Posted (edited)
on the same recovery menu for the zip update there is also a backup voice

Ok, I saw it now. I just searched for "nandroid" and didn't notice the Backup/Restore line^^

flashing the zip now...

Edit: didn't work that great. Apps2SD wasn't working anymore and the launcher kept crashing. Restoring now...

Edited by cTrox
Guest Richard Trip
Posted
Ok, I saw it now. I just searched for "nandroid" and didn't notice the Backup/Restore line^^

flashing the zip now...

Edit: didn't work that great. Apps2SD wasn't working anymore and the launcher kept crashing. Restoring now...

This boot image has apps2sd working. Using it with apps2sd + dalvik-cache on Ext4 partition.

Guest Kali-
Posted
Edit: didn't work that great. Apps2SD wasn't working anymore and the launcher kept crashing. Restoring now...

same problem with launcher (helixlauncher2), not using a2sd/a2sd+

this kernel does not working well with CM

Guest Richard Trip
Posted (edited)
same problem with launcher (helixlauncher2), not using a2sd/a2sd+

this kernel does not working well with CM

Only tested on MCR. CM uses a 2.6.33 kernel

Edited by Richard Trip
Guest Richard Trip
Posted
Can I still use my Ext3 A2sd after flashing?

Yes, I did not disable anything compared to base config (only enabled extra stuff and patched the kernel with another scheduler BFS)

Guest antihero_
Posted

How are camera and bluetooth with Cyanogen?

Guest cTrox
Posted
Yes, I did not disable anything compared to base config (only enabled extra stuff and patched the kernel with another scheduler BFS)

Flashed it, but the launcher still crashed all the time.

Guest Richard Trip
Posted
Flashed it, but the launcher still crashed all the time.

OK, see the problem. This kernel will not work on CM 5.06 because there's a 2.6.33 kernel in it.

Someone need to port the htc stuff to 2.6.33. (i can't do that :-))

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.