yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] rynosaur:
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.
[G1 Android Development] blackvyper:
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.
[G1 Android Development] hugerobot:
Calling me lame when it appears that you didn't even read my post=the reason why I hardly ever post here. Ugh.

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?
[G1 Android Development] hugerobot:
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.
[G1 Android Development] rynosaur:
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.
[G1 Android Development] hugerobot:
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.
[G1 Android Development] rynosaur:
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.
[G1 Android Development] hypersonicx:
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.
[G1 Android Development] hugerobot:
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.
[G1 Android Development] bkmo:
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.
[G1 Android Development] rynosaur:
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 :D
[G1 Android Development] Sleeepy2:
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 ;)
[G1 Android Development] mejorguille:
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:

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?
[G1 Android Development] htcclay:
SuperBad v1.4.2 will be up in a bit...

It'll be fixed. ;)

In Christ

Clay
[G1 Android Development] hugerobot:
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.
[G1 Android Development] bkmo:
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. :)
[G1 Android Development] bkmo:
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?
[G1 Android Development] rynosaur:
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
[G1 Android Development] arefin:
there must be some mod out there to shut up this silly stupids like this guy...why this people ever answer in a post?!!!!
[G1 Android Development] rynosaur:
SILLY STUPIDS?

Oh I have been put in my place!;)
[G1 Android Development] hypersonicx:
Like I said, im on Super E 2.1 and everything stays in memory as it should. Home screen loads right up when exiting apps. Thats with compcache enable with home in memory enabled and 256 swap enabled. all in spare parts.
[G1 Android Development] h.nocturna:
256MB swap is kind of ridiculous from what I've seen... I usually run a 32MB swap with a 24MB Compcache with compcache set to a higher priority than swap so that swap is only used when compcache fills up. How does the 256MB swap work after say... 2-3days (without reboot, ofc). I hear that once it fills up the phone slows down to molasses.
[G1 Android Development] bkmo:
I am on cyanogen 5.0.7 with a few personal tweaks, but basically stock. I have just loaded the ADW launcher 0.7.5 system version (not from market), and my dialer is now working fast again. Maybe 2 seconds load the first time, then almost instantly. I am not running any swap or CC. It is all about how the launcher uses memory as far as AFAIK. :)
[G1 Android Development] hypersonicx:
256MB was just an example you can set it to what ever best fits you. At 256mb I had my phone on for like a day and only used like 7mb of swap according to the Swapper 2 app. So yeah 32mb is fine with compcache. Im just stating that by enableing swap and compcache that solves the problem of the homescreen and other apps opening so slow.
[G1 Android Development] rynosaur:
I personally would rather have the OS let my locked/foreground apps have buckets of memory which are occasionally taken away and replaced with dixie cups, rather than every app get the same dixie cup. That's why I use CC/BS and AutoKiller. More elbow room + important stuff gets to keep, but my logic works in Sense, Cm-Eclair confounded me by its erratic hurry up and wait performance w/r/t sleeping apps.
[G1 Android Development] Vermithrax:
Try this:

1. Open a terminal of your choice.

2. Type in the following:

su
renice -18 pidof com.android.phone

3. Close the terminal.

4. Call yourself, from another phone of course, and see if it responds almost instantly.

5. If satisfied, you can try placing it into your userinit.sh file.

I have done this in the past and not had any problems...

Note: I know it worked with CM4, but I have not tried this with CM5... Do not need to... I have tweaked

so many other settings that this is not a problem for me... Please do not ask about them... I refuse to

be ridiculed by others because my changes do not line up with what they read in a ROM Developers thread...

L8r...
[G1 Android Development] IronWolve:
su
renice -18 pidof com.android.phone

Ha, that was simple. ;)

Some good tips here, exclude contacts from kill, renice, try different dialers, etc.

I can understand the OP idea, if we can keep the launcher in memory why not the phone. Since the number one use for a phone is calls. That should be super fast.

Some of us are not in the *know* of all the tweaks or issues. This forum is the only resource many users know about, so thanks for posting tips here.
[G1 Android Development] rynosaur:
Haha, good point . . . like JIT is pointless on a G1 (even though it makes almost everything faster), swap is horrible (but somehow backingswap is ok??), flash everything from fastboot, don't do that, you'll go blind, etc etc :D
[Desire General] snerkler:
I currently have the HD2, and whilst it's a great phone it's starting to annoy me with how many glitches there are, and how many times it crashes and I have to reset it. I have all the cabs running to prevent this such as memmaid, but it does drive me mad sometimes. The other thing is the lack of apps, having come from the iphone. The 2 things I absolutely love about the HD2 though is the gorgeous home screen (the reason I haven't even looked at windows 7 for it, sad but true) and the size of the screen.

What I would like to know is if you can get the home screen of the Desire to look as stunning as the HD2, what features does the desire have over the HD2, and how good the apps are on android phones? Can you get similar apps to that of the iphone like yell.com, ebay apps etc as well as games? Would I miss the larger screen?

I'm toying between the desire, and waiting to see what the iphone 4g is like when it is released, but they would have to make a lot of improvements on the iphone for me to consider it. I would very much be interested in the Sprint HTC Evo 4G but it appears as though it won't be available in the UK
[Desire General] raxor:
I come from hd2, now im very happy with desire, all its working as desired and no cabs needed ;)
[Desire General] sviftcz:
I was happy HD2 owner. Switched to Desire. I see it this way:

HD2:

- unstable, after 8 years of developing WM (thx microsoft).

