Database Users

WiFi has a mind of its own, enables itself.

Hey all! Long time XDA-er, but I don't post much. Anyways...
Recently the WiFi on my Cingular 8525 has been quite problematic. I have gone through many custom ROM's recently searching for one that fits me, and I eventually settled on CRC's most recent build, TouchFlo2D running on top, and am very happy with the speed and usability of my phone. I always make a point of checking all hardware after a flash and at the time the WiFi worked fine. However, recently I noticed that when disabled, WiFi enables itself automatically every ten seconds for a short instant, then shuts off again. This change is reflected in the Comm Manager, the Taskbar, the WiFi configuration - everywhere. However if I turn WiFi on, it stays on, and works just fine. This has been causing me a lot of headache, mainly when using CPU-intensive applications, since every time it enables itself the CPU gets pegged, frames are dropped and virtual lives are lots. It also now takes FOREVER for 3G or HSDPA to connect, and I have noticed a slight decrease in battery life since I discovered the problem.
My device has the most recent HardSPL. I have tried flashing multiple radios, re-flashing the ROM, different ROM's, and every combination of settings I can think of. I searched everywhere I can think of, (posting is my last life-line) and I just can't find anyone else with this exact problem. I assure you there is no software trying to activate the WiFi and the phone is set up to use 3G for data by default. The registry is clean and there are no other problems, hardware or software-wise (aside from the touchscreen issue present on all Hermes). I am completely baffled, I can't find any logical reason for it to behave this way. I am considering a solution in an old thread by pof, an EEPROM trick where you acquire an image from one Hermes with working WiFi, hex edit the MAC address to be different, then flash to the affected device's EEPROM, however this is only reported to fix non-functioning WiFi, and I'm not convinced my EEPROM is corrupt, plus I can't seem to find the thread anymore. I am pulling my hair out over this! Even bouncing around ideas would help, all replies will be considered.
P.S. On a side note, I have been seeing a lot of threads lately calling the Hermes dead. I recently "downgraded" from a Touch Diamond to the Hermes, and I am extremely glad I did. Aside from the QVGA screen and lack of working GPS, I find the Hermes superior in most if not all ways, and I use my phone for just about everything. Long live the Hermes!

2.1 Blue Tooth Drain Issue ?? [6.35 Radio]

Since the Transition from 1.5 to 2.1 no the 6.35 radio bluetooth, when enabeled has kept hte phone from going to sleep, the vattery drains very quickly as well as the Phone is Quite warm.
Example:
on a 2.1 rom with Blue tooth Disabled the battery will fall to 50% in 24 hours, With Blue Tooth Enabled the battery will fall to 25% in only 6 hours.
where as on a 1.5 rom the battery drain will drain at a less then noticeable pace weather blue tooth is on or off.
-------------------------------
When Bluetooth Is enabled:
* Cell Standby uses most of my battery
* Awake Time Matches the amount of time the Blue tooth Is on
I have looked at the possible causes with no Success:
* Blue tooth Transfer
* PairableTimeout in main.inf
are there other that are experiencing this issue, Has anyone found a solution, i would like to have my bluetooth enabled all day long again.
Does anyone know a way i can strip the settings for blue tooth so i cant pair or file transfer or anything, except have my phone connect to one blue tooth headset with minimal battery drain.

Bluetooth draining battery is known issue on new radio. I've messaged Sanpei about this and he is looking into it. It may take him sometime to fix this since he is a busy man
If you are like me that needs to use bluetooth, you will have to revert back to ROMs with old radio

raspdeep said:
Bluetooth draining battery is known issue on new radio. I've messaged Sanpei about this and he is looking into it. It may take him sometime to fix this since he is a busy man
If you are like me that needs to use bluetooth, you will have to revert back to ROMs with old radio
Click to expand...
Click to collapse
no, you don't need to revert back to old radio
you just need to flash back stock rom
that's the only rom that doesn't have this issue

I confirm! I've written many times, but this problem has been ignored.
Read here: http://forum.xda-developers.com/showpost.php?p=6679745&postcount=1350.
Stevak.

Omg people, it has not been ignored, but the man that made this kernel has a life of its own jeez....

People U think that fixing BUGs is like "finger click" ? Deva are doing this for free in spare time ... Ehhh ... Instead of complaining to devs please complain HTC :/

@Krzysiec and Klothius.
You do not write so. I respect and appreciate the work of developers (including Klothius). They work very hard and seriously as professionals. I understand that they working in their spare time. They "steal" time in their lives and at their family. They do all this for free.
I thank them and I respect them because they entertain us.
In my post I meant that I (along with others users) have often written of the problem, but none (or few people) replayed. Some answers ignored the problem: "replace the battery", "reset battery status","switch off the radio" etc..
Only a few days the community accepts that the problem is real.
... and now... I think that Sanpei has solved the problem.
Thanks.
Krzysiec and Klothius... you forgive me?

