Related
I downloaded the visualizer app (the one with the 2 dots and not the square)
and yea if I begin on the left side of the screen then touch the right and move around the points hang a bit when they cross and will hardly ever switch (unless u do complex rotating action with both points but then the switch is periodic at best)
but if I begin on the right side of the screen, the points ALWAYS switch...always...
Interesting...does that mean it's a software issue?
I already KNOW this is the wrong section but I feel this is something that could benefit from the most viewed sub forum.
edit: starting from the right side, the points fix themselves when I do the same complex rotating action that sometimes causes point switch starting from the left. I'd record it if I had a camera, but yea.
none of the 163 (at the time of this posting) viewers have anything to say?
not even a "WRONG SECTION NOOB" (Despite my non noobishness) post?
sheesh.
wrong section, noob.
wrong section noob.
hahahhaha LOVE IT.
another interesting update: The previous results were on a Cyanogen Mod...
Using Modaco Desire Alpha 14 I get the EXACT opposite results...
Starting with a finger on the left side of the screen then the right side point switch is guaranteed...whereas starting with a finger on the right then the left point switch is non-existent.
I think it is entirely a software fault...anyone who knows anything have anything to say about it?
then again, the overall finicky-ness of it is probably just a flaw period...though I think it can be fixed with a software update due to the different behavior between ROMs.
seems to switch points at random actually...on the desire ROM especially.
still wrong section noob. haha.
It has been covered by pretty much all tech blogs on the 'net already.
Some think it is a hardware bug, and others think it's software. Who knows.
I don't think it will matter for most people, although I consider it a serious flaw if it is not possible to fix it with software.
And yeah, this might be the wrong section, but it could also turn into a dev issue. "wrong section, noob" was funny the first time.
yea that's why I put it here in the first place, I shoulda added [Think Tank] and then squeezed my statements there...def belongs in General though...any Mod please move there without any Snarky comments prior.
i 'll move it but with snarky comment : use edit button when you want to replay to yourself instead of creating two posts
I just tried that Multitouch Visible Test, and it does not always switch the dots. It is a little bit strange though, because it seems like the dots are just put on the wrong intersect of the red and blue lines. If it is a hardware malfunction it is a very weird one. Some kind of random mirror function.
Maybe its a problem with the app itself and nothing with phones.... comon now, I don't have a problem with multitouch and I think that app is horrible to determine a bad phone..
No offence people, but these issues everyone brings up on this phone isn't a issue at all... the 3g issue is network not phone, the wonky screen is from the wrap around effect, the multitouch issue is retarded.....
The only valid one imo is the dust...... everything else seems irrelevant
temperbad said:
Maybe its a problem with the app itself and nothing with phones.... comon now, I don't have a problem with multitouch and I think that app is horrible to determine a bad phone..
No offence people, but these issues everyone brings up on this phone isn't a issue at all... the 3g issue is network not phone, the wonky screen is from the wrap around effect, the multitouch issue is retarded.....
The only valid one imo is the dust...... everything else seems irrelevant
Click to expand...
Click to collapse
The multitouch issue is not app based, otherwise it'd be present on the Droid as well (where it isn't, infact Droid's multitouch is damn near flawless looking at that video and having owned one) Though it's not going to be an issue for anything I and many others current use the phone for (Browsing, Maps, Gallery, anything else that uses pinch to zoom) it will become an issue and may already be for multitouch games...From what I saw it seemed like it is likely software based due to the fact that on the Cyan ROM one thing happened in one order and on the Desire ROM same thing happened (and a bit more buggy) in another order.
But yea, about the 3G issue..I never had that either...in fact my 3G with my N1 is better than the 3G i had with my G1.
AbsoluteDesignz said:
The multitouch issue is not app based, otherwise it'd be present on the Droid as well (where it isn't, infact Droid's multitouch is damn near flawless looking at that video and having owned one) Though it's not going to be an issue for anything I and many others current use the phone for (Browsing, Maps, Gallery, anything else that uses pinch to zoom) it will become an issue and may already be for multitouch games...From what I saw it seemed like it is likely software based due to the fact that on the Cyan ROM one thing happened in one order and on the Desire ROM same thing happened (and a bit more buggy) in another order.
But yea, about the 3G issue..I never had that either...in fact my 3G with my N1 is better than the 3G i had with my G1.
Click to expand...
Click to collapse
It may be just that There is different hardware/software in one vs the other.....
I still don't believe it will be a issue, I mean that app your sliding both fingers at the same time, and it only happens some of the time..... I don't believe there will be many games where your performing that kind of action, and even if so it don't happent all the time and may act completely differently in a game than it does in the app..... I mean, if it was a big deal we would notice it in the other pinch to zoom apps, I've tried on pinch to zoom to get it to do anything weird and it don't..... just saying, I don't think this video/app proves much....
Then again, who the hell am I.. lol I don't know shat like anyone....
temperbad said:
It may be just that There is different hardware/software in one vs the other.....
I still don't believe it will be a issue, I mean that app your sliding both fingers at the same time, and it only happens some of the time..... I don't believe there will be many games where your performing that kind of action, and even if so it don't happent all the time and may act completely differently in a game than it does in the app..... I mean, if it was a big deal we would notice it in the other pinch to zoom apps, I've tried on pinch to zoom to get it to do anything weird and it don't..... just saying, I don't think this video/app proves much....
Then again, who the hell am I.. lol I don't know shat like anyone....
Click to expand...
Click to collapse
In fact, N1 has only pinch and zoom multitouch whereas droid has native multitouch...
temperbad there are a lot multitouch app in the market which state that Nexus One is not supported due to its multitouch misfunction..
ping pong multitouch is one of these applications..
Propably it is a hardware issue.
temperbad said:
Maybe its a problem with the app itself and nothing with phones.... comon now, I don't have a problem with multitouch and I think that app is horrible to determine a bad phone..
No offence people, but these issues everyone brings up on this phone isn't a issue at all... the 3g issue is network not phone, the wonky screen is from the wrap around effect, the multitouch issue is retarded.....
The only valid one imo is the dust...... everything else seems irrelevant
Click to expand...
Click to collapse
Try it in the browser. Pinch zoom out, then rotate your fingers in a circle and continue pinch zooming out. Instead of zooming out, it zooms in.
jerhoyet said:
Try it in the browser. Pinch zoom out, then rotate your fingers in a circle and continue pinch zooming out. Instead of zooming out, it zooms in.
Click to expand...
Click to collapse
I have. No issues
temperbad said:
I have. No issues
Click to expand...
Click to collapse
It's not all the time, but it happens. It's caused my axis flipping.
maedox said:
It has been covered by pretty much all tech blogs on the 'net already.
Some think it is a hardware bug, and others think it's software. Who knows.
I don't think it will matter for most people, although I consider it a serious flaw if it is not possible to fix it with software.
And yeah, this might be the wrong section, but it could also turn into a dev issue. "wrong section, noob" was funny the first time.
Click to expand...
Click to collapse
Its supposed to a software bug.. The same thing produces two different results with two different ROMs....so its not a hardware issue....
AbsoluteDesignz said:
another interesting update: The previous results were on a Cyanogen Mod...
Using Modaco Desire Alpha 14 I get the EXACT opposite results...
Starting with a finger on the left side of the screen then the right side point switch is guaranteed...whereas starting with a finger on the right then the left point switch is non-existent.
I think it is entirely a software fault...anyone who knows anything have anything to say about it?
Click to expand...
Click to collapse
temperbad said:
I have. No issues
Click to expand...
Click to collapse
I too have absolutely 0 issues with pinch to zoom and rotating, getting my fingers really close together, etc. 0 issues whatsoever.
I'm on the Desire rom though.
Anyway, you have to remember this has absolutely NO importance whatsoever unless you play a lot of games.
If you don't, like me (I have a 360, so I couldn't care less), you'll never really have an issue with this.
Hi,
My Desire HD updated itself to Android 2.3.3 a few days ago and now it plays video at a terrible quality, with all kinds of mpeg artifacts. Both the stock video player and Vplayer do it. I haven't seen this issue mentioned in any of the threads about the update on this forum.
Has anyone else noticed this? Is there anything I can do about it?
Thanks in advance...
I dont think theres much you can do about it with the stock ROM apart from a factory reset.
Other than that I would highly recommend rooting and installing a custom ROM. I just did it a few days ago and I'm the last person that would tinker about with expensive electronics. Very easy to do and very safe as long as you know what you are doing. I made myself a guide combining many other guides on XDA which I can post for you if you want.
Robrecht said:
Has anyone else noticed this? Is there anything I can do about it?
.
Click to expand...
Click to collapse
Nope, i haven't noticed it.
Since the Gingerbread update my DHD has been playing videos better than it ever did on froyo.
Only thing i can suggest is a factory reset, or clear the data for the programs you're running the videos with.
Robrecht said:
Hi,
My Desire HD updated itself to Android 2.3.3 a few days ago and now it plays video at a terrible quality, with all kinds of mpeg artifacts. Both the stock video player and Vplayer do it. I haven't seen this issue mentioned in any of the threads about the update on this forum.
Has anyone else noticed this? Is there anything I can do about it?
Thanks in advance...
Click to expand...
Click to collapse
there is no problem in mine,
do factory reset
When did yours update? Was it an Orange update, or have you rooted or something else?
Thanks everyone for your helpful replies. Fortunately, the issue seems to have disappeared.
It's weird because it happened persistently with both the stock video player and a 3rd party one (vplayer), with videos that showed perfectly before, and soft resetting initially didn't help, and it was really bad -- about the worst mpeg artifacts I've ever seen!
So I guess all's well that ends well, although I'm still slightly baffled.
For the record, I'm on the Dutch stock HTC ROM, unrooted.
@raze559: If this issue hadn't resolved itself I might have considered a custom ROM. I'll probably try one some day, but it's hard to find good and simple info among all the different options. Especially since I'm a bit late to the Android party after years with Windows Mobile. So yeah, your guide sounds like it could be very useful for a lot of people.
enough is enough
its starting to get really annoying seeing people constantly asking
about when the gfx glitches will be fixed ,even though 2 or 3 posts
above theres someone has already said when they will be fixed
i can probably count 30 or more posts in differnt threads in the last 12
hours asking that same question
so here it is in a nut shell and read it really slow
the gfx glitches on GB Sense roms will be fixed when HTC releases the Kernel Source Code, untill that happens we will have those small glitches
so please out of common courtesy for the Devs of the sense roms
stop asking when the gfx glitches will be fixed every other post
Unfortunately I say let trolls roll. I just ignore moronic posts that have been asked before whenever I search the forums anyways
Sent from my HTC HD2 using XDA App
Kameirus said:
the gfx glitches on sense roms will be fixed when the source code
is released, untill that happens we will have those small glitches
Click to expand...
Click to collapse
When you say "source code," do you mean the HTC Sense source code or the source code of the custom ROMs from which Sense was ported? Either way, it seems likely that it'll be a while before either will be released
EDIT: You edited it with more description. Thanks!
When the gfx glitches will be fixed?
it's bug not in videos drivers in the kernel, it's bug gralloc library
Does anyone know if these same issues are effecting any other phones?
Sent from my HD2 using XDA App
Thanks for the information. Now i can stop asking when the gfx glitches will be fixed
Greetz
Belp
What do the glitches actually look like? I have a Sense rom installed but a Froyo. So, not sure what they look like. Can you post a screen shot or direct me to a post that shows?
I rarely notice the glitches on the Sense 3 ROM I'm using. But I figure when a Sense 3 ROM is released that is closer to the HD2 in hardware specs...like HTC releasing a Sense 3 ROM for the Inspire 4G/DesireHD, the glitches and bugs will continue to be an issue. Although they are a monor issue in my current ROM.
Egrier said:
What do the glitches actually look like? I have a Sense rom installed but a Froyo. So, not sure what they look like. Can you post a screen shot or direct me to a post that shows?
Click to expand...
Click to collapse
They are in GB sense not froyo, If you want to see what they look like flash a GB rom.
Egrier said:
What do the glitches actually look like? I have a Sense rom installed but a Froyo. So, not sure what they look like. Can you post a screen shot or direct me to a post that shows?
Click to expand...
Click to collapse
I also didn't know what glitches where, but....
Yesterday I tried the Pyramid port from dungphp and there they where, the nasty little buggers!
As I don't have a screen-shot from any glitches I'll try to describe it for you.
Here we go...
They seem to appear when there's graphical activity (i think).
Like for instance in scrolling text (like in the app Quick System Info) and in the text under the scene (loading preview) in the scene picker in Sense 2.1 and 3.
So the glitches are mostly seen around and through text.
It's no more than little white lines completely running through your white text, making it hard(er) to read.
It's there, sometimes annoying, sometimes not.
For me it was one of the reasons not to stay on the Pyramid port or use any other GB Sense rom.
Luckily we have many roms to choose from here
Here you go mate, hope this clarifies it somewhat.
Thanks for the explanation. That helps out alot. I think I will just stay with Froyo. It's been working great for me so far.
Egrier said:
Thanks for the explanation. That helps out alot. I think I will just stay with Froyo. It's been working great for me so far.
Click to expand...
Click to collapse
which froyo build are you using?
By the way, I'm not sure if you are aware of this or not but there is a flashable fix for the Graphics, However it will kill your camera .
Link to fix.
kawazaki said:
By the way, I'm not sure if you are aware of this or not but there is a flashable fix for the Graphics, However it will kill your camera .
Link to fix.
Click to expand...
Click to collapse
and messes up your dialer
boysha8 said:
which froyo build are you using?
Click to expand...
Click to collapse
I've been running the MAGLDR version of Frankinstine DROID HD v1.2. It has sense and works pretty good.
So I tend to answer more questions that I ask on here, but now it's my turn!!
So, I've noticed at times that my KF is totally unresponsive from sleep. No power light, nothing. I have to press the power button for 20 seconds, then again to power on. This used to happen every so often on the Stock ROM.
However, since I've been on CM7 w/ TWRP/FFF, it hangs up every single day. At first I thought it was due to low charge, but it's doing it whilst the battery is over 90% full. I've had a nose around the CM7 settings and tweaks, but can't see anything obvious.
Running services at startup are:
Settings (presumably because I'm looking at settings to see this info!)
Google Services
Amazon Video (Not sure why this is running. I may uninstall to see if this is the problem) - Uninstalled. Will see how it goes.
DSPManager
Swype
Anybody else seen this? Anybody else got any ideas on how to resolve this?
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
I've not experienced this problem. My kindle fire has been pretty much perfect and I've never had to force a reboot. I'm also using the Sywpe keyboard.
asb2164 said:
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
sl0ttedpig said:
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
Click to expand...
Click to collapse
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
asb2164 said:
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Wow, seriously?!
I *did* read about it, and concluded that it was a memory management app. Given my symptoms, I cannot find one example of where this app would help me, and I'm not about to install something that is possibly just going to add further variables to an already odd behavior.
Show me where you think it's going to help (specific examples), and I'll gladly accept your thanks/suggestions.
Until then, I would ask you keep your snark for sites like Slashdot.
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
asb2164 said:
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Again, Wow Seriously?!
Your definition of me not reading is based on me calling it an app over a script!? Interesting logic there.
However, I'm still wondering how you deduce that this is going to help my problem, and hence why I asked for specifics. I'm quite capable of finding information, but it's like you saying to me "Dude, install Angry Birds, it will solve all your problems". My conclusion was that there was nothing in that post that specifies "This will also help your system if it sleeps permanently" (clearly I'm paraphrasing there, just in case that wasn't clear). If I'm missing something, I'm all ears, but blindly recommending apps for no reason is no help to anyone.
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
asb2164 said:
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
Click to expand...
Click to collapse
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
asb2164 said:
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
Click to expand...
Click to collapse
I guess it's entirely possible. I'll do a Titanium Backup now, re-flash, and see what happens. But as mentioned in my OP, I had this happen on stock 6.2, just not as frequently, so I'll be hoping that it is a bad flash, and not something inherently worse.
See how much better this conversation is now!
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Your problem is a bit unique so I don't mind throwing out a few ideas.
Mine is solid as a rock I am ready for a good overclocking kernel so I can stretch it's legs
Sent from my Kindle Fire using Tapatalk
altitude909 said:
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Click to expand...
Click to collapse
Yep, I always clear everything when moving to a new ROM. It's a habit that was drilled into me during my first custom ROM exploits on my Droid. I've even told people on here to do it too, so I'm practicing what I'm preaching!
I think what I'm going to do is, reflash to stock 6.2.1, use the new root method, push TWRP/FFF again, and then CM7. A little drastic, but I think that having a clean run at this might prove/disprove the theory.
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
krelvinaz said:
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
Click to expand...
Click to collapse
Yeah, this is happening a little too frequently for my liking. Occasionally is fairly OK, every day is not. But it has got worse since going to CM7, but that could be purely coincidence at this point.
Trying some different things right now, but it will be a few days before I know for certain.
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
butterflygirl said:
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
Click to expand...
Click to collapse
Thanks, that hadn't crossed my mind, but I like my brightness at a pretty high level, and as the sensor is not working currently, it pretty much stays at that level.
Back at stock 6.2.1 now. Going to root it and leave it like this for a few days to see what happens.
sl0ttedpig said:
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
Click to expand...
Click to collapse
Not sure if you have resloved this issue, but having read most of the Forum Dev Thread for the CM7 initial release and the newest reboot of the first ROM I think many others are having this issue as well. I remember reading many post people were referring to something similar to your problem as "the sleep of death." I however am not having that problem with mine, but thought it might be helpful to know that it might not be your device specific and may be something with CM7 itself with some devices.
So I am not usually the guy to post new threads. Most everything I need I can find already. But after I was video recording my son at the park today and missed yet another video due to FC issues I guess it's time to finally ask. I have had my HD2 running some android rom or another for almost 2 years. I presently have CM7 Tytung v 3.8.5-MAGLDR. The reason I am asking this here and not in that thread is because it has always been an issue regardless of the ROM I am running at the time. The video recorder force closes. It's that simple. It works intermittently and then it will inevitably force close and can not be re-opened. The only fix is to reboot the phone. I have tried about every camera/video app in the Play store. I have flashed different cameras. My wife also has an HD2 Tmobile the exact phone as me and has the exact same issue as me. The video recorder force closes. I have to wonder if I am just missing something simple? Is there an app or something to flash differently? I recently had WP7 on my HD2 and the camera was AWESOME ! WP7 just doesn't do what Droid does.I am open to suggestions. Is this a known issue I am just forced to deal with on my HD2? How can I make my Iphone buddies stop laughing at my force closing Android HD2?
jcnbama said:
So I am not usually the guy to post new threads. Most everything I need I can find already. But after I was video recording my son at the park today and missed yet another video due to FC issues I guess it's time to finally ask. I have had my HD2 running some android rom or another for almost 2 years. I presently have CM7 Tytung v 3.8.5-MAGLDR. The reason I am asking this here and not in that thread is because it has always been an issue regardless of the ROM I am running at the time. The video recorder force closes. It's that simple. It works intermittently and then it will inevitably force close and can not be re-opened. The only fix is to reboot the phone. I have tried about every camera/video app in the Play store. I have flashed different cameras. My wife also has an HD2 Tmobile the exact phone as me and has the exact same issue as me. The video recorder force closes. I have to wonder if I am just missing something simple? Is there an app or something to flash differently? I recently had WP7 on my HD2 and the camera was AWESOME ! WP7 just doesn't do what Droid does.I am open to suggestions. Is this a known issue I am just forced to deal with on my HD2? How can I make my Iphone buddies stop laughing at my force closing Android HD2?
Click to expand...
Click to collapse
Youre not alone, same thing happens to me :/ no matter the ROM, i remember reading a thread about it but what i read didnt really help. It said something about not using the fix because most newer ROMs have the fix installed. So i didnt bother downloading it and cant find the thread anymore. Im gonna go look fo rit. hope others can help us both!
I found this earlier today here on the XDA site "props to whomever it came from " I just did a random search and found it. I was using my phone so I'm not sure the page exactly. Never the less I unistalled the stock camera via Titanium Backup and flashed this through CM Recovery. It has a video feature and a decent camera interface. So far no lock ups. Only this afternoon though. Time will tell. I've been running test to try and fool it. Using lots of memory, taking multiple shots switching back and forth, rebooting etc. So far its worked. Try it out, lemme know if it works.
Well, I had been using a CM7 Nightly neared build with a few mods that jar never failed me with camera and camcorder- it was so dependable that I have it on my old, some-hard-keys-dont-work HD2 because am using ICS primarily nowadays.
I'll post what changes I make later, and can post the ROM itself here if anyone wants to try...
Swyped from my HTC HD2 using XDA App
hai bro........dont worry i use nand typhoon nightly rom latest.......
use free lg camera ...search in market download free version of lg camera
seetings for lg camera:
video:
encoder:mpeg4
resolution:640*480
bitrate:6mbits
frame rate:auto(it records in 22frames)
audio:
encoder:acc
bitrate:128mbit(stereo)
no lag for me very clear..................(you can record in 800*480 with 4mbits stable)
i personally recommand to increse saturation value to 10 in settings for good natural quality....
vigneshjack3 said:
hai bro........dont worry i use nand typhoon nightly rom latest.......
use free lg camera ...search in market download free version of lg camera
seetings for lg camera:
video:
encoder:mpeg4
resolution:640*480
bitrate:6mbits
frame rate:auto(it records in 22frames)
audio:
encoder:acc
bitrate:128mbit(stereo)
no lag for me very clear..................(you can record in 800*480 with 4mbits stable)
i personally recommand to increse saturation value to 10 in settings for good natural quality....
Click to expand...
Click to collapse
<OT> Whoa bro! Go eay on smilies and ......... - it makes your post pretty hard to read, especially on the XDA app!</OT>
*Update* So after almost two years of agony I may have finally found a fix. The .zip file I posted earlier has worked so far. I fooled around with it all day yesterday and last night as well as this morning. I tried everything I know to make it crash from running multiple apps, opening a camera during a call, playing music then opening the camera etc. Rebooted a couple of times. Still not crash. I'll keep posting here with status updates. I found this yesterday on the XDA site. I just did a Google search. I am not sure who originaly posted this .zip file. If it continues to work I will give them a hug