Develop Bugs

[Q] wtf

can someone please inform me how the tmobile galaxy s phone can reach quadrant scores of 2400 and im only pushing 1200

I've hit 2700 on my Evo my penor is HUGE!

haha funny i actually seen his quad score so i know its true

I wouldn't think too much of it. Cyanogen showed that the difference between 1200 and 40 gabillion in quadrant can be something as rediculous as the filesystem. I don't put much weight in those scores when comparing different phones.
http://briefmobile.com/cyanogen-demonstrates-quadrants-flaws

ok so other then cm what other rom/kernel would reduce lag and increase speed right now im trying fresh 3.3.0.1 with king kernel #9

jjarn said:
ok so other then cm what other rom/kernel would reduce lag and increase speed right now im trying fresh 3.3.0.1 with king kernel #9
Click to expand...
Click to collapse
Why don't you try installing >>Snap 7.6 kernel on a Sense ROM and then try to enable TURBO? That'll *should* get you scores beyond 2000 but I'm not sure how well it works. >>Snap kernels are designed for CM ROMs ONLY and there is no support for installing a >>Snap kernel on a Sense ROM - but I've read about others who've done it. Maybe give that a try? I haven't done it so I won't be any help but I've read about it which means maybe it'll work for you.

Dude I really don't understand why you're so concerned with Quadrant scores. It's just a number.

_MetalHead_ said:
Dude I really don't understand why you're so concerned with Quadrant scores. It's just a number.
Click to expand...
Click to collapse
Well, it does ultimately represent something. But unless you can see a real difference, I wouldn't care so much.

If your phone is snappy and smooth, it shouldn't matter what score you get in Quadrant. When I was on CM6 I was scoring 2000+, on Fresh I get around 1650 and I think my Evo is running way better with Fresh than it did with CM6.

well see ive tried fresh with the kings kernel and still not gettin that high i wanna try nets kernel but not sure which one is compatible i like baked but takes too long to boot i also like fresh

Have you tried the new official kernel? It's not going to give you crazy quadrant scores but it will make your battery last a lot longer + I think the way HTC lifted the cap makes it smoother than the custom kernels. It makes the phone more useful which IMHO is more important than Quadrant scores.

Sporkman said:
WATCH OUT his e - penis just shrank 2 inches
Click to expand...
Click to collapse
thanks for providing me with my new signature!

[KERNEL]1.28Ghz?!

