Database Users

(Q) Swype Beta

Does anyone have the exact method for installing Swype Beta on a stock based Rom (i.e. Iced Glacier)? I can't get it to install correctly at all.
Geoi1006 said:
But without further chit chat here's what I did:
Using Super Manager I:
1) Mounted the system as r/w.
2) Went into System» App» Deleted the swype.apk
3) went into System»lib» deleted the libswype file
4) Then followed normal install procedures as laid out in Swype Beta using the Swype Installer you receive when signing up for their beta.
It should be noted as with any system file you may or may not need later that its always smart to back up the stock Swype files for future restoring if needed.
[\QUOTE]
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse

yes, I currently running cyanogen I pulled the following from stock, or evil roms..
you ll need two files....
system/app/swype.apk
system/lib/libswypecore.so
Anytime I updated from cyanogen, I would still have swype but received the for close error, until I pulled the libswpecore
hope that helps
edit....think you want to download it from the swype site, enroll in the beta program and you should be good to go, may have to remove the above files to get the beta though

I got it figured out. I'm already enrolled in swype beta, thanks though. The question was how do I install swype beta on a stock based rom, Iced Glacier in this case, in which Swype is a system app(protected if you will). I got it figured out though. If anyone uses swype beta then they know that its much sexier than the stock Swype included lol. But without further chit chat here's what I did:
Using Super Manager I:
1) Mounted the system as r/w.
2) Went into System» App» Deleted the swype.apk
3) went into System»lib» deleted the libswype file
4) Then followed normal install procedures as laid out in Swype Beta using the Swype Installer you receive when signing up for their beta.
It should be noted as with any system file you may or may not need later that its always smart to back up the stock Swype files for future restoring if needed.
Sent from my HTC Glacier using XDA App

My lib was named libSwypeCore.so not libswype.so. Although that may be because I had / mounted rw but didn't actually delete the files first.
This was really terrifying. Swype is what makes the difference between me needing a phone with a keyboard or not. I find the poke&peck keyboards absolutely unusable.
But I was very envious of the mic button built into the keyboard because I've also found the voice recognition to be shockingly good. Historically I've found voice recognition software to be about 30% accurate and generally produced results one would expect from a slightly retarded monkey.
But I digress. These instructions worked perfectly and the new Swype is even cooler than the stock one.
Swype is an application I would pay a significant amount of money for. But free works too!

Glad to help man
Sent from my HTC Glacier using XDA Premium App

And I hate the white keyboard swype is skinned with from the stock apk.
Sent from my HTC Glacier using XDA Premium App

i did this on my stock rom, and swype basically deactivates itself after the phone is rebooted. swype keyboard will come up, and peck-typing works, but the swyping function is disabled. i've seen this before when playing with swype hacks. it means it's not licensed properly. i removed swype.apk and libswypecore.so manually before doing this.
is yalls swyping functions still working properly after a phone reboot?

I have to select the android keyboard then reselect the swype keyboard on every reboot. I find this is necessary on sense based roms mostly.
Sent from my glacier using XDA Premium App

So is there any way to get the beta version to properly recognize its license, so you don't have to manually switch away from, and then back to, the beta Swype keyboard after each reboot to get it to work correctly?

Like maybe there's some type of an auto-script that could be written to run on each boot that would select the stock keyboard and then re-select the Swype beta keyboard?

I thought swype comes preinstalled?
Sent from my HTC Glacier using XDA Premium App

The beta version has the microphone button on the keyboard, which is why I want to use that one instead of the pre-installed one...

Swype Problems?

Myself and alot of users are/were having the Swype problem with it not working and saying trial period is over time to upgrade. Also the blue borders when trying to use and swype is not responding. Took me a couple hours today, but I got it. I tried everything else First, but this WORKS.
1: Use Root Explorer and Delete the Swype files in System/App (1 File) and System/Lib (2 Files). (Mount in R/W to Delete)
2: Go to Swype Beta online with your phone. Sign up for beta and they will send it to your Gmail.
3: Install and be happy again with your Swype!!
This is a Swype specific Problem and the beta is kick A$$!! Check it out on swype.com and you will see many with this same problem. It is not limited to MT4G.
Now you can recieve all new Swype Upgrades Via E-Mail.

