Related
This is for rooted user only (kitkat and Lollipop) (Stock and custom rom)
DO IT AT YOUR OWN RISK AND TAKE A BACKUP OF YOUR SYSTEM BEFORE
i found tweak that work with our moto g . It increases performance and battery draining and battery drop too decrease as compared to stock kernel
Download link-
http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443
(press thanks to dev @k1ks for creating this tweaks)
People who are on stock rom and stock kernel need to install init.d
Custom rom and custom kernel dont need to flash init.d as it already support it
Requirement
busybox and Android terminal emulator(to modify if u want and for uninstall the tweaks) both this app available in playstore
Recommended settings nitro- aggressive (do it from terminal emulator)
stock Lollipop kernel have init.d support?
plantator said:
stock Lollipop kernel have init.d support?
Click to expand...
Click to collapse
Im currently on lollipop 5.0.2 Asian soak version
I flash mallory script which add init.d support then flash this Tweaks
And all is working fine see the Screenshot
i flash it over stock br 5.0.2 without mallory or other scripts and working same to
edit: need to instal mallory to takie init.d support sadly, now working good
plantator said:
i flash it over stock br 5.0.2 without mallory or other scripts and working same to
edit: need to instal mallory to takie init.d support sadly, now working good
Click to expand...
Click to collapse
I have provided flashable init.d.zip. Flash this. That will not work
Delete init.d folder from system/etc and flash this
but mallory gives innit.d support and makeing changes in script working- don't giving errors
plantator said:
but mallory gives innit.d support and makeing changes in script working- don't giving errors
Click to expand...
Click to collapse
But both r use for increase battery and performance which can complicate
First uninstall tweak
Flash init.d
Then again flash nitro
ah ok sure understand, thanks for advices
uninstaled nitro, flashed your init.d but it not appears in system/etc, try twice
plantator said:
ah ok sure understand, thanks for advices
uninstaled nitro, flashed your init.d but it not appears in system/etc, try twice
Click to expand...
Click to collapse
Yeah i too had same problem
Delete init.d file in system /etc and create the folder init.d and reboot . Its now working
ok thanks working for now
plantator said:
ok thanks working for now
Click to expand...
Click to collapse
I found a app on playstore which detect init.d and script installed or not
Guys latest nitro tweaks 2.2 is just awesome wonderful performance and battery give it a try u will love it
http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443
Using this on optimized stock asian 5.0.2 rom. Enabled init.d using Init.d Toggler on app store and installed busy box and terminal emulator. Aftrt enabling init.d l, I flashed the zip from the download page.
Checked via terminal emulator and everything seems to be in order!
Thank you OP for sharing
can i use this with stock recovery?
thanks.
vbnoob said:
can i use this with stock recovery?
thanks.
Click to expand...
Click to collapse
Nope your phone needs to be rooted
abhi0502 said:
Nope your phone needs to be rooted
Click to expand...
Click to collapse
mine is rooted with stock recovery.
how long you phone can lasts after using this mod?
thanks.
vbnoob said:
mine is rooted with stock recovery.
how long you phone can lasts after using this mod?
thanks.
Click to expand...
Click to collapse
It depends how u use it
But performance and smoothness is increased without effecting battery
OldYellowBricks said:
Using this on optimized stock asian 5.0.2 rom. Enabled init.d using Init.d Toggler on app store and installed busy box and terminal emulator. Aftrt enabling init.d l, I flashed the zip from the download page.
Checked via terminal emulator and everything seems to be in order!
Click to expand...
Click to collapse
In case anyone is interested, init.d support can be enabled with Stock Kernel by adding the following to: /system/etc/init.qcom.post_boot.sh
/system/etc/init.d/*
lost101 said:
In case anyone is interested, init.d support can be enabled with Stock Kernel by adding the following to: /system/etc/init.qcom.post_boot.sh
/system/etc/init.d/*
Click to expand...
Click to collapse
This does not work for me. Exactly how and where do I put this line? By the way, while were talking about init.d, init.d doesn't work in your XT1031 Stock Optimized 4.4.4 ROM with Archidroid init.d. Been meaning to go on your thread and mention this.
amarc78 said:
This does not work for me. Exactly how and where do I put this line? By the way, while were talking about init.d, init.d doesn't work in your XT1031 Stock Optimized 4.4.4 ROM with Archidroid init.d. Been meaning to go on your thread and mention this.
Click to expand...
Click to collapse
U can check this out for init.d support
http://forum.xda-developers.com/showthread.php?t=1933849
Hello
I got tired waiting for an official fix, so I came up with this workaround.
twrp-flashable_OPX2.2.0_camera_patch.zip - This zip with apply the OPX front camera configuration.
twrp-flashable_OPX_camera_patch_imx214.zip - This zip will apply the OPO rear camera configuration
You'll be able to record 1080p at night without worrying about the fps drop issue.
I am not responsible for any damage on your device when applying this patch.
EDIT: Added a revert flashable zip.
EDIT2: Added zip file with imx214 libchromatix_default_video.so
Sweet. Thanks
Swapped my Recent and Back buttons.
Edit:
A couple reboots might've fixed this, but I also messed with Gravity Box a bit as well. There's two options to fixing that problem, potentially.
RJMacReady said:
Swapped my Recent and Back buttons.
Edit:
A couple reboots might've fixed this, but I also messed with Gravity Box a bit as well. There's two options to fixing that problem, potentially.
Click to expand...
Click to collapse
This patch shouldn't mess with buttons layout. You might had a pending operation that took effect on reboot when you flashed this zip.
try hydrogen os.
does your phone need to be rooted or will it work fine with stock?
Does this patch works also with custom roms like cm13?
Sorry. This patch is for default camera only? Or its for any camera apps running on oss 2.20?
It works perfect now, thank you so much for this mod. Where did this libs came from?
Shame on One Plus btw.
#E1005
Loureiro said:
This patch shouldn't mess with buttons layout. You might had a pending operation that took effect on reboot when you flashed this zip.
Click to expand...
Click to collapse
Maybe, maybe not. Just letting people know a few reboots might help.
Thank you for the patch!
Great work mate, Oneplus have to work really hard about software
Loureiro said:
This patch will replace the binary file libchromatix_s5k3m2_default_video.so
Click to expand...
Click to collapse
did you take it from s4 or hydrogenos?
do you think any more improvements are possible by replacing the blobs?
Can anybody upload a sample on YT? Please I wan't to see what is this beauty capable of in low light video. Maybe I'll pop the cherry of my OPX and root it tomorrow OP thanks for the fix!
Loureiro said:
Hello
I got tired waiting for an official fix, so I came up with this workaround.
This patch will replace the binary file libchromatix_s5k3m2_default_video.so
You'll be able to record 1080p at night without worrying about the fps drop issue.
This has been tested on my device only.
I am not responsible for any damage on your device when applying this patch.
Do a system backup if you're worried.
EDIT: I've added a revert flashable zip.
Click to expand...
Click to collapse
Great job! What did you need to change in that file to get it done?
5star02707 said:
does your phone need to be rooted or will it work fine with stock?
Click to expand...
Click to collapse
No. You just need a recovery to flash the zip file
logan99 said:
Does this patch works also with custom roms like cm13?
Click to expand...
Click to collapse
I should work if the custom rom uses the same BLObs as Oxygen OS.
It means that, for now, it works on cm12.1 and cm13
Tiongkia said:
Sorry. This patch is for default camera only? Or its for any camera apps running on oss 2.20?
Click to expand...
Click to collapse
This patch is system wide. Any camera app will work with this.
ChavitoArg said:
It works perfect now, thank you so much for this mod. Where did this libs came from?
Shame on One Plus btw.
#E1005
Click to expand...
Click to collapse
ckret said:
did you take it from s4 or hydrogenos?
do you think any more improvements are possible by replacing the blobs?
Click to expand...
Click to collapse
I've tested other s5k3m2 binaries from other devices but they all miss some needed instructions.
This is the front camera binary
tested the imx214 file but it pushes iso way too high.
Awesome. Thank you OP
Loureiro said:
No. You just need a recovery to flash the zip file
I should work if the custom rom uses the same BLObs as Oxygen OS.
It means that, for now, it works on cm12.1 and cm13
This patch is system wide. Any camera app will work with this.
I've tested other s5k3m2 binaries from other devices but they all miss some needed instructions.
This is the front camera binary
tested the imx214 file but it pushes iso way too high.
Click to expand...
Click to collapse
Wait it does not require root and a custom recovery?
alabama20 said:
Wait it does not require root and a custom recovery?
Click to expand...
Click to collapse
root =! custom recovery
You need custom recovery to flash this.
ChavitoArg said:
root =! custom recovery
You need custom recovery to flash this.
Click to expand...
Click to collapse
I know what is what, I was just asking -.-"
alabama20 said:
I know what is what, I was just asking -.-"
Click to expand...
Click to collapse
Sorry, I forgot to say that custom recovery is needed
Right so many of us use stock rom on A500FU (2015) as its a good daily driver. Not the issue is I'm useless at compiling so is there anyone who can compile a stock kernel but... permissive as standard for us viper4android users and other reason, I'm sure there are 1000s who would appreciate it. I can provide the stock boot if nessacary
Sent from my SM-A500FU
jimbomodder said:
Right so many of us use stock rom on A500FU (2015) as its a good daily driver. Not the issue is I'm useless at compiling so is there anyone who can compile a stock kernel but... permissive as standard for us viper4android users and other reason, I'm sure there are 1000s who would appreciate it. I can provide the stock boot if nessacary
Sent from my SM-A500FU
Click to expand...
Click to collapse
Here you go:
A500FUXXU1BOL1_permissive_boot
.
ashyx said:
Here you go:
A500FUXXU1BOL1_permissive_boot
.
Click to expand...
Click to collapse
Thanks man but it hangs on splash then reboots constantly
Sent from my SM-A500FU
jimbomodder said:
Thanks man but it hangs on splash then reboots constantly
Sent from my SM-A500FU
Click to expand...
Click to collapse
Which firmware build are you on?
Can you post up your boot.img?
Try this one: A500FUXXU1BOL1_permissive_boot
ashyx said:
Which firmware build are you on?
Can you post up your boot.img?
Click to expand...
Click to collapse
Here you go
ashyx said:
Which firmware build are you on?
Can you post up your boot.img?
Try this one: A500FUXXU1BOL1_permissive_boot
Click to expand...
Click to collapse
Get kernel warning but just hangs at splash.
Sent from my SM-A500FU
jimbomodder said:
Get kernel warning but just hangs at splash.
Sent from my SM-A500FU
Click to expand...
Click to collapse
I have recompiled the kernel with no changes except set the enforcing flag to false and used your ramdisk.
If this doesn't boot then Samsungs source code is probably borked.
I have also uploaded a simply unpacked and repacked kernel with absolutely no changes. If this doesn't boot then there's an issue with simply repacking the kernel which could be because it is unsigned. This is not the first time Ive had this happen.
https://www.androidfilehost.com/?fid=24533103863137813
https://www.androidfilehost.com/?fid=24533103863137814
ashyx said:
I have recompiled the kernel with no changes except set the enforcing flag to false and used your ramdisk.
If this doesn't boot then Samsungs source code is probably borked.
I have also uploaded a simply unpacked and repacked kernel with absolutely no changes. If this doesn't boot then there's an issue with simply repacking the kernel which could be because it is unsigned. This is not the first time Ive had this happen.
https://www.androidfilehost.com/?fid=24533103863137813
https://www.androidfilehost.com/?fid=24533103863137814
Click to expand...
Click to collapse
First one hangs, second boots with the warning
jimbomodder said:
First one hangs, second boots with the warning
Click to expand...
Click to collapse
This is the exact same situation I had with the Tab A which uses the same platform and source code: Qualcomm MSM8916 Snapdragon 410.
Looks like again Samsung have fudged up the kernel source.
Are you able to set permissive via ADB or SElinux changer?
ashyx said:
This is the exact same situation I had with the Tab A which uses the same platform and source code: Qualcomm MSM8916 Snapdragon 410.
Looks like again Samsung have fudged up the kernel source.
Are you able to set permissive via ADB or SElinux changer?
Click to expand...
Click to collapse
Yeah selinux changer works fine. Thanks for the efforts
jimbomodder said:
Yeah selinux changer works fine. Thanks for the efforts
Click to expand...
Click to collapse
Well you're lucky that actually works. It usually doesn't.
Are you sure it states permissive in settings after using SElinux changer?
ashyx said:
Well you're lucky that actually works. It usually doesn't.
Are you sure it states permissive in settings after using SElinux changer?
Click to expand...
Click to collapse
Yes I check it, now and again Google flags as dangerous but I keep it lol
Sent from my SM-A500FU
jimbomodder said:
Yes I check it, now and again Google flags as dangerous but I keep it lol
Sent from my SM-A500FU
Click to expand...
Click to collapse
Any chance I can see a screen shot of that as its unusual?
ashyx said:
Any chance I can see a screen shot of that as its unusual?
Click to expand...
Click to collapse
The dangerous part? It normal as ive allowed google to check for harmful apps and an app they changes the selinux is dangerous to google, ill get one soon as currently on RR
Sent From either S4, S4 mini, S5 neo, A500FU, T210, T230
jimbomodder said:
The dangerous part? It normal as ive allowed google to check for harmful apps and an app they changes the selinux is dangerous to google, ill get one soon as currently on RR
Sent From either S4, S4 mini, S5 neo, A500FU, T210, T230
Click to expand...
Click to collapse
Just the about page where it says permissive.
ashyx said:
Just the about page where it says permissive.
Click to expand...
Click to collapse
I'll get it later today:good:
ashyx said:
Just the about page where it says permissive.
Click to expand...
Click to collapse
Better late than never
Highly unusual, every single Samsung 5.1.1 kernel I have compiled always has the enforcing flag set in the configuration without the ability to override unless the kernel is custom.
ashyx said:
Highly unusual, every single Samsung 5.1.1 kernel I have compiled always has the enforcing flag set in the configuration without the ability to override unless the kernel is custom.
Click to expand...
Click to collapse
Well it's actually 5.0.2, I just changed it in build prop. I also deleted some of the security apks and no longer get a warning that it's permissive and need to reboot, also the smart manager says system is secure. Running viper4android just fine
Hello,
this thread is only for development discussion about enabling camera2 api on xperia camera. If you have anything useful, it's the right place, however, it's not for non-dev things.
What are we going to do ?
The best way for enabling camera2 api is porting camera hal from sony aosp camera.
So I have attached sony aosp camera hal at this thread. We should do some modifications on kernel to make it working on stock rom.
Current Status : CSID needs to be updated on kernel
This can help us :
https://github.com/sonyxperiadev/ke...rch/arm/boot/dts/qcom/msm8974-camera.dtsi#L63
*Before testing camera hal, you should do 2 important works :
1. Remove following line from default.prop located at ramdisk : (At the moment, this is optional)
camera2.portability.force_api=1
2. Go to system>lib>hw and delete camera.qcom.so (This one is necessary)
Thanks To:
@davidteri91
@aquaboy11
works with cm12? or only with stock?
brickhayabusa said:
works with cm12? or only with stock?
Click to expand...
Click to collapse
This is dev only thread bro :laugh:
EugenStanis said:
This is dev only thread bro
Click to expand...
Click to collapse
i know, but if you read, he wrote "Need some testers to test attached camera hal on Z1/Z1C"
PS: you're not a dev too
I will get myself multirom to run stock, if it works I will start testing and try to edit the kernel. If we do it properly, we could maintain BIONZ right?
brickhayabusa said:
i know, but if you read, he wrote "Need some testers to test attached camera hal on Z1/Z1C"
PS: you're not a dev too
Click to expand...
Click to collapse
Well it doesnt need to have the physical RD or SRD title to have the privilege to post in DEV-ONLY thread, as long as you are contributing to the project on DEV basis.
aquaboy11 said:
I will get myself multirom to run stock, if it works I will start testing and try to edit the kernel. If we do it properly, we could maintain BIONZ right?
Click to expand...
Click to collapse
Thanks.
Nope, we can't have Bionz and a new camera hal at the same time
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
when i wanred to test it i dont understand this "Before testing camera hal, you should do 2 important works :
1. Remove following line from default.prop located at ramdisk : (At the moment, this is optional)
camera2.portability.force_api=1
2. Go to system>lib>hw and delete camera.qcom.so (This one is necessary)"
and i forgot about it)
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
I don't have a z1/z1c ...but i can try it on z2 mm if you want. If this mod was for z2 i'm the first who became your betatester. If you extend the compatibility with z2 or you want a betatester for one of your mods for z2 variant...just contact me
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
I tried so:
I removed the line as noted in Step 1
I extracted the file and copied to the folder "system" (with overwriting files)
Result: bootloop
I dont have a z1/z1c. I can became your tester on my z2.
mkdmc said:
Everyone is asking for camera2 api and raw
But
No one has tested this after 1 month
So don't ask me again for raw!
Click to expand...
Click to collapse
Hey, I could not get multirom to work. I also had quite some stuff to do for school so I could not test either. Today I switched back to stock rom and will have more time the coming weeks.
I did as you said, except for the default.prop. Put all the right permissions, copied over the files, and rebooted. The camera, as expected, does not work, so I captured a logcat and dmesg.
Sorry for taking so long .
aquaboy11 said:
Hey, I could not get multirom to work. I also had quite some stuff to do for school so I could not test either. Today I switched back to stock rom and will have more time the coming weeks.
I did as you said, except for the default.prop. Put all the right permissions, copied over the files, and rebooted. The camera, as expected, does not work, so I captured a logcat and dmesg.
Sorry for taking so long .
Click to expand...
Click to collapse
Thanks a lot for testing
It seems csid is incorrect
Kernel needs to be updated
mkdmc said:
Thanks a lot for testing
It seems csid is incorrect
Kernel needs to be updated
Click to expand...
Click to collapse
Which HAL did you use? Also, could you explain a bit more about csid, and how we should fix it? Would getting drivers from the AOSP kernel be any good, or should the stock code itself be updated?
aquaboy11 said:
Which HAL did you use? Also, could you explain a bit more about csid, and how we should fix it? Would getting drivers from the AOSP kernel be any good, or should the stock code itself be updated?
Click to expand...
Click to collapse
Latest AOSP 5.1.1 camera HAL.
I'm not sure how we can update csid btw we should use aosp kernel drivers.
This can help us :
https://github.com/sonyxperiadev/ke...rch/arm/boot/dts/qcom/msm8974-camera.dtsi#L63
mkdmc said:
Latest AOSP 5.1.1 camera HAL.
I'm not sure how we can update csid btw we should use aosp kernel drivers.
This can help us :
https://github.com/sonyxperiadev/ke...rch/arm/boot/dts/qcom/msm8974-camera.dtsi#L63
Click to expand...
Click to collapse
I'll play around with the kernels a bit to see if I can get something to work.
EDIT:
Doesn't seem like I can .
EDIT 2:
Is it safe to have Cyberian installed? Or should I reflash stock every time before testing?
Please provide the download link for kcal.zip file which can be used for screen color adjustments in kernel auditor.
I accidently deleted that file, if anyone here has it please share it.
ch3tan007 said:
Please provide the download link for kcal.zip file which can be used for screen color adjustments in kernel auditor.
I accidently deleted that file, if anyone here has it please share it.
Click to expand...
Click to collapse
Kcal is actually the hardware's display settings exposed by a sysfs interface
What zip? You need to compile a kernel with the patch to get this feature
anupritaisno1 said:
Kcal is actually the hardware's display settings exposed by a sysfs interface
What zip? You need to compile a kernel with the patch to get this feature
Click to expand...
Click to collapse
I somewhere found the kcal zip file which i flashed over h20s stock rom for color adjustments. But yesterday i accidently formatted my phone so need that file again.
ch3tan007 said:
I somewhere found the kcal zip file which i flashed over h20s stock rom for color adjustments. But yesterday i accidently formatted my phone so need that file again.
Click to expand...
Click to collapse
Are you sure you didn't unknowingly flash a kernel?
Because what you're saying is impossible without touching boot.img
anupritaisno1 said:
Are you sure you didn't unknowingly flash a kernel?
Because what you're saying is impossible without touching boot.img
Click to expand...
Click to collapse
Donno mate but when i checked kernel version in about pbone all were stock and i could see screen options in kernel auditor
ch3tan007 said:
Donno mate but when i checked kernel version in about pbone all were stock and i could see screen options in kernel auditor
Click to expand...
Click to collapse
I can make the kernel show perf+ too
Just need to change one variable in the defconfig and 2 exported variables in the shell
Why don't you try a ROM that comes with kcal, like seraph's build or try out something like halogenos
Or maybe you can find my thread in the development session and flash my ROM and custom kernel from there?
Anyways if you want kcal on hydrogenos, boeffla kernel, I'm not going to say it again
anupritaisno1 said:
I can make the kernel show perf+ too
Just need to change one variable in the defconfig and 2 exported variables in the shell
Why don't you try a ROM that comes with kcal, like seraph's build or try out something like halogenos
Or maybe you can find my thread in the development session and flash my ROM and custom kernel from there?
Anyways if you want kcal on hydrogenos, boeffla kernel, I'm not going to say it again
Click to expand...
Click to collapse
I have tried seraph's and other cm14.1 based rom, yes sure will give a try to ur rom too microg looks useful feature.:good:
Thanks for ur replies.