yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 General] Luinwethion:
The only think I see in the pictures you posted, is that the Locked bootloader is "lighter", but with a inaccurate white balance, something wrong with the flash.

I can't see the picture details (iso and shutter speed) from the pictures.

It's very difficult to compare the results between LB and UB, a small change in the scene can affect the final result... Even the way you hold your phone (and it gets more important while using Superior Auto, but you can say the same for Manual mode, that isn't really Manual).

In this test I show that the way you hold your phone can have drastic result in the picture quality (more or less ISO / noise).

PS: Pictures from both sets are taken with a unlocked bootloader:

https://www.flickr.com/photos/97274591@N06/12161589033/in/set-72157640187444416/

https://www.flickr.com/photos/97274591@N06/sets/72157638572108166/

Once I unlock my bootloader again, I will try to make a comparison, trying to keep the scene, settings and etc the same.
[Xperia Z1 General] Riyal:
Bionz doesn't have anything to do with DRM AFAIK. DRM stands for Digital Rights Management. It is a software used to protect digital media from piracy which isn't at all related to Bionz since Bionz is an encoder not decoder. DRM only restricts decoding illegal media but not encoding because there's no piracy involved there. Also you can't create a perfect comparison shot of a camera without a still stand and an controlled environment. A little shake on the device while taking a photo could affect noise radically and same goes for the lighting, contrast and colors of the subject. And also for the focus.

The reason why the camera doesn't work before on Xperia Z1 on unlocked bootloader because the viewfinder shares the same decoder library as used in video playback which utilizes a part of DRM feature hence it won't work. Doing a little logcat at that time shows the error clearly.

If bionz was the problem that time the camera app could have worked since bionz is only used when you take a picture not while the camera is idle or whatelse :)

Do take note that AR Effect works that time because it has it's own seperate viewfinder libs for inserting the AR functions.
[Xperia Z1 General] petalex99:
I think you are right. But, Sony....

what is the Sony answer

at that very simple question: unlocking bootloader affect the photo quality or not?

That for finish up once forever at this endless discution. I am on unlocked BL (C6903), stock-based JB (I proved and I hate KK), and I am afraid to downgrade, relock BL and restore my TA, because the possibility of a hardbrick.
[Xperia Z1 General] kantk20111:
BIONZ is working, however in unlocked bootloader it does not work the same way it does with locked bootloader.

I insist there's a difference in picture quality. To prove it, I took a total of 12 shots. 6 shots of the same subject in a row in 15mp manual mode with 400ISO in UBL, and then I relocked my BL, restored my TA and took the same 6 shots again in the same conditions merely 10 minutes later.

I took 6 shots so that the 'random picture quality difference' is negated.

Here are the pictures. I can provide originals as well if people wish. I uploaded to imgur because it's easier for me.

Unlocked bootloader pictures

http://i.imgur.com/Ft94Zm2.jpg

http://i.imgur.com/QHq0NBv.jpg

http://i.imgur.com/EFbgo5w.jpg

http://i.imgur.com/zKoNEkg.jpg

http://i.imgur.com/xgEJvV5.jpg

http://i.imgur.com/iEFCUea.jpg

Locked bootloader pictures

http://i.imgur.com/w52Ww4A.jpg

http://i.imgur.com/7e5mggz.jpg

http://i.imgur.com/wjO8r8d.jpg

http://i.imgur.com/MXZpnpE.jpg

http://i.imgur.com/9r8gB7Z.jpg

http://i.imgur.com/DnKPCKJ.jpg

At first glance, they look similar. HOWEVER, if you look into the dark part of the images, you will notice something different in UBL compared to LB. There is a lot more 'digital noise' present in ULB pictures. What I'm talking about is random green/red pixels in the dark area that the BIONZ processor (or whatever else) removes in locked bootloader state.

EXAMPLE 1

Left is LB, right is UBL. You can notice the difference immediately in the blacks of my PS3. There is noise present in the UBL part that is NOT present in the LB part. Picture quality is NOT compromised, both are about equal sharpness, however LB looks considerably better because of the lack of 'digital noise'.

Example 2

Again you can see a greenish hue on my heater with some of that noise that is not present on the left LB picture.

Example 3

Look at the blacks of my HP box. Again there is that random green/red noise on the UBL pictures that isn't present in the LB picture. LB picture is also slightly sharper but that could be a coincidence.

