[Q] oprofile: functional after initial Android setup? - Android Q&A, Help & Troubleshooting

One of my Android phones (the third in my signature), with limited /data partition storage size, shows a large subdirectory, 'oprofile' in /data/bin/oprofile. Running out of space in this partition seems to be a common problem, so I'd like to keep it as lean as possible.
Some research shows oprofile to be a tool for 'tuning' an Android setup -- but exactly when it's useful is not clear, from what I've been able to find.
My question is, is oprofile purely useful while Android is being configured for a specific phone's hardware? In this case, perhaps someone just forgot to delete it, after it served its purpose -- and then, there's no harm in removing this subdirectory and regaining the space it consumes.
Or, does oprofile serve an continuing purpose, being used by the OS to continue the 'tuning' -- as the user adds new apps? In this case, that directory is functional and should be left alone. Or, is there data in these files, created during the initial 'tuning' that must be retained, for the benefits to continue?
? So, what to do? Take it out, or leave it in??

Moderator, should this post be moved to a different forum?
! Bump !
to the moderator, it's been three days with no reply.
Could you suggest a different forum as being more appropriate for this type of question?

Bump, again ...
Belamigo said:
! Bump !
to the moderator, it's been three days with no reply.
Could you suggest a different forum as being more appropriate for this type of question?
Click to expand...
Click to collapse
... to the moderator, it's been over a week since the original post, with no reply. This secion is quite active, so it another 'Bump' OK after this lapse of time?
Please suggest a different section, or a different forum, where there may be interest in replying to this type of question.
There was discussion of oprofile in a Developers' Forum for a specific phone, but I hesitate to repost this question into that thread -- unless you say only these folks have an opinion on this utility. This is a general question, not specific for any one brand of phone -- apparently oprofile may be used with a variety of devices, as well as other distros of Linux.

Related

[Q] LG Axis AS740 and ROM Development

First, I would like to start this post off by stating that YES I am very new to Android development, please don't flame me for this, as everyone was once a beginner. Second, I have only made one post thus far, so I am trying to abide by the forum rules, I'm hoping that I have chosen the correct section for this thread. I was going to use the development section, but noticed that it was mainly used for posting ROM's, and I didn't want to bloat up the guru's development posts with a commonly 'n00b' post (LoL).
I doubt I need to ask the question, "Where is all the development for the LG Axis AS740?", as I'm sure we all know how crappy of a phone this is, however, I would like to know if there is any current paths I may take towards ROM Development for this particular device? To be more precise, if anyone could point me to any development resources for this phone, it would be very appreciated. I have already installed JAVA JDK, and the Android SDK, so I'm on my way to learning program dev for my device. If I need any help with app development, I know I'm in the right place, as I have a immense respect for you guys here on the XDA forums because of the immense amount of information everyone has worked so hard on, and provided to the users of this forum.
I did notice the post "LG Axis Rom", I browsed it hoping to find my answer there, but no one has responded to the author. I for one do not wish for a senior member, or veteran to magically provide me with their hard work by asking for someone to develop a working ROM for me; as I have seen some poster's do. I am asking that someone be gracious enough to provide me with the information to help me onto the proper path, so that I may have a proper starting point. I have read over a few development sections, but alas, I know how development for one device can be vastly different for another.
Thanks go out to all whom may respond to this thread, and many thanks for your time, and any information you may provide.
Vasdeus
If possible will a moderator please delete this POst....thank you.
Sent from my Milestone X2 using XDA

Keep Chef Central clean - Guidelines

