yashsingh1/xdaforums huggingface dataset:
[Xperia Z Android Development] BrateloSlava:
How to small decrease the value of Auto Brightness on the next RR build

Range of display brightness - from 0 to 255. The current minimum brightness value - 10. I have made some changes to the kernel, which allows to reduce the brightness.

Two parameters:

lm3533_bl_reduction - determines the value of reduction Auto Brightness

lm3533_bl_brightness_min - defines the lower threshold for the reduction Auto Brightness

Explained by the example.

I want, that the brightness decreased by 9 units. But only, when the actual brightness is not more than 30. That is, I want to display has been more dim in low light, and the "normal" - at other times.

Result. Add this lines in your init script:

if [ -e /sys/module/leds_lm3533_ng/parameters/lm3533_bl_reduction ]; then
echo "9" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_reduction
fi;

if [ -e /sys/module/leds_lm3533_ng/parameters/lm3533_bl_brightness_min ]; then
echo "30" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_brightness_min
fi;
[Xperia Z Android Development] Nameless One:
I would imagine the new blobs would be of much greater use with the newer kernel source to use them with, whenever Sony get round to releasing it.
[Xperia Z Android Development] airlessproject:
I think [MENTION=4422297]mohdsubaie[/MENTION] had the below in mind, because it was written in the post just before his.
[Xperia Z Android Development] airlessproject:
New build 05/25

changes:

- LP updated to 5.1.1_r3

- RR/CM/LP sources synced with latest commits (05/25)

- (ROM) Reverted some erroneous code for setting charging/notification LED color.

- (ROM/device) Hopefully fixed external storage (USB OTG) - not yet tested due to lack of needed hardware.

- (kernel) Imported the shiny new bootlogo from Sony stock LP FW.

- (kernel) Switched to -Ofast instead of -O3 build optimization flag.

- (kernel) Rewrote the algorithm for decreasing the value of Auto Brightness. See here for details/how-to.

- (kernel) Made all remaining kernel modules built-in.

- all other changes can be seen in my github sources.

AFH Download

Cheers! :cowboy:
[Xperia Z Android Development] AndreasDay:
Two quick questions, probably something small im missing.

In Privacy guard I no longer have root access options for each app, instead i have to use SuperSU. Is there a way to get the root control options back into Privacy Gaurd rather than having to use SuperSU?

And also(not exactly rom related) but using TWRP to format my data to F2FS fails every time. Any ideas why?
[Xperia Z Android Development] zakitheracer:
Tried the latest build and unfortunately USB OTG is still not working [emoji20]
[Xperia Z Android Development] Artyomska:
Regarding the SuperSU problem, the only way I know to eliminate it from your ROM is to make a completely clean flash (Wipe cache,system,data) and, obviously, don't install it again.

And regarding the TWRP problem, are you using the official build or the one made by Olivier? From what I know, the original version of TWRP doesn't support f2f (someone correct me if I am wrong).

---------- Post added at 16:10 ---------- Previous post was at 16:03 ----------

Also thank you for the new build :) . It seems that the desktop and app drawer lag I experienced is gone (maybe because of the new optimization flag).
[Xperia Z Android Development] BrateloSlava:
Maybe, this because we squash some patches for launcher from CM team.
[Xperia Z Android Development] airlessproject:
This is actually great news :)

Next step - ask this at RR's G+ and/or CM github or idk.
[Xperia Z Android Development] airlessproject:
I think data doesn't have to be wiped for this, wiping /system is enough (to avoid SuperSU addon.d survival). Then, just uninstall the app itself (not functional anyway)
[Xperia Z Android Development] BohArie:
nice one bro.. thnks for ur work bro.. kindda love RR because of ur work.. keep ur good.. ops not good, I MEAN AWESOME!!!!
[Xperia Z Android Development] zakitheracer:
Couldn't it be kernel related cause it was working perfectly in 11/5 build

Also in the latest build the colors are a bit too warn IMO
[Xperia Z Android Development] airlessproject:
here and here are kernel commits since May 11. I don't see anything that could cause this issue. If you do, please inform me of it.

About colors, you can always use kcal control to make them cooler or warmer. This temperature was chosen for Sharp displays to make it by default closer to even with that of other display.
[Xperia Z Android Development] zakitheracer:
This one

https://github.com/airlessproject/kernel_apq8064/commit/ddc48e74114bce6ba235f09e62fb77d757c2e5c7

