Jump to content

EVO 4G LTE Android Jelly Bean Update 3.15.651.16


wjrandon

Recommended Posts

I did the factory reset and reloaded everything. It runs better for the most part, however the ram being used is ridiculously high. i don't know about anyone else, but on the stock reboot with nothing installed it ran at 800+MB according to the task manager and with all of my programs loaded it is nearly .9 GB. I recall before the update that i would barely peak at .50GB with an average of .30 GB.

Maybe someone can explain this to me, but it seems like something has become a memory hog.

Outside of that the other issue i have is swype not putting spaces in google searches and some other random areas. it has auto spacing checked and works fine in other apps.

I do like the music controls in the drop down menu, and the increased volume from the beats audio.

Link to comment
Share on other sites

So my launcher has been running really slow and choppy every now and then on my EVO lately. Mine has done it about 3 times in the past week or so and the only remedy is to reboot my phone. Maybe its an app that I have installed recently or just could it just be a bug in Sense? Has anybody seen anything like this on their device after updating to JB?

 

I think I found one cause of this. I was able to trigger it by starting an OpenSignal Maps speed test and pressing the back button before it finished.

 

Sent from my EVO using Tapatalk 2

 

 

Link to comment
Share on other sites

I did the factory reset and reloaded everything. It runs better for the most part, however the ram being used is ridiculously high. i don't know about anyone else, but on the stock reboot with nothing installed it ran at 800+MB according to the task manager and with all of my programs loaded it is nearly .9 GB. I recall before the update that i would barely peak at .50GB with an average of .30 GB.

Maybe someone can explain this to me, but it seems like something has become a memory hog.

Outside of that the other issue i have is swype not putting spaces in google searches and some other random areas. it has auto spacing checked and works fine in other apps.

I do like the music controls in the drop down menu, and the increased volume from the beats audio.

 

There also used to be a pretty noticeable "hissing" sound when you used to use beats audio that appears to be improved a lot.

Link to comment
Share on other sites

I've had high RAM usage as well, but JB has managed it well so I haven't had any performance issues.

 

I think too many people put a little too much emphasis on ram usage, not realizing how android's memory management works.

  • Like 4
Link to comment
Share on other sites

 

I think too many people put a little too much emphasis on ram usage, not realizing how android's memory management works.

 

Smart man. Glad someone said it.

 

Sent from my rooted LTEVO running CM10.

 

 

  • Like 3
Link to comment
Share on other sites

I've never worried about RAM either, and every time I have, whether its with some app killer app or whatever, it just causes problems. I wouldn't get fixated on some number/spec, just let Android do its thing. Can't say I've ever had an issue due to RAM. And that dates back to Eclair.

 

Slightly off topic but, in Phx we've been having some very cold weather, by our standards anyway, with lows of about 29 the last couple days. I went on a hike at 0530, went to take a picture, and noticed a message pop up at the bottom of the screen saying something to the effect of, Flash is disabled due to cold temperature. First time I've seen that! I'm sure its not a discovery, but just throwing it out there. It was certainly new to me.

 

Also, I've hiked this trail just north of Phx numerous times, but have taken a 3 or 4 month hiatus from it. I used get very poor Sprint signal on the back side of the mountain, if any. Roaming was pretty iffy as well. Streaming Google Music was out of the question. Today I noticed I had strong Sprint signal the entire time. It was brought to my attention when I noticed that I could stream Google Music the entire hike, whereas before I definitely could not. Not sure If Sprint put up a new tower in the area, or fixed something on an old one. But, major signal improvement.. it was cool!

  • Like 3
Link to comment
Share on other sites

I've never worried about RAM either, and every time I have, whether its with some app killer app or whatever, it just causes problems. I wouldn't get fixated on some number/spec, just let Android do its thing. Can't say I've ever had an issue due to RAM. And that dates back to Eclair.

 

Slightly off topic but, in Phx we've been having some very cold weather, by our standards anyway, with lows of about 29 the last couple days. I went on a hike at 0530, went to take a picture, and noticed a message pop up at the bottom of the screen saying something to the effect of, Flash is disabled due to cold temperature. First time I've seen that! I'm sure its not a discovery, but just throwing it out there. It was certainly new to me.

 

