Related
Hello,
I'm using the latest Google Maps version on my Nexus One. I regularly get a message saying "Memory is Low, Traffic is disabled".
This is quite odd because I quickly go into my memory manager and see that in this case (and 2 others since Sunday), there are about 210 MB of RAM available.
Anyone else experiencing this?
I'm seeing the same thing on my Evo running cyanogenmod 6.0. Sometimes it happens at all zoom levels, sometimes not all for several days. I can't pin it down. Restarting doesn't seem to help either, & I have the maps update from several days ago installed. I haven't tried flashing back to a Sense ROM, though.
I haven't seen much talk of the problem on google looking back several months.
Setting the VM heap size back to 24m fixed this for me on my N1 running CM6 final.
It's in Settings > CyanogenMod Settings > Performance Settings.
Thanks, dlee. I reduced the heap size from 32 & rebooted, but I still have the problem. Traffic is almost unusable. It will sometimes be ok for a minute, but once it happens the first time, it then happens again within seconds. I haven't tried flashing a nightly since I don't want to worry about backing up and redoing settings. I don't recall ever seeing this on a sense ROM, but I updated my google maps around the time I installed CM6. I'll try flashing back and checking again.
UPDATE: Same thing running Vaelpak sense ROM. Turning on the terrain layer seems to make it happen more quickly.
Samsung Galaxy S I9000 original IRD now with JPY 2.2.1 XEU Rooted with super one click. No lag fix
Few days ago it got slow, laggy, choppy. Especially in the market. As it got out of battery and wouldn't boot up anymore. Just kept vibrating once in a while with buttons light on. I could get past the boot screen but then screen black + occasional vibrates + buttons lit on.
I did a factory reset since recovery worked and seemed fine.
Now it rebooted again after installing an app (maps + csipsimple)
I tried to run games that worked a day earlier. Now they just closed with the annoying vibrate sound would describe it as "vibra....(pause) .... vibr vibr vibr"
(This sound I have till now in NFS shift, but since more ppl are saying it doesnt work on SGS I didnt thought it might be relevant)
Reinstalling app helped. These I did so far
Ninjump works after reinstall
ShootU! doesnt work after reinstall... just shows some strange screen, but doesnt vibra close anymore
Worms works after reinstall
Any help? I mean is there something I should do, try ?
I think there was some threads about internal memory corruption. And I think I wrote to them too. Could this be it?
Hi people!
On my Galaxy S i9000 I have on Juwe 5.3 (JVR) with Semaphore 1.6.0.
I have the following problem: my GPS works (good accuracy and locking speed) only when the screen is on. As soon as the screen goes off, I lose the fix and precision, while using tracking apps like Runkeeper or My Tracks and diagnostic ones like GPS Status.
I've tried to force the CPU on 1000 MHz with Voltage Control but the problem remains so I'm guessing it's not a performance issue.
Any ideas?
Everything else works fine.
Thanks!
The same happens on my phone (albeit w/ CM7), but I don't mind, since that would eat the battery. I can see how that would render certain apps useless, though. I've used a few ROMs in my day, and never noticed GPS staying locked while the screen was off. I'm interested in how you'd achieve this as well.
Hi.
Yes in fact when I was on stock the gps worked as expected but I was on froyo.
Than I updated to a beta GB and then to Juwe.
I'd prefer not to put a froyo rom just to test if possible. I'll wait for someone to come with some idea
Thanks!
Some updates:
- It seems not to be kernel releated (tried with both semaphore and CF-Root, will try also TalonDEV)
- Not rom releated also (from Juwe JVR to Simplicity JVT, passing thru stock JVT).
Any ideas?
Is there someone whose GPS stays locked even if the screen is off?
Thanks.
Interested as well. Anyone?
Hmm, my gps would always lose lock if i turned off screen (froyo too).. thought that was normal behaviour
i thought that depends on the app. navigon has a setting which says to keep gps on or off when minimised.
oswade said:
i thought that depends on the app. navigon has a setting which says to keep gps on or off when minimised.
Click to expand...
Click to collapse
Probably this is right. Should be app-related.
I used to have a lot of GPS problems, but I solved them connecting GPS for the first time with WiFi on google maps, after that, GPs worked great without wifi being necessary anymore.
gtluis said:
Probably this is right. Should be app-related.
I used to have a lot of GPS problems, but I solved them connecting GPS for the first time with WiFi on google maps, after that, GPs worked great without wifi being necessary anymore.
Click to expand...
Click to collapse
I will try that.
It seems that also other phones are affected by this problem/feature, after the update to Gingerbread.
Little update: the navigation app does not let the screen to turn off to not to lose gps fix.
Sent from my GT-I9000 using XDA App
I bought a Nexus One off of craigslist on Monday for $30. It looks a little beat up, but almost everything works on it (bluetooth, wifi, GPS, battery). I bought it mostly so I can use it as a 32 GB (w/ microSD) bluetooth player in the car, and just to have a piece of Google and Android history.
However, as the title states, it will reboot and get stuck in a bootloop, eventually vibrating 7 times and getting stuck on the X screen afterwards if I make it do too much. Sometimes it'll happen if I install too many applications at once, or even if I'm playing music and charging it at the same time. Using Google, I found that this is a relatively common problem with N1s, where overheating can make it restart. I have Evervolv's ICS rom running on it, and have it underclocked to 650 MHz, with the scaling set to 'powersave.'
Are there any other things I can do to make it run a little faster without causing it to reboot? Maybe underclocking or flashing a different ROM? There was a CM7 ROM on it before, with the same rebooting issue.
ben9322 said:
I bought a Nexus One off of craigslist on Monday for $30. It looks a little beat up, but almost everything works on it (bluetooth, wifi, GPS, battery). I bought it mostly so I can use it as a 32 GB (w/ microSD) bluetooth player in the car, and just to have a piece of Google and Android history.
However, as the title states, it will reboot and get stuck in a bootloop, eventually vibrating 7 times and getting stuck on the X screen afterwards if I make it do too much. Sometimes it'll happen if I install too many applications at once, or even if I'm playing music and charging it at the same time. Using Google, I found that this is a relatively common problem with N1s, where overheating can make it restart. I have Evervolv's ICS rom running on it, and have it underclocked to 650 MHz, with the scaling set to 'powersave.'
Are there any other things I can do to make it run a little faster without causing it to reboot? Maybe underclocking or flashing a different ROM? There was a CM7 ROM on it before, with the same rebooting issue.
Click to expand...
Click to collapse
Vibrating 7 times is the hardware issue. You might want to research the Nexus One forum for more information.
So I really only use my tablet to view pdf documents so no intensive gaming or anything. So recently my tablet has been crashing randomly, showing these multicolour bars down the whole screen and after about 15 seconds it shuts itself off. After it shut itself down I am able to turn it back on and it runs normally again. I have no idea why this is happening and I am unsure whether it is a hardware problem or software. This happens everyday I use my tablet. I am running the teclast ROM that was installed when it arrived. I have never changed ROM's but I am willing to do it if it will fix this problem. Also I have never flashed an android device before so a noob friendly tutorial would be really helpful.
EDIT: Here are pictures of my tablet crashing, any help would be appreciated
imgur.com/a/wtgox
I got the same problem since I bought it a few months ago man, nobody could help me back then and thus my tablet is in gathering dust here ... I hope someone can fix it
rekopel said:
I got the same problem since I bought it a few months ago man, nobody could help me back then and thus my tablet is in gathering dust here ... I hope someone can fix it
Click to expand...
Click to collapse
Have you tried changing the ROM?
I have the same problem. Flashed different roms including dualboot windows 10 (I have 32 gb version) but it's still crashes everywhere. Be careful if you want to install another roms, it can crash during the flashing (mine crashed when I was installing windows 10 for the first time). Also it looks like the tablet works fine after powering it off properly and charging for some time. It also not crashes if it's charging constantly. Can't find any other fixes unfortunately.
CensoReDdD said:
I have the same problem. Flashed different roms including dualboot windows 10 (I have 32 gb version) but it's still crashes everywhere. Be careful if you want to install another roms, it can crash during the flashing (mine crashed when I was installing windows 10 for the first time). Also it looks like the tablet works fine after powering it off properly and charging for some time. It also not crashes if it's charging constantly. Can't find any other fixes unfortunately.
Click to expand...
Click to collapse
Thanks for the reply! I will try powering it off and charging it completely but I am not very hopeful.
For my tablet I still find it crashes even when charging so that does not work for me
I also have the same problem... did someone find a solution until now?
Bump
---------- Post added at 07:04 AM ---------- Previous post was at 06:40 AM ----------
Presumably this is a hardware problem although the stripes alternate 'good' / 'bad' with each crash (first stripe normal, next stripe corrupt then the next crash the first stripe is corrupt, next stripe is normal) and it happens both portrait and landscape. It is also becoming more frequent - used to be every 2 hours; now every 10 minutes. But I like this tablet with the cut down google ROM. What would be a good alternative in today's market - x98 air ii ?