Why do ROM devs include telephony apps in custom ROMS for non-telephony devices? Even Samsung, in their great wisdom, included all of the telephony apps on my Galaxy Tab S (SM-T700). This device is NOT capable of making phone calls, period! I've installed about 15 different ROMs on several different devices, including a Kindle Fire, and they all had telephony apps.
I would think that if one is going to all the effort to create a "custom" ROM one would *customize* it to that device, and that would include gutting it of all unnecessary cruft, and crap. I know how to delete all that stuff and it's one of the first things I do after rooting. But why should I even need to do that?
Am I missing something here?--possible. Am just a dumbass?--again, possible. What I am NOT is a n00b...I've owned and modified and tweaked and broke and fixed numerous PCs since 1983. As well as several android devices over the last few years.
Just so you know, I have all the appreciation and respect in the world for the real experts who do the hard work and provide the fruits of their labor to all of us for free. All they ask is that we make the effort to find the info on xda [use the search function and your brain] and other places ourselves--of course there is nothing like a simple Thank You to show appreciation.
Thank You, TiTiB (tweak it 'til it breaks Galaxy Tab S SM-T700
TiTiB said:
Why do ROM devs include telephony apps in custom ROMS for non-telephony devices? Even Samsung, in their great wisdom, included all of the telephony apps on my Galaxy Tab S (SM-T700). This device is NOT capable of making phone calls, period! I've installed about 15 different ROMs on several different devices, including a Kindle Fire, and they all had telephony apps.
I would think that if one is going to all the effort to create a "custom" ROM one would *customize* it to that device, and that would include gutting it of all unnecessary cruft, and crap. I know how to delete all that stuff and it's one of the first things I do after rooting. But why should I even need to do that?
Am I missing something here?--possible. Am just a dumbass?--again, possible. What I am NOT is a n00b...I've owned and modified and tweaked and broke and fixed numerous PCs since 1983. As well as several android devices over the last few years.
Just so you know, I have all the appreciation and respect in the world for the real experts who do the hard work and provide the fruits of their labor to all of us for free. All they ask is that we make the effort to find the info on xda [use the search function and your brain] and other places ourselves--of course there is nothing like a simple Thank You to show appreciation.
Thank You, TiTiB (tweak it 'til it breaks Galaxy Tab S SM-T700
Click to expand...
Click to collapse
I'm not a dev but it would be my guess that these are included because they are part of the source direct from Android or AOSP. Removing them would probably break many things and cause considerable problems.
Evolution_Tech said:
I'm not a dev but it would be my guess that these are included because they are part of the source direct from Android or AOSP. Removing them would probably break many things and cause considerable problems.
Click to expand...
Click to collapse
I always delete them from my devices [non-telephony type] and have had zero problems. In fact, it frees up RAM and processor resources. I don't recall the names of the folders and files I delete, but I recognize them when I see them...anything with "telephony" or "SIM" or "phone" [NOT Phonesky, that's a Google app that will break Play Store if removed, as I eventually realized]. They are (where) in system/priv-apps and data/data.
Anyways, this is just something I observed and am curious about. I wonder how many folks have those apps on their devices that don't need them, and they are low on resources. Maybe this will prompt a discussion and create awareness. I don't know...
TiTiB (tweak it 'til it breaks ∆ Galaxy Tab S
Related
Hi all,
I have a concept for a single update application that would be driven from the AndroidSPIN release database so all developers could use it for ROM, Themes, Applications and anything releases to devices.
If you wouldn't mind taking a couple of minutes to read this post, I would greatly appreciate it.
http://www.androidspin.com/forum/viewtopic.php?f=260&t=226
I'd really love to get a group together to collaborate and either help design this and/or write an application and back end to do it.
Let me know what you think.
Thanks
Simon
Sounds like an awesome idea, I'd love to help any way I can, but I dont fit in any of the needed positions for the post. Looking forward to see what develops though
Fantastic idea!
I only ever use XDA so god knows what I'm missing out on elsewhere and to be honest after searching the word android on google and trawling through one crap site after another becomes tiresome so hence the 'XDA only' policy.
Sorry I can't offer any programming skills but you have my support on this project whole heartedly, not that it counts for much I know buh MeH!
Hope you can get this off the ground.
As I mentioned to Simon already, I was thinking about building an update application for my ROM. I love the idea of having an on-phone ROM database, update capability, something that can easily be used by any developer in the community.
Some initial thoughts on functionality:
- Browse ROMs
- Download ROMs to SD Card
- Monitor specific ROMs for updates
- Monitor currently running ROM for updates
I'm willing to lend a hand on the Android side of things, but this will be a large undertaking and we will also need some people to contribute to the UI, server side of things, etc.
I do iPhone UI design for applications now (I don't have an iPhone, but most of my contracts and clients are iPhone based), but let me know and I can whip up anything you guys need UI related.
Send me a PM and I can get the ball rolling on how the functionality can be laid out as well.
Even tho I know I wouldnt be able to help out with this. I know I would love to test this out if you needed it.
Its a great idea!!!
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
michinohatoresu said:
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
Click to expand...
Click to collapse
Well, we can reuse a lot of code from Cyanogen updater.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Well, of course.
If anything else needs doing, however, I volunteer what spare time I have.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Could be easily done, would require quite a lot of laborious work ripping out all the stuff you wouldn't need though.
I would take a look at this but unfortunately I have another Android project on at the moment which is taking all my development spare time.
@SimonNWalker What sort of backend having you got going? REST? SOAP?
Ups wrong theread
not that it matters (since i kept the source 100% open)....
you have my blessing to tear the cmupdater to shreds if it will give us a unified solution to all our ROM cravings
firefart has done a good job of keeping the code pretty clean so there shouldnt be too many issues with grabbing it
and the new code for the screenshots for themes could probably be used to the advantage of this project with ease
I'm not really interested in a rom updater, but a market replacement with an "upgrade all" feature (à la apt-get / yum) drawing from multiple repositories would be most exciting.
The Cyanogen updater could be used, it just needs some modifications. Stuff like sub-sections and update all
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
The only other method I would consider, besides JSON, is an advanced and well thought out web-based form that the developer is forced to complete upon uploading a ROM. This would place more burden on the server, but should be relatively easy to attach the provided ROM information to the rom database.
Think: Check boxes for firmware compatibilities, check boxes for device compatibilities, version number, change log, etc.
Maybe something a little like this?
Wow this would be/ is gonna be awsome!
I would suggest also that you can backup your sd card settings (and maybe also sms...) to an ftp server (or some other server you can install on your pc) from this app...
like (incremential) backup>partition>wipe>install update>boot>getbackupback
problem is to get the server adress back after wipe. maybe stored in web database and encrypted with phone imei number? or uploaded as google
whatever...
or just not wiping that single adress
just saying ^^
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
JSON is just a file format. The CM Updater works via a static JSON file that gets updated manually. The way I'd design this (which is what I asked a couple of posts back) is a dynamic web service (probably REST based) which delivered JSON dynamically. Wouldn't be too difficult at all.
As SimonWalker said he's using PHP + MySQL I'm guessing that's already being done.
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
senab said:
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
Click to expand...
Click to collapse
I know it is open and I don't need to give my blessing for people to use the source. I did so because a lot of people don't feel comfortable using other peoples code without permission, regardless of whether or not its 100% open source.
And as for the 'credit crap'... I don't see you asking for your name to be removed from the 'about' section of the app
I am not asking for any credit
Anyway, lets not get off topic...
Guys, before this becomes Android Open Alliance, the sequel (you all remember how that went), I think we better set up a way to work together first and then toss in the speculative stuff later.
How about starting simple; set up a wave?
Has anyone thought of making an XDA Market App that the ROM developers could put their ROMS in, ROM Updates in, Custom Applications, Themes, etc? I would think it could be hugely popular, and a good way to distribute ROMs/Apps which are specific to our forums.
Broken into categories, searchable, very similar to how Verizon Market works (by piggy backing on the Market app) or even as a completely separate app? Would 'bake' into ROMs nicely.
Would be a nice way for devs to get feedback on their apps, and could even integrate bug reports (complete with simple logcat dumps!)
Just a thought. I have zero Java experience so I can't do it myself.
I've always wanted the same thing. It's overdue if you ask me.
+10
Would be an awesome app.
It could in theory be setup with aptoide if it allows you to control what it looks for and downloads (meaning something other than .apks). I'm not sure if it does though.
Edit: Well it's open source, both the app and the server. So in theory it could be made to do anything. ha.
This topic would probably be better suited for the Android Software Development threads. I know a lot more Android users besides us HTC Hero users could benefit from this. Definitely a great idea though.
flipzmode said:
It could in theory be setup with aptoide if it allows you to control what it looks for and downloads (meaning something other than .apks). I'm not sure if it does though.
Edit: Well it's open source, both the app and the server. So in theory it could be made to do anything. ha.
Click to expand...
Click to collapse
Looks like it could be a good starting point. Would have a lot of the 'framework' already setup and could therefore be modified to fit specific needs of the ROM devs. (logcat dump, bug reports, etc)
This wouldn't even make sense to restrict to CDMA Hero either; GSM would be right at home as well, especially for non-ROM devs who are making apps/widgets/themes/etc.
So I have thought about this for a long time. There are some great custom roms/mods/hacks out there. But even they can lack features or have features you don't want.
I mean like choosing individual options that show up in the settings menu, etc...
Isn't it possible to have some source code that contains all the features of all the roms, and have an application that you use to design your own custom version of that rom. Say I want to fix my homescreen to have 4 screens and each screen to have its own background image... If we could just hardwire that capability into the OS via a custom designer/compiler off the source code, and flash it to the phone, that would be awesome...
Maybe that is asking a bit too much, but it seems possible. Although I am on the lower end of the spectrum when it comes to coding and modding, so I may just have no idea what I'm talking about. Maybe there are others out there who have thought of this, or are working on it, or maybe it already exists, but anyway... Just an idea...
Kinda hard with all these different devices and UIs, making compatibility an issue.
Ummm there is an app that lets you have different wallpapers for each home screen
ya... I mean it would have to be restricted to certain devices or something... but i dunno... just a thought.
If only every phone company only released 1 or 2 models.
Sent from my HTC Incredible S
govindadas said:
So I have thought about this for a long time. There are some great custom roms/mods/hacks out there. But even they can lack features or have features you don't want.
I mean like choosing individual options that show up in the settings menu, etc...
Isn't it possible to have some source code that contains all the features of all the roms, and have an application that you use to design your own custom version of that rom. Say I want to fix my homescreen to have 4 screens and each screen to have its own background image... If we could just hardwire that capability into the OS via a custom designer/compiler off the source code, and flash it to the phone, that would be awesome...
Maybe that is asking a bit too much, but it seems possible. Although I am on the lower end of the spectrum when it comes to coding and modding, so I may just have no idea what I'm talking about. Maybe there are others out there who have thought of this, or are working on it, or maybe it already exists, but anyway... Just an idea...
Click to expand...
Click to collapse
I completely understand what you are trying to achieve over here. But there are various factors in place. You are trying to make a kitchen more advance so we can fully customize it but it is not possible with the number of device that are out there and the number of processors. Its not impossible but quite hard to achieve
I am very pleased with the thought and don’t feel like adding anything in it. It a perfect answer.
robertsmigel22 said:
I am very pleased with the thought and don’t feel like adding anything in it. It a perfect answer.
Click to expand...
Click to collapse
Which answer.....?
Android with a WebOS UI=Better than Sense.
that's a good idea actually.
Well, I mean, start with one phone model on a specific carrier that is very popular among developers and general users. If a large number of people who work on mods/roms and other customizations got together... then they could probably whip up something.
But, yeah... doing it for a large number of phones would be very difficult...
but starting off simply, could slowly add in features, or a select your phone and carrier type thing...
In other words, an xda phone. Well gluck rounding up the devs to a particular phone.
$1 gets you a reply
Great
Thank you for your work
Kailkti said:
In other words, an xda phone. Well gluck rounding up the devs to a particular phone.
$1 gets you a reply
Click to expand...
Click to collapse
So everyone should get an HD2?
that's a good idea actually.
I really would like to see a newer HD2 like device. I mean like the phone that runs everything. but those come with time they aren't made that way
It's not impossible. I mean it would take a lot of time to complete but you could do it device by device. First you achieve the idea within 1 device. Combine all the roms and put features together and maybe if you add a UI to the application End Users can pick the features they want and tailor their own rom. Developers instead of updating roms they'd add new features to the application. After that you could combine phone's from the same company. Like the Sony X10 & X8. They're not that different and porting won't too hard. And then eventually you get to a General app. Some phones have some features other don't but it'd be just like Market. Some apps are compatible with your phone some aren't. It's a good idea~
Sent from my X8 using XDA App
That's a good idea actually.
What about a GUI rom "cooker"? Devs build their standard roms, but let the end users crunch them through a GUI that lets the users filter what little things they want or dont want to keep in the rom. GUI then repackages it and then we flash it.
Skv012a said:
What about a GUI rom "cooker"? Devs build their standard roms, but let the end users crunch them through a GUI that lets the users filter what little things they want or dont want to keep in the rom. GUI then repackages it and then we flash it.
Click to expand...
Click to collapse
Ya, thats pretty much what i mean. So you can choose what options show up in the settings menu, completely customize the power/lock button menu and actions, etc...it seems like it should be possible. Just take a highly customized rom and create an intetface to remove features and compile it. It could all be done in the cloud and notify you when its ready for dl.
Hi, I was wondering if there was a list of HTC One S (Ville) Build.Prop tweaks. I did some searching and saw some lists in other forums, but I wasn't sure if the build.prop was the same for all devices, I guess I'm assuming not as some organizations are totalitarian and such.
In any case, I think we should create a list of build.prop tweaks specifically for the One S that are very effective, saying what the tweak changes and how it effects the device, also what other settings you can give it and what those effects do. Maybe I'm thinking of to much information, but I think a lot of people would be interested in the other information as well.
Maybe I just don't know enough about the build.prop file yet, but if someone could give me any links about more information on it that would be great. Or if anyone has a link to a list already like this that would be great as well. Sorry if I'm being a noob, but I've done quite a bit of searching and haven't found anything yet.
Thanks in advanced for any posts,
Cobra
It doesn't matter which phone, android is android.
But everyone uses other build.prop edit's, there are no original one's..
Thanks for that information.
So if there aren't any original ones, are there possibly ones that work well specifically for the One S? I know the Fast.Dormancy one is supposed to be effective for some carriers. And though, this may be a setting that could be effective for many devices, does it not make sense to maybe start a thread or some sort of page listing all the settings that effect this device in particular in certain ways and which carriers they work effectively on?
I ask these questions because, yes I am a newb and I feel like these things could be helpful to other noobs. it's almost as if I'm trying to learn some sort of ITIL based thing I guess. I guess to me it just seems effective to have a list of things that can help make your device work more effectively. For instance, have one page, say the wiki, linking to different things to help you setup your phone how you want it, and to make it so it will work as effectively as you want it for yourself.
Now I realize that the Wiki currently has things such as how to unlock, root, flash roms, lists of roms, etc. But, it doesn't really say, "Hey, here are a list of things you can do to make your phone more efficient without having to flash a new ROM, and here are ways you can make your own ROM, here are some paths to certain things specific to this phone.
I know the Wiki is new, but I guess what I'm saying is if nobody else is working on this stuff, can someone give me a hand in finding all this information so I can start adding it to the Wiki?
So I am going to post this here, because the development section is ferboten to people trying to offer useful suggestions. Geez, I hope this is the right section.
Let me set it up. ANDROID IS BASED ON THE LINUX KERNEL. Everything, and I mean everything after that fact becomes android and bloat. Given this as the basis of all things android, I have a simple set of guidelines that should be used to create a solid, reliable, bullet proof operating system for devices able to use the android operating system.
#1. Create the kernel boot section of the basic platform that supports the very basic hardware features, including touch screen, radios, power/charging/battery management, wifi, bluetooth, nearfield, audio, microphone, s-pen,etc. Basics only. Root access is standard and can be turnd on/off just like developwer functions. No special tricks or addon hoops to jump through.
#2 At this point STOP. Every single process or service to be run on the device from this point forward should be able to be individually selectable - or not. Yes, I understand that individual services or apps may have dependancies to other processes and that thouse need to be functional in order for a particular app to work. That is why, each additional service or app must list the dependencies and in the selection process, the installion will be required to verify you have the proper services installed and functioning, if not to list them and allow you to make the decision to proceed. Viola, we have NO MORE BLOAT WARE.
#3 Make selecting additional services/apps selection process a menu driven, tag selectable process. Make the unselection process smart to verify and identify the other apps dependant on the item you are killing/removing.
#4 Allow a built in snapshot option to capture the entire system as you have customized it for yourself and allow it to be backed up to external memory with the ability to bring it back, AT WILL. With no big hassles.
Those 4 items are a good start. By themselves alone, it would put all of us in the drivers seat of controlling and living with our devices.
I am aware that such a system is not for everyone. It does require some basic technical understanding of the process. But for the vast majority of users, I am certain, that an a la carte system is far superior to the bloated monstrosities being forced down our devices.
I would appreciate any refinements to my suggestions.
The silence is deafening. It has been days. Kind of says something, don't you think?
I am so very happy (not) that these boards a compartmentalized to the point where you can't get through.
Pretty much a waste of my valuable time, especially considering the fact that if my suggestions where applied, people would be clamoring for an installation with those features. I guess there is not much true "developer" in xdadevelopers anymore.
Funny guys, with the pay to remove ads spam here. Really? Why? For what.
I leave here disappointed. Not angry. Just sad.
I'm not a developer so I have nothing valuable to contribute to your suggestions in your original post but I can offer an observation regarding your perception of the level of contribution to your thread and that is the fact that is particular area of the forums probably isn't the ideal spot to have a discussion such as this. You figured that out already so sure you can call me Capt. Obvious if you wish but I'm just pointing out that yes the forums are compartmentalized (as you've stated) in such a way that development for each device is separated out. This development is centered around AOSP based ROMs or "stock" ROMs (using manufacturer released source) so if you're looking to have higher level discussions about what AOSP should look like then deep down at this device specific level probably isn't where you want to be. So there's that . . . then there's the fact that for this particular device you can basically hear a pin drop in the sub-forums as it is since nothing much is going on by way of development.
Where specifically such a discussion would see more input I'm not sure, perhaps the main general discussion section?
Thank you for your sobering reply. I get frustrated. Already had my post bounced out of "wrong" forum while trying to speak directly to "developers" (i wanted air quotes because the term does not accuratly describe its target) So I tried this. The note pro 12.0 is still the best hardware giving the ipad a run for its money. The problem its monkeyshines kiddie software running it, or not running, or barely running it. ANDROID, indian word for crappy wannabe software, developed by clueless kids.
Again, thanks for the gentle nudge. I appreciate someone willing to conduct a conversation
Are you looking for an Ubuntu or SUSE type of setup?
I think what you are looking for is similar to apt-get type of installs, I could be wrong of course. This might be helpful for many "users". I think one of the barriers is that there are slight differences between the models of tablets, and creating the logic to put in for the sub-dependencies might prove problematic. You might get more answers to this possibility by asking one of the developers directly and sharing with them. Not a developer myself.