- manufacturers mistake causes most devices to develop a "ligter spots" on the screen due the digitizer is coliding with actual display.

- Soft plastic body it deforms on impact.

- laggy touch imput

-+ Is big with BIG screen

+ ActiveSync - working with no problem !

+ multitasking - multitasking - multitasking - multitasking

+ very easily customizable (WM)

+ independent on internet connection (WM)

+ most needet tools alredy integrated in stock rom (file explorer,task manager etc.) = fully usable out of the box.

Desire:

- 5mpix camera makes worse photos then HD2. its like 70% of HD2´s quality.

- only one diode.

- unusable withou internet connection (you wont be able to install anything without downloading at least some file explorer)

- battery compartment doors are stupid and they will be damaged when sim card is exchanged oftenly.

- faulty detection of headphones!!! most regular headphones will work bud no Reproductors !!! Any active HW on jack will cause Desire to act mad. Its TRS and TRRS detection problem (desire exlusive Iam afraid)

- Complicated synchronization (50% cases just wont sync), waiting for official HTC android 2.2

+ Speed of OS

+ stability is better then WM bus Iphone OS is still most stable.

+ Android OS (it is still new and under development, bud already lightyears ahead in front of WM)

+ Google Market lots of apps in one place.

+
[Desire General] foxmeister:
It would be rather pointless if it was, since it is a CDMA/WiMAX device and there are no networks in the UK that support either of these for telephony (though I believe there are some small WiMAX networks for local wireless broadband in places).

Regards,

Dave
[Desire General] foxmeister:
Why have this as a particular plus point for WinMo, when Android multitasks too?

Regards,

Dave
[Desire General] Borgini:
Just a thought:

I came from 3gs to desire and consider it better, actually so much better that it makes you wonder just what apple will come up with. Apple are used to having a market to itself and a widely accepted "best" phone of its kind. That has been blown away by the desire (my opinion) but I do wonder just how good the 4g will be against such competiton as the desire on android 2.2. I just cannot imagine apple accepting defeat by releasing something only as good or not quite as good as the desire. It would mean a uturn on flash and maybe some new tricks. I bought my phones outright just in case apple come up with an absolute show stopper BUT it will have to make the desire look like an abacus before I'd pay the mad iphone tariff's again. Android is just to good to be slung over a barrel by apple's controlling ways and prices. Bottom line, I'm fasicinated what the 4g will offer but suspect not enough, though its only a week or so to being announced so watch the "unveiling first" then you'll most likely go get a desire. If we were months away from unvieling I'd say just get a desire. I have only one negative of susbstance to offer about the desire and that is battery life. If you used only as a phone and text then of course its fine but using its capabilities I find its worse than iphone on battery but I can live with it via usb chargers in home, car and work.
[Desire General] alias_neo:
Apple?

Apple is out of the game.

All they ever try and do is put bigger storage, and a slightly better camera to make a fatter phone.

It's the same old since the start of the iPod.

They won't come up with anything new, and the whole idea behind the iPhone OS is what holds it back.

As long as you stick with an OS that insists that access to everything is done by shortcuts on your homescreen (and yet still not multitask the way it should), it's going nowhere.

They're trying to do the Windows/Mac thing without the menus.

Look at it this way. I don't have a single icon on the desktop of any of my computers, but still I can access anything I want just as simply, or even see what I want without clicking anything. (a la android + widgets).

Apple made it so you can't see a thing on your home screen, except maybe the current date if you have your calendar icon set to display it.

I speak from experience here, I started with WinMo, and couldn't handle it, I moved to the iPhone and it was a heap of junk, gave it away (free) weeks after spending several hundred on it. Moved to the Xperia, WinMo again, it was nice, but still lacking, even with developing WinMo 6.5 ROMs etc. Then I came to the HTC Hero, amazing phone, best ever I'd say. Then came along the Desire and blew it out of the water. Lets just say, I'm Android for life now, until the next big startup comes and knocks it off its podium.

That being said, if you like customization without the trouble, the nexus is also a nice device, if somewhat slightly less capable than the desire, but it will always get the latest first.
[Desire General] snerkler:
I tried the desire out instore the other day, and I have to say I prefer the HD2. The Desire has some nice features, but I wasn't wowed by it. I've read reviews about how good screen is and I have to say I was very disappointed. Yes it was more colourful/vibrant than the HD2, but it's nowhere near as crisp imo.

I'm not wowed by the new specs of the iphone 4 either, it's a slight improvement on the 3Gs, but not exactly groundbreaking and only just catching up with other phones out there.

So I'm at a lost as to which phone to get, the only other phone that looks interesting is the Samsung Galaxy S, but I haven't tried one yet, and it's only on vodafone.

I think I'll just keep the HD2 and go on a sim only contract until something takes my fancy
[Desire General] Vlad_M:
LOL. :D:D:D
[8525, TyTN, MDA Vario II, JasJam General] tgben123:
I have a cingular 8525 (Herm100) that I was running windows 6.5 on from Scotty 93.

This ROM the HTC Home version.

Recently it started hard resetting randomly and finally the last time it hard reset on its own, it became stuck in bootloader mode. Whenever I try to flash a Rom on it everything works fine and the progress bar comes up until the very end. As soon as the progress bar disappears, the Rom should boot but the bootloader just comes back up. I have HardSPL 2.10 from Olipro on it.

I looked at common bricked hermes cases and it didnt fit any of them. I have run out of ideas of what to do. Any help would be greatly appreciated.