The only problem I have is that MIUI doesn't seem to be compatible with the swype download from their site. Any ideas?

Try pulling swype from one of the roms that had it. It works flawlessly for me
If you pm me, I can tell you the easy way of getting swype
Sent from my HTC Glacier using XDA App

Yes pull it from a working rom,
Pull the following
System app swype.apk
System lib lib.swype
something along those lines, and use adb to push them into rom of your choice,
Sent from my HTC Glacier using XDA App

I've had a lot of problems with previous betas on my mt4g, especially with the swype not working at times (usually when I have to send a fast/important message, lol) but after a few days with 3.0 I haven't had the same. It's working great (nock on wood).
Sent from my HTC Glacier using XDA App

Android market

Anybody know why I can't access the AMarket from my phone? It keep crashing the past couple of days...
Sent from my Nexus One using XDA App

On another problem I'm having is my phone keeps saying the "su binary is outdated" , when I try to update from my phone it downloads but quits on the final move.....
Sent from my Nexus One using XDA App

Try wiping the data for Market. This can be done in Settings -> Applications -> Manage Applications -> All

bassmadrigal said:
Try wiping the data for Market. This can be done in Settings -> Applications -> Manage Applications -> All
Click to expand...
Click to collapse
you can also try to select "uninstall updates" on your market.
Sent from my Nexus One using xda premium

Try to wipe the dalvik cache.

Try to uninstall by titanium backup pro.And install another one

Solution
TJJSDJ said:
Anybody know why I can't access the AMarket from my phone? It keep crashing the past couple of days...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Go to settings->Language & Input->Language; and select English US (or whichever u prefer). And Market should work after that.
I had the same problem when I switched to ICS rom (by texasice). Found this solution after a lot of searching and it definitely worked for me.
Btw, no other solution worked for me (clearing cache, dalvik..).

I always get the msg "Authentications required. Please log into your Google account." :-(
P.D I use the Market Enabler

My Apps in Market FIX!!

Thanks to MyronJ906 for the start of this. FINALLY!! Anyone who's having trouble with My Apps not showing in the Market, here's what did it for me. To get Market to show My Apps, change the following in build prop. (I used prop editor via ROM Toolbox.)
Changed:
Code:
ro.build.id=4.5.133
ro.product.manufacturer=motorola
ro.build.product=olyatt
ro.build.description=olympus-user 2.3.5 4.5.133 111012 release-keys
ro.build.fingerprint=MOTO/olyatt/olympus:2.3.5/4.5.133/111012:user/release-keys
to
Code:
ro.build.id=4.5.91
ro.product.manufacturer=Motorola
ro.build.product=olympus
ro.build.description=olympus-user 2.3.4 4.5.91 110625 release-keys
ro.build.fingerprint=MOTO/olyatt/olympus:2.3.4/4.5.91/110625:user/release-keys
ro.buildversion.release=2.3.4

I had this problem when I was using the 2.3.4 BLUR ROMs (retail UK, wet dream, etc). These problems made be rollback (or rollforward depends on how you see it) to CM7 week4 rom.
Will flash a blur ROM to test this and report my results.
Cheers!!

Flashed retail UK ROM (SBF), have the "market problem".
Apply the change to build.prop, no luck.
delete data & cache from market app, no luck.
wipe data & cache, no luck.
Flash Wet Dream 1.3 lite, modify build.prop,
clear market data & cache, restart.
still doesn't work

Cm7 redpill. This did not work. I even had the problem with cm9
Sent from my MB860 using xda premium

I don't have problem on CM7/9 (touch wood). but I have problem with all blur based roms.

In my case, I managed to fix it by
1) Uninstall Preset 1.0 using Titanium Backup
2) Clear Data from Market
I compared the CM7 market database and Blur market database, found com.motorola.contacts.preloaded in the blur version, but not in the CM7 version, and traced it back to the Preset 1.0.

i just download something from the market and all they appear again...

do you mean, without making any change at all?

