I'm having trouble with the stocks tab on my HD2. The historical graphs show only the future now, and are flat as a result. For instance, the yearly graph starts in November and extends into 2012. The line is flat.
Does anyone have an idea as to how to fix this?
Same problem here, but no solution
same problem. i think its affecting everyone cause the website that the data is pulled from has probably changed. i find that i only get the line graph when using 1 day and 5 day charts .. anything more than that now returns a flat line.
this sucks ass
same prob..
Nothing new on this?
suggs said:
Nothing new on this?
Click to expand...
Click to collapse
I'm afraid not. The application has worked correctly once since I noticed the problem. I think it's another dead tab.
It works again!!!
DrATty said:
I'm afraid not. The application has worked correctly once since I noticed the problem. I think it's another dead tab.
Click to expand...
Click to collapse
Hi, I have just noticed that the Stocks Tab works again and the charts are updating correctly. Straight line is gone
I've just checked and some of my stock graphs appear to be working. Some are still a mess though, and others show nothing at all. The graphs are blank for some entries.
I've found that Sense crashes after viewing my graphs now. This didn't happen before. Has anyone else noticed this?
DrATty said:
I've just checked and some of my stock graphs appear to be working. Some are still a mess though, and others show nothing at all. The graphs are blank for some entries.
I've found that Sense crashes after viewing my graphs now. This didn't happen before. Has anyone else noticed this?
Click to expand...
Click to collapse
I set the stocks tab to check currencies, it's
monthes since the graphs issue appeared on my device, firstly all graphs did not work, after some time only the "5 days" one didn't and caused the device freezing.. and so it's still (tested on different ROMs)
tried this app http://forum.xda-developers.com/showthread.php?t=767688 that is a porting of htc stocks tab and it works correctly (at least with currencies)... so why htc's tab still crashes on "5 days" graph?
Related
Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....
Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.
hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..
screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)
bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?
screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.
Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.
I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.
Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates
Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.
I've owned my Rogers Dream (rooted, no custom ROM) for a couple of weeks now - this bug has been around since the start but it's getting worse these days and it's really starting to bother me.
Basically what happens is I'll get the notification for a text message. I can see the summary in the notification bar (with the new message), but when i open a messaging app (the default one or Chomp) the message won't be there. SMS Popup will also just display the previously most recent SMS in the conversation.
It seems like the system just isn't saving the message. Besides for the notification (which disappears after i clear), it's as if I never got the message. It kind of sucks...
My searching skills came up with nothing so i'm wondering - has this happened to anyone else - any idea what the reason could be - please let me fix this.
Thanks!
Well blyn100, interesting you should point this flaw out. I have a similar issue, but so far only 1 contact has given me this same summary with no msg. Trying to figure out the source of this problem, right now I have one suspicion. A few times, i think i received these msg's after being in a no service area. I am curious if this might be a possibility for you?
Also, I have similar phone setup as you, ie same stock Rogers ROM, obviously since no choice...yet.
i have the same issue
i had a thread started, but no response yet as to how to fix this
http://forum.xda-developers.com/showthread.php?t=542178&highlight=SMS+issue
but now it seems like more and more ppl are having this issue (or it is more apparent)
its the same with Chomp, handcent, even the native app
Looks like this is mostly just a Rogers issue then?
Most of mine are occuring when I have pretty good reception, so I think i can confirm that that's not it.
Proccessor usage / avaiable RAM is what I'm leaning towards though. I might try uninstalling the virtual keyboard to free up some RAM and see if it helps anything.
Or just a bug in the stock ROM. Seems like for this to happen, the network is sending the message to the device and the device just forgets to save it, but confirms to the network that it got it. Still, i have a hard time believing a problem like this would suddenly appear for the Rogers build.
I had like 3 dropped ones last night, it's starting to get really annoying.
Are you sure it's not the timestamp bug? Look further up in your conversation to see if SMS' have been inserted there.
hellfenix said:
Are you sure it's not the timestamp bug? Look further up in your conversation to see if SMS' have been inserted there.
Click to expand...
Click to collapse
Yup, i checked all of the conversations, this isn't the case for any of them.
I had this issue on my T-Mobile G1 with the Rogers' ROMs. But I haven't had issues with Cyanogen builds...
Hello,
quite suddenly, my GPS signal got instable. It happens in several software programs so it really seems to be the signal that is not correct. It gets a fix quite easily, but position is off mucht of the time, and also the direction and alitude are wrong. I attached a profile recorded during a car ride, here in Holland everything is flat, the profile should have been around 0m height all the time. But you can see it goes from -180m to +20m. Everytime when there is a jump, there is also a jump in the location. Before I do a hard reset I wanted to check if this has happened to anyone else before?
Also, I ran Android before, but the swtiching back and forth has not given this issue before.
I can confirm that the GPS time is exactly 2 hours behind !
Edit:
also the direction and Altitude are different from the "Navigon" (native device)
GPS uses now UTC-1 as Timezone ??
It was previously UTC+1 Timezone
15MA1L said:
I can confirm that the GPS time is exactly 2 hours behind !
Edit:
also the direction and Altitude are different from the "Navigon" (native device)
GPS uses now UTC-1 as Timezone ??
It was previously UTC+1 Timezone
Click to expand...
Click to collapse
what does this help me with my problem?
pwel said:
Before I do a hard reset I wanted to check if this has happened to anyone else before?
Click to expand...
Click to collapse
You asked I answered , now you see you're not the only one with this problem
You're welcome!
Hard reset also does not solve the problem. One thing is clear that the bug is in the android, in determining UTC "only one row of letters" (the code) must be changed: that GPS should use local system time and everything will work correctly, however I am not so talented to get it solved.
15MA1L said:
You asked I answered , now you see you're not the only one with this problem
You're welcome!
Hard reset also does not solve the problem. One thing is clear that the bug is in the android, in determining UTC "only one row of letters" (the code) must be changed: that GPS should use local system time and everything will work correctly, however I am not so talented to get it solved.
Click to expand...
Click to collapse
I still don't understand why the time is the problem. I think it is normal that in western europe, the time is UTC+2 in summer and UTC+1 in winter. So to me this looks normal. If I look at the raw track file, the time stamp for each line is ok, but the position/altitude info is unstable. But today, everything was fine again. So I get lost a bit, and I will keep a track on what happens and record it here again.
pwel said:
I still don't understand why the time is the problem. I think it is normal that in western europe, the time is UTC+2 in summer and UTC+1 in winter. So to me this looks normal. If I look at the raw track file, the time stamp for each line is ok, but the position/altitude info is unstable. But today, everything was fine again. So I get lost a bit, and I will keep a track on what happens and record it here again.
Click to expand...
Click to collapse
Just finished a 500km trip. No issue at all! So it seems to have been a temporary problem
i have no gps signal. it does not work. never!
what can i do?
ninnitto said:
i have no gps signal. it does not work. never!
what can i do?
Click to expand...
Click to collapse
if you have used android read the forum or use search
if you didn't go with your phone in service
I havent used my KF for like 1 month, so yesterday I charged it and Flashed "Energy CM9 ROM" (if that matters at all...) and then after a couple of minutes I noticed that the screen is acting weird I dont know if this behavior haves a name or whatever, anyways here what it does. It keeps like a "shadow" of what ever was being displayed before, Ex. If Im on the home screens and I have the clock widget and a few apps icons and I move to the 2nd screen which its empty, I can see what was on screen 1, it stays there for a couple of minutes till it disappears slowly.
Is this normal ? is this the ROM? (I doubt it but I'll still ask...) To me it seems like some sort of hardware problems. Any Ideas or advice?
Thanks
BTW: I can try to take pics if you guys dont understand me...
I have heard of this ghosting happening to varying degrees even with the stock rom. Its visibility depends on what you have displayed, so you may have had it before but never had the opportunity to observe it. I see it once in a while but it's very faint; others have had it happen badly enough that it can be photographed, and some people have returned their Fire and gotten a new one without the issue.
So it probably depends on the exact batch of screen you have.
I've seen a few comments on other threads where this is an issue. Some suggested doing a factory reset and wiping your caches before flashing the rom. Are you sure you got the most up to date rom as well.
hello,
as the title says, i get these notifications all day long..
they appear for half a second and are gone before i can click on them.
the attached notification log shows that they pop up in irregular intervals, sometimes several times a minute.
i tried to disconnect and reset the watch, but the issue remains.
the problem came up just recently, but i didn't notice any updates.
any ideas what i can do?
watch: misfit vapor (fossil brand), android 8.0, wear os 1.5 (idk why it's not labled 2.something anymore, but it's definitely not the old 1.5 without playstore and so on..)
phone: sony xperia x compact, android 8.0
seems like a secomd reset made it a bit better.. now i get the notifications about 20 times a day..
what can that be? how often is normal?
could someone please check his log?
to get access you might have to enable developer options, then place a homescreen widget for settings -> notifications log
nobody?
xda isn't what it used to be...
I noticed the same. I belive it started after recent update of Google Wear.
I just installed Notification Saver app (my phone does not have notifation log option) and will revert back once I collect some information...
armsel said:
...will revert back once I collect some information...
Click to expand...
Click to collapse
Yeh, it is checking a lot sometimes, sometimes not that much (6 times a day yesterday!).
But today a lot more (attached picture)!
This is not normal...
thanks for the info, so it's a google problem.
i reported it now via the feedback button in the wear os app and i suggest you do the same.
hopefully they fix this soon..
A.D.I.O.S said:
thanks for the info, so it's a google problem.
i reported it now via the feedback button in the wear os app and i suggest you do the same.
hopefully they fix this soon..
Click to expand...
Click to collapse
I just did - although today it had only checked twice (so far), let's see...
yesterday i had about 70 checks..
it's so annoying an i think it's also draining the battery..
how about you @armsel ? problem still present? did you hear anything from google?
A.D.I.O.S said:
yesterday i had about 70 checks..
it's so annoying an i think it's also draining the battery..
how about you @armsel ? problem still present? did you hear anything from google?
Click to expand...
Click to collapse
Nope, noting and I don't think they will ever revert back...
I didn't use my watch the past week or so... let me see next week if the problem persists.
just updated to wear os 2.0..
still the same..