49 replies to this topic

[sawta]

targetbsp, on Feb 9 2011, 21:42, said:

But your approach to dealing with a group of people who believe the moon is made of cheese is to simply walk up to them and say 'you're all wrong - prove its made of cheese'?  When going against popular opinion - surely you have to be the one providing an argument?  If you think it speeds up decoding h.264 then provide some benchmark figures to back that up.  Obviously not from Quadrant as its issue with stagefright is well known but is there a media player out there that can show frame rates maybe?

Personally, I neither care about benchmark scores nor video playback so it doesn't much affect me. My last rom had it disabled by default, my current one has it enabled by default.  I didn't, and don't plan to, change either.

Erm actually no stagefright working for h264  in a correctly configured ROM is not opinion, its fact just as 1+ 1  = 2 is fact. the popular opinion here appears to be the equivalent of 1 + 1 = monkey.

Stagefright having occasional issues with AAC and eACC quality from streamed media is also fact, but non relevant to any of the discussion here.

I dont believe it speeds up h264 decoding ,the fact is that stagefright makes it more flexible for a given HW configuration (check the google docs: fact).

You try to help people who are shooting themselves in the foot to point the gun away and they point it at you instead. No wonder funkimunk doesnt want his ROM on this place.

[sawta]

PeteBest, on Feb 9 2011, 21:50, said:

Doesn't look like trolling to me, if the people that had fully checked into stagefright already gave sufficient technical details then sawta wouldn't have gone with the "prove it" type response.

Thank you PeteBest, at least someone here has sense.

[flibblesan]

PeteBest, on Feb 9 2011, 21:50, said:

Doesn't look like trolling to me, if the people that had fully checked into stagefright already gave sufficient technical details then sawta wouldn't have gone with the "prove it" type response.

Saying "prove it" does nothing to help the issue and just winds people up. If anybody wants stagefright enabled then a 2 second build.prop edit will sort it out. It was disabled for a reason in the original roms.

Anyway there is way too much arguing here over a feature that can be simply enabled by the user if they want to.

sawta: Since you seem to know a lot about this, could you possibly provide a solution to this. You mention a correctly configured rom resolves the problem, how?

[targetbsp]

sawta, on Feb 9 2011, 21:52, said:

I dont believe it speeds up h264 decoding ,the fact is that stagefright makes it more flexible for a given HW configuration (check the google docs: fact).

OK, but the only advantage you gave for stagefright in your first post was that you thought it did speed up h246? I was only responding to that:)  What specific advantages does it give you otherwise?  Cause I linked some disadvantages in my post that you may have missed as you replied before I had completed the edit.
I know it fixes some gameloft game intro's but should you not have any of their games, are there any advantages for the average person enabling it to counter the bugs it has?

Edited by targetbsp, 09 February 2011 - 10:12 PM.

[sawta]

flibblesan, on Feb 9 2011, 22:03, said:

sawta: Since you seem to know a lot about this, could you possibly provide a solution to this. You mention a correctly configured rom resolves the problem, how?

Ill ask Funkimunk what he did when I see him in the computer lab next week (possibly tomorrow if im in early enough)  but I must warn he really doesn't like this place (something to do with "disingenuous donation scams" and "instantly getting your work published to some SEO savvy tw*ts 3rd party page") I think he doesn't even like putting stuff on XDA ('to get ripped off by credit grabbing......').

[flibblesan]

sawta, on Feb 9 2011, 22:11, said:

Ill ask Funkimunk what he did when I see him in the computer lab next week (possibly tomorrow if im in early enough)  but I must warn he really doesn't like this place (something to do with "disingenuous donation scams" and "instantly getting your work published to some SEO savvy tw*ts 3rd party page") I think he doesn't even like putting stuff on XDA ('to get ripped off by credit grabbing......').

OK in that case where does Funkimunk publish his rom?

[sawta]

flibblesan, on Feb 9 2011, 22:13, said:

OK in that case where does Funkimunk publish his rom?

He gave it to me in person after seeing my phone in the lab (hes helped me with semantic web lab classes in the past, a class tutor guy).
Ill ask him can I post it here, this is why I wanted you guys to look over your roms... ill bet he tells me to f off.

Edited by sawta, 09 February 2011 - 10:24 PM.

[voradorpt]

