"Car Dashdroid" Default Launcher Problem - MTCB Software Development

Totoix said:
I use car dashdroid. After upgrading to a newer version of xdauto, car dashdroid started to forget that it is the default launcher. Sometimes the device opens directly with cardashdroid interface, but sometimes it doesn't and asks for an interface (google launcher or the other launcher). In that screen, there is no car dashdroid option. I select, default launcher with just once option and open car dashdroid manually. In its properties, I set (which is already set, but, by unselecting and selecting again) the application as the default launcher by clicking on option that assigns home button to car dashdroid default interface.
After selecting the option and pressing home, the xdAuto asks for default launcher. This time, the list includes car dashdroid. I choose to use always this launcer. But after one or two boots, it asks again for a launcher without car dashdroid on the list.
Do you have any idea why this is happening?
Click to expand...
Click to collapse
I have the exact same issue on the Malysk ROM for all versions I've used since last year. This isn't isolated to the xdAuto ROM for Newsmy Carpad. Anyone have any ideas?

Related

default launcher wont stay default.

on villain rom 2.4.2 and use launcher pro
last few days whatever launcher I choose , the launcher won't stay as default after ive ticked the box.
happens on tw launcher asell so is not launcher pro.
have cleared defaults in mange applications numerous times
have reinstalled launcher pro.
have frozen some apps, so that could be a culprit. but none I would of thought would cause this issue.
anyone got any ideas?
any help much appreciated before I reflash vr.
have also tried home switcher app to clear the defaults and choose but still same issue.
a restart has fixed the issue for about 5 mins before, but it always starts again
this unfortunately happens from time to time with launcher pro. I love the launcher but the application has not been updated in a while. just press the home button and it should automatically bring back launcher pro.
blunted09 said:
this unfortunately happens from time to time with launcher pro. I love the launcher but the application has not been updated in a while. just press the home button and it should automatically bring back launcher pro.
Click to expand...
Click to collapse
just pressing the home button leaves the select your launcher window up. I think our problems are different.
launcher pro is working fine, even if I select touch wiz as my default launcher, enter an app, then press the home key it asks me again to select the launcher and the default tick box.
same as when I reboot the phone, first thing it asks me is what launcher I want!
think I'm gonna wipe and reflash, but just wanted to see if anyone else had experienced this problem. as this only started a week after I flashed villain rom, so don't think, its rom related either.
Other than having to change my default launcher on boot, I'm quite happy with my nexus 7. Wonder if the stock launcher can be removed without crippling the system.

[Q] -SOLVED- Work around twlauncher crash loop w/o wipe?