Also, I've hiked this trail just north of Phx numerous times, but have taken a 3 or 4 month hiatus from it. I used get very poor Sprint signal on the back side of the mountain, if any. Roaming was pretty iffy as well. Streaming Google Music was out of the question. Today I noticed I had strong Sprint signal the entire time. It was brought to my attention when I noticed that I could stream Google Music the entire hike, whereas before I definitely could not. Not sure If Sprint put up a new tower in the area, or fixed something on an old one. But, major signal improvement.. it was cool!

 

Quite odd. Wonder if the cold was affecting the tower at that time.

Link to comment
Share on other sites

 

Slightly off topic but, in Phx we've been having some very cold weather, by our standards anyway, with lows of about 29 the last couple days. I went on a hike at 0530, went to take a picture, and noticed a message pop up at the bottom of the screen saying something to the effect of, Flash is disabled due to cold temperature. First time I've seen that! I'm sure its not a discovery, but just throwing it out there. It was certainly new to me.

 

 

That's a new one to me... It was 9° outside last night, and I was using my phone to take pictures of the ice and frost on trees and such, my EVO didn't complain. Though I was only outside for about 20 minutes or so.

Link to comment
Share on other sites

I've never worried about RAM either, and every time I have, whether its with some app killer app or whatever, it just causes problems. I wouldn't get fixated on some number/spec, just let Android do its thing. Can't say I've ever had an issue due to RAM. And that dates back to Eclair.

 

Slightly off topic but, in Phx we've been having some very cold weather, by our standards anyway, with lows of about 29 the last couple days. I went on a hike at 0530, went to take a picture, and noticed a message pop up at the bottom of the screen saying something to the effect of, Flash is disabled due to cold temperature. First time I've seen that! I'm sure its not a discovery, but just throwing it out there. It was certainly new to me.

 

Also, I've hiked this trail just north of Phx numerous times, but have taken a 3 or 4 month hiatus from it. I used get very poor Sprint signal on the back side of the mountain, if any. Roaming was pretty iffy as well. Streaming Google Music was out of the question. Today I noticed I had strong Sprint signal the entire time. It was brought to my attention when I noticed that I could stream Google Music the entire hike, whereas before I definitely could not. Not sure If Sprint put up a new tower in the area, or fixed something on an old one. But, major signal improvement.. it was cool!

 

That's too funny. Even your devices get thin blood and wimpy down there. :lol:

 

I took a picture this morning with my Galaxy Note 2 and it was 7 degrees below zero. However, it wasn't outside for very long when I took the pic. I promptly found warmer environs.

 

Robert

  • Like 2
Link to comment
Share on other sites

That's too funny. Even your devices get thin blood and wimpy down there. :lol:

 

I took a picture this morning with my Galaxy Note 2 and it was 7 degrees below zero. However, it wasn't outside for very long when I took the pic. I promptly found warmer environs.

 

Robert

 

7 below? Wow. I haven't been in below zero conditions for a couple years. I did camp in 6 below once, that was an interesting.... experience. Wonder if my EVO would have complained about that? Haha

Link to comment
Share on other sites

7 below? Wow. I haven't been in below zero conditions for a couple years. I did camp in 6 below once, that was an interesting.... experience. Wonder if my EVO would have complained about that? Haha

 

Sub zero temperatures are common at our elevation. Happens every year. Our normal low is typically high single digits in January and February.

 

Robert

Link to comment
Share on other sites

Sub zero temperatures are common at our elevation. Happens every year. Our normal low is typically high single digits in January and February.

 

Robert

 

It USED to be an every year occurrence around here, but we're on a multi year streak of not breaking 0. Record setting streak even. Coldest I've been in was 11 or 12 below in Colorado.

Link to comment
Share on other sites

That's a new one to me... It was 9° outside last night, and I was using my phone to take pictures of the ice and frost on trees and such, my EVO didn't complain. Though I was only outside for about 20 minutes or so.

That's too funny. Even your devices get thin blood and wimpy down there. :lol:

 

I took a picture this morning with my Galaxy Note 2 and it was 7 degrees below zero. However, it wasn't outside for very long when I took the pic. I promptly found warmer environs.

 

Robert

 

LOL

 

It would take pictures just fine... it was only the flash that was disabled. Similar to how the flash is disabled when the battery level is low.

