Database Info

IDEA : 4x4 level and tilt meter

If anyone out there wants an app idea.
Using the g sensor on the HD2 display two views of a 4wd.
One view (Top) is a rear view showing tilt left to right.
The second (Bottom) shows a side view showing its tilt front to back.
Requirements maybe skinnable and also a reset/zero button to compensate for mounting.
Basically as your driving the images rotate to show what angle and slope you are driving on.

That would be a cool app...

+1
Tryed a few inclinometers but it's not the same...
//Johan

Been playing with this tool. Pretty close.
Only needs a graphic change and screen saver blocker. Would be cool if it could re-call a previous zeroing.
http://forum.xda-developers.com/showthread.php?t=535944
This is the screen it uses
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Found this
http://my-maemo.com/software/applications.php?name=4x4_Inclinometer&fldAuto=1146&faq=47
this one looks the fruit.
For the iphone thou.

And after looking found a bunch
http://forum.xda-developers.com/showthread.php?p=6514101
http://forum.xda-developers.com/showthread.php?t=568139

Landmeter 2.0
Update:
Completely reworked version with many advantages:
- Even more precise angle calculation up to 100+ degrees sideways
- Completely reworked design
- Much faster reactions ensured with getsensordata function redevelopment
- Digital font for numbers
- Adjustable filter quality
- Scale changes dynamically depending on adjusted parameters
- Full WVGA support
- Side indicators
- More comfort for driver-optimized view,larger fonts
- In the future planned skinning-on-demand(you will send me basic pictures,I will recompile it for you)
Available here:
http://software.connect.de/product.php?pf=pocketpc&prod_id=53777&xsearch=landmeter

Tomas.
Is it possible to get it working in Portrait mode?

Well,actually this would be not a problem.
Development modifications are minor to make it portrait,but there is lot of work with graphics. Therefore I have to wait a long time for the graphics from my designer.
Check this out...

TomasNM said:
Landmeter 2.0
Update:
Completely reworked version with many advantages:
- Even more precise angle calculation up to 100+ degrees sideways
- Completely reworked design
- Much faster reactions ensured with getsensordata function redevelopment
- Digital font for numbers
- Adjustable filter quality
- Scale changes dynamically depending on adjusted parameters
- Full WVGA support
- Side indicators
- More comfort for driver-optimized view,larger fonts
- In the future planned skinning-on-demand(you will send me basic pictures,I will recompile it for you)
Available here:
http://software.connect.de/product.php?pf=pocketpc&prod_id=53777&xsearch=landmeter
Click to expand...
Click to collapse
Hi Tomas!
Tryed your demo and it looked great! But the round meters didn't work/show...? Not available in demo or did i do something wrong?
//Johan

Hmmm,strange... I don't understand,what exactly is wrong. Can you describe it better? Maybe screenshot will be helpful. Btw,tried on many devices,without problem.

Screenshot!
It looks like this. Everything works but the two meters...
Stock Rom, HTC 1.66 swe
//Johan

Well,it seems to have some memory problem. I see this kind of problem during development first version. The rotation pictures are stored separately in 162 position images in one bitmap. This bitmap is quiet large with dimensions 1250x2125. 125x125 pixels per one image,10x16+1x2 in matrix. 125sq is also reason,that the image is not VGA sharp. If I tried to have 250x250pix images,the bitmap was so huge,that cannot load into the memory and I had same problem. What's your free memory? Tried softreset before starting?

I also have the same issue.
No pretty Lada.

Hello.
So I have replaced resources,so this is much smaller rotation image to fit into memory.
Try this out...
Please note,actually this is not a cab,but exefile with renamed extension.

Hello,the attached file is corrupted ...

Btw,if you want to use different "cars",you can create your own and post me them. In attachment,they are some examples.

Marcdu81 said:
Hello,the attached file is corrupted ...
Click to expand...
Click to collapse
Maybe because it is an exefile,not a cab?
did you renamed the extension to exe?
Sorry for that,but I cannot upload larger exefiles,XDA server doesn't allow it.
And that's an executable for your PDA,not PC.

