Related
I'm sure I'll hear differing opinions, but I see big show stoppers here. I've gone back to 3.1 already.
I've tried stock, custom, different kernels, and from what I can see it all points to that version of Android, not any particular customizations.
1. Dropped wifi connections - I'm not the only one
2. Something a bit more obscure:
The latest version of the email client does not allow you to set the port for your incoming mail server. While most folks wouldn't care or even notice, this is something that I require and has been an option available on 3.0 and 3.1.
3. Streaming Flash videos seem to just lock up on you at random times.
Realky piss poor job, Acer/Google! Ever hear of Quality Assurance, or are we your testers?
Sent from my A500 using xda premium
I dont have and never had and dont believe I ever will have any Wifi problems whatsover.
The email thing I do not know but you should email Acer about this.
bleez99 said:
I'm sure I'll hear differing opinions, but I see big show stoppers here. I've gone back to 3.1 already.
I've tried stock, custom, different kernels, and from what I can see it all points to that version of Android, not any particular customizations.
1. Dropped wifi connections - I'm not the only one
2. Something a bit more obscure:
The latest version of the email client does not allow you to set the port for your incoming mail server. While most folks wouldn't care or even notice, this is something that I require and has been an option available on 3.0 and 3.1.
3. Streaming Flash videos seem to just lock up on you at random times.
Realky piss poor job, Acer/Google! Ever hear of Quality Assurance, or are we your testers?
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Two things:
1. Seeing that you have gone back to 3.1 indicates that you haven't used the ROM provided by Acer but by one of the developers here. So maybe the problems you are seeing with wifi might not be result of Acer/Google's work. Correct me if I'm wrong but the new recovery can't be downgraded (still).
2. Have you tried to set the port in the name of the server? Like mail.provider.com:25 ? I'm waiting for root for 3.2 before I update because after months of flashing my phone I came to the conclusion that stock is aways the best option when stability is a must. Maybe when Acer discontinues supporting the A500, custom ROMs will be the better option, but surely not now (in the mean time you have to be sure not to flash a unrootable recovery). Having said that, I don't know if setting the port in the server name would work but definitely worth a try.
Sent from my A500 using XDA Premium App
Sounds like you might have just gotten a bad model. I would return it for a different one.
tkolev said:
Two things:
1. Seeing that you have gone back to 3.1 indicates that you haven't used the ROM provided by Acer but by one of the developers here. So maybe the problems you are seeing with wifi might not be result of Acer/Google's work. Correct me if I'm wrong but the new recovery can't be downgraded (still).
2. Have you tried to set the port in the name of the server? Like mail.provider.com:25 ? I'm waiting for root for 3.2 before I update because after months of flashing my phone I came to the conclusion that stock is aways the best option when stability is a must. Maybe when Acer discontinues supporting the A500, custom ROMs will be the better option, but surely not now (in the mean time you have to be sure not to flash a unrootable recovery). Having said that, I don't know if setting the port in the server name would work but definitely worth a try.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
What does recovery have to do with this?
Before writing my post, I did try a stock 3.2 from Acer. Nothing to do with custom or stock. I started with stock 3.0, just like most people here.
When I saw the port number issue, I went to Acer's servers, downloaded 3.2, and the it was, a missingport number inputbarea. Still there for outgoing servers.
I've been around the block a few times. I'm no newbie when it comes to technology, and I won't brag about what I do for a living.
As soon as you enter mail.somewhere.com:6799 or whatever your favorite port numer is, the Next button becoms greyed out. Just typing the colon after the server name does the trick, you don'even have to go as far as the port number. In the pervios versions of Email, there is an input box for the port number, it's gone missing.
The problem with wifi has been reported by users of 3.2 in general, meaning Asus and other brands as well. I did do some poking around on here on xda.
Sent from my A500 using xda premium
claytonmedic said:
Sounds like you might have just gotten a bad model. I would return it for a different one.
Click to expand...
Click to collapse
Nah, I doubt it's bad, and I got my A500 in May, the day it hit the shelves. This is not a defective unit. The software is defective.
Sent from my A500 using xda premium
Johnny0906 said:
I dont have and never had and dont believe I ever will have any Wifi problems whatsover.
The email thing I do not know but you should email Acer about this.
Click to expand...
Click to collapse
"My wifi is fine" - I hear that from a lot of people. Mine isn't. Ohters are complaining about this as well. Acer's support claims it's the router. Oh, come on, Acer. I have a couple of routers here, servicing FreeBSD systems, Mac OS X systems, iPhones, whatever a guest to my home might bring over, and gasp - Windows systems. It's not my router(s). And the fact that 3.0 and 3.1 work just fine, custom or stock, throws up a big red flag to me.
Emailing Acer support, or calling them for that matter, is the same as emailing or calling a brick wall.
Sent from my A500 using xda premium
tkolev said:
Two things:
1. Seeing that you have gone back to 3.1 indicates that you haven't used the ROM provided by Acer but by one of the developers here. So maybe the problems you are seeing with wifi might not be result of Acer/Google's work. Correct me if I'm wrong but the new recovery can't be downgraded (still).
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
Do you work for Acer? From what I've seen from the devs here, they do a better job than Acer would ever care to do.
I use CWM for recovery, it really does nothing but facilitate the switching of ROMs and doing a backup.
Sent from my A500 using xda premium
bleez99 said:
I'm sure I'll hear differing opinions, but I see big show stoppers here. I've gone back to 3.1 already.
I've tried stock, custom, different kernels, and from what I can see it all points to that version of Android, not any particular customizations.
1. Dropped wifi connections - I'm not the only one
2. Something a bit more obscure:
The latest version of the email client does not allow you to set the port for your incoming mail server. While most folks wouldn't care or even notice, this is something that I require and has been an option available on 3.0 and 3.1.
3. Streaming Flash videos seem to just lock up on you at random times.
Realky piss poor job, Acer/Google! Ever hear of Quality Assurance, or are we your testers?
Sent from my A500 using xda premium
Click to expand...
Click to collapse
The fact that you reverted back to 3.1 means you never had stock 3.2, but the buggy 3.2 that was made off the 501 3.2 with its problems.
Well I must have a good router I don't have issues with my wifi, may I ask what sheadule did you use for kernel in setcpu, I had abrather laggy experience until I changed it to userspace
Sent from my A500 using xda premium
Is there a commonality in type of encryption used with wifi issues?
bleez99 said:
I'm sure I'll hear differing opinions, but I see big show stoppers here. I've gone back to 3.1 already.
I've tried stock, custom, different kernels, and from what I can see it all points to that version of Android, not any particular customizations.
1. Dropped wifi connections - I'm not the only one
2. Something a bit more obscure:
The latest version of the email client does not allow you to set the port for your incoming mail server. While most folks wouldn't care or even notice, this is something that I require and has been an option available on 3.0 and 3.1.
3. Streaming Flash videos seem to just lock up on you at random times.
Realky piss poor job, Acer/Google! Ever hear of Quality Assurance, or are we your testers?
Sent from my A500 using xda premium
Click to expand...
Click to collapse
The fact that you reverted back to 3.1 means you never had stock 3.2, but the buggy 3.2 that was made off the 501 3.2 with its problems.
I for one have really never had a problem to ***** about. If you don't like the product you bought with Android then you must be looking for an excuse to go to the other side.
HoneyVillain ROM as stated below has run perfect. I'm not a dev, just know how to read and follow directions.
Sent from my Acer Iconia A500 running HoneyVillain 1.1 HC 3.2 for A501, OC'd 1.5GHz
shaun298 said:
The fact that you reverted back to 3.1 means you never had stock 3.2, but the buggy 3.2 that was made off the 501 3.2 with its problems.
Click to expand...
Click to collapse
I can second this: If you'd used 3.2 from Acer, you'd be stuck with it. Right now it locks you in and you can't downgrade. Really douche move from Acer, if you ask me. It's this kind of crap that you would expect from Mac.
As for your wifi issues, it might be a faulty unit like others have said, but I doubt it. I know the radio on mine is rather week (can't go more than 20 feet from the router). The GPS is also weak (only works on sunny days) with a low SNR even then. I suspect these two transmitters are underpowered on mine. I was an early adopter and I noticed that Acer had refurb units out only a few weeks after the initial release. This usually means they had many many returns. This is never a good sign.
The good news is that it is likely not a hardware thing in your case. If it worked better with 3.1, then you know that your transmitter is at least capable of a solid connection. If you don't mind losing root, try the OTA update. Keep in mind this is a one-way trip.
Otherwise, just stick with 3.1 until ICS comes out in a few months. 3.2 really is nothing spectacular; i wouldn't recommend upgrading unless it specifically fixes something you need.
Cheers,
-PW
shaun298 said:
the fact that you reverted back to 3.1 means you never had stock 3.2, but the buggy 3.2 that was made off the 501 3.2 with its problems.
Click to expand...
Click to collapse
+1.
Wifi Issues
As someone who has had the occasional wifi issues and been trying to hunt it down, I can say it almost always has to do with the AP, regardless of whether or not other devices have issues. I have about 8 different APs at my house that I have used to test across a wide variety of manufacturers. The biggest issues I have seen are tied to WPA2-PSK AES/TKIP support, and pre-N support. If the device is set to support both AES and TKIP I have seen issues. Set it to either one, it's fine. N has had major issues as well. Any AP I have tried that is Pre-N gives issues. Anything after the standard has been ratified has not had issue. It's not just A500 that I've noticed this behavior. I have a Moto Defy that acts the same way as well Smartbook. If you crank the support down to G only the issues disappears. Ironically the only device that I have had 0 issues with is my roommates Apple AP........go figure the irony on that.
---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------
Also as far as 3.2 goes.....I've noticed the only people that are getting the 3.2 update are the ones with Gen1 devices. I have a Gen2 and have seen nothing. Maybe there was a slight hardware revision?
I had really some problems after updating the device but after doing a factory reset all problems vanish.
There aren't different hardware gen versions by software update. The use of "gen" in the rom/update name appears to merely be some sort of codeword for acer and acer only.
Check out this post to see the original code lines for 3.1..
http://forum.xda-developers.com/showpost.php?p=16061585&postcount=3
Updated it to reflect the various 3.2 roms that have popped to upgrade from 3.1. I still have not seen one for the US rom line that was up to Acer_A500_4.010.13_COM_GEN2.
Originally the US rom line was gen1 prior to 3.1.
If anyone was on 4.010.13 and got the update could you please post your software versions?
There is a version of 3.2 posted in the dev section that is the best bet for those wanting to try it out before a userland root exploit is figured out. It's version A500_4.010.41_7.006.01_COM_GEN1. The only thing done to this otherwise stock rom is root, custom recovery (CWM), busybox, and the new bootloader removed. This rom is ready to go and flashable from CWM which means no need to unroot and revert recoveries.
http://forum.xda-developers.com/showthread.php?t=1265847
We need to have a DEV work on the other codetrain versions that exist to have a similar rom posted for each section of the world.
bleez99 said:
Do you work for Acer? From what I've seen from the devs here, they do a better job than Acer would ever care to do.
I use CWM for recovery, it really does nothing but facilitate the switching of ROMs and doing a backup.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
No, I don't. That's my honest opinion and I stand by my words. The devs here do outstanding job considering they don't have the resources the manufacturers have. But at the end of the day, custom roms just lack proper testing. They do bring more features but if you read carefully what I have written in my post, I said they are inferior in terms of stability not features.
EDIT: If you have gone back to 3.1 you did NOT update with the stock ROM. Period. At best you updated with a near-stock ROM (with removed recovery, added superuser app, busybox and God knows what else) and in the process you should have wiped cache, etc. You are the only one who knows what you have done in the process and that's exactly why manufacturers void warranties on rooted/custom recovery devices. There are many with wifi problems you say, well there are also many that don't have them. The only way we could know if those problems are caused by Acer or by the users is to have someone that had stock unrooted 3.1 working who updated OTA with the stock 3.2 provided by Acer and started having wifi issues. Not someone who flashes every other day something cooked by anyone but Acer.
Sent from my A500 using XDA Premium App
Please delete this post.
So since my N7 doesn't have WAN connectivity, I'm trying to play with any/all apps that take advantage of anything wireless. I know there's the standard NFC, BT, WiFi apps, but I recently learned of this new thing called WiFi Direct. Does anyone know of any apps that use this new technology? I came across one which I posted about here, which I thought was really cool so i'm looking for other apps that use this kind of wireless P2P connectivity. Anyone know of anything else besides Tapestry?
whatisreal7 said:
So since my N7 doesn't have WAN connectivity, I'm trying to play with any/all apps that take advantage of anything wireless. I know there's the standard NFC, BT, WiFi apps, but I recently learned of this new thing called WiFi Direct. Does anyone know of any apps that use this new technology? I came across one which I posted about here, which I thought was really cool so i'm looking for other apps that use this kind of wireless P2P connectivity. Anyone know of anything else besides Tapestry?
Click to expand...
Click to collapse
Nothing? There's really only one app in the Android world that uses WiFi Direct? Either these guys are onto something or they're screwed!
Wi-Fi Direct is just beginning to get places, it seems. I know it's a feature that Miracast will utilize when it comes out in a few months, and most of "smart"/wifi tvs will be compatible with it.
But who knows?
-Ara
WiFi Direct is already supported in many connected TV's today...its just that CE companies do a poor job productizing it, and advertising it.
if you want to connect from android device to android device for transmitting media, check this one:
https://play.google.com/store/apps/details?id=com.budius.WiFiShoot
different from tapstry (that is a presentation app) WiFi Shoot is a direct share app, and works with ICS.
this was developed by yours truly, and I developed it exactly because I noticed there was nothing out there for WiFi Direct
I tested it between Nexus 7, Galaxy Nexus, Asus TF300 and Galaxy SII (stock ICS) and all worked fine.
The most problematic of those were the Galaxy Nexus that not always want to connect, but between N7-GalaxySII was flawless.
At the moment the app just works for photo and video but I'll be expanding more, if you guys fancy helping spreading the word about it, I'm really looking forward to see the downloads explode on it.
Hi guys,
is anyone with interested in beta test my WiFi Direct app?
I started a new thread in the development section asking for Logcats if you're experiencing force close.
Also it's a cut down version of the .apk there to test part of the system.
http://forum.xda-developers.com/showthread.php?p=30012554
any help will be great appreciated.
thanks.
Budius said:
Hi guys,
is anyone with interested in beta test my WiFi Direct app?
I started a new thread in the development section asking for Logcats if you're experiencing force close.
Also it's a cut down version of the .apk there to test part of the system.
http://forum.xda-developers.com/showthread.php?p=30012554
any help will be great appreciated.
thanks.
Click to expand...
Click to collapse
can't wait to be able to share files, I like sideloading apk "not compatible" to my other devices and it's a pain uploading/downloading to device and sometimes the network is slow, so it's a hassle. hope this solves it, I have 5 devices I am testing this app currently.
WinDroidGuy said:
I have 5 devices I am testing this app currently.
Click to expand...
Click to collapse
Please post force closes or problems on the beta test tread.
Sent from my Nexus 7 using xda app-developers app
I think it's great that there are many choices for custom roms, and when I had my nook color I immediately went to cm7 for the obvious benefits. But with my nexus 7, I'm not so sure of the clear benefits of a custom rom.
Again, it's great they do this work and I know there are some features like being able to use custom kernels, over-clocking etc, but I think there are some good features that would really attract other users.
For ex, with miracast, a lot of people were anxious to have that on the nexus 7 but were disappointed that it was only the n4. I thought, cyanogen or some group will enable it in their rom, but so far nothing.
I'm really surpised though that no one seems to know exactly why it wasn't enabled. Like what in the hardware is preventing it? Some have said because the wifi chip is only 2.4 ghz but that doesn't seem confirmed. And if that's the case, then why not on the n10? Then with the n10 some say it's because of the high resolution, but I think res scaling is in the miracast spec. I guess I'm suprised some dev hasn't looked at the code and said, ah this is the reason it wasn't enabled. Like is there proprietary code with the encoder or wifi chip? Or is all of miracast in aosp?
Another example is the n4 not getting multi-user. This is obviously not a hardware limitation but a decision on google's part as tyically a tablet is shared but a phone is not. I don't own an n4, but sometimes people want to borrow your phone and it would be nice to be able to just let them play with your phone without any worry of someone seeing private data.
What I'm getting at is, if it's obvious that the n4 could have multi-user (btw has any custom rom enabled that for the n4?) but it doesn't because google decided as such and it's also obvious the N7 could have the sip dialer, is it the same case with miracast or is it actually a hardware issue?
The other thing I mentioned was the dialer. It's disabled on n7 because it's not a phone, but for a long time now the built-in dialer has had support for sip, and you see mentioning of voip all the time with regards to the N7. cm7 had the dialer enabled on the nook (which wasn't useful because of no mic) so why not on the n7? From what I've read no custom rom enables the dialer. Again, I know the functionality is there, all you need to do is change the dpi to a phone value. So it would sound as simple as taking out that check.
Yes there are lot's of voip alternatives but I want the built-in dialer because I heard it works with bluetooth headsets.
I tend to ramble, but basically getting miracast and sip dialer would be two nice features out of a custom rom, and I could some users of N4 wanting multiuser. I think it's pretty obvious that any n7 could have the sip dialer enabled and any n4 (or other phone) could have multi-user so wondering if it's the same for miracast.
This is the power of open source. The company decided we can't have feature X on device Y so why not enable it if the code is there?
Over 400 views but no replies. Does anyone know?
Really, I don't want to ask other users like myself, I want to ask developers but it sounds like posting something like this in any dev forum is against the rules.
sark666 said:
Over 400 views but no replies. Does anyone know?
Really, I don't want to ask other users like myself, I want to ask developers but it sounds like posting something like this in any dev forum is against the rules.
Click to expand...
Click to collapse
Nexus 7 lacks the correct WiFi hardware for miracast, that's why it didn't come with it enabled and why no one is working on it. There is, however apps in the store for streaming over WiFi.
Sent from my Galaxy Nexus using xda app-developers app
I'm curious, where did you read that? I've read speculation that it's because it's 2.4 ghz only but no where did I read that was confirmed. And then why not the N10?
VonEsch said:
Nexus 7 lacks the correct WiFi hardware for miracast, that's why it didn't come with it enabled and why no one is working on it. There is, however apps in the store for streaming over WiFi.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can confirm it has 5ghz band. I use the net gear n600 (I think?) Dual band router and it connects to my 5G band.
Sent from my Nexus 7 using xda app-developers app
I looked up it up on Google. Crazy, right?
Sent from my Galaxy Nexus using xda app-developers app
VonEsch said:
I looked up it up on Google. Crazy, right?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I call bs
Sent from my Nexus 7 using xda app-developers app
I looked up it up on Google. Crazy, right?
Click to expand...
Click to collapse
Hmm, I googled it extensively, and found many speculating that it's because of 2.4 ghz and other speculating that the N10 didn't have miracast because of it's high resolution. But that's all it was, speculation. Nothing from an official at google as to why, or a rom/android dev who has actually taken a look at the code.
So I'd like to see a link or otherwise to me it's another comment that falls under the speculation column.
And my post wasn't just about miracast, but rather seemingly easy features (well sip and mutli-user for phones) that rom devs could enable but for some reason don't.
Hi guys
You doesn't need any of the patches or 3rd party apps.
You just need to follow these steps in order to use cast screen in custom roms:
1. Just enable wifi 'on'
2.Open cast & it shows all available devices:fingers-crossed:
After update 20140825 I've been experiencing issues with my WIFI connection, it keep on "Obtaining IP" and after a some time it will restart the connections as it fails....I saw some people experiencing the same problem on this thread :
http://forum.xda-developers.com/showthread.php?t=2735565&page=78
but as im kind of new a can not replay for my lack of posts published, so my question in general is, should I try the PhilZ Touch 6.48.6 Recovery with a clean install with the latest Nightly in other to see if it solve the WIFI problem ?
I don't think anyone knows for sure yet but yes that is what the one person has claimed to have found a fix did.
Sent from my XT907 using XDA Free mobile app
mrkhigh said:
I don't think anyone knows for sure yet but yes that is what the one person has claimed to have found a fix did.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Didnt work for me :crying: .... I went back to 20140729 Nightly
Exactly the same problem as you're having, and PhilZ didn't help with the problem at all. The main thread guys doesn't seem to be responding to the issue either. I'll see what I can do from here.
Oh, and cc @ATTACK - you must have acknowledged the issue by now, I guess.
Sent from Google Nexus 4 @ CM11
The Wifi issue has been reported. Dhacker added this commit to CM, but I don't know if it's been merged yet.
One way to fix the issue is to set a static IP. Dhcp is what seems to be the issue
jb14813 said:
One way to fix the issue is to set a static IP. Dhcp is what seems to be the issue
Click to expand...
Click to collapse
Static IP makes it connect successfully, but for unknown reason, data only uploads (as indicated by the arrows on the WiFi icon), and no website would load, even when other phones connected to the same WiFi works. Tried multiple IPs to make sure the IP I choose is legal, but still no dice.
jb14813 said:
One way to fix the issue is to set a static IP. Dhcp is what seems to be the issue
Click to expand...
Click to collapse
Well for me this is not an option, but thanks for the tip.
ATTACK said:
The Wifi issue has been reported. Dhacker added this commit to CM, but I don't know if it's been merged yet.
Click to expand...
Click to collapse
I'll be waiting patiently with 20140729 Nightly then...
AndyYan said:
Static IP makes it connect successfully, but for unknown reason, data only uploads (as indicated by the arrows on the WiFi icon), and no website would load, even when other phones connected to the same WiFi works. Tried multiple IPs to make sure the IP I choose is legal, but still no dice.
Click to expand...
Click to collapse
Try setting the DNS to 8.8.8.8 and 8.8.4.4 ( Google DNS)
jb14813 said:
Try setting the DNS to 8.8.8.8 and 8.8.4.4 ( Google DNS)
Click to expand...
Click to collapse
8.8.8.8 is the default value for the 1st DNS slot. My habit is to fill 8.8.4.4 in the 2nd one but it still doesn't work.
Sent from Google Nexus 4 @ CM11
AndyYan said:
8.8.8.8 is the default value for the 1st DNS slot. My habit is to fill 8.8.4.4 in the 2nd one but it still doesn't work.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
What about OpenDNS 208.67.222.222 & 208.67.220.220 ?
teckem said:
What about OpenDNS 208.67.222.222 & 208.67.220.220 ?
Click to expand...
Click to collapse
Doesn't work either. I'm pretty sure this isn't a DNS problem.
EDIT: Downgraded to JB and flashed JB BL version, WiFi and GPS both working splendidly out of the box. I'll stick to JB BL at the moment because it also supports arrrghhh's overclocked kernel. Thanks for all the help anyway.
AndyYan said:
Doesn't work either. I'm pretty sure this isn't a DNS problem.
EDIT: Downgraded to JB and flashed JB BL version, WiFi and GPS both working splendidly out of the box. I'll stick to JB BL at the moment because it also supports arrrghhh's overclocked kernel. Thanks for all the help anyway.
Click to expand...
Click to collapse
Ur welcome .... But As I mentioned the problem was apparently from 20140825 and above (Well for me), so in order to keep my KK BL I went back on a Nightly I had which in my case was 20140729 (Which does not have bugs as I've tested).
teckem said:
Ur welcome .... But As I mentioned the problem was apparently from 20140825 and above (Well for me), so in order to keep my KK BL I went back on a Nightly I had which in my case was 20140729 (Which does not have bugs as I've tested).
Click to expand...
Click to collapse
Suggestion: try scratching goo.im for previous nightlies and isolate the issue between certain ones. Back in March CM11 had stutter issues on this phone and I successfully traced the issue back to November 2013. Helped solving the issue in 3 days after the discovery.
Sent from Google Nexus 4 @ CM11
0825 is when those commits were built, right? Dhacker's commits to fix the WiFi, it involved something in the kernel, or reverting something.
Sent from my DROID RAZR M using XDA Free mobile app
TheForceUnleashed said:
0825 is when those commits were built, right? Dhacker's commits to fix the WiFi, it involved something in the kernel, or reverting something.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
They are trying to fix it, but I don't know if it is on kernel o somewhere else... The only way I could get back to "normal" was using a previous Nightly.
AndyYan said:
Suggestion: try scratching goo.im for previous nightlies and isolate the issue between certain ones. Back in March CM11 had stutter issues on this phone and I successfully traced the issue back to November 2013. Helped solving the issue in 3 days after the discovery.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I'll try it... I'm considering to try pacman ROM, they say they had no issues and it's compatible with KK BL
Enviado desde mi DROID RAZR M mediante Tapatalk
So I'm in Europe for a few weeks and have been enjoying T-Mobile's unlimited data roaming while I'm here. I still try to be fair and use wifi for heavier downloads when I have access to it. I was able to update and download apps using just cellular data when I was using Marshmallow. I updated to Nougat and it no longer works. It downloads fine on wifi, and with data roaming off, when I try to download individual apps I get asked if I want to use only wifi as it will use alot of data. With data roaming on, no such question is asked and it just says pending until I connect to wifi.
Is anyone else experiencing this? Is there a fix?
Thanks in advance for your responses!
Just reporting back. I'm back in the US and apps now download via cellular data again so it's clearly an android nougat "feature." They should give us the option to choose as this can be be a huge inconvenience for many as it was for me.
Sent from my Nexus 6P using Tapatalk
toyanucci said:
Just reporting back. I'm back in the US and apps now download via cellular data again so it's clearly an android nougat "feature." They should give us the option to choose as this can be be a huge inconvenience for many as it was for me.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Exactly what i'm facing after updating my Nexus 4 with nougat.
t18 said:
Exactly what i'm facing after updating my Nexus 4 with nougat.
Click to expand...
Click to collapse
It's stupid and annoying and they should give us the choice and not make it a default "feature"
Sent from my ZTE A2017U using Tapatalk
Same
Got the same issue and can't find a solution. Anyone has an idea how to change this?
Already tried all standard settings, altering updates on roaming etc.
Not fixed yet. All options tried.
M facing the same issue and there seems to be no solution to this currently
Same here, in different device. Reverted back to MM.
Either Motorola or Google has to take this issue of 'Disabled App Download/Upgrade on Roaming' feature seriously. This is a stupid kind of thing I have ever seen. It should be the decision of end user whether to update or not to update while on roaming. With implementing this irritating feature Android is ruining it's own image. This is one of the 'Dumbest thing' ever happened in software industry.
Totally upset with it. I am facing this issues & have seen many people complaining on different community forums regarding this issue since SEP-2016.
Only God knows when Android Developers will take it seriously. May GOD en-light Google on this !