Develop Bugs

[Q] Xdandroid call/wake issue

So I've had this problem as far back as I've been trying the various builds of xdandroid where if my T-mobile TP2 is in full sleep and it receives a call it fails to wake properly causing it to lose the ability to accept or make calls until rebooted. It's been there regardless of build version, ril version, rootfs version, and kernel version. Pretty much the only thing I haven't tried is changing the radio rom since I figure that shouldn't be where the problem lies since I'm using the same radio version as the guy who designed the current ril according to his XDA profile.
I've tried dealing with the xdandroid guys directly but they refuse to accept it's a problem with their code instead of my phone despite the fact everything else the should work in android works flawless and no such problem exists in Winmo. So I come to you the public of the XDA forums does anyone else have this problem with this model of TP2 so I can point out it's not my phone but in fact an issue with their code. I've also tried contacting highlandsun directly via email and PM with no response.
Oh and before anyone suggests sending them log dumps I did that. I even pointed out to them exactly where the ril fails during the incoming call and how when I attempt to make outgoing calls before a reboot how the oncreate function for the new call never finishes because the ril has gone screwy.

If you know where the issue is occurring, then why not fix it?
You say you've sent logs, yet you don't attach them here.
You say you know where the issue occurs, but don't document it here, for everyone...?
If you honestly feel there's an issue with the code (which we all know there are still many) then please, submit a patch. Improvements are always welcome, there's GIT repo's which you can make merge requests and everything.
This also belongs in the Android section, but it seems you don't have enough posts to post in that section...

arrrghhh said:
If you know where the issue is occurring, then why not fix it?
You say you've sent logs, yet you don't attach them here.
You say you know where the issue occurs, but don't document it here, for everyone...?
If you honestly feel there's an issue with the code (which we all know there are still many) then please, submit a patch. Improvements are always welcome, there's GIT repo's which you can make merge requests and everything.
This also belongs in the Android section, but it seems you don't have enough posts to post in that section...
Click to expand...
Click to collapse
First of all I'm not looking for help fixing the problem from the forum at large. I'm looking for additional people with the error in order to prove it's not unique to my phone, something that you personally tried to claim on the bug tracker.
Second I know enough to be able to diagnose where the problem lies but unfortunately cell phones aren't my specialty so I have neither the knowledge of the android source code nor the code for interacting with cell phone hardware necessary to fix it or else I would have long before approaching the team with the problem. I figured giving you guys all the necessary details on the issue including all the dumps would have been enough to get it fixed in a time frame faster then I could have done it myself since you already know the system quite well but instead you blew off the issue claiming that since it doesn't happen to all Rhodium 210's it can't be a problem with the code and it must be my phone.
If you'd like me to resubmit the bug to the bug tracker I can do so with a fresh set of logcats and dmesg with the problem spots highlighted to make them easy to find along with any other details you might need about firmware versions, running software and condition under which android was launched since we both know having certain things on in Winmo will effect how things run in android.

Daemeon6.7 said:
First of all I'm not looking for help fixing the problem from the forum at large. I'm looking for additional people with the error in order to prove it's not unique to my phone, something that you personally tried to claim on the bug tracker.
Second I know enough to be able to diagnose where the problem lies but unfortunately cell phones aren't my specialty so I have neither the knowledge of the android source code nor the code for interacting with cell phone hardware necessary to fix it or else I would have long before approaching the team with the problem. I figured giving you guys all the necessary details on the issue including all the dumps would have been enough to get it fixed in a time frame faster then I could have done it myself since you already know the system quite well but instead you blew off the issue claiming that since it doesn't happen to all Rhodium 210's it can't be a problem with the code and it must be my phone.
If you'd like me to resubmit the bug to the bug tracker I can do so with a fresh set of logcats and dmesg with the problem spots highlighted to make them easy to find along with any other details you might need about firmware versions, running software and condition under which android was launched since we both know having certain things on in Winmo will effect how things run in android.
Click to expand...
Click to collapse
Pretty hard to fix an issue that only you can reproduce.
hyc hasn't had much time at all for XDAndroid lately. C'est la vie. He is the best one to look at it, but PMing him about the problem over and over isn't going to do any good. The bug you already submitted is fine. I don't know what else to tell you other than good luck.

