Database Users

Color Calibration ( Blue tint fix :) ) - Needs some work though

http://forum.xda-developers.com/showthread.php?t=745248
Have a look (not my work, just wanted to share)
This little fix lets you adjust the colors, so I thought you would be interested.
It does seem to screw up the camera (only white preview) , but other than that it works great
howto: flash the zip in CWM and then install the apk...
so when the camera bug gets sorted it would be awesome

-Yaya- said:
http://forum.xda-developers.com/showthread.php?t=745248
Have a look (not my work, just wanted to share)
This little fix lets you adjust the colors, so I thought you would be interested.
It does seem to screw up the camera (only white preview) , but other than that it works great
howto: flash the zip in CWM and then install the apk...
so when the camera bug gets sorted it would be awesome
Click to expand...
Click to collapse
isn't that what Supercurio's Voodoo Color does ?

where can I acces the voodoo color settings?
I use darkys rom (9.3) and voodoo should be included but I only find an Voodoo control app which adjusts the sound but not the color.
In CWM I can only adjust lagfix settings?

You can use Galaxy Tuner for that.

-Yaya- said:
where can I acces the voodoo color settings?
I use darkys rom (9.3) and voodoo should be included but I only find an Voodoo control app which adjusts the sound but not the color.
In CWM I can only adjust lagfix settings?
Click to expand...
Click to collapse
the Voodoo Control App includes the settings
you only need to switch to a kernel which includes newest Voodoo Color changes
(dunno if it exists for 2.2* kernels though)

Well I just installed the latest Voodoo kernel (5.4.1) but no changes

If I'm not wrong that voodoo colour app only apply to nexus s.. Not available for 2.2..
Sent from my GT-I9000 using XDA App

ccs1988 said:
If I'm not wrong that voodoo colour app only apply to nexus s.. Not available for 2.2..
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
it applies to Nexus S and SGS using CM7 (the kernel-sources are based on Nexus S sources)

Apparently non of these works for us, so we're stuck with the bluish screen
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.

need4steer said:
Apparently non of these works for us, so we're stuck with the bluish screen
Click to expand...
Click to collapse
from what I can gauge from all this, is that certain parts (screens) used by Samsung were not capable of screen variations in/for later builds as such they totally declined further upgrades for all. This would be common in manufacturing the initial device (galaxy S) as trial and error would play a part in releasing the most cost effective product and the part used coming from different sources. The Galaxy S had 20 versions, meant for different locations and pricing, so the componaents would be from from various sources, some of top quality and others of lower grade going to lower priced models meant for third world locations.
so it may be wise to see when and where this models having blue screen problems are cropping up most.
Check this out! Links to useful Guides and " Banned " Documentaries ​

