Even with 10J and 10K I'm getting the dynamic screen refresh reverting to 'enabled' after a while.
I'm trying an old trick to see if it will lock, adding the line debug.gr.swapinterval = 0 to the build prop. This is suppose to allow FPS over 30, but might be forcing it in this case.
Can someone else try this to see if im not imagining things.
Related
Everytime I get an incoming call, I always need to use the job wheel and turn the in call volume up to the highest level (its currently one below that on every incoming call).. how do I get the phone to save the volume setting to always be on the highest level?
Same problem here. I would be interested in that too.
Same problem. But only after reboot, until that it's saved. (using Dutty's WM6 Premium)
same prob, only in reboot. Goes back to one below full. Using vpg wm6 3.0
Try a program called "phone alarm". The in-call volume level is one of its profile configuration options. It works pretty well.
Yeah, but why do I need to install a damn program just so it remembers my settings? Thats not a very good solution Doesnt phonealarm have a bunch of today screen and other crap I probably wont use?
cirial said:
Yeah, but why do I need to install a damn program just so it remembers my settings? Thats not a very good solution Doesnt phonealarm have a bunch of today screen and other crap I probably wont use?
Click to expand...
Click to collapse
Exactly. I don't need any profile app, because I use just Sound On/Off. Why should I waste memory? In addition, I do reboot 2-3 x a week, so it is not a huge problem. Altough some elegant solution would be welcome.
Anyone else have any suggestions besides phonealarm?
Same problem. All versions of WM6 seem to have this problem. Looking for solution too.
Hopefully its fixed in the final version... or, someone finds a solution..
I'd suggest (and I don't have to do it this weekend as doing my loft and have a new phone to sort out too) that someone does a full Reg dump from standard install and then same after that software (which I've never used) is installed and the settings sorted and phone rebooted - and then uses windiff or simlar to find out what's changed.
It should be fairly easy to isolate the reg setting that does the trick, if it is actually a reg setting that we're after.
It could be a reg setting that resets itself after a boot (like the landscapeoffonratation setting) or it might not. If it's not, we're in business. If it is it'll be a bit more complex but still probably still doable.
If someone can isolate that reg setting it's an easy business to either cook it into a rom as it'll just need a rgu file, or to put it into a cab.
Maybe a solution
Hi all,
I would suggest playing around with those registry keys:
HKCU/ControlPanel/Notifications/ShellOverrides
and there the following value: SavedVolume
and
HKCU/ControlPanel/Volume
and there the following value: Volume
Didn't try any other value for myself, just a hint
for all thos around who want to try and maybe report
if you have success
Olioaglio
I have my 1006 reg value set to 1. That allows me to run apps that aren't signed/trusted. So that's all well and good, but for some stupid reason that I can't figure out, every day I find that value moved back to 0. Anyone else ever heard or seen this? It's beyond frustrating because there's no rhyme or reason. I set that value back to 1 and all is well until the next morning.
Ugh.....thanks for any leads...
sounds like it reverts back after a reset. You could write a mortscript to change the value and then place it in startup folder
Thanks for the reply. The thing is that it's not directly related to a reset. Example: I'll mess with my phone in the evening, and the value is 1. I'll get up in the morning and it'll be 0. I didn't do anything in particular. Some times the phone is charging, sometimes it's just idle. While a start up script seems like a good idea, I'm not it's the full situation here.
Thanks.
Today Lumos 1.0 final is released, besides other changes now has better support for HVGA in settings dialog.
never tried this on other phones, but it sounds fantastic
going to give it a whirl and see if anything improves
Well, I was about 6 monthes with previous release and it really helps to save battery.
Just played a little to make own backlight profile.
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
I’ve tried ‘LumosWizard’ 5 month ago but I’ve never managed to make it work correctly
So that, I use ‘Mylostblog Mylight’ now.
Not the same but its easy to use with a shortcut in "Cookie’s Home Tab".
Well, just try run calibration correctly, my sensor's range is 0..1904,
minimum level 1, maximum level 5.
There are issues with g-sensor games - lookup the original Lumos thread.
tkur said:
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
Click to expand...
Click to collapse
ok, this bug has been driving me insane. AOKP and CNA have it, or atleast I know the latest CNA has it, and I had it on AOKP as of a few weeks ago.
Ever notice that your max cpu resets to 700 mhz randomly? I saw a lot of talk on this but no reasoning why, which I have now found. Thanks to another post (which I will try to find) I saw that people that are affected by this (you know if you are) can reproduce by doing to the following... turn screen off via button, and call your phone... when it wakes it will now be changed to 700mhz YAY! or not...
so this lead me to start looking into why this was happening, and some reported not happening... also wiping, updating, and changing kernels doesn't fix this... but how are some not able to reproduce with the above? then I found it! once you set your screen off to a value (can even be 700) it will no longer happen! I guess these roms are shpiping with out this set, and assuming that android will go to 700 like it always has, but in JB this hasn't been the case. sure screen on and off via the button does this, but the phone wake somehow messes it all up... soooo setting the screen off setting in to anything fixes it...
I used system tuner to set this btw, as soon as it's set (to 700 or 1.2) and i turn my phone off and call it, it resumes to my normal max of 1350..., but if I then go back into system tuner and chose the option to leave the settings the same from 700 I can reproduce the original problem.
Working now to see if I can find the actual culprit and fix it and send to AOKP, etc. if not, then we will have to push a script to set this on first run to prevent it form the future.
Anyone else able to test this on CM, etc? I haven't had the time to, but I think I had the same issue on CM also, and would lead me to beleive it's everywhere unless the rom is pushing a default value, or most users are just used to setting it when they flash and thus haven't seen this issue
looks like they might have fixed it, I'm running 3.6.6 and it's still not working though ven though it was made 3 days after this... perhaps it's in the nightly though:
https://github.com/CNA/android_device_samsung_tuna/commit/b5282efd34ac6a05869d08e7054512cf022c575d
further testing of CNA 3.6.6 shows that the only way I can get this to stick is if I use an app like system tuner, or something else that runs in the background to change the screen on and off settings. Updating the value in the sys folder isn't seeming to work, still reverts to 700 when a call is accepted. . .
latest aokp does not have this issue (jb_4)
winner0's CM from mid sept DID have this, latest winner0 cm10 linaro build doesn't...... looking into changelogs now
slim 2.4 doesn't have this issue
ok, was able to fix this by either setting screen off settings something that runs in the background like system tuner as mentioned above up or using Lean's latest kernel.
I've seen this on certain ROMs, and wondered what it might be and if I can adjust or tweak something to fix it, (but maybe it's just something you have to live with depending on where the ROM development is at). It's kind of like a wave that goes across the screen. It seems totally random, I haven't been able to predict it, but it happens maybe once every 10 scrolls or something. You can see it in the mp4, near the end of the clip. Any ideas?
https://mega.nz/#!dx0w3AyB!9kpI1ZgyBp6ymLiUt5GMk3Hhe3Rc2eTVeEA9exVmYT4