Currently I am using the Community Rom 1.2 flashed from the stock OTA ED01.
As the title states, I have chosen to use the Gingerbread keyboard in settings and at random times it will switch to the Swype keyboard. As an example, I can sometimes start to type a text using the Gingerbread board, which is good, and within a few minutes I can open the browser to type and the swype board pops up? Also, when I reboot it pretty much always reverts back to the Swype keyboard.
Any ideas on how to make the setting for using the Gingerbread keyboard stick?
Could I maybe get a link to the Gingerbread APK that is used in the Community Rom?
Appreciate the help ahead of time...
Update...
Flashed latest Red Voodoo CWM 3.x UPDATED 4.26.11 with Odin and wiped cache, dalvik, reloaded Community Rom 1.2 Patch and fixed permissions.
Gingerbread keyboard seems to be working now without switching to Swype.
Update 2
Spoke too soon...
As soon as I plugged the phone in to charge and let it sleep for a while, it reverted from the Gingerbread board back to Swype.
Any ideas???
Root your device. Once its rooted, you can then install Superuser and a root-enabled uninstaller. You can then uninstall swype, which (if you're like me) is not a feature you'll miss.
Related
THIS ROM HAS NOW BEEN SUPERCEEDED BY MODACO ROM 2.0. I WILL NO LONGER BE PROVIDING UPDATES/SUPPORT FOR THIS ROM.
12/18/09 Update
Here is my most recent version of the updated MoDaCo rom. I have fixed the version display info.
This rom should be safe to upgrade from stock or MoDaCo 1.1 roms.
If you experience force closures the issue is with your dalvik-cache or your boot-cache.
You can clear your dalvik cache from the recovery mode. Do not do a factory wipe. Choose the dalvik-cache wipe/clear.
You can clear your boot-cache from adb as a temporary fix by typing:
rm -r /data/boot-cache
reboot
Changelog:
1.3a:
-rebuilt properties file
-shuffled some apk's around
1.3:
-no longer requires wipe to install/upgrade
-fixed ssh password in about screen
-fixed version info to show correctly
-all market apps should show correctly
-updated to busybox without color codes (this is for the windows users using adb shell)
-upgraded to latest relase of wifi tether
-minor performance tweaks and optimizations
-minor interface tweaks (new lockscreen animations)
1.2c:
fixed issue with protected apps not showing up in market
reverted displayed version # in phone settings (sprint update is still there though)
1.2b:
fixed builld/version info
fixed force close issues for people who upgrade from MoDaCo 1.1
1.2a:
manually patched Sprint Maintenance Release to MoDaCo 1.1 rom.
Get 1.3 here.
Install from the recovery console. No wipe should be necessary!
Please post here if you have problems.
Just flashed from 1.1, getting a bunch of force close messages on boot can't use internet, software version 1.29 so no update, don't know if I should've flashed from stock but thought id try from 1.1.
I'll look into it later right now I need sleep. FYI I updated from a stock patched Rom freshly rooted. You may need to do a wipe for it to work properly. Also i hand copied the individual patched files into the modaco 1.1 to make this work. I am new to this so I do not know how to update the version # by hand editing yet.
getting a bunch of force close messages also,plus it lags pretty much
dunno why but i tried it,thx anyway..time to flash again .
Is the bluetooth audio streaming working?
works great nice job man
i would also like to know if you can play media via bluetooth speakers on this ROM...all ROMs w/ the MR update don't seem to be able to do it, but the Sprint MR update w/ no custom ROM installed can
I got a bunch of force closes when it booted up. I also noticed the browser and some google apps will no longer open and just force close.
mine works perfect
Works fine for me. I did revert back to stock before doing the update and reset my data to be sure.
The build number in the "about" screen is the old number, but things do seem to be updated to the new stuff anyway. To change the build number, I think you need to edit the /system/build.prop file.
Great work!
My force closures have healed themselves! Well, except for the "market" app but I bet I can uninstall/reinstall it.
Obelisk, hopefully this description of my steps helps in finding some answers...
Last night, before I saw obelisk's first few posts regarding his experiment, I had decided to bite the bullet and flash back to the stock Sprint RUU.
First I copied all of my app and app-private folders to my SD card. Then, I did a nandroid backup and then flashed the RUU. I let Sprint download and install the MR. Then I rooted and flashed the recovery image. This is when I found obelisk's posts and decided to try it out. After I flashed his "unofficial" update I booted up and then rebooted (it stated "reboot required" in the menu\settings\about phone\build number after "MoDaCo Custom ROM"). At that point everything was working fine. No force closures, phone was sleeping correctly, I had mute and speaker phone buttons in the call screen, etc...
I decided to copy my apps back, restore my nandroid backup (even though I knew this would undo everything I had just done) and then reflash obelisk's updated modaco again. After doing that I rebooted and got a ton of force close errors. I just closed them all and went to bed!
HERE"S THE WEIRD PART! I woke up this morning and the only force close I'm getting now is with the market app (and ONLY if I try to open it). All my other restored apps are working fine. I am about to go to work but I will play around with this some more. I'm keeping it for now!
I just rebooted and all of the force close errors came back. I guess I'm going to go back to my original pre-MR nandroid backup.
i think the problem is related to the software version number which i haven't figured out how to update yet, so a lot of the apps, and yes there were about 20, that were patched in the maintenance release don't get updated properly until i increment the rom version somehow. i'll mess with it tonight when i get home from work.
did a fresh ruu, and updated this custom rom over a rooted stock, did a factory reset after the install and absolutely no issues.... A+ job buddy
johnsongrantr said:
did a fresh ruu, and updated this custom rom over a rooted stock, did a factory reset after the install and absolutely no issues.... A+ job buddy
Click to expand...
Click to collapse
How do you go about doing a fresh ruu?
I'm going off of memory here but...
1. download the sprint RUU
2. install HTC Sync on your pc if you have not already done so
3. connect your phone to your computer
4. run RUU (it's an executable file)
5. Follow prompts
6. Reboot phone into stock un-rooted goodness/badness depending on your opinion.
obelisk79 said:
I'm going off of memory here but...
1. download the sprint RUU
2. install HTC Sync on your pc if you have not already done so
3. connect your phone to your computer
4. run RUU (it's an executable file)
5. Follow prompts
6. Reboot phone into stock un-rooted goodness/badness depending on your opinion.
Click to expand...
Click to collapse
im getting an error 107. the ruu nor htc sync connects to my phone anymore
ABNinja said:
im getting an error 107. the ruu nor htc sync connects to my phone anymore
Click to expand...
Click to collapse
Is your battery fully (or at least mostly) charged?
EDIT: Sorry, I just noticed that's a different error.
Great Rom
I came from a rooted stock Rom wither the Mr update...wiped, flashed...apps2sd, then reboot. Worked flawlessly! I also added the extras from another Rom and everything is running fine. Great work on this..
are you getting error code 107 or 170? google provides no help for error code 107...
CM6 Extender was put together to enhance CM6 with a few small tweaks, but not make any major changes to the UI. Everything included can be found around the xda-developers forums, or directly from the developer, for free. I just combined them into a single zip that can be flashed in place of the GAPPS zip when installing CM6. Changes to stock CM6 below.
Includes all latest Google Apps (GAPPS)
Removed Facebook/Twitter (because they are easily found/updated in the market, makes sure you always have latest version)
Removed ADW Launcher, Replaced with LauncherPro 0.7.6.0
Replaced kernel with CM6-Snap-v7.4-havs875/OC/UV http://forum.xda-developers.com/showthread.php?t=733099
Added SNAP-widget by spiicytuna to manage/monitor it
Replaced Default Keyboard with Droid-X Multitouch: http://forum.xda-developers.com/showthread.php?t=754948 (White with green highlights)
Creates a folder in your SD card with installers for Swype 1.61 and HTC Sense KB with 2.2
Added ES File explorer (To install those keyboards)
Added MSL Reader (Donate to the dev link within app)
Added Flashlight Alerts by apristel (not enabled by default, Donate to dev by purchasing from market) http://forum.xda-developers.com/showthread.php?t=699978
Added Sprint TV
I will update Snap kernel once the 8.0 battery issue is solved.
Please donate to the CyanogenMod team at http://www.cyanogenmod.com/
Recommended Instructions:
1. Back that NAND up!
2. Do a full data wipe from recovery.
3. Flash CM6 (update-cm-6.0.0-Supersonic-signed.zip)
4. Flash CM6_Extender.zip
5. Reboot, enjoy
Updated: Moved LauncherPro to Data folder due to stability problems having it in the RO System folder. Also moved ES File explorer and Sprint TV to data folder so you can uninstall them if you want. (You can also download ADW launcher from the market and uninstall LauncherPro).
Also added a bunch of wallpapers to the SD card folder. A bunch of CM wallpapers plus the Galaxy S Wallpapers (all static)
New download link below.
Download Link: http://www.megaupload.com/?d=FHWJYYWV
If you use Firefox like me and want some sweet Chrome to phone action, go here: https://addons.mozilla.org/en-US/firefox/addon/161941/
You should also grab SetCPU to take advantage of the new kernel here: http://forum.xda-developers.com/atta...6&d=1278385677
Should work with both RA and ClockworkMod Recoveries!
If you find any bugs or know of something cool I need to add, post it below! Thanks!! Also, if someone could provide a better mirror, that would be awesome!
This sounds pretty awesome! Why no replies or feedback?
Vandam500 said:
This sounds pretty awesome! Why no replies or feedback?
Click to expand...
Click to collapse
I just finished 20 minutes ago! lol, so far so good for me and my gf.. Let me know how it goes for you
Well I have no feedback because I'm all configured. It may be useful when I start messing around again.
Also, I just like my open source ADW. But this is a great idea. Thanks for the contribution. I will give this a try later.
Vandam500 said:
This sounds pretty awesome! Why no replies or feedback?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I will give it a try. Thanks for putting this together for us.
Sent from my PC36100 using XDA App
Tried it, running Cyanogen RC2. RA recovery and it could not open. Error trying to open. I really wanted to try this.
Sent from my PC36100 using XDA App
f3rrand said:
Tried it, running Cyanogen RC2. RA recovery and it could not open. Error trying to open. I really wanted to try this.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Was it a syntax error by chance? I've gotten that a few times. Been trying to figure out a permanent fix.. will re-upload when fixed..
EDIT: I think I've got it. Updating with Snap 8.1, then a new upload coming.
EDIT again: Snap 8.1 is causing a ton of boot loops for me. I'll try and fix this tomorrow night :/
After reboot, I get the HTC screen and then nothing. Have to remove battery to get anything to work again (at which point, the same scenario occurs unless I boot into recovery mode).
Never mind - I just realized this was for EVO's only. I'm using the Hero.
sucks i cant run 875 but i can run 8.1 900 for some odd reason when i try to flash the other kernel over the extender its gets a error after the intial setup page and screen goes black then i restart it and get bootloop... o well i really just want the keyboard i found it though thanks is there a way to remove adw launcher and use launcher pro?
nevermind...
When are you putting the updated version, with the 8.1 kernel. I'm waiting.
Sent from my PC36100 using XDA App
Thanks
You're REALLY making me want to switch from Valpack to CM6. Gonna have to do that this weekend and let you all know how it goes.
Has any thought been put into sticking Hulu in?
http://forum.xda-developers.com/showthread.php?t=752582
f3rrand said:
When are you putting the updated version, with the 8.1 kernel. I'm waiting.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The new Snap 8.1 kernel was EXTREMELY unstable for both me and my gf, so I'm skipping this version. I'm going to try the one he posted earlier today without HAVS and see if it works any better. It would boot loop every 30 seconds...
I'll also put in the new google voice with widgets while I'm at it.
dragonfyre13 said:
You're REALLY making me want to switch from Valpack to CM6. Gonna have to do that this weekend and let you all know how it goes.
Has any thought been put into sticking Hulu in?
http://forum.xda-developers.com/showthread.php?t=752582
Click to expand...
Click to collapse
I actually put in hulu in the beginning and it didn't work.. I couldn't figure out why after a good amount of tinkering, so I took it out.. Perhaps I'll give it another try soon.
I am having an issue. I am trying to install MyBackup Pro to restore my settings and apps from my CM6 nightly ROM and every time it starts to install the app, the phone locks up and shows the cyanogenmod loading screen and then launcherpro restarts. Any ideas?
Changing the wallpaper also locks it up. It was stuck in a loop where the launcher was crashing out to the cyanogenmod screen and then wouldn't start and then back to the cyanogenmod screen. This lasted for about 3 minutes.
Well, I tried reflashing it and now I'm worse off than I was. Can't get past the setup step. Keeps boot looping then crashing. I have been using this thing for 20 min and have already had more force closes than I have the last week and a half on my previous nightly. I give up.
Benjio12 it looks like you are attempting to simplify my life. Thank you for the tweeks I'll make sure to ck it out and follow this thread.
8.2 kernel and battery life?
Do you know if the new 8.2 kernel has resolved the battery issues and if so would you be willing to make an updated zip?
Thanks!!
e_heinemann said:
I am having an issue. I am trying to install MyBackup Pro to restore my settings and apps from my CM6 nightly ROM and every time it starts to install the app, the phone locks up and shows the cyanogenmod loading screen and then launcherpro restarts. Any ideas?
Click to expand...
Click to collapse
I'm also running into similar issues except launcherpro doesn't restart and cyanogenmod load screen loops
Ok I installed this patch and after placing the widget my phone became laggy and the HTC dialer will not install.
I'm running a clean slate of cm6.0 but it doesn't install. I even dropped it in system/apps/. The droidx installs, its the default when you first boot.
What do I do?
Swype came pre-installed on the stock Skyrocket, after updating to the new deodexed rom i seemed to have lost it. I can't find it in any of the markets, anyone have any idea how to get it back on without have to go back to full stock?
just download any of the STOCK AT&T ROMs from the DEV section and unzip it to find the swype.apk within the /apps folder
The Swype that came with these phones is 3.23. The latest version of swype is 3.26 and you can download it on the swype beta official page. I'd recommend the newer version as it has a few more fixes and such in it that make a difference for me.
You can then back it up with titanuimbackup and when you restore it after flashing other ROMs, it will restore your personal dictionary as well.
Sign up for the swype beta and they will send an installer with the newest version of swype.
Or perhaps try another keyboard w/ swype-like capabilities? I'm using Touchpal right now, and it seems to work just fine for swype'ing, and I also like their word prediction (though maybe not as good as Swiftkey).
Hi,
I recently switched over to HyperSensation v 1.5, works very well so far. After some days I experienced the (already known) keyboard freeze bug (see http://forum.xda-developers.com/showpost.php?p=21036318&postcount=2851). Users in the ROM thread suggest to disable predective typing completely or install the LatinIME.apk via adb push.
As I wanted to use predictive typing, I installed the apk but the keyboard still freezes all the time.
Can I somehow verify that I've installed the apk correctly via adb? I'm pretty sure I've done it right but I want to check it if possible.
Anybody else experiencing the same problems?
Bumping. :/
Again.
Sent from my Sensation using XDA App
move on to 1.6
also try flashing the latinime.zip from whatever recovery u r using
I have asked this question in the eyecandy ice cream sandwich thread but no one has said anything. evertime i try to load swype from the beta invite email it goes all the way until i hit to 'fetching swype beta download' then you pic 'swype beta' then is says "parse error, there is a problem parsing the package".
i have even loaded up sense roms and any rom i flash it always says the same thing. every time i flash a rom i run a "wipe sensation" program thengo thru the usual data wipe, cache wipe, them flash rom, then go back and wipe dalvic cache and fix permissions. same combo i have been doing for a year or so.
does anyone have any insight to this problem? I really miss not having swype.
ksnexusone said:
I have asked this question in the eyecandy ice cream sandwich thread but no one has said anything. evertime i try to load swype from the beta invite email it goes all the way until i hit to 'fetching swype beta download' then you pic 'swype beta' then is says "parse error, there is a problem parsing the package".
i have even loaded up sense roms and any rom i flash it always says the same thing. every time i flash a rom i run a "wipe sensation" program thengo thru the usual data wipe, cache wipe, them flash rom, then go back and wipe dalvic cache and fix permissions. same combo i have been doing for a year or so.
does anyone have any insight to this problem? I really miss not having swype.
Click to expand...
Click to collapse
It's not just you man. I've been trying this for days. I'm on an HTC sensation running elegancias sense 4. I have no idea what's up with it. Not having swype sucks
Did you try pushing it to system/app?
have not tried it on your ROM, but on the MIUI v4, this worked for me.
Its a flashable swype.
http://www.mediafire.com/?l5brukdug885u6u
I was getting this error with other apks when my memory card was corrupt. Try a different memory card maybe?
This was happening for me a few days ago. Then resolved itself, however it has started again. It's not only you. A lot of people are reporting it on their forums.
Sent from my HTC Sensation XE with Beats Audio using XDA
Hi I am running ordroid rom and replying to this post using swipe. No problems here. Just enable it in settings. I even choose the color of my swipe. Works perfectly just like with stock. But yes, you do have to enable it first for it to work. Not sure about other Roms but I can confirm ordroid 8.6.5 is running swipe perfectly. Hope this helps.
Sent from my Sensation 4G using xda premium
wow, thank you guys for all your replies. guess i forgot to follow this thread like i normally do. I am going to try the flashable apk in top of this thread. i will let you guys know.
btw, I am a swype fanboy all day long but with these problems trying to load it i have went back to running the swiftkey x keyboard til i can get my beloved swype back.
rolltideburr said:
have not tried it on your ROM, but on the MIUI v4, this worked for me.
Its a flashable swype.
mediafire.com/?l5brukdug885u6u
Click to expand...
Click to collapse
Does not work. Someone has a working version of the installation?
Flash version worked great! Thanks!
There's nothing wrong with your phone.
It seems they forgot to upload the file on their servers; at least this is what they're saying on their forum
http://forum.swype.com/showthread.p...a-Error-Download-Failed-Password-Reset/page12
Hopefully they'll have a fix soon..
rolltideburr said:
have not tried it on your ROM, but on the MIUI v4, this worked for me.
Its a flashable swype.
http://www.mediafire.com/?l5brukdug885u6u
Click to expand...
Click to collapse
Thanks so much for the flash zip. I kept trying to download via swype installer but no luck. Flashed this and set to default input in keyboard settings and it works beautifully! Gonna keep this one for backup.
Sent from my HTC Sensation XE with Beats Audio using XDA
Swype error - permission problem?
Guys/Gals,
I also found another error in alogcat, that could be the issue... it says "Not granting permission android.permissions.INSTALL_PACKAGE to package com.swype.android.installer (protectionlevel=3 flags=0xae44)"
Not sure, but it may be the issue. Anybody know how to allow that permission for this app?
*edit* tried copying the installer app to system/app , but that does not do anything. I am also getting the FileNotFound exception, but that could be a problem with Swype installer in ICS...
The flashable file worked like a charm, boom... I've been having the same issue with parsing errors. I guess the dummies from Swype have not fixed the problem yet.
Thanks rolltideburr
I am trying TouchPal now (free in google play)... so far quite good (better than SlideIT). If Swype wants to scare their beta users away, they are making a good effort of it.
Here is how I got Swype back:
If any of you have a NAND backup of before you lost Swype, you can pull out com.swype.android.input (or something very similar) from the backup and extract it. Once extracted and restored (app + data), wipe cache and dalvik and go enable it in Settings --> Language and Input. BAM!!! You got Swype!!