xsenman said:
from what I can gauge from all this, is that certain parts (screens) used by Samsung were not capable of screen variations in/for later builds as such they totally declined further upgrades for all. This would be common in manufacturing the initial device (galaxy S) as trial and error would play a part in releasing the most cost effective product and the part used coming from different sources. The Galaxy S had 20 versions, meant for different locations and pricing, so the componaents would be from from various sources, some of top quality and others of lower grade going to lower priced models meant for third world locations.
so it may be wise to see when and where this models having blue screen problems are cropping up most.
Check this out! Links to useful Guides and " Banned " Documentaries ​
Click to expand...
Click to collapse
That's a very interesting thinking.
I just found out that this problem appears to be a known issue which is caused from incorrect calibration data which exists in some devices and affected by cyanogenmod 9+ (the later 9 ROMs, some of the older don't have this issue)
I think I'll post a new thread to help people understand this problem and its origin, and in the same time I might ask them their model and location, according to your great suggestion.
Thanks again!
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.

bluish screen - dark blue tint / hue after flashing AOSP ICS and above on GT-I9000
-Yaya- said:
http://forum.xda-developers.com/showthread.php?t=745248
Have a look (not my work, just wanted to share)
This little fix lets you adjust the colors, so I thought you would be interested.
It does seem to screw up the camera (only white preview) , but other than that it works great
howto: flash the zip in CWM and then install the apk...
so when the camera bug gets sorted it would be awesome
Click to expand...
Click to collapse
There's a known problem for a little amount of Samsung Galaxy S GT-I9000 devices that are getting bluish screen after flashing AOSP Ice Cream Sandwich (4.0.x) and above.
By bluish screen I mean that there's a dark blue color, a blue tint / hue all over the screen.
This bluish screen appears everywhere in the ROM, in the recovery, and even when charging the phone while it's off.
According to DerTeufel1980 and pawitp, this issue is caused by the updated framebuffer driver of the Nexus S in the CyanogenMod 9 kernels, and the actual problem is that some devices contain incorrect calibration data.
I posted a thread in which I summarize all I know about this issue.
This issue is fixed thanks to pawitp.
We can flash this fixed CyanogenMod 11 nightly.
Any release from now on will be updated with this fix.
There are detailed instructions in pawitp's thread - [NIGHTLY][ROM][4.4] CyanogenMod 11 for Samsung Galaxy S
This is the official thread of CyanogenMod 11 in this forum.
Please note that in CyanogenMod's download site we should flash any version that is newer than cm-11-20140211-NIGHTLY-galaxysmtd.zip which was posted today, the 11.02.2014, at 04:51:57 (according to the "Date Added" column in the download site)
I'd like to appreciate pawitp for his willing to help and for his truly tremendous effort to the community.
Thanks a lot!

[BOOTANIMATION] Playstation 1 boot + sound

My first post here so i'll try to be as good of an OP as possible!
So, i looked around and i couldn't find one i liked so i made my own with some help of course! And i finaly decided i want to share it with you all ^^
Since i first noticed that if you make a 1 loop bootanimation you can't make it big so even though the screen is 480x800 i scaled down the images to 360x600(75%) which made it VERY fluent when scaled up to 480x800. No chopping like it otherwise did and i could have higher fps+more frames.
This is my first bootanimation and the only thing i did was taking frames from this remastered/recreated(but slightly non-cannon *Look at where the TM is placed in the first half*) version of the PS1 boot:
"Link 1"
And i used this sound:
"Link 2"
Which i normalized so it wouldn't destroy my speaker!
links.rar has the two credit links as well as the example link(youtube) in a txt file til i get more posts
PS: Filenames in the bootanimation have their original vlc snapshot names. I will fix this in a later version now i just want oppinions and to share the beauty i've created ^^
Any ideas for a splashscreen or what to have as an ending for the animation is appriciated. Im new to all of this so!
LINKS IN THE SECOND POST!

Pettingson said:
This is my first bootanimation and the only thing i did was taking frames from this remastered/recreated(but slightly non-cannon *Look at where the TM is placed in the first half*) version of the PS1 boot:
http://www.youtube.com/watch?v=oAhvQoLpvsM
And i used this sound:
http://soundcloud.com/alexeino/ps1-startup-remastered
Which i normalized so it wouldn't destroy my speaker!
example link(youtube)
http://www.youtube.com/watch?v=tUQwa58yEp8
Click to expand...
Click to collapse
Thanks for sharing your efforts, nice first attempt Have linked to your sources/ sample video for you.

fisha21 said:
Thanks for sharing your efforts, nice first attempt Have linked to your sources/ sample video for you.
Click to expand...
Click to collapse
And thank you for that ^^ Very helpfull! Thanked

Nice work man I love the boot sound on the ps1

could someone make this flashable?

nice share, thank you

Great job, thank you!

Beautiful mate, thank you.

Funny on the xperia play

lost
daksha303 said:
Funny on the xperia play
Click to expand...
Click to collapse
Man I'm so lost I've been trying to do this for hours I've got a Samsung Galaxy S 2 I recently rooted it and put a custom rom on it I've managed to get the boot animation on it but I cannot find the sound I have to rename or anything Where am I meant to put the sound ?

interesting!
interesting boot animation tnx for that

This is cool, thx

Holy smokes this is cool. Can you upscale that for the Galaxy Nexus?

Is anyone able to resize for sensation? I love this. Reminds me of the good old days Would love to be able to have it on my sensation with boot sound. Running Ordroid 8.0.0 atm. If it is easy enough to do, someone kindly point me to a guide and I will have a crack at it
---------- Post added at 09:03 PM ---------- Previous post was at 08:49 PM ----------
Don Brachino said:
Man I'm so lost I've been trying to do this for hours I've got a Samsung Galaxy S 2 I recently rooted it and put a custom rom on it I've managed to get the boot animation on it but I cannot find the sound I have to rename or anything Where am I meant to put the sound ?
Click to expand...
Click to collapse
I know it has been a while since you asked this question but to find out where and what name the bootanimation is meant to be named and kept, simply use root explorer (available on play store to buy or similar alternative)
Navigate to /system/customize/CID and open the file 'default.xml'
Now scroll all the way to the bottom and look for <BootConfiguration> should be about 30-40 lines up from bottom. There you will find the locations for bootanimation and audio. simply rename your bootanimation and/or audio to the name it says there. In my case they are
system/customize/resource/bootanimation.zip
system/customize/resource/android_audio.mp3
system/customize/resource/downanimation.zip
Hope it helps somone atleast if not you

thank you

animation is so good however the boot sound is more wonderful

very nice but how do I flash it?

Good share dude..

How bout a transformers one???
Sent from my HTC Desire CDMA using xda premium

thank you

CIA Bootanimation

I found the CIA bootanimation but it was showing the last pictures before the first ones. I fixed it. It is currently 720x1280 but I cannot correctly change the resolution. I change the numbers in the desc.txt but it doesn't work then. Anyway, this works but it is a little small. If anyone wants to correctly change the resolution, feel free to do so.
original file post: http://forum.xda-developers.com/showthread.php?t=1898386

Instead of working against them, just embrace it?

Zilol said:
Instead of working against them, just embrace it?
Click to expand...
Click to collapse
What?

vman411gamer said:
What?
Click to expand...
Click to collapse
He was making a joke about how instead of bashing the CIA (for privacy reasons, etc.) we should embrace them by having its logo as our bootanimation

vman411gamer said:
I found the CIA bootanimation but it was showing the last pictures before the first ones. I fixed it. It is currently 720x1280 but I cannot correctly change the resolution. I change the numbers in the desc.txt but it doesn't work then. Anyway, this works but it is a little small. If anyone wants to correctly change the resolution, feel free to do so.
original file post: http://forum.xda-developers.com/showthread.php?t=1898386
Click to expand...
Click to collapse
to change the resolution of the bootanim you have to do more then just edit desc.txt you have to edit the actual images that are part of it...

Works beautifully on my N4 running N5 Port.
Sent from my Nexus 4 using xda app-developers app

Android Wear Boot Animation for MotoACTV

Many of your likely saw the news of the LG G Watch system dump yesterday. It was pretty exciting stuff. I thought the boot animation looked really cool and I have just got hold of a MotoACTV and thought I should try and put them together.
I have managed to port the Android Wear boot animation from the LG G Watch system dump to the Motorola MotoACTV succesfully and I think it looks really nice. It is running at the same 30fps as it is designed to on the G Watch which looks a lot nicer than the 15fps stock animation. Obviously you still have the Moto logo on the bootloader but I may try and swap that for something neater too at some point. Anyway enough talk, below is link to a video of it in action!
https://www.youtube.com/watch?v=DI5j4ScKt8U
I have attached the bootanimation.zip for other people who want to try it out and I'll add instructions on how to install it for those unsure a bit later on.
Update! - New version with more optimised frames for a smaller filesize and an even smoother animation on the device. Grab the replaced attachment! Also I have created a preview gif as you can see below. The video is still nice to look at to see how it actually performs during the boot but this gif gives a clearer view of the actual animation.
Update 2: - New PNG version! JPG version normally works better on this device though. See post #11
{
"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"
}

ClearD have you tried it?

Nexus 4
Hi @wollac11 ... thanks so much for this amazing boot animation !!! Can you pls change the size of the animation for my N4 .. it is little bit small .. but i really like it ... thanks!

IgnorCZ said:
Hi @wollac11 ... thanks so much for this amazing boot animation !!! Can you pls change the size of the animation for my N4 .. it is little bit small .. but i really like it ... thanks!
Click to expand...
Click to collapse
No problem, glad you like it! But yeah this one is designed specifically for the MotoACTV and although it will be compatible with some other devices which support this type of boot animation it won't look good. I could potentially make it for other devices too though I just thought doing it for an existing smartwatch would be a cool thing to try first given that is what it was designed for.
The main issue is that the LG G Watch has a pretty small screen too (not as small as the ACTV) so the resolution of the source images is not that high. I may have to recreate each frame from scratch at a higher resolution to make it look good for large devices which would be very time consuming. I might be able to vectorise each fame and then scale them it I guess. There are a few other things I could potentially try to make it look okay as well.
Anyway, I have the Nexus 4 so I'll see of I can produce something for phones of that display size which still looks good. If I do, I'll post it.
Sent from my Nexus 4 using Tapatalk

wollac11 said:
Yeah this one is designed specifically for the MotoACTV and although it will be compatible with some other devices which support this type of boot animation it won't look good. I could potentially make it for other devices too though I just thought doing it for an existing smartwatch would be a cool thing to try first
The main issue is that the LG G Watch has a pretty small screen too (not as small as the ACTV) so the resolution of the source images is not that high. I may have to recreate each frame from scratch at a higher resolution to make it look good for large devices which would be very time consuming. I might be able to vectorise each fame and then scale them it i guess. There are a few other things I could potentially do to make it look okay.
Anyway, I have the Nexus 4 so I'll see of I can produce something for phones of that display size which still looks good. If I do I'll post it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
It's up to you!! .. Now I can see how hard it can be to done this.... I like the idea of this boot animation ... but if it takes to much energy and time ... don't do it ....
.. anyway good job!!!!

@IgnorCZ Good news! I have managed to make a version for the Nexus 4! I was able to trace and vectorise every frame to create scalable SVGs of each. From which I can create PNG or JPG frames (depending on device requirements) of every resolution. That means I can make them for any device now. Also, because the Nexus 4 has greater than Android 4.1 I can use C loops in this one which means the loops of the animation work in the same way as you would see on the LG G Watch (which is better than what I did on the MotoACTV as it runs Gingerbread). It doesn't matter so much for the ACTV anyway because the boot time is so low and is pretty consistent.
See a video of it in action: https://www.youtube.com/watch?v=3jior6pwamg The boot animation is attached here but I am also going to do a separate thread explaining the installation process, how I made it and taking requests for other devices (I shall be doing the N7 2013 next).
I may also make flashable zips for ease. Eventually I'll probably bundle them all together with an AROMA installer zip so you can flash it to a range of devices (choosing your resolution and Android version in the installer).
This zip is for the Nexus 4 but will work well on any device with a 1280x768 display and Android 4.1 or higher. Enjoy!

wollac11 said:
@IgnorCZ Good news! I have managed to make a version for the Nexus 4! I was able to trace and vectorise every frame to create scalable SVGs of each. From which I can create PNG or JPG frames (depending on device requirements) of every resolution. That means I can make them for any device now. Also, because the Nexus 4 has greater than Android 4.1 I can use C loops in this one which means the loops of the animation work in the same way as you would see on the LG G Watch (which is better than what I did on the MotoACTV as it runs Gingerbread). It doesn't matter so much for the ACTV anyway because the boot time is so low and is pretty consistent.
See a video of it in action: https://www.youtube.com/watch?v=3jior6pwamg The boot animation is attached here but I am also going to do a separate thread explaining the installation process, how I made it and taking requests for other devices (I shall be doing the N7 2013 next).
I may also make flashable zips for ease. Eventually I'll probably bundle them all together with an AROMA installer zip so you can flash it to a range of devices (choosing your resolution and Android version in the installer).
This zip is for the Nexus 4 but will work well on any device with a 1280x768 display and Android 4.1 or higher. Enjoy!
Click to expand...
Click to collapse
Hi you are THE MAN !!! It's absolutely beautiful!! I don't really understand what you did but it's working!!! Flashable zip would be cherry on top of the cake .... THANKS!!!
Igy
PS: out of "thanks" .. I will do it tomorrow

IgnorCZ said:
Hi you are THE MAN !!! It's absolutely beautiful!! I don't really understand what you did but it's working!!! Flashable zip would be cherry on top of the cake .... THANKS!!!
Igy
PS: out of "thanks" .. I will do it tomorrow
Click to expand...
Click to collapse
Nice to see you enjoy it! I have actually found I can improve the animations for the Nexus 4 and 7 (and other future devices) by quite a bit through better optimising the PNG frames in the animation to reduce the boot-animations overall file-size. The result of this is that the animation looks much smoother. I will post an updated version of the bootanimation.zip in the new thread I will create later and add a link to there from here.

wollac11 said:
Nice to see you enjoy it! I have actually found I can improve the animations for the Nexus 4 and 7 (and other future devices) by quite a bit through better optimising the PNG frames in the animation to reduce the boot-animations overall file-size. The result of this is that the animation looks much smoother. I will post an updated version of the bootanimation.zip in the new thread I will create later and add a link to there from here.
Click to expand...
Click to collapse
Perfect!!! Best gonna be even better .. huge thanks

IgnorCZ said:
Perfect!!! Best gonna be even better .. huge thanks
Click to expand...
Click to collapse
The new optimised version for the Nexus 4 can be found on my new thread along with other devices here: http://forum.xda-developers.com/and...-boot-animation-devices-t2776091/post53236022
This thread will now only be for the MotoACTV version. I have also uploaded a new version of the MotoACTV version in the OP here (replacing the old attachment) which is better optimised as well although the difference is less significant than it is on other device versions as due to the resolution being so low and using jpg frames the MotoACTV version was already tiny!

Quick update
Turns out the PNG frames will work on the MotoACTV however it doesn't seem to load them as fast as JPGs for some reason despite the opposite being true for the bootanimations on most other devices and so in my experience at least, the JPG versions are better (smoother) on this device.
However I understand people's mileage may vary and some people will take a trade off in framerate for the sharper edges and so I have uploaded a PNG version. This will of course need to be renamed before dropping in /data/local or /system/media. You will also notice I have also replaced the preview gif for one with a higher framerate that more accurately represents the speed it appears on the device!

How do you change it?
So, how do you change the boot animation? Do we just flash the attached zip in recovery?

C--Dog said:
So, how do you change the boot animation? Do we just flash the attached zip in recovery?
Click to expand...
Click to collapse
Hi, no this is not a flashable zip. You push it to /data/local or /system/media with adb or using a root file explorer. If pushing to /system/media it will actually overwrite the existing animation so I suggest backing it up first. If using a root file explorer then you will also need to set the file permissions to 644.
For example: running "adb push bootanimation.zip /data/local/" should do the trick.

wollac11 said:
Hi, no this is not a flashable zip. You push it to /data/local or /system/media with adb or using a root file explorer. If pushing to /system/media it will actually overwrite the existing animation so I suggest backing it up first. If using a root file explorer then you will also need to set the file permissions to 644.
For example: running "adb push bootanimation.zip /data/local/" should do the trick.
Click to expand...
Click to collapse
So, do I need to root first my MotoACTV and then copy this file as indicated? Thanks.

jctlmm said:
So, do I need to root first my MotoACTV and then copy this file as indicated? Thanks.
Click to expand...
Click to collapse
That is correct
Sent from my Nexus 4 using Tapatalk

MagiskPack for bullhead (Android N and O supported)

These are a few mods that I made recently in order to improve a few bits of our device. This includes some build.prop tweaks, optimized camera libs, and VR support.
Little Mix => enabling Qualcomm Adaptive Display, Miracast (needing a lib from Pixel or Pixel 2 so if u got one DM me), and faster fingerprint detection.
Optimized Camera Libraries => really just self-explanatory, also enables 60fps and 100% quality JPEG photos.
Snappy Prop => build.prop additions, this is a collection of many to enable device features your ROM may not even have. THIS IS MOSTLY USELESS. I got bored and tried porting Snappy Prop to see it's effect that's all.
Daydream => Enables VR support and also improves thermal responsiveness.
Charging Boost => Allows fast charging at higher temperatures, still safe.
White Boot => A Watchdogs inspired bootanimation with a white background. For those Pixel lovers out there. This took 20 mins to upload. XDA is slow.
If anyone wasn't credited for something prove you made it and I'll add ya [almost] instantly to the list below.
Code:
Changelog:
Snappy Prop - removed props relating to rotation
Optimized Camera Libraries - correct placement of camera libs
Charging Boost - an actual magisk module this time :p
Thanks to:
@Miustone for build prop stuff
@ravinder0003 for the charging config

Charging boost doesn't seem to work, Magisk Manager says it's not a Magisk Module.

TemperateRoot said:
Charging boost doesn't seem to work, Magisk Manager says it's not a Magisk Module.
Click to expand...
Click to collapse
Thanks mate. I forgot to upload the Magisk Module of that one abs I uploaded the flashable :silly:

1. Flashing the 'Snappy Prop.zip' module results in a vendor image mismatch message on the screen after booting into system. The message says that 'bullhead-opm3.171019.016' vendor image should be installed. 'bullhead-opm3.171019.016' is the current installed vendor image. After disabling the module in Magisk and rebooting, the messages no longer displays.
2. Flashing the 'White Boot.zip' modules causes the screen to flash repeatedly displaying geometric shapes and messages during the boot process. Disabling the module in Magisk and rebooting, the boot process is normal displaying first the Android logo and the AICP logo before displaying the lock screen.
Flashing the other four modules, does not result in any errors or problems with the phone during the flashing, boot up, or operation of the phone.
Running AICP 13.1 bullhead+TWRP+Magisk+Open GApps+ElementalX-Kernel on the Nexus 5X LG-H790.

dynamo1950 said:
1. Flashing the 'Snappy Prop.zip' module results in a vendor image mismatch message on the screen after booting into system. The message says that 'bullhead-opm3.171019.016' vendor image should be installed. 'bullhead-opm3.171019.016' is the current installed vendor image. After disabling the module in Magisk and rebooting, the messages no longer displays.
2. Flashing the 'White Boot.zip' modules causes the screen to flash repeatedly displaying geometric shapes and messages during the boot process. Disabling the module in Magisk and rebooting, the boot process is normal displaying first the Android logo and the AICP logo before displaying the lock screen.
Flashing the other four modules, does not result in any errors or problems with the phone during the flashing, boot up, or operation of the phone.
Running AICP 13.1 bullhead+TWRP+Magisk+Open GApps+ElementalX-Kernel on the Nexus 5X LG-H790.
Click to expand...
Click to collapse
well for 1) you are correct I will try to fix this matter tomorrow morning
for 2) the flashing geometric shapes... that's the boot animation for my module it's the point of the module :silly: (if you haven't played the game WatchDogs you probably won't get the reference)
PS - nice to see you're also using AICP

