Using the ROM][GT-I9305][Marshmallow][6.0][Cyanogenmod 13.0][UNOFFICIAL] with pleasure
No problems, battery uses more when there is no wifi around, but I guess that is normal?
The only problem I had was that the screen did not rotate, after boot it worked for a while, then stopped.
The fix for that, well, it works for me is to change a setting:
In the Developer options turn on the Multi-windows mode, you will get a message that it may cause some problems, but I did not notice that.
But it fixes the screen rotation, it works perfect now!
(My first posting on XDA)
Related
Since Sprint is going to try and screw me big time if I get a new phone, I've decided to see what new life I could put into my old Touch Diamond (DIA500). I installed XDAndroid FRX05, and it seems to be working really well, with a few exceptions. One of the first things I tried was to enable Bluetooth. What happens is that it enables, but about 4 seconds after being enabled, it says it's shutting down, then it starts back up, and shuts down. It keeps doing this forever, until I turn it off. Now that I tried Wifi, it does the exact same thing. I've rebooted a few times, and took the battery out once, but still nothing. I've since installed a battery-saving program, but this happened on a fresh install.
The next issue is with the backlight. If I try and change the brightness, it changes for a second, then goes back to the brightness it was. It does this whether I turn the brightness up or down. It's not set to auto.
The third issue is the GPS. It works, but seems to take a long time to get a lock. Under WM, I'd have some kind of location within seconds, even inside. I'm guessing it was using the phone network to speed things up. Under android, it takes a few minutes sometimes, and it's worse inside.
I also had a nightmare calibrating the screen. It's still a little off, but it works. Does anyone know a screen calibration program that would work?
Any ideas?
Thanks!
To solve the brightness problem. Boot WinMo and turn off auto brightness there. That will solve that problem.
Thanks for share you knowledge here DA01
I noticed people are using power management apps to "fix" the SOD in CM7.1. I use green power myself, and it works great. Stopped my SOD's completely.
I ran across this thread to fix a wifi off at screen off issue. http://forum.xda-developers.com/showthread.php?t=774507
It seems the default wifi off at screen off is timed at 15 minutes after the screen turns off. If we could have an option under cyanogen settings, or advaced wifi settings, to change this timer to just a few seconds, I think it could temporarilly fix many of the SOD problems, until the real culprit is found. I know Dalingrin said he would get to the SOD problem after a couple of other projects, but maybe this could be a temporary fix until he really gets into it.
I would have put this under the developers thread, but I read a lot, and post a little.
What do you think?
jameshmiller said:
I noticed people are using power management apps to "fix" the SOD in CM7.1. I use green power myself, and it works great. Stopped my SOD's completely.
I ran across this thread to fix a wifi off at screen off issue. http://forum.xda-developers.com/showthread.php?t=774507
It seems the default wifi off at screen off is timed at 15 minutes after the screen turns off. If we could have an option under cyanogen settings, or advaced wifi settings, to change this timer to just a few seconds, I think it could temporarilly fix many of the SOD problems, until the real culprit is found. I know Dalingrin said he would get to the SOD problem after a couple of other projects, but maybe this could be a temporary fix until he really gets into it.
I would have put this under the developers thread, but I read a lot, and post a little.
What do you think?
Click to expand...
Click to collapse
Just use Setting Profile Lite or Tasker or whatever to turn off wifi at screen off and back on when it's back on. Doesn't seem like adding a setting in CM7 to set the length of time is worth it.
This is the part I'm not quite following...the behavior you're describing (wifi off with screen and on with screen) is actually the CM7 default, so why the need for a special app?
Rodney
I haven't looked at these 3rd party apps yet but I don't believe shortening the wifi sleep timeout would help. I believe the reason these apps prevent SODs is because they forcibly turn off the wifi after some time. There seems to be some condition that the wifi driver or wpa supplicant gets locked and the sleep timeout has no effect.
What is the default time period before wifi turns off when the screen turns off?
I am noticing people in the various SOD threads having success stopping their SOD's with third party software that does what the advanced wifi setting "should" do, cuts the wifi off when the screen turns off. I am using "green power" and set it to turn off wifi 5 seconds after the screen turns off, unless there is traffic. I have not had an SOD since. The thread I linked to says the default android time period for wifi off is 15 minutes.
Maybe, just maybe, SOD's are occurring in this 15 minute time period. That's why people are having success with these 3rd party apps.
This was a reply to rhester72. I should have quoted.
Dalingrin, Did you happen to read the thread I linked to? It may be of some use to you. It may not. It may not pertain to your kernel.
I'm no Dev, just someone that appreciates the work you do, and am trying to help.
Well, I guess I learned something. WiFi off when screen turns off, in the advanced wireless setting, does not actually turn the WiFi off. It only puts it to sleep.
The third party apps that turn WiFi off when screen turns off, actually turn the WiFi off. That's why they "fix" SOD.
I'm still curious as to the default WiFi off/sleep when screen turns off timer is. Just for knowledge sake.
Thanks again, to all of the Devs, for all of your hard work.
Well, interestingly enough, I updated from n150 to n157 last night and this morning after disconnecting from power (with wifi set to never sleep when plugged in), about 5 minutes later I had my first SOD in a *long* time. Not running any special power-management apps.
Rodney
rhester72 said:
This is the part I'm not quite following...the behavior you're describing (wifi off with screen and on with screen) is actually the CM7 default, so why the need for a special app?
Click to expand...
Click to collapse
My NC hasn't had a single SOD since selecting the option to turn wifi off when screen is off. Surely, unless you need notifications while the NC is in sleep, this is the simple solution to SOD?
CM7 #150
Hiya folks. Running CM10.1 stable on my targa (aka Droid Bionic). It was beautiful except for lack of nav dock support, a problematic Google Now (different problem, with workaround), and this particular problem, which I hope someone know what I am talking about...
When a call comes in and I answer by the slider, the screen goes black, whether or not I held the phone up to my head.
I cannot turn the screen back on. None of the buttons seem to do anything, though backlight for the 4 hard buttons does turn on indicating that some command was received by the touchscreen. Not even the power button will bring the screen back during the call.
If the other party hangs up, the phone goes back to normal.
With screen off, I can't hang up.
I can hang up if my Bluetooth headset was connected and I hang up with that.
I've searched all over and this issue seem to be a pretty popular issue last December across all CM 10 builds. However, I don't know if this was ever resolved for this build.
I can't find an option in the ROM to just flat "turn off face proximity detection" either. Or in any way to "tweak" it.
CPU-Z says my proximity sensor is working, so I guess it's just not calibrated properly for the dialer?
Can we get a "special hidden tweaker" much like the light sensor tweak for the auto-brightness levels?
Figured it out. It wasn't CM. It was Screebl and the stupid orientation sensor, and how the Launcher is fixed to portrait mode.
I think I had my phone laid down and it's at a diagonal so it's in landscape mode, and the phone's fine with that when it's just showing contacts. Screebl kicks in and determines that landscape, phone orientation says stay on, so screen stayed on. It was set to turn off the screen IMMEDIATELY when the orientation goes out of "viewing range". (Saving batteries, ya know).
When the call was answered, Screebl should have turned itself off (i.e. ignore input while call is in progress). But it didn't. The "answer the phone" screen flipped the display back to portrait mode. The phone, still laid flat, in "landscape", is now "out of viewing range", and Screebl turned off the screen.
Strange interaction among the various apps, yes.
I'm still trying to figure out how to make my Bionic, with extended battery last the whole day. Juicedefender Ultimate somehow just keeps turning the screen back on every X seconds (taking root control for SOMETHING) and Wakelock detector says the phone is not going into enough deep sleep (kinda like me, hahaha)
I recently installed CM 10.1.2 Stable and it was working fine until about a week ago - great work, thanks to the Devs.
The problem that I am having is that the home screen and drawer is locked in portrait mode. I have tried EVERY setting I could find and it only stays on portrait. All the other apps stay in landscape when rotation lock is on (my preferred usage mode) with the exception of the dialer and the lock screen. The only time the home screen behaves is when I put the device in it's car dock - THEN it orients correctly.
The actual events right before it went wonky are as follows:
1) I was using it in the car dock, turned off the vehicle, and removed it. The lock screen seemed to be taking it's time orienting.
2) While I was fumbling with it I dropped it on the corner closest to the USB port (I know, normally it's in an Otterbox but I had just pulled it out of the car). It also got a little moisture on it, but none appeared to penetrate.
3) After I dropped it, everything was stuck in portrait mode - all apps, etc.
4) I restarted, and then did a cold boot, and it got to where I am now.
I have tried reinstalling CM, and various combinations of car dock/rotate settings but I'm baffled. It is my understanding that the accellerometers might cause bad rotation behavior, but it doesn't affect the other apps. Any suggestions?
Thanks,
R
R2.0 said:
I recently installed CM 10.1.2 Stable and it was working fine until about a week ago - great work, thanks to the Devs.
The problem that I am having is that the home screen and drawer is locked in portrait mode. I have tried EVERY setting I could find and it only stays on portrait. All the other apps stay in landscape when rotation lock is on (my preferred usage mode) with the exception of the dialer and the lock screen. The only time the home screen behaves is when I put the device in it's car dock - THEN it orients correctly.
The actual events right before it went wonky are as follows:
1) I was using it in the car dock, turned off the vehicle, and removed it. The lock screen seemed to be taking it's time orienting.
2) While I was fumbling with it I dropped it on the corner closest to the USB port (I know, normally it's in an Otterbox but I had just pulled it out of the car). It also got a little moisture on it, but none appeared to penetrate.
3) After I dropped it, everything was stuck in portrait mode - all apps, etc.
4) I restarted, and then did a cold boot, and it got to where I am now.
I have tried reinstalling CM, and various combinations of car dock/rotate settings but I'm baffled. It is my understanding that the accellerometers might cause bad rotation behavior, but it doesn't affect the other apps. Any suggestions?
Thanks,
R
Click to expand...
Click to collapse
If that happened after your dropped it, you can try to recalibrate the accellerometer (if that's still an option on the cappy).
If that doesn't work, you can always try to flash stock odin KK4 without bootloaders (after a backup of course). But my guess is that it's hardware related so flashing won't change much.
If all fails, you can contact Josh @ mobiletechvideos.com. He's well known around here for fixing cappys.
Hi guys.
I got an issue of screen time out timer.
Sometimes it works but mostly not.
Display isn't turning off at all.
Sometimes it's turning off like normal (set at 1min) but sometimes not turning off at all.
It's all happening with any notifications (not specific one).
Can't find the reason it's happening,
Even made a clean flash and nothing changed
Need advice.
Thanks.