Develop Bugs

[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][AOSP][CM][SafeStrap]Cyanogenmod 11 for SafeStrap with locked bootloaders

[ NO LONGER ACTIVELY BEING DEVELOPED - SORRY, READ THE POSTS FOR INFORMATION ]
Yes, you read that right. What we have here is a semi-functional CM11 (Kit Kat 4.4.4) for those with the locked boot loader using Safe Strap. I have been working on this for about a month, and this is what has come of that work. However, I need some help. I am not Android savvy enough to fix all of these problems to make this a fully functioning phone.
That being said, the phone does boot up and appears to mostly work. At this time, it is not a stable daily driver.
I did search all the threads, and I believe that this is not covered in another thread, so please forgive me if there is another CM11 thread that is for SS users on AT&T's locked boot loader phones. I don't see any.
How I got here:
Well, I wanted Cyanogenmod on my AT&T locked boot loader Safe Strapped phone. Every thread says we can't do that, and I just don't like hearing people tell me we can't do something and not provide any reasons. So I decided to try for myself. For the most part, they are right, but with enough perseverance, anything could happen.
I wanted to still use my phone as my daily driver, so I needed SafeStrap to work without having to bounce between kernels.
I was currently using Safe Strap with the NB1/NC1 kernels, and running Joe-Tech's GPE 4.4.4, so I decided that I should start with a 4.4.4 variant of CM, which lead me to CM11. I tried all of them, the nightlies, the home builds, the official builds, and I stumbled across one particular CM11 nightly (20151115) that would boot and then crash as soon as it booted. So I decided to use that as a base.
Reviewing the situation/logs/errors after each crash, I slowly removed, edited, or replaced something until it would not receive that error and would move on to the next error. By the grace of God it was slowly coming together! Hence why the built in camera app is gone and replaced with open camera, etc.
If we get this working, we may be able to use these hacks or tricks to get higher versions such as CM12 or perhaps (fingers crossed) CM13. I know this is kind of lofty, but perhaps we could get something going here. Once we identify the key problems, perhaps we can also apply these tricks to other AOSP variants, such as Slim Roms.
However, let's stick to putting one foot in front of the other right now and focus on CM11.
The Setup:
AT&T boot loader locked phone with NB1/NC1 kernel and modules flashed.
Safe Strap 3.75, currently using Rom Slot 1 for this, as my daily driver is on the stock slot, however I have done it both ways, and it works either way.
Download the below CM11 zip and put it on your phone.
In Safe Strap, choose stock or rom slot, then wipe and flash the CM11 zip.
After flashing the zip, flash the wifi modules for your kernel.
Once it boots:
Go to the settings->about phone->tap on build to enable developer mode.
Then, in developer menu, choose "Disable HW overlays" to always use GPU for screen compositing. (To improve graphics performance, you may find playing with the other graphics options help also.)
Then disable the lock screen by changing "slide" to "none" (To prevent sleep of death until we fix it.) Thanks @Sterben Pistole
Temporary Root:
Simply open the KingoRoot app and click on the padlock. This will take roughly 3-5 minutes, but it will successfully give you root permissions. After reboot, root permission will be lost, but you can simply open KingoRoot and give yourself root permissions again.
Download link:
http://www.mediafire.com/download/at7iw100uawi74k/CM11-20160322-SS.zip
OR This version, which includes the qcom scripts (testing):
http://www.mediafire.com/download/nb98rtkk2j0vjpa/CM11-20160326-SS.zip
Screenshots:
Boot animationhttp://www.mediafire.com/view/wgn5m57mjk5irvm/IMG_20160310_165320.jpg
Boot animationhttp://www.mediafire.com/view/7k8y591adrwsscw/IMG_20160310_162451.jpg
Settings http://www.mediafire.com/view/lrni6kpw04oi43d/IMG_20160310_165713.jpg
About phone1http://www.mediafire.com/view/8hb8slcwxgqxycl/IMG_20160310_165603.jpg
About phone2http://www.mediafire.com/view/ugra6jdeiz6wro5/IMG_20160310_165610.jpg
Dev. optionshttp://www.mediafire.com/view/qvd2q9uwd2vv8pn/IMG_20160310_165652.jpg
Home screen2http://www.mediafire.com/view/5h9vg4wxaacfpio/IMG_20160310_165742.jpg
Menu screenhttp://www.mediafire.com/view/55bvds7k08b2nkk/IMG_20160310_165548.jpg
Home screen1http://www.mediafire.com/view/qkod20qyyv3fska/IMG_20160310_165449.jpg
Check the following posts for issues and known working items. If you have an idea of how to solve the item, the best thing to do would be to download this CM11 and try it out. If you can't do that, or if you did and found a solution, just post your thoughts/trials/2 cents here in the forum and we can hopefully integrate it into the final product!
Team Members and Contributors: (People who have contributed to the project.)
@Sterben Pistole
@Evant28
Beta testers: @DeadlySin9
Huge special thanks to @jmsq and @Joe-Tech for permission to use things we need from their GPE roms!