--twlauncher crash problem solved, see below. Feel free to answer general question though
Hi all!
Ran into a problem with my Galaxy S that I'd be really greatful if you could help me with.
THE QUESTION:
Is there some way of accessing the phone from my PC via USB and changing settings?
THE THING:
I have been running my system without problem for a while. Haven't made a backup though, stupid #%ยค as I am. When I was using the (stock) Internet browser I tried to add a (mobile) web page to the Start panel (or whatever it is called). Since then I get the error message "The application Start (process com.sec.android.app.twlauncher) has stopped unexpectedly." Gives option to "Force Close". Whenever I do, the error comes back after a few seconds if I am at the default screen and don't quickly go into the phone or sms app. Basically, I can't do anything that my Ericsson T10 couldn't do in 1999...
I think all of my "start screens" were already filled with apps, that there wasn't room for another, and this might be the problem that causes the twlauncher crash loop.
THE QUESTION (again, in context):
So, is there some way of accessing the phone from my PC via USB and changing settings? During my searching I've come to believe that two possible solutions might be to clear twlauncher's settings or to set another launcher as default, but in the current state I can't get to the settings neither from the started phone or from the Darky recovery console.
I know I could just wipe and reinstall everything but that feels like nuking a mosquito...and it's so tedious... If there is some smoother way to get at the problem that would be nice. Also I'm curious if it can be done, and I'm probably not alone.
THE SYSTEM:
Samsung Galaxy S (GT I9000)
Rooted
Android 2.2.1
Darkys' ROM v9.4 Extreme edition
Voodoo
Any pointers would be greatly appreciated, thanks a lot!
/Fredrik
Ok folks, I am happy again!
It seems things fix themselves for me if I only write a thorough post on some forum...
I went to android market with my PC, logged in with my google account (where I had apparently added my phone before) and downloaded another launcher (ADW) to replace my crashed twlauncher. After that I fiddled some more with the phone - obviously turned off network mode from the power menu (the menu that you get when holding the power button 3 sec). And then I wrote the above post.
Just now I was going to make a phone call (which was about the only thing working, remember?) but the screen had gone all black except from the status bar at the top, which didn't respond when I tried to pull its menu down. Brought up the power menu. At first it didn't respond to my touch but after a while it agreed to turn on network mode for me. Then ADW downloaded and installed itself. I still couldn't pull down the status bar menu to click on the "Download complete" icon and launch ADW that way, but I pressed the Home button and got a menu asking "Complete this task with:" and some choices. I ticked the box "always use this program" and selected ADW. Now, ADW started and I am back on track! No wipe or reinstall needed!
SO, short version solution to twlauncher crash loop: log into your Android market account from a PC, search for "launcher" and install one of your choice, then wait for the phone to download and install it. Then press Home, tick "Always use this program to complete this task" and select your new launcher!
Yeah, that solved my problem with Tw.launcher but if anyone has an answer to the question in the thread - is there a way to log into the phone from a PC to change settings - feel free to share your knowledge!
Addition - resetting twlauncher to be able to use Kies
Ok, after installing another launcher as described above, proceed with the following to prevent twlauncher from crashing in the future. You will need to this do if you want to connect with your computer using Kies, since Kies apparently cannot connect to other launchers (such as GO launcher or ADW).
1. Open Settings | Applications | Manage Applications.
2. Go to the tab "All" and scroll down and tap on twlauncher (or maybe it is called something else, on mine it is "Start" - check the twlauncher crash message to get it, or follow the instructions below under "Another way..." to find it in the Home button menu. You still need to complete the whole procedure to get it running though).
3. Tap the "Clear data" button. This clears your settings, i.e. the app shortcuts that you put on your start screens.
DONE!
In my case I believe the twlauncher crash was due to adding one more shortcut to an already full app drawer, so when I cleared the settings I can use twlauncher again.
USING TWLAUNCHER TO CONNECT WITH KIES
Now you can use the Home Swithcher app to launch twlauncher if you want to use Kies, and when you are done you can use Home Switcher again to switch back if you prefer the other launcher you installed.
Another way to get back to twlauncher if you don't have Home Switcher, is to go to Settings | Applications | Manage Applications, find your current launcher (e.g. GO launcher or ADW) and tap the "Clear default" button. Then (when you have exited back to the start screen) if you press the Home button, you will be asked which launcher you would like to use to complete the task. Select twlauncher (or "Start" whatever it's called). After you're done with Kies you can switch back the same way if you don't want to use twlauncher as default.
maratonic said:
Ok, after installing another launcher as described above, proceed with the following to prevent twlauncher from crashing in the future. You will need to this do if you want to connect with your computer using Kies, since Kies apparently cannot connect to other launchers (such as GO launcher or ADW).
1. Open Settings | Applications | Manage Applications.
2. Go to the tab "All" and scroll down and tap on twlauncher (or maybe it is called something else, on mine it is "Start" - check the twlauncher crash message to get it, or follow the instructions below under "Another way..." to find it in the Home button menu. You still need to complete the whole procedure to get it running though).
3. Tap the "Clear data" button. This clears your settings, i.e. the app shortcuts that you put on your start screens.
DONE!
In my case I believe the twlauncher crash was due to adding one more shortcut to an already full app drawer, so when I cleared the settings I can use twlauncher again.
USING TWLAUNCHER TO CONNECT WITH KIES
Now you can use the Home Swithcher app to launch twlauncher if you want to use Kies, and when you are done you can use Home Switcher again to switch back if you prefer the other launcher you installed.
Another way to get back to twlauncher if you don't have Home Switcher, is to go to Settings | Applications | Manage Applications, find your current launcher (e.g. GO launcher or ADW) and tap the "Clear default" button. Then (when you have exited back to the start screen) if you press the Home button, you will be asked which launcher you would like to use to complete the task. Select twlauncher (or "Start" whatever it's called). After you're done with Kies you can switch back the same way if you don't want to use twlauncher as default.
Click to expand...
Click to collapse
Such a great thread and no one else has added anything else to it I'm dealing with this crap atm and it is even worst. Holding power doesn't pop up the power menu. Cant access settings. I can bring the notification bar down and turn on wifi but it doesnt actuallly connect to my wifi so I can't do the remote app installation from the web store. I really don't want to do a factory reset.
as was asked here, is there a way to clear the data of the TWLAUNCHER app by using my pc and usb connection to the phone? I'm able to turn on usb storage and access it. Halp!

Strange launcher behaviour on Fiio X7 - Android 5.1.1

Hi Guys,
The Fiio X7 is an android based DAP, it's recently received an update to Lollipop 5.1.1. The device can be rooted using Kingoroot / kingroot.
It has a default launcher called 'Launcher3' which I believe is the AOSP launcher and is also able to be set to what they call 'Pure Music Mode' where the launcher can be set to their Music application (apparently closes all background processes). This can be toggled in the quick settings pulled down from the top.
I am able to install a new launcher - Nova for instance, but cannot set it as default, when the option is selected within Nova, the default launcher immediately pops back up and Nova seems to be shut down (not in the recent apps list). This occurs with any other launcher.
Checking any Launcher within Apps the 'Launch by defaults' section states 'No defaults set' and the 'Clear Defaults' button is greyed out. Default launcher applications don't seem to work either.
So the launcher lives in /system/Launcher3/Launcher3.apk and I've managed to replace this with the Nova launcher apk after renaming it to Launcher3.apk via adb push. This causes the Launcher 3 to throw up errors as expected, but after rebooting the Nova launcher works fine as the default launcher. Even persists after shutting the device down / rebooting it etc.. at this point I thought I had solved the problem...
However leaving the device on for some time, something happens and the Nova launcher process seems to be killed. After this occurs, it goes into the 'Pure Music Mode' launcher, pressing the home button does nothing, and as this isn't an actual launcher means that no applications or anything can be launched. The only way to get things working properly again is to re-flash the firmware (it is a update.img) using Fiio's application leaving me stuck with the default horrid launcher....
It seems that somehow and for some reason Fiio have baked the launcher into the firmware making it impossible to change it's behaviour. I'm hoping someone here can shed some light on how to eradicate this.
Thanks
Paul
Really sorry to bump this, i'm sure someone on here will know the answer to this.
Thanks

