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?!!!!
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
Not sure if this is the place to get an answer, but I have a big problem. HelixLauncher has locked my Droid Getting a pop-up message: "Helixlauncher has stopped unexpectedly, please try again" with a small command window that says "Force Close". Touching Force Close just brings back the message again and no other commands are possible. Tried removing battery, but same issue repeats. Phone is currently unusable until I find a solution. Please help.
You could use adb to remove helixlauncher. That is, if you didn't remove the stock launcher.
adb remount
adb shell
rm /system/app/ whatever the name of the helix launcher app is
Click to expand...
Click to collapse
sounds like someone should have nanded ..... if whats posted above doesn't work, re-flash your rom.....take it as a lesson, nanding is your best friend
Your, ah, Droid? Not that I think you should be stoned and chased out for posting about something non-N1, but...
That aside, were you using just plain HelixLauncher or HelixLauncher2? The latter was developed for the N1 and, as I understand, doesn't play nice with Droids.
N1 in same trouble
Although tech savvy, still new to Android & N1.
Thought I needed HelixLauncher and installed it on to my N1 w/ 2.1 u1. Was working ok, but I decided to drop screen size to 1.
It's also possible, but unsure about this, that I tried installing HL2.
In short ended up with unending prompt and the same issues as listed in original post.
Looking into resetting, using pwr+vol.dwn. Is that what was meant by re-flashing, or that's something harsher? Couldn't find what 'nanding' means.
Also, the N1 is not rooted, whatever that means again.
Ended up eventually resetting phone to factory values. Reconfiguring phone now..
Actually, if you're fast enough you can stop this fc loop.
You need to get to Settings | Applications | Manage Applications and then clear the defaults for HelixLauncher so that you can select the regular launcher.
But how with constant fc? I did it this way:
When HL fc's it will briefly throw you out to the last screen you had active before it tries to reload (you only get half a second or so). The time that you do get should be enough to enter one or so commands... so after fc #1, press close then quickly hit the menu button and 'Settings', HL will launch again and fc again, after pressing close you should see the settings page, hit Applications, HL will launch again and fc, press close and hit Manage Applications... etc, etc.
Painful but perhaps better than a rebuild if you have no other way.
YMMV
Yeah, I tried, but wasn't fast enough. It's like the wild wild west.. the slowest gun lost.
It seems either Android or the launcher should offer a more graceful bailout in scenarios like this. Seems like a serious bug to me. And I've written a few of those myself..
EkoTonic said:
Yeah, I tried, but wasn't fast enough. It's like the wild wild west.. the slowest gun lost.
It seems either Android or the launcher should offer a more graceful bailout in scenarios like this. Seems like a serious bug to me. And I've written a few of those myself..
Click to expand...
Click to collapse
lol, yeah, the gun slinging took me a bit of time!
And the problem is a recognised one BUT the instructions are clear... wipe the data before reverting from Helix to stock and when upgrading roms... the dev has tried to put failsafes in but short of deleting the data there are few options...
But, since the warning is in place, I don't think we can call it a bug, rather an understood limitation... painful nevertheless.
PS - if you've got Set CPU installed you could try and get to that and set your speeds a low as possible, this will give you more time... still requires the gun though.
Did you install it as a system app? Launcher2.apk ?
The suckiest option is to always do a factory reset, as long as you didn't flash the helix launcher. This will delete the Helix Rom, but it will also delete everything from your phone. Proceed with caution!
britoso said:
Did you install it as a system app? Launcher2.apk ?
Click to expand...
Click to collapse
Installed from app store. Went searching for Helix and got 2 versions. Installed 1st and was trying to figure out how much I liked it. Noticed it made things faster, so I was loving that. But then decided to see if settings->scrn size option allowed me to jam more apps on the front page. So, I was playing with that, I believe {set it to 1?}.
As I would be hitting the Home page, it kept asking me how I wanted to complete that action, Default or Helix? So, I made Helix the default action. Then at one point, I was unable to return to the Home page.
Misery followed..
Now, I see from djmcnz's posting that there is supposed to be some sort of warning somewhere, but none on the App store intro of the app.
In either case, imho, it's not ok for an app to risk this kind of loss of functionality, not to mention data.
FYI, I have not left any of the negative comments that show in the app store. I understand the developers behind this app are proud of their work and rightly so. I however will not risk it again. It's not that important to me to be bleeding edge.
EkoTonic said:
Now, I see from djmcnz's posting that there is supposed to be some sort of warning somewhere, but none on the App store intro of the app.
Click to expand...
Click to collapse
Yes, sorry I was referring to notices in this forum.
I have rooted my phone, MT4GS, and discovered the /system/app with all the things that are installed and some that are not installed on the phone. These include all the CRAP that I will never use. (teleNAV, friend feed, Zino reader, etc.) I have copied off the contents VIA SD and removed about 33MB if files. Most were pretty obvious. I will include a list. I have made the assumption that if I remove select apps and reset (to factory) my phone, the removed apps will not be installed thus de-crapifying my phone. I would like to know from those more knowledgeable on Android that myself if I am correct. Here is a list of files I have selected for removal. As far as I can tell there is nothing too important, just all the apps I don't use and don't want.
Any thoughts or suggestions would be greatly appreciated. Thanks.
(can provide the rest of the list if needed, i.e. those to be kept)
Bejeweled2_trust5.apk
com.htc.FriendStream3DWidget.apk
com.htc.FriendStream3DWidget.odex
com.htc.TrendsWidget.apk
com.htc.TrendsWidget.odex
com.htc.Twitter3DWidget.apk
com.htc.Twitter3DWidget.odex
com.mobitv.client.tmobiletvhd.apk
desktopPointer-signed-v6.apk
Flickr.apk
Flickr.odex
FriendStream.apk
FriendStream.odex
HtcTwitter.apk
HtcTwitter.odex
Jazz.apk
MobileBackup.apk
MyAccount.apk
MyReportAgent.apk
MyReportAgent.odex
netflix-17-release-android-marketplace-upgrade.apk
qik.apk
slackerradio.apk
TmobileAndroidDeviceCarbon-c42-n123.apk
TMOUS_Navigator.apk
ZinioReader.v2.03.3312.Regular.apk
ZinioSettingsProvider.v2.03.3198.TMobile.Smartphone.apk
If you factory reset using the pdimg59.zip then they'll all be put back on.
Sent from my MT4GS running Bulletproof
Where is that file? I did a search and didn't find anything....
There was also an excellent write-up done in the apps section. It's no longer updated and is kind of buried on page 3 but it's still a great place to start.
http://forum.xda-developers.com/showthread.php?t=1222672
Thanks for the help. I used the bloater apk from the thread. The only thing it would not let me uninstall was Netflix. It's funny also that the MP3 and video trim programs don't show up to be installed, the mysketch, and a few other apk files that are in the app folder.
I will be taking over bloater within the next few days.
Expect it to be updated to include a lot more.
I depreciated the thread siani_8 linked to because of the sticky I have in the developers section.
The sticky hasn't been updated in a while because:
1 - what's there is solid, and useful.
2 - no one else has posted app descriptions.
If other people are willing to post descriptions of what the apps actually do in the thread, i'll update that into the actual reference posts.
I figure that i've set the stage for the rest of the info to be put in, and i've done that much so far. If the community is interested in having descriptions posted, then the community at large will provide them.
The app reference is what inspired Romanbb to write that awesome Bloater app, and what we've all learned since then means more to be added. Bloater is very high on my project list, and it will be included in the new version of Bulletproof just like the last.
Also, that thread that got depreciated is from way back when - right after we first got S-OFF and were able to start deleting useless garbage we were all sick of being stuck with.
Definitely read through it if you are working on this from the ground up, because you'll see how we started to learn what we know today. It's a great exercise, and you'll learn a lot about your phone approaching it by playing along instead of just skipping to the end result.
Any questions feel free to ask, we're all here to help.
I need to add your thread in the compendium too. Its a good write up blue, I can't believe I missed it.
sent from my Agent Orange MT4G Slide using xda premium
I still can't find anything on this pdimg59.zip. Can anyone shed some light on it?
I think what you're referring to is the Stock ROM.
Easy answer:
Think of it like a failsafe for your device. If there is a file by that name on the sdcard, the phone will try to flash it on boot.
It's a more in depth answer then that from a technical perspective, but for just a quick "what is this?" that'll suffice. Someone with more time on their hands will probably come through here to expand on that if you're still curious.
To really decrapify your phone, just delete Rosie and HTCSense from /system/app. Just install another launcher app first.
Blue6IX said:
I think what you're referring to is the Stock ROM.
Easy answer:
Think of it like a failsafe for your device. If there is a file by that name on the sdcard, the phone will try to flash it on boot.
It's a more in depth answer then that from a technical perspective, but for just a quick "what is this?" that'll suffice. Someone with more time on their hands will probably come through here to expand on that if you're still curious.
Click to expand...
Click to collapse
sent from my Agent Orange MT4G Slide using xda premium
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
So I just wanted to make a thread for these units where people can ask/answer questions specific to these devices. May help others as the info online isn't the best, including their own forum site which I have unable to access with a few weeks due to persistent ads...... ?
To get the ball rolling;
I have updated to the new official firmware with the new widget launcher, I like the launcher, well the fact that I have large icons and can have widgets on the home screen.
My issues are,
1) when I start the car (dormancy mode) I am trying to get tasks to run automatically (open rocket player, play audio etc.) Problem is there seems to be a built in task killer that kills macrodroid (which I'm using for my tasks). I have tried autostart apps but these don't trigger as the HU is coming out of dormancy mode and not actually booting. Anyone have a work around for this? If I could get Macrodroid to run I could solve the rest using macros (tasks)
2) Since the new update with the new launcher i no longer have Voice to text, i installed the google app but this caused the launcher to crash and only left me with the recent apps screen, luckily I was able to get back into play store from here and uninstall google app again which brought all back working again.
3) When playing a podcast (Bluetooth streaming from phone) and I want to change to rocket player to play music, if I just tap play on the rocket widget the media starts playing but I get no sound until I open the app, kind of defeats the purpose of the widget being there!
4) when I first installed the unit I had no problems with the illuminate function (headlights dim screen and turn on button lights) this worked for about a month and then for no reason just stopped, now if I turn on my lights the button lights flick on for about half a second and then turn off again, its not an issue with the lights as they work fine when I chose the timed option. I haven't checked my 12v feed yet as I'm guessing its OK due to the flicker, it will happen every time I turn the lights on.
I have tried reset, reflash combos about 6 times at this stage but always with the same results.
I know there are options to change the ROM but I would like to keep it stock for now just in case I need to return it.
fado5ster said:
So I just wanted to make a thread for these units where people can ask/answer questions specific to these devices. May help others as the info online isn't the best, including their own forum site which I have unable to access with a few weeks due to persistent ads...... ?
Click to expand...
Click to collapse
I assume you mean the http://forum.carjoying.com/ forum? If so, mention that. Be concrete.
That is indeed annoying, but there are many hundredths of users on that forum without issues. Maybe your ISP doing something weird.
fado5ster said:
To get the ball rolling;
I have updated to the new official firmware with the new widget launcher, I like the launcher, well the fact that I have large icons and can have widgets on the home screen.
Click to expand...
Click to collapse
The new official ROM?? Which one? The 5 March version? And did you pick the right one of the two? And which unit do you have?
Mention all that! This makes your remark/question useless as people trying to help first need to ask you that.
fado5ster said:
My issues are,
1) when I start the car (dormancy mode) I am trying to get tasks to run automatically (open rocket player, play audio etc.) Problem is there seems to be a built in task killer that kills macrodroid (which I'm using for my tasks). I have tried autostart apps but these don't trigger as the HU is coming out of dormancy mode and not actually booting. Anyone have a work around for this? If I could get Macrodroid to run I could solve the rest using macros (tasks)
Click to expand...
Click to collapse
Search the forum. already many time mentioned. You need the NoKill app. Can be downloaded from here and mentioned here.
fado5ster said:
2) Since the new update with the new launcher i no longer have Voice to text, i installed the google app but this caused the launcher to crash and only left me with the recent apps screen, luckily I was able to get back into play store from here and uninstall google app again which brought all back working again.
Click to expand...
Click to collapse
Don't you search at all? Also known issue and mentioned here on the forum.
fado5ster said:
3) When playing a podcast (Bluetooth streaming from phone) and I want to change to rocket player to play music, if I just tap play on the rocket widget the media starts playing but I get no sound until I open the app, kind of defeats the purpose of the widget being there!
4) when I first installed the unit I had no problems with the illuminate function (headlights dim screen and turn on button lights) this worked for about a month and then for no reason just stopped, now if I turn on my lights the button lights flick on for about half a second and then turn off again, its not an issue with the lights as they work fine when I chose the timed option. I haven't checked my 12v feed yet as I'm guessing its OK due to the flicker, it will happen every time I turn the lights on.
I have tried reset, reflash combos about 6 times at this stage but always with the same results.
I know there are options to change the ROM but I would like to keep it stock for now just in case I need to return it.
Click to expand...
Click to collapse
Again: which ROM are you on? You should mention that. ROMS before 2017 contain bugs, so do they in 2017 but at least a lot less. So make sure you are on a newer ROM. If you already are, like you mentioned above, mention the version. That saves people from asking for the obvious. Before you post read the rules.
Look at this thread and this thread
First of all: Search the forum.
And secondly: Search the forum.
And third: Be concrete. Mention versions, forums, etc. You don't even mention which head unit you have.
I was looking but could only find info on the 1gb model and the thread about the release of the 2gb model.
Thanks for the info but you don't have to be a **** about it.
I missed stuff when searching, I couldn't access the joying forum, I thought saying "their own forum site" would have cleared that. I couldnt access the site to find out if there had been updates, at the time i was on the ONLY UPDATED ROM with the new launcher with customizable widgets.
When i found NoKill I thought it was for steering wheel controls which I don't have so I moved on.
When I asked about model numbers on the joying forum (when I could access it) I was made out to be an idiot too because "They are all the same thing" so forgive me for thinking that. Mine is the JY-UL135N2
Again, Thanks for the info but you don't have to be a cranky prick about it, this is a forum isn't it? Used for discussion and help?
I was only saying something like this with info in one place would be good, if its out there already then sorry, mods can delete and ill crawl back into my hole of idiotness
Yes, I was annoyed but I did give you a number of helpful links and be honest: you were not very exact in your phrasing.
And w.r.t. the roms: They are on the joying blog59 page which is also mentioned several times on several postitions in this forum, and you could also have found it from the "normal" joying website carjoying.com
Even though I was annoyed I tried to help you. If your phrasing was more concrete that would have been a lot faster. And you still don't mention which ROM you are currently using, so nobody can give you an exact answer.
You can be angry with me, but clear communication would have prevented my irritated reply.
I am on the 2017222 rom but will be updating to latest tomorrow, have downloaded just need to do the HU side of it. I can get access to the Joying site using your link and only your link, not sure why or whats going on as this includes the main joying site too.
I plan on updating, attempting root then install NoKill.
I am giving the info I have, I don't know a lot about these devices and although I have rooted phones and tablets before I have never done anything like this.
You did give me helpful links and I thank you for that but please don't be too angry with people asking questions. I realise you know how this works but others don't and are afraid of damaging the device. Before your link which I used to access the updates page I had no way of checking for updates as I couldn't get onto the page
fado5ster said:
I plan on updating, attempting root then install NoKill.
Click to expand...
Click to collapse
There is no real need to update to the March 5 ROM if you already have the 22 Feb ROM.
The ROM is rooted. What you mean is that you want to install a SuperUser app like SuperSU or Kingroot or the like.
You don't need to SuperSU your ROM. You can install the NoKill version just like that as the ROM is rooted. You simply don't have the nice, userfriendly superuser apk on the system.
surfer63 said:
There is no real need to update to the March 5 ROM if you already have the 22 Feb ROM.
The ROM is rooted. What you mean is that you want to install a SuperUser app like SuperSU or Kingroot or the like.
You don't need to SuperSU your ROM. You can install the NoKill version just like that as the ROM is rooted. You simply don't have the nice, userfriendly superuser apk on the system.
Click to expand...
Click to collapse
So there is no real advantage to the March 5 ROM?
Oh, I didn't know it was rooted still, thought they stopped that on the 2gb devices.. I'm not even sure if I need root for anything, all I wanted it for was to get to the /system... folder to copy NoKill to. Can I get there without SuperSU app using ES file explorer? Am I safe to delete the existing nokill.apk in there 1st and then copy in the new file? It won't cause any issues not having the apk for the few seconds? (Probably a stupid question)
fado5ster said:
So there is no real advantage to the March 5 ROM?
Oh, I didn't know it was rooted still, thought they stopped that on the 2gb devices.. I'm not even sure if I need root for anything, all I wanted it for was to get to the /system... folder to copy NoKill to. Can I get there without SuperSU app using ES file explorer? Am I safe to delete the existing nokill.apk in there 1st and then copy in the new file? It won't cause any issues not having the apk for the few seconds? (Probably a stupid question)
Click to expand...
Click to collapse
The Sofia server is loaded upon boot and stays in memory. So no problem there.
Best thing to do via adb.
Code:
adb push Sofia-1-C9-Server-V1.0.apk /sdcard/
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk.old"
adb shell "su -c cp /sdcard/Sofia-1-C9-Server-V1.0.apk /system/app/Sofia-1-C9-Server-V1.0"
adb shell "su -c chmod 644 /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk"
adb shell "su -c ls -l /system/app/Sofia-1-C9-Server-V1.0"
last command does nothing toyour system. It should only list the new apk and the old apk.old.
and then reboot your unit.
I know you are going to hate me for this but any time I've tried pushing files using adb I end up messing it up and bricking it.
Looks like the illumination problem was due to the car.. The illumination wire was in a different place to the joying connector, I repinned it and working now but still doesn't explain how I had it working fine for a month.. Really weird, had issues with 12v switched and constant 12v too.. Had to swap them around.. Seems to be Kia's doing and not joying.. Very strange
Macrodroid not running in background FIXED
Hey there! You probably fixed the issue with macrodroid by now but I had the same issue and I fixed it by installing Macrodroid as a system app. That did the job for me. Just did a reboot and waited for macrodroid to come up.