Related
So I've been noticing that after a certain amount of use my Hero eventually slows down to the point where typing on the keyboard is frustrating because of the slow response. I did some searching and I came across this online
http://code.google.com/p/android/issues/detail?id=3453
since I'm no where near the level of a dev, I figured I'd put this out there and see if anyone can make heads or tails of it, and possibly create a signed-zip so we can just use the update feature in the recovery screen to flash it to our system.
Seems legit as a fix, and apparently this was something that was a known problem with Android 1.5 that I guess has been fixed with 2.0.
Any Dev help would be hot.
Excellent. Thank you for tracking that down.
The TL;DNR explanation: Location services are causing multiple "heartbeats" on the phone all on top of each other. One guy counted as many as 253 in 5 seconds. This consumes the CPU. I will look at the patch.
Would disabling location services be a temporary fix?
kynetx said:
Would disabling location services be a temporary fix?
Click to expand...
Click to collapse
Yes. We're pretty close to 2.1 though so shouldn't need more then that.
ive seen this problem too but not until recently, it lags the phone and drains the battery amazingly fast.
abcdfv said:
Yes. We're pretty close to 2.1 though so shouldn't need more then that.
Click to expand...
Click to collapse
I'm taking a wait and see approach on the 2.1 progress right now, what's there looks very promising but without the camera, accel., & (for me anyway because I do have alot of apps that i use) a2sd, I'm content with Fresh 1.0, just wanna get help get that issue solved cuz I'm sure I'm not the only one who is experiencing it.
PS: I know I said I have alot of apps, but I know that's not the cause because the same thing happened when I did a wipe and just left things "stock" with Fresh Rom 1.0 for a few days
If they got the accel and wifi tether working, I'd make the jump to 2.1, but I need the accel for work, and the wifi tether for internet.
What app can be used to show the system_server process? I use task manager but it isn't listed. I want to monitor this process.
Also, does anyone know about the patch? How Do you apply it?
1) I can't answer the first question. I just took the advice here and turned all location services off. My phone is back to its snappy self. The only way I'm really impacted by having to do this right now (I'm sure I'll use this phone for more after 2.1) is using google maps. I already kept GPS off when I wasn't using it but having to go into the settings and allow Location Setting before using gmaps is a PITA.
2) I know very little about android and ROM DEV but think the "patch" is programming code, only useful to people who know how to read and write it.
jdlumley said:
What app can be used to show the system_server process? I use task manager but it isn't listed. I want to monitor this process.
Also, does anyone know about the patch? How Do you apply it?
Click to expand...
Click to collapse
RoboTop???
You can use DDMS from the Android SDK toolkit to monitor processes running on the phone. Should be able to pull up a process list from there.
Now, I'm using Locale but not with Location settings for my different profiles. I also have Location settings turned on for use with Google Maps as well as the HTC Flip Clock / Beautiful Widgets Home. Surprisingly, my system_server process is sitting at 0% right now, and the phone has been on for over a day. Both DDMS and running "top -n 1" in the adb shell confirm this. If there's much of a change over the day, I'll be sure to let you know. So, it's possible that HTC found and fixed this issue with their SenseUI CDMA 1.5 build. Unlikely, but possible.
So I was seeing this issue even with the modified services.jar from that thread. Granted I didn't test it very long and it was only maxing out at 1%, but it was enough for me to feel that it wasn't working.
I have since removed HTC's location service. After rebooting it looks as if because the phone couldn't find HTC's service anymore it installed the stock one. Time to see if it makes any difference.
with my BB for example there was an application which rebooted your phone at a custom time that u have set .. is there an application that can be used to do the same with the hero? ... reboot device while u are sleeping.. so it runs nice and quick for u the next day?
flipzmode said:
So I was seeing this issue even with the modified services.jar from that thread. Granted I didn't test it very long and it was only maxing out at 1%, but it was enough for me to feel that it wasn't working.
I have since removed HTC's location service. After rebooting it looks as if because the phone couldn't find HTC's service anymore it installed the stock one. Time to see if it makes any difference.
Click to expand...
Click to collapse
On the Fresh ROM thread I thought you said that it was using 16% previously... and is this an issue that's apparent immediately or is it something that gets worse with time?
Any chance of including the modified services.jar in the next release even if it doesn't immediately appear to make a difference? I mean, if it's not crashing things and is supposed to be an improvement, then why not stick it in there, right?
Just read nearly that entire chain of messages. now somebody (fresh, ima callin you out!) dooo eeeet!
What's the word on progress for this in Fresh ROM? I have found it to be a very significant issue for me (and apparently so has my roommate), as I use location services quite a lot. GMaps being most in particular, but some other apps as well (Aloqa, Sprint Navigation). I'm really glad there's a workaround that doesn't involve a reboot!
I looked at the other link and I have downloaded both the services.jar file and the LocationManagerService.patch. Which one should I apply and do I apply it? I am having problems with this now.
bcellis said:
On the Fresh ROM thread I thought you said that it was using 16% previously... and is this an issue that's apparent immediately or is it something that gets worse with time?
Any chance of including the modified services.jar in the next release even if it doesn't immediately appear to make a difference? I mean, if it's not crashing things and is supposed to be an improvement, then why not stick it in there, right?
Click to expand...
Click to collapse
The bug is that it gets worse over time. I can include it for sure. I believe the reason it's not working is because our hero's code is all stored in services.odex, not services.jar. And I haven't been able to deodex that file yet. But I'll include it regardless because it can't hurt.
scirio said:
Just read nearly that entire chain of messages. now somebody (fresh, ima callin you out!) dooo eeeet!
Click to expand...
Click to collapse
patches11 said:
What's the word on progress for this in Fresh ROM? I have found it to be a very significant issue for me (and apparently so has my roommate), as I use location services quite a lot. GMaps being most in particular, but some other apps as well (Aloqa, Sprint Navigation). I'm really glad there's a workaround that doesn't involve a reboot!
Click to expand...
Click to collapse
I'm working on testing whether disabling HTC's location service will fix our issue. However with the release of the kitchen I was rebooting my phone non-stop. Impossible for me to know if it was working or not.
ElAguila said:
I looked at the other link and I have downloaded both the services.jar file and the LocationManagerService.patch. Which one should I apply and do I apply it? I am having problems with this now.
Click to expand...
Click to collapse
The patch is designed to apply to the source, so that won't help you. The services.jar would replace the one that's already there.
turning off location has been a dramatic difference in speed. its obvious theres something to that. it would get so bad the whole phone would lag
I am constantly seeing blogs about fragmentation and how it is poisoning the well for developers. I personal think it is a load of crap, but i thought i would ask the developers.
What do you guys think?
Is fragmentation an issue?
YES, it could be an issue if Google did nothing to fix it, but they are:
http://www.engadget.com/2010/03/29/exclusive-android-froyo-to-take-a-serious-shot-at-stemming-plat/
Not pretending to be an expert, or even a developer, but plenty of apps didn't cross well from various WinMo builds, or devices. WinMo fragmentation hasn't been trending. It's a rhetorical buzzword sustained by iPhanbois, imo.
bwhite82 said:
YES, it could be an issue if Google did nothing to fix it, but they are:
http://www.engadget.com/2010/03/29/exclusive-android-froyo-to-take-a-serious-shot-at-stemming-plat/
Click to expand...
Click to collapse
Yea I saw that too
It's just today we are suppose to be in fragmentation hell... It's just i don't see it.
Once in a while i will tell my friend with a Samsung Moment about an app, and for some reason he does not see it in the market, but this is few and far between.
I chose yes but I doubt it will kill android. It is annoying though to have a phone that is way behind because the maker of the custom UI is too lazy to do anything.
It did not kill the pc, or Windows for that matter. It will probably be gaming benefiting the most of future power increases.
Yeah, iFanboys are the most common people to critizise android for fragmentation - but they are not safe either.
Now with 2g, 3g, 3gs and ipad - and all having diffrent hardware in one way or another - they will also experience fragmentation. Esp. now that OS4 wont be feature-complete on 3g vs 3gs - and ipad wont get it until later.
Just because android got 3 res (320, 480 and 800) doesnt mean that it will be problems since 1.6 came out. Sure they need to fix/force vendors to upgrade handsets to latest android, so that people wont be left out - but since 1.6 that problem is much smaller, and there aint many handsets left out there with builds earlier then 1.6.
It's a problem.
Why do you think there are so many apps that are rated lowly on the market because of incompatibilities.
If there was only 1 phone and 1 version of android to code for, then bugs and compatibility would nearly be a thing of the past.
I think it's an issue, but a minor one. I'd rather them improve the OS rapidly and deal with not being able to use some apps, than sit with a stagnate OS but have more apps.
Like the other poster said though, they are going to try to fix it after 2.2 and work on making apps more compatible with all OS versions.
Hell, at least they realize it's a problem. Microsoft sure didn't give a ****, and doesn't now with 7 series.
Because of the "vendor delay" and the frequent Android releases, Android phones seem to have a 5-month lifecycle (my 1.5 Magic is 6 months old now, and I still can't use Donut/Eclair apps like Goggles, Maps w/ Buzz and many new apps that require 1.6+).
Access to applications is what makes most people buy smartphones. Remove or limit this, and people will switch to other vendors or platforms.
For people that root and switch custom roms, this doesn't seem like a big issue. But the majority of the users won't have access to all the new 1.6/2.1 apps being released on the market.
clamknuckle said:
I think it's an issue, but a minor one. I'd rather them improve the OS rapidly and deal with not being able to use some apps, than sit with a stagnate OS but have more apps.
Like the other poster said though, they are going to try to fix it after 2.2 and work on making apps more compatible with all OS versions.
Hell, at least they realize it's a problem. Microsoft sure didn't give a ****, and doesn't now with 7 series.
Click to expand...
Click to collapse
@Clam*, you're right about them realizing it's a problem and working on it.
I believe they plan to have every phone running the same version of android, but with many add-ons available from the market.
This is surely a desirable route. Might it never happen? I haven't the slightest.
Alternatively a big pack of goodies you can get from online or preferrably the market that has all the addons depending on the sufficiency of phone hardware.
Hell, better yet! It could be part of the "first use tutorial" we all know and love
The first time the user turns on the phone after entering google info etc. they can check all the options they want and it will automatically download them from googles servers and set them up on the phone.
Very reminiscent of certain linux installations with addons from repositories.
OpenSuSE comes to mind.
Or to speed that process up, the phone retailer can install the addons specific for that phone.
Though it would still be nice to have the option to checkmark features at our own whim, allowing the system to discard the rest for example.
Of course if the addons were discarded or never installed by phone retailers in the first place they could still be downloaded from googles servers automatically.
**To Google Gods: It would be nice to have such options in the settings where we could enable and disable features and have them download or be discarded in the background**
There are so many methods out there to make fragmentation nothing more than a bygone.
I hope Google can turn this OS into what I've dreamed (figuratively) that it could be..
Ahh how I concieve ideas that will likely never occur..
Sorry.. i could write volumes about my futile ideas for the world, though I'm too hopeful and eager.
I'm sad to say..
"Such is our reality serving as the torrent thrusting back creative thought." -me
I am running an eclair rom on my g1 (latest superbad), but that's not really important. What is important is that I like having the launcher in memory because it lets me get back to the home screen faster (for the most part).
In similar fashion, it takes a long time for the phone app to start when I hit the green button, or when I have an incoming call, and so logically I think that keeping the phone app in memory might fix that issue as well. Technically I could be completely wrong. I don't know. I'm not a developer.
Is this possible/feasible? Would it fix the issue?
Note: In all likelihood this post will result in touchy moderators complaining about how it's in the wrong place, or I didn't search or myriad other posts that I often have to sift through before someone answers the question...But I searched and couldnt find any one asking this question, and I thought it was worth asking. I just don't have the time or energy to try and figure out where or when it is appropriate to post. Maybe it's exactly where it belongs, and it is a worthwhile post, but that would be completely accidental.
hugerobot said:
I am running an eclair rom on my g1 (latest superbad), but that's not really important. What is important is that I like having the launcher in memory because it lets me get back to the home screen faster (for the most part).
In similar fashion, it takes a long time for the phone app to start when I hit the green button, or when I have an incoming call, and so logically I think that keeping the phone app in memory might fix that issue as well. Technically I could be completely wrong. I don't know. I'm not a developer.
Is this possible/feasible? Would it fix the issue?
Note: In all likelihood this post will result in touchy moderators complaining about how it's in the wrong place, or I didn't search or myriad other posts that I often have to sift through before someone answers the question...But I searched and couldnt find any one asking this question, and I thought it was worth asking. I just don't have the time or energy to try and figure out where or when it is appropriate to post. Maybe it's exactly where it belongs, and it is a worthwhile post, but that would be completely accidental.
Click to expand...
Click to collapse
Pre-complaining about others' complaints = lame.
To answer your questions, have you: 1. checked Spare Parts to see if the "keep home app in memory" bit is set? (at the bottom of the list) 2. have you used a task manager like Auto Killer to manage your memory more aggressively ? 3. Have you used a task manager to see dialer.apk's status after using the phone for other stuff? 4. Have you posted this question to the devs/other users of this ROM to see if they have similar problems?
BTW, your config including ROM type/build/version, etc is extremely important.
No doubt someone will complain about the placement of your thread but to be honest some of these people have no lives. Anyway, I don't know if this helps but I exclude my dialer from my task manager and it starts instantly. I am using Advanced Task Manager... hope it works for you.
rynosaur said:
Pre-complaining about others' complaints = lame.
Click to expand...
Click to collapse
Calling me lame when it appears that you didn't even read my post=the reason why I hardly ever post here. Ugh.
rynosaur said:
To answer your questions, have you: 1. checked Spare Parts to see if the "keep home app in memory" bit is set? (at the bottom of the list) 2. have you used a task manager like Auto Killer to manage your memory more aggressively ? 3. Have you used a task manager to see dialer.apk's status after using the phone for other stuff? 4. Have you posted this question to the devs/other users of this ROM to see if they have similar problems?
BTW, your config including ROM type/build/version, etc is extremely important.
Click to expand...
Click to collapse
I think maybe you only read the part where I precomplained... since that seems to be the only item you commented on appropriately. But to answer your questions...
1. I clearly stated that I keep home app in memory because I like the performance gain. I have no idea what your asking me.
2. I don't use task killers/memory managers. Cyanogen and most other experts have argued against them enough to convince me that it's not the right solution.
3. huh?
4. I'm not complaining. This is not geared toward any particular dev. Slow phone is a known inconvenience with all eclair builds on G1. Didn't think I needed to go asking if anyone else was experiencing it. I have flashed so many eclair roms to my phone, and with all of them the phone app has behaved more or less the same way.
BTW- I also clearly stated that I have a G1 running the latest superbad.
Here's my question again... Would keeping the phone app in memory improve it's performance in the same way that keeping the home app in memory does? If so is there value in including this option in spare parts?
blackvyper said:
No doubt someone will complain about the placement of your thread but to be honest some of these people have no lives. Anyway, I don't know if this helps but I exclude my dialer from my task manager and it starts instantly. I am using Advanced Task Manager... hope it works for you.
Click to expand...
Click to collapse
Thank you for your suggestion... but I'm leery about using task managers/killers based on some of the discussions I've read from some of the expert devs (cyanogen, etc). I suppose if it works, the result is the same. I am surprised no one has asked this question before. I searched quite a bit and couldn't find a mention- on here, and a straight up Google search.
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
rynosaur said:
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
Click to expand...
Click to collapse
I don't know where the arrogance was in my opening post??? You decided to start off your first reply with name calling. Cool it. Don't waste your time on me anymore, ok? I don't need your help, man. There's plenty of polite, helpful people here. I'll look to them. I don't need advice wrapped around names and swears and put downs.
Edit:I just deleted 3 paragraphs... you're just not worth the effort.
Let me repeat my question, slightly reworded, since I don't know what OOMs are and I don't want to know.
Spare parts has an option to keep launcher in memory. Is there a chance that adding another option to keep the phone in memory might help with phone app performance? I don't want to use task killers, etc.
That is my question. My only question. Sorry for all of the drama, folks.
hugerobot said:
That is my question. My only question. Sorry for all of the drama, folks.
Click to expand...
Click to collapse
Yes, I'm sorry for my part -- I started sarcastic and then thing flew out of hand. My point about priority and memory allocation is this: dialer is, by its nature, held in memory-it doesn't have to be loaded after boot, it just has to be recalled. I'm sure you've noticed that no matter what you're doing on the phone, it all takes a backseat to an incoming call, and usually very quickly, <5 seconds. The phone is still built to take calls above any thing else.
So my answer to your question is this: bump up the priority of phone.apk. It will respond to the green button more quickly. In my ROM, Phone has an OOM of -12, while HTC Sense is 0 -- that's Spare Parts working to make dialer higher on the food chain. Think about it. Don't wait for someone to rewrite a ROM, just use AutoKiller to bump it up the foodchain and push other background processes further to the back. If you use compcache, remember dialer.apk may end up there, where it takes more till (being compressed) than normal to recall. Also Phone Prioritizer (which I can't find on the market anymore due to my build) is nice fore renicing more frequently than the OS does by default. All these things could help. Reducing other concurrent background tasks will help as well.
hugerobot said:
I don't know where the arrogance was in my opening post??? You decided to start off your first reply with name calling. Cool it. Don't waste your time on me anymore, ok? I don't need your help, man. There's plenty of polite, helpful people here. I'll look to them. I don't need advice wrapped around names and swears and put downs.
Edit:I just deleted 3 paragraphs... you're just not worth the effort.
Let me repeat my question, slightly reworded, since I don't know what OOMs are and I don't want to know.
Spare parts has an option to keep launcher in memory. Is there a chance that adding another option to keep the phone in memory might help with phone app performance? I don't want to use task killers, etc.
That is my question. My only question. Sorry for all of the drama, folks.
Click to expand...
Click to collapse
I know what you mean. Im not sure what happend to XDA lately. Back when it was ALL windows mobile forums (phones no android), everyone was very helpfull ect... When android phones started coming out that brought the whole world to XDA and now we have people on here who have nothing else to do but bash people instead of helping them... Anyways... LOL
As for the dialer / home in memory situation. I found that enabling swap / compcache makes a huge difference.
I been on every 2.1 rom on G1 and ALL of them had problems with loading apps very slow and opening the home screen real real slow even with "Home in Memory" checked in spared parts.
And then I flashed Super E yesterday wich is a 2.1 rom that has swap / compcache settings inside spare parts. I partitoned my sdcard with 254mb swap and enabled Swap and Compcache of 32mb. I also went to the market and downloaded "Swapper 2" which will also enable swap and tell you your swap statistics. After doing that everything and I mean everything opens rather instantly.
My sdcard is class 2 so I never been a fan of using swap but using swap with compcache makes a huge performance difference for me on my G1 on the Super E rom. I think theres an update to Super E that I havnt flashed yet but with the perfomance so far I dont see a need to update but I might update just for the hell of it.
Long story short. Enable swap partition on your SD card / Install Super E / Install Google Apps / Enable Aps 2 SD / Spare Part Enable compcache / swap 32mb / Enable Launcher in memory / Download Swapper 2 from market and set to on.
Thank you. I will try your suggestion.
One last comment- since I started running eclair roms on my G1, the phone app has taken longer to load than it used to. It doesn't feel like it has priority over the other apps. I do need my phone to be a phone, first and foremost, and it has gotten better, but it's still often very slow to load. Also, I run a very vanilla install. I wipe my phone so often that I don't bother loading a lot of apps. This behavior would be typical for anyone with a fresh install of one of the eclair roms.
hugerobot said:
Thank you. I will try your suggestion.
One last comment- since I started running eclair roms on my G1, the phone app has taken longer to load than it used to. It doesn't feel like it has priority over the other apps. I do need my phone to be a phone, first and foremost, and it has gotten better, but it's still often very slow to load. Also, I run a very vanilla install. I wipe my phone so often that I don't bother loading a lot of apps. This behavior would be typical for anyone with a fresh install of one of the eclair roms.
Click to expand...
Click to collapse
All these replies you are getting about phone.apk and dialer.apk have nothing to do with your problem. In fact there is no dialer.apk. And phone.apk is mainly for incoming calls. The rest of the dialing, such as when you use the green button, is done via contacts.apk. The slow load times are really a part of the way android kills processes. If you are running a replacement launcher like LauncherPro or GDE, etc, what you are seeing is that acore needs to reload and takes a long time. The stock launcher is much more forgiving. I have found that by installing the "DialerOne" dialer from the market, that these alternate launchers do not cause the acore reload, and the dialer is very fast to load.
bkmo said:
All these replies you are getting about phone.apk and dialer.apk have nothing to do with your problem. In fact there is no dialer.apk. And phone.apk is mainly for incoming calls. .
Click to expand...
Click to collapse
I never said phone.apk but I did transpose dialer and phone as interchangeable names for the same process. My fault, but what runs in the background to let let you make phone calls is name com.android.phone.
This advice/his characterization of how the dialer-contacts tool works might hold true in Eclair/2.1 Cyanogen-based ROMs, but it is not an "android" universal truth. I am running a Sense 2.1 ROM and believe me, there is no "contacts" process. Foregrounding com.android.phone brings up the dialer, and decreasing its OOM brings up the dialer instantly when the green button is pressed.
The other gentleman's response that more cache is the answer may be a great answer for cm5.0.7 ROMs--if you can get a good cache going, I never could--but it's almost a non-question in Sense ROMs since everyone will run one anyway, whether it be backingswap or linux-swap.
Now that's we've cleared this question up completely
I couldn't bother reading all of the back and forth stuff, I am using Xtreme-1.2.2-black it is 2.1 CM5 base.
I have been using shadowch31 Renice Script that gives the "phone" app a higher priority and it starts up a lot faster.
Also using and ogg file instead of an mp3 has been know to help.
I haven't seen the script in any of the forms so I am not sure if shadowch31 wants it released so pm me or him if you want to give it a try
This is from the getting hero to run faster thread in general:
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:[/I]
[I][B]setprop ro.HOME_APP_MEM 1536[/B][/I]
adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
Can't we do something similar with the phone.apk?
SuperBad v1.4.2 will be up in a bit...
It'll be fixed.
In Christ
Clay
htcclay said:
SuperBad v1.4.2 will be up in a bit...
It'll be fixed.
In Christ
Clay
Click to expand...
Click to collapse
From the man himself! So did my suggestion help? Did I actually contribute by posing the question?
For the record, I did say that this was the case with all 2.1 roms I've tried, not a problem with superbad.
rynosaur said:
This advice/his characterization of how the dialer-contacts tool works might hold true in Eclair/2.1 Cyanogen-based ROMs, but it is not an "android" universal truth. I am running a Sense 2.1 ROM and believe me, there is no "contacts" process. Foregrounding com.android.phone brings up the dialer, and decreasing its OOM brings up the dialer instantly when the green button is pressed.
Click to expand...
Click to collapse
You are right, there is no "contacts" process. And I have seen this contact.apk loading issue since "donut", so it is not an "eclair" only issue. What I do see is that when you are running an alternate home app, that when you press the green button, or the phone icon, what you get is an "acore has died" in adb logcat. At this point acore reloads all the programs under it including launcher, before it runs the contacts app to get you the dialer. I have seen up to 20 seconds before the dialer comes up. Renicing phone.apk does not help this issue in my testing. I have just tried dialerone from the market, and it does not suffer the slow load times. I do not know what brings up the dialer when you press the button, all I know is that the dialer is included in contacts.apk, and what I see in a logcat whn I press the button or icon. Dialerone is working for me, and I can use the latest ADW launcher without a delay to the dialer. Thanks for setting me straight....seriously.
mejorguille said:
This is from the getting hero to run faster thread in general:
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:[/I]
[I][B]setprop ro.HOME_APP_MEM 1536[/B][/I]
adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
Can't we do something similar with the phone.apk?
Click to expand...
Click to collapse
AFIK phone.apk is not the dialer, and is already locked and does not get killed. Just think about it, if it was able to be killed, what would be running to handle an incoming call?
bkmo said:
Thanks for setting me straight....seriously.
Click to expand...
Click to collapse
Hey, everybody's got to be wrong at least once a day, me . . . . more 10 or 20 times a day. I don't know what it is with gapps and acore crashing regularly in cm eclair builds, but my impressions from t1-stable were: Hero-like instability, without the Hero bells and whistles. So I switched to Sense 2.1 Result, apps do die when I look at the phone funny (or press Dial -- fring dies when I press dial, or the mysterious com.smithmicro.DM -- probably a keylogger), but the bells and whistles are nice, so there's tangible payoff for dealing with a stretch of a mod.
Hope HTCClay works a miracle and fixes your phone. Maybe he can share the secret with other devs Peace
rynosaur said:
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
Click to expand...
Click to collapse
there must be some mod out there to shut up this silly stupids like this guy...why this people ever answer in a post?!!!!
Does anyone have a full listing of every app removable from the stock rom without killing it? I've frozen lots of stuff that I don't believe should impact general performance, but end up having to completely wipe and reinstall due to something I've frozen rendering my screen unusable. I think it's in the Samsung apps, but haven't done enough testing to determine which apps it NEEDS to have running in order to work.
The tablet can boot up just fine but as soon as I go to unlock it, it just sits at the homescreen unresponsive to any button or touch input.
nickhimself said:
I've frozen lots of stuff that I don't believe should impact general performance ... The tablet can boot up just fine but as soon as I go to unlock it, it just sits at the homescreen unresponsive to any button or touch input.
Click to expand...
Click to collapse
This is not a "bloatware" issue (and it kills me when people go hunting for this stuff, unused software really has minimal impact).
You may be suffering from a problem I'd discovered with the Samsung kernel (namely, it doesn't reserve enough memory that the Android framework needs in order to do InterProcess Communication).
Can you try this kernel (rename the file to "boot.img" and flash it with either Odin or Mobile Odin) and tell me if that fixes anything for you?
The meaning of my quoted sentence in your post was central to the freezing issue I had following a reboot after I'd disabled apps. I didn't disable them because I thought my tablet was running slowly, I disabled them because I didn't want 200 applications installed because some guy in Samsung's marketing department said "well they have to have twelve different notepad applications, nine clocks, four calendars, several methods of backing up data to various cloud services, and also put a whole bunch of wallpapers in there for no reason because I really like cats and flowers so other people probably do too."
Also, sorry to tell you this kcrudup, but... I'm already using your kernel anyway
nickhimself said:
... following a reboot after I'd disabled apps ... I'm already using your kernel anyway
Click to expand...
Click to collapse
OK, as long as this is a case of "shooting yourself in the foot", then.
BTW, wallpapers (as just one example) take up NO resources if not used, and since you're not going to be installing anything in /system anyway, what's the point?
(BTW, it's not just you I'm talking to here- it's all the other Quixotic "bloatware" folks out there. Unless something like "Better Battery Stats" are showing multiple wakelock instances and/or Alarms, y'all are wasting your time on that; eliminating "bloatware" is the "ATK" of ICS+)
kcrudup said:
OK, as long as this is a case of "shooting yourself in the foot", then.
BTW, wallpapers (as just one example) take up NO resources if not used, and since you're not going to be installing anything in /system anyway, what's the point?
(BTW, it's not just you I'm talking to here- it's all the other Quixotic "bloatware" folks out there. Unless something like "Better Battery Stats" are showing multiple wakelock instances and/or Alarms, y'all are wasting your time on that; eliminating "bloatware" is the "ATK" of ICS+)
Click to expand...
Click to collapse
I think it's more carryover from working with windows for so long. I'm used to, possibly even trained, on expecting the first steps after a new install to be Clean Out Everything and Trim Services ASAP.
I just don't like feeling like I have no power over a stock ROM through removing any and every piece of software I just don't want.
nickhimself said:
I just don't like feeling like I have no power over a stock ROM through removing any and every piece of software I just don't want.
Click to expand...
Click to collapse
Sure, I get that. One thing to remember (and I've worked on a number of Android devices over the years for a number of manufacturers and carriers) is that no manufacturer (nor carrier, believe it or not) wants to do anything that reduces overall performance (even predatory ones like VZW who'd rob your Grandmother if there's a dime to be made off her).
What's instructive is to run BBS and check on "Alarms", "Network" and "Partial Wakelocks" at the reference "Since Boot" after the tablet's been on a while- you'll see that all this "bloatware" isn't even a factor in the parts of the system that count.
Basics
http://forum.xda-developers.com/showthread.php?t=1634624
jje
I tried doing a search and couldn't find a relevant thread, but I have a few questions...
OK first, the issue that brings me here is the only web browser that I like (Boat) has long been dead and out of development, it's long not been on the play store but I've had the APK for a long time and just transfered it to every new phone I got so I could keep using it. I have tried finding a different browser, but I hate them all, none of them have any of the features I want. My last phone was running Android 9.0 and Boat was still working on it. Well, I got a new phone now (Pixel 4a 5g) that has Android 11 and boat still mostly works... except it crashes if I click the bar at the top to type in a URL and a few other bugs... but otherwise still works flawlessly.
1. So, I'm wondering first is it even OK for someone to look to hire a developer to basically update a dead app? Any website and contact information for the original developer no longer exists, but I don't know if it's OK for someone to take over a dead app like that, if it would be considered stealing or something.
2. Second, well if it's OK... I have the last APKs of the browser and I had used a guide to deconstruct the APK into a project thinking maybe I can figure it out and how to update it so that it still works but... yeah that's not happening. So I have the APK files and the already deconstructed into a project and was wondering where I can ask about hiring a developer just to basically update the app so that it still works (bug fixes only, not really making any changes to the look/feel/etc, just fix any bugs or code that's old and deprecated and doesn't work anymore)? And when I say hire, I mean like actually hire, with real money.
sardonicus87 said:
I tried doing a search and couldn't find a relevant thread, but I have a few questions...
OK first, the issue that brings me here is the only web browser that I like (Boat) has long been dead and out of development, it's long not been on the play store but I've had the APK for a long time and just transfered it to every new phone I got so I could keep using it. I have tried finding a different browser, but I hate them all, none of them have any of the features I want. My last phone was running Android 9.0 and Boat was still working on it. Well, I got a new phone now (Pixel 4a 5g) that has Android 11 and boat still mostly works... except it crashes if I click the bar at the top to type in a URL and a few other bugs... but otherwise still works flawlessly.
1. So, I'm wondering first is it even OK for someone to look to hire a developer to basically update a dead app? Any website and contact information for the original developer no longer exists, but I don't know if it's OK for someone to take over a dead app like that, if it would be considered stealing or something.
2. Second, well if it's OK... I have the last APKs of the browser and I had used a guide to deconstruct the APK into a project thinking maybe I can figure it out and how to update it so that it still works but... yeah that's not happening. So I have the APK files and the already deconstructed into a project and was wondering where I can ask about hiring a developer just to basically update the app so that it still works (bug fixes only, not really making any changes to the look/feel/etc, just fix any bugs or code that's old and deprecated and doesn't work anymore)? And when I say hire, I mean like actually hire, with real money.
Click to expand...
Click to collapse
First topic is about licence agreement and legal stuff. It is owned by "Boatmob, Inc." / "Digital Life International Limited" / "Crunchbase Inc.". Although the app was for free, it does not seem to be a free licences. But I am not an expert in this area.
About the browser app itself, I have seen that you were already active here: https://forum.xda-developers.com/t/boat-browser.3821682/
You either need a permission of the owning company and then maintain the app yourself (or via a hired dev), or you have to switch to another and still actively supported browser app.