Related
Hello guys I'm using cyanogenmod with a combination of cm tweaks and build.prop tweaks and it's running lightning speedy.
My combination here is:
CM TWEAKS: jit enabled, 16-bit transparency enabled. Disable others.
BUILD.PROP: added line "windowsmgr.max_events_per_sec=150" which is said to increase scrolling performance. Also, changed Dalvik virtual machine heapsize to 12m. Yes, 12m.
Damn fast for me. Share your combination!
I'm the same as you , except without that build.prop tweak and with 32m heapsize
Im using these tweaks on my SGA :
V6 SUPERCHARGER script
Loopy Smoothiness script
and CM Tweaks, pretty much the same as yours
It runs like hell lol just like that game on iOS.
just would like to ask how you apply those tweaks.
how to apply 16 bit transperancy? and how it helps to bosst up speed?
and also i have class 2 mmc and i have moved dalvik cache to sd, now i want to revert it to phone memory or cache but in A2SD it shows not enough memory...
I have supercharger too, applied it too long ago to remember
jameslaurence2004 said:
just would like to ask how you apply those tweaks.
Click to expand...
Click to collapse
CM tweaks refer to the one in cyanogenmod settings>performance.
Build.prop tweaks, use root explorer and go to system>build.prop, and mount r/w. Then add in the line.
and what about 16 bit transparancy?
nilzkul said:
and what about 16 bit transparancy?
Click to expand...
Click to collapse
I have the overclock-compatible kernel, maybe that was the one that added the transparency option in CM settings.
And how does tht helps in improving performance?
Scrolling seems better. Though I see visual glitches in some apps, but nothing big. Google it then if you want the technical explanations!
Hey I flashed with OC kernel though I couldn't find 16 bit transperancy option....could u tell me where I can find that option?
nilzkul said:
Hey I flashed with OC kernel though I couldn't find 16 bit transperancy option....could u tell me where I can find that option?
Click to expand...
Click to collapse
Cyanogenmod settings->Performance
CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7
Overclocked @ 921Mhz
Dta2sd: enabled
8gb class 2 + 1gb ext4 partition
I didn't find such option dear :/
What best CM performance setting you recomend for Behrad rom 2.2 update?
Im at:
normal 800 Mhz CPU ondemand
using enabled JIT
enabled surface dithering
VM is 32
1 Gb sd-ext
256 Swap
Dalvik is on sd...
Is there any option how to make it faster without overclocking?
I dont use any supercharger...
Best result in quadrant is 1875 without any airplanemode ar app killer....
Thx ;-)
Zeduaz said:
What best CM performance setting you recomend for Behrad rom 2.2 update?
Im at:
normal 800 Mhz CPU ondemand
using enabled JIT
enabled surface dithering
VM is 32
1 Gb sd-ext
256 Swap
Dalvik is on sd...
Is there any option how to make it faster without overclocking?
I dont use any supercharger...
Best result in quadrant is 1875 without any airplanemode ar app killer....
Thx ;-)
Click to expand...
Click to collapse
Supercharge it, ram probably works more efficiently. Use 16 bit transparency!
I don't use swap. A slow sd slows it down, swapping also uses CPU.
nilzkul said:
Hey I flashed with OC kernel though I couldn't find 16 bit transperancy option....could u tell me where I can find that option?
Click to expand...
Click to collapse
I'm on the kang newest build, does that help?
i am on Behrad's CM ....
nilzkul said:
I didn't find such option dear :/
Click to expand...
Click to collapse
Its der. Search it cirrectly. Its d 5th option, jus under Enable surface dithering.
CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7
Overclocked @ 921Mhz
Dta2sd: enabled
8gb class 2 + 1gb ext4 partition
Thanks a lot for advice!!! I will test it after this changes ;-)
Edited: qudrant is now better at 1905 points with normaly everything running...
One more question: what about compcache ram usage? I have it disabled - is that ok?
Sent from my GT-S5830 using XDA App
What is benefit of reduce kernel size?
and What is benefit of xz decompression?
only faster booting time?
kgp700 said:
What is benefit of reduce kernel size?
and What is benefit of xz decompression?
only faster booting time?
Click to expand...
Click to collapse
Main reason for most kernel devs to reduce kernel size by decompression is that the system partition (in which the kernel has to be placed) is no so big.
Some kernel devs have already reached the size limit with adding many modules, libs and add-ons, that on some phone's the kernel can't be flashed any more.
I think that e.g. gokhanmoral has come to this situation with a special version of his ICS SiyahKernel ... maybe you should have a look at his changelog.
It_ler said:
Main reason for most kernel devs to reduce kernel size by decompression is that the system partition (in which the kernel has to be placed) is no so big.
Some kernel devs have already reached the size limit with adding many modules, libs and add-ons, that on some phone's the kernel can't be flashed any more.
I think that e.g. gokhanmoral has come to this situation with a special version of his ICS SiyahKernel ... maybe you should have a look at his changelog.
Click to expand...
Click to collapse
oh i see
thank you answer
this is not mine, someone else has thought to do this mini-guide, so if there is helpful before putting a thanks to me put it to him.
http://forum.xda-developers.com/showthread.php?t=1853669:laugh:
You'll need to flash a kernel which support all those features ...
pator5 said:
You'll need to flash a kernel which support all those features ...
Click to expand...
Click to collapse
There is a kernel for xperia active that supports this?
I think mesa and panik kernel support these functions, correct me if I'm wrong
but still not able to run the swap ... I can run swapper only in fat32
Also rage has swap but need to put the script for it in init.d, but tbh there really is no point in using swap...
I need a solution because I love the MIUI rom but after some time of use is heavy and slows
devlopers plz help , we want 318mb ram kernel for cm10.1 v1.1 .
how can i edit zimage ?
kktkaran said:
devlopers plz help , we want 318mb ram kernel for cm10.1 v1.1 .
how can i edit zimage ?
Click to expand...
Click to collapse
Realy ? You want edit zimage ? hahahahah
DOWNLOAD .... SOURCE- make customize - built it via ubuntu
there is no servant to you
http://forum.xda-developers.com/showthread.php?t=2276481
No idea what exactly for Kernel is needed...
More mandatory IMHO is background info about RAM handling in badadroid...
What is where reserved... in 256 MB and in 128 MB RAM
Is 512 MB OneNand involved with write access or not...
Is it possible/helpfull to use memory area in 512 MB as "SWAP" to increase faster RAM...
And only Devs who allready released Kernel know what they have tried...
Otherwise ""we"" start again from scratch... to reverse hundreds of Bytes Sourcecode...
Best Regards
with 318 you break full video (cam, web, film)
wait we make new way without bigmem but full work
Is it possible to make "ON/OFF Button" in Kernel...
So user can select self, without change different kernel.
In this kind...
Choose FULL stable
or
MAX RAM with no Cam etc...
Best Regards
adfree said:
Is it possible to make "ON/OFF Button" in Kernel...
So user can select self, without change different kernel.
In this kind...
Choose FULL stable
or
MAX RAM with no Cam etc...
Best Regards
Click to expand...
Click to collapse
in newest kernel of fnf you go to terminal and type "reboot bigmem"
Tigrouzen said:
with 318 you break full video (cam, web, film)
wait we make new way without bigmem but full work
Click to expand...
Click to collapse
thank u so much for this :good:
kktkaran said:
devlopers plz help , we want 318mb ram kernel for cm10.1 v1.1 .
how can i edit zimage ?
Click to expand...
Click to collapse
I saw a man here said that he is working on akernal that have 386 mb and he will publish it soon so just wait and see ..
adfree said:
http://forum.xda-developers.com/showthread.php?t=2276481
No idea what exactly for Kernel is needed...
More mandatory IMHO is background info about RAM handling in badadroid...
What is where reserved... in 256 MB and in 128 MB RAM
Is 512 MB OneNand involved with write access or not...
Is it possible/helpfull to use memory area in 512 MB as "SWAP" to increase faster RAM...
And only Devs who allready released Kernel know what they have tried...
Otherwise ""we"" start again from scratch... to reverse hundreds of Bytes Sourcecode...
Best Regards
Click to expand...
Click to collapse
bada use 512mb onenand as write access memory , and 256+128mb access memory also ?
@mylove90 , where r u ? he had made 318mb kernel for cm10 v0.3 by rebbelos
Sorry for late reply
I stopped playing with kernel and such stuff for a while and my sources got corrupted again
Regarding big memory thing....Devs like @Tigrouzen or @volk204 can do it without any efforts
Here i am posting how to get a 318 mb RAM configuration (for Devs who can build the kernel)
got to path : *kernel_path*/arch/arm/mach-s5pv210/mach-wave.c
look for these lines or something similar
//FIMC stands for Fully Interactive Mobile Camera
#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC0 (11264 * SZ_1K)
#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC1 (9900 * SZ_1K)
#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC2 (11264 * SZ_1K)
//MFC stands for Multi Format Codec
#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC0 (11264 * SZ_1K)
#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC1 (11264 * SZ_1K)
Click to expand...
Click to collapse
So as you can see FIMC is reserved RAM for the Camera....replace corresponding numbers with "0" zero and you will get a 295 Mb RAM kernel with no camera
MFC is for video playback....replacing this too by "0" you will get a 318 Mb RAM kernel
Sorry again but i am stopping my development for a while because i am looking for a job !
Best Regards
mylove90 said:
Sorry for late reply
I stopped playing with kernel and such stuff for a while and my sources got corrupted again
Regarding big memory thing....Devs like @Tigrouzen or @volk204 can do it without any efforts
Here i am posting how to get a 318 mb RAM configuration (for Devs who can build the kernel)
got to path : *kernel_path*/arch/arm/mach-s5pv210/mach-wave.c
look for these lines or something similar
So as you can see FIMC is reserved RAM for the Camera....replace corresponding numbers with "0" zero and you will get a 295 Mb RAM kernel with no camera
MFC is for video playback....replacing this too by "0" you will get a 318 Mb RAM kernel
Sorry again but i am stopping my development for a while because i am looking for a job !
Best Regards
Click to expand...
Click to collapse
best of luck :good:
but plz make kernel , when u will be free
I have created this thread for requesting the devs for compiling cm7 ROM for our wave's device
As everybody knows that wave has very less ram and in jb and kitkat ROMs after installing several apps and gapps it lags like hell
so if anybody can build cm7 for waves it will be appreciated for devs it will not take much effort so please make it
Hm good idea..
But:
1. Source od Android 2.3.6?
2. Kernel (zImage)?
Bootloader and Fota we have.
A Early build You can find
AT this Forum its froyo
Sent from my GT-N7100 using XDA Free mobile app
ghoslslender124 said:
Hm good idea..
But:
1. Source od Android 2.3.6?
2. Kernel (zImage)?
Bootloader and Fota we have.
Click to expand...
Click to collapse
u can download official cm7 sources and there are many compress sources across 200 to 300 mb
u can compile it inlinux
karan1719 said:
u can download official cm7 sources and there are many compress sources across 200 to 300 mb
u can compile it inlinux
Click to expand...
Click to collapse
well i have knowledge in porting ROM, it would be easy to port bettwen i9000 and s8500, just edit kernel, keys, build.prop and some google codes.. but i dont have testdevice, i to brick phone is very easy with this
If you use badadroid as basis, you can't brick the phone since it do everything on virtual partitions...
But it need to adapt all the work oine by the badadroid team on a GB kernel
Maybe possible to use Oleg froyo sourrces, update to GB and backport all new things from badadroid (wave 2 compatibility,modem,wifi,gps...)
I think GB also work with 3.x kernel so there is nothing to worried cause jb and kitkat also uses same version of kernel
Now, this is interesting, given the amount of RAM we have nothing would run better than GB.
Hmm.. true story
Fidelator said:
Now, this is interesting, given the amount of RAM we have nothing would run better than GB.
Click to expand...
Click to collapse
I have one really wierd question that might piss off some badroid devs, and I am very sorry about that. But, why was kitkat ported to Wave and not JB ot GB? I mean, low RAM is really a bad problem and with GApps, the lag is a bit anoying.
TheBasterd said:
I have one really wierd question that might piss off some badroid devs, and I am very sorry about that. But, why was kitkat ported to Wave and not JB ot GB? I mean, low RAM is really a bad problem and with GApps, the lag is a bit anoying.
Click to expand...
Click to collapse
Jb has been ported to wave, (Android 4.1, 4.2 and 4.3) but are not updated (see old badadroid threads) (GPS is only on 4.4 i think, maybe on 4.3).
Also, ICS has been ported to wave 1 by mike (that's the beginning of Badadroid project), upgrading the GB kernel from Oleg, if i remember correclty (that's old). But in Mike ICS or Oleg GB, only wave 1 is supported, and there is no network.
kitkat is big joke from google
even wave2(ics) is faster than note2(kitkat)
google was saying at the time of release of kitkat that it is optimised for low ram device
but its very hard to find anything running official kitkat with less than 1 gb ram
BTW to my understanding virtual RAM partitions on solid storage are very likely to damage it if I'm not wrong.
And yeah, KKs main goal was to fix the nonsensical performance hit taken from the 4.3 update, IMO they could have done even better by trying to optimize it for even lower end hardware, such changes would be noted around the whole device lineup, still its noticeably better than 4.3 and pretty close to 4.2/4.1 levels
Fidelator said:
BTW to my understanding virtual RAM partitions on solid storage are very likely to damage it if I'm not wrong.
And yeah, KKs main goal was to fix the nonsensical performance hit taken from the 4.3 update, IMO they could have done even better by trying to optimize it for even lower end hardware, such changes would be noted around the whole device lineup, still its noticeably better than 4.3 and pretty close to 4.2/4.1 levels
Click to expand...
Click to collapse
BTW to my understanding virtual RAM partitions on solid storage are very likely to damage it if I'm not wrong.
Click to expand...
Click to collapse
WTF! Really? How so? Could you explain please?
TheBasterd said:
WTF! Really? How so? Could you explain please?
Click to expand...
Click to collapse
zRam doesn't damage nand or SD, but swap does.
zRam use real RAM and compress it, but swap create file on SD or Nand, and constantly write on it.
Flash memory have a limited write lifetime (like SSD), so, using swap is not good for flash memory.
Not dangerous, but it use it faster.
BenzoX said:
zRam doesn't damage nand or SD, but swap does.
zRam use real RAM and compress it, but swap create file on SD or Nand, and constantly write on it.
Flash memory have a limited write lifetime (like SSD), so, using swap is not good for flash memory.
Not dangerous, but it use it faster.
Click to expand...
Click to collapse
But, I did not make the swap file on SD card, but in the internal partition of bada, that is the bada_app or something like that. All I know is that it is in the internal memory, so if I use it, will it damage it ?
TheBasterd said:
But, I did not make the swap file on SD card, but in the internal partition of bada, that is the bada_app or something like that. All I know is that it is in the internal memory, so if I use it, will it damage it ?
Click to expand...
Click to collapse
It's flash memory, so yes.
TheBasterd said:
But, I did not make the swap file on SD card, but in the internal partition of bada, that is the bada_app or something like that. All I know is that it is in the internal memory, so if I use it, will it damage it ?
Click to expand...
Click to collapse
Yeah, as BenzoX said, use a microSD for the swap partition, if you kill the internal storage you'll probably be screwed.
BenzoX said:
It's flash memory, so yes.
Click to expand...
Click to collapse
Fidelator said:
Yeah, as BenzoX said, use a microSD for the swap partition, if you kill the internal storage you'll probably be screwed.
Click to expand...
Click to collapse
OK! So, thats the kind of sh!t you dont wanna do. Deleting it ASAP. Thanks for the info guys.
But, without that, the ROM is pretty slow.