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.
Related
Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.
Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.
Tried all panels all have the same problem.
Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.
What kind of phone do you have?
Sent from my HTC Vision using XDA App
do you have an SD card you can try to boot from and share your settings?
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.
PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?
dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.
Hello,
I got an problem on like 4 of the 5 kaisers here.
The problem is that sometimes the kaisers goes into an sleep where it doenst come out without reset.
You will get an black screen and the light of your keyboard is on and doesnt turn off. When this happens the battery goes from 100% to 0% in like 40 mins. without the problem i can use the phone for 2 days.
My question is how to solve this? I tried the following things.
- Radio 1.65, 1.70. 1.71
- 2 different hspl
- old and new kernel.
- and loads of different roms. from gingerbread to eclair.
Any solution or fix for this? because i can't use it for daily base now since when i dont notice the battery is empty of that bug.
Best Regards,
Veldmuus
That's the black screen of death. I never get that, but it's one of three problems that I have heard of. I think it might be related to going to sleep. I use the latest kernel, from git, which is pretty much identical to scooter1556's kernel with separate cache. What kernel are you using?
The second problem is the white screen of death, which I get a lot when I leave the phone on the charger. The screen is white bright, the kernel is not crashed. Sometimes Fn-Right-soft-key twice will cure this, but usually not. Some have guessed that this has something to do with the phone going to sleep not quite properly while charging. There is an option to not go to sleep while connected to a charger, and I haven't tried that option for a long time.
The third problem is a kernel crash (screen freezes, keyboard doesn't turn on LED, etc) caused by compcache (zram). Can be avoided by not using compcache.
The most annoying issue I have is that I've never figured out how to tweak the build so that apps can be installed to SD. I've been trying to change initrd so that, when installed completely on NAND, the sdcard is completely managed by vold. So far no success, and I've pretty much moved on to my newer phone (Rhodium, aka AT&T Tilt2).
I have spent the last week or so "tweaking" my build.prop file, adding lines for disabling sleep mode, 3G speed tweaks (doesn't do much yet) and fixing small compatibility issues such as AGPS/GPS not working. So far so good, no more sleep of death/black screen/white screen.
If successful, I would ask that the modified build.prop file be added to the Froyo builds on SourceForge, intergrated directly as to eliminate "end user interaction", meaning you won't have to touch it.
I am also looking into some sysinit.rc mods as well, but I haven't had much time lately.
Veldmuus, do you have a way to edit your own build.prop file such as Root Explorer, or would you have to push it to the phone via ADB?
Does anyone else have issues with the WiFi connection while the screen is turned off? I noticed that not a single one of my music streaming / radio apps work when the screen isn't on. It works for maybe a minute before all sound just stops. Starts just fine again once I power up the screen.
Has there been any changes done to the handling of these matters in ICS perhaps?
Pretty annoying not being able to stream music over WiFi as I think I'll hit my 5GB limit on data pretty fast if I can't use the WiFi at work for this.
So has anyone else noticed these issues?
SBS_ said:
Does anyone else have issues with the WiFi connection while the screen is turned off? I noticed that not a single one of my music streaming / radio apps work when the screen isn't on. It works for maybe a minute before all sound just stops. Starts just fine again once I power up the screen.
Has there been any changes done to the handling of these matters in ICS perhaps?
Pretty annoying not being able to stream music over WiFi as I think I'll hit my 5GB limit on data pretty fast if I can't use the WiFi at work for this.
So has anyone else noticed these issues?
Click to expand...
Click to collapse
Yeah same here. I remember this being an issue with Android 2.1 for my Desire but was fixed in custom roms. Might be the same situation here again.
I remember this being an issue with my Nexus One, don't remember if it was fixed in 2.2 or 2.3. I remember testing file transfer using SwiFTP, with the bug the file transfer would go down to double digits (kB/sec), with the bug fix it would be a few hundred kB/sec, with the screen on it would hit mB/sec or so (in any Android version).
I believe this is the official issue:
http://code.google.com/p/android/issues/detail?id=9781
With my Nexus S I'm not experiencing this bug. Sscreen on still gives me a major wifi speed boost, but screen off I get a few hundred kB/sec, which should be more than enough for any streaming app. KiloBYTES btw, not bits. I'm surprised ICS and/or Galaxy Nexus brought this problem back. Or it could be something else entirely.
Are you connected via 2.4GHz or 5GHz wifi? I would think the new 5GHz radio in the GN probably has more aggressive power saving features. Try switching to 802.11b/g (instead of 802.11n, in any frequency), see if it helps.
Have you changed your WIFI sleep policy?
On my Froyo phone, if you hit menu while in the WIFI settings (I know there is no menu in ICS) you get an option to go into advanced settings where you have the option to choose your WiFi sleep policy (When screen turns off, never when plugged in, never).
There should be a way to access that advanced settings area somewhere.. My phone is a couple hundred miles away right now and I won't see it for another week so I can't be of much further help right now. However, there "was" a setting in previous versions.
best info at the time last year was here for the N1
http://www.google.com/support/forum/p/android/thread?tid=01a47ff5b0a92d52&hl=en
7xx replies there to read, but really good info. somewhere in there, maybe around#600 the info gets good, can't remember. But shortly around this time the problem was gone/fixed.
there was a guy with an app i think it was wifi fixer, i could be wrong. that worked sometimes, but battery drain was bad. Whatever google, or CM did fixed the low power save mode issue. I'm thinking it was something at the kernel level?
edit, on second thought, there's no good reason to read all that. You won't get a fix out of it anyway. It was updated away in the end, something related to MAC addresses and build numbers and frf50 or some such.
BUT this seems like the same kind of thing going on in the power save mode.
Have you checked your advanced settings?
Wi-Fi>>(settings [bottom right])>>Advanced>>Keep Wi-Fi on during sleep...
Mine was set to always by default, so I suspect that the issue lies else where...
Neville.Holland said:
Have you checked your advanced settings?
Wi-Fi>>(settings [bottom right])>>Advanced>>Keep Wi-Fi on during sleep...
Mine was set to always by default, so I suspect that the issue lies else where...
Click to expand...
Click to collapse
Same here. Mine was set to always by default but still getting this issue.
Sent from my Galaxy Nexus using XDA App
I would suggest that this issue is related to the individual applications you are using, rather than anything to do with Android.
I am able to stream music from Google Music via WiFi just fine when the screen is off, and I am also able to talk to someone on Skype via WiFi just fine when the screen is off.
oscillik said:
I would suggest that this issue is related to the individual applications you are using, rather than anything to do with Android.
I am able to stream music from Google Music via WiFi just fine when the screen is off, and I am also able to talk to someone on Skype via WiFi just fine when the screen is off.
Click to expand...
Click to collapse
Thanks for posting that; I was getting pretty worried and disappointed after reading this thread. I had to deal with this when I first got my Nexus One, until Google released the 2.2.1 update with a new Broadcom driver which finally fixed the issue. No streaming, no pushes, just nothing at all from wifi when the phone went to sleep. All traffic to/from the phone would just stop. It was maddening.
The Galaxy Nexus comes to Canada a week from today, and this would've been a show-stopper for me. At least it's working for you, so my day isn't ruined quite yet
Has this issue ever been nailed down? I've seen considerable discussion on it going back years. I've seen considerable speculation regarding WIFI mode and Governor. I've seem many of the bug reports marked closed.
Yet I have a GN on v4.0.4 and the moment the screen goes off - either because you turn it off or it just times out - the WIFI goes to h*ll. I've run ping and network trace from both sides and there is no doubt the WIFI stays connected, however latency goes way up and packets are lost... and with TCP connections it gets congested with retransmits. I've run with the governor set to "Performance" and there is no difference.
So, is there any consensus on what is causing this problem with current stock hardware/software?
I read that it's something that's been coded in for a while. Try using this:
https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
-Sent via XDA Premium-
Ok, to answer my own question, this is still related to the PSP issue from years ago:
code.google.com/p/android/issues/detail?id=9781
code.google.com/p/android/issues/detail?id=15549
Bottom line is that some hardware - like GN - has an additional level of PSP on WIFI. The issue was resolved by inclusion of an additional lock mode - WIFI_MODE_FULL_HIGH_PERF - some time ago. However, its up to an application to request the new lock state if it thinks it needs it. Many don't.
So, its probably not a bad idea to contact developers of the various applications and recommend they look into the new lock level in the later APIs.
Also, the "WIFI High Performance Widget" can be used to manually hold a WIFI_MODE_FULL_HIGH_PERF lock on the WIFI if you're dealing with an application that isn't doing it its self. Beware of the other "WIFI fixes" out there, none of the ones I tested were acquiring the correct lock.
Also, from an adb shell you can use "dumpsys wifi" to see who is holding what lock, for example:
Code:
Locks acquired: 5 full, 5 full high perf, 5 scan
Locks released: 4 full, 4 full high perf, 5 scan
Locks held:
WifiLock{PANDORA type=1 [email protected]}
WifiLock{HighPerformance type=3 [email protected]}
Here you can see Pandora is only holding type=1 (WIFI_MODE_FULL) and HighPerformance is holding type=3 (WIFI_MODE_FULL_HIGH_PERF). Dumping the WIFI state takes the guess work out of it.
Tried that widget, having absolutely no luck with 'in tune' and 'winamp' for radio with the galaxy nexus verizon...
as soon as the device sleeps, wifi goes to hell and buffer drops in and out every 2 seconds. Completely unusable, any recent fixes? this is totally making me think I just bought a $400 brick since this feature was very important for me.
What may be confusing about that widget is that it is a "widget". You have to locate it under "widgets" and then put it on the surface and then click it to enable it... it should be blue when on, and black when its not.
tlum said:
What may be confusing about that widget is that it is a "widget". You have to locate it under "widgets" and then put it on the surface and then click it to enable it... it should be blue when on, and black when its not.
Click to expand...
Click to collapse
I have been trying to put the 'widget' itself (2x2 square) on the home screen but even if i hold and drag it to where I want it, it never actually appears on the screen. And of course i'm still getting crazy ping times...Does anyone else have this working on a GN (verizon - not that it should make a difference)?
I have found a few workarounds to this issue, none are great and frustrate me greatly.
1. Root and use the franco kernel. Seems people with that have no issues - since you can set? the wifi to full performance.
2. Use this wifi performance widget
3. Use an app that has properly set its own wifi settings. - Going through all the radio apps on the google market, i am finding only one app that seems to be doing this right: DI Radio - some kind of dance/techno/etc - confirmed it with ping times, they remain low on sleep.
Not one other radio app seems to have set 'proper' settings - which shows that something needs to be addressed in the os...I was having good luck with the yahoo music app, but depended on the stream (maybe some buffer more :dunno - the ping results are garbage.
EDIT: I tried installing high performance wifi again, and finally got the widget to one of the homescreens! Let me break it down for anyone else who comes across this. After install, the small 1x1 blue app box is put on your desktop and the black screen comes up with the wireless networks and a checkbox. I then went to apps->widgets and tried putting the 2x2 widget on the home screen again, and like always it clicks on like its there (and when you click home and its never there). However, this time I hit BACK instead of home after dropping the widget and it took me back to the black screen with the checkbox, then i hit home and voila its sitting there. You can click on it like you mentioned! Confirmed with ping for tune in...pings remain low.
If this continues to work, it may be a godsend. It is annoying having to have this, but far far better than not.
I had that problem also especially when i tried to download big files when the screen turn off the download speed became extremely slow, this widget solve this, i think to that moment its the easiest solution tap it when you need it tap it again when you done.
By the way i had this problems with franko kernel also and again to my opinion it is the good solution for now, until the apps developers update their apps.
Sent from my Galaxy Nexus using XDA
If you download the SDK - you only need Android SDK Platform-tools - to a PC and use the adb shell it is easy to dump the WiFi lock state with dumpsys wifi and see exactly which app(s) are holding what locks. Completely takes all of the guessing out of who is doing what when. Judging the behavior can be subjective because there are other reasons that the WiFi can break up which can be very frustrating.
developer.android.com/guide/developing/tools/adb.html
Erlang2012 said:
I had that problem also especially when i tried to download big files when the screen turn off the download speed became extremely slow, this widget solve this, i think to that moment its the easiest solution tap it when you need it tap it again when you done.
By the way i had this problems with franko kernel also and again to my opinion it is the good solution for now, until the apps developers update their apps.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
The app does work well, however I have been running into some issues as I continue to use it. It randomly decides to turn off the forced max wifi (even though its still blue and looks like its operating) or perhaps the phone is forcing the wifi issue again. It seems to happen when you are downloading, playing with some other apps? You only notice it when you sleep it and the streaming radio immediately starts having issues.
Solution is to flip back to the widget turn it off and turn it on again. It works, but is another annoyance.
I haven't yet ascertained exactly what causes it to switch off yet.
tlum said:
If you download the SDK - you only need Android SDK Platform-tools - to a PC and use the adb shell it is easy to dump the WiFi lock state with dumpsys wifi and see exactly which app(s) are holding what locks. Completely takes all of the guessing out of who is doing what when. Judging the behavior can be subjective because there are other reasons that the WiFi can break up which can be very frustrating.
developer.android.com/guide/developing/tools/adb.html
Click to expand...
Click to collapse
I will look into this, thank you.
---------- Post added at 06:16 PM ---------- Previous post was at 05:28 PM ----------
I used the adb shell (learned how to install all these dev tools and how to use it first ) and here is some updated info:
Tunein = type=1
Pandora = type=1
Audioaddict service (Digitally imported app I posted above previously) = type=3
google music = type=3
High performance app = type=3 (havent figured out why this likes to stop randomly)
I will update with more app info, hopefully others can also email the developers and see that it gets fixed, so we no longer have to use damn workarounds...
jeep364 said:
... It randomly decides to turn off the forced max wifi (even though its still blue and looks like its operating)...
Click to expand...
Click to collapse
Yes, it definitely has an issue holding its lock, and it definitely seems related to another application taking over and also when it switches to cell and back, I can confirm that. It may be related to the OS since the widget thinks it still on when clearly the lock as been released, so it may be that the OS released the lock and the widget has no idea. I haven't taken the time to look into the details yet, and this is something we should make the developer aware of.
tlum said:
Yes, it definitely has an issue holding its lock, and it definitely seems related to another application taking over and also when it switches to cell and back, I can confirm that. It may be related to the OS since the widget thinks it still on when clearly the lock as been released, so it may be that the OS released the lock and the widget has no idea. I haven't taken the time to look into the details yet, and this is something we should make the developer aware of.
Click to expand...
Click to collapse
Yup, from what I can see it loses lock:
1. when cell switching
2. manually killing/starting wifi
3. when ANY application is downloaded/removed (ie. changes in permissions)
4. when playing with dolphin, other apps for more than a few minutes, it will kill it even though the blue stays lit. I think its as you mentioned, during general use of the phone, at some point some permissions are changed and hifi performance is tossed off its lock.
If you only are streaming music and re enter the phone to check a gmail alert or two...it seems to be fine. otherwise you need to hit the lock widget one more time before sending it to sleep with pandora/tune in playing.
Hi guys,
I've updated the phone to the last global beta - 7.12.28 and noticed one big issue and a few other smaller ones. I hope someone might have ideas on how to fix them.
The WiFi turns on as soon as the screen is off. What I've done so far is to make sure no app has permission to turn the WiFi on (using the built in permission manager). I've cleared cache and rebooted the phone several times.
Another issue is the MIUI memory optimization is always disabled, no matter if you change it to something else or not.
And the third one that I can think of right now is the region - it always reverts back to China. Now this has been outgoing for a while, so it might be something with my phone.
What I've done on the phone is to root it and have Xposed install and active. I've also ran Unbloatmi, great script to get rid of apps you don't need. I haven't tried alternative roms like Lineage.
Recently I installed floppy kernel, but the wifi issue remains with the stock kernel too.
I'm open to suggestions
Issue resolved with the next update.
I suggest to you to use global stable. It's old, but global dev is always bugged for this phone. Do what you want, but my experience is bad
Yeah it's always preferred to use stable roms on phones in production environment. But I like to live on the edge And I got into the routine to remove most of the unnecessary apps right after the update. So overall - the phone is quite stable. But now it has the same MAC as my wife's phone. Go figure...