As you seem to have disabled a lot of USB host related stuff in this
[Xperia Z Android Development] airlessproject:
that in which you see USB stuff disabled is a full deletion of an unused defconfig, kma_fusion3_yuga_defconfig.

what you need to look in is this defconfig.
[Xperia Z Android Development] schorsch.funke:
It is there, you must look under advanced
[Xperia Z Android Development] airlessproject:
I still think he meant what I and [MENTION=5626906]DragosBad[/MENTION] talked about, root access for apps to be taken care of by Privacy Guard.

Advanced app permissions are available with or without SuperSU installed.

You and I, zaki, might have solved this usb-otg problem by accident, just as it was created :) I'll know this by tomorrow :fingers-crossed:

Expect the fix (if it is what I think it is) in the next build or in a kernel bugfix build soon.
[Xperia Z Android Development] AndreasDay:
Yes this is what I meant. The settings were gone after a clean install, had to install SuperSU app, the app informed me that the binary needed to be updated. Tried to update the binary and it wouldnt work so I manually extracted the update SuperSU binary zip from a previous backup and flash it to get a working binary.

Now SuperSU works, but no settings in Privacy Guard as before.

Is there a way to get them back?
[Xperia Z Android Development] airlessproject:
s

If you didn't install SuperSU addon.d script (check SuperSU app -> Settings -> Custom ROM -> Install SuperSU backup script, should not say "Script is already installed"), just uninstall SuperSU app and dirty reflash ROM (only clean cache+dalvik).

If you did install the addon.d script (the said setting says "Script is already installed"), first uninstall SuperSU app, then either go to /system/addon.d with a root-enabled explorer and delete the file "99-supersu.sh", and dirty reflash ROM, or in recovery, wipe system and cache+dalvik, then reflash ROM and Gapps if needed.
[Xperia Z Android Development] AndreasDay:
That fixed the problem Yeah. Thanks
[Xperia Z Android Development] airlessproject:
Ok friends I'm going to do a little unofficial survey for something I started to notice after I used Auto Brightness for a day or so, and was also reminded by [MENTION=2894202]zakitheracer[/MENTION]:

- Sharp display users: do you like the current default color temperature on your display? Have you noticed a big difference, especially a subjectively negative one, in the last two builds?

When Adaptive Brightness is on, I started noticing the colors being a bit too saturated, especially in low-light situations, but this could only be my subjective and objectively wrong impression, and that's why I ask you about this.

Of course I can easily revert back to the previous color temperatures, so if enough of you think this should be done, please state so during the next few days, and I will fix this in the next build.

Thanks in advance!
[Xperia Z Android Development] TrueFriend-cz:
I have problem with this and Validus ROM. If turn off display then after 1-2 mins hard disconnect wifi. After screen on reconnecting to wifi. Sleep WiFi function is not activate.
[Xperia Z Android Development] ratworks:
I haven't thought about this in terms of the color temperature - rather I've had trouble maintaining a good level of brightness in the last two builds. Before then, I pretty much never changed the brightness - it all seemed to kept itself just where I wanted it.

Now, it's often a bit too dim, or a bit too bright, I just can't find that one setting that I can leave it at.

Previously, walking to work and reading in bright sunshine, or lying in bed reading, in complete darkness, it all adjusted itself to a good setting.

But, as you say, it's all very subjective - a bit like the air conditioning temperature at work, which is never quite cool enough :)

Thanks for asking!
[Xperia Z Android Development] zakitheracer:
Instead can't we have two versions of the kernel?

As color temperature is a personal choice which differs from person to person.
[Xperia Z Android Development] airlessproject:
Thanks for the answer, [MENTION=3756395]ratworks[/MENTION].

The Auto Brightness issue has unveiled itself as a consequence to a hack allowing lowest possible overall minimum brightness level.

To correct this, our friend [MENTION=4842205]BrateloSlava[/MENTION] has made some changes to that hack, allowing users to choose at what level of actual brightness should it be lowered than usual.

This is described as a how-to in his post just before the changelog for the 05/25 build, and basically says that one can make an init.d script containing the following:

if [ -e /sys/module/leds_lm3533_ng/parameters/lm3533_bl_reduction ]; then
echo "9" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_reduction
fi;

if [ -e /sys/module/leds_lm3533_ng/parameters/lm3533_bl_brightness_min ]; then
echo "30" > /sys/module/leds_lm3533_ng/parameters/lm3533_bl_brightness_min
fi;