Known problems
Here is a list of the Known issues:
SYSTEM:
-USB - MTP, UMS, and PTP are not currently working properly. The PTP may be working, but my Linux computer cannot connect to it. The UMS will not mount. The MTP says the connection is taking too long and resets (on my computer).
-Sleep of Death - Lock screen causes sleep of death and reboot errors. Must disable the lock screen to prevent this. Thanks @Sterben Pistole !
-Mounting external SD card - Currently the extSdCard is mounted, however it requires root privileges to use it.
-SU - Currently, @Sterben Pistole has found a SU temporary work around, however, it is lost on reboot.
-GPS - Not currently functioning.
-APN settings - Since that portion of the settings crashes, I thought we could edit the xml file directly and set a default option for the carrier of choice. Not ideal, but perhaps a good work around?
-TeleService.apk has been removed, it causes too many crashes, this apk is really important for phone calls/radio control, so this would really need to be replaced.
APPS:
-GPS Status - The app works, but GPS does not appear to be functioning.
-Messaging - Crashes when you open it. I think due to settings issue with connectivity to network.
-Settings - Mostly works, a few settings options cause it to crash, most importantly, the mobile network settings for APN's etc. crashes.
-Torch - Torch apk does not function at this time. Found that during CM kernel init, changes are made to facilitate the torch.apk, which are not done by the stock kernel init. However, it is possible that these could be written in as a init.d script.

Known Working
Here is a list of the known working:
SYSTEM:
-ADB - Fully functional.
-Audio - Makes sounds when you tap on buttons, appears to work fine.
-Bluetooth - Fully functional, used it to tether internet to use the browser, worked great.
-Bootlogo - Fully functional.
-Bootup - Boots all the way up the first time.
-Camera - Fully functional.
-External SD Card - Currently mounts, but requires super user privileges to use it.
-Internal Storage - Fully functional.
-Themes - @Sterben Pistole has verrified that different themes work.
-Wifi - Remember to flash your modules in SS! Thanks @Sterben Pistole
APPS:
-Apollo - Works great.
-Browser - Works great when you have an active network connection.
-Calculator - Works great.
-Calendar - Works great.
-Camera - Works great. Thanks @Sterben Pistole
-Clock - Works great.
-CM File Manager - Now working!
-DSP Manager - Appears to work.
-Email - Appears to work.
-Gallery - Works great!
-Movie Studio - Appears to work.
-People - Appears to work.
-Phone - Appears to work, but due to a settings issue with setting the carrier, I could not connect to make a phone call.
-Terminal Emulator - Works great.
-Voice Dialer - App opens, don't know if it works as I did not add my contacts.