arrrghhh said:
Pretty hard to fix an issue that only you can reproduce.
hyc hasn't had much time at all for XDAndroid lately. C'est la vie. He is the best one to look at it, but PMing him about the problem over and over isn't going to do any good. The bug you already submitted is fine. I don't know what else to tell you other than good luck.
Click to expand...
Click to collapse
Hence why I'm looking for more people with the problem. Once I find them then I can start searching for commonalities to help make it easier to fix by ruling out causes or if lucky find a specific trigger such as how having bluetooth on in Winmo will cause android not to go into full sleep.
Also only tried both once so as not to needless fill up his inbox. I figured he'll read one or the other eventually unless he's prone to deleting things without reading them.

Daemeon6.7 said:
Hence why I'm looking for more people with the problem. Once I find them then I can start searching for commonalities to help make it easier to fix by ruling out causes or if lucky find a specific trigger such as how having bluetooth on in Winmo will cause android not to go into full sleep.
Click to expand...
Click to collapse
I wish you luck.

i have the same problem too... xdandroid 2.3, thaidai nice, everything works fine, but when i click Call End, the htc sleeps, and it suck for wake again.
htc Diamond
i find this on google, i think solve the problem, but i'm a android newbie ^^

This same thing was happening to me as well, up until a week ago. I had the latest incremental updates on FRX 7.1 , AT&T TILT 2 (Rhodium 300).
In addition, I was also seeing very bad performance lag, freezes, often eventually leading up to a reboot, and other issues which I chalked up to being I/O related whenever more than 3 or 4 large programs were running at once (such as Facebook, Google Maps, Browser, and Market 3.0).
After doing some research, I found out that my PNY 16GB Class10 MicroSD Card may be to blame since Class 10 cards (and maybe Class 6) have built-in hardware read-ahead, and doing any kind of Random Access I/O on them like these Android builds is less than ideal...
So I ditched the Class 10 card (gave it to my wife to use on her BB Torch) went up to Walmart and bought the Class4 Sandisk for only $29, formatted it in the same way with the HP USB FW format Tool using the card's native cluster size (32K), copied all files over as-is and sure enough using, the exact same installation, every last stability and performance issue has completely gone away. Froyo has been running rock-solid for three days now, and the call-answer bug isn't happening anymore either!

Is there any WiFi Error solution?

I went through google, here, and other android blogs and where I found people who've had a similar problem to mine, there seemed to be no concrete solution.
What I'm talking about is literally in front of my eyes, though I didn't know the extent at the time, the wifi \ bluetooth died. I was listening to a podcast and the wifi turned off. I had no problems that led to this, no issues with the ROM (Energy) and anything else to indicate anything was wrong. So after turning it on it would just say error, and that was it.
Like other posters who've brought this up, I cleared cache and dalvik, went to stock, went to other backups from different ROMS, and still nothing. So is there anything concrete anyone here knows about? Thanks in advance!

ImAMember said:
I went through google, here, and other android blogs and where I found people who've had a similar problem to mine, there seemed to be no concrete solution.
What I'm talking about is literally in front of my eyes, though I didn't know the extent at the time, the wifi \ bluetooth died. I was listening to a podcast and the wifi turned off. I had no problems that led to this, no issues with the ROM (Energy) and anything else to indicate anything was wrong. So after turning it on it would just say error, and that was it.
Like other posters who've brought this up, I cleared cache and dalvik, went to stock, went to other backups from different ROMS, and still nothing. So is there anything concrete anyone here knows about? Thanks in advance!
Click to expand...
Click to collapse
So as to fix this problem,some people suggest to do a Factory reset.But, it is completely unnecessary.Instead you can try the following methods, which where tested by me successfully.
1. Dial *#*#526#*#* to reload the wifi driver.If it doesn’t work, restart your phone and dial it once gain.It will work for sure.
2.There is an app “Wifi-Fixer” from android market,which claims to be fix this problem.But seriously,it hadn’t worked for my mobile phone(Samsung Galaxy Ace).But,
if you are interested, can download and try it here.
For HTC users, I have a pretty good trick which works very well.
When you have obtaining IP address problem,
1.Turn off wifi.
2.Open “Allshare”, then you will be asked to connect to a wifi network.
3.Then select the wifi network that you need to connect from the list opened.
Magically, you will be connected without any extra effort.This works 100% sure without fail.
If that doesnt work try this:
1.Dial *#*#526#*#*.Then a message will be shown “Driver loading Successful”.
2.Now Start the WiFi, it should work.
If the message “Driver Loading Unsuccessful” is shown, follow these steps:
1. Dial *#*#526#*#* again and click options button on your phone.
2. Select Rx test.
3. Select Channel >9 .
4. Click Start and exit.
5 . After some time, turn on the wifi.It should work.

