[Q] bugreports, lag, ICM mode - Desire HD Q&A, Help & Troubleshooting

Hello,
My /sdcard/bugreports/ directory is full of bugreport- txt (each ~4mb)
Can this by caused by USB debugging enabled ?
Also one more question - what application can generate these messages?:
[46610.035736] LeaveICM: leave ICM MODE done !!!
[46610.288085] EnterICM: enter ICM MODE done!!!
I get these every 2-3 seconds in OSmonitor (dmesg), and bugreports .txt files is full of these lines. What application generates this? How to disable it?
Can it by related with DHD lag? For example app menu is scrolling so laggy!
My DHD is unrooted
USB debugging is enabled because of init 100%cpu bug
Kernel: Linux version 2.6.32.21-gf3f553d (htc-kernel and18-2)
Only few applications is installed

Yes, the .log files are created because usb debug is on.
Hmm but i don't know which app causes these lines. I know it's a huge effort, but do a full wipe and check if these lines are still there. If not, reinstall your apps one by one and check if these lines occur again. So you should be able to figure out which app causes them.
Sent from my Desire HD using Tapatalk

Full wipe - it's Factory reset?
Because I did it and nothing changed.

dkbrz said:
Hello,
My /sdcard/bugreports/ directory is full of bugreport- txt (each ~4mb)
Can this by caused by USB debugging enabled ?
Also one more question - what application can generate these messages?:
[46610.035736] LeaveICM: leave ICM MODE done !!!
[46610.288085] EnterICM: enter ICM MODE done!!!
I get these every 2-3 seconds in OSmonitor (dmesg), and bugreports .txt files is full of these lines. What application generates this? How to disable it?
Can it by related with DHD lag? For example app menu is scrolling so laggy!
My DHD is unrooted
USB debugging is enabled because of init 100%cpu bug
Kernel: Linux version 2.6.32.21-gf3f553d (htc-kernel and18-2)
Only few applications is installed
Click to expand...
Click to collapse
Those lines are normal, albeit a bit verbose. No need to worry about them. They wont slow down your phone.
You can install a custom kernel to remove it.

Related

[MOD] LoSD - LoS Repair Daemon v1.3.1 [Updated 2012-08-08]