I see that you're saying the problem is solved. Could you provide a link to the solution? I am having the same issue. Streaming to my stereo Bluetooth is draining my battery in no time. Would like to quit having to use the wired headphones again. Thanks.
-------------------------------------
Sent via the XDA Tapatalk App

lotherius said:
I see that you're saying the problem is solved. Could you provide a link to the solution? I am having the same issue. Streaming to my stereo Bluetooth is draining my battery in no time. Would like to quit having to use the wired headphones again. Thanks.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
hi. try this
http://forum.xda-developers.com/showthread.php?t=695406&page=3

Mod. edit: not dev related, moved to general

Something interesting I noticed.

Forgive me if this has been discussed already but I haven't really found anything relating to it when I did a search.
I had started my wifi router when I was using my winmo, then I booted to android. I was at work and my friend noticed that my winmo wifi network was showing up on his phone even though I had been in android for the entire morning. He could even connect.
I had been having freezing problems and high battery drain problems so I thought maybe this could be something that is causing the problems. So as of right now I disable all my wireless communications within winmo before I start my android and things actually seem to run better. I don't know if this is just a fluke or what but I will know more in the morning, as my android almost never fails to freeze when I leave it in standby overnight.
What are your thoughts? Is this common practice to disable these things or is this something new?
Thanks.

Forgot to say I am using Kumars premium 2.10 ROM I think? and Froyostone sense V2.

maybe disabling connections in winmo helps with heavy battery drain, but i can't imagine that it helps with freezes, since they seem to be related to the g-sensor.
or do you have freezes that require a reboot?!

fruchtfliege said:
maybe disabling connections in winmo helps with heavy battery drain, but i can't imagine that it helps with freezes, since they seem to be related to the g-sensor.
or do you have freezes that require a reboot?!
Click to expand...
Click to collapse
I still have freezes occasionally even with the G-sensor disabled with g-script. I get the SOD with NO button lights.

what radio rom do you have? some people report that another radio rom fixed the sod's.

EvilDylan said:
I still have freezes occasionally even with the G-sensor disabled with g-script. I get the SOD with NO button lights.
Click to expand...
Click to collapse
I disable my WiFi in Windows Mobile first.
You may be interested that I found a post suggesting the use of an app called "Lite Setting Profiles" to disable the WiFi when your screen turns off. This, along with having the G-Sensor disabled (SetCPU and Autokiller running as described in various places), seems to have solved my freezes and SoD.
In fact I'm currently testing with my G-Sensor enabled again to see if I can get away with it running as well.

Now that I think about it, yes, I do also see the WinMo version along side Andriod.
But... Even when I was just on WinMo by itself, I would see the Wifi in my laptop's list, even if I had WiFi on the phone turned off. I couldn't connect, but it always did show, so I've been used to it and haven't thought of it once I tried out Android.

fruchtfliege said:
what radio rom do you have? some people report that another radio rom fixed the sod's.
Click to expand...
Click to collapse
I have 2.10.50 radio
Still getting SOD in fact it's getting really bad now. If my screen sleeps for more than 5 minutes I get the SOD.

Here is my 2 cents on your wifi router story.
I doubt that wifi was still running on your windows ROM as windows is killed when android starts.
What I've noticed in the past is when I connect to the wifi router on my phone using my laptop, it remembers the connection for later. In fact, I've had times when my phone is off and my laptop still shows the phone router as available. I haven't tried connecting to it when its not actually available but my guess is that in your friend's case, he would not have been able to browse. His phone probably just showed as connected to your wifi router but did he try browsing something using that connection?

No he killed the connection before he tried to browse anything. My question is though how is the wifi router signal even being seen, i killed windows at home and when I got to work he saw it. That's my main question.
Also I changed my radio to 2.12
maybe that will help some.

I had SOD with almost every build till I switched to the 2.12 radio and have not had one SOD since then.

orangekid said:
I had SOD with almost every build till I switched to the 2.12 radio and have not had one SOD since then.
Click to expand...
Click to collapse
I hope that's the case with mine. So far so good, but if im using it regularly it never seemed to SOD, but if i left it overnight it always SOD without fail.

I had an odd thing happen as well. I had some wifi connection issues in Android and rebooted and turned wifi on in WM and then booted android. Once android was up I had a slow blinking Green LED..which I never get any LED lights on in Android.

[Request] Known NAND builds with 60mA notification bug/fix

