Official Android M Discussion Thread
- Thread starter taino211
- Start date
S
siddlv
Guest
As if 10 hours is long enough to know.
That said, it's fixed in 5.1.1 so you would expect it to be fixed in M too.
" Gone back to the basics "
" Polish and quality "
“literally solved thousands of bugs.”
Flashlight bug/Camera bug still exists on M, Nice one Google. :good:
In fact the flashlight/camera bug existed on the L Dev preview - 5.0, 5.0.1, 5.1, 5.1.1 and now Dev Preview M
" Polish and quality "
“literally solved thousands of bugs.”
Flashlight bug/Camera bug still exists on M, Nice one Google. :good:
In fact the flashlight/camera bug existed on the L Dev preview - 5.0, 5.0.1, 5.1, 5.1.1 and now Dev Preview M
Last edited:
Anyone have an issue where the typing sound cuts in and out if typing fast?
Sent from my Nexus 5 using XDA Free mobile app
Sent from my Nexus 5 using XDA Free mobile app
I can't see my phone when I connect it to PC to transfer my images and music, it just charges. Tried to get USB tethering, it states, that USB is not connected. Any ideas?
EDIT: Nevermind, found the problem. USB was set to PTP by default, and my pc is on Linux. Searched in settings for USB, found the USB toggle mode, set it ot MTP and all is well with the world
EDIT: Nevermind, found the problem. USB was set to PTP by default, and my pc is on Linux. Searched in settings for USB, found the USB toggle mode, set it ot MTP and all is well with the world
Last edited:
Hi
There is a new DHCP client in use in Android M. If you hit upon an issue where the Wi-Fi connects then immediately disconnects due to no Internet access (where it worked fine on L), the reason is likely a change to the DHCP client.
Either the DHCP client is only setting a primary DNS server, or some code that checks for internet access does not try the back-up DNS server if the primary fails. In my case, the primary DNS server wasn't working, however all other PCs and Android L happily used the back-up (the reason we normally have a back-up), hence I was unaware. On Android M because the primary DNS server didn't work, it decided there was no Internet access.
I can see this tripping some people up so thought I'd mention it. Options are to try and use the original DHCP client (option in the Developer menu) or if you have access to the Wi-Fi/router check the primary DNS server IP address.
Regards
Phil
There is a new DHCP client in use in Android M. If you hit upon an issue where the Wi-Fi connects then immediately disconnects due to no Internet access (where it worked fine on L), the reason is likely a change to the DHCP client.
Either the DHCP client is only setting a primary DNS server, or some code that checks for internet access does not try the back-up DNS server if the primary fails. In my case, the primary DNS server wasn't working, however all other PCs and Android L happily used the back-up (the reason we normally have a back-up), hence I was unaware. On Android M because the primary DNS server didn't work, it decided there was no Internet access.
I can see this tripping some people up so thought I'd mention it. Options are to try and use the original DHCP client (option in the Developer menu) or if you have access to the Wi-Fi/router check the primary DNS server IP address.
Regards
Phil
Seems to work for me - I went through disabling a bunch of stuff. A surprising number of apps wanted telephone access and for some reason the nest app wanted access to my camera...
Quinny899
Recognized Developer / Recognized Contributor
I wrote a guide on enabling multi-window here:
http://xdaforums.com/android/general/guide-enable-multi-window-mode-android-t3121483
http://xdaforums.com/android/general/guide-enable-multi-window-mode-android-t3121483
Can someone tell me if I did it right? been waiting 40mins now for this to boot.
turn phone to fastboot
connect to pc
open cmd
fastboot bootloader, radio,system,userdata,boot,recovery then erase cache
go to recovery mode using volume down then when see android logo, press volume up and power button(which looping) turned it on then 40mins wait
turn phone to fastboot
connect to pc
open cmd
fastboot bootloader, radio,system,userdata,boot,recovery then erase cache
go to recovery mode using volume down then when see android logo, press volume up and power button(which looping) turned it on then 40mins wait
Not yet, Chainfire (SuperSU developer) is still working on it. We might get it at weekend or around next week.
S
siddlv
Guest
What? You can't go in Stock recovery?Can someone tell me if I did it right? been waiting 40mins now for this to boot.
turn phone to fastboot
connect to pc
open cmd
fastboot bootloader, radio,system,userdata,boot,recovery then erase cache
go to recovery mode using volume down then when see android logo, press volume up and power button(which looping) turned it on then 40mins wait
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
96I wrote a guide on enabling multi-window here:
http://xdaforums.com/android/general/guide-enable-multi-window-mode-android-t312148354Hi
There is a new DHCP client in use in Android M. If you hit upon an issue where the Wi-Fi connects then immediately disconnects due to no Internet access (where it worked fine on L), the reason is likely a change to the DHCP client.
Either the DHCP client is only setting a primary DNS server, or some code that checks for internet access does not try the back-up DNS server if the primary fails. In my case, the primary DNS server wasn't working, however all other PCs and Android L happily used the back-up (the reason we normally have a back-up), hence I was unaware. On Android M because the primary DNS server didn't work, it decided there was no Internet access.
I can see this tripping some people up so thought I'd mention it. Options are to try and use the original DHCP client (option in the Developer menu) or if you have access to the Wi-Fi/router check the primary DNS server IP address.
Regards
Phil
