Related
Here I provide a half legal (I included the HTC drivers for the hardware...) stock AOSP (android-1.5_r3) ROM!
You can add Google Apps legally if you have bought a Google experienced phone by running this script on a linux-machine:
http://forum.xda-developers.com/showthread.php?t=564744
Features:
-No special features
-Just stock w/o Google apps
Download for G1:
http://www.4shared.com/file/135524283/e812c64f/dream.html
Instructions:
Unzip the file, then:
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
To Do:
I'm a lazy guy.
Next release will be cyanogenmod w/o googleapps.
Well does the rom working without all googles stuffs ?
Can we add them easily ?
Thanks for the new build, hope this googles' issue will be fine
It does work, but it's nearly useless.
I work on a windows version of my script which adds google apps legally.
I also will create a script for recovery.
I'll work on this ROM when I'm done with these, as soon as the scripts are ready, this ROM will get some goodies from Cyan.
Nice work Maxisma!
Its a good start
awesome bro
keep it up it's a start!
maxisma said:
It does work, but it's nearly useless.
I work on a windows version of my script which adds google apps legally.
I also will create a script for recovery.
I'll work on this ROM when I'm done with these, as soon as the scripts are ready, this ROM will get some goodies from Cyan.
Click to expand...
Click to collapse
Excellent.
With all this doom and gloom.
Surely this is the problem solved?
But what do you mean by google experience?
I know I got all the apps with my phone... T-Mobile G1...
Google Experience are all phones with Google Apps preinstalled.
Just some indian and russian HTC devices don't have it.
Out of interest would this boot fine without running the script?
I am presuming not, but i am just curious?
I would try it out, but at the moment I am not at home and only have 2g coverage on my phone so its a bit slow to download
Edit //
Could i (in theroy) install, boot and then use wget to download sam3 from slideme.org and then download a third party dialer / K9 etc... etc..
So use all third party apps
vixsandlee said:
Out of interest would this boot fine without running the script?
I am presuming not, but i am just curious?
I would try it out, but at the moment I am not at home and only have 2g coverage on my phone so its a bit slow to download
Click to expand...
Click to collapse
It boot's fine w/o the script ;-)
Not to rain on your parade, but ....
Hi Maxisma,
Not to rain on the parade, but ...
Per Google, this ROM is no more "legal" than any other ...
The following is taken from http://source.android.com/documentation/building-for-dream
* The Dream device software contains some proprietary binaries. For contractual reasons, these cannot be redistributed separately from the shipping hardware, but the provided script may be used to extract these binaries from your development device so that they can be correctly included in your build. These libraries include the openGL|ES library, the Qualcomm camera library, the HTC Radio Interface Library, etc. You need adb to be in your path, and you need your device to be configured for adb access. If you don't have adb already, do a generic build first, which will put it in your path.
Click to expand...
Click to collapse
Just my understanding of things.
~enom~
Interesting, i am going to have to have a look and a play later.
Cheers for the work (forgot to say that in my first post)
if you're interested on maybe trying to do this on your own:
http://www.johandekoning.nl/index.php/2009/06/07/building-android-15-build-environment/
Contrary to what you might think, a room w/o google apps is not entirely useless. Probably the major setbacks are the lack of market access, the lack of a YouTube player (we need to work on a port of Totem's Youtube implementation but for android), and a way to manage contacts (irrenhaus is looking at the posibility of setting up a Google Contacts sync), plus we'd probably need to write an utility to actually read/write contacts to and from SIM.
G-mail, you can acess from the browser (which, AFAIK, is still free and open source under the Apache Licence), Maps can be downloaded once we get Market access.
Other than that, a bone-stock android build will keep you connected to the internet, allow you to tether, allow you to run scripts, deliver your mms, give you camera and music player, have theme support, and ofcourse, make phone calls just like any other build will. You'll just have to go a bit off of your way to get apps, but again, that's the main drive here, either get acess to market of create a new one and invite app developers to submit their apps there too
enomther said:
Hi Maxisma,
Not to rain on the parade, but ...
Per Google, this ROM is no more "legal" than any other ...
The following is taken from http://source.android.com/documentation/building-for-dream
Just my understanding of things.
~enom~
Click to expand...
Click to collapse
That's dead on too, and I forgot about it. The issue would not be with google anymore though, but with HTC and it's hardware partners. This is what cyanogen realized, now that the spotlight is on rom development, companies will have watchdogs for re-distribution of binary code. If you own an ADP device, you can legally download the binaries from the HTC website and MAKE YOUR OWN BUILD (so redistribution targeting dream is out, unless we can talk to HTC about it), either that, or, as I've said before, move onto an open hardware platform so we can write our own drivers.
---edit---
By the way, I still don't agree with the whole feeling of gloom floating around here. This is only a change to the way we're doing things right now, but it doesn't hinder development in any way. If you're the kind of dev that's here for the praise, then yeah, you wont like it that now people will have to actually know what they're doing, so your fanbase will be reduced. I for one welcome the change. This rom, for example, can still be distributed without the HTC binaries and maybe have instructions for the user to download them, install them in their OTA package, and the actually flash the rom. But then that requires that people actually know what they're doing, since we can't legally provide them the finished product.
Also, it doesn't hinder improvement of the platform. None, I repeat, NONE of cyanogen's or other dev's work ever even touched the proprietary parts of the build, as this is nearly impossible without the source (I know, baksmali, but really, I'm trying to make a point here!...) and most of what made his work awesome was the behind-the-userland work; kernel's bfs patches, scripting, cpu time management, modifications to available source, for example, the settings package.
We can still improve the platform, we can contribute, and maybe this time around the way Google wanted people to, by submitting code for their consideration to have it maybe implemented in android's next build.
I'll be glad to see all the "OMG, MY PHONE WONT START" threads diminish as people realize that this will no longer be the place where you get it all dumbed down and easy to use.
hey just by simple curiosity, how do you then log into the phone, if this rom is google less? I presume you still need a google account to set up your machine right????
kmassada said:
hey just by simple curiosity, how do you then log into the phone, if this rom is google less? I presume you still need a google account to set up your machine right????
Click to expand...
Click to collapse
You don't need to login as there is no setupwizard.
jubeh said:
That's dead on too, and I forgot about it. The issue would not be with google anymore though, but with HTC and it's hardware partners. This is what cyanogen realized, now that the spotlight is on rom development, companies will have watchdogs for re-distribution of binary code. If you own an ADP device, you can legally download the binaries from the HTC website and MAKE YOUR OWN BUILD (so redistribution targeting dream is out, unless we can talk to HTC about it), either that, or, as I've said before, move onto an open hardware platform so we can write our own drivers.
---edit---
By the way, I still don't agree with the whole feeling of gloom floating around here. This is only a change to the way we're doing things right now, but it doesn't hinder development in any way. If you're the kind of dev that's here for the praise, then yeah, you wont like it that now people will have to actually know what they're doing, so your fanbase will be reduced. I for one welcome the change. This rom, for example, can still be distributed without the HTC binaries and maybe have instructions for the user to download them, install them in their OTA package, and the actually flash the rom. But then that requires that people actually know what they're doing, since we can't legally provide them the finished product.
Also, it doesn't hinder improvement of the platform. None, I repeat, NONE of cyanogen's or other dev's work ever even touched the proprietary parts of the build, as this is nearly impossible without the source (I know, baksmali, but really, I'm trying to make a point here!...) and most of what made his work awesome was the behind-the-userland work; kernel's bfs patches, scripting, cpu time management, modifications to available source, for example, the settings package.
We can still improve the platform, we can contribute, and maybe this time around the way Google wanted people to, by submitting code for their consideration to have it maybe implemented in android's next build.
I'll be glad to see all the "OMG, MY PHONE WONT START" threads diminish as people realize that this will no longer be the place where you get it all dumbed down and easy to use.
Click to expand...
Click to collapse
I could probably write a Java application that would allow the user to:
1) hook their google phone up over USB and grab the existing google apps off of it
2) point to the location of their proprietary drivers on a manufacturers website for download
3) point to a central location of legal ROMS for download
4) click an ASSEMBLE button to put it all together. The resulting update file would be like they have always been, but no illegal redistribution has taken place.
One little problem ...
Ohsaka said:
I could probably write a Java application that would allow the user to:
1) hook their google phone up over USB and grab the existing google apps off of it
2) point to the location of their proprietary drivers on a manufacturers website for download
3) point to a central location of legal ROMS for download
4) click an ASSEMBLE button to put it all together. The resulting update file would be like they have always been, but no illegal redistribution has taken place.
Click to expand...
Click to collapse
Hi Ohsaka,
One little problem with that is ... the manufacturers do not post the drivers (standalone) on their websites for download, they only redist with the hardware. Also, there are other library files as well, it's not only drivers.
~enom~
Simple fix.. just don't include it. People will have to "magically" find the drivers on their own.
If it boots, why is it nearly useless?
So I am brand new to Android and like it so far. I have a Vodafone HTC magic 32b. But really miss Exchange native support.
So my question is can anyone point me to ROMS that have Native Exchange support. I hear Android 2 can do this and like the sound of that. But also I hear that some 1.6 one will do it.
Please remember that I am new to android and I have found the HTC_Sapphire_Hacking site. I have flashed plenty of windows mobile in my time (those days are gladly gone now) but not done android.
Thanks
Just download dwang's rom (check my signature) or Cyanogenmod (any version) and extract the Mail.apk from it, and install on your phone.
You can extract it just by going into the zip file and having a look around, can't remember the exact location but it was easy to find.
To install the apk either use "adb" from the android SDK (adb install mail.apk) or copy it to your sd card and install it using Astro.
Hope this helps.
PS. you are better off posting in sappire general for this as your questions are not related to rom development.
Thanks for that
Great answer and will open up a new thread in the the apropriate thread as I get an error saying
--------------------------------
Application not installed
Work email could not be installed on this phone
---------------------------------
I guess i may need to flash yet
Thanks again
Need FULL Exchange support (Mail, Contacts, and Calendar) ?
If you need REAL Exchange support (not just email), you really need an HTC (not GOOGLE) branded ROM. Nearly every HERO ROM fits this criteria, but the following link provides a non-Hero ROM (EVERYTHING works, and it's FAST because it's meant for the sapphire). I've used it on two 32B Sapphires now for a couple months is it's the best ROM I can find that provides full exchanges support. Aside from not having SenseUI, I can't see any reason to run another ROM yet either. If Eclair/2.0 get perfected, that would be a reason to move because it appears to have native Exchange support built in (whereas the HTC ROMs have the support because HTC added it, not Google). I did a LOT of research to come to this conclusion.
http://forum.xda-developers.com/showthread.php?t=555499&highlight=%2Arogers%2A
Now that sounds like my answer, will do this tonight.
Thanks rainabba
One more question guys?
I am all ready to go but need advice on the "wipe device" option on the recovery rom.
There are half a dozen options. Which should i choose?
Thanks
rainabba said:
If you need REAL Exchange support (not just email), you really need an HTC (not GOOGLE) branded ROM. Nearly every HERO ROM fits this criteria, but the following link provides a non-Hero ROM (EVERYTHING works, and it's FAST because it's meant for the sapphire). I've used it on two 32B Sapphires now for a couple months is it's the best ROM I can find that provides full exchanges support. Aside from not having SenseUI, I can't see any reason to run another ROM yet either. If Eclair/2.0 get perfected, that would be a reason to move because it appears to have native Exchange support built in (whereas the HTC ROMs have the support because HTC added it, not Google). I did a LOT of research to come to this conclusion.
http://forum.xda-developers.com/showthread.php?t=555499&highlight=%2Arogers%2A
Click to expand...
Click to collapse
This was exactly the information I was looking for. Not what I was hoping to hear, but what I was looking for.
I rooted and installed Cyanogen on my previously virgin Rogers Magic 32A, and was a little disappointed to see Exchange Calendar sync gone along with the other HTC trims.
Don't get me wrong - Cyanogen is awesome, but I'm really looking forward to a fully working Eclair ROM now... I think the ROM you link to is 1 step forward, 2 steps back.
coreyinoz
coreyinoz said:
This was exactly the information I was looking for. Not what I was hoping to hear, but what I was looking for.
I rooted and installed Cyanogen on my previously virgin Rogers Magic 32A, and was a little disappointed to see Exchange Calendar sync gone along with the other HTC trims.
Don't get me wrong - Cyanogen is awesome, but I'm really looking forward to a fully working Eclair ROM now... I think the ROM you link to is 1 step forward, 2 steps back.
coreyinoz
Click to expand...
Click to collapse
Yep, I couldn't give up all the Cyanogen goodness just because of lameExchange.
Best scenario I have come to love:
-Keep Cyanogen w/ Work Email
-Run Google Calendar Synch 2-way on the Corpo Laptop
-Export Outlook Contacts to Gmail (include frequent Co. Directory contacts)
I just keep working right along; emailing, scheduling, contacting without a hiccup (meetings pop-up, no duplicate contact bs, etc).
Exchange support
The options (I've used all three of them)...
1). Buy an app from the market that offers Exchange support (Roadsync is only US$10, works fine... safest option, as it doesn't involve flashing a ROM).
2). Get a custom rom that supports it. The 2 general types that I've used include Hero ROMs and ROMs based upon the Rogers phones. Hero is too slow for me, however, and the Rogers ROMs don't even have Donut yet.
3). Get an Eclair ROM. I'm currently using Eugene's AOSP, and while there are some issues (no camera, sync loop), the Exchange support is pretty nice. It's not completely clear to me, but I think the Exchange calendar suppport comes from a Moto app that was sucked off the Droid. Eclair offers calendar and mail sync with Exchange natively.
You can choose which one works best for you. For the longest time, I was running cyanogen with Roadsync, and had no problems whatsoever.
@hackitall and @jstegeman
Good posts both. Thanks for that.
I think for me I like hackitall's kluge... at least until a more stable Eclair ROM is out. It doesn't have to be cyanogen, but at least stable with all of the "normal" features like camera, etc.
At the breakneck development pace, I'd expect this sooner than later. Happy times.
coreyinoz
hackitall said:
Yep, I couldn't give up all the Cyanogen goodness just because of lameExchange.
Best scenario I have come to love:
-Keep Cyanogen w/ Work Email
-Run Google Calendar Synch 2-way on the Corpo Laptop
-Export Outlook Contacts to Gmail (include frequent Co. Directory contacts)
I just keep working right along; emailing, scheduling, contacting without a hiccup (meetings pop-up, no duplicate contact bs, etc).
Click to expand...
Click to collapse
Not to take anything from the great Cyanogen, but what "goodness" is lost with the Rogers ROM (or do you even know)?
BTW, your solution is beyond a PITA. I know because I tried it and a number of other "solutions" before realizing that it was all a waste of time for someone like myself that needs REAL syncing (not exporting contacts for example). Also, if you're willing to pay for a Google corp account, might as well save the hassle and buy a license for cemaphore. It does all the syncing w/o any of the BS.
rainabba said:
Not to take anything from the great Cyanogen, but what "goodness" is lost with the Rogers ROM (or do you even know)?
Click to expand...
Click to collapse
Two words: Google Navigation
It's totally awesome and requires 1.6... at least I haven't seen anyone supporting it on 1.5 yet.
Ahh
Ok, i guess if I wasn't already running 2.0 on a droid, didn't have such a need for Exchange support, and/or didn't already have nDrive or my Alpine Navi unit, that would make sense
Well seing as I asked the question I thought I would say thanks for all the great help and advice.
I have ended up with roadsync on the origional rom.
I did try every rom out there 2 buggy, HERO Sssllllllooooowwwwww built in exchange support on 1.6 did not work with exchange at work (not enough security)
Great fun
I've been browsing the other device forums and seeing some success with modifying the ICS gmail for use on devices that don't yet have ICS running. Is this possible for the MT4GS? The new Gmail app in ICS is a huge improvement. Same with the Google Calendar. The new Google music isn't linked to ICS so we have that. Wondering if there is a way to get some of the other Google goodness til we have full ICS. Anyone working on this for our phone or know anything related?
Doubt it but it would be awesome. At least to be able to take the GMAIL app its a definitely must, but I can wait for now.
_atlien_ said:
I've been browsing the other device forums and seeing some success with modifying the ICS gmail for use on devices that don't yet have ICS running. Is this possible for the MT4GS? The new Gmail app in ICS is a huge improvement. Same with the Google Calendar. The new Google music isn't linked to ICS so we have that. Wondering if there is a way to get some of the other Google goodness til we have full ICS. Anyone working on this for our phone or know anything related?
Click to expand...
Click to collapse
Absolutely it's possible.
The only issue is how much work has to be done to make it compatible - on that score some people would say it isn't, because they don't/can't do the work necessary to make it happen.
I haven't had the time to look closely enough at the ICS stuff to tell ya for sure, but even if it came down to basically re-writing the whole app to include the new changes in a gingerbread installation it would work.
(I did download ICS source from google a bit ago, but haven't had time to comb through it much at all)
Anything using stuff like Face Recognition or any of the new technologies would most likely be off limits without re-writes to other parts of your ROM.
It's nowhere near drag-and-drop if that's what you're asking, but the right attitude and investment of time can get it all worked out.
Thanks for the replies! I'm only a beginner developer (thx to your tutorials actually Blue6IX) so I'm looking into it to see how things work and just poke around. My goal is stability. I LOVE the work that has been done on ICS but it still doesn't run too many different apps that I (and presumably others) have already bought on the market while GB runs them all flawlessly of course. Seems like it might at this point be easier to make google apps run on GB than make an assortment of apps from different developers run on ICS.
Sent from my HTC myTouch_4G_Slide using Tapatalk
_atlien_ said:
Thanks for the replies! I'm only a beginner developer (thx to your tutorials actually Blue6IX) so I'm looking into it to see how things work and just poke around. My goal is stability. I LOVE the work that has been done on ICS but it still doesn't run too many different apps that I (and presumably others) have already bought on the market while GB runs them all flawlessly of course. Seems like it might at this point be easier to make google apps run on GB than make an assortment of apps from different developers run on ICS.
Sent from my HTC myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
That would be pretty awesome.
I've been wrapping up all the stock apps we have from the 1.28.531.9 and 1.55.531.3 update for our phone, and turning them into flashable zips.
What you might want to keep in mind for after the app is compiled and working (right - easier said then done) is to download a couple of said zips to see how I did it - then you could just use them as a template for the new ICS apps you make. I also have a tutorial on edify scripting and a thread with a whole mess of scripting tips in it, so I can link them later if you want.
Get yourself a linux install if you don't already have it and download the ICS source code, then start the trail and error of compiling the apps to work. I'd start with something simple you can compare with, like maybe:
Stock ICS calculator, and compare it to the stock Gingerbread calculator. I'll be posting the stock gingerbread calc in a flashable zip within the next few hours as I get more of the zips I already made linked to the thread.
If you can make the calc work, then you have a winner, and an easy step on the learning process of making it happen, then the rest of the ICS apps from source become easier.
Just a thought
I'll help when I can, but i've got a lot on my plate - I think this is a great project for someone to tackle though!
Hi Folks
Feeling too happy to report that even GB users can get a glimpse of what Hangout 2.0 performs on android 4.4 KITKAT!!
First of all let me announce the device I've tested it on. Mine is a Dell Streak running GB 2.3.3 Traveller's DSC ROM.
How I did it:
1. I have my phone rooted
2. Renamed existing hangout apk so that if in case i need a backup. Mine was in /data/app folder
3. Moved and renamed attached hangouts 2 apk as "com.google.android.talk-2.apk" (without quotes) - don't know if this a useless step?
4. changed permission of the renamed apk to rw-r--r--
5. Cleared dalvik cache
6. Opened the app and enabled SMS on the prompt and allowed it to collect all existing SMS messages
7. Voila! everythings works so far.
Features:
1. SMS integration
2. More fluid (in my opinion)
3. Online/offline notifier
4. Still exploring the differences
5. Will check if this can be integrated into the ROM itself or not by getting rid of MMS.apk
Need your feedbacks and press thanks if it works for you too. :victory:
Link: here u go! My dropbox shared URL
Came to know that video chat in hangout wasn't working with only the steps above. to fix
1. Download the libvideochat_jni.so
2. Move to system/lib
3. Change permission to rw-r--r--
4. Try video calling. Should work now!
5. Let me know
*NEW ADDITION*
HOLO themed black version (via- makers of Ultima ROM) of the same 2.0.012 version here
IMP: Please do NOT update hangout or else you will lose SMS functionality.
Successful, tha nks
This worked just fine on my Samsung Proclaim with 2.3.4. I had just been trying to sideload the new 2.0 yesterday, and it wouldn't work and I was afraid I might be getting screwed here in the near future. I use google voice extensively, and with the recent announcement that google would be dropping xmpp support for voice, I can tell that it a sign of much greater hangouts/talk integration and I'm a little concerned that my numerous pieces of older hardware are going to be left out in the dust. So, I had tried to sideload the new one yesterday, and it wouldn't work, but following your prescribed steps, it's working just fine now.
ammujee said:
3. Moved and renamed attached hangouts 2 apk as "com.google.android.talk-2.apk" (without quotes) - don't know if this a useless step?
Click to expand...
Click to collapse
This step shouldn't be necessary if embedding it in /system. Hangouts.apk works just as well. Like I mentioned in my ROM thread, I'll have to try this out. If I like the change, then I'll update Traveller DSC.
Have you attempted this with any of the other KitKat apps?
Works for me by just installing it and not pushing it as a system app. Android 2.3.7
Sent From My Phone?
Strephon Alkhalikoi said:
Have you attempted this with any of the other KitKat apps?
Click to expand...
Click to collapse
Yes, I did with few more like launcher, email but no luck. It gives parsing error.
Sent from my Dell Streak using Tapatalk 2
NRG001 said:
Works for me by just installing it and not pushing it as a system app. Android 2.3.7
Sent From My Phone?
Click to expand...
Click to collapse
How about video calling? Does it work without pushing the .lib file?
Sent from my Dell Streak using Tapatalk 2
What about the gallery app? Does it give you the parsing error?
Yes, gallery also gives parsing error.
Sent from my Dell Streak using Tapatalk 2
ammujee said:
How about video calling? Does it work without pushing the .lib file?
Sent from my Dell Streak using Tapatalk 2
Click to expand...
Click to collapse
I don't know i just install it because it can be used now as sms app. And no one i know uses hangouts sadly they use other messaging app like wechat etc.
Sent From My Phone?
If you don't have to add that file, you might want to check to see if your ROM already includes it.
On a side note, the KitKat version of Hangouts is apparently available on the Play Store, but only for ICS and up.
Strephon Alkhalikoi said:
If you don't have to add that file, you might want to check to see if your ROM already includes it.
On a side note, the KitKat version of Hangouts is apparently available on the Play Store, but only for ICS and up.
Click to expand...
Click to collapse
The newest one released yesterday will install on Gingerbread phones. However, SMS has been removed for folks below 4.0. The previous version pulled from the Nexus 5 did put Hangouts SMS on Gingerbread.
One thing the portal article doesn't mention is that Google does version checking on its files. If the API version isn't sufficient what is downloaded is an older version that would work at the given API version. Case in point is Gmail. The current version is 4.6, as my ICS tablet will attest. However on a Gingerbread device, a freshly delivered version from the Play Store will be version 2.3.6.
In the case of Hangouts, the version being downloaded to Gingerbread devices is version 1.1 build 12 or something similar. Only ICS and up will get Hangouts 2.0. So to summarize, it's not that certain features are being disabled (as this thread can attest to) it's that Google is sending an older version of the app to the device.
Strephon Alkhalikoi said:
One thing the portal article doesn't mention is that Google does version checking on its files. If the API version isn't sufficient what is downloaded is an older version that would work at the given API version. Case in point is Gmail. The current version is 4.6, as my ICS tablet will attest. However on a Gingerbread device, a freshly delivered version from the Play Store will be version 2.3.6.
In the case of Hangouts, the version being downloaded to Gingerbread devices is version 1.1 build 12 or something similar. Only ICS and up will get Hangouts 2.0. So to summarize, it's not that certain features are being disabled (as this thread can attest to) it's that Google is sending an older version of the app to the device.
Click to expand...
Click to collapse
It's kind of silly really, since the 2.0 version works fine on my Gingerbread ROM. Sending texts, receiving texts, pictures, video etc. Even the holo style settings menus work. Nothing appears badly broken, but from time to time it might force close.
The API support is within the APK, because otherwise it wouldn't allow you to install it. So if google strip that away then they're doing it simply to get people to update to a newer version of Android.
The file here is 2.0.012 (884159-30). The version Play Store will install is 1.2.018 (849105-30).
In one respect it isn't all that silly. Gingerbread is a few years old now and Google wants to focus on Android 4.x. I actually can understand that. What I would like to see, but never will, is Dell going back and making a KitKat ROM for the Streak, especially knowing KitKat will work on the Streak.
I can understand that they'd like people to upgrade, but blocking a feature for no good reason is silly. The 2.0 version clearly works. Yes theres the force close that happens 2% of the time, but that's going to be a bug in the code and not an API issue, because if it were API related it wouldn't even run or it'd force close every single time.
Of course I'm due for an upgrade anyway, and I probably will soon, but it still would of been nice to see google officially support the 2.0 version on Gingerbread.
Hey it works bt always show the number.... I mean showing the number insted showing the name which I save in my phone or sim card
Sent from my MT11i using xda premium
Yes, that is a known issue even for Nexus 5 owners. An application bug probably to be fixed in next few versions. For now few people have found changing their contacts to international format helpful (like for Indian nos changing it from 022xxxxxxxx to +9122xxxxxxxx). It didn't work for many but there is no harm in trying for now. Do make sure to force sync contacts and then switch off your phone and switch back on.
Let us know if it helps!
Sent from my Dell Streak using Tapatalk 2
Hey man, can you see if the latest Hangouts update with messaging will work on Gingerbread? I'm certain it won't, but maybe you can give it a shot again.
I checked all later versions but those don't work with SMS support. May be @theos0o can help us by enabling SMS support for all devices as he did for FB messenger.
Sent from my Dell Streak using Tapatalk 2
Thanks for at least checking. I'm sure many of us appreciate it.
Does tap and pay work for this phone with CM11? Is there anything special I need to do to make it work?
I've installed google wallet successfully, enabled tap and pay in settings, but I've tried tapping at several stores and nothing seems to happen, both from the lock screen and after unlocking and opening the wallet app (not sure if that's necessary, but tried it anyway).
I did some searches and read stuff about hacked versions of google wallet and other workarounds (like forum.xda-developers.com/showthread.php?t=2280943 ) but it seems these apply to older android versions only.
I don't think Google Wallet was ever officially supported on the Q. Like you said, some people hacked it up and I think a few made it work... but not many. Doesn't seem to be worth the effort.
arrrghhh said:
I don't think Google Wallet was ever officially supported on the Q. Like you said, some people hacked it up and I think a few made it work... but not many. Doesn't seem to be worth the effort.
Click to expand...
Click to collapse
Someone with a similar username to you is one of the few that made it work last year (from that other thread):
Aaargh! said:
I made an in store purchase today and it worked perfect. Pretty cool technology
Click to expand...
Click to collapse
However that thread seems to be for CM10.1/Jellybean not CM11/Kitkat so was hoping for something more recent before I start just trying things I don't fully understand.
After much more reading and questiong etc I think I figured this out and thought I'd post the details incase anyone else is interested:
#1 - Google stopped supporting tap&pay for anything earlier than KitKat summer 2014. So the older versions/hacks won't work anymore even if running older android version, etc.
#2 - There are several NFC chips, our phone uses NXP PN544 - same as Droid Razr any many other brands. There are no open source drivers for this chip, so AOSP, which CM is based on, doesn't have these drivers. Other NFC chips, like Broadcom BCM20793, do have open source drivers and they are included in AOSP, so phones with those do work for tap & pay with CM11. It also seems there is a newer NXP chip in some new phones, PN547, which may possibly work with recent AOSP 4.4.3 but I didn't keep reading about those details.
#3 - People have been trying to get NXP to release open source drivers for PN544 to AOSP, as well as trying to reverse engineer closed-source drivers from factory roms that support it natively, as well as looking at possible compatibility with PN547 drivers, but no success in any case yet. The following thread tracks that effort: http://forum.xda-developers.com/showthread.php?t=2573842
Conclusion - No way to make it work with our phone at this time. Perhaps in the future if NXP releases open source drivers or someone brilliant hacks something out.