This isn't a one time occurrence.. This 'digital noise' exists in ALL of the 6 UBL shots I took, and it is NOT present in my LB shots. In daylight the difference is negligible, but in low light the difference is evident. That noise reduction that occurs, whether it be through BIONZ or whatever else, is not present in UBL shots. This results in lower picture quality especially in low light. I don't know what is removed, but there is a definite difference between the two.
[Xperia Z1 General] fer2503:
Thanks for your test, i don't understand why sony do this difference and don't make a fix
[Xperia Z1 General] Jonas740:
Sony

I have an ongoing discussion with a Sony employee and he says this about bootloader: "The only thing i know of is that the camera stopped working in Z1 if you unlocked the bootloader before it was officially supported." And this has been fixed.

From personal experience and from reading alot about ongoing problems. It´s pretty random what would cause that some get no difference in photos with UB or LB, and some get huge differences.

Sony aint super keen on discussing theese matters and you really have to PULL info out of them and even then you aint really getting a solid answer. The answers you get are always "bendable".

Wouldnt a normal company say like " Sorry dear customers, we know we have issues atm and we are trying to solve it ASAP. The issues we noticed are the following etc"

/Jonas
[Xperia Z1 General] omegastarr:
Great job [MENTION=3721363]kantk20111[/MENTION] ! This is what a smart man does. I think "that" and I can prove it - "look". One of the best posts I've seen for a long time ! I also noticed the same thing on my Z1c and the camera is the only reason I won't switch to cm/aosp. After all we have a great sensor with LOTS of potential and it's just the software algorithms that prevent us from taking even better pictures. I'm sure we'll see massive improvements in future android upgrades !
[Xperia Z1 General] pranii23:
Tap the potential?

Imagine the same sensor with Nokia algorithms!!

Wouldn't it be stunning :D

I have a doubt, If anyone saw OnePlus One phone's camera capabilities, especially color reproduction and its HDR vs Z1.....

Can the software in it be ported to CM11 as Oneplus runs CM11!!
[Xperia Z1 General] Jonas740:
I tried this for myself now since I had a hard time understanding what the difference is.

Anyways, I shot similar photos like you did, quite alot of black things in the photo. And my ones look just like your locked bootloader ones.

My phone has been unlocked once but is now relocked with flashtool. Meaning I don't have the DRM keys present.

Stock firmware,.757 and not rooted.

I haven't tried this with UB though.
[Xperia Z1 General] yasser707:
Look at the colors on example 1 and 2

In UBL is better
[Xperia Z1 General] kantk20111:
Color balance is random. It's sometimes better on LB, sometimes on UBL. LB is better in lower light areas where UBL camera does not apply noise reduction resulting in the 'digital noise' in my pictures.
[Xperia Z1 General] dnzdeniz:
There is no much change in back camera.

But, front camera gets really worse. It gets noisy so much.
[Xperia Z1 General] Anonymuszymus:
I did a petition about this thing http://xdaforums.com/showthread.php?t=2896647
[Xperia Z1 General] user822:
I myself recently went from Stock LB to Cyanogenmod UB and have to say the camera is still really good in low light situations.

Maybe it is just me, but I like to keep as many details as possible in a picture (be it noise) and if I really want I can still enhance it on my PC later.
[Galaxy S III Mini Q&A, Help & Troubleshooting] droidboy29:
Really liked this option on some of my other galaxy phones. Dont know why samsung does not just put a notification light on all there phones its annoying.
[Galaxy S III Mini Q&A, Help & Troubleshooting] efaustino84:
none that i know of

samsung design their phones based on market research so they probably found the number of people that cared about BLN control was not that high
[Galaxy S III Mini Q&A, Help & Troubleshooting] Aronuser:
/edit: oops i thought you mean s3 mini

cm11 novafusion for example has backlight notification enabled by default
[Galaxy Tab Q&A, Help & Troubleshooting] Darkergothic:
In short, there is a huge need for a for a GTP31xx kernel with Fast Charge patch as that would dramatically increase recharge speed!
[Samsung Galaxy Star] ArshArora:
No News of cm ???

Any. Developer not fixing bugs ?