Change log
Code:
3/26/16
-New QCOM script testing download link CM11-20160326-SS.zip
-Removed two of the scripts, the BT, and the BTDUN scripts. Those two scripts cause the Bluetooth to fail. Now the bluetooth works just as it did before the scripts were added.
3/24/16
-Alternate CM11-20160324-QCOMSCRIPTS-SS.zip download link
-Our NB1/NC1 kernel will need certain settings, services, and scripts run to be fully functional in regards to the hardware. Our kernel, through init, was calling for several qcom shells that did not exist. They have been added into this zip. Although it does not immediately solve any issues, it may be worth trying some of the things in these scripts, thus the original 20160322 zip is still available for download.
3/22/16
-New CM11-20160322-SS.zip download link
-Removed /recovery, boot.img, and file_context from zip as well as from updater-script. This makes it smaller and quicker to flash to your phone.
-Removed Loki script from installation script, as we do not need it on SS.
3/16/16
-New CM11-20160316-SS.zip download link
-External SD card now is auto mounted to /storage/extSdCard, however, it requires super user permission to use it.
-Dropped UltraExplorer and added ES File Manager for maintenance tools. Not intended for final product.
3/15/16
-New CM11-20160315-SS.zip download link
-Added Kingoroot for simpler one click rooting, root is still temporary.
(We had already achieved temporary root, but it was more complicated to activate than this. Kingoroot can re-root after restarting your phone.)
3/14/16
-New CM11-20160314-SS.zip download link
-Subtle changes in build.prop, fixed model # in about phone.
-Added TowelRoot, UltraExplorer, and Pushbullet for maintenance tools. Not intended for final product.
3/13/16
-New CM11-20160313-SS.zip download link.
-Camera2.apk fixed, open camera removed. Thanks [user=6053184]@Sterben Pistole[/user]
-CM File Manager fixed, removed ES File explorer.
3/12/16
-New CM11-20160312-SS.zip download link.
-WiFi Fixed, be sure to flash the appropriate modules in SS! Thanks [user=6053184]@Sterben Pistole[/user] !
3/11/16
-New CM11-20160311-AKLU-SS.zip download link with fix for internal phone memory "sdcard" mounting with SS.
-Sleep of death and reboot error workaround - Thanks [user=6053184]@Sterben Pistole[/user]
- Disable the lock screen to prevent sleep of death and to allow future reboots. We will want to disable or fix the lock screen function, but the workaround allows us to continue working at this time!
3/10/16
-Uploaded to XDA for assistance from other members and to share what has been done so far.
2/26/16
-Created new boot animation reflecting SS and CM.
2/24/16
-Removed Torch.apk, camera.apk, camera2.apk due to issues.
-Added OpenCamera - works great, and you can choose where to save pics.
-Added /system/lib/modules, but still cannot insmod them, due to no root permission.
-Tried Kingroot, will not root without internet connection, used bluetooth tether, but it did not recognize internet connection, even though browser worked online.
-Tried SuperSU, but it cannot update the binary.
2/23/16
-Removed teleservices.apk from /system/priv-app due to issues.
-Edited build.prop
-Now the crrashing has stopped, however we cannot use data or make phone calls without teleservices.apk. Perhaps we can steal it from another rom?
-Camera app crashes when accessing the camera.
-Settings sometimes crash.
-File manager could not find any storage devices, internal or external. Replacd with ES File Manager and now can see all files in mounted partitions.
-sdcard and extSdCard are not mounted at boot. Write script to do that?
-GPU needed set to no HW overlays in dev. options to prevent graphics errors/tearing.
-Bluetooth tests sat! :)
2/22/16
-Installed CM11 nightly through SS, but it constantly crashes.

I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.

Wow, this looks great! I'd love to help with this if I can.

Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.

Sterben Pistole said:
I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.
Click to expand...
Click to collapse
Tested, works great! Updated thread! Great work!
Now we should replace or fix the lock screen. At least now we know what the problem was. Great insight!