sawta, on Feb 9 2011, 22:23, said:

He gave it to me in person after seeing my phone in the lab (hes helped me with semantic web lab classes in the past, a class tutor guy).
Ill ask him can I post it here, this is why I wanted you guys to look over your roms... ill bet he tells me to f off.

Conveniently.

Also, I'm still waiting for you to prove it works.

[sawta]

voradorpt, on Feb 10 2011, 00:11, said:

Also, I'm still waiting for you to prove it works.

EH what?
I shouldnt have to prove that its working as im NOT THE EXCEPTION TO THE ANDROID 2.2 WORLD!
Prove that stagefright is broken , prove that its not a misconfiguration in these ROMs that the rest of the world does not incorporate in their 2.2 roms (you cant because it is a misconfiguration).

I am so sick of having to explain to brain dead people that hacky misconfigured ROM mod projects are the issue notSTAGEFRIGHT!

I repeat this h264 bug was never an issue and was not fixed in Android 2.2.1+ merely those unofficial 2.2.1 roms that noticed a fix configured their ROM correctly , Google even state something along these lines in their mailing list.

I was accused of trolling for asking for proof that stagefright was broken and not that the ROMS are misconfigured, clearly the trolls in this thread are going to deflect any chance of finding out this information ("disable it because I don't know how to fix it" syndrome).

Damn I give up, use the outdated media framework with limited support and reduced flexibility if you want i'm away to watch HQ Youtube over wifi and then seamlessly play some gameloft games before I go to sleep.

Edited by sawta, 10 February 2011 - 02:22 AM.

[IronDoc]

Surely this is just a (pointless) argument about semantics. It means exactly the same thing to say 'stagefright does not work correctly with our ROMs' as it does to say 'the ROMs do not work correctly with stagefright'.

[Rotmann]

sawta, on Feb 9 2011, 22:52, said:

Erm actually no stagefright working for h264  in a correctly configured ROM is not opinion, its fact just as 1+ 1  = 2 is fact. the popular opinion here appears to be the equivalent of 1 + 1 = monkey.

Stagefright having occasional issues with AAC and eACC quality from streamed media is also fact, but non relevant to any of the discussion here.

I dont believe it speeds up h264 decoding ,the fact is that stagefright makes it more flexible for a given HW configuration (check the google docs: fact).

You try to help people who are shooting themselves in the foot to point the gun away and they point it at you instead. No wonder funkimunk doesnt want his ROM on this place.

Dude, your problem is the harsh attitude, are you frustrated or something? Chill down. You just insulted a whole community. If you don't want to be a flaming troll stop throwing with mud all over and bring something constructive. The discussion is good but acting crazy is not even funny. Btw. I have stagefright enabled for the gameloft games, it sure is something with it.

[sawta]

IronDoc, on Feb 10 2011, 02:23, said:

Surely this is just a (pointless) argument about semantics. It means exactly the same thing to say 'stagefright does not work correctly with our ROMs' as it does to say 'the ROMs do not work correctly with stagefright'.

Its not pointless as both the CM6 guys  (whoever logged the issue from CM6 that Google laughed off the issue tracker) and Funkimunk eventually worked out ways to get this new 2.2 feature working correctly in their respective ROMS, if its just some fine tuning of the build prop or another ASCII conf file to get it working correctly then it may be worth repairing.

[sawta]

Rotmann, on Feb 10 2011, 02:27, said:

Dude, your problem is the harsh attitude, are you frustrated or something? Chill down. You just insulted a whole community. If you don't want to be a flaming troll stop throwing with mud all over and bring something constructive. The discussion is good but acting crazy is not even funny. Btw. I have stagefright enabled for the gameloft games, it sure is something with it.

If you look over this thread you will see my attitude getting gradually getting more inflamed by trolls, I am reacting to their attitude.

[Rotmann]

sawta, on Feb 10 2011, 03:21, said:

I am so sick of having to explain to brain dead people that hacky misconfigured ROM mod projects are the issue notSTAGEFRIGHT!

I repeat this h264 bug was never an issue and was not fixed in Android 2.2.1+ merely those unofficial 2.2.1 roms that noticed a fix configured their ROM correctly , Google even state something along these lines in their mailing list.

sawta, on Feb 9 2011, 22:52, said:

