Hi,
Im running CM11 and i have xposed.
Thus far i cant find an 'easy fix' to remove the dark tint from my lock screen.
1. is there one?
2. if i have to manually modify an xml, which is it and where to find it?
I found one other request of the same nature but it was specific to a HTC handset.
Any help is appreciated.
Cheers.
EDIT; so i found keyguard.xml in framework-res.apk /res/layout.
Pretty sure thats what i need?
Anyway to modify the apk on the fly or do i need to rebuild it then flash again with modified apk?
Really hoping theres an xposed mod ive missed.
=(
Wobzy said:
Hi,
Im running CM11 and i have xposed.
Thus far i cant find an 'easy fix' to remove the dark tint from my lock screen.
1. is there one?
2. if i have to manually modify an xml, which is it and where to find it?
I found one other request of the same nature but it was specific to a HTC handset.
Any help is appreciated.
Cheers.
EDIT; so i found keyguard.xml in framework-res.apk /res/layout.
Pretty sure thats what i need?
Anyway to modify the apk on the fly or do i need to rebuild it then flash again with modified apk?
Really hoping theres an xposed mod ive missed.
=(
Click to expand...
Click to collapse
Try GravityBox Xposed module, in the lock screen settings I believe you can set the background opacity.
guetzli32 said:
Try GravityBox Xposed module, in the lock screen settings I believe you can set the background opacity.
Click to expand...
Click to collapse
Hey thanks for the reply.
Got GB installed, tried that setting, didnt have any effect.
Pretty sure i need to edit the keyguard.xml in framework-res.apk but im not very practised in modifying APKs.
I made a Deodexed custom Lollipop ROM for Note 4 N910C.
Everything is working fine except that Wifi takes time to turn on and it will not save the previous wifi login credentials.
Anyone has deodexed ROM having the same problem? What could be the fix for this?
Thanks.
Any developer can help me with this?
I want to share my custom 830mb Lollipop ROM but only this minor wifi issue I want to fix first
Did you change the build.prop? To set ro.securestorage to 0?
iridaki said:
Did you change the build.prop? To set ro.securestorage to 0?
Click to expand...
Click to collapse
I cannot find this in buildprop, should I add it?
If ro.securestorage.support line is not there add it:
ro.securestorage.support=0
If it's there change 1 to 0.
iridaki said:
If ro.securestorage.support line is not there add it:
ro.securestorage.support=0
If it's there change 1 to 0.
Click to expand...
Click to collapse
Oh my God! Thank you very much. Solved my problem
Hello.
Based on these findings and this commit, I've made a patch to fix the noise cancellation issue. You don't need this if your ROM already has the fix built-in.
This is an universal patch. It is meant to work on every custom ROM
Tested:
-Official CM13
-AOSParadox
-...
If, for some reason, you want to go back to initial state, just flash revert zip
Thanks:
@ashwin007
@saurabh40629
Report back mentioning the ROM you're using.
Downloads
Thank you very much
If I've already done this fix, is it worth flashing the zip in this thread?
Shinr3x said:
If I've already done this fix, is it worth flashing the zip in this thread?
Click to expand...
Click to collapse
I've added a modified audio_platform_info.xml as seen in the ashwin's latest commit.
But if the build.prop alone fixes the noise cancellation issue, then you don't need to flash this.
In the fix from @saurabh40629 the "persist.audio.fluence.speaker" is set to false and here you set it to true. What's the difference? Saurabh40629's fix worked good for me
Rom: official cm13
Honestly, I haven't tested that much.
I wanted to keep inline with the ashwin's commit, since that's the one that will merge on official CM device tree.
Op indicated custom rom. So oss cannot?
Tiongkia said:
Op indicated custom rom. So oss cannot?
Click to expand...
Click to collapse
Oxygen OS does not have the noise cancellation bug.
Loureiro said:
Honestly, I haven't tested that much.
I wanted to keep inline with the ashwin's commit, since that's the one that will merge on official CM device tree.
Click to expand...
Click to collapse
I think what @phoberus meant was that you changed more than Ashwin did.
Ashwin's changes:
Code:
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
Your changes:
Code:
ro.qc.sdk.audio.ssr=false
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
Firefly1337 said:
I think what @phoberus meant was that you changed more than Ashwin did.
Click to expand...
Click to collapse
Yes, the script overrides the values already present on build.prop, making it compatible with any custom ROM.
Ashwin's commit just changed what was missing for CM13.
Loureiro said:
Yes, the script overrides the values already present on build.prop, making it compatible with any custom ROM.
Ashwin's commit just changed what was missing for CM13.
Click to expand...
Click to collapse
Nope, if you look at the full file you'll see that your additional lines aren't there.
Firefly1337 said:
Nope, if you look at the full file you'll see that your additional lines aren't there.
Click to expand...
Click to collapse
You're right.
I might got those from AOSParadox or OOS. But if they have no effect, there's no need to include them.
I'll update with the most recent commit
Loureiro said:
I might got those from AOSParadox or OOS. But if they have no effect, there's no need to include them.
Click to expand...
Click to collapse
That's the problem with these things, we don't know. They might have no effect at all but they could have a negative effect aswell. That's why I wrote my comment in the first place.
Thanks for changing it and thanks for your work
I'm running AOSParadox .Other party , while calling, after flashing the provided zip, reported that the echo was present whenever Loud speaker option is turned on.
After flashing the "revert" zip, the problem got solved.
Sent from my ONE E1003 using XDA-Developers mobile app
sankarshan said:
I'm running AOSParadox .Other party , while calling, after flashing the provided zip, reported that the echo was present whenever Loud speaker option is turned on.
After flashing the "revert" zip, the problem got solved.
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
thanks for reporting.
I'll look into it
i think the patch on ashwin's github is still in testing phase as this commit is different
https://github.com/ashwinr64/androi...mmit/857d8cae45731813859f3afa07fae0bbb3bf9200
well done with the zip anyways, thank you
phoberus said:
In the fix from @saurabh40629 the "persist.audio.fluence.speaker" is set to false and here you set it to true. What's the difference? Saurabh40629's fix worked good for me
Rom: official cm13
Click to expand...
Click to collapse
Yes I had better results when speaker set to false. I used @saurabh40629 fix on Purity Rom . Phone and hands free speaker where 100% better when noise present in background . (I tested in bathroom with exhaust fan on.) Thanks for taking the time to make a flashable zip. Gives some people who are not comfortable editing a good starting point.
That was the main purpose for doing the zip file, to make it easier to apply the patch until ROM devs do the commit. It is easier to apply between nighties
All the credit goes to saurabh40629.
By the way, you can easily edit the zip at your will. Just open it and edit the "patch/fluence_config" file.
I've tested a phone call on speaker mode and persist.audio.fluence.speaker set to true causes echo on the other party. Better leave it off
I'll update the 1st post as soon as I get to my laptop.
1st post updated with these build.prod edits:
Code:
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
It is also included the updated audio_platform_info.xml from here
Hey, thanks for your investigation. What's the difference to ashwin's changes.
I did some testing and it was always a little noisy or the sound was little crappy. Wondering why...
Gesendet von meinem ONE E1003 mit Tapatalk
hi,
adding 'qemu.hw.mainkeys=1' to the buildprop stops my camera from working. im using cm 14.1 on my xt1572
regards
edit; I fixed it using this mod I only had assistant enabled in the aroma installer http://forum.xda-developers.com/onep...7#post70291365
Why would you want your camera to stop working though, that is the question!!!
lmulli said:
Why would you want your camera to stop working though, that is the question!!!
Click to expand...
Click to collapse
its the opposite camera is stopping because I edited the buildprop now the camera is back working
Hi guys
Has anyone got this working? I am on an S8 Port Project Dream 1.3b2
I saw on Youtube some guys has the Navbar working on Ports? Was it removed? Ie buggy etc, or is there an easy way to add it back?
Thanks!
^^rac said:
Hi guys
Has anyone got this working? I am on an S8 Port Project Dream 1.3b2
I saw on Youtube some guys has the Navbar working on Ports? Was it removed? Ie buggy etc, or is there an easy way to add it back?
Thanks!
Click to expand...
Click to collapse
The S7 Edge already has the S8 softkeys installed, but are disabled by default. If rooted, open up build.prop and search for "qemu.hw.mainkeys". Change the value to 0 and reboot.
If u don't find it add this line qemu.hw.mainkeys=0 . Save and reboot
Thanks. Wierd. I tried it? But when I reboot there is nothing. Also. They line is removed from the build.prop?
I'm using es explorer?
I'm not sure if this is useful or not. But I have used system ui and rom control to sac23 s8 port rom.
here
here
mashardpro said:
I'm not sure if this is useful or not. But I have used system ui and rom control to sac23 s8 port rom.
here
here
Click to expand...
Click to collapse
Thanks, can i just flash this and test? Will let you know
^^rac said:
Thanks, can i just flash this and test? Will let you know
Click to expand...
Click to collapse
Yes it might be useful for me someday
It works, I use Renovate Dream Rom. But TouchWiz doesn't agroup five icons on drawer. So, I reedited \System\Build.prop to remove the line qemu.hw.mainkeys=0. S7 doesn't need virtual buttons, it has fisical buttons.