Hello developers and aspiring developers!
Seeing Chef Central is a pretty good resource for beginners and current developers to exchange info, it would be nice to have it a bit more organized.
I propose the following:
Tags
As you've probably seen around more places on XDA, TAGS are used to show us what the thread is about. Some threads here are already tagged, and it's that what we'd like to see.
Think about TAGS along the line of: [TUT], [Guide], [PORT], [Kernel], [Tool], [Kitchen], etc. Also, the [Q] tag should ALWAYS be used when a question is posted that couldn't be solved after taking the following steps...
Posting in threads instead of creating new ones
If you have a question about anything found in Chef Central, ask them in their respective threads. Don't open a new one just because no one answered your question in one day. Ask again, if you have to, in the same thread. Or, try the next best thing...
Searching
You should know that most of the stuff on XDA is searchable, even through Google's searchengine. I even recommend doing a search BEFORE asking a question. And if we keep this forum organized, searching would be pretty easy, now won't it? Speaking of organized...
Cleaning up
Obviously, this is something a moderator should do. In this particular case, we have several moderators that can do this: Some Recognized Developers are able to moderate this forum. To see who is able to do so, look at the bottom right of the Chef Central main forum.
Reporting also works wonders here; maintenance work is something we mods do too. Report a thread that needs to be cleaned/closed/stickied/etc. Make it a bit easier for us.
Device specific threads
All device specific questions should be posted in their respective forums. If there isn't any, post in general Android development.
So, with this, I want to start a "spring cleaning" if you will. Development is key here on XDA developers, and the place where most development is happening, it's a mess... Oh, the irony.
Oh and please, if you have any ideas or comments regarding this post, do not refrain from posting them here.
Let's start cleaning, shall we?
good post
I really hope this is a great source of info for me. So far everything that I've needed has been found here. So keep up the great work.
Thanks for this post. Totally agree and would like to add few things. We all want easy and quick access to the information and quick answers. But, before you ask, please think about what EXACTLY you want to ask, is your question make sense , or just like - "my ROM is not working, can you help" and then wait and see long long long thread of messages where people trying to understand - what ROM, how it failed, which device, what environment, symptoms of failure... etc.. Do not make a mess , keep this "home of knowledge" tidy.
Looks like OP forgot to mention that posting "Thanks" instead of just hitting thanks button is also a source of unnecessary clutter
shoey63 said:
Looks like OP forgot to mention that posting "Thanks" instead of just hitting thanks button is also a source of unnecessary clutter
Click to expand...
Click to collapse
Fix'd
Everything is with a clear explanation of the very open
Challenges. It was really informative. Your website is very helpful.
Thanks for sharing it publicly!
Coad base
This is one of the sets of more consistent coding standards I've seen. It 'clear that it is written by someone with a deep knowledge and passion for the great design of the system to improve its ability and maintainability of its code base efforts everyday.
Great.. Glad to have it. Thanks again for the share
Best Guidelines regarding CC cleaner, apart form this can i have any another cleaner for my Andorid Phone, that should be trust able as CC cleaner and good to use.

[GUIDE]How To Be A New User And Not A Noob

