[Q] Samsung transform and intercept one area? - Intercept General

So I know the Intercept and the Transform are similar phones. Since the Transform doesn't have a forum area and both our communities seem kinda small right now... what do you think of having both phones in this one area?

if the development is cross platform sounds good to me but it may be better to see if the mod could create some sub forums or something for the whole line.
Considering the moment (m900), intercept (m910), and transform (m920) are all in the same product line.
However they are all different hardware so it would most likely not be benifical.

Related

The Future of Android

Hello Everyone!
Let me start off by reaching out to the XDA Administrative staff. I would like to thank you for keeping this awesome place in operation. Without you, and the XDA community, I'm not sure Android development would be as vibrant. Also, if this thread is in the wrong location, please shift it to where you would like it.
I am an Android user, not a developer, and I feel the future of the Android OS is not headed where I want it to. I'm writing this post to see if anyone has any further thoughts on the matter.
Google is marketing Android as an Open Source OS. You are able to download the source, modify it as you wish, and then build it. If you are running a vanilla build of Android (i.e. Nexus S) you are able to alter your experience as you see fit. The issue I foresee isn't the fragmentation of the Android versions (which is still debated as an issue), but rather the fragmentation of the user experience.
When an end-user purchases a handset from most major carriers, they receive an Android device. Between different handsets, and carriers, the features that are available to a single user can vary exponentially (i.e. the inability to install APK files, bypassing the market, on AT&T devices). This device is still based on Android, but is it still Android?
I have no problem with manufacturers adding their own code to the Android system, as long as the core functionality is kept the same. When you begin to alter the basic functionality of the system, at what point is it no longer Android? Linux Mint is derived from Ubuntu, but it is no longer Ubuntu. The system is a derivative of Ubuntu. If the base of the OS is going to be altered drastically (by manufacturer or by request of carrier) it needs to be known that the device is not Android.
As I am most familiar with HTC Android devices, I will use HTC SenseUI as an example (although, as I think about this more it may not be the best example). The core functionality of the HTC devices is similar, but not entirely the same. Most of the default applications (Browser, Contacts, Dialer) have been altered to what HTC feels is more atheistically pleasing. However, these features are additions. They are not removing functionality from the device.
With my HTC Evo (by default) there are core functionalities removed. Without rooting my device, I am unable to tether via WiFi. Even when rooting, if I want to keep the 4G experience, I need to install a third party application to tether instead of simply using the functionality that was supposed to be built in to Android. Why? Sprint has decided to bake their own hotspot functionality into the core of the OS. Yet to use it, I am required to pay an extra $30 fee on top of my [i/unlimited[/i] data plan. I am not knocking Sprint, here. As long as I have used their service, I’ve had nothing but stellar performance and the price point is perfect.
I feel with this core functionality removed, my Evo is no longer Android. It’s simply Android-based, an Android derived OS. The problem with these manufacturers, and their Android-derived operating system, is the lack-luster experience the consumers get with the product.
I started my Android experience on an HTC CDMA Hero. It took me eight months to get any major software upgrades (The device ran Android 1.5 from factory). Why? Because it was taking so long for manufacturers to bake their Features into the OS. If I was not a techie, I feel this experience would have pushed me away from the Android platform. I fear this fragmentation that is occurring could be the downfall of the Android platform.
I want to be able to buy a device. I want to be running the newest version of Android. If I do not like the ROM that came on the phone, I want to be able to change that. But I do not want to purchase a phone with all of this baked in garbage, or aesthetic features that require me to wait long periods of times for my device to be upgraded to the newest version of Android. And, I hope that I am not the only person to feel this way.
So here is my idea, pending input from the Android community of course: An open letter, with a petition, to all members of the OHA requesting for Android devices to be Android! Unadulterated Android OS from Google (With minor modifications to ensure specific hardware is working properly). Requesting that we are given access to the entire device, that we paid for, without having to exploit the operating system to obtain the ability to modify it as we see fit. If a manufacturer, or carrier, does not wish to comply with this, they will not be able to market the device as being Android. Rather, the device is based on Android.
Honestly, I’m not sure what I am looking to accomplish. Maybe, just so they know we are just as interested in Android as they are. And that we want nothing but for Android to succeed. Or maybe, that we support Android being open source, but not being heavily modified to the point where it’s a bastardized.
What do you think?
Tim, I support you in your belief that carriers, not manufacturers, are taking the wrong turn by messing with the full functionality that people pay a hefty price to OWN!
Do we truly OWN what we paid for, or are paying for? I don't believe so, for example, the SAMSUNG Vibrant t959, aka the Samsung Galaxy S i9000, same phone but the carriers decided to have certain features removed from the phone, not be MADE without these features, the FM radio HW and the FFC. Many people know these features were REMOVED, due to the leftover molding and other " skeletons"! Would anyone want to have a carrier when they know that they don't want there customers to have the FULLEST experience, like it was meant to be?
Sent from my HTC MyDesireHD 4G!
I would also like to share with you that MANUFACTURERS creating these "skins", I'm going to use HTC Sense for my example, is actually NOT a bad thing at all!
HTC Sense has opened a huge amount of rich content and functionality to there users immensely! HTC Hub, HTC Locations for example! All these add ons are very useful to users and does NOT restrict the full functionality but yet BOOSTS its functionality!
Unfortunately though, carriers decide to take these hearty and supreme names and totally rip it apart by taking away functionality, features, and the most...a good user experience! For example, my phone..the HTC MyTouch 4G aka the HTC Glacier. I received it with something called Sense on it, but any owner knows that is NOT Sense! That is not HTC Sense! After burying myself in the bowels of my new phone, I now have a HTC Desire HD Rom on it that will stay on it until I get the new HTC Sense 2.3 update! The full HTC Sense is a good thing and I strongly believe its worth waiting for!
Sent from my HTC Glacier
I agree, but believe Android is a growing mobile OS. If Google did not push their mobile OS (and let manufactures do what they want). Android probably would not have last against the competition. Its all a survival of the fittest situation. Some people are going to make use of their phones others aren't. Too bad bloatware has been the success for some Android phones. Glad someone else noticed this. Thank you for your thread.
The fact that Android is open source will inevitably have benefits and downfalls.
Benefits being that carriers and manufacturers can add cool stuff. Downfalls being that they can remove good or add awful stuff.
However Google can't have double standards. If it's open source, it's open source, for better or for worse.
An advantage of OEMs participating is that more parties are contributing to coding for android. More innovative ideas are potentially contributed.
For techies this is particularly awesome as we can port awesome features that perhaps weren't designed for our phone and disable lame restrictions. By this way we potentially can have all software benefits of more than one company brand etc.
Being an ordinary consumer in this context can suck.
Tim, while I understand your frustration (trust me, I've felt similar over the past few months), I don't fully agree.
The heart of Android is that it is Open. Open Source is a part of the openness that envelops Android, but what is meant by "Android is open" is so much more. OEM's skinning their devices is part of it; carriers stuffing devices full of their crapware is part of it; heck, even manufacturers/carriers limiting devices' use in one form or another is technically part of it. I think that Google's model with Android is that people can use in whatever way they see fit (except, you know, literally stealing it and claiming that they made and own it) and adapting it to be the OS that they want. Android gives people the freedom to do with it what they like.
I think that Google hopes that carriers, OEMs and everyone else will use it for the better and add to the functionality and maybe even contribute to the Open Source project and thus to the greater Android community and the vision thereof. Sadly, it is not always the case and then you get situations where a carrier or an OEM will limit a device in some way for a quick buck (your example of tethering on the EVO being a good one). I think that what AT&T did/does on their Android devices is as a final product a good example of what Android is not intended to be, but their actions are, technically, still in the spirit of Android.
The way I see Android, it is about the freedom to do whatever you like. Android is then also more for the thinking person as there are literally hundreds of devices to choose from and each one has strengths and weaknesses when compared to the rest. You as a user need to consider what it is that you want from your device and then select the device that is the most suited to your needs.
I want to be able to buy a device. I want to be running the newest version of Android. If I do not like the ROM that came on the phone, I want to be able to change that. But I do not want to purchase a phone with all of this baked in garbage, or aesthetic features that require me to wait long periods of times for my device to be upgraded to the newest version of Android. And, I hope that I am not the only person to feel this way.
Click to expand...
Click to collapse
You are not the only person that feels that way, I feel the same, which is why I've decided to get myself a Nexus S. It's tricky to get it to this country, but it'll be worth it. I realise that you're on Sprint which means that a Nexus device won't work, correct? A better petition IMO, would be to petition Google to release CDMA versions of their devices.
Sorry to say, but 4G is not derived from android. The phone itself will always support it, harware wise. So, what are you saying? /: Who are you complaining to? ROM chefs for not managing to make the 4G fully functional?
totally agree with you
he is complaining about gimped devices being marketed as android devices. to sum up what i think his messages is; a device should not be called an android device if it is not fully capable of all it's natively supported features, wireless tether, root access etc. but rather should be called android based device.
Good idea but never going to happen. This is driving me away from this platform...
Sent from my SGH-T959 using XDA App
I'm curious as to what functionality we can get by simply rooting. I'm not seeing the huge deal I may be missing something so I'm asking
Sent from my Incredible using XDA App
To me, they should just change the launcher and add their own apps in (NOT replacing) and not touch other stuffs already. If totally not changing the OS makes them look alike. To me, thinking about Windows phone 7 in the future. Imagine seeing so many people holding a phone that has the totally same UI, its like seeing a Sony Ericsson X10 and a HTC Desire totally same except that the casing is different.
Technically, the fact that its open source is supposed to help the majority of OEMs, and in turnfilter down to end users as price cuts/ feature enhancements.
But premium features are premium features. You want some kind of 4g? You wont be getting it from end users at xda - it will come from manufacturers who build the radios and APIs into the device.
Android is a very modular os... if you want something all you have to do is a bit of research and buy the device that fits you best. If you go with one of the other systems you will simply have less choice. That is why android is cool.
aint gonna happen guys, doesnt make good business sense to make a device that does everything, why sell one model when you can sell two!
you can pick up any device out there and say, "wouldnt it be cool if it had VGA out or HD camera or x y z", they wont do it, and the same goes for the OS as well.
Open source has an inherant flaw, and that is its fragmentation, everyone believes it should be going in a direction they would like (including yourself). at the moment its not suffered as much as its desktop cousins probably because of its market place keeping one common aspect through all devices but give it time and you will be right, it will lose its "android" identification
If you want an alternative and a device that keeps its personality then get an Iphone or a new WP7 device at least until they crack that wide open too. Its a bit ironic really that WM may well suck but its very customizable and has been consistant throughout the ages
evo4gnw said:
he is complaining about gimped devices being marketed as android devices. to sum up what i think his messages is; a device should not be called an android device if it is not fully capable of all it's natively supported features, wireless tether, root access etc. but rather should be called android based device.
Click to expand...
Click to collapse
But that's just the thing isn't it? Android can probably support ANYTHING. But because of that, you aren't supposed to release hardware that isn't as flexible? That to me.. is just looney.

new os for phones

so just a thought , you guys know of any other new os for phones that are in development that look really promising?
With out the app market systems og Android, IPhone, and the Windows, I do not see how any OS Will grab a foothole for a long time.
boominz28 said:
so just a thought , you guys know of any other new os for phones that are in development that look really promising?
Click to expand...
Click to collapse
There's bada, which appears to be stripped down android that samsung wants to start using for entry level "smart" phones.
MeeGo springs to mind as the only OS that isn't already out and has a chance to be a contender
The only two real possibilities might be WebOS and Meego, but even they probably have no real future unless they can encapsulate Android compatibility and offer something compelling that goes above and beyond it. WebOS might pull it off, but IMHO Meego is a lost cause, just because:
a) Nokia is its only real supporter,
b) Nokia has allowed itself to become almost completely irrelevant in America as both a brand name AND technology provider,
c) it's almost impossible IMHO for any hardware platform with basically zero mindshare in America to become more than a niche local product. America might be a small part of the global market in terms of units sold, but it's a very influential part of it. Nokia's fatal mistake was assuming that the sole value of the American market was the (minimal) revenue it made by selling phones to American carriers, while totally ignoring the staggering global influence of American media on the rest of the world. The outcome is something we've all seen... 5 years of "Smartphone Roundups" that didn't even mention the EXISTENCE of Nokia phones, and led to them becoming all but irrelevant among high end phone users even in their own home market: Europe. Nokia might try waving the flag and getting people to think Android is "too American"... and they'll fail, because it seems like at least half of Android's core developers are European (even if they live and work in Mountain View), and I don't think even Google will ever really be able to control Android's future global destiny once Chinese developers get tired of waiting for Google to fix things they care about passionately and just take matters into their own hands in ways that cause it to lose full compatibility with "mainstream" Android in ways that can't easily be reconciled.
It's not impossible that some other standard might emerge from China (unique in the sense that its domestic market is basically the same size as the entire rest of the world minus India and Africa, and most phones sold worldwide actually COME from China), but even in China, I'd put the smart money on either Android or a mostly-compatible fork of it. IMHO, China's contribution to our future happiness will be phones that are like PCs... more or less commodity hardware differentiated by speed, aesthetics, ergonomics, and niche peripherals that's perfectly happy running GoogleAndroid, a Chinese variant of Android, Windows*, or a slightly hacked & pirated copy of IOS. Phones sold by companies like Motorola and Samsung will be the equivalent of a micro-sized PC made by HP, sold at Wal Mart, ships with Windows, and nobody has ever successfully gotten Linux to work on because it uses some wacky proprietary video chipset that's undocumented and lacks drivers for anything besides the specific version of Windows that PC shipped with from the factory. Companies like Dell and HTC will sell phones intended for Android, but capable of being coaxed into other OS'es with a bit of work (like running Linux on a Dell Laptop today), and most of US at XDA will have phones designed and marketed by medium-sized companies that focus on trying to outdo each other with arms-race hardware based on bleeding-edge chip and circuit designs that looked good in cad, in the analyzer, and maybe even in the prototype... but inevitably have some major problem that didn't become obvious until 250,000 were made, sold, and bought by users who assumed the flakiness was due to rushed beta drivers instead of some deeper design flaw or premature attempt at cost-cutting that went a bit too far.
SBP Mobile Shell 5.0
Lets not forget android has only been out a few f years and its in its infant stage still. I think future development will blow away the competition once its fully established. The monopoly windows has on pcs is why people still haven't realized the advances of linux yet at the same time we are starting to see that break with some major pc companies shipping systems with linux pre loaded.
Sent from my SPH-D700 using Tapatalk
To a degree, yes... but pervasive Windows hegemony is also part of the reason Linux could get a foothold in PCs at all. By being largely compatible with hardware capable of running Windows, PCs capable of running Windows ended up being capable of running Linux by default.
Even now, the fact that it's *possible* to run desktop Linux (KDE, Gnome, etc) on non-x86 hardware doesn't mean that your life won't be *way* more complicated if you insist on trying. Even x86-64 users get a pretty good taste of the sting that comes from deviating from the de-facto hardware norm.
Sent from my SPH-D700 using XDA App