Can anyone CONFIRM whether their build has the 60mA bug fixed or not? And I don't mean this 60mA after call bug every one is complaining about, it's the Unread Notification 60mA bug.
To check: Send yourself a text and put your phone on Standby without reading the message for about 5 minutes so it stays Unread and then see if Current Widget is reading 60mA, then Read the message and do it again and it should be reading your 4-5mA (or whatever your typical drain is).
I can confirm DFT and PRJ v0.3.1 HAVE this bug.
In my opinion, this is the most annoying bug right now for NAND; everything else I have managed to find fixes for and it's a real battery drainer.
Edit: The 'fix' posted by Darkstone doesn't solve this (turning off Wireless Network Location), it only solves the theoretical random 60mA drain, but I've yet to have an issue with that on DFT, only the notification bug.

hd2k10 said:
Can anyone CONFIRM whether their build has the 60mA bug fixed or not? And I don't mean this 60mA after call bug every one is complaining about, it's the Unread Notification 60mA bug.
Edit: The 'fix' posted by Darkstone doesn't solve this (turning off Wireless Network Location), it only solves the theoretical random 60mA drain, but I've yet to have an issue with that on DFT, only the notification bug.
Click to expand...
Click to collapse
Have you tied turning off led Notifi ?
Just tested mine .. it doesnt do that thank god lol
I do however have my led notification turned off for all notices.

