Related
image sources: mik_os' profile and franciscofranco's dev thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
True, there are (tho outdated) threads like [Q] CM7 + Franco's Kernel??? and [Q] MIk + Franco but now this is NOT ONLY A THREAD FOR QUESTIONS.
As I've seen many people asking questions about this combination in one of the ROM/Kernel thread and they can't get answers from experienced users of this combination,
(some in mik's thread dont use franco, some in franco uses devoid only)......
QUESTIONS ARE NOW OPEN!
But make sure yourself is not a noob! if you are, try [READ FIRST] [REF] Dictionary for n00b - What is.../What does ...mean? first
Introduction
Many users have found that this combination is totally cool right?
however there may still be bugs in this combination
because mik_os' ROM is Android 2.3.x Gingerbread
and franco.Kernel is made for Android 2.2 Froyo <<< Yay BFS version for 2.3 is out XD
If you want to ask questions based only on mik_os' rom?
Here: [discussion]LG P500 mik_os's port of cyanogenMOD7, problems, questions, and answers.
If you want to ask questions based only on franco.Kernel?
Here: [Q] franco kernel problem
If you want to ask questions about the fantastic combination?
If you absolutely want to flash and try yourselves, but sometimes would prefer searching in XDA in advance and see what the others' results are?
or if you have tried this combination out, and would like to share to others so they can take your results as references before flashing?
Here, this thread, is what you want.
Btw, feel free to vote the poll at the top
Their Development Threads
[DEV][UNOFFICIAL][ROM][stable:version/testing:version] CyanogenMod version
[KERNEL][date of update] franco.Kernel |version|VR|CFS|SLQB|SMARTASS|TinyRCU|ZRAM|GPU+|. 39 |
Main Purpose of This Thread
- To share our results after flashing the combination
- When they update, we update!
- Confirm it if a bug has solved in later versions!!
- Questions are now open! Just make sure you've searched around and not wasting time here
- Only share your results after you confirm the errors are bugs of the combination instead of your own problem
- Also, we can directly answer the problem of a result if you know it is just human error instead of a bug BETWEEN THE COMBINATION!
- All other discussions are totally welcome!
Complete Results Sharing Form (if needed)
Italic words as examples
Bold words for you to copy
ROM version: 6.5.2
Kernel version: v15.1
App2SD: Darktremor 2.7.5.3-beta04
Data2SD: None
Additional information: ZRAM enabled
Stable Overclocking: 600/806 InteractiveX
Benchmark scores:
Quadrant 2000
Neocore 60fps
Error(s) or bug(s) discovered:
Bluetooth doesnt work
Call waiting disabled
Any suggestions for this thread are totally welcome!!
Hope this can help other users which are new to this combination but get tempted by the great performance comments everywhere
Remember, only share your results after you have tested the combination for at least 12 hours, thanks!
Myself as the first
ROM version: 6.5.2
Kernel version: v15.0
App2SD: Darktremor 2.7.5.2-1
Data2SD: None
Additional information: ZRAM enabled
Stable Overclocking: 122/729 SavagedZen
Benchmark scores: (if you want to share)
Quadrant 1534
Error(s) or bug(s) discovered: (if there is)
Random shutdowns/reboots!
with the latest v16 franco's kernel cmparts error on boot is gone
overclock settings are applied correctly, no need of setcpu anymore.
well done! there's still just the battery temperature bug though
vizzze said:
with the latest v16 franco's kernel cmparts error on boot is gone
Click to expand...
Click to collapse
what do you mean by cmparts error on boot?
You mean, there wont be random shutdowns when im using the phone?
there was, when it is v15
Miasmic said:
what do you mean by cmparts error on boot?
You mean, there wont be random shutdowns when im using the phone?
there was, when it is v15
Click to expand...
Click to collapse
never happened to me the shutdown problem... i mean the cmparts process that couldn't start on andoid boot because of franco's kernel
vizzze said:
never happened to me the shutdown problem... i mean the cmparts process that couldn't start on andoid boot because of franco's kernel
Click to expand...
Click to collapse
oooh would appreciate a lot if someone can tell me whether the shutdown problem has solved in v16
anyway thanks
for me
Cm7 6.5.2
kernel v15.1
zram enabled
oc 480/768 smartass
neocore 59.9
quadrant 1638
bug, kernelpanic with oc at 806 Mhz
indian65 said:
for me
Cm7 6.5.2
kernel v15.1
zram enabled
oc 480/768 smartass
neocore 59.9
quadrant 1638
bug, kernelpanic with oc at 806 Mhz
Click to expand...
Click to collapse
cool!! there are no random shutdowns in 15.1? did u experience v15.0 before
Sent from my LG-P500 using XDA Premium App
No random shutdowns in v16 ...
I'm on miks cm 6.5.2 with Franco kernel + zram and 320/748 oc on interactiivex.
Sent from my LG-P500 using XDA Premium App
I just flashed this kernel and zram and the quadrant scores at 806 mhz are almost the same scores I get with the original CM 7 kernel. Performance wise I think in games and just regular use it feels a lot more smoother. I just don't see it in the scores.
Heheheh Im now flashing the combination of miks 6.5.4 and franco's v16 BFS version
report to u guys 2 days later!
Cyanogenmod 7 by mik_os 6.5.4-stable with Franco's Kernel v16fix @729/480 smartass governor, no App2sd nor Data2sd due to my ****ty stock SD...
Linpack >= 8.8
Neocore (w/ audio): 57.3
Neocore (no audio): 60.5
Quadrant: 1486
6.5.4 Stable + v16.0 BFS Results
Ok so hey guys after using the newest combination for about a day ive come up with a detailed report for u
ROM version
6.5.4 Stable
Kernel version
v16.0 BFS for andy and mik
App2SD
Darktremor 2.7.5.2-1
Data2SD
None
Additional information
ZRAM enabled
Stable Overclocking
122/710 SavagedZen
Benchmark scores
Quadrant ~1400
(idk may be i got too many apps lol around 400)
LIST OF BUGS OR UNUSUAL ISSUES DISCOVERED AND COMMENTS
*"pure" = mik's rom + mik's kernel (the one attached with the rom)
- USB debugging icon is missing even it has solved in 6.5.4
- (already found this in older versions of the combination but didnt post) the keyboard sometimes doesnt pop out when necessary and wastes one more click (for me, App Protector Pro password insert page)
- My phone was stable @748 max using this combination but yesterday it panics at 729 and i was like =.=
- Performance boost is not as significant as when i was at 6.5.3 + v15.0 + zram
- (very disappointing) The CPU is not sensitive/reactive as before, even less reactive than pure 6.5.3, so i had to increase the minimum from 122 to 480 (I tested this with SeePU on at 0.5 second interval and scrolling homescreens, launching benchmarks etc.)
- Yea the camera crashes when restoring defaults in recording mode as stated in mik's dev thread
- The phone's temperature is average 39 degree vs pure's 33 degree
- Temperature displays incorrectly (39 degree as 3.9 degree) vs correctly in pure
CONCLUSION
lol mainly because of the insignificant performances boost even zram is on, im back to mik's pure now
good luck to u all and hope these help
Miasmic said:
Ok so hey guys after using the newest combination for about a day ive come up with a detailed report for u
ROM version
6.5.4 Stable
Kernel version
v16.0 BFS for andy and mik
App2SD
Darktremor 2.7.5.2-1
Data2SD
None
Additional information
ZRAM enabled
Stable Overclocking
122/710 SavagedZen
Benchmark scores
Quadrant ~1400
(idk may be i got too many apps lol around 400)
LIST OF BUGS OR UNUSUAL ISSUES DISCOVERED AND COMMENTS
*"pure" = mik's rom + mik's kernel (the one attached with the rom)
- USB debugging icon is missing even it has solved in 6.5.4
- (already found this in older versions of the combination but didnt post) the keyboard sometimes doesnt pop out when necessary and wastes one more click (for me, App Protector Pro password insert page)
- My phone was stable @748 max using this combination but yesterday it panics at 729 and i was like =.=
- Performance boost is not as significant as when i was at 6.5.3 + v15.0 + zram
- (very disappointing) The CPU is not sensitive/reactive as before, even less reactive than pure 6.5.3, so i had to increase the minimum from 122 to 480 (I tested this with SeePU on at 0.5 second interval and scrolling homescreens, launching benchmarks etc.)
- Yea the camera crashes when restoring defaults in recording mode as stated in mik's dev thread
- The phone's temperature is average 39 degree vs pure's 33 degree
- Temperature displays incorrectly (39 degree as 3.9 degree) vs correctly in pure
CONCLUSION
lol mainly because of the insignificant performances boost even zram is on, im back to mik's pure now
good luck to u all and hope these help
Click to expand...
Click to collapse
Excuseme how can i found mik_os's kernel??
chessy018 said:
Excuseme how can i found mik_os's kernel??
Click to expand...
Click to collapse
It is attached with the zip mik has provided in his dev thread
you have to flash the rom in order to get the attached kernel
for reference, the version of the kernel is displayed 2.6.32.41 on about-phone now
good luck!
ok guyz
i haven't tried 6.5.4 yet coz 6.5.3 working well until now ..
i have 6.5.3+ franco kernel 16 (old one) no zram nothing else
and performance is quit Good bt i think it was more better in Franco 15 kernel ..bt may b its only my thinking coz i analyze when we use data 3g wi fi phone getting heated nt tht much bt u can feel it don;t know..may b its only me feeling bt i have seen some users who already told me about that ..ok then as far as performance concern here check my attachment
battery is nt that bad at normal uses its around 30 hr long
Y.u.v.i said:
ok guyz
i haven't tried 6.5.4 yet coz 6.5.3 working well until now ..
i have 6.5.3+ franco kernel 16 (old one) no zram nothing else
and performance is quit Good bt i think it was more better in Franco 15 kernel ..bt may b its only my thinking coz i analyze when we use data 3g wi fi phone getting heated nt tht much bt u can feel it don;t know..may b its only me feeling bt i have seen some users who already told me about that ..ok then as far as performance concern here check my attachment
battery is nt that bad at normal uses its around 30 hr long
Click to expand...
Click to collapse
lol yea for me even zram activated there are significant performance regression of v16, could really feel it! i think its probably the "cpu responsiveness" ive mentioned
but well the 15 gives random shuts hate it
thx for ur info
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
franciscofranco said:
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
Click to expand...
Click to collapse
Haha franco thx for giving advice in this thread
oh ur tempting me mate thats cool
just a side question do i have to wipe anything except cache, dalvik, battery stats? if i give it a try to swap from mik's to andy's
or do i have to wipe everything and do a complete titanium lol
also why cant i see ppl using or comment about savagedzen? i personally use it idk why
and yeah thanks ive been searching for that for a while but cant find the clue and you answered me directly all my profile mins are 480 now!
franciscofranco said:
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
Click to expand...
Click to collapse
yes excuseme how do i change mik to andy? wipe which? thanks very.
I have made a lot of searches and read a lot about battery calibration... and of course i know what the hell is kernel panic, its definition and its symptoms.
However I still have some confusions and I hope some of you may be able to solve them
Maybe some of them are noobie questions but I honestly sorry for that also this may help others who has these confusions too
My situation:
The system stats are shown in my signature.
on 5/9 I have flashed franco.Kernel v19.4 bfs and then started a lot of OC tests,
finally I was stable on stress test (SetCPU) 729mhz for 2 hours non-stop,
and also I used the phone stably for over 24 hours without reboot.
However I faced a problem which is related to Darktremor scripts.
I used 2 weeks to solve it and finally it is gone now.
I started battery calibration which is the final process before I use my phone normally in my daily lives.
But in these two days, my kernel panics after ~4 hours of usage of 729mhz max CPU frequency.
without the need of advice, surely i have downclocked to 710mhz max and its all good. but however i am super curious about why 729 becomes from stable to unstable before and after.
1) Does battery stats related to kernel panics in ANY extent? if yes, how?
Ignore all questions under 1 if the answer is No.
1.1) Does wiping battery stats before flashing a kernel helps you OC higher?
1.2) Does wiping battery stats before flashing a ROM helps you OC higher?
1.3) Does wiping battery stats (for calibration purposes) has possibilities to produce kernel panics?
2) Why is there a sudden drop of battery level (~4-5%) after kernel panics?
3) Is there any other possible causes of kernel panics BESIDES overclocking too high?
3.1) *2sd scripts?
3.2) ext4 barrier = 0?
3.3) inputting EXT4 data writeback?
(tune2fs -o journal_data_writeback /dev/block/mmcblk0p2)
4) Is SetCPU the problem?
Some says "dont use SetCPU when you can overclock using CM7 settings."
Is that true?
5) BESIDES the max speed, does it also depends on Governors?
Ignore powersave governor or others which forces the clock to the minimum frequencies.
So, is there any difference between setting the same maximum speed, different governors?
(for example) Would smartass gives a panic at 729mhz but ondemand doesnt?
6) Does the "change of frequencies" gives easier kernel panics?
Situation A: 729min, 729 max
Situation B: 480min, 729max
In situation B, the system makes the frequencies change due to load, means it may switch from 480 -> 600 -> 729 -> 710 -> 691 -> 480 etc.
so does this "change of frequencies" makes the kernel loads more and finally gets it to panic?
Thanks for your time reading and answering my questions!
Please just quote one of them if you would just like to answer one of the above
Thank you very much!
1) no.
2) It happens when u remove the battery and put it back.
3) There are some strange reports of kernel panic at 600Mhz which are weird. Sometimes Roms/kernel play a part(unknown).
4) it is because you can overclock in Cm7 settings menu, so no need to install another app such as SetCpu
5) Maybe, a governor who stays more on the highest frequencies i think are easy to panic because hardware can't handle it.
6) for me, i would say situation A would be easier to kernel panic, as it is constantly on the highest frequency and stressing your cpu too much that it can't handle it.
Since you get stable at 729mhz for 2h and panicked when 4h of use, that means the cpu can't handle 729mhz for above 4h.
@terratrix
thanks for your reply!! at least im not using my stupidity to wipe battery stats and trying to avoid kernel panics, lol.
@info update and conclusion after 1 more day of testing
And there, after some readings on the forum and the experiences myself, i think i have found the critical point already - QUESTION NO.5
Conclusion : kernel panics are related to governors, at least, our new amazing profiled one - SmartassV2!!
On the thread of Franco's .35 v1 kernel, there are some users reporting the panic issues faced with ONLY SmartassV2.
And me myself, has joined the party as well
Smartass(v1) has been my best bud all the time at 729mhz or even higher for more than 6 months. And when I left it and went to choose his next generation, my phone got a generation gap with Mr.V2, lol.
On my phone: (Franco.kernel 19.4bfs and no any reflash or stuffs between testings)
SmartassV2 ---
very unstable panics AND random shutdowns at random times
729mhz - sometimes 2 hours, sometimes 4 hours
710mhz - yeah I justnow kernel paniced with this also, you know how long after boot? 30minutes!!!
Why 30minutes? I suspect that it.is related to franco's network speed hack. I'm on EDGE data plan and because of Franco, I can enable HSDPA with 4x more speed.
On 710mhz, my phone was stable for over 8 hours with EDGE on (I intended to save battery), but after a reboot (manual one for some other purposes) I started to use (the hacked) HSDPA. After 30 minutes, panic. I remembered when I was at 729 on smartassv2 I panicked after 3 hours and at that time I was using HSDPA too.
Smartass (v1) ---
Well now I'm on smartass v1 at 729mhz stably typing this message. Funny huh...?
Results:
Franco's network speed hack
OR
3G network/HSDPA network
OR
Even just because of specific phone hardwares
IS NOT COMPATIBLE WITH THE ALMIGHTY SMARTASS-V2 GOVERNOR AND WOULD RESULT IN KERNEL PANICS AT THE FREQUENCIES WHERE THE PHONE CAN BE STABLE WITH OTHER COMMON GOVERNORS.
If I am wrong or you can confirm this by testing yourself, please let me know!!! thanks and hope I have provided some useful information
Goodnight and I'm going to continue working with my old friend smartass-v1 despite v2 has better profiling tweaks, lol
Sent from my LG-P500 using XDA Premium App
Dude, as i had mentioned earlier in franco's thread, that it had to do with the governors... cause i usually try and find out the cause of the issue myself before posting a bug..
SO all i tried were playing around with the performance settings... and i start off with changing the governors... the best targeted experimental ones are MINMAX (my personal fav), SMARTASS, SMOOTHASS (now removed but one AWESOME governor), and INTERACTIVE-X (rewritten by franco i guess).... About the frequencies... from what i have observed so far apart from reading stuffs is that, at 729 Mhz our optimus DOES pretty much stay stable even in the ****TIEST devices.. LOL i can say that cause we indians get the crappiest hardware of all... the point is... if you got a kernel panic at 729, it is most likely that you would get it again at 600 Mhz too cause its not overclock related..!!!
Bottom-line: Avoid SmartassV2 unless your phone is made of the finest hardware i.e. you can easily overclock it to 806 Mhz (ive seen some users using it at this frequency without any issues at all .. :O ) Use Smartass older or Minmax instead...!! And avoid overclocking above 729..!!!
P.s.: mine works fine even at 768 BTW....
We have to wait for Franco's next release for more smartass2 updates
Sent from my LG-P500
SmartassV2 is kind of strange, at least in my phone. I notice my battery draining faster while I use it, and it's probably because it stays in the max frequency longer for some reason, despite screen off. I use NoFrills for my CPU setting and it has the ability to view stats, and when I'm using V2 it stays longer at the max than at the min (65 vs 35%). The opposite is true for Smartass v1, which to me makes more sense because my phone stays at standby more often than being used.
As comparison data, my phone with smartass v1 can typically be OCed up to 787 MHz. 748 MHz on v2 is stable, but I haven't extensively tested higher freqs.
I have a Indian phone , smartass v2 oc to 768 stable xD
Sent from my LG-P500
Hi there
As I cant post on the SPARTAN ROM thread I´ll post my own experience with it
I´m going with the running specs:
- Rootet
- CWM for mini/mini pro/active
- Unlocked bootloader
- Custom stock OC
- Spartan Rom 1.4
Everything works like a charm. I went on trying ANTUTU BENCHMARK with stock rom/kernel getting 3004 points and moved to 4715 with SPARTAN ROM 1.4. The 1.3.5 Rom went only to 4500 ish points.
So there is a slightly increase in speed in the [V6] script. So keep going on with the development spartan lad.
I will for sure use this one. Hope in the future to be able to use custom themes, launchers and even maybe resolution (cant get why I cant play HD on the TINTIN game).
Greetings again ;-)
Running tests
Test using:
- Overclocked kernel with V6 9 script RC4
- V6 scripted SPARTAN ROM 1.4
- Rootet and CWM
- MiniSD with class 6 read
- Overclocked to 1,9 (performance and noop)
Its a shame the ACTIVE hasnt got a bigger screen
Almost 4800?
Normally I´m running daily basis at 122/1024 and Noop I/O Scheduler.
This ROM runs best using the SIO I/O Scheduler regardless of what I´ve read about it.
So testing and Overclocking for hours I´ve got this score using:
- Overclockable kernel
- Spartan ROM 1.5.1 with V6 Script v8 (revertet and re-applied)
- SD boost set to 2048
- VM darvik set to 48.
- Overclocked to 1,9 Ghz and with performance as guvernor and SIO schedule
- Minor tweaks
Thats on the fast part. I cant seem to go up to 2 Ghz. I did leave in the freezer for some minutes without random crash or reboot. So Im planning to leave it for about 1 hour and run a test again. Think it can reach 4900 on antutu and might reach the 5000 mark.
Also After running the Stability Test v 2.3 for hours the mobile reaches 50 degree celsius. Cant be healthy for the phone.
Havent finded so many bugs in this build mainly because its the stock rom somehow.
Give it a try. I could do wish the no background theme and black theme. Call it spartan? Go spartan all the way.
4800 hit
Well did hit the 4800 marker. Dont think we´ll never reach the 5000 marker unless we see a new script or tweakable kernel going far beyond 2 Ghz. Doomlord?
step by step
almost there to reach the 5000 points.
so close
almost hitting 5000. god knows what in trying to prove . but sure its stable all the way. can do say and recommend this build. nice work dumraden ;-)
well using uncap fps improved things here. not even a Samsung S2 beats this timings.
do Sony know what they've build? will try 2 GHz tomorrow.
nena.se/nenamark/view?version=1
EDIT: No longer necessary
With the dawn of the ICS ROMs behind us and now that we have all settled in a bit, I am interested in some of your parameters for overclocking and undervolting. I am mainly wanting these to put in my Battery Guide as some examples bc when I created the guide, the ICS ROMs were fledgling at best.
Mattymat brought this up in the Passion thread and the more I thought about it, the more some people are probably going to be wanting these. Plus I have already seen some people talk about random reboots and freezes and others asking about overclocking as well.
ICS runs well on its own at stock frequencies but there are those out there that want to push it a bit further. I could care less about Quadrant scores or benchmarks or YOUR battery life (especially with all the different batteries out there now).
What I want is voltages/frequencies with stability. Obviously every Vibrant is different. Also please list what ROM/kernel you are on as well.
Thanks to all
I use -50 across the range, normally i use frequencies set 200-1000 notice minimal lag, the improvement in user experience i get is minimal when I crank it further. Governor set to Conservative and Scheduler to SIO.
Currently i am using MP's latest subzero kernel found in the ICZen thread. Though i would also like to mention that this setting has worked on almost every ICS rom/kernel combo.
- Cheers
Overclocking (stable for my device) w/ Icy Glitch: 200mhz-1400mhz, 1400mhz step (1500mV), and 1200mhz step (1400mV), GlitchassV2.
It's stable, for me at least, and battery life isn't bad at all (8-9 hours).
Undervolting (stable for my device) w/ Icy Glitch: 100mhz - 1000mhz (-25mV w/ each step), GlitchassV2.
Definitely better battery life with this one (12-13 hours).
I notice that the lower frequencies (100mhz & 200mhz) have the same voltage (950mV), and when one gets undervolted and one doesn't (i.e 100mhz: 925mV; 200mhz: 950mV), videos get really choppy and unbearable to watch.
Sent from my SGH-T959 using XDA
Rom: ICS Passion v13
Kernel: Kiss v2.2 (Yum yum good #2)
Governer: SmartassV2
I am running -0mV on the two upper frequencies (they seem more sensitive to under volting) and -50mV across all other frequencies used. No problems encountered.
1200MHz : 1350mV
1000MHz : 1275mV
800MHz : 1150mV
400Mhz : 1000mV
200MHz : 900mV
100KHz : 900mV (not used but I lowered the voltage anyway)
Edit: upper frequencies do not like undervolting - experienced stutter on Angry Birds even at -25mV
Bump....I am going to be reworking the battery guide tonight or tomorrow and could use some more of theses, please
Here is Mahdi ROM 9/20 performance benchmark running the Dorimanx 7.8 Kernel provided thru Vanir developers..
21px said:
Here is Mahdi ROM 9/20 performance benchmark running the Dorimanx 7.8 Kernel provided thru Vanir developers..
Click to expand...
Click to collapse
holy crap, that's good. I got 34,000 with Cloudyflex 2.6, Dorimanx 7.9
benchmark tip
bloof said:
holy crap, that's good. I got 34,000 with Cloudyflex 2.6, Dorimanx 7.9
Click to expand...
Click to collapse
To achieve the higher score: enable 16bit transparency graphics under the Performance section which only AOSP roms have (and even then, only some have it). Then install Dorminax and set max freq to 2.8Ghz and use ondemand CPU governor. Then place phone in freezer after letting it cool down when you are ready to start the benchmark. This is not to cheap but to ensure temps don't cause the CPU to lower freq which would provide inconsistent benchmarks.
21px said:
To achieve the higher score: enable 16bit transparency graphics under the Performance section which only AOSP roms have (and even then, only some have it). Then install Dorminax and set max freq to 2.8Ghz and use ondemand CPU governor. Then place phone in freezer after letting it cool down when you are ready to start the benchmark. This is not to cheap but to ensure temps don't cause the CPU to lower freq which would provide inconsistent benchmarks.
Click to expand...
Click to collapse
LOL. good to know some tricks for making us feel better in benchmarks
But very good reminder to let my phone actually cool off more than I actually do. Hopefully I will learn more on Dorimanx tweaks to help with making this more automated.
I bet the phone types the text and then you're typing it on the keyboard because the multi score is awesome
Lol mine just restarts awhile after starting antutu at 2.8 what binning you have?
What do you mean by binning? I would tell you if i knew.
bloof said:
What do you mean by binning? I would tell you if i knew.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2489998
thanks for that link.
my numbers are:
speed bin: 2.3 GHz (but Dorimanx overclocks at 2.8 - also set in STweaks)
PVS bin 2