Related
I decided to make a thread for kaos that gives a more complete set of incomplete/broken things so he doesn't half to. I will try to keep this up to date as possible and if you see something that has been fixed that i have listed as broken please post and I will correct it. I will try to do as many detailed things as possible for now and as things are fixed I will remove them and if a fix is required to be applied manually will try to include it also. Keep in mind this is an unofficial thread and I am not responsible for anything you do to your phone. Now to the list (PS if this is an inappropriate posting area feel free to move it)
Data: FIXED entirely update to latest build
Wifi: FIXED update to latest build.
Bluetooth: Somewhat working, will pair but won't connect.
Browser: UPDATE: fixed, still crashes on flash and javascript some though according to people in irc.
USB notification: no usb mount notification not sure if USB mass storage will work or not but adb still works so a work around is using the commands adb push and adb pull (google on how to use these commands if you dont know already)
Vibrate notifications: vibrate works on the stock messaging app fine but I can't get it working on go sms. Workaround would be just use the stock notifications.
Quadrant: quadrant doesnt work for me gets stuck at database writes, not a big deal no known fix though
Sensors: FIXED update to latest build
Headphone jack: Headphone jack is now fixed somewhat. Still buggy to a degree some headphones won't work (it seems to only work for headphones that have a mic built in for me but it could be just hit and miss with all headphones).
Haptic feedback: haptic feedback in general doesn't work. No known fix
Camera: Currently not working. No known fix.
Cyanogen Settings has some things that make the phone freeze, DO NOT ENABLE JIT its not working yet.
Recovery: Currently broken for me and some other people. Not sure if its working for others (kaos's works and has been apparently.) JT said it shouldn't be a hard fix for him in the future (likely next release?) Use odin to get back to stock and restore your backup from before you had CM installed if you made one if you want. (report any problems in thread please) UPDATE: Greyone and Kaos informed me that recovery works if you go to recovery mode and select advanced > reboot recovery (thanks!)
Wireless tethering:Works if you use the Wireless tether app! fix found by ae55. Might work with other wireless tether applications but it WILL NOT work with the wireless tether in the settings menu.
USB tethering: Not working for me (try it and post if it works for you, its in settings, wireless and networks) more than likely a 3rd party app like easy tether would fix this as long as your 3g is working
MMS: MMS also does not currently work. A workaround is to simply get the message sent to your email for receiving but it seems that the sending of gmail messages isnt working atm i just did a test message to my number and it is sitting in my outbox. Been there for a good bit so its more than likely not sending it. A 3rd party application could fix this possibly? Update: Message finally went through it took a solid 15-20min though so I wouldn't rely on it myself. Again, 3rd party app would prob be your best bet around this. IT DOES NOTIFY YOU IF YOU RECEIVE AN MMS JUST WONT DOWNLOAD IT!
ADW launcher app drawer: not really a bug just many users have looked for this and cant find it, its pretty simple to fix just longpress on the homescreen and tap custom shortcuts then the adw launcher things then app drawer. Hope this clears some things up.
YOUTUBE: seems as though the youtube application isnt playing videos, I dont have good enough service to test it but I will take everyone in the threads word for it. Other video playback apps seem to be having trouble too.
Pandora: Currently my pandora isnt working, could just be me but i think its a problem with the 3g still.
Thats all that I can find for now that isn't working but its likely I missed something, I more than stress to keep in mind Kaosinate is still a VERY alpha build. Its about a 50-50 split between things working and things not working for now but it is coming along thanks to Kaos' work on it and I invite everyone to follow him on twitter and join IRC for the MOST up to date information about this ROM.
Edit: Nevermind. Haven't checked his tweets (well, his reply tweets). Good write up.
bendbowden said:
From Kaos' thread:
Click to expand...
Click to collapse
Kaos permitted and favored this thread on his twitter. (check it)
wirless tether worked for me on v1
Sound hound doesn't work lol. Can't recognize any song that it could before.. Not a hardware issue but still
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Cannot delete files using root explorer
rm: no such tool
so far i love this rom. here are the few things i have noticed so far, some are probably known already
-unable to setup an exchange 2010 account. I fixed it by loading a new e-mail.apk i found in CM forums.
-Unable to watch videos. sling, vevo, movie trailers.
-Some funky thing happened when i powered the phone off. had to pull battery.
minor things i know, but i wanted to point them out.
I get no service from verizon at all. Roaming symbol then no service. Dunno why. Will try flashing again later when I have easy access to odin
Sent from my sch-i500 using dj05 w/ stupidfast kernel
my slingplayer works.. i get a "There was a problem while playing" error for youtube.
daavy said:
my slingplayer works.. i get a "There was a problem while playing" error for youtube.
Click to expand...
Click to collapse
Same here, YouTube does not work. No big deal.
I just want my GPS
aes55 said:
wirless tether worked for me on v1
Click to expand...
Click to collapse
]\
I would love to know how this is possible when the wifi drivers wont even load... post up some pics or something.
EDIT: Kaos has informed us that the drivers do load its the wifi scanner files that arent working yet.
BartJJ said:
]\
I would love to know how this is possible when the wifi drivers wont even load... post up some pics or something.
Click to expand...
Click to collapse
here you go
EDIT: This is with the stand alone "wireless tether" app
aes55 said:
here you go
Click to expand...
Click to collapse
Interesting I'll update the thread to include such information
2296 in quadrant...
To fix the rm: no such tool prompt;
Threax said:
Thanks this works perfectly. You can even do it in root explorer by navigating to /system/bin/rm and choosing rename from the long press menu and renaming it rm.old. Don't forget to mount rw at the top.
Click to expand...
Click to collapse
Sling started working after reboot but I found a few others.
Pandora and Sirius wont stream
Speakerphone no workie
Sent from my SCH-I500 using XDA App
The latest Swype beta works wonderfully in Kaosinate v2.
There is an extra step you have to perform to get it working.
Download and install the swype installer from your beta.swype.com page. Install swype. It will force close when trying to configure swype after the install or generate a license.
Delete the libSwype.co from system/lib/. Then reinstall swype and voila! You will have a fully working, fully up to date, swype keyboard.
--I'll post this in the kaosinate thread too to make sure everyone knows it works. I was dying w/o it.
Edit: just realized someone already posted this in the kaosinate thread so i'll just leave it at this post.
Anyone else still getting the skipping in audio with this? Damn annoying..
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Audio only skips when you change the volume or something of that sort for me, not a real big deal.
Does it a ton during playback for me
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Neuman.Tim said:
Anyone else still getting the skipping in audio with this? Damn annoying..
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Click to expand...
Click to collapse
My notification sounds do this if the screen is off. Play briefly then stop, soon as I wake the phone it continues to play
After GSB Gingerbread 1.7 and up, swype has given me the message "The swype package you installed is configured for another device and will operate with limited functionality. Please contact Swype about this issue." However, using 1.6 and below, it works fine.
P.S. I really think this 10 posts or less can't post in the development discussion forum is not needed. Some people like me are just naturally good at things and want to post to report an issue or a bug. If we really are supposed to post in the question and answer thread, then having others post in the rom pages is unnecessary...
Swype is pretty finicky with GB in my experience. I've hit this problem a number of times. remove swype, remove installer, I use estrongs (any explorer with root privileges will do) I don't remember the exact location but there is a random swype file that sometimes gets left in a folder in /data somewhere. Delete it. Reboot and wipe dalvik. Reboot and let the apps reload and then follow the swype email. This has always worked for me, maybe it could for you too. Swype will still disable on reboot, but just change to a different keyboard and back and it will work again. Doesn't seem to be a real fix for that aspect yet.
Sent from my GSBv1.7-ERIS using XDA Premium App
Clearing the dalvik cache seemed to have done the trick! I didn't find the random swype file though. Thanks!
I have had some new trouble starting with 1.9. Previously with GSB (and KGB) all I had to when it booted up was switch keyboards and switch back and it would quit some latin process and then be fine. However, starting with 1.9, it works just fine on startup except that it won't let me double tap to edit. After switching keyboards around, the latin process still force closes, but I don't get the double tap feature back.
Swype already knows about this issue and says that you should just click the swype key for now.
andrew951 said:
Swype already knows about this issue and says that you should just click the swype key for now.
Click to expand...
Click to collapse
I didn't even know you could do that! That will help a bunch. Thanks!
Sent from my GSBv1.9 ERIS using XDA App
i haven't had a chance to try it on my NC yet, but i think we might now be official.
http://stage3-beta.swype.com/android/supported/
I'm installing the update now i will tell you if it works.
ngrenn35 said:
I'm installing the update now i will tell you if it works.
Click to expand...
Click to collapse
Thanks! Don't forget to include what ROM you're running.
Honeycomb build 4 not working w swype
I installed todays swype and i can tap out words but not swype. I know i am using the right keyboard because it does trace but the words wont display.... Honeycomb build 4.
Works great for me on CM7 v14
It looks great but I can't actually use the swype function, like the poster before said.
Running CM7 and when I swype the border flashes blue but no word appears. Otherwise, it's nice to see some large screen support from Swype. I love it on my Vibrant
Doesn't work for me (NF 0.6.8.3). I can type but can't Swype.
It worked for a second then quit, cm7 v14 Keyboard is nice for fat fingers. Soo close.
I have phiremod v4.1 and the swype does as the others said; I can see the keyboard and the swpe gestures, but no words appear, I can tap them out as with the regular android keyboard, but swyping does nothing. It does make a noise after a swype gesture though.
Also when I put the NC in landscape view, the skype app takes up the entire screen.
still not able to try on my NC, but when swype does that behavior on my nexus one, if i switch to the android keyboard then back to swype through the input method selector, everything works great.
fzr-r4 said:
still not able to try on my NC, but when swype does that behavior on my nexus one, if i switch to the android keyboard then back to swype through the input method selector, everything works great.
Click to expand...
Click to collapse
You may well be my hero. I can't confirm that it worked for sure, as it threw a licensing fit since I used it on HC instead of CM7, so I'll revert back to HC and try this again. The licensing fit never occurred until I tried what you suggested.
Tried that method of switching to Android KB and back, still didnt work for me, same as everyone else.
I'm getting the same results on CM7 v17. I'm also getting a message that says swype is configured for another device and may not work correctly when I first switch over to it.
g
Boinky said:
I'm getting the same results on CM7 v17. I'm also getting a message that says swype is configured for another device and may not work correctly when I first switch over to it.
Click to expand...
Click to collapse
yeah, shoot, me, too. eMMC Honeycomb 2nd edition.
Sent from my Nexus One using XDA App
I have read in another thread that Nookie Froyo tends to spout random IMEI numbers when an app asks about the device it is installed again. Swype authenticates the beta by IMEI and you are limited as to how many IMEIs you can install it on. Thus the licensing problem - install Swype and it locks itself to the reported IMEI. Then run it again, and it thinks it's installed on another device.
Licensing errors
I'm also getting licensing errors but the keyboard does appear to load correctly on, CM7 #17,
damn. Was so excited too. Wont swype. Have been dying to put it on my NC, typing on this thing sucks.
Sometimes the betas get hacked (but no posting warez here!) so they are not IMEI locked anymore. Unless we can figure out a way to report a stable IMEI on the NC across all firmwares per device, that may be our best bet .
Will try when the WSVGA will be supported in french..
Yes I can confirm what is being said here about the IMEI... Definitely the root cause here as reported on the swype official forums.
The way I see it, this can be worked around without the need to hack the Swype package. My understanding is all we need to do is spoof the telephony stack a little better, so that the IMEI is consistent. I am at work so I cannot do too much to find out how hard that would be.
android API call for getting IMEI is
android.telephony.TelephonyManager.getDeviceId()
First step would probably be to override this function and just report to logcat to confirm the Swype Licensing process (Would have to check both "Swype installer" and "Swype" applications this way, full end to end install process) calls that function to retrieve the IMEI instead of using another method.
Then if that works, override the function to return a static number. Does anyone know if the IMEI can be used to reverse lookup manufacturers and devices models the same way MAC addresses can? If so, we may need to carefully pick the number returned so that if Swype does a reverse lookup it thinks we are using a valid device - Such as Galaxy tab, which I believe is functioning under the latest beta.
I am definitely not an expert android dev, I barely understand this stuff so far. Just hoping to get the conversation started because I'd really like to swype.
Would someone be kind enough to send me a link to a STABLE version of a Swype apk for my Eris. I have tried searching the boards for a file, but I mostly find tuts that either have the newest unstable apk, or are for phones that are not even close to Eris specs. Thanks in advance and I am much obliged.
Sent from my ERIS GSBv2.1 using XDA App
I'm not so sure there's a stable swype release for the eris running gsb. I'm pretty sure you are either in the beta and deal with it or you get a different keyboard and deal with that....
I figured there might not be...more or less I want to try if out and see if I like it, I just don't want to install a build that has major bug issues.
Sent from my ERIS GSBv2.1 using XDA App
FWIW, I've been running swype beta on GSB and on FroShedYo's, xtr's, etc.. and the only bug that I've found that's consistant (to me) is that after you reboot, you have to long-press a text field to change input method back to the regular keyboard and back to swype before it will work...Otherwise, it works great for me again until I reboot.
Stable
I have a version that was sent to me that I haven't run into any problems with.
email me if you want the apk. I'm thinking about trying it out on my archos 101 tablet.
robert dot beers ii at gmail dot com
Matt
there are two that I know of but its against the rules to link to them directly.
search google for the following and find it yourself. =-)
swype_1.60.36.8214_HVGA
there is another one but I can't remember the file name since I dont have my phone on me today. but 1.60 that was floating around 6 months ago never expired. most of the other versions did, but I believe I had a 2.60 version (or close to that version) that worked just fine too.
oh, and i've found no issues running swype on GSB 2.2 or any other previous version. It sticks, and does good. the only issue that isn't a big deal is double tapping any word to change it (because of a bad swype) is testy as the new GB selection tool likes to auto apear "cut or copy" I have to select cut, in order to reswype in place of that selected word.
dan46n2 said:
FWIW, I've been running swype beta on GSB and on FroShedYo's, xtr's, etc.. and the only bug that I've found that's consistant (to me) is that after you reboot, you have to long-press a text field to change input method back to the regular keyboard and back to swype before it will work...Otherwise, it works great for me again until I reboot.
Click to expand...
Click to collapse
Thank you for that tip!! Mine had quit working but I tried that and now it works again. Awesome man
Thank you everyone for the help. I did a Google search and found what I was looking for...thanks again!
Sent from my ERIS GSBv2.1 using XDA App
Might just be operator error here, but I installed Swype yesterday and it worked just fine. Didn't alter build.prop or anything. I get the pop up keyboard, but when I try to actually type by swiping nothing comes up. the line appears like it's trying to trace out the word but no letters ever show up on my screen. Am I doing something wrong?
PS-The keyboard works fine if I tap the keys, so it installed successfully, it just won't let me trace out the words(which rather defeats the purpose of having it installed)
That is because while swype works on our nook colors, our nook colors do not have an androidID or IMEI, which is a unique number given to any device with a cell radio. That number is required to give swype its "swype" functionality.
well that's depressing. Is there no workaround as of yet?
Swype works just fine, no build.prop edits needed. Refer to this thread
http://forum.xda-developers.com/showthread.php?t=973010&highlight=swype
You do have to be rooted, follow the instructions in post 29 (step 1 not needed if already rooted). I was rooted with AutoNooter, and used Root Explorer to put the apk in the posted location.
As my original post said, I am rooted(using CM7) and did get it installed fine. It's the swyping function that isn't working. Is that working for you?
has anyone got it working on honeycomb?
nicbennett said:
As my original post said, I am rooted(using CM7) and did get it installed fine. It's the swyping function that isn't working. Is that working for you?
Click to expand...
Click to collapse
Yes, the swyping function works fine for me. Sorry, though, can't help you as far as CM7, I am stock autonootered.
fwiw, I just downloaded the SlideIT trial and it is B-E-A-Utiful. swype is way too much hassle when you can pay $6.50 and have the same features for no work.