I tried before and it still did it --- I'll turn them off and reboot (didn't reboot last time) and test again though; gonna be a bummer with no LEDs =( I rely on those pretty heavily.
Edit: Restarted with all notifications off and it still sticks at ~60mA till read, I guess I'll try the build you're using and see how it works.
Edit: Can't seem to find your build anywhere --- Only a squashed v1.2, http://forum.xda-developers.com/showthread.php?t=894965

Bump ---
Can't get this to go away, have tried DFT, PRJ and MDJ Cyanogen and still have this issue.
I've noticed that on a fresh flash of a build it seems to be working fine but after a little bit it seems that the problem starts.
I've tried Task 29ing, different builds, hard resets, wipes, with/without SD, with a fresh format of the SD, going to an Official Win Mo and back throughout the entire Android process, I can't seem to get it to go away. Either there's something wrong with my phone (everything works flawless minus that though) or it's a NAND issue that people tend to miss, I have no idea.
Anyone else that can confirm this happening? Would be nice to know I'm not the only one.

hd2k10 said:
I've tried Task 29ing, different builds, hard resets, wipes, with/without SD, with a fresh format of the SD, going to an Official Win Mo and back throughout the entire Android process, I can't seem to get it to go away. Either there's something wrong with my phone (everything works flawless minus that though) or it's a NAND issue that people tend to miss, I have no idea.
Click to expand...
Click to collapse
I've tried almost every build worth trying and read every post and fix regarding 60ma drain, and I'm convinced there is something wrong with the way the kernel talks to the radio or something. It's a driver bug or something in my opinion. I think the only fix is a couple of those $9 ebay batteries to keep in the pocket. I guess we could be thankful that we can swap batteries and that they are slim and cheap. That's an awful solution, but that's all I got.

If it's of any help, I see this same 60ma drain when the sim card is OUT of my phone and my android is just on airplane mode with wifi.
Also, has anyone heard that 'radio buzzing sound' you get from 'cheap speakers' when you put a cell phone next to them? Has anyone heard this 'buzzing' sound during 60ma drain when the phone is next to some cheap speakers? On an older pc I had with some cheap speakers the speakers would 'start to buzz' before my phone would ring -- like a pre-ring telling me my phone was talking to cell towers. Just asking because I don't know if the 60ma drain happens 'inside' the phone or if it is 'trying to contact outside' the phone.

have you tried comparing a log file from alogcat and the current log from current widget to see if theres some repeating event or error that coincides with the reported 60mA drain? it maybe would shed some light on whats causing this..

pablo71 said:
I've tried almost every build worth trying and read every post and fix regarding 60ma drain, and I'm convinced there is something wrong with the way the kernel talks to the radio or something. It's a driver bug or something in my opinion. I think the only fix is a couple of those $9 ebay batteries to keep in the pocket. I guess we could be thankful that we can swap batteries and that they are slim and cheap. That's an awful solution, but that's all I got.
Click to expand...
Click to collapse
I have one of the $13 2400mA Ebay Batteries and it truly is 2400mA, well worth $13 --- It's good to know I'm not the only one having it.
pablo71 said:
If it's of any help, I see this same 60ma drain when the sim card is OUT of my phone and my android is just on airplane mode with wifi.
Also, has anyone heard that 'radio buzzing sound' you get from 'cheap speakers' when you put a cell phone next to them? Has anyone heard this 'buzzing' sound during 60ma drain when the phone is next to some cheap speakers? On an older pc I had with some cheap speakers the speakers would 'start to buzz' before my phone would ring -- like a pre-ring telling me my phone was talking to cell towers. Just asking because I don't know if the 60ma drain happens 'inside' the phone or if it is 'trying to contact outside' the phone.
Click to expand...
Click to collapse
That's actually a really good thought, I never thought of testing that. If I can find out a way to get my speakers to do it, I'll give it a test.
pyrorob said:
have you tried comparing a log file from alogcat and the current log from current widget to see if theres some repeating event or error that coincides with the reported 60mA drain? it maybe would shed some light on whats causing this..
Click to expand...
Click to collapse
I've never used alogcat (nor do I know what it is, checking now) but I can assure you that when CurrentWidget reads the 60mA drain, it really is draining 60mA, my standby time is terrible if I leave a notification Unread.
--- It seems it may have been Handcent causing my drain? Installed a new build last night (imalka's Glacier Sense --- http://forum.xda-developers.com/showthread.php?t=919148) abd I wasn't getting the drain. I installed Handcent this morning and it appeared again, uninstalled it and a few minutes later I got another text and it wasn't draining. Been good since then so...I guess no more Handcent =( I love that messaging app too, oh well. I'll confirm it that was the problem tonight.

Turns out it was LED Me Know in Compatability Mode, apparently Nand isn't pulse friendly or something because if your LED Pulses, you get the drain.
LED Me Know is pointless if you can't use Compatability Mode so you're better off just saving the space and using the default LED Notifications.
Handcent also causes it because I guess it calls for the LED notification but it's not recognized.
Either way, to fix the 60mA drain I had to remove Handcent and LED Me Know (or use compatibility but it serves not purpose over stock)

[RESEARCH] Mobile network standby drain (Oreo)

Since the first release of oreo I started using the rom as a daily driver, later on paired with a good kernel it had some good perfomance
But after some days of using the rom i started to notice a huge battery drain caused by the Mobile network standby process?
My battery was old (OEM 2014 battery) so i decided to revert back to lineageOS just after a couple of days where I haven't had any issues with that mobile network standby
Now I'm really curious what is causing this issue,drain because I am using the phone on the same settings as on 7.1 nougat, I am living in a country where all networks run on 3G,H+,2G etc. so no 4G if this can be a cause
Changed the network modes many times and tested throughout the days but there was no sucess the drain was still persist, tried updating,downgrading bootloaders swithing modems but again no sucess
If there, in the world of android is any solution, here is the thread to discuss about this issue. :fingers-crossed:

I've wondered this too. I've been running los15 on my g900v , I rooted and boot the first ROM that would work without having or remembering todomuch, I ran the first custom kernal I could find via google, and ran whatever was noted as the latest Verizon modems. its like right off the bat, smooth , consistent battery life and nice. Then the next day I noticed things would crash, my Bt temperamental at best and restarted it just to get by. if I have sync on at home, WiFi off, it just chills , if I turn sync off and drive around town, my battery life gets eaten by the unknown. I pulled some logs to see whats up with my BT but haven't got around to it yet. But my battery too is old (I literally found my s5 in the trash) and I run weird processes and tweak settings all the time just to mess with it, so that could be it to. If I see anything weird I'll let you know.

I'm struggling with this issue for months, since the first port of an Oreo custom ROM (LOS and RR) for the Galaxy A3 Duos (my device) started being developed.
From the beginning I had this problem, and what, since then, puzzles me the most is the fact that only some of us, flashing the same ROM in the same device, experience the issue. Whenever I flash any of those ROMs, even before installing any user apps (or when running in safe mode), the drain is there, which leads me to think that the culprit must be some setting: not an app, because I have none installed; not the ROM itself, because not everybody has this problem.
Unfortunately there seems to be no developers looking into this bug.
For the sake of information, I've observed two things that should help to narrow down the issue; or maybe not.
First, all the devices affected, as far as I've searched, are double SIM.
Second, the Mobile Network Standby (MNS from now on) drain is narrowy connected with the Bluetooth drain (which "also" occurs in Oreo). I've experienced the following: If, after a full charge, I don't switch on Bluetooth at all, then what drains my battery (according to Advanced Battery Usage information) is MNS. However, if I switch bluetooth on -even if only for one minute- then what apparentlyh drains my battery is Bluetooth, at the same speed as MNS did before switching bluetooth on.
Funny enough, the battery use info reports zero minutes activity for both Bluetooth and MNS. But how can a process which runs zero minutes drain 50% of the battery?? I'm afraid that the battery use information isn't reliable. But then that's very bad news, since, in such case, it might well happen that the real juice sucker is neither MNS nor Bluetooth!! We might be dealing with a "ghost" here, since we can't even trust the battery use information provided by the OS.
If someone has something with which to contribute to this research, or any ideas, please comment.

I'm having the same trouble on android 9 betas, even better, my phone gets without signal during those times and there's nothing I could do but rebooting the phone.
How can we help solve this? it looks like it's annoying a lot of people now