:( :(
[Samsung Galaxy Star] insomaniacdev:
No buddy,

No developer is working on cm :(

Just call me Rahul :cool:
[Samsung Galaxy Star] ArshArora:
[emoji22]
[Samsung Galaxy Star] aroradevesh:
Emoji

Hey how did u put that emoji??
[Samsung Galaxy Star] ArshArora:
Lol
[Samsung Galaxy Star] akshaygalaxystarmod:
:-p

click thanx if u helped
[General Topics] frax:
Hi,

I have a vague memory of a setting for my Magician (win mobile 2003) where one configures the phone number format to not use parantheses in random places (as if they were north american area codes). I would like to place dashes and parantheses where I like!

Any tips... ?
[General Topics] Rudegar:
look if the regional settings is set correct
[General Topics] frax:
thanks, that helped it, I had it set to a tweaked US setting.

Does anyone know, btw, where the regional settings are located in the registry... ?
[General Topics] levenum:
Regional settings are taken from a file called wince.nls, not from the registry.

You can however put overrides in the registry to replace some of the nls settings.

Search this forum for nls override, there was a big post on all available strings to put there.

The key to look at is:

HKEY_LOCAL_MACHINE\nls
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordblue969:
I have an i747 and after a week of research and trail and error I was able to get back to a factory working phone. I wanted to share my findings so that the next person may get up and running a bit quicker. First off, my phone was never rooted. I was getting it ready to sell and was going to factory reset it when I realized I forgot the system password. So I installed Kies and proceeded to factor rest it there. For whatever reason the reset did not take and after several failed attempts with kies the phone began to boot in ODIN mode. I built a USB jig and was able to get back into download mode but nothing would bring it back to life. Downloading the official rom from sammobile and flashing with ODIN3.07 would fail every time. Emergency recovery in kies also failed. So here was my final approach that worked. Maybe the wrong way to do this, maybe the long way to do it.. IDK.. but it worked for me..

1) get the official Samsung files from kies (google -"does kies store firmware")

2) boot do download mode

3) flash CSC file with auto reboot and F. reset time checked

4) boot do download mode

5) flash PDA file with auto reboot and F. reset time checked

6) boot do download mode

7) flash Modem file with auto reboot and F. reset time checked

* I closed ODIN between each step, might be overkill.

** I did not flash the bootloader file

I have read that it takes a long time the first boot, and I have been waiting 15 minutes at the SAMSUNG screen but it is still pulsing so i think it is still processing. If it is still at this screen in the morning, I will let you all know but this is further than I have been in over a week.

On a side note, when it crashed I took this into AT&T they told me over the past month or so they have seen numerous people with the same issue. All from doing a factor rest in Kies. My phone was out of warranty and they barely looked at it before asking me to upgrade. I took it to BestBuy and they fixed it from booting to ODIN mode but it still locked up on the AT&T logo, so I was back to square one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
Food for thought. How about waiting to see if your instructions actually work on your phone before posting them here for people with similar issues to use. Kind of useless if it doesn't end up working, huh?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
Seems a pretty long route to take. If you are on an Odin flashable firmware version (e.g. 4.1.1), you only need to flash one partition - PDA. This updates all partitions to stock including bootloader, modem, recovery, kernel. The newer firmware versions - 4.1.2 & 4.3 are, however, not Odin flashable. Also, if you couldn't do a factory reset from settings because of password issues, you could have booted into recovery mode and done a factory reset there. This wouldn't require a password and would still have the same effect of wiping data and returning to factory settings.

If your phone is stuck at the Samsung screen for 15 minutes, then it's stuck. Reboot into recovery mode and try a reset there. If this doesn't work, then it means you have a soft brick you need to restore your firmware via custom recovery. Your phone is never hard bricked when you can get to download and recovery modes. Flash custom recovery via Odin in download mode. Reboot to custom recovery and flash a clean, complete stock image for 4.3. That's your best option now since you are selling
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordblue969:
So like the true repository of knowledge we have here, Larry you are correct.. After about 30 minutes I decided it was really stuck.. So this time I watched the process I described above a bit more closely and as you stated the PDA file is all i needed.. but I had tried several from different sources including the office from sammobile and they always crashed. So what eventually worked for me was after being stuck at the samsung logo...

I booted into recovery mode

wiped the cache

factory reset it

then flashed with the Kies PDA file that I obtained in Kies in emergency recover mode.

This finally worked.

and as stated was a shorter route to take. The PDA that i used had 4.1.1 on it.

Thanks for the clarification in the fact that flashing with the PDA takes care of the bootloader, cache, file system, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordblue969:
excitement over came me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordblue969:
Still having issues

Ok, keepers of knowledge.. I have a phone that will boot up but I have no baseband version. It shows unknown.. I have tried just flashing the modem file but i still do not get it back.. if I try to flash anything other than the official files from kies, ODIN fails. My phone is now at 4.1.1, build JR003L.I747UCDLK3.

If I try to update via wifi with the software updater, it says I am up to date. If I try to update with Kies, it fails..

I am at a loss...

Please help..

Thanks in advance..
[Galaxy Grand Duos i9082 Android Development] jayc137:
Aki.kernel is a kernel created by me to further enchance Grand's performance on AOSP based ROMs like CM11, AOSPA, PAC, etc.

