At some point in time my garage door opener app (MyQ by Chamberlain) stopped working. I upgraded a while ago to android 10 and have tried multiple flavors, settling on StagOS. The app now gives me a "error connecting to server" message when trying to do anything (log in, sign up for new account, forgot password, etc). Not sure what the issue is. I've tried fresh installs of StagOS and Potato with the same result. Have also recently (?) started failing safety net /CTS profile, so I'm not sure if that has something to do with it or not. No problems with my older tablet and wife's stock S9 running 10. Was hoping someone could install the app and see if they get the same issues, maybe let me know what ROM you're using. Thanks.
Anybody?
Seriously, nobody is willing to try this?
You're looking for a very specific user who 1) comes to XDA, 2) has a MyQ system, 3) has StagOS. It's not surprising you're not getting an answer, as there may not even be another person here with the exact setup you have... so how do you expect someone to test this? Your best bet is probably to ask on the StagOS thread, as you'll have more luck? (I haven't even heard of StagOS, but I also don't run a custom ROM.
Bottom line, you'll have to do the testing yourself, as you are probably too specific for others to help. For example, I don't have Pie, StagOS, or MyQ, so I can't help... I'm sure many others are in the same boat for various reasons.
Actually, I'm looking for someone who has any custom ROM to see if it's specific to this one, all lineage builds, Android 10 only, maybe a Google play services update broke it, etc. And you don't need a myq system. You just need to install the app and hit "sign up" to see if you get the error.
Ok, that wasn't clear in your request. But even still, I'm confused. You already tested this (with your wife's phone) so what are you asking people to do? You know it works on Pie (per your wife's phone), so it's clearly an issue with the two custom ROMs you tried. I'm guessing that's the issue... but I'm not sure how me testing on my VS996 Oreo will help you any more than your test on your wife's phone does? Custom ROMs often have such issues... have you tried a stock ROM instead?
schwinn8 said:
Ok, that wasn't clear in your request. But even still, I'm confused. You already tested this (with your wife's phone) so what are you asking people to do? You know it works on Pie (per your wife's phone), so it's clearly an issue with the two custom ROMs you tried. I'm guessing that's the issue... but I'm not sure how me testing on my VS996 Oreo will help you any more than your test on your wife's phone does? Custom ROMs often have such issues... have you tried a stock ROM instead?
Click to expand...
Click to collapse
I think he does need someone with an Android 10 LOS ROM. Not necessarily StagOS, but still an LOS ROM vs stock. I can't help either.
Yeah, if anyone has any other Android 10 custom ROMs it would be helpful to know if any work. I got safety net to pass, but that didn't do it either
Related
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
The data dropping out may be due to some work/upgrades in your area ... call VZW to see if they know anything.
As far as updating to GB, my advice is tread lightly ... especially if you're just wanting a stock version of it. There are bugs, the biggest being voice mail notifications not working, that may drive you nuts. That being said, there are several custom ROMs around that have fixes/tweaks that make this plagued GB build VZW & HTC released much more manageable. Look around and there are a few "stock" custom ROMs out there - or if you prefer a totally different look/feel there are several Sense 3.0 ports to choose from too.
As far as a how-to guide, the best one I've seen is THIS ONE. Read it and get knowledge my friend
Happy flashing!
2.11.605.3.zip is the [gb] patch - "It changes camera libs, and some insignificant
framework, and apks." as stated on teambamf.net, i did read it is running smooth,
increased battery life but,with issues pertaining to vm notification error and front facing camera
upside down. i agree with Yank talk with carrier, im currently running dasBAMF Forever
kernel 2.6.35.10 stock radios have had no issues.
vinny2006 said:
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
Click to expand...
Click to collapse
Can you link me to that download? I would like to see exactly what you are making reference to before I comment.
Some of those update .zips are the full unrooted rom. You wouldn't want to flash that. You want to make sure and look for something like...
"Rooted Debloat Blah Blah Blah"
The link provided by Yank is a good one. #3 for "Flashing a Rom".
Also another hint (just in case you are unfamiliar with recovery). the camera buttons toggle up/down and the power button is used to make a selection. you can select "go back" by toggling to it and selecting it or you can use the soft back key.
hope that helps.
As to the voicemail issue, Eris has fixed that. Took him 30 minutes, he said.
Sent from my ADR6400L using Tapatalk
Did you read this?
http://teambamf.net/showthread.php/718-How-to-flash-a-ROM
Hello everyone,
I'm not sure if I'm the only one or not since I haven't seen this issue in any of the threads for any JB Roms. This doesn't seem to be a problem for any 1 Rom, so I'm thinking it has to do with the CM10 base everyone is using. Here is the problem:
Everything is fine on the Rom for a few days - I can browse the web, make calls, get emails, etc... Then, I'll make a call, and the call will connect (call timer starts on screen), but I can't hear the person on the other end, and they can't hear me. I know this for a fact because I called my wife's phone which I was using as a test.
It would continue to stay like this (even after rebooting normal, rebooting to recovery and wiping cache / dalvik). The only thing that seemed to fix the problem would be to re-install the Rom.
For now I'm back on one of the CM9 Roms, and everything is ok. I really like CM10, but don't want to potentially get into an emergency situation, and then not be able to use my phone, or go to make a business call, and look like an idiot because people can't hear me, etc...
I just wanted to know if anyone else has experienced this, or has a fix? Thanks for your input.
what Rom ? (specific)
what carrier? ( is this an ATT device running with a different carrier? )
what region? (are you in the US, Canada, or elsewhere? )
Most reports are leaning toward the modem as the issue. If we know the above information, we can suggest a fix or patch based on them....g
gregsarg said:
what Rom ? (specific)
what carrier? ( is this an ATT device running with a different carrier? )
what region? (are you in the US, Canada, or elsewhere? )
Most reports are leaning toward the modem as the issue. If we know the above information, we can suggest a fix or patch based on them....g
Click to expand...
Click to collapse
Rom: I've tried all of the CM10 Roms currently available, and it happened on each of those. Most recent was CM10Hybrid Paranoid Android.
Carrier: AT&T
Region: US. More specifically - South East.
The last modem I flashed directly (unless one was cooked into a rom), was UCLF6.
scotty2hotty1125 said:
Rom: I've tried all of the CM10 Roms currently available, and it happened on each of those. Most recent was CM10Hybrid Paranoid Android.
Carrier: AT&T
Region: US. More specifically - South East.
The last modem I flashed directly (unless one was cooked into a rom), was UCLF6.
Click to expand...
Click to collapse
Lets test this a bit more....
Download and flash the Stock, UCLA1 modem, then reboot it 3 times. then try a call to a test device.
I've had marginal success with the modems above the UCLA range, and am using the UCLA1 Modem on virtually all of the roms I use. ( now if I could get all 1352 apn's from the stock rom to work...LOL ).....
It may show up as "unknown" in the "about phone" settings, but based on the tests I've done with it, you should be safe on the IMEI loss issue that some TMO users are reporting.
There is always that chance, but where you are US based on ATT, and that is their modem, you should be fine.
Test that bad boy out, and report back if ya would...thank you....g
I think its just the cm10 roms ..mainly because I've seen a post like this in all the JB forums...
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
scotty2hotty1125 said:
Hello everyone,
I'm not sure if I'm the only one or not since I haven't seen this issue in any of the threads for any JB Roms. This doesn't seem to be a problem for any 1 Rom, so I'm thinking it has to do with the CM10 base everyone is using. Here is the problem:
Everything is fine on the Rom for a few days - I can browse the web, make calls, get emails, etc... Then, I'll make a call, and the call will connect (call timer starts on screen), but I can't hear the person on the other end, and they can't hear me. I know this for a fact because I called my wife's phone which I was using as a test.
It would continue to stay like this (even after rebooting normal, rebooting to recovery and wiping cache / dalvik). The only thing that seemed to fix the problem would be to re-install the Rom.
For now I'm back on one of the CM9 Roms, and everything is ok. I really like CM10, but don't want to potentially get into an emergency situation, and then not be able to use my phone, or go to make a business call, and look like an idiot because people can't hear me, etc...
I just wanted to know if anyone else has experienced this, or has a fix? Thanks for your input.
Click to expand...
Click to collapse
I second that as the same happened to me, but all I did was reboot and it solved the issue. Happens at least once or twice a day for me.
Sent from my SAMSUNG-SGH-I717 using xda premium
Have any of you tried a scheduled cache clearing app ?
I've found many issues due to cache building in the background APK's....
It effectively bogs down everything , and once cleaned , fixes "a lot " of issues ...
Could someone test this and report back ?
At least we would know where to look at fixing the issues, rather than assuming it's a modem issue .....g
I love the CM 10.1 build of 4.2.2. It is my dream phone right now. The problem is that no WIFI tethering works on it as of yet. If anyone has anything working I'd love to be proven wrong. This is a show-stopper for me. I can't use bluetooth because my laptop doesn't have bluetooth.
I tried every tethering app out there. Barnacle was the best in that it reported the errors it was seeing instead of just refusing to work.
Anyway, I am thinking of working around the problem by keeping a ROM stored as a TWRP backup that I can restore when I need tethering. I don't need tethering on a moment's notice.
I would like the tethering ROM as slim as possible. I haven't tried any yet. Would a restore be any faster with a slim ROM?
Can someone suggest what ROM I should use that has a small footprint and can restore quickly? I'm thinking that I won't have any apps and no account logged in. If I'm tethering I will be using the other device for email etc. And I'm sure the phone will work no matter what I'm running.
Can anyone suggest a better workaround than this?
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
crutzulee said:
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
Click to expand...
Click to collapse
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
mchahn said:
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
Click to expand...
Click to collapse
Sounds like a bad download...Did you download straight to your phone? While I've never had this issue, I have heard that some prefer to download to their computers and transfer the zip to their phones..
You might be right. I did download it to my PC and copy over the zip. However, I had trouble copying and I had to copy a second time. So, I'll try again.
I did a fresh download, copied, wiped, flashed, and it didn't work. Apparently bam won't run on my phone.
...and your using the latest version of twrp?
Yes. I checked. I might be doing something wrong but I doubt it. I'm guessing there is a bug somewhere that rarely shows up. Until the source code is available these custom roms are somewhat a shot in the dark.
I'm just going to go back to my ICS backup when i need tethering. I guess I started this thread with the hope that someone would have a workaround. I really like 4.2.2 and I've decided to live with this. Maybe it will be fixed soon?
Thanks for your help.
The only tethering app that seems to work is "Open Garden." It's in the Play Store but you'll have to side-load it if on AT&T.
Sent from my SAMSUNG-SGH-I717 using xda premium
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
How do you keep AT&T from seeing that you're tethering?
knoshann said:
How do you keep AT&T from seeing that you're tethering?
Click to expand...
Click to collapse
I don't know who you are replying to, but I tethered all the time with ATT when using ICS. I didn't know they were trying to block it.
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
knoshann said:
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
Click to expand...
Click to collapse
I know that Verizon has folded tethering into the normal data plans. They make it sound like a benefit but they're raising the overall price so they are really forcing you to buy tethering. I thought ATT and the others were going the same way.
I assume they realized they couldn't enforce it any other way.
mchahn said:
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
Click to expand...
Click to collapse
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
chp said:
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I've been to their home page a million times because everyone said you could get the apk there. I was going crazy because all I ever saw was a big orange button to download a version for windows. I had just now typed a reply to you that said you were crazy and then it hit me. You meant to go there on the phone! I'd only been there from my laptop.
Thanks, I'll give it a try now.
-- later --
As I feared, open garden is bluetooth only.
I was researching the hotspot issue that only a few users have been having and found that it is inherent to android 4.1.2 and newer. What I found out:
"Throughout the previous iterations of Android (<4.1.2), Android has not identified for the carriers which data is for tethering, and which is not.
Android 4.1.2 introduced that ability (and requirement) for Android devices to properly flag when data is for tethering purposes. This is the first time this has been used in a vanilla release of Android...
For everyone frustrated by this update to Android: Android respecting a carrier's request to know if data is for a tethered device IS NOT A BUG. IT IS A FEATURE. It's not a feature for users like you and me, it's a feature for manufacturers like Samsung and HTC, so they can in turn build devices that carriers can have more control over.
So, to be clear, THIS IS NOT A BUG. Google INTENDED to respect carrier tethering rules. The only way to circumvent this is to either get a plan from your carrier that allows tethering, revert to a build of Android of 4.1.1 or earlier (I used wugfresh NRT tools, google it, they're amazing and simple: FOR NEXUS DEVICES ONLY, SORRY), or for a developer to find and KILL THE ****ING ABILITY FOR ANDROID TO TAG DATA AS TETHERING DATA and release that to the public; either by providing an modded Android image, or as an app (much less likely to work unless you're rooted)."
Copied from a past on another forum, and apparently I can't post a link to it.
Even though I clicked on Thanks, I'd like to thank you again for that clear explanation. I'm sure it won't take long for that to be hacked.
i think the next nightly may fix it
Next to fix on next Nightly
msm8660: Add Wi-Fi AP module args (i wonder if this is it?)
rkpsym ftewed
I sent JamieD a message about it a few days ago. I'm not sure if all developers were aware with source of the problem. Its especially hard when only some users report having an issue. Hopefully they get it working soon.
my wife and I both have i777's, and I keep them rom'd similarly always, although I do a lot more experimenting with my own.
I recently found a few behavioral differences inbetween hers and mine, even though the most recent installs were after rom-wipe scripts, and TiBU restoraton of user apps only.
when I nfc-beam photos to hers, hers does not ask any permission, and the beam always completes successfully.
when I nfc-beam from hers to mine, It starts, then I am asked permission, and it fails after I grant permission.
the issue occurs whether we are on the same (cm) or different kernels
The only thing that I truly recall doing grossly differently with mine, is that I tried out a 4.3 rom recently, and then went back to cm10.1.3.
Once I noticed the issue, and couldn't correct it with a cleaning and re-rom, I even Odined back to stock, then started the whole process over, but still the NFC-beam/bluetooth issue remains.
currently we are on cm10.1.3 stable, I've googled the hell out of it, but others' issues don't seem to be the same, and their resolutions didn't help me.
any ideas?
Sorry, cyril, like you I've never heard of this. The best I can do is offer a few thoughts...
- The first culprit would be the CM nighty you're both running. Has your NFC problem always existed, or just since you installed CM?
- Do you both have the same battery, or is one different than the other? Specifically, are they OEM?
- Do you have anything remotely related to NFC turned off via autostart or something similar?
As you can see these are all guesses, hopefully whatever trouble you're having will correct itself.
Sent from the i777
I don't mess with cm nightlies at all; we both went from 10.1.3 rc2 to stable. I didn't notice when the issue began, because I really don't use the feature very often, and didn't even try it until installing cm.
Same battery? No clue, I haven't replaced them, I expect that they're OEM, but I'll pop them from their cases later to verify.
Nfc feature Turned off? I'm not sufficiently android savvy to have done anything intentionally, but I'll look up "android autostart" and see where it leads me...
No, don't worry about the autostart. I was referring to using a 3rd party app to control what starts up at boot; there's no way that's the cause if you're not familiar with what I was suggesting, because it's something you have to do manually.
Sent from the i777
Hi there, everyone. Relatively new to all this custom rom stuff, but I have been able to change roms and such with a usable level of success. A few months ago I ran into an issue that I can't seem to fix on my own, so I'm reaching out to see if someone more knowledgeable might have some experience and can point me in the right direction.
After test-driving a few different roms for a few months at a time, I ended up trying out ArrowOS. While I really enjoyed the rom itself, my phone would only ever use the speaker phone, even when it was set to use the regular ear speaker. Recently, I changed to LineageOS thinking the issue was with the Arrow rom, but the issue persists. I figured it was a firmware issue so today I flashed the firmware package and, to my surprise, the phone is still behaving the same way.
The firmware I flashed in was (fw_curtana_miui_CURTANAGlobal_V12.5.6.0.RJWMIXM_84796eb2cc_11.0.zip). It flashed with no errors, so I assume everything is fine there.
Anyone have any tips for me to follow? Much appreciated!
EDIT: This might be a newbie mistake, but the firmware I have flashed says it's for Android11 and the LineageOS I'm using is an Android 12 base. I wouldn't think it would make such a difference, but this is coming from a long-time Windows user who is used to getting by on old drivers when necessary. The ArrowOS I was using when the problem first popped up was Android 11, but I hadn't updated the firmware of the device so it may have still been on Android 10 (or even 9, I don't know).
Double posting for clarity. After trying multiple roms and firmwares, the problem still persists. The weirdest thing is that when using a hardware testing app, the earpiece speaker works fine. I've also tried using other dialer apps and they all act the same way. I am completely stumped on this. If anyone can help I would appreciate it, otherwise I guess I give up. This is way beyond me.