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.
Related
Hi all!
I'm sort of new here, although i've been reading forums for quite some time now.
I have a Galaxy S (the main reason i'm here in the first place), and given i have a programming experience on different platforms i figured - what the hell. I am planning to try myself in Android apps development and possibly get down to custom ROMs and all that jive.
It is obvious where i should start with development (e.g. download SDK, read some tutorials, books etc.). As for messing with ROMs, i couldn't find an easy introduction to that. I mean, come on, everyone can root the device and install Voodoo lagfix (as i did already), but actually *creating* these ROMs is another story. If someone could possibly point me in the right direction (i just don't know where to start) it will be very appreciated.
P.S. I'm not your usual noob. I am neither afraid of command line, nor technicalities that are involved with this, and i completely understand that this will require HELL OF A LOT of reading, understanding, learning, and i completely understand that all this is way above my current knowledge, that's why i'm interested in the first place.
I think a good start would be to search tutorials for "deodexing" as this is one of the methods to prepare a ROM. From there it should lead you deeper into the rabbits burrow.
Thanks for the tip. Now i have questions that are probably belonging to the Chef section (started to read threads in there and realized that i should have started reading that section in the first place), but anyway.
If i compile the AOSP from source - will it work straight away on any device? Probably not, as the hardware needs drivers and stuff. So, next thing is drivers. As my device is Galaxy S, you can assume that all i ask is related to that device.
I saw that the open-source package (including the drivers) for Galaxy S has been released by Samsung. Does that mean that i can take Eclair AOSP source, copy the drivers, compile and use the result on my device? Well, probably Samsung made some modifications to the kernel, so it would be good idea to copy the kernel source too (i have never done kernel development before but i hope i have a somewhat general idea of how things work down there).
Anything else i need to be aware of?
Following the advice given earlier, i have googled for deodexing and ended up having a folder full of apk's. Does that mean that if i wish to install some Samsung stock apps (like camera) - i can take these apk's and install them as a regular app (or even include them in a resulting vanilla android ROM)?
i would love to learn how to incorporate this functionality into a rom (i'm an owner of a htc phone and primarily use sense roms). from what i've read, it's only a matter of adding a couple of files (phonewindowmanager$12.smali and phonewindowmanager$13.smali) and modifying phonewindowmanager.smali. if done right, this functionality can be added to any rom.
i've been comparing the cm7 smali file to a sense smali file to see what the differences are in terms of code but it just makes my eyes go wonky since i know nothing about reading/writing code.
until yesterday, i had no idea how to extract classes.dex from android.policy.jar nor was i aware of any of the information mentioned above. in other words, i'm a noob at this. i would like to learn how to do this and by the looks of it, many others on the forum are interested as well.
is there a dev out there that would like to share his/her knowledge/wisdom/experience on this with the rest of the xda community? i realize this is a lot to ask but i thought i'd try. thanks in advance.
I'd also be interested in this, for phones where Cm7 isn't available
Me too. Am going to put this thread as my signature until some kind soul comes up with an tutorial. Or at least a rhetoric answer.
By the way, the only guy that i know is, Andy Thompson, who's always update his mod/hack for MIUI roms
http://miuiandroid.com/community/threads/mod-skip-track-via-volume-press.7356/
and also CosmicDan
http://miuiandroid.com/community/th...hold-volume-to-skip-tracks.17381/#post-131527
Must have skill/mod/hack or even app for music lover and flashaholic.
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?
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.