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?
Related
Here is an apk for Google Talk that I have hacked to work on the NC. Rename /system/app/Talk.apk to something else and stash this one in there.
http://www.muffinworld.net/android/nookcolor/Talk.apk
You WILL need a different keyboard other than the stock one! This one is great:
http://forum.xda-developers.com/showpost.php?p=9826968&postcount=11
Known Issues:
App exits immediately if you tap on a contact's avatar. This is because the contact management dependencies are not available on the NC.
Thank you very much. It works well.
I'm curious... what did you modify to get the Talk.apk to work?
Could you post a link on how to replace the keyboard? I think you rename the new one latinime.apk and place it somewhere...
Sent from my LogicPD Zoom2 using Tapatalk
No, you need to go to /system/app/ and rename LatinIME.apk to something else and then install the multitouch keyboard APK I linked to and reboot. That's it.
Mistar Muffin said:
Here is an apk for Google Talk that I have hacked to work on the NC. Rename /system/app/Talk.apk to something else and stash this one in there.
http://www.muffinworld.net/android/nookcolor/Talk.apk
You WILL need a different keyboard other than the stock one! This one is great:
http://forum.xda-developers.com/showpost.php?p=9826968&postcount=11
Known Issues:
App exits immediately if you tap on a contact's avatar. This is because the contact management dependencies are not available on the NC.
Click to expand...
Click to collapse
All hail the Muffin Man!
This got Talk to work...thank you...but the keyboard is being truncated. I am only seeing the top 2 rows...
rxr said:
This got Talk to work...thank you...but the keyboard is being truncated. I am only seeing the top 2 rows...
Click to expand...
Click to collapse
That's why you need to switch keyboards
I am using smart keyboard pro and the talk apk you posted doesnt work. I even tried changing the permissions and nothing happened.
Ellerbestyle said:
I am using smart keyboard pro and the talk apk you posted doesnt work. I even tried changing the permissions and nothing happened.
Click to expand...
Click to collapse
Did you also apply the hack to enable Gmail and Android Market previously posted by Mistar Muffin? I believe those steps are a prerequisite to get GTalk to work.
Hmm...this is where I am...gmail/market all set, original talk application didn't work, so I renamed the talk apk's to end in bak, so they wouldn't be running in the background.
I've renamed the other two back to normal, and have slid the apk from this thread over into system/apps. I can't install it from the unit (not allowed anymore since the gmail/market install)
Talk doesn't appear in my app list. Is it because I haven't installed the apk? Assuming this is the case, if I install it using adb when I get home, that should clear thigns up, correct?
graymulligan said:
I've renamed the other two back to normal, and have slid the apk from this thread over into system/apps. I can't install it from the unit (not allowed anymore since the gmail/market install)
Talk doesn't appear in my app list. Is it because I haven't installed the apk? Assuming this is the case, if I install it using adb when I get home, that should clear thigns up, correct?
Click to expand...
Click to collapse
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
works great. thanks, muffin!
johnopsec said:
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
Click to expand...
Click to collapse
can permissions be changed within root explorer?
on vending.apk, for example, long press to get to the permissions option. Theres a 3x3 grid with 'read' 'write' 'execute' as columns and 'user' 'group' 'others' as rows.
edit: dont mean to get off topic but my market worked when i checked all the boxes in the row 'user' then rebooted. so maybe that works for talk as well.
johnopsec said:
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
Click to expand...
Click to collapse
I renamed them to .apk, from .bak. I had changed them rather than moving or deleting them, and meant that I had renamed them to their original names. Which still makes no sense...lol.
I didn't think to change the permissions...I had it sitting at rwx-r-r, swapping to rwx-rx-rx did the trick. Thanks for putting up with stupid questions, your help is greatly appreciated.
Link issues
The "talk.apk" link doesn't work for me; I've tried copying and pasting the link on both Google Chrome and also on IE9, chrome says the site doesn't exist and IE does nothing (acts as if I just clicked the refresh their default homepage).
Ok (after rooting) here is how I installed GApps (Market, Google Framework, etc) on the Nook Tablet, as well as the steps I took to stabilize everything...
1. Downloaded GApps package from goo-inside.me and extracted files.
2. Deleted the setupwizard.apk file from the set of extracted files (in the system\app folder).
3. Copied "system" folder from extracted files to tablet via USB.
4. Used Root Explorer to remount /system and copy files into their designated locations, and also set permissions (644) on all copied apk's in /system/app folder.
5. Rebooted.
6. Ran the market, signed in with my Google account, and downloaded/installed Superuser. Ran the binary update within the app.
7. Install any additional apps from Android Market.
8. Profit.
Known issues...
1. If setupwizard.apk ends up on your tablet you will not be happy.
2. A factory reset is recommended after installing GApps (though probably not necessary).
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
this is a second good news after rooting!
anlong:
Use either wireless adb found here: https://market.android.com/details?id=siir.es.adbWireless
or use debugging toggle found here: http://code.google.com/p/secure-set.../detail?name=ADBWidget-0.2-alpha.apk&can=2&q=
^ instructions for that:
Download ADBWidget.apk
Copy ADBWidget.apk to /system/app (you can use root explorer or something.)
Add ADBWidget to your home screen
Anlog,
I was able to get SuperUser installed following the directions on the other discussion! Thanks for much for all your hard work.
Working on getting Google Apps installed right now.
Update: Well I have SuperUser on my Nook, but whenever I try to copy anything to \system\app it tells me I don't have permissions. Looks like I can't get root to actually run.
run chmod 4755 /system/bin/su
which version of Gapps do I need Cyanogen 6 MDPI?
Make sure root is fully working before you try to install GApps. Use the latest ones for CM7 (I think its from August). You need to remount /system as RW before copying the files and setting permissions. Root Explorer lets you do all of that.
All of this could be done with an ADB script as well, but I won't have time to write one today. Anyone?
anlog said:
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
Click to expand...
Click to collapse
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Drewmungus said:
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Click to expand...
Click to collapse
Do not install chainfire! I just tried it and it boot-looped, had to force factory restore.
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
bkerk25 said:
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
Click to expand...
Click to collapse
What gapps did you use?
I used the cyanogen 7 universal gapps.
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
theundeadelvis said:
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
Click to expand...
Click to collapse
I ran into issues copying the whole folder over. I am currently running the google market though.
do everything one step at a time, install the googleframework first (from the directions on the kindle page), then do the market. I ran into the first time through the market would not actually connect so I rebooted the NT.
*note*
each time you reboot your NT you need to go in and what appears is toggle the usb debugging off then on, same with the "auto mount", and I did the unknown sources as well (not sure if this is necessary). It appears a reboot resets the flags and our menu isn't actually writing the settings so you have to toggle it.
Push comes to shove, start over with fresh reboot. It took me a few times (as it probably did others as well).
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
JoeM01 said:
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
Click to expand...
Click to collapse
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
suicideclown said:
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
Click to expand...
Click to collapse
It needs go in system/apps
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
i'm copying from the system/apps directory (unzipped gapps files), to where on the nook?
I tried copying the files into several locations, but nada.
this is literally the last thing need to knock out for me to be set until the days of ported roms.
please. halp (lelu dallas, multipass).
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
that part is clearly stated but using root explorer and getting it to mount doesnt seem to work properly on my device. I have root and superuser. titanium backup works fine. for some reason root explorer on es explorer says it fails every time
-1 Go download latest Gapps and extract the contents to your HD. There will be two folders, one of which is "system."
-2 In the system folder there will be more folders, one of which is "app." Inside of app are all the system APKs.
-3 Detele SetupWizard.apk
-4 Now copy the app folder to the root of your NT SD card via USB.
-5 Next step you need to use ADB or Root Explorer...I used Root Explorer.
-6 Open root explorer, then go to sdcard and you should see the APP folder you copied.
-7 Once there, hit menu -> multi select > then put a check mark to what you want copied then hit the copy button.
-6 now hit back untill you're back in the root
-8 Then navigate to system, and at the top you should see button "Mount RW" hit that button.
-9 Then go into the App folder, and hit paste.
-10 All the selected APKs are now in the system/app folder.
-11 Now you need to give each of the copied apps permission by long-clicking on it till a menu comes up, hit permissions, then check all the check boxes next to "Owner"
-12 After you did that to all the apps hit the "mount RO" button on top of the screen
-13 Reboot the NT.
That should do it...hopefully I havent missed anything.
!!!!!!!!!THIS THREAD IS STRICTLY FOR MODS, AND MODS ONLY, THERE WILL BE NO ARGUING ON THIS THREAD!!!!!!!!!
Users, i am not dev, but i want to help.....do here is this thread.
On this thread feel free to post how-to's, non play store apps etc. So long as its mad based/related. Questions are allowed!
So lets get to it!
Sent from my MB855 using Tapatalk 2
Mod what?
Android>iOS... Android FTW!
so to load a new launcher for root users:
1. Root Your Device!
2. Using a root explorer like es file explorer or root explorer mount system R/W
3. Grab the all for whatever you want from wherever you have it, and just copy it into you /system/app/ folder
4. Re-name the "Launcher.apk" application in the /system/app/ to "Launcher1.apk"
5. Voila you can now use any launcher in the system app folder-->note you may need to reboot
Sent from my KFTT using XDA Premium HD app
craby1925 said:
so to load a new launcher for root users:
1. Root Your Device!
2. Using a root explorer like es file explorer or root explorer mount system R/W
3. Grab the all for whatever you want from wherever you have it, and just copy it into you /system/app/ folder
4. Re-name the "Launcher.apk" application in the /system/app/ to "Launcher1.apk"
5. Voila you can now use any launcher in the system app folder-->note you may need to reboot
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
There is no need to rename the launcher.apk. After another launcher is installed you will be given the choice of which launcher you want to set as default, you can change back to stock launcher by clearing the defaults of the custom launcher. Better to not change system files if you dont have to. After you move the new launcher to system/app folder change the permissions to rw-r--r--.
onemeila said:
There is no need to rename the launcher.apk. After another launcher is installed you will be given the choice of which launcher you want to set as default, you can change back to stock launcher by clearing the defaults of the custom launcher. Better to not change system files if you dont have to. After you move the new launcher to system/app folder change the permissions to rw-r--r--.
Click to expand...
Click to collapse
Would you need to rename the new launcher to anything special, or is setting these permissions and/or placing into this directory enough?
4Bn0rmL said:
Would you need to rename the new launcher to anything special, or is setting these permissions and/or placing into this directory enough?
Click to expand...
Click to collapse
Nope, I just got a special/stupid kfhd, that wouldn't work unless launcher was renamed.
Sent from my Fire HD with root!
Alright,
1st, device spoofer will cause BOOTLOOPS!!!! so don't buy!
(I learned this the hard way)
so this isn't really a mod but if you boot-looped your device by messing with build.prop than here is a quick fix:
1.Make sure you have adb set up nice for your fire by following the amazon developers @ https://developer.amazon.com/sdk/fire/getting-started.html AND that you have the orignal build.prop file
Make sure you read the entire page verbatim, especially if your a mac user, because all the answers are either on the page or in the links
2.You either will need to have temp root or have already been rooted.
3. Make sure the device is actually reaching adb, check this by waiting until the sparkly kindle fire logo comes up, and then doing adb devices
4. Down to Business: Turn on the fire and wait until you reach sparkly kindle fire logo.
5.Navigate to platform-tools folder and place your original build.prop file there
6.type
Code:
adb shell
su
mount -o remount,rw /system
mv build.prop /system/build.prop
exit
exit
reboot
7. If you already kept a backup of the original build.prop file on the device, than change the mv line to
Code:
mv /system/build.prop.bak /system/build.prop
-->and there ya go, post if you have problems
craby1925 said:
so to load a new launcher for root users:
1. Root Your Device!
2. Using a root explorer like es file explorer or root explorer mount system R/W
3. Grab the all for whatever you want from wherever you have it, and just copy it into you /system/app/ folder
4. Re-name the "Launcher.apk" application in the /system/app/ to "Launcher1.apk"
5. Voila you can now use any launcher in the system app folder-->note you may need to reboot
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
Will this replace this awful carousel thing ? And therefore, redirect the home button ?
Sorry, i'm not a native english speaker, i don't understand the "Grab the all for whatever you want from wherever you have it".
Does it mean that i copy the new launcher's apk file to /system/app/ ? And do i have to install the new launcher ?
Thanks
iCoN3o said:
Hi,
Will this replace this awful carousel thing ? And therefore, redirect the home button ?
Sorry, i'm not a native english speaker, i don't understand the "Grab the all for whatever you want from wherever you have it".
Does it mean that i copy the new launcher's apk file to /system/app/ ? And do i have to install the new launcher ?
Thanks
Click to expand...
Click to collapse
Download a launcher from the play store
With a file manager move the apk from /data/app/ folder (It will be named differently than you are used to, usually has the company or developers name instead) to /system/app/ folder then reboot.
No need to change permissions as they are the same coming from /data/app/ folder
onemeila said:
Download a launcher from the play store
With a file manager move the apk from /data/app/ folder (It will be named differently than you are used to, usually has the company or developers name instead) to /system/app/ folder then reboot.
No need to change permissions as they are the same coming from /data/app/ folder
Click to expand...
Click to collapse
Thanks ! It worked perfectly. Goodbye carousel !!!
Sent from my KFTT using xda app-developers app
Are there any alternates to the soft button bar like a stock jb one or something? Or can we not do that because of the odex? I know it's systemui.apk I tried installing a cm9 systemui.apk on my kf2 and system/app rwrr but on reboot all I got was black screen. I backed it up and restored it with adb so I know what i'm doing... for the most part. Sorry for an y random spaces or periods... swype doesn't like furious tapping on the kf2. Needless to say, I have swype as default keyboard and launcher pro as launcher.
Well, I tried the same wpthing with a similar result. My best guess is that it works off of framework res so...until there are custom ROMs we have to wait. But, I've been toying with an idea: if the favorite button on the saftbar was rewritten to display recent apps, e.g. that it always displays 8 apps from data list x, and data list x is a list constantly updated saying the most recent app. Then the app could be themed minorly to have the window over window PNG and voila: a little bit better stock ROM. My problem is that I'm not a coder of any kind, so its a slow process.
Sent from my Fire HD with root!
fmkilo said:
Are there any alternates to the soft button bar like a stock jb one or something? Or can we not do that because of the odex? I know it's systemui.apk I tried installing a cm9 systemui.apk on my kf2 and system/app rwrr but on reboot all I got was black screen. I backed it up and restored it with adb so I know what i'm doing... for the most part. Sorry for an y random spaces or periods... swype doesn't like furious tapping on the kf2. Needless to say, I have swype as default keyboard and launcher pro as launcher.
Click to expand...
Click to collapse
I could try to edit it for you. I don't have a Kindle Fire HD, so you'll have to upload me the framework-res.apk and test it for me. Make sure you backup before you test it though.
Sent from my Kindle Fire
Has anyone figured out or tried to replace or disable stock search and get Google search to work. I've tried a few things with no luck. I would also like Google now.
For Google search, it's really tedious.
For it to work you have to rename the stock search to iforgothenameofit.apk.bak
Than you have to grab the Google search app from jelly bean gapps via goo.I'm, and push it to the system/app folder with permissions rw-r--r--
Than you have to push all the framework files, permission files, basically any other non-apk file to the folder of which it belongs.(you can get this from the whole zip file that you got from goo.I'm
MAKE SURE THAT EVERY FILE YOU PUT IN THE SYSTEM DIRECTORY HAD PERMISSION RW-R--R--
*This can actually be done with a root explorer fairly easily
Sent from my Fire HD with root!
I used root explorer to move some system apk & its corresponding odex file from /system/apk to sdcard. I rebooted and found that I have moved some essential app like the stock dialer (it wasn't possible to figure out from the apk name). So now the dialer was gone. I then moved them back from sdcard to /system/app using root explorer thinking that it would undo the mess.
However the apps didn't come back, for example the dialer. The phone still tells me that there is no dialer.
What do I need to do?
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Gregrin said:
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Click to expand...
Click to collapse
I didn't move anything from any other directory. I moved back each and every file to /system/app that I had moved from it earlier. Still no luck.
I didn't delete anything in this process. I don't see dialer in app drawer either.
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Markuzy said:
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes, umpteen number of times.
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
RavinduSha said:
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
Click to expand...
Click to collapse
Yes, you are so right.
The apk permissions have screwed up after all the moving. I issued ls -l command in adb shell and this is what I found out.
-rw-r--r-- 1 root root 3973 May 7 2012 HTMLViewer.apk
-rw-r--r-- 1 root root 8784 May 7 2012 HTMLViewer.odex
----rwxr-x 1 system sdcard_r 562553 Feb 9 04:31 LatinIME.apk
----rwxr-x 1 system sdcard_r 327896 Feb 9 04:31 LatinIME.odex
-rw-r--r-- 1 root root 14569 May 7 2012 LiveWallpapersPicker_gles20.apk
-rw-r--r-- 1 root root 21392 May 7 2012 LiveWallpapersPicker_gles20.odex
LatinIME.apk is the keyboard with screwed up permission.
Now how do I fix it? What command do I issue?
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
You can also change permissions in Root Explorer itself. Hold down on the files, choose permissions and tick the first column and the first box of the second one. Leave the rest blank and press ok. That's it. If it still doesn't show, reboot. Fixing permissions in recovery does exactly this, but for all files in /system/app, /data/app and /data/data. Every time you copy something to /system or /data, you have to set the right permissions. Either in a root explorer app, adb shell, terminal emulator or fixing permissions in recovery.
LatinIME is the stock Android keyboard btw.
Sent from my Desire HD using xda premium
calisro said:
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
Click to expand...
Click to collapse
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
sashank said:
LatinIME is the stock Android keyboard btw.
Click to expand...
Click to collapse
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
sashank said:
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can see two apks in my phone with dialer icon.
Phone.apk (& Phone.odex)
TelephonyProvider.apk (& TelephonyProvider.odex)
How do I get back the dialer? This is a dual sim phone and only the stock dialer gives the option to select sim before dialing. None of the market dialers provide this option.
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
RavinduSha said:
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
Click to expand...
Click to collapse
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
ontherocks62 said:
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
Click to expand...
Click to collapse
advanced section. look through. it should be self explanatory.
ontherocks62 said:
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Click to expand...
Click to collapse
the dialer is Phone.apk
calisro said:
advanced section. look through. it should be self explanatory.
Click to expand...
Click to collapse
Fixed permission. Still dialer doesn't appear. :crying:
ontherocks62 said:
Fixed permission. Still dialer doesn't appear. :crying:
Click to expand...
Click to collapse
reflash the rom. easy peasy. next time careful what you delete! sry guy.
if u have a backup just restore only system partition
RavinduSha said:
if u have a backup just restore only system partition
Click to expand...
Click to collapse
I have a backup. Unfotunately, I took a backup after messing up. So after re-flashing it with the backup, it boots in the messed up state.
I downloaded one gingerbread Phone.apk yesterday. I renamed the Phone.apk and Phone.odex in my phone to Phone.apk.bak & Phone.odex.bak. Then copied the downloaded Phone.apk to /system/app. Then fixed permissions via recovery and rebooted.
To my horror, not only did the dialer didn't appear, but also the phone wouldn't detect the sim cards. It would say no connection available...
So Phone.apk is affecting other stuff too. So I deleted the new Phone.apk and renamed the .bak to its original names, fixed permissions via recovery and rebooted. The phone still wouldn't detect the sim cards.
Then I went back to recovery, cleared Dalvik cache & user data, and performed clear data & factory reset. After reboot, the phone started detecting the sim cards again.
So this leads me to believe that something else other than permissions has a role to play.
PLEASE READ
This mod ONLY applies to UNLIMITED USERS who DO NOT have tethering on their plan
This mod DOES NOT apply to SHARE EVERYTHING plans
I took a peak over at this thread http://forum.xda-developers.com/verizon-lg-g3/help/g3-hotspot-hack-t2812305 and saw that there were issues with using the G2 apk. I decided to take a looksy at it and see if I can replicate the functionality of the G2 apk with out having to re-apply settings to turn on tethering.
I have always had issues using root explores and database explorers messing up permissions and causing boot loops so until I have a proper recovery I use the android terminal emulator. Many people here have had plenty of success using file explores so give it a shot if you like!
Skip down to the bottom for a video walkthrough created by { owenbeals aka DroidModderX}
First things first you will need root!
0.) Start a root shell
Code:
su
1.) mount the system partition for read and write access
Code:
mount -o remount,rw /system
2.) Rename stock files HotspotProvision.apk and HotspotProvision.odex to something memorable. I use .bak and .bakdex
Code:
cd /system/app
mv HotspotProvision.apk HotspotProvision.bak
mv HotspotProvision.odex HotspotProvision.bakdex
3.) Now copy over the new file, can be the root of the extSD card which is /storage/external_SD/HotspotProvisionVzG3.apk
Code:
cp /storage/external_SD/HotspotProvisionVzG3.apk .
4.) The last thing is to change permissions to 644 (RW- R-- R-- for you file browsy types )
Code:
chmod 644 HotspotProvisionVzG3Mod.apk
5.) Now reboot and enjoy your glitch free hotspot action!
You must reboot! Do not try to "install" it, it does not function like that.
N.B.
Some users have noted that their cpu governors change to Performance while the hotspot is on and change back to On Demand when off instead of normal Interactive. This is the stock behaviour of the kernel, and not a bug introduced by this mod.
Thanks to { owenbeals aka DroidModderX} for this handy video walkthrough.
Thanks { Robshr, JayGoat } for bringing this up
Also thanks to { nrage23 } for answering a ton of questions on here
CREDIT:
Guest who started previous thread
Anonymous original creator
WACOmalt for making the original G2 thread
what was glitchy about the first hotspot app? HotspotProvision_24A_mod.apk
rp201 said:
what was glitchy about the first hotspot app? HotspotProvision_24A_mod.apk
Click to expand...
Click to collapse
You have change something every time you use it.
The modded apk works perfectly. I used root explorer to do it though. I renamed the original files, copied your apk to system/app, renamed it to HotSpotProvision.apk, fixed the permissions and rebooted.
Sent from my VS985 4G using XDA Premium HD app
Pretty cool. I'll have to give this a try when I'm bored later on today at work. Could you explain what you actually did to the hotspot apk though?
One thing though - why not just append ".bak" to the end of the existing filename/extension? That way, you don't lose the original extension so you can't forget what it was. It works fine. That's what I always do. In other words, your files would end in ".apk.bak" and ".odex.bak". The system only sees the extension after the final period.
nrage23 said:
You have change something every time you use it.
The modded apk works perfectly. I used root explorer to do it though. I renamed the original files, copied your apk to system/app, renamed it to HotSpotProvision.apk, fixed the permissions and rebooted.
Sent from my VS985 4G using XDA Premium HD app
Click to expand...
Click to collapse
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
The downloaded apk he modded is named differently from the original one in the system/app folder. After I changed the names for the original files in system/app. I changed the name of the modded apk to match the original apk in system/app. I copied the renamed modded apk to system/app, set the permissions correctly, then rebooted. I went into Settings then More... under wireless networks,Mobile HotSpot and changed the SSID and password. I can turn it on via settings or the quick setting in the notification bar.
sstapley_56 said:
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
Click to expand...
Click to collapse
I'd guess for it to work from stock menus (i.e. without starting the apk directly from a file browser app or terminal emulator) you'd have to rename it the same as the stock apk so that the path is the same for the various apps that would call it.
nrage23 said:
The downloaded apk he modded is named differently from the original one in the system/app folder. After I changed the names for the original files in system/app. I changed the name of the modded apk to match the original apk in system/app. I copied the renamed modded apk to system/app, set the permissions correctly, then rebooted. I went into Settings then More... under wireless networks,Mobile HotSpot and changed the SSID and password. I can turn it on via settings or the quick setting in the notification bar.
Click to expand...
Click to collapse
So I have renamed it exactly as the original apk was and rebooted but still no go. On reboot I get a force close of VZWAWSService. I have some of the system bloat frozen, maybe this has something to do with it.
phobos512 said:
I'd guess for it to work from stock menus (i.e. without starting the apk directly from a file browser app or terminal emulator) you'd have to rename it the same as the stock apk so that the path is the same for the various apps that would call it.
Click to expand...
Click to collapse
---------- Post added at 09:36 AM ---------- Previous post was at 09:33 AM ----------
Sweet it's working now, I had the lgmobilehotspot GUI.apk frozen and that's what was causing the issue. Thanks for the apk and tutorial guys!
sstapley_56 said:
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
Click to expand...
Click to collapse
Did you reboot?
There should be no reason to rename the apk. When android installs applications it goes into the /data... Dir as the package name. All intents are handled via package names therefore the apk name is inconsequential.
To use you should be able to go settings > more and see all the tethering options.
To verify placement and permissions use
Code:
su
ll /system/app/Hotspot*
You should see your two backup files and the new HotspotProvisionVzG3Mod.all
Permissions should be rw-r--r--
Let me know if you still have issues.
I will post a DIY response so that people who want to learn about the modification can play along at home. Think of it as source code for this mod:good:
[email protected] said:
Did you reboot?
There should be no reason to rename the apk. When android installs applications it goes into the /data... Dir as the package name. All intents are handled via package names therefore the apk name is inconsequential.
To use you should be able to go settings > more and see all the tethering options.
To verify placement and permissions use
Code:
su
ll /system/app/Hotspot*
You should see your two backup files and the new HotspotProvisionVzG3Mod.all
Permissions should be rw-r--r--
Let me know if you still have issues.
I will post a DIY response so that people who want to learn about the modification can play along at home. Think of it as source code for this mod:good:
Click to expand...
Click to collapse
Thanks for the detailed response, I got it working now. I had previously frozen some of the bloat on the phone when I got it and one of the apps I froze was the lgemobilehotspotui.apk which is needed to work correctly. Thanks for all the help from the awesome devs here.
Nice work, thanks. I just installed it with Root Explorer, and it worked perfectly. Just have to do it to the wife's phone, now.
Well done. Working great!
Thanks! Works perfect. And now I can use the toggle on the drop down menu to activate the hotspot. Thanks so much.
Worked
Worked perfectly for me. Used ES file explorer to move the files around.
I have downloaded, changed permissions, changed the file names to .bak but when I try to install the nodded split says application not installed. I'm using root explorer. I did have the othe mod installed and deleted it first. Wondering if that is the problem
Edit...Stopped trying to install and just rebooted and it turns on just fine, and my laptop connects...the app shows it connected and listed as an approved device...yet I'm not able to actually get a a connection.
Sent from my VS985 4G using XDA Free mobile app
Thanks! Works like a champ.
works great!
I'm also getting the VZWARSService has stopped message, and when I go into settings and turn on the hotspot, nothing happens. If I go into mobile hotspot and turn it on from there, I get this message: Unfortunately, com.lge.mobilehotspot.ui has stopped. Followed the directions exactly, so I'm not sure what's going on.
Works perfectly. I used Root Explorer to rename and move everything. Thanks!
Worked like a charm the only thing is still changes the cpu governor to performance the g2 one did it to I don't know if someone is able to fix that
It's just when I turn on the hotspot afterwards I use android tuner and change it back to interactive
Does anyone else have this issue