This means that whenever actual brightness is below the value of 30 (which is quite dim), it will be reduced ; or in other words, lowest minimum brightness will only be reduced in low-light situations.

I have used this in an init.d script and it makes Auto Brightness act pretty normal, while also having a lower minimum.

Thanks for the response, [MENTION=2894202]zakitheracer[/MENTION].

To be honest, I really wouldn't split the kernel in two branches just for this, imo, small reason.

The question was whether to keep the defaults at the new values, or revert them.

Anyway, as one can always use a Gamma/Kcal adjustment app like Kernel Adiutor or FauxClock, I've decided to revert them, since the majority of users won't bother to adjust colors and the defaults were a bit too warm.

So in the next build, defaults are going back to usual Gamma values for Sharp displays, and whoever wants warmer (or cooler) color, can easily do that by using adjustment apps.

Btw, for the next build, among the changes are:

- fixed USB OTG, now also allowing mounting of NTFS-formatted media;

- a possible fix of MHL/Screen Cast, which now only depends on ROM support of the said features, with the kernel part of it being fully done;

- disabled the outdated intellidemand governor which also became unusable in the last build and has solid alternatives in intelliactive/elementalx/uberdemand/ondemandplus;

- various security and performance-related patches, and more is to be done in the few next days.

The new build will probably be out whenever enough bigger changes pile up at the RR/CM/LP sources, so stay tuned..

Regards friends!
[Xperia Z Android Development] zakitheracer:
[MENTION=5396196]airlessproject[/MENTION] RR 5.4.6 is out

So when can expect this update?[emoji16]
[Xperia Z Android Development] airlessproject:
Very nice, asking eta and getting away with a smiley :D

Actually, I need only to write changelog and make a post, the build is ready since last night, I tested it and it's good for me at least.

Will post the build today.
[Xperia Z Android Development] airlessproject:
New build 05/30

changes:

- RR updated to 5.4.6

- RR/CM/LP sources synced with latest commits (05/30)

- (ROM/device) Adreno: changed blobs from Mako to Sony (.454)

- (ROM) Fixed setting Vibration Intensity in RR settings

- (kernel) Added support for storage with NTFS/FAT FS and refined support for VFAT/exFAT ones

- (kernel) Reverted patch for Sharp panel's gamma calibration

- (kernel) Removed FSync/Asynchronous FSync/Dynamic Fsync Control

- (kernel) Removed buggy and dated intellidemand governor.

- (kernel) Modified code of the end of the procedures to ARMv6+ recommendations. More about this here

AFH Download

Greets to all! :)
[Xperia Z Android Development] zakitheracer:
USB OTG works in the latest build! [emoji16] [emoji16]
[Xperia Z Android Development] schorsch.funke:
Hi, why do you remove the fsync kernel control?

Thanks for your continous hard work.
[Xperia Z Android Development] airlessproject:
My pleasure :)

The implementation of dynamic/async/plain fsync control that was used wasn't as good as was expected, and was causing some FS errors in some cases. This could be a temporary removal and fsync control may soon be re-added using other code.

Yes and you had a part in that. Thanks mate :)
[Xperia Z Android Development] BrateloSlava:
We must also remove Intelli_thermal and make some changes for stock msm_thermal. Some test result "says", that Intelli_thermal - not fully compatible with us. At least in the current implementation - for sure.
[Xperia Z Android Development] Cr33D OrB:
THANKS [MENTION=5396196]airlessproject[/MENTION]

MIRACAST (AND OTG) WORKING ON LATEST BUILD!

HOPE that stays so.. :)
[Xperia Z Android Development] TrueFriend-cz:
I have problem all build with Wi-Fi. If screen off after many seconds turned Wi-Fi off and reconnecting if screen on. In Wi-Fi settings i selected Wi-Fi if screen off Always ON. Where problem? Can you fix dev's? Thanx
[Xperia Z Android Development] acutraaq:
Nice boot animation...
[Xperia Z Android Development] Ghost ic0n:
Can anybody confirm that with the implementation of .454 blobs, the no incoming/outgoing voice in calls bug is gone?
[Xperia Z Android Development] BrateloSlava:
How anyone can confirm, if there is no source code? And not known, how to work with these blobs.
[Xperia Z Android Development] airlessproject:
In the latest build I have so far imported only Adreno .454 blobs. The rest should follow when we have the new kernel source code. Then we will probably know if that issue is gone, although I don't know why, but I never had that bug in my phone usage with my RR 5.1 builds, and no one so far has stated how it can be reproduced so it could be debugged.

