Prism fix on 4.2? - Nexus 7 Q&A, Help & Troubleshooting

Hi Folks, used Prism app to disable the tegra prism setting to avoid washed out videos, but after updating to 4.2 this doesnt seem to have any affect any more - has the prism defect been fixed in 4.2 therefor negating the need for the app?
Cheers,
Mick

micks_address said:
Hi Folks, used Prism app to disable the tegra prism setting to avoid washed out videos, but after updating to 4.2 this doesnt seem to have any affect any more - has the prism defect been fixed in 4.2 therefor negating the need for the app?
Cheers,
Mick
Click to expand...
Click to collapse
I have noticed that is has been reduced drastically. The slight effect is there (you can see it when exiting a video back to the home screen quickly), but it is nowhere near as bad as it was. Seems they recalibrated it.

Related

Possible Cause of Camera White Screen - Gingerbread

I installed DSC 0.61B today. I'm reasonably pleased with its performance, except for 3G not wanting to wake up with the rest of the phone (a known issue). Besides that issue I encountered a problem that plagued me when using StreakDroid. An issue crops up where the camera display turns white, rendering the camera and all apps that depend on the camera useless. It took me three hours to pin down the issue, but I believe I have found it.
Something in LBE Privacy Guard 2.x is causing the camera to cut out on my Streak. Don't ask me exactly what in the app is causing the problem. All I know is that I need to find a copy of the 1.x APK and install it to see if that version also causes the camera to cut out.
To everyone else that has encountered the camera white screen of death, post here whether you use LBE or not, and what version.
EDIT: LBE 1.x also causes the camera screen of death. Guess I'll have to use Droidwall instead.
Yes, the same to me?
My camera display turns white screen, but I dont know how to fix it.
Thanks,
Are you running LBE Privacy Guard? If so, you have to do a factory reset and not install it. If you're not running LBE one of your apps is not compatible with Gingerbread. You'll need to factory reset and install your apps one by one, checking the camera each time. The app that breaks the camera is likely the last app you install. Once you find it, then factory reset (again!) and don't install the incompatible app. Using nandroid backups do not work. At least they didn't for me.
I wasn't kidding when I said it took three hours to pin things down.
Same problem here:
DSC 0.62b & LBE Privacy Guard
==> white screen when using camera
==> white screen when trying to play youtube videos
In LBE Privacy Guard I unchecked "Start automatically at phone boot"
After a restart, camera & youtube worked fine.
Obviously, the LBE app causes the issue.
Unfortunately, Droidwall can't compete with LBE Privacy Guard's features.
So let's find a solution.
i have DSC 62b and without this problem, I have this problem only if I install Chainfire3D and his drivers ...
Sent from my Dell Streak using Tapatalk
Sackradi said:
In LBE Privacy Guard I unchecked "Start automatically at phone boot"
After a restart, camera & youtube worked fine.
Obviously, the LBE app causes the issue.
Click to expand...
Click to collapse
That's good to know for the future. People at least won't have to do a hard reset.
Sackradi said:
Unfortunately, Droidwall can't compete with LBE Privacy Guard's features.
So let's find a solution.
Click to expand...
Click to collapse
Contact the developer, if you can. They seem to have no contact information on their pages. Droidwall may not be able to compete with LBE's features, but it's also not intended to. Droidwall is simply a front end for the built-in IPTables.
I will be looking into Permissions Denied by the man who put out Busybox as an alternative.
I think switching video driver mode to mdp should help.
@_n0p_: LBE Privacy Guard should function regardless of what video mode is used. While I am sure changing the video mode helps, the point is that people shouldn't have to make that change just to use the software. The fact that LBE has a bad interaction with the camera means LBE has a bug somewhere in its code.
I personally think that composition type gpu mode is quite experimental, it functions, but it's not an app fault, if it (probably) uses hw accelerated features of GPU chip, that breaks hw accelerated surfaces on camera output.
What really should be done - is fixing adreno driver/libs that are the real problem.
I've already tried some other adreno drivers with no luck so far, but as we are working on updating and improving kernel so a solution may be found in near future.
--
Sergei
Perhaps I'm not understanding you here, so forgive me if I restate myself.
LBE Privacy Guard only deals with app permissions and has no control over other hardware or software, especially at the driver level. Yet it's interacting with the camera driver to render the screen useless? If that is the case, StreakDroid is also using the same video mode. The question is whether the other Gingerbread ROMs are encountering this problem and whether they use the video mode you and Streakdroid use.
As a side note, Permissions Denied works perfectly and has no autostart option. This means Sackradi is absolutely correct in that the LBE autostart mode has a problem. So what is the connection between LBE's autostart mode and the camera?
I got your point.
To be more specific - it's not the app that controls harware. It's a bug in video driver function, called by app.
Glad you've found a workaround.
I freeze the LBE by using titanium backup then restart, and then I defrost LBE.
Everything work fine for me until I restart my phone.
I like LBE very much, so I just do the step everytime I restart my phone.
Sent from my Dell Streak using XDA Premium App
Which essentially renders LBE useless since LBE has to be active to monitor the permissions and deny them as needed. If Permissions Denied has such a monitor, it's written so that it doesn't screw up the camera like LBE does.
I get this issue when I patched libwebcore.so with Arabic patcher. How to change the video mode?
system/build.prop
change
debug.composition.type=gpu
to
debug.composition.type=mdp
I am using Power_rom_lite and this issue was bugging me from last two days, when I installed LBE. I realised the problem during video call on Gtalk. I saw white image in place of my video but other end was able to see me without any problem, only I was not able to see myself. Changing gpu to mdp solved the problem. Thanks a lot.
_n0p_ said:
system/build.prop
change
debug.composition.type=gpu
to
debug.composition.type=mdp
Click to expand...
Click to collapse
can you tell me how to use this ?
i have a problem whit white screen camera, i tried ewerything expect this
chynol said:
can you tell me how to use this ?
i have a problem whit white screen camera, i tried ewerything expect this
Click to expand...
Click to collapse
That's quite old thread. You should edit system/build.prop file.
_n0p_ said:
That's quite old thread. You should edit system/build.prop file.
Click to expand...
Click to collapse
yes i know its old thread, but this problem happend to me few days ago on my samsung a51, only 0,5 zoom works, i know it is not a hardware problem because i changed it and didnt help
i cannt find any other solution for this problem, so i gona try this, but i cant find system/build.prop file, can you tell me where to find and how to change it(through win? or?)
thank you