Just wondering if anybody has tried this kernel yet? Found it over on AndroidMobileJunkie.com (Followed a link in somebody's sig here n XDA that said 1.28Ghz so naturally I was curious lol) Anyways, here's the link for the post over on AMJ. http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-22-oct.11/

yea ziggy's kernel. It's been in discussion in both of the Desire rom port threads. 1.28 is very rough on the processor though, and mostly unstable for a lot of people's phones (mine included), even ziggy admits it's a risky business, but he has proven it is possible.

I am so tempted to try this, but I'm afraid to fry my phone. My go big or go home mentality may make me give in. Wish there was someone who posted on the thread link

I ran it. No problems a 1.28 but really didn't use it long. Here's my Quadrant post in the Desire Z port thread:
http://forum.xda-developers.com/showpost.php?p=8775977&postcount=168
X

I'd imagine that clocking the processor that high wouldn't make much difference than say, 1.19GHz.
In fact, in plenty of ROMs I've tried, anything clocking over 1152mhz actually gives me a decrease in my quadrant scores. Not to say its not a stability issue - I'd assume that most Snapdragons actually clock higher than 998mhz, but then are reduced because that's baseline performance, anything less than 998mhz would get kicked.
I've never had a ROM crash, even running at 1.19GHz, but didn't notice any performance gains, plus, unless you just happen to get a chip that is capable of 1.28GHz no problem, it's probably near bottle-neck anyway.
And Quadrant has several variables way outside of clock speed that can pull 1800's, including just your flavor ROM.
Bottom Line: It's not worth frying your phone just for a barely-existent performance gain. If you happen to have a processor that is incapable of stability at 1.28GHz, you might fry out some transistors, then get stuck with something that freezes if you clock it over 700, let alone the 998 stock.

For me personally 1.28 is no improvement over 1.152. In fact, it gives me worse benchmarks.

sorry for repost

I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.

I tried this kernal and my camera stopped working...

HeyItsLou said:
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
Click to expand...
Click to collapse
Lou hit the nail on the head. I love the .17 kernel. Im using the new guy with great performance, battery life, charging, and neat transitions. its like a new phone.

I'm using this with a vanilla froyo ROM and my battery life is amazing. Haven't noticed any freezing or any program not working.

Wow!
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol

dimebagdan65 said:
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
Click to expand...
Click to collapse
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z

Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?

Nevermind...found it!

ziggy471 said:
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Click to expand...
Click to collapse
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy

hajabooja said:
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Click to expand...
Click to collapse
What AOSP kernel??? I only see one kernel, and it references skyraider, which leads me to believe it is a sense kernel
edit: I am dumb. It is a different thread on the same site as listed above
http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-aosp-23-oct.24/

rmaccamr said:
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
Click to expand...
Click to collapse
I didn't take it as such, and I agree with you fully. I prefer somewhere between 1.113 and 1.15. That's the reason I included the init script to set the max at 1.113, which I find very stable and fast, hell I'd say 1865 quad with ID's Z port isn't too shabby at 1.13.
I should be able to get 1.28 more stable with playing with the voltages, it's just that takes time, and I wasted too much this morning doing both AOSP INC and Evo kernels, so I'm worn out for awhile on kernels. I still need to fix the Evo for puertoblack, since it appears I left the debug port out, so no adb for it. lol
Z

[q] Livewallpapers

Hello!
I-m trying to apply several live wallpapers. Some crash, its acceptable.
Others, plain buggy. Example: Galatic Core.
I select it in the Livewallpapers selector, it does not error, and shows a black screen. i press settings, get the message "buy the app", and then it shows!
If i then select it, i get a black screen... and then the original wallpaper again.
Anyone got more luck than i ?

They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App

thoughtlesskyle said:
They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Could you guys please stop doing that ?
"" XPTO was not meant to run on our phone ""
What is it there... that our phones have... or have not... that make a given app not run ? Sure... we can agree on "it wasn't designed for 320x240. Ok, i agree too.
But either than that ?? Yeah, our CPU is the slower MSM on the field, at least compared to Diamonds/Raphaels and upwards... but hey!! We have 1/4 of the pixels to take care of. That sould give us some room...
Now, don't get me wrong. It was not designed to run Android. But that doesn't mean it was not meant to. Take for example a simple little phone, sold here on Portugal as Optimus Boston. It has a MSM cpu... it came with 1.6 running at 600mhz... but the latest update to Eclair 2.1... underclocked it to 480. My kaiser usually runs at 550. (official rom, its possible to have custom roms running at the original 600.) and it still is a great phone... look at the simple specs :
http://www.gsmarena.com/gigabyte_gsmart_g1305_boston-3201.php
Now, someone explain... why can't our Kaiser/Vogue/Polaris run Android like that leatle freak underclocked to 480 runs. Please.

The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App

thoughtlesskyle said:
The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Do not feel ofended. It was not my intention.
My point is that if we had accepted the slowness of our devices, we would never had attempted to port Android.
As for the RAM, agree.. it is a bottleneck...
Now, has for speed... i've seen them run well... on other devices of course.

I did many tests on my Kais130 Fresh Froyo, about livewallpapers
I agree with Daedric on the ability of our device.
I managed to run the "Grass" Wallpaper properly. Others, like Mario, Galactic Core, ... Sometimes with bugs and/or too many resources used.
It seems to me that LiveWallpapers work less well in the latest Froyo

Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.

aceoyame said:
Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.
Click to expand...
Click to collapse
Should we assume... that at the same speed, diferent MSM devices offer diferent performance ? Or, are we simply doing still things wrong, i don't know, perhaps a poor schedule, buggy drivers which introduce lag, perhaps the graphic one.
We must remember, they kick our kaiser hard, but they have much more pixels, how can that be ?

Leedroid but what kernel

Hi all,
I've got Leedroid and would like to know how the hell people get the 3000+ scores on quadrant ?
I've used most of the roms with a lot of the kernels but the most i get is around 2500 - 2600 , i've heard that the kernel by Kamma is a good one but i'm at a loss as to which one i should use.
So if anyone could point out which one i could use for .
1. Stability.
2. Battery saving.
3. Benchmarking (without smoking my device of course)
Any answers would be appreciated.
Thanks.

dladz said:
Hi all,
I've got Leedroid and would like to know how the hell people get the 3000+ scores on quadrant ?
I've used most of the roms with a lot of the kernels but the most i get is around 2500 - 2600 , i've heard that the kernel by Kamma is a good one but i'm at a loss as to which one i should use.
So if anyone could point out which one i could use for .
1. Stability.
2. Battery saving.
3. Benchmarking (without smoking my device of course)
Any answers would be appreciated.
Thanks.
Click to expand...
Click to collapse
the first thing you need to understand is quadrant is ****, it is not an acurate indication of the speed of your device, a few devs have made kernels that trick quadrant into giving it massive scores, but in reality there kernels are not the best that being said, you wont find a better kernel for stability or speed than leedroids one, it is flawless you can download it here
http://www.multiupload.com/U2ECLTRT7V

AndroHero said:
that being said, you wont find a better kernel for stability or speed than leedroids one, it is flawless you can download it here
Click to expand...
Click to collapse
Have you noticed much difference between 2.0.5 and 2.0.6 kernels? The LeeDroid thread is getting very lengthy to read through these days to catch up on new updates lol!

RobSimmo said:
Have you noticed much difference between 2.0.5 and 2.0.6 kernels? The LeeDroid thread is getting very lengthy to read through these days to catch up on new updates lol!
Click to expand...
Click to collapse
Yeah the new one is based on the latest kernel source, with the 1.75 libs,
Sent from my Desire HD using Tapatalk

Tbh I use leedroids newest one an its really good, quadrant gets 2500 +
The device is smooth as silk, bit then again it always was.
I didn't know that quadrant was pants, I thought it was a good benchmarking tool.

Confirm that the newest kernel of Lee is the best!but in a few days he prepare a new awesome BFS kernel...

Mmm badly ****ed scheduler. My favourite.
If you want good quadrant, buy the paid app which gives higher scores than the free one. Do the I/O hack which core and lee droids use. Use Leedroid kernel at max freq, performance governor, and finally run it in airplane mode.
Follow all those steps and you will get around the 3000 score.
You should state if you use quadrant standard or advance when posting results as they do differ. Otherwise it's like comparing oranges to mandarins. They are both orange but one is always bigger.
Sent from my super slick Android device.

dr.m0x said:
Mmm badly ****ed scheduler. My favourite.
If you want good quadrant, buy the paid app which gives higher scores than the free one. Do the I/O hack which core and lee droids use. Use Leedroid kernel at max freq, performance governor, and finally run it in airplane mode.
Follow all those steps and you will get around the 3000 score.
You should state if you use quadrant standard or advance when posting results as they do differ. Otherwise it's like comparing oranges to mandarins. They are both orange but one is always bigger.
Sent from my super slick Android device.
Click to expand...
Click to collapse
Yea it's just the standard version of quadrant, I thought that it would do the job.
Also i don't want to trick it or actually buy an app just so it can give me higher scores, that's not actually helping at all, i'll try the airplane mode to see if that helps, my phone is rapid anyway so it's only for my own satisfaction and to see how high i could get the score to go to.

Defy+ = high frequency roundkicks or just serious OC

Hi,
Im trying to get a bit of rock ´n roll out of my Defy+ thru serious overclocking,
im running MS2Ginger 3.0 at the moment that doesnt seem to be the perfect rom for getting great speeds, but it works.
Been running 1350Mhz for a while which seems to work rather good, going to 1400 makes my Defy more sluggish than a led slug. So that doesnt work, atleast not for what i can see.
The problem i see is when running Quadrant benchmarks, i only get numbers around 300 on the 2D test, is that normal?
Can someone tell me about a rom that could make me roll even faster and higher up in the result lists of Quadrant benchmark?
Regards.

So 214 views and nobody knows anything? Sounds impoosible on this forum

Don't know much about fast ROMs but everybody brags about CM7, of course. Also there are some people who claim Mokee os (CM7 Based) is the fastest. Check them out and let us know what you find out
Anyway, they say Quadrant isn't everything.
Sent from my Defy+ using xda premium (app needs update!)

fiskenigaten said:
Anyway, they say Quadrant isn't everything.
Sent from my Defy+ using xda premium (app needs update!)
Click to expand...
Click to collapse
exactly...
if you want fast delete all apps except for system ones...
& lob it off a tall building ^^ :chortle:

fiskenigaten said:
Don't know much about fast ROMs but everybody brags about CM7, of course. Also there are some people who claim Mokee os (CM7 Based) is the fastest. Check them out and let us know what you find out
Anyway, they say Quadrant isn't everything.
Sent from my Defy+ using xda premium (app needs update!)
Click to expand...
Click to collapse
Ok thanks for the advice, i'll check them out and post some kind of measurments
King_Rat said:
exactly...
if you want fast delete all apps except for system ones...
& lob it off a tall building ^^ :chortle:
Click to expand...
Click to collapse
Ok they say the Defy is a rugged phone but hell knows if that would be healthy for it. But as they say it aint the speed that kills its suddenly coming to a stop that kills so maybe i should go for a try

I recommend setting max and min to 1350 and also performance governor, on v6 supercharger before benching run an enginge flush and kill all apps using process manager except quadrant
DEFYing the Android planet with ICS

Ok i´ll try that V6 thingie but before that i thought i would tell what i have noticed so far.
MS2Ginger stayed around 1900 score on Quadrant with a top of 2100.
CyanogenMod seems to stay around 2400 with a peak of 2501 so far.
CyanogenMod seems to be better on the hardware tests except on the graphical parts where it seems to drop a couple of FPS, Anyone know any good
advice to maximize the graphical parts of CM?
A fun thing to notice is that with the original settings and MS2Ginger i achieved a score of 1350 and now riding around 2500, pretty nice.
One down thou with CM is that i woke up this morning without a statusbar and when the alarm went off i couldnt shut it off except for rebooting the phone.

mihovil13 said:
I recommend setting max and min to 1350 and also performance governor, on v6 supercharger before benching run an enginge flush and kill all apps using process manager except quadrant
DEFYing the Android planet with ICS
Click to expand...
Click to collapse
Ok now im un-supercharged again, either i did something very wrong or that script only worked in the wrong direction on my Defy+. Installed it and ended up running 1700 - 1800 scores on Quadrant, uninstalled it and is now back to 2300, dont know where the last 100 - 200 points ended up, will do some more tests before moving on to the Mokee OS rom.
Have a safe day/evening

I jujst wanted to say that im in no way is trying to put down the MS2Ginger developers work, this is just me and personal opinions in the hunt for a better performing Defy+
Cheers

in my opinion, oc-ing the defy to over 1.2ghz makes no sense and it only damages your cpu in the long run. i think that managing your ram gives a lot smoother experience than oc-ing your phone, because the only apps that dont run smooth on this little beauty are hd games, but they were never intended to. im using ram manager pro from market (play store), try it, maybe it helps!
sent from my cm7 defy...