LazerL0rd said:
well for 1) you are correct I will try to fix this matter tomorrow morning
for 2) the flashing geometric shapes... that's the boot animation for my module it's the point of the module :silly: (if you haven't played the game WatchDogs you probably won't get the reference)
PS - nice to see you're also using AICP
Click to expand...
Click to collapse
@LazerL0rd - Just wondering if you are going to fix the matter with the 'Snappy Prop.zip'? Also curious about what features it attempts to enable in the Nexus 5X
The other zips, excluding 'White Boot.zip', have been enabled on the phone for a week or so and no problems to report :good::good:

dynamo1950 said:
@LazerL0rd - Just wondering if you are going to fix the matter with the 'Snappy Prop.zip'? Also curious about what features it attempts to enable in the Nexus 5X
The other zips, excluding 'White Boot.zip', have been enabled on the phone for a week or so and no problems to report :good::good:
Click to expand...
Click to collapse
Nice, well as I said white boot was a boot animation changer but hey it doesn't seem to be your thing.
I'll upload a fix hopefully. Well it attempts to enable a plethora of build props and some work some don't. I've had a prop of useful options I've collected over a year and added them there. It's universal so works on any second device.
I wonder how hot your device gets in VR, though?

LazerL0rd said:
Nice, well as I said white boot was a boot animation changer but hey it doesn't seem to be your thing.
I'll upload a fix by today hopefully. Well it attempts to enable a plethora of build props and some work some don't. I've had a prop of useful options I've collected over a year and added them there. It's universal so works on any second device.
I wonder how hot your device gets in VR, though?
Click to expand...
Click to collapse
When running Daydream VR apps, the phone heats up. The center of the back feels the hottest.
With the case off the phone, I insert it into a Google Daydream View 2017 headset. With a magnesium heat sink, the headset draws the heat from the phone quite well. The VR experience on the Nexus 5X has some lag, stutter and a bit blurry at high resolution. Otherwise, it offers a feel for the VR experience.