Evant28 said:
Wow, this looks great! I'd love to help with this if I can.
Click to expand...
Click to collapse
Evant28,
You bet, if you can, download the files and play around with it. Let us know if you find any way to fix anything and we'll put it to work.

Sterben Pistole said:
Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.
Click to expand...
Click to collapse
Great find on the disabled lock screen allowing reboots! I've added it to the instructions after booting up the first time. I am breaking down @jmsq GPE 4.4.3 rom to look at the script. I've also pm'd to ask their permission.

To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.

*deleted*

DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.

Mounting of sdcard fixed.
DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Internal phone storage "sdcard" mounting is fixed, new download link in OP. Turns out SS roms use a special sdcard mounting script. Thanks for the suggestions though, we need all the help we can get!

Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?

Evant28 said:
Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?
Click to expand...
Click to collapse
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great

Sterben Pistole said:
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great
Click to expand...
Click to collapse
Just about to flash, did you by chance get the build uploaded? Awesome work!

Evant28 said:
Just about to flash, did you by chance get the build uploaded? Awesome work!
Click to expand...
Click to collapse
uploaded wrong file lol There you go btw, there's still no service.
EDIT: Reuploading... Uploaded the original one by accident :/

Sterben Pistole said:
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.
Click to expand...
Click to collapse
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.

DeadlySin9 said:
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.
Click to expand...
Click to collapse
http://ubunmobile.blogspot.com/2015/03/moddev-enable-unsigned-kernel-modules.html Here's a link to what seems like it's what we're looking for.

Problem with Rooted Stock Rom with AirWatch

My company is now enforcing and managing BYOD with AirWatch. I'm trying to enrol my Magisk-rooted Pixel 2 XL. I've searched around XDA and other sites and I was able to enrol the phone when I use Magisk Hide to hide from the AirWatch agent, aka now the Intelligent Hub. It creates a Work profile and installed several work related apps. The only other app aside from Intelligent Hub I've tested so far is Boxer and it works for the few minutes during my test.
When I say Boxer works for a few minutes, that is because next I attempted to open Workspace One. As it loads, I'm guessing it checks other details about the phone, then it would popup a message saying Work apps and profile removing because the device is "compromised" and uninstall the work apps and Word profile.
I would like to use Magisk Hide and hide from Workspace One app, but Magisk Hide doesn't even list that and other apps in the Work profile. An admin at work checked the AirWatch server and it shows the device compromised detection with the status "Malicious file found - Check files in system or exec folder".
So my question is, outside of troubleshooting step by step from wiping phone and setting up each thing from scratch, anyone else have an insight on what else I can check?
FYI, these are the following setup I have on my phone
- Pixel 2 XL
- Rooted with latest version of Magisk and Manager
- Latest Pie 9.0 Aug 2019 Update
- Magisk Modules Installs: Busybox, Viper4Android
- Apps with Root Access: AdAway, BetterBatteryStats, Franco Kernel Manager, Material Terminal, Titanium Backup

