Develop Bugs

[TOOLS] Screen ColourControl, Camera Enhancements, Screen Density, Boot Anim + MORE!

GALAXY NEXUS PHONE MODS
This is all part of the Galaxy Nexus ToolKit but I have made a new Thread for people who may not have noticed it, people who didnt need the ToolKit but may find some of the Mods useful or just people who want to talk about the Phone Mods specifically.
FUNCTIONS OF THE PHONE MODS SECTION V1.4 [GSM + LTE][13TH MARCH 2012]
Change the Screen Density (DPI)
CWM Recovery, Only 1 No in the Confirmation Screen
Camera Sounds (Disable/Enable Camera Shutter, Video Camera Shutter, Focus)
Camera Enhancements (Increase Video Bitrate, Sound Bitrate, Photo Quality)
Change WiFi Scan Interval (Time between scanning for new Wifi Access Points)
Startup Boot Animation Screen (Disable/Enable which affects Boot Time)
Screen Colour Control (Change Gamma Offset and Colour Multiplier)
--------------------------------------------------------------
DOWNLOAD
The Phone Mods are part of the Galaxy Nexus ToolKit. You can download the latest version *HERE* (no need to install drivers if you already have adb/fastboot drivers installed) and select option 18 in the Main Menu to enter the Phone Mods Section.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
USAGE
STOCK ROM users will need to enter the Mods Section via the Galaxy Nexus ToolKit as most functions need an insecure boot image which is set up from the Model Selection Screen of the ToolKit. If you are running a CUSTOM ROM (with insecure boot image) then you can run the ModsSection.exe directly if you wish.
ALL Mods Section functions require you to be booted into Android and connected to the PC via usb with adb/fastboot drivers installed. If you havent done this already then refer to the Galaxy Nexus ToolKit Thread for setup instructions.
The Galaxy Nexus ToolKit and Mods Section are very tightly integrated and so is impossible to seperate the 2 parts unless I want to cut out Stock Rom users (which I dont) so please dont ask if I can split them up. I could but its just not worth it.
Lastly if you have any ideas for functions that can be added to the Mods Section or just want to discuss a particular function then feel free.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

*reserved for future use*

Already used your tool kit to root, unlock, and flash recovery!!! Awesome work you've done, it's too easy Glad to see you made a separate thread for this, I agree it got kind of lost in the original thread.
Sent from my Galaxy Nexus using Tapatalk

Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!

graymulligan said:
Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!
Click to expand...
Click to collapse
Thank you im sure your geeks learn alot from you lol
Disabling the boot animation knocks about 5 seconds off the bootup time and there are a few Roms with not very desirable graphics lol.
Please do report back I always welcome any feedback and ideas for additions.

I get an error when trying to backup the xml file...Any ideas?

Looks great . You don't happen to have a unix version?

If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
Are you using Franco kernel? Disable the fast usb charge.... Your good to go

MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
What Rom and kernel are you using?
Are you booted into Android and connected via usb cable before starting?
I dont know where the fast usb charge option is but as the previous user posted you can try to disable that and try again.
Also if you go back into the main ToolKit are you seeing the serial number under adb at the top?
Mark.

yyz71 said:
If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
Are you using Franco kernel? Disable the fast usb charge.... Your good to go
Click to expand...
Click to collapse
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot

MysticDeth said:
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot
Click to expand...
Click to collapse
Glad it went well after the reboot
Mark.

io53 said:
Looks great . You don't happen to have a unix version?
Click to expand...
Click to collapse
I do want to have versions of the ToolKit for Mac and Linux if I can get some testers and/or people who can help me convert the scripts. Im guessing most of the scripts should work fine as they are just adb/fastboot commands but there may be differences with pauses and some search replace routines.
Do linux bash scripts work on unix?
Mark.

Wow.. that's more handy..
Thanks for the nee options being included in your tool..

What exactly does the camera enhancements option do?

