I'm not sure if this is the correct place to post this, but it does have a direct bearing on what people will think of a rom.
Base android ie: not based on an HTC kernel has a problem with networking which will usually only manifest on wifi connections.
If you have a classless static route being pushed by the dhcp server then android will load that route but fail to load the default route. That will lead to you having no external network connectivity on wifi.
It took me awhile to figure out exactly what was going on because my home and work servers both have static routes to cater for on demand VPN dialing.
From what I can see the HTC engineers have patched this in their kernels because I only get the problem on AOSP roms, not on roms based on the HTC leaks or release versions. Perhaps some very bright kernel hacker (RichardTrip) would be able to figure out what they patched. The problem does not occur in the eclair stock rom.
I'm having the same issue with wifi on vanilla 2.2 roms. Currently OD 3.0.2 but have also had issue in CM6 nightly.
And as you mentioned, I've had no issue with sense roms.
Its different to the now fixed wifi sleep bug in that it stays connected to the AP just no data passes through?
And it seems some Nexus users also have this issue with their stock 2.2 roms also....
Hi wmobr,
it's easy to fix if you can modify the config of the dhcp server. If you can't then you have to manually add the default route.
You might be able to do it if you modify the rom to include a route update when connecting to wifi networks.
Related
When i make a call the call is immediately interrupted (after a short *bleep). Getting called works though.
I have done a full-wipe and using:
- LeeDrOiD V2.3.4 BETA 4 R2
- Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2
After some simple tests i found that wifi was interrupting the call. When disabling wifi i can make calls again.
I think i have the corresponding logfile (using adb logcat).
I am aware that the rom i am using is still a beta, but since i haven't (yet) found any other user having the same issues i decided to create this question thread. Who can give me some advice to fix this problem? Thanks!
When wifi is on, but not connected to a wifi-network i can make phone calls. Only when connected to a wifi-network, the call immediately gets disconnected after a short bleep.
Found only a single user having simular issues, only he runs on another ROM:
http://code.google.com/p/cyanogenmod/issues/detail?id=2732
E-mailed this person but we both came to the conclusion his problem was different and solved by a ROM update.
Attached is the logcat output. Three lines got my attention:
Code:
D/CallNotifier( 7167): - onDisconnect: cause = ERROR_UNSPECIFIED, incoming = false, date = 1300277007142
D/CallNotifier( 7167): - DisconnectCause is ERROR_UNSPECIFIED: play TONE_CALL_ENDED!
D/InCallScreen( 7167): onDisconnect: incoming: false state: DISCONNECTED post dial state: NOT_STARTED, cause=ERROR_UNSPECIFIED
Full-wiping again and installing LeeDrOid again didn't fix the problem. Installing CoreDroid V4 didn't fix the problem either.
Anyone got some advice how to fix this problem on the Gingerbread beta releases?
Just letting you guys know my issue is resolved, maybe it will help anyone later on experiencing same issues.
I found out not only disabling wifi will make outgoing calls work again, also changing the network settings from 'gsm / wcdma automatic' to 'only gsm' and reverting back again temporarily fixed the problem (outgoing calls were allowed again while wifi was enabled).
I Just flashed a new radio: Radio_12.41.60.19_26.06.04.14_M_Test - HTC Ace Gingerbread S Generic 2.16.0.0
Now everything is working as it should be! I thought it wouldn't be the radio as the issue was solved on an older rom with the same radio.
Edit: The problem persists. At first it seemed to work, but later on the problem came back. It looks like the Gingerbread beta contains a bug, but strange enough not effecting much people... Comparing the dmesg log with a dmesg log of a successful call pointed out that the next few logs are missing on a interrupted call:
Code:
[10894.955902] wds: 0020 @ 01
[10894.956024] qmi: wds: got handle 0x02a73d58
[10894.956542] wds: 0022 @ ff
[10894.956665] qmi: wds: CONNECTED
[10894.957977] wds: 002d @ 01
[10894.958068] qmi: got network profile
[10894.959259] rmnet_open()
Can anyone figure this out?
Isn't there anyone that can help me find out what is wrong or how to troubleshoot this furthermore? Can someone help me analyze the log files. The last thing i want to do is revert to stock and send the phone back for repair . Please advice!
I think it is a kernell/radio issue....
Yes it really looks like a kernell thing, now running excellent on LeeDroiD HD 2.2.2 with LeeDroiD's kernel 2.2.8 using radio 12.28e.60.140fU_26.04.02.17_M2. Still find it strange i am one of few experiencing it. That's the only thing that makes me uncertain about this being a kernell issue, as others should then have experienced simular problems wouldn't they?
I think i will just have to wait for a new (major) kernell release of GB.
Hey,
I am using CM7 and get this issue as well.
Sometimes when I call people all I get is a beep and it disconnects.
Switching to 2g works for me but that is not a good solution imo.
Wish I could get this fixed.
I am glad to see I'm not on my own on this one! 2g isn't a fix for me either, its a not-so-pleasant workaround. Temporarily disabling wifi was a faster workaround, maybe this works for you too. I went back to 2.2.1 because of this problem, maybe you should too.
Please keep me updated!
I always have wifi off when out and about.
Did you get stock rom or something? Post a link to the rom please.
I am just about to try cm7 rc3 - out today.
I installed RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed.exe from http://forum.xda-developers.com/showthread.php?t=824357
After that i gained root and ENG S-OFF again, did a full-wipe and installed LeeDroiD HD 2.2.2 with LeeDroiD's kernel 2.2.8 (http://forum.xda-developers.com/showthread.php?t=842802) followed by radio 12.28e.60.140fU_26.04.02.17_M2 (http://forum.xda-developers.com/showthread.php?t=877295)
So what do you think I should do?
Go back to stock and stick with it?
That depends... I am no expert on this as I am on the same boat as you are. If this is disturbing you as much as it disturbed me you could give the ROM I am now using a go, that's LeeDroiD HD 2.2.2.
Sent from my Desire HD using XDA Premium App
Well I am using CM7 rc3 for now with the latest radio.
I have also changed to GSM auto (PRL).
Will report back tomorrow.
did you set up an voip-account with your cellphone?
I am imagining a scenario like this: voip-Account set up and the option "use internet calls" set to "for every call" (may be called differently, my rom is set to german).
Now, if you enable Wifi, your phone would try to connect to your voip provider and if that fails for whatever reason you should be getting error messages...
If you have your phone sync your settings through you google account, that would explain the error reappearing after full wipe, new radio software and even on a new rom. Flashing a 2.2 rom would make the issue disappear though, as 2.2 doesn't support voip...
Thanks for your reply! Unfortunately this was not the case. There weren't any SIP-accounts configured. I also tested this by not configuring any synchronization accounts after fully wiping and installing a Gingerbread ROM.
Sent from my Desire HD using XDA Premium App
HamsterHam said:
Well I am using CM7 rc3 for now with the latest radio.
I have also changed to GSM auto (PRL).
Will report back tomorrow.
Click to expand...
Click to collapse
Yesterday-evening i installed CyanogenMod 7.0.0-DesireHD and I did not have any issues. After that i installed CoreDroid HD GB 2.3.3 V5.1 but with that rom the problem came back. How did it go for you, you didn't report back.
So does anyone know what the similarities and differences between those two roms are? Both are running on Android 2.3.3 (Gingerbread). CM is No-Sense while CoreDroid is Sense. Are both using the same kernel? Could a difference in drivers be causing our problem? How can i find the drivers that are being used?
Have u checked your apn settings? I had to manually enter proxy and port after cm7 stable install for my phone to work.
Sent from my DHD
Yes, checked those too. At the moment happily using CM-7 without any problems, so as long i stick with this rom everything is fine. Not really a solution but at the moment very happy with this ROM.
So, ever since I upgraded to 2.2.1 (yes the official one, because I didn't check >-<), I've been experiencing problems with my WiFi.
I can't seem to connect to it. It says it's connected, but nothing.
A sorta fix was using WeFi, but even then there's like a 60% chance it won't connect.
Any help?
Try wifi fixer, it helped me while i have problems with wifi
https://github.com/Zanshinmu/Wifi-Fixer/archives/master
Actualy, I already fixed it by using a static IP adress, but thanks for your effort
Wifi n
I beg your pardon but I have a problem with wifi which could be answered in http://forum.xda-developers.com/showthread.php?t=995301
but I can't post there, cause I have no permission. I'm a newbie that does't post too much. That's my first one.
I rooted my wildfire to overclock cpu, I didn't want to change stock rom, so flashed nfinity kernel mc4. Usually I link to 4 wifi servers. After nfinity installation I can't link one of the 4 servers anymore. Is a free access server (named netgear, this factory produces advanced wifi routers I saw). I think the problem could be a question of wifi mode disabled after kernel flashing. Could someone confirm me wildfire uses all b/g/n wifi modes and nfinity kernel disables the n mode? Very pleased if you can give me another explaination of the problem.
Thanks.
Edit: anyway I flashed HDCR v4.1 kernel and now wifi server is accessible again.
at firts i am running cm7.2_rc_buzz_kang(03-14-2012),with original radio(never had to flash another,just few times sometimes reflashed to make gps work),custom mtd
i would like to ask devs for this question, but i cant, so i try at least here...
some time ago our router at home has been changed and so has wlan...and that started to cause me problems,because i cant set router up for my phone to provide "g" wifi which works flawlesly..(actually,discovering,that everything is caused by "n" wifi provided by router was very funny,because it was the last thing i thought i could be ) however..after some googling and much xda reading i found app called Wifi fixer,which in most cases fixes my problem,but it doesnt work in 100% cases,and its not the "coolest" solution
few days ago i found Sympnotics kernel,and flashed it,one of reasons was its declared "n" wifi fix,which didnt work...i know,its beta,im not complaining,just saying what i found...btw thats the only thing,that is not good FOR ME on that kernel
so i thought to look for another...
i found infinityplay,which didnt work in "my" way,neither did "official" arco68s,neither last hcdr.kernel_v4.2...
the only one i found working is HCDR.Kernel_v4..
my next idea was (i am noob,so sorry... ) to copy bcm4329.ko (which should be wifi module of kernel) from HCDR.Kernel_v4 to SympKernV4.1..that (surprisingly ) didnt work...at least i tried...
so there is my question...(in this moment,youre the only person who i know is developing kernel,most for Sympnotic) would it be possible to have your kernel with hcdr.kernel_v4 wifi module??
if i have known to do this on my own,i wouldnt bother to ask here, but i have no idea how to build my own kernel,even how to take one,change wifi module and again make flashable zip...
sorry for my english,its not my native language
thx you all here
edit:i have the same problem with cm9,bulit does not matter...btw with hcdr.jacobs v4 wifi does not work...
As many of you know, since the 4.3 update, WiFi on the galaxy nexus stops automatically scanning after going into deep sleep. The only way to get it to scan again is to go into the WiFi menu or toggle it on and off. Let's try to find which change in 4.3 broke this on the galaxy nexus.
I have been looking through the changes that have been made between 4.2 and 4.3 to how wifi is handled and may have found what is causing the issue.
Right now this is not working. Trying to find the real issue
I think I may have found something. In /system/etc/wifi/wpa_supplicant_overlay.conf
Theres a line:
disable_scan_offload=1 (has to do with allowing scanning to be offloaded to the driver)
This line didn't exist in 4.2.2. Change it to 0 and reboot and see if your wifi scanning doesn't stop working after a while.
I just ran an errand and it connected perfect when I got home which is usually when it stops working. I need further testing but would appreciate some more testers to see if there's a real change in behavior.
Original Thread:
http://forum.xda-developers.com/showthread.php?p=45325052#post45325052
Testing now
testing now also. hoping that its gonna work!
will Test it :good:
This was added here https://android.googlesource.com/pl...an/+/b9eb5a1254e16f160bce0294fc33f59a177c6ff5
But now the question becomes what is Bug: 8725307
Ugh. Seems like this wasn't the culprit. Will have to start digging some more.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
go to the wifi screen. in the bottom right corner there should be a 3-dot menu button. click on it and go to 'advanced'. there's an option 'Keep Wifi on during sleep'. Set it to 'Always'.
Sent from my Galaxy Nexus using XDA Premium 4
That's not the issue. I have that set to always.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
@blackhand1001 hopefully it helps http://forum.xda-developers.com/showthread.php?p=46402184
aosp said:
@blackhand1001 hopefully it helps http://forum.xda-developers.com/showthread.php?p=46402184
Click to expand...
Click to collapse
Is that in the kernel itself or part of the OS. If its kernel I should let franco know since that is the kernel I am running and I recall a few weeks ago seeing that commit merged into CM. I wonder if the stock CM kernel already has this fixed.
blackhand1001 said:
Is that in the kernel itself or part of the OS. If its kernel I should let franco know since that is the kernel I am running and I recall a few weeks ago seeing that commit merged into CM. I wonder if the stock CM kernel already has this fixed.
Click to expand...
Click to collapse
Kernel WiFi drivers
aosp said:
Kernel WiFi drivers
Click to expand...
Click to collapse
OK, so this may be fixed in the stock CM kernel then and using franco is what screwed me up.
aosp said:
@blackhand1001 hopefully it helps http://forum.xda-developers.com/showthread.php?p=46402184
Click to expand...
Click to collapse
blackhand1001 said:
Is that in the kernel itself or part of the OS. If its kernel I should let franco know since that is the kernel I am running and I recall a few weeks ago seeing that commit merged into CM. I wonder if the stock CM kernel already has this fixed.
Click to expand...
Click to collapse
Hmm, I'm not so sure that would be the issue
The current wifi module (driver) should, without other interference, give you the SAME wifi performance it always has, no matter what android version
as far as i know, all modules are contained within the zImage of kernels which are fairly compatible over android versions, its the ramdisk that changes
4.3 kernels that use your rom's built in ramdisk (any kernel type) are relatively easy to port back to 4.2.2 and vice versa, but kernels that use a full boot.img are very very incompatible over different major android versions (usually you never get past the boot logo or at least get stuck in a constant boot loop)
The only issue i could really see with older wifi drivers would be some incompatibility with something in the OS, which would be more of a google issue (they DID push 4.3.x to the gnex and should have either updated the kernel or made 4.3.x more compatible with the older wifi module)
again this is simply educated guesswork here, and i could be entirely wrong lol
metalspring said:
Hmm, I'm not so sure that would be the issue
The current wifi module (driver) should, without other interference, give you the SAME wifi performance it always has, no matter what android version
as far as i know, all modules are contained within the zImage of kernels which are fairly compatible over android versions, its the ramdisk that changes
4.3 kernels that use your rom's built in ramdisk (any kernel type) are relatively easy to port back to 4.2.2 and vice versa, but kernels that use a full boot.img are very very incompatible over different major android versions (usually you never get past the boot logo or at least get stuck in a constant boot loop)
The only issue i could really see with older wifi drivers would be some incompatibility with something in the OS, which would be more of a google issue (they DID push 4.3.x to the gnex and should have either updated the kernel or made 4.3.x more compatible with the older wifi module)
again this is simply educated guesswork here, and i could be entirely wrong lol
Click to expand...
Click to collapse
Its not the performance thats the issue. Its the fact that it randomly stops autoscanning. I think the newer 4.3.1 kernels and some kernels that pulled the updated wifi drivers fix the issue though.
Edit: never mind, this is still borked even on the 4.3.1 stock kernel.
Currently i'm using 4.3 on top of JSS15Q build though usually it happens very rare, the issue that's messing with NP is the HD playback Stuttering !
Doesn't seem to work for me :/
I have tried the Kitkat ROM of Evervolv and I want to report my experience.
You can find the ROM here:
http://nikez.nu/Download.php?getFile=dlc/ev_bravo-4.0.0p2-turba.zip
I found the ROM very reliable. No crash no reboot no SOD. There are 2 main bug:
1) The hotspot doesn't work.
To fix this problem is sufficient to replace the file hostapd and hostapd_cli with those in this ZIP:
http://forum.xda-developers.com/attachment.php?attachmentid=2434441&d=1386246859
as reported here:
http://forum.xda-developers.com/showpost.php?p=48161953&postcount=128
2) The browser has flickering screen. You can disable it from Settings->Apps->All->Browser and try another browser. I use Opera because is lightweight and usable. Try it out: https://play.google.com/store/apps/details?id=com.opera.browser
Without a2sd the system is very fast and fluent. If you want to use it would suggest to use at least a Class 10 sd card otherwise the app loading and even the screen unlock can take more than 5 seconds.
If you want to install a2sd DO NOT put the dalvik cache on the sd card unless you have a very fast sd card. Otherwise this will slow down your phone. I've installed 15 / 20 app and I have about 30 MB left on the internal storage, so I think this is enough. To install app data only to sd card install the script in this way:
a2sd install
N
Y
Y
There is a feature that i liked of the previous Evervolv JB and was the home screen rotation. In this ROM there isn't such feature. In my opinion is very frustrating to have the screen rotated back to the portrait mode when in landscape mode i press the home key. To enable home screen rotation I installed Nova Launcher app and enabled screen rotation by: Nova Settings -> Look and feel -> Screen Orientation -> Auto Rotate
Thank you again to the Evervolv Team.
It's 2 week that I installed this ROM and still no problems.
The olny thing I noticed sometime is a delay in the screen power on when you want to hang up a call. The screen remains black for 3-4 seconds and then if you press the power button again it work. I think this could depend on the number of the apps opened on the phone indeed this doesn't happen every time.
VPN - Another Kitkat bug with evervolv?
Hi,
currently I'm running the ev nightly-2013-12-15. Since yesterday I tried to activate a VPN connection into my home lan (connected with an AVM Router). It does NOT work. While the "internal" VPN Software does not tell me some interesting information a second try with VPNCilla shows:
--- cut here ---
Error on establish:
command '693 interface fwmark rule add tun0'
failed with '400 693 Failed to add fwmark rule (File exists)'
Possible reason: invalid server parameter or TUN device unavailable
---cut here ---
With this error message I find in google some information about a VPN problem in 4.4. BUT: my wife's brand new nexus 5 with Kitkat connects without trouble immediately with the same login data.
So what's the problem with ev here?
Any ideas?
Thanks in advance
I have never tested VPN with android though I had problems getting hotspot to work. I had to substitute the hostapd and hostapd_cli file to fix the problem (I posted how to achieve it in the previous post).
Have you tried the turba release ? Maybe the problem is related to a nightly bug.
However It is true that the Nexus 5 has a 4.4 too but the kernel version is different. The evervolv version run with the 2.6.37 kernel version because probably the driver (or kernel modules) of the HTC desire are not available for the new kernel version 3.x.x that is the version used for Nexus 5 and other official release.
So different hardware and software can lead to different behavior of the software.
The only thing that come into my mind is to try with a shell (adb shell) to manually create a VPN connection to see what specific errors are showed up.
I think this is a great rom, which runs very smoothly.
I have currently installed the ev_bravo-nightly-2014.01.22-squished.zip from yesterday on my desire.
But I have a problem using Wifi connection. At first it worked, but now Wifi wont turn on. It also says MAC-Adress is unavailable. What I have done was to delete the app2sd script from init.d and to install Int2ExtV2 (runs perfectly). I don't know if this can cause the interference? I have not made any other changes.
It would be great if anybody knew, how to fix it.
I have not tried connecting to a VPN so far.
ProDC
Hi,
I'm running Nikez's 4.0.0p2 version and it's great! No JB rom is such stable and fast. For me, there are no bugs, but I don't use hotspot feature. Is it worth to upgrade to nightly versions? I'll maybe wait until Nikez releases next version with stable 3.0 kernel .
Do MMS work?
Sent from my HTC Desire using xda app-developers app
I haven't already tried the new nightly but I guess that it is not as stable as the 4.0.0p2. I prefer stable ROMs because I use my Desire daily. This is the most stable and faster ROM I found among Evervolv ROMs. So I would suggest you to keep the 4.0.0p2 unless you have a blocking problem with this ROM.
SemaiCZE said:
Hi,
I'm running Nikez's 4.0.0p2 version and it's great! No JB rom is such stable and fast. For me, there are no bugs, but I don't use hotspot feature. Is it worth to upgrade to nightly versions? I'll maybe wait until Nikez releases next version with stable 3.0 kernel .
Click to expand...
Click to collapse
For quimbexa :
I've tried two times but the screen only show "SENDING...". I waited for 2 hour and then i deleted the messages. So this feature could be buggy.
Why do you need this feature ? Using whatsapp or similar app it's faster and cheapest than using MMS today.
Prodc said:
I think this is a great rom, which runs very smoothly.
I have currently installed the ev_bravo-nightly-2014.01.22-squished.zip from yesterday on my desire.
But I have a problem using Wifi connection. At first it worked, but now Wifi wont turn on. It also says MAC-Adress is unavailable. What I have done was to delete the app2sd script from init.d and to install Int2ExtV2 (runs perfectly). I don't know if this can cause the interference? I have not made any other changes.
It would be great if anybody knew, how to fix it.
I have not tried connecting to a VPN so far.
ProDC
Click to expand...
Click to collapse
Are these nightlies KitKat or ...?
---------- Post added at 05:01 PM ---------- Previous post was at 04:06 PM ----------
vixx1978 said:
Are these nightlies KitKat or ...?
Click to expand...
Click to collapse
Just installed it, yup, it's KitKat