Related
I thing that everybody wants to have a g-sensor in their mobile . I have one idea . Is there any chance to develop a driver or software that can emulate g-sensor by rear or front camera ? Camera can catch "move" maybe in the same way like a g-sensor... Please think about it ...
I believe it was at least done on the Kaiser. The only issue I can see [apart from shoddy accuracy!] is, imagine the battery life being eaten!
Still, I'd like to see it, because it's the only thing I really want on my KS20
Function can be assigned to a hardware button, so it will start only if you want and then safe your battery
Ive asked about this a couple time and really got no where. I do know that the instinct uses this feature for scrolling web pages up and down
EurEye said:
Function can be assigned to a hardware button, so it will start only if you want and then safe your battery
Click to expand...
Click to collapse
Then why not have the hardware button rotate the screen?
I see your point. I'd prefer to just have it running in the background. Drop the accuracy of it, and we could keep battery drain to a minimum perhaps.
Girvo said:
Then why not have the hardware button rotate the screen?
I see your point. I'd prefer to just have it running in the background. Drop the accuracy of it, and we could keep battery drain to a minimum perhaps.
Click to expand...
Click to collapse
that, and emulating the g-sensor would mean better games
...I didn't think of that. Good point
kidnamedAlbert said:
that, and emulating the g-sensor would mean better games
Click to expand...
Click to collapse
No it wouldn't, because as others have said the accuracy would be horrible.
mattcoz said:
No it wouldn't, because as others have said the accuracy would be horrible.
Click to expand...
Click to collapse
but im sure that the great devlopers here could probably makes work better.
it makes me feel so bad not having a g-sensor.
today my friend was playing pocketgravity and he tried making things move by tilting my phone and it made me realize i need me a g-sensor.
kidnamedAlbert said:
but im sure that the great devlopers here could probably makes work better.
it makes me feel so bad not having a g-sensor.
today my friend was playing pocketgravity and he tried making things move by tilting my phone and it made me realize i need me a g-sensor.
Click to expand...
Click to collapse
Well, doesn't the game lack that feature or does it not need that implemented?
The thing is, there has to be a comprimise.
Get some serious accuracy, but to do that you'd need to sample a hell of a lot, thus killing battery life.
Or, sample less, less accuracy [but still good enough for screen rotation I'd wager], but less drain on your battery.
kareem9nba said:
Well, doesn't the game lack that feature or does it not need that implemented?
Click to expand...
Click to collapse
nope, someone just implemented it because it sounded like a good idea.
Will never work
Cameras have been used in the past for robotics and simply didnt work since they dont understand depth very well
What about combining the Camera and letting it work with the Infrared on the device? I know not all phones support both, but for the ones that do, its a step in the right direction.
External gsensor
Lets go back to the year 2000 where everything was external. remember the external camera on the sony ericssons? lets get an external gsensor
Maybe build in the battery like the fibration in the old Nokia 5100!
This thing must be possible.
I remember the game for Nokia phones, where you were controlling the ball in the maze. It was controlled by camera but it behaves like a g-sensor.
i dont know if this has been done but when you think about it many questions come to mind. first n foremost is depth. the softwares going to sense motion by motion in pictures from the cam. now if you have a white wall sufficiently lit and you shake your phone in front of it, hows a camera gonna judge motion from it? second, imagine a dot on the wall. now if ur close to it, theres gonna be alot more "motion" for the cam than if ur far away. i dont know the technicalities of the concept and if these problems will exist in a potential implementation, but, building on problems like these, i dont think its feasible or useful.
I think the theory behind it is fairly simple (and using the camera as a game input works as in Fishopolis http://rivia.net/Fishopolis.aspx Works on the Wizard). Take a pic A from camera at time x then take pic B from camera at time x + interval y then compare the two pics (get list of positions of same objects from both pix). If the objects in pic A are to the left of the same objects in pic B then you're moving right, left otherwise and a similar calc to determine up and down.
I think it is (actually know evidenced by the game previously mentioned) very doable and should take just as much battery power as using the video camera except for the storage since only a few images would need to be kept in memory at any one time and nothing needs to be stored on "disk".
Some matrix transformations and linear algerbra should do the trick... I'm sure someone has already done this in some form or another by now... Guess I'll see what I can dig up on the old internet.
why doesnt someone just work on internal accelerometers rather then trying to use the camera?
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.
I suppose the rumors weren't true, then?
halorin said:
I suppose the rumors weren't true, then?
Click to expand...
Click to collapse
I saw someone on here posting a quote about the multi-touch fix... lemme find it
by Paul22000:
Also "A scale gesture detector API provides improved definition of multi-touch events."
I wonder if that means the N1's multitouch axes will be fixed for gaming!
halorin said:
I suppose the rumors weren't true, then?
Click to expand...
Click to collapse
since nobody has froyo yet, we dont know if it was fixed or not. i really hope they did though.
Thanks for the responses, guys. I guess in hindsight it might have been good to leave out any negative things in such a positive conference.
But still, some mention would have been comforting.
halorin said:
Thanks for the responses, guys. I guess in hindsight it might have been good to leave out any negative things in such a positive conference.
But still, some mention would have been comforting.
Click to expand...
Click to collapse
I feel the same way halorin. It's natural to voice displeasure over something important missed in an update (I would have loved 360* rotation, colored trackball, fm radio, etc) but I know your happy about the update when it does occur and a great guy to have on the forum
All progress is still progress toward perfection, no matter how small.
Thing is, they were just demoing the OS, not device specific things like the N1's trackball & whether it has working FM etc.
Very valid point, Rusty.
Yup, each device will have their own seperate updates with device exclusive things.
Rusty! said:
Thing is, they were just demoing the OS, not device specific things like the N1's trackball & whether it has working FM etc.
Click to expand...
Click to collapse
*in Kramer voice* ........ you just blew my mind...
ap3604 said:
I saw someone on here posting a quote about the multi-touch fix... lemme find it
by Paul22000:
Also "A scale gesture detector API provides improved definition of multi-touch events."
I wonder if that means the N1's multitouch axes will be fixed for gaming!
Click to expand...
Click to collapse
That quote is from the highlights web page:
http://developer.android.com/sdk/android-2.2-highlights.html
The axis problem can never be fixed 100% because the hardware doesn't report enough info to do it for all cases, but currently it is pretty bad and I think better drivers/software could get it close. I believe that Cyanogen's ROMs have had some tweaks that have greatly improved its responsiveness for some time now so perhaps the Android engineers adopted similar fixes. It will hopefully get good enough over time that you'd have to know exactly how the sensors work and deliberately try to fool the drivers in order to get it confused.
I tested a nexus one on froyo today at google i/o, some things that were absent, colored track ball, touch screen wise they didn't have any multi touch analysis program installed, but just pinching around I don't detect any notable differences, so i'm guessing no to those 2 features on nexus, at least on their current build
I was also at I/O and while I did play with a few different Nexus Ones that were loaded with FroYo, I was unable to determine if any screen fixes were applied.
I asked a few times and each time I was politely told that they could not talk about anything that was not already made public (fair enough btw).
However, pinching and zooming on maps seemed to be smoother (not sure if it just my impression or some actual change) and it seemed to respond overall to my finger movements more smoothly.
Also, some games that I demoed on a few different Nexus Ones did employ finger gestures and those games functioned flawlessly from the touch perspective.
I am not sure that translates into any real fix or just my biases, but I am putting it out here for whatever it is worth.
Dan
dan1431 said:
I was also at I/O and while I did play with a few different Nexus Ones that were loaded with FroYo...
Click to expand...
Click to collapse
Did you notice if there was 360 rotation? ie could you flip it from 12 to 3 O'Clock clockwise and get it to rotate to landscape when in a rotating app like Maps?
logger said:
Did you notice if there was 360 rotation? ie could you flip it from 12 to 3 O'Clock clockwise and get it to rotate to landscape when in a rotating app like Maps?
Click to expand...
Click to collapse
I hate to admit this, but I did not even think about testing that feature.
Dan
Dorick said:
I tested a nexus one on froyo today at google i/o, some things that were absent, colored track ball, touch screen wise they didn't have any multi touch analysis program installed, but just pinching around I don't detect any notable differences, so i'm guessing no to those 2 features on nexus, at least on their current build
Click to expand...
Click to collapse
Dorick, by any chance have you noticed wifi-n connection?
I'm almost certain from the API improvement and UI modifications listed on the Android SDK site that we have a software fix for the crazy multitouch issue.
Having said that, it means the screen won't go crazy when the paths "swap". But, it's still limited to two touchpoints and not 10 like the 3000 series screen.
A fix is a fix though. =)
Personally if the have fixed up pinch zooming somewhat and made it smoother that will cover me 99% of the way as I use the device so that will be pretty much a fix assuming we actually see it in the official N1 rom.
First the brightness issue,
Now that I actually tried to use it for a extended period, I'm finding my palm always hits the edge and moves the scrollbars
I had a tablet pc many years ago that provides a much better note taking experience
Cool Story Bro
Mine is awesome.
Sent from my GT-I9300 using Tapatalk 2
dtziheucdavis said:
I'm finding my palm always hits the edge and moves the scrollbars
Click to expand...
Click to collapse
Poor Samsung. First, everyone *****ed about the panning box they used to allow you to move through a note you're working on. Then, they changed it and replaced it with a scroll bar and people are *****ing about that too. I don't know which version of S-Note you're on but in the version included in JB with "only recognize the S-Pen" enabled it's really really hard to inadvertantly hit the scroll bars so maybe that'll solve your problem. As for the brightness being ramped up in S-Note I get the logic and it shows how much they think about how people use their devices and apps. If you think about, since the Note's a drawing device, people could be using it at any angle and in any position. Disabling auto-brightness kind of makes sense so that the screen doesn't fade in and out if someone's hand is over the ambient light sensor. Oh well, you can't please all the people all the time.
"version included in JB"
Jelly Bean? I thought the US Note 10.1 were still in ICS
dtziheucdavis said:
"version included in JB"
Jelly Bean? I thought the US Note 10.1 were still in ICS
Click to expand...
Click to collapse
Doesn't mean that you can't flash another rom...
I don't use autobrightness so it changing the levels drives me absolutely nuts. E.g. I'm working in a dark room so have the level turned down to what suits me best. I open snoteb and up it goes. I turn it back down manually, jump to another app for a moment for whatever reason, say to read some info in a pdf, switch back to snote and, bam, blinded again.
There's a reason why autobrightness can be toggled on and off, and one app ignoring that convention is infuriating.
actually if you use autobrightness, the brightness levels still change
"Disabling auto-brightness kind of makes sense so that the screen doesn't fade in and out if someone's hand is over the ambient light sensor. Oh well, you can't please all the people all the time."
If this is the case, then there are definitely better solutions than the one Samsung implemented. For example, putting a timer on the ambient light sensor so it doesn't react to accidentally being covered up. If it's only briefly covered up, the brightness won't change. If it's really in a dark room and sensing low light with no interruption for say 1 minute, then change the brightness.
So, it's hard to believe that Samsung would make SNote change the brightness autmoatically as a "feature". Samsung makes great products, but we dont have to idolize them the way that iOS Sheep idolize Apple.
dtziheucdavis said:
So, it's hard to believe that Samsung would make SNote change the brightness autmoatically as a "feature".
Click to expand...
Click to collapse
OK, since we know it wasn't done accidentally, care to take a more reasoned guess as to why they did it?
Samsung makes great products, but we dont have to idolize them the way that iOS Sheep idolize Apple.
Click to expand...
Click to collapse
If you're referring to me I chose the Teg3 One X over the SGS3 and am very happy with my choice. Here's a demonstration of my lack of idolization. In JB, putting the multiview selector to the right of the more important and more often used "settings" selector wasn't very well thought out from a usability perspective.
S-Note turning up the brightness works fine for me and I kind of like it since auto-brightness tends to be on the dim side normally. I'd probably like it less if I frequently took notes in a dark room which I don't. I don't assume everyone uses their device like I do so I certainly wouldn't invoke my opinion of a feature on others.
This is why I use lecture notes.
There is no brightness ISSUE.
They increase brightness on purpose to make drawing more precise.
You can never satisfy everyone....
Can someone share the apk of the first version with no bars?
Sent from my GT-N8000 using xda app-developers app
bsilvino said:
Can someone share the apk of the first version with no bars?
Click to expand...
Click to collapse
You can't upgrade or downgrade S-Note with just the single APK. There are supporting files that have to be changed along with it. When PDF import was borked on some versions of S-Note folks tried to update it with a newer version of the APK alone and it failed.
Actualy, I did the backup with titaniun but when I tried to restore now I am getting FC. Any idea how can I fix it then?
Sent from my GT-N8000 using xda app-developers app
legion1911 said:
There is no brightness ISSUE.
They increase brightness on purpose to make drawing more precise.
You can never satisfy everyone....
Click to expand...
Click to collapse
Yes they can, they can let us make up our own mind as to what level of brightness we want, the same as we do with every other app. Why bother having a brightness setting at all if that's the case, just get rid of it entirely as they know better.
So I saw this in the build prop
"qualcomm sensors enable
#
# LGE CHANGE_S, 2013-10-29, [email protected]
# below sensor is default true by HAL source.
#ro.qualcomm.sensors.qmd=true
#ro.qc.sdk.sensors.gestures=true
#ro.qualcomm.sensors.pedometer=true
#ro.qc.sensors.step_detector=true
#ro.qc.sensors.step_counter=true
#ro.qualcomm.sensors.pam=true
#ro.qualcomm.sensors.scrn_ortn=true
#ro.qualcomm.sensors.smd=true
#ro.qualcomm.sensors.game_rv=true
#ro.qualcomm.sensors.georv=true
# LGE CHANGE_E, 2013-10-29, [email protected]"
Not sure if anything there can help, but I know that the sharpening is applied when there's something light on a dark background or vice versa and also if you have any type of floating menu it'll sharpen everything in the background.
Samsung does this as well but as far as I know only in multi window mode.
Its not a screen issue as its not always apparent. And as far as I know the oppo find 7 has the same panel and doesn't exhibit these effects.
So anyone have any ideas?
Kernel related ?
Display drivers?
Maybe we should all email lg and ask them for an option to remove it.
Just fyi oppo use japan display inc panel while lg use their own panel
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
daleski75 said:
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
Click to expand...
Click to collapse
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Lostatsea23 said:
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Click to expand...
Click to collapse
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
daleski75 said:
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
Click to expand...
Click to collapse
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Lostatsea23 said:
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Click to expand...
Click to collapse
When it finally rolls out to the USA then I think it will get better dev support.
I'll have the device soon, but I'm not sure we're able to turn it off since it may be the part of the driver. Haven't done it yet, but if we can debug the running code and binary patch the trigger effect into not signaling, we may fix it. If it IS a trigger at all; e.g. we should find when it does signal the driver/gpu to apply sharpening and just switch code from JE to JNE or similar to kill the trigger and never apply it.
Theoretically.
Hopefully LG can turn it off and not a hardware combo issue with the 801 and this particular display tech.
It can be turned off. They purposely added it
Lostatsea23 said:
It can be turned off. They purposely added it
Click to expand...
Click to collapse
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Lostatsea23 said:
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Click to expand...
Click to collapse
Well, I don't believe a whole bunch of smart engineers, designers and such in dev and QA would not notice it sucks...
And for screen modes, after so much hassle, I hope and expect LG is preparing us a "turn bloody thing off" setting...
Well once it comes out in the states I will be contacting some devs about it. We need a boot loader unlock as well though
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
flaring afro said:
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
Click to expand...
Click to collapse
They're dumb because it makes it look worse. In almost positive a fix will be found. If anything maybe the carrier releases will have this fixed already.
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
haris182 said:
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Nope. Exactly the same. Placebo
Sugar pills taste so good
rushless said:
Sugar pills taste so good
Click to expand...
Click to collapse
Lol. If an update to remove this isn't out in the next couple weeks. Bye bye G3