Might be pointless but I am asking for your support - Samsung Galaxy Nexus

Found the place to submit bugs or enhancement requests to the Android Development team. Created a request to get the output of the screen shots changed to JPG or to get option to select between JPG and PNG.
Please post your support at the link below. All it requires is for you to be signed into your google account.
Who knows....maybe this will work if it gets enough posts.
Issue 23969 - android - ICS setting change request for Galaxy Nexus as well as future devices - Android - An Open Handset Alliance Project - Google Project Hosting
All you have to do is click the star....you do not need to comment....but you MUST click the star...it is on the left right next to "issue"....by clicking the star it increases the stars count which in turn supposedly drives the attention. Meaning more stars equals faster results
To stop the emails
Dippa said:
Click the link again, select profile up top > settings > scroll down and uncheck the 2 boxes for comment notifications > save preferences.
Click to expand...
Click to collapse
Thanks Dippa...

I don't really see it being a big deal but... done.

I honestly dont see the need for this. What's the big deal?
I'd rather file a feature request with XDA allowing us to upload PNGs instead of having XDA converting our crisp PNGs to blurry JPGs

josteink said:
I honestly dont see the need for this. What's the big deal?
I'd rather file a feature request with XDA allowing us to upload PNGs instead of having XDA converting our crisp PNGs to blurry JPGs
Click to expand...
Click to collapse
actually that would be nice or even if Tapatalk as a whole did a better job with the conversion.
I don't think it is a big deal either really....but a simple change to JPG would eliminate the need for people relying on photobucket to post images or converting via paint...or as you said....having other apps try to convert.
Would just be so much easier if the screen shot was saved as a JPG from the start....wouldn't you agree?

I actually prefer .png and would rather camera photos were saved as .png also.
I think a user preference setting would be nice.

nerdslogic said:
Would just be so much easier if the screen shot was saved as a JPG from the start....wouldn't you agree?
Click to expand...
Click to collapse
No. JPG is a lossy format and works by smoothing out fourier wavelets, or if you want it less scientific: blurrying out too sharp or crisp lines. This is an absolutely horribly format and compression technique to use on screenshots. It's good for photos, but an absolute disaster for anything where pixel-perfection matters. Both quality-wise and when it comes to compression-efficiency.
PNGs relies on RLE and similar non-lossy technologies and often produces smaller files for screenshots and since they are non-lossy always has better (perfect actually) visual quality.
So no. I dont want ugly and blurry JPG screenshots. I never want that. Which is why I suggested XDA get with the times instead and let us post PNGs.

josteink said:
No. JPG is a lossy format and works by smoothing out fourier wavelets, or if you want it less scientific: blurrying out too sharp or crisp lines.
Click to expand...
Click to collapse
I'm not sure you're thinking of the right format. Simply put: JPG scans the image for similar blocks of colour that are next to each other and groups them together as the same colour.
The compression method doesn't leave the image blurry and will generally leave lines intact, but instead leaves the image pixelated.
http://en.wikipedia.org/wiki/JPEG#Effects_of_JPEG_compression
Which is why I would prefer a lossless format like .png and then still have the option to turn it in to a lossy format later if I want to upload it somewhere.

Kinbote said:
I'm not sure you're thinking of the right format. Simply put: JPG scans the image for similar blocks of colour that are next to each other and groups them together as the same colour.
Click to expand...
Click to collapse
Said less simply, it actually uses a fourier transforms, quantizes the frequency matrix of that transform and runs RLE compression over the quantized matrix before mashing it all together using a huffman-alghorithm, trying to achieve a Shannons-ratio on the data.
The result is that small changes in colour etc can get erased, but also that maintaininging sharp edges during the quantization process is hard, because it requires an accurate frequency matrix.
And the JPG compression process works as well as it does because it does not bother with an accurate frequency matrix.
So yeah.
I stand by what I said.

Fair enough, looks like I've got some studying to do.

fair enough....I am down with simply getting a choice....that is all I am really after....that way us JPG guys can have our "flavor" and the PNG's can have theirs.
So vote...and specify a choice rather than JPG only.

