I wanted to post this is in the correct thread but I don't have enough posts to use the DEV forum. I just installed nightly #4. It was my first time installing a nightly and I'm pretty sure it worked since I now have an orange CWR. Is there any way to tell other than rebooting into recovery?
while im on the subject
the only reason i even went to the nightlies is because the latest "stable" cm7 build began giving me endless FCs on everything. browser, messaging, etc. i just did a cache/davlik wipe as well since ive already started having the same problem on nightly #4. is anyone else experiencing this or have any advice?
I think the easiest way would be go to settings then about phone. Should give you all the answers you need
Sent from a CM7 nightly mod testing fascinate.
inmybrain said:
I think the easiest way would be go to settings then about phone. Should give you all the answers you need
Sent from a CM7 nightly mod testing fascinate.
Click to expand...
Click to collapse
#4 was awful anyway. I had to nandroid back to jt's latest build.
Sent from my SCH-I500 using XDA Premium App
Phantom Phone rings in 7/29 nightly
I install the latest nightly 7/29 and I have had several phantom rings that I have never had and have had real legit rings on the phone where there is no caller id info and I can not answer the phone going to have to go back to 7/23 where I had only gps locking issues
about those phantom rings, do you ever have two ringers going on at the same time when receiving a call and sometimes one still going on during the call?
phantom rings continue and no signal bars
To the last post yes I have experienced 2 rings at once and can not answer either. I installed the latest cm7 nightly 7/31 hoping for some fixes but none , I still have phantom rings no bars for signal and after 30 min my mms was still on send. even tried cm7- 7/26 pretty much same them no bars and 20 min. later my mms is still sending not sent. back to cm7- 7/23 again . by the way I was using the modem and kernel that came with the rom tried glitch and ec09 and got even worse performance and a lot of force closes Anyone else experiencing this.
Yes, I was experiencing those as well. Ill install nightlies whenever I have enough time to play with it for a few hours and restore a more stable build but it is apparent that these are beta, at best.
CM7 Nightly #6 running good
Earlier today I Installed the cm7 nightly #6 8/02 so far so good no phantom or double rings, MMS sends right away like they did in froyo. only thing I have notice is I have no bars on my signal strength ever
Defragger51 said:
Earlier today I Installed the cm7 nightly #6 8/02 so far so good no phantom or double rings, MMS sends right away like they did in froyo. only thing I have notice is I have no bars on my signal strength ever
Click to expand...
Click to collapse
I just switched to the dBm signal until it's resolved.
Replying to OP here:
No worries, you're MUCH better off posting questions to this Q&A section by default. Posting questions anywhere else (especially Development) is, at best, playing with fire...
Sent from my SCH-I500 using XDA Premium App
Related
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
[SIZE=+1]Edit 2/15/2011 - A very likely fix for this problem has been identified. See this post:[/SIZE]
http://forum.xda-developers.com/showthread.php?t=956091
Edit 9/14/2010 - see diagnostic information in post #27
bftb0 said:
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
Click to expand...
Click to collapse
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
jrozga said:
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
Click to expand...
Click to collapse
I poked around a little and couldn't find any mention of it as an official feature of 2.2; do you have a link?
Does it seem to happen to you about as frequently as you were getting plain ole' dropped calls on 2.1 or 1.5, or more frequently?
bftb0
Never had a call dropped =\ can't say, sorry.
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
carycooke said:
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
Click to expand...
Click to collapse
Does it happen more frequently than the rate at which you used to get dropped calls when you were on 2.1 (or 1.5) ROMs?
I don't know whether it is a bug or not - if jrozga is correct, then it should happen about as often as plain-ole dropped calls occurred with 1.5 or 2.1 ROMs. (Or maybe to be fair, as often as dropped calls occur with stock 2.1 phones with the July 2010 OTA - they have the same radio as most rooters are using)
I still haven't found anything on line from "official" sources that mention that this is expected behavior in Android 2.2 phones. The last time it happened to me, I questioned the other party on the line, and they said "I heard one buzz for about half a second". (They were on a land-line, so it eliminates their end of the connection as the source of the trouble.)
That's a little bit bizarre if they heard the first of the two vibrations on my Eris - it means my Eris had decided that the call had terminated even though it had not. That alone inclines me to believe it is a bug, not a feature.
bftb0
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
I'm running celb 2.1 and today made a phone call in a poor signal area and still made it all the way thru without dropping or anything is it a radio problem per chance?
tburns said:
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
That's exactly why I think it is a problem with the current batch of developer 2.2 (Froyo) ROMs.
As I said, I don't make that many calls, so I don't really know how often it happens - but given that it has happened to me a couple of times now (given the small amount of calling that I do), it makes me think it is not just a signal reception issue.
Which ROM and Radio firmware are you using BTW?
I've used kaos for about a month and been on celb for almost a week and have not had such an issue. I use my phone frequently for work, too. I have had the current radio from the july update since a week after it was available.
Sent from my ERIS using XDA App
Bump.
We now have 15 people on XDA (in the Eris forums) reporting the symptom:
bftb0: Tazz V6; Kaos Froyo V29 [Froyo]
jrozga: (unknown) [Froyo]
carycooke: Tazz V8 [Froyo]
tburns: ??? [Froyo]
mcook1670: "All Froyo ROMs" [Froyo]
punkxdead: CELB [CyanogenMod]; CELB Froyo [Froyo]
Macrodroid: Kaos & Tazz [Froyo]
droiderisuser: ??? "2.1"
danwguy: CELB 2.7 cyamogenmod 5.0.8-DS firmware 2.1-update1 [CyanogenMod]
pablocasiano: WW4.6, KaosFroyo V29
crax0r: KaosFroyo V29
tjthebest: CELB 2.8-CM5.0.8
mistaj: CELB 2.8-CM5.0.8
npong: CELB 2.8-CM5.0.8
mflane: CELB 2.8-CM5.0.8
Some of them say "it happens all the time"
And 10 more people over in the AF Eris forum reporting the same oddity - on different Froyo/AOSP ROMs:
erisuser1: Tazz V6; Kaos Froyo V29 [Froyo]
snozzcumber: Kaos Froyo V?? [Froyo]
TJTHEBEST: CELB 2.9 [CyanogenMod]
MrBojenglz: Buufed v???
BlueDC2: CELB v?, Kaos V?
rick311:
BellaSkye: Kaos V32
Kaessa: Kaos V32
tpatnoe: Kaos V30
rc346: Kaos V34
funkyfender: "CM6"
john58543: KaosV30
So far, only one user has said "this also happened to me on a 2.1 ROM" - droiderisuser
[ Edit ]: At least two people have reported this on older radios, and and also on non-Froyo (but CyanogenMod ROMs)
If it happens to you, and you have the SDK set up on your PC, and it is convenient to do so, try to make a note of the time when it happens, and then when your call is complete, dump a "logcat" to your PC, and post up the log during that same minute here.
Code:
C:\blech> [B][COLOR=green]adb shell logcat > strange_call_reconnect.txt[/COLOR][/B]
[I](wait about 30 seconds and then hit ^C (Control-C) )[/I]
I've had it happen on all Froyo roms. I work for the FDOT so I'm on the highway 8 hours a day. I don't know if its the phone changing towers or what. I always have a good signal because the towers are next to the highway. Not sure what it is but its annoying
Sent from my ERIS using XDA App
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
bftb0 said:
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
Click to expand...
Click to collapse
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
punkxdead said:
I have had this problem with ErisLightningBolt and CELB Froyo, (and KaosFroyo when I tested it). I never had this issue in a Sense based ROM (PlainJane), only in the AOSP/Cyanogen based ROMs. I live in a city with great 3G coverage and never experience the issue while at home, however I travel alot for work. When driving through rural areas it happens to me all the time. My call "ends" screen goes away, phone beeps and vibrates (like when you end a call), audio drops out, 5 secs later, screen comes back, call resumes. The caller on the other end always assumes I had another call/call waiting beep, etc. I believe the phone is switching from 3G to 1x in the process causing this, but I can't be certain. I have been patiently searching/working to find a solution but to no avail. Just thought I'd post since I'm finally hearing of others with this issue.
Click to expand...
Click to collapse
Never happens to me, and I make phone calls about twice per day.
punkxdead,
Thank you for that detailed report. Very useful information
Turns out that TJTHEBEST from AndroidForums experienced the problem on 2.1 CELB, which is not Froyo - but I guess it is a CyanogenMod build. That further corroborates your experience.
So far, nobody has reported this in a Sense-based ROMs. I'm a little fuzzy on the genealogy of the kernels in the various roms, although I suppose the problem could also be occurring in "rild" or it's supporting libraries.
It's not a show stopper by any means, but it is annoying; it would be nice if we could figure out how to get it fixed, since it seems to appear in lots of different dev ROMs.
If you are able to do the 'logcat' thing to see if we can find some more info, please give it a try; I will do likewise.
bftb0
punkxdead said:
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
Click to expand...
Click to collapse
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Macrodroid said:
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
bftb0 said:
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
Click to expand...
Click to collapse
I'm not really sure what the network option really would do. I do know that froyo isn't an eris os, so maybe it's something related to how it interacts with our phones... Either way, i'm waiting to see if the bug comes back on home only. Still love froyo, regardless!
Sent from my Froyo Eris using XDA App
Not sure if this helps but I have an Eris and pre Froyo when I was using Plain Jane I believe it was not sure precisely but It was a 2.1 rom for sure I had this happened to me quite frequently. So I would assume it is not just a 2.2 issue.
What is the best nightly to use for CM 7? There are 9 now and I am running 4...
Any thoughts?
7 was best in my experience.
Well, it seems 8 and maybe 7 have wifi connectivity issues, and nightly 9 has calling issues (both directions are messed up, outgoing and incoming).
If you find a nightly that works, stick with it until there is a new version that fixes something you desperately need, otherwise you might end up worse on a new nightly than you were before on an old nightly.
Sent from my SGH-T959 using XDA App
geoffcorey said:
Well, it seems 8 and maybe 7 have wifi connectivity issues, and nightly 9 has calling issues (both directions are messed up, outgoing and incoming).
If you find a nightly that works, stick with it until there is a new version that fixes something you desperately need, otherwise you might end up worse on a new nightly than you were before on an old nightly.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
looks like I will be sticking with #4 then! thanks for your input. on #4 everything seems to be working fine... As far as I know...
idk i ran wifi all night last night last night on 7 partly to kill my batt for a recondition and partly to test the wifi issues i saw reported in the thread. i never had a disconnect once and had no issues letting the phone sleep for over an hour and picked right back up surfing as soon as i unlocked the screen. i couldn't seem to reproduce the wifi issues people were experiencing. also i've updated consecutive with every nightly until 9. once i realized calls were f'd up i went back to 7. 8 seemed to be worse on battery however i'm not comfortable blaming the nightly as i never conditioned and let it settle.
For me the only one that had issues was 9, I'm on 8 now and don't have any issues. There seem to be some people that have Wi-Fi issues on 7 and 8 but I have not. If 4 is working stay there and just read when the next one comes and see I'd there are major issues.
Sent from my CM7 Powered Vibrant
On 8 & happy
s15274n said:
On 8 & happy
Click to expand...
Click to collapse
Hmmm...
It looks like I will give 8 a try! lets see what happens! BTW Wicked good article on helping us noobs out! I liked it. lol
8 is great, especially battery wise. Though the call issue is still there (the mute/unmute one). Some running the same nightly don't have it though...
Be sure to flash gapps after 8.. Mine didn't stick around after updating to it.
Also, rom manager (premium maybe) has the option to send notification when there is a new nightly.
Running 8 and NO issues. Best nightly IMHO
Sent from my SGH-T959 using XDA Premium App
im gonna have to agree wit everyone and say #8
movieaddict said:
im gonna have to agree wit everyone and say #8
Click to expand...
Click to collapse
On #8 and no issues at the moment! Runs great!
Currently running 8...tried 7, 8 and 9.
Both 7 and 8 seemed to work ok wifi and all just shows roaming all the time, international roam and have to use wifi for data. Also get the bug of incoming callers not hearing me well...outgoing seem fine though.
9 actually connected to Edge and could use data, but no calling in or out.
I'm sticking with 8 right now. I haven't had any issues with it so far and I flashed it when it was released.
#8 didn't run any videos for me which I found annoying as hell! Also it seemed to break down over time for me. It started out fine and over time things stopped working and it became glitchy I didn't have that problem to I moved up to 8 though. I actually ended up leaving CM7 all together. I found it not stable enough to do normal everyday stuff on.
Sent from my SGH-T959 using XDA App
now im on MIUI1.5.20~
anyone tried nightly 10 or 11? i want to know if i should update or stick with 8 for now
Stick with 8 for now. The rest still suffer from the same call issue.
s15274n said:
Be sure to flash gapps after 8.. Mine didn't stick around after updating to it.
Also, rom manager (premium maybe) has the option to send notification when there is a new nightly.
Click to expand...
Click to collapse
Be weary of new nightlies--the vibrant is still pretty experimental with CM7. It is not nearly as stable as the N1 nightlies tend to be.
Okay, this is potentially a really stupid question...but here goes.
I'd installed CM7.1 on my Fascinate as soon as I got it (was running a Vibrant with CM7) and immediately started seeing the weird issues like:
-data connection disappearing
-"double ring"...ringer ringing away during a call, requiring an end and re-dial to have a clean conversation
-call volume being ear-piercingly loud
As a result, I've started ROM hopping. However, the ROMs I've tried all seem to have the same issues.
Not trying to flame anyone, or bag on any of the ROM authors/maintainers, but are all the Fascinate ROMs out there a copy/modification of the CM ROM? Or are these issues I'm seeing (as others are too) a common failing of anything other than the stock ROM that came on the phone?
im running cm7.1 and have none of those issues.
What modem do you have? The ringing you are experiencing is called the phantom ring. I thought it was a known issue in all mtd roms, but I haven't used one in awhile. I remember having the call volume the same way. You have to press vol down once.
Sent from my SCH-I500 using XDA App
droidstyle said:
im running cm7.1 and have none of those issues.
Click to expand...
Click to collapse
I was running pool party and loved it except the WiFi kept dropping. I need a reliable network connection. I would have continued using it if not for that. TSM resurrection has been my more stable second choice.
Sent from my SCH-I500 using xda premium
uzumaki82 said:
What modem do you have?
Click to expand...
Click to collapse
I flashed Evil Fascinate over the weekend and I'm running DL09.
However, this doesn't answer the deeper question as to if the issues I saw in CM7.1 are pervasive in the other ROMs for this phone, as I've already experienced them in Evil, and it's been three days in use.
I'm not sure if I should simply accept the issues and find a ROM that I like, or if there's a different ROM out there that doesn't have the CM7.1 issues.
I am having the issues with the volume but, pressing volume up or down works to clear that up. I have also gotten complaints of the other end having an echo. This is on all calls with multiple carriers from other people. Anyone having this issue as well and know how it can be resolved? It doesn't echo on my end. Just the person I am talking too. Also I am running modem Baseband EDO5. I was running EBO1 and still have the same issues with each. I have tried MIUI as well and still the same. I flashed to stock fascinate as if you were to get it from Verizon and all of that seemed to go away. When I flashed back to CM 7.1 all of these issues arose again.
thedoman said:
I was running pool party and loved it except the WiFi kept dropping. I need a reliable network connection. I would have continued using it if not for that. TSM resurrection has been my more stable second choice.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
my wifi never drops...sometimes I have to toggle it off/on after a reboot but thats it.
I have had that problem on all my android devices that I have had. Sometimes hardware just freezes up and you have to do a reboot. They are basically little computers anyway but, if you are constantly having to reboot to get something to work. It is more than likely a problem with the mod.
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
alphax_0 said:
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
Click to expand...
Click to collapse
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
droidstyle said:
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
Click to expand...
Click to collapse
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
I see. It's just sometimes my 3g/wifi will be colored and still won't be receiving signal every so often even when I disable the other data method. Oh well
sendan said:
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
Click to expand...
Click to collapse
same here...but quite a few report the same issue as op. I seen a post where chopper said to only leave one on or the other. just passing the info along.
Hmmm, it may have to do with the radio. I've seen a few people mention that the handoff is better with the eh03 radio; coincidentally that's what I've been using since I came back to MTD.
Sent from my SCH-I500 using xda premium
i'm curious what is worse with the missed call bug.
I am talking about when people call, are phones don't even ring or show a missed call.
I have a new job that is a on call job and 3 times already within 5 days my phone didn't ring when i was called. and as anyone can expect that doesnt look good to the employer
I will be replacing my fascinate soon with a bionic but until friday i must try to make this work if anyone can point me in the direction for the rom that this bug doesnt affect as bad. thanks.
darkmage1991 said:
i'm curious what is worse with the missed call bug.
I am talking about when people call, are phones don't even ring or show a missed call.
I have a new job that is a on call job and 3 times already within 5 days my phone didn't ring when i was called. and as anyone can expect that doesnt look good to the employer
I will be replacing my fascinate soon with a bionic but until friday i must try to make this work if anyone can point me in the direction for the rom that this bug doesnt affect as bad. thanks.
Click to expand...
Click to collapse
I too have a job that requires me to be on-call so I fully understand the importance of your question.
I had the missed call bugs a handful of times back before the ed05 over the air update was released but have not had a single problem, that I know of, since then. I am currently running AOKP M4 rom with glitch kernel and the eh03 radio.
So, what rom are you currently using?
Sent from my SCH-I500 using XDA
Sry for taking long for a reply been in the mountains with no signal working. But I'm on stock eh03 with root and kgb kernel.
I generally don't care for aosp on the fascinate due too data drop a lot but if it isn't as effected by the missed call bug ill use it.
Sent from my SCH-I500 using Tapatalk