x96mini wont save default lancher - Android Stick & Console AMLogic based Computers

Im trying to change my default launcher ( mbox launcher) choose "always" but after restart it return to the old one.
Any ideas?
Thanks

Try changing it to default under Settings->Apps->Defaults?

Do you have root installed? If so, just rename your launcher to the same name as the default one and then replace it in /system/app. Don't forget to set the permissions correctly to RW, R, R and then reboot.

@AthieN how do you set the permissions correctly to RW, R, R Before reboot? My new X96 air has the same dumb issue and apart from booting to the wrong launcher it's perfect! Even Clicking home takes me to the correct launcher. No clue why it goes to the wrong one at boot. Thanks for any help you can provide.

Related

[Q] Widgets do not load after a restart

I designed my wall with few widgets such as honeycomb clock and memo widget. But it won't load every time i restart my NT. Does anyone know how to fix this problem?
which launcher are you using? i am using adw launcher and dont have that problem. it is the paid version though
Yep, widgets don't work on the Nook Tablet for some people. (Actually, go launcher widgets work for me, but nothing else.) I wonder if this is a go launcher paid vs not paid issue though? Hmm.. I assumed it wasn't since it affected people with ADW launcher as well (unless they also had Go Launcher installed, just not using it).
http://forum.xda-developers.com/showthread.php?t=1357009&highlight=widget
Some people fixed it with a go launcher update or downgrade, some with not using homecatcher, some with adding 160dpi fixes to their build.prop file. The only one I haven't tried for me was the 160dpi edits, and nothing else has fixed widget issues for me.
Actually, a recent post I haven't tried is moving go launcher to the system folder. *tries*
edit: Yep, that fixed it. Or at least my non-go launcher widget is still there after one reboot, whereas previously it wasn't.
Thanks guys!!
ffwalrus's post helped me to solve the problem!
So this seems to have worked for me on my Nook Tablet. Using Go Launcher 2.66 and Home Catcher to re-purpose the "n" button. Go Launcher is set as default upon boot, and upon hitting the "n" button. The 160 dpi fix mentioned above didn't work for me, and I was having this issue on all 2.65 and 2.66 of Go Launcher. This workaround seems to have fixed it for me. I got the initial idea from this post http://forum.xda-developers.com/showthread.php?t=1360036
Using Root Explorer or similar tool move your alternate launcher APK from /data/app to /system/app. Change the permissions to 777 (all 3 rows checked in root explorer). Then restart, and you should be good. I have restarted numerous times now, and had no widget problems.
Step-by-Step Directions:
Open Root Explorer
Browse to /system
Click Mount R/W button
Navigate to /data/app
Long Press launcher APK file (for me it was com.gau/go/launcherex-1.apk)
Choose Move
Navigate to /system/app
Press Paste button
Long Press freshly pasted APK file
Choose Permissions
Check all the top 9 checkboxes (Read, Write, Execute for Owner, Group, Others), leave all others as they are.
Press OK
Navigate to /system
Press Mount R/O button
Restart Nook
Usual at your own risk disclaimer applies.
This method worked for me.
Thanks, worked well, widgets keep working after a reboot.
boradori said:
Thanks guys!!
ffwalrus's post helped me to solve the problem!
So this seems to have worked for me on my Nook Tablet. Using Go Launcher 2.66 and Home Catcher to re-purpose the "n" button. Go Launcher is set as default upon boot, and upon hitting the "n" button. The 160 dpi fix mentioned above didn't work for me, and I was having this issue on all 2.65 and 2.66 of Go Launcher. This workaround seems to have fixed it for me. I got the initial idea from this post http://forum.xda-developers.com/showthread.php?t=1360036
Using Root Explorer or similar tool move your alternate launcher APK from /data/app to /system/app. Change the permissions to 777 (all 3 rows checked in root explorer). Then restart, and you should be good. I have restarted numerous times now, and had no widget problems.
Step-by-Step Directions:
Open Root Explorer
Browse to /system
Click Mount R/W button
Navigate to /data/app
Long Press launcher APK file (for me it was com.gau/go/launcherex-1.apk)
Choose Move
Navigate to /system/app
Press Paste button
Long Press freshly pasted APK file
Choose Permissions
Check all the top 9 checkboxes (Read, Write, Execute for Owner, Group, Others), leave all others as they are.
Press OK
Navigate to /system
Press Mount R/O button
Restart Nook
Usual at your own risk disclaimer applies.
This method worked for me.
Click to expand...
Click to collapse
Help me please. I think i accidentaly pasted into /system instead of /stystem/app and now i do not have goluancher. I am back to Nook UI.
---------- Post added at 12:54 AM ---------- Previous post was at 12:00 AM ----------
Okay i got it...just in case someone else makes a similar mistake and needs this help:
i went to browser and installed amazon app store and then installed root exlplorer (had to pay again 3.99 alas). Then I was able to move it from /system to /system/app.
Now my widgets are there everytime i reboot. Awesome...thanks again.
boradori said:
Thanks guys!!
ffwalrus's post helped me to solve the problem!
So this seems to have worked for me on my Nook Tablet. Using Go Launcher 2.66 and Home Catcher to re-purpose the "n" button. Go Launcher is set as default upon boot, and upon hitting the "n" button. The 160 dpi fix mentioned above didn't work for me, and I was having this issue on all 2.65 and 2.66 of Go Launcher. This workaround seems to have fixed it for me. I got the initial idea from this post http://forum.xda-developers.com/showthread.php?t=1360036
Using Root Explorer or similar tool move your alternate launcher APK from /data/app to /system/app. Change the permissions to 777 (all 3 rows checked in root explorer). Then restart, and you should be good. I have restarted numerous times now, and had no widget problems.
Step-by-Step Directions:
Open Root Explorer
Browse to /system
Click Mount R/W button
Navigate to /data/app
Long Press launcher APK file (for me it was com.gau/go/launcherex-1.apk)
Choose Move
Navigate to /system/app
Press Paste button
Long Press freshly pasted APK file
Choose Permissions
Check all the top 9 checkboxes (Read, Write, Execute for Owner, Group, Others), leave all others as they are.
Press OK
Navigate to /system
Press Mount R/O button
Restart Nook
Usual at your own risk disclaimer applies.
This method worked for me.
Click to expand...
Click to collapse
thx,this worked for me
Voyaging said:
Help me please. I think i accidentaly pasted into /system instead of /stystem/app and now i do not have goluancher. I am back to Nook UI.
---------- Post added at 12:54 AM ---------- Previous post was at 12:00 AM ----------
Okay i got it...just in case someone else makes a similar mistake and needs this help:
i went to browser and installed amazon app store and then installed root exlplorer (had to pay again 3.99 alas). Then I was able to move it from /system to /system/app.
Now my widgets are there everytime i reboot. Awesome...thanks again.
Click to expand...
Click to collapse
I'm not 100% but if you had access to standard launcher you could have used the search function to load up your original file explorer (I always use es file explorer, works a bit better in some cases than root explorer and it's 100% free), then you could have moved your software back to the correct place. I think you can even find market using search if you needed to install.
This works beautifully. Thanks so much!
Widgets are working after reboots again. I even left a couple failed widgets in place and they were restored without having to rebuild all my home screens
I agree that ES explorer is easier to use and being free doesn't hurt either.
If I do this fix will Go Launcher still update properly?
---------- Post added at 03:09 PM ---------- Previous post was at 02:56 PM ----------
I would actually recommend creating a symbolic link to the file instead of moving it. this will ensure that any changes and updates are made to the file in its original location.
I've verified that this works. follow all the steps, except instead of moving the file create a link in system/app that points to the apk in data/app.
How do you create a link with root explorer?
I use esexplorer and when I open the file manager it show me only the sd card file. How can I open the file system?
nooknut said:
How do you create a link with root explorer?
Click to expand...
Click to collapse
you long tap on the file and select "link to this file". A button will appear that says "create link"...or something like that.
Ok. Thanks. Guess that was rather "noob" of me. Should've just tried first. Thanks!
Strange, when I create the link, the system folder will not allow me to revert back to R/O. Stays in R/W mode. Is that do to the link? Is it an issue?
I've tried:
- the 160dpi fix
- getting rid of home catcher
- moving golauncher + all widgets to /system/apps and changing the permissions
Nothing has worked.
Any other workarounds out there? Would be eternally grateful.
widgets disapear
I used the link file method with root explorer, and when I rebooted there were no widgets on my screens. There were also no problem loading widget boxes either. When I tried to replace the widgets I found that the widgets were still there but invisible. When I long pressed on the screen I got the re size/delete box. I was able to delete and replace them.
I just recently pulled the GO Launcher and other apps out of the System\Apps folder, figured there was no real reason to have them their. I also updated GO launcher at the same time. I thought it was the update, that stopped the widgets on reboot, will try moving GO Launcher back to system\apps folder. I also moved all the GO themes and GO locker .APKs, should they get put into the system\apps folder as well. I am also having issues with GO Locker not coming up on reboot. does any body have an answer for GO locker?
ChillFactorz said:
I just recently pulled the GO Launcher and other apps out of the System\Apps folder, figured there was no real reason to have them their. I also updated GO launcher at the same time. I thought it was the update, that stopped the widgets on reboot, will try moving GO Launcher back to system\apps folder. I also moved all the GO themes and GO locker .APKs, should they get put into the system\apps folder as well. I am also having issues with GO Locker not coming up on reboot. does any body have an answer for GO locker?
Click to expand...
Click to collapse
I have my launcher and beautiful widgets in system\apps folder and it fixed my issues. It has nothing to do with the update.
Sent from my Nexus S using Tapatalk
HMG10 said:
I have my launcher and beautiful widgets in system\apps folder and it fixed my issues. It has nothing to do with the update.
Click to expand...
Click to collapse
I appreciate your response about GO Launcher, my question was about GO Locker. The GO Locker app turns off it's lock screen after a reboot, only the system lock screen is their. Again my question is, will moving GO Launcher app to the system\apps folder fix the GO Locker app issue? or should I move all the GO Apps, GO Themes, GO Widgets, GO Keyboard etc. .apks, to the system\apps folder to fix issue? I am a person who likes to know why as well as how. I already know how, and it's an easy fix, I just find it helpful to know as much of the why as possible. This gives me the tools to solve other issues later, and the knowledge to help others to.
I asked this once before, don't remember if I ever got an answer; If you create a symbolic link in the system/apps folder, will it have the same effect as copying the original file?