dynamo1950 said:
When running Daydream VR apps, the phone heats up. The center of the back feels the hottest.
With the case off the phone, I insert it into a Google Daydream View 2017 headset. With a magnesium heat sink, the headset draws the heat from the phone quite well. The VR experience on the Nexus 5X has some lag, stutter and a bit blurry at high resolution. Otherwise, it offers a feel for the VR experience.
Click to expand...
Click to collapse
Ah great, I haven't had my hands on a headset yet but that's great. With an OC'd kernel and 4GB RAM mod that should be pretty good (as long as you don't have the bootloop lol.
How did you apply the heatsink?

LazerL0rd said:
Ah great, I haven't had my hands on a headset yet but that's great. With an OC'd kernel and 4GB RAM mod that should be pretty good (as long as you don't have the bootloop lol.
How did you apply the heatsink?
Click to expand...
Click to collapse
Sorry for misunderstanding. The heatsink is in the Google Daydream View headset. Also, do not have the 4GB RAM mod. My Nexus 5x phones are unmodified hardware.
As the module is now, displaying the Vendor image mismatch on boot, does it still work as intended? Can the vendor image mismatch error message be ignored? Thanks.......
---------- Post added at 06:35 PM ---------- Previous post was at 06:25 PM ----------
dynamo1950 said:
Sorry for misunderstanding. The heatsink is in the Google Daydream View headset. Also, do not have the 4GB RAM mod. My Nexus 5x phones are unmodified hardware.
As the module is now, displaying the Vendor image mismatch on boot, does it still work as intended? Can the vendor image mismatch error message be ignored? Thanks.......
Click to expand...
Click to collapse
In addition, for your info, both of my Nexus 5X phones began intermittent boot looping (sticking on Android logo at bootup) after 18 months + of usage this past January. They would need multiple hard resets using the power button to successfully boot into system.
I sent them, one at a time, to the LG Wireless repair center on RMA's. To my surprise, LG repaired each phone by replacing the main board. If I understand correctly, LG has extended its warranty to about 30 months from date of purchase to cover this kind of failure. :good:
There was no cost involved, just the one-way shipping to the repair facility. Again, I did not purchase any extended warranty at time of purchase. Both phones now work fine without that boot loop issue.

