Database Users

[Q] Remove Camera Click Sound

Heya, new to fiddling with root files but really wanted to get rid of camera click. Followed advice about renaming camera_click.ogg in terminal Emulator using:
ADB shell
SU
mount -o remount,rw /dev/block/mtdblock4 /system
mv /system/media/audio/ui/camer_click.ogg /system/media/audio/ui/camera_click.ogg.old
(source: www droidforums net/forum/droid-hacks/23107-droid-remove-camera-click-shutter-sound html) - sorry new poster not allowed to post url
Now have issue when open stock camera and vid in Motorola Atrix (gingerbread 2.2.2) where:
1) camera opens, but have lost all previous images.
2) camera takes silent shot
3) camera 'locks' open and can't return to 'desktop', can't view image taken,, can't access menus etc
Basically camera is stuffed...
is there a solution, is there code to go back and follow some of the other advice in here etc?

It is a setting. What's the point?
Sent from my MB860 using xda premium

it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!

have you tried to add the following line to local.prop file located in /data?
ro.camera.sound.forced=0
If you don't have the file then just create the file and add it, otherwise append it to the end of file.
File permission is: 0644
Good Luck

I never heard of adding ".old" on the end of the file. I always add ".bak", then reboot. Works everytime.
EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse

I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk

Thanks for pointing that out, that gave me a good laugh to start the day off.
Phalanx7621 said:
I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse

EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse
I was on my phone at the time (tiny keyboard) and was trying to succinctly say that if you open the camera app and touch "settings", there is an option to quiet the click.
When I first read your OP I didn't notice that you identified Gingerbread as v2.2. You are confused. v2.2 was named Froyo (frozen yogurt). Gingerbread is v2.3. My answer relates to Gingerbread. If you are actually on Froyo, I don't remember if the setting was available on that release.
So, in Gingerbread silencing the camera is a setting and there is no point performing internal surgery.

Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice

Seriously....why would you want to silence your camera again?

Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
EchoK8 said:
Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice
Click to expand...
Click to collapse

I'd like to replace my shutter sound. Does anyone have a sound file of a shotgun blast/ slide rack?

Thannnks

island-guy said:
Seriously....why would you want to silence your camera again?
Click to expand...
Click to collapse
i actually dont want or need to silence it again. my query is how to restore my camera to a mode where it is functional bcs at the moment its stuffed. If theres a simple string to go back that'd be ideal.

live4nyy said:
Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
Click to expand...
Click to collapse
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta

Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
EchoK8 said:
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta
Click to expand...
Click to collapse

live4nyy said:
Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
Click to expand...
Click to collapse
Thanks L4NYY.. yep had rebooted. Tried clearing data but all the same
Had a quick look in the internal storage DCIM folder..All files appear to be there. The one vid file has a play button icon. The .jpg's have the android robot icon. I don't know what was there before. Trying to open the files from here freezes the phone.....
Connecting usb and viewing dcim shows that any images taken since the change to camera_click.ogg appear unknown thumnails in the PC explorer..and can't be opened on the PC via USB connection or when stored locally on the PC itself 'can't display this is an empty file' . This is probably all irrelevant but might be useful to someone, somehere...