PNGs are less adopted for the mass market although they produce better highly quality images, they weight more, but are more effective for plain colour images.
JPEG is more efficient at reproduction of images in a manner which keeps reproduction close to the original source, but with compression methods applied.
Already stated, but I wanted my two cents.
Sent from my Galaxy Nexus using xda premium

Kinbote said:
I actually prefer .png and would rather camera photos were saved as .png also.
I think a user preference setting would be nice.
Click to expand...
Click to collapse
I'm with you in that I certainly prefer the lossless PNG format for screenshots, but unfortunately PNG doesn't support as much EXIF information as JPG, so for camera photos it's a worse format choice, even though the image quality would be better.
Now if these cameras could save in RAW....

josteink said:
Said less simply, it actually uses a fourier transforms, quantizes the frequency matrix of that transform and runs RLE compression over the quantized matrix before mashing it all together using a huffman-alghorithm, trying to achieve a Shannons-ratio on the data.
The result is that small changes in colour etc can get erased, but also that maintaininging sharp edges during the quantization process is hard, because it requires an accurate frequency matrix.
And the JPG compression process works as well as it does because it does not bother with an accurate frequency matrix.
So yeah.
I stand by what I said.
Click to expand...
Click to collapse
Mind.Blown.

Related

Galaxy S2 Stock Bootanimation finally extracted!

Finally Samsung bootanimation binary started to talk to me, she lets film her!
Especially for Themers this meight be interesting.
DOWNLOAD:
http://www.mediafire.com/?6mfvaff436n7at6​
How can we apply this bootanimation?
It works on MIUI?
yea how to apply?! Usually they come in a .zip format and called bootanimation.zip right?
Yes!
The fle have .zip format and is located in /system/media, but this file only have the images of the bootanimation, not properly the final boot animation file to replaced
I didn't release this as a bootanimation, cause it is a lot of data, that would need to be processed, I already tried it, but it lags as hell. If you want to try, or if you know how to optimize the performence of it:
DOWNLOAD
Updated Version see a few posts below!
janis605 said:
I didn't release this as a bootanimation, cause it is a lot of data, that would need to be processed, I already tried it, but it lags as hell. If you want to try, or if you know how to optimize the performence of it:
DOWNLOAD
Click to expand...
Click to collapse
Maybe the lag is caused by the current number of pictures, not?
I'll see if I can reduce the size by some MB, maybe this will reduce the lag...
will post here as soon as I find time to put my hands on this.
Ok, I optimized it a bit, a bit of quality is lost again, but it's performence seems quite good.
janis605 said:
Ok, I optimized it a bit, a bit of quality is lost again, but it's performence seems quite good.
Click to expand...
Click to collapse
Maybe the lag is related with the number of pictures and pictures quality.
If it's true, we have to reduce the number and/or quality....
celiocalves said:
Maybe the lag is related with the number of pictures and pictures quality.
If it's true, we have to reduce the number and/or quality....
Click to expand...
Click to collapse
I tried many configurations, but the one I uploaded is the best so far. I also reduced the amount of frames or the compression, but well... it just didn' t look right.
Sent from my GT-I9100 using XDA App
Thanks! excellent!!
So here we go:
Didn't try it on my phone but should work.
Put the glowing part at the end as part1 folder and set it on infinite repeat so I could delete some redundant pics and the rest was optimized, so no deleted frames inbetween or whatsoever..
Guess 5mb size should reduce lag to a minimum
Good extraction, like this boot
Thanks alot 4 sharing
KcDaRookie said:
So here we go:
Didn't try it on my phone but should work.
Put the glowing part at the end as part1 folder and set it on infinite repeat so I could delete some redundant pics and the rest was optimized, so no deleted frames inbetween or whatsoever..
Guess 5mb size should reduce lag to a minimum
Click to expand...
Click to collapse
To reduce the lag, It is needed to reduce to size of the images this means to reduce the resolution to 75% and use jpeg then it runs smooth. What I uploaded had already the looped part at the end.
Sent from my GT-I9100 using XDA App
i reduced the size of the images without reducing the resolution and know its 5 instead of 15mb and still png-format...
didnt try yours so i didnt know you already looped the second part
edit: just flashed mine and it works pretty smooth without seeable quality loss i would say
Sent from my KillShip Galaxy S2 using XDA App.
I took this a step further and got it to play quicker by removing some frames and increasing the framerate. Just need to figure out how to smooth the shutdown animation now.
http://www.youtube.com/watch?v=dO_K22ynMW8
nelwyn2 said:
I took this a step further and got it to play quicker by removing some frames and increasing the framerate. Just need to figure out how to smooth the shutdown animation now.
http://www.youtube.com/watch?v=dO_K22ynMW8
Click to expand...
Click to collapse
Nice work
---------- Post added at 03:25 PM ---------- Previous post was at 03:23 PM ----------
Upload the last version plz
Here you go. I basically just made it 60 FPS and deleted every other frame along with a few others that looked like duplicates because I noticed a slight hesitation during playback. I just used the windows photo viewer preview and looked for frames that didn't change and removed them. Then I had to double the frames for the part1 folder because it was playing too fast so every 2 frames is the same. Then spent a LONG time renaming files although it doesn't seem to be necessary as it just reads them in sequential order even if they aren't side by side numbers.
It's not quite as smooth as the video from the OP, but it's a lot better than stock.
Here's another version that's even smoother, but plays slower as a result because of the additional frames. I just removed the duplicate frames and converted them all to jpg. It won't seem to play any faster than 60 FPS. It's not a perfect match for the bootup sound like the previous one, but it's nice if you prefer a smoother experience.
I'm working on one that will include 2 bootup animations. It will have the android glow 1 from Dysgenic's thread and the "droid" sound followed by the smooth animation and sound in this post.
I noticed that in the youtube video it has the sound as well. Any chance you can post the poweron.wav?

