i have an Inspire4G, an iPhone, and an Atrix... i have unlocked and rooted and put Cyanogen & other mods on my Android based phones that I have now, and my N1 from the past as well as others for friends.
but i fully admit, i am NO expert... i rely on those who understand the system more than i, to do what i've done.
And, i am THANKFUL for all the work you have all put in.
SO - here's my issue, the iPhone has the group/threaded MMS ability... its a commonly known issue, a common question, and run through google shows many asking for options. some Blackberry devices can join these threads, and i'm pretty sure my iDen devices back in the day could as well. but Android cannot (currently).
i have tried GoSMS and Handscent, and it seems like they are merely better front-end clients with more/different notification features that feed off a base SMS/MMS from the core system. someone please correct me if i am wrong.
so - my questions: what keeps us from joining them? is it that an app can't be written to do this because the system can't do this?
is it simply that there is no way to modify the base Android system to handle this, and we all must wait for Google to include the needed code or libraries to do so?
is there not a... 'standard' or maybe available code from other systems that could be applied to the current base SMS/MMS system to allow for grouping in some way?
i ask today because the majority of the people in my world are iPhone users, and now that Group Messaging is active by default in iOS5, its becoming used more and more... to a frustrating level. i originally thought it would be as simple as waiting for GoSMS to thread the incoming texts, but as i've tried various options and apps it seems they're all based on something limiting.
and i'd like someone who knows more than i to explain (hopefully in simple terms) what keeps Android from adding what seems to be an old ability, really so i can know if there's hope for a change soon... or if its not even possible. hell, maybe this will come in ICS/4.0, or maybe its not possible.
again, thanks to all the devs - if it weren't for your skills and work, none of us would have the great devices we do.
Related
i posted this in another forum, thought i'd see what our brains together can think of.
An app that allows us to use SMS with voip services like voipbuster. Similar programs have been created for pocketpcs (SMSoIP, IPSMS) but will not work for smartphones. Find this idea extremely useful as you'd be able to send text messages for essential nothing at cost. Does anyone know if there indeed is a program like this for smartphones, cause i know currently people are manually logging in using their browsers. Those programs mentioned above are extremely small and incoporate your contact list, which is amazing and efficient. Wish there were something similar for us smartphone users - hopefully this inspires someone
Hi pals
As many apps developers here on XDA what I develop and publish on Android market is device-specific.
(Free and Commercial)
Those apps
- require certain hardware features (like an Audio codec, Super AMOLED screen & driver), often related to additional Kernel features.
- can only support a limited set of devices but also Kernel versions.
And like everyone I'm really annoyed by 1-star comment.
"pure crap, doesn't work on my beloved phone"
Of course, it's not the majority, but its always increasing with the popularity.
It's annoying when its free apps, but when you decide to sell apps and try to give the best service, it becomes really bad.
And people disappointed is really not what you hope when you share your creation.
This is why I'll appreciate some backup from you by leaving a comment on this thread named
Missing filter by Build.DEVICE and ability to contact customers from comments
I propose the idea of filter by Build.DEVICE because it's useful for my app. You need additional filters too right ?
By custom ROM? By Kernel version? Explain you needs
− in this thread on official Market forum of course - writing your comment here is nice too.
We are all used to an unprecedented level of user support here on forums, by the hackers themselves or the community of users. This is really something special.
Its maybe a bit bold to say that, but I'm sure Android Market has a lot to learn from communities like ours in order to improve its consumer satisfaction... so lets show them how to
PS: sorry for inviting people to another page (Google's one) at the occasion.
This is, I guess the best way to be heard by them: by posting on their dedicated tool for requesting features (they'll read)
supercurio said:
I propose the idea of filter by Build.DEVICE because it's useful for my app. You need additional filters too right ?
By custom ROM? By Kernel version? Explain you needs
Click to expand...
Click to collapse
Filtering by ROM / kernel is way too specific, but by device is great. I support this proposal.
this would be an incredibly useful feature for developers on XDA. since many hobbyist developers put an app that only works on the device they're developing it for, it would make sense to be able to whitelist or blacklist certain phones so they can be restricted to certain phones.
for instance, I'm sure the developer of RealHDMI (the Droid X HDMI mirroring app) would have loved this feature when people with EVO's were trying to install and were (not shockingly) unable to use it and giving the developer negative feeback. for a community such as this, I can't help but see how this could be an amazing addition to the marketplace.
I don't think its realistic. Google may well come round to a warning message (after accepting permissions perhaps?) saying 'your device is not supported'. This would help in situations such as the Android 2.1 Galaxy S's inability to play ball with Skype, and various games that don't support or fully support some chipsets, as well as your own, very real, problem.
Filtering per device will only pave the way for more fragmentation jibes and claims by Apple/Microsoft that Google are inflating number of apps available. We have to remember Google's priorities: PR > OEMs > Developers > Consumers > Facebook. They *need* to stop any fragmentation claims and *need* to boost app numbers in line with App Store, all to prevent counter PR.
HazzBazz said:
I don't think its realistic. Google may well come round to a warning message (after accepting permissions perhaps?) saying 'your device is not supported'. This would help in situations such as the Android 2.1 Galaxy S's inability to play ball with Skype, and various games that don't support or fully support some chipsets, as well as your own, very real, problem.
Filtering per device will only pave the way for more fragmentation jibes and claims by Apple/Microsoft that Google are inflating number of apps available. We have to remember Google's priorities: PR > OEMs > Developers > Consumers > Facebook. They *need* to stop any fragmentation claims and *need* to boost app numbers in line with App Store, all to prevent counter PR.
Click to expand...
Click to collapse
Its not by ignoring facts and developer needs that you prevent fragmentation.
Youtube: RealTime UI - New Phone Interface Concept
Hey! So I made a video that shows what I feel like the future of mobile devices and phones should be. Perhaps this can be made into a new launcher or a special version of android... Essentially it merges Android notifications with iPhone spotlight and some webOS elements. I hope to get feedback on this idea so knowing xda, I am pretty sure I will get many great responses here.
Let me know what you think! Would love to hear from you guys! Thanks!
*Also feel free to share and repost!
First, almost all your ideas can become reality developing a new Launcher, but it'll require a lot of very hard work, since you'll need to develop the launcher and the clients for the social nets.
However, merge the Android notifications with your concept will be an impossible task for a Launcher. You can hide the status bar, but you can't manage the notifications (in an easy way, you only are allowed to delete your own notifications, you can't delete the notifications that other apps puts on the status bar).
Overall, you have an atractive idea for many users (although not for me, I don't need social nets on my phone hahaha).
Best regards.
RoberGalarga said:
First, almost all your ideas can become reality developing a new Launcher, but it'll require a lot of very hard work, since you'll need to develop the launcher and the clients for the social nets.
However, merge the Android notifications with your concept will be an impossible task for a Launcher. You can hide the status bar, but you can't manage the notifications (in an easy way, you only are allowed to delete your own notifications, you can't delete the notifications that other apps puts on the status bar).
Overall, you have an atractive idea for many users (although not for me, I don't need social nets on my phone hahaha).
Best regards.
Click to expand...
Click to collapse
Thanks! Perhaps a whole new OS would be the best solution.
Maybe modifying some system files, not the entire SO (as a beginning... )
RoberGalarga said:
Maybe modifying some system files, not the entire SO (as a beginning... )
Click to expand...
Click to collapse
Haha true that! Wonder if making a custom ROM with all this would be in the realm of possibility..perhaps someone would have some insight!
It does seem like a great idea, but perhaps targetting only those who primarily use their phones socially... I, personally, don't really use even the basic social apps on my phone (perhaps only whatsApp, and twitter when I'm reeaaally bored ). It seems to me, that you are gonna target a community that goes social network crazy on their phones (half the girls in my school )
I’ve been a CyanogenMod user since CM6 for the HTC EVO. While I can’t claim to have contributed much directly to the community (I’m no developer and more of a sys admin kind of guy), I have installed CM on countless phones over the years - basically any friend or family member who sat their phone down long enough. As soon as it was available, I snagged a OnePlus One, and it’s still the phone I have today. While I was initially excited to see where the foundation of Cyanogen Inc. would take the project, I’ve become increasingly disappointed with the direction that things have gone (both CM and COS), and I think my next phone will likely be a Nexus device with stock Android. I’m fairly certain that this post won’t accomplish much (aside from starting a flame-war/trolling/what-have-you), but I thought I would post it just to see what might come of it.
What I initially loved about CM was the fact that it added a number of useful features to stock Android, it allowed a ton of functional customization, it seemed to be more efficient and stable, and it let me continue to update devices that manufacturers had artificially sunsetted. I was impressed by the fact that lead developers were more interested in code quality and security than by shiny features. Amidst the desire to make Android better, there was also a sense of perfectionism to CM as evidenced by the “don’t ask for ETAs” mantra - it would get done when it was ready, and I was always willing to wait.
When Cyanogen Inc. formed, I was curious to see how they planned to make money. I actually decided to be a bit bold, contacted Kirt and Steve via LinkedIn, and offered to share some of my ideas. One of my biggest suggestions was that they should do something to fill the gaping hole left by Blackberry. At that point (and even still today), no manufacturer had really been able to provide the enterprise-grade functionality provided by Blackberry and BES. MDM solutions were (and are) a double-edged sword that are really just a patch for the solution. Given the huge priority that Cyanogen placed on security, I thought it would be a good direction to take. I’ve sent a few other suggestions over the years (including attempting to get the OnePlus One on the shelves at Walmart when I worked at the corporate offices), but it never seemed to go anywhere.
Right now, when I wake my phone, I have a reminder that there is a system update ready for my OnePlus One that will install COS 13.1. This update adds “new mods for Cortana, OneNote, Microsoft Hyperlapse, Skype, and Twitter.” I have yet to hit install. My issue is far less that Cyanogen is working with Microsoft and more with the fact that the company, much like Canonical/Ubuntu, seems to have the not-invented-here syndrome. (Side note: here’s a great article from the Turnkey Linux team that serves as partial inspiration for this post https://www.turnkeylinux.org/blog/ubuntu-not-invented-here-syndrome). Instead of offering new and useful features, Cyanogen is reinventing wheels and cramming the OS full of things that aren’t really at the top of anyone’s list for issues that could be solved or features that could be added. The innovation just seems to be gone. Most of the features that were exclusive to CM and drew me to the project are now part of stock Android. It makes me wish Cyanogen had taken up Google on their $1B offer.
Here are a few examples. Who remembers when ADW was the stock launcher of CM? I do. In contrast, who actually uses Trebuchet? I think it’s a featureless piece of junk. No gestures? No ability to hide icons in the drawer? No useful functionality that really sets it apart from other launchers? Why develop something new just for the sake of doing it yourself when it only provides basic functionality? Right up there with it is the File Manager application. There are plenty of other more feature-rich applications on the market, and I frankly never use the app provided by Cyanogen because it isn’t nearly as functional as something like ES File Explorer.
Similarly (but more egregiously), is the Browser application. Show of hands: who uses the browser provided in AOSP? No? Me, neither. Be it Chrome, Firefox, Opera, or something else, no one uses the browser built into the ROM. Why did Cyanogen feel the need to create another browser that lacks functionality, is rarely updated for security patches like mainstream offerings, and is basically just another piece of lint on everyone's phones? I fail to see the innovation, there.
I initially loved the idea of having a Cyanogen Account because it was pre-Google Device Manager. However, now that Device Manager exists, I don’t see a reason to use my Cyanogen Account because there haven’t been any additional additions to the feature set. I emailed Kirt and Steve once about potentially folding the WebKey project into Cyanogen and linking it to the Cyanogen account. That would provide remote access, remote file management, a remote shell, and countless other features (most or all of which could be made to work without needing root if baked into the ROM). How much would that add to the ROM and set it apart from other offerings? Neither Google, Apple, Microsoft, or Blackberry have anything close, and it would be a game-changer.
The Themes engine. Alright, so some may disagree with me, here, but I don’t really care about theming my phone or my computer. For me, that was cool back when Compiz/Beryl were the hotness for Linux. Now, I’m more interested in function over form. Why spend so much time building this thing when there are actually useful additions that could be made to CM/COS?
In conjunction to this, there are a number of features provided by CM that are now part of AOSP and make me wonder why I'm still on CM/COS. Google has added permissions management. They have included tethering. The majority of Developer Options are baked in. They switched the whole tap/long press to turn on/off/open settings feature in the notification panel. There isn't much to set Cyanogen apart, anymore.
Instead of just complaining, I wanted to start a list of things that I really thought Cyanogen would have provided by now (or would have at least considered). Some of these would provide Cyanogen with a revenue stream so they wouldn't have to keep cozying up to Microsoft, something that I'm sure most of us would appreciate (does anyone actually use Cortana?) I’d be interested to hear what other features the community would like to see added to CM/COS:
WITHOUT root, implement NFC tag actions that are available with the screen off. For example, allow a user to unlock/wake their phone, turn certain settings on or off, switch to a different profile, or perform a set of pre-defined actions by tapping a NFC tag. Obviously, there would have to be some security mechanisms built in order to whitelist trusted tags so the functions can be used with the screen off, but I’ve always wanted to be able to set my phone down on a tag at my desk and have it automatically connect to my company’s WiFi, put my phone on vibrate, etc.
Partner with an existing developer or independently build parental controls into COS.
Add a login manager for public hotspots to accept terms and conditions on subsequent logins after the first connection (would need to use MAC address, GPS, or some other unique identifier since some companies use the same provider, e.g. Starbucks and McDonald's both use ATTWiFi as their network name but have different captive portals)
Make a Kiosk version for customers at coffee shops and the like.
Create a mobile pay kiosk version similar to the Chili’s tablets since Cyanogen is known for security.
Make a version tailored toward the elderly (lock certain features, provide a restricted set of capabilities that are easy to access, etc).
As previously mentioned, build in WebKey or similar functionality that is tied to a Cyanogen account.
Include Tor without needing root.
Allow the ability to modify DNS settings.
Develop AirPlay compatibility for the Cast feature.
Right now, I’m at the point that I was at with Ubuntu about five years ago. Canonical had “improved” Debian into a bloated nightmare complete with in-house developed projects such as Unity, Ubuntu One, the Ubuntu Software Center, Mir, and others that no one asked for or wanted. If Distrowatch rankings are to be believed, Debian (and Mint) is now more popular than Ubuntu, likely as a result of Canonical’s decisions.
This is not a call to arms but rather a suggestion. Perhaps it is time that the community creates, by way of analogy, a Cyanogen Mint. Maybe we need to go back to the foundation of AOSP just like many users have done by going back to Debian. For me, at least, Cyanogen isn’t satisfying the same needs that it did two years ago, and I’d like to have a mobile OS or ROM that does. There are a lot of custom ROMs out there like Paranoid Android, AOKP, and OmniROM, but they are incredibly fragmented in the devices that they support, and none of them have the level of backing that Cyanogen gained. Perhaps as a community, we need to consolidate our efforts, focus on a common project, and bring forth a high-functioning ROM that can fill the void that Cyanogen no longer does.
In light of today's news about the layoffs at Cyanogen, thoughti might bump my thread to see if anyone would be interested in joining this conversation.
Hi everyone,
Here is a little history first. In 2014 I helped develop a traffic counting app for an engineering buddy. I designed the UI's, the flow charts and wrote the 275-page illustrated, developers manual. The developer had it working in less than 6 weeks, thanks to, as he said, "to the awesome documentation provided". The app has been in use since then and has worked flawlessly on the original 24 tablets I originally purchased for him.
Recently, we have been asked to bring the app to a wider audience so, my question is, "Is there a way to prepare an image of the Android OS containing only the setup we need, and then clone it to the new tablets?" The app is designed as engineering tool and is not listed through Google Play and as such, it does not require most of the bloatware found on the new tablets. The app does require the use of photos, some file management along with network connectivity to send and receive the various data files required and produced by the app.
I have limited experience in rooting, but I have been successful when I done it on my Samsung phones.
As a certified Graphics Designer/Windows and Mac tech/COVID-19 survivor (nearly killed me, literally...LOL), I am aware of the amount of work that goes into aiding people with their "little" projects. Any help or direction in this matter would be deeply appreciated.