Have just noticed today that battery was going flat very quickly. Realised since rooting and using that script (can't decipher which) that location services are no longer working, hence apps that provide location services are continually searching and draining battery. Yes i can turn those services off, but wouldrather resolve the issue!
I'm thinking more and more like factory reset Any thoughts?

Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao

The ".bak" just stands for "backup". It will essentially hide any file/app and keep it from running (which in turn frees up RAM). So if you had a system app that you don't use you can just add ".bak" and it would be the same as freezing it. It's much safer than deleting files and apps as you can always go back and remove the extension (and reboot) and it will be back to normal.
EchoK8 said:
Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao
Click to expand...
Click to collapse

Nexus Q LED and Cyanogen

Is there any way to control the LEDs with Cyanogen installed?

AstroPuls3 said:
Is there any way to control the LEDs with Cyanogen installed?
Click to expand...
Click to collapse
i noticed that too. Seems to be missing a service that qremote uses.

I would just at least like it to pulse different colors, or at the very least I would like to have control over which color the ring is..I wonder if anything is in the works

AstroPuls3 said:
I would just at least like it to pulse different colors, or at the very least I would like to have control over which color the ring is..I wonder if anything is in the works
Click to expand...
Click to collapse
i know anthony was talking about leaving them pink when he was developing cm10 for the q. might search or ask him. there are (or were) some commands that could be issued to change the colors.

I'd also like to be able to just turn them off. I'm pretty sure LightFlow is able to control the LEDs as normal because I noticed the other day my ring was white from a notification.
I think setting it to 255 255 255 might do the trick if we can figure out a way to set a persistent value.
Sent from my Nexus 4 using Tapatalk 2

Malnilion said:
I'd also like to be able to just turn them off. I'm pretty sure LightFlow is able to control the LEDs as normal because I noticed the other day my ring was white from a notification.
I think setting it to 255 255 255 might do the trick if we can figure out a way to set a persistent value.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So I tried Lightflow, and it disabled the Q from adjusting the volume with the sphere, and it didn't change any colors. I have to find something..

LEDs
Actually, looking at the CM 10.1 source for steelhead - there's some pretty easy to understand code in there for the LEDs - and even a clue about the LEDs - try doing a setprop on 'persist.sys.ringcolor' - set the value to the _integer_ value of the RGB you want (default is 14428 - aka 0x00385C - pale blue in RRGGBB) - and reboot. I'm going to start work on something a bit more interesting - maybe even an audiotap that will let you know the audio on the LEDs (like the Q did) - or set them with a visual tool (child's play).
---------- Post added at 11:07 PM ---------- Previous post was at 10:51 PM ----------
BitVenom said:
Actually, looking at the CM 10.1 source for steelhead - there's some pretty easy to understand code in there for the LEDs - and even a clue about the LEDs - try doing a setprop on 'persist.sys.ringcolor' - set the value to the _integer_ value of the RGB you want (default is 14428 - aka 0x00385C - pale blue in RRGGBB) - and reboot. I'm going to start work on something a bit more interesting - maybe even an audiotap that will let you know the audio on the LEDs (like the Q did) - or set them with a visual tool (child's play).
Click to expand...
Click to collapse
Actually - I just did the tests - and indeed, you can just live set that prop and it will change. I wish the author had thought to support 0xRRGGBB format (dude, check the string for 0x!) - but it's a start. All kinds of fun projects will come from this...

BitVenom said:
Actually, looking at the CM 10.1 source for steelhead - there's some pretty easy to understand code in there for the LEDs - and even a clue about the LEDs - try doing a setprop on 'persist.sys.ringcolor' - set the value to the _integer_ value of the RGB you want (default is 14428 - aka 0x00385C - pale blue in RRGGBB) - and reboot. I'm going to start work on something a bit more interesting - maybe even an audiotap that will let you know the audio on the LEDs (like the Q did) - or set them with a visual tool (child's play).
---------- Post added at 11:07 PM ---------- Previous post was at 10:51 PM ----------
Actually - I just did the tests - and indeed, you can just live set that prop and it will change. I wish the author had thought to support 0xRRGGBB format (dude, check the string for 0x!) - but it's a start. All kinds of fun projects will come from this...
Click to expand...
Click to collapse
I have no idea how to do that, is there a link that can help me, or a tutorial? lol Sorry, not that skilled with code yet.

AstroPuls3 said:
I have no idea how to do that, is there a link that can help me, or a tutorial? lol Sorry, not that skilled with code yet.
Click to expand...
Click to collapse
If you were able to install CM10.1 - you shouldn't have any issue with that...
Just in a terminal prompt - much like installing CM10.1 - with adb:
adb shell
su
setprop persist.sys.ringcolor 14428 (DEFAULT color!)
setprop persist.sys.ringcolor 8288 (0x2040 - so in RGB - that's blue with a bit of green)
Experiment with the values you set to get the right color for you. I'll be working on an app for this soon enough...

Thank you!
If anyone wants to turn the LEDs off:
setprop persist.sys.ringcolor 0
I think I'm going to make a Tasker toggle on my phone to connect to my Q via network ADB and change the color.
Sent from my Nexus 4 using Tapatalk 2

I am glad I am not the only one who sort of wanted to do something with the LEDs. I get you can customize it and flash, but are there any apps that allow you to change it on the fly? Are any apps Q enabled such that they can manipulate the LED ring? I was hoping Play Music would at least have a visualization that might do it.
I love the added functionality of CM (google pretty much killed what little was there out of the box by now) but I kind of feel the ring might as well not even be there as it doesn't do anything anymore.
Ben

I use Lightflow to control the LED.
Sent from my Nexus Q using XDA Premium 4 mobile app

Does that app mimic the original functionality of the visualization of the LEDs while music is playing?
Sent from my DROID RAZR using xda app-developers app

BitVenom said:
Actually, looking at the CM 10.1 source for steelhead - there's some pretty easy to understand code in there for the LEDs - and even a clue about the LEDs - try doing a setprop on 'persist.sys.ringcolor' - set the value to the _integer_ value of the RGB you want (default is 14428 - aka 0x00385C - pale blue in RRGGBB) - and reboot. I'm going to start work on something a bit more interesting - maybe even an audiotap that will let you know the audio on the LEDs (like the Q did) - or set them with a visual tool (child's play).
---------- Post added at 11:07 PM ---------- Previous post was at 10:51 PM ----------
Actually - I just did the tests - and indeed, you can just live set that prop and it will change. I wish the author had thought to support 0xRRGGBB format (dude, check the string for 0x!) - but it's a start. All kinds of fun projects will come from this...
Click to expand...
Click to collapse
is there anything to set other than ring color? maybe the individual ring leds or the mute button?

animal24 said:
is there anything to set other than ring color? maybe the individual ring leds or the mute button?
Click to expand...
Click to collapse
So... About that. There is a binary called "avrlights" that exists in standard CM10+ that allows for settings LEDs, but it's far from perfect. Seeing the flaws with this, I've rewritten avrlights (source file lightsctl.c) to allow for the setting of each LED in the ring along with the mute LED. For now, this is just a program you run from a shell.
My end goal is to basically have the original LED functionality of the Q restored. To this end, I'm working on some other handy bits. If you're interested in trying it out, you can pull the changes from my Github and build yourself. I'll throw up a link to a few build zips some time.

mcsaucy said:
So... About that. There is a binary called "avrlights" that exists in standard CM10+ that allows for settings LEDs, but it's far from perfect. Seeing the flaws with this, I've rewritten avrlights (source file lightsctl.c) to allow for the setting of each LED in the ring along with the mute LED. For now, this is just a program you run from a shell.
My end goal is to basically have the original LED functionality of the Q restored. To this end, I'm working on some other handy bits. If you're interested in trying it out, you can pull the changes from my Github and build yourself. I'll throw up a link to a few build zips some time.
Click to expand...
Click to collapse
Ah, so just avr lights from a prompt or adb shell? Is there an avrlights help in shell?
Also, throw up a link, I want to buy you a beer for even trying.

animal24 said:
Ah, so just avr lights from a prompt or adb shell? Is there an avrlights help in shell?
Also, throw up a link, I want to buy you a beer for even trying.
Click to expand...
Click to collapse
There is no help functionality, unfortunately. I think I'll add that in today. I'll put up a link once I can actually post them.
EDIT:: just added a usage message complete with examples
EDIT #2:: and now that I can post links, you can find my current build at http://daedalus.csh.rit.edu (uptime not really guaranteed). The most up-to-date version is in "untested" and includes the help documentation.
EDIT #4:: I've started marking the most up-to-date version current for the sake of convenience. Play with avrlights and hsv2rgb if you're feeling it.

mcsaucy said:
There is no help functionality, unfortunately. I think I'll add that in today. I'll put up a link once I can actually post them.
EDIT:: just added a usage message complete with examples
EDIT #2:: and now that I can post links, you can find my current build at http://daedalus.csh.rit.edu (uptime not really guaranteed). The most up-to-date version is in "untested" and includes the help documentation.
Click to expand...
Click to collapse
10.2?

animal24 said:
10.2?
Click to expand...
Click to collapse
Yup. I plan to take a stab at CM11 next.

mcsaucy said:
There is no help functionality, unfortunately. I think I'll add that in today. I'll put up a link once I can actually post them.
EDIT:: just added a usage message complete with examples
EDIT #2:: and now that I can post links, you can find my current build at http://daedalus.csh.rit.edu (uptime not really guaranteed). The most up-to-date version is in "untested" and includes the help documentation.
Click to expand...
Click to collapse
Thanks for this, I am having way too much fun! Hope this can get merged in the CM source tree.
Heres a nice bouncing rainbow script for anyone who wants to mess around.
http://pastebin.com/nd0Bpnus

[Q] Malicious daily "alarm"

I have an issue that is making me crazy. Starting about 1 month ago, my N7 plays a very annoying "tune" for about 1-2 minutes precisely at 12:35 AM every day.
Some specifics:
- volume cannot be controlled or muted
- the "tune" that is played is not one of the normal choices. It is kind of crude sounding (like MIDI).
- does not provide any notification of any kind or show up as a running app
- does not appear to be associated with clock or calendar
- the only way to stop it is to power off
Steps I have taken to try to kill this thing (leaving out the obvious)
- "soft" factory reset/restore from N7 Settings menu - fail
- "Hard" facory reset using power/volume controls. Did not do a restore.. Only logged onto wireless and into my Google account . - fail
- complete wipe/reflash using adb/fastboot/nakasi image from Google developer page instructions. - fail
I'm a complete Android noob, but not a software/hardware noob. This defies logic to me. I found reference to a very similar problem on another forum, but the post was never answered. I have several other Android devices and none have this issue. I'm convinced that this is something malicious. Where is this thing hiding that it can survive a reflash? Please help, I'm beginning to think my N7 is haunted.

Bump for help
Sorry to bump this but it appears that the views have stopped and so far no replies. As noted in my original post I have seen this issue reported elsewhere but not solved. I even tried loading Cyanogenmod and it's still there! I realize that asking for help on you first post is asking a lot, but I really could use some help/suggestions. Is there somewhere in the file system I should look for the code that is running this? Are there monitoring tools I could use to identify the process that is running? Are there log files somewhere I could look at?
Besides being really annoying, it's hard to feel secure when something like this keeps coming back after the device has supposedly been wiped multiple times. If I can't solve it, it's probably going to get beaten to a pulp with a sledgehammer! Thanks for any suggestions.
gdbbcmi said:
I have an issue that is making me crazy. Starting about 1 month ago, my N7 plays a very annoying "tune" for about 1-2 minutes precisely at 12:35 AM every day.
Some specifics:
- volume cannot be controlled or muted
- the "tune" that is played is not one of the normal choices. It is kind of crude sounding (like MIDI).
- does not provide any notification of any kind or show up as a running app
- does not appear to be associated with clock or calendar
- the only way to stop it is to power off
Steps I have taken to try to kill this thing (leaving out the obvious)
- "soft" factory reset/restore from N7 Settings menu - fail
- "Hard" facory reset using power/volume controls. Did not do a restore.. Only logged onto wireless and into my Google account . - fail
- complete wipe/reflash using adb/fastboot/nakasi image from Google developer page instructions. - fail
I'm a complete Android noob, but not a software/hardware noob. This defies logic to me. I found reference to a very similar problem on another forum, but the post was never answered. I have several other Android devices and none have this issue. I'm convinced that this is something malicious. Where is this thing hiding that it can survive a reflash? Please help, I'm beginning to think my N7 is haunted.
Click to expand...
Click to collapse

Solved!
This is solved. I'd like to say I know exactly what worked, but apparently after the umpteenth wipe/re-flash, the poltergeist got bored and moved on. Thanks for thinking about it.
gdbbcmi said:
Sorry to bump this but it appears that the views have stopped and so far no replies. As noted in my original post I have seen this issue reported elsewhere but not solved. I even tried loading Cyanogenmod and it's still there! I realize that asking for help on you first post is asking a lot, but I really could use some help/suggestions. Is there somewhere in the file system I should look for the code that is running this? Are there monitoring tools I could use to identify the process that is running? Are there log files somewhere I could look at?
Besides being really annoying, it's hard to feel secure when something like this keeps coming back after the device has supposedly been wiped multiple times. If I can't solve it, it's probably going to get beaten to a pulp with a sledgehammer! Thanks for any suggestions.
Click to expand...
Click to collapse

always on display

moderator please feel free to move this to correct section thank you
ok i already know that this is probably in the wrong section but my post count is not high enough to post in other section
i have my rooted verizon note 4 (sm-910v) i rooted it my phone with dr.keaton rom for the s7edge and its awesome everything works great
i seen that the always on display does not work like everyone said so i tried my self to make it work and like other people are saying you can see it in settings but cant see it on the shut off screen .......
well i can i went to the internet and typed in samsung aod apk and downloaded 1.7.3.4 and when in google play and downloaded fx files explorer with the root add on for it then went into sysyem root found priv app the aodservice and deleted everything that was in folder and copied my new aod in then added a second copy of it as well i named one AODService.apk and named the second one AODService.apk.bak and set both security permissions to 644
and taa daa it works you can go to settings turn it on open it up change clocks etc and even see it on the lock screen know but the problem is that its very dim hard to see it
anyone in here with more knowledge then me to go into the xml settings or what ever you call it to change the brightness setting or what ever so you can actually see it better on the lock screen
lots of people could not even get it to the lock screen or even get it to turn on i figured that all out just need someone with more knowledge now to fix the brightness of it and we will all have working aod

note2junky said:
moderator please feel free to move this to correct section thank you
ok i already know that this is probably in the wrong section but my post count is not high enough to post in other section
i have my rooted verizon note 4 (sm-910v) i rooted it my phone with dr.keaton rom for the s7edge and its awesome everything works great
i seen that the always on display does not work like everyone said so i tried my self to make it work and like other people are saying you can see it in settings but cant see it on the shut off screen .......
well i can i went to the internet and typed in samsung aod apk and downloaded 1.7.3.4 and when in google play and downloaded fx files explorer with the root add on for it then went into sysyem root found priv app the aodservice and deleted everything that was in folder and copied my new aod in then added a second copy of it as well i named one AODService.apk and named the second one AODService.apk.bak and set both security permissions to 644
and taa daa it works you can go to settings turn it on open it up change clocks etc and even see it on the lock screen know but the problem is that its very dim hard to see it
anyone in here with more knowledge then me to go into the xml settings or what ever you call it to change the brightness setting or what ever so you can actually see it better on the lock screen
lots of people could not even get it to the lock screen or even get it to turn on i figured that all out just need someone with more knowledge now to fix the brightness of it and we will all have working aod
Click to expand...
Click to collapse
Just to sum the situation up:
These bugs are known. Yes, with proper apk's you can get it to show up. With an XPosecd module you can change the brightness, but in the end it breaks autobrightnes completely. After AOD activates, your phone won't change brightness anymore.
All in all, you could get it to work somehow, but if you plan to use your display in varying brightnesses you won't be happy. I've invested several days worth of research. I just accepted the fact, that samys AOD won't work on our device right now.

domsch1988 said:
Just to sum the situation up:
These bugs are known. Yes, with proper apk's you can get it to show up. With an XPosecd module you can change the brightness, but in the end it breaks autobrightnes completely. After AOD activates, your phone won't change brightness anymore.
All in all, you could get it to work somehow, but if you plan to use your display in varying brightnesses you won't be happy. I've invested several days worth of research. I just accepted the fact, that samys AOD won't work on our device right now.
Click to expand...
Click to collapse
Can you point me at the xposed modules that you're talking about?
I'm always using my n910f at maximum brightness so for me is not a probleem to break autobrightness.
Thanks in advance.
-M-

Interface is as a phone...

Hi all, I bought an m3 a couple of weeks ago and the interface for all my apps show up as they would on a phone display rather than on a tablet.
My question is, if I root the device and just put straight android on, would I be able to specify that this is a tablet device rather than a phone? Or even, are there 2 versions available to install? Or is all this built into the hardware?
I know you can shrink the size of text and the general look within settings but that's not the issue. it's how the apps function .e.g. on some apps if I click on a link it takes me to another page rather than just popping up on a side bar. I had a Samsung previously, identical screen size and I can see the difference.
Any help is much appreciated
Thanks

Dig around on this forum, there are a few threads. If you are rooted there are ways to change the DPI which will trigger the apps to correctly display tablet mode. Less severe than loading a ROM.
Here is one of them:
https://forum.xda-developers.com/mediapad-m3/help/huawei-mediapad-m3-chrome-running-phone-t3487236

portisgreg said:
Hi all, I bought an m3 a couple of weeks ago and the interface for all my apps show up as they would on a phone display rather than on a tablet.
My question is, if I root the device and just put straight android on, would I be able to specify that this is a tablet device rather than a phone? Or even, are there 2 versions available to install? Or is all this built into the hardware?
I know you can shrink the size of text and the general look within settings but that's not the issue. it's how the apps function .e.g. on some apps if I click on a link it takes me to another page rather than just popping up on a side bar. I had a Samsung previously, identical screen size and I can see the difference.
Any help is much appreciated
Thanks
Click to expand...
Click to collapse
Hi!
Unlikely it is a known issue. Nothing you can do except changing the dpi to 325. If you do that all apps run in tablet mode but if you restart the tab it goes back over 400 dpi so it's not a perfect solution.

Thanks for the replies I've managed to root it and I got a really terrible rom (the only one I could find in the forums)
A couple more questions:
1. the density settings don't stay even if you root - it there any way to keep them?
2. are there any better ROMs than this?
Thanks
Greg

Ok!
So here's the latest build from Huawei with Android 7.0.
I accept no liability as it's clearly a pre-release with glitches etc but I've not found any issues yet
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v80058/f2/full/update.zip
I used the Huawei Firmware Finder Team Tool to find it.
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146

portisgreg said:
Thanks for the replies I've managed to root it and I got a really terrible rom (the only one I could find in the forums)
A couple more questions:
1. the density settings don't stay even if you root - it there any way to keep them?
2. are there any better ROMs than this?
Thanks
Greg
Click to expand...
Click to collapse
adb.exe shell wm density 330 && adb reboot
https://forum.xda-developers.com/me...chrome-running-phone-t3487236/page3?nocache=1

famedoro said:
adb.exe shell wm density 330 && adb reboot
https://forum.xda-developers.com/me...chrome-running-phone-t3487236/page3?nocache=1
Click to expand...
Click to collapse
thanks but it doesn't retain the settings after reboot still

Nougat doesn't solve this problem.
Sent from my BTV-W09 using Tapatalk