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
Related
[flameproof suit]
Hey guys, been away a couple weeks due to my mother having some health issues. Oh what a difference a couple weeks makes around here. So I see there's a second 2.1 leak out now. I scanned MOST of the thread titles (at least the first 6 pages) and opened a few of the threads looking for info on the new one. From what I found, it looks like the main difference is fixing of the issue with google requiring login over and over. Is there more to it than that? I installed the first leak on my wife's Eris and it's been working well, but I've been (not so) patiently waiting for the "official" OTA for my own Eris. Starting to feel like it's never going to happen and wondering if I should just go ahead and leak on mine!
And while (if?) I've got your attention, my wife has had one complaint about her phone since I installed the 2.1 that I've not seen mentioned elswhere. Now mind you, gadgets are NOT my wife's forte`, and I'm definitely not ruling out operator error. However, she 'says' that her phone keeps somehow ending up on "silent mode" and she has no idea how. Again, knowing my wife, it could easily be her doing, but just wondering if anyone else has experienced this with first leak 2.1?? [/flameproof suit]
TIA,
i have installed the 1st Leak on my Girlfriends phone, and no she doesn't have this problem, shes actually very happy with it and says its very fast and the battery now last her long unlike before!
Dangerous Dave said:
[flameproof suit]
Hey guys, been away a couple weeks due to my mother having some health issues. Oh what a difference a couple weeks makes around here. So I see there's a second 2.1 leak out now. I scanned MOST of the thread titles (at least the first 6 pages) and opened a few of the threads looking for info on the new one. From what I found, it looks like the main difference is fixing of the issue with google requiring login over and over. Is there more to it than that? I installed the first leak on my wife's Eris and it's been working well, but I've been (not so) patiently waiting for the "official" OTA for my own Eris. Starting to feel like it's never going to happen and wondering if I should just go ahead and leak on mine!
And while (if?) I've got your attention, my wife has had one complaint about her phone since I installed the 2.1 that I've not seen mentioned elswhere. Now mind you, gadgets are NOT my wife's forte`, and I'm definitely not ruling out operator error. However, she 'says' that her phone keeps somehow ending up on "silent mode" and she has no idea how. Again, knowing my wife, it could easily be her doing, but just wondering if anyone else has experienced this with first leak 2.1?? [/flameproof suit]
TIA,
Click to expand...
Click to collapse
From scanning one of the threads over at Android forums, it seems like the only major difference with the new leak is, as you said, that the google login bug is now fixed. Some people did report one more bar of reception in certain areas where it had previously been lower; however, I don't believe that anybody reported the "time without a signal" bug being fixed, so it could be that the software was re-calibrated to report more bars even though the actual signal strength was the same. If you've already updated to the first leaked 2.1, I personally wouldn't bother flashing the new leak...too much work to back-up and restore apps, contacts, etc. for little improvement.
As for your wife, it's quite probable that she's accidentally hitting the volume down button on the side of the device (maybe from pressure in her purse or pocket) until it goes into silent mode. Nobody's reported that as a bug that I know of, and I haven't experienced it personally (on first leaked 2.1), so I think you're correct in assuming it's user error.
Hope that helps.
Hey Dave, new to the forums here, but I'll throw in my 2 cents.
On my last Eris, I installed the very first 2.1 leak (which I'm assuming is the one your wife has) and I found that the bug on mine was that the volume was set to the max for ringtones, notifications, alarm, etc.. But when I would receive a notification it wouldnt play. I'm guessing maybe that's what she is experiencing. I understand you said it was actually going into silent mode, but the problem she is telling you could be this.
I've also noticed a couple of other differences but I just Installed it yesterday. The download more Htc widgets now works(no big deal there) I am pretty sure I have noticed a change or 2 in settings also. I'll post again if I notice anything else.
ericFuels999 said:
From scanning one of the threads over at Android forums, it seems like the only major difference with the new leak is, as you said, that the google login bug is now fixed. Some people did report one more bar of reception in certain areas where it had previously been lower; however, I don't believe that anybody reported the "time without a signal" bug being fixed, so it could be that the software was re-calibrated to report more bars even though the actual signal strength was the same. If you've already updated to the first leaked 2.1, I personally wouldn't bother flashing the new leak...too much work to back-up and restore apps, contacts, etc. for little improvement.
As for your wife, it's quite probable that she's accidentally hitting the volume down button on the side of the device (maybe from pressure in her purse or pocket) until it goes into silent mode. Nobody's reported that as a bug that I know of, and I haven't experienced it personally (on first leaked 2.1), so I think you're correct in assuming it's user error.
Hope that helps.
Click to expand...
Click to collapse
Yeah, my wife is so bad with gadgets I don't even like to let her set the alarm clock. Thanks for the reply though. I did mention to her that she should make sure she's not accidentally hitting the volume down button.
On my last Eris, I installed the very first 2.1 leak (which I'm assuming is the one your wife has) and I found that the bug on mine was that the volume was set to the max for ringtones, notifications, alarm, etc.. But when I would receive a notification it wouldnt play. I'm guessing maybe that's what she is experiencing. I understand you said it was actually going into silent mode, but the problem she is telling you could be this.
Click to expand...
Click to collapse
It's not notification sounds that are the problem, it's the ringer. I call her, but she says she never heard it ring. Eventually she sees the "orb" glowing and checks notifications to see she missed a call, then checks to once again find it in "silent mode". Really annoying for me. I pay good money for her to have a cell phone and I can never reach her when I need to. Then again, it was that way before she got her Eris. Again...gadgets..............................
And BTW, I think notification sounds are controlled by "media volume", not "ringer volume", but I could be mistaken.
On the new 2.1 leak here.
1. Google Voice app still not routing calls through the GV #. I have to use the older app version (0.2) which doesn't have voicemail integration native or synchronized inbox.
2. HTC get more widgets does not work. I get an error message saying, "Unable to download widgets. Tap to try again."
3. I have noticed improved battery life. On the previous leak, if I forgot to charge it around 9pm it would quickly die. But I was able to leave it unplugged all night and still have a little juice in the morning.
regis_star said:
On the new 2.1 leak here.
1. Google Voice app still not routing calls through the GV #. I have to use the older app version (0.2) which doesn't have voicemail integration native or synchronized inbox.
2. HTC get more widgets does not work. I get an error message saying, "Unable to download widgets. Tap to try again."
3. I have noticed improved battery life. On the previous leak, if I forgot to charge it around 9pm it would quickly die. But I was able to leave it unplugged all night and still have a little juice in the morning.
Click to expand...
Click to collapse
HTC 2.1 Release Candidate (AKA OTA) Leak Rom
1) I agree latest GV not working , using 0.2.0 seems fine
2) I am able to get more widgets to work : shows six (6) more widgets Battery, daily chalange etc
3) Still testing , not sure if battery has improved for me.
4) still no pictures in Gmail ( shows ? )
Happened to me
There's a setting under Sound & Display that says "Quiet ring on pickup"...check to see if that is active. It happened to me where I was keeping my phone in my purse, and anytime someone would call me, because i would be carrying my purse, the motion would silence the ring, and I wouldn't know that anyone called. That's certainly a possibility.
Does anyone kno of a ROM that has the new version of the 2.1 leak that will work on the g1?
UPDATE: Thank you guys so much for the help! My phone is running well so far! The GPS works well enough for navigation, and I should hopefully be able to limp through until my full upgrade. I can't tell you guys how thankful I am that you all took the time to help me answer my questions and get my phone going again!
what would you do? I have a Vibrant, and have done quite a lot of troubleshooting with it. Tmo's tech support said it's a hardware issue and that they've done all they can.
I've tried just about all the Froyo ROMs on it, and things seem to work well for a while, then it gets odd. I regularly clear my call logs, messages, and browser cache. I use wifi whenever I'm at home, and whenever I'm in the minivan I have my phone plugged in.
I am currently running Axura - Moped/FishmanMod v1. This has seemed to work the longest.
Lately, though, I've been missing phone calls...as in, no notification, no log, nada. I rebooted last week and suddenly had a voicemail icon...I had 7 new voicemails. One from my son's teacher. I never knew she even called. I've since reinstalled Tmo Visual Voicemail and at least now I think I'm getting my voicemails. Missing phone calls can't happen though. We don't have a landline, and we have a child with health issues. I have to be available.
Other issues:
*My battery died about halfway through the day yesterday, even though it had charged fully overnight.
*This thing is slowing down. As in, taking a photo with my phone isn't really viable. By the time it finally snaps the picture, my kiddo has grown an inch.
*Lag! I'm using Swiftkey X and it often hangs on a key for several seconds before finally typing it. It's very slow to open apps, etc as well.
Does anyone have any more advice for me? I'd love to run an ICS or JB ROM, but having the ability to call 911 is not negotiable for me. Woodrube and some others have given me some great advice, which has helped, but I'm still having some issues.
I could pare down the apps and use it just as a phone, but what would be the point of having an Android...and data? I need the calendar, email, task list, etc. to keep track of everyone.
I'd love to try to figure out how to make this phone last longer. I could upgrade now, but our checkbook doesn't like the idea.
Personally I'd Odin back to stock JFD and either do a reflash or pick a new ROM (bionix comes to mind).
Could do a fresh install of the apps you want on your phone. Your battery could be going bad and may need to be replaced, and if your sim card is getting old, you may need to stop by T-Mobile and have them replace it.
Not sure if that could be the trouble with your notifications or voicemail, but they are all quick things to try that should be cheap and quite possibly very effective.
The_MamaBee said:
what would you do? I have a Vibrant, and have done quite a lot of troubleshooting with it. Tmo's tech support said it's a hardware issue and that they've done all they can.
I've tried just about all the Froyo ROMs on it, and things seem to work well for a while, then it gets odd. I regularly clear my call logs, messages, and browser cache. I use wifi whenever I'm at home, and whenever I'm in the minivan I have my phone plugged in.
I am currently running Axura - Moped/FishmanMod v1. This has seemed to work the longest.
Lately, though, I've been missing phone calls...as in, no notification, no log, nada. I rebooted last week and suddenly had a voicemail icon...I had 7 new voicemails. One from my son's teacher. I never knew she even called. I've since reinstalled Tmo Visual Voicemail and at least now I think I'm getting my voicemails. Missing phone calls can't happen though. We don't have a landline, and we have a child with health issues. I have to be available.
Other issues:
*My battery died about halfway through the day yesterday, even though it had charged fully overnight.
*This thing is slowing down. As in, taking a photo with my phone isn't really viable. By the time it finally snaps the picture, my kiddo has grown an inch.
*Lag! I'm using Swiftkey X and it often hangs on a key for several seconds before finally typing it. It's very slow to open apps, etc as well.
Does anyone have any more advice for me? I'd love to run an ICS or JB ROM, but having the ability to call 911 is not negotiable for me. Woodrube and some others have given me some great advice, which has helped, but I'm still having some issues.
I could pare down the apps and use it just as a phone, but what would be the point of having an Android...and data? I need the calendar, email, task list, etc. to keep track of everyone.
I'd love to try to figure out how to make this phone last longer. I could upgrade now, but our checkbook doesn't like the idea.
Click to expand...
Click to collapse
Well, although it isn't too helpful to say...I honestly believe that if you simply must be available because you have a child with health issues, you definitely should not be tinkering with your device. True, my phone runs better, faster, stronger, and longer (ha daft punk) than it did running stock, but I have certainly had the occasional issue such as data issues, force closes, battery drains, SODs, etc, etc...it's simply a fundamental part of the life of modifying your phone. It's not to say that you won't have issues if you kept it stock, but you really shouldn't be messing with your phone if you don't have a land line and you NEED to be available for something so important.
Now, onward!
I will look into similar occurrences of your problems and report back..(sorry in class atm, then off to a meeting). Until then, Gl!
you could try and use a cyanogenmod based Rom. They are one of the best roms out there except you can't as of right now call 911 (some phones can and some cant ) also gps is semi-broken.
blizzardproof said:
you could try and use a cyanogenmod based Rom. They are one of the best roms out there except you can't as of right now call 911 (some phones can and some cant ) also gps is semi-broken.
Click to expand...
Click to collapse
Thanks for the advice, but not an option. I have to have 911 capability, and we're pretty active geocachers, so my GPS gets used a ton. I've been so tempted by CM Roms, and my husband is rocking one on his One S, but going without 911 isn't an option.
After this last round of my phone's slowness, we did ODIN back to stock, then did the ((*^&^%$*&^) updating it to Froyo. (Yay!) We were hoping that taking it back to stock would help our issues, but it actually seemed slower. (And oh, the agony of using TouchWiz!) I very, very carefully added back ONLY the apps I used on a daily basis, watching carefully to see if there were any issues. It was crazy slow.
We then went to this last ROM and I added back apps even more slowly. I noticed that I had issues after I put the Zedge app back on, so it's gone. I also noticed that it acted funky after I put Google Goggles on, so it's gone as well.
I am not, by the way, storing any music on my device. I stream it through Google Music.
I do have another battery for it. I'll put Battery Calibration on and swap batteries to see if that helps. Good idea.
Also, my SIM is pretty old. I hadn't thought about seeing if I could get a new one! I know it solved some issue LONG ago with my BlackBerry. I'll see if I can do that at our TMo store today. Appreciate that suggestion.
I've been just about the give up on this phone altogether and just going with the One S like The Hubs, but forking over the money for it (not to mention that it would be $200 for me and $49.99 for a new contract!) is just not in the budget now. Might be getting close to something we just can't avoid though.
Try flashing back to stock 2.1 with repartition checked. Then flash one of Fishman/Moped 2.2 ROMS ( he has odin files if you prefer that method). I think you may still have some "ghosts" left behind from the last ROM or two you had on your phone. A fresh odin to stock with repartition checked should get rid of any "ghosts". Also when restoring apps make sure you restore app only, not app+data. Remember, after installing a ROM allow your phone to sit for a good 10 minutes then reboot before you use the phone.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Try flashing back to stock 2.1 with repartition checked. Then flash one of Fishman/Moped 2.2 ROMS ( he has odin files if you prefer that method). I think you may still have some "ghosts" left behind from the last ROM or two you had on your phone. A fresh odin to stock with repartition checked should get rid of any "ghosts". Also when resorting apps make sure you restore app only, not app+data. Remember, after installing a ROM allow your phone to sit for a good 10 minutes then reboot before you use the phone.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
That could definitely be it. I used to just restore all my apps+data with My Backup Root. I'll see if I can convince The Hubs to help me work on the phone this weekend. I'll let you know how it goes. Thanks!
Okay, we did the repartition flash, then put it on FishmanMod Blue 2.2 Frankenstein Slim. Seems to be running a little better, but now my GPS won't lock at all. I've rebooted, tried Samsung GPS Restore (never locks) and GPS Test. Test sees 4-5 satellites but doesn't ever lock on. I've tried Nav as well and it is not able to lock on.
I've checked our forums and I see a lot of fixes, but no recent fixes and most of them are for 2.1. I've tried dialing the *#*# numbers, but they don't do anything.
I sure could use some suggestions. I'd like to be able to use my GPS. I know it's generally an issue with Vibrants, but mine has never failed to lock on before. Might be slow, might take it until the end of the block, but it always locks. Until now...
Thanks in advance!
Go to the Dev section and look for a thread called GPS Fixes by Solisfiend. It'll be buried way back and I'm mobile so I can't link it. It has directions and app to fix Froyo GPS.
I have 2 posts in there, 1 is clarification of some things and the other is a download app you can use. Should work well for you.
Thank you, Woodrube. I'll do just that.
ETA: Found the link.
http://forum.xda-developers.com/showthread.php?t=1393991&highlight=gps+fixes
Sent from my SGH-T959 using xda app-developers app
My EVO 4G LTE has, with all custom ROMs, lost stability after a month or two, developing different arrays of performance quirks or problems.
I'm interested in if there's a way to test the hardware on the phone? I'm tired of switching / reinstalling ROMs.
At first I thought the problem was that the ROMs were unstable but I've chosen from the bet ones available - PACman, Viper, a couple others I can't recall right now. The phone is rooted via Dirty Racun FYI...
Currently, with Carbon, the problems consist of:
With screen lock off, when waking the phone via the power button, something on the current screen will activate, whether it's an app shortcut on the homescreen, or a function inside of an active app.
Setting for LTE / 3G will not stay on 3G (LTE coverage is spotty enough that I just don't use it)
Random crashes / resets / bootloops; occasionally the phone will freeze on the loading screen with the Carbon logo and require me to hard-reset it.
Once in a while it's ignored my alarm clock.
Usually when dialing out, the phone will hang and fail to connect / ring, and I'll have to hang up and dial out a 2nd time to connect / ring through.
With ROMs I've used in the past, the arrays of problems have been different but of similar nature. At first I was inclined to blame the ROM in use but as my phone is the common element between them, I'm interested in how I can determine if I have a lemon on my hands or what.
Thanks for reading this.
Go back to stock rooted and see how it runs.
Captain_Throwback said:
Go back to stock rooted and see how it runs.
Click to expand...
Click to collapse
I'm not unwilling to do that, but I have extra time this weekend to run diagnostics as well if there's any method by which that's possible? It seems to take a few weeks for problems to start developing when I install a fresh ROM.
baccaruda said:
I'm not unwilling to do that, but I have extra time this weekend to run diagnostics as well if there's any method by which that's possible? It seems to take a few weeks for problems to start developing when I install a fresh ROM.
Click to expand...
Click to collapse
Any such diagnostics when not on a stock ROM can be issues with the custom ROM, not the device. If they occur when on stock, that helps determine hardware may be at fault.
Most of the AOSP ROMs suffer from kernel and data issues because they use the same base. You might want to try the Android 4.3 RUU as well since that's the latest we have for the device.
Captain_Throwback said:
Most of the AOSP ROMs suffer from kernel and data issues because they use the same base. You might want to try the Android 4.3 RUU as well since that's the latest we have for the device.
Click to expand...
Click to collapse
Ah, thanks for this. I didn't think it would be reasonable to blame the ROMs across the board. I'll look into the 4.3 RUU.
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband
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