Related
guys, I found out that the G-sensor daemon "akmd" alwasy takes up to 3% cpu on my N1 with CM-5.0.5/6.
I compared with stock ERE-27 rom, in which "akmd" in that takes less than 1%.
While during standby, it take no CPU usage.
Does it matter? I mean, would that kill our battery?
Actually I first found that out when I was using CM-5.0.5. One day I put my fully charged N1 beside my pillow and after 7-hr sleep, only 86% power left..
Maybe it has something to do with the 360 degree launcher2.
I personally don't use that feature. I'm gonna take a look at my usage.
I just noticed this as well while tinkering.
Gimpeh said:
I just noticed this as well while tinkering.
Click to expand...
Click to collapse
I realize I'm bumping an older thread now but I still feel this might be relevant.
Running top at any point will still show "/system/bin/akmd" which is the system daemon for the compass.
In my case, it almost always resides underneath "system_server". I've tweeted it at Cyanogen once but got no response to my question.
So, after doing some digging, I pulled down the SDK and fired up the "Dalvik Debug Monitor" here's what I saw (See attached: android-troubleshooting2.jpg)
Edit: i42.tinypic.com/m953rq.jpg
Not that it needed reiterating but the AK8973 is the 3-axis compass chip and something calling it or (the driver itself) is throwing an error almost precisely every 10 seconds. Now, I belive this has only been happening since the upgrade to CM5.0.6-N1 (Although I am now on CM5.0.7-Test1) either way whatever bug there is, still remains.
Edit: i40.tinypic.com/21liauh.jpg
Googling for that error: "Compass driver encountered fatal error2" pulls up a single page in the CyanogenMod Forums and two error logs on PasteBin.
Bump!!-Bumb!!
Thanks for the bump! Being a lurker has it's definite disadvantages.
prophetjinn said:
Maybe it has something to do with the 360 degree launcher2.
I personally don't use that feature. I'm gonna take a look at my usage.
Click to expand...
Click to collapse
In my testing, the use of 360º rotation nor the setting of "Launcher Rotation" changed whether akmd was consuming resources.
Full size image link: i40.tinypic.com/dxh0yu.jpg
Just as GaryD had posted here:
forum.cyanogenmod.com/index.php?/topic/3129-ak8973-compass-driver-encountered-fatal-error2
after a reboot the errors disappear for a while. I don't know the pattern to which they reappear (e.g. due to a buffer overflow or some other reason.)
confirmed...
I think this issue is with newer kernels. I saw it on various versions of CM before switching to enom's TheOfficial rom. Doesn't exist on unmodified versions of enom's rom, but I just loaded several of the newer 2.6.33.x kernels and all show akmd using 1% cpu while the phone is sleeping.
Additionally, power drain while sleeping with these kernels is between 5 and 7 milliamps, while with the stock rom (and enom's stock kernel) it is between 3 and 5 milliamps.
If anyone wonders how I am getting these numbers, I am using OSMonitor (from the market). I sort the processes, reversed, by CPU%. To get the power drain, I look at the dmesg log and filter for the "batt" tag.
I may post this as a new topic for the kernel devs to review if it gets no attention here...
bubbahump said:
I think this issue is with newer kernels. I saw it on various versions of CM before switching to enom's TheOfficial rom. Doesn't exist on unmodified versions of enom's rom, but I just loaded several of the newer 2.5.33.x kernels and all show akmd using 1% cpu while the phone is sleeping.
Additionally, power drain while sleeping with these kernels is between 5 and 7 milliamps, while with the stock rom (and enom's stock kernel) it is between 3 and 5 milliamps.
If anyone wonders how I am getting these numbers, I am using OSMonitor (from the market). I sort the processes, reversed, by CPU%. To get the power drain, I look at the dmesg log and filter for the "batt" tag.
I may post this as a new topic for the kernel devs to review if it gets no attention here...
Click to expand...
Click to collapse
Since I haven't run any other roms I was hesitant to drag anyone else's ROMs into the discussion. I've seen it with InsectrRaven and the Pershoot but they're obviously all pulling from CM's commits on Github. I realize they're not large amounts of cycles but any usage that can be minimized is something. Right? Maybe I'm just a minimalist at heart.
Much appreciated on the bump and the bump towards the devs.
Another confirm here.
I'm on CM5.0.7-test2 with pershoot 2.6.33.4 kernel. Mine was steady at 6% CPU though.
Confirmed..
E/AK8973 ( 101): Compass driver encountered fatal error2 is thrown in every 10 seconds.
CM-5.0.7.1-N1
Kernel 2.6.33.4-cyanogenmod
this TOTALLY makes sense to me. used the stock ROM for last 3 months and had great battery life. after using cyanogen 5.0.7 the last 4 days, battery life is much worse than the stock ROM for me. also different is in cyanogen this "akmd" always shows up in my battery usage, but this never appears in the stock ROM. i'd make a solid bet that this is a cause of the poor battery life on current cyanogenmod, especially if this thing is hitting every 10 seconds with some fatal error. wonder if it can be easily fixed?
I have an EVO, unrooted, no OTA update, fully stock but used the 'top' app to notice the compass /system/bin/akmd consistently using resources.
Disabling auto orientation has fixed it, and done miraculous things for my battery life (battery graphs can have flat lines!), but I want my auto-rotate back. Is this a case of the accelerometer writing out a bad settings file, or it's a bug or what?
I'm still seeing this issue in the latest cyan r c 2 nightly. I'm confused why the compass would be used for the screen orientation. As far as I know, we are talking about 2 different sensors. The phone has a compass sensor, which is akmd, and also has an accelerometer sensor, which is used for auto screen rotation. The compass I thought is only used in things like maps street view and Google sky map.
Regardless, is there any solution to get akmd to stop running all the time? What process is calling this to even run all the time exactly?
I have the exact same problem (though akmd often takes up 80% here) on Hero with CM6 nightly build Aug 19th. I hope I can simply delete the file somehow.
dvfk said:
I have the exact same problem (though akmd often takes up 80% here) on Hero with CM6 nightly build Aug 19th. I hope I can simply delete the file somehow.
Click to expand...
Click to collapse
was same for me.. i had disabled auto-rotating in "settings->display" and in cyganamod settings.. AND in launcher pro.. (i always lay down on the side and the phone flips and i dont like it).. i did this 2 days ago.. and phone been laggy as **** since then. akmd have had 70-99% cpu all the time.. so i turned it all back on again. and now akmd takes 1% wake and 0% sleeping.. so wierdo.. shud be the other way around!
any updates on this?
having the issue as well, can't get rid of it.
please someone let me know.
alright it is with great pain that i am writing this, but i really need some help here. for months i've read the forums, searched for answers, asked little individual questions, IMed with people directly for help... and i'm still having trouble.
i rooted my T-Mobile G1 all the way back when cupcake first came out. everything was great. life was grand. everything ruled. i was a happy android fanboy, talking friends into switching to android, talking crap about iphones... the works... but slowly things started getting slower and slower and slower...
the obvious thing was to wipe and reflash. i was constantly just updating to newer cyanogen roms at that point without wiping. so i wiped to the newest cyanogen at the time (can't remember at this point, but just picture it was like a couple months after cupcake). so things were good again for a little bit, but then it started slowing down again, getting FC's, etc. so a friend recommended i switch to superD... i did, and again, everything was great for a while. i consistently upgraded superD roms (sometimes wiping in between sometimes not). eventually i got to the point where i was on the most recent superD release. it lasted about a day before things started slowing down. examples include when i hit home to exit an application and go to the home screen, the whole screen would either turn black or just show my wallpaper for a good 5 seconds before my home screen would appear, or opening the browser would take like 10 seconds. lots of slow down.
so with the help of a friend i decided to completely wipe and reformat/repartition my sd card. i bought titanium backup but i didn't even bother with it, i said to myself, look, you barely use any of the stuff you have right now, how about just start fresh and reinstall things as you need them manually. so i formatted, repartitioned (using amon Ra's recovery, using the menu option that helps you do it automatically). i made sure i had the most recent radio and spl (this was just a couple months ago), and reflashed the most recent superD (i think its 1.11 if i remember correctly)... again, maybe one day of good performance before everything slowed down. this was also about the time when my battery life started becoming an issue. i'm not exaggerating when i say i couldn't make it home without breaking under 20% battery by the end of the day... and i really don't use my phone THAT much. i'd say i'm a little above average on my usage. i'll get into my widgets and apps in a second, but i really don't use that much stuff...
SO... continuing my story (thanks for sticking with me if you're still reading...). when cyanogens 2.1 for the g1 rom came out (5.0.8d/s) i decided it was time for a change. i reformatted AGAIN, repartioned AGAIN, and flashed 5.0.8. basically, i've got the same story going on. slowdowns, poor battery life, etc.
so here i am with my cyanogen 5.0.8 flashed g1. let me tell you about apps and widgets and stuff. right now i have a regular wallpaper (not live), 14 icons between my 5 screens and just the google search and power management widgets. i used to have calwidget, the genie widget (both news and weather), and the setcpu widgets too, but i decided to take them off to see if it would help with performance. zero help. apps that i either know for sure are always running or i think may have some impact are twidroyd, newsrob, craigsnotif (craigslist notifier), and dealdroid. i don't think any other apps are running and/or do automatic updates for content and stuff like that.
i also use cachemate (purchased) regularly to clear my caches. apps2sd is enabled.
i'm not sure what other information you'd need to help me out, but just let me know and i'll try to give you more details.
right now, i've got slow down like almost all the time. things are constantly pausing, slowing down. i feel like i'm back on my t-mobile mda with winmo5 haha. and forget about it with the battery. i left the house with 90% battery this morning. i went to the gym. went home. picked up lunch. came to work. its been like 4 hours. i currently have 19% battery. all i've done is make 2 phone calls, about a dozen text messages and i've sent 2 tweets (about my battery problem haha). i also used google maps once to look up a number. my wifi and gps is off.
so there we go. really guys, please please please. help me out if you can. any help would be appreciated. i'm so sick of this. and i'm stuck in contract until july 2011. so i'm not getting a new phone any time soon. i gotta figure this thing out.
i really appreciate your help.
thanks.
Dave
OH... and PS... forgot to mention that I just got a new battery this week thinking maybe the battery was just getting old and bad. obviously, no such luck.
I had the same issues till I flashed a SuperD, then everything was fine. I just recently flashed the Froyo from Cyanogen and its like it fixed everything and I'm on a brand new device (knock on wood)!
How old is your G1? Do we know if there are issues with the first run out of the factory? Is that even an issue?
i got the g1 last july. so it was already out for a while at that point. it was new from a store though. i suppose there could be something actually wrong with the phone itself, but i don't know. i was thinking of trying the cyanogen froyo but because its not a stable release yet i figured it would be just this bad or worse...
I promise cm5.0.8 has wonderful battery life when no custom apps are installed and not on any network..
so the question is what is your phone doing, and ought it be doing what it is doing.
There are some nice built in tools for this
Applications->running services
And
Applications -> manage applications (check out the filter in the menu from that screen)
You may be surprised by the apps the think they need to constantly have a service running for some painful trivial job the android API has better interfaces for.. if in addition to that you don't need the app uninstall it.
Otherwise experiment with comp cache and lock launcher in memory.
another example, as i was reading this i was on the phone and i just finished the call and hung up, and i was previously in text messages, it took 12 seconds for my text messages to come up. thats just insane...
as for running services:
- GTalkService <--- I use GTalk all the time
- GenieRefresh Service (Restarting) <--- weird considering I disabled this widget, although I'd LIKE to have it back
- Maps FriendsAppWidgetUpdater (Restarting) <--- never used this in my life
- NewsRob UnreadWidgetProvidor (Restarting) <--- never used the widget before (as a matter of fact, you have to pay to use the widget and i have the free version... weird)
-Twidroyd Background Service <--- understandable, I use this constantly
- AKNotepad Snaptic Update (Restarting) <---- umm... I use this all the time but I don't know why a notepad program would need an updater service running... interesting...
- Swype <---- gotta have that
- CM Updater (Restarting) <--- Don't really think that needs to be on all the time. Can easily manually refresh that...
So that's it. I didn't realize this was included now. Very cool. On older roms I had to use task managers which don't seem to really work. I'm going to stop everything except twidroyd, gtalk and swype right now and see how that does... at the bottom it says Avail: 3.2MB+0.00B in 0 ... Other: 55MB in 4 ... While typing that the Maps FriendsAppWidget just popped back up... I'm gonna see if theres a setting...
In the meantime, does any of this give you any ideas? thank you so much for the advice. Also what does (Restarting) mean?
ezterry said:
Otherwise experiment with comp cache and lock launcher in memory.
Click to expand...
Click to collapse
oh and i have compcache not checked and launcher in memory IS checked... i just tried turning on the compcache option... lets see how that goes...
ok so...
now that i know about those things that were running, i stopped all the ones i don't need, and also went into the apps to see if there was any options for turning off automatic updates, background syncing, etc etc for those things... i'm gonna charge my phone while getting ready to go out and then we'll see how it goes throughout the evening. lets see if i make it home with more than 20% battery left (i'll be gone for like 5 hours). if so then we're on to something here still i find it weird that i can't have a few widgets loaded. but whatever, i'll take a smoothly running phone that lasts all day and i just have to click on icons to get to stuff any day... thanks for the help, i'll let you know how its going tomorrow.
the next day
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
so back to square one... any ideas guys?
thanks so much for any help you can give me. i really really appreciate it.
polarbearmc said:
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
Click to expand...
Click to collapse
Um... The compcache instability scares me a bit
Compcache has had issues (maybe still does) where the first time you enable it the phone crashes.. but then works fine with Compcache on reboot. Otherwise it really ought no make the phone unstable. (it may or may not speed things up depending on how memory is being used.. usually however it allows 12MB of memory that is rarely used to be compressed, allowing a little more active memory to be utilized) You may want to look into wiping dalvik-cache both on the internal memory and SD card:
Enter console and run (this will restart the phone)
Code:
rm -rf /data/dalvik-cache/*
rm -rf /cache/dalvik-cache/*
rm -rf /sd-ext/dalvik-cache/*
reboot
if you get an error about no files found thats not an issue; but other errors may indicate a problem.
This may help system stability (with or without compcache) .. but won't do anything about the battery life (nor speed unless something was seriously wrong)
-------------------
Unfortunately you will either need to erase all your apps and just run stock CM5 [maybe slowly restore your apps you really need] -- OR -- be very patient and debug whatever application(s) are causing issues on your phone (and maybe complain to the dev for failing to read/understand google's documentation on how to write android applications.. not that some of the google apps haven't quite figured that out until recently)
Thus again the main question is what is running on your phone.. The places I mentioned before allow you to see the services (most of which usually restart if you run the related application again) but not strictly all the details to look for.
Example 1 An widget service is likely holding onto memory starving timer services (those not listed) and swapping out other services (phone/launcher making everything feel slow) At the same time the widget is not very active usually and may not connect to the internet at all; thus may not reduce battery life.
Example 2 An IM client on the other hand may requires a service to keep TCP/IP connections alive, and if not coded properly may be very persistent and cause a slow continual stream of data from your phone requiring a large amount of power to keep the phone on 2G/Edge.
Example 3 A Task killer an kill tasks that re-spawn, or kill a task in use if it doesn't know better causing things to behave in strange ways.. so can killing services/applications from the setting screens btw.. but at least that is a one off by user decision not a automatic operation in the background. Tasks when re-spawned may require more data from the internet thus more power to 2G/Edge
User: Then the one that causes me the most problems: A user that keeps the phone in his/her pocket rather than surfing the web, checking XDA, or continuously checking the battery level is using the device less thus will have longer battery life. (careful to not fall into this trap)
Other Ideas:
SetCPU: set the sleep CPU low in profiles (sleep for me is 245/160)[/*]
Verify End action: Settings->End Button Behavior->Go to sleep[/*]
Set longer periods between polls in applications that poll the net (example twitter every 10 or 20mins.. not 5)[/*]
Larger net transfers on wifi if available (example tell newsrob to sync on wifi only) wifi drains the battery faster than idle, but is much cheaper if larger amounts of data are involved.[/*]
As you can see many things will impact the system. You will need to find the ones eating your battery
Another helpful screen for debugging this may be Settings->Spare Parts->Battery History and Settings->Spare Parts->Usage Statistics
I get between 4h and 12h batter life under semi-normal conditions. 4h = surfing 3g + tappatalk + games.. 12h check email/tweat if i get one.. otherwise stays in my pocket. I've seen my test phone hang out for days on a 2g network without data. (so you can always set your apn type to mms if you just need it to be a phone for many hours.. mms keeps mms support btw)
Ebuddy (and most other MSN/AIM/ect chat clients is frequently one of the biggest problems on my phone.. so if I need more battery those are the first to go.. and whomever it is can poke me on gtalk/txt/or wait
Good luck in your search.. Took me a while to make cm5 work as long as cm4.. most of it was mis-behaving apps that I either know to shut off when I need longer battery life.. or have found replacements for.. or avoid widget functionality if the widget was misconfigured. (
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Latonya1 said:
i had same problem and what i did is i opened battery from the device and inserted its again and did a factory reset on my device
Click to expand...
Click to collapse
Removing the battery on the kindle isn't an easy feat. Are we talking about the same device, or did you attempt this on a phone? Because if this worked with the kindle, I am more than happy to put the time into trying but I want to make sure.
Thanks for the reply.
dlenoxx said:
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Click to expand...
Click to collapse
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
itouchables said:
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
I should have read over what kinology was before flashing it.. I'm sure it's a great rom, but I'm wanting something more android-e. Went great though, as far as the install- and thanks for the tip. Worse case I'll have that file to fall back on.
stunts513 said:
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Click to expand...
Click to collapse
As I've been doing a bit more testing trying to figure out what is going on, it does seem to happen more often when under 100~75mg of memory available. Idling now at 550 memory available now, thanks to a few tweaks here and there which has almost erased the problem when doing things like browsing the internet, youtube, netflix, etc. It's just happening now during games. Not as much- but still, in the middle of a game of Kingdom Rush it's a little frustrating to all of sudden have no control. And currently I've still got almost 7 gigs of space available as far as harddrive goes so that doesn't seem to effect it by much (at least for me).
Setting the I/O to noop, overclocking to 1500 (leaving the minimum to 350), and setting the zram compression to 28% were the tweaks. Also having Task Killer by rechild set to kill tasks when screen off has been a great fix when I do lose the touch pad controls as it'll free up some memory when I turn it off, leave it off for a minute, then turn it back on without really interrupting progress in several apps.
Still searching for a true, 100% fix so tips are still welcome and I'll keep everyone posted if I run across anything myself.
Note 4 Bell Canada
Updated 5.0.1
Day 3 Extra Info
>>>>>>>>>>>>>>
Full day at work 85% battery at the end
Google Chrome PC and Android bookmark history sync works perfectly
Wifi hotspot works perfectly every time ... no dreaded "Limited connectivity" like I used to see with the GS3
Fast charging is awesome .... with the stable battery usage of Note4 with 5.0.1 it is so easy to keep this phone charged.
Bad: My phone keeps taking screenshots when I am on the lock screen and I don't know why.
Day 2 Extra Info:
>>>>>>>>>>>>>>
The Good:
As far as I can tell everything works.
Bluetooth dropouts during locked state drastically reduced ..... sometimes stutters once a few seconds after lock and none observed after (JVC Car Audio Unit)
Menu multitask key is just as snappy as before (I had already disabled Google talkback)
Battery life is great ..... At 6*% after a full day at work ..... my GS3 was often near zero after a ful day in the same location
I can now give permissions to write to a microSD card
Standby battery life is great ...... charged 100% went to sleep .... woke up at 98% (My GS3 would be somewhere between 60 and 70% same location)
Every app I have is behaving normally
The Bad:
I got one random Google + forced close so far (that is no so bad I guess)
Update Process: Smooth as silk, no crashes, no lockups, no forced closures
The UI: New notifications are great, a lot of little improvements including and x if you want to close an app
Performance: same as before ... great no keyboard issues yet, no issues with toggling things on and off, Chrome scrolls web pages smoothy
Apps: All apps seem to work ... no forced closes
Battery: no obvious differences ... to early to tell
Things Fixed: My bluetooth connection stuttered like crazy in the car if the phone was locked .... seems like this was fixed in 5.0.1 ....
Seems like the max volume is louder now
I'm on Bell too and my experience is very similar to yours. So far I'm very happy with the update. No problems and I'm enjoying some of the new changes.
Sirandar said:
Note 4 Bell Canada
Updated 5.0.1
Update Process: Smooth as silk, no crashes, no lockups, no forced closures
The UI: New notifications are great, a lot of little improvements including and x if you want to close an app
Performance: same as before ... great no keyboard issues yet, no issues with toggling things on and off, Chrome scrolls web pages smoothy
Apps: All apps seem to work ... no forced closes
Battery: no obvious differences ... to early to tell
Things Fixed: My bluetooth connection stuttered like crazy in the car if the phone was locked .... seems like this was fixed in 5.0.1 ....
Seems like the max volume is louder now
Click to expand...
Click to collapse
1. Power Saving on/off from setting not working. (No changes when u slide on the slider to on/off, only working via notification toggle)
2. GPU thermal throttling for benchmark. (I'm not a fan of benchmarking, but it's interesting to see the 3D behaviors on 5.0.1 unable to perform as what it should be if the phone temperature not cold enough)
3. Waze graphical glitches.
These are some of the possible bug that I realized and it need to be fixed in the next update.
However, overall experience still not that bad. The main issue for me now is the Waze graphical glitches which force me to temporary using Nokia Here Map at the moment.
I'm on BOC3 Malaysia. You may take a look on my signature for version information.
DreamerTKM said:
1. Power Saving on/off from setting not working. (No changes when u slide on the slider to on/off, only working via notification toggle)
2. GPU thermal throttling for benchmark. (I'm not a fan of benchmarking, but it's interesting to see the 3D behaviors on 5.0.1 unable to perform as what it should be if the phone temperature not cold enough)
3. Waze graphical glitches.
These are some of the possible bug that I realized and it need to be fixed in the next update.
However, overall experience still not that bad. The main issue for me now is the Waze graphical glitches which force me to temporary using Nokia Here Map at the moment.
I'm on BOC3 Malaysia. You may take a look on my signature for version information.
Click to expand...
Click to collapse
I'm from Malaysia too. But i don't have power saving problem.
Wake did not work properly.
Recent apps slower than before. Like 2 second lag.
No more option to change lockscreen animations
Data usage unable to view data usage in short period of time.
Some features were removed after upgrade.
Only useful additional thing is smart lock
Sent from my SM-P605 using XDA Premium HD app
As on 5.0.1, there are Pros & Cons.
Pros:
1. The finger print now is much much better than Kitkat
2. Feel like a bit faster.
Cons:
1. The Bluetooth is not so clear like on Kitkat and time to time no voice even if still on Bluetooth connecting. (Already try to unpair and repair, still not ok)
2. A bit warmer than Kitkat.
3. Eat more RAM than before
4. After sync calendar with Kies, all calendar on device are gone but still existing in outlook calendar.
Remark: I'm on SM-N9100 DUOS
Anyone having trouble with super su not granting privilege after rooting in G ?
I hate the lag and switch between screens on the brightness slider. I've gone back to kk
My experience has been great when it works (smoother UI, better battery life surprisingly).
One major issue though. 3 times, the phone rebooted overnight. All three times, it was while it was plugged into the charger, and it was stuck on the SAMSUNG logo (with bubbles animation). But I cannot get past it, and trying to restart via holding down the power button does not work.
Has anyone else experienced this yet?
Finally. Me too. Samsung Lollipop Update Problem
jbkmin said:
My experience has been great when it works (smoother UI, better battery life surprisingly).
One major issue though. 3 times, the phone rebooted overnight. All three times, it was while it was plugged into the charger, and it was stuck on the SAMSUNG logo (with bubbles animation). But I cannot get past it, and trying to restart via holding down the power button does not work.
Has anyone else experienced this yet?
Click to expand...
Click to collapse
I AM experiencing this. I honestly think this update has broken my phone. My Samsung Galaxy S4 - when turned on, stays on the logo screen. Luckily for you it doesn't always do that but my phone won't even fully start up so I haven't been on it for two days. I really suggest you back up your phone because there may be a chance of it not turning on ever, like mine and a few phone shops are saying I need to completely wipe it. Does anyone know how to help? It would mean the world, thanks!
Battery life pretty disappointing. getting a good 10-14 hours under light usage. Heavy usage is out of the question if I'm leaving the house.
I downloaded the update yesterday and until now I must say it's amazing. Problems I had before with kitkat are gone. The speed is much faster. It's all so smooth and flat. I like it. I can't understand why everyone has issues with it. I'm using Note 4 SM-N910F.
Hello. I recently stupidly flashed RC29 on my phone. That's how I got out of there.
How to:
1. You realized that you are on RC29. Do not worry. Let's start the escape.
2. Start phone without sim card. Type on the keyboard <ENTER button>setprop persist.service.adb.enable 1<ENTER button>. Reboot with a SIM card (any, not even a valid one)
3. Connect your phone to PC, download ADB and type command: adb shell am start -a android.intent.action.MAIN -n com.android.launcher/.Launcher
4. Download and install telnet: adb install telnet.apk
4.1 Once at the Home screen, open the keyboard and press the Enter key twice.
4.2 Type telnetd & press Enter. The Contacts screen will come up, just ignore it. There will be no indication that you did it right.
4.3 Open Android Telnet Client; type localhost in the large text box and 23 in the smaller text box on the right.
5. Download the recovery to a memory card and type the command in telnet:
flash_image recovery /sdcard/<your recovery>.img
Just type reboot recovery! Now you have a complete Recovery!
6. WARNING! Install 2.22.19.26I and reboot into recovery 2-3 times. Check the radio version in HBOOT. If version 2.22.19.26I install the HBOOT package. Reboot 2-3 times.
7. It's all. Install roms.
Pay attention! Clockworkmod is not recommended by Cyanogen developers. Use AmonRa. (cwm recovery left in the post in case of emergency)
The story of how I installed CyanogenMod 7:
1. Download CyanogenMod 7 build (DM me if rom not downloading)
2. Install HBOOT 1.33.0013d
3. Install ROM. Download the kernel (ezgb_2636_v1.5.1_S.zip). Install kernel.
4. Just restart and wait. Now you have working system!
Notes:
Restart in recovery - HOME + POWER
Restart in HBOOT - PHOTO + POWER
Reset - CALL + MENU + POWER
Safe mode - hold MENU while booting
# sites (not all)
HTC Dream: Rooting - CyanogenMod Wiki
web.archive.org
Google Code Archive - Long-term storage for Google Code Project Hosting.
code.google.com
Please buy the HTC Sensation
I alone am bored in the forum Sensation
It can be found for 500 rubles
Ulumia said:
Please buy the HTC Sensation
I alone am bored in the forum Sensation
It can be found for 500 rubles
Click to expand...
Click to collapse
sorry, even though it costs 500rub, I spent everything on MiPad 2. I don’t have money for it. Sorry((
PS. and notice. I am now trying to bypass android and make my firmware on android 1.0 for dream.
I quote the article on rooting G1 from Cyanogen Wiki "ClockworkMod is not recommended for Dream due to memory shortage and file corruption."
That's why I think it's better to use Amon_RA's
On my Desire Amon_RA 2.0.1 seems better than CWM 2.5.0.7
Below you can find CyanogenMod themed version of Recovery
By the way the new Telnet version is already on Mod edit: 4pda link removed
@russanandres Thanks a lot for the tutorial, you are a real lifesaver! Exactly what I needed to get a custom rom on my G1.
Although now I'm wondering, is android 2.3 perhaps too much for this phone? I was shocked to see that the actual usable ram out of the 192mb is just 96 and out of them ~30mb free. The device itself seems to be somewhat sluggish on 2.3, the default browser can't even load google without crashing. Although I noticed it's kinda inconsistent, sometimes it speeds up a bit and gets pretty close to 1.6 speed. On the stock 1.6 the phone was fairly snappy for what it could do, although it had terrible idle battery drain. The battery on 2.3 seems better from my first impressions.
For daily driver usage in 2022 what would make most sense, if you have experience with more roms on this device? 2.3 just really seems pointless to me, as the device doesn't have enough power to run properly apps that require android 2.3 as minimum, pretty much all apps that I have installed run on 1.5/1.6+. For example, I have my music library in .opus format, tried foobar2000 and gonemad music player(they supposedly support opus) versions that are 2.3+ and they both straight up crashed on startup, perhaps due to the low ram/lack of instructions.
The speed itself doesn't annoy me as much as the soft reboots that happen from time to time when the phone gets too ''tired'', especially after reboot, for me in about 50% of the time the phone just soft reboots again like a half minute after the first reboot.
Edit: The reboots after the bootup happen if I just don't let it idle for 2 minutes or so white it's reading my sdcard, which has quite a lot of files. I doubt it's from the actual speed of the sdcard as it's a 16gb sandisk ultra, should be sufficient for this phone.
A slight overclock option seems to be present in the performance settings but I won't dare to use it, two days ago I had to do a somewhat professional solder reflow+SoC heat revive on 400C for 30 seconds with a bga soldering station and some flux, that brought it back to life, previously it would work only for about an hour after I heated it with a hairdryer. My point is that the processors in these devices haven't aged too well, in terms of wearing out mine is pretty much done for and who knows when it's gonna die again. I also managed to put a copper heat plate over the soc(with thermal paste) to absorb some of the heat in addition to the metal plating and hopefully to increase the remaining lifespan of the silicon.
Back on the topic, maybe android 2.1/2.2 would be more suitable and still with good features(mostly looking at the quick settings), although I have no idea honestly, I haven't played around with android versions this old to know which ones are lighter and heavier. 2.3 definitely seems heavier than 1.6, that is for sure.
Availability in terms of links is another issue but with research and some use of the web archive I suppose we would be able to find at least one rom per android version.
MaRtYy01 said:
@russanandres Thanks a lot for the tutorial, you are a real lifesaver! Exactly what I needed to get a custom rom on my G1.
Although now I'm wondering, is android 2.3 perhaps too much for this phone? I was shocked to see that the actual usable ram out of the 192mb is just 96 and out of them ~30mb free. The device itself seems to be somewhat sluggish on 2.3, the default browser can't even load google without crashing. Although I noticed it's kinda inconsistent, sometimes it speeds up a bit and gets pretty close to 1.6 speed. On the stock 1.6 the phone was fairly snappy for what it could do, although it had terrible idle battery drain. The battery on 2.3 seems better from my first impressions.
For daily driver usage in 2022 what would make most sense, if you have experience with more roms on this device? 2.3 just really seems pointless to me, as the device doesn't have enough power to run properly apps that require android 2.3 as minimum, pretty much all apps that I have installed run on 1.5/1.6+. For example, I have my music library in .opus format, tried foobar2000 and gonemad music player(they supposedly support opus) versions that are 2.3+ and they both straight up crashed on startup, perhaps due to the low ram/lack of instructions.
The speed itself doesn't annoy me as much as the soft reboots that happen from time to time when the phone gets too ''tired'', especially after reboot, for me in about 50% of the time the phone just soft reboots again like a half minute after the first reboot.
Edit: The reboots after the bootup happen if I just don't let it idle for 2 minutes or so white it's reading my sdcard, which has quite a lot of files. I doubt it's from the actual speed of the sdcard as it's a 16gb sandisk ultra, should be sufficient for this phone.
A slight overclock option seems to be present in the performance settings but I won't dare to use it, two days ago I had to do a somewhat professional solder reflow+SoC heat revive on 400C for 30 seconds with a bga soldering station and some flux, that brought it back to life, previously it would work only for about an hour after I heated it with a hairdryer. My point is that the processors in these devices haven't aged too well, in terms of wearing out mine is pretty much done for and who knows when it's gonna die again. I also managed to put a copper heat plate over the soc(with thermal paste) to absorb some of the heat in addition to the metal plating and hopefully to increase the remaining lifespan of the silicon.
Back on the topic, maybe android 2.1/2.2 would be more suitable and still with good features(mostly looking at the quick settings), although I have no idea honestly, I haven't played around with android versions this old to know which ones are lighter and heavier. 2.3 definitely seems heavier than 1.6, that is for sure.
Availability in terms of links is another issue but with research and some use of the web archive I suppose we would be able to find at least one rom per android version.
Click to expand...
Click to collapse
I think a swap of 256 MB or more will save your G1 on 2.3.7
So if 2.3.7 was slow, then any Android 2.x.x will be slow
Within 2.x.x the system showed more and more performance with each version
Ulumia said:
I think a swap of 256 MB or more will save your G1 on 2.3.7
So if 2.3.7 was slow, then any Android 2.x.x will be slow
Within 2.x.x the system showed more and more performance with each version
Click to expand...
Click to collapse
That's a great idea. I have to look into it, as far as I know I have to make a partition for the swap on the sdcard then enable it on boot with some sort of a script. Is that correct?
Guess that's what I'm gonna be doing today after work, apart from transcoding my music library to mp3 unless the music players decide to work with the swap enabled.
Another thing I wanted to mention, is it normal to have such high idle drain on this phone? Even on cm7 in airplane mode it seems to drain ~4-5% per hour or so. Perhaps my battery calibration is off, I charged it overnight and wiped the battery stats hoping to resolve this issue but it seems to persist. I got a nearly brand new vhbw aftermarket battery which should be about 900-950mah capacity from my measurements, so it's not due to an aging battery.
In comparision I also have a galaxy s1 on cm7.2 with a 12 year old battery on ~70% capacity and that phone lasts like 10 days idle with a sim card.
MaRtYy01 said:
That's a great idea. I have to look into it, as far as I know I have to make a partition for the swap on the sdcard then enable it on boot with some sort of a script. Is that correct?
Guess that's what I'm gonna be doing today after work, apart from transcoding my music library to mp3 unless the music players decide to work with the swap enabled.
Another thing I wanted to mention, is it normal to have such high idle drain on this phone? Even on cm7 in airplane mode it seems to drain ~4-5% per hour or so. Perhaps my battery calibration is off, I charged it overnight and wiped the battery stats hoping to resolve this issue but it seems to persist. I got a nearly brand new vhbw aftermarket battery which should be about 900-950mah capacity from my measurements, so it's not due to an aging battery.
In comparision I also have a galaxy s1 on cm7.2 with a 12 year old battery on ~70% capacity and that phone lasts like 10 days idle with a sim card.
Click to expand...
Click to collapse
Swap partition can be done directly in CWM
You need to find Partion SDcard!!! ALL DATA ON THE SD WILL BE REMOVED!!!
For swap you can use this script
Code:
busybox mkswap /dev/block/mmcblk0p3
busybox swapon /dev/block/mmcblk0p3
echo 100 > /proc/sys/vm/swappiness
And about the battery: on all the HTC smartphones that I had (Sensation XE, Desire A8181, Wildfire S) it has been bad since
So try to replace it.
Ulumia said:
Swap partition can be done directly in CWM
You need to find Partion SDcard!!! ALL DATA ON THE SD WILL BE REMOVED!!!
For swap you can use this script
Code:
busybox mkswap /dev/block/mmcblk0p3
busybox swapon /dev/block/mmcblk0p3
echo 100 > /proc/sys/vm/swappiness
And about the battery: on all the HTC smartphones that I had (Sensation XE, Desire A8181, Wildfire S) it has been bad since
So try to replace it.
Click to expand...
Click to collapse
I see, thanks for the explanation.
I'll hold off from getting a new battery for now, hoping that this battery will get better calibrated. I'm also not certain that the problem is in the battery, if I use the device non-stop from full charge it seems to hold on for about 1h45mins SoT before going flat, which for a device with a tiny battert and a 65nm soc doesn't seem unusual.
But I was also wondering about your experience with the battery, do you also get this high idle drain or is it just my unit?
Lastly, I was wondering if multitouch can be enabled somehow. From my quick search it appears that the G1 screen supports it but its purposely disabled, although some people show it off being enabled.
MaRtYy01 said:
I see, thanks for the explanation.
I'll hold off from getting a new battery for now, hoping that this battery will get better calibrated. I'm also not certain that the problem is in the battery, if I use the device non-stop from full charge it seems to hold on for about 1h45mins SoT before going flat, which for a device with a tiny battert and a 65nm soc doesn't seem unusual.
But I was also wondering about your experience with the battery, do you also get this high idle drain or is it just my unit?
Lastly, I was wondering if multitouch can be enabled somehow. From my quick search it appears that the G1 screen supports it but its purposely disabled, although some people show it off being enabled.
Click to expand...
Click to collapse
The G1 supports multi-touch
It's very strange why it's not in CM7
Xperia X8 has multitouch on the custom ROM but no multitouch on the stock ROM
I found a better opmitized gingerbread rom, that still has a working link.
The system runs much smoother than on cm7.
I have to add, something missed in the tutorial is updating the radio to an even newer version that expands the available ram by 15mb. That is like 50%, considering that the phone has 30mb ram free otherwise.
Link for the radio- here
I directly updated to 2.22.28.25_S via recovery and faced no issues. It is recommended to use superwipe first, with a custom configuration file in the root of the sdcard, that will do a full wipe except for the sdcard. (Source) (Source 2)
In the custom config set:
Wipe_Sd_Secure=no
Wipe_Sd_Ext=no
I received a new sdcard that I will use for the phone, a 64gb Patriot EP series that I got for 5€, these are very fast and dirt cheap. Probably faster than the phone's sdcard reader can candle but that is fine. Point is, I ran the partition sdcard option in the recovery, I noticed it doesn't only ask for swap but it also asks for ext2 partition, what capacity should I select for that? Can't find much info for the ext2 parititions other than they are used for moving apps to the sdcard, although I have no clue how to enable that ability in the android os.
As for my battery issues, I'm certain that the culpit isn't software related but rather a failure of the Qualcomm PM7540 power management ic. The easiest way to test that, which I did, turn off the phone and wait, if the chip is fautly it will drain the battery while it is off, which it does for me(there is nearly no difference in discharge speed between the phone being on and off). I actually remember a year ago when the phone was still just sitting as a decoration on my shelf and just turned on with the hairdryer from time to time, that I had to pull out the battery or it would drain it completely while off, so the power ic failure isn't related to the processor failure at all. I don't know what is my luck, to have 2 dying important chips on one board
Perhaps I will try to remedy it the same way I did with the processor, clean it, place some flux and heat it for 30 secs at 400C. Or maybe a bit lower temperature this time. Technically both chips can be replaced and finding a donor isn't hard(especially for the power management ic, it appears that HTC HD2, Touch HD, Nexus One, Touch Pro, Diamond 2, Desire, SE Xperia X10, X10 Mini, BlackBerry Storm are only part of the devices that use this same power ic. But replacing such chips is extremely difficult and beyond my current abilities, giving it to a professional is not worth it either, the entire phone costs 40-50€(as collector's value) so with the cost of such repair I can instead purchase another G1.
Thank, it work fine
MaRtYy01 said:
I found a better opmitized gingerbread rom, that still has a working link.
The system runs much smoother than on cm7.
I have to add, something missed in the tutorial is updating the radio to an even newer version that expands the available ram by 15mb. That is like 50%, considering that the phone has 30mb ram free otherwise.
Link for the radio- here
I directly updated to 2.22.28.25_S via recovery and faced no issues. It is recommended to use superwipe first, with a custom configuration file in the root of the sdcard, that will do a full wipe except for the sdcard. (Source) (Source 2)
In the custom config set:
Wipe_Sd_Secure=no
Wipe_Sd_Ext=no
Click to expand...
Click to collapse
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
@Ulumia you know anything about this? is the "RAM Hack" SPL required?
jonnyprogamer said:
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
Click to expand...
Click to collapse
I don't know anything about Dream because I don't have this device.
I think if you need that file, you know what to do to install it.
jonnyprogamer said:
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
Click to expand...
Click to collapse
Hey sorry for my late response, I just fired up my G1 which to my surprise(or not) failed to cold boot yet again so I had to give it the hair dryer treatment. Guess the hot air station fix worn out at some point after I stopped using the phone 2 weeks after applying it.
I have 1.33.0013d on mine, which appears to be the recommended version. looking at the description of the rom. I would avoid using another one if possible. Unfortunately I don't remember anything specific, so I can't give you more feedback.
MaRtYy01 said:
Hey sorry for my late response, I just fired up my G1 which to my surprise(or not) failed to cold boot yet again so I had to give it the hair dryer treatment. Guess the hot air station fix worn out at some point after I stopped using the phone 2 weeks after applying it.
I have 1.33.0013d on mine, which appears to be the recommended version. looking at the description of the rom. I would avoid using another one if possible. Unfortunately I don't remember anything specific, so I can't give you more feedback.
Click to expand...
Click to collapse
As i found out you need that SPL to get the extra 15MB of Ram, but be aware that SPL is pretty dangerous, because it doesn't support Fastboot flash (and fastboot boot doesn't work, gets stuck when i try to boot recovery), so if you accidentally brick your phone and do not have a custom recovery it's RIP.