It is possible you've fried your wireless card.
Can you test Bluetooth calling?
If enough heat built up for a long enough period of time both could be affected.
ie charging while on wifi using Bluetooth and a heavy CPU workload is a perfect recipe.

Okay Diablo, thanks for the suggestions but of course, it didn't work. So many times I read these threads where people are having trouble for one reason or the other and nothing ever seems to work... Now I'm that guy.
So like I said, I would dial those numbers and nothing would come up. Now I did try wifi fixer and it really looked it was doing something, but again, nothing happened.
And 9h0S7, I'm fearing you may be right... I've read the bluetooth and wifi are on the same antenna, and I can't get the bluetooth working either. A friend of mine checked the board and everything looked fine so visually speaking nothing seemed corroded or messed up in anyway.
Anyway, thank you both for your help and I continue to hope this can be fixed!

Help! No Wifi connection now...
I had the "Wifi Error" problem with my Samsung Galaxy Ace device, so tried to follow the procedure described with Allshare. It didn't work, and now my device is not able to connect via wifi in any way! I've tried restarting the phone many times and dialling the code to reload the driver, I tried to download Wifi fixer, but no method works. The phone "sees" the Wifi network, tries to get the IP address and then disconnects. I don't know what to do... I'm desperate...:crying: :crying: :crying:

[Q] Wrong ARP WiFi annoucements with JB ROMs

I've got a significant problem with my DHD when running any of the latest JB releases I've tested -- the problem appears with the JellyTime, codefireX, pipelinerard's CM and also the AOKP ROM's I've tested, even on a clean install (complete wipe of everything but the radio, install only the ROM; gapps not needed to cause the issue). The problem is however not manifest in IceColdSandwich, so I suspect something is broken in the way JB uses the WiFi network compared to how ICS did it. Maybe that triggers a bug somehow in the radio or misses some important radio settings?
To some/many people, it may not be immediately visible, but if you have this problem and use your phone on a large network, you might get banned/kicked off the network if they use rules similar to what e.g. Princeton recently implemented. You may also experience this as intermittent network problems with some hosts being unavailable from time to time.
Here is what happens:
Whenever the phone sleeps (i.e. the screen is off), it sends out bogus ARP message every 15.1 seconds (give and take 10mS or so). The message typically announces "IP x.y.z.v is at MAC ii:ii:ii:ii:ii:ii:ii" where the MAC address is the one of the phone and the IP addresses seems to come from some predetermined list and/or the routers IP -- or it might be 0.0.0.0.
On my network, when using one of the AP's, it will send out seemingly "real" IP addresses that will clog up the main router, trigger additional traffic to poll the ARP addresses and eventually cause misfunction and loss of connectivity also for other clients on the network -- it will however heal itself after some minutes, when the ARP cache times out, just to reappear again later randomly.
On the other AP it will always announce an IP of 0.0.0.0, which is obviously incorrect -- but doesn't cause any direct malfunction.
From time to time, I've also seen incorrectly formatted ARP packages.
I've debugged this with wireshark and pcap's on my network (as I started to wonder about more frequent network problems after using this phone).
I've also tried running tcpdump on the phone itself, and have inspected the pcap from the locally captured file. That pcap does NOT contain the ARP messages, so somehow somewhere deep down the kernel or in the radio, ARP messages are triggered to be sent out (i.e. below the capture interface).
To see if you have this problem, you need to run wireshark on another device and check for traffic from your phone's MAC address. It is easy to see if you know what to look for. You cannot know if you have this problem unless you check for it -- but you might suffer weird connectivity issues from time to time also on other devices/PC's, depending on the rest of your network components, that are not immediately discernable as related to the phone.
Technically this looks similar to ARP spoofing/flooding, with similar symptoms.
Does anyone have any ideas how to fix this? I think this requires someone with kernel/network knowledge, and it is likely related to how parts of the legacy parts (binaries) are being used.
I'm initialy trying to figuring out what runs every 15 seconds on the phone, and would then like to start tracing/bisect ICS vs JB code here.
Would also be nice if someone else could confirm this -- even though the specific symptoms apparently depend on certain WiFi related parameters.
Any ideas?
For reference, I'm using the latest radio 12.69.60.29_26.17.14.11_M. But as ICS does not have this problem, it might not be related to the radio version directly.

