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?
Related
What I mean is, it seems to me that it would be more efficient to put any/all files that may be upgraded as packages and instead of flashing cooked roms, we could flash a generic rom and uninstall old/reinstall new packages
Am I making sense to anyone?
I understand you
I believe this is part of what chefs who create "lite" or "unbloated" or "clean" or "naked" (in Garmin's ROMs) are trying to achieve.
I personally like the idea, and hope we see more of them.
My personal favorite ROM of all time was the very first Hyperdragon III
mbarvian said:
I understand you
I believe this is part of what chefs who create "lite" or "unbloated" or "clean" or "naked" (in Garmin's ROMs) are trying to achieve.
I personally like the idea, and hope we see more of them.
My personal favorite ROM of all time was the very first Hyperdragon III
Click to expand...
Click to collapse
Up until recently the problem has been that cooks either created loaded ROMs with tons of stuff added to them, or lite ROMs, where they stripped this out.
The issue was however that it is quite easy to strip things out of a ROM. Making CAB packages out of those stripped out files however can be one of the more time consuming tasks and cooks didn't always offer those packages. In addition, CABs which were made available from other sources weren't always packaged in entirety and wouldn't always install.
Cooks have been getting better at this recently however. My new set of ROMS follows these concepts precisely:
http://forum.xda-developers.com/showthread.php?t=429117
I have been calling and advocating for this too basically since the dawn of UC
Previously I didn't post much under different nick, but I have "put up together" this concept in THIS thread finally, albeit with somewhat misleading "temporary" title, but it is good discussion if anyone is interested.
Granted, few apps have to be cooked-in in order to function properly, but those are really just very few. But as you can read there, most objections against this kind of "real lite" ROMs (where any "upgraedable apps" are NOT cooked-in) come from people who don't understand it, or don't know much about UC or Sashimi (BTW I'm for UC rather than Sashimi because UC is much easier for any newbies), or just don't know/have no clue how it works and are affraid it would make troubles to them if they don't have the same apps cooked-in.
Perhaps any of you could add your input there, since there isn't much sense in starting new thread about basically same thing.
Bengalih, I will test your ROMs with pleasure when I have bit m,ore time (or actually a second Kaiser would be great ).
But I can already give you my sincere congratulations now if you have created such ROMs
I have made ROM based on hang.tuah's ROMeOS (it was going to be an update, but ended in another ROM, LOL - not quite "lite" as I would want it, but I can't change the things that were "always there" now ). I try to steer its users into UC and use "extended packs" for things like dialers, comm managers etc. They'll have best proof that "cooked-in" is *worse* than "installed" soon, when they will have i.e. choice of Opal or Kaiser dialer in the extended pack - which obviously would be impossible if the dialer was cooked-in in the ROM...
@bengalih: your post is what got me to thinking about this again
I'm happy to see that you others share my attitude towards efficiency
I have not completely read thru both of your threads but I suppose what needs to be done is to create a universal standard
The way I see it, this type of system would be beneficial to cooks and end users alike. End users need a minimal variety of options to install these collections and a minimal variety of each basic rom release to install the collections to. Cooks need a simple system to adhere to that requires no more work to put together their collections than the current amount of work they do to create their roms.
Here is a sample proposal (what I'm thinking right now with a minimal knowledge of rom cooking )
A base rom of each flavor could be made available to download. By each flavor, I mean a different rom with each combination of files that must be cooked in to work. I haven't read anything like that before so if there are more than a couple combinations then no more than 4-5 with typcal combinations should be considered.
I need to do some reasearch to learn what benefits and/or caveats are associated with UC and Sashimi. I suppose cooks should be the ones to decide whether to make their collection(s) combatible one installer or the other.
selyb said:
@bengalih: your post is what got me to thinking about this again
Click to expand...
Click to collapse
In the future it might just be best to post in the thread about this then. As a topic that has been tread over several times putting additional input into an existing thread would be more effective.
selyb said:
I have not completely read thru both of your threads but I suppose what needs to be done is to create a universal standard
Click to expand...
Click to collapse
Perhaps you should read through the threads that are already out there before staring a new one that re-hashes the same information.
selyb said:
The way I see it, this type of system would be beneficial to cooks and end users alike. End users need a minimal variety of options to install these collections and a minimal variety of each basic rom release to install the collections to. Cooks need a simple system to adhere to that requires no more work to put together their collections than the current amount of work they do to create their roms.
Click to expand...
Click to collapse
Good luck trying to get cooks to follow anything you propose. Not that it might not be a brilliant idea, but cooks are going to do their own thing. I decided to take matters into my own hands and cook my own ROMs according to the principles I thought best. I put the ROMs and my principles out there in hopes others will adopt them, but that's the best you can do...
selyb said:
A base rom of each flavor could be made available to download. By each flavor, I mean a different rom with each combination of files that must be cooked in to work. I haven't read anything like that before so if there are more than a couple combinations then no more than 4-5 with typcal combinations should be considered.
Click to expand...
Click to collapse
Again, pretty much what I have done already with the HTC and AT&T official 6.1 releases. A base ROM for each with a set of CAB file to customize to your desires.
selyb said:
I need to do some reasearch to learn what benefits and/or caveats are associated with UC and Sashimi. I suppose cooks should be the ones to decide whether to make their collection(s) combatible one installer or the other.
Click to expand...
Click to collapse
No offense, because I realize I am coming off a bit gruff in this post, but you do need to do alot of research. I agree with alot of what you are saying, but it has been said before (by myself and others). Also, there is no reason that a collection of CAB files wouldn't work with SASHIMI instead of UC or vice-versa. To your own admission, you don't understand how these installers work, but when you do your research you'll see that in essence they are both just installing CAB and XML files (and with SASHIMI the capability for much more).
Again, please don't take anything here as a personal attack. I can see that you are coming off of inspiration from my posts and I don't disagree with your basic ideas. However you will get better reception from all if you do these things:
1) Research what is out there before posting so you don't retread old ground.
2) Don't just "propose" ideas, put them into action. Even the best ideas are unlikely to be adopted unless you put effort into implementing them youself.
I say these to you for your own protection before someone not as nice as me begins to bash you for not doing research
Ok, well, I will quit posting to this thread before someone not so nice does come along.
selyb said:
Ok, well, I will quit posting to this thread before someone not so nice does come along.
Click to expand...
Click to collapse
Heh... well seriously, take some time and learn more of what is currently out there and see where it is lacking.
I generally invite user feedback on my development projects. If you go back through the older threads, and take a look at what I am trying to do with my BRR ROMs, please feel free to comment in there about what additionally you would like to see and why.
Trust me, I very much welcome an open debate about what would be an effective way to do things. I just wanted to burst your bubble a little bit (seeing as you are a newer member) that your aspirations, although maybe valid, are most likely not going to get implemented by a majority of the cooks throughout the site.
I don't mean to shut down your thread, and you should continue posting if you see it as the best place to do so. I just feel that if you contribute to some existing projects that already have momentum then your ideas are more likely to get some attention.
So, I have the feeling this isn't the place to post this, but seeing as how I was unable to find a section for the Focus S (yet there is one for the HTC Titan, which isn't even out yet) I figured I might as well post somewhere.
I've interlop unlocked and loaded a few different .xap's onto my device and have found that most either will not work (they close shortly after loading up) or they allow you to navigate around, but not edit anything. Advanced Config, Registry Editor, Samsung Tools, etc. will not allow for any kind of registry changes. Is there anyone who can point me to the right place for solving this issue?
Give me, oh, another hour. Reverse engineering the Focus S DLLs now. Already have registry, provxml, quite possibly filesystem, and a few other things (including the interface for call blocking, which doens't seem to exist in the older phones - sorry people with first-gen phones).
The new SecProxyClient.dll is super-useful. The new FCRouterProxy.dll looks to be amazing too, with lots of new APIs, but they obfuscated the function signatures, so it's going to take me a while to figure them out.
Of course, I don't have Focus S or Focus Flash, so I'm going to need some testers to make sure I've reassembled these APIs correctly. Any takers? I make no guarantee that these functions will work correctly, and if they don't it could mess up something, but I'll try hard to avoid that.
EDIT: Of course, the apps will need to be modified to use the new APIs and DLLs. It's not like I can publish my results and eisting apps will magically just work. I'll include the source of course, though, so it should be easy to build on my work. If schaps were willing to distribute the source for his own apps, I could fix them myself, but no such luck. That's what you get for closed-source, I guess.
I'm right here to test what you need.
I am more than willing to test. Just post it here or shoot me an email: [email protected]
I'm western time, so ill be up for a while
Yeah, I'm not.
Ill leave the testing for you, hope you guys have **** worked out by the morning.
i'm also willing to test as well, but please don't break my phone
All right folks, have at it. I'd like a few testers from each device, if possible, but mostly I just want good reports. PLEASE read the first post carefully - yes, I know it's long, but it will save both of us time.
http://forum.xda-developers.com/showthread.php?t=1348914
Moved to WP7 Q&A
You are correct there is no focus s forum. There are some posts relating to that phone there, but they are different so i will not move it there. As it is a question it has been moved to WP7 Q&A. Hopefully if and when a focus s forum is created you can request the thread is moved again.
Take it easy
O_G
You know, I'm beginning to wonder of the reason that the call blocking app is struggling so much is just because there's a problem with this DLL that it is (and I am) trying to use. Sigh...
Speaking of which, if anybody can get me the XAP for the Call Blocking app, or for any other Samsung Gen2 app, that could be very helpful.
Here you go
Hello, long time user of the forum, first time posting on a sort of recently made account. Before I let my inner Noob show I wanna thank you all for such an amazing experience on a very talented base network of like minded individuals with the same purpose, making our phones truly our phones.
I've used Roms, root, and recovery threads/ guides with such detailed information that I'm glad to be finally able to thank an show my appreciation for Devs and users alike.
My main questions are involving Kernels and scripts, such as init.d support, a2sd and a2ext4
Now from my understanding kernels are made for individual OS ie gingerbread, ics, jb etc. Etc.
So there not all equal though I don't know how to find a specific kernel to work with my Rom or phone model an was wondering if theres a simple way for me to understand what to look for on my own. Since I do have a 10 post intro to go through I can't specifically ask the dev and honestly I'd be more happy if I could just understand and do it on my own.
as for scripts same issue incompatibility and understanding. Not sure what the differences are or which would benefit my needs better. For ex: I have a 32g SD card partitioned with 4g an swap enabled. I mainly use it for link2sd and mounts2sd preferring the latter of the two and on some roms either my busybox won't configure or init.d wasn't properly installed or configured. as for link2sd it won't find my extension knowing that I did partition my card, assuming its the kernel or the base Rom itself but no clue on how to resolve or even pinpoint the issue.
If I'm in the wrong place or have made a mistake please, I'm sorry in advance an if you could guide me to the right area I will gladly move an assume what needs to be done.
hi all!
please note: i am nothing near a professional user or even coder! i rooted my phone and i install custom roms on it, and thats about it. in addition to that i am concerned about my privacy. for me it started with the LBE Privacy Guard from the play store, it was quite nice until it stopped working, and made my phone stuck in a boot loop...
i have read and searched a lot of stuff before i decided to write this. but i havent found an easy and understandable how to. maybe that is because there no easy way to this. please go easy on me if there is already a thread for this...
i just installed openpdroid on my samsung galaxy s+ (i9001) and that is just because user bululu has made a patch for the rom i am using (cm10.1 from user davidteri) - thanks to both of them! i installed the patch with cwm (clockworkmod) and afterwards i was wondering there is no privacy setting in my menu or anything that would let me set up permissions. but from all the stuff i was reading before i figured i will need some kind of gui (not sure this is the right word - that goes for most of the stuff, but please correct me where u can, i will try and learn) so i installed 'pdroid manager' from the play store. that would finally let me set permissions for the apps! so far, so good. i am now using openpdroid...
should be all good at this point u might think, but this is where my questions begin ^^ f.ex:
is this the best solution atm? are there more solutions? what are the differences? what can u recommend?
furthermore i try to figure out how to encrypt email on android. most things i read point to k9 mail and using agp (or apg? is this the same?). i did some research on that topic an it seems to be the 'android privacy guard'. more questions here too...
it seems to be out of development, since the last changes are from 25.12.2010. is there a newer alternative for that or something i missed? or maybe it is still the thing to use or it is quite finished in its current state?!? but i dont wanna clog my device with old or unsupported software until i am 99% sure on what to do...
so basically i am asking if there is a nice and user friendly (with images) 'how to' for this kind of stuff i was just missing or is it just impossible (at the current state) to do such thing? if both answers are 'no' i'd like to start something like that, of course with your help that is...
because it seems the info i found is not coherent, its all bits and pieces one needs to bring together (in the right order and with compatible software). at least thats what it feels like for me as non-professional user and linux noob. i have no problem with puzzling stuff together but i also would like to help others who would like to do increase their security and get different opinions on whats the best way to do some things...
so if any of u got an opinion to any of the above please let me know! and help or links would be greatly appreciated! lets see if we can bring some things together and make our devices, our communication and our data more secure! and please note: this should not be device specific, my device and rom was just for information and for better understanding my starting point. this should be as broadly defined and open minded as possible. so everybody could partake and make use of it...
thanks for reading!
kind regards
bad1080
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.