On the left of the 10.1IT, there's the camera.
What it the light grey spot right above it? The Archos docs do show it but don't explain it.
You recognized it right...
It's a gey spot
I think its a default camera covering - with space for a light/ambient-sensor but archos didn't include one in the device...
anyway im not sure as it also sound weired as they build their "own case" but use a default camera cover!!?? - but they obviously did - and not included the camera window right into the case.
But it's the best answer i can give - can't remember anything beneath while had it disasembled... - perhaps someone else (scholbert?) can ...
Actually, my first thought was that this would be a nice place for a flash, or IR. But you've seen there's nothing behind it... Strange.
Related
Purely a cosmetic enhancement - does anyone know if there is a way to get rid of the horizontal separating lines on the today screen? Is there a way to disable them/change them to invisible/remove them?
I've been after doing this for aaages, but noone ever seems to know how. There is a way via installing a tweaker thingy (I forget the name of it now but always when I installed it in the past it was a waste of resources and prone to crashes) and because of that I assume there is a registry hack for it somewhere...I've never been able to find it.
If anyone does know or cojones if you find out, I'd be interested in what the answer is.
Cheers
Anthony
bump I'd like to know too.
I have a Cingular 3125. I'm changing jobs, and the new one does not allow camera phones. I don't use the camera, anyway. They say it's OK if the camera is present but disabled, but physically covering the lens is not (even though I think sandpaper would do a pretty good job of making it useless).
Is there an easy way to disable the camera (both camera button and the apps) that will survive a reset? Hopefully, something as simple as a registry and menu edit (OK, I could undo that, but they won't know that) or a CAB to load. Changing to another version of the ROM is an acceptible option, but I'm not really one for cooking my own ROM and I've not seen any 6.x ROMs for the 3100 (camera-less 3125) or ones that list no camera function.
Found some messages from folks who lost and wanted to regain the camera function but nothing the opposite or even a clue as to what unintentionally disabled the camera so I could do the same intentionally.
you can replace the Short_Camera.lnk (and maybe the Long_Camera.lnk) in the windows directory with a shortcut that points to another app. This would stop the camera button from starting the camera app, but it wont totally disable the camera, as you can still manually launch the camera app.
Your other option would be of course to physically disable the camera. Its just plugged in to you can remove the actual camera.
just delete a registry key
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Camera]
and reboot
Erofich said:
just delete a registry key
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Camera]
and reboot
Click to expand...
Click to collapse
Wouldn't let me delete the key, but changing the Dll REG_SZ to nothing or an illegal name seems to do it. Camera button now brings up "Pictures & Videos" and both the Video Recorder and Camera apps fail to work. I thought changing SensorType from 1 to 0 would do it, but it doesn't seem to have any effect.
Thanks for the speedy reply. Might have found it by myself, but wouldn't have known not to mess with the other Camera keys.
XtreMe_G said:
Your other option would be of course to physically disable the camera. Its just plugged in to you can remove the actual camera.
Click to expand...
Click to collapse
Hoping Erofich's solution is good enough for them. Don't want to go that far, but will if it's the only way to keep my precious 3125.
I'm not sure how an easily reversed registry-edit would by sufficient if sandpapering the lens isn't.
Physically removing the camera isn't that hard to do, there is an instruction on how to disassemble the phone here with pictures:
http://www.modaco.com/content/strtr...sembling-htc-strtrk-8500-s300-f600-smartflip/
Taking the camera out really shouldn't be too tricky, here is picture of it:
http://www.modaco.com/index.php?act=attach&type=post&id=19448
You could probably also just put a little bit of tape over the camera and then close the phone back up, which would be the least destructive way of disabling the camera with it being sufficiently hard to re-enable for a reasonable employer.
Can be very wonky at times. When the two points are directly beside or above/below each other on the x or y axis it seems to lose tracking of both points most of the time. Makes the pinch to zoom somewhat more difficult as you have to do it at an angle. Just wondering if everyone elses G tablet does this also.
Thanks!
Hmmm 52 views and no replies?
Nope, no issues here. Have you tried the touch recalibration app? Or reflashing? Do you only notice this in certain apps or is it everything?
Thanks for the response! Haven't tried reflashing but did do the calibration app a while and it helped somewhat. It does seem to be with every app. Think I will reflash and see if that alleviates it.
Thanks!
I don't believe the G-Tablet multitouch is as good as people say it is. My girlfriend had purchased Glow Hockey 2 on my tablet because she wanted to play air hockey against me, only to find that when two points on the screen are touched, the accuracy and responsiveness of the touches drop nearly 75%. It's a shame too, as that game looks to be a sure-fire hit with tablet devices.
I'm pretty sure that it is a hardware limitation, not a software limitation that can be fixed with re-flashing or calibration.
Enectic said:
Can be very wonky at times. When the two points are directly beside or above/below each other on the x or y axis it seems to lose tracking of both points most of the time. Makes the pinch to zoom somewhat more difficult as you have to do it at an angle. Just wondering if everyone elses G tablet does this also.
Thanks!
Click to expand...
Click to collapse
have you calibrated your screen ?
slsmag said:
have you calibrated your screen ?
Click to expand...
Click to collapse
Yup, responsiveness is great. Multitouch leaves a bit to be desired.
I can confirm this problem on my tab, with all rom's except the TnT ones (never tried them). Using multitouchvisualizer app from the market you can see that the screen will not register 2 points immediately when they have the same x (horizontal line) or the same y (vertical line). The problem is definitely better after calibrating the screen (doesnt take as long to register the second point), but the problem persists and leaves something to be desired for this multitouch screen. When pinch to zoom is at an angle to vertical or horizontal, its perfect. If pinching on the horizontal or vertical axis, there is lag.
Normally this doesn't matter because you can just pinch-to-zoom on an angle, but when playing games like cordy or jetcarstunts, where buttons are aligned horizontally, the second tap sometimes isn't recognized immediately. Its somewhat nit-picky, but there are many other touch screens where this is not a problem.
Make sure that you have the proper permissions files available. If you are missing the "Multitouch Distinct" XML file then it doesn't work properly...
Early ROMs didn't have it, so you had to add it manually...I think newer ROMs have it though...
I've attached it here JIC -- just remove the ".txt" extension and drop it in
TeutonicWolf said:
Make sure that you have the proper permissions files available. If you are missing the "Multitouch Distinct" XML file then it doesn't work properly...
Early ROMs didn't have it, so you had to add it manually...I think newer ROMs have it though...
I've attached it here JIC -- just remove the ".txt" extension and drop it in
Click to expand...
Click to collapse
"Drop it in" where? What folder?
Thanks
AndreCole said:
"Drop it in" where? What folder?
Thanks
Click to expand...
Click to collapse
Second that request!
Put it in /system/etc/permissions/ as android.hardware.touchscreen.multitouch.distinct.xml, and make it readable for all.
But, before you do, make sure that the file doesn't already exist. It does on CyanogenMod 7.0.3.
rajeevvp said:
Put it in /system/etc/permissions/ as android.hardware.touchscreen.multitouch.distinct.xml, and make it readable for all.
But, before you do, make sure that the file doesn't already exist. It does on CyanogenMod 7.0.3.
Click to expand...
Click to collapse
Yeah - went looking and found it. There are two files.
android.hardware.touchscreen.multitouch.distinct.xml
and
android.hardware.touchscreen.multitouch.xml
And a review as text file seems to show the same contents.
This post (12/2010) is unclear on what to do.
Thanks!
Um, is it natural for the FFC that I installed into my phone to reverse things from their place? (I am sure this is not natural.) Like for example, if something is on the left side of the screen, when the picture is taken and I took a look at it using gallery, it ends up on the right side. Any fixes to this?
Sent from my SGH-T959 using XDA
FFC Issues...
Normal? lol lets just say its a Vibrant...then moan and say its a Samsung...
Sounds like you have the same camera I installed... sold as a rev2...
Couple things to help you..
1] Pictures taken with the FFC ... when your in gallery hit the menu button and "rotate left" will fix and save the picture in the proper direction wanted.
2] Grab Mirror app from the market it has in the options the ability to rotate image properly and stay that way....usefull to show off your new FFC
Im using the Slim ICS v3.6 rom right now.. it comes with FFC built in..[no it wont rotate image at this time...]
Hope that helps!
Hit the button
p.s. look for my cwm flash file to add FFC to other ICS/cm9 roms [use search]
Good Luck!
Resurrecting the question
Alright, I flashed my phone to Slim ICS 3.6, but it still does the same thing. Like if my face is on the right side of the screen, when I take the picture and go to Gallery, my face is magically on the left side. When I try to use rotate left, it still ends up the same thing. Is it only happening to me or does anyone else experience this? And is there a fix to this?
I have an Allwinner A20 tv box, I trying to use it on a device with an old, low res, 4:3, 5" screen. It works but I have a few problems - firstly the box has "pal" and ntsc" settings for use with AV out, but when connected the picture is squashed inwards so circles are represented as ovals. I ve tried to mod the aspect ratio/resolution but nothing works, the picture is always distorted.
On top of that everything is too small for the screen, it is readable but things really need to appear bigger, so I also played about with the dpi, this does make things bigger and a better match for the screen, even though the device doesnt actually have a screen itself.
I ve done both these mods with several apps and modding the build prop and I always get "sorry systemGUI has stopped", constantly - when you close it, it opens again straight away. Clearly settings doesnt like these mods, so I m trying to work what I need to change so it DOES accept them.
Can anyone tell me how I can successfully mod the setting.db and get this working at the correct aspect ratio and a dpi that is suitable for use on a low res screen ?
Thanks
Anyone ?
typos1 said:
Anyone ?
Click to expand...
Click to collapse
Did you ever figure it out?
And if so how as I have a Vega S89 Elite (Clone) and it has the same text-is-too-small-on-a-sd-tv problem, thanks.