[Q] Camera exposure settings

I have consistent problem with camera while taking shots during shows/concerts. Take a look at the pic, the normal looking one at the top is actually under exposed -2. The bottom is exposure 0. I have the same problem while taking videos. For some reason Samsung gets very sensitive while there is a big differential in the light settings. My friend's LG HD and all iPhones don't have this glare.
Is there a place I can edit and modify exposure settings? I'm on TW Jedi X12, but found all TW roms have that 'problem.'
C'mon, no one has the answer to this basic question/problem?
Bronyr said:
C'mon, no one has the answer to this basic question/problem?
Click to expand...
Click to collapse
Hi. I don't know where to edit exposure but, have you tried Camera FV-5? It's a really neat app, and it does a real job. You can adjust the exposure, ISO, shutter controls, white balance, metering and it also display a live histogram while focusing. DSLR controls on your Note2.
Hope it helps!
Thanks for the tip. Great app indeed but no video option. Will be looking to find how to edit the camera app file and make exposure -2 to stick as default.
Sent from my SGH-T889 using xda app-developers app
Do you have auto contrast on? Seems like that may be worth looking into
Sent from my SGH-T889
Bronyr said:
Thanks for the tip. Great app indeed but no video option. Will be looking to find how to edit the camera app file and make exposure -2 to stick as default.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Check your PMs
dwitherell said:
Check your PMs
Click to expand...
Click to collapse
have anybody tried to update camera firmware?
thx dwitherel, it worked perfectly.
Okay. what was the tip that worked perfectly? Wanna share or is it some "If I tell you, I'm gonna have to kill you" thing?
dkb218 said:
Okay. what was the tip that worked perfectly? Wanna share or is it some "If I tell you, I'm gonna have to kill you" thing?
Click to expand...
Click to collapse
LOL - it was a smali edit that fixed it. I am away from my laptop so I can't tell you the specifics at the moment, but there is one particular smali file that sets the defaults for a number of things - including exposure value. There were a few places where the exposurevalue:I and camcorderexposurevalue:I were set to 0x0 (i.e. 0 on the exposure setting). Each integer seemed to be equivalent to a half step on that scale (so 0x1 would be an exposure of 0.5, etc.), so where those values were being set I changed them to -0x4 (or -2). If folks are interested I could post just the modified camera apk, and dkb218 if you want the super-specifics shoot me a PM and I'll go into some more detail once I have the files in front of me (this is all being said from memory, which in my case is rather fallible lol).
Post the modded camera.apk when possible and thank you
camera exposure settings
Is there a way to get the exposure value to go lower than -2? I'm trying to take pictures of powerpoint presentations. The Ipads in the audiences are having no problem with tapping on the screen, the camera focuses on the powerpoint slide and it is clearly visible. The Note 8 still whites it out. An exposure of -2 helps but not enough.