An Open Letter to Android via Google and Forwarded to Samsung

Hi XDA-Samsung Users,
I've been a member of XDA since Jan last year. I went from owning a Nexus One to a Samsung Galaxy S i9000. The reason for the change was for the better specs and superior hardware of the Samsung Galaxy.
The phone is an incredible piece of machinery, but is severely hampered by the modifications that Samsung makes to the Android OS. I admit that the codec support within TouchWiz is impressive, but too much of the core framework of the phone is inefficient and sluggish.
Even using the latest release of unofficial firmware Samsung, Android 2.2.1 (JPY), there is still the occasional hang and the missing RAM (which is there somewhere, but not for user applications).
Samsung is mostly to blame, but there is also a quality control element that Google should be responsible for.
I have prepared an open letter that I sent to Android via Google Press and then forwarded on to Samsung for their reference. This were all through publicly available channels so will have to filter through customer service centers and the like.
I'm not expecting much, Google appears to use Amazon's customer service approach, "No customer service is good customer service".
But would like to post it here to hopefully get it out into the wilderness.
I tweeted it here http://twitter.com/#!/ibproud/status/27528781828722688
and would appreciate if you agreed with the content to retweet it. Hopefully it should give it a bit more weight.
It would be interesting to get the communities feedback on how mature they believe Android is.
Do they need to keep trying to make everyone happy or can they start to use the weight of their OS to get manufacturers to align the user experience?
Dear Android Team,
I am writing this letter to air my frustrations and to hopefully get some peace of mind that your strategy for Android will resolve some of the main issues plaguing the platform.
I have now been with Android for over 12 months. I used to be an iPhone user, but couldn’t stand the walled garden that Apple put me in. I couldn’t download directly to the phone, replace the messaging app or sync wirelessly. I went to Android because I wanted the freedom to use my phone more as a desktop replacement than as a phone/mp3 player.
When I joined the Android family (January 2010), I started with the Google Nexus One. I was so keen to get into the Android community I didn’t even wait for it to be on sale in Australia to get it, thus I hit eBay and bought it outright.
I was very pleased with the platform but could still see a few rough edges around the Operating System. It had the usability I was looking for but was lacking the polish I had grown use to with Apple. There was good news on the horizon with an Éclair update that would give the already beautiful phone a nudge in the right direction. As I was in Australia and the phone wasn’t here yet, I had to push the update through myself, after seeing how easy this was and getting the feeling of being a little phone hacker, I was hooked, I started preaching Android to the masses. Australia is still building momentum for the platform and it’s taking some time. Most of the major carriers stock between 4-6 Android devices, most of which are low end or outdated in the overseas markets.
I follow all the key players in the industry through Twitter and have a majority of Google News trackers picking up articles with android related words. I have also now converted my Wife to Android (HTC Desire Z, also not available in Aus) and I picked up the Samsung Galaxy S and gave my sister the Nexus One. The problem I face now is that I’ve run out of money and can’t go out and buy a new Android phone just to be up to date with the latest Android OS (Gingerbread), this would also be the case for most consumers. The Nexus S is so similar to my current hardware that I must be able to leverage the extra performance from the update.
But alas, we reach the major problem with the platform. Fragmentation. I’m not referring to the Fragmentation of the various app stores and apps available based on different OS versions but more to the Fragmentation of the OS based on the custom skins and manufacturer update cycles. The open platform that is closed at 2 levels, Manufactures and Carriers. I will continue to buy my phones outright as it gives me the freedom and flexibility to upgrade my plans as better ones become available. This always guarantees that I’m free from the bloatware that is preloaded on most Carrier bought phones and free from 1 of the barriers to the true AOSP experience. The next barrier is one that is running rampant in the interwebs rumour mill at the moment and that’s manufacturer updates and in my case I refer to Samsung.
Samsung Galaxy S phones come loaded with Android 2.1, most of them internationally are running Android 2.2 and just recently as select group of the devices is getting Android 2.2.1. This is now a month after Android 2.3 was released. For Samsung I would consider this largely negligent, considering they had the opportunity to work with Google to build a Google Experience Phone (Nexus S). The specs of this phone are so similar to the Galaxy range that a port shouldn’t be too difficult. I understand that there are a lot of constraints and dependencies in the development cycle that could cause delays as well as manufacturers agendas (mostly in unit sales). It is great that Samsung have sold so many devices globally but at a cost of the user experience as well as potential damages to long term retention.
I understand the Open nature of Android and the push to encourage manufacturers to put there own spin on the platform, but Android is getting bigger and more mature, it doesn’t need to be High school girl bending to the whims and peer pressure from the carriers and manufacturers.
There are a team of Devs in Germany who are working to port CyanogenMod 7 (Gingerbread) to Galaxy S i9000, but these guys have now spent over four months just trying to get through Samsungs drivers. The team didn’t start just to customise the phone but to actually make the phone work properly, I of course refer to the RFS lag issue and Samsungs modification to the framework that slowed it down. The goal of the team is to maximise the potential of the hardware and operating system.
It would be great to see some muscle from Google thrown into the mix, there doesn’t need to be requirements dictated, but maybe ethics encouraged.
There seems to be a few options here:
- Encourage device manufacturers to share their drivers, if it is too sensitive to share at least work with the community to help them do it themselves.
- Start to break down the way the platform is customised so that way the manufactures (Samsung/HTC/Motorola) skin the platform can sit a layer above the core code, thus be a quick implementation/customisation to get their skins working.
- Get each manufacturer to offer the AOSP experience to advanced users. This can be done through an agreement between the user and manufacture that states this will void the warranty and have its own terms and conditions.
- This last one is a long stretch, but how about taking all the manufacturers drivers into a repository, the way Windows do updates. When a new Android version is developed the drivers can be updated or incorporated and be packaged out through the Android SDK.
I may be completely off the mark. I’m not a developer and couldn’t pretend to know what effort is involved at any stage of the process, from building Android to rolling it out into the latest and greatest phone. The one thing I am though is an End User, a person that wants my phone to do more, to get close to being a desktop replacement.
Maybe I’m also being a bit idealistic.
I hope the Android platform continues to flourish and for it to become the Windows of the mobile era.
Sincerely,
Irwin Proud
E: [email protected]
Click to expand...
Click to collapse
It's really an excellent summary. Consider there're even more black sheeps out there. For example Sony Ericcson which ones recently made a statement like Android is their favourite Smartphone OS and left Symbian in Nokias hands.
But we found also the good ones like HTC, which every Manufacturer should have HTC as its Paragon concerning Android Software Development.
Great write-up; I agree 100%
I agree with your post fully, and concur that the Windows Phone 7 model for OS updates is more efficient, and strikes a happy medium between iOS and Android's approach to upgrades. However it is also more restrictive in terms of handset hardware limitations
I suppose the idea is that customers should vote with their wallets and buy from companies with good software and firmware support. The problem with that is a majority of phone users (android or otherwise) are technically savvy enough to take such support into consideration when looking at the latest and greatest fancy phone in a store. We could all buy the Nexus One or Nexus S only, but this too is restrictive to the customer as other phones offer more/different features
my 2 cents worth:
I agree on your points - but I'd skip the first few paragraphs if I were the one who write the letter. Other than that, thank you for making the effort.
What exactly are you hoping to achieve with this letter? Google has absolutely nothing to do with the fact that samsung don't want to update their phones. In these type of situations it's just better to vote with your wallet and buy another manufacturer's phone next time and let Samsung know why you don't want to use their phones in the future.
Writing letters like these is just a waste of time imho.
What Google should do?
Toss3 said:
What exactly are you hoping to achieve with this letter? Google has absolutely nothing to do with the fact that samsung don't want to update their phones. In these type of situations it's just better to vote with your wallet and buy another manufacturer's phone next time and let Samsung know why you don't want to use their phones in the future.
Writing letters like these is just a waste of time imho.
Click to expand...
Click to collapse
Please allow me to politely disagree. Google can do a lot about this and they have done this also. When I say they have done this - I am talking about not having Market application on Android OSes which come on non-phone hardware.
Google should put similar restrictions for loosley coupled skins, upgradable drivers. I had been giving this a lot of thought lately. I will sum up my thoughts with above letter as above:-
i) Device manufacturer skinning - Google should mandate that it should be just another APK within AOSP and users should be given a choice to turn it off.
ii) Device Drivers - Google should mandate there should be a better way of installing device drivers - similar to what we have in MS Windows (MS Windows is an excellent model of how hardware device should be handled - this lead to the exponential growth Windows is enjoying now).
iii) Android OS Update - If Google can achieve the above two, then the choice to upgrade the OS should be at user discretion. Of course, Google should mandate that there is OTA availble as an option. And obviously this OTA would be served by Google, not by device manufacturers. This would also free up time, effort and cash spent by device manufacturers in upgrading the OS.
So this is in the best of interest of everybody.
These restrictions if put in place, would free us all from this phenomena of running outdated OS.
Not sure what ti say on this one. It's true that Samsung has failed on some levels, however I must say that this is the first phone that has allowed me to get to know so much about the internals of the Android OS.
Modifying kernels, ROM's, reading about different file-systems etc... it's not a thing for the common user but I expect the people on this forum to be interested in such things.
Ok, if Samsung had done it right, we may have discussed these things anyway but it would've drawn less attention as people would not be looking for solutions to their problems.
But of course we have to strive to quality for everyone and this letter may just open some people's eyes at both Google and Samsung.
Thank you so far for the feedback.
poundesville said:
my 2 cents worth:
I agree on your points - but I'd skip the first few paragraphs if I were the one who write the letter. Other than that, thank you for making the effort.
Click to expand...
Click to collapse
Remember most members of XDA would be a cut above the average user. The reason this letter was written the way it was, was to demonstrate that I am a typical end user. Although I would consider myself leaning slightly to the more advanced side I wrote the letter based on a very general experience of the platform, an experience a lot of consumers would go through.
Toss3 said:
What exactly are you hoping to achieve with this letter? Google has absolutely nothing to do with the fact that samsung don't want to update their phones. In these type of situations it's just better to vote with your wallet and buy another manufacturer's phone next time and let Samsung know why you don't want to use their phones in the future.
Writing letters like these is just a waste of time imho.
Click to expand...
Click to collapse
What am I trying to achieve with this letter?
I really don’t know, but it helps to just get the thoughts out there.
With approximately 300,000 activations daily, I don’t think Android sees the true reflection of how their platform is received.
When the Galaxy range of phones was released in the US, they would have been seen as the closest thing to an iPhone that non-AT&T customers could get. So sales and activations shouldn’t be seen as the indicator of clever consumers or consumers wanting an open platform, but of consumers who wanted an iPhone but for the various reasons didn’t want to go with AT&T.
Remember: The international Samsung Galaxy is the only Android phone I know of that looks more like an iPhone than any other phone.
What I would really like to see is, that annually google will release a major version of Android. So V1, V2, V3, etc…. the mobile manufacturers commit to any minor or incremental updates per major version. So if Google says they are releasing Android 2.4 then they are saying to the manufacturer that this version will also work on any phone that currently supports v2.1 to v2.3.
As more and more people move to smartphones and tablets, more and more will we see hackers, spammers, botnets and so on attempt to access our devices. If we can’t have the latest updates that close any open holes then our phones become a huge liability.
Pierreken said:
Not sure what ti say on this one. It's true that Samsung has failed on some levels, however I must say that this is the first phone that has allowed me to get to know so much about the internals of the Android OS.
Modifying kernels, ROM's, reading about different file-systems etc... it's not a thing for the common user but I expect the people on this forum to be interested in such things.
Ok, if Samsung had done it right, we may have discussed these things anyway but it would've drawn less attention as people would not be looking for solutions to their problems.
But of course we have to strive to quality for everyone and this letter may just open some people's eyes at both Google and Samsung.
Click to expand...
Click to collapse
Not really sure if Samsung has failed as such, but have put too much focus on unit sales rather than quality control and great user experience. They started releasing different iterations and modifications to the same phone without considering that each minor tweak to the hardware would mean more resources to develop updates and maintain each device.
I also agree that without Samsung I would know very little about linux filesystems, kernel and custom roms, but shouldn't all of these be more to push the phone above it's limits and not to just get it working properly?
There's nothing wrong with knowing the advanced stuff, however it shouldn't be a necessity.
The problem ironically is that Android is open source. I agree wit the letter above, but I can;t see how you can stop manufacturers doing what they want.
Also the Drivers being proprietary isn't going to change and device manufacturers aren't going to suddenly start releasing their closed driver sources.
Agreed Google should stand up and restrict the Skins to a single APK that can be removed, this would stop all the associated problems with HTC and Samsung skinning too deep in to the OS that it becomes impossible to remove it. The problem with that is, then any manufacturers APK will be installable on any phone. Which is something we know they don't want.
We already know Androids biggest downfall and so does Google. Fragmentation.
I believe once Google has the strong position they want and users demand Android when they buy a new phone, they will start to put their foot down and try to enforce standardisation across Manufacturers, but until they get to what they feel is that point, we're stuck.
Anyway much luck with the letter, I hope someone who matters get's to see it.
Logicalstep

