Related
I am experiencing my clock loses time when not connected to Power (from PC or the Charger); in just one hour approx. 30minutes?!
As soon as I connect to Power (and WiFi or Network enabled) then Auto sync sets the time correctly....
Also - if I turn the Legend totally Off then it'll pick up the correct time when turned On again (if Network enabled that is), but again it starts losing the time right away if Power is not applied.
And - just leaned I believe, that if I keep the screen from turning off it will also keep the time (to be tested further though).
It looks very much like the internal Clock for the Time-keeping (RTC) is reduced by 2 when it enters the different power saving modes; overnight it lost exactly 4 hours in 8 hours being turned Off....?! There seems to be a clear relationship between the power management of the Legend and the RTC/Time-keeping.....
Very annoying as my Legend was supposed to keep all my daily appointments
BUT all that said - I love the shape and looks and feel and the speed of the Legend
Anybody any clues - I would surely appreciate good advices as HTC have duck their heads?
Notes:
Nordic Region
Firmware: 2.1
Kernel: 2.6.29
SW Version: 1.23.405
Doesn't happen to me.
Perhaps if you could post your ROM version etc. it may be useful so that the peps here can counter-check.
I'm on Asian ROM btw.
I really wonder why there is none of such thread here!
Gingerbread unfortunately brought only bad things to my Nexus. I already forgot why I was so crazy about installing it.
What feature did it introduce again?
Okay the response is much better and everything seems faster...but with lots of bugs?
That screen off animation? Seriously?
Things that I hate now:
- Battery Time: this is bad, can't even run half a day with lot of usage, b
efore I could listen to mp3's one day, ie. more than 4 hours without any problems...now
- Camera: either Cam or Video, the application crashes after I take a photo or video and then I can not connect to it anymore
- Gallery: often crashes, especially if you have an online photo account connected
- unlock screen: I use a pattern, often there is no overlay of what pattern I drag, still the screen can be unlocked
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
- 3G and Wifi: if you are connected to wifi more than 15 minutes and then disconnect from it you do not get any 3G, you have to go to airplane mode and back, this bug appeared ages ago and was fixed, now back again...tells you a lot about their merging control, ie. sucks
- notification led: you know...
- apps: there are a lot of apps running even though I never used them since restart (see it in a task killer app)
- gps: on a random bases it tries to lock even though no app that uses gps is running
- phone reboot: it even rebooted without any notice two times since I installed it
(- Contacts: I still can't enter a simple thing like a birthday on an expensive phone like this)
MOD EDIT: Borderline trolling removed. If you switch OSes, that's your own choice. No one here is stopping you.
Got any troubles? Tell here.
DarsVaeda said:
1. Battery Time
2. Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
3. notification led: you know...
Click to expand...
Click to collapse
4. Blank keyboard- fixed by switching to another keyboard and back again, or a reset
5. Blank Launcher- fixed with reset
6. In the stock SMS app a long press>delete conversation doesn't always delete the selected conversation; sometimes you have to do it twice.
As far as battery goes, my display is still the thing that takes up the most battery (which is normal) but I had been experiencing severe declines in battery life. Does the switch to 32-bit color require more processing power and therefore battery?
I *#*#4636#*#*>phone information and saw it was set to WCDMA preferred. I remember playing with the option when froyo came out but didn't remember what it was set to (Maybe Gingerbread reset the option...?). I changed it to GSM PRL (Auto), and have experienced increases in battery life, as my phone isn't hunting for 3G all the time- it uses a service provided list of tower locations.
The LED REALLY bugs me.
Hate about Gingerbread
No trackball wake
Juice Defender Doesn't work (but Green Power does - works well but with less flexibility than JD)
Short battery life
Useless keyboard selection gimmicks
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
Click to expand...
Click to collapse
Well, glad to know mine isn't the only one that does this!!
On Froyo I would wake up in the morning to freshly updated apps that had updated automatically over night.
I have not had this happen a single time on Gingerbread, and nearly every time I go in to the market there are updates waiting.
What is the point of the automatic update feature when it doesn't work???
NexusDro said:
To be fair, the OP did mention about switching to Apple.
Click to expand...
Click to collapse
GldRush98 said:
Well, glad to know mine isn't the only one that does this!!
On Froyo I would wake up in the morning to freshly updated apps that had updated automatically over night.
I have not had this happen a single time on Gingerbread, and nearly every time I go in to the market there are updates waiting.
What is the point of the automatic update feature when it doesn't work???
Click to expand...
Click to collapse
auto update never worked for me, even in froyo.
-Battery with CM7 roms
-Trackball wake blocked in non-CM7 roms
-More difficult to mod themes like statusbar (before we just had to change a png and now we have to edit a bunch of files)
So in summary GB roms are still not stable and complete, they have either TB wake missing or poor battery life too
My annoying issues?
- 2 second mic mute after I answer a call
- stock launcher choking after a while
Less annoying ones:
- Market does not automatically update apps
- gps activations without an apparent reason
My annoyances
In no particular order:
The cursor select triangle not lining up with the cursor
Launcher unresponsive/vanishing
Lockscreen pattern not showing (as in the OP)
Phone randomly stays awake at night
GPS turns itself off
Not able to view an apps wakelock any more
USB mount screen shows 'turn off' even when it isn't mounted (UK issue)
USB debugging icon doesn't appear, or doesn't turn off depending on how you enabled it
Exchange push is just crap now, I swear it's getting worse by the day
DarsVaeda said:
- Battery Time: this is bad, can't even run half a day with lot of usage, b
efore I could listen to mp3's one day, ie. more than 4 hours without any problems...now
- Camera: either Cam or Video, the application crashes after I take a photo or video and then I can not connect to it anymore
- Gallery: often crashes, especially if you have an online photo account connected
- unlock screen: I use a pattern, often there is no overlay of what pattern I drag, still the screen can be unlocked
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
- 3G and Wifi: if you are connected to wifi more than 15 minutes and then disconnect from it you do not get any 3G, you have to go to airplane mode and back, this bug appeared ages ago and was fixed, now back again...tells you a lot about their merging control, ie. sucks
- notification led: you know...
- apps: there are a lot of apps running even though I never used them since restart (see it in a task killer app)
- gps: on a random bases it tries to lock even though no app that uses gps is running
- phone reboot: it even rebooted without any notice two times since I installed it
(- Contacts: I still can't enter a simple thing like a birthday on an expensive phone like this)
I think there is more if I think about it.
Seriously thinking about switching back.
Click to expand...
Click to collapse
While I'm not a big Gingerbread lover at all, here are answers to some of the points:
Battery time is fine, at least in freshly installed ROMs it far exceeds what Froyo mastered.
Camera is your own problem - you didn't update radio, or your update went bad.
Gallery never crashed - again, your own problem (you get the feeling now, right?).
3G and WiFi - again, your own problem. No bug.
Apps - and why do you care? Isn't the "DO NOT USE TASK KILLER" thread clear enough? 150-200MB free RAM aren't self-explanatory?
Due to your comments, you might really consider switching to Apple. It would be beneficial both for you and for this forum.
Or you could back up user data, wipe, install new radio and bootloader, load fresh Gingerbread ROM (NOT CM7 or CM7-based), and have most of your points addressed.
Now, having said that, if you want a much better overall feel - install Froyo-based Desire port, or if you don't have any use for Hotspot - DesireHD port. I hate using barebone Android after some experience with it.
have you guys heard about Cyanogenmod ROM? I am using CM7 RC4 and I have no problems that anyone mentioned in this thread....
Maybe you haven't heard that your experience not necessarily represents anything.
For me (and another 2 guys that asked me to reinstall other ROM on their Nexus Ones), CM7 was a huge, awful pile of bugs. Starting with the ill-famous "wonk".
Plus, again, after having some SenseUI I don't really want to go back to plain Android, and wouldn't suggest it to anyone looking for a good overall experience.
I have an occasional problem with the application tray where it stutters, flashes and doesn't scroll properly. It seems to happen only after exiting certain apps, and needs the launcher to be force closed to fix.
xxlikquidxx said:
have you guys heard about Cyanogenmod ROM? I am using CM7 RC4 and I have no problems that anyone mentioned in this thread....
Click to expand...
Click to collapse
Exactly my experience too. Absolutely brilliant ROM.
Jack_R1 said:
..after having some SenseUI I don't really want to go back to plain Android, and wouldn't suggest it to anyone looking for a good overall experience.
Click to expand...
Click to collapse
Just lost all credibility in my book...
I would suggest the OP decides what features he/she wants in a ROM and then try a few different ones out. There are plenty to cater to all tastes and i'm sure they'll be able to find one that works well for them.
1. exchange sync stops syncing without any reason. can't start a manual sync. only reboot of the phone helps for a short period of time. needs a fix very urgently.
2. TINY TINY notification icons...the worst idea google had for the GB update. i cannot see the difference between the gmail and exchange mail icon on normal usage in example.
There are some more points which i also mentioned in my blog about gingerbread for nexus one:
http://smartphoneblogging.com/2011/03/review-android-2-3-3-gingerbread-for-nexus-one/
Thread Cleaned
Let's play nicely in here and keep this on-topic. This is not the place to discuss other operating systems. This is about issues pertaining to the OTA Gingerbread updates.
Thanks,
Your loving moderator.
One bug and one annoying change:
- The instability of the launchers. I hope they address this.
- The inaccessible GPS toggle. Tasker can't access it and neither can the toggle widgets. Why did they change this?
my mms sometimes does not send if i configure 2 APNs (one for mobile data and one for mms), while i disable the one for mobile data...
it's working fine on Froyo and CM6 before
benjatt said:
- The inaccessible GPS toggle. Tasker can't access it and neither can the toggle widgets. Why did they change this?
Click to expand...
Click to collapse
QFT!!!!!!!!!!!!
Auto brightness adjustment no longer fades, now it just jump straight to the target brightness which is quite abrupt visually.
And of course... trackball wake is gone.
I concur with these points:
- Battery Time: this is bad, can't even run half a day
- Gallery: often crashes, especially if you have an online photo account connected
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
- GPS: on a random bases it tries to lock even though no app that uses gps is running
- Creating shortcuts on desktop: sometimes you can't drag/drop icons to the desktop or to a different spot on the desktop.
- The cursor select triangle not lining up with the cursor
- Auto brightness adjustment no longer fades, now it just jump straight to full bright or full dim.
As for the people suggesting we update the radio and try different roms, while that is primarily what this board is about, it doesn't "solve" anything. This is a stock Nexus One with official everything. If it doesn't work then it doesn't work.
First the tip: Don't use the "Show Station ID" option, it causes a massive battery usage.
Here are some numbers, with it turned on 4 hours of uninterrupted radio listening drains 36% of my battery. With it turned off the same 4 hours only drains 20% of my battery.
This is caused because with it turned on the phone never goes to sleep when the screen is off. When it is off the phone actually goes into deep sleep will still playing music which causes the drastic difference.
My numbers are based on 40 hours a week listening for 5 months of Station ID being turned on without thinking about it and getting a consistent 36%/4hr daily
Then I did my only factory reset when going to a ICS rom a couple weeks ago and not thinking to set it I started only losing 20%/4hr and noticed I was spending time in deep sleep.
It's great leaving work after a 8 hour day with a extra ~30% battery then I have been used to.
Actually that's not an accurate comparison seeing that you've switched roms.
Try to compare it now on your new rom so that the comparison is done on same roms.
But thanks for the info anyway.
I think this may be due to the HUGE number of messages written to logs when RDS is enabled. I see this with my FM app using the RDS in my app's Samsung FM API mode, and there's not too much I can do about it in that mode.
====
BTW, I very much need people with S2's to help me get my app working on stock or stock derived ROMs on which the stock FM app works. It works fine on Galaxy S for a while and probably just needs a tweak or 2. See my post here and respond via PM or on my thread, since it's Off Topic to this thread.
Except that... perhaps my app can use less power when in background or screen offm since it can turn the RDS off then.
bpivk said:
Actually that's not an accurate comparison seeing that you've switched roms.
Try to compare it now on your new rom so that the comparison is done on same roms.
But thanks for the info anyway.
Click to expand...
Click to collapse
I did a quick 1 hour test with it on and the numbers still match up. My phone lost 9/hr which does equal 36/4hr.
shadowofdarkness said:
I did a quick 1 hour test with it on and the numbers still match up. My phone lost 9/hr which does equal 36/4hr.
Click to expand...
Click to collapse
I'll run a test on my Galaxy S and I'd bet the same thing happens. I think a dozen or more log messages every second can do the battery in faster.
For you or anyone else looking to test my app, there's not much to it:
Feb 26 release on the Market: https://market.android.com/details?id=com.mikersmicros.fm
Possibly better Feb 28 release: http://www.mediafire.com/file/i5654nm9vzd9d9m/Spirit_FM_Radio_v120228.apk
Just ensure a wired headset is plugged in, install the app and run. If you are rooted you should deny SU when it starts. At the Intro screen, press "Disable".
Hopefully, it will "just work" at that point.
NOTE: I just realized now that if you give my app SU, it will not try the Samsung FM API, it will go straight to the low level mode which gives no audio on the GS2. So set Menu->Settings->Debug->FM API to "OEM Proprietary" to force use of the Samsung FM API. If this API fails, I think the app will fall back to the low level mode. That can be prevented by setting Debug->FM Chip to "TI" and if the OEM API fails, then power up will fail.
Working or not, please give SU to my app, restart the app and send me a debug log with Menu->Help->EM Logs. After a few seconds. enter "GS2" and/or any useful phone or ROM etc. information in the email text and press send.
Remember, this test request is for stock or stock derived ROMs that can run the stock FM app only.
My app has been running in a "low level device driver mode" for over 6 months now on rooted GS2s, but without audio, except I think on the MIUI ROM which supports the CyananogenMod audio method. I need no testing for this mode, unless you know how to enable the FM audio or want to try the different Audio Methods to see if any magically work.
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain
Hey all,
So I've had my S8 since launch and I've enjoyed it but I have an issue that I've been trying to pinpoint the cause of for a few weeks now. At a high level, if I reboot the phone in the morning, I can use it all day as I wish and it works perfectly, no slowdown anywhere and good battery life. I plug the phone in at night when I go to sleep and when I wake up I start using it again. Either right after I wake up or over the course of a few hours the phone begins to slow down with things like notification shade/app switcher crawling until I either a) reboot or b) change display resolution. Doing either of these "fixes" it until the next night and then again when I wake up I have the same issues.
I've been trying to figure out what's causing this. I've tried disabling features, uninstalling apps, etc.
One thing I have found is that when I'm having this problem if I force close 'System UI' in App Manager (this is just restarting that process since you can't kill it really) the smoothness comes back but it doesn't last as long as when I either reboot or change resolution.
My theory is that something is conflicting with the Android UI and over time it's causing it to slow down. Rebooting or changing display resolution restarts the Android UI so essentially same thing.
My first question is has anyone seen this behavior where the notification shade/app switcher (native UI not apps) slow down? I know there's at least some people on Reddit with same issue. If you have this issue does FC'ing System UI 'fix' it for you temporarily?
I'm trying to figure out what is running on my phone while I'm sleeping at night which is obviously causing this. Any ideas would be helpful. Oh also when I wake up and I go into app switcher it only shows like 3 cards where before I go to bed it would be like 10+ so something is killing apps at night too. I turned off Google backup for today and will reboot before tonight to see if maybe that's it.
Appreciate your help.
Thanks.
I've had my S8+ since the launch weekend on ATT, always connected to my Gear S3, and connected to my Misfit Ray. I've not noticed any slowdown of the UI. My AOD clock is slow to show the hands if the screen is off when I use the numerical clock AOD, but nothing else observed.
I would guess you've installed (or haven't uninstalled/disabled) some apps that are using a lot of background processes. I removed/disabled the few ATT apps on the device except Call Protect, and I don't use Gmail (resource hog). I actually use very few Google apps, they're just not very well coded, it seems (maybe a "goof off" day every week isn't such a great policy?)
In settings, go to Device maintenance, click on battery, and see if anything strange is going on there under App power monitor.
I've NEVER liked Samsung phones, and I've NEVER been interested in owning one, but I saw the Galaxy Gear S3 and fell in love, and truthfully, I bought the phone as an accessory to the watch, so I'm not an apologist for any shortcomings.
Instead of restarting, go to settings/device maintenance, what's the percentage here? go to optimize, does it help? which apps use the battery most? How much RAM is available. If nothing shows up, you probably would need something like wakelock detector (it needs root) to trace apps usage, especially at night. Also you could try to force stop other apps and see which one is interfering? For example phone is slow, force stop first 10 apps, if not fixed force stop next 10, if fixed, next time force stop one at the time from that batch of tens.
Mines just started doing this the other day. I think I have an idea if the problem, I'm just trying to find proof at this point. I recently downloaded this all to let me see the upload/download speeds if my network in the notification bar. It lets you set the refresh rate, to which I set it to 2 seconds, which I knew regardless would tax my system, I just didn't expect my ui to slow to a crawl.
Delete any Bixby remapping app as well, known to cause many issues including unpredictable lag.