Any news on the camera enhancement and weather it works?

bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)

frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..

bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
The enhancement does exactly what it states on the screen when you select option 4 in the phone mods section:
This mod focuses on the media_profiles.xml file in the /etc/ folder on your phone.
The x2 Quality Settings doubles the standard camcorder bitrate for 480P, 720P and 1080P [8M, 16M, 24M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 25000000.
The Medium Quality Settings push the camcorder bitrate up even more for 480P, 720P and 1080P [10M, 20M, 35M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 30000000.
The High Quality Settings push the camcorder bitrate up to the max for 480P, 720P and 1080P [14M, 30M, 50M] as well increase the Audio bitrate up to 128k and increase the Audio channels to 2. The duration setting has also been changed to 60 from 30 for the above formats. All the quality settings for the camera have been forced to 100 and the memcap setting has been pushed up to 40000000.
These 3 profiles are for testing and I hope you get improvements using them but if you want to you can customize either of them from the mods folder and push them back to your phone.
Click to expand...
Click to collapse
As for proof that the mod works I havent taken tests shots/videos with each mod but the stock bitrates for the camcorder are a bit low so increasing it can only benefit the quality of the captured image. Whether the highest setting is neccessary or not doesnt really matter as it is upto the end user to decide if they prefer it but I would definitely recommend applying at least the 2x setting .
frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I put a compulsory backup step in every mod section so that even on custom roms the original file can be saved to your computer before it is altered and pushed back if you dont like the changes. There is absolutely no chance of screwing up the camera app as only bitrates and quality settings are altered.
MuayThaiFighter8 said:
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..
Click to expand...
Click to collapse
A NAND backup isnt needed as the file to be altered has to be backed up by the ToolKit in order to proceed so it can be easily and safely restored if the user wants to.
Mark.

Ah okay, so stills aren't affected at all?

bemymonkey said:
Ah okay, so stills aren't affected at all?
Click to expand...
Click to collapse
Does noone bother reading my posts properly lol
If you read my above post the camera quality (stills) is pushed up by pushing the modded settings.
The 2x and medium profiles pushes the 3 quality values of stills upto 100, 85 and 75 (instead of 95, 80, 70). The high quality profile pushes all 3 values upto 100 (meaning there is no compression in the images taken).
Mark.

DashClock Sleep Extension for CM/AOSP based ROMs

So, I had an idea this afternoon that it would be convenient, if you are a DashClock Widget user, to be able to put your phone to sleep via a DashClock extension. If possible, this would help reduce wear and tear on the power button, and allow you to put the phone to sleep quicker than other options.
I turn the screen on to check various statuses using dashclock, and frequently just need to put it back to sleep again, so something like this, I thought, would be nice to have, as it allows me to more quickly / conveniently put the phone back to sleep after checking, without having to use the power button.
The problem is, Google does not expose the PowerManger "goToSleep" method to non-system apps for security reasons.
However, if we have root, I can make it a system app by signing it with CM keys, in order to be granted the necessary permissions to pull it off. This is why this is a CM/AOSP specific "system app" extension. I'm not sure if it will work on other non-CM based ROM as a result, but if you'd like to try, please do so and report back. If the extension doesn't appear after flashing, or it force closes upon clicking, this indicates it is not compatible with your ROM.
If interested in using, this is what you will see once installing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Attached is a signed zip to flash via recovery (since it needs to be pushed to /system/app).
Figured others may find it useful as well, so thought I'd share.

Re: DashClock Sleep Extension for CM 10.1
Awesome idea! I'm gonna check it out
Sent from my Nexus 4 using xda premium
---------- Post added at 03:59 AM ---------- Previous post was at 03:53 AM ----------
Flashed.... Works as expected! Thank you!
Sent from my Nexus 4 using xda premium

Re: DashClock Sleep Extension for CM 10.1
chuckenfoot said:
Awesome idea! I'm gonna check it out
Flashed.... Works as expected! Thank you!
Click to expand...
Click to collapse
Great. Thanks for the confirmation.
Just realized it works nicely to put the phone to sleep when using Dash clock as a home screen widget too!
Sent from my Nexus 4 using xda app-developers app

Re: DashClock Sleep Extension for CM 10.1
Awesome idea but a hassle for me since I have to enter my pattern before it sleeps.
[LG NEXUS⁴] [CARBON] [MATR1X]

Re: DashClock Sleep Extension for CM 10.1
Anyone try this on any other rom I know it says cm10.1 but it's a good idea
Sent from my Nexus 4 using xda premium

CheesyNutz said:
Anyone try this on any other rom I know it says cm10.1 but it's a good idea
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I'm running an AOSP rom and this extension works fine

Re: DashClock Sleep Extension for CM 10.1
Where did you get the nest dashclock extension?

dEris said:
Awesome idea but a hassle for me since I have to enter my pattern before it sleeps.
Click to expand...
Click to collapse
Ah, didn't think about that, as I don't use a pattern lock.
This is a limitation of how DashClock extensions work. Since the original "intent" (no pun intended) is to click an extension, for which DashClock unlocks the screen and it takes you to the particular app (email, weather, etc), all you can pass to the DashClock API in an intent to launch a particular app, activity, etc.
I'm assuming the same happens for you when clicking any other DashClock extension when having a pattern / pin unlock in place?
I can't put the phone directly to sleep as a result, but rather, have to instruct DashClock to launch an intent (which then unlocks the screen), and the intent issues the goToSleep method. Unfortunately, I don't think there is a way around it, given DashClock's primary purpose for extensions.

Re: DashClock Sleep Extension for CM 10.1
CheesyNutz said:
Anyone try this on any other rom I know it says cm10.1 but it's a good idea
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I'm on aospa and it works perfectly
Sent from my Nexus 4 using xda premium

22sl22 said:
I'm running an AOSP rom and this extension works fine
Click to expand...
Click to collapse
Interesting.
I wanted to hedge my bets and play it safe by assuming only CM. Thanks for the confirmation. I'm guessing in light of this, that perhaps any non-stock ROM (AOSP based) ROM that shares similar keys may work.
If you attempt to install, and you simply don't see the extension listed in DashClock, or it force closes when clicking, this is most likely a result of lack of permissions to execute.
If anyone tries running on any other ROMs, please report back, and I'll update the OP.

Rockwig said:
Where did you get the nest dashclock extension?
Click to expand...
Click to collapse
I made it :laugh:
For some reason, Nest continues to keep their API private, so that third parties can't easily interface with it, but I found some documentation out there where someone has reversed engineered much of the API calls.
Based on the documentation, I put together a little Nest DashClock extension to display various statuses as reported by my thermostat, which I think is pretty cool.

JsChiSurf said:
I made it :laugh:
For some reason, Nest continues to keep their API private, so that third parties can't easily interface with it, but I found some documentation out there where someone has reversed engineered much of the API calls.
Based on the documentation, I put together a little Nest DashClock extension to display various statuses as reported by my thermostat, which I think is pretty cool.
Click to expand...
Click to collapse
Mind sharing?

Rockwig said:
Mind sharing?
Click to expand...
Click to collapse
Wish I could. Given the API is private, I am using a PHP server the extension makes calls to, and the PHP server calls Nest, using my hard coded device ids, username, password, etc., which returns back to the phone some JSON formatted data to parse. So, right now, it's not "portable" in any way.
If I get a chance, I want to try and think of a way to make it more universal, but right now, it is very specific to my environment.

JsChiSurf said:
Wish I could. Given the API is private, I am using a PHP server the extension makes calls to, and the PHP server calls Nest, using my hard coded device ids, username, password, etc., which returns back to the phone some JSON formatted data to parse. So, right now, it's not "portable" in any way.
If I get a chance, I want to try and think of a way to make it more universal, but right now, it is very specific to my environment.
Click to expand...
Click to collapse
Completely understandable.
Thanks!

If anyone running AOKP and has tried this can let me know if it works, I'd like to compile a running list of known working ROMs.
Thanks!

JsChiSurf, How did you make your dashclock look that AWSOME Jellybean style?
- there is no line under the clock so the extensions becomes right under it.
- the clock is in the middle and not aligned to the left side.
You have to explain me how youve done that!
Thank you!!

Bunjii said:
JsChiSurf, How did you make your dashclock look that AWSOME Jellybean style?
- there is no line under the clock so the extensions becomes right under it.
- the clock is in the middle and not aligned to the left side.
You have to explain me how youve done that!
Thank you!!
Click to expand...
Click to collapse
Ha, funny thing is, the removed line is a by-product of the mod I did here for conditionally removing the clock when installing DashClock on the homescreen. Since it doesn't make sense to have the line when the clock is gone, I just removed the line all together.
The clock being centered is just an option in the 'Advanced' settings for DashClock directly.

So what should i do to remove the line? ( No contact for the extension you made in this threade) , do i have to still download your mod?
Thanks so much!

Very nice. You should upload it to the play store. You'll get a million downloads.
I wish I didn't have to swipe it to unlock it when the clock is minimized.

scottx . said:
Very nice. You should upload it to the play store. You'll get a million downloads.
Click to expand...
Click to collapse
Unfortunately, since this has to be a system app, it's not something that can be put on the play store.
scottx . said:
I wish I didn't have to swipe it to unlock it when the clock is minimized.
Click to expand...
Click to collapse
Unfortunately, I can't override the behavior of DashClock itself, and since this is what it does for all extensions, I don't have the ability to do anything different for the sleep extension (though I wish I could).

Why can't we produce the same camera output as oneplus?

I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Edit:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Sources: Android Source

0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..

Puddi_Puddin said:
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..
Click to expand...
Click to collapse
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?

0xelectron said:
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?
Click to expand...
Click to collapse
Maybe because it is a **** ton off work? Or noone has the knowledge?

Puddi_Puddin said:
Maybe because it is a **** ton off work? Or noone has the knowledge?
Click to expand...
Click to collapse
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.

0xelectron said:
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.
Click to expand...
Click to collapse
Yes.. Maybe a proper after processing is more work? I have no clue how you need to do those things.. But if it was easy I'm pretty sure someone would've done it already.

0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.

Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).

Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
I get that they want protect their camera code to stay ahead in the game. But, I still don't understand why, we(community) are missing that, we are not able to produce the same quality as theirs. I think either its too hard, or, maybe we don't have required information about the camera module or something like that.

AcmE85 said:
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).
Click to expand...
Click to collapse
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?

