[Q] Swype problem on 3.2 - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Since updating to 3.2 I have a problem with Swype on the browser. When I type something it auto highlights the last 2 letters of whatever word it is so that when I swype the next word it goes over what was highlighted. It is incredibly annoying.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

StormtrooprDave said:
Since updating to 3.2 I have a problem with Swype on the browser. When I type something it auto highlights the last 2 letters of whatever word it is so that when I swype the next word it goes over what was highlighted. It is incredibly annoying.
Click to expand...
Click to collapse
This seems to be a bug introduced with the newest 3.2 Samsung released. Since I love Swype so much, I rooted my GT just so I could remove the old version of Swype and install the Beta, which I am happy to report does not have this deletion issue!
The quick how-to for removing the pre-installed Swype is as follows:
If you don't already have it, install ES File Explorer
To set up ES File Explorer:
Menu > Settings > Home Directory: change from /sdcard/ to /
Scroll down, check the boxes for Root Explorer and Mount File System
Hit Back
Press the 'Up' icon to get to the root folder
Tap 'System' then 'lib', and find libSwypeCore.so. Long press it, select 'Rename' and change the name to libSwypeCore.so.bak
Tap 'Up' again, and next go to the 'app' folder, find Swype.apk and change it's name to Swype.apk.bak
Exit ES File Explorer and proceed to install the Swype Beta.
Changing the names of the old Swype files to have .bak at the end allows you to easily remove the updated Swype Beta install and restore the old Swype should you ever need to (simply remove the .bak from the file names - it may require a restart to get it working again after restoring these files).
Click to expand...
Click to collapse
Edit: the one oddity I did notice is that in the Google Search bar at the top of the screen, the Dragon Dictation won't start, though the Google Voice Search will, but the Dragon Dictation seems to work everywhere else.

Thanks man, that worked great

Related

[Q] Swype / SlideIt / Shapewriter

I don't get it. I'm on caulkin and clems 2.2 rom and when I try to change the keyboard it warns me of possible data collection and asks if I want to proceed....but the box wont stay checked. Both slideit and swype do this. I haven't found shapewriter yet. Someone tell what I am doing wrong plz!!!! I can't stand this keyboard.
The rom you are using does not support changes in keyboard. Do this:
1) Open root explorer
2) Navigate to sdcard/data/apps
3) Long press>edit>copy the apk of the keyboard you want to use
4) Navigate in root explorer to system/data/apps
5) Mount r/w
6) Paste
7) Mount r/o
8) <<Do the same for all your other input methods you want to install>>
9) Reboot and it now works.
amusedkid said:
The rom you are using does not support changes in keyboard. Do this:
1) Open root explorer
2) Navigate to sdcard/data/apps
3) Long press>edit>copy the apk of the keyboard you want to use
4) Navigate in root explorer to system/data/apps
5) Mount r/w
6) Paste
7) Mount r/o
8) <<Do the same for all your other input methods you want to install>>
9) Reboot and it now works.
Click to expand...
Click to collapse
First, I just wanted to thank you since no one else replied! I tried to upgrade to the latest Calkulin and Clem combo but the tablet doesn't like the newer kernel so I put Pershoot's latest kernel on instead.
Robeet is apparently pulling all his ROMs and developing one called Mountain Laurel. Honestly, I don't know what a good ROM is. I want GPU acceleration so I guess that means I have to use a 2.2 ROM because Ginger doesn't accelerate. And I want NTFS access.
ANYWAAAAYyyyy..... I tried to find the apk in the sdcard/data/apps and it didn't seem to be there. I tried to move the original installer apk file (sitting in my download folder) to the folder you suggested but I'm guessing that it's not THAT apk you are telling me to move. But may be I'm wrong.
Any idea what I'm doing wrong? Besides this and not getting any EA games to work (??...they won't download additional data) I actually like the ROM I'm on.
So unless you think I should change ROMs or know what I'm doing wrong I guess I'm screwed right now.
Hey,
No problem I was equally new 2 months back and had great help from the community. Next time when you can solve probs for others do it too
I personally love Roebeet's roms so i think TNT Lite is awesome.
If the apk is not there, it is probably in data/apk_private. Btw, if you are using swype, the beta version doesnt seem to work -> i tried a month back. Not sure about slideit. I used shapewriter before on the g tab and found it incredibly ugly haha.
For swype you need a modded version:
Instructions:
1) Google this: swype v2.6.48.12226 wsvga
2) Click on first result
3) Go to post 53 and read it.
Disclaimer: i found this over the net as well.

