Since I'm not allowed to post in the dev forum, I'll just leave this here:
The light sensor code on the HTC vision is out of date. It can only return 10 light levels, which range from 0..1024. I've been told this is apparently a Froyo standard and that modern phones return from 0..10240.
github dot com/CyanogenMod/android_device_htc_vision/blob/gingerbread/libsensors/LightSensor.cpp
wtf, can't even link to things as a new user?!?
On line 143, you can see the 10 constants that the light sensor code picks between. They are supposed to be in "Lux", but can anyone with a photography rig confirm this? Looking at this chart,
engineeringtoolbox dot com/light-level-rooms-d_708.html
1024 lux is an overcast day. If that's the maximum it can report, that seems like a particularly ****ty light sensor.
Is the hardware that bad, or is the Cyanogenmod code not taking full advantage?
Once we can figure out what the light sensor readings should be, I'll submit a patch to fix the default Automatic Brightness settings (which right now are totally out of sync with the hardware light levels). See line 40 here.
github dot com/CyanogenMod/android_device_htc_vision/blob/gingerbread/overlay/frameworks/base/core/res/res/values/config.xml
Anyhow, only 9 more posts to go before I can participate in the CM9 dev thread
Definitely submit a CM bug report explaining this. Then when you can post links, post a link to the issue thread and everyone will happily plus 1 it.
Hardware is not that bad - this is a CM problem. I've patched mine so it works properly, also, don't use CM. My recommendation.
Thanks for the encouragement. I've filed a bug here. My etiquette may or may not get a warm reception there, so +1s would be appreciated.
code.google [dot] com/p/cyanogenmod/issues/detail?id=4796
I agree with the comment, you should submit it as a patch on gerrit cm review
code.google.com/p/cyanogenmod/issues/detail?id=4796
Alright, installing git now, let's see if I can use it properly.
I might just submit the easy update to the default config.xml AutoBrightness values. My C++ is pretty crap and I doubt I can tell what's going on with the light sensor code.
That seems like an ugly kludge, but it is an open source project after all...
ERROR - JOKES NOT ALLOWED AS NEW USER
What a pain to sync the entire CM source with my crappy internet connection... the 'repo' script recommended in the Gerrit howto hangs overnight.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Killing and restarting the script seems to start again from scratch, so I'm making no forward progress.
I wonder if there's a way to submit patches to gerrit by way of github or some other remote git hosting service?
While setting up git / repo to submit a change to Gerrit, I learned two things - the G2 / Desire Z has a Capella Microsystems CM3602 Light sensor, and the reason the lux values are screwed up - cyanogen did it!
https://github.com/CyanogenMod/andr...mmit/2b53447ec6b2a3fd3e299428d359b3603db19025
Why, I don't understand. The change reason is "Match lightsensor values to kernel". Anyone know more?
Nice, I saw your gerrit submission here http://review.cyanogenmod.com/#change,12845
I hope it gets some good feedback!
Thanks c00ller, I wish I could have added some explanation to the change submission. It would make it a lot easier for a reviewer to figure out what's going on. The real fix would be to change the Vision's lightsensors values to the standard 10..10240 . But without knowing why cyanogenmod reverted them to 1..1024, there's a lot of potential confusion.
The reason for the change is, like the commit message says:
"Match lightsensor values to kernel"
If you look at the kernel source,
Code:
github.com/CyanogenMod/htc-kernel-msm7x30/blob/android-msm-2.6.35/arch/arm/mach-msm/board-vision.c#L317
you can see that these are exactly those levels:
Code:
static struct microp_function_config microp_lightsensor_function = {
.name = "light_sensor",
.category = MICROP_FUNCTION_LSENSOR,
.levels = { 0x1, 0x3, 0x5, 0x13, 0x1A, 0x45, 0xDB, 0x135, 0x1F2, 0x3FF },
.channel = 3,
.int_pin = 1 << 9,
.golden_adc = 0xC0,
.ls_power = capella_cm3602_power,
};
He probably just forgot to adjust the sensor <-> display level mappings in the config.xml (which is what you did in your patch):
Code:
review.cyanogenmod.com/#change,12845
I tried it and it works fine, and I gave it +1
Aha, thanks for the explanation m0viefreak!
I still don't understand exactly where in the code the hardware sensor outputs should be translated into engineering "lux" units. Libsensors seems like the right place to me (naiive non-programmer).
I'd like to advocate for migrating to the gingerbread light sensor standard, since some cyanogenmod auto brightness functionality assumes its 1..10240 lux light sensor range. For example, the "reset threshold".
Is the kernel code using the obsolete 1..1024 range for reverse-compatibility with froyo?
Thanks for bringing this up. I was actually just wondering if the kb backlight issue on Vision keeps coming up because of incorrect light sensor range.
..although this would seem to suggest that the backlight would be on all the time, rather than never on...anyway
I was going to talk to somebody about this but didn't know who to tell about this issue. The brightness can be right at times but the brightness can be changing every few seconds.
Sent from my HTC Vision using xda premium
Any update on the submitted Gerrit change?
Sent from my HTC Vision using Tapatalk 2 Beta-5
azrash said:
Any update on the submitted Gerrit change?
Sent from my HTC Vision using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Was wondering the same thing.
Same here.
Would anyone be willing to file a glitch/issue in the CM7 github for me?
Any news on this one?
When the light sensor can work properly, than battery life would also get a boost.
Can someone maybe post a link to a (flashable)file to get the right readings from the light sensor? Or tell me if there's a editable file on the system partition I can manually edit?
Anyone know where I can download the latest CyanogenMod 9 for the Lenovo Thinkpad?
The link from the developer thread points to everyandom dot com and it is saying invalid file.
Thanks!!
Daren
It suddenly got very cold in that thread. I hope those boys are ok.
Anyway, on the web page select continue as guest at the bottom of the right column. On the next page enter the security code after waiting the required 20 seconds, then click download when that appears. It works. I just checked.
I believe they are students, along with Volker of Quill fame. Spring break, midterms, and life in general will tend to interfere.
http://forum.xda-developers.com/showthread.php?t=1490831
thats the closest your going to get for your TPT, little buggy but definitely gets better with every release
Hadn't much time the last days, compiling a new version for uploading right now (some minor bugfixes and the batterystat fix). Don't worry, CM9 for TPT is still alive
This thread is aimed at people running nightlies on their oneplus one. I think it is good to have a place where we can write about bugs we see on the nightlies. The developers can check this page now and then to see the common issues being faced. Bugs mentioned here can also be transferred to the JIRA.
The issue with the network icon being transparent in the notification bar is being worked on here http://review.cyanogenmod.org/#/c/72566/.
Therefore the next nightly should fix this.
One other bug I have seen is the colour calibration that is not well calibrated and recalibrating it has no effect on the colour. The only way to correct it is to install a kernel and modify the color gamma settings. I started seeing this issue after installing 20140905 nightly.
Please feel free to use the existing thread for nightlies located here:
[OFFICIAL] CyanogenMod 11 Nightlies for OnePlus One
Can anyone confirm that they are able to take panoramas or photospheres using Google Camera?
My app crashes or hangs after 5+ pictures are taken, and the small crosses seen in the background of each image are on a slant.
I have seen this issue come up elsewhere but it hasn't been confirmed that it's broken for everyone. I saw someone suggest that this can only be fixed at kernel level, does this mean that AK (for example) could implement a fix?
Same basic results here.... Mine won't take the 4th shot in the panoramic. I tried a few times and the last time, it wouldn't do the 3rd shot. The blue dot appears, but when you align the frame to it, it does nothing and you have to close the camera to get out of it.
I'm running stock Oxygen 2.1.1
Sorry to dig up an old thread, but I thought I would chime in here by saying that I too cannot take photospheres (running OOS 2.1.1). Is Oneplus ever going to address this?
Hello,
I'm experiencing an issue with the Loop VR headset and my OnePlus Two.
When I use t the two halves of the images doesn't converge and hence it is almost unusable.
I've tried it with my OnePlus One and the LoopVR is perfectly working.
Comparing the two images (see attachments) I can see that on the OPO the image is split in two perfectly symmetric circles while on the OPT the two halves are not symmetric.
I'm using CM 13 nightlies.
Does anyone have any idea how to fix it?
Screenshots:
OPO: http://i64.tinypic.com/9gii3d.jpg
OPT: http://i64.tinypic.com/2njae7c.jpg
Thank you!
EDIT: Sorry, this should probably be in the "ONEPLUS 2 Q&A, HELP & TROUBLESHOOTING" section. Please move it there if it is the case
yes, I have the same problem.
I tried to get the engineer code * # 808 # in the dialer (seen here https://forums.oneplus.net/threads/re-calibrating-accelerometer-magnetometer-gyroscope-sensor.405894/"]https://forums.oneplus.net/threads/re-calibrating-accelerometer-magnetometer-gyroscope-sensor.405894/ ) but cyanogen does not recognize!
I decided to reinstall oxygen os to enter the engineer code, I then have to recalibrate the sensors but when I pass under cyanogen, settings are lost and her again the problem.
I tried with remix os but I do not think because this rom is based on cyanogen.
should we know how to recalibrate the sensors in cyanogen.
ps: sorry for my english, this is the first time I post in xda simply to say you're not the only one to have this problem
EDIT : with remix os, the sensors is not good. The same with cyanogen 13. BUT with the paranoid aospa, IT'S GOOD.
Hello shousky,
thank you for your reply!
Glad to hear I'm not alone
Then I will try to fill a bug report to CyanogenMod when I have time.
Does anyone know how to ricalibrate the sensors?
Hello,
could you please move this to the "ONEPLUS 2 Q&A, HELP & TROUBLESHOOTING" section?
Hello,
a quick update.
I have tried the Google Exploration app and it allows you to chose another cardboard type than the standard. Using this one the experience is much better but the alignment is still not perfect.
I would like to try generate the correct profile but the dedicated site (https://vr.google.com/cardboard/viewerprofilegenerator/) doesn't work for me. After opening the link on the smartphone I have only a blank page.
Has anyone been able to generate a cardboard profile using the cardboard website?
Thank you,
Daniele