Too bad they changed it again earlier today. I like yesterday's better so I might revert the replacement and continue using that one.
[Xperia Z Android Development] zakitheracer:
[MENTION=5396196]airlessproject[/MENTION] For the gamma could you merge this commit?

https://github.com/daeiron/android_...mmit/5a5b9db3b55a15bf884020d9dcd22638de2afeb1

As this were the values which were used in the CM11 builds of Thomas and afterwards in the official CM11 builds after merging of the CM11-new kernel and IMO these are better than the stock values but not too warm like the one which was reverted
[Xperia Z Android Development] Ghost ic0n:
Ah, I see. I didn't know Sony hasn't released the official kernel source code yet. I'm pretty sure that once they do, implementing the Sony blobs should do just the trick to fix it as I'm not getting the bug on Sony's official Lollipop release.
[Xperia Z Android Development] cagdas:
Recovery

Thanks for the nice rom, I tried my best to read most of the post and search the tread for recovery but couldn't found what I was looking. I was using dual recovery before this rom As I can see the dual recovery cause a boot loop in lolipop till we get a fix. After I installed this rom I got Cyanogen recovery which is fine, but I can not install anything it either says the it cannot access the sd or if I use a zip in the internal storage it says footer is wrong and signature verification failed. I did not see any place to toggle signature off in the recovery.

Sorry for the noop question am I not seeing the elephant in the room .
[Xperia Z Android Development] airlessproject:
From the OP:
[Xperia Z Android Development] mohdsubaie:
Download twrp manager or rashr from playstore, download the latest twrp recovery image for yuga from their site and flash it using twrp manager or rashr.
[Xperia Z Android Development] cagdas:
Thanks for the quick response, will try soon.

---------- Post added at 11:07 AM ---------- Previous post was at 10:40 AM ----------

Well it worked thanks and sorry for not reading the instructions thoroughly.
[Xperia Z Android Development] BohArie:
Bro Airless, this rom still daily use for me.. coz it is awesome.. haha.. keep up ur Awesome work!
[Xperia Z Android Development] nihilista:
Hi, testing this ROM for last 10 builds and its getting better and better. But only one thing: Needs much time till getting screen for pin at boot. I thought it has been fixed some builds ago, but on newest builds its the same.

Any fix for that?

Thx
[Xperia Z Android Development] Cr33D OrB:
Yeah same here :|
[Xperia Z Android Development] airlessproject:
Hi,

how much time does this take for you approximately?

I just tried setting SIM PIN, and it took no more than 10 seconds after first appearance of UI/lockscreen until I got the PIN unlock screen.

I compared this to a clean flash (without Gapps), where carrier registration (not a pin request, but essentially the same) takes less than 2 seconds to complete - it would mean that some of the startup apps when one has lots of apps including Google's, may be delaying SIM carrier registration by some 7-8 seconds.

This certainly isn't a deal breaker for me, and if for you it is somehow a lot longer than the ~10 seconds I get with app data, maybe trying a clean flash and testing the lag you'd get there would provide some insight into this.

In earlier builds there was a bug with kernel-side modem activation but that was solved and as proof I'll mention clean flash without any apps again, where there's virtually no lag at all.

You can also first try re-choosing automatic network carrier selection after searching for carriers, set again the preferred network type, and reboot to see if this persists.
[Xperia Z Android Development] nihilista:
Hey, it does not take very long, i get my lockscreen, unlock it, launcher starts, so maybe 15-20 sec. Not too much, but with my other rom (slimkat) and all kitkat rom's before i can type my pin instantly after ui start, just before lockscreen comes up. Not a big thing, but a noticeable difference to kitkat rom.

thx
[Xperia Z Android Development] airlessproject:
No prob, but you can still try re-enabling automatic carrier selection and re-selecting network type.

Also there's a workaround for this, that takes a few taps to complete: 1) bring down quick settings tiles; 2) long tap on Network/Data tile 3) close settings.

It will register carrier immediately like this, and also bring up pin request screen.

Still I don't know why on clean install none of this is needed and the issue is not present..
[Xperia Z Android Development] mohdsubaie:
[MENTION=5396196]airlessproject[/MENTION] incase you haven't seen this already source code been released by Sony

http://developer.sonymobile.com/dow...rchives/open-source-archive-for-10-6-a-0-454/
[Xperia Z Android Development] Vmo x:
recovery keeps switching to CyanogenMod Recovery, How can i stop this? Can you give me the kernal Link please so i can flash it
[Xperia Z Android Development] v7:
Flash the recovery in fota partition.It'll survive ROM flashes.