Hey guys and girls, I've created this thread as a means to help out new members of our corner of the community, or XDA as a whole.
I've posted this in the hopes that it'll make a new users journey here begin nice and smoothly. Once you read this thread, you'll know the basics of how things run around this site, where to make sure you post in the correct section and how to avoid the people who will try to troll and flame you.
My aim is that after reading this, you'll have gained an advantage by reading and understanding this guide.
However, this guide isn't only for the new members of this sub-forum. This is for anyone who reads this, whether you're a new member, a senior member, a recognized contributor etc, as a lot of the "veteran" members seem to have lost their way, as of late. I hope that this will help transform you from a noob into a new user and that you'll give back to this community even part of the mass that you learn.
One thing you should remind yourself is that we were all noobs at some point. Maybe some weren't when they started XDA, but I guarantee you that they were at one point. But just because you're a noob on XDA, there's still no excuse for not following the Forum Rules.
The most important thing you'll need to do to get along well around here, is to search. If you have any kind of problem, first of all you should search. If you can't find anything, then you should try using different keywords to help you find your answer. If you find a similar thread then you can post your question in there instead. If however, your question hasn't been asked before and there's nothing around which is similar then you can post your question, but make sure you post it in the Q&A forum. QUESTIONS DO NOT BELONG IN GENERAL OR THE DEVELOPMENT FORUMS​
Before diving right in, let me overview the rules set by xda:
*Search Before Posting, Behave In A Nice And Friendly Manner, Make Sure You Make Your Titles And Threads Clear To Other Users, Use The English Language, Post A Message Only Once (Do Not Multi-Post), Do Not Post Warez​(I'll explain what this means later) , Do Not Spam (again, more explanation to come regarding this) , No Requests For Donations (If People Want To Donate, They Will), Do Not Use Copyrighted Materials Or Anything That Does NOT Belong To You, Be Helpful To Others, Using The Work Of Others MUST Be Approved, Do NOT Create More Than One User Account, and Keep On Topic In Threads And With Your Posts.
For a full list and explanation of the rules of this site, please view the FORUM RULES.​
---Getting Started (With The Basics)---​
I figure that if you're reading this, you're already a registered member and have read the Forum Rules above. Below I'm going to recap the most important rules briefly, so they will be imprinted into your mind a bit more.​
1) Search, Read, Post
As I've already mentioned in this thread and as you'll hear a lot of times, searching and reading before you post is the most important thing you need to do around here. The first thing you should be reading when in this forum is the stickied threads. Those threads have been stuck to the top of the forum because they contain the must have information you'll need to learn everything you need to. Don't get mistaken and think that those threads are there for no reason. That's not the case. If you read them, should you have any of problems you'll be able to easily know how to solve it. Searching before you post is just as important as reading because if you search for your answer then you probably won't even need to post your question. This will save you time and save others time from needing to help you Even if there's not a thread for your problem, if there's a thread which is similar then post in there instead. Doing so will help to keep our forum as clean and tidy as possible, meaning it's easier for all of us to find the answers we need.
Of course, we are all here to help each other out but if you haven't tried to help yourself then why would others waste their time trying to help you? So do the searching and reading as mentioned, once you've done that you'll know exactly where to post to get the best answer for your problem.
2) Posting Protocol:
Over your time on XDA you'll either find yourself lurking (not posting a lot), or you'll find yourself making the most out of this site and posting quite a lot. However, you shouldn't be posting a load of rubbish simply to get your post count up. This is especially true for new members who have less than 10 posts and want to post in a development thread. Please take note of the Post count limit in developmental fora and remember that if you need something posted in a development thread then you can make use of the following thread -I Will Post Your Question In A Dev Thread IF.... That thread will allow you to get your question posted without getting in trouble for spamming.
Another must have when posting is to give as much information as possible. If, for example, your device has started rebooting itself randomly and you decide to ask why it's happening, you need to give all information possible. This means you should include what device you have, which ROM you are using, which kernel you are using, what you did just before the problem occurred, what you have done to try and fix it etc... The more information you can give, the better help others will be able to provide you with.
3) Don't BUMP Your Posts
Whenever you make a post on this site, whether it's a question, a general post or even a response to someone else, don't be impatient. You need to give people time to think about what you've posted and then respond to it. Also remember that the person may not be in the same part of the world as you, so just because it's morning for you it could be nighttime for someone else. Don't be in such a hurry that you BUMP (Bring Up My Post) your own post in an attempt to get a quicker response. Doing that can make people feel less inclined to help you because they feel forced and pressured into doing so. People will respond to you, you just need to give it time. The quickest way for you to know that someone has responded to you is to subscribe to the thread. This way, you'll receive an email notification as soon as someone replies.
4) Showing Appreciation Via The Thanks Button:
There's one feature of XDA which you'll all be aware of. That is indeed the Thanks button/meter. This was implemented into XDA a while back in an attempt to cut down on users making posts simply saying "Thanks". Also, if a post has thanks on it, you know it has been a useful post for others and you may be able to get some use from it aswell. Please be sure to utilize this feature. If you ask a question and somebody gives you the correct answer, click the thanks button on their post. Even if somebody doesn't have the right answer but has been trying to help you solve your problem, give them a thank because they've used there own time to help you when they could've just ignored your post. As you'll be able to see, underneath everyone's avatar is the Thanks meter. This allows you to see at a glance that this user has been really helpful with there answers. It's by no means a perfect system as some users (myself included) will use the button if I find a post funny or if I agree with someone's post. Because of that, it doesn't always indicate a users status or stature on XDA. It's a potentially wildly inaccurate measure of a members ability to answer your question correctly.
It is always best to hit that button though because it's good to feel appreciated. If you feel the need to actually post "Thank you" then follow it up with a click of that button aswell. Once you start helping out others by answering their questions and you receive a Thank from it, it may make you feel that your work/effort is truly being appreciated and that your time is being valued.
In order to be able to give another user Thanks, you must have one post. The best place to gain your first post is by using The "Say Hi" Thread and introducing yourself to XDA. You're limited to give 8 thanks per day and if you're using them right, you should use them all everyday.
Below is a breakdown of how many thanks you need to have for the bar on the Thanks Meter to increase.
Getting Thanks: You will see that everyone here has a "Thanks Meter" above their avatar. Here are the thanks counts needed to get to the next bar:
1st bar - 26
2nd bar - 51
3rd bar - 101
4th bar - 201
5th bar - 501 (There's a a bug here, never gets to 5 bars)
6th bar - 1001
7th bar - 2001
8th bar - 5001
9th bar - 8001
Maxed! - 10000​
5) Trolls And Flamers:
Trolls and flamers are a part of this community, whether we like it or not. I'll briefly explain them below in case you aren't aware of what I mean.
Trolls - Trolls are basically members who will attempt to make "fun" of you or something you post. But it's only a bit of fun. It's not meant to be serious and is not meant to be aggressive or upset you in any way. If someone tries to 'troll' you when you make a post and you don't like it, then be sure you don't respond to them. Leave them to it and they'll go elsewhere.
Flamers - Flamers are essentially more extreme trolls. They will make fun out of you but will take it too far and attack you. If you asked a question, which they felt was dumb, then they will have a go at you for being "so stupid" and "being a noob".
While some of you may have a sense of humour, others won't so you need to be careful about what you post. As posted above, the best option is generally to ignore any posts of that kind, as they can escalate quickly and you could find yourself getting in trouble aswell for responding in such a manner. If, however, you feel you can't ignore what's being said or you feel that someone has been overly aggressive and attacking, you can report the post to any of our moderators and they will look into it and take the appropriate action.
6) Warning About The Warez:
As you'll know by looking at the name of this site - xda-developers - you'll know that this site was primarily based around developers of modifications, apps, ROMs etc. That means that this site is based around their work and contributions, which they have spent a lot of time and work in making and may require that a payment be made for their work. That being said, it's against the rules to post anything which avoids paying for the software. There's zero tolerance in regards to people posting such things or even asking about it. Out of all of the rules, this is definitely the most important and you will probably be infracted or banned if you post about it anywhere on this site.
If you keep stealing a developers work then the developer is not making money from it which could mean that they can't keep releasing more work. This then affects all of us just because you were too selfish to pay for it.
7) Admission To The Development Section:
A load of new users seem to want to jump in head first and want access to post in the development section. The reality is, YOU CAN'T! This isn't to try and make you feel inferior to anyone else or to stop new users coming to this site. The reason is to stop a hell of a lot of spam and to stop people simply posting "Thanks" and thus making the development threads look like a mess. We want all parts of XDA to look as nice and tidy as possible so the same goes for the development sections. You will need to make 10 constructive posts before you're allowed access to the development fora. If you're unsure of how to get to 10 posts properly, then you should try helping out some people who have questions or queries in your devices forum and you'll soon find that your posts will climb quickly. If it is extremely urgent that you post in a development thread but don't have time to get to 10 posts, then you can either use the following thread - I Will Post Your Question In The Dev Thread IF... - or you can PM the developer and explain the problem to them. *NOTE* Only PM one of the developers if you've looked all through the thread and what you're reporting hasn't been mentioned before Here's a summarization of the 10 post rule by Fallen Spartan: "The 10 post rule was put in place to make new users think, and hopefully contribute and help others by making useful posts rather than the usual crap like "thanks", "kewl" etc or ask questions which have been asked countless times before. They still have access to dev forums, just cannot post in them. Its not a massive restriction and to provide 10 useful/helpful posts is not hard."
8) User Title's Explained:
You'll see that every member has a "title" under their avatar. If you've seen these and wondered how to get them, then read the following passage from juzz86: "I'll sum it up for you (or try, anyway!) There are Junior Members, Members, Senior Members first. These make up the vast majority of XDAs userbase. Recognised Contributors are nominated by other users and/or Mods/Developers. They are recognised for their contributions which are not specifically Development, such as detailed guides, one-click utilities and other tools/mods. Recognised Themers are also nominated by users/Mods/Developers, for their work themeing custom ROMs and providing standalone themes for flashing. Recognised Developers are nominated and approved by the Developer Committee, for their work in Development whether it be ROMs, Root methods, bootloader unlocks etc. Elite Recognised Developers are again assessed by the Developer Committee, and are deemed to have gone above-and-beyond in providing knowledge/hacks/tools/apps/ROMs for the XDA community. Forum Moderators are appointed by the Moderator Committee, after submitting an application (see the 'sticky' at the top of this forum - currently applications are not open). They are the first-line of keeping the forums tidy, friendly and orderly. Senior Moderators are the next step up the ladder, providing site-wide support for Forum Mods and looking after the nitty-gritty issues, as well as areas of XDA not policed by FSMs, such as the Marketplace. Administrators are next. There are several Admins - each look after a specific part of XDA such as the Portal, the Members and the User Experience of XDA as a whole. At the top is Mike Channon, who is overall Forum Administrator. Other titles you may come across:
Moderator Committee - sits on the Mod Committee Developer Committee - as above, but for Developer Committee XDA News writer - publishes articles for the Portal (front page) Retired xxxx - have since officially 'left' their XDA position
Hopefully that clears most of them up for you. Contrary to what a lot of people expect, the thanks-meter does not figure at all in determining a users tag."
0 to 29 posts - Member
30 to 99 posts - Junior Member
100 + posts - Senior Member​
9) Helpful Links:
Forum Rules
Postcount limit in developmental fora
Guide To Getting A Moderators Help
XDA New User Guide
Index of ROMs, Kernels, Recoveries& Guides
[SOLA]Index of ROMs, Kernels, Recoveries & Guides
[ACRO S] Index of ROMs, Kernels, Recoveries & Guides
[GO]Index of ROMs, Kernels, Recoveries & Guides
Index of ROMs, Kernels, Recoveries & Guides
[P]Index of ROMs, Kernels, Recoveries & Guides​
CREDITS: Apex_Strider for the permission to base this in his thread.
E.Cadro for letting me post this thread here.
---Welcome To The 2012 Xperia Community---​
Well I'm glad we've got all of that covered I'll bet you are aswell
Now I'll take this moment to welcome you to our community, so welcome Come and join us and help us make this forum as good as it can be.
If you've paid attention to what's been said in this thread and actually apply it to your time here, you'll never be a noob. Instead, what you'll be is a New User (which sounds much nicer).
With all the knowledge you gain from around XDA, you'll definitely be able to help other people out and feel the satisfaction when you have been able to help someone finally solve their problem.
This is how you can give back to the community. I urge you all to stick around and have fun, learn a hell of a lot and get to know people.
I look forward to speaking/interacting with you all
Should you have any problems, questions, concerns or just fancy a chat feel free to Private Message me at any point and I'll be glad to help you out
Time To Let You Know Who The Standout Members Of Our Community Are!
I'll be listing our Forum Specific Moderators, Developers, Recognized Contributors and the most helpful members across this forum.
Xperia Moderators:
'cooleagle'
E.Cadro​
Xperia Developers:
This Is Currently A Work In Progress. If Someone Could Possibly Get A List To Me, That Would Be Great.​
Xperia Recognized Contributors:
This Is Currently A Work In Progress. If Someone Could Possibly Get A List To Me, That Would Be Great.​
Xperia Most Helpful Members:
This Is Currently A Work In Progress. If Someone Could Possibly Get A List To Me, That Would Be Great.​​
And, just in case, here in the video of the rules of xda developers site. Doesn't hurt to watch it more than the obligatory first time for your registration process. Enjoy xda, and I welcome you to our community!​
I hope this guide helps you make your experience on XDA a better one. I'll be glad if you click the Thanks button, instead of saying Thanks, but I'll be even more glad if you take this guide to heart and actually follow what it says. Doing so will help make your time here easier and more comfortable for everyone involved.
Thank you for reading, and happy forum'ing! :good:​​
Around these forums you're likely to hear some terminology or lingo which you're not familiar with. Check out this list of Android Terms, Slang & Definitions by Diablo67.
I'm going to post some of the more relevant definitions below, but if you see a term you're not sure about but it's not in this thread then check out the above thread by Diablo67.
So here we go…
ADK: Android Development Kit, What people use to develop anything for the droid such as ROM's
AOSP: Short for Android Open Source Project, and when the term is used in ROM descriptions, it usually indicates that the ROM in question is based on the Android source code provided by Google itself, and not on some other ROM project or a company’s firmware.
Baseband: In communications and signal processing, the baseband describes signals and systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loader: Executes code before any operating system is launched. On Android devices, the bootloader is usually locked because manufacturers want you to use the version of Android they’ve provided. With a locked bootloader on Android phones, custom ROMs cannot be flashed.
Boot Loop: simply means something is preventing the phone from completing it's boot cycle and is stuck between the boot animation and the unlock screen, creating a looped animation. This is often fixed by either reloading a Nandroid, or Reflashing a rom from the Boot Loader.
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight).
Bug or Software Bug: an Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better and smoother running than others because certain developers have taken the time to input "perfect" code
ClockworkMod or CWM: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Dalvik: is the cryptic name of the virtual machine (VM) in Android, and it’s the basis for running apps (with the .apk filename extension) on the platform. Before Android apps are launched, they’re converted into the compact Dalvik Executable (.dex) format, which is designed to be suitable for systems that are constrained in terms of memory and processor speed. Dalvik was originally written by Dan Bornstein, who named it after the fishing village of Dalvík in Eyjafjörður, Iceland, where some of his ancestors lived.
Dalvik Cache: Simply put it is the cache used by Dalvik, and it’s the result of Dalvik doing optimizations of running apps. Some Android ROMs allow you to move the Dalvik cache to your SD card, in order to free up internal storage.
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
What the heck does it mean, exactly? Well, it’s probably the hardest term to explain in this rooting dictionary...
When a ROM has been deodexed, it means that its apps have been prepared so they can be modified. Deodexed ROMs feature apps that have been repackaged in a certain way. Android applications (.apk's) contain .odex files that devs supposedly use to save space. These .odex files are extracted from the application packages and put in the /system/ folder on your phone, to speed up boot processes and to allow parts of applications to be preloaded.
However, this makes hacking and modifying those apps difficult because parts of the apps have been extracted to another location. Deodexing means that all pieces of an application package are put back together into one file, and it makes sure that a modified .apk won’t conflict with some separate odexed parts located somewhere else. Developers of custom ROMs choose to deodex their ROM packages, since it lets them modify various .APKs, and it also makes theming possible after the ROMs have been installed.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Ext2/3/4: This refers to partitions on your SD card. They’re extended file systems for Linux that can be used by Android, usually in order to preserve internal storage space. Many custom Android ROMs require that you have an Ext2, Ext3 or Ext4 partition on your memory card. Ext2 is the oldest type of extended file system, and Ext4 is the newest.
Firmware: A phone’s firmware is basically its operating system. A “firmware update” means that the operating system, the software that controls the phone, is updated. “Stock firmware” means that the firmware is unmodified: it’s the version of the operating system the phone’s manufacturer delivers.
Flash or Flash Memory: To flash a custom ROM, or a firmware, simply means that you install it. So, flashing is the process of installing a new version of the Android operating system, or just parts of it, like such as the radio and/or kernel. Flashing new ROMs is done via the Recovery Mode, usually with ClockworkMod Recovery.
Kernel: Central component of most operating systems: it’s a bridge between applications and the actual data processing done at the hardware level. Android kernels are often customized, optimized and modified for different purposes, such as over-clocking the processor or extending the battery life. Custom ROMs usually include a new kernel.
NanDroid or Nandroid Backup: Anyone with root access make a complete system backup. It lets you create a backup of every piece of information on your phone, and it can be restored later whenever you want. NANDroid backups are usually performed before flashing a new ROM, in case anything goes wrong with an update or when flashing, or if you want to return to your previous setup later. NANDroid backups are created from the Recovery Mode often found with CWM.
Odexed: See Deodexed
Radio: It’s the radio on your phone that handles communication, the radio that sends and receives voice and data. Flashing (installing) a new radio can improve your reception, and bring other benefits.
Root: Common word associated with giving a user "super user" access to their phones programming and other various aspects that would normaly not be possible, also known as "Jailbroken" for iPhones.
OS: Operating system, e.g. Windows, Mac, Ubuntu...and Android.
Overclocking: Speeding up the CPU past the factory presets to achieve a faster and more responsive device
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen, to icons to custom boot animation
SetCPU: This is a popular application for overclocking or underclocking your phone’s processor, making it faster or slower. It may require a special kernel in order to work.
Stock:Simply means an unaltered state, such as when you first purchase your phone from Verizon, or when you do a factory reset to "go back to stock."
SU or Superuser: When you root your Android phone, you will get superuser access. The superuser or root user is sort of a special user account for system administration.
Terminal or Terminal Emulator: An app that lets users access Android’s built-in Linux command line shell. It’s useful for programmers and for those with root access. There are some Roms that have built in theme and/or tools that are accessed from Terminal.
Theme: A set of icons, backgrounds and app trays that change the aesthetics of the overall look of the droid and its applications
Underclocking: Slowing down the CPU mainly to limit battery usage
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened and inspected using common archive tools
.tar: Similar to a zip file, a tar file archives multiple files into one file
Reserved.
I've now filled in a couple of the reserve slots and will leave it at that for now.
Please be sure to let me know if you have any queries, concerns or requests regarding this thread.
Thanks
Bumped
Sent from my Nocturnalized One XL using Forum Runner
Bumping up
I've added links to an index of ROMs, kernels etc. for each device into the OP.
As always, if I've made any mistakes throughout this thread or you think there's something missing, please be sure to let me know
"My badboy megazord whip's got more features than iOS5"
This is a very good and informative thread. There should be something like this in every forum, but then it might become repetitive.
Sent from my LT15a using xda-developers app
might wanna change
OS: Operating system, I.E. Windows, Mac, Ubuntu...and Android.
to
OS: Operating system, eg. Windows, Mac, Ubuntu...and Android.
although grammatically vorrectt
theres bound to be someone thnking the I.E. is for internet explorer
-PiLoT- said:
might wanna change
OS: Operating system, I.E. Windows, Mac, Ubuntu...and Android.
to
OS: Operating system, eg. Windows, Mac, Ubuntu...and Android.
although grammatically vorrectt
theres bound to be someone thnking the I.E. is for internet explorer
Click to expand...
Click to collapse
I hadn't thought about it that way.
Changed
Read all the new terminologies
Where do I post a question, in the general section? ( sorry if I missed it in reading in post )
XPERIA U
Stock ICS 4.0.4
Rooted
drsanket_xperia_u said:
Read all the new terminologies
Where do I post a question, in the general section? ( sorry if I missed it in reading in post )
XPERIA U
Stock ICS 4.0.4
Rooted
Click to expand...
Click to collapse
Questions go in the Q&A section. Hence the name Question & Answer
Must have noticed that
Thanx
Bumping up :thumbup:
KidCarter93 said:
Bumping up :thumbup:
Click to expand...
Click to collapse
Now that was a nice introduction...:good:
im still at first one

[GUIDE]Where and how to post QUESTIONS?

Hello,
Here, I will try to bring a method to your notice which will maximize the chances of your question being answered and that too in very less time.
Introduction​
Let me introduce you to Android Question and Answer, Help and Troubleshooting Section
This section serves the purpose of a hub to people seeking answers to their questions. Any miscellaneous query related to Android devices is to be posted here. Some good guys check around for questions and try their best to solve them. They try their best to make you understand in easiest way possible
(Their Thanks button can be pressed as a reward to them )
However, we try to answer each and every question with our knowledge but sometimes, some quesions remain unanswered. This isn't the fault for people here but some reasons can be held responsible. Here are some of that:
Nobody really knows the answer.
They aren't able to understand the question itself.
The question requires higher developer knowledge to be answered.
Question is too device specific which can't be answered generally.
There are many more reasons but these are the General Ones.
So, let's try to ward off these reasons and boost the chances of your question getting answered. :highfive::victory:
Tips to avoid these conditions​
☻Generally, answer is right there, staring at our face but we don't do a little search. So, we may get our answer easily if we search a bit. So, let's start some searching before posting. :fingers-crossed:
New to XDA and trying to know it more? Here is your All in One Solution-
[GUIDE] - XDA New User Guide - Getting started on XDA
You are looking for a guide ? You may find them here -
Android Software Development Section
Android Software Hacking [General]
Looking for themes? Try here -
Android Themes Section
Want some Xposed Modules? Go here -
Xposed Framework Modules
Looking for some Apps or Games? Here -
Android Apps and Games Section
Looking for some ROMs but can't find your device forum? Maybe they are here -
Miscellaneous Android Development
Other General Items -
Android General
[IMPORTANT]​ Generally, people can't help people much because they don't own same device as in question and may tell something that may not work on that device. So, here community proves to be useful. You probably own a well known device and XDA has Forum for that. If so, you can ask there in the QUESTIONS AND ANSWERS SECTION
If you own a very popular device, you may find there forums here-
XDA Forums Index
If your device is a little older or with less activity, then you may find it's forum here-​ XDA Legacy and Low Activity Device Forums
If you think your device is a popular one and does not have any forum, then you can request one here -
Request your Device Sections here
(Please post in respective forums as your awesome community knows your device better than us. They may answer more appropriately and correctly than we may. It will certainly make you accomplish your answer easily :good​
☻Sometimes people can't understand what we are trying to convey. This may be due to insufficient information we are giving or due to us understanding that the information we gave is sufficient. If this problem gets solved, you may get your answer in one turn. This is explained in next section How to make a good question
How to make a good question?​
One thing we all agree that few things only are general in Android, so wee can't give one answer to a similar question. Many times confusion arises and people hesitate to answer because they're not sure if they will be correct or not. Many times a question badly written remain unanswered. So, These are some tips on how to make a good question and increase chances of getting it answered:
Here's an example of a good question:
Mr.GoodQuestioner said:
Good Evening/Hello/Hi,
I own a Nexus 9(11 GB) and I am running stock firmware (KLP 5.0.3), unrooted and bootloader locked. I recently downloaded an app called malALARMware v0.1 from Play Store but it didn't seem to do anything. I tried contacting dev via email but he replied me with a "lol". It was the last thing I did with my device before this happened:
When I rebooted my device today, i found that all my apps were secured by a password which I didn't set. Hope you'll help me.
Thank You
Click to expand...
Click to collapse
You will notice the amount of details given here. Don't think that we know all things. Pretend that we don't know anything and tell everything possible to us.
☻You Device with as many details possible (Android Version, carrier, root status, bootloader status, etc)
☻Problem with details
☻What you did before problem
☻What have you tried till now
☻What would you like us to do
(If forum exists for your device, try to check for a solution there)
If asking for help regarding any mod or app
☻Clear specs of the mod/app you're referring to (If possible, with link)
☻Device details and Android Version, etc
☻What you tried?
☻Where you failed?
☻Try to provide brief and to-the-point logcat always
☻What would you like us to do
Always remember, as easy you make it for us, more quickly and better the answer you get!
Bye
Have a nice visit on XDA
May your problems get solved ASAP

LG G2 Korean ROM Options (F320L F320K F320S)

I interested to learn about other Korean G2 owners success (or epic failure) with the ROM's available today on the forums.
I use LamHoang v3.3 on Android 4.2.2 which does fine as a stripped down version of stock, debloated,with English as the primary language.
Are there any other recommendations for a fully working ROM? I see very little in the way of options coming through for the F320 models even though the only difference is the existence of an SD slot (correct me as this is probably not the only difference).
Please discuss...
Thanks, Bert
The korean model has an external SD card slot and a removable battery but less at 2610 Mah
Sometimes little sacrifices must be made
For sure its the device setup I prefer. 2 batteries make over 5000 mAh combined.
But we need ROM choices because the Korean OTA doesn't work anywhere else in the world.
Sent from my LG-F320S using Tapatalk
@lbert said:
For sure its the device setup I prefer. 2 batteries make over 5000 mAh combined.
But we need ROM choices because the Korean OTA doesn't work anywhere else in the world.
Sent from my LG-F320S using Tapatalk
Click to expand...
Click to collapse
i have F320S too using stock 4.2.2 downloaded kitkat but i don't want it really
I've had a F320S for a couple of weeks now. Setting the default language to English was really easy. The main frustration I've had is with all the bloatware included by the Korean carrier.
Mobile T World, Mobile T Money, NateOn, MelOn... got knows what any of this stuff does. The only part that's English is the apps name. I've ended up freezing the applications and it's gone and forgotten. There were about 20+ apps that needed to go, but being a bit of a geek; it does irritate me that they're still taking up space.
I did try installing a new ROM but it failed multiple times (not the easiest device to flash apparently) Still, there haven't been enough irritations to turn me back to Apple.
I've own a F320K from November. It really differs from D80x, not only DS-card, battery and operator's SW, but also it have a TV and compatible with differ LTE baseband.
Also, LG FW from D802 is not compatible with F320 and vice versa. But F320 was the first device after Nexus with KitKat official update (4.4 was released on cristmas for my F320K).
I gave up on LamHoang. Confusing instructions on installation and debugging, lack of answering questions and a complete lack of a changelogs was the final straw. I installed Cloudyflex and it has been fantastic. Great support too. Light and day compared to LamHoang.
the_chinaman said:
I gave up on LamHoang. Confusing instructions on installation and debugging, lack of answering questions and a complete lack of a changelogs was the final straw. I installed Cloudyflex and it has been fantastic. Great support too. Light and day compared to LamHoang.
Click to expand...
Click to collapse
Is this the Cloudyfex you are using? http://forum.xda-developers.com/showthread.php?t=2618864
Can you please give me a link how to root and install TWRP to the F320S?
Thanks in advance
@lbert said:
I interested to learn about other Korean G2 owners success (or epic failure) with the ROM's available today on the forums.
I use LamHoang v3.3 on Android 4.2.2 which does fine as a stripped down version of stock, debloated,with English as the primary language.
Are there any other recommendations for a fully working ROM? I see very little in the way of options coming through for the F320 models even though the only difference is the existence of an SD slot (correct me as this is probably not the only difference).
Please discuss...
Thanks, Bert
Click to expand...
Click to collapse
Hello, and welcome to the forum,
Before you click the "New Thread" or "Post Reply" buttons, please take the time to read some rules/guidelines for posting in this forum:
1) Read and follow the Forum Rules:
Plain and simple. No further explanation needed​
2) Post your message in the proper subforum (see above):
All questions, requests, and help & troubleshooting needs, go in the Q&A Help & Troubleshooting subforum, if one exists for your device, and any misplaced messages will be promptly moved to their respective location. Users that make it a habit of posting in the wrong forum will be addressed accordingly. If you're unsure of where your post or thread belongs, please read the Forum Rules again.​
3) No off-topic discussion:
While some Moderation Teams may allow some off-topic discussion and the creation of off-topic threads, we do not. There is an entire General Off-Topic forum devoted to this type of discussion and there are enough threads already available to meet anyone's off-topic needs. All off-topic threads, and posts containing off-topic discussion, will be deleted promptly and without warning. If you're concerned with the amount of off-topic discussion and misplaced questions in the Development forums, please consider making a Q&A Thread for your ROM/Kernel/Project/etc.​
4) No threads or posts asking for the best/most stable ROM/Kernel/Mod/whatever, or created for the purpose of comparing Phones/ROMs/Kernels/Mods/whatever:
These threads/posts will be deleted promptly and without warning. They have a history of causing problems due to trolls, and fanboys, along with various troublemakers, and therefore are no longer allowed. Regardless of that, there is really no way to judge whether or not a particular piece of work is better than another because it's all relative to begin with. If you want to know what piece of work is better for you, install something and try it out for a while. If you don't like it, try something else. Our Developers work hard to provide us their contributions, free of charge. Please show them the respect they deserve by trying something out and giving them your feedback.​
5) Don't ask for an ETA (Estimated Time of Arrival):
Asking for an ETA is the XDA equivalent of telling a Developer that the free work they do just isn't enough for you. It usually comes across as rude and/or demanding, and most developers will take offense to it. Even if a particular Developer doesn't mind being asked for an ETA, there are many that do, and there's a good possibility that it will incite arguments in the forum. In the end, it's just best to avoid doing it altogether. If you have no other choice but to ask for an ETA (i.e. the work you're doing absolutely depends on it), then please, do it through a private message and keep it out of the public forums.​
6) Keep your signatures at a respectable size:
While members are given a great deal of freedom in creating personalized signatures, it is expected that this freedom is not abused. Abnormally large signatures are obnoxious to most users and they tend to be a major distraction from the topic at hand. If your signature is double the size of an average post or larger, expect be asked to change it. If you're not sure whether the size of your signature is within the respectable limits, feel free to contact a member of the Moderation Team that is assigned to this forum for clarification.​
7) Be nice:
It's not that hard. If you can't say something nice to someone, don't say anything at all. If you feel the need to respond negatively to someone, please refer to #8.​
8) Report all violations of the aforementioned rules/guidelines and DO NOT respond to them in the open forum:
If you happen to notice a rule violation, use the "Report Post" button in the upper right hand corner of the offending post, or send them a polite reminder through private message so they may resolve the problem on their own (for minor violations of course). Please do not respond to posts that are in violation of the rules in public. Regardless of the fact that it leaves more work for us to do when cleaning the forum, responding to them in public only compounds the issue and it puts you at risk of getting in trouble yourself. Moderators have much more effective ways of dealing with these situations than by arguing back and forth and disrupting the entire conversation, so please, let us handle it.​
If there are any questions or concerns regarding this or any other matter, please feel free to contact a member of the Moderation Team that is assigned to this forum. You can find a list of the assigned Moderators at the top of each sub-forum page.
With that, here are a few great threads to help you get the most out of your experience here...please take advantage of them:
Get the most out of XDA!!
How to make a good THREAD, POST, QUESTION or POLL
Why you get short/one word answers! (The Long Answer)
How to give constructive feedback to developers
How To Logcat
GPLv2 tips for developers
Getting a moderator's help
And as always...
Thank you, and have a great day!
Please existing threads for discussions about the existing ROMs
Thread closed

Categories

Resources