0xelectron said:
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?
Click to expand...
Click to collapse
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg

0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app

Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?

defcomg said:
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app
Click to expand...
Click to collapse
I don't have examples currently, but, I've noticed that the post processing of aosp is generally inferior compared to stock. Also, it doesn't have features such as 60fps video recording and proper EIS/OIS.

AcmE85 said:
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg
Click to expand...
Click to collapse
I think I'm not explaining myself properly. What I'm trying to ask is that why the the quality/features of the the camera in custom roms a little inferior compared to stock OOS? I did some digging and found out that most of the capabilities are included in the hal api, and it's implementation, I think is provided by Oneplus. I can be totally wrong (correct me, if I'm).

0xelectron said:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Click to expand...
Click to collapse
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at

defcomg said:
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at
Click to expand...
Click to collapse
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!

0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
Hex Workshop CPP Bookmark
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached the offset bookmark as well as the chromatix source if youd like to check it out

0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Sent from my ONEPLUS A3000 using Tapatalk

fcisco13 said:
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Click to expand...
Click to collapse
You're right. I didn't understand. But, that's a good thing. I'm learning. I'm digging. I'm doing something I would've not done, normally. For example, the first simple answer didn't satisfy me, so, I started learning the inner workings of the android camera. Second complex answer gave me more in-depth knowledge then I leaned, and it is making me study more to understand. So, say what you want, but, I'm thankful for both the answers. Thank you everyone!