Copy the recovery img to sdcard and execute the following commands via Terminal Emulator

su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
[Xperia Z Android Development] airlessproject:
Of course I've seen it.. :)

I will try merging it into my kernel these days but as simple as it sounds, likewise hard it can get, and there probably will be many things to be taken care of. Also along with this, the rest of the blobs need to be imported, and there may be some trouble in that department too..

I'll do my best to make everything fine and you folks can expect a build implementing new stock stuff in not too long from now.
[Xperia Z Android Development] mohdsubaie:
Awesome thanks mate!
[Xperia Z Android Development] schorsch.funke:
Remember there is also a private live . So don't work to hard, we can wait. For me everthing is working fine!
[Xperia Z Android Development] zakitheracer:
In the latest build when taking a screenshot of a HEVC/x265 video or when exiting from that video there is a color distortion of sorts

Is this because of the new Adreno blobs as it wasn't present in the previous builds

Although this doesn't hinder the actual viewing of the video but still is a bug
[Xperia Z Android Development] chintu_2000:
Service Menu not working

yesterday my Xperia Z - 6602 accidentally slipped from my child's hands. there is a long hair line crack in the touch digitizer. :crying::crying::crying:

i wanted to check the touch by using the SERVICE MENU from *#*#7378423#*#* as i am getting little problem in touch (because of hair line crack i think so).

So i was trying for service menu but in vain. nothing comes after *#*#7378423#*#*. I just want to check if my digitizer is working properly or not.

Can anyone help me in this...??:confused:

I have an unlocked bootloader with the latest build installed
[Xperia Z Android Development] v7:
This is a development forum.You can move your post to the Q&A thread HERE.

Thanks.

Tapped from my furious dogo ;)
[Xperia Z Android Development] mohdsubaie:
Download xperia diagnostics app from playstore and test your screen
[Xperia Z Android Development] chintu_2000:
Sorry
[Xperia Z Android Development] Olivier:
It's actually not hard, I've already done it - was just a matter of diffing stuff (beware though, untested!): Cherry-pick everything after the CAF LA.AF.1.1_rb1.18 merge from here. Should that be too hard, try again with the pure Omni kernel (branch lp5.1 of the sony-fusion3 kernel).
[Xperia Z Android Development] airlessproject:
Thanks Oli mate for the advice, I'm only now seeing it after I already managed to accomplish something with the kernel :) it is not a 100% conventional merge as it should be but I had to make some compromises in order to save myself some time.. but however it boots and so far testing goes alright.. I was also just about to tell you to look at the new commits, they're on branch 'test-lp'.. :)

Anyway, I was more referring to importing the remaining blobs as being potentially troublesome since the first time I tried a full import I managed to get up to the end of art cache rebuild where the boot hung the same way it did when enabling Logd.. any heads up on this import?
[Xperia Z Android Development] iDroid8:
Great ROM, it's definitely improved my battery life, I consistently get 4-4.5 hours of SOT.

However, I due have a few questions. I've had problems with the main speaker, earpiece speaker, and the microphone. I've used the Xperia Diagnostics app, and checked that the main speaker does work, but for some reason in general use, it doesn't work at all. The microphone works when making calls via loudspeaker, which is helpful considering I can't use it normally as the earpiece doesn't work, but this isn't always practical, obviously. Any ideas at all, is it a software issue etc.?

Lastly, is there a way to set permissions for which apps have access to location/internet? When I search "App Ops" in settings, it comes up as an option but then doesn't come up in the list when I tap on it.
[Xperia Z Android Development] airlessproject:
I've never had any problems with neither main speaker, earpiece, 3.5mm output, nor mic, at all. They all work as they should in all scenarios.

One small exception is, and this has been a bug with CM on yuga since forever, that ordinary stereo headphones can't be used for calls, and only a headset with a mic works for that.

App ops in RR are done by Privacy Guard's advanced settings.
[Xperia Z Android Development] Cr33D OrB:
SMALL ETA :

:)

CUZ nearly a Week (at least felt) no updates..

Thats not usual for u man !

Hah'tak Ur time :good:
[Xperia Z Android Development] airlessproject:
:)

Not very far from an update, I have only a few more things to be taken care of (and tested afterwards)
[Xperia Z Android Development] BrateloSlava:
A small notice. The update will be today. ;)