How to activate Wifi calling on your Mate 20 Pro if you don't have it yet

I came across this 'fix' and it has worked for me ever since.
Essentially, I never had Wifi calling unless I had no GSM/4G data connection (eg. on the London Underground). In order to activate it whenever I was connected to Wifi, I did the following:
Download Nova Launcher or Action Launcher (other launchers may work for this, but I can't confirm that it works for them)
Using one of those launchers, hard press on a homepage and click on 'Widgets', then select 'Activities' under Action Launcher or Nova Launcher
Under activities, it will give you a long list. Go down to 'Settings'
Then under settings, select 'Wi-Fi calling' (in case there is another, choose the one that is 'calling' with a small c, not capital C)
This creates a 'Wi-Fi calling' setting icon on your homepage. Click on it
You then have the option to enable 'Wi-Fi calling' if it isn't already, then below under 'Mode', choose 'Wi-Fi preferred' if the option currently reads as '4G network preferred'.
Once chosen, you should then see the 'VoWiFi' icon on the top left.
Good luck.
Actually mods, this should probably be in the 'Guides' folder, not this one seeing as it is not a question. Sorry and thanks in advance
clarkgable said:
I came across this 'fix' and it has worked for me ever since.
Essentially, I never had Wifi calling unless I had no GSM/4G data connection (eg. on the London Underground). In order to activate it whenever I was connected to Wifi, I did the following:
Download Nova Launcher or Action Launcher (other launchers may work for this, but I can't confirm that it works for them)
Using one of those launchers, hard press on a homepage and click on 'Widgets', then select 'Activities' under Action Launcher or Nova Launcher
Under activities, it will give you a long list. Go down to 'Settings'
Then under settings, select 'Wi-Fi calling' (in case there is another, choose the one that is 'calling' with a small c, not capital C)
This creates a 'Wi-Fi calling' setting icon on your homepage. Click on it
You then have the option to enable 'Wi-Fi calling' if it isn't already, then below under 'Mode', choose 'Wi-Fi preferred' if the option currently reads as '4G network preferred'.
Once chosen, you should then see the 'VoWiFi' icon on the top left.
Good luck.
Click to expand...
Click to collapse
Does this work even if it isn't supported by your carrier? I doubt that it would

Andoird 9 launcher problem

Hi everyone, I own a TUREWELL T95Z MAX, with Android 9 and would like to change the default launcher.
I downloaded various launchers such as ATV launcher or TVLauncher. They work, only that when I turn the tv box off and on again, the old launcher appears.
If I then navigate and press the HOME button on the remote control, the launcher that I set as the default appears again.
NB: In the settings I set the preferred launcher as "home app".
Is this normal?
Thanks
microinfo said:
Hi everyone, I own a TUREWELL T95Z MAX, with Android 9 and would like to change the default launcher.
I downloaded various launchers such as ATV launcher or TVLauncher. They work, only that when I turn the tv box off and on again, the old launcher appears.
If I then navigate and press the HOME button on the remote control, the launcher that I set as the default appears again.
NB: In the settings I set the preferred launcher as "home app".
Is this normal?
Thanks
Click to expand...
Click to collapse
is there perhaps a kind of setting that starts the luncher at boot ?
microinfo said:
is there perhaps a kind of setting that starts the luncher at boot ?
Click to expand...
Click to collapse
I add that the name of the manufacturer launcher is: "Mediabox launcher".
But what if I eliminate it? what would happen?
Is there a default Andoird 9 launcher?
@microinfo
The launcher that comes pre-installed is a system app means get automatically started after Android has booted. You only can replace it by another launcher of your choice if you freeze and/or delete it what requires device's Android got rooted. WARNING: If you do so then you'll see a black screen and nothing else, you can't open and/or launch any app anymore.
jwoegerbauer said:
@microinfo
The launcher that comes pre-installed is a system app means get automatically started after Android has booted. You only can replace it by another launcher of your choice if you freeze and/or delete it what requires device's Android got rooted. WARNING: If you do so then you'll see a black screen and nothing else, you can't open and/or launch any app anymore.
Click to expand...
Click to collapse
I would just like to replace it with another launcher. And prevent the manufacturer from starting.
ps:the device is already root
I dont think this is normal. New launcher should take over.
p4rp said:
I dont think this is normal. New launcher should take over.
Click to expand...
Click to collapse
instead there is something strange. Some settings that the manufacturer has entered. It is as if it had set the luncher as an app that starts at the starting.
does anyone know how to remove the original launcher from boot andoird?

Categories

Resources