[ROM][11.0] AwakenOS [OFFICIAL][Ginkgo]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AwakenOS for the Redmi Note 8/8T [ginkgo/willow]
Code:
#include <std_disclaimer.h>
/*
* Your warranty is void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About Us
Born different, now awaken.
AwakenOS aims to bring a more consistent, fluid and smooth experience with all your must-have customizations, for you, for the community, and for everyone.
Core Team
Saikiran
Ninad Patil [REIGNZ]
Mukul [_undead]
Designers
Hugwalk
Jagadish
Glitch
Features
-RGB Accent picker
-Color Bucket
-QS tint
-Pre-Pie mobile style network icons
-4G icon instead of LTE
-Volume rocker music control
-Volume rocker wake
-Reboot/Reboot to recovery quick settings tile
-Some More options which you are about to find after flashing
-more stuff on the way!
Downloads
ROM: Download
Bugs
-You tell me
Flashing Instructions
Clean Install
- Boot into recovery
- Wipe Cache, System, Data
- Flash ROM
- Flash Gapps (only for vanilla variant)
- Flash Magisk.zip (optional)
- Reboot
Update/Dirty Flash
-Boot into recovery
-Flash ROM
-Wipe cache
-Reboot to system​
Kernel source: Click here
Credits
- Google for AOSP
- LineageOS
- StatixOS
- PixelExperience
Telegram support

Does it rely on AOSP or CAF or LOS?
Does it support Sunlight mode?
Does it support Wifi Coverage Extend Option?
Does it support whitelisting apps from dark mode?
Does it support MIUI Camera with the same stock 48MP quality?
Does it support adjusting freeform windows despite the manifests?
Does it support skipping unlocking the device with a PIN after a reboot
Does it support invert-nav-bar (force close back button)?
Does support Game Mode?
Does it kill apps in the background for just switching between them?
Does Mi sound work for wireless and wired headphones?
Does it support pop-up?
Does it show internal shared adopted storage on TWRP?
And does it have ADB over network/NTFS File format/Soft Reboot/Advanced Power Menu/Quick actions via pop-up notifications.
If it does all of these, I will pay the time and effort to change into your ROM even though I only have one phone and despite that I need to resetup Magisk and Edxposed and System Settings.
Good luck with development

tberma said:
Does it rely on AOSP or CAF or LOS?
Does it support Sunlight mode?
Does it support Wifi Coverage Extend Option?
Does it support whitelisting apps from dark mode?
Does it support MIUI Camera with the same stock 48MP quality?
Does it support adjusting freeform windows despite the manifests?
Does it support skipping unlocking the device with a PIN after a reboot
Does it support invert-nav-bar (force close back button)?
Does support Game Mode?
Does it kill apps in the background for just switching between them?
Does Mi sound work for wireless and wired headphones?
Does it support pop-up?
Does it show internal shared adopted storage on TWRP?
And does it have ADB over network/NTFS File format/Soft Reboot/Advanced Power Menu/Quick actions via pop-up notifications.
If it does all of these, I will pay the time and effort to change into your ROM even though I only have one phone and despite that I need to resetup Magisk and Edxposed and System Settings.
Good luck with development
Click to expand...
Click to collapse
Why asking so much questions? 1 or 2 is Ok.
If you want answers to your question, install and check yourself. This is not a place to ask so many questions. Describe the bugs you face here after installing this ROM. If you want to install, install. Nobody forces you to install this ROM.

devaponnadsm said:
Why asking so much questions? 1 or 2 is Ok.
If you want answers to your question, install and check yourself. This is not a place to ask so many questions. Describe the bugs you face here after installing this ROM. If you want to install, install. Nobody forces you to install this ROM.
Click to expand...
Click to collapse
Well, the developer should have some idea about the ROM he complied.

tberma said:
Does it rely on AOSP or CAF or LOS?
Does it support Sunlight mode?
Does it support Wifi Coverage Extend Option?
Does it support whitelisting apps from dark mode?
Does it support MIUI Camera with the same stock 48MP quality?
Does it support adjusting freeform windows despite the manifests?
Does it support skipping unlocking the device with a PIN after a reboot
Does it support invert-nav-bar (force close back button)?
Does support Game Mode?
Does it kill apps in the background for just switching between them?
Does Mi sound work for wireless and wired headphones?
Does it support pop-up?
Does it show internal shared adopted storage on TWRP?
And does it have ADB over network/NTFS File format/Soft Reboot/Advanced Power Menu/Quick actions via pop-up notifications.
If it does all of these, I will pay the time and effort to change into your ROM even though I only have one phone and despite that I need to resetup Magisk and Edxposed and System Settings.
Good luck with development
Click to expand...
Click to collapse
Cann you stop with the bombarding of questions on every single post you make.
Stick with Stock MIUI.
DO NOT install a custom ROM.

Great rom! Thanks!|

tberma said:
Does it rely on AOSP or CAF or LOS?
Does it support Sunlight mode?
Does it support Wifi Coverage Extend Option?
Does it support whitelisting apps from dark mode?
Does it support MIUI Camera with the same stock 48MP quality?
Does it support adjusting freeform windows despite the manifests?
Does it support skipping unlocking the device with a PIN after a reboot
Does it support invert-nav-bar (force close back button)?
Does support Game Mode?
Does it kill apps in the background for just switching between them?
Does Mi sound work for wireless and wired headphones?
Does it support pop-up?
Does it show internal shared adopted storage on TWRP?
And does it have ADB over network/NTFS File format/Soft Reboot/Advanced Power Menu/Quick actions via pop-up notifications.
If it does all of these, I will pay the time and effort to change into your ROM even though I only have one phone and despite that I need to resetup Magisk and Edxposed and System Settings.
Good luck with development
Click to expand...
Click to collapse
Alright, let me comment:
Does it rely on AOSP or CAF or LOS?
Click to expand...
Click to collapse
Of course. It's an Android ROM. If you want something not based on those install a mobile Linux distro.
Does it support Sunlight mode?
Click to expand...
Click to collapse
The what
Does it support Wifi Coverage Extend option?
Click to expand...
Click to collapse
You mean hotspot? Or do you actually want to get free Wi-Fi anywhere you go!!!!1!1!?
Does it support MIUI Camera with the same stock quality?
Click to expand...
Click to collapse
Why do you need MIUI Camera with Xiaomi's sub par processing?
Does it support skipping unlocking the device with a PIN after a reboot?
Click to expand...
Click to collapse
Ser does it support PIN bypasser too?
Does it support invert-nav-bar (force close back button)?
Click to expand...
Click to collapse
No but it does support recent apps and settings with which you can force close an app. Also, how are nav bar inversion and force close related?
Does it kill apps in the background for just switching between them?
Click to expand...
Click to collapse
Aggressive power management like that is generally frowned upon. And if the ROM does that you will probably shout "Ser my music stopping after switch app and alarm not works too please fix!!!!!!!!!!" at the dev.
Does Mi sound work?
Click to expand...
Click to collapse
If you want Xiaomi features use MIUI.
And does it have ADB over network
Click to expand...
Click to collapse
Android 11 has a quick action, which is much better
NTFS File format
Click to expand...
Click to collapse
Just imagining you screaming "Ser u bad dev I press on notification in accident my all data is gone!!!!! PLEASE FIX!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
Soft Reboot
Advanced power actions
Click to expand...
Click to collapse
Power menu: helo
Quick actions
Click to expand...
Click to collapse
Is swiping down with 2 fingers bad? Or do you want some special actions?
Also, I doubt the dev cares about you installing or not installing the ROM.

thegreatporg said:
Alright, let me comment:
Of course. It's an Android ROM. If you want something not based on those install a mobile Linux distro.
The what
You mean hotspot? Or do you actually want to get free Wi-Fi anywhere you go!!!!1!1!?
Why do you need MIUI Camera with Xiaomi's sub par processing?
Ser does it support PIN bypasser too?
No but it does support recent apps and settings with which you can force close an app. Also, how are nav bar inversion and force close related?
Aggressive power management like that is generally frowned upon. And if the ROM does that you will probably shout "Ser my music stopping after switch app and alarm not works too please fix!!!!!!!!!!" at the dev.
If you want Xiaomi features use MIUI.
Android 11 has a quick action, which is much better
Just imagining you screaming "Ser u bad dev I press on notification in accident my all data is gone!!!!! PLEASE FIX!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
Power menu: helo
Is swiping down with 2 fingers bad? Or do you want some special actions?
Also, I doubt the dev cares about you installing or not installing the ROM.
Click to expand...
Click to collapse
Haha, I don't care about your feelings about my wanted features.
And you're not the dev to talk on behalf of the dev to make fun of me while I want just for them to develop the ROM for better user experience.
Melt in your hatred and don't expect from me to make you whole again.

tberma said:
Haha, I don't care about your feelings about my wanted features.
And you're not the dev to talk on behalf of the dev to make fun of me while I want just for them to develop the ROM for better user experience.
Melt in your hatred and don't expect from me to make you whole again.
Click to expand...
Click to collapse
Well, the moral of the story is, if you want to know what features a rom packs, then try it. Stop asking 69 questions and expect me to write an essay just to answer to you. It's impolite and incoherent. The answers you got are the ones your question deserves. And, as I saw, you do this on multiple threads.
To somewhat answer to you, Awaken is a highly customizable rom, I guess most of the features one wants are there.

kostas gp said:
Well, the moral of the story is, if you want to know what features a rom packs, then try it. Stop asking 69 questions and expect me to write an essay just to answer to you. It's impolite and incoherent. The answers you got are the ones your question deserves. And, as I saw, you do this on multiple threads.
To somewhat answer to you, Awaken is a highly customizable rom, I guess most of the features one wants are there.
Click to expand...
Click to collapse
And is it polite to force someone to try something before find proofs on what is on the something denying the fact that he has only one phone to test and it's hard to set the phone each time just for seeing what is inside another brand ROM. I have to see good reasons before believing in the ROM. This is logistian way. I'm not fancier to make me believe before finding the proofs.
And what is wrong with writing an essay when you are going to help me with instead of hardening stuff?

tberma said:
And is it polite to force someone to try something before find proofs on what is on the something denying the fact that he has only one phone to test and it's hard to set the phone each time just for seeing what is inside another brand ROM. I have to see good reasons before believing in the ROM. This is logistian way. I'm not fancier to make me believe before finding the proofs.
And what is wrong with writing an essay when you are going to help me with instead of hardening stuff?
Click to expand...
Click to collapse
Did I point a gun at you and yelled "flash my ROM"? I guess not, so no, I didn't force you. When you dive in to custom roms, it's about trying things. I spend time and energy in making the rom, you can spend some of these, since you're interested in it, to try it. Yes I'd like to help you, but I'm not going to spoon-feed you. If you read the main post, it already mentions many of the features. Also, I would write an essay for something which would require it, not to give an exhaustive list of every single point of a rom to anyone who demands it, that's not how it works. I'm doing this as a hobby in my free time, I'm not an employee. And as a last point, I've been a flash-o-holic and tester for the last couple of years and I don't remember my life getting ruined because the rom I flashed lacked a feature I wanted. I found some good backup methods and created a backup/restore flow which worked fast and easy to save my time switching.

I made a mistake.

abe520 said:
I made a mistake.
Click to expand...
Click to collapse
What mistake?

will this rom coming back?

OmnioPT said:
will this rom coming back?
Click to expand...
Click to collapse
There's a probability it comes back, but I can't say with certainty.

Got my first touch on Android 12 with this wonderful ROM and I think it should not stay so far from the first page. I'm running it since yesterday and it performs quite nice so far.
I'll leave the direct link here (since community seems a little lazy):
Awaken a12 Luna (vanilla only)
Working a12 Gapps (Canary, basic)
Cheers
(and never forget pressing the thanks button instead of writing a post with it keeps the threads clean )

General Sailfish OS for Xperia 10 III

Xperia 10 III is now officially supported by Sailfish OS: https://blog.jolla.com/xperia-10-iii/
From Wikipedia:
Sailfish OS is a Linux-based operating system based on free software, and open source projects such as Mer as well as including a closed source UI. The project is being developed by the Finnish company Jolla.
Click to expand...
Click to collapse
Anyone in here tried it yet?

I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!

Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
According to its readme file, Newflasher runs on Linux too: https://github.com/munjeni/newflasher
So I think it should be possible to flash an Android 11-based firmware from here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/ using this tool. But I never used it (neither on Windows nor on Linux) so I can't say for sure whether that works.
As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?

As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?
Click to expand...
Click to collapse
Ha! Yes I did do all the required steps. I found an Android 11-based build on the Sailfish forums which worked, after doing it twice with Newflasher. Once this was done the OEM unlock command did its thing without a hiccup. Sailfish OS is now running nicely on the 10 III - hopefully Jolla are able to provide some more complete instructions for those who have managed to upgrade themselves into a documentation loop!

I've been using the X10III with Sailfish for several days now, and the experience is quite smooth. There is no green tint visible, but the "color space" gets really smashed and mangled in low light + low brightness situations... I think it's more or less the same bug. The best way to describe is that the dark areas of the screen are rendered with 8-bit color palette and way too high brightness. I created a bug report for it over at Sailfish OS Forum for those who wish to keep an eye on that.
There are three known issues: Camera API doesn't support the three back cameras (Camera2 API does support it, so it's very fixable), the indicator led is way too green (driver issue), and issues with noise cancellation during phone calls (seems to be fixed in git).
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.

direc85 said:
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
I have a hard time understanding why it is necessary to repair a thing that is not broken?
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
And in general, calling is the least used feature of the phone lately.

ksuuk said:
I have a hard time understanding why it is necessary to repair a thing that is not broken?
Click to expand...
Click to collapse
What exactly are you referring to? 3G, the OS in the device, or something else..?
ksuuk said:
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
Click to expand...
Click to collapse
Why shouldn't I use what I already paid for?
But yes, phone calls are getting rarer; for me it's something between daily and weekly. But still, it's the official method to be reached, supported by pretty much every device, so why not just use it instead of apps.
Also, if I wanted to use only apps to talk with my friends, I'd have five chat apps installed, some of them analyzing me, and all of them draining my battery. No thanks...
But let's get back to topic. Does anyone know how to solve the color banding issue on AOSP?

direc85 said:
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.

Aranornen said:
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.
Click to expand...
Click to collapse
I can't say anything about features built into the OS (as I've never used it), but I was able to find two 3rd party apps which let you limit the maximum battery charge level:
Battery Buddy | OpenRepos.net — Community Repository System
openrepos.net
takimata / harbour-battery-charging-control · GitLab
SailfishOS application which allows to stop battery charging at user-defined levels.
gitlab.com

Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
hi can you help me o i have an Xperia 5 phone running sailfish os same as your Xperia 10 mark 3 i cant buy license to run apk app you can extract aliendalvik file can you give it to me, i will keep it from sharing to anyone, because it is the source of life jolla , i will transfer you a small amount of money, i come to sailfish os full of passion but not enough money , hope you can help, thank you very much