Camera fixed by winsuk?
On 13 may instagram, ics camera + is force close, and on winsuk all great.
Camera fixed by winsuk?
On 13 may instagram, ics camera + is force close, and on winsuk all great.
Very, very very very hard work!Camera is original Evervolv with working barcode scanner. Instagram not tried...
Great work!
So far I have only noticed one issue: The capacitive keys backlight works initially, but after installing some basic apps and rebooting several times, they stop working. I have checked all the settings and they appear to conform with the settings listed for prior versions of this ROM.
if you are already testing it: did you used the google apps in the link? I haven't seen them installing on the previous version when I've used the google apps in the link.
Why not use automaticbacklights ? Its full fixed in my build. Try these settings:Great work!
So far I have only noticed one issue: The capacitive keys backlight works initially, but after installing some basic apps and rebooting several times, they stop working. I have checked all the settings and they appear to conform with the settings listed for prior versions of this ROM.
How to enable utomatic backligh:
- go to settings/display/brightnress and set it to automatic
- go to settings/display/automatic_backlight select use custom
- go to settings/display/automatic_backlight/edit_other_levels and set 0,33,77,220,308,397,485,698,860,1023 seccond column 66,96,103,115,130,152,152,255,255,255 third column 255,255,0,0,0,0,0,0,0,0, than save&apply
- go to settings/display/automatic_backlight and select allow light decrease
- go to settings/display/automatic_backlight/decrease_hysteresis and set it to 50%
The second number in the first column should be 34 not 33 for the auto back light.
Sent from my Liberty using XDA
No... see levels in hex format = { 0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x2BA, 0x35C, 0x3FF },
so in dec format it is: 0, 33, 77, 220, 3...
Hello all.
Installed this ROM and I'm loving it. Some thoughts concerning cpu frequencies though.
So, out of curiosity, does anybody use the frequency settings below 400-480 Mhz? In my experience, that range is either completely useless or it results on FC's and/or "(x) has stopped working." messages on this ROM. I stuck with the default CPU settings for the first day or so, then I increased the min to 480 and any messages like the above have stopped. Also, 864mhz seems a bit high. I don't mean to remove it, using it is entirely up to the end user, but just to use a lower max freq out of the box. 864mhz causes my Aria to run too hot and hardlock if used for too long.
Hello all.
Installed this ROM and I'm loving it. Some thoughts concerning cpu frequencies though.
So, out of curiosity, does anybody use the frequency settings below 400-480 Mhz? In my experience, that range is either completely useless or it results on FC's and/or "(x) has stopped working." messages on this ROM. I stuck with the default CPU settings for the first day or so, then I increased the min to 480 and any messages like the above have stopped. Also, 864mhz seems a bit high. I don't mean to remove it, using it is entirely up to the end user, but just to use a lower max freq out of the box. 864mhz causes my Aria to run too hot and hardlock if used for too long.
Are you sure these are the default speeds? last version was set on 245Mhz -806MHz
I think you not understand how that working in our aria. Aria hardware sensor have only 10 fixed steps (0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x2BA, 0x35C, 0x3FF) and nothing more! In kernel its defined same! To understand, you can watch at top of screen raw sensor value (filtered/raw) that is filtered directly from hardware!I don't know about the hex to decimal conversion. But, just looking at the "upper" "lower" label it appears that the the lower limit for the second row should be greater than the upper limit for the first row. This is the pattern that is followed for all the subsequent rows of settings. Why is this not followed through in the second row?