NOTE:
If you came here looking to fix recent problems with LoS in recent builds of Jelly Bean, be aware that this utility has not been tested with JB or ICS at this time. I figured LoS was a solved problem, so retired the project. I'm looking into it again, and may have something out later depending on how much has changed in the OS updates.
Introduction
Has your phone ever had a circle with a line through it instead of signal bars? Has your phone ever shown signal bars, but all calls and texts fail until you reboot? Well, those situations are called Loss of Service, or LoS, and while we can't actually stop them from happening yet, those situations can be detected and repaired. The Loss of Service Daemon (LoSD) does that, so you don't have to!
It does this by:
Restarting problematic radio daemons when detected.
Rebooting when all attempts to fix have failed.
In addition, it can create a log dump of various system logs for debugging purposes.
Requirements
Phone must be rooted.
An init.d compatible kernel.
Busybox must be installed.
Many ROMs and custom kernels do this automatically, but check the feature of your basic tool-chain before installing.
Installation
All files are located in my github projuct, if you'd like to get a closer look at how all LoSD works. But what you really want to to know:
Download LoSD
This will be a file you can flash using ClockWorkMod. Simply copy it to your internal or external SD card, reboot into recovery, and flash. The next reboot will be running LoSD.
NOTE : Installing LoSD will automatically remove -viperboy-'s LoSChecker, as they should not both run at the same time.
Download LoSD Uninstall
The above package will fully remove all traces of LoSD from your phone. Flash if you're having problems or no longer need/want LoSD.
WARNING! Do not wipe anything before or after install of this utility! It is not a ROM. You will be left with an unbootable system.
Usage
If you installed the flashable zip, your phone will automatically launch the LoS daemon at every boot.
Or you can call it manually to obtain debugging logs!
Code:
LoSD dump
When called with the 'dump' command, LoSD will dump all debugging logs and exit, creating a timestamped directory in LOGPATH (/data/local/LoSD by default), as well as a tar archive named logs.tar.gz. This lets you capture situations where LoSD did not detect a LoS, and send the logs for analysis.
Frequently Asked Questions
These are taken from the README file that gets installed with LoSD. There's more dev-related info in that file, so give it a look!
Q: Will this restart the radio or the phone if I lose 4G?
No. 4G is actually a separate radio from the CDMA radio used for texts and phone calls. This script ignores the 4G radio entirely and can not trigger no matter what happens to the 4G radio.
Q: Will this restart the radio or the phone if I'm using WiFi?
No. Turning on WiFi *will* disable your 3G data, but will leave the CDMA radio in an available state so you can still receive phone calls and texts. The LoS daemon knows the difference, so feel free to use your WiFi as you please. LoSD may restart your radio while you're on WiFi, but only because your CDMA radio stopped responding and you wouldn't have received any texts or phone calls if it didn't try and fix the radio.
Q: Where do I find the logs?
Logs produced when the radio is restarted, or the phone is rebooted, are stored by default in /data/local/LoSD in a directory time and date stamped for when the fix was attempted, or a reboot was triggered.
Q: Help! My log directory is getting huge!
By default, LoSD will not dump system logs when it repairs a LoS. But you may have enabled it on your own if you modified the configuration file. If you're in a spotty coverage area, the log directory may start to fill with several timestamped log dumps, each of which are around 5MB. If you'd like to stop this, please ensure your LoSD.ini configuration file does not contain the following line:
Code:
DUMPLOGS=1
Such a line will enable log dumping, which again, is disabled by default!
Q: I think I have LoS the daemon didn't detect. How do I get logs?
Very easily! LoSD has a built-in logging command! Just type this into a terminal, or an 'adb shell':
Code:
su
LoSD dump
This will create a timestamped directory just like LoSD had detected it. In addition, a file named logs.tar.gz will be dropped in your LOGPATH directory (that's /data/local/LoSD by default) you can send to us. We recommend putting it in dropbox, or some other binary-file hosting site.
Credits
Many thanks to -viperboy- for the original concept of checking for LoS with a script.
HaiKaiDo gave us the idea of restarting the radio daemon before rebooting.
If I'm forgetting anyone, please PM me!
Configuration
There are several settings you can apply to the LoS daemon while it's working. These settings should be placed in a file named LoSD.ini in the /data/local/LoSD directory of your phone. If you change any settings, you must either restart the daemon, or reboot your phone.
Currently recognized settings:
DEBUG
Many log entries are only informative in nature and can be very noisy. If you are having trouble and want to see LoSD activity reported in the system logs and LoSD.log, set this to 1. Default is 0.
DUMPLOGS
Whether or not logs should be dumped during a LoS repair or system reboot. Should be 0 for false, or 1 for true. Default is curently 0.
LOGPATH
Full path to where logs should be dumped. This is also where LoSD keeps its own LoSD.log file. Default is /data/local/LoSD because the daemon knows that directory exists. Feel free to place it somewhere on your SD card. If this directory does not exist, LoSD will attempt to create it for you. Please make sure the path is writable!
RESTARTS
How may times should the daemon attempt to restart the radio before giving up and initiating a system reboot. Default is 2. This setting was primarily defined because ghost LoS can sometimes degrade into full LoS, and subsequent radio restarts may be necessary to regain service.
RESTART_LIMIT
How many successful radio restarts before LoSD considers the phone state tainted? Too many RILD restarts may damage other services, or cause other unknown side effects. After this limit is reached, further LoS events will not result in an RILD restart, but a full reboot. Default is 3.
SLEEP
How long to wait between radio checks, in seconds. Default is two minutes.
Example:
Code:
LOGPATH=/sdcard/los
RESTART_LIMIT=1
Again, if these settings are changed, you must either restart the LoS daemon, or restart the phone. To restart the daemon, execute the following in an ADB shell or terminal:
Code:
su
killall LoSD
nohup LoSD &
The 'nohup' is there to prevent the command from attaching to your TTY, so you can disconnect without your session hanging. Feel free to omit this if you were just going to close your TTY.
Change Log
Version 1.3.1
Added third Airplane mode check for ICS firmwares.
Third firmware check also works on phones with disabled logcat.
Version 1.3.0
Improved CDMA connection FAILED detection.
Added second Airplane mode check for EL13, EL26, EL29 firmwares.
Version 1.2.0
Added debug log level.
Moved several informative messages to debugging only.
Debugging is now disabled by default.
Tweaked RILJ error detection for RIL_REQUEST_CDMA_GET_SYSTEMPROPERTIES.
Can now ignore false positive ghost LoS caused by phone calls.
Phone call and Airplane mode now checked before anything else.
CONNECTING status no longer skips LoS check.
Added ghost LoS check for CDMA 'Unknown data error' messages.
Version 1.0.0
Log dumping is now disabled by default.
Now uses 'setprop ctl.stop/ctl.start' to try restarting RILD nicely.
Does a quick check to prevent multiple running copies.
Added a radio restart limit to avoid glitchy post-fix systems.
Clear radio log in case of false positive ghost LoS.
Version 0.9.0
Added non-LoS check for transient CONNECTING status.
Now check for ghost LoS *after* standard LoS.
Calling LoSD with 'dump' now dumps and tarballs all debugging logs.
Version 0.8.1
Fixed bug in grabbing bugreport dump.
Now removes -viperboy-'s LoSChecker on install.
Removed LoSD logcat dump in favor of persistent LoSD.log.
Version 0.8.0
Now maintains a separate log for tracking all LoS events.
Added DEBUG configuration setting.
Version 0.7.1
Fixed typo in AirplaneMode check. Should no longer reboot in airplane mode.
Version 0.7.0
Fixed bug in radio log dump.
Now tries multiple times to restart RILD before reboot.
Added DUMPLOG as boolean to disable / enable log dumps
Added RESTARTS as number of RILD restart attempts before reboot.
SLEEP, LOGPATH, DUMPLOG, and RESTARTS are now user configurable.
Now searches for /data/local/LoSD/LoSD.ini for config settings.
Version 0.6.0
Initial public release
Good deal, the more people working on this the better and I know viperboy had a lot of work going. I'll give your version a go today.
Sent from my SPH-D710 using xda premium
Just_s said:
Good deal, the more people working on this the better and I know viperboy had a lot of work going. I'll give your version a go today.
Click to expand...
Click to collapse
Haha. Thanks. The way I see it, Viper has his hands full with way more important projects right now. With his ROM, the EK02 pull, the ICS work... why should he have to worry about this too? He was going to rewrite his script anyway, so I just took the opportunity to do it while he was distracted being useful.
While I was at it, I just... added a few things. That's all.
installing now.. thanks for this, and thanks viper
How about an option that appends to a file a date and time that the los happened instead of the full log? How about a notification after it fixed a los? The viper script made the phone appear like I never have los. Good but I still would like to know how often it happens.
gedster314 said:
How about an option that appends to a file a date and time that the los happened instead of the full log? How about a notification after it fixed a los? The viper script made the phone appear like I never have los. Good but I still would like to know how often it happens.
Click to expand...
Click to collapse
I can do the feature to keep a running tally of LoS, but so far as I can tell, there's no way to send notices from the command line. If there is, I can't find it. Sorry.
Sent from my SPH-D710 using xda premium
Question... Do I need to be uninstalling this script everytime I update, or just flash over the old? -Grand
Sent from my SPH-D710 using XDA App
grandmastem said:
Question... Do I need to be uninstalling this script everytime I update, or just flash over the old? -Grand
Click to expand...
Click to collapse
Just flash it over the old one. I've made the install smart enough to install over previous versions of LoSD. If you're running -viperboy-'s LoSChecker, you should run his uninstall first, though.
Also:
Edited OP to reflect new 0.8.0 version. Added a setting to suppress the Info-level log messages. Now it also keeps a LoSD.log in the LOGPATH directory so you can keep a log of its activity between reboots without having the log dumping enabled.
I also updated the Configuration and Change Log sections.
After u install it wat u do to run it or do it run on its own
Sent from my SPH-D710 using xda premium
pats4life100 said:
After u install it wat u do to run it or do it run on its own
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It runs on its own.
Is this JarJar Binks?
Sent from my SPH-D710 using xda premium
Just_s said:
It runs on its own.
Is this JarJar Binks?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1 sir.....+1.......
Also thanks for the shoutout trifthen! Nice work
Giving this a go. I'll report in with anything that seems odd. I definitely get LoS on occasion, and the girlfriend doesn't approve haha.
trifthen said:
I can do the feature to keep a running tally of LoS, but so far as I can tell, there's no way to send notices from the command line. If there is, I can't find it. Sorry.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Trifthen, I'm glad you took this over cause I had alot of other stuff going on. If I see any enhancments, I will send them your way. Also, you have my permission to include the line in your updater-script to remove my LoSChecker because I don't want it to affect users who use yours and don't uninstall mine. Just add this into your updater-script:
Code:
delete("/system/bin/LoSChecker");
And you can also add a line to remove my logs as well if you want. The files might be taking up a good bit of space...
Code:
delete_recursive("/data/local/LoS");
Those should be right, I'm at work so I'm typing from memory
For counting when LoS happens, you could just write a timestamp or something else into a file (>> adds into a file, > overwrites any data in a file) and then just do a wc on it (-l option reads lines, I think) which would give you the number of times that you had LoS from reading the amount of lines in the file. Just a thought.
Yay no more this ****
Sent from my SPH-D710 using xda premium
-viperboy- said:
Trifthen, I'm glad you took this over cause I had alot of other stuff going on. If I see any enhancments, I will send them your way. Also, you have my permission to include the line in your updater-script to remove my LoSChecker because I don't want it to affect users who use yours and don't uninstall mine. Just add this into your updater-script:
Code:
delete("/system/bin/LoSChecker");
Code:
delete_recursive("/data/local/LoS");
Click to expand...
Click to collapse
Thanks man. I'll do that. I'll be waiting in anticipation for those enhancements. I actually just got a reboot following a ghost LoS where I couldn't send any texts. It couldn't restart the radio, and boom. The best enhancement we could get is to have no need for this utility. Heh.
... and then just do a wc on it (-l option reads lines, I think) which would give you the number of times that you had LoS from reading the amount of lines in the file. Just a thought.
Click to expand...
Click to collapse
Yep. The new /data/local/LoSD/LoSD.log is basically everything it sends to the system log, so it's like a mirror that persists after reboots, unlike the system logs. In addition, you can turn off those pesky "Radio appears normal - no LoS." information messages by setting DEBUG=0 in the config file.
I just found a cut-n-paste bug in the line that dumps the bugreport, so I may just add the lines that remove LoSChecker along with that fix.
Thanks again, Viper!
Is anyone else running a hacked PRL and running into issues like I am?
EDIT: Rebooted manually, held up at splash screen, weird series of beeps and now back up....running Blazer v.12 on EG31.
DizDroid said:
Is anyone else running a hacked PRL and running into issues like I am?
Click to expand...
Click to collapse
Well, if your hacked PRL is the 000000 one that puts you permanently on Verizon, that might be an issue. I noticed the phone killed my radio about 6 times today around the same 20-minute period while I was right on the edge of Sprint service and kept roaming on and off. I was standing in line for lunch in a building that's not nearly as tall or as deep as where I work, yet it was driving my radio nuts. LoSD's ghost LoS checks triggered multiple times, so I have plenty of logs to work with now so I can revise the check to be a little less overzealous.
I can't say for sure, but forcing yourself to roam may have a similar effect. Take it with a grain of salt.
trifthen said:
Well, if your hacked PRL is the 000000 one that puts you permanently on Verizon, that might be an issue. I noticed the phone killed my radio about 6 times today around the same 20-minute period while I was right on the edge of Sprint service and kept roaming on and off. I was standing in line for lunch in a building that's not nearly as tall or as deep as where I work, yet it was driving my radio nuts. LoSD's ghost LoS checks triggered multiple times, so I have plenty of logs to work with now so I can revise the check to be a little less overzealous.
I can't say for sure, but forcing yourself to roam may have a similar effect. Take it with a grain of salt.
Click to expand...
Click to collapse
Thanks for the reply, keep up the great work. If I wasn't trying so hard to get out of my Sprint contract I'd ditch the .000000000000000000000000000 in a heartbeat.

[Ref] Galaxy Nexus 4.3 tips & tricks with important info to know

Hello everyone, i see here to collect and post some known and maybe unknown tips and tricks with some important information, hoping this will be useful for users.
Any more tips, tricks and suggestions from users are always welcomed. And please feel free to make corrections for any wrong or missed information in this post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preface:​
The Galaxy Nexus (GT-I9250) is a touchscreen Android smartphone developed by a partnership between Google and Samsung. The phone and operating system were developed collaboratively by engineers from both companies. It is the third generation successor to Google's previous flagship phones: the Nexus One and Nexus S. The Galaxy Nexus has a high-definition (1280 × 720) Super AMOLED display with curved glass, an improved camera and has an unlockable bootloader to allow further development and end-user modification. Nexus devices are the first Android devices to receive updates to the operating system. The name of this smartphone is the result of co-branding between the Samsung Galaxy and Google Nexus brands of Android smartphones. The device is known as the Galaxy X in Brazil, however, due to a trademark on the "Nexus" brand.
The Galaxy Nexus was unveiled jointly by Google and Samsung on October 19, 2011 in Hong Kong. It was released in Europe on November 17, 2011.
It is one of the few phones recommended by the Android Open Source Project for building Android from source.
The Galaxy Nexus is no longer available for sale on the Google Play Store as of October 29, 2012 with the announcement of its successor, the LG Nexus 4.
Click to expand...
Click to collapse
OTA 4.3 (JWR66Y)​
Google begins to roll Jelly Bean 4.3 on Gnex which have some notable modifications but not at the level that users expect. Not as usual, OTA begun to roll first on yakju build not takju. Users who already got their hands on the latest firmware update have reported what is new:
- More secured ADB. (as 4.2.2)
- Fix the Bluetooth audio bugs.
- Better battery performance noticed.
- Performance enhancements.
-System UI lag also gone.
-Camera rotation lag is reduced.
-Dial pad autocomplete, can be enabled from call settings.
-you will notice more ram freeing.
-Google Hindi Input is added in "Language and imput".
-supporting of App Ops (optional permissions), see here.
** 4.3 supports now "OpenGL ES 3.0" for High-Performance Graphics and "Connectivity with Bluetooth Smart devices and sensors" and "Optimized Location and Sensor Capabilities", but unfortunately, our devices does not support it.
Support for "Restricted Profiles" is only for Nexus tablets
Did you install Android 4.3 on your Nexus device? Have you noticed anything new in Android 4.3? Please post it.
Click to expand...
Click to collapse
Questions & Answers​
Q1) I didn't receive OTA update and i am on unrooted stock firmware?
A Go to Settings > Apps > All > Google Services Framework, clear data, then go to Settings > About phone > System update > Check now. repeat procedure many times.
Q2) Kies program does not recognize my Gnex, i want to update firmware?
A Gnex firmware is not supported by Samsung Kies. it is updated directly from Google.
Q3) Can i make a screen shot on stock firmware?
A Yes you can! user doesn’t need to root the device or employ third-party apps just to take a photo of what's happening on screen. Taking a screenshot is simple, just press the volume down and power buttons together. The device will quickly take a snapshot of the screen and you will find it in your notifications.
Q4) What is Barrel Roll?
A As part of Google's regular antics, it had introduced a "barrel roll" trick for desktop browsers. Type "do a barrel roll" as a search term, and Google would demonstrate the power of modern browsers by flipping everything around on your screen. Your Android device can also do a barrel roll if you speak out the same command. Again, It's great fun to show off.
Q5) How can i uninstall an app. without going to setting?
A Long-pressing on an app within the app drawer pops up a couple of menus along the top of the screen. App Info gives you the boring technical stuff about how much memory it's taking up, or you can fling it off the other way to uninstall it.
Q6) How can i go directly to the quick settings menu?
A expand notification bar by sliding two fingers.
Q7) What is inverted rendering?
A Inverted rendering is a posh way of saying it makes the pages black and turns the text white, so it looks like you're reading the internet from 1997. It also supposedly saves battery, plus is easier on the eyes if you're reading in the dark. It's under the browser's settings tab, within the accessibility area - and there's a contrast slider, too.
Q8) How can i reboot into safe mode?
A Safe mode, the savior of so many Windows PCs! If you are experiencing a problem with your Gnex and you want to determine whether it is being caused by a third-party app, long-press the power button, then long-press the Power off option. Choose OK to reboot in safe mode, which completely disables all third-party apps on your device. If the problem goes away when you’re in safe mode, you should reboot your device and start removing recently installed apps until the problem goes away.
Q9) What does reset app. preferences means?
A Android gives you loads of different options for each installed app, and on the whole this is a very good thing. Sometimes it can be a bad thing, though: you may find your phone playing up because a crucial app has been disabled, or you've changed the notifications for something important like emails. In the apps drawer, you'll find Reset app preferences under the settings. This resets all your apps on a global level, returning actions and data settings to their original levels.
Q10) What is imojis?
A "Emojis" are the Japanese version of emoticons. You can enable emoji support for the default Jelly Bean keyboard by choosing Language & input in the settings app, then going to the settings for the stock Android keyboard. Here, choose Add-on dictionaries and select Emoji for English words. When you next type certain words (there's a complete list here) you'll see its symbol appear in the predictions bar.
Q11) What is the difference between takju and yakju?
A These android builds are almost the same but there are some differences in terms of their android updates. Takju: Mobiles which brought from Google play store in USA and come with a Google wallet pre-installed. In these devices, android update is pushed by Google itself and they are almost first to receive an OTA update. Yakju: Mobiles which brought from Google store but outside of USA, update are also pushed by Google, but this update might delay by some days or weeks. So, do check your android build if your device is running android build other than takju, then change it in takju build to an OTA update first.
Q12) How do i know what is my Gnex android build?
A Download Android System Info application from play store or you can check it from Maps>setting>about.
Q13) I can not see Developer Options in settings?
A Google hide this option, to enable it just go to settings---->about phone, tap 7 times on "build number" and it will be shown in settings.
Q14) how to make apps, data and sdcard backup & restore?
A Refer to post # 286.
Q15) I received 4.3 OTA update, ADB can not recognize my Gnex. What should I do?
A Download and install Android SDK, if you already have it on your PC just update tools and platform-tools. you must have latest ADB version (1.0.31). If you do not want to install Android SDK, download attached file (thx to xaueious).
Q16) How can i make my Gnex feel snappier?
A By speeding up (or disabling) the animated fade-in effects you see when switching between tasks, you’ll see a boost in performance and faster screen transitions. Start by unhiding “Developer options” as described above. Once in “Developer options,” scroll down to the “Window animation scale” and “Transition animation scale” options and set both to .5x. You can even turn each of these off and transitioning between apps and pages will be almost instant. If you ever want to go back, remember the defaults for both of these settings are 1x.
Q17) How can i improve my gaming graphics?
A If you are a hard-core gamer, you probably already know what 4x anti-aliasing is. First, enable Developer Options as described above, then go to Settings and click on Developer Options and enable Force 4x MSAA. Multisample anti-aliasing (MSAA) is a technique used to improve image quality. Since the Gnex has a GPU capable of supporting MSAA, this setting should make your graphics look more detailed when you are playing advanced games. Keep in mind this will also cause your GPU to work harder and your device may get hotter and consume more power than normal. It’s also possible that all games may not support this.
Q18) I want to see Jelly Bean on my screen, can i?
A Yes you can, go to settings---->about phone tap quickly 4-5 times on android version, you will see a big Jelly bean, touch and hold it, you will see small flying Jelly beans.
Q19) How can i customize my LED notifications?
A A free app called Light Flow Lite allows you to take control of the colors of your notification LED. It also makes your Gnex flash one color after another. This app allows you to set the notification color for over 250 applications and system events including missed calls, low battery, no signal, voice mail, calendar reminders, Gmail messages, email messages, SMS messages, MMS messages, Twitter notifications and more.
Q20) How can i put my Gnex in fastboot/recovery mode?
A Turn off your phone, press and hold down Volume Up and Down keys + Power button at the same time until fastboot (bootloader) mode (image of an Android with Start) appears then release the keys. Press volume up or down and select recovery by pressing power button. (For stock recovery, when you see an android logo with exclamation mark, press power + volume up to see the recovery menu).
Q21) How can i put my Gnex in download mode (odin mode)?
A Turn off your phone, press and hold down Volume down + Power button at the same time until odin mode appears then release the keys.
Q22) Why google voice search is crashing when i press on mic when i am on a custom rom?
A Update google search from play store.
Q23) My Gnex screen is turning on by itself, what is happening?
A It is caused by an application, usually by live wallpapers, try to find it and delete it, or install an antivirus app., i recommend Dr.Web Anti-virus, scan, delete, wipe cache and dalvik (optional).
Q24) sometimes i lose packet data (3G) when i turn it off then on, i turn off then turn on my Gnex to enable packet data again?
A There is no need to turn your phone off and on to re-enable packet data, just long press on power button, enable airplane mode for 3-5 seconds then disable it.
Q25) I rooted my Gnex, what to do next?
A It is recommended to make a nandroid backup immediately.
Q26) I rooted my Gnex 4.3, made a nandroid backup, but i can not find my backup folder?
A Use a file manager, enable root option, your backup folder is located in data/media/clockworkmod or mnt/shell/emulated/clockwordmod.
Q27) The kernel does not support PGM, is there a solution?
A change the kernel, or install intellicover application.
Q28) Do i need to wipe cache partition when flashing a new rom?
A No, there is no need to wipe cache, because when you wipe data/factory reset, cache is wiped automatically. Some said to wipe cache and dalvik after flashing a new rom to prevent any potential conflict.
Q29) I rooted my Gnex 4.3, flash custom recovery, but when i reboot into recovery, it shows the stock recovery!?
A Every OTA update places two files on device system (that are not there on a non-update stock ROM) that re-flash the stock recovery on EVERY boot. The two files are /system/recovery-from-boot.p and /system/etc/install-recovery.sh. You need to make sure that these files are either deleted or renamed, or else custom recovery will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, by using something like Root Explorer, delete or rename them, and re-flash your custom recovery.
Q30) My Gnex won't start, i can not get into fastboot mode, only i can get into download mode?
A Use odin to flash stock firmware here.
Q31) What is the easiest way to install samsung driver?
A The easiest way is to install Samsung Kies.
Q32) How can i flash stock image on my Gnex?
A See efrant thread.
Q33) What about governors, I/O schedulers.....?
A See droidphile thread.
Q34) How to properly post a kernel bug (LAST_KMSG)?
A See ciprianruse88 thread.
Q35) What is the best kernel for my Gnex?
A There is no something called "best kernel". You must try many kernels and decide what suit your rom and your need.
Click to expand...
Click to collapse
Rooting:​
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. Rooting is similar to jailbreaking devices running the Apple iOS operating system. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Rooting enables all the user-installed applications to run privileged commands that are typically unavailable to the devices in their stock configuration.
Legality: The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.
On July 26, 2010, the United States announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.
Safety: I Have always said that the person should learn the Android OS before rooting. It is a good idea to have an idea of what rooting is doing and what it will affect. I would say spend your time really learning the OS which is not a small task. Then, if you still feel like it, go ahead and root. While rooting can help you learn many things about your device, it also can reap very bad consequences, such as:
-Bricking your phone (or in an easier way to explain, making your phone a pretty paper weight).
-Corrupting core files.
-Stopping OTA updates from going to your phone.
-Voiding phone warranty.
-Have your phone open to malicious software and applications that can do serious harm to your phone.
As you can see, it can reap very negative things. I have read/seen people who have literally had to buy brand new phones because they tried the latest and greatest rom. Rooting is essentially something that you must take at your own risk & caution. Generally, if you follow exactly the procedure of rooting made by developers, you will be more likely on the safe side.
Root process: See jabakuba thread.
What to do after rooting?: 1) make a nandroid backup via custom recovery 2) backup efs partition (save your IMEI and NV_DATA):
Install "terminal emulator" from play store, open it and type the following (enter after each line):
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
Then move efs.img to a safe place on your pc.
Click to expand...
Click to collapse
Problems can happen:​
-Stuck into a Bootloop: Bootloops are mainly caused by system files interfering with each others which cause instability and/or crash at the boot sequence. so what to do??
Pull out battery then reinsert it, boot into recovery, wipe cache and dalvik, reboot. If not, format data, system, cache using recovery and restore stock firmware (supposing that you did a nandroid backup before). if you don't have a backup to restore, flash any custom rom from your sdcard after formatting system & data & cache. If you don't have a custom rom in your sdcard, push one from your pc using adb (supposed that you have adb file or sdk on your pc): boot into recovery, connect your phone to the computer open command prompt and write the following command then hit enter (supposing that your rom is placed on D):
Code:
adb push D:\name of rom.zip /data/media/
Or
Code:
adb push D:\name of rom.zip /sdcard/
Then
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip from recovery, reboot.
If none of above methods works, then flash stock image for your Gnex using fastboot commands here.
-Phone-Triangle-computer: If your phone can not boot, can not boot in fastboot or download modes, maybe after a bad flash, and screen shows phone--triangle--computer pic, so it is sort of download mode, use odin to flash stock firmware using this tutorial.
-Nexus is quietly dead: If your phone did not respond to anything, it won't turn on, can not boot into fastboot or download mode, black screen, try "OMAP FLASH", it can save your Gnex.
For 4.2.2 only:
-AOSP Rom incompatibility: After supplying all needed hardware drivers by AOSP, developers has updated AOSPA. So you absolutely need to be up to date regarding Google Bootloaders and Radios, which are not part of the Rom. Or else your device will be incompatible, unable to make calls perhaps and maybe other issues.
Regarding Bootloader, it still the same build for 4.2.2 (primelc03) but the Radio has changed to xxlj1. So you must flash Radio to the latest build using "Fastboot" or through "Recovery":
Fastboot method:(I prefer this)
Unzip "fastboot-radio-maguro-i9250xxlj1.img.zip" (attached), put unzipped image (in the file) into fastboot folder (attached), enable "usb debugging" option, boot into fastboot mode, connect your device to your PC, open a command prompt into fastboot folder and type:
Code:
fastboot flash radio radio-maguro-i9250xxlj1.img
Hit "enter"
Code:
fastboot reboot-bootloader
Hit "enter"
Code:
fastboot reboot
Hit "enter
Recovery method:
Put "cwm-radio-maguro-i9250xxlj1.zip" (attached) into your sdcard. Boot into recovery and flash the zip file.
Click to expand...
Click to collapse
Battery Conservation Tips:​
-Enable Auto Brightness: Brightness can lure a lot of battery if not changed intelligently with time to match the surroundings, Jellybean in this case brought the “Auto Brightness” function which uses the accelerometer within the device to detect the amount of light in the surroundings and then act upon the brightness level according to it. To enable, go to Settings > Device > Display > Brightness, and tick “Automatic Brightness“. And if you want to save more battery drain, set brightness manually at low level depending on the external amount of light.
-Remove Live Wallpapers: Using a live wallpaper is another battery sucking feature. If you turn out to be truly saving battery, make sure not to use any live wallpaper. A wallpaper with a black background uses less power than a wallpaper with a light-colored background.
-Disable Location and GPS services: Keeping GPS ON at all times, decreases your battery life, so its better to disable it while not in use. To disable, go to Settings > Personal > Location access > and switch it off.
-Disable Wi-Fi or Mobile Data when not in use: Try to avoid situations when you keep your Wifi or Mobile Data ON even when the phone is set in standby.
-Manage Sync carefully: Keeping the Sync ON all the time is another reason for decreased battery life. Enable it anytime you want, manage your emails or services and again turn it off. For those who are on work and want real-time push notifications are advised not to follow this tip.
-Turn OFF Haptic Feedback and screen sounds: To save a little more on battery, its better to switch off the screen touch sounds and vibrations. To do so, go to Settings > Device > Sound and untick Dial pad touch tones, Touch sounds. Screen lock sound and Vibrate on touch.
-Turn OFF bluetooth and NFC: Disabling bluetooth and NFC when you are not using it, is another way to save battery juice.
-Follow the method of full charge and full discharge: Don’t put your phone on charging when there is the battery remaining it for another few hours unless it’s very important. Charge it when your battery is about to get totally discharged and when you put it for charging, let it get charged totally.
-Set sleep time: Check the Sleep setting (under Display) and make sure it is set to 1 minute or less.
Keep calls short: This is obvious, but how many times have you heard people on their mobile phone say, "I think my battery’s dying," and then continue their conversation for several minutes? Sometimes, the dying battery is just an excuse to get off the phone (and a good one, at that), but if you really need to conserve the battery, limit your talk time.
-Turn OFF mobile network when not in range: Its very often that you lose the mobile network when you are travelling, so its advisable to turn OFF the mobile network by switching ON Airplane mode. Go to Settings > Wireless & Networks, tick Airplane Mode.
- After each month remove your battery from mobile phone and let it rest for an hour, it will give battery a breath and it will last longer.
-You should not have to turn off your phone to charge it. Most battery chargers deliver more than enough current to power your phone and charge it at the same time. Doing so will not lengthen the charge time, and leaving a phone on allows the user to be aware of its fuel gauge, so that you can remove it when the battery is full.
-When using a car charger, do not charge the battery when the inside temperature of your car is hot. Wait until the car has cooled before you plug in the phone.
Click to expand...
Click to collapse
Gnex secret codes:​
*#*#4636#*#* Testing menu(Phone, Battery & Wifi Info, Usage Statistics).
*#06# MEID number(Display's your IMEI).
*#*#2432546#*#* Checkin(Manually check for System Updates).
*#*#8255#*#* For Google Talk service monitoring.
*#*#786#*#* Hard Reset(Wipes/Resets Data/Profile & internal storage!) (think before you do it! no warning, no go back).
*#*#1234#*#* or *#*#7873778#*#* Open superuser application.
*#123# then press dial. Shows you if you are in your home network or not (only across networks in USA/Canada).
Click to expand...
Click to collapse
Recommendations:​
-Too loud wallpapers may sometimes disturb the look of your home screen and make the icons quite invisible, simple or a less-colored wallpapers are always suggested as to be the best choice. But your choice is what matters.
- Use only essential widgets on your home screen - each widget consumes memory and processing power which can slow your down your phone.
- Uninstall apps that you don't use - after awhile your phone can get cluttered as some Apps are designed to always run in the background. If you rarely use an App, then uninstall it to free up memory and CPU resource.
- It is best to avoid task killers such as Advanced Task Killer. Android is designed to automatically pre-load certain applications, even if you don't load them yourself. If it starts to run low on memory, it will smartly unload the oldest running apps automatically. Manually killing tasks will only mean they get loaded in memory again. Task killers can make the phone slow, laggy, or drain battery life more quickly.
- Always use latest CWM or latest TWRP recoveries.
- Disable USB debugging when it is not in use. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).
- Avoid putting your Gnex in direct sunlight, it may affect touch screen & your battery performance.
- Learn how to use ADB & FASTBOOT commands instead of using toolkits, the last could not function properly.
- Flash stock firmware using fastboot is preferred than using odin.
- Check rom/kernel.zip md5 before flashing if it is convenient.
- Always update applications, if available, for better performance.
- Make a backup of your data, applications, contacts...always ready to restore from your computer.
- Read, read and read before you mess with your Gnex.
- Always be sure that you are flashing the right thing for your Gnex variant.
- If you do not know what you are doing, so don't do it .
Click to expand...
Click to collapse
Did you finish reading? Please press Thanks & Rating buttons
Big thanks to the developers of attached files.
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
Great off topic post in AK thread!!!
Thanx for your love and looking out for others
"powered by AK purity v17 Kernel + purity ROM + C.R.88 Wallpapers for beauty"
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
I love this type of thread ... When my mind goes off here I have all infos
Xda with AK Kernel inside
MOD EDIT: For God's sake, Don't quote the entire OP, post edited.
anarkia1976 said:
I love this type of thread ... When my mind goes off here I have all infos
Xda with AK Kernel inside
Click to expand...
Click to collapse
thx AK. im ready for anything to add from any user :good:
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
samersh72 said:
thx AK. im ready for anything to add from any user :good:
Click to expand...
Click to collapse
If I can help ... You can TOC TOC on my door
Xda with AK Kernel inside
hell yea bro!!!!!:good::good::good::good::good::good::good::good:
great thread bro...will be very helpful to new users :good:
k786 said:
great thread bro...will be very helpful to new users :good:
Click to expand...
Click to collapse
Thx for your post bro:good:
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
I'm impressed the majority of best contributor of ak thread create a new place with his experience for help users .....
Keep up the good work
Xda with AK Kernel inside
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
anarkia1976 said:
I'm impressed the majority of best contributor of ak thread create a new place with him experience for help users .....
Keep up the good work
Xda with AK Kernel inside
Click to expand...
Click to collapse
You are the professor AK
Sent from my Galaxy Nexus using xda premium
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
Hi guy can you add to your guide reference for resolve problem Like sk8 battery .... :thumbup:
Thanks a lot for your great guide ....
I hope every user read this make a thanks to you
Xda with AK Kernel inside
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with some Recommendations
anarkia1976 said:
Hi guy can you add to your guide reference for resolve problem Like sk8 battery .... :thumbup:
Thanks a lot for your great guide ....
I hope every user read this make a thanks to you
Xda with AK Kernel inside
Click to expand...
Click to collapse
No problem my friend:thumbup:
Sent from my Galaxy Nexus using xda premium
anarkia1976 said:
Hi guy can you add to your guide reference for resolve problem Like sk8 battery .... :thumbup:
Thanks a lot for your great guide ....
I hope every user read this make a thanks to you
Xda with AK Kernel inside
Click to expand...
Click to collapse
i couldn't figure out properly what is sk8 problem
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with important info to know
jrgilbert79 said:
I have found out how to fix low volume phone wide and give you a reason to buy quality headphones....Guide here. http://forum.xda-developers.com/showthread.php?t=2117648
Click to expand...
Click to collapse
Thx very useful. Testing:thumbup:
Sent from my Galaxy Nexus using xda premium
The code for dialer for manual update checking is nice.
I didn't know that code even exists..
That was really helpful... Thanks!
dmourao said:
That was really helpful... Thanks!
Click to expand...
Click to collapse
you are welcome my friend:good:
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with important info to know
Great topic got a lot useful info :thumbup:
Sent from my smartphone
Amazing
:good:
samersh72 said:
Hello everyone, i see here to collect and post some known and maybe unknown tips and tricks with some important informations, hoping this will be useful for users.
Any more tips, tricks and suggestions from users are always welcomed. And please feel free to make corrections for any wrong or missed information in this post
Questions & Answers​
Q I didn't receive OTA update and i am on stock firmware?
A Go to Settings > Apps > All > Google service framework, clear data and force close it, then go to Settings > About phone > System update > Check now. repeat procedure many times.
Q Can i make a screen shot on stock firmware?
A Yes you can! user doesn’t need to root the device or employ third-party apps just to take a photo of what's happening on screen. Taking a screenshot is simple, just press the volume down and power buttons together. The device will quickly take a snapshot of the screen and you will find it in your notifications.
Q What is Barrel Roll?
A As part of Google's regular antics, it had introduced a "barrel roll" trick for desktop browsers. Type "do a barrel roll" as a search term, and Google would demonstrate the power of modern browsers by flipping everything around on your screen. Your Android device can also do a barrel roll if you speak out the same command. Again, It's great fun to show off.
Q How can i uninstall an app. without going to setting?
A Long-pressing on an app within the app drawer pops up a couple of menus along the top of the screen. App Info gives you the boring technical stuff about how much memory it's taking up, or you can fling it off the other way to uninstall it.
Q How can i go directly to the quick settings menu?
A expand notification bar by sliding two fingers.
Q What is inverted rendering?
A Inverted rendering is a posh way of saying it makes the pages black and turns the text white, so it looks like you're reading the internet from 1997. It also supposedly saves battery, plus is easier on the eyes if you're reading in the dark. It's under the browser's settings tab, within the accessibility area - and there's a contrast slider, too.
Q How can i reboot to safe mode?
A safe mode, the saviour of so many Windows PCs! Long-press the power button, then long-press the Power off option. Choose OK to reboot in safe mode, which completely disables all third-party apps on your device.
Q What does reset app. preferences means?
A Android gives you loads of different options for each installed app, and on the whole this is a very good thing. Sometimes it can be a bad thing, though: you may find your phone playing up because a crucial app has been disabled, or you've changed the notifications for something important like emails. In the apps drawer, you'll find Reset app preferences under the settings. This resets all your apps on a global level, returning actions and data settings to their original levels.
Q What is imojis?
A "Emojis" are the Japanese version of emoticons. You can enable emoji support for the default Jelly Bean keyboard by choosing Language & input in the settings app, then going to the settings for the stock Android keyboard. Here, choose Add-on dictionaries and select Emoji for English words. When you next type certain words (there's a complete list here) you'll see its symbol appear in the predictions bar.
Q I can not see Developer Options in settings?
A Google hide this option on JB 4.2.1, to enable it just go to settings---->about phone, tap 7 times on "build number" and it will be shown in settings.
Q I want to see Jelly Bean on my screen, can i?
A Yes you can, go to settings---->about phone tap quickly 4-5 times on android version, you will see a big Jelly bean, touch and hold it, you will see small flying Jelly beans.
Q How can i put my Gnex in fastboot/recovery mode?
A Turn off your phone, press and hold down Volume Up and Down keys + Power button at the same time until fastboot (bootloader) mode (image of an Android with Start) appears then release the keys. Press volume up or down and select recovery by pressing power button.
Q How can i put my Gnex in download mode (odin mode)?
A Turn off your phone, press and hold down Volume down + Power button at the same time until odin mode appears then release the keys.
Q Why google voice search is crashing when i press on mic when i am on a custom rom?
A Update google search from play store.
Q My Gnex screen is turning on by itself, what is happening?
A It is caused by an application, usually by live wallpapers, try to find it and delete it, or install an antivirus app., i recommend this, scan, delete, wipe cache and dalvik (optional).
Q sometimes i lose packet data (3G) when i turn it off then on, i turn off then turn on my Gnex to enable packet data again?
A There is no need to turn your phone off and on to re-enable packet data, just long press on power button, enable airplane mode for 3-5 seconds then turn it off.
Q I rooted my Gnex, what to do next?
A It is recommended to make a nandroid backup immediately.
Q I rooted my Gnex 4.2.1, made a nandroid backup, but i can not find my backup folder?
A Use a file manager, enable root option, your backup folder is located in data/media/clockworkmod or mnt/shell/emulated/clockwordmod.
Q The kernel does not support PGM, is there a solution?
A change the kernel, or install intellicover application.
Q Do i need to wipe cache partition when flashing a new rom?
A No, there is no need to wipe cache, because when you wipe data/factory reset, cache is wiped automatically. Some said to wipe cache and dalvik after flashing a new rom to prevent any potential conflict.
Q I rooted my Gnex 4.2.1, flash custom recovery, but when i reboot into recovery, it shows the stock recovery!?
A Every OTA update places two files on device system (that are not there on a non-update stock ROM) that re-flash the stock recovery on EVERY boot. The two files are /system/recovery-from-boot.p and /system/etc/install-recovery.sh. You need to make sure that these files are either deleted or renamed, or else custom recovery will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, by using something like Root Explorer, delete or rename them, and re-flash your custom recovery.
Q My Gnex won't start, i can not get into fastboot mode, only i can get into download mode?
A Use odin to flash stock firmware here.
Q What is the easiest way to install samsung driver?
A The easiest way is to install Samsung Kies.
Q How can i flash stock image on my Gnex?
A See efrant thread.
Q What about governors, I/O schedulers, TCP congestion?
A See MBQsniper thread.
Q How to properly post a kernel bug (LAST_KMSG)?
A See ciprianruse88 thread.
Q What is the best kernel for my Gnex?
A There is no something called "best kernel". You must try many kernels and decide what suit your rom and your need. But for me AK kernel is the most active kernel in update releases that suit most roms.
Rooting:​
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. Rooting is similar to jailbreaking devices running the Apple iOS operating system. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Rooting enables all the user-installed applications to run privileged commands that are typically unavailable to the devices in their stock configuration.
Legality: The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.
On July 26, 2010, the United States announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.
Safety: I Have always said that the person should learn the Android OS before rooting. It is a good idea to have an idea of what rooting is doing and what it will affect. I would say spend your time really learning the OS which is not a small task. Then, if you still feel like it, go ahead and root. While rooting can help you learn many things about your device, it also can reap very bad consequences, such as:
-Bricking your phone (or in an easier way to explain, making your phone a pretty paper weight).
-Corrupting core files.
-Stopping OTA updates from going to your phone.
-Voiding phone warranty.
-Have your phone open to malicious software and applications that can do serious harm to your phone.
As you can see, it can reap very negative things. I have read/seen people who have literally had to buy brand new phones because they tried the latest and greatest rom. Rooting is essentially something that you must take at your own risk & caution. Generally, if you follow exactly the procedure of rooting made by developers, you will be more likely on the safe side.
Problems can happen:​
-Stuck into a Bootloop: Bootloops are mainly caused by system files interfering with each others which cause instability and/or crash at the boot sequence. so what to do? pull out battery then reinsert it, boot into recovery, wipe cache and dalvik, reboot. If not, format data, system, cache using recovery and restore stock firmware (supposing that you did a nandroid backup before). if you don't have a backup to restore, flash any custom rom from your sdcard after formatting system & data & cache. If you don't have a custom rom in your sdcard, push one from your pc using adb (supposed that you have adb file or sdk on your pc): boot into recovery, connect your phone to the computer open command prompt and write the following command then hit enter (supposing that your rom is placed on D):
Code:
adb push D:\name of rom.zip /data/media
once done, go to your phone and install the rom.zip from recovery, reboot.
If none of above methods works, then flash stock image for your Gnex using fastboot commands here.
-Nexus is quietly dead: If your phone did not respond to anything, it won't turn on, can not boot into fastboot or download mode, black screen, try "OMAP flash", it can save your Gnex OMAP FLASH.
Battery Conservation Tips:​
-Enable Auto Brightness: Brightness can lure a lot of battery if not changed intelligently with time to match the surroundings, Jellybean in this case brought the “Auto Brightness” function which uses the accelerometer within the device to detect the amount of light in the surroundings and then act upon the brightness level according to it. To enable, go to Settings > Device > Display > Brightness, and tick “Automatic Brightness“.
-Remove Live Wallpapers: Using a live wallpaper is another battery sucking feature. If you turn out to be truly saving battery, make sure not to use any live wallpaper.
-Disable Location and GPS services: Keeping GPS ON at all times, decreases your battery life, so its better to disable it while not in use. To disable, go to Settings > Personal > Location access > and switch it off.
-Disable Wi-Fi or Mobile Data when not in use: Try to avoid situations when you keep your Wifi or Mobile Data ON even when the phone is set in standby.
-Manage Sync carefully: Keeping the Sync ON all the time is another reason for decreased battery life. Enable it anytime you want, manage your emails or services and again turn it off. For those who are on work and want real-time push notifications are advised not to follow this tip.
-Turn OFF Haptic Feedback and screen sounds: To save a little more on battery, its better to switch off the screen touch sounds and vibrations. To do so, go to Settings > Device > Sound and untick Dial pad touch tones, Touch sounds. Screen lock sound and Vibrate on touch.
-Turn OFF bluetooth: Disabling bluetooth when you are not using it, is another way to save battery juice.
-Turn OFF mobile network when not in range: Its very often that you lose the mobile network when you are travelling, so its advisable to turn OFF the mobile network by switching ON Airplane mode. Go to Settings > Wireless & Networks, tick Airplane Mode.
Gnex secret codes:​
*#*#4636#*#* Testing menu(Phone, Battery & Wifi Info, Usage Statistics).
*#06# MEID number(Display's your IMEI).
*#*#2432546#*#* Checkin(Manually check for System Updates).
*#*#8255#*#* For Google Talk service monitoring.
*#*#786#*#* Hard Reset(Wipes/Resets Data/Profile & internal storage!) (think before you do it! no warning, no go back).
*#*#1234#*#* or *#*#7873778#*#* Open superuser application.
Recommendations:​
-Too loud wallpapers may sometimes disturb the look of your home screen and make the icons quite invisible, simple or a less-colored wallpapers are always suggested as to be the best choice. But your choice is what matters.
- Always use latest CWM or latest TWRP recoveries.
- Disable USB debugging when it is not in use. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).
- Avoid putting your Gnex in direct sunlight, it may affect touch screen & your battery performance.
- Learn how to use ADB & FASTBOOT commands instead of using toolkits, the last could not function properly.
- Flash stock firmware using fastboot is preferred than using odin.
- Check rom/kernel.zip md5 before flashing if it is convenient.
- Always be sure that you are flashing the right thing for your Gnex variant.
- If you do not know what you are doing, so don't do it .
Did you finish reading? Don't forget to press Thanks & Rating buttons ​
Click to expand...
Click to collapse
Its Amazing post .. Thanx buddy .. Good luck for the future ..
Re: [Ref] Galaxy Nexus 4.2.1 tips & tricks with important info to know
Subscribed! Awesomeeee OP! this is soo worth a sticky!
Sent from my Nexus Prime