s0l1dsn8k3 said:
My company is now enforcing and managing BYOD with AirWatch. I'm trying to enrol my Magisk-rooted Pixel 2 XL. I've searched around XDA and other sites and I was able to enrol the phone when I use Magisk Hide to hide from the AirWatch agent, aka now the Intelligent Hub. It creates a Work profile and installed several work related apps. The only other app aside from Intelligent Hub I've tested so far is Boxer and it works for the few minutes during my test.
When I say Boxer works for a few minutes, that is because next I attempted to open Workspace One. As it loads, I'm guessing it checks other details about the phone, then it would popup a message saying Work apps and profile removing because the device is "compromised" and uninstall the work apps and Word profile.
I would like to use Magisk Hide and hide from Workspace One app, but Magisk Hide doesn't even list that and other apps in the Work profile. An admin at work checked the AirWatch server and it shows the device compromised detection with the status "Malicious file found - Check files in system or exec folder".
So my question is, outside of troubleshooting step by step from wiping phone and setting up each thing from scratch, anyone else have an insight on what else I can check?
FYI, these are the following setup I have on my phone
- Pixel 2 XL
- Rooted with latest version of Magisk and Manager
- Latest Pie 9.0 Aug 2019 Update
- Magisk Modules Installs: Busybox, Viper4Android
- Apps with Root Access: AdAway, BetterBatteryStats, Franco Kernel Manager, Material Terminal, Titanium Backup
Click to expand...
Click to collapse
The following works but I am not sure if all the steps are crucial and which ones may be superfluous. Those instructions in (parentheses) may be not necessary).
I am not a programmer (Basic on a C-64 doesn't count, I take it), don't know anything about computer architectures etc., just able to follow instructions and wrap my mind around them to tweak my devices.
The main part is to "Hide Magisk Manager" after Boxer is installed (but before it is opened/setup) as that also creates another Magisk app (instance?) with the new name for the work profile where Boxer etc. show up and can be hidden with Magisk Hide.
The other (first) part is to hide anything that would alert and conflict with Hub before or during setting up the work profile - I pretty much hid everything under Magisk Hide...
I don't know BYOD nor Workspace One, so the solution below may not work.
- uninstall Hub (that's the only app remaining after the auto-uninstall, right?)
- if Magisk Manager is already hidden: go to Settings\Restore Magisk Manager "with original package and app names" - that seems to be important, as hiding it later and with another name will then also create a Work Profile where one can see and click and hide the work profile apps such as Boxer (not sure if it works the other way around, i.e. starting off hidden with a different name and then later restoring to original will create a Magisk work profile)
- Magisk Hide: click almost every system app, not just the Google ones, but almost everything, camera, calendar, contacts etc. and your phone maker's versions as well (not sure what is necessary, but only Google system apps didn't seem to do it...), also all root and SU related apps like BusyBox etc. (not sure what Hub looks for)
(- System\Apps > clear storage data for Google Play Store and other Play Apps, also make sure Hub is really uninstalled. If not or having problems at least clear data storage as well)
- reboot (can also go into TWRP and wipe cache/Dalvik, not sure if necessary)
- install Hub, don't open it
- open Magisk, go to Magisk Hide: click Hub
(- close Magisk)
(- reboot)
- open Hub, let setup run its course creating the work profile
- if there are conflicts showing in Hub (and/or on your employer's MDM website for your device), e.g. root certificate not installed, don't install any apps yet such as Boxer etc. and reboot instead
- Are those conflicts resolved after reboot?
- install Boxer and other apps (trough Hub itself, MDM website push (or Google Play)) but don't open/start them
(- reboot)
- open Magisk, go to Settings\Hide Magisk Manager and click on it, pick a name and confirm: this will then change the name of Magisk AND create a another Magisk app (with the new name) for the work profile.
- open that new Magisk work profile and go to Magisk Hide: click Boxer (and other apps controlled by Hub); Hub itself and everything already hidden in the private (= non-work) profile Magisk app should show up here as already hidden. Double and triple check.
(- reboot)
- open Boxer and start set-up
That's it. Stable, even after another reboot.

Did this solution work for you @s0l1dsn8k3?

I am in a similar boat. @s0l1dsn8k3 please let me know if you found an alternate solution.

I am in a similar boat. @s0l1dsn8k3 please let me know if you found an alternate solution.

HowTo setup Shelter or Island with debloated stock ROM One Ui 3.1 and Android11 ?

Hi everyone,
Iam running my G981B with Android 11 and One UI 3.1.
- I debloated it using the following post Ultimate Debloat S20.
- I reinstalled "com.samsung.android.knox.containercore" and "com.android.managedprovisioning"
When I try to setup Shelter I get the message "Device cannot be setup. If you need assistance please contact..."
When I try to setup Island I get the message "Setup of the work profile not possible. Security rules of your company..."
For Island there is the possibility to do a manual setup: Island Manual Setup
However, if I execute "pm create-user --profileOf 0 --managed Island" I get the most useless response "Error: couldn’t create User".
fw.max_users is set to 10...
Is that a common problem or do I just oversee anything else which I might have debloated and blocks the process right now ?
Thanks for any help !

Okay... obviously tripped knox prevents the device from creating a work profile.
Seriously...
So is there any viable workaround to get something like Shelter or Island running ?

I'll ask to move your thread to Q&A.

I kind of solved my problem by facilitating Samsungs' Dual Messenger functionality.
If dual messenger gets enabled it sets up a separate user profile which is used with a workprofile in order to run multiple messenger app instances.
The beauty is that you can use this to install any app within that profile using adb. So basically the feature is not limited to those few apps you can tick from the settings menu.
Credit goes to @VincentThacker who is describing the procedure here:
Add non-messenger apps to Samsung Dual Messenger?
So the creation of parallel workspaces is blocked in the Security Policy of 8.0, preventing multiple copies of the same app. However, Samsung's Dual Messenger still successfully copies apps it sees as messenger apps, and allows them to run just...
forum.xda-developers.com
One additional hint from my side:
- If you install aurora through ADB in the work profile all apps you install from this version of aurora automatically get installed on the work profile as well. So no need for installing apks through adb afterwards anymore.

flunkyball said:
Okay... obviously tripped knox prevents the device from creating a work profile.
Seriously...
Click to expand...
Click to collapse
Actually, it doesn't seem to be Knox related: If I setup the phone (Samsung S20) from scratch without FBE encryption (by flashing multidisabler), I can set up Island with the root way and/or by ADB.
If I set up the phone with encryption, Island can't be set up like described here.

gorthon said:
Actually, it doesn't seem to be Knox related: If I setup the phone (Samsung S20) from scratch without FBE encryption (by flashing multidisabler), I can set up Island with the root way and/or by ADB.
If I set up the phone with encryption, Island can't be set up like described here.
Click to expand...
Click to collapse
Good to know. However having the device unecrypted just to use Island is not an option. Currently Iam quite happy with facilitating Samsungs Dual Messenger functionality for it.

How To Guide [GSI] [A13] Pixel Experience Plus for Galaxy S21 FE 5G (Snapdragon/Exynos)

* Your warranty is now void.
* I'm not responsible for bricked devices, dead SD cards,
* Please do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, i will laugh at you.
Click to expand...
Click to collapse
Pixel Experience Plus for Galaxy S21 FE (Snapdragon/Exynos) based on Android 13​Unlock bootloader first:
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
Click to expand...
Click to collapse
Guide for flashing system image:
Flash recovery for snapdragon version, i'm using: OrangeFox Recovery is also provided for exynos soc
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
reboot when you sure recovery is permanent and check if phone is on "hello screen"
How to boot on recovery first time BEFORE "hello screen":
Uncheck reboot after flash AP recovery in Odin, unplug cable and then push vol - and power -> immiedietly after turn off download mode hold vol + and power and plug in cable -> now should work
Flash GSI image:​First you need to download image from here: here or find thread here: click. This images have Google Apps allready included.
Remember to use arm64 with b !
Reboot to recovery
Now u should see on PC when u connect via cable internal memory - copy image to folder, probably should be "Fox" or create new
Touch files, find image
Now select to flash System image
Reboot
And thats it you should boot to system.
Post install settings​On Phh Treble Settings set:
Samsung features:
Use alternate audio policy
Enable stereo audio mode
Enable extended brightness range
Enable double tap to wake (if u want)
Enable reversed wireless charging (if u want to reverse charge other device)
Enable access to all cameras
Enable extra sensors
Misc features:
Force FPS to [email protected] if you want 120Hz refresh rate display
On camera set expose aux cameras and force enable camera2api
Select Use System Wide BT HAL if u use bluetooth headphones and don't have audio (tested on galaxy buds 2)
Qualcomm features:
select use alternate camera profile if u have trouble with ultrawide photos
Root access on Pixel Experience Plus:​
You should first patch boot img from your stock samsung rom what you allready using
U need to select ap tar.img file in Magisk and wait to be patched
Extract boot.img from it after patch
Flash boot img in recovery on boot image
Root stays even if you reflash system on other GSI
Works:
WiFi 2.4GHz and 5GHz
RIL (phone and mobile data)
Bluetooth with bluetooth audio
fingerprint sensor
Google Pay with NFC (you need to pass safynet check if you have magisk)
120Hz display
Camera front and back (you need other camera app for using ultrawide photo)
Fastcharge
Stereo speakers
Galaxy accessories (Watch 4 and Buds 2 tested)
MHL mode
Probably other functions too
Not work/problems:
Netflix have videwine L1 but no HDR content support
Movies only record max on 30FPS on 4K
On the go don't work any of galaxy wearable devices, you need to patch via magisk some files
Clear View cases (phone don't response for open or close case) even on AOD
Some problems with updates for Chrome and web framework (need to install manual newer version)
Device is showing as Huawei Nexus 6P need to be changed somehow to our model
Workaund for Galaxy Wearable and Google Pay:​
Magisk need to be in zygisk mode
Flash Universal SafetyNet Fix, here: github download
Install FoxMMM for magisk modules finder here: here, find and install MagiskHide Props Config
Flash this for workaund of wearables: gdrive module download
Now download Galaxy wearables from store, and plugins for your proper device form apkpure or other website.
You need to allow all permisions for apps first
Try to find your watch and pair it, you need to be fast to accept all pop ups - u dont need to login to samsung account , for me got it after 2-3 try, you should see "prepairing device" etc.
For galaxy buds should be easier just find it and pair.
Google Pay works out of the box after installing this modules
Get better sound and equalizer:
If you want to have better audio - you need to flash magisk module ViperFX
Download here: click here on github
Flash via magisk
Uncheck legacy mode for work

@hunter3000
Greetings. Since this appears to be a "guide," I have changed the thread designation accordingly.
-Regards: Badger50

@hunter3000 i think you can change the model number in the build.prop if im not mistaking

Hi, can i flash it like the offical pixel experience? Because the offical one is a zip file and this one not

this is GSI style rom, not specific ROM for specific model, so you must flash it by twrp or by fastboot command. Like universal rom for all phones than have project treble.

Thanks for support
Im looking to xda everyday for a stable pixel rom

MemurBey said:
Thanks for support
Im looking to xda everyday for a stable pixel rom
Click to expand...
Click to collapse
Majority of GSI are stable but you will have bugs tho. Like either bad battery life or camera isnt working

On this build all functions is working, for camera ultrawide support you need 3rd party app like OpenCamera.

hunter3000 said:
On this build all functions is working, for camera ultrawide support you need 3rd party app like OpenCamera.
Click to expand...
Click to collapse
Does Gcam Works on any Gsi on the SnapDragon variant? No freezing viewfinder?

no gcam working on snapdragon, or i dont find any working for our model.

hunter3000 said:
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
Click to expand...
Click to collapse
When disable encryption how safe is the Data stored on the Device?

OptixWolf said:
When disable encryption how safe is the Data stored on the Device?
Click to expand...
Click to collapse
you must disable encryption to boot to non official rom, so you got answer for your question

Master, any solution to this ? "Device is showing as Huawei Nexus 6P need to be changed somehow to our model ", and Call Recording is working on this version ? many thanks for your hard work to G990B version.

This device showing is related to magisk safenet fix for working root with NFC and banking apps but probably also because of GSI rom as is. No call recording as is stock Pixel Experience ROM u need to root and use some magisk module.

Works great on my Samsung s21fe just charging.. sometimes works then other times says it's charging and then does down. Doesn't really go up unless phone is off.

May I know if VoWifi / VoLTE works?