Multitouch possible in theory?

[Guest BigBearMDC]

No that's all good :lol:

Cool B)

I'm looking forward to tomorrow!

[Guest JimJam707]

Cool :lol:

I'm looking forward to tomorrow!

Bobo, what time is it where you are?

It's 9:21 here in England.

[Guest BigBearMDC]

Bobo, what time is it where you are?

It's 9:21 here in England.

Its 22:23 (10:23pm) here :lol:

[Guest thisweb]

Overclock will help us, we'll just have to find the exact right clock with which the Pulse works best.

Sorry if I sound dumb, but what do you mean by clock? Is it not just a case of higher is faster? Ie 785MHZ is faster than 575Mhz ? (until the phone melts anyway !).

[Guest JimJam707]

Its 22:23 (10:23pm) here :lol:

Ah, cool. You and dan are spamming my twitter feed XD

Is this revenge for that time that we did it to you?

B)

[Guest Simon O]

Just so people know, the boot.zip I uploaded isn't a flashable zip. It contains a boot.img which is only for FLB 1.5/1.6 as a test.

[Guest BigBearMDC]

Sorry if I sound dumb, but what do you mean by clock? Is it not just a case of higher is faster? Ie 785MHZ is faster than 575Mhz ? (until the phone melts anyway !).

A higher clock brings several side effects with it. A CPU and all the surrounding circuits are built for a special clock frequency. If you alter this frequency (especially if you increase it) you'll get a higher error rate, meaning that the CPU will maybe have to calculate the same operation a few times to get the right result. In the worst case those errors my be that fatal that the machine crashes. So you'll have to find the right frequency. The error rate should be low while the clock should be as high as possible.

[Guest BigBearMDC]

Ah, cool. You and dan are spamming my twitter feed XD

Is this revenge for that time that we did it to you?

B)

Sorry :lol:

I'm mostly developing in the evening, then I have the right atmosphere. Its dark outside, raining and cold, and I'm sitting in front of my monitor, which is the only thing that lights up my room.

Got the picture?

B)

[Guest BigBearMDC]

Okay I'm out for today.

See you guys tomorrow.

Bye!

[Guest DanWilson]

Ah, cool. You and dan are spamming my twitter feed XD

Is this revenge for that time that we did it to you?

:lol:

XD

Oh yeah baby!

Just so people know, the boot.zip I uploaded isn't a flashable zip. It contains a boot.img which is only for FLB 1.5/1.6 as a test.

So no Froyo love?

Sorry bros, missed the partay, was in my cousins house...

EDIT - Don't use it on Froyo, boot loops and Network doesn't connect...

Was going to compare the Eclair and Froyo kernels (Froyo SWAP A2SD) and couldn't even open the boot.img up...

Edited September 25, 2010 by DanWilson

[Guest Epic-Emodude]

Bobo,

Any news on your kernel editing adventures?

[Guest thesinger]

Hi guys. I totally mist everything this days.I wasn't home and i didn't see anything of this. Can you tell me is the mt going well or not? An if it is how to install it?

By the way:Great work Toti,BB and Flibb

[Guest DanWilson]

Hi guys. I totally mist everything this days.I wasn't home and i didn't see anything of this. Can you tell me is the mt going well or not? An if it is how to install it?

By the way:Great work Toti,BB and Flibb

Kinda bad I think.

We need to flash the touch controller firmware to get MT working, and the kernel doesn't work on Froyo.

Dunno about Eclair though...

[Guest thesinger]

Kinda bad I think.

We need to flash the touch controller firmware to get MT working, and the kernel doesn't work on Froyo.

Dunno about Eclair though...

Thanks for the information Dan :lol: keep the nice work.

[Guest thisweb]

A higher clock brings several side effects with it. A CPU and all the surrounding circuits are built for a special clock frequency. If you alter this frequency (especially if you increase it) you'll get a higher error rate, meaning that the CPU will maybe have to calculate the same operation a few times to get the right result. In the worst case those errors my be that fatal that the machine crashes. So you'll have to find the right frequency. The error rate should be low while the clock should be as high as possible.

I see. Thanks for clearing that up. Nice work by the way!

[Guest Simon O]

It's going to take some time before a newer kernel is released guys. And the multitouch, well I know nothing about it.

[Guest DanWilson]

Anyone notice that Bobo is watching us...

Well, we can only pray Flib, we can only pray.

What is the plan for the new kernel?

[Guest Daz555]

A higher clock brings several side effects with it. A CPU and all the surrounding circuits are built for a special clock frequency. If you alter this frequency (especially if you increase it) you'll get a higher error rate, meaning that the CPU will maybe have to calculate the same operation a few times to get the right result. In the worst case those errors my be that fatal that the machine crashes. So you'll have to find the right frequency. The error rate should be low while the clock should be as high as possible.

When it comes to CPU operations the error rate should be zero. If we run a equivalent test to say something like Prime95 on the PC we should be able to run a stress test and check for errors following the overclock. I imagine there is such an app out there in Android land.

Edit: StabilityTest seems to do this.

Edited September 25, 2010 by Daz555

[Guest thisweb]

It's going to take some time before a newer kernel is released guys. And the multitouch, well I know nothing about it.

If multitouch turns out to be impossible in Froyo, may I suggest you ditch it and pool efforts to try getting a working froyo without. Was looking forward to MT but can live without it :lol: . I have to say I've been using FLB1.6b, it works just fine, but after trying FLB 2 froyo alpha I am really, really missing Froyo. Only dealbreakers for me were camera and GPS. I don't think multitouch and overclock are too important on froyo either. Its much more fluid without any mods. Having said that, if the expertise are specialised only in those areas then hell go for it!! This place is nailbiting....( am I a bit sad?) If we get 2.2 i definitely wont be bothering with the ZTE.

[Guest gusthy]

Only dealbreakers for me were camera and GPS.

Froyo supports GPS, it works fine.

[Guest DanWilson]

Froyo supports GPS, it works fine.

I think it occasionally reboots the phone. Not that I every use GPS. My dad's Desire does that for him, and I can't drive. :lol:

[Guest thisweb]

Froyo supports GPS, it works fine.

Huh! Really, it never worked for me. The symbol would come on saying connected but no apps would see it. Also when I turned it off with power widget it would stay on in notification bar. Perhaps I should try and reinstall. So just leaves camera then. I know there are a few other bugs but nothing major right?

EDIT: 'Video playback does not work in any application' ....oh yeh, I forgot about this! This really screws it.

Edited September 25, 2010 by thisweb

[Guest starkos]

When it comes to CPU operations the error rate should be zero. If we run a equivalent test to say something like Prime95 on the PC we should be able to run a stress test and check for errors following the overclock. I imagine there is such an app out there in Android land.

Edit: StabilityTest seems to do this.

SetCpu from http://forum.xda-developers.com/showthread.php?t=505419 which I use to control overclocking also has a stress test in it...

[Guest thisweb]

Meant to ask, is anyone working on the camera and video playback issue at the moment or is it a dead end?

[Guest Daz555]

SetCpu from http://forum.xda-developers.com/showthread.php?t=505419 which I use to control overclocking also has a stress test in it...

Even better cos I imagine most of us will be using that util anyway once the overclockable kernel is available.