[PROBLEM] Nexus 4 Brightness

I wonder if the nexus 4 of you are having problem in brightness.
updating.. I'm uploading video on youtube
youtube dot com /watch?v=dvgt17sKQsU
Which problems exactly?
Too dim or bright? Flickering? Problems with the auto brightness?
At least a few informations about the issues should be included when creating a new thread.
Nuu~ said:
Which problems exactly?
Too dim or bright? Flickering? Problems with the auto brightness?
At least a few informations about the issues should be included when creating a new thread.
Click to expand...
Click to collapse
look on youtube /watch?v=dvgt17sKQsU
if you can help me
No problems with my Nexus 4's brightness.
Solutions Etcetera said:
No problems with my Nexus 4's brightness.
Click to expand...
Click to collapse
My Nexus 4 have Stock ROM 4.2.1 this is problem with hardware?
erivaldo said:
My Nexus 4 have Stock ROM 4.2.1 this is problem with hardware?
Click to expand...
Click to collapse
Same here, stock everything; no problems.
erivaldo said:
My Nexus 4 have Stock ROM 4.2.1 this is problem with hardware?
Click to expand...
Click to collapse
Go to Settings>Brightness or whatever its called in english, try manually lowest and highest brightness.
If it works > delete this widget, use better coded ones.
If the screen goes off > hardware issues.
Testraindrop said:
Go to Settings>Brightness or whatever its called in english, try manually lowest and highest brightness.
If it works > delete this widget, use better coded ones.
If the screen goes off > hardware issues.
Click to expand...
Click to collapse
i just try manually lowest and highest brightness. and my screen goes off =(
For brightness, I use LUX app, I manually set brightness levels according to light level!
Asking for help is asking a question so please post threads like this here in Q&A in future. Also try to be as descriptive as possible to help people help you.
Thanks
AvRS
my brightness slider doesn't work at all, tried the lux program, only subzero works but from zero to backlight its the same, no dim to turn off display.
i backed up and reformated and the brightness does work now, my one was stuck at 50%, it broke some time ago, maybe updating to 4.1.2 or developer animations disabled.
i will occur again soon, hopefully google releases another update.

multitouch issue, hardware or software problem?

i got the same issue showed in this video: http://www.youtube.com/watch?v=gz27tAD1IBQ
Can anyone please tell me if is an hardware or software problem? Shell i use warrenty and contact asus? Thx
The only way to identify it as a software problem would be to change the kernel, or maybe even ROM. But it will probably be a hardware issue.
korockinout13 said:
The only way to identify it as a software problem would be to change the kernel, or maybe even ROM. But it will probably be a hardware issue.
Click to expand...
Click to collapse
in this way may i'll have problem in case of warranty? I dont know asus warranty behavior
Do you observe multitouch issues in other applications, or are you assuming that because you can reproduce the effect in that video that you have a problem.
If you enable developer options on the N7, and then turn on (Settings -> Developer options):
- Show touches
- Pointer location
can you reproduce the effects shown in that video? (Probably you need to do this on a blank homescreen or maybe viewing a picture or something so that you are not launching apps).
[Edit] I d'loaded a free market app "Multitouch Visible Test" from the market - it looks like the one in the video, although I can't be 100% sure. There are a lot of those kinds of apps in the market. FWIW, I couldn't reproduce what was demonstrated in the video. Not sure if that means anything though. I'm on rooted stock 4.2.1
tonettothebest said:
in this way may i'll have problem in case of warranty? I dont know asus warranty behavior
Click to expand...
Click to collapse
As long as you send it in completely stock, they'll never know or care.
Sent from my SGH-I777 using xda premium
bftb0 said:
Do you observe multitouch issues in other applications, or are you assuming that because you can reproduce the effect in that video that you have a problem.
If you enable developer options on the N7, and then turn on (Settings -> Developer options):
- Show touches
- Pointer location
can you reproduce the effects shown in that video? (Probably you need to do this on a blank homescreen or maybe viewing a picture or something so that you are not launching apps).
[Edit] I d'loaded a free market app "Multitouch Visible Test" from the market - it looks like the one in the video, although I can't be 100% sure. There are a lot of those kinds of apps in the market. FWIW, I couldn't reproduce what was demonstrated in the video. Not sure if that means anything though. I'm on rooted stock 4.2.1
Click to expand...
Click to collapse
i observe multitouch problem durin broswer and photo pinch to zoom. So i download the same application of the video and i understand to have the same problem! :'(
Today i'll try to flash a custom ROM and Kernel. If the issue will persist i'll go to saturn hoping is a quick sostitution. I dont want to send my N7 to ASUS.....
I have not get rid of the issue changing kernel and ROM but it has improved a lot with the combination of Franco kernel, Cm 10.1 and some tweaking in kernel parameters. I also noticed that enabling Force gpu in development options made it go better. I have read somewhere in this forum that all Nexus 7 have the same issue and it will be solved in 4.2.2. I hope it is true.

[Q] Instagram Filters Issue On I9500?

So I've been experiencing filter issues with my I9500 for as long as I can remember...
Some filters such as X-Pro II, Brannan and Kelvin either give a black output or a previous filter that was applied. Sometimes they just flip the picture upside down.
Tried clearing data/uninstalling-reinstalling/unchecking features in advanced features, nearly anything I can think of. Have the app updated to the latest version.
Wanted to know if others are facing this issue as well and if they have resolved it somehow, would like to know in what way...
Running official 4.3 ROM (rooted/Adam Kernel)
Anyone?
same issue bro...I just avoid to use these filters...cannot find the way to fix, hope someone could help
Sent from my GT-I9500 using Tapatalk
MajorAly said:
So I've been experiencing filter issues with my I9500 for as long as I can remember...
Some filters such as X-Pro II, Brannan and Kelvin either give a black output or a previous filter that was applied. Sometimes they just flip the picture upside down.
Tried clearing data/uninstalling-reinstalling/unchecking features in advanced features, nearly anything I can think of. Have the app updated to the latest version.
Wanted to know if others are facing this issue as well and if they have resolved it somehow, would like to know in what way...
Running official 4.3 ROM (rooted/Adam Kernel)
Click to expand...
Click to collapse
Same here bro, i'm on omega 4.2.2 UBUBMH1 and Adam Kernel, my favorite filter is X-PRO obviously for everyone, i have filter problems which pixelate my pics when i upload them, my old S3 do better job than my s4.
Please if anybody know a solution to this frustrating problem, he'll be very welcome !
PS Just for laughs ; i'm using Genymotion android emulator on my pc, and using instagram on it to apply filters i can't on my pics to upload them. that F***** hilarious in my opinion as being a Galaxy S4 owner !!
same here bro...no solution...i've tried everything and still no luck...i remember it use to work fine in a old version of instagram and then in one update it stopped working....
USING: Omega v16 | Base: XXUEMK8 | JB 4.3
Kernel: Adam Kernel

[Q] Screencast black screen? any alternatives?

Finally I got my phone rooted just so I can use a Screen Recorder for my Samsung Galaxy S4.
People recommend to use Screencast, so I did.
Sound is getting recorded but the Screen is ALL Black!
I did the configuration Force GPU Rendering and deactivated HW Overlays.
Any Solutions or alternatives?
Immanueldk said:
Finally I got my phone rooted just so I can use a Screen Recorder for my Samsung Galaxy S4.
People recommend to use Screencast, so I did.
Sound is getting recorded but the Screen is ALL Black!
I did the configuration Force GPU Rendering and deactivated HW Overlays.
Any Solutions or alternatives?
Click to expand...
Click to collapse
The only one that seems to work for me is called "Rec" and it's on the Play Store. You must have a 4.4.2 rom to use it.
Sent from my SGH-I337 using Tapatalk

Categories

Resources