dynamo1950 said:
Sorry for misunderstanding. The heatsink is in the Google Daydream View headset. Also, do not have the 4GB RAM mod. My Nexus 5x phones are unmodified hardware.
As the module is now, displaying the Vendor image mismatch on boot, does it still work as intended? Can the vendor image mismatch error message be ignored? Thanks.......
Click to expand...
Click to collapse
Yeah it can be ignored, it's just a wild prop causing it. To be honest I don't use it myself but some people like having every "useful" prop available enabled for them. I personally use it for debugging when a port of mine doesn't work so that I know whether a prop line caused it.
dynamo1950 said:
In addition, for your info, both of my Nexus 5X phones began intermittent boot looping (sticking on Android logo at bootup) after 18 months + of usage this past January. They would need multiple hard resets using the power button to successfully boot into system.
I sent them, one at a time, to the LG Wireless repair center on RMA's. To my surprise, LG repaired each phone by replacing the main board. If I understand correctly, LG has extended its warranty to about 30 months from date of purchase to cover this kind of failure. :good:
There was no cost involved, just the one-way shipping to the repair facility. Again, I did not purchase any extended warranty at time of purchase. Both phones now work fine without that boot loop issue.
Click to expand...
Click to collapse
They didn't for me. LG declined to fix mine due to having a third party repair. I may aswell buy the 4GB RAM mainboard and use that lol.

