Related
Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.
Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any TOPAa-specific tweaks that others should be made aware of!
Update to this - I changed around how topic 4 is done. Feel free to re-read that section.
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
metho88 said:
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
Click to expand...
Click to collapse
For the pm disable stuff? If you find an app that does it, more power to you. I want to control Android directly, hence the reason I went with a script that utilizes that concept. The pm disable stuff is obnoxious I know - so if you do find an app that'll do it for you, have at it. I didn't want to add any more apps into the mix if it wasn't necessary .
Rhod400 in startup.txt
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
1edge1 said:
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
Click to expand...
Click to collapse
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
arrrghhh said:
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
Click to expand...
Click to collapse
yeah i do use the startup for topaz. Was just wondering. haha. thanx for clearing it up
Hi All,
Having already committed the original sin on my first Droid3, and seeing the profusion of various threads (good threads, mostly) developing here, I would like to commit a thread to be stickied that will include rooting guides, safe bloat removal guides, exploit scripts, (and we hope!) ROMs and Recoveries. If this is a good idea and the Moderators will approve of it, please help me help you help me help you by posting:
1. Type of Mod/Guide/Script/Recovery/ROM/SBF/Image/etc
2. Device it applies to (eg Droid3 US, XT8xx, country, telco etc)
3. Level of Difficulty (n00b --> coding wizard)
4. Risk Level (from installing market app --> damn near microwaving your D3)
5. External thread for file hosting, cross-linked sites, etc
6. Android version (2.3.4 --> ???)
suggestions to further categories will be appreciated!
Thanks all, let's make the D3/XT a quality, fun, and safe modding platform by working together.
Obviously, I will be the maintainer of this thread, unless someone else feels they have a religious duty to take it instead!
I would love a proper list of apps that can be frozen/renamed for when I get my droid 3.
I know there's a script and several topics/posts with 'safely to remove' apps, but most still list apps that cause minor faults/bugs like calender not working etc.
DoubleYouPee said:
I would love a proper list of apps that can be frozen/renamed for when I get my droid 3.
I know there's a script and several topics/posts with 'safely to remove' apps, but most still list apps that cause minor faults/bugs like calender not working etc.
Click to expand...
Click to collapse
I'm pretty sure that any app not relating to the Framework can be safely removed. That is a pretty short list: Citrix, the games, and that's just about it.
volcanomike said:
Something with the built in text messaging causes picture messages to not be received when disabled with your script
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
There's more stuff out there that make me not want to use the script.
I'd just want to remove all the obvious bloatware without destroying core features of the phone.
DoubleYouPee said:
There's more stuff out there that make me not want to use the script.
I'd just want to remove all the obvious bloatware without destroying core features of the phone.
Click to expand...
Click to collapse
Let's put it this way: if you can download it from the Market for Free or for Money, you should be able to zap (freeze, move, or delete) it without consequence.
Until then, wait for AOSP or rebased/ported ROMs to appear.
rynosaur said:
Let's put it this way: if you can download it from the Market for Free or for Money, you should be able to zap (freeze, move, or delete) it without consequence.
Until then, wait for AOSP or rebased/ported ROMs to appear.
Click to expand...
Click to collapse
I don't care about deleting apps that can't be downloaded from the market as long as they don't affect anything important
I open this thread for some reasons.
1. and most important: The developer thread should not be overloaded with discussions to convince me or any other user
2. I am really interested in to optimize my phone however I am still satisfied with the original JB (have not tried a possible better rom on Razr i)
3. I like some features of Moto's Blur launcher as there are the quick settings page, the circle widget and the favorite contacts widget
4. I am interested in to get a still longerlasting battery on my Razr i as it already is
5. I am sure, some of you guys think as I do.
My current questions:
1. Some of you should have had enough time to compare the battery life. Is there a real advantage when using Omar's Rom?
2. Does anyone have a recommandation in terms of Moto's quick settings page?
3. Is there a similar or better contact widget available? I like the wish gesture to open the entire widget on Moto's widget
4. Changing to Omar's Rom should be possible without wiping data if the system is on JB EU Rom. Did anyone try it without wiping data and if yes which side effects occured?
I have been following the developer thread with high interest so I hope this thread may help clarifying open questions and convincing people like me.
Edit: Oops, actually I wanted to start this thread in Q&A Forum. Maybe a Mod can move the thread to this forum.
The objective of this thread is to answer the commonly asked questions, give the newbies a little head-start, protect them from getting flamed and keep this forum focused on more important things
1 > What is root?
If you’re an Administrator on a Windows machine, you have access to the entire operating system and you can do whatever you like. That’s essentially what happens if you root your Android device. With root access, you can get around any restrictions that your manufacturer or carrier may have applied. You can run more apps; you can customize your device to a greater degree; and you can potentially speed it up in a variety of ways.
Click to expand...
Click to collapse
Basically, Rooting a phone grants you the permission to do stuff you normally aren't. Remember that the process of Rooting itself will not change anything on your phone or make your your faster. It is what you do 'after' rooting that makes a difference. Rooting just allows you to make changes that were previously not allowed.
2 > Why to Root?
One of the most obvious incentives to root your Android device is to rid yourself of the bloatware (apps that come pre-installed with your phone) that’s impossible to uninstall. You’ll be able to set up wireless tethering, even if it has been disabled by default. You can also access your entire file system, install special apps that require a root, and flash custom ROMs, which can add extra features and streamline your phone or tablet’s performance. A lot of people are tempted by the ability to completely customize the look of their phones. You can also manually accept or deny app permissions.
Click to expand...
Click to collapse
You can also get the latest android version before HTC releases it. For example we have Jellybean (4.1.2). HTC has not officially released it for our phone. Mostly they never will! You can also overclock (increase the speed of your CPU) your phone!
3 > Why not to root?
There are essentially three potential cons to rooting your Android.
Voiding your warranty: Some manufacturers or carriers will use rooting as an excuse to void your warranty. It’s worth keeping in mind that you can always unroot. If you need to send the device back for repair, simply flash the original backup ROM you made and no one will ever know that it was rooted.
Bricking your phone: Whenever you tamper too much, you run at least a small risk of bricking your device. This is the big fear everyone has. The obvious way to avoid it happening is to follow instructions carefully. Make sure that the guide you are following works for your device and that any custom ROM you flash is designed specifically for it. If you do your research and pay attention to feedback from others, bricking should never occur.
Security risks: Rooting may introduce some security risks. Depending on what services or apps you use on your device, rooting could create a security vulnerability. For example, Google refuses to support the Google Wallet service for rooted devices.
Click to expand...
Click to collapse
You must be willing to compromise with these factors before you decide to root. Personally, I haven't regretted my decision of rooting even for a second! I'm sure most of the guys on this forum feel the same way. However it is your choice.
4 > How do I root my phone?
You can either use this step by step guide
Or use this All-in-one Toolkit
5 > What is Recovery?
A recovery is a small distinct environment separate from Android that allows diagnostic updates, and the ability to perform factory resets. The main purpose of this is to provide a way to reset an Android device when it may be impossible to boot into it.
The Android stock recovery is very basic and controlled via the volume keys and power button at the top of the device.
Custom Recoveries perform the same tasks as the stock-Android recovery with a few addition features, such as the ability to make full system backups, as well as flash custom roms. It is important to note that custom recoveries are recommended to those users with rooted devices, however a rooted device is not required. Anyone with an unlocked bootloader can install a custom recovery on their device.
Click to expand...
Click to collapse
Basically, Recovery saves your ass when you screw up! But it has many other important features.
6 > What are the different Recoveries available for HTC Desire C?
Currently there are two recoveries available for HTC Desire C.
Team Win Recovery
Clockwork Mod Recovery
7 > How do I install a recovery?
Follow Step 3 of this thread. But instead of the link provided there, use one of the two links I posted in the previous question.
8 > Which recovery is better?
I use TWRP because I find it user friendly and it has got more functions.But CWM is more famous and widely supported. You can choose what you like.
9 > What is a Custom ROM?
A stock ROM is the version of the phone's operating system that comes with your phone when you buy it.
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way.
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, strip them of garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow.
Click to expand...
Click to collapse
My definition - A Custom ROM is a developer's idea of what the phone 'should have been like'. He takes the stock rom and modifies it to improve performance, looks, animations, battery life etc.
10 > Why to install a Custom ROM?
Updated versions: You can load the latest and available Android versions which can make your old phone look new.
Great number of feature filled custom ROMs: It will be a chaotic task for you to find the apt one as there are bunches of great custom ROMs available for different devices.
Personalization: There are a number of features that can be customized to suit your taste and working environment. For instance, Custom themes can bring a new look and feel to your device.
Improve performance: The custom ROMs allow its users to find out the unnecessary apps they have on their device and helps them to get rid of them, thus increases the speed of processing and improves battery life.
Install Apps on SD card: This is currently not possible with stock ROMs. If your phone ran out of space occasionally when install new apps this is a killer feature to have.
Better signal and quality: Custom ROMs help you to improve your base-band which in turn increases the signal and quality of your phone call.
Click to expand...
Click to collapse
Other reasons that you won't find on Google - "The thrill factor involved", "To show off to your friends" and "Because you can!"
11 > Why not to install a Custom rom?
Bricking: This is one of the main reason why people hesitate to root their devices. Some devices after the rooting process may become useless and the only option left with you is to get a new one as the manufacturer will cancel the warranty if they find any attempts of rooting.
Loss of all Data: When you install a new custom ROM, it will clean up your system and therefore you will loss all your installed apps and data.
Risk Factor: Most of the apps will be open source and the trust you have on developers may cause a potential risk to you in the future.
Reboot: If the rooting is not successfully done, the device may enter to an infinite loop of booting.
Click to expand...
Click to collapse
Even though this may seem concerning, it will happen only if you don't follow instructions correctly or do something extremely stupid. As of now, there is no way to completely brick an HTC Desire C! You can fix 'Loss of Data' by taking a backup and you can fix reboot by using the Recovery mode we discussed earlier.
12 > What are the different Custom ROMs available for HTC Desire C?
Look HERE. Take your pick!
13 > Which is the Best ROM for this phone?
NEVER EVER ASK THIS QUESTION!! This is a very subjective question. It differs from person to person. It takes a lot of time/energy/efforts to build a custom ROM and asking this question is a very big insult to the makers of these ROMs! Try out different ROMs and choose what you like.
14 > What is a Kernel?
The central module of an operating system. It is the part of the operating system that loads first, and it remains in main memory. Because it stays in memory, it is important for the kernel to be as small as possible while still providing all the essential services required by other parts of the operating system and applications. Typically, the kernel is responsible for memory management, process and task management, and disk management.
Click to expand...
Click to collapse
If our phone was a movie, the Kernel would be the director! It is the brain of our phone. And even though it is the most important part of our phone, it is just a single (.IMG) file and only a couple of MBs!
15 > What are the benefits of a custom Kernel?
Adjust CPU frequencies and set profiles like OnDemand, Battery Saving, etc.
Underclock and overclock CPU speeds
Underclock and overclock GPU speeds
Adjust voltage
Adjust touch screen sensitivity
Equip your phone with BLN (backlight notifications)
Custom recovery that allows backups and restorations of entire ROMs as well as installation of .zip files
Minimum screen brightness pushed past the limitations of stock kernel
Conserve battery (with the right settings)
Click to expand...
Click to collapse
There are a lot of Technical advantages of a good coded custom kernel. Fortunately, you don't have to worry about all that. Most of the work is done by the developer himself.
16 > How to flash (install) a custom kernel? OR How to flash boot.img?
You can either use this Auto Boot.img Flasher
Or read this
17 > Which is the best Kernel for this phone?
NEVER EVER ASK THIS QUESTION!! This is a very subjective question. It differs from person to person. It takes a lot of time/energy/efforts to build a Kernel and asking this question is a very big insult to the makers of these Kernels! And remember, not all Kernels are compatible with all roms.
REMEMBER - Use Sense Kernel with Sense ROMs. Use CM10 Kernel with Cm10 based ROMs. It can't get much simpler.
18 > How to overclock my phone?
You cannot overclock with a stock kernel. You MUST have a custom kernel to overclock your phone. Once you have a custom kernel you must install either 'SetCPU app' or 'NoFrillsCPU app'. You need any one of these to control the CPU speeds.
19 > Is it safe to overclock my phone?
I will not say this is completely safe. But i have yet to come across somebody who actually screwed up his phone just by overclocking. So use at your own risk. Also remember that all phones have a different capacity to overclock. If you try to overclock it higher than that, it will go into a 'reboot loop'. But you can fix that by flashing a lower frequency Kernel. It is not a problem.
Miscellaneous Questions > What is GAPPS?
Gapps is short for Google Apps. These are apps made by google like Google Maps, Playstore, Gmail, Google search etc. They are available to download in the Play Store and can also be flashed as a zip in recovery mode. For a complete list of apps click HERE. Not all Gapps are available in all countries.
> How to increase battery life? OR How to save battery?
Read THIS (Not only read it but apply it too! ) . If nothing else works, buy a better battery.
> Task Managers - Good or Bad?
Long story short - If you don't know what you are doing, Stay away from task killers. If you think that constantly killing apps will free more RAM and therefore speed up your device, you are mistaken. The app that you kill will restart itself and this will cause you more of your phone's resources than you think you saved. In fact, task managers do more harm than good. A lot of Developers agree with this. Android itself does a very fine job of managing tasks so that you don't have to mess with it.
Read this in-depth article on task managers HERE
> What is Clean Flash? What is Dirty Flash?
Clean Flash is wiping cache, dalvik cache and data before flashing a zip or installing a ROM through recovery.
Dirty Flash is wiping cache and dalvik cache only
Clean flash is much recommended and causes less problems down the road. If the instructions specifically ask to to clean flash, you must do so. You will lose all your data when you will clean flash. But dont worry, clean flash will not affect your internal or external memory card. You will lose your apps and settings and game data. Your phone will act like it is just out of the box.
You can Dirty flash when flashing small modification zip files. Or perhaps a minor update to the rom (unless the instructions ask you to clean flash). You will not lose any data while Dirty flash. But sometimes, you are more likely to face problems like apps closing which could have been prevented by Clean flashing.
Personally, i always clean flash when installing a new Rom. It is a good habit to follow in the long run.
> What is ADB?
ADB stands for Android Debug Bridge. It is a very useful tool. Using ADB, we can control our android phone using our PC. We can copy or delete files, install or uninstall apps, take a logcat, reboot our phone and a lot of other functions. Here is a really cool guide to ADB.
Here is the list of the common adb commands :
adb devices – lists which devices are currently attached to your computer
adb install – lets you install an Android application on your phone
adb remount – Remounts your system in write mode – this lets you alter system files on your phone using ADB
adb push – lets you upload files to your phones filesystem
adb pull – lets you download files off your phones filesystem
adb logcat – starts dumping debugging info from your handset to the console – useful for debugging apps
adb shell – drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
> How to get a logcat?
There are basically 3 ways to get a Logcat:
Using an app (Catlog ; aLogcat ; Logcat Extreme)
Using terminal emulator
Using ADB
I personally use ADB whenever I have to take a logcat. Also, it is the only method where it is possible to take logcat when the phone boots (bootanimation).
For Method 3, connect your phone to the PC, open command window, navigate to C:\Program Files\Android\android-sdk\platform-tools
Then type
Code:
adb logcat > (any name).txt
Wait for some time as the logcat builds. Then press Ctrl+C to stop taking logcat. You fill find a .txt file in the platform-tools folder. That is your logcat! Now upload it to a site like Dropbox and post a link when required.
Make sure you have USB Debugging enabled when doing this.
> How does the thanks meter fill up?
ngoralph said:
1st bar - 26
2nd bar - 51
3rd bar - 101
4th bar - 201
bug here, never gets to 5 bars, probably 501 if fixed.
6th bar - 1001
7th bar - 2001
8th bar - 5001
9th bar - 8001
Maxed! - 10000
Click to expand...
Click to collapse
> User Titles on XDA
ngoralph said:
- Junior Member - New members with less than 30 posts.
- Member - Members with more than 30 but less than 100 posts.
- Senior Member - Members with 100+ posts.
- Recognized Contributor - A title given to members who have helped people with various problems. You can apply for this position or ask a Forum Moderator, Senior Moderator, Recognized Contributor to nominate you. They don't give it away for free though; you have to meet some requirements.
- Recognized Themer - A member who's known for original themes. You can apply to the Senior Moderators yourself, or ask a Recognized Contributor to nominate you.
- Recognized Developer - A title given to a member for his/her work in his/her device-specific development. You can apply to the Senior Moderators yourself. I don't think anyone can nominate you here. The developer committee assesses your overall activity and decides whether you're eligible for this position.
- Elite Recognized Developer - This title is given to Recognized Developers who have provided outstanding work, way beyond the knowledge of us mere mortals. A Recognized Developer is re-assessed by the developer committee before being given that title.
- Forum Moderator - This title is given to Recognized Contributors who are responsible enough to handle a forum on their own with some other such members of course. They have to fill out an application (which is no longer available now) and then the moderator committee approves of them.
- Senior Moderator - Senior Moderators are in charge of the whole site-wide support for Forum Moderators and nitty-gritty business that Forum Moderators cannot look after.
- Administrators - Next comes the admins who are responsible for everything as a whole. Each look after a specific part of XDA.
- MikeChannon's the dude behind all this. He's the Forum Administrator.
Other titles you may come across are
- Moderator Committee - sits on the Mod Committee
- Developer Committee - as above, but for Developer Committee
- XDA Newswriter - publishes articles for the Portal (front page)
- Retired xxxx - have since officially 'left' their XDA position
Click to expand...
Click to collapse
Thread Layout Tips (by me4488)
Here are some basic Layout tips that will make your thread look more appealing, and pleasant to read.
1 > You need to have all of the basic 5 stepping-stones for every thread you create.
ROMS: Features, Requirements, How-to, Screenshots, Download links. (Optional: Notes/Warnings you may add)
KERNELS: Features, How-to, Download links. (Optional: Benchmarks)
THEMES, APPS AND MODS: Features, How to, Download links, Screenshots. (Optional: Play store links.)
GUIDES: FAQs, Credits, Links, Explanations. (Optional: Personal comments.)
2 > Optional but highly recommended.
Some of you guys let this pass over your head, but i cannot emphasize enough how much you need to have those.
CREDITS - Thank the people who helped you during your hard work. It really helps you establish some good allies and prevent arguments. Not to mention the warm sensation in an assistants tummy when he sees his name in a thread that exploded.
CHANGELOGS - Please add every single change you make when you update your work. Its really frustrating sometimes, to wait for a big update and then have to go through everything to figure out what it did. Also it helps yourself to stay organized and aware of the changes you make, because let's admit. We all forget.
3 > Follow the rules.
Stealing, swearing, and blaming in an OP will get you banned.
Remember to set up a github where all the changes to your work are made. Its against the rules to not do so. Don't abuse caps, big fonts, colors, styles, etc. It just makes people want to report your thread.
4 > Cosmetics
Use colors and [Bold] to separate the different points of your thread(Headers/Sub-Titles). For example the basic 5 points should be in bold and a different color so that readers can easily make out what they are going to get information on. This thread itself is an example on good cosmetics.
5 > Optional stuff
Regular updates on the working process are greatly appreciated by the users. It shows that you are interested in providing updates and communicating.
Mirrors to your work are really helpful, you might upload them yourself or you may let other people do so, but either way, it ensures that everyone has access to your work at any point of time.
Videos showcasing the work you are presenting. Its always nice to have a visual demonstration of what you are offering, even though it may be a little hard to execute.
6 > Some tips:
Have the headers centered and use bigger fonts on them.
Don't use bright or hard to read colors like cyan, yellow or pink, it irritates the eyes and makes it less appealing to people that are willing to read.
Follow the example you started with. If you decide to make your layout in a specific manner don't go changing it mid-way.
If in doubt, reference other threads for examples.
Get creative, use your imagination, think outside the box. Innovation is good.
Examples of threads that have great layouts, and a basic template.
Great Layouts: Example #1 ; Example #2 ; Example #3
Everything is well organized here and cannot be criticised.
Note: Example #1 is missing the changelogs because the dev just helped us out. Support is up to us.
Good/Mediocre Layouts
Example #1 - The layout itself is very well structured but those little details like the bright yellow and the monotone text size/style.
Example #2 - Not the best way to post a thread. Most times 2 posts are unnecessary. Features list missing. Also i am a little against the excessive urging for people to thank/donate to you.
Bad layouts - Any thread missing the 5 important stepping stones, or not following common sense.
Experiment with your own styles, and use common sense, asking yourself “Jee, will this look good if I did this and that?”
P.S. The examples given were chosen based on my sense of giving examples and are completely randomly chosen.
Proper Forum Manners (by aashay960)Being a member here on XDA, you are expected to behave in a manner that will not cause any inconvenience to your fellow members. People are here because they choose to be here, because they like being here and helping out. They do not owe you in any way. They can choose not to help you if they find your manners disrespectful. You are here because you need their help. Disrespecting any one member or not following rules can leave a negative impression on the other members about you and they might choose to ignore you.
XDA Forum Rules <-- Read this
Here are some points to help you follow proper forum manners/etiquette.
1 > I have a Question, What should I do?
The first thing you should do is use the ‘Search’. Xda has an excellent and organised searching mechanism. You can search within a particular thread, a particular forum or search the entire website at once. It is very likely that you are not the first person to encounter this problem. If searching on XDA does not satisfy you, Search on Google.
From my personal experience I can tell that searching is indeed the best way to solve your problem. More often than not, I find the answer by searching rather than asking on a thread.
If you still cant find the solution, post your query in the Q and A section.
Don't Post vague titles like “HELP!”, “EMERGENCY!” It will not attract more people to your thread to help you. In fact, it irritates people. Xda members will try their best to help you with all kinds of problems - small or big. It would be much more appreciated if you name your thread clearly like [Q][NAME OF PROBLEM][WHAT ROM]. And avoid posting things like “HELP!!” or “pls halp!” in your posts as well. Doing so will not be any help.
2 > I am excited about the release of the next version of this rom. What should I do?
Never ask things like “When will you release the next version?” “How much more time to the next release?” “Please release the next version soon”. This is called asking for ETA and this is not welcomed here. The developers pursue this as a hobby and do so in their free time. They will release the Rom when they feel it is ready to be released. Trust me, they have no gain keeping it to themselves. They WILL share it with you.
Also, do not post things like “Waiting for the ROM” or “Excited about the next release”. They do nothing to help others and just add to the clutter.
One rule to follow before posting anything is to ask yourself - Will this make a difference? If the answer is no, don’t post it.
3 > I am facing a bug with the Rom. What should i do?
Be descriptive about your problem. Try to give as much information as you can about it rather than writing “pls help”. Mention the name of the rom, name of the kernel. Provide screenshots if you think they might help. Also mention what you did ‘before’ you found the bug/problem. It is often the last thing you do that messes up your ROM.
Also, Learn how to take a logcat. There are hundred of guides showing you how to do it. Use the Search box. It’s not Rocket science..
4 > I really like somebody’s work and would like to share it. What do I do?
Make sure you ask permission from the original maker of the guide/rom/kernel/app you want to share. And make sure you mention his username in your thread and thank him for doing his work. It is also recommended to provide a link to the original thread.
5 > I really like somebody’s work. I want to tell him that I appreciate it. What do I do?
This is pretty obvious but, HIT THE THANKS BUTTON. The developers feel really happy when you press the thanks button. It encourages them to keep working hard.
The thanks button is enough to show your gratitude. You don’t need to post things like “thank you” or “i really like your work” or “Great job”. This will increase the clutter in the forums. This is what the thanks button was made for.
Some developers also give you the option to donate money to them. If you would really like to show your appreciation, you can click on the “Donate to Me” button in the signature, or under their profile picture.
6 > Another user is disrespecting me or disobeying the rules. What should i do?
Use the “Report Post” button (the exclamation mark on top of the post). DONT fall down to his level and start disrespecting or abusing him. That could result in both of the users getting banned.
Wanna learn more?
[Lists]Guide Ride-From a Newbie to a Dev, Get all you need here
[READ FIRST] [REF] Dictionary for n00b - What is.../What does ...mean?
This thread will always be a 'Work in Progress'. Please post any suggestions/questions/additions/feedback
I suggest making it sticky.
Great work , much appreciated :good:
Added - What is GAPPS?
Great job on this topic. Just 2 things: Undervolt is most commonly used. Also " therefor " has an e at the end( Therefore ).
Code:
therefor: adv. for that [thing]; for that, for it
Ex. I will give you my pocket knife if you will give me your watch therefor.
therefore: adv.consequently, hence
Ex. I think, therefore I am. I was afraid; therefore I ran.
me4488 said:
Great job on this topic. Just 2 things: Undervolt is most commonly used. Also " therefor " has an e at the end( Therefore ).
Code:
therefor: adv. for that [thing]; for that, for it
Ex. I will give you my pocket knife if you will give me your watch therefor.
therefore: adv.consequently, hence
Ex. I think, therefore I am. I was afraid; therefore I ran.
Click to expand...
Click to collapse
1) If I'm not mistaken, our phone does not have a kernel with undervolt support right?
2) I know the meaning/spelling of therefore. Must be a typing mistake. Haha
aashay960 said:
1) If I'm not mistaken, our phone does not have a kernel with underclock support right?
2) I know the meaning/spelling of therefore. Must be a typing mistake. Haha
Click to expand...
Click to collapse
Thanks for taking that in mind man <3 I'm just a grammar nazi, sorry bout that. And I undervolted it to 75 MHz.
me4488 said:
Thanks for taking that in mind man <3 I'm just a grammar nazi, sorry bout that. And I undervolted it to 75 MHz.
Click to expand...
Click to collapse
I think there is a misunderstanding between us. There s a difference between underclock and undervolt. What you are talking about is underclock. Undervolt has got to do with how much voltage the battery is supplying. We can reduce it to save battery but it causes stability issues.
PS - I'm all for correct grammar too And Congratulations on becoming a senior member! :good:
Added - How to save battery?
aashay960 said:
Added - How to save battery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=991276( save battery+performance).
aashay960 said:
I think there is a misunderstanding between us. There s a difference between underclock and undervolt. What you are talking about is underclock. Undervolt has got to do with how much voltage the battery is supplying. We can reduce it to save battery but it causes stability issues.
PS - I'm all for correct grammar too And Congratulations on becoming a senior member! :good:
Click to expand...
Click to collapse
I am a senior member? Wow xD Thanks for actually telling me, i dont pay attention to that stuff. If you dont mind, im going to look for some more stuff that you can add here so we can make this more helpfull. For example, you can dedicate a little paragraph for task killers. Here is the link Cons (and no pros)
me4488 said:
I am a senior member? Wow xD Thanks for actually telling me, i dont pay attention to that stuff. If you dont mind, im going to look for some more stuff that you can add here so we can make this more helpfull. For example, you can dedicate a little paragraph for task killers. Here is the link Cons (and no pros)
Click to expand...
Click to collapse
Thanks bro. Any help would be appreciated. My college started today so I'm gonna be super busy. My college is 1 and a half hour away from my home!
But I will still continue to give my time and effort for this forum because i love it and the people here.
Ohh I have already read that article before!. But everyone seems to have a different view about task killers. I myself don't use it. So honestly I don't know what to believe..
aashay960 said:
Ohh I have already read that article before!. But everyone seems to have a different view about task killers. I myself don't use it. So honestly I don't know what to believe..
Click to expand...
Click to collapse
Ive seen recognized developers talk about how bad task killers are. I would rather believe them than the people who download task killers to have more ram which is actually unimportant. Like said in the article, the low memory killer does its job nicely without the need of additional help.
This and This
So my thought is completely against them.
Also keep your studies at 1st priority. :3
me4488 said:
Ive seen recognized developers talk about how bad task killers are. I would rather believe them than the people who download task killers to have more ram which is actually unimportant. Like said in the article, the low memory killer does its job nicely without the need of additional help.
This and This
So my thought is completely against them.
Also keep your studies at 1st priority. :3
Click to expand...
Click to collapse
Looks good. I use watchdog too.. I will add it soon :thumbup:
ADDED - Task managers - Good or Bad?
Added - Clean flash and Dirty flash
So, I wonder?
I've been digging through the system files in my unlocked, rooted UA v40, and except for the apps that came installed with the phone, there's also some in the root that didn't come alive, just taking up space? I know, there's no need to clear space, but I still wonder!? And it also seam to exist some dalvik even for the apps that never came alive in the first place?
Following today's Android rules, is it still possible to clear Dalvik?
Say, if I delete the apps in root/system/product that aren't even installed, will it scr.. something up?
I guess there's some kind of script executed while flashing the rom. If I delete apps (in the right place), and factory reset my phone, will that corrupt something? Is there a file (command/script) I can edit in root, that decides what app to install, to make this work?
Back in the days I deleted unvanted apps before flashing the rom, but I understand it's different today...
Not very important, but would be nice to know
Not a dev but thought I'd throw in some thoughts. We don't have any "stock based" dev to bug regarding stock fw really.
From my own digging through newer fw releases, it seems that LG hired some really lazy mofos as coders. Looks like they create new fw from old ones, then updated it to new versions plus some tweaks to suit the target model.
For a programmer that'd make sense since you already have the base code, you just change modules and libs as needed. However, in LG's case, their guys didn't bother to remove anything that was already there. They just kept adding on stuff. That's where you see the unused apps (and also explain why stock fw sizes keep getting bigger). Hell, I even found G8 specific settings in the service menu earlier today. Best I can tell, there aren't any symlinks that tie back to these unused apps, so, technically, removing them won't break anything. But given how sloppy the existing structure is, it wouldn't be surprising if it does either.
Now dalvik on the other hand, that' and interesting point. Since dalvik was dropped when google implemented ART, it theoretically, shouldn't even be on the phone. Where did you find those?
That's just stupid of LG
I mean, what does "Airmotion" do in v40? Hahaha!
Oh, I still say Dalvik, aware of art.
Thanks
This is what I mean
This is one of the apps that wasn't really installed to be used in v40. Is it normal that one of those apps still got art files? So if I was to delete this app, can I delete the linked art files too?
Can anyone port the v40 camera app for lg v30 pie?
This was my main question:
I guess there's some kind of script executed while flashing the rom. If I delete apps (in the right place), and factory reset my phone, will that corrupt something? Is there a file (command/script) I can edit in root, that decides what app to install, to make this work by factory reset?
neocyke said:
Not a dev but thought I'd throw in some thoughts. We don't have any "stock based" dev to bug regarding stock fw really.
From my own digging through newer fw releases, it seems that LG hired some really lazy mofos as coders. Looks like they create new fw from old ones, then updated it to new versions plus some tweaks to suit the target model.
For a programmer that'd make sense since you already have the base code, you just change modules and libs as needed. However, in LG's case, their guys didn't bother to remove anything that was already there. They just kept adding on stuff. That's where you see the unused apps (and also explain why stock fw sizes keep getting bigger). Hell, I even found G8 specific settings in the service menu earlier today. Best I can tell, there aren't any symlinks that tie back to these unused apps, so, technically, removing them won't break anything. But given how sloppy the existing structure is, it wouldn't be surprising if it does either.
Now dalvik on the other hand, that' and interesting point. Since dalvik was dropped when google implemented ART, it theoretically, shouldn't even be on the phone. Where did you find those?
Click to expand...
Click to collapse
I noticed that on the V30 already too.
Settings are enabled/disabled depending on the props set, and which device its running on, some you should even be able to activate/deactivate during runtime...
Makes things way easier to develop that way, yes... but also unneccessarily bloats the whole UI... should have set flags during compilation to fully exclude the code (e.g. how the HALs do that lol)