Camera preview is cropped

For quite a while, I have noticed that the preview in stock camera app which comes with several ROMs is simply not full screen, but rather cropped. Final images looks fine though.
I'm currently on latest nightly Rootbox and problem still persists. Is that normal behaviour?
krneki10 said:
For quite a while, I have noticed that the preview in stock camera app which comes with several ROMs is simply not full screen, but rather cropped. Final images looks fine though.
I'm currently on latest nightly Rootbox and problem still persists. Is that normal behaviour?
Click to expand...
Click to collapse
Well if you refer to the fact, that the final images include a wider/higher(depending on orientation) image than the previewed, it's because the camera sensor has a different aspect ratio than your screen. This means that either google had to put 1cm black bares on the top and bottom of the screen in preview mode or they could use the entire screen to show a cropped preview. They chose the latter, and in that case they could either crop the final image as well or include the full photo. Again they chose the latter option.
mortenmhp said:
Well if you refer to the fact, that the final images include a wider/higher(depending on orientation) image than the previewed, it's because the camera sensor has a different aspect ratio than your screen. This means that either google had to put 1cm black bares on the top and bottom of the screen in preview mode or they could use the entire screen to show a cropped preview. They chose the latter, and in that case they could either crop the final image as well or include the full photo. Again they chose the latter option.
Click to expand...
Click to collapse
That was a foolish choice then. The point of a preview is to show what your photo will look like. The gallery displays photos properly and so should the camera. I don't need a full screen camera display, but I do need to see what my picture will look like before I take it.
Well I'll have to disagree with you on that one, we are talking about a mobile camera, and a bad one at that. This is no expensive high end dslr. Your image includes everything shown in the preview and more, allowing you to crop the image if you coincidently included something not meant for the picture.(the phone even includes an easy tool allowing you to do this) This fits the usecase in which a smartphone camera will actually be used, e.g. point and shoot to save the moment, perfectly.
Had they thrown in huge black bars everybody would hate the camera app, and to me a cropped 16:9 image is horrible, leaving only one viable option. I get that you disagree, but that doesn't make it a stupid decision.
edit: Even apple was forced to make the same design choice on the iphone 5 because they switched to the 16:9 screen ratio:
http://blog.crushapps.com/2012/09/with-the-iphone-5s-camera-app-what-you-see-is-not-what-you-get/
mortenmhp said:
Well I'll have to disagree with you on that one, we are talking about a mobile camera, and a bad one at that.
Click to expand...
Click to collapse
Just because it's not a good camera, no reason to make it worse.
Had they thrown in huge black bars everybody would hate the camera app, and to me a cropped 16:9 image is horrible, leaving only one viable option. I get that you disagree, but that doesn't make it a stupid decision.
Click to expand...
Click to collapse
I can't agree with that at all. The old camera was not full screen and I liked it much better because it was easier to use. The current one it seems to be all form before function, this full screen preview being just one example.
Just because it's not a good camera, no reason to make it worse.
Click to expand...
Click to collapse
Correct but that wasn't at all the point i made, which you would have known, had you read more than the first sentence in that paragraph. The point is that this is not a camera used to take high quality precision photos. This is a point and shoot camera, and for that purpose you don't lose any function, making it perfectly justifiable to prioritize the ui.(hence that is what the average user would prefer, since they would never notice the preview being cropped)

[Root] [Guide] How to change your Resolution & DPI on AOSP ROMs

