Related
After flashing CM6.1 I got the notorious wifi connectivity issue that numerous people have been reporting around the web. The issue is the following:
1: Wifi discovers neighbor's AP but no longer home AP.
2: Wifi problem randomly fixes itself, but sometime comes back and home AP can't be found again.
Many random solutions on the web include removing all stored AP's on the phone, resetting the router, rebooting and power cycling the phone numerous times, etc. Most people report that wifi miraculously start working again after the above but there is no consistency to exactly why and what works.
I tried all of the above with no luck, and even flashed three different roms with different kernels, did wipes, formatted everything inculding boot partition etc.
Here is the ACTUAL problem:
Different regions use different wifi channels. North America uses the first 11, most of the world uses 13, and Japan uses all 14. After flashing CM6.1 it changed the regulatory domain on the phone to only scan the first 11 channels meaning my European router broadcasting on 13 wouldn't show up. This setting seems to be persistent and doesn't change just because a new rom is flashed.
The reason people report the problem to be randomly fixed after a few days (and sometimes coming back days later) is because most routers automatically select which channel to broadcast on and therefore might end up within the first 11 at occasion. If it changes to something higher after that however, the problem is back.
Solution:
Open Settings, Wireless & network settings, Wi-Fi settings. Press "Menu" and select Advanced. Press regulatory domain and change to 14 channels.
To learn more about this and understand which channels are used in which countries, look here: http://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4.C2.A0GHz_.28802.11b.2Fg.2Fn.29
Thanks man, even I still met an issue which was wifi disconnect frequently (usually after 12 seconds or less, it's re-scanning AP and trying to re-connect again) when I was trying to share my broadband internet from laptop to my legend.
BUT, after I update my wlan driver (now using 8.0.0.238 for my Atheros AR5XXX), the issue seems gone.
I found that by updating wlan driver to the very latest driver (for mine is 9.2.0.xxx) is not a guarantee to resolve this problem.
Now, by combining your suggestion and an "appropriate" driver version for my wlan, it work flawlessly until now
PS: driver version which will work varies from devices to devices. Do trial and error if you must
edit: well, not 100% gone, but much better . the connection is far more stable
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Rapier said:
My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause
Click to expand...
Click to collapse
I think you're right. Yesterday, I tried my friend's phone (which has a stock ROM), using the same AP and there was no dropped signal or disconnected in wifi. I also tried using other android phone brand (5 series from samsung) which also has a stock ROM and there was no problem at all. Drivers is the culprit
Work
Thanks u very much.worked on my milestone
Thanks. Actually worked.
Rapier said:
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Click to expand...
Click to collapse
Hello Rapier,
I have installed the CyanogenMod 6.1.1 (stable) on my HTC Desire (GSM / France) with latest radio image (32.49.00.32U_5.11.05.27) and taken some time to configure it. Now, everything seems to run well ... excepted the WiFi (and perhaps also the GSM). My problem is exactlw what you have described:
- on stock ROMs, the WiFi signal is stable and quite strong
- on Cyanogen ROM 6.1.1, the WiFi signal fluctuates, the connection is unstable and gets lost.
I like CyanogenMod ROMs very much. The WiFi issue is the only thing that I was not able to correct. You were speaking about WiFi drivers: would it be possible to extract the WiFi drivers from the latest HTC Desire stock ROM and copy them into the CyanogenMod installation?
My impression is that the CyanogenROM is scanning for networks in the background, even if a stable and strong WiFi network has been found and is currently connected. Perhaps there is a possibility to disable this scanning?
To finish, I have also the impression (I know, this is not very scientific ... but perhaps it could help to determinate where the issue comes from) that the GSM network is also fluctuating. I use WiFi Analyzer (available on the Android market) and when I plot a graph, without moving the phone or even without moving myself, the plot oscillates between -80dBm and -30dBm (I swear that there is nobody playing with the on/off button of my ZyXEL router ).
@sz1a: Thank you very much for your post: this helped me to discover these "hidden" settings, but my configuration is manual on the ZyXEL and everything was fine. Perhaps you should switch the thread to "unsolved".
I'n not a developer, only an ethusiast with a Legend. Also I'm not a Linux expert so I can only guess and experiment...threfore I cannot tell if porting HTC proprietary drivers is possible. I'd say not...if it was, we would have it by now. The main reason I think, is that those drivers are not open source, so nobody can port them since the sources are not available. I'm sure that if it was possible, they'll have been included in CM
Sent from my Legend using XDA App
pleaaaase help, im running CM 6.1 RC 1
wifi was working fine untill yesterday, i tried to connect to my friends router but couldnt.. i tried putting it in manually too.. then i couldnt connect to any router infact my phone wont even pick up any even my home one.. i tried switching to 14 channs like this said but no luck
any help please
Hello,
If you don't want the boring details of how I discovered the problem feel free to skip the next couple of paragraphs and go straight to the technical details.
I got my first Android phone (Motorola Defy) a couple of weeks ago and at first I was only using it with wifi because my data plan wasn't activated yet. While playing with it a little I realised that I saw a lot less ads than my boyfriend on his 6 month old Defy. I thougt it was weird but, well, seeing less ads is not a big problem.
Then when I got my data plan I saw that when I wasn't home I saw a lot more ads, so I began to suspect it had to do with how my phone was connected to the internet : wifi or 3G.
Next I wanted to try out Astrid and when I tried to log in using my Google account it failed repeatedly. Until I disabled wifi and it logged in fine using 3G.
Then I installed RTÉ DocOnOne to listen to documentaries while falling asleep. When wifi is enabled, it cannot start up because it can't connect (network timeout). Over 3G, no problem.
At first I thought it was my router blocking ports or something but it happens with different wifi APs and more importantly my boyfriend's phone, connected to the same access point, loads everything without a problem.
Let's sum up:
Some apps can't access the network using wifi but work fine when using 3G.
It happens regardless of the wifi AP (tried 4 different ones with different routers) and another phone using the same app connected to the same wifi AP can access the network just fine.
If I initiate the connection using 3G then switch to wifi (typically I launch the app with 3G, switch wifi on without closing the app), it still works after that (RTE DocOnOne has no pb streaming the documentaries once it has launched)
My phone is a Motorola Defy, French retail ROM, not rooted, no motoblur account (skipped the configuration), Froyo 2.2.2 (already on the phone when I got it), system version (if that means anything to you) Version.34.164.3.MB525.Retail.en.FR, kernel 2.6.32.9-g050ccf2, build 3.4.2-164
I can't give as much details about my boyfriend's phone (that doesn't have the problem) because he's not here right now but I can tell you that it is a Motorola Defy too, French retail (I think) ROM, Froyo updated from preinstalled Eclair (using the official Motorola update), not rooted, with a motoblur account
I have no idea if that's relevant or not, but my phone has the "google maps 5.7.0 crashes on Defy" issue (18446 in the android issue tracker) and my boyfriend's phone hasn't.
Has anyone encountered this issue before ? I couldn't find anything on this forum or with a google search.
Is there any tool I can use to try and find the cause of the problem ?
Thank you for reading all this, sorry if my message was long but I wanted to give as much detail as possible to help the nice people who may find what is wrong with my phone
I didn't read all..
but if your phone don't have problems then check this:
1. go to settings
2. Select "Location & security settings"
3. enable this "Use wireless networks" Location determined by WiFi and/or mobile networks
4. test does it work...
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Anne-Laure said:
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Click to expand...
Click to collapse
Hello, did you solve the issue?
This thread is about the 3 types of known wifi-roaming bugs, how to differentiate these and fix at least one of them with a little hack.
Documentation of the bug avioded by this workaround on Google: Click Here
BIG NEWS!! As mentioned by a spanish user above there are newer firmwares, that are correcting the wifi-roaming bug, that was fixed by this fix.
Confirmed by an german OTA-Update. So try upgrading your firmware to fix the bug.
But : Keep in mind that an OTA-Update, official from Samsung wont install on a modified system. This includes also our modified wpa-supplicant. So if you want to use a newer firmware you have to restore the old wpa-supplicant: View attachment wpa_supplicant.zip(From The newest Firmware in Germany[OTA-Eplus, JZO54K.I9300XXELL4)
General facts to know about buggy Wifi-Roaming on Android Devices:
Bugs types that are existing
1.The phone never tries to roam by, unless it completely loses signal. Then it connects to the strongest AP. This is the typical Galaxy S2 bug.
2.The phone never tries to roam, and on top of that tries to reconnect to the specific AP that it knows, even if it is right next to a better one while connecting. This has been observed on some Nexus devices, but is apparently fixed on the Galaxy Nexus running CM10.
3.The phone tries to roam as it can see a better AP, but drops the connection and reconnects to the stronger AP shortly after. That's the typical Galaxy S3 and Galaxy Nexus bug, which is fixed by the hack described in this thread.
Only Bug 3 in this list is fixed by this hack. It will not help for the other two bugs!
To determine which bug you are observing, try this:
- Pick two access points that are within range of each other, we will call them AP1 and AP2.
- Locate the phone close to AP1, turn on wifi, and connect to the network. You should get full signal strength.
- Start listening to a web radio stream using e.g. TuneIn Radio (available on Play Store), configure the buffer size to the minimum possible.
- Slowly walk towards AP2, watching the signal strength indicator.
- If you reach AP2 and the phone still shows a low signal strength (at most one bar) after 10-20 seconds:
You are observing a different bug which is not avoided by this workaround.
- Turn off wifi and turn it back on again.
- If the phone now connects to AP2 and shows a high signal strength, you are observing the Galaxy S2 bug --> Bug 1 in the list
- If the phone still connects to AP1 and shows a low signal strength, you are observing the Nexus bug --> Bug 2 in the list
- If the connection drops before getting close enough to AP2, the access points are too far away from each other. -->Retry with a different set of access points.
- If the signal strength seems to increase while getting closer to AP2, but then the wifi icon disappears briefly and comes back after a few seconds, and the web radio stream drops, you are observing the Galaxy S3 bug, and this workaround will help you. --> Bug 3 in the list
- If the signal strength increases while getting closer to AP2, the wifi icon doesn't disappear, and the web radio stream doesn't drop, everything is working normally --> no bug:
-You might have a device that just doesn't have a wifi bug. Apparently such devices indeed exist.
-You might have a Galaxy S3 or Galaxy Nexus, but you were lucky. Try walking back to AP1 and check if it drops the connection this time.
-You might have already applied the workaround above, or a different fix for the same bug. (However there doesn't seem to be one yet.)
______________________________________________________________________________________________________________________
Now as you know which bug your device has you maybe have noticed that your device has bug type 3, here is the hack to fix it:
IMPORTANT: IM NOT RESPONSIBLE FOR NOT WORKING DEVICES AFTER THIS PROCEDURE. INSTALL AT YOUR OWN RISK!! THIS MOD IS EXPERIMENTAL!!
THIS MOD ONLY IS CONFIRMED WORKING FOR THE SAMSUNG GALAXY i9300 AND THE SAMSUNG GALAXY NEXUS i9250
For the installation procedure i give here root rights are needed. It also is recommended to make a CWM-Backup before. If you are unsure about root rights or dont know how to use a Custom Recovery feel free to ask before you do anything.
Installation Instructions for the Standalone-file(no Custom-Recovery needed):
1. Download View attachment Standalone-file.zip and unzip
2. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
3. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
4. Delete the original "wpa_supplicant"-file from the folder
5. Paste the modified "wpa_supplicant"-file downloaded from here in \system\bin. Make sure the file still is named "wpa_supplicant"
6. Reboot your device
Installation Instructions for CWM Flashable-file(CWM-Recovery needed):
1. Download View attachment 1549825
2. Copy the downloaded file to your sdcard.
3. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
4. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
5. Reboot to recovery and flash the downloaded file.
6. Reboot your device.
Your device should now roam correctly from one AP to another.
Please leave your feedback here in the thread and hit the thanks-button if it fixed your problem. ENJOY
FOR ADDITIONAL INFO: Click Here
______________________________________________________________________________________________________________________
Special Thanks to:
- TheSeven, who created this hack
- querty12, who created the flashable CWM-file
- Gabeloooooo, who was the first to give me feedback about this
I hope this leads to a fix. GS3 is garbage when there is more than 1 AP, makes VOIP useless.
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
felixchris said:
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
Click to expand...
Click to collapse
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Gabeloooooo said:
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Click to expand...
Click to collapse
Actually this fix was tested on Stock Rom and Cyanogenmod It works on official Stock Roms as well Just have to be rooted
Tried it, breaks wifi. Can't enable wifi anymore. (i9300 stock 4.1.1)
And oddly enough, restoring the old file back to system\bin doesnt fix it. Will do a couple of tests than will restore from nandroid.
Ok, the reason it didn't work is permissions. Copying using ES explorer did not give the execute permission. Now both files allow me to enable wifi. Will report back on AP roaming after using for a while.
Thanks for your feedback Gabeloooooo
Can you please, after finishing your tests, tell me which permissions you did to set ? as i can mentione it in the instructions
i only tested with root browser...
Used this: rwx r-x r-x
thx will add it to the instructions
Things seem MUCH better with this fix. It is no longer constantly disconnecting. MAJOR IMPROVEMENT!!
I haven't tested groove ip yet, too many bad experiences in the past, but will try it this week to see how it fares.
So maybe if you like the world you could drag it out to the SGS3 - World as i am normally focused on the SGSL- Forums But thanks gor the feedback
Sent from my GT-I9003 using xda app-developers app
Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Click to expand...
Click to collapse
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Click to expand...
Click to collapse
It was tested on this Version and till now they never changed it
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/showpost.php?p=35143039&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2? :fingers-crossed:
felixchris said:
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Click to expand...
Click to collapse
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Jard16 said:
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Click to expand...
Click to collapse
did this fix work on your Nexus 4?
drewski_1 said:
did this fix work on your Nexus 4?
Click to expand...
Click to collapse
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
SGS2 and Nexus4
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/show...9&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2?
Click to expand...
Click to collapse
The SGS2 also had problems with WifiRoaming, but they were different as far as i know. This fix shouldnt work for the Galaxy S2.
Quote:
Originally Posted by drewski_1 View Post
did this fix work on your Nexus 4?
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
Click to expand...
Click to collapse
I dont know of what kind the bug of the Nexus 4 is. So i dont know if it will fix anything. As posted above you can just install it and see if it changes anything Be sure to follow the instructions and BACKUP!!
chhaggerty has compiled a T900 version from source, why this thread is no longer needed and will no longer be maintained.
This is a port of CyanogenMod 12 | P900 made by bonuzzz and Valera1978 and adapted to T900 | Galaxy Tab Pro 12.2 (SM-T900).
Download T900 - cm12 v. 3, T900 - cm12 v. 5, T900 - cm12 v. 6 and an updated Gapps 5.0.x minimal (You choose what to install from Play Store, after flashing).
Flash in TWRP 2.8.0.0 or later. Here is the latest unofficial TWRP-2.8.3.0.img
attn. updated 12/21/2014 For latest versions of the ROM, check TweakerLs' MediaFire folder
His ROM-port is additionally patched with;
- Functioning Cursor
- 5GhZ Wifi channels enabled
- Bluetooth shows as SM-T900
Be patient both at flashing as during first boot it will take a few minutes and the screen will turn Black, just hang on and your device will eventually reboot, and you can enjoy cm12 Lollipop.
It's really nice and smooth. However, it's a pity that Xposed is not yet compatible with Lollipop (ART), why I will most likely stay with a 4.4.4 ROM.
Enjoy,
Thanks! What a great surprise.
Any issues at all? Screen rotation and other things that were an issue in CM11 working in CM12?
omniomi said:
Any issues at all? Screen rotation and other things that were an issue in CM11 working in CM12?
Click to expand...
Click to collapse
This a P-900 port why there will be some incompatibility issues, notably the screen rotation. The alternative is to wait for someone to write it from cm sources and it might take some time.
A guess
I imagine it has the same screen rotation problem that was prevalent on the CM11 version for a while. Might want to check on how it was fixed.
Edit: using it now. Working very well
arcadia2uk said:
This is a port of CyanogenMod 12 | P900 made by bonuzzz and Valera1978 and adapted to T900 | Galaxy Tab Pro 12.2 (SM-T900).
Download T900 version and the updated Gapps
Flash in TWRP 2.8.0.0 or later
Be patient both at flashing as during first boot it will take a few minutes and the screen will turn Black, just hang on and your device will eventually reboot, and you can enjoy cm12 Lollipop.
It's really nice and smooth. However, it's a pity that Xposed is not yet compatible with Lollipop (ART), why I will most likely stay with a 4.4.4 ROM.
Enjoy,
Click to expand...
Click to collapse
Can somebody test this and list all of the working and non-working function of the ROM? That would be awesome.
vi6s said:
Can somebody test this and list all of the working and non-working function of the ROM? That would be awesome.
Click to expand...
Click to collapse
To my knowledge there's only an issue with automatic screen-rotation. However, as I earlier mentioned I don't use Lollipop as I am very fond of Xposed. The fact that that Xposed isn't working, is not a problem with this ROM, but the fact that Android 5.0 is using ART, while Xposed only works with Dalvik.
Running for two days now. I can confirm the following:
- WiFi - Joined multiple networks, no issues
- GPS - locked almost immediately after starting Google Maps
- Cameras - front and back
- Screen Cast (mirroring) - works with my Amazon Fire TV. Interestingly it would fail with the stock Samsung build.
- Hard to quantify, but it feels smoother than Samsung stock. Perhaps the lack of bloatware?
Issues of note:
- As stated by others, auto-rotate doesn't work. Is there a way to force rotation on demand?
- I miss the stock keyboard. I extracted the keyboard APK before flashing, but it fails to install. Lollipop keyboard seems plain in comparison.
- Since this is a port, apps detect this tablet as a P900. However, since specs are so similar to a T900 I doubt this will be an issue.
If anyone wants to test something specific, just ask.
Sent from my SM-T900 using XDA Premium HD app
Nomedias said:
Running for two days now. I can confirm the following:
Issues of note:
- As stated by others, auto-rotate doesn't work. Is there a way to force rotation on demand?
- I miss the stock keyboard. I extracted the keyboard APK before flashing, but it fails to install. Lollipop keyboard seems plain in comparison.
- Since this is a port, apps detect this tablet as a P900. However, since specs are so similar to a T900 I doubt this will be an issue.
Sent from my SM-T900 using XDA Premium HD app
Click to expand...
Click to collapse
- There are a few apps that can force rotation on demand; I like Ultimate Rotation Control, but there is also Set Orientation just to mention a couple.
- Hacker's Keyboard has a lot of the same functionality, and so has A.I type tablet keyboard and a few others.
- The detection as a P900 is just visual and has no impact, other than the stated screen rotation issue. It was just laziness on my part that I didn't change the build.prop to show T900 and v2wifixx, rather than P900 and v1awifi. However, I just uploaded a version 5, with a modded build.prop.
TweakerL said:
I imagine it has the same screen rotation problem that was prevalent on the CM11 version for a while. Might want to check on how it was fixed.
Edit: using it now. Working very well
Click to expand...
Click to collapse
Absolutely correct, it's the same issue and you can consult chhaggerty's github repos to port necessary changes.
I thought having the same name in build.prop lets you auto restore your apps from google play after you wipe and flash a new rom but I could be wrong; anyone know
I use thumb keyboard for my tablet and phone; love it.
A couple of issues.
First let me say that overall I'm impressed with this build. It works quite well for the most part.
I'll just quickly confirm the rotation problem.
Now, a couple of odd problems:
#1 I can't see one of my 5ghz Wi-Fi connections. It's weird because I can see two other 5ghz connections. The one I can't see I can see on my phone, and I've changed several settings on the router to see if that would affect it. I have also killed wpa_supplicant to see if that would get it to show, but no luck.
#2 Bluetooth audio seems to be skipping a lot. I'm not sure exactly what can be done in this aspect, however, because I'm streaming music I suspect that whatever the issue is with the wifi might be the cause for the problem.
Again, overall very solid build.
EDIT: I remember that with the CM11 version, changing the country band configuration for WIFI would solve this problem, however, I don't see that option in CM12. Will look into build.prop.
EDIT2: I changed “ro.WiFi.channels=“ to “ro.WiFi.channels=14“ in build.prop, then rebooted and the missing network popped up. I'm not sure if it was just coincidence but if anyone comes across this problem I'd suggest they try it and report back results. As for my bluetooth streaming problem, as I expected once I was in the better network the problem went away. Now everything seems perfect except for rotation, which doesn't bother me because I already use ultimate rotation control on a regular basis. I haven't tested the IR blaster, but that's hardly something I use.
TweakerL said:
#1 I can't see one of my 5ghz Wi-Fi connections. It's weird because I can see two other 5ghz connections. The one I can't see I can see on my phone, and I've changed several settings on the router to see if that would affect it. I have also killed wpa_supplicant to see if that would get it to show, but no luck.
#2 Bluetooth audio seems to be skipping a lot. I'm not sure exactly what can be done in this aspect, however, because I'm streaming music I suspect that whatever the issue is with the wifi might be the cause for the problem.
Click to expand...
Click to collapse
Higher channels than 11 is normally only used for outside usage (U-NII-3), and is rarely used on standard routers, at least in the US, which is most likely the reason for the setting. I also believe as you suspected that the blue-tooth issues you have experienced is due to this fact. I have no issues at all with the channels, but I believe my routers set-up is channel 6.
Updated to v.6, 2014-12-17 in OP
arcadia2uk said:
Higher channels than 11 is normally only used for outside usage (U-NII-3), and is rarely used on standard routers, at least in the US, which is most likely the reason for the setting. I also believe as you suspected that the blue-tooth issues you have experienced is due to this fact. I have no issues at all with the channels, but I believe my routers set-up is channel 6.
Updated to v.6, 2014-12-17 in OP
Click to expand...
Click to collapse
Is there a change-log for v.6?
Ludespeed said:
Is there a change-log for v.6?
Click to expand...
Click to collapse
No. All info about changes would be in the original post in the P900 version thread.
arcadia2uk said:
No. All info about changes would be in the original post in the P900 version thread.
Click to expand...
Click to collapse
Ok cool; thanks! Still trying decide flashing this or waiting till a sources build
Ludespeed said:
I thought having the same name in build.prop lets you auto restore your apps from google play after you wipe and flash a new rom but I could be wrong; anyone know
I use thumb keyboard for my tablet and phone; love it.
Click to expand...
Click to collapse
I recommend you use Titanium Backup. It restored both apps and the settings. Google Play only restores app, not the settings.
In the us 5 GHz wifi channels are in the 100's range. I had the same issues with my note 10.1 using gnabo rom. It is based on a european build. I had to set my router to channel 48 for the 5 ghz band and it now picks it up loud and clear.
Sent from my SM-T320
I'm in the US and entering the 14 in the line ro.WiFi.channels=14. Didn't allow my 5g channels to show up. Still looking for an answer.?
You have to change the channel on the router. Try 48
Sent from my SM-T320
I have a Huawei P8 Lite since 3 months and one day when I wanted to share my 4G mobile data internet via Hotspot(which I do very frequently) it was not detectable in any other device I have. Also when I turn on WiFi it doesn't show any available connection (while in other devices it does show many).
Another question, considering to make a factory reset, the Huawei Backup system app does it backups apps and app data, like savedata and saved games???
Thank you to everyone in advance!!!
I had the same problem (with wi-fi hotspot) on any Lollipop based firmware (tested Play branded B144, B052, B170) - when moved to Android 6.0 beta - problem stopped occuring.
wolfensg said:
I had the same problem (with wi-fi hotspot) on any Lollipop based firmware (tested Play branded B144, B052, B170) - when moved to Android 6.0 beta - problem stopped occuring.
Click to expand...
Click to collapse
Thank you so very much! I would give more than 1 like if I could!
I'm disturbing you too much I think, but I will ask you for some details:
-The Marshmallow 6.0 BETA Rom it scares me just because of the word "BETA". Is it stable enough? Any big problem? Is it easy after to update to the Final Marshmallow build when it comes out?
-Did you had any problem with WiFi or just with the Hotspot?
-Did you root your phone? I didn't root just because of the possible problems when flashing a Rom or the difficulty of re-locking bootloader.
-About the Huawei Backup app, do you know if it backups the app data/savedata also? And about compatibilities when jumping from Lollipop to Marshmallow?
Thank you and sorry again for disturbing too much! You can answer only to the questions you know.
amarildo.rajta said:
Thank you so very much! I would give more than 1 like if I could!
I'm disturbing you too much I think, but I will ask you for some details:
-The Marshmallow 6.0 BETA Rom it scares me just because of the word "BETA". Is it stable enough? Any big problem? Is it easy after to update to the Final Marshmallow build when it comes out?
-Did you had any problem with WiFi or just with the Hotspot?
-Did you root your phone? I didn't root just because of the possible problems when flashing a Rom or the difficulty of re-locking bootloader.
-About the Huawei Backup app, do you know if it backups the app data/savedata also? And about compatibilities when jumping from Lollipop to Marshmallow?
Thank you and sorry again for disturbing too much! You can answer only to the questions you know.
Click to expand...
Click to collapse
I'm using european 6.0 BETA (ALE-L21C432B524) and have not rooted the phone (I simply don't see any point in rooting at the moment). Xposed framework if working properly maybe could encourage me to root the phone but since EMUI is not 100% AOSP compatible - I don't see a benefit of using Xposed framework as I cannot predict which module will be working properly.
Going back to the 6.0 beta: System is very stable. I did have some problems in the beginning (I did standard upgrade via local update file). The problems were: callendar entries disappearing at random (and then reappearing), some other glitches with UI, etc - but nothing really bothering. All problems were gone since I made factory reset - so I DO RECOMMEND making factory reset after the upgrade.
Also - to be honest - as for the wi-fi hotspot - I needed this as from time to time I'm working from home and I need to set up VPN to my company each time (my internet provider however does not allow me to set up VPN tunnel). That is why I've tested few days ago if wi-fi hotspot option is working now (as I was unable to make it work on previous firmware) and... voila - it works just fine now And I'm able to work from home without issues.
As for the Huawei Backup - I haven't use this one so I cannot tell if the backup will work, etc (I have made the manual backup of all the data files (Music, Pictures,etc) before the wipe and my mobile is connected all the time with the google account so I didn't bother about making any backups of apps/contacts.
Good things I see in this beta:
- much more battery friendly (dual-sim enabled handset with quite a lot of calls is able to be operational for the whole day on a single charge (on Lollipop it was not possible at all)
- contacts and messaging apps are separated (yeah - I did not like that idea of having one app for everything as in Lollipop based EMUI
- contacts and messaging are not a battery hog now (on LP EMUI 3.1 they consumed 30% of battery each day and it was a pain to replace them with something useful as many apps on the google market just does not support properly dual-sim)
- in general the phone is smoother and feels faster
Bad things:
- lockscreen wallpaper seems to be stretched somehow and if you are making a theme of your own (as I am) - you would need to rebuild lockscreen image (fixed in B574!)
- double-tap problem seems to still exist (the problem when typing quite fast on ANY keyboard - you still get double letters, regardles of "gloves modes on/off" or screen protectors, etc, etc - Huawei support which I contacted - also confirm the problem STILL exists... but don't know WHEN it will be adressed... (fixed in B574!)
Neutral things (may be considered bad but seems to be unrelated of this beta and occur also on older firmwares):
- some software seems to be incompatible (but this also applies to LP based EMUI for this phone) - I had problems with starting up ExaGear Strategies (crashes), Winulator (crashes when starting StarCraft (but it seems to be bug with Winulator and ANY android newer than KitKat), fHeroes2 (colorful artifacts when on the "battle" screen, does not occur on map and on title screen - requires running OLDER version of fHeroes2 (downloadable from authors website and not from Google Play) and selecting 24 bpp color and smooth stretching) (problem with fHeroes2 fixed in the latest fHeroes2 update!)
wolfensg said:
I'm using european 6.0 BETA (ALE-L21C432B524) and have not rooted the phone (I simply don't see any point in rooting at the moment). Xposed framework if working properly maybe could encourage me to root the phone but since EMUI is not 100% AOSP compatible - I don't see a benefit of using Xposed framework as I cannot predict which module will be working properly.
Going back to the 6.0 beta: System is very stable. I did have some problems in the beginning (I did standard upgrade via local update file). The problems were: callendar entries disappearing at random (and then reappearing), some other glitches with UI, etc - but nothing really bothering. All problems were gone since I made factory reset - so I DO RECOMMEND making factory reset after the upgrade.
Also - to be honest - as for the wi-fi hotspot - I needed this as from time to time I'm working from home and I need to set up VPN to my company each time (my internet provider however does not allow me to set up VPN tunnel). That is why I've tested few days ago if wi-fi hotspot option is working now (as I was unable to make it work on previous firmware) and... voila - it works just fine now And I'm able to work from home without issues.
As for the Huawei Backup - I haven't use this one so I cannot tell if the backup will work, etc (I have made the manual backup of all the data files (Music, Pictures,etc) before the wipe and my mobile is connected all the time with the google account so I didn't bother about making any backups of apps/contacts.
Good things I see in this beta:
- much more battery friendly (dual-sim enabled handset with quite a lot of calls is able to be operational for the whole day on a single charge (on Lollipop it was not possible at all)
- contacts and messaging apps are separated (yeah - I did not like that idea of having one app for everything as in Lollipop based EMUI
- contacts and messaging are not a battery hog now (on LP EMUI 3.1 they consumed 30% of battery each day and it was a pain to replace them with something useful as many apps on the google market just does not support properly dual-sim)
- in general the phone is smoother and feels faster
Bad things:
- lockscreen wallpaper seems to be stretched somehow and if you are making a theme of your own (as I am) - you would need to rebuild lockscreen image
- double-tap problem seems to still exist (the problem when typing quite fast on ANY keyboard - you still get double letters, regardles of "gloves modes on/off" or screen protectors, etc, etc - Huawei support which I contacted - also confirm the problem STILL exists... but don't know WHEN it will be adressed...
Neutral things (may be considered bad but seems to be unrelated of this beta and occur also on older firmwares):
- some software seems to be incompatible (but this also applies to LP based EMUI for this phone) - I had problems with starting up ExaGear Strategies (crashes), Winulator (crashes when starting StarCraft (but it seems to be bug with Winulator and ANY android newer than KitKat), fHeroes2 (colorful artifacts when on the "battle" screen, does not occur on map and on title screen - requires running OLDER version of fHeroes2 (downloadable from authors website and not from Google Play) and selecting 24 bpp color and smooth stretching).
Click to expand...
Click to collapse
Thank you very much once again! I really appreciate it! I would buy you a beer or a coffee.
The review of the Marshmallow Rom from you is clear and complete, and right too as you use it in work and me I'm just a student. Now I'm considering seriously to jump to the 6.0 BETA, as it looks more STABLE than BETA.
-Talking about the future and a possibly soon Final build of the Rom, do you think the update to that will be problematic or difficult?
-And you didn't had any problem with WiFi or you don't remember?
amarildo.rajta said:
Thank you very much once again! I really appreciate it! I would buy you a beer or a coffee.
The review of the Marshmallow Rom from you is clear and complete, and right too as you use it in work and me I'm just a student. Now I'm considering seriously to jump to the 6.0 BETA, as it looks more STABLE than BETA.
-Talking about the future and a possibly soon Final build of the Rom, do you think the update to that will be problematic or difficult?
-And you didn't had any problem with WiFi or you don't remember?
Click to expand...
Click to collapse
Always happy to help anyone (if only I have some free time)
Ad 1. Since I have no information about the official release it is hard to say.
However I see two options - either it would be possible to simply do the local update to the non-beta version or to do the downgrade to Lollipop (as per the official tool which is already available (you can search the XDA issues) and then do the upgrade again.
Ad 2. I'm constantly using wi-fi at home (due to the poor GSM signal) and I did not see any issues so far (I'm using 6.0 for at least month now).
Ok, small correction
I've tried today for at least an hour to create the Wi-Fi hotspot and it failed on 6.0. I've also tried on my fiances ALE-L21 with the same result - it was working for around 30 seconds :/
Previously I've also tried to work with VPN via Wi-Fi hotspot on this 6.0 but I (unfortunately for me) did not test long enough (just tried to connect and to run few company websites ;/
wolfensg said:
Ok, small correction
I've tried today for at least an hour to create the Wi-Fi hotspot and it failed on 6.0. I've also tried on my fiances ALE-L21 with the same result - it was working for around 30 seconds :/
Previously I've also tried to work with VPN via Wi-Fi hotspot on this 6.0 but I (unfortunately for me) did not test long enough (just tried to connect and to run few company websites ;/
Click to expand...
Click to collapse
Ok then! Anyway I still hope a little bit to succeed fixining that because I haven't been trying to make the Hotspot work with VPN.
Thanks for letting me know!
amarildo.rajta said:
Ok then! Anyway I still hope a little bit to succeed fixining that because I haven't been trying to make the Hotspot work with VPN.
Thanks for letting me know!
Click to expand...
Click to collapse
On the other hand - I am able to set up VPN on the phone and to use VPN environment from it (browsing, etc) but it's not the solution
Im also having this prob please tell the procedure to solve
wolfensg said:
I had the same problem (with wi-fi hotspot) on any Lollipop based firmware (tested Play branded B144, B052, B170) - when moved to Android 6.0 beta - problem stopped occuring.
Click to expand...
Click to collapse
Please tell procedure how to solve
parthis said:
Please tell procedure how to solve
Click to expand...
Click to collapse
Actually... You've quoted my "solution" ... I just upgraded to Android 6.0 (beta build) but also works fine for standard (non-beta) builds. Currently I'm using B574 and works flawlessly.
wolfensg said:
Actually... You've quoted my "solution" ... I just upgraded to Android 6.0 (beta build) but also works fine for standard (non-beta) builds. Currently I'm using B574 and works flawlessly.
Click to expand...
Click to collapse
I tried B574 but it doesnt works its failed now what i do
parthis said:
I tried B574 but it doesnt works its failed now what i do
Click to expand...
Click to collapse
What you may do is to try the following:
- check the compatibility of the device which tries to access the hotspot (you can test by attempting to access the hotspot from another device and vice versa - check this "non working" device by trying to connect to wi-fi via router, another phone's hotspot, etc)
- if the above not working and if you are sure that you are on B574 and you did not make any factory reset after the upgrade - you may try to make factory reset and try afterwards
- you can also try to take the phone to on warranty repair (maybe something is not entirely ok)
As I've mentioned - it is perfectly working for me (I have B574, unmodified stock, without any custom addons and without root), but since it is not working for you - I'd suggest to try the above in the exact order - or maybe someone will come up with another solution.