Related
Process
From Wikipedia, the free encyclopedia
Process or processing typically describes the act of taking something through an established and usually routine set of procedures to convert it from one form to another, as a manufacturing or administrative procedure, such as processing milk into cheese, or processing paperwork to grant a mortgage loan, or converting computer data from one form to another.
Ok first off I'm the biggest noob at all things root as could be. I have managed to make some custom clocks for my old LG voyager way back in the day and have even jailbroke some Ipod touch's so I was able to load bootleg games and apps.
But this root thing has got my brain traped in a vortex and I really want to not just know how to root my droid (That info is everywhere) but I want to know how it all works. What terms like kernel mean and how they relate to clock speed. What is the difference between all the custom rom's? What happens when I root my phone and can't figure out what rom I should use? Do I have to reset all my apps and preferences every time i want to try a new rom?
I understand the how-to's I'm sure when I try to root my phone that I will not have much trouble doing so. But there are so many things I want to learn and know before I do anything.
I would like to say I'm not looking for links to tech reports on rom's that I will not understand I'm looking for alink (or someone who knows the things I wish to learn,) something that will explain the terms what they mean, how they relate to my phone and what outcome I should expect from loading custom rom's.
I understand that most users of this forum fall into one of two category's ONE ether super wonder techs that know exactly what they are doing and know how things work, TWO people who can read follow directions and root there phones while trying NOT to sound like noob's when they ask for help.
And then there's me I'm a number two, now I know that kinda makes me sound like **** but I really want to be a number ONE
So who want's to teach me ? Who's got some time to kill or link's to post? I'm even willing to go buy a android programmers book if there's one that would be recommended reading to help me understand the OS better.
I want to learn from the masters and this is where they all live. So will someone apprentice me ?
To close my rant out I would like to say I'm a 37 year old man with a masters in chemistry 119 IQ and ex-stream case of OCD that drive's my compulsive need to learn how things work, So I make for a good student
Thanx
รถ
Thank you so much, I was hoping to be able to reply first, (this sh*t is my crack)
Ok, First off, the kernel is the basic system that controls how the cpu reacts, as well as how programs interact with the hardware on your phone, such as the screen, wifi and bluetooth modules, accelerometer, gps, ambient light and the battery. When a dev wants to overclock their android, add a module for EXT, or TUN, or add wifi support, this is where the magic happens. this is probably the most important part of the firmware. It also controls battery life via voltage, as well as cpu speed.( the average droid can be overclocked to 1200-ish, depending on the randomness of processors, though I've heard of a ridiculous version called OMAP Ti39 or something that could be stable at 2ghz, even 2.3. As I think you may know, Fat32 doesn't support file transfers of more than about 4 gigs at a time, which is why add in ext support is so important, especially since someone made a video player that reads matroska video files (blu-ray) Ive tried it, its beautiful, (V player - on the market) after kernels is framework, the framework is what renders the gui, basically everything that you see on the screen is thanks to the framework-res. We edit it either manually, or through the use of an app called metamorph, which swaps the xml files the framework uses with edited ones, such as one I recently used to give my droid a circular battery, however these xml files can change anything you could need them to visually about your droid, you just have to find what you need. Now on to shell. shell is the engine that is accesible through command prompt and terminal using the android sdk and adb, more on that can be found easily on the google android homepage. however, much use is made through devs and an app called terminal emulator that is basically a straight to shell terminal screen app. Uses for shell may include but are basically limitless, include moving any app to your sd-card to conserve rom (rom is the phones total system memory, apps usually go in there, but before froyo, and ext partition could be used, and with froyo stock support for most apps was allotted, and without the need of an ext partition.) Ram is basically ram, if you use a rom that originally came with a larger ram supported device, something called a swap partition must be implemented, otherwise it won't boot, there is an app or two that will do that for you, manual swap creation is also possible. Swap basically creates virtual ram on the sd-card. Root access, which can be acheived manually through the recovery flashing of specific zip files, or via free apps that do it with one click, basically allows you to flash kernels, change the framework, or allow tethering which I will cover next, is possible because the kernel the phone uses is linux, the unlocking of which is called granting super user access, in ubuntu a linux distribution, typing su, and your admin password will give you access to your computers system files, much in the same way we apply it to android. (However, it is unlikely you would try to flash an alternate kernel to your desktop, as it runs on either ie36 or x64 architecture, whereas phones run altogether seperate architectures , for instance android runs on ARM, and that is the base and primary reason your phone won't run windows.) Since android is free (open-source) there is an x86 version of android, including a froyo port that you can use on laptops and desktops. (Really quickly I would like to interject that recovery is an option on all phones android based that is usually accessible by holding volume up while booting, however the droid requires you press x while booting to get to recovery, which btw is what you flash a custom version of after rooting that allows you to flash roms and kernels. It also allows for backing up all of your phones firmware and data in the event of a problem. Basically its your new best friend, get familiar.) Also there is another form of booting called bootloader, it allows you to flash specific system files that are normally untouched, a guide to using that and a program called rsd lite will help you if you've bricked your phone ( Bricked- term used to describe the state of a phone that is unable to be recovered to an earlier condition and is essentially a brick or "expensive paperweight".) by allowing you to flash a completely untouched sbf (firmware) file. note that you can also use it to change your boring m boot logo with any image that fits 480x182 bytes through a slightly difficult, but fun proccess, a guide to which ,can be found here at xda, including a file that allows for the flashing of just the logo, whereas previously you had to reactivate your phone (you just have to follow the instructions on the phone) reroot, and restore the rom you previously backed up. Now on to tethering, the most important feature available to root users, which, if carriers have anything to do with it, would normally cost an extra 10 dollars a month. (Tethering- using shell or an app with the proper kernel to allow the use of your phones mobile network via usb connection, or the creation of a wifi hotspot with your desktop or laptop.) However thanks to devs who believe that what you pay for should be used how you want, most roms will tether, even in the settings, without carriers any the wiser. Windows 7 and almost all linux will automatically tether, vista is the most difficult, and xp has a quick install init file that works like a charm. The only reason we root is because we believe in the freedom to change our phones to fit us personally, and lets face it, because we can, because its fun, because its not illegal, and it brings a sense of satisfaction and pride in pushing the limits of technology. (P.S. I tried not to take to long so I couldn't really look it over, so sorry for grammatical or vocabulary based errors.)
(P.P.S. I recommend any book to do with android programming, but you'll need programming experience in linux, especially eclipse.)
Oh, and I'm a 17 year old junior with a vocabulary skill level of 139, just in case you wondered.
There are plenty of applications on the market where you can backup apps and data once you root, I personally use titanium, but I never restore system data if I'm flashing roms, only apps n data that comes with apps. Youre gonna have to search around other forums and whatnot to find the right roms.
Sent from my ADR6300 using XDA App
Well i searched around XDA a bit and found many threads related to this bt all for WM and not android.
Multi-tasking is getting a bit tough. Apps get auto-closed after sometime.
Samsung Galaxy SL i9003
Stock firmware and everything stock, nothing chngd much. Only apps installed from the Market.
Say m surfing the opera, and even if a small app like messaging is open and aftr some roaming around when i return of opera, it has closed.
PS - Above is jus an example so dnt claim Opera is a power-hogger so it wil b to open up ram for other apps and all......
So any way of disabling the auto-closure of apps?
Love XDA
@ mod who moved it...
Its related to i9003 nt i9000.
Anyways tnx for moving. Wil get more views here....
Any dev der? Help!
Sent from my GT-I9003 using XDA App
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Exactly.
There's an app on the market, Spare Parts, in it ders a option on hw android handles suc apps.
There r two options. Normal and aggressive. Keep it normal and try and c if it helps.
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Exactly.
I hv migrated frm Symbian, and m a hard multi-tasker, and disappointd with Android jus cos of tis...
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Is this the reason why I have to constantly log back into Evernote, and Tweetdeck every time i wanna have a look at them?
The whole concept of syncing periodically doesn't work anymore because they are constantly logging out on me.
Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.
I wonder y others @xda & @google dnt feel tis....
paleozord said:
Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Erm....why do you think people flash custom roms?!
GTi9000 insanitycm010/insaneglitch
slaphead20 said:
Erm....why do you think people flash custom roms?!GTi9000 insanitycm010/insaneglitch
Click to expand...
Click to collapse
Custom ROMs do not change or affect this system auto-close functionality in any way. At least I've never seen any that did so successfully. It seems to be coded too deeply into the OS to be changed, from what I can tell. That is, I'm sure theoretically it *could* be changed, but most custom roms I've seen tackle far more surface-level interface issues and not the way the kernel manages processes in the background.
I didn't realise this happened after 2.1... I already was thinking why all apps were getting closed so fast after I updated my i9000 to froyo and then to 2.3. I just bought i9100 mainly because of the 1gb ram and still, with 400mb free ram, apps getting closed after couple of hours. (Not minutes, or even seconds like i9000, thankgod).
Autokiller lets you manually change some value of a running app, so it won't get killed... unfortunately this isn't automated so it's no use.
The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.
Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
paleozord said:
The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
ggclanlord said:
Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
Click to expand...
Click to collapse
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).
Tats really Awesome!
paleozord said:
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
ggclanlord said:
Tats really Awesome!
Click to expand...
Click to collapse
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!
I guess so it'd b more effective if tis is wrttn to Google...
paleozord said:
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Cn any1 tel me whthr tis issue is der @GB o nt?
M on Froyo cos GB nt yet released for my device (only a Dev update yet)
I can't say with 100% certainty but I'm reasonably confident it's the same under Gingerbread (2.3). Google considers this "feature" of the Android operating system to be a significant improvement and benefit, so they're not likely to remove it on their own anytime soon unless they get a massive influx of complaints about it.
The best we can hope for is probably a user-controllable setting of some sort that determines the degree of system aggressiveness in auto-closing background applications. There are already plenty of third party root-based utilities available in the market with similar settings, but they only affect their OWN auto-closing tendencies and do not override the system itself's default auto-close behaviour. I know this because I have tried them all at the lowest possible setting levels, and everything still gets closed in the background just the same.
I had Android for a while, and I remember there was an App that broke down Battery/Cpu usage. It would even keep track of how long the screen was on, what was being used most that could potentially be using the battery more.
Ive yet to see an App like this for WP7, let alone 8. Is it even possible? Or is it just yet another thing impossible due to MS lock down on some aspects of the phone OS?
I really do like this OS, but it seems more and more, MS's lock down really hurts development, preventing Devs from really bringing out the most of the OS and prevents functions and abilities youd normally think would exist.
I can understand the want for an app like this (I had it on android myself), but since switching over to WP8 I don't see the need.
All the apps on here run very well and nothing is going crazy like it does with android. Locking down the OS is a good thing sometimes, devs have a much harder tune creating system level apps that run way out of control or have memory leaks that cause battery to run dry in an hour. The only thing I have done is gone to the background apps in settings and stopped what I didn't want running in there.
Sent from my RM-820_nam_att_100 using Board Express
LudoGris said:
I can understand the want for an app like this (I had it on android myself), but since switching over to WP8 I don't see the need.
All the apps on here run very well and nothing is going crazy like it does with android. Locking down the OS is a good thing sometimes, devs have a much harder tune creating system level apps that run way out of control or have memory leaks that cause battery to run dry in an hour. The only thing I have done is gone to the background apps in settings and stopped what I didn't want running in there.
Sent from my RM-820_nam_att_100 using Board Express
Click to expand...
Click to collapse
I initially thought this when I had WP7 and a Trophy. Now that I have the 920, I would love to have this. Partially just to prove out that using my phone (screen on) and games and other things just eats up the battery like crazy. Others over at WPCentral have also posted issues with the battery. Many people have in fact. It would be very useful to some of us who are experiencing issues.
I know some claim to get over a day or more use out of their 920. I, among many others, could only dream of such a thing, or perhaps achieve it if we just didnt do much with our phones.
I disagree on the lock down. While I get your point, having used Android also, I enjoyed many great apps that just wont ever be possible on WP's. No other email clients, no true 3rd party browser not built on IE, no new keyboards to name a few. Some of these apps I had used on Android really were superior to what Ive seen MS do with WP. Which is why I think sometimes 3rd party Devs or home Devs sometimes can just do things better as well as think outside the box and give us real options. You dont get real options for many thing on WP. Everyone is stuck with the same keyboard, browser, mail, messaging client, etc.
True...but remember, there was a time when nothing like that was available for Android either.
Devs have made things more than possible - granted an open system helps - but don't discount what may become available in the future.
Yes there are battery monitor apps for Windows Phone 8. Battery Level for Windows Phone 8 seems to be the most popular. The nice part is that it will autoupdate the live tile with the battery level and you can add it to the lockscreen to show it there as well. It's not quite as in depth as Android with regards to telling you what is pulling the most power but as others have mentioned on WP8 it's a slightly different mechanic than Android as the background processes are a lot more regulated with regards to how they can do that (as are the developers when making their apps). It would be kind of interesting to see something like Android's built-in battery stats but I honestly haven't really haven't had any problems (not that I was really having problems on Android either).
Battery Measure is similar, and has a free version with ads - live tile, graph over time. etc.
and can you tell us where we can get the battery monitor for th WP 8? I want one...
Battery App
inconceivable said:
Yes there are battery monitor apps for Windows Phone 8. Battery Level for Windows Phone 8 seems to be the most popular. The nice part is that it will autoupdate the live tile with the battery level and you can add it to the lockscreen to show it there as well. It's not quite as in depth as Android with regards to telling you what is pulling the most power but as others have mentioned on WP8 it's a slightly different mechanic than Android as the background processes are a lot more regulated with regards to how they can do that (as are the developers when making their apps). It would be kind of interesting to see something like Android's built-in battery stats but I honestly haven't really haven't had any problems (not that I was really having problems on Android either).
Click to expand...
Click to collapse
That sound very good but where can I get the apps Battery Level?
*Before I begin, I must warn everyone that I am a newly registered XDA-Developers user, therefore I am technically a noob.
*English is NOT my first language/mother tongue. If some of the the questions posted below are not understandable, feel free to ask me and I will try my best to rephrase what I said. More information is added below every question for the same one.
*I have read the Forum rules, and did my best to comply with them. Hopefully this does not violate any of the aforementioned rules. If there is such a thing, I will immediately remove any parts/the entire thread.
*As stated above, I did use the search tool, however I did not find any similar thread to this one, hence the reason of opening one.
*Not really experienced with using forum tools, you'll notice the lack of formatting here.
*Summer just started, and with that I have a lot of free time that I wish to devote that time in increasing my knowledge of Android and (hopefully) start being useful with developing something.
1.1. What programming language is required to know when developing an app?
-I've been informed that most apps are developed in Java for Android, however I am curious as to whether or not I can program in C++ as well.
1.2.What programming language(s) is/are required to know when building a ROM from source?
-Many OS's are developed in different programming languages, does this apply to Android as well?
1.3. What IDE is best for developing an app?
-I am referring to the Integrated Development Environment. Which is best for Android?
2.When building from source, is it necessary to have a distribution of Linux running on your computer, or can this be done on Windows/OSX as well?
-Installing Ubuntu on my PC is problematic. For whatever reason, it can not initialize the drivers for my GTX 560 SE, thus rendering my computer unusable. So as stated, can't I work with Windows, or do I have to be forced to buy a new machine?
3.What programs/files are required to install or download to create an environment for building from source?
-IDE's, libraries etc.
4.What system requirements are needed?
-If I do need to buy a new computer, what are the minimum requirements to work freely, as in without much stuttering when compiling?
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
6.What is the current highest version of kernel working on our device?
7.Does our SGM have a custom ROM flash counter?
-In the Play Store, Chainfire has an app that resets the number of times you have flashed a custom ROM. Does our device have this?
8.What group/team(s) are currently building Android versions from source for our SGM?
-I do know of AndroidARMV6, any other team I should know of?
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
11.What does porting mean for ROMs and games?
-Simply put, with permission from the original developer, porting a ROM and a game means making it available for our device. But what are the limitations of this? I certainly can not take NFS Shift, scale down the textures and post it, right?
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
14.What is the output power of our 3.5mm headphone jack?
-If I plug my 2 small desktop speakers, the phone just hangs, while, for example, my cousins IP5 has no issue with having 300W 2 speakers plugged in to it. What is the limit? I take it it is very small.
15.What does GPU rendering mean?
-I've noticed a few custom ROMs being able to use GPU rendering. Does it mean it renders the UI with the GPU instead of the CPU to give a smoother experience? If so, does this impact battery life?
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
18.What is our GPU?
-You read it correctly. I mean this as in is it a standalone chip or is it integrated? Can you also provide information on how fast is exactly our Adreno 200?
18.1. Can we overclock our GPU?
-Like on PCs, can we overclock our GPU to gain more performance? Has this been done before, and how successful is it?
18.2. Do different drivers exist for our GPU?
18.3. If so, does using them make a difference in terms of performance?
19.Do different (if any) drivers exist for other hardware located on our phone?
-Like our GPU, do we have individual drivers for Wi-Fi, Bluetooth etc.? If so, does using them make a difference?
That is all, and thank you to whoever can answer at least some of these.
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
At the moment TWRP is not fully working, better choose CWMR.
A third one will be RZ Recovery, you can find it in "original development" thread.
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
Try to change as much as possible.
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
Yes
This is present on cm7.2/9/10/10.1
On every Stock ROM or custom stock ROM headphones sound is limited by samsung.
I don't take this as a problem... i think it's a plus
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
No
There are Rom's with huge battery drain, and there are others that can make your phone last for 2-3 days
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
Via Custom Recovery.
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
32GB max storage/ uhs-1 max speed
I have a class 10 8GB Kingston and it's perfect
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
The highest indeed is 864Mhz but i never heard anyone running at such high speed. Mine is at 729Mhz, that's 20% overclock...and never had problems like freezing or random rebooting.
Thanks for the answers XDRdaniel.
About the sound output, I think this should be considered a flaw, why push the jack above it's limit, all you get is defected sound, no matter what headphones you are using.
And the clarity also is worse on custom ROMs. Whether this has something to do with my ears, the sound is not clear as having a stock ROM.
Why not take the stock music app with its optimized equalizer and install it on CM for example. Is it copyrighted or something?
Hopefully, other users will answer the rest of my questions.
Reaper's Scythe said:
Thanks for the answers XDRdaniel.
About the sound output, I think this should be considered a flaw, why push the jack above it's limit, all you get is defected sound, no matter what headphones you are using.
And the clarity also is worse on custom ROMs. Whether this has something to do with my ears, the sound is not clear as having a stock ROM.
Why not take the stock music app with its optimized equalizer and install it on CM for example. Is it copyrighted or something?
Hopefully, other users will answer the rest of my questions.
Click to expand...
Click to collapse
It's not about the music player. The rom is the one that has volume boost. It's not that simple
also if you are using a CM based rom i recomend you to use this audio mod.
1.1. What programming language is required to know when developing an app?
-I've been informed that most apps are developed in Java for Android, however I am curious as to whether or not I can program in C++ as well.
A > Java, and sometimes C++. But Java is better.
1.2.What programming language(s) is/are required to know when building a ROM from source?
-Many OS's are developed in different programming languages, does this apply to Android as well?
A > No programming language needed, except when you want to add features to kernels, base, etc. Mostly Java and C++ are needed
1.3. What IDE is best for developing an app?
-I am referring to the Integrated Development Environment. Which is best for Android?
A > Eclipse IDE
2.When building from source, is it necessary to have a distribution of Linux running on your computer, or can this be done on Windows/OSX as well?
-Installing Ubuntu on my PC is problematic. For whatever reason, it can not initialize the drivers for my GTX 560 SE, thus rendering my computer unusable. So as stated, can't I work with Windows, or do I have to be forced to buy a new machine?
A > No, building can only done using Linux. Try using another distro.
3.What programs/files are required to install or download to create an environment for building from source?
-IDE's, libraries etc.
A > Many libraries needed, you can search google for it.
4.What system requirements are needed?
-If I do need to buy a new computer, what are the minimum requirements to work freely, as in without much stuttering when compiling?
A> A power PC, with 64 Bit architecture. Around 10 GB RAM, more is better. Also, a fast internet speed is needed.
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
A > TWRP isn't stable yet. Use CWMR
6.What is the current highest version of kernel working on our device?
A > 2.37.6
7.Does our SGM have a custom ROM flash counter?
-In the Play Store, Chainfire has an app that resets the number of times you have flashed a custom ROM. Does our device have this?
A > No
8.What group/team(s) are currently building Android versions from source for our SGM?
-I do know of AndroidARMV6, any other team I should know of?
A > Team GingerDX or whatever they call it. They build GingerDX ROM based on Gingerbread.
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
A > Do some theming. To make it unique.
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
A > No, sound is perfect for me, basically stock ROM music player have it's own equalizer. BUT, if you do a little more tweaking sound will be perfect.
11.What does porting mean for ROMs and games?
-Simply put, with permission from the original developer, porting a ROM and a game means making it available for our device. But what are the limitations of this? I certainly can not take NFS Shift, scale down the textures and post it, right?
A > No, you're already right. But for NFS, i think you can't.
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
A > Well, it's ROM problem or hardware problem. I have CM7.2 and the battery stand for 2 hours for browsing + music, and 5 hours for listening music, OR 24 Hours without being used.
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
A > Some uses recovery some uses ODIN.
14.What is the output power of our 3.5mm headphone jack?
-If I plug my 2 small desktop speakers, the phone just hangs, while, for example, my cousins IP5 has no issue with having 300W 2 speakers plugged in to it. What is the limit? I take it it is very small.
A > It's jack limitation.
15.What does GPU rendering mean?
-I've noticed a few custom ROMs being able to use GPU rendering. Does it mean it renders the UI with the GPU instead of the CPU to give a smoother experience? If so, does this impact battery life?
A > Yeah, sorta like that. No it doesn't impact battery life.
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
A > Storage 32 GB. Speed 10 MBs.
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
A > This is what make phone unique, some phone can handle 800 and more Mhz, some only handle 700 and more Mhz.
18.What is our GPU?
-You read it correctly. I mean this as in is it a standalone chip or is it integrated? Can you also provide information on how fast is exactly our Adreno 200?
A > Intergrated. Not really fast, search for google for the answer.
18.1. Can we overclock our GPU?
-Like on PCs, can we overclock our GPU to gain more performance? Has this been done before, and how successful is it?
A > It can't.
18.2. Do different drivers exist for our GPU?
A > No, only patched drivers exist.
18.3. If so, does using them make a difference in terms of performance?
A > It does on some Android version.
19.Do different (if any) drivers exist for other hardware located on our phone?
-Like our GPU, do we have individual drivers for Wi-Fi, Bluetooth etc.? If so, does using them make a difference?
A > Only if you source build a ROM, you can change the drivers. Drivers are exist, like WiFi driver, etc. Yes, it's make a huge or small difference.
F4uzan said:
1.1. What programming language is required to know when developing an app?
-I've been informed that most apps are developed in Java for Android, however I am curious as to whether or not I can program in C++ as well.
A > Java, and sometimes C++. But Java is better.
1.2.What programming language(s) is/are required to know when building a ROM from source?
-Many OS's are developed in different programming languages, does this apply to Android as well?
A > No programming language needed, except when you want to add features to kernels, base, etc. Mostly Java and C++ are needed
1.3. What IDE is best for developing an app?
-I am referring to the Integrated Development Environment. Which is best for Android?
A > Eclipse IDE
2.When building from source, is it necessary to have a distribution of Linux running on your computer, or can this be done on Windows/OSX as well?
-Installing Ubuntu on my PC is problematic. For whatever reason, it can not initialize the drivers for my GTX 560 SE, thus rendering my computer unusable. So as stated, can't I work with Windows, or do I have to be forced to buy a new machine?
A > No, building can only done using Linux. Try using another distro.
3.What programs/files are required to install or download to create an environment for building from source?
-IDE's, libraries etc.
A > Many libraries needed, you can search google for it.
4.What system requirements are needed?
-If I do need to buy a new computer, what are the minimum requirements to work freely, as in without much stuttering when compiling?
A> A power PC, with 64 Bit architecture. Around 10 GB RAM, more is better. Also, a fast internet speed is needed.
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
A > TWRP isn't stable yet. Use CWMR
6.What is the current highest version of kernel working on our device?
A > 2.37.6
7.Does our SGM have a custom ROM flash counter?
-In the Play Store, Chainfire has an app that resets the number of times you have flashed a custom ROM. Does our device have this?
A > No
8.What group/team(s) are currently building Android versions from source for our SGM?
-I do know of AndroidARMV6, any other team I should know of?
A > Team GingerDX or whatever they call it. They build GingerDX ROM based on Gingerbread.
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
A > Do some theming. To make it unique.
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
A > No, sound is perfect for me, basically stock ROM music player have it's own equalizer. BUT, if you do a little more tweaking sound will be perfect.
11.What does porting mean for ROMs and games?
-Simply put, with permission from the original developer, porting a ROM and a game means making it available for our device. But what are the limitations of this? I certainly can not take NFS Shift, scale down the textures and post it, right?
A > No, you're already right. But for NFS, i think you can't.
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
A > Well, it's ROM problem or hardware problem. I have CM7.2 and the battery stand for 2 hours for browsing + music, and 5 hours for listening music, OR 24 Hours without being used.
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
A > Some uses recovery some uses ODIN.
14.What is the output power of our 3.5mm headphone jack?
-If I plug my 2 small desktop speakers, the phone just hangs, while, for example, my cousins IP5 has no issue with having 300W 2 speakers plugged in to it. What is the limit? I take it it is very small.
A > It's jack limitation.
15.What does GPU rendering mean?
-I've noticed a few custom ROMs being able to use GPU rendering. Does it mean it renders the UI with the GPU instead of the CPU to give a smoother experience? If so, does this impact battery life?
A > Yeah, sorta like that. No it doesn't impact battery life.
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
A > Storage 32 GB. Speed 10 MBs.
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
A > This is what make phone unique, some phone can handle 800 and more Mhz, some only handle 700 and more Mhz.
18.What is our GPU?
-You read it correctly. I mean this as in is it a standalone chip or is it integrated? Can you also provide information on how fast is exactly our Adreno 200?
A > Intergrated. Not really fast, search for google for the answer.
18.1. Can we overclock our GPU?
-Like on PCs, can we overclock our GPU to gain more performance? Has this been done before, and how successful is it?
A > It can't.
18.2. Do different drivers exist for our GPU?
A > No, only patched drivers exist.
18.3. If so, does using them make a difference in terms of performance?
A > It does on some Android version.
19.Do different (if any) drivers exist for other hardware located on our phone?
-Like our GPU, do we have individual drivers for Wi-Fi, Bluetooth etc.? If so, does using them make a difference?
A > Only if you source build a ROM, you can change the drivers. Drivers are exist, like WiFi driver, etc. Yes, it's make a huge or small difference.
Click to expand...
Click to collapse
Thank you so much, I guess that's all. This thread can be closed now
It is very essential to boost up speed and Betarry stability to friendly use device. Some time, there found that many unused software were running and decries the performance of phone. More over when the unused program running on background, it distressed charge of the phone batarry which is disgusting to any user. So it is need to set a module for manage start-up program whether it is running on first boot or not.
I personally use the "all-in-one toolbox" to manage the start-up programs and feel very happy. Have a look valuable feedback from developers.