WiFi and Bluetooth won't turn on - Hardware defect or persist folder?

Hey all,
So I've been working on this for quite some hours now for two nights, but I'm done for and hope someone can give me clarity:
HTC One m9, running stock, latest update VDF Germany, Android 6.0.
Problem occured last week. I was using the phone quite extensively (yeah, tbh I was playing Pokemon Go... like a lot). With it being constantly on wifi/4g/GPS and all, charging it all the time, the battery also became quite warm.... And then while walking about it crashed and rebooted. I never had such a crash before tbh. After Reboot HTC Error Report even popped up and I also sent it. Then I found that the Bluetooth and Wifi Connections were off, which I usually both have activated all the time. And now I cannot turn them on anymore. No matter which shortcut is used. Wifi displays "error" after some minutes, while BT is just greyed out after triggering. Wifi Mac is showing with a 02:00:00:00:00 now as well.
So I did my research and performed quite some things, trying to get it fixed, because I am still not sure wether this is a Hardware or Software issue. A lot of people reported the issue at least for the wifi part. Less people reported it for both, wifi and BT, but I would guess that not too many people use BT regularly anyway. I found one person mentioning, that if both is not working it is most probably a hardware related issue. Which was my first thought exactly, thinking it overheated, something had gone loose internally and now the antenna is killed or at least not connected anymore.
As for the physical methods, I only tried the "whacking the back part of the device"-technique, which did not do anything. I haven't gone through "freezer" or "hair dryer" yet....
Some people were able to fix it via draining the battery and then restarting and draining again and what not.. but that all sounded weird to me.
I am still hoping it is software related so I went:
- Wifi Fix and Rescue App
- Unlock
- TWRP
- Root
- Reflashing stock
- numerous factory and network settings resets
Because I read about the /persist partition or folder and that it should contain wifi or mac address related info. Some guy had simply deleted those files and they were recreated upon reboot. But those files are not existing in my /persist folder (checked via Root Explorer - got the paid version) and I have Root - as stated above. Still that folder only lists:
\data
\display
\hlos_rfs
\lost+found
\rfs
\tee
I found a thread in google's cache of someone on how to recreate or fix that folder and contents, based on a nexus 5 however and that is probably not working on the HTC one m9 I was presuming.
So, what do you guys think?
Is there any way to get the wifi back to work? Would you say it even might be software related, looking at the persist partition/folder contents? Or am I totally wrong and the fact that BT AND Wifi are not working, rules everything else out and only leaves a Hardware Issue?
Looking forward to hearing your thoughts on this.
Thanks in advance!
- Arne

I'd bet a bollock its the hardware popped. Bluetooth and wifi are on the same board, probably the same rf chip. A local phone repair shop should ve able to fix it seeing as it's out of warranty.
Beamed in by telepathy.

Question Phone reboots a few seconds after loss of mobile data connection?

Hello guys/gals,
I am anything but an Android pro, but generally I know a bit about tech stuff.
This new Redmi Note 8 (ginkgo) is currently driving me crazy, though.
Had bought it specifically due to the LineageOS support, that I was looking for.
However, I am facing a VERY ANNOYING issue with this phone, with both stock OS (MIUI 12.1) and LineageOS 17.1:
Wanted to run the phone with a Vodafone SIM card.
Behavior with LineageOS it is like this:
As soon as the phone loses the mobile data connection, it only takes a few seconds and the phone will reboot. Will do it as long as there is no mobile data connection. Boots up again afterwards, but upon login, it again only takes a few seconds and then it reboots again. Useless this way.
With stock OS, the phone does not reboot, however I see it indefinitely detect SIM ==> loose SIM ==> switch to WLAN ==> drop WLAN ==> detect SIM ==> loose SIM ...
Same again in an endless loop. As a result, the phone is more or less unusable, as it can neither use mobile data, nor WLAN.
ONLY with a stable mobile data connection, this thing seems to run like intended with both stock and Lineage.
Have never seen something like this before!
And the best part:
Also tried two Telekom SIM cards.
No problems whatsoever with the Telekom SIMs, even with no mobile data connection!
If anyone should have insights on what might be happening here, let's hear it.
BTW, already once replaced the Vodafone SIM. No change in behavior.
Thanks to anyone who's willing to help. Certainly much appreciated!
Maybe this problem is already known.
Best regards,
madocer