Fix Market problem: AmeriCanAndroid AOSP HD2 GB2.3.7 CM7.1

Hi,
The thread for AmeriCanAndroid AOSP HD2 GB2.3.7 CM7.1 is now 17K+ replies & I was lost in there trying to find a solution for the Market problem "This app is incompatible with your phone" even for some apps already installed like facebook!
What I did after getting help from lots of replies in the thread is:
1- Install ES file Explorer.
2- in ES FE: settings->Root Explorer (checked)
3- in ES FE: settings->Mount File System (checked)
4- Brows to /sdcard/Android/
5- Click to edit "startup.txt" & chose an editor (I've ES Note Editor)
6- Edit the lcd_density=167 to lcd_density=240
7- Exit editor saving the file.
8- Brows to /system/
9- Click to edit "build.prop" & chose an editor (I've ES Note Editor)
10- Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=240
11- Exit editor saving the file.
12- in ES FE: settings->Mount File System (UN-CHECK)
13- Exit ES FE.
14- Open Android App Manager
15- Select Market App
16- Select "Details/Clear cache/Force stop"
17- Click "Force stop" & "OK"
18- Click "Clear data" & "OK"
19- Exit App Manager
20- Re-boot
My problem was fixed & I installed all the apps without any problems.
Thanks to Warren and Cope
All I did was to force close Market and clear data, no reboot required.
THX I Love It
I am faced with the same issue so was very excited to find your post; however I cannot even go past step 1 since ES file explorer turns out to be one of those apps that the market says are not compatible with my device.
Do you have a workarround for that?
Thanks a lot!
Dude, seriously?
You're opening a new thread in the wrong section for this?
Your way costs lots of time and changes the resolution.
Just change in startup.txt the lcd_density=167 to lcd_density=160.
This won't change your resolution, compared with your way.
Start Android, open the Rom Manager app.
Touch "Fix Permissions".
When it's done reboot and you're ready to go.
Resoution Changed
wh_hsn said:
Hi,
The thread for AmeriCanAndroid AOSP HD2 GB2.3.7 CM7.1 is now 17K+ replies & I was lost in there trying to find a solution for the Market problem "This app is incompatible with your phone" even for some apps already installed like facebook!
What I did after getting help from lots of replies in the thread is:
1- Install ES file Explorer.
2- in ES FE: settings->Root Explorer (checked)
3- in ES FE: settings->Mount File System (checked)
4- Brows to /sdcard/Android/
5- Click to edit "startup.txt" & chose an editor (I've ES Note Editor)
6- Edit the lcd_density=167 to lcd_density=240
7- Exit editor saving the file.
8- Brows to /system/
9- Click to edit "build.prop" & chose an editor (I've ES Note Editor)
10- Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=240
11- Exit editor saving the file.
12- in ES FE: settings->Mount File System (UN-CHECK)
13- Exit ES FE.
14- Open Android App Manager
15- Select Market App
16- Select "Details/Clear cache/Force stop"
17- Click "Force stop" & "OK"
18- Click "Clear data" & "OK"
19- Exit App Manager
20- Re-boot
My problem was fixed & I installed all the apps without any problems.
Thanks to Warren and Cope
Click to expand...
Click to collapse
Hi man,
i tried your solution, before i even go to market to test.. it changed my screen resolution and everything became bigger and my Launcher icons become very big so i revert back.
Is this also happening with you or only me?
Thanks
zakolb said:
Hi man,
i tried your solution, before i even go to market to test.. it changed my screen resolution and everything became bigger and my Launcher icons become very big so i revert back.
Is this also happening with you or only me?
Thanks
Click to expand...
Click to collapse
READ!
seriously dude. How did you ever passed the registration form.
TT5555 said:
You're opening a new thread in the wrong section for this?
Your way costs lots of time and changes the resolution.
Just change in startup.txt the lcd_density=167 to lcd_density=160.
This won't change your resolution, compared with your way.
Start Android, open the Rom Manager app.
Touch "Fix Permissions".
When it's done reboot and you're ready to go.
[\QUOTE]
Click to expand...
Click to collapse
TT5555 said:
You're opening a new thread in the wrong section for this?
Your way costs lots of time and changes the resolution.
Just change in startup.txt the lcd_density=167 to lcd_density=160.
This won't change your resolution, compared with your way.
Start Android, open the Rom Manager app.
Touch "Fix Permissions".
When it's done reboot and you're ready to go.
Click to expand...
Click to collapse
I'm glad that your way is shorter - I wish you posted before - I just wanted to share what fixed my problem after going through 1000's of posts in the thread!
I think adding more posts to the original ROM thread is really complicating things ... anyway, the moderators can just move this post to any where appropriate.
Thanks,
zakolb said:
Hi man,
i tried your solution, before i even go to market to test.. it changed my screen resolution and everything became bigger and my Launcher icons become very big so i revert back.
Is this also happening with you or only me?
Thanks
Click to expand...
Click to collapse
Yes, this is what it is all about - but you may try TT5555 method - it didn't work on my device but it seems that every device has its own personality
wh_hsn said:
I'm glad that your way is shorter - I wish you posted before - I just wanted to share what fixed my problem after going through 1000's of posts in the thread!
I think adding more posts to the original ROM thread is really complicating things ... anyway, the moderators can just move this post to any where appropriate.
Thanks,
Click to expand...
Click to collapse
You took my overreacting post very good, sport.
Well, thanks for trying to help people I think this question has been asked over and over again in the ROM thread, so actually you've got a point there.
Thank you so much for posting this. I've tried both methods and they both work. For me, TT555's method is my favorite. What I love about the AmeriCanAndroid build was the resolution.
Actully the original post has the solution long time ago!!
Do you why that happens "check the original post"!!
Mr. AmeriCanAndroid also recommended to set it 1x0, 240 just back to the way it was!!
@kontradictions:
I use this to control the resolution after applying the fix:
https://market.android.com/details?id=com.wemobs.android.lcdresolution
@hkmate:
I said that I got the solution from the original thread but try to look for it in +17000 posts & tell me how to find it
that fixed that problem, does anyone know how to fix why it doesnt let me send pics thru picture messaging
TT5555 said:
You're opening a new thread in the wrong section for this?
Your way costs lots of time and changes the resolution.
Just change in startup.txt the lcd_density=167 to lcd_density=160.
This won't change your resolution, compared with your way.
Start Android, open the Rom Manager app.
Touch "Fix Permissions".
When it's done reboot and you're ready to go.
Click to expand...
Click to collapse
This was the best and most correct hint here! I tryed at first the first one up there and my resolution was not good. After that I read that one and it´s perfect for me!!! Thank you very much
TT5555 said:
You took my overreacting post very good, sport.
Well, thanks for trying to help people I think this question has been asked over and over again in the ROM thread, so actually you've got a point there.
Click to expand...
Click to collapse
Hi,
I have applied your fix for LCD Density and Market device compatibility. It is awesome and I thank you. I have struggled with this for last few months!
Now I have changed my HD2 to 800x480 to 160dpi resolution and run Fix Permissions. Then rebooted the phone, cleaned Market cache and settings, run it again, and every application that I could not update before now is compatible with device
I have a problem though. There are artifacts on some gadgets, there is artifact on left side of the status buttons (once I expand status bar). There are artifacts on my on-screen keyboard (button images are different, strange empty gaps, transparencies).
Are there any fixes for these problems?
wh_hsn said:
Hi,
The thread for AmeriCanAndroid AOSP HD2 GB2.3.7 CM7.1 is now 17K+ replies & I was lost in there trying to find a solution for the Market problem "This app is incompatible with your phone" even for some apps already installed like facebook!
What I did after getting help from lots of replies in the thread is:
1- Install ES file Explorer.
2- in ES FE: settings->Root Explorer (checked)
3- in ES FE: settings->Mount File System (checked)
4- Brows to /sdcard/Android/
5- Click to edit "startup.txt" & chose an editor (I've ES Note Editor)
6- Edit the lcd_density=167 to lcd_density=240
7- Exit editor saving the file.
8- Brows to /system/
9- Click to edit "build.prop" & chose an editor (I've ES Note Editor)
10- Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=240
11- Exit editor saving the file.
12- in ES FE: settings->Mount File System (UN-CHECK)
13- Exit ES FE.
14- Open Android App Manager
15- Select Market App
16- Select "Details/Clear cache/Force stop"
17- Click "Force stop" & "OK"
18- Click "Clear data" & "OK"
19- Exit App Manager
20- Re-boot
My problem was fixed & I installed all the apps without any problems.
Thanks to Warren and Cope
Click to expand...
Click to collapse
I did not edit the build.pro and it still works. In my case, ro.sf.lcd_density= in build.pro will be changed automatically according to the lcd_density in startup.txt
TT5555 said:
You're opening a new thread in the wrong section for this?
Your way costs lots of time and changes the resolution.
Just change in startup.txt the lcd_density=167 to lcd_density=160.
This won't change your resolution, compared with your way.
Start Android, open the Rom Manager app.
Touch "Fix Permissions".
When it's done reboot and you're ready to go.
Click to expand...
Click to collapse
why is this not working for me? i was on android changing the txt - fixing permissions - even clearing market cache - rebooting - and im not rdy to go.... does it make a difference if i change txt on win and then start android?
sry im very new to roms etc
or is it possible that those apps i want to use just even dont work with this fix? cause my market works just some specific apps do not like aldi talk app or skype app? can u pls help me out on this? are their roms who support all apps?
stevennus said:
why is this not working for me? i was on android changing the txt - fixing permissions - even clearing market cache - rebooting - and im not rdy to go.... does it make a difference if i change txt on win and then start android?
sry im very new to roms etc
or is it possible that those apps i want to use just even dont work with this fix? cause my market works just some specific apps do not like aldi talk app or skype app? can u pls help me out on this? are their roms who support all apps?
Click to expand...
Click to collapse
EDIT:
It now does work and i have no idea why or what changed ...
Not sure what's going on with my HD2 but I'm no longer able to update basic apps like Google Maps, I get the "not compatible with your device" message. Actually Google Maps wasn't even listed anymore so I set the density to 160 with LCD Density, cleared the cache of Google Play and it's back but I still have that error message. Is Google Maps "gone" for good from our HD2s ?

[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?

Boot AOPK as default

Hey guys,
I've installed the latest AOPK on my touch pad - and I like it. It just works great. Because of its nearly perfect state I decided to set this as the default is on the device. So how can I St the things up to boot AOPK instead of WebOS in the boot menu?
cheers
Couple of ways.
First way (easier), is to use a file explorer (I use Root Explorer), and browse to /boot. Hit the mount button so that it's mounted, and look at the file listing in there. There should be one called "moboot.default", and one "uImage.AOKP" (or something of the like - I don't have AOKP installed, so not sure the uImage filename). Then you long-press on the file "moboot.default" and hit Open With... and choose Text Editor. In there, change what it says to the AOPK (minus the uImage. part), save, delete the backup file (moboot.default.bak), and reboot. You should be good to go.
Second option, is to reboot into WebOS, load up Preware (if you have it already - if not, google and install it), then look for an app called Cyboot. That'll allow you to change your default boot, and many more settings related to it.
Hope that helps, mate.
Thank you! I've installed Preware and Cyboot - it worked.
ve6ay said:
Couple of ways.
First way (easier), is to use a file explorer (I use Root Explorer), and browse to /boot. Hit the mount button so that it's mounted, and look at the file listing in there. There should be one called "moboot.default", and one "uImage.AOKP" (or something of the like - I don't have AOKP installed, so not sure the uImage filename). Then you long-press on the file "moboot.default" and hit Open With... and choose Text Editor. In there, change what it says to the AOPK (minus the uImage. part), save, delete the backup file (moboot.default.bak), and reboot. You should be good to go.
Second option, is to reboot into WebOS, load up Preware (if you have it already - if not, google and install it), then look for an app called Cyboot. That'll allow you to change your default boot, and many more settings related to it.
Hope that helps, mate.
Click to expand...
Click to collapse
Thanks a ton mate!
Sent from my Galaxy Nexus using Tapatalk 2

[Q] question: language settings in Go Keyboard

I rooted my Nook Tablet (8gb) following jichuan89 and others' thread. I installed Go Launcher and everything works great.
However, I could not get Go Keyboard work. I installed it, and when I am trying to enable it by selecting "step 1: choose Go Keyboard". it tells me "please click settings --> language&keyboard to enable Go Keyboard". BUT I do not have a "language&keyboard" option in any of my settings.
Please help.
To get a keyboard to work on a stock rooted rom takes some extra work beyond just rooting.
There is a post on this for Swype keyboards. I have been able to get it to work with pretty much any keyboard.
Using your root explorer (i use es explorer and be sure to enable the r/w of the root directory)
Copy the .apk of the keyboard you want to to /system/app
Long press on the .apk file and adjust the properties. Press change. Make sure all the boxes are checked.
Reboot. You got me i had to go back into the root and has to install the program from there because i was getting force closes. They stopped one i did that.
Sent from my BNTV250 using XDA

Categories

Resources