ken218 said:
In my case, I managed to fix it by
1) Uninstall Preset 1.0 using Titanium Backup
2) Clear Data from Market
I compared the CM7 market database and Blur market database, found com.motorola.contacts.preloaded in the blur version, but not in the CM7 version, and traced it back to the Preset 1.0.
Click to expand...
Click to collapse
Will try this but went from Cm7 to CM9 and still the same bullocks.
Edit Cannot find preset 1.0 maybe cause im on C9 but looked at all system files on system files using Tit back

check the market database, see if there is anything likely to caus problem.
preset 1.0 is only in the blur roms.
Sent from my MB860 using XDA App

Weird, I cleared data on market and froze updator as well as cleared its data. Loaded market, as soon as I accepted I hit my apps and my apps populated. I could update and did update an app. I closed the market, reopened, went to my apps and the same old thing happened.
Sent from my MB860 using xda premium

one of your app is causing this issue. when you wipe data from market, it rebuild market links from apps on your device.
after you wiped the data and check back to the arket, it is still busy building the database, that is why it worked for a short period of time.
look in data\data\com.android.vending\database
the market database is there. if you can find the app causing the issue and remove it, you can get your apps showing again.
Sent from my MB860 using XDA App

just to add, the app might not be what you have downladed, it might be something in the rom.
Sent from my MB860 using XDA App

Thanks but couldnt find problem in databases. Will wipe and restore in batches.
Sent from my NookColor using xda premium
News; found the culprit, warez app (blackmart) don't use it anyway since I've spent like $100 bucks on apps. I like the updates. All is well now. Thanks

How do you disable OTA updates on Nexus 7?

I am on stock 4.1.2. I recently flashed back from 4.2. I do not want to update as I found it extremely buggy. I keep getting a notification to update and it is annoying. Anyone know how to disable it?
Sent from my Nexus 7 using xda app-developers app

You need to root
Then do this - http://forum.xda-developers.com/showthread.php?t=1998378&highlight=disable
If you don't use sync you can also force stop "Google Service Framework"
BUT... this way isn't recommended by most... but it worked for me before rooting, would stop it for days, then it might come back after a while

Search for fotakill.apk in Google search. Place it in system/app using ES File Explorer or other file app (if using ES make sure to go into preferences - root options and enable all selections available). Change permission from RW to:
R W E
R W
R W
Then tap the app in system/app to install it. After install reboot to custom recovery and wipe cache. Reboot. Once it reboots you might still see the icon for system update. Clear the notification. If you check for an update after that it should say up to date.
Sent from my Nexus 7 using xda premium
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
TokenAntiAppleRant said:
Search for fotakill.apk in Google search. Place it in system/app using ES File Explorer or other file app (if using ES make sure to go into preferences - root options and enable all selections available). Change permission from RW to:
R W E
R W
R W
Then tap the app in system/app to install it. After install reboot to custom recovery and wipe cache. Reboot. Once it reboots you might still see the icon for system update. Clear the notification. If you check for an update after that it should say up to date.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Pfff oops. Didn't see the hyperlink in the previous post. Sorry!
Sent from my Nexus 7 using xda premium

Thanks for the comments! I am not wanting to root at this time because I am enjoying how this is running. So I hope this post will stay here if I place in my favs to come back to if I ever root. I will do the framework thing for now. I doubt I will be updating to 4.2. I noticed my offline GPS was not working on Google maps after updating to 4.2. So many problems with that update. Glad I went back. Thanks again! You guys rock!
Sent from my Nexus 7 using xda app-developers app

For what it's worth, I used the Google provided 4.1.2 files and scripts to go back from 4.2.1 so an expensive app would work on the Nexus 7. I have not yet locked the bootloader if this makes any difference. What I then did was install System Tuner Pro. From the menu in that app, go to System (red android symbol), find Google Services Framework and click on it to highlight it. Then at the bottom of the screen choose Settings and turn off Notifications and then Disable it. You can simply go back, I suppose, and Enable which is that the box says now. After doing this it will show that as frozen.
So I have not rooted my Nexus 7 and this seems to stop the OTA prompts for updates. I'm unclear what else this stops, but I'm not using much involving Google syncing, so probably not any harm. (You can also use System Tuner Pro to backup up your user apps and it writes these backups to the sd card. I have not tried to restore them yet, having no need.)