Can you just share magisk module for miracast enablement for Nexus 6p on Oreo 8.1
Appreciate your hard work on creating these mods

ashu347 said:
Can you just share magisk module for miracast enablement for Nexus 6p on Oreo 8.1
Appreciate your hard work on creating these mods
Click to expand...
Click to collapse
Little Mix zip - that's the one you want
and thanks :laugh:

Awesome...just installed and it works. Nexus 6p ..now enabled to cast ..

LazerL0rd said:
Little Mix zip - that's the one you want
and thanks :laugh:
Click to expand...
Click to collapse
Installed with mm no issues pixel c 8.1 mm 16.4
Miracast originally worked out of the box but stopped on 8
You ever get those pixel libs?

SPL Dust said:
Installed with mm no issues pixel c 8.1 mm 16.4
Miracast originally worked out of the box but stopped on 8
You ever get those pixel libs?
Click to expand...
Click to collapse
Na, no one ever sent it to me . I'd be grateful if anyone can cause Little Mix uses a prop line to tell system to look for that lib when casting.

So far, so good
LazerL0rd said:
These are a few mods that I made recently in order to improve a few bits of our device. This includes some build.prop tweaks, optimized camera libs, and VR support.
Little Mix => enabling Qualcomm Adaptive Display, Miracast (needing a lib from Pixel or Pixel 2 so if u got one DM me), and faster fingerprint detection.
Optimized Camera Libraries => really just self-explanatory, also enables 60fps and 100% quality JPEG photos.
Snappy Prop => build.prop additions, this is a collection of many to enable device features your ROM may not even have. THIS IS MOSTLY USELESS. I got bored and tried porting Snappy Prop to see it's effect that's all.
Daydream => Enables VR support and also improves thermal responsiveness.
Charging Boost => Allows fast charging at higher temperatures, still safe.
White Boot => A Watchdogs inspired bootanimation with a white background. For those Pixel lovers out there. This took 20 mins to upload. XDA is slow.
If anyone wasn't credited for something prove you made it and I'll add ya [almost] instantly to the list below.
Code:
Changelog:
Snappy Prop - removed props relating to rotation
Optimized Camera Libraries - correct placement of camera libs
Charging Boost - an actual magisk module this time :p
Thanks to:
@Miustone for build prop stuff
@ravinder0003 for the charging config
Click to expand...
Click to collapse
Will you be well for now waiting for updates and improvements please and thank you I would like you to specify more about your SNAPPY PRO module and in depth all the modules for which they serve Since your summary is good but I need more depth if I make myself understand I hope you take it in the best way and apologies for my English I am using a translator. I'm using the modules In normal Motorola G4 with 2GB of RAM 8 cores and Android 8.0.1 with magisk root

richardontaneda88 said:
Will you be well for now waiting for updates and improvements please and thank you I would like you to specify more about your SNAPPY PRO module and in depth all the modules for which they serve Since your summary is good but I need more depth if I make myself understand I hope you take it in the best way and apologies for my English I am using a translator. I'm using the modules In normal Motorola G4 with 2GB of RAM 8 cores and Android 8.0.1 with magisk root
Click to expand...
Click to collapse
I’m probably gonna close down this thread and make individual threads for the good modules here. A lot of this was experimental learning stuff for me and it’s embarrassing even some of the dumb stuff I did. Like “Snappy Prop” lmao.
Thanks for your reply tho.

LazerL0rd said:
I’m probably gonna close down this thread and make individual threads for the good modules here. A lot of this was experimental learning stuff for me and it’s embarrassing even some of the dumb stuff I did. Like “Snappy Prop” lmao.
Thanks for your reply tho.
Click to expand...
Click to collapse
You're the one who knows better. Please, before closing this thread, provide the links for the new threads. Thanks!