Clocktopia Font?

I had a question about changing the clock font that displays on the lock screen. I have a recently rooted Sprint S III. Does anyone know what the actual name of the font is? I'm pretty sure I've checked everything in system/fonts, but nothing seems to work. Font changer didn't seem to do anything either. I was going to try to move it manually, but I cannot find a file explorer that can change file permissions. Also, would chmod work for from terminal emulator to change permissions? Thanks in advance.

how can i install the stock samsung sms app ?

hi,
I'm trying to install stock sms app but i can't achieve this. It keeps saying : installation aborded
I am on chameleon rom 1.1 ( hybrid aosp/samsung rom)
Can you help me ?
(sorry if i made mistakes in my post i'm not english XD )
You should copy the apk into /system/app, then change permissions into 644 (rw--r--r), change group and owner to 'root', and finally reboot and try.
gb.yolo said:
You should copy the apk into /system/app, then change permissions into 644 (rw--r--r), change group and owner to 'root', and finally reboot and try.
Click to expand...
Click to collapse
i already tried it and it didn't work. and i am not sur about the about i trid to install because it s difficult to find the stock sms app.
i changed the permissions but i don t understand what you are saying by " 644 (rw--r--r)"
theoricaly it should work since i use an hybrid app ?
With a file manager, backup your mms.apk in /system/app in whatever folder you want. Then, copy the stock mms.apk into /system/app.
You shouldn't click on the .apk and let the app install as you do with other apk files, because this is a system application.
644 means read/write-read-read.
rw-r--r means u set read and write in the owner row , and set read only in the group row , and set read only too in the others row
Note : u get to permissions window in root explorer afer changing r/o read only to r/w read write from the button at the top
then just long click the item u want to change its permissions
i tried what you have said and it didn't work. Is a flashable zip existed ?
up
The stock mms.apk might not be compatible with the custom ROM you have on your phone...
Why do you say it doesn't work? What happens? You open it and it FCs or something else?
I just followed instructions given by posters above and it didn't worked. ( remove the old Mms.apk by the stock one, and fix the permissions, then reboot ) Maybe i don't have the good app, i don't understand why it didn't work; The chameleon rom support stock camera app of samsung and others apps...
piing said:
I just followed instructions given by posters above and it didn't worked. ( remove the old Mms.apk by the stock one, and fix the permissions, then reboot ) Maybe i don't have the good app, i don't understand why it didn't work; The chameleon rom support stock camera app of samsung and others apps...
Click to expand...
Click to collapse
Maybe the pakage cant be praised because of android version differnece , some apks from ics dont work on Jb and vice versa
So if u want a stock sms to work on jb , then download another jb rom that has it and take it from there
For pushing files to system app , it is better to first delete the app u want to replace then do a reboot after that copy the new app to system app and set premissions and set r/w back to r/o

Can't write to /sys/class ??

Galaxy S3 rooted + unlocked
Can someone tell me how to write to "/sys/class" files? I have checked to make sure that the files I want to modify have permissions to 0777.
From terminal I enter..
"echo 1 >/sys/class/lcd/panel/gamma_mode"
I am still unable to change the setting. What gives?? What am I doing wrong?
There must be a way right??
Any help is appreciated!!!!!
You have a quoting problem there try it like this.
su
echo "1" >/sys/class/lcd/panel/gamma_mode
Unfortunately it still doesn't change the setting. If I go straight to the gamma_mode file and change it with root explorer, save and exit it will go right back to it's default setting. It will not hold the new value. It's value is currently 2. I can't change it to anything else. Same thing with any of the files located there such as contrast and brightness. Permissions are set to write but they immediately go back to there default settings if you try to change them.
I seem to have this issue with all files in /sys/class.
razz1 said:
Unfortunately it still doesn't change the setting. If I go straight to the gamma_mode file and change it with root explorer, save and exit it will go right back to it's default setting. It will not hold the new value. It's value is currently 2. I can't change it to anything else. Same thing with any of the files located there such as contrast and brightness. Permissions are set to write but they immediately go back to there default settings if you try to change them.
I seem to have this issue with all files in /sys/class.
Click to expand...
Click to collapse
Hi, I am knowing this thread is very old, but did you find a solution? I am having the same issue on my galaxy s7 rooted (4 years later )

setting permissions for android.permission.CALL_PHONE

hi,
i've been wanting to make the direct call work for launcher 8 launcher, but it says i need to set permissions for android.permission.CALL_PHONE, how do i do this? where can i find android.permission.CALL_PHONE? and how do i set the permissions?
thanks

Categories

Resources