EDIT!!! F*&% photoshop defaults to background again when I save! This is ****ting me to tears.
EDIT: Just had a read of this articleabout photoshop background layer being saved by default after reading this guy's thread here
Short answer is that Layer 1 is an arbitrary assigned value to any layer above the background. Layer 0 is what your image needs to be so simply renaming the default value of 1 to 0 works AFAIK. I will be testing this in a couple of minutes.
Will leave the rest as a reference for everyone else. They may learn from my stupidity. I did use the search button though it just took searching and searching till I found that guys thread above that had something specific that applied to my situation.
Hi,
I have am a confident at Android, I have build ROMs and I have a great deal of knowledge and for some reason the most simplest thing stumps me and that is getting bootanimations to work. I understand how they work and I know its not the frame rate or anything like that it has to be something to do with my export settings? Can someone here point me in the right direction?
I will give you a scenario here and why I have mentioned the above. I can get an existing boot animation that is 100% functioning and working and then I might edit the images, say for instance I am changing the colours. I don't change their size or physical dimensions in any way shape or form (they will even play in the preview emulator perfectly), I flash them to the device and nothing? Blank screen on boot up. It completed the boot and opens the OS, but for teh duration of the boot sequence when there is usually a boot animation working it shows completely blank?
Surely it has to do with my export settings? I'm competent with use of GIMP and Photoshop, I have GIMP 2.8 the latest and PS CS6.
Can someone with some knowhow here PLEASE help me with supply "secret settings" for their export of images?
I read somewhere that the images need to be reindexed? I don't know how to do this? I have edited other PNGs that are non-bootanimation PNGS and I knew I had to uncheck indexing and check the box for R,G,B and that allowed me to edit the image.....but if I check the box for an boot animation image (set to R, G, B) back to indexed; when I close the image and re-open it again its back as a R, G, B image? WTF?
I have heard somewhere they need to be 24bit? I have NFI what that means or where to change it? My version of photoshop only has listings for 8bit, 16bit and 32bit?
Yes my kernel allows for bootanimations. Yes a boot animation was working on my phone!
I can change nothing except the colour of the images; package them in the same location in the zip; Test on the previewer for Windows; load it to the phone -> nothing!
EDIT: YES Permissions are set correctly. I can even change back to the boot animation that I changed the colour and it works perfectly
I read now 8 bits per channel. And there is 3 being that they are RGB, which makes them 24bit anyway? WTF is wrong. I fail hard if I can't get a boot animation working LOL.
Jarmezrocks said:
I read now 8 bits per channel. And there is 3 being that they are RGB, which makes them 24bit anyway? WTF is wrong. I fail hard if I can't get a boot animation working LOL.
Click to expand...
Click to collapse
you should upload here that bootanimation.zip file
Yet Another Auto Brightness (YAAB)
A small open source application designed to enhance user control over screen brightness. Initially it was developed to make the screen as dim as possible to save battery on old devices. AND to provide a simplest possible user interface without any complicated calibration procedures and so on.
It is Beta version now. It has ascetic interface and very simple in use.
Source code, issue tracker and latest APKs are available here: http://bitbucket.org/gyrussolutions/yaab/
Google Play link: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Any feedback is highly appreciated, especially from other Android developers
Tester initial impressions
A nice small download and a simple and clean interface. Started service and it immediately started dimming my brightness. A few points to begin with:
The manual slider does not seem to work as there was no change in the brightness.
It doesn't seem to alter the brightness in different lighting (unsure if it is supposed to do this or not from documentation).
It is making my screen too dim, I have a GT-I9300 and the auto brightness on it is excellent and always keeps my screen at the good readable and useable settings.
Will run for an hour or so now and update this with further thoughts then.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Ok it's keeping my screen to dim to be usable so have had to uninstall for now. A few further points though:
Application Force Closes when you stop the serverce.
The manual slider does not work.
Handset - GT-I9300
ROM - Paranoid Android 2.51
OK log wouldn't upload, here's a link for it on dropbox.
https://www.dropbox.com/s/mbyfz33b7audtxz/2012-11-02-17-10-36.txt
Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.
andrvo said:
Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.
Click to expand...
Click to collapse
Let me know when you have a new version and will test again for you.
Hi!
IIIIkoolaidIIII said:
Let me know when you have a new version and will test again for you.
Click to expand...
Click to collapse
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.
andrvo said:
Hi!
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.
Click to expand...
Click to collapse
Details bellow, Sensor name - CM36651 Light sensor
Darkened Room:
Accuracy 3, MAX 121240, last 0.0
Bright light:
Accuracy 3, MAX 121240, last 3700.0 (fluctuating around this point)
I've not read much in relation to sensor issues on this ROM, will do some digging myself now. Hope this information is useful to you.
B
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
I have just done some digging and found no Liight sensor issues mention in the CM10 threads or known bug list. There was a light sensor issues back in September for Paranoid Android but this was fixed back then. Where have you seen the information about peoples concerns with the light sensor?
I have attached a link to the CM10 known issues bellow.
http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-I9300:Nightly:Known_issues
I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.
andrvo said:
I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.
Click to expand...
Click to collapse
Yeah those were two months ago and the bug was fixed in a few days, there have been about 10 version updates since then as well.
Let me know when you're new version is available and will test again.
B
Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.
HTC Wildfire S (Marvel)
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
I'm curently on custom SENSE 2.1 rom but I switch often so will test this one on them too.
Tnx,
GermainZ said:
Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.
Click to expand...
Click to collapse
Will be done, thanks. I don't know how could I have missed that
kobredabre said:
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
Click to expand...
Click to collapse
Thanks for the update.
We are working on automatic/manual "night reading" mode and manual range adjustments now, but we intend to keep the main screen and the defaults in this way, so most of the users would not even need to open menus and dig deeper into the settings.
IIIIkoolaidIIII said:
Let me know when you're new version is available and will test again.
Click to expand...
Click to collapse
I've uploaded current version to the downloads section: https://bitbucket.org/gyrussolutions/yaab/downloads
Check this one please when you have time.
To be honest I still don't know why did it set brightness to minimum on your phone and didn't ever rise it again.
But your log revealed a number of thread synchronization issues that I fixed in this version. I believe there could be connection between these issues and your dark screen.
UI is a bit different, it is my current development version. But start/stop buttons still do the same.
Don't wait long, 10-15 seconds is enough, if it doesn't track ambient light changes right from the beginning - it will not start after some minutes.
Thanks.
Hi andrvo,
Yaab works on my Nexus 7. It is also very easy to use. But I have two remarks.
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.
Thanks, checking it out...
benkxda said:
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
Click to expand...
Click to collapse
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
benkxda said:
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Click to expand...
Click to collapse
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
benkxda said:
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.
Click to expand...
Click to collapse
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Test it on Galaxy Note 2
Everything looks working. Closing the sensor with my hand causing the screen light dim.
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.
andrvo said:
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Click to expand...
Click to collapse
That new release I get then via Play, thanks for that. Delighted me.
jimmod said:
Test it on Galaxy Note 2
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.
Click to expand...
Click to collapse
Ok, I'll check it, thanks.
Version 1.6 is rolling out to the Play store.
What's new:
night mode, manual and automatic. The latter will work only on new devices with high quality sensors which are able to provide accurate values in the lower part of the range. Manual works on any device.
range controls added. Now it is possible to shrink the actual range of automatic brightness values.
bugfix (of course)
Beta testing is still going on, all testers are welcome.
Fresh APK is also available here: https://bitbucket.org/gyrussolutions/yaab/downloads
When build the custom watch face, the setting for Galaxy Watch Designer 'Current OPR' for 'Always on state' is too high which recommend to set lower than 15%. It is advice to reduce lower than 15% for this setting before build successfully.
Is anyone know how to adjust the low bit color to lower than 15%?
I suggest you have the image for the AOD to have more black in the background. Pure black pixels are completely off so it will help in lowering your OPR. Check images for a face I use. You can see the difference in OPR in the sample images. Hope this helps.
https://imgur.com/a/5uFHZjt
https://imgur.com/a/BrdfLPX
I was having the same issue with my OPR (On Pixel Ratio) being too high and searched the net for a long time tonight. I even modified the background image that I was using to be very dark (almost couldn't even see the original graphic). I also played with the text color for each section. I turned off all AOD settings and still couldn't build my TPK. I didn't seem to have this problem before version 1.6.2 but finally figured it out.
The image I was using was 256 X 256 so of course I had to resize it to fix within the Circle Template. What I did wrong was to stretch the image out way beyond the Circle Template lines. So I went and modified my original image so when I re-sized it, it didn't go beyond the Circle Template lines very much. This allowed me to not even have to create an AOD image (I was creating a watch face for personal use only) then I could build the .TPK (for either 4.0 or 3.0) and install on my watch.
I've included a screenshot to show my mistake and the correction.
https://www.mediafire.com/view/awxhd398q129jct/012419_Before_and_After_Circle_Templates.jpg/file
Hi, I'm running stock rom and wondering how to get the best out of my camera. I've seen people installing the google camera but confused as to which one to download and what config settings. If someone could point me in the right direction or link to the right files I need for my phone that would be really appreciated.
If you want natural "life like" colors use: https://forum.xda-developers.com/t/gcam-for-x3-pro.4256287/post-85804879
For "insta" photos use: https://forum.xda-developers.com/t/gcam-for-x3-pro.4256287/page-10#post-85826307
Open sample photos for each and see difference, you'll understand what i mean.
Thanks, I'll give that natural one a try, what do I do with the config file?
After installing camera you go into settings, Load Config and choose the .xml you downloaded in this case "MK+V7.3.5+FIX+4.4+BSG.xml"
ps.
If you want to change config in the future you need to first clear Gcam data/cache before applying new config to avoid issues. Or just reinstall Gcam.
As for the Video recording don't use [email protected] / [email protected], use 30 fps instead it's much better quality. (60fps is upscaled lower resolution)