Devs challenge: CPU leak in Stock ROM &Custom maybe (GPS+WIFI Location Services) - HTC Wildfire S

Description: (http://youtu.be/YEKa24hhYd4)
Before running Google Maps (or any Location software) the CPU load of 'Android System' is near 10%. After enabling both GPS module AND WiFi connection (connected to IPV6 Router) and running Google Maps the CPU load will jump and remain at around 85%.
How to check:
Reboot phone (without fast startup enabled) and install 'CPU Usage' app. See the load of 'Android System' process. Enable both GPS module AND WiFi connection and start Google Maps. Close Google Maps after a position lock and check load of 'Android System' process.
My experiments:
- I had this problem on 2.13.401.3 and also on stock 2.14.401.1 ROM
- no custom kernel installed or root active, only CWM 5.0.2.8 recovery
- it is not related to Google maps version
- google latitude is not enabled
- tried it with no other apps installed (stock only)
- Pico TTS has nothing to do with it
- GPS fix 1.2 has no effect, still same behavior
- dalvik cache clear and user cache clear has no effect
- as I said, factory reset to stock did not help
- a reboot temporary solves the issue
LOG file:
I have attached log file. I opened Maps at 23:12 and between 23:13-23:14 CPU load has jumped to over 85%
Challenge:
Do you have this problem too (please confirm or infirm)? Is it present on your stock or custom ROM? Your router has IPV4 or IPV6?
Do you have any idea what might be the root cause?
FINAL CONCLUSION: the issue appears for me only on a ipv6 router. might be because of tomato firmware on router or ipv6 bug in htc. either way, let's forget this thread

So you thought your question was SO important it had to be put in the DEVELOPMENT section? Get real. I KNOW the site asks you if you're posting a question, and then warns you that you're breaking the rules. AND it was ALREADY in the right place earlier. Reported.

BigChillin said:
So you thought your question was SO important it had to be put in the DEVELOPMENT section? Get real. I KNOW the site asks you if you're posting a question, and then warns you that you're breaking the rules. AND it was ALREADY in the right place earlier. Reported.
Click to expand...
Click to collapse
Yes, let's move it. thanks for testing and being so helpful... always a pleasure.

Related

[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

Can't turn off Google Now [SOLVED]

As the title said for some reason I cannot turn off Google now today. Never had this problem in the past.
It just gives this toast message (see attachment as well):
"Failed to turn off cards due to a network error. Please check your network connection and try again."
Has anyone come across this before?
EDIT:
Clearing data for "Google Framework Services" and "Google Search" reset "Google Now".
Have you rebooted your phone and tried again?
WiredPirate said:
Have you rebooted your phone and tried again?
Click to expand...
Click to collapse
*nods* of course.
Unfortunately not too many things I can explore with this unit. It's a stock SCH-i515 on 4.1.1.
im also having exact problem with exact phone..
hope someone can help too
Same problem, saw Maps app was chewing up battery after turning it on and now it won't go off
Using a CM10.1 build on Infuse... Grrrrr
I did a catlog dump, I believe this is the relevant error:
W/Velvet.VelvetNetworkClient( 1814): Network error: com.google.android.searchcommon.util.HttpHelper$HttpException: 500 Internal Server Error
Can you turn it off when connected to wifi?
Can you turn it off after disabling sync?
I'm just trying to think what I would do in that situation, sorry if I am no help.
Just some suggestions:
If possible clear Google service framework and then try freezing Google search.
Also deleting your google account and then setting it back up could be tried
SOLUTION
namtombout said:
Just some suggestions:
If possible clear Google service framework and then try freezing Google search.
Also deleting your google account and then setting it back up could be tried
Click to expand...
Click to collapse
Found a solution based on your prodding.
Load up TI Backup Manager:
-Backup/Restore Tab
-Tap Google Services Framework - Wipe Data - Yes [This step might be optional, doing just this step didn't fix it, but the next step did, so next step may be only necessary one.
-Tap Google Search - Wipe Data - Yes
-Reboot [Recommended]
Now you should be back at square one like you never enabled Google Now
Don't forget to thank the noob!
WiredPirate said:
Can you turn it off when connected to wifi?
Can you turn it off after disabling sync?
Click to expand...
Click to collapse
Tried with no success, this is turning out to be an odd one.
blastagator said:
Found a solution based on your prodding.
Load up TI Backup Manager:
-Backup/Restore Tab
-Tap Google Services Framework - Wipe Data - Yes [This step might be optional, doing just this step didn't fix it, but the next step did, so next step may be only necessary one.
-Tap Google Search - Wipe Data - Yes
-Reboot [Recommended]
Click to expand...
Click to collapse
I think you may be right in that clearing data for Google Search is the only step necessary.
I had cleared data for Google Services Framework before and it didn't do anything, but after doing that and clearing data for Google Search, Google Now was indeed off.
Since this is a stock unit I didn't clear data through TI Backup Manager, but just from the plain old apps list.
I hope Google fixes whatever causes this error.
Thanks!
Nice.:good: OP you might want to edit your thread and put a [resolved] in there so other people having this problem can spot the fix easier.

[Q] Another 4.3 Wifi Tether TrevE problem thread

I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??
Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.
I'm running synergy 4.3 rom and native hotspot works no problem. .
I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.

Problems using Blank Store

Hi folks,
I'm trying to keep my Fairphone free of googleApps (because, you know, $reasons), but as usual it's not that easy.
I am struggeling to get NoGApps working. First of all: kudos to @MaR-V-iN - I don't have a paypal account, but I could invite you for a Kölsch next time I'm in the area.
Can anybody review my steps and possibly describe how to get it running properly?
0. installed OI File Manager (to be able to access the internal partition)
1.1. downloaded μg v1.3.2 (NetworkLocation.apg)
1.2. ( tried to copy to /system/app/NetworkLocation.apk - to no avail: "... could not be copied")
1.3. installed NetworkLocation, allowed access in XPrivacy popup, rebooted.
1.4. downloaded cells-world.db, renamed to cells.db, moved it to /sdcard/.nogapps/cells.db
1.5 tried to find any sign of the application. (Found nothing.)
Sadly, Network location does not show up, anywhere. Am I looking in the wrong places?
2.1. downloaded Blank Store 0.6.6 (BlankStore.apk)
2.2. (renamed it to com.android.vending.apk, tried to copy it to /system/app/com.android.vending.apk - no success.)
2.3. renamed again, installed BlankStore.apk, allowed access in XPrivacy popups, rebooted.
2.4. downloaded android-checkin-1.0.jar and bla.bat, copied them to the location of java.exe, generated an android ID.
2.5. went to menu [Settings]{Accounts}
2.5.1 entered (dedicated...) google credentials and android ID,
2.5.2 entered slightly changed credentials that @DSoundso mentioned (SDK should be 17, I think. I also used a German carrier's MCC-MNC).
2.5.3 rebooted.
2.6 opened BlankStore: yay, I can search it. But I can't install any app: it crashes constantly.
I should mention that the Account settings were gone several times, so the BlankStore would close immediately. I had to re-enter them, and tried also exactly the credentials @DSoundso mentioned in the NOGAPPS thread.
I can't "sync" the account under [Settings]{Accounts}{Sync}. It just "says Sync is OFF", "sync now" does not seem to work.
I logged into the google account on a desktop PC, and no devices show up. ("No active devices").
So, the next steps are unfinished:
3.1. downloaded Maps API v1 (nogapps-maps.zip)
3.2. tried to download via Blank store: BusyBox, TWRP, TitaniumBackup. (BlankStore crashes.)
...to be continued?
Can anybody walk me through?
Or at least single out any errors I made above?
Hey, did you have a look at the XDA-Wiki section about installing the Blank Store? Following this step-by-step should hopefully install the Blank Store
I am too avoiding the Google Apps and also installed the maps successfully (didn't try NetworkLocation yet) and your problems with "could not be copied" sound like a problem with the user rights.. I'm not sure how your file manager works but the with the Android SDK (see above link) and the right commands it should work.
As far as the crashes of the Blank Store are concerned: at first mine also didn't start and crashed, which was caused by the missing Store account but as it sounds yours IS starting but then not really functioning, right? :|
arghwhymustiregister said:
Hey, did you have a look at the XDA-Wiki section [...] As far as the crashes of the Blank Store are concerned: at first mine also didn't start and crashed, which was caused by the missing Store account but as it sounds yours IS starting but then not really functioning, right? :|
Click to expand...
Click to collapse
Thanks, I gave that a try yesterday. 1.7 gb download, what a mess... But solved the problem: it was a rights issue. I was under the impression that the OI File Manager had superuser rights. I was wrong. Got BlankStore working now, but it crashes still quite often on download.
I'm still not sure what to make of it. As I said, it *seemd* to be working before as well, but *no* download was finished. Now, *some* finish their dl, and if they don't I get an error notification (was missing before).
However, whenever I try to load a paid app, the BankStore crashes instantly.
I tried to read the whole NOGAPPS thread and realised: it only works for free apps. And I already redeemed a gift card at the Play Store to buy a paid Titanium Backup version. ****e, I'm stupid. :silly:
Still, it would be nice if it would not crash, or at least tell me it would crash when trying to load a paid app.
Also, I still can't see any active device when logging into the account on the web. Any ideas there? Is that supposed to be like this?
(Funny enough, I *can* see which apps I downloaded through BlankStore.)
arghwhymustiregister said:
also installed the maps successfully (didn't try NetworkLocation yet)
Click to expand...
Click to collapse
It seems both are not working properly for me. OSMAnd can find it's position by GPS. Offi is working, but can not find a location (GPS turned on). Also in Offi Stations, 'Acquiring location' never gets finished. The map stays blank in landscape mode. I would very much appreciate it if you would report your status here: if you can get it to work, how - and if not, what $reasons do you assume?
The permissions are not the problem. /system has to be mounted writable.
Sent from my FP1 using xda app-developers app
permissions for Offi / Maps Api access?
elchi1234 said:
The permissions are not the problem. /system has to be mounted writable.
Click to expand...
Click to collapse
Thanks for pointing that out, @elchi1234. I'm not used to work on linux-like systems, but I'm eager to learn.
However, I assume this could have something to do with permissions:
boondiordna said:
Offi is working, but can not find a location (GPS turned on). Also in Offi Stations, 'Acquiring location' never gets finished. The map stays blank in landscape mode.
Click to expand...
Click to collapse
I tried to figure out why Offi is not showing any map. It seems like it's trying to DL / access map tiles and not getting access, which sometimes even causes crashes:
Code:
W/MapsAPI ( 5201): MapTileDownloader: Problem downloading MapTile: /17/65535/65535 HTTP response: HTTP/1.1 403 Forbidden
According to the crash report, this happens with every tile the app is trying to access.
Did I mess up somehere?
Nice to hear that the Blank Store is now working for you.
Hm, that problem with Öffi sounds familiar to me - I seem to recall that I had these problems too.. since you could install those Apps it looks like your installation of the map files was succesful. I think you should try the GPS fix mentioned here. It really helps A LOT (or did you already do that..?)
Report back!
Well, the MapsAPI seems to be installed correctly. (It was never working for me, too. I use it for that apps that require it but don't really need it.)
I would guess that there is a change in the API of the webserver that MapsAPI doesn't know about.

Themes / Apps / Mods [Magisk] UnifiedNlp enabler module for stock ROM

UnifiedNlp enabler for stock ROM (Magisk module)​​What's this and what does it do?​
It's a Magisk module. You need to have Magisk working to use it. This thread can help with that.
It installs UnfiedNlp 1.6.8 as a system app and also does the magic that allows it to work as a location provider alongside Google Apps (aka GApps).
I've only tested it on the stock Sony ROM (firmware 62.0.A.3.163 to be more exact). Reports of whether it works on other versions are welcome.
It can in theory work on other ROMs but it depends a lot on the ROM. ROM variations is actually what makes it so fiddly and why such a deceptively simple module is so hard to find for your device. I don't intend to install other ROMs to test it but again reports are welcome. Please see below for explanations about how it works if you want to tackle it.
​No but seriously, what's UnifiedNlp and why do I care?​Your location provider (on a stock ROM from an established vendor like Sony) is Google. Elephant in the room, Google spies on you. They watch your location 24/7 and they learn things about you: where you work, where you live, where you shop, where you go to school, where you go in your spare time. They use this information to serve you ads. All vendors that want to be able to carry the Android trademark and be friends with Google are forced to put Google's location provider on their phone.
But Android actually has the ability to install multiple location providers, and switch them on and off at will. Except most stock ROMs come with this ability deactivated.
UnifiedNlp is an open source location provider with very cool features. It uses modules which let you use more privacy-oriented location services when you're online, and also let you determine your location offline, which gives you better privacy and also is very useful when you don't have a data connection. This Magisk module installs UnifiedNlp and tells the stock Sony ROM to let you use it.
But GPS already works fine on my phone​This isn't about GPS. Every phone/ROM has built-in GPS as a basic location provider. GPS doesn't depend on Google or anything else. You either get direct visibility to 4+ GPS satellites or you don't, and the AGPS (Assisted GPS) data that speeds up GPS fix is freely available online.
This is about being able to use WiFi spots and mobile cell towers for location. This works faster than GPS and also works indoors.
In order to use something to determine your location you need to know its position. The positions of GPS satellites are well known, but the positions of wifi spots and cell towers isn't. To get those positions you need to go to someone who has walked all around your street and has used GPS to determine the exact position of the spots and towers.
Google has cars that go everywhere in the world doing that, but every time you ask Google for this information they also use your location to track you. This module will give you access to that information from sources other than Google.
How do I use this?​
Install UnifiedNlp:
Download the attached ZIP on your phone (preferably under Download/).
Open Magisk, go to the modules tab, hit "install from storage" and pick the ZIP, then reboot.
After reboot you should have a UnifiedNlp system app installed. Some launchers will show it in their app drawer or even put it directly on the home screen for you, but regardless you can always open it from Settings > Location > Advanced >UnifiedNlp Settings. If it's not in the settings something is wrong.
Open UnifiedNlp settings and hit "Self Check".This gives you a screen with several checkmarks that should be on so everthing will work fine:
Permissions check: most of this will have been taken care of by the Magisk module, but you still need to tap it at least once. Grant location access if prompted.
Android version supported: will most likely never be checked, but like it says it doesn't mean much.
System supports this location provider: must be already checked. If it isn't, reboot once more after you've granted the location permission.
UnifiedNlp is registered in system: same as above, must be already checked. If it isn't, try a reboot. If this and the above check still don't enable something is wrong and this module doesn't seem to work on your ROM. See below for possible tinkering solutions.
Location backends set up: this will only become enabled after you install some modules. It's ok if it's off for now.
Network based location enabled: if this isn't checked, go to Settings > Location > Advanced > Google Location Accuracy and turn it on. In spite of the name it has nothing to do with Google, this enables/disables the use of wifi and mobile cells for location.
The last two checks ("has known location" and "provides location updates") may or may not show a check, but it doesn't matter, the real test will be getting your apps to work.
Install some modules. UnifiedNlp won't do anything without them. If you have F-Droid installed you can get these modules from it, otherwise you can grab the APKs from the F-Droid website.
NominatimNlpBackend: this is a must-have. It's an address backend, not a location backend. It matches a position to a postal address (city, street, number, that sort of thing).
MozillaNlpBackend or Apple UnifiedNlp Backend: at least one of these must be installed. These are the main location providers, equivalent to Google's. They need a data connection. They send information about nearby wifi spots and cell towers to Mozilla or Apple, and they get back an exact position. Both work equally well. Apple's has slightly higher precision, but Mozilla's privacy policy is better.
Modules below this point are optional. If you just wanted UnifiedNlp to be functional you can skip them, but they can be very useful when you don't have a data connection.
Deja Vu: when you have a GPS fix, this module saves/updates the position of nearby wifi spots and cell towers. When you don't have a GPS fix, it uses previously saved spot/tower positions to give you an approximate location. Doesn't need a data connection, doesn't need you to do anything, and it never needs any external service.
GSM Location Service: this module will offer to download a database of cell tower locations for your area. Then it will use it to determine your location based on cell towers detected nearby. Only needs data connection for the initial database download or for updates, after that it works offline.
WiFi Location Service: same as above, but for wifi spots.
After you install a module you must activate it in the UnifiedNlp settings, under "Configure location backends" or "Configure address backends".
Some of them may have additional settings available in there (gear icon). The GSM and WiFi location modules will need you to indicate your area and download a database.
If you can't enable location modules you've most likely missed a step (Network based location enabled) in Self-check.
If you're using XPrivacyLua you may want to either extempt these modules from restrictions or allow them location access.
Remember to grant Internet access in your firewall, if you have one, to the modules that need a data connection.
Verify that UnifiedNlp works:
Some app suggestions:
The NLP Test app lets you explicitly use "LM" (network-location like wifi/cells) or "GMS" (GPS) and also shows you lots of useful information, accuracy, different map markers for high/low precision etc.
The Gmaps WV app is a lightweight alternative to the Google Maps app (it uses the Google Maps website wrapped in a webview).
The OsmAnd app is a feature-rich map and navigation app that uses open map data from sources completely independent from Google.
The GPS Test app by Chartcross is very good for checking whether you're getting a GPS signal or not.
For testing that network-based location works you want to be indoors and you want GPS positioning to not work.
Disable all location modules in UnifiedNlp and check that NLP Test can't determine "LM" location.
Enable only one module, Mozilla or Apple, and check that NLP Test can get a "LM" location and also what accuracy you get.
The following tests are optional and results will also vary depending on your area and what cell/wifi coverage you get.
Enable only one module in turn between the GSM or WiFi service and see if you can get a "LM" fix with it.
Activate Mozilla or Apple module and Deja Vu, get a GPS fix, wait a minute or two, go indoors, check that you no longer get a GPS fix, disable Mozilla/Apple, and see if you get a "LM" fix in NLP Test with just the Deja Vu module activated.
​I don't like it, how do I uninstall and go back to Google location?​
Uninstall the module in Magisk and reboot. That's it.
Optionally you can uninstall the UnifiedNlp modules. They don't do anything without UnifiedNlp. Consider keeping them in case you change your mind and reinstall UnifiedNlp later. If you uninstall the modules you also lose the databases that they've created and you'll have to re-download them or let them recreate them (in Deja Vu's case).
How does this work (and how can I make it work on other ROMs)?​There are three things needed to make this work:
The UnifiedNlp app needs to be installed as a system app in /system/priv-app/UnifiedNlp/UnifiedNlp.apk. You want the version with GAPPS. Can get it from F-Droid or GitHub.
UnifiedNlp (org.microg.nlp) needs a bunch of system-level permissions. They can be granted manually, but the more elegant method is to put them in /system/etc/permissions/org.microg.nlp.xml.
Overwrite several location provider-related settings in framework-res.apk by using Runtime Resource Overlays (RROs), to allow UnifiedNlp to act as location provider.
Which packages are allowed to act as a location provider is set inside framework-res.apk in the config_locationProviderPackageNames array. This array typically only lists Google packages and org.microg.nlp needs to be added in there. There's also some string settings that indicate the "master" location provider which need to be set to org.microg.nlp.
In the olden days the only way to do this was to unpack framework-res.apk, modify the values, repack it with a custom signature, put it back on the ROM and hope for the best. Often this would fail if the ROM was checking that the apk was not tampered with.
At some point a better method came along: RROs. These are APKs that overwrite values in framework-res.apk. Sounds pretty simple, but it's complicated by the fact that different ROMs have different rules about what overlays can overwrite what settings. The Xperia 10 III (XQ-BT52) /system/build.prop gives the following priority order for RRO locations: odm,vendor,product,system_ext,system. Therefore this module installs the /system/product/overlays/UnifiedNlpOverlay/UnifiedNlpOverlay.apk RRO.
You will need to accomplish all three things above to make this work on another ROM. The 3rd one is the tricky one because there are multiple places where a RRO can go and not all of them work. Some custom ROMs already take care of step 3 for you. Otherwise, check the documentation I linked. You may want to try other dirs instead of /system/product (alternatives are listed in the docs). Or you may need to change the overlay XML files, in which case it gets more complicated, and you'll also need apktool to unpack and repack the overlay.
Credits​
The microg project for making UnifiedNlp.
TontyTon for the overlay.
Misaka4e21 for the Magisk module and the permissions XML.
I added the UnifiedNlp.apk to the module and figured out where the overlay needs to be placed on the stock Sony ROM to make it work.
Doesn't seem to install in Magisk. But I'm very interested in this module though ideally I'd want stock rom with microg.
lufei said:
Doesn't seem to install in Magisk. But I'm very interested in this module though ideally I'd want stock rom with microg.
Click to expand...
Click to collapse
What version of Magisk are you using? I'm on v24. Are you getting any errors, or are you just not seeing the zip in the Magisk installer?
wirespot said:
What version of Magisk are you using? I'm on v24. Are you getting any errors, or are you just not seeing the zip in the Magisk installer?
Click to expand...
Click to collapse
When trying to install the zip in Magisk I just get "copying zip to temp directory ! Unzip error" installing other modules work and I use Magisk 24.2
Can you also check that the zip was downloaded correctly? You can do this with md5sum from a terminal or adb shell, it should have checksum a54c4de46ecdbb228c496c59bc2cf275.
You can also try to install the zip from the command line like this: magisk --install-module filename.zip
Found the problem, I was putting the files inside another directory instead of putting them directly in the root of the zip. I've swapped the attachment in the first post with a correct file. Added a MD5 in the filename too, just in case. Thanks @lufei !
wirespot said:
Found the problem, I was putting the files inside another directory instead of putting them directly in the root of the zip. I've swapped the attachment in the first post with a correct file. Added a MD5 in the filename too, just in case. Thanks @lufei !
Click to expand...
Click to collapse
Now it installs and I was able to get all boxes checked, let's see how it works!
Thank you for the detailed explanation.
The topic of finding a location provider other than Google had interested me for a long time.
Until now, however, I had not yet dealt with it.
With this excellent tutorial I am now not only wiser, but can also confirm that everything as described also runs with the LOS18.1 GSI Rom and latest Sony Firmware.
Don't know if it's the GSI lineageOS or because I flashed the OpenGapps via Magisk, but I had trouble getting the current location in certain apps via both "LM" and "GMS".
The error was exactly as described here:
No GPS fix for most apps
With the solution described there, the problem could then be solved:
Code:
adb shell pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
adb shell pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Do you still get a LM fix if you disable all location modules in UnifiedNlp, or if you disable this Magisk module? Because I suspect you're actually using the Google location provider.
This Magisk module relies on the assumption that the UnifiedOverlay.apk file is placed in a location that will override the values provided by /system/framework/framework-res.apk. For the stock ROM it seems to work with /system/product but if that's not true for Lineage you may want to try modifying the zip and also copying system/product/overlay as system/vendor/overlay, system/oem/overlay, system/odm/overlay, system/system_ext/overlay and system/overlay.
wirespot said:
Do you still get a LM fix if you disable all location modules in UnifiedNlp
Click to expand...
Click to collapse
No, if I disable the location modules LM fix is not possible anymore.
psychofaktory said:
No, if I disable the location modules LM fix is not possible anymore.
Click to expand...
Click to collapse
Ah that's cool then. It's interesting that it requires .gms to also have location rights even if it's not using it. I guess as long as it's installed and listed as an official location provider it needs to have the permissions that go with it too.
@wirespot
Is there anything against using this Magisk module on a device other than the Xperia 10 III?
It won't break anything, it just won't work if the folders aren't good. UnifiedNlp settings will complain that the service could not be registered.
See post #10 for a list of folders. If it doesn't work as is, duplicate the system/product folder with all those other names, repack the zip, and try with that.
What ROM are you planning to try it on?
wirespot said:
What ROM are you planning to try it on?
Click to expand...
Click to collapse
Offical LineageOS 18.1 von Sony Xperia XA2 an unofficial LineageOS 18.1 on Xiomi Mi 9 lite.
On LineageOS you don't need the overlays (so none of the /system/*/overlay/* files or dirs) because its framework-res.apk already allows you to use UnifiedNlp (it lists org.microg.nlp as an approved location provider). This actually solves a major headache.
You can still use a Magisk module to install the UnifiedNlp apk to /system/priv-app and the permissions file to /etc/permissions/ systemlessly if you want (as opposed to actually mounting the root partition read-write and copying them there). This makes it easier for these modifications to survive LineageOS updates. (If you need to install them physically you will either need to copy them again after every update, or you can use a script that protects them during updates as described here.)
Please note that the actual apk you need to install depends on whether you install with Gapps or without. My module is made for a stock Sony ROM with Google Apps so of course there's already a location provider from Google (com.google.android.gms), so I need to use the UnifiedNlp.apk, package name org.microg.nlp, which is designed to work alongside Gapps. If you plan on installing Gapps on LineageOS then you need to do the same so you can use my module with just the */overlay/* stuff removed.
If you plan to use LineageOS without Gapps then you need to get the NetworkLocation.apk version of UnifiedNlp, which has package name same as the original Google package (com.google.android.gms). You will need to replace /system/priv-app/UnifiedNlp/UnifiedNlp.apk with /system/priv-app/UnifiedNLP/NetworkLocation.apk in the module zip, and also edit /system/etc/permissions/org.microg.nlp.xml and change the package name from "org.microg.nlp" to "com.google.android.gms". (The actual file name of the .xml doesn't matter, the system loads all the .xml files in that dir anyway, but you can change that too if you want to be tidy.)
Thank you very much for your answer.
Whenever possible, I prefer the systemless variant.
Therefore, your Magisk module would be a good way.
For all LineageOS installations I have installed the OpenGApps.
That means I simply remove the system\product\overlay\ folder and its contents from the zip file and can then flash the module directly with Magisk?
Is it enough to adjust the values in the module.prop to change the display name of the module, or is there anything else that needs to be considered here?
Tried with the steps I described in my post above.
Everything worked so far.
Except UnifiedNlp didn't register in system.
What's wrong with my setup?
Does it say "system supports location provider" in UnifiedNlp self-check?
Two common gotchas:
In the Self-check list, tap "permission to access location" at least once. It may be needed to grant additional location permission.
Make sure that using network-based location is enabled in the settings. I don't know what it's called on Lineage. On stock ROM it's called "Google location accuracy" which of course isn't useful.
Reboot once after doing all of the above.
Wait a couple of minutes after restart before you do Self-check, sometimes it takes a bit longer.
If none of this works try copying system/product/overlay as system/vendor/overlay, system/oem/overlay, system/odm/overlay, system/system_ext/overlay and system/overlay, in the zip, reinstall the module and reboot.
Self-check says that system supports location provider. Permissions are set and every mark is checked.
Network-based location is also active.
Phone was rebootet several times and I waited bevore testing with NLP TEST app.
I have created and installed a new ZIP file based on your recommendation. That seemed to did the trick.
Got a location wie LM NLP test. But far from my actually position.
But then I figured out, that the problem came from somewhere else:
Mozilla NLP gave me wrong Informations about my position. So I disabled it and enabled Apple NLP instead.
Since then everything works find.
If I see this correctly, the newly created Magisk module should then work on all LineageOS roms with GApps installed. Regardless of the device type.
Am I correct here?

Categories

Resources