Link to comment
Share on other sites

LOL

 

It would take pictures just fine... it was only the flash that was disabled. Similar to how the flash is disabled when the battery level is low.

 

I had my flash disabled when the phone got too hot once, lol. Anyone on the EVO LTE have that happen yet?

Link to comment
Share on other sites

 

Not I. I've never had my EVO get hot' date=' though.[/quote']

 

Car Dock + sunny summer day + black phone = overheat.

 

I haven't had that error since I started running the AC through the windshield vent when my phone is docked.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • I've now seen how things work in Kobe, Hiroshima, and Osaka, as well as some areas south of Osaka (e.g. Wakayama, Kinokawa), and tried three more SIMs. The two physical SIMs (different branding for each) both use IIJ, which provides a Japanese IP address/routing on NTT, aleit LTE-only, so latency is ~45ms to Tokyo. The catch with NTT is that it uses two frequency bands (B42/3500 MHz LTE, n79/4900 MHz NR) that you're not going to get on an Android sold in the US, and I'm guessing that B42 would be helpful speed-wise on that network, as it doesn't have B41. I also found one place that doesn't have cell service: a vending machine in the back of the Osaka Castle tower. Or, rather, the B8/18/19 signal is weak enough there to be unusable. Going back to 5G for a moment, I saw a fair amount of Softbank n257 in Hiroshima, as well as in some train stations between Osaka and Kobe. 4x100 MHz bandwidth, anchored by B1/3/8, with speeds sometimes exceeding 400 Mbps on the US Mobile roaming eSIM. Not quite the speeds I've seen on mmW in the States, but I've probably been on mmW for more time over the past few days than I have in the US over the past year, so I'll take it. My fastest speed test was actually on SoftBank n77 though, with 100 MHz of that plus 10x10 B8 hitting ~700 Mbps down and ~80 Mbps up with ~100ms latency...on the roaming eSIM...on the 4th floor of the hotel near Shin-Kobe station. Guessing B8 was a DAS or small cell based on signal levels, and the n77 might have been (or was just a less-used sector of the site serving the train station). I'm now 99% sure that all three providers are running DSS on band 28, and I've seen 10x10 on similar frequencies from both NTT and SoftBank IIRC, on both LTE and 5G. I also picked up one more eSIM: my1010, which is different from 1010/csl used by US Mobile's eSIM unfortunately, as it's LTE-only. On the bright side, it's cheap (10GB/7 days is like $11, and 20GB for the same period would be around $15), and can use both KDDI and SoftBank LTE. It also egresses from Taiwan (Chunghwa Telecom), though latency isn't really any better than the Singapore based eSIMs. Tomorrow will include the most rural part of our journey, so we'll see how networks hold up there, and from tomorrow night on we'll be in Tokyo, so any further reports after that will be Tokyo-centric.
    • I think the push for them is adding US Mobile as a MVNO with a priority data plan.  Ultimately, making people more aware of priority would allow them (and other carriers) to differentiate themselves from MVNOs like Consumer Cellular that advertise the same coverage. n77 has dramatically reduced the need for priority service at Verizon where the mere functioning of your phone was in jeopardy a couple of years ago if you had a low priority plan like Red Pocket. Only have heard of problems with T-Mobile in parts of Los Angeles. AT&T fell in between. All had issues at large concerts and festivals, or sporting events if your carrier has no on-site rights. Edit: Dishes native 5g network has different issues: not enough sites, limited bandwidth. Higher priority would help a few. Truth is they can push phones to AT&T or T-Mobile.
    • Tracfone AT&T sims went from QCI 8 to 9 as well a couple years ago. I'm pretty neutral towards AT&T's turbo feature here, the only bad taste left was for those who had unadvertised QCI 7 a couple months ago moved down to 8. In my eyes it would have been a lot better for AT&T to include turbo in those Premium/Elite plans for free to keep them at QCI 7, while also introducing this turbo add on option for any other plans or devices. As it stands now only a handful of plans can add it, and only if you're using a device on a random list of devices AT&T considers to be 5G smartphones.
    • My Red Pocket AT&T GSMA account was dropped to QCI 9 about a year ago.  Most recently 8 for the last few years prior.  Voice remains at 5.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...