It places emphasis on increasing performance through frandom module, SIO Scheduler and smartassv2 governor.

Ain't nobody got time for that.

Features

- Frandom support.

- ULTRA KSM

- zRAM

- Dynamic FSync

- XZ Compression

- F2FS support

- Smartassv2, Pegasusq and Adaptive governor.

- SIO Plus,VR and ROW Scheduler.

- Compiled with Linaro 4.7.4 toolchain.

-O3 Optimisation flags used. (from ver. 1.1)

- OC upto 1.5 Ghz

XDA:DevDB Information

Aki.Kernel AOSP (4.4) , Kernel for the Samsung Galaxy Grand Duos i9082

Contributors

akiratoriyama, androidbaba

Kernel Special Features: I love testing and creating stuff for myself and my fellow members. Here's a kernel for all ya flasoholics.

Version Information

Status: Stable

Current Stable Version: 2.3

Stable Release Date: 2014-05-31

Created 2014-04-18

Last Updated 2014-06-22
[Galaxy Grand Duos i9082 Android Development] jayc137:
Reserved

Downloads

Every version of my kernel is available on AndroidFileHost

http://www.androidfilehost.com/?w=files&flid=13908

Performance control (credits [MENTION=4674443]h0rn3t[/MENTION])

http://xdaforums.com/devdb/project/?id=600#downloads

Source

https://github.com/akiratoriyama/android_kernel_samsung_i9082/

Don't expect too much.
[Galaxy Grand Duos i9082 Android Development] jayc137:
Reserved

Changelog

Version 2.3

- Added SmartassH3 governor.

- Merged some changes from [MENTION=3117667]pawitp[/MENTION]'s sources.

Version 2.2.1

- Compiled with Linaro 4.7.4

- XZ compression for small Kernel file and better performance

- Increase Max READAHEAD for better performance.

- staging: Add Snappy compression library (v3).

- Network speed increased.

- Sched Tweaks to improve performance.

Version 2.2

- Substantial performance and battery optimizations.

- Now compiled with GCC 4.6 instead of Linaro.

Version 2.1

- Dynamic FSync

Version 2.0.1

- F2FS support added.

- Fixed deletion of modules

Version 1.6

- Added SIO Plus scheduler

- Disabled Pegasusq governor for the the time being.

- Removed scsi_wait_scan.ko module

- Add RCU Boost

- Increased Entropy

Version 1.5.1

- Reduced WiFi wakelocks.

- Added Pegasusq governor.

- Added Performance Control app.

Version 1.5

- Added Ultra KSM.

Version 1.4

- Added VR and ROW scheduler.

Version 1.3

- Reverted O3 optimisations for a stable kernel.

- Added zRAM with a swapiness of 60.

- Now based on AnyKernelUpdater by Koush and modified by [MENTION=5456406]CoolDevelopment[/MENTION].

Version 1.2

- Added adaptive governor.

- Cleaned some code and improved stability.

Version 1.1a

- Fixed FCs.

Version 1.1

- Added O3 Optimizations .

- Removed Underclocking.

Version 1.0.2

-Added Experimental Underclocking.

Version 1.0.1

- Added Experimental Overclocking.

Version 1.0

- Based on CM Defconfig.

Below Version 1.0

- Created for personal testing only

CREDITS

YOU for testing and using this kernel.

[MENTION=943196]k2wl[/MENTION] For helping me and guiding me.

[MENTION=3117667]pawitp[/MENTION] For his kernel source.

[MENTION=5273865]xenon92[/MENTION] For responding to a query and also used much of his Nebula Kernel code.

[MENTION=5367286]TripRex[/MENTION] For much assistance and used some of his Project Kernel code too.

[MENTION=4082678]sweetnsour[/MENTION] My primary inspiration for building a kernel :D

[MENTION=1357470]androidbaba[/MENTION] For extensively testing the early builds of Aki.Kernel.

[MENTION=4576707]Ryuinferno[/MENTION] for Frandom module.

[MENTION=4825437]Christopher83[/MENTION] For his Kernel commits and also his Linaro toolchain.

[MENTION=5456406]CoolDevelopment[/MENTION] For his ver. of AnyKernelUpdater and also used some of his commits from MoshKernel.

[MENTION=4717890]coldsorrow[/MENTION] For Ultra KSM.

[MENTION=4674443]h0rn3t[/MENTION] For his Ultra-awesome Performance Control app.

[MENTION=4615478]boype[/MENTION] For his commits from Fancy Kernel.

[MENTION=3332811]faux123[/MENTION] For Dynamic FSync.