evice suggestions for demonstration of JTAG benefits

I tried to get some help in the Q&A section, but it appears this is more technical/hardware seeking question than just generic "which phone" thread.
I have been suggested Samsung Galaxy Spica/i5700 by boofman (thank you), but the device is cost prohibitive.
I would very much appreciate anyone's suggestion.
I am planning a presentation to demonstrate the benefits of JTAG for data recovery on embedded systems. The audience has approx. 12th grade education, but higher than average computer understanding.
I have most of the equipment already, including a uLINK2, Bus Blaster, and Raspberry Pi for the UART-to-USB, and OpenOCD for the software.
What I am missing is the simplest cell phone (or other inexpensive embedded device) to make the demonstration.
I would like to connect to the device and list the devices on the JTAG chain, and recover the data from them.
What cell phone brand and model would work well for this presentation?
I would need to know the JTAG points, have access to the data sheets of the onboard chips, and since it is out of my own pocket, I hope to get the phones on eBay for a low price.
Any suggestions are welcome.
huperetes said:
I tried to get some help in the Q&A section, but it appears this is more technical/hardware seeking question than just generic "which phone" thread.
I have been suggested Samsung Galaxy Spica/i5700 by boofman (thank you), but the device is cost prohibitive.
I would very much appreciate anyone's suggestion.
I am planning a presentation to demonstrate the benefits of JTAG for data recovery on embedded systems. The audience has approx. 12th grade education, but higher than average computer understanding.
Click to expand...
Click to collapse
You'd be surprised what kids know these days.
huperetes said:
I have most of the equipment already, including a uLINK2, Bus Blaster, and Raspberry Pi for the UART-to-USB, and OpenOCD for the software.
What I am missing is the simplest cell phone (or other inexpensive embedded device) to make the demonstration.
I would like to connect to the device and list the devices on the JTAG chain, and recover the data from them.
What cell phone brand and model would work well for this presentation?
I would need to know the JTAG points, have access to the data sheets of the onboard chips, and since it is out of my own pocket, I hope to get the phones on eBay for a low price.
Any suggestions are welcome.
Click to expand...
Click to collapse
Check out gsm-forum, under the hardware repair section.
Googling for jtag pins and your phone model number usually works for me. I'd assume you might have to wait a little bit for brand new devices, unless you feel like scoping the pins to find out which is which or hope their labeled.
These individuals are not kids. :fingers-crossed:
Excellent resource at the other site. Thanks!
But, I think I do not think I made myself clear regarding what I am looking for:crying:. I am not looking for info on how to JTAG a specific phone.
I am looking for 3 or 4 of the same model of cell phone that
I can pick up on eBay or similar for reasonable price (<$30/phone),
the JTAG TAP is known on the motherboard, and
it would be a bonus if the JTAG command set was known (besides the basic requirement).
This would allow me to make test run on one of the phones, then demonstrate the use of JTAG on the others.
The Samsung Galaxy Spica is a good phone, but I do not have the budget at $100+/phone. I need to find something cheaper. It does not need to be fancy telephone, or even smart phone - just have sufficient JTAG documentation.
If anyone has any ideas on what to use for this demo, I am still in need of a good idea.
You can look into any of the older HTC phones for this. I think that would be your best bet. I've done plenty of hardware repair, disassembling, reassambling, flashing, etc... on Android, & non-Android phones, & from my experience, the older HTC phones are the best. Specifically, concentrate on the GSM ones, such as for T-Mobile. Look into HTC myTouch 3G Slide (awesome little thing) , HTC G2 (one of the best keyboard phones ever), myTouch 4g, myTouch 4G Slide (overheating, self-destructing piece of crap), even the HD2 & the HD7. These are all devices that you can get for around $30 or so with a cracked, but still working digitizer, or some other kind of problem. Screens & other parts for them are very cheap as well.
Also, these are all known to RIFF Box. Look it up. You can do JTAG repair with these, & RIFF Box have all the JTAG ports labeled & documented. They might have some of the documentation right on their site, but I'm not totally sure. Anyway, check it out & see. I think this will be exactly what you're looking for.
Excellent! Thank you very much.
I have looked at looked at many commercial products, including RIFF Box. I narrowed the selections down the RIFF and ORT, but they are both very expensive for demonstration purposes.
I do love the fact that one can buy "jigs", "clips" or "adapters" (names change depending on vendors) which removes the soldering requirements for some of the phones. Except, these are still very expensive. :cyclops:
Again, thanks. I will look into these.
3ndymion218 said:
You can look into any of the older HTC phones for this. I think that would be your best bet. I've done plenty of hardware repair, disassembling, reassambling, flashing, etc... on Android, & non-Android phones, & from my experience, the older HTC phones are the best. Specifically, concentrate on the GSM ones, such as for T-Mobile. Look into HTC myTouch 3G Slide (awesome little thing) , HTC G2 (one of the best keyboard phones ever), myTouch 4g, myTouch 4G Slide (overheating, self-destructing piece of crap), even the HD2 & the HD7. These are all devices that you can get for around $30 or so with a cracked, but still working digitizer, or some other kind of problem. Screens & other parts for them are very cheap as well.
Also, these are all known to RIFF Box. Look it up. You can do JTAG repair with these, & RIFF Box have all the JTAG ports labeled & documented. They might have some of the documentation right on their site, but I'm not totally sure. Anyway, check it out & see. I think this will be exactly what you're looking for.
Click to expand...
Click to collapse
I'd go with Galaxy S 1 as it's really cool to work on and relatively well documented and demonstration on such stuff always looks well. But if you want something low-budget. I've seen JTAG pads on Nokia E50'ish stuff. Or try with some Samsung S3000's, these are pretty cheap. But I don't know how's JTAG there.
as @3ndymion218 told you , search old HTc .. also some Samsung that I think cheap could help too .
Samsung F480 , F490 , U700 , U900 etc ... some news Corby model also .. I think cheap .
I could help if you were near to me . I have 3 phones that I could offer you ...
Thank you for the further info.
Definitely will try to track down the HTC and Nokia information.
Samsung is a bit pricy as you said, but maybe down the road.
Again, thank you all!