* I am not responsible for bricked devices, displays not working, or your phone melting *
Now with that out of the way, hello! Welcome to my first guide-thingy. As it is my first, I apologise if there is a mistake or if I have left something out, but this process is exactly the process I have used.
Recently I've had a few people ask me about changing their phone's resolution and DPI as said in my signature, so I thought I'd write up a guide for people to use! The ROM I've done this on is the BlissPop AOSP ROM but the process should be similar for most if not all other Custom AOSP-Based ROMs. I am UNSURE if this process works on the stock ROM or any stock-based ROMs.
Prerequisites:
- Root access
- Root File Manager & Explorer (Such as Root Browser or ES File Explorer)
* Root Browser: https://tinyurl.com/aytbttu
*ES File Explorer: https://tinyurl.com/cd4u27q
- NOMone Resolution Changer
* https://tinyurl.com/kjg63jn
- OPTIONAL (For Multi-DPI Patch) Latest AROMA (Now known as Open) GApps Package
* http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
Lets get started!
Firstly, the Multi DPI Patch. It's not essential but allows apps to be properly resized to match your custom DPI, and in the latest Google Apps package it has an option when installing to install a multi-DPI patch for people who are using custom resolutions on their phone. Like me, I'm not using 2560x1440 (Stock 1440p resolution) I'm using 1920x1080 (1080p) resolution @ 370 DPI.
Changing your Resolution & DPI
1. Download NoMone Resolution Changer from the Play Store above (It's free) and grant root access
2a. Open a root file manager (Like Root Browser or ES File Explorer (You have to enable root-access for ES) ) and navigate to the /system folder on internal storage. Find your build.prop at the bottom. Now, you're going to want to create a backup of this file before we do anything as it defines how things work on the phone, so create a copy and move it somewhere safe from being wiped (Like an external SD card)
2b. Click on build.prop and open with a root file browser
2c. Find the line under the #ADDITIONAL_BUILD_PROPERTIES section that says ro.sf.lcd_density=xxx and change 560 (default DPI) to something like 430 if you want the font and stuff to stay the same size or 370 to make it smaller and hit save, grant root-save access if required. Then, open the file with another file manager to verify it's saved and changed. Adjust the DPI to something that you like, but be cautious as not all DPIs work properly (I only know of 370 & 430 that have worked for me). This step may vary depending on how your ROM sets out your build.prop.
3. Set your desired resolution in NOMone Resolution Changer (Mine is 1080x1920, remember to do it backwards so 1080x1920 not 1920x1080 otherwise your phone's GUI will be landscape and not portrait, and will go off the screen)
3b. Set your desired DPI to match the DPI you put into your build.prop file and hit apply (Grant root access if requested). The app will apply your settings and change your screen to match the new settings. It will then prompt you if you'd like to keep these settings, hit yes or no. If you hit yes, it will give you an option to change back the settings after a minute so you can see what the phone looks like at that setting.
*This next step only applies if your ROM has an option to manage the DPI setting itself, like BlissPop does, otherwise skip it*
4. After you've applied your custom resolution and DPI, go to Settings (Yes everything will be massive-sized don't worry) -> Display & Lights -> Scroll down to the bottom, hit advanced Display Settings, and change the LCD Density DPI to match the one you set in your build.prop and NOMone app.
5. Hit yes to reboot or reboot your phone if not prompted.
6. You're done! Your phone should reboot and apply your new resolution and DPI changes.
I have attached some screenshots showing off the BlissPop & Facebook UI at 1920x1080 Resolution & 370 DPI, as well as an example change in the NOMone Resolution Changer App. Lowering the Resolution and DPI is beneficial to those who want to squeeze more stuff onto their screen (it enables lots more text on the screen that isn't really big.) As well as gamers (The lower resolution doesn't strain the GPU as hard.)
If you have any issues, just delete the build.prop you edited from the /system folder in TWRP and copy over the original one you backed up and put it in the /system folder.
Known issues caused by this guide:
- Boot animation may stretch when booting.
- Recent app previews will also be larger for some unknown reason, this is a small side effect however.
Hope this helped!
Now ...again...me....you forgot to mention borked gigantic recents and borked bootanimation on boot.....you should add it to issues list...IMHO
Subbed here as well
/LG-G3/d-855/16Gb/Titanium Black/
m1trand1r said:
you forgot to mention borked gigantic recents and borked bootanimation on boot
Subbed here as well
Click to expand...
Click to collapse
I have added this to the end of the post, thanks.
iDefalt said:
I have added this to the end of the post, thanks.
Click to expand...
Click to collapse
oh...even using 1080p bootanimations doesn't solve that issue....i've never looked deeper into it myself....but tried many workaround w/o succes
/LG-G3/d-855/16Gb/Titanium Black/
I've used this application to lower resolution on my G3 to 1080p but found that the small text and other stuff was blurred because it's disproportionate to the amount of pixels, since 720p would be a more accurate number to downscale to on a 1440p screen (1/2).
Do you notice this "fuzziness"? I forget exactly which DPI I set it to when I did go down to 1080p, but the other thing I realized was that the performance gain was marginal. I did not do long-term battery testing with this, though. So the verdict is still out on whether or not there is any gain there.
xocomaox said:
I've used this application to lower resolution on my G3 to 1080p but found that the small text and other stuff was blurred because it's disproportionate to the amount of pixels, since 720p would be a more accurate number to downscale to on a 1440p screen (1/2).
Do you notice this "fuzziness"? I forget exactly which DPI I set it to when I did go down to 1080p, but the other thing I realized was that the performance gain was marginal. I did not do long-term battery testing with this, though. So the verdict is still out on whether or not there is any gain there.
Click to expand...
Click to collapse
you might not gain much or if any juice on battery....but...performance boost is noticeable on.my side...I forgot how it feels at 1440p ...and switched to for a moment....oh gosh....why do apps take longer to open?....back to 1080p and it flies again...
Oh...you must have set too low dpi to get blury text...I don't even know how that looks like...and if you'd change it to 720p your dpi would be around 220 or something ......
/LG-G3/d-855/16Gb/Titanium Black/
m1trand1r said:
you might not gain much or if any juice on battery....but...performance boost is noticeable on.my side...I forgot how it feels at 1440p ...and switched to for a moment....oh gosh....why do apps take longer to open?....back to 1080p and it flies again...
Click to expand...
Click to collapse
I had tested both normal applications and some 3d games that sometimes bring down fps and neighter seeemd to be any better, but I will have to test this with Bliss as that was some time ago.
m1trand1r said:
Oh...you must have set too low dpi to get blury text...I don't even know how that looks like...and if you'd change it to 720p your dpi would be around 220 or something ......
Click to expand...
Click to collapse
Hmm, you could be on to something. I need to test with your recommended DPI to see if it fixes the blurriness of small text. Thanks!
xocomaox said:
I had tested both normal applications and some 3d games that sometimes bring down fps and neighter seeemd to be any better, but I will have to test this with Bliss as that was some time ago.
Hmm, you could be on to something. I need to test with your recommended DPI to see if it fixes the blurriness of small text. Thanks!
Click to expand...
Click to collapse
some games are badly coded...hence there's no improvement
/LG-G3/d-855/16Gb/Titanium Black/
So I used the recommended settings of 1080p and 370dpi and the blur is minimized but not completely gone. Bearable, though.
I'll be testing out some other performance things and more long-term battery savings. Thanks again for the write-up. Hopefully it will help with people willing to try out different resolutions and DPI's.
xocomaox said:
So I used the recommended settings of 1080p and 370dpi and the blur is minimized but not completely gone. Bearable, though.
I'll be testing out some other performance things and more long-term battery savings. Thanks again for the write-up. Hopefully it will help with people willing to try out different resolutions and DPI's.
Click to expand...
Click to collapse
show me the blur please...my screen of settings and homescreen
Nothing blury here...[emoji41] [emoji106]
/LG-G3/d-855/16Gb/Titanium Black/
m1trand1r said:
show me the blur please...my screen of settings and homescreen
Nothing blury here...[emoji41] [emoji106]
Click to expand...
Click to collapse
Sorry, but this is the kind of thing that cannot be shown on a software level. Screenshots will not work.
The images and text is just not as crisp because since it's not 1:1 with the pixels it will naturally display fuzzy. This is unavoidable but can be lessened by using better ratios (ideally 720p, but that would just be too low) and different DPI settings. If you do not see this yourself then you may lack the eyesight. Again, it's not very noticeable and the positives may very well be more beneficial than having a perfect 1:1 ratio.
xocomaox said:
The images and text is just not as crisp because since it's not 1:1 with the pixels it will naturally display fuzzy. This is unavoidable but can be lessened by using better ratios (ideally 720p, but that would just be too low) and different DPI settings. If you do not see this yourself then you may lack the eyesight. Again, it's not very noticeable and the positives may very well be more beneficial than having a perfect 1:1 ratio.
Click to expand...
Click to collapse
You could try going to 1080p @ 430 DPI. This makes the text similarly sized to the default 560 DPI, only on lower resolution. If you did this, the GPU wouldn't have to work as hard, and your text would still be the original size
But yeah it's worth playing around a bit. I haven't noticed any fuzziness at all at 370 DPI, and I do a lot of reading on my phone.
iDefalt said:
You could try going to 1080p @ 430 DPI. This makes the text similarly sized to the default 560 DPI, only on lower resolution. If you did this, the GPU wouldn't have to work as hard, and your text would still be the original size
But yeah it's worth playing around a bit. I haven't noticed any fuzziness at all at 370 DPI, and I do a lot of reading on my phone.
Click to expand...
Click to collapse
than our sight must be damaged in a way, eh?...LOLZ
/LG-G3/d-855/16Gb/Titanium Black/
If you lower the resolution on any lcd screen made for a specific resolution it will make things fuzzy. You can even do this on your computer monitor.
Everyone should expect this as it is not 1:1, but I still consider it pretty useful.
xocomaox said:
If you lower the resolution on any lcd screen made for a specific resolution it will make things fuzzy. You can even do this on your computer monitor.
Everyone should expect this as it is not 1:1, but I still consider it pretty useful.
Click to expand...
Click to collapse
you really have to look very very very closely to notice anything IMHO
And If that was written somewhere...most people will fall under mass hysteria and take it as granted .....that's a fact....i'm enjoing my huge screen like I did before on 1440p ...it makes no difference for me and side by side comparison with my co-worker's G3 which is all Stock except rooted(by my advice)....makes no difference at all....none, 0,....he didn't notice that I changed anything except THE Beautiful Rom and pure raw power against his Stock G3...so...don't complicate to much....
/LG-G3/d-855/16Gb/Titanium Black/
m1trand1r said:
THE Beautiful Rom and pure raw power against his Stock G3
Click to expand...
Click to collapse
Just two reasons we all love Bliss <3
iDefalt said:
Just two reasons we all love Bliss <3
Click to expand...
Click to collapse
yeah...just two...out of many more
/LG-G3/d-855/16Gb/Titanium Black/
Does it only work for LG G3 in particular? I tried it on my rooted Galaxy S6 Edge and it doesn't seem to work.
Zaberz said:
Does it only work for LG G3 in particular? I tried it on my rooted Galaxy S6 Edge and it doesn't seem to work.
Click to expand...
Click to collapse
The guide is for the G3 running AOSP ROMs.
I suggest you check this out: http://forum.xda-developers.com/galaxy-s6/help/resolution-phone-changed-t3075664
It's look interesting, gonna try this one up. Ty @m1trand1r for your kind answer [emoji3]
Sent from my LG-D855 using Tapatalk

Question Pixel 6 Pro gcam mod?

Whilst this may initially seem pointless, given we have the Pixel gcam of course, has anyone found/tried any gcam mods for our device? The reason I ask is I'd maybe be interested in adjusting some of the saturation/sharpness levels saved as a profile, to suit my personal preferences
I haven't seen any yet. I'm sure there will be in time.
I'm very keen on seeing this as well. Especially the ability to turn down sharpening and noise reduction (so that it can be done more elegantly in post).
Gnaius said:
I'm very keen on seeing this as well. Especially the ability to turn down sharpening and noise reduction (so that it can be done more elegantly in post).
Click to expand...
Click to collapse
If you are planning to go post, why not use the DNGs in the first place? They offer way more room for adjustment.
The main use I peronally got from the modded GCAM on my Pixel 3, was to get better JPEGs out of the box that retain the level of detail and natural sharpness off the DNGs. I so hope to be able to do this for my 6 soon. The DNGs are AWESOME, but the JPEGs are just weak.
cd993 said:
Whilst this may initially seem pointless, given we have the Pixel gcam of course, has anyone found/tried any gcam mods for our device? The reason I ask is I'd maybe be interested in adjusting some of the saturation/sharpness levels saved as a profile, to suit my personal preferences
Click to expand...
Click to collapse
I experimented a bit (since the new P6 GCam is oversaturating/HDR-ing the s*it out of every picture), and people had some discussion about this in the P6 Dev group - summary: Nope, previous mods/versions don't work properly, just sideloading them doesn't give good results.
We'll have to wait for "decent" custom GCam mods that are tuned for the P6. As far as I know, there are none (yet).
Morgrain said:
I experimented a bit (since the new P6 GCam is oversaturating/HDR-ing the s*it out of every picture), and people had some discussion about this in the P6 Dev group - summary: Nope, previous mods/versions don't work properly, just sideloading them doesn't give good results.
We'll have to wait for "decent" custom GCam mods that are tuned for the P6. As far as I know, there are none (yet).
Click to expand...
Click to collapse
I'd like to adjust some levels too so yeah looking forward to seeing what can be done!
ThoroSOE said:
If you are planning to go post, why not use the DNGs in the first place? They offer way more room for adjustment.
Click to expand...
Click to collapse
Can you explain/link to what are these DNGs please?
EDIT: nevermind, found it: https://en.wikipedia.org/wiki/Digital_Negative
ThoroSOE said:
If you are planning to go post, why not use the DNGs in the first place? They offer way more room for adjustment.
The main use I peronally got from the modded GCAM on my Pixel 3, was to get better JPEGs out of the box that retain the level of detail and natural sharpness off the DNGs. I so hope to be able to do this for my 6 soon. The DNGs are AWESOME, but the JPEGs are just weak.
Click to expand...
Click to collapse
Well, by "post" I sometimes just mean sharpening a bit in Snapseed or Instagram; and adjusting levels. I like to set the jpegs to be slightly soft, with a bit more noise than most find acceptable, and with lower contrast. Frankly, once I had the modded GCam set up correctly, the 3XL did a great job with the rest of the parameters. You have to do a *lot* of work on a DNG just to bring it up to the level of Pixel's computational processing (once you've dialled down the overprocessing). After which, yeah, you have a 16-bit image with much more latitude, but that's not generally how I use my phone.
I try to do critical work with larger cameras. And on anything larger than a phone, I never shoot jpegs — only raw. Although even that may change if the big camera makers start getting serious about computational photography; Olympus is making noises in that direction. I'm old school, when it comes to working with unprocessed files, but there's a lot to be said for relying on the latest cameras' computational wizardry.
Anyway, I sense that we basically agree here.
Hmm ... I find, that mostly dialing down lighting and highlights as well as pushing saturation and vibrancy by about 10-20 in Lightroom mostly brings Pixel DNGs to a reasonable base, where editing them is not more work than touching up the JPEGs - albeit with much more latitude for edits. But I get, that everyone has their own workflow and baselines.
I just am glad, that we have these possibilities at all
Sine. said:
Can you explain/link to what are these DNGs please?
EDIT: nevermind, found it: https://en.wikipedia.org/wiki/Digital_Negative
Click to expand...
Click to collapse
Glad you found it. If you set your camera app to also take the RAW files, you can find them in the pictures -> RAW folder on your phone. Try it, it really is worth it. They look not that nice at the beginning. But turn down lighting and highlights a bit, push up saturation and vibrancy a notch and you will see, that the details are WAY better.
Free tools to do that on your device are Snapseed and Lightroom.
This mod works pretty good with p6p:
https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/
in Mod Settings -> Developer Settings : untick "segmenter_use_darwinn_tpu_delegate" to avoid app crash whenever you shoot a face.
out of this small but fixable bug, with this mods default settings, there are a lot more details vs the stock google camera app.
As always, more details = a bit more noise.
But noise is not a big problem when it's controlled, especially if you make prints.
The xhdr processing in settings increase the dynamic range further too.
Everything can be adjusted in the settings, this mod deserve to be known.
All of you concerned about the over-processing issue, please weigh in here, so that Google can see our complaints: https://issuetracker.google.com/issues/208860802
The more people who post, the more likely the complaint will be noticed. (I posted this on similar threads. Apologies if this looks like spam — it's strategic.)

Categories

Resources