Galaxy Grand Testers Group

Galaxy Grand Developers Group
[Galaxy Grand Duos i9082 Android Development] tazo08:
link asking for login??? :P

support dual sim??

made an acc thn the link specified acces denied
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
Download Link is asking for login.....:(
[Galaxy Grand Duos i9082 Android Development] mukeshpacheria:
Log in

when

downloading:p
[Galaxy Grand Duos i9082 Android Development] jayc137:
[MENTION=5443112]tazo08[/MENTION] [MENTION=5806395]supersaayuj[/MENTION] and [MENTION=5156741]mukeshpacheria[/MENTION]

Links fixed.
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
Taking a nandriod backup currently..will flash the kernel..and test it throughout the day ;)

BTW thanks for this kernel! :good:

EDIT : Unfortunately, the process com.andriod.phone has stopped ?? :(

Wiped dalvik cache and cache before install...on cm11 latest build..not using dual sim!
[Galaxy Grand Duos i9082 Android Development] RIPPER:
Grrt wrk buddyyy...will test and report:good:
[Galaxy Grand Duos i9082 Android Development] jayc137:
Using ART ?
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
help plzz:(
[Galaxy Grand Duos i9082 Android Development] androidbaba:
Which version you are trying??
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
1.1

---------- Post added at 11:23 AM ---------- Previous post was at 11:21 AM ----------

NO
[Galaxy Grand Duos i9082 Android Development] jayc137:
[MENTION=5806395]supersaayuj[/MENTION]

Use ver 1.0
[Galaxy Grand Duos i9082 Android Development] RIPPER:
Force close is only at starting...after that it is working smooth.(till now)

Will update with further testing:good:
[Galaxy Grand Duos i9082 Android Development] jayc137:
Anyone who is using facing FCs please use ver 1.0.1.
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
my all connections gone....like wifi...calls..it was in airplane mod...as u can see in the screenshot

---------- Post added at 11:52 AM ---------- Previous post was at 11:43 AM ----------

Not facing fc on v1.0 :laugh: :highfive:

What are the best config to use on this kernel....like ondemand..cfq ?
[Galaxy Grand Duos i9082 Android Development] jayc137:
Use smartassv2/interactive with 800-1200 for medium performance.
[Galaxy Grand Duos i9082 Android Development] RIPPER:
Don't Spam..everything is working for me:good:
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
LOOOL:D... i was not spamming...i know everything works for u...but not for me..so asked a little help ;)
[Galaxy Grand Duos i9082 Android Development] supersaayuj:
Whats the Difference between Linaro & GCC Toochain?

I mean ...in performance wise...
[Galaxy Grand Duos i9082 Android Development] jayc137:
GCC is the standard toolchain under which most ROMs/Kernels like those of CM are compiled.

Linaro is a new toolchain and it is said to have better performance and battery life than GCC.

I find the difference between Aki.Kernel compiled by GCC and Linaro to be negligible, not to mention GCC is stabler.
[Galaxy Grand Duos i9082 Android Development] xenon92:
Just don't make it "too much" as mine! :)

By the way, I was looking at your commit history and your source. I would like to suggest something that would help you better manage the kernel source. When you cherry-pick commits from mine or k2wl's source, try to rebase it based on your source before finally committing it. That way you'll not get ">>> HEAD" thingy, which we all hate.
[Galaxy Grand Duos i9082 Android Development] jayc137:
[MENTION=5273865]xenon92[/MENTION]

I was just testing how cherry-picking works by using commits from your kernel :P. I will take care of my source now.

Thanks for your suggestions :)
[Galaxy Grand Duos i9082 Android Development] fakhruddin.razi:
How to configure the settings I mean governor and io will be best for battery backup ? Please provide

---------- Post added at 05:03 PM ---------- Previous post was at 04:23 PM ----------

Its giving me only 1% for 4 min using adaptive , sioplus and 1200mh-- 312mh. ® very very sad:(

---------- Post added at 05:20 PM ---------- Previous post was at 05:03 PM ----------

Please add galaxy grand undervolting
[Galaxy Grand Duos i9082 Android Development] fakhruddin.razi:
Hello dev how much screen on time you are getting on grand with. Your kernel?
[Galaxy Grand Duos i9082 Android Development] jayc137:
5-6 Hours maximum on CM11 with my kernel.

If you want good battery life I'd recommend Cosmic CM by [MENTION=943196]k2wl[/MENTION].
[Galaxy Grand Duos i9082 Android Development] fakhruddin.razi:
Hello dev battery discharging very early please just fix it in next build

And how do you get such long screnn on time?