Related
I recently encountered a weird bug when SGSII would establish wireless "g" connection at 54mbps (instead of regular "n" at 65mbps) when doing 3G to wifi tether on my Lenovo Laptop.
My other 2 laptops work fine as expected, however after doing some troubleshooting, its concluded that the wifi router IP forms a "black hole" hope because of which the external communication to Internet dies after 4 or 5 hops (internal to the ISP). While doing a Trace route, the first hop (the IP of the phone's wireless router - 192.168.43.1) doesn't respond to the trace route ICMP requests and fails, however it does work for the next 4 hops before eventually dying after that.
This proves that wifi connectivity between the phone and laptop remains good despite it being downgraded as "g" network when my laptop is capable of "n" at upto 300mbps.
Never had this issue before KG5 or higher builds and it seems all the custom kernels and ROMs based on these newer kernels are affected.
As this issue is affecting only my Lenovo Laptop, not sure if it was ever reported.
Fortunately I am able to flash kernels based on earlier than KG5 build like Ninphetamine-2.0.x (till 2.0.5).
All Ninphetamine-2.1.x builds and kernels like "RAGEmod v1-T30" are also affected.
I am currently on "TOUCH X-treme KH3 2.0 'PERFORMANCE'" ROM and fortunately it seems to be working fine on Ninphetamine-2.0.5 as per my preliminary testing.
I have 2 more laptops which seems to be working fine otherwise on any latest kernels.
I would appreciate if someone could shed some light on the reason behind this bug as I am still investigating the cause and on a fix other than older kernel versions.
My primary usage of this phone is completely impacted by this bug and I hope Samsung would be able to resolve this bug before their next official release of 2.3.4 or higher version builds.
Hmm like the battery drain while charging bug on SGS1 I seems to be the only person shaken up by this bug which makes my SGS2 completely useless when using the latest kernels/ROMs.
My laptop has Intel WiFi Link 5100 AGN. Can someone having same/similar Wifi adapter report their experience?
Not surprised that Wifi tether is not used by most of us and hence such bugs go unnoticed and I paid a HUGE price of crashing my laptop which trying to fix the issue as I never thought it is the phone doing something weird which is preventing my laptop to get proper wifi connectivity.
Unfortunately no resolution till date. All the latest kernels and ROMs are affected. Not sure what is the issue as it defies logic why only one series of Wifi adapters are affected by this bug.
No resolution till date. All the recent kernels are still affected except the one on CM7 ROM.
Seems I need to wait for this update to become official in India before raising with Samsung here.
Ahhh.. Finally a respite after several MONTHS! The latest Siyah v2.5 kernel (http://forum.xda-developers.com/showthread.php?t=1263838) with new Wifi Driver has restored Internet access through Wireless Tether though the speed is still limited to g instead of regular n at 65mbps. But atleast I can now switch from the good old Ninphetamine-2.0.5 kernel to this latest kernel I always wanted to keep. Such a RELIEF!
No internet
Prankey said:
Ahhh.. Finally a respite after several MONTHS! The latest Siyah v2.5 kernel (http://forum.xda-developers.com/showthread.php?t=1263838) with new Wifi Driver has restored Internet access through Wireless Tether though the speed is still limited to g instead of regular n at 65mbps. But atleast I can now switch from the good old Ninphetamine-2.0.5 kernel to this latest kernel I always wanted to keep. Such a RELIEF!
Click to expand...
Click to collapse
I still get a no internet access notice on my laptop... Any tips?
Fix
leondb said:
I still get a no internet access notice on my laptop... Any tips?
Click to expand...
Click to collapse
Downloaded the newest beta from their website and installed. Then chose my device, and I am happy to report it is now working
leondb said:
Downloaded the newest beta from their website and installed. Then chose my device, and I am happy to report it is now working
Click to expand...
Click to collapse
I have faced the similar problem. But how my problem was solved is give below:
Update you windows OS using windows update
Then manually switch off the radios and switch on
That's all and now I can use wifi tethering as normal. First check with second option, if doesn't work, then try updating the PC OS too.
grgsiocl said:
I have faced the similar problem. But how my problem was solved is give below:
Update you windows OS using windows update
Then manually switch off the radios and switch on
That's all and now I can use wifi tethering as normal. First check with second option, if doesn't work, then try updating the PC OS too.
Click to expand...
Click to collapse
Latest Siyah 2.6.x kernels have AGAIN brought back the bug on my face!
None of the other options you suggested worked. I have spent hours trying to figure it out and this is what I get when I am affected:
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 * * * Request timed out.
2 164 ms 123 ms 127 ms 218.248.84.5
3 228 ms 68 ms 81 ms 10.42.43.101
4 79 ms 79 ms 80 ms 10.42.43.28
5 * * * Request timed out.
Doesn't make ANY sense on how the first hop is getting blackholed when it otherwise respond to ping requests. I am able to reach till the last hop of ISP before dropping off.
Can any network gurus out here explain this phenomenon? I am unable to locate any logic behind it.
Hope Siyah team fixes it soon for me to enjoy a glimpse of Voodoo Sound on my SGS2.
I have a Lenovo T520 and am using the KK2 stock firmware/rom with no problem whatsoever in tethering...using it at this very moment
It actually seems to be affecting only Intel 5100 adapters like on my R400. I have 3 other laptops and a mobile phone which are working fine otherwise
As I said, it defies logic why only this adapter has compatibility issue when even older Intel 39xx based adapters work perfectly fine otherwise.
Fixed in Siyah 2.6.2 kernel again
Finally got it fixed on Siyah 2.6.2 kernel (to be released shortly) while working directly with the dev "gokhanmoral" in the past few days. All seems to be working now like it was in 2.5.x builds for me.
I sincerely thank gokhanmoral for taking the pain of looking at this isolated bug by Samsung which has fortunately been resolved on the latest drivers (to an extend, still no n mode access).
So I've searched all around these forums and I've yet to find someone who has the same situation as me. So I recently got a brand new Nexus 4 on T-Mobile, and right now it has CM 10.2-20131011-NIGHTLY-mako ROM installed. Although I am on a prepaid no-tether plan, I am able to tether anyway through USB or Bluetooth with no limitations (tested through a Mac and other mobile devices). However, whenever I try to tether through Wifi, in the "Tethering & portable hotspot" menu in Settings, when I try to check "Portable Wi-Fi hotspot", it turns on for a second, then turns back off (unchecked) and says "error" under portable wi-fi hotspot. It doesn't allow me to try to turn it on again because the option becomes greyed out and unselectable. Also, my wifi refuses to turn back on, like the phone still thinks it's tethering. The only fix to my wifi is a simple reboot and everything's back to normal.
TL;DR, Tethering works except through wifi, and attempting wifi tethering breaks wifi altogether. Any fixes/solutions?
solution.. try a different rom. i believe cm broke it for the time being.
simms22 said:
solution.. try a different rom. i believe cm broke it for the time being.
Click to expand...
Click to collapse
Wifi tethering worked just fine on my old Verizon Galaxy Nexus, same nightly ROM too (I literally just got the Nexus 4 today).
keemer1028 said:
Wifi tethering worked just fine on my old Verizon Galaxy Nexus, same nightly ROM too (I literally just got the Nexus 4 today).
Click to expand...
Click to collapse
2 different phones with different modules, with varying codes.. wifi tethering works perfect on stock and on aosp based roms. cm isnt stock nor aosp based anymore.
Which AOSP-based ROM would you prefer? I don't prefer stock compared to the amount of customization one can get from these various ROMs out there. Is AOKP or Paranoid Android AOSP-based?
simms22 said:
2 different phones with different modules, with varying codes.. wifi tethering works perfect on stock and on aosp based roms. cm isnt stock nor aosp based anymore.
Click to expand...
Click to collapse
Which AOSP-based ROM would you prefer? I don't prefer stock compared to the amount of customization one can get from these various ROMs out there. Is AOKP or Paranoid Android AOSP-based?
keemer1028 said:
Which AOSP-based ROM would you prefer? I don't prefer stock compared to the amount of customization one can get from these various ROMs out there. Is AOKP or Paranoid Android AOSP-based?
Click to expand...
Click to collapse
yes, they are aosp based now. when cm changed their source from aosp to qualcomm a few weeks ago, and custom kernels stopped working fully on cm, many cm based roms switched their bases to aosp. personally, i prefer rasbean
simms22 said:
2 different phones with different modules, with varying codes.. wifi tethering works perfect on stock and on aosp based roms. cm isnt stock nor aosp based anymore.
Click to expand...
Click to collapse
Tethering works here and I am running cm 10.1.2
Sent from the Far Reaches Of The Earth! now Free
help @keemer1028 getting it going, i dont run cm.
Berrydroidcafe said:
Tethering works here and I am running cm 10.1.2
Sent from the Far Reaches Of The Earth! now Free
Click to expand...
Click to collapse
simms22 said:
help @keemer1028 getting it going, i dont run cm.
Click to expand...
Click to collapse
It was implied that tethering didn't work with cm, hence the statement.
Sent from the Far Reaches Of The Earth! now Free
Berrydroidcafe said:
It was implied that tethering didn't work with cm, hence the statement.
Sent from the Far Reaches Of The Earth! now Free
Click to expand...
Click to collapse
i missed the 1 in cm 10.1.2
Berrydroidcafe said:
Tethering works here and I am running cm 10.1.2
Click to expand...
Click to collapse
I did a clean wipe and flashed back to the Oct. 2 nightly CM 10.2 and wifi tethering works, then when I flashed the latest nightly wifi tethering was broken again. I've come to the conclusion that maybe it's just the recent nightly build and the CM team hasn't fixed it yet.
keemer1028 said:
So I've searched all around these forums and I've yet to find someone who has the same situation as me. So I recently got a brand new Nexus 4 on T-Mobile, and right now it has CM 10.2-20131011-NIGHTLY-mako ROM installed. Although I am on a prepaid no-tether plan, I am able to tether anyway through USB or Bluetooth with no limitations (tested through a Mac and other mobile devices). However, whenever I try to tether through Wifi, in the "Tethering & portable hotspot" menu in Settings, when I try to check "Portable Wi-Fi hotspot", it turns on for a second, then turns back off (unchecked) and says "error" under portable wi-fi hotspot. It doesn't allow me to try to turn it on again because the option becomes greyed out and unselectable. Also, my wifi refuses to turn back on, like the phone still thinks it's tethering. The only fix to my wifi is a simple reboot and everything's back to normal.
TL;DR, Tethering works except through wifi, and attempting wifi tethering breaks wifi altogether. Any fixes/solutions?
Click to expand...
Click to collapse
I have the exact same situation with my HTX One XL AT&T with CM 10.2-20131014-NIGHTLY. I hope this gets fixed soon.
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.
Hi, I have a problem with mi redmi note 7 (lavender)
the problem is that the wifi gets disconnected at some distance (something normal from redmi note 7) the real problem is that it doesn't reconnect, even if i have the router with me, in the lower area of the wifi it shows the message "saved" i try to forget the network and reset the password but i still can't connect, I have to restart the phone to be able to connect normally, but after a while the problem returns.
I'm using a custom rom called AOSIP with android 10, I have already used pixel experience, Crdroid, Evolution x, Havoc os and absolutely, all have the same problem. I want to make it clear that I have already used android 10 on my redmi note 7 (pixel experience) and I didn't have any problems, the problem started after the February updates this year.
I don't think it's a hardware problem because going back to miui or a custom rom with android 9 solves the problem.
I would like to know if you already know about this subject or if you are already working on it or if there is a solution.
thanks
here are some links of the captures I made
https://drive.google.com/file/d/1TEPKK4GGpW8QlM9xzb3FidWZQhxVJZw2/view[/IMG]
https://drive.google.com/file/d/1xAWkt_PYIUnaHLcE2RC-mDaBJYgCq-zE/view[/IMG]
I think you might be onto something. In my case, the problem has been with Wifi Tethering. The phone is basically unusable as a hotspot, cutting out frequently and randomly and I think this has something to do with your wifi problem, maybe a driver issue? Like yourself, I've tried several aosp roms, all have the same problem.
Do you recall the last Pixel Experience release without this wifi issue? I am considering rolling back...
darkhandsome18 said:
I think you might be onto something. In my case, the problem has been with Wifi Tethering. The phone is basically unusable as a hotspot, cutting out frequently and randomly and I think this has something to do with your wifi problem, maybe a driver issue? Like yourself, I've tried several aosp roms, all have the same problem.
Do you recall the last Pixel Experience release without this wifi issue? I am considering rolling back...
Click to expand...
Click to collapse
Good morning, I've already tried the most recent version of pixel experience, in fact the AOSIP rom is from May 17, 2020, practically yesterday.
Obviously it's a driver problem, but I don't understand why all custom roms have the same problem and I don't know how to solve it either (in android 10)
darkhandsome18 said:
I think you might be onto something. In my case, the problem has been with Wifi Tethering. The phone is basically unusable as a hotspot, cutting out frequently and randomly and I think this has something to do with your wifi problem, maybe a driver issue? Like yourself, I've tried several aosp roms, all have the same problem.
Do you recall the last Pixel Experience release without this wifi issue? I am considering rolling back...
Click to expand...
Click to collapse
Could you tell me what rom are you currently using?
Could you also tell me the release date of the rom?
Brxyan said:
Could you tell me what rom are you currently using?
Could you also tell me the release date of the rom?
Click to expand...
Click to collapse
Currently on StagOS May 11 build. I settled on that after trying Pixel Ex, Evolution, etc as it was the one with the least hotspot issues; which isn't saying much as tethered devices would randomly lose internet connection while the phone clearly had internet and you could browse on any browser on the phone.
Since you say the issue occurred for you after the February updates, maybe you could point me to the last stable build you used so I can roll back.
darkhandsome18 said:
Currently on StagOS May 11 build. I settled on that after trying Pixel Ex, Evolution, etc as it was the one with the least hotspot issues; which isn't saying much as tethered devices would randomly lose internet connection while the phone clearly had internet and you could browse on any browser on the phone.
Since you say the issue occurred for you after the February updates, maybe you could point me to the last stable build you used so I can roll back.
Click to expand...
Click to collapse
I recommend all the versions that are from February, I would like to use pixel experience from that date but the page only has recent versions.
if you want a specific version use Crdroid 20200209
crdroid if you keep your old versions in the cloud so I recommend it, but I can not guarantee that it is totally stable. Pixel experience if stable but they don't have the versions of those dates.
darkhandsome18 said:
Currently on StagOS May 11 build. I settled on that after trying Pixel Ex, Evolution, etc as it was the one with the least hotspot issues; which isn't saying much as tethered devices would randomly lose internet connection while the phone clearly had internet and you could browse on any browser on the phone.
Since you say the issue occurred for you after the February updates, maybe you could point me to the last stable build you used so I can roll back.
Click to expand...
Click to collapse
I would like you to install the most recent version of pixel experience and when configuring the wifi, you will move away from the router until the signal goes away and try to connect again, just to check if it is really my phone or not.
Obviously making a backup before and also doing all this is optional. If you don't want to do it there is no problem thanks.
Brxyan said:
I would like you to install the most recent version of pixel experience and when configuring the wifi, you will move away from the router until the signal goes away and try to connect again, just to check if it is really my phone or not.
Obviously making a backup before and also doing all this is optional. If you don't want to do it there is no problem thanks.
Click to expand...
Click to collapse
I already tried StagOs, I still have the same problem with the wifi, I also tried the hotspot and as you say if there is a data problem and in general it is unstable.
I downloaded the latest version of pixel experience and as expected the wifi was still failing, but the hotspot was working correctly so you can install it without any problem.
Brxyan said:
I already tried StagOs, I still have the same problem with the wifi, I also tried the hotspot and as you say if there is a data problem and in general it is unstable.
I downloaded the latest version of pixel experience and as expected the wifi was still failing, but the hotspot was working correctly so you can install it without any problem.
Click to expand...
Click to collapse
Okay sorry for the delay, been busy experimenting. Your recommendation of the Feb 09 crdroid build was spot on, flashed it, wifi and hotspot works like a dream, no issues at all.
After confirming that I decided to take a backup and try a recent AOSP build. I had already tried the Pixel Ex May 11 build and had the same issues so I downloaded the most recent build of Evolution X (May 17) and flashed.
So far, (Fingers crossed) I have not been able to replicate your WiFi issues or my tethering issues. WiFi did not disconnect even at a distance of over 50ft from the router. Keep in mind that these connection issues occur randomly but there's been nothing so far.
I will continue to use this build and test for the rest of the day. If I experience any dropouts I will restore to the stable crdroid build. Maybe you should try the newest evolution or go back to the stable crdroid to test if the issues are software related or specific to your device.
At this point I've been testing the latest build of Evolution (May 17) for about half a day, and zero problems so far, very stable.
I recommend you try it, may fix your wifi issues.
darkhandsome18 said:
Okay sorry for the delay, been busy experimenting. Your recommendation of the Feb 09 crdroid build was spot on, flashed it, wifi and hotspot works like a dream, no issues at all.
After confirming that I decided to take a backup and try a recent AOSP build. I had already tried the Pixel Ex May 11 build and had the same issues so I downloaded the most recent build of Evolution X (May 17) and flashed.
So far, (Fingers crossed) I have not been able to replicate your WiFi issues or my tethering issues. WiFi did not disconnect even at a distance of over 50ft from the router. Keep in mind that these connection issues occur randomly but there's been nothing so far.
I will continue to use this build and test for the rest of the day. If I experience any dropouts I will restore to the stable crdroid build. Maybe you should try the newest evolution or go back to the stable crdroid to test if the issues are software related or specific to your device.
Click to expand...
Click to collapse
I am very happy that I found a solution to your problem, then I made some tests by creating an access point with my sister's phone ( xiaomi mi a1 ) and I performed the distance test and my phone connected normally. After several tests I am reaching a preliminary conclusion that there is an incompatibility with my router, I would need more tests with another router to conclude that my router is practically obsolete. That would also explain why I haven't found another thread with this same problem
good luck, tell me if you have finally solved your problem