maybe this could help HTC revive themselves

so we all know HTC is in trouble. The cellphone market is constantly moving forward and looking to the future for their next big thing. I, however, suggest that htc should take a page out of their old book and come out with a next-gen hd2. When I think about freedom in a handset, I think about this phone first and THEN android's early days. We live in a time where mainstream phone manufacturers give us a product and thats that whether we like it or not. my last 4 android phones weren't able to be rooted and so I gave up altogether. I'm currently an iphone user. Not because I think it's better but because I just gave up. I am not happy with todays offerings. I feel like phones should be more advanced now. I mean yeah there are very nice phones today with tiny bezels and crazy specs but I'm speaking more from a OS perspective. Yes pixels are nice, yes samsung has amazing phones but at the end of the day they're only still running android. Android has evolved but, in my eyes, just barely. It's still the same at its core. Back on topic, I think it would be in everybody's best interest if htc were to look back to this phone for the future. This time next year will mark the 10th anniversary of the HD2 and they're in a very troubled state right now so why not? HD3, the all new HTC HD, whatever they may call it is irrelevant as long as they just do it. The smartphone market is stagnant right now, there's countless evidence to support this claim. Manufacturers should start focusing more on operating systems than bezels. It is clearly inevitable that there will eventually be new contestants in the duopoly we have right now.
I'm not sure how to approach this but let's just put it like this. If i had it my way; it's November 2019 and HTC releases the hd3, theres a whole back to the future campaign. they trademark the phrase "the future is in your hands." it's on billboards and ads with the phone sitting comfortably in a pair of palms. there's black hands, white hands, brown hands, robot hands to show that this is the phone for everybody. it runs android by default but it is meant to run other operating systems. HTC has invested money into smaller os manufacturers and home-based devs to develop/port their existing OS. they run competitions and such for people to show off their OS offerings. Not for them to purchase and license but to show that the whole movement is about the people and their freedom phone. the device is a tinkerers dream. The app stores are limited but that isn't the point. We're approaching a time where AI is slowly eliminating the need for 6 billion apps. XDA is the go-to spot again. We need a more capable mobile OS and why shouldn't HTC be one of the first to push that with their hardware. I know microsoft will be putting out the surface phone soon and I'd be willing to bet it will run full windows 10. Why not have a legitimate early competitor to push the agenda? If I want to run ubuntu desktop or kali linux on my phone fluidly why can't I? This may very well be a niche product but it will be huge for developers and will most definitely be a big conversation. That alone would gain some traction. hardware revisions thereafter could include multiple usb-c connectors, maybe an x86 architecture, maybe modularity, maybe this maybe that. I just dream of a pocketable device that would truly feel free of restraints and I believe HTC is the one for the job. Manufacturers are always giving us what THEY think we need instead of actually leaving it up to us. Ask any savvy person what the most legendary smartphone was and they'll say the HD2, ask them why and I guarantee every answer is the same. This is something I am passionate about and I haven't slept yet and I know the format is all messed up but I just wanted to put the idea in peoples heads.
I second this motion. The HTC HD2 Leo I own is a beast. I will admit that it was frustrating at first. I must have soft bricked it half a dozen times messing with settings and software I had no business touching as I didn't have a clue what I was doing. Then I found some good tutorials and finally, the promised land. XDA DEVELOPERS FORUM.
I found that the HD2 was an incredibly versatile and robust piece of tech. I did soft brick it again a time or two, but always I was able to rejuvenate it. The downfall, I believe was Microsoft ending the 6.5 os right after release. That coupled with the power house of android and the backing and resources it had soon overshadowed the HD2. But quite a few kept a place in there heart for it. The capability of the device and the developers to modify and utilize the platform to do extraordinary things has, in my opinion, never been matched. HTC needed a flagship. They were in the pack, but had a desire and opportunity to pull to the forefront. With the HD2 they did surge ahead. They didn't fail us, the market and consumer failed them. Too many got overly frustrated as they failed to understand the accessibility and basic root to pathway to app to accessories. The various models also caused consumers, who were hearing of this wonder of Google and Android, some with the apple iPhone in hand and its "friendly yet restrictive" os, and they rage quit on the HTC.
After reading the above post, I have thought long and hard on what was, what is, and what could be for HD devices. I have several interesting observations.
1. The versatility of the HD2 opened it up to power-users, techs, devs and wide eyed dreamy technophiles like myself. The ability of the HD2 to use Java, WinMo, PPC software, Android and linux gave so many a highly adaptable device for personal preference, personalization and experimentation.
2. The HD2 could act as a PDA, Phone, PC, Diagnostic tool, Microsoft Office companion and controller... The list goes on. Yes you can do all those things with an android or apple device now, but the ability to adjust the hardware settings, application features, information export and format has been greatly handicapped by a gap between developer abilities an end users abilities. Rooting helps with this, but rooting itself is a tricky and iffy prospect. I have noticed that certain areas of focus and purpose for applications have software that does not cover everything desired, or is entirely too broad and basic to be fully accurate. I have found myself and others needing 2 or three applications to accomplish with accuracy what could be done with one openly versatile and layered 'package'.
3. The HTC HD2 is still capable of competing with most of the low to mid level devices on the market today. I can hear some of you rolling your eyes, but I stick by that statement. Even with some outdated components and slower buss and cache speeds, it can hold its own. I attribute that to the versatility.
4. The vision of the HTC HD3 MODULAR COMPONENT ENGINE. Yup. I may be insane after all. Yet my madness has reason, I am just not linguistically skilled enough in Techaneeze to put it to words. Basically, the device by itself is a fully functioning phone with the latest capabilities and trends. The average user will be able to use it straight out the box, though with multiple new options such as dual OS preinstalled, dual SD card slots, Mega More than anyone needs camera resolutions, speakers that actually work loud and clear, maybe predocked gizmos, chochkies and dodads like Bluetooth earpiece(beats me on the design so far), NFC tags or keyring fobs(whatever those are called), a hidden micro sim/sd card compartment, an actual headphone jack, plasma lighter/taser, multi use survival card, toothpick, tweezers, det-cord crimper. OK OK i am being silly, but its late and I am hungry.
The added wow factor is that the HD3 is a driver/interface for a modular expansion platform that can be customized for various trades. IT tools like frequency counter, component tester, etc.; scientific lab tools and sensors; in the field career specific tools for geologist, meteorologist, anthropologists, etc.
So far, i just have envisioned a framework buss with plug in ports for specific electronics and sensors, etc.
I will try to expand on this idea, but I am now at the point that I believe I need to poll the public. I will attempt to create an effective poll(s) at a later time when I have all cylinders firing.
Good night, and good luck!
I just stumbled on to this forum browsing xda in the new year..and as each year passes i feel sad that these HD2 forums get more and more silent ( I bot the HD2 in 2009, the year of its launch) ...strange this phone got so many people to love their device like no other, I guess people remember the joy they felt when they used it and the fact that it was probably the most modded phone on the planet....fact that it ran android marshmallow not too far back is testament to the loyalty of developers and users of this phone who never gave up on it, kept it alive and relevant .... I guess we all miss the extreme flexibility of our beloved device today, of course also miss the huge flutter of activity on the xda forums for this phone, the forums were always buzzing with something new ( ROM, app ) the phone could run or some feature that was finally made to work...so so great to see the above 2 posts in 2018, good to see activity and that people still remember this great device and are still hoping it will be reborn in some form in the future, cheers to that!!!!
Same sentiments here. I bought the hd2 on release in 2009 and it was a lovely device. I remember installing the latest Android ROMs and kernels on it, was so fun. We're at a point if perfection though, most modern devices run at well you hardly need to tinker with them anymore. My Galaxy note 9 and Huawei mate 20 pro are proof to that, these 2 phones are Android in it's perfection but the hd2 will always have a place in our hearts!
I am still amazed to see what the HD2 achieved.. I also bought it in 2009.. had loads of fun flashing it (or may i say them, i ended up having 4 of them at the same time ) whith android and windows.. I still have 2 or 3 of them laying around somewhere.. was an incredible device that gave loads of fun

Categories

Resources