Related
---
yeah i have lunarglide 3 and sensor. i want to use it. =(
+1 for nike+ on android.
I looked into this (Also a Nike+ and Atrix user), unfortunately I don't think it's possible because Nike+ isn't bluetooth, ANT+ (in which case our phone doesn't support it either) and mostlikely uses a proprietary protocol/frequencies for communicating with the foot sensor. Also, Nike signed an exclusive contract with Apple so, while they could create an Android App & some receiver device they won't....Unless they want to lose their lucrative deal with Apple
Also, your GPS is built into the phone and doesn't cost you anything if you have a data plan to get Google Maps. You don't need to pay for it to AT&T (They basically just tell you where your family is, which you can do for free with Latitude)
The few viable solutions that I can see for treadmill running (which is the case why you couldn't use the GPS solutions abundant on Android) are:
Garmin 405 (or similar) watch + footpod sensor which runs ANT+
A Sony phone which has ANT+ which you can pair with footpod and ANT+
MotoActiv which has ANT+ and can be used with a footpod and ANT+
What you really want, that doesn't exist (to my knowledge) is a bluetooth cadence sensor and an Android App to convert the candence information into human readable data like Nike+
^+1
Nike+ will probably never see support for the Android.
I would even buy an alternative to nike + as long as it were as intuitive and as easy to use. Nike + for android +1
You can allways go with the nike sportband
GPS
orphan22 said:
You can allways go with the nike sportband
Click to expand...
Click to collapse
GPS is a free service that is built into your phone you don't need to subscribe to some navigation app.
According to Anandtech:
Until recently basically all satellite based location has used GPS, which consists of a constellation of 27 satellites. GLONASS is its Russian cousin, with 24 satellites. The two can be used in conjunction to get faster 3D fixes, better coverage, and greater accuracy. We'll see more and more GNSS solutions start shipping in 2012 as well.
...
If you fire up GPS Test, satellites numbered 65-88 are GLONASS. Qualcomm’s GNSS only uses GLONASS when there either aren’t enough visible GPS satellites for a fix, or SNR is bad (basically an urban canyon or indoors scenario), so you’ll often see a set of bars pop in or out depending on how good the normal GPS SNR is. This implementation is the same for all of the Qualcomm SoCs and MDMs that include GNSS support.
Click to expand...
Click to collapse
I just tried out GPS Test on my phone, and it picked up the GLONASS satellites as well!
Additional confirmation: http://androidandme.com/2011/12/news/qualcomm-enables-dual-core-location-on-snapdragon-phones/
Just one more way our phones are the best phone on the market.
Yea, it was announced a while ago: http://forum.xda-developers.com/showthread.php?t=1393727
It's pretty cool!
Hello Xda-Developer Members,
My Name ist Robin, I'm from Germany and almost 20 Years old. This is my first post here (since 5-6 years ago), please be patient if my English is not that good or i'm writing in the wrong topic.
I've been customizing HTC Devices almost 5 oder 6 Years ago, so deep in my mind there are some rememberings about flashing XDA's left, but actual i would rather call myself an absolut beginner If you have interesting links or tutorials for me, that can answer my questions, please just post the link. I guess my english is that bad that i don't have the right keywords to find what i'm looking for.
I've bought myself an R56 Mini Cooper S and i'm very happy about this car, except of the Entertainment. The original Headunit has no functions than the tuner,an auxiliary input and a CD-Player. The sound is not powerful ( i already managed to customize and delete the 100Hz Limiter the Radio has for the "Stereo-System-Speakers") as this lays in the low ampfiler power. Upgrades are very expensive (Bluetooth just for calls - 300€ all around- no A2DP Support at all!!) and doesn't satisfy me as they won't work properly ( Problems with ID3-Tags, USB-Storage Sizes...).
Professional Digital Sound Processing (about 300€) requires a MOST-Bus Interface(very expensive). Summing up all togheter, working with the original Headunit will never make me happy at all.
I was looking for some alternatives and found two kinds of upgrade head units, that fit into the original interior design and which seems very interesting to me expecting the functions.. I'd like to ask the professionals here some questions about ist.
Headunit Version 1: Please search on Aliexpress for " ZESTECH New mini cooper car dvd player with gps navigation radio bluetooth steering wheel car dvd player mini cooper ", I'm not allowed to post a link in here
This Headunit is equipped with an ARM11 Processor 800Mhz, 256MB Ram, 128 MB Rom and a custom version of WNCE 6.0.
There are several functions that i would be really interested in- like the GPS Receiver, Bluetooth (With A2DP!) Touch Display, CAN-Bus interface for wheel steering control and so on.
Also i'm afraid of a very slow system ( 256MB Ram and 800Mhz is not very much, isn't it?!), a crappy software design with bad german translation, navigation software that doesn't work properly.... Problems we know from "NoName China Devices"..
So i'm wondering if it is possible to install a clean Version of WIN CE i could customize by myself ? Can i upload the ROM that is installed on the device just to take out drivers? (I guess, i'll have to?!)
I have heard, Windows Phone 7 is based on the WIN CE 6.0 Core. Is it possible to install Phone7 on a WINCE device ? I like the Design of it better than the WINCE- and Windows Phone would deliever a Software store, were i could easily download Apps, i guess.
Would it be possible to install a clean version of Android on this device? In those days i was hacking my HTC, Android actually came on and some custom ROMs appeared that managed using Android on WInMob Devices by using HaRet as "boot loader" , i deeply remember....
Headunit Version 2: Please search on Alieexpress for " Pure Android 4.4 Car radio DVD GPS for BMW Mini (up to 2013) with Bluetooth RDS USB SD IPOD SWC Rearview 3G Wifi Support DVR "
This Headunit is equipped with a more powerful 1,9 Ghz Cortex A9 CPU, 1GB Samsung Ram and 8 GB ROM. Even the quality of the software design and display resolution is much better. Also it has WIFI, a Can Interface, Bluetooth, GPS Receiver, and so on. Another benefit that there is already a version of Android running on it- but it's still no clean version. The description says something about that the google market is installed on the device. Could any problems come up to me that the market won't work properly?
Is it possible to take this device, take the hardware drivers out of the original ROM and finally install a current clean Android ROM on it?
Can man make the Google Market work? ( I heard there are Problems with self-cooked ROMs and the Google Market- but im only a noob )
I still remember, building a custom rom and make a upgrade ROM work is a big amount of work- but if this is possible it would be worth it, for me and sure for other Mini Drivers since most of them are sad about the bad Entertainment.
Please don't be angry about the large text and maybe some dumba** questions. I did much to find a solution by myself, but still im sitting here without any idea
I'm looking forward for your answers,
Robin
If you want a hackable Chinese headunit, I would recommend the 2 most popular here on XDA:
http://forum.xda-developers.com/and...4-4-2-kitkat-head-unit-newsmy-carpad-t2865525
http://forum.xda-developers.com/showthread.php?t=2660662
But I don't know how well they or their variants will fit in your car.
If you just want "Android Auto" you can try my headunit app on a tablet: http://forum.xda-developers.com/showpost.php?p=60894402&postcount=94
Hey hey! Thank you for your fast response!
The Version 1 Headunit you wrote about is my absolute favourite. very nice thing. Sadly, putting a 2-Din Headunit into my car means a lot of work, and there is still the old command unit for the standard radio that won't work anymore if there is a new sound station installed.
If there is no better solution i'm fine with that. But as long as there are - maybe - head units that fit into the original interior, this would be more satisfying.
A few Minutes ago i sent a Mail to the Customer of the Android DVD radio if there are any limitations within his android version and if there would be a possibility sending me a clean rom version if i buy the radio. Last point is a high expectation- but who knows
Testing iOS and Android software presents unique challenges that require unique test conditions.
Testing iOS and Android software presents unique challenges. As easily portable devices, smartphones and tablets are used in a variety of settings, and wireless connectivity may widely fluctuate and acutely affect the performance of any applications in use. Unlike with PCs that have wired connections, dev/test teams cannot assume relatively stable network conditions when crafting a mobile game, messaging client or news reader.
Moreover, despite enormous leaps forward in CPU and GPU design since the iPhone’s debut in 2007, mobile hardware still is considerably less capable than desktops or laptops, especially when it comes to device memory. In practice, this can means suboptimal performance when working with mostly interpreted languages such as JavaScript (in contrast, PCs often have RAM to spare and can accordingly overcome flaws in language design), as well as frequent crashes.
Still, the difficulties of have not discouraged shops from trying their luck. There are more than 1 million apps in both the Apple App Store and Google Play, and Microsoft has revealed that the count for the Windows Phone Store is now at 300,000. With the market moving toward mature software that takes advantage of increasingly powerful endpoints and addresses functionalities once reserved for PCs, will be instrumental for fostering collaboration and coordinating both manual and automated tests.
How can developers and QA engineers deal with so many mobile devices and platforms?
Creating software for mobile devices has never been simple or easy. In the early days, there were incredible constraints on hardware as well as relatively few APIs and toolkits for expediting development. Over the years, some of these challenges have been overtaken by new ones surrounding sustainable monetization and consistency across a wide range of platforms.
Teams have to address users who may delete an app if it crashes even once, but how can they do so when there are so many device/OS combinations to account for? Native vs. HTML5 development is a conversation for another time – let’s look at how an application developed with either of these methodologies might be tested. Many of the issues that apps face in the wild originate from overlooked mobile testing conditions, which if implemented may have produced a more polished product. Here are a few to keep in mind:
Too much manual testing: Manual tests aren’t bad – they’re critical to many QA workflows. But teams can easily become over-reliant on them, which doesn’t scale well given how fragmented the mobile ecosystem is. Android KitKat, for example, only runs on 20 percent of Android devices as of August 2014. Automated processes are needed.
Insufficient simulation of real-world conditions: As discussed earlier, smartphones and tablets don’t exist in a vacuum. They’re carried inside buildings with poor reception, or packed along into remote regions with only 2G or 3G coverage. Tests have to account for these realities as well as limitations on memory, screen resolution and battery life.
Low attention to region/language settings: This one flies under the radar since many developers target only specific sets of users. For apps with an international or multilingual audience, it is important to see if the platform in question has a translation option and whether app performance is affected by switching from setting to another.
Overall, mobile testing is about scalability for many devices and consistency despite constraints. A blend of automated and manual tests is usually the best way forward.
“Manual testing is a definite need, however, there are so many devices and combinations in the market today that it is necessary to use automated mobile tools as well,” stated a software engineer from CallFlow, in a post on LinkedIn. “User expects (sic) the application to stay on, connected, and perform at all times. To meet these expectations, the mobile testing strategy should include real device testing under various real world conditions. That includes various signal strengths, networks, speed and more.”
The stakes for mobile testing: Even big companies can miss bugs as apps scale
Facebook, with its 1 billion users, is obviously an outlier in the software world, but its recent battle with a bug in its iOS app illustrates how mobile testing requires tremendous time and effort as well as top-notch tools. The social network’s engineers were noticing an issue related to the Apple CoreData System, but due to the size and rapid evolution of the Facebook codebase, parsing the crash reports proved a monumental undertaking.
“[C]ertain fundamental programming challenges inevitably become more difficult with scale,” explained Slobodan Predolac and Nicolas Spiegelberg, engineers at Facebook. “Debugging, for example, can prove difficult even if you can reliably reproduce the problem – and this difficulty increases when debugging a highly visible but nondeterministic issue in a rapidly changing codebase.”
Ultimately, the Facebook team was able to identify the issue through close collaboration and a focus on programming fundamentals. The fix may have reduced the app’s iOS crash rate by 50 percent.
Users often have little patience for app crashes, so this is an important development. While most other shops won’t operate at Facebook’s scale, they’ll still have to deal with similar performance issues that could manifest due to adverse real-world conditions and/or other flaws in the code. A test management solution enables developers and software testers to scale their workflows and find defects early and often at low cost.
Advice, developing a high end video compression codec on Shield Android TV for Camera Acquisition and HQ video.
Hi
Aims
I am researching doing a high end streamlined video compression/decompression codec that can be installed and registered under Android, and be available to third party camera, editing and video apps.* Shield seems like a good top end development target.* I am hoping it will be able to compress 4k+ video streams, with small file sizes and reduced processing overheads.
Even though it is meant to be more for high end camera acquisition on Android in general, it also has other uses on the web.
I am trying to find out general, and detailed, information to see what I need to address.* I'm a newbie to all this, from back in the days that C++ was new and untaught in my college. I'm going to have to reteach myself programming, but have a lot of knowledge on the design side due to previous work.
Codec Programming?
So basically, I need advice on broad programming info on programming and registering a codec on Android and gp-gpu use?
But with Android things seem a bit more complicated to get performance due to the way things are structured:
Backend Camera Streamlining?
Previous high level camera projects have failed due to the underlying restrictions of the android camera interface and customisations from phone to phone, but also Android's slow nature. This is an attempt to bypass this with a high performance codec section.* L and M, reportedly address the deficiencies somewhat, but for the codec I realise the data rate of video data coming in might be poor, and* I might have to write a back end to acquire the frames from the hardware to the codec quick enough, which I don't want to do, but if I can't get frame data delivery fast enough I will have to look at it. I want to use mainly the GPU or other processing units instead of the main processor, for power efficiency and speed, but realise nothing is simple. All that sort of stuff that you have to do because it was not done right in the first place. So, avoiding going through slower high end camera interfaces as much as possible. I understand it is all based on a standard Linux camera API. If the camera software does not have to be rewritten and it can deliver frame data at streamlined timely speeds to a codec, then I can avoid much of this. So, I probably need advice in these things too.
Backend Storage Streamlining?
Now, on the other side we have storage**Hopefully the data rate can be small enough to avoid issues, but that is unlikely on a 4k-8k frame and would need advice on this too.
JavaScript to Android, Android to JavaScript transportability?
I actually want to develop the core of it within JavaScript primarily, for transportable use on the web and Firefox OS, so will have to find out the best way to transfer it to Android for compilation? As I know next to nothing about these new languages, it will be an uphill learning curve. As I understand, JavaScript syntax is separate from Java, and not a even a logical subset, which makes life hard.
----------
Anyway, it is a shame we don't have a kick starter like funding scheme, to pay a good programmer to do most of the background stuff, and upgrade the Linux code and drivers, so anybody can use the new code with any codec and camera app combination. My main interest is my own codec, not all the other stuff, that is really fixing Android and Linux camera code, which would help everybody.
This is not an official project start, just implementation research.
If anybody knows of anybody that can contribute, please direct them here?
Thanks.
Stevio2 said:
Advice, developing a high end video compression codec on Shield Android TV for Camera Acquisition and HQ video.
Hi
Aims
I am researching doing a high end streamlined video compression/decompression codec that can be installed and registered under Android, and be available to third party camera, editing and video apps.* Shield seems like a good top end development target.* I am hoping it will be able to compress 4k+ video streams, with small file sizes and reduced processing overheads.
Even though it is meant to be more for high end camera acquisition on Android in general, it also has other uses on the web.
I am trying to find out general, and detailed, information to see what I need to address.* I'm a newbie to all this, from back in the days that C++ was new and untaught in my college. I'm going to have to reteach myself programming, but have a lot of knowledge on the design side due to previous work.
Codec Programming?
So basically, I need advice on broad programming info on programming and registering a codec on Android and gp-gpu use?
But with Android things seem a bit more complicated to get performance due to the way things are structured:
Backend Camera Streamlining?
Previous high level camera projects have failed due to the underlying restrictions of the android camera interface and customisations from phone to phone, but also Android's slow nature. This is an attempt to bypass this with a high performance codec section.* L and M, reportedly address the deficiencies somewhat, but for the codec I realise the data rate of video data coming in might be poor, and* I might have to write a back end to acquire the frames from the hardware to the codec quick enough, which I don't want to do, but if I can't get frame data delivery fast enough I will have to look at it. I want to use mainly the GPU or other processing units instead of the main processor, for power efficiency and speed, but realise nothing is simple. All that sort of stuff that you have to do because it was not done right in the first place. So, avoiding going through slower high end camera interfaces as much as possible. I understand it is all based on a standard Linux camera API. If the camera software does not have to be rewritten and it can deliver frame data at streamlined timely speeds to a codec, then I can avoid much of this. So, I probably need advice in these things too.
Backend Storage Streamlining?
Now, on the other side we have storage**Hopefully the data rate can be small enough to avoid issues, but that is unlikely on a 4k-8k frame and would need advice on this too.
JavaScript to Android, Android to JavaScript transportability?
I actually want to develop the core of it within JavaScript primarily, for transportable use on the web and Firefox OS, so will have to find out the best way to transfer it to Android for compilation? As I know next to nothing about these new languages, it will be an uphill learning curve. As I understand, JavaScript syntax is separate from Java, and not a even a logical subset, which makes life hard.
----------
Anyway, it is a shame we don't have a kick starter like funding scheme, to pay a good programmer to do most of the background stuff, and upgrade the Linux code and drivers, so anybody can use the new code with any codec and camera app combination. My main interest is my own codec, not all the other stuff, that is really fixing Android and Linux camera code, which would help everybody.
This is not an official project start, just implementation research.
Click to expand...
Click to collapse
I wish you all the luck in your endeavour, as this sounds really interesting, and different........
Saying that, i dont think your suppose to post anything in the dev thread that is'nt an actuall work, im just giving you a heads up, incase a moderator might come along............also i could be wrong, if this has changed recently
Your best bet i reckon, is to post in this thread
http://forum.xda-developers.com/general/general
Its the main general thread of the entire xda, so you'll have more eyeballs.........and maybe a better chance of getting a "start in the right direction" from someone knowledgeable
Ive also read many android technical question being asked at the "stackexchange" website, by devs working on their projects, so that might be another avenue to explore if your unlucky here
Anyways, wish you luck with this
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Click to expand...
Click to collapse
Thanks. From forum discussion rules. I mistook this to mean development research discussion as well. If it actually should, then I'm happy for it to be moved to general.
Stevio2 said:
Thanks. From forum discussion rules. I mistook this to mean development research discussion as well. If it actually should, then I'm happy for it to be moved to general.
Click to expand...
Click to collapse
The Shield is based on the Nvidia X1 chip. Nvidia also just released the Jetson TX1 development board which is similar. If you register as a developer with nvidia (which is easy) you get access to all the dev docs (including video codec docs) for the TX1, which boots Ubuntu. That should be a good start.
Sounds good, it was an andriod development related question though (using shield hardware under android so it can be shared with different platforms, you just can do more on the shield hardware. Maybe there is a Linux overlap with andriod in codec support but I doubt it isva full story. I am interested in dealing with 8k content too. There is a way to do a 8k over HDMI 2, but muchntoo involved at this stage, the display has to also be modified or an adaptor made to interface to a future 8k interface.
I have just realised the shield might be good for touch table work (not so good on the software side as there are no established software base to work on). I located a new good cheap fine grained more transparent touch surface overlay technology a little while ago that is being used to do cheap touch tables in Asia. Using a 4 subpixel screen I can do a semi 8k display out of a 4k (though you can't directly access the white pixel through hdmi, which is useless). There is also now 6 color pixels. A firmware change might allow a display to sub pixel address. However, you can get panel frames without the internal section and get direct access to the internal panel interface (why hdcp is probably useless). Anyway, 8k would yeild 16k, a nice minimum for a 80 inch table, with OLED, or projector. Reprogramming a display to use display port/thuderbolt interfaces on a display would be more useful. I tried to negotiate access to a 16k projector chip once to connect up to a low powered processing array, but got nowhere. Henceforth I've been dealing with embedded machine code level concerns for decades off and on and let the newer high level language and OS stuff (like C# and Linux) go, due to health issues.
Another intetesting thing that can be done with a shield, is it can be hooked up to a camera head and rigged up to be a camera (or the next version). Problem is that USB 3 is useless compared to Thuderbolt 3 etc (though camera head computet interface standards take a while to catch up). My codec could be used for recording. We used to do this with PC's but the Shield offers a much better power consumption. There is Linux software around to do this, but the development board is half powered and expensive.
Bump
Well, when I said bump, I didn't really mean to move it to a third subforum
Seriously, I want to do a less than 20mbit/s 8k visually lossless codec. But at the moment I'm waiting to get checked out for dementia, which explains a lot about the last few decades and my decreasing amount I can do (beta amyloid in particular builds up for 10-20 years with low grade symptoms before it gets seriouse enough that it is can be picked up on older scanning, by then it has permanent problems. Apart from other types of dementia). At this stage I can't do much much of the time.
Anyway, as the thread has skipped to a second forum in two days, any more short cut advice is welcome.