Ok,it's really an exe file,i convert it to a cab file .

I posted this file just for a test for those,who has problems with car displaying. Can you confirm,if this works for you(if original doesn't)?

Green line of pixels down left hand side

I've noticed that on the very left hand side on the edge of the Captivate that there's a column of green pixels going down the whole screen. It looks to be about 1 pixel wide. For me it's most noticeable when you pull down the drop down menu.
I don't know if it's normal or what. I exchanged it at my AT&T store and got a new one, and the new phone also had that column of green pixels on the left hand side.
Any one else notice or have this problem? Is it normal?

I do not have this on mine...sounds like a good reason to take it back and get a replacement..

I took it back yesterday and got a replacement, but it still had that green line. While I was there I looked at all the other display models and every single one also had that problem.
Anyone else? Or is it just that certain AT&T store lol

I can only reproduce this effect with the drop down notification menu and nothing else. Try pulling the menu down on a black screen or by looking at the area where the notification bar and menu meet and you'll see that only the drop down is affected.

its norm, if you browse a completely white page in explorer you'll see it there too. If anyone is worried about it, its deff not noticeable and i have severe ocd issues.

This is normal of any Pentile display such as the one found on the Samsung Captivate. It is not an issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

brilliant wish there was a +1 rep button on the forum

If you can actually notice the Pentile matrix, you have really good eyes

bwolmarans said:
brilliant wish there was a +1 rep button on the forum
Click to expand...
Click to collapse
Hahaha. +1!
But yeah, that's just how the led's are aligned in the display. Completely normal.

Here's some more information for those curious about Pentile Matrix's. This infomation predates the actual manufature of Pentile matrix's, and explains why it is used over a traditional grid matrix. Enjoy!
"This is a color subpixel-rendering system that promises to improve LCD resolution significantly, while reducing data driver requirements. The PenTile Matrix by ClairVoyante (Sebastopol, CA) doubles the addressable resolution in each axis and the modulation transfer function.
An LCD differs little in basic concept from a stained-glass window, modulating the light that shines through it to create a color image for the viewer. The need to generate a moving image, however, requires that the image elements be as small as possible, yet arrayed to blend subpixels in close proximity to properly represent colors.
In the PenTile Matrix, each color is surrounded by the other two colors, using a pattern of alternating red and green pixels to carry the logical pixel information. The blue pixels provide only low-resolution chroma information, matching human vision characteristics, while significantly reducing the number of data drivers. The light intensity is regulated by white subpixels (a recent innovation being explored by other display configurations and technologies as well).
Conventional color LCDs use three subpixels--red, green, and blue--in vertical stripes. A principal disadvantage of the arrangement is that it relies on the blue pixel to carry high-resolution luminance information--a difficult task because of limitations in human vision.
Subpixel font rendering on the RGB stripe is limited to increasing the addressability by a factor of 2, while the PenTile Matrix can double that number in both the horizontal and vertical axes for a fourfold improvement. Another advantage is that the arrangement is nearly rotationally symmetrical, allowing the display to be rotated more easily for portable devices and other displays that may be viewed from different orientations based on the information displayed.
There are currently no displays using this matrix available, but Samsung is working on some prototypes for possible release in 2005/6."
And now for the Wikipedia link to additional more recent information: http://en.wikipedia.org/wiki/PenTile
And another link: http://www.displayblog.com/2009/04/16/samsung-oled-pentile-matrix-why-is-the-red-sub-pixel-so-big/

I've tried looking for this and really dont see it. I see what may look like one line of green pixels all the way on the left as you slide down the notification area. But I basically have to tilt the phone and look inside that area.

I see it. Its pretty damn small though lol.

The green line is only noticeable against brighter background when the green subpixel is being used to trick the eye into seeing white, etc. For example, my background is mostly darker colors, but where an area of white touches the edge of the screen, the green line appears; but only next to the brighter colors, not the darker ones. Kind of weird now that I look at it lol

This makes me feel a lot better that the screen is that way. I just wasn't sure if it was normal or not.
Thanks for clarifying!

jhannaman82 said:
This is normal of any Pentile display such as the one found on the Samsung Captivate. It is not an issue.
Click to expand...
Click to collapse
Funny, since reading this thread last night, I do now notice that one really thin green line running down the leftmost edge of the screen on certain occasions. Its got to be caused by the pentile matrix arrangement of pixels. That first entire left row is all green, thats whats doing it. Especially when you're on a black background like when you slide the notification area down.

[APP] Simple Auto Brightness

Hi,
I was not satisfied with how Android system auto-brightness work. It just don't allow me, nor us to setup maximum screen brightness level for auto-brightness just like iOS did. This problem is really bugging me about my Nexus S battery usage which is bad because of screen is just too bright while i just need maybe just half of it since i spend most of days indoor.
Then i started to learn Android development (this is my first Android app) and here is my simple app to configure my Nexus S auto-brightness. Currently app feature are:
Save battery! Service implementation is really battery friendly (not even shown on Android battery stats)
Custom maximum screen brightness level (in %) (require modify system settings permission)
Custom screen brightness threshold to apply new brightness level (in %)
Allow to use smooth screen brightness level transition
Custom ambiance level pool interval (in seconds). But when screen is awake, brightness level is calculated as soon as possible
Auto-start service on boot completed (require run at startup permission)
Auto-start service when destroyed by Android OS because of system low memory
Display live current screen brightness level (in %)
Display live current light sensor levels (in lx)
FREE!
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Known issues:
On my Nexus S (CyanogenMod 10.1 nightly) maximum light sensor value is 3.6 million (wow!). Each device could provide different sensor value and steps. Example, Nexus 4 Stock would provide 10.000 for maximum sensor value.
Currently using this and this as calculation method
Because of above issues, i still looking for best implementation to normalize light sensor values. Maybe anyone can help about this?
Download and try it from here
UPDATE
20120212 - Check if device has any Light Sensors

Hey! I like the idea of your app. However, I haven't found the issue of auto brightness being set at too high of a maximum value in my usage. What I have found is that auto brightness does not kick it down enough when in low light/dark situations. Are you planning on adding the feature of setting a minimum screen brightness level as well?

crashed when i start the service on my xperia active ics

kino1122 said:
Hey! I like the idea of your app. However, I haven't found the issue of auto brightness being set at too high of a maximum value in my usage.
Click to expand...
Click to collapse
Hi, sorry for my bad english, the issue is not the screen auto brightness being too high above Android maximum brightness setting (on manual brightness). But, its the same as the problem you described below
kino1122 said:
What I have found is that auto brightness does not kick it down enough when in low light/dark situations. Are you planning on adding the feature of setting a minimum screen brightness level as well?
Click to expand...
Click to collapse
To tackle this problem, auto brightness setting is mimicking how iOS implementing its auto-brightness.
By configuring maximum brightness allowed to certain amount (by %). For example, in dim indoors (light sensor lux values ranging from 201 to 400), the default Android auto-brightness will be 30% to 40% (based on this formula, which is log10(lux)/5), then in this app, I configure maximum brightness to 50%, then screen brightness will be 50% of this Android default 30%-40%, which is 15% to 20%. Exactly how iOS device did with its screen auto-brightness.
About minimum screen brightness, it always will be 0%-3%. Android system use 0 to 255 brightness value. By configuring maximum brightness to 50% (it will be 127), then your device screen brightness will be half lower than standard Android auto-brightness. Since the most battery draining items is screen, by cutting its brightness to half or more, i think it will be longer my battery cycle, as i posted above.
oldsap said:
crashed when i start the service on my xperia active ics
Click to expand...
Click to collapse
Oops sorry for that, i did not test it on other device than my Nexus S with CM 10.1 yet, would you send me your logcat? This link will show you how to get logcat

oldsap said:
crashed when i start the service on my xperia active ics
Click to expand...
Click to collapse
i just updated apk with light sensor checking. i suspect Android could not find any light sensor on your device.
the service was trying to start, check if there is no any light sensor, since it found no light sensor, service is not registering screen on/off broadcast. then when service stopped, service try to un-register a never registered screen on/off broadcast resulting a Force Close/crash.
please try to update it. thanks

Just what I was looking for. Thanks!

[APP] AMOLED PWMfree

Summary:
A simple application that uses a transparent overlay to dim the device brightness, effectively removing PWM.
Download PWMfree
More Information:
Why PWM is such a headache
Brief explanation about PWM
Default brightness control:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PWMfree brightness control:

Thanks, runs on my S9 on AOSP 8.1. Affects auto-brightness a bit but seems to work as intended. Great work!

Wrong section man

Can someone explain to me what this app on s9 does?

Its suspicious

@amakuramio
Not sure why the installation is prevented.
The application itself just creates an accessibility overlay and changes the permission for /sys/class/backlight/panel/brightness to prevent access from liblights.
Edit:
Seems like this is the common behaviour for non-playstore apps: disable Google Play Protect

The brightness does not change while sliding the slider, only after releasing the slider. Please fix, thx.

Can this work on other models (like my Galaxy A3 2017 AMOLED) ?

vratnik said:
The brightness does not change while sliding the slider, only after releasing the slider. Please fix, thx.
Click to expand...
Click to collapse
Unfortunately not possible.
victo24dord said:
Can this work on other models (like my Galaxy A3 2017 AMOLED) ?
Click to expand...
Click to collapse
The overlay itself should work on every device, only the brightness slider override that requires root is device dependent.
But this isn't particularly well-working, i will probably ditch this override and just add a widget slider so it can be used without root.

So is this root only? Cause I saw my screen change brightness immediately after turning accessibility access on, and I'm not rooted, stock rom.

@qb74
Root permission is used to prevent liblights (android system brightness handler) from accessing the kernel brightness path (/sys/class/backlight/panel/brightness).
The brightness slider on the notification bar then only modifies the transparency of the accessibility overlay, not the display (kernel) brightness.
Without root permission it controls both the overlay and kernel brightness, but this prevents the pwmfree usage as the kernel brightness needs to be at 100% to avoid pwm dimming.

Trying out on s8+. But weird thing is, when enabled, if you lower the brightness to 0% the screen becomes completely dark. It should not happen like this, I presume. The app has root access too.

@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: (link in the original post)
It locks the device brightness at 100% and uses it's own slider to control it.

Wootever said:
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: pwmfree.apk
It locks the device brightness at 100% and uses it's own slider to control it.
Click to expand...
Click to collapse
So this version works with non-root? Great! Why does the brightness need to be 100%? From the looks of your graph, all brightness levels seem more consistent?

Wootever said:
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: pwmfree.apk
It locks the device brightness at 100% and uses it's own slider to control it.
Click to expand...
Click to collapse
Hmm, well than I hope you make this wonderful app s8/+ compatible too
Thanks for your work mate. Would love to use it :good:

qb74 said:
So this version works with non-root? Great! Why does the brightness need to be 100%? From the looks of your graph, all brightness levels seem more consistent?
Click to expand...
Click to collapse
Only the device (kernel) brightness needs to be set at 100%, at this stage the amoled panel only uses a short 59hz vsync signal (this is the small amplitude on the graph).
Anything below ~95% uses the amoled typical 240hz pwm dimming.
The pwmfree overlay now dims the full kernel brightness by decreasing it's transparency, this is somehow similar to lcd contrast dimming.
@parser
The new version should work on all amoled devices, although the widget type brightness slider is a bit less comfortable than the android system one.

Wootever said:
Only the device (kernel) brightness needs to be set at 100%, at this stage the amoled panel only uses a short 59hz vsync signal (this is the small amplitude on the graph).
Anything below ~95% uses the amoled typical 240hz pwm dimming.
The pwmfree overlay now dims the full kernel brightness by decreasing it's transparency, this is somehow similar to lcd contrast dimming.
@parser
The new version should work on all amoled devices, although the widget type brightness slider is a bit less comfortable than the android system one.
Click to expand...
Click to collapse
Trying it atm, the only down side is, as u said, adjusting the brightness by hand. If I am in a game and need brighter screen, have to go desktop and adjust it :/
Would it have an effect on battery efficiency too?

@parser
The overlay is managed by SurfaceFlinger and shouldn't cause any impact. The amoled panel seems to work identical with the contrast dimming and i would guess the battery usage is similar, but i can't tell for sure yet.
As for the brightness slider, i think this can be placed on the notification bar instead, which should increase the usability.

Wootever, you're BEST!
P.S. I sold my Note 8

I installed it but it won't run, s7 stock rooted.

Is there a way to simulate IOS display color filter on android device?

Hello. I wanna ask if there is a way to simulate IOS display color filter setting by some app or dev setting on android. I want to have this thing on android for one big reason - Blue light. Default Blue light filter Is quite insufficient on both android and apple devices because blue light is still pretty much present with it turned ON. You need to have no Blue light present if you want to have melatonine production in your brain. Apple have an color filter option in accessibility where you can tune your display in a way that It doesn't emitate Blue light. This video shows how it's done:
.I tried various different blue light filter apps like twilight, night filter etc but none of them filter 100% Blue light. Any ideas how to get this Done?

I think this is unrealistic unless you want to use a red or yellow based grey scale. Blue is a component of white so even greyscale has blue in it.
Your brain senses light through the skull as well. Low blue light is more for protecting the retina from the high energy higher blue wavelengths which are damaging. Newer Samsung's from the N10+ up already filter much of these out with the blue pixels themselves which are designed to a emit a lower bandwidth blue without compromising color.

blackhawk said:
I think this is unrealistic unless you want to use a red or yellow based grey scale. Blue is a component of white so even greyscale has blue in it.
Your brain senses light through the skull as well. Low blue light is more for protecting the retina from the high energy higher blue wavelengths which are damaging. Newer Samsung's from the N10+ up already filter much of these out with the blue pixels themselves which are designed to a emit a lower bandwidth blue without compromising color.
Click to expand...
Click to collapse
If I understand it right, Chainfire´s Lumen app have an red based greyscale option. Maybe Lumen can get this thing done at least better than default android blue light filter? By the way here is samsung´s default Blue light filter on S20+ compared with android Twilight app and iP 11 Pro tuned with color filter all meassured with spectro-flicker meter: https://www.instagram.com/p/CJtmA0GH0Sy/ First meassurement is S20+ with default BL filter; second is without it; third is twilight app and fourth is IP 11 Pro with color filter.

LinkinLover2013 said:
If I understand it right, Chainfire´s Lumen app have an red based greyscale option. Maybe Lumen can get this thing done at least better than default android blue light filter? By the way here is samsung´s default Blue light filter on S20+ compared with android Twilight app and iP 11 Pro tuned with color filter all meassured with spectro-flicker meter: https://www.instagram.com/p/CJtmA0GH0Sy/ First meassurement is S20+ with default BL filter; second is without it; third is twilight app and fourth is IP 11 Pro with color filter.
Click to expand...
Click to collapse
The human eye is most sensitive to green, quite a bit more than red. Argument being if you bath everything in red light will need to adjust the lumens higher level to be usable.
Personally I like color accuracy so I don't even use blue filtering on my N10+'s. I find it annoying. Instead use manual brightness control and keep it at a reasonable level for the ambient light conditions. Use dark mode and a layout that conserves your battery, pixels and retinas. With AMOLED displays you have much more capabilities than with LCD's
Read a book rather than look at these bloody ambient light sources late at night. Paper and print are far more relaxing, immersive and easier on the eyes.
My stock N10+/Pie homepage and pull down menu modified with Good Lock Quickstar:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}