Erm actually no stagefright working for h264  in a correctly configured ROM is not opinion, its fact just as 1+ 1  = 2 is fact. the popular opinion here appears to be the equivalent of 1 + 1 = monkey.

You try to help people who are shooting themselves in the foot to point the gun away and they point it at you instead. No wonder funkimunk doesnt want his ROM on this place.

Dude, your problem is the harsh attitude, are you frustrated or something? Chill down. You just insulted a whole community. If you don't want to be a flaming troll stop throwing with mud all over and bring something constructive. What are YOUR contributions to this community, as opposed to the brain dead hacky developers on this forum? Everyone behind a keyboard can pretend to have a gigantic c*ck when in fact they have a microscopic one. Show your gigantic contributions instead of trolling in a tiny microscopic manner. The discussion is good but acting crazy is not even funny. Btw. I have stagefright enabled for the gameloft games.

[IronDoc]

sawta, on Feb 10 2011, 03:31, said:

Its not pointless as both the CM6 guys  (whoever logged the issue from CM6 that Google laughed off the issue tracker) and Funkimunk eventually worked out ways to get this new 2.2 feature working correctly in their respective ROMS, if its just some fine tuning of the build prop or another ASCII conf file to get it working correctly then it may be worth repairing.

If you've got a fix then great. But if we need to build our own lib in order for it to work, then it's essentially broken. What people meant is that it was broken both in our stock ROMs (which people have then modified) and in an AOSP build for our hardware.

It's not broken in the sense that GPS was broken in some beta ROMs. Its more similar to how flash is broken (though google fixed it later whereas adobe hasn't decided to release flash for our CPU.

Correct me if i'm wrong anyone.

[sawta]

Rotmann, on Feb 10 2011, 02:35, said:

Show your gigantic contributions instead of trolling in a tiny microscopic manner. The discussion is good but acting crazy is not even funny. Btw. I have stagefright enabled for the gameloft games.

I have no giant contributions (I help any way I can e.g setting up the MoDaCo Kernel contrubition github and I believe this thread ultimately will help if people will drop their assumptions), but honestly repacking another persons ROM package as your own isn't a giant contribution either.

All I have been saying all along is that a reconfiguration by knowledgeable people is all thats needed to create a better experience for us all, this is probably a quick fix.

Edited by sawta, 10 February 2011 - 02:45 AM.

[voradorpt]

sawta, on Feb 10 2011, 02:21, said:

...
I shouldnt have to prove that its working as im NOT THE EXCEPTION TO THE ANDROID 2.2 WORLD!
...

You certainly are the exception in the ZTE Blade world, which you'll find is the sub-forum you're in.

I'm not asking for much I think. Clearly it would be simple for you to show people you got it working. Simpler than a bunch of posts of "prove it" and unverifiable claims that you have it "working".  Most people here have only claimed that it was broken on the Blade. It's verifiable. I can verify it.

So, if you or your friend really have a fix, in the spirit of Android you should publish it here or somewhere public. No need to reinvent the wheel after all.

You verify your claims, and the biggest ZTE Blade community gets to take advantage of stagefright. Everybody wins, no?

What are you waiting for?

Edited by voradorpt, 10 February 2011 - 03:46 AM.

[PeteBest]

Becoming a bit harder to defend you now sawta. Remember the no one wants to post a rom that isn't 100%, just remember that when you are fighting the general tide of opinion you have to work a bit hard. Just makes it even more satisfying when/if you're right

I'm not familiar with this Funkimunk, but I've always found this site a lot more friendly than XDA. Sure, there might be disagreements here, but as long as everyone stays respectful I can't see the problem in a spirited debate

[flibblesan]

This Funkimunk isn't eve on XDA. It's a ROM he made himself and hasn't released it anyway, so sawta says.

The whole thread could have been a lot better if he just posted that the ROMs claim stagefright is broken. I know a way to fix it properly, here it is. Done. The whole prove-it attitude is childish.

[rayraven]

I guess the OP can also tell us why most android 2.2 [not 2.2.1 or 2.2.2] based phones come with stagefright turned off out-of-the-box.

Examples? the Droid X and the Optimus One etc.
It's because stagefright is broken, and if you think it isn't, you should talk to Motorola or LG, cos they definitely use a dev like you!