I am running Serendipity VII and Hellraiser on my Infuse 4G. Love it!!!!
That said, I have tried a few ROMS and every one that runs 2.3.3 causes me major headaches trying to sync to my OWA server for work emails. It claims authentication failed which I KNOW is crap.
I used the mail client in 2.2.1 (Froyo) and everything worked perfectly. What gives?
For the interim I have downloaded and am using RoadSync, which is nice, but I would rather run the stock email as integration is better. Any ideas?
Related
So I downloaded KIK and I noticed that the notifications use Push, but they weren't working on my phone. I was running cog 2.3b2 // i reformatted and tried again and same thing. I posted up a question on their forum :
http://getsatisfaction.com/kik/topi...tm_medium=email&utm_source=reply_notification
It seems like others on the leaked Froyo are having the same problem. Is it possible that Push doesn't fully work correctly on our leaked build of Froyo?
I'm having the same problem as everyone else in that post. I'm on cog 2.2 beta 7. The wife is on 2.1 and has no problems.
All of my push problems seemed to be related to not having a unique Android_ID. You can fix it by installing a rooted 2.1 based ROM pulling the Android ID and writing it down then installing the Froyo ROM of choice and changing the ID with a Market app. There are details how to do this but I can't seem to locate them at the moment.
Here is the thread I think you were talking about: http://forum.xda-developers.com/showthread.php?t=810967
Yep that's it.
Since doing the fix I'm getting word feud notifications again.
Very cool, this fixed my Kik push notifications. Thanks!
No Problem.
So I just updated to 2.2 using the leaked Froyo non root method with my At&t Samsung captivate. Everything seems to work fine but my downloading speed is terribly slow in the marketplace, my youtubing and websurfing speed is still fast though. Anyone know what's up with this?
A lot of market related issues can be fixed by going in to:
Menu - Settings - Manage Applications - All
then scroll down to Market, select it, then clear cache/data.
i tried that but there wasn't any data/cache to clear it was just 0.0kb....I tried rebooting and I went back to 2.1 and the dling speed works fine. I then rooted and flashed di11i's 6.0 and everything worked but once again dling from android marketplace was super slow while web browsing, youtubing, etc. was fast....
I have noticed that with some of the roms the market does not adjust correctly the first few times you access it. I went to Cognition 3.04 and at first it took forever to load, now it works fine after a week or so.
a week huh? Hmm maybe I'll just give it time....I am liking the di11i's 6.0 with blue theme very much =P
kumo21 said:
So I just updated to 2.2 using the leaked Froyo non root method with my At&t Samsung captivate. Everything seems to work fine but my downloading speed is terribly slow in the marketplace, my youtubing and websurfing speed is still fast though. Anyone know what's up with this?
Click to expand...
Click to collapse
Do you have a generic Android ID? Some of the roms change your ID to the same everyone else has. Market throttles because it looks like 1000 downloads are all going to the same phone. Try Android ID Changer, if you have your original, and change it back. Or just change a few characters so your not on the same ID.
how would i find my Android ID? And how would I change it?
cappysw10 said:
Try Android ID Changer, if you have your original, and change it back. Or just change a few characters so your not on the same ID.
Click to expand...
Click to collapse
It will tell you your current ID and let you change.
Yeas I wish I had known about this android ID before flashing, I'm currently using the Odin 1.0 flashed 2.1.1's android ID, so just any characters and it'll be fine?
http://www.engadget.com/2011/05/12/netflix-releases-android-app-for-select-htc-phones-samsung-nexu/
And it works!
Edit: My current setup is a AMOLD dinc, running CM7 with 2.3.3. 16GB msd in to.
Download from market:
https://market.android.com/details?id=com.netflix.mediaclient
Netflix is apparently blocking unsupported devices when you try to login, I uploaded the apk to my xoom to test it and it did not let me login.
I have the app and have not yet been able to get it to load. I just get a black screen.
However, I noted that the details on the market page state it is official for the Incredible running 2.2, and I'm running CM7.
Has anyone else tried with CM7?
Assuming there are indeed compatibility issues, I'm hopeful the devs will find a way to make it work, because I'm not looking forward to going back to stock, but I need Netflix.
(Actually. Right now, I'm thinking about loading up one of the dual-boot options with some stock Froyo. This is worth the effort.)
Edit: The dual-boot option is awesome and all... But then, I tried again in CM7, and I found that I spent a few hours heavily tweaking my phone for nothing but the thrill; the app works, and I was watching Ong Bak 3 in seconds. Since I don't need a Sense rom, I undid the dual-boot configuration.
So. Works on CM7.
Just saw this. Not showing up for me in the market. I assume its a CM7 thing.
Maybe we can find locate an apk.
Sent from my DInc
Just installed! Going to test now! Biggest app missing since switching from iPhone 4!
Sent from my Nexus S using XDA App
Here's a market link.
http://market.android.com/details?id=com.netflix.mediaclient
I am up and running on CM7.0.0.
Sent from my DInc
Im running evervolv and it works fine for me
Sent from my DInc
no it works. i had to scroll down in the market a bit to find it. i was able to watch a movie also
apk please!
Can someone pull the apk please? I know it probably won't work, but I can't wait to try running it on my DX and Xoom!
Installed from the market, but all I get is a black screen for a long time, then an FC...
CM 7.0.3
Just tested and it does stream on CM7.
Works fine for me as well.
CM7.0.3
running CM 7.0.2.1 DINC, and program will shut off right after I try to log in
If somebody could post the APK, Thunderbolt folks would be grateful. I know it is blocking unsupported devices, but our devs want to take a crack at it. Thanks!
I am on CM Nightlies and it doesn't work. Considering a move to 7.0.0.3 just for netflix.
Works for me on CM and my DInc
Here's the apk
Working on my DX!!!
I'm streaming Law and Order right now!
Greatest.
Day.
Ever.
(until it stops working again like last time hopefully not)
Xoom trial coming soon.....!!
buya97 said:
running CM 7.0.2.1 DINC, and program will shut off right after I try to log in
Click to expand...
Click to collapse
Im getting the exact same thing on latest CM7 nightly
Running stock (rooted) 2.2 and mine force closes immediately after trying to launch the app. Somebody mentioned something about Flash 10.3 so I updated and still get force close. Any ideas?
Not sure if this info helps, but it works fine on mine:
CyanogenMod-7-04172011-NIGHTLY-Inc
[email protected] #1
Sorry, I'm not sure how that converts to the actual nightly number, but its what I was able to gleen out of the Rom Manager.
Recently upgraded my DINC to ICS using Abduction v1.81 and I'm having a problem with Chrome Beta. When I launch it initially everything seems fine, it asks for log-in info which is provided and then shows the tab and search icons. When actually entering a web address, though, the entire page is blank. It would seem that it is going to the address but nothing ever shows, regardless of what website is chosen.
I have searched the Abduction forum to no avail, no one else seems to be having this problem after the AOKP Build 26 update, or at least hasn't spoken of it. Possibly an HWA problem?
HTC Incredible
Abduction ICS v1.81
V6 SuperCharger (tried Chrome before/after running scripts...same issue)
Holo-mod
No other mods to speak of really. Any ideas would be appreciated.
chrome beta
i have had the same problem on my nexus s 4g running 4.0.4 and it would only open up and it would be blank and foreclose shortly after i noticed that it is a rom problem because i just flashed a new rom and chrome has been working great maybe do a back up and try a new rom see if that helps!
Hi all, Updated to CM10.1 AOSP 4.2.1 Jellybean on my HTC Sensation. All works excellently other than I can no longer connect to Exchange, getting the "this server requires security features that your android..." error. I've Google it and looked on this forum but can't seem to find any definitive answer. My Sensation is running the above ROM, rooted, and, Android 4.2.2 and the Exchange server is 2003. Firmware is 3.3 which I had to update prior to this ROM. Nothing has been changed on the Exchange server and indeed until I flashed this new rom it sync'd no problem. My previous rom was on ICS and I though I had heard that there were problems with ICS and active sync but can't find any details on it.
I tried this hack too http://forum.xda-developers.com/showthread.php?t=1117452 but it doesn't seem to make any difference. Interestingly enough, when I look at exchange via OWA and remove all mobile devices and then try to connect the phone again it shows up.
Is this problem because CM10.1 AOSP doesn't support EAS?
Thanks for any help.
Derf66 said:
Hi all, Updated to CM10.1 AOSP 4.2.1 Jellybean on my HTC Sensation. All works excellently other than I can no longer connect to Exchange, getting the "this server requires security features that your android..." error. I've Google it and looked on this forum but can't seem to find any definitive answer. My Sensation is running the above ROM, rooted, and, Android 4.2.2 and the Exchange server is 2003. Firmware is 3.3 which I had to update prior to this ROM. Nothing has been changed on the Exchange server and indeed until I flashed this new rom it sync'd no problem. My previous rom was on ICS and I though I had heard that there were problems with ICS and active sync but can't find any details on it.
I tried this hack too http://forum.xda-developers.com/showthread.php?t=1117452 but it doesn't seem to make any difference. Interestingly enough, when I look at exchange via OWA and remove all mobile devices and then try to connect the phone again it shows up.
Is this problem because CM10.1 AOSP doesn't support EAS?
Thanks for any help.
Click to expand...
Click to collapse
I am not any help, but I see the exact same issue with my EVO LTE on CM10.1. Shows up in the OWA devices log and everything. I have googled the heck out of it to no avail. I am able to gain access using the Touchdown app, but that is not a very good solution (and it costs $20 when the stock app is perfectly fine). I have not tried the custom apps that remove security like the one you link to. I do not mind the security features as much as I just want to connect to my work email. My company has an "iPhone only" policy, but If I revert back to a 4.1 ROM, I am able to connect. As far as I know, there is no way to restrict the type of device from the server side; it just checks to see if the correct sercurity is in place.