[ROM][CM7] Defy Pro XT560 Support Thread

This is a support thread for the ROM posted here.
http://forum.xda-developers.com/showthread.php?p=49394355
* It is very important to clear factory data/cache after installing the CM7 rom.
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
* The battery_charger has been replaced in this build as a safety backup to get into bootmenu. Anytime the phone is powered off and then plugged in it will boot to bootmenu instead of the charging screen.
* It is very important to clear factory data/cache after installing the CM7 rom.
Click to expand...
Click to collapse
I make all wipe data/cache and even Dalvik cache before and after install CM7 - but I stuck on the android boot screen.
But note: I made all wipes from CWM, because stock recovery is not works on my phone (only green robot and yellow triangle and that's all - nothing key works, only pull battery helps).
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
Click to expand...
Click to collapse
How can I make this (run logcat)?
Thanks for the advices.
Im not sure the clear data/cache works right in CWM. I have not tested it. To access the menu in the stock recovery hit the Home key.
To output a logcat open a command prompt and run "adb logcat"
If you want to output it to a file use "adb logcat > filename.txt"
so there is some querrys:
- torch app does not work as a flashlight, while it stay in status bar and even task killer wont help
- led notification light does not work at all, i guess there is no app for that and original is missing
- it wont unlock sim card, or lock it while it's unlocked. message is "incorrect pin". previously unlocked on other phone sim works fine. pin correct.
- the reboot menu list wont operate with joystick, only touch.
- both cameras wont work in skype, when forced induce crash.
- dev tools options become a force close
- voice dialer started by long press call button opens in wrong screen orientation and does not work. it work if started from all apps.
- superuser does not ask about allowing su permissions, there is no app listed as allowed su perm. while all super su apps works fine as usual.
- yandex maps app issue. rendering map result is quite not what it should be
I did it! Thanks for stock recovery main key (Home) .
And now some my notes (first, I use Russian language and CM7 has it).
- torch app doesn't work - this right for me too;
- about led - not work too;
- about sim - not check this yet;
- the reboot menu OPERATE for me with D-Pad;
- I don't use Skype;
- dev tools work in full for me;
- all correct about voice dialer;
- it's right too;
- don't install yandex maps yet.
wifi is not work
clxer said:
wifi is not work
Click to expand...
Click to collapse
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent
I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
retr13 said:
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent
Click to expand...
Click to collapse
superdave said:
I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
Click to expand...
Click to collapse
antutu now running, mx harddecoding on the other hand dont
yandex. maps still weird
Good Job, and thank you
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.
jimway said:
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.
Click to expand...
Click to collapse
With poot.apk
http: / / ofimatica-programacion[dot]blogspot[dot]com/2014/02/rootear-telefonos-android-sin-necesidad[dot]html
Any updates?
edit- specifically, does CM7 fix the poor bluetooth A2DP quality of the stock ROM?
Sent from my XT560 using xda app-developers app

[Q] Encryption don't work CM11-12 - help please

Hi, I'm new in android. I install CM12 nightly and run encryption.
- Phone do something, say 10:00 minutes,I don't see at him. After that (about 10 min) phone say something like "UI don't run, Music don't run, video ...".
- So I restart phone and process continued, but after that some aplication corrupted - UI don't respond said, more restart don't help
- Then I reset to factory and all is ok, but unencrypted
- then i run encrypt again - after 30 sec phone return back to lock screen - stay unencrypted, do nothing
- install stable CM11, run encryption - the same - phone after 30sec return to lock screen and stay unencrypted
- now I'm back to CM12
when install new rom, I use wipe/format/clear anything possible in menu
I install aLogcat to see some log, but there is imho little log - one screen. Maybe I don't know using it.
All this looks like in the first encryption corrupt some rights of directory and another encryption process corrupt immediately, i don't know.
Maybe 1 thing - widget cLock in weather says: It is not possible to determine the position - Switch on, but it switched ... weather don't respond, but I remember that it run correct, in the first ROM CM12 install.
Thans for any help
- on phone: activate adb in developer settings
- on pc: run 'adb logcat'
- on phone: start encryption process
- on pc: check logs the moment you start the encryption
aguaz said:
- on phone: activate adb in developer settings
- on pc: run 'adb logcat'
- on phone: start encryption process
- on pc: check logs the moment you start the encryption
Click to expand...
Click to collapse
Thanks for help, I find out solution - install another superuser. Probably this help, I´m not realy sure, many reinstalation tried .
But still have 2 problems:
- cannot fix cell position, only GPS work
- upgrade to new nightly CM12 never continues - there is "cannot mount /dev/. ." in recovery mode, I think that is problem with encryption - recover mode cannot acces to encryption files. I upgrade it manualy from SD, but still can´t access "/data", but system show new build, I hope thats ok even this error during upgrade.

How To Guide Debloating Samsung Galaxy F62 running on One UI 3.1 A11 Using ADB APP Control

Kindly follow the steps carefully:
1. Install ADB App Control [ Download ]
2. Go to Load Preset
3. Import the attached file
4. Click disable
5. Go to stock recovery > wipe cache partition > reboot
6. Run galaxy app booster and optimize the device.
7. Enjoy the snappy and debloated experience
Note:
1.Uncheck any package from the list that you might need before clicking disable.
2. Not stable with latest one ui 4.1 update.
Thanks for this.
I dont know how much faster or anything is, but Im glad to have wiped fb off of my phone!
somewhere I went wrong
i have error 3020
"your phone is locked device services was uninstalled without authorization"
help please?
usb debugging is enabled but not "always"
the phone isnt seen by adb app control
Id be happy to just boot into recovery and do a factory reset. But I cant get the right button
combination. Is it power and up volume or power and down volume?
To boot into recovery press power + vol up while connecting the usb
theres a setting that I cant figure out.
something gets deleted or reset, and I cannot enter into the setting for the camera?
any idea on what it might be?
Vishnuisgod said:
theres a setting that I cant figure out.
something gets deleted or reset, and I cannot enter into the setting for the camera?
any idea on what it might be?
Click to expand...
Click to collapse
i think the probleme is device services apk (com.samsung.android.kgclient). Don't uninstall it.
yes. i solved the problem and i have tested on my phone. The solution is : Don't uninstall device services apk. (com.samsung.android.kgclient)
you can disable device service without any probleme for android 11

Categories

Resources