Here's a question for all you ICS testers: NFC working?
I think this Q&A section is redundant - seems like general section would be fine for questions. Just my opinion/suggestion.
newowner said:
Here's a question for all you ICS testers: NFC working?
I think this Q&A section is redundant - seems like general section would be fine for questions. Just my opinion/suggestion.
Click to expand...
Click to collapse
No, NFC is not working as it the Razr does not have an NFC chip. Which is required for NFC to work.
I read that there is a NFC chip, but the motorola, not handed to google the drivers included in the ICS ...
3dgard said:
I read that there is a NFC chip, but the motorola, not handed to google the drivers included in the ICS ...
Click to expand...
Click to collapse
I think that you're mistaken, here are two different sources claiming the Razr doesn't have an NFC chip.
One
Two
http://mediacenter.motorola.com/New...-Executive-Q-A-with-Dave-Rothschild-3933.aspx
What are the benefits of upgrading a device to Ice Cream Sandwich?
Ice Cream Sandwich brings an entirely new look and feel to Android. It has a redesigned user interface with improved multi-tasking, notifications, Wi-Fi hotspot, NFC support and a full web browsing experience. With Ice Cream Sandwich, Android has been rethought and redesigned to be simple, beautiful and useful. Ice Cream Sandwich introduces innovations such as Face Unlock to unlock your phone, a Data Manager to control your network data usage, and advanced multimedia and imaging features. Ice Cream Sandwich also provides developers with new APIs, unified U.I for phones and Tablets, and improved performance by enabling developers to leverage hardware graphic acceleration.
-All About Ice Cream Sandwich (Android 4.0): Executive Q&A with Dave Rothschild
*** What is the NFC support?
By NFC support, they mean just on the software end. Android as a platform could not interact with NFC prior to ICS, even if the device had an NFC chip. However, regardless of Android's software support, the Razr twins do not have the hardware to utilize it.
i'm inclined to agree with you, except the whole article is about the razr/max not other moto phones.
i seem to recall another press release saying the same thing.
it's really misleading on motorola's part, if there is no nfc support besides just android o/s with no functionality.
I think it's more just a disconnect between them talking about putting ICS on the Razr and them actually discussing what ICS is, but it is deceiving in a way.
newowner said:
i'm inclined to agree with you, except the whole article is about the razr/max not other moto phones.
i seem to recall another press release saying the same thing.
it's really misleading on motorola's part, if there is no nfc support besides just android o/s with no functionality.
Click to expand...
Click to collapse
As i know the razr not have the nfc chip. BUT! I use offical 2.3.6 android on my razr. Only rooted, without any mod, or tweak. Only root.
If i want to share something... i can select the nfc tagging option. I dont know why an how. But there is nfc option. (If i select it, its force closeing, so didnt work. But as i write, it is the latest offical rom.
Screenshot attached. (If its matter, i use quickpick)
https://www.box.com/shared/0c6d9eb53d202e8730a4
Related
i tink that LG was waiting for cooking a stock rom based on android 2.4 (instead of the 2.3 promised) because of their similarities, in fact the gpu accelerations for 2D, rumored for the 2.4, can only help our P500 performance.
i hope this, and you?
Ps: i tink that a P500 at 150$ with 2.4 in the very next month can bring android for many doubtful people..
I'm not really keeping my hopes up. I bet the last official update we'll receive is Gingerbread. Most companies focus on their flagship phones, and despite the O1's popularity, I don't think it'll receive much.
Also, IMHO, Google is going too fast. Manufacturers are having a hard time catching up and stuff.
But if you ask me, I'm contented with Froyo. Unless, of course, there's a really badass killer feature available only to future releases.
And I think this should be in the General category
kpbotbot- It's more like manufacturers use the differente Android os'es for marketing uses . Look at samsung , they're waiting to release the native 2.3 devices and bearly then will they release gingerbread for their current flagship : Galaxy S . It's a dirty world .
Yeah. Here's a super thank-able screenshot I took weeks ago
LG and Samsung seem like very different companies. The Optimus line is a very good buy for most carriers. It will convert a lot of users to the Android world like me. LG seems to catter to their users too.
The manufacturers should understand Android devices should follow Googles releases. It seems like most manufacturers just barely make the software and communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Sent from my VM670 using XDA App
why would companies spend money and time in the software when
communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Click to expand...
Click to collapse
@orlox - Imagine buying a phone that doesn't come with an operating system.
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
ccdreadcc said:
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
Click to expand...
Click to collapse
I like the idea!
Post delivered via piece of paper tied to a brick... sorry 'bout the window! XD
The reason I chose this phone is because, for me, it's a small portable computer. If only every bit of hardware of this phone had a corresponding device driver (that we can get hold of), I think there's nothing stopping us from using a full Linux desktop, or other operating systems capable of running on the ARM architecture.
Not so relevant note: Some say the bootloader is locked. True?
kpbotbot said:
The reason I chose this phone is because, for me, it's a small portable computer.
Click to expand...
Click to collapse
So true!
I am very satisfied with my first Android experience, in spite of all the bugs and hardware limitations of this cheap phone. Almost anything I needed but couldn't do before on my "dumb" phone became possible with this micro computer. So I don't really care if it's running Eclair, Froyo, Gingerbread, Ice Cream or Milk & Toast & Honey.
You would care if it was running Cupcake.
P.S There really is a possibility for us to get 2.4 on our phones. It is still called Gingerbread but it will support Honeycomb apps.
Sent from my LG-P500 using XDA App
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
kpbotbot said:
Yeah. Here's a super thank-able screenshot I took weeks ago
Click to expand...
Click to collapse
This makes perfect sense from the carrier's perspective. If people had to pay to upgrade to the next version the carriers might have more incentive; as it is now they aren't seeing any more money so why bother investing time on something that could blow up in their face.
andy572 said:
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
Click to expand...
Click to collapse
Yeah , bro , but you're one man fighting against the tides . It's bound that LG has at least a reminder of 5 man cell team working on getting gingerbread out . And besides they have other ways of getting info and ironing out bugs faster then you can .
Sad that they didn't place on the internet a god damn ETA by now .... thus I guess may or june might a realistic launch date
Oh and to be on-topic with the thread , I guess we'll see 2.4 by CM7 if any of the legendary devs still take interest in this phone ofc
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
sarfaraz1989 said:
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
Click to expand...
Click to collapse
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
andy572 said:
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
Click to expand...
Click to collapse
if everything's open then it is unlikely they make money. Then they close down and there won't be any phone.
Sent from my LG-P500 using XDA App
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
sarfaraz1989 said:
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
Click to expand...
Click to collapse
Seems like you have not worked in and managed any technology firms before.
I'm sincerely hoping your dream come true where you will own a successful openmoko company develop cutting edge technology with over 100 staff and offer your sw and hw for free with no claims to patent rights. All the best!
Sent from my LG-P500 using XDA App
ORIGINAL SOURCE CAN BE READ HERE : http://www.rethink-wireless.com/2012/03/08/verizon-announces-ice-cream-sandwich-update-12-devices.htm
Any Verizon customers wondering when they can expect to get the update to Android 4.0 on their handset or tablet has a little more to go on as of this week as the carrier has released a list of fourteen devices which will receive Ice Cream Sandwich. While it reveals what will be getting the latest version of Android it doesn't go into the more crucial detail of when.
Handsets set to get the upgrade include; HTC's ThunderBolt, Droid Incredible 2, Rhyme and Rezound, Motorola's Bionic, Razr, Razr Maxx and Droid 4 and LG's Spectrum. Among the tablets getting the upgrade are Samsung Galaxy Tab 7.7 and 10.1 and Motorola's Xoom and Xyboards.
The fact the Droid devices make the list isn't surprising as Motorola had already said so in its own announcement. If it's anything to go by then it means anyone eager to receive the update could face waiting up to Q3 this year to get it on their handset.
In addition to refining the Android UI with common actions made more visible, more intuitive gestures and other features such as Android Beam and Face Unlock the new OS works across both tablets and smartphones. This avoids the divergence of the two branches of the Android that was seen when the tablet-friendly 3.0 was released.
Verizon promises to update the list as more information becomes available "throughout the year". This doesn't exactly suggest that the update is going to be available soon and may encourage Android loving customers to look elsewhere for their Ice Cream Sandwich thrills. If they stick with Verizon this mainly means opting for the Samsung Galaxy Nexus which was released in December and comes with the OS pre-installed.
It was already posted - http://forum.xda-developers.com/showthread.php?t=1533907
already knownnn...omg HOW COULD YOU POST THIS AGAIN...((((
Tell them to scrap the rollout and get goin' on Jellybean or whatever 5.0 will be Our devs already made ICS for the Rezound
Jellybean's already obsolete. It's all about Key Lime pie now.
graymonkey44 said:
Jellybean's already obsolete. It's all about Key Lime pie now.
Click to expand...
Click to collapse
Pssh, the cool kids are already calling it KLP. Get with the program!
chupajr said:
Pssh, the cool kids are already calling it KLP. Get with the program!
Click to expand...
Click to collapse
hope to god it won't key lime coloring. it was bad enough to deal with green for so long
It seems to be overlooked by EVERYONE, but all of the articles i've read say that the Jellybean 5.0 OS will be tablet based ONLY. Not for phones... much like the Honeycomb OS. Correct me if im wrong
That would be absolutely retarded. They just brought them together under ICS and then break them apart again with JB?
I hope they don't do that...
tCizler said:
It seems to be overlooked by EVERYONE, but all of the articles i've read say that the Jellybean 5.0 OS will be tablet based ONLY. Not for phones... much like the Honeycomb OS. Correct me if im wrong
Click to expand...
Click to collapse
Not true, its supposed to implement some sort of desktop mode for tablets. I'm pretty sure they aren't going to fragment it anymore
Never believe every article you read, or any for that matter. Unless they have concrete proof their full of it
Sent from my ADR6425LVW using Tapatalk
I hope to when HTC gives us ICS they also update the Rezound to 4.0. I would love to see this happen but with 4.0.
Id love vanilla ice cream from htc but sadly i know this wont happen. Hopfully the devs can get aosp going. Id say we should have the OTA by mid summer.
Think this qualifies as development
Quoted:
We are now releasing a sensor framework, referred to as DASH (Dynamic Android Sensor HAL), as an open source GitHub project. This actually means that we are the first manufacturer to release such a sensor framework. By making this open source, we hope that custom ROM developers will gain a lot from using it, and we also hope to see the community of developers help us improve the framework by contributing back (which we’ve already seen from CyanogenMod team). In this article, Oskar Anderö, a Sony Mobile software engineer, explains how DASH works, and how developers can contribute.
OskarAnderö,Software Engineer.
A few months ago, we announced the open sourcing of the Dynamic Android Sensor HAL, internally called DASH for short. The sensor HAL is the software layer giving applications direct access to the sensor components. DASH was invented as a way to use the same sensor HAL implementation across multiple devices and hardware. When doing bring-ups of new Android platforms, we had to reinvent the wheel every time when it came to sensors. Nowadays, it is only a matter of enabling the sensors we need for that specific platform and configuring them according to their mounting and specifications.
Source:
http://developer.sonymobile.com/wp/...l-dash-developers-can-contribute-open-source/
Sent from my Paranoid SGS2
Cool even tho im not a developer
let next will be camera sources and not need for Sony to release jb.
coolkaas said:
let next will be camera sources and not need for Sony to release jb.
Click to expand...
Click to collapse
The ICS camera libraries are on developers site. I don't know it is usable to JB....
Wechy77 said:
The ICS camera libraries are on developers site. I don't know it is usable to JB....
Click to expand...
Click to collapse
Damn I sure hope so, camera is one of few major issue what I know they've been struggling with on JB/CM10 for some time .
Wechy77 said:
The ICS camera libraries are on developers site. I don't know it is usable to JB....
Click to expand...
Click to collapse
no. this not help us. all developers of course know about the drivers.
quote from your link: 'This version is for Android 4.0 (Ice Cream Sandwich).'
usually all HAL have deep dependence from operation system.
Does any rom support Bluetooth 4.0?
I heard that the official roms does not support it.
I really would like to use Polar H7 with the Galaxy S3.
mirdones said:
Does any rom support Bluetooth 4.0?
I heard that the official roms does not support it.
I really would like to use Polar H7 with the Galaxy S3.
Click to expand...
Click to collapse
Stock firmware has Bluetooth 4.0 built in, it's a hardware kind of thing.
Skander1998 said:
Stock firmware has Bluetooth 4.0 built in, it's a hardware kind of thing.
Click to expand...
Click to collapse
I heard it was a lack of support by android itself. Something to do to a lack of drivers, not hardware.
Anyway, this is false propaganda as it says on the box that it is a Bluetooth smart ready device. Anyone can see it clearly here: http://www.bluetooth.com/Pages/Bluetooth-Smart-Marketing.aspx
mirdones said:
I heard it was a lack of support by android itself. Something to do to a lack of drivers, not hardware.
Anyway, this is false propaganda as it says on the box that it is a Bluetooth smart ready device.
Click to expand...
Click to collapse
I've been pissed since I bought the H7...Can't use it, was told by Polar that the only device that works is the iPhone 4S or later model...No Android phone is supported, not even the listed Droid Razr...the S3 was listed as having Bluetooth Smart technology, but Samsung Customer/tech support said that its not usable due to the Android OS Ice Cream Sandwich, which makes it useless. I ended up buy the Zephyr HXR, which works seamlessly with S3. The polar h7 is sitting on a table collecting dust, 100 ones downs the drown I guess...I can only hope that the Jelly Bean OS allows the S3 to do what it's advertised to do...I refuse to get an iPhone, luv the android devices, but getting increasingly frustrated with the lack of support from devices and apps treating the android user like second class citizens. I mean, how can you have a P90X App for iPhone but not for the Androids, we have more users, which would equate to more dollars for these developers, but whatever, end of my rant. carry on.
ION vs PMEM
What is the difference?
Google is your friend - http://lwn.net/Articles/480055/
In the case of the Rezound specifically, ION is generally faster and less laggy, but has a purple tinted camera, and no working front camera (for now).
To quote shrike (I hope that's alright)
Originally Posted by shrike1978 View Post
ION is the new unified memory management architecture that Google is advancing. Prior to ION, every SoC manufacturer had their own way of doing memory management. Qualcomm's was pmem, Nvidia's was nvram, etc. It made it's debut as an option in ICS and is preferred in JB. Being unified also means that it is a good candidate for integration into the Linux kernel mainline, which would mean that Android would no longer require it's own separate branch of Linux.
So I've read this but what would that mean in terms of developement? If Android didn't have to be a separate branch of Linux, would it be easier to spread ROMs to all the different phones?
regnsy pronounced
noo_too_droid said:
To quote shrike (I hope that's alright)
So I've read this but what would that mean in terms of developement? If Android didn't have to be a separate branch of Linux, would it be easier to spread ROMs to all the different phones?
regnsy pronounced
Click to expand...
Click to collapse
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the HTC One X to the HTC Rezound, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based on different versions of HTC Sense.
But porting a ROM from, let's say a Samsung Galaxy III is nigh impossible, because it uses a different system-on-a-chip exclusive to Samsung phones and its stock kernel is based on TouchWiz. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why cyanogenmod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? The Droid Incredible 2, for example, is still waiting for an official ICS release it may never get, which means running Jellybean as it is meant to be run is that much harder. It's hard enough on the Rezound, where we have official ICS kernel source.
That's why I give lots of kudos to people who take custom ROMs like BAMF paradigm, paranoid android and the like that were developed for other devices and port them to the Rezound. And mega kudos to people like chad who can port/re-factor underlying hardware code originally developed for another device to work on the Rezound. We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
It makes stuff awesomer
wildstang83 said:
It makes stuff awesomer
Click to expand...
Click to collapse
An answer i can understand.....thx!
Dcnovicky said:
An answer i can understand.....thx!
Click to expand...
Click to collapse
Ha, anytime my friend
Sent from my ADR6425LVW using Tapatalk 2
brenuga said:
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the HTC One X to the HTC Rezound, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based on different versions of HTC Sense.
But porting a ROM from, let's say a Samsung Galaxy III is nigh impossible, because it uses a different system-on-a-chip exclusive to Samsung phones and its stock kernel is based on TouchWiz. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why cyanogenmod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? The Droid Incredible 2, for example, is still waiting for an official ICS release it may never get, which means running Jellybean as it is meant to be run is that much harder. It's hard enough on the Rezound, where we have official ICS kernel source.
That's why I give lots of kudos to people who take custom ROMs like BAMF paradigm, paranoid android and the like that were developed for other devices and port them to the Rezound. And mega kudos to people like chad who can port/re-factor underlying hardware code originally developed for another device to work on the Rezound. We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
Click to expand...
Click to collapse
I'll hit that thanks button just for that essay you typed
Sent from my ADR6425LVW using xda app-developers app