Related
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 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?!!!!
Hi guys,
I rooted my phone and have been using Cyanogen since and never looked back. The phone works like charm, and with 2.2.1 installed, they keyboard is much better and I can actually use the phone for dialing (the number pad doesn't get stuck!)
I looked in the form but my search brings back hundreds of results that do not seem related to what I need. Cyan comes with some apps I simply do not ever use: The car home one, terminal emulator, DSPMAnager (what is it anyway?) and the voice dialer. First, are any of these apps are needed to run the phone, and can I re-install them separately (without reloading the whole ROM) if something goes wrong? Then, the question is, how do I uninstall them, since I do not have an uninstall option? Is it possible to uninstall Google Talk (because I think it comes as a part of the Google Tools or whatever...), since it does not allow me to log in for more than one account?
Then, I have a more general question:
Is Cyan with gingerbread available from the HTC Hero? Would you guys recommend it? I don't feel I really need it because the phone is fine, but maybe I'm missing out on something I do not know... what are the big new things, besides the keyboard (which I understand can be installed individually anyway).
Thanks!
Use titanium backup it uninstalls stock apps. But be careful which ones u uninstall they will mess ur phone up and cause foreclosures
Sent from my HERO200 using XDA App
beholder121 said:
Hi guys,
I rooted my phone and have been using Cyanogen since and never looked back. The phone works like charm, and with 2.2.1 installed, they keyboard is much better and I can actually use the phone for dialing (the number pad doesn't get stuck!)
I looked in the form but my search brings back hundreds of results that do not seem related to what I need. Cyan comes with some apps I simply do not ever use: The car home one, terminal emulator, DSPMAnager (what is it anyway?) and the voice dialer. First, are any of these apps are needed to run the phone, and can I re-install them separately (without reloading the whole ROM) if something goes wrong? Then, the question is, how do I uninstall them, since I do not have an uninstall option? Is it possible to uninstall Google Talk (because I think it comes as a part of the Google Tools or whatever...), since it does not allow me to log in for more than one account?
Then, I have a more general question:
Is Cyan with gingerbread available from the HTC Hero? Would you guys recommend it? I don't feel I really need it because the phone is fine, but maybe I'm missing out on something I do not know... what are the big new things, besides the keyboard (which I understand can be installed individually anyway).
Thanks!
Click to expand...
Click to collapse
1. Like the above poster said, use titanium backup to uninstall. It's free in the market. All four of those apps can be removed with no ill effects, however, I would keep terminal emulator in case you ever need to push our pull apk's, decide to use the batt-tweak. Stuff like that. DSPManager is a equalizer.
2. Yes, gb is available in cyanogenmod flavor right here: http://mirror.teamdouche.net/?device=heroc It had some minor lag issues with the home screen, but camera and gps is working for me. Not sure if compcache and jit is, though.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
user7618 said:
1. Like the above poster said, use titanium backup to uninstall. It's free in the market. All four of those apps can be removed with no ill effects, however, I would keep terminal emulator in case you ever need to push our pull apk's, decide to use the batt-tweak. Stuff like that. DSPManager is a equalizer.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Click to expand...
Click to collapse
I'd watch out for Google Talk though...doesn't that break some push notifications (i.e. Gmail)? Could be wrong, have been before
Off the top of my head without looking at a fresh install, these are safe to remove without doing anything special (I dont have any of them):
DSP, Protips, PacMan, FileManager, email (if you only use the gmail app), Live Wallpaper Picker, CMStats, CM Wallpaper, Latin tutorial, Development, Theme Chooser (and the other theme apk along with the two themes preloaded in the /system/app folder), Spare Parts, ROM Manager...If you want to know about any others, just ask...there are far more I have removed, but like I said, they are gone, so I don't remember them
how about fotakill? don't know what it does, so I didn't remove it.
Sent from my HTC Hero CDMA using XDA App
FOTAKILL i believe is the cyanogen updater, do a google search
I removed it with no issues.
-- Sent from my Sprint SuperHero --
Here's link from Cyanogen wiki that gives a list of apps and some details about them - like what they are, can they be removed and such. Also, it documents ways to remove apps.
http://wiki.cyanogenmod.com/index.php?title=Barebones.
ranger61878 said:
I'd watch out for Google Talk though...doesn't that break some push notifications (i.e. Gmail)? Could be wrong, have been before
Off the top of my head without looking at a fresh install, these are safe to remove without doing anything special (I dont have any of them):
DSP, Protips, PacMan, FileManager, email (if you only use the gmail app), Live Wallpaper Picker, CMStats, CM Wallpaper, Latin tutorial, Development, Theme Chooser (and the other theme apk along with the two themes preloaded in the /system/app folder), Spare Parts, ROM Manager...If you want to know about any others, just ask...there are far more I have removed, but like I said, they are gone, so I don't remember them
Click to expand...
Click to collapse
No, I think you may be right. For whatever reason, I was thinking google voice, which isn't even part of the gapps or cm apps. Leave talk installed.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
If you delete Google Voice Search, you will need something else (Vlingo, etc.) in order to have a mic on your keyboard I believe.
Sent from my HTC Hero CDMA using XDA App
Wow thanks for all the responses guys.. I installed some apps and so far I'm good. Now I just need to figure out how to get my dial pad to show up after it turns off during a phone call.
beholder121 said:
Wow thanks for all the responses guys.. I installed some apps and so far I'm good. Now I just need to figure out how to get my dial pad to show up after it turns off during a phone call.
Click to expand...
Click to collapse
Press the menu key.
-- Sent from my Sprint SuperHero --
Evening folks, as phones such as my trusty HTC Sensation come to the end of their useful lives, to be replaced by other newer phones, I was wondering if there was such a thing as a 'non phone' ROM I could flash which would remove the calling, texting etc functions and allow it to be used as a 'ipod touch' (for want of a better description). I would be quite happy putting a dummy SIM card into the phone and simply not allowing it to touch the network but I would be happier with the calling etc functions removed from the phone, especially as I'm hoping to give it to my kids to play with.
Any advice? Does such a thing exist? I had a quick google and couldnt really see anything too relevant. Happy to be corrected on that though!
Haven't seen a ROM like that here..
I'm not sure why you want those features removed, but if you want that your kids don't use them, you can set up a password lock on those apps.
I don't think there's any such ROM. But why you insisting on no network feature. Just don't insert the SIM and it will work.
Sent from my HTC Sensation Z710e
Oh, I know I could stop it like that but just was wondering if there was a 'lighter' ROM without the phone aspects.
bowser4 said:
Oh, I know I could stop it like that but just was wondering if there was a 'lighter' ROM without the phone aspects.
Click to expand...
Click to collapse
Or then maybe Link2SD can freeze the apps, so they won't be shown in appdrawer.
bowser4 said:
Oh, I know I could stop it like that but just was wondering if there was a 'lighter' ROM without the phone aspects.
Click to expand...
Click to collapse
You can remove those by using certain apps that can do it. I think titanium backup has this functionality. However, as these apps are not heavy, simply hiding them will do the work.
Edit: Just remembered, on most ROMs. the phone and messaging apps have other apps that depend on them, so removing them completely might cause issues. Hiding them from the drawer (possible on many AOSP based launchers and some Sense ROMs built-in) would be the simplest way to "remove" the apps.
astar26 said:
You can remove those by using certain apps that can do it. I think titanium backup has this functionality. However, as these apps are not heavy, simply hiding them will do the work.
Edit: Just remembered, on most ROMs. the phone and messaging apps have other apps that depend on them, so removing them completely might cause issues. Hiding them from the drawer (possible on many AOSP based launchers and some Sense ROMs built-in) would be the simplest way to "remove" the apps.
Click to expand...
Click to collapse
Thanks for that, I'll go ahead and hide them. Appreciate the info folks, many thanks.
First off, great forum, tons of awesome information.
I apologize in advance as I am sure these questions have been answered a million times but being new to a Rooted device, I'm looking for a little clarity and guidence.
I have the AT&T variant of the LG G3, awesome awesome device.
I rooted the device with Stump Root (doesn't get any simplier then that)
I then installed "Xposed Installer", "Titanium Backup", "SuperSu", and "G3 Tweak Box".
Questions,
Xposed
1) Seems pretty straight forward, is there anything as a newbie I should know, avoid, lookout for?
Titanium Back Up
1) Well, it all looks like chinese to me. First off, I have backed up all my apps, but when I check "Backup/Restore" I still see certain apps as "No Backup Yet". Why?
2) Also, how often should I backup the apps? Is once enough?
3) After backing up bloatware, is it then safe to remove and delete?
4) Schedules, should I be enabling either option?
5) Main Menu, whats the most important actions to take here?
SuperSu
1) Seems fairly straight forward, what are "logs" and do I need to pay attention to them?
2) Settings, is there any options I need to change, take advantage of? Anything I should avoid tampering with?
Misc Questions
1) When system updates come out, will this cause me to lose Root access, if so why and how do I avoid that?
2) Is there any prevenitive measures that I need to take to protect my device against any crashes, bricking, or any other general screw ups a newbie might cause with Root access?
3) Also, how do I not destroy my device while learning to take advantage of Root access?
4) In addition to what I have already installed, is there any other must have apps for the Rooted user?
I appreciate any & all help, thanks alot in advance!
I'll answer what I can, as best I can.
Vic098 said:
Xposed
1) Seems pretty straight forward, is there anything as a newbie I should know, avoid, lookout for?
Click to expand...
Click to collapse
Make sure you have BusyBox installed as well.
It's best to change one setting at a time. It's tedious, especially if you have to reboot after changes, but if something goes awry, it's much easier to track down the conflict or bug, especially if you're using multiple modules.
Titanium Back Up
1) Well, it all looks like chinese to me. First off, I have backed up all my apps, but when I check "Backup/Restore" I still see certain apps as "No Backup Yet". Why?
Click to expand...
Click to collapse
There's a definite learning curve with TB. I'm not sure why some apps might not back up. It could be because they're core components of the OS and are write protected.
2.) Also, how often should I backup the apps? Is once enough?
Click to expand...
Click to collapse
When talking about batch backups, "enough" is at your discretion. No harm in doing them periodically, especially if you install a bunch of new apps. Backing up individual apps is good to do before updating them, in case you decide you preferred the older version. Or a game you don't want lose progress in or revert to an old "save".
3) After backing up bloatware, is it then safe to remove and delete?
Click to expand...
Click to collapse
Depends on the bloat. Some apps by AT&T or LG might seem unnecessary or unwanted, but actually are necessary and can cause crashes or force closes ("unfortunately XXXXX process has stopped"). Always back them up first, and remove them one at a time. It's better to freeze them first, then delete after testing. Personally, I don't delete bloat, just freeze it.
4) Schedules, should I be enabling either option?
Click to expand...
Click to collapse
Both, if you want to schedule period backups rather than just doing them youself. Again, your discretion .
5) Main Menu, whats the most important actions to take here?
Click to expand...
Click to collapse
Batch actions and Preferences (where to store them) are all you really should be messing with now. At least until you learn more.
SuperSu
1) Seems fairly straight forward, what are "logs" and do I need to pay attention to them?
Click to expand...
Click to collapse
The logs keep track of what was granted SU access and when. Not really necessary.
2) Settings, is there any options I need to change, take advantage of? Anything I should avoid tampering with?
Click to expand...
Click to collapse
PIN code is your choice. If you're the only one that ever uses your phone, it's not really necessary, but if if you let others use it frequently(for games, or to browse or log into Facebook), you might want to use a PIN so they don't simply hit "grant" whenever SuperSU requests rights. I use "prompt" as the default action, so I know what needs to access the system. For example, some apps that don't require root (like Clean Master) have additional functions if you are rooted, and this might not be clear in the description in Play. That way you know, and you won't accidentally screw something up. Also, malicious apps that have no business with root access can be identified and blocked.
Misc Questions
1) When system updates come out, will this cause me to lose Root access, if so why and how do I avoid that?
Click to expand...
Click to collapse
You can sometimes (usually?) lose root access after an update, but it's usually possibly simply to re-root with the same method. If not, it's best to wait to do the update until others can confirm/deny. SuperSU has a "survival mode" that can try to keep root during an update, but again, it's best to wait for confirmation by others.
2) Is there any prevenitive measures that I need to take to protect my device against any crashes, bricking, or any other general screw ups a newbie might cause with Root access?
3) Also, how do I not destroy my device while learning to take advantage of Root access?
Click to expand...
Click to collapse
Read, ask, and learn. It's easy to grow confident and think you're more clever than you really are and really screw something up (I know from experience). If you look at the first couple pages of general Q&A/Help forums, you'll see lots of people who did stupid stuff and now have bootloops and crashes and bricks. Do lots of searches, here, on google, and youtube. You can often find guides for what you're wanting to do.
4) In addition to what I have already installed, is there any other must have apps for the Rooted user?
Click to expand...
Click to collapse
AdAway or other ad blocker. Not only does it block ads in your browsers, it blocks Google ads in free apps. Apart from being cleaner and more convenient, since ads don't get loaded, pages load faster and you consume less data.
BetterBatteryStats gives you much more info on what's draining your battery than the stock Android function.
Some sort of root browser/explorer is essential. You can use it to completely delete folders/data that got left behind even after an app is deleted (which can sometimes cure Google Play Store errors), among other things.
I personally like ROM Toolbox Pro. It doesn't really do anything special, just packs a ton of utilities that you can get elsewhere into a single app.
SQLite editor is necessary to do some things, but you'd better make sure you know what you're doing before doing anything with it.
WiFi Tether Router might be able to bypass AT&T's tether app. Changing some settings with SQLite might be necessary. You'd have to research this for your device.
Those are the root apps I use, as well as Xposed and assorted modules to do theming or other functionality tweaks. Xposed is quite powerful, and you should familiarize yourself with what the multitude of different modules can do. The possibilities are seemingly endless, as developers come up with no mods every day to do new things that nobody else has done yet (or ported other mods to work with other devices).
I appreciate any & all help, thanks alot in advance!
Click to expand...
Click to collapse
Good luck and have fun!
Planterz said:
I'll answer what I can, as best I can.
Make sure you have BusyBox installed as well.
It's best to change one setting at a time. It's tedious, especially if you have to reboot after changes, but if something goes awry, it's much easier to track down the conflict or bug, especially if you're using multiple modules.
There's a definite learning curve with TB. I'm not sure why some apps might not back up. It could be because they're core components of the OS and are write protected.
When talking about batch backups, "enough" is at your discretion. No harm in doing them periodically, especially if you install a bunch of new apps. Backing up individual apps is good to do before updating them, in case you decide you preferred the older version. Or a game you don't want lose progress in or revert to an old "save".
Depends on the bloat. Some apps by AT&T or LG might seem unnecessary or unwanted, but actually are necessary and can cause crashes or force closes ("unfortunately XXXXX process has stopped"). Always back them up first, and remove them one at a time. It's better to freeze them first, then delete after testing. Personally, I don't delete bloat, just freeze it.
Both, if you want to schedule period backups rather than just doing them youself. Again, your discretion .
Batch actions and Preferences (where to store them) are all you really should be messing with now. At least until you learn more.
The logs keep track of what was granted SU access and when. Not really necessary.
PIN code is your choice. If you're the only one that ever uses your phone, it's not really necessary, but if if you let others use it frequently(for games, or to browse or log into Facebook), you might want to use a PIN so they don't simply hit "grant" whenever SuperSU requests rights. I use "prompt" as the default action, so I know what needs to access the system. For example, some apps that don't require root (like Clean Master) have additional functions if you are rooted, and this might not be clear in the description in Play. That way you know, and you won't accidentally screw something up. Also, malicious apps that have no business with root access can be identified and blocked.
You can sometimes (usually?) lose root access after an update, but it's usually possibly simply to re-root with the same method. If not, it's best to wait to do the update until others can confirm/deny. SuperSU has a "survival mode" that can try to keep root during an update, but again, it's best to wait for confirmation by others.
Read, ask, and learn. It's easy to grow confident and think you're more clever than you really are and really screw something up (I know from experience). If you look at the first couple pages of general Q&A/Help forums, you'll see lots of people who did stupid stuff and now have bootloops and crashes and bricks. Do lots of searches, here, on google, and youtube. You can often find guides for what you're wanting to do.
AdAway or other ad blocker. Not only does it block ads in your browsers, it blocks Google ads in free apps. Apart from being cleaner and more convenient, since ads don't get loaded, pages load faster and you consume less data.
BetterBatteryStats gives you much more info on what's draining your battery than the stock Android function.
Some sort of root browser/explorer is essential. You can use it to completely delete folders/data that got left behind even after an app is deleted (which can sometimes cure Google Play Store errors), among other things.
I personally like ROM Toolbox Pro. It doesn't really do anything special, just packs a ton of utilities that you can get elsewhere into a single app.
SQLite editor is necessary to do some things, but you'd better make sure you know what you're doing before doing anything with it.
WiFi Tether Router might be able to bypass AT&T's tether app. Changing some settings with SQLite might be necessary. You'd have to research this for your device.
Those are the root apps I use, as well as Xposed and assorted modules to do theming or other functionality tweaks. Xposed is quite powerful, and you should familiarize yourself with what the multitude of different modules can do. The possibilities are seemingly endless, as developers come up with no mods every day to do new things that nobody else has done yet (or ported other mods to work with other devices).
Good luck and have fun!
Click to expand...
Click to collapse
Thanks for the detailed response. Just a follow up, when googling AdAway, I see some long threads and what I think are different versions, is there a link, or a place that I can find the latest (and safe??) version to download?
Again, appreciate the feedback.
Vic098 said:
Thanks for the detailed response. Just a follow up, when googling AdAway, I see some long threads and what I think are different versions, is there a link, or a place that I can find the latest (and safe??) version to download?
Click to expand...
Click to collapse
http://d-h.st/BZs
If you haven't done so already, you'll have to go into your settings and check the box to allow app installation from unknown sources. Then just go to that link on your device, download the .apk, then install. Go to a site with a heavy amount of ads like phonearena.com (Verizon ads up the wazoo) and see how long it takes to load. Then reboot, and load the app. It'll update sources, and it'll be good to go. Go back to that website and marvel at how quickly it loads without the ads.
Vic098 said:
Thanks for the detailed response. Just a follow up, when googling AdAway, I see some long threads and what I think are different versions, is there a link, or a place that I can find the latest (and safe??) version to download?
Again, appreciate the feedback.
Click to expand...
Click to collapse
Is this a Xposed Module or some APK off the google market? Because if it's an Xposed Mod then links are direct.
Radigen said:
Is this a Xposed Module or some APK off the google market? Because if it's an Xposed Mod then links are direct.
Click to expand...
Click to collapse
Gotchya.
Planterz said:
If you haven't done so already, you'll have to go into your settings and check the box to allow app installation from unknown sources. Then just go to that link on your device, download the .apk, then install.
Click to expand...
Click to collapse
The link downloads a file called mobogenie. Is that correct?
Vic098 said:
The link downloads a file called mobogenie. Is that correct?
Click to expand...
Click to collapse
No. I don't know what that is, and I can't recreate whatever you did to get that. Whatever it is, don't install it.The file to download will match the name in the description. Make sure you're not clicking an ad (oh, the irony).
Try this link instead. https://f-droid.org/repository/browse/?fdid=org.adaway or try downloading on your computer to Dropbox or Drive or whatever cloud storage you use, or just download it to your computer, plug in your phone, copy it to your phone's storage, and run it from there.
Radigen said:
Is this a Xposed Module or some APK off the google market? Because if it's an Xposed Mod then links are direct.
Click to expand...
Click to collapse
Neither. It's not an Xposed module, just a regular app, but it's not available from the Google Play Store because they don't want you blocking your ads, so you have to side load it.
Planterz said:
No. I don't know what that is, and I can't recreate whatever you did to get that. Whatever it is, don't install it.The file to download will match the name in the description. Make sure you're not clicking an ad (oh, the irony).
Try this link instead. https://f-droid.org/repository/browse/?fdid=org.adaway or try downloading on your computer to Dropbox or Drive or whatever cloud storage you use, or just download it to your computer, plug in your phone, copy it to your phone's storage, and run it from there.
Neither. It's not an Xposed module, just a regular app, but it's not available from the Google Play Store because they don't want you blocking your ads, so you have to side load it.
Click to expand...
Click to collapse
Oh alright, thanks then, good thing we're all developers here.