[Q & A][ROM] [4.4.4] Plain-Andy - G2 Q&A, Help & Troubleshooting

Feel free to discuss any possible bugs/issues that are to arise.
Plain-Tweak:
Ever wanted to control your kernel from a file on your internal storage? Now you can! There are currently 3 different ways
1.) Manually create a text file on the root of /sdcard
named 'plaintweak' with the following values:
gov=(your choice of governor)
maxkhz=(max cpu clockrate for all cores)
minkhz= (min cpu clockrate for all cores)
scheduler=(choice of IO scheduler)
tcpcong=(choice of TCP Congestion control)
2.)Invoking the instruction 'plaintweak' with adb shell or Terminal Emulator.
3.)Separate aroma package for your device(not yet created) or through the rom installer.
When I run 'plaintweak' from aroma package adb shell or Terminal Emulator wouldn't it get overwritten?
No! Not at all. Your old settings are saved at /sdcard/plain-tweak listed by date.
Don't like the values? Want a different configuration? Rather use Performance Control or another app?
Simply rename your current plaintweak file or move an older plaintweak file located in /sdcard/plain-tweak to root of /sdcard.

Def the most stable aosp on lg g2. On the new build im getting echos while in convo. Not on my side but on their side. Tried both dirty and clean flashing. Reverted to 10/25 and issue is gone. Regardless thanks for your work. Saves me from the stock software ?

Awesome rom I love the feel and how quick it is.. head and shoulders above the last stable CM11 (M6, which I had been using since May) for D800.
Couple questions - I viewed back about 15 pages but couldn't find anything..
I know CM has had some issues lately with rotation, proximity sensor and light sensor. I just flashed the 11/7 version and my phone won't rotate. Not a big deal to me, and I'm not sure if it's known, but I wanted to throw that out there.
Also, might be a stupid question but I removed the stock lockscreen and can't seem to get it back. Reflash?

@RamOdin
First, thank you for the feedback. Second; Reflash. Third; make sure you're on an unmodified kitkat baseband. Also check your quick toggles for the autorotate toggle prior.

Thanks - will do this evening. Is it normal for all ROMs to only be able to do google login from Wifi?
---------- Post added at 10:54 AM ---------- Previous post was at 10:42 AM ----------
Ignore that last post.. I'm a dummy sometimes. Additionally, I cannot edit it.

@RamOdin
Flash ROM. Boot. Reboot back to recovery. Flash gapps. Then on boot, launch Play store, that will bring up the Google account wizard.

@Snuzzo
So it's not your ROM causing the issues on my phone. I flashed both LiquidSmooth and DirtyUnicorns, both having the same issue.
Strangely, the only thing that fixed it was flashing the latest nightly from CM11, watching it go into a bootloop and then wiping in recovery and restoring my last backup of CM11 M6...
Weird.. *shrugs*
Any ideas? I know it's not your job to troubleshoot me, but I really love this ROM and would love to use it daily.

No clue unfortunately. These G2's can be finicky. Try doing a TOT/KDZ restore to stock.

I love it. Will update to your L rom when available.
On a side note for anyone who doesn't know, if you're using the ls980 (sprint variant) but on an American gsm network the dialer trick does work.
Remember, it's *#*#4636#*#*

Related

Overclocking HTC Wildfire

Hey Guys,
Being a PC overclocker I felt like a fish out of water when it comes to overclocking a phone
I recently got a HTC Wildfire and found out how to root it and flashed my own ROM, Kenral etc. (with some difficulties)
So I downloaded SetCPU and started OC'ing. Being a PC overclocker I followed the logic of set speed and run stability test.
So I slowly started upping the max speed and then stress testing for 20 min odd. I just kept on upping the speed until I got to the limit of SetCPU (768Mhz). Where to from now?
I have not changed the minimum speed because I have read that it can make your phone rather unresponsive.
Is it possible to go above 768Mhz or will I damage the phone or have to up voltage?
I ran linpak and at 768Mhz I got just under 3 MFLOPS. Is that good or bad or what?
Thanks in advance guys
Mikrouwel
768 is the safe limit, you'll need to make a kernal that will allow the processor to go further, 3mflops is good on a sense ROM but on an AOSP ROM you will get over 5 easily. Why do you want to go over 768 anyway?
What is the difference between sense and AOSP ROM? If it is just the sense feture then I dont mind changing ROMS. (Dont use sensce)
Also what is Cyanogenmod 7 RC1? Is it the same os CM7? Seem alot of people talking but dont now what it is?
Thanks
Mikrouwel
AOSP -> Android Open Source Project. It is vanilla Android, without Sense. So Yes, your assessment is correct. It is just the Sense feature.
Cyanogenmod 7 = CM7. Just a short way of writing it.
Hi There
Is Cyanogenmod 7 a ROM?
Also is Android Open Source Project ROM too or a app?
Sorry kinda confussed
Also what is Clockworkmod Recovery? Does it have something to do with ROM Manager?
Thanks
Mikrouwel
1: Yes, CM7 is a ROM
2: AOSP Official Page: http://source.android.com/
3: Recovery Images are found whenever you boot into Recovery. Example: All that you see like Clear Cache, Install ZIP from SDC etc. are part of a recovery. ROM Manager is a standalone app and is not related to Recovery, although, it can help update the recovery since the developer of Clockworkmod Recovery and ROM Manager are the same.
Technical Definition of Recovery: (Sourced from Turkeys Ultimate Guide Glossary)
The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the #data partition of the phone (a hard wipe), or perform an update using an update.zip file on the root of the microSD card. It is common (although not necessary) to flash a patched Recovery image, such as Amon RA's one. This allows you to run Nandroid backup from the device, and flash modifications, such as update.zip files to the device, essentially becoming a means to install sotware to the device. Recovery mode is separate from 'normal' mode, and can be entered by holding down home whilst turning the phone on.
Oh, you should probably go through Turkeys guide and glossary yourself. It should help a lot.Thread : http://forum.xda-developers.com/showthread.php?t=824396
Glossary : http://bit.ly/9HtICk
Many thanks Guys,
ATM I am using this ROM with this kernal. Were can I download CM& and will the notiable differences be between the one im using and CM7?
Also what is New Nightly? (You have #13 next to yours?)
Thanks alot guys
Mikrouwel
CM7 can be found here:
http://forum.xda-developers.com/showthread.php?t=918072
Or, the latest, i.e. RC2 can be found here:
http://forum.xda-developers.com/showthread.php?t=957140
Nightlies are automated builds created by the Build bot. If you check the first link I posted, in that post's download link, you will find new nightlies everyday. Nightlies implement minor code changes, and, are experimental releases. They may add new features (eg: Nightly #11 implemented Android 2.3.3, #13 implemented FM Radio etc.), but may also add new bugs sometime.
As for differences, one cant say for sure, since ROM preference is a personal choice. Try it, if it suits you, use it, else, switch back.
Hi There,
I am going to try CM7.
IS the RC2 stable and if so is it more or less stable than RC1?
Also if I just go into recovery and flash will I have to flash nightlys or not?
If I am not mistaken it runs 2.3 and I thought that there were many features that didnt work on 2.3? (Gingerbread)
Also what kernal do you recommend I should use on CM7 that will let me got 768+?
Many many thanks guys for all the help
Oh yes and what app do I use if I want to keep all my apps and contacts and stuff like that? I used titanium backup last time and only got like half the stuff back?
Thanks Guys
Mikrouwel
* RC2 is stable for me. No issues so far, although camera sound bug is still there - If you take some pics using flash, phone loses all sound and you have to reboot.
* After RC2, it is upto you whether you want to flash nightlies or not. There is no compulsion.
* Can you list some features that dont work on 2.3? Personally, I cant find anything amiss over 2.1 / 2.2
* CM7 comes by default with an overclocked kernel, which will allow OC to 768. Overclocking beyond 768 is not possible since that is the safe limit for the Wildfire's CPU. Because it is overclocked by default, if you get a bootloop, flash HCDR.Kernel v4.1 after flashing CM7. This will restore stock clocks, but, still allowing OC using an app like SetCPU
* Apps can be backed up using Ti backup / Mybackup Pro etc. Contacts can be backed up by going to Contacts > Export > To SD Card. Then, after flashing, again going to Contacts > Import > From SD Card, and select the VCF File. SMS'es can be backed up by using the free SMS Backup App from the market.

[REF] Nexus S ROM&Kernel Survival Guide

Introduction:
Please read and try to do some research instead of bombarding the developers with the same questions over and over, cluttering the threads with useless and recursive information. I will try to include terms for all the ROMs and Kernels in the Development Section, and remove the obvious things as much as possible. That doesn’t mean it will be perfect! I hope this will be useful for beginners, because it provides most of the basic information you need to get started. From now on, it’s up to you what you do.
I am fully aware that the information included here is for one time use, enough to get you started. Some of these things ARE well known by many of you, but they are still useful for others that are just beginning to learn about their NS. Besides definitions and explanations, I’ll also link to useful posts around xda and other sites, which provide further information on the respective subject.
ROMs​(ROM: a firmware that contains the Android operating system, and at least critical apps necessary for running your phone (but usually more apps than just those); can be stock or custom, and comes packaged in a *.zip file, flashable under recovery)
AOSP-built ROMs
Features: these are built from source code, from the Android Open Source Project, delivered free of bloatware and with rich customizations.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyanogenMod 9 (still in alpha stages for now)
IML74K Android 4.0.3 Build 4 - Quad Lockscreen + More MODS (1/15/12)
nuhetri- v1.0.0
Slim ICS
AOSP+ V2.3|ICS 4.0.3|Source Built|Status Bar Widgets + Nice Mods
4G VERSION
vhgomez36-ICS-NXS-4G-4.0.3 r2.0
IML74K Android 4.0.3 Build 3 - Quad Lockscreen+More MODS
Crossbones v0.1.3
CyanogenMod 9 v4.0.3 - Alpha 20
Click to expand...
Click to collapse
Moddified ROMs
Features: these are modified versions of stock/AOSP ROMs/other custom ROMs, that keep the look of the base ROM up to a certain point. Also generally free of bloatware and with some additional modifications.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyberGR-MOD|NS.NGN ver. 4.0 Ultimate
NSCollab 1.0.60
Ultimate ICS v4.0
-=Nexus MV 1.12.09=-
KANGY6 | ICS | AOKP |
NexusBeam 4.2.3
CyberGR-MOD|NS.NGN ver. 3.0 Hybrid ICS
Click to expand...
Click to collapse
MIUI-style ROMs
Features: unique type of ROM, developed by the Chinese. Has a strong iOS feel, highly customizable.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
◄ ▌ [09.Jan.12] [ROM] Brainmaster's MIUI 2.1.6 ICS | Stable 2.3.7b v2 GB ▌►
DianXin OS (DX ROM) ICS | GB ROM
4G VERSION
◄ ▌ [28.Nov.11] [ROM] brainmaster's MIUI NS4G 1.11.25 | OTA ▌►
Click to expand...
Click to collapse
Stock ROM
Official releases from Google. The reasons most people here flash a stock ROM are: they want to update/ are bored of custom ROMs/ want to start over with their phone/ warranty reasons.
If you want to go back to stock for some reason, check this thread and read carefully, so you get the correct version for you.
Click to expand...
Click to collapse
Once we decide for a type or ROM (except stock), we head over to the ROMs thread and begin reading the list of features. Now would be a good time to PANIC! No, no, just kidding Those words do exist in some kind of language (not necessarily English). So here’s a very basic list of the most common terms found in our ROM threads:
Code:
[B]AOSP[/B]
[quote]Short for [url=http://source.android.com/]Android Open Source Project[/url]. Its purpose is to maintain the development
of the Android platform. Anyone can use the Android source code for
any purpose, and this is when custom ROMs come in. The [AOSP]
tag is used here to signal a ROM built from Google’s source, a pure
ROM, free of bloatware, with very good performance (generally)
and a very extended degree of customization. [/quote]
[B]Build.prop[/B]
[quote]This file is located in /system/build.prop. It holds the majority
of the runtime flags that are used when Android boots. Basically, it
lists specific information about your device, for applications to use.
You can also edit lines, with a file manager that has access to
/system, in order to change LCD density, build number, device
model and many more. [/quote]
[B]Busybox(ed)[/B]
[quote]Busybox is a collection of simple, but powerful Linux
utilities, that Android doesn't come with by default. It is used
by applications like MetaMorph and Titanium backup in order
to do special operations. You can manage ther version installed
on your phone with various apps from the [url=https://market.android.com/search?q=busybox&c=apps]market[/url] [/quote]
[B]/boot partition[/B]
[quote]This partition includes the bootloader and kernel, and
it enables the phone to boot. Wiping it must be done only if
requested, and the phone must not be rebooted after this operation.
Instalation of a new one is done by flashing a ROM that includes
the /boot partition. [/quote]
[B]/cache partition[/B]
[quote]Inside this partition, Android stores frequently accessed
data and app components. Performing a wipe of the /cache does
not affect personal settings or files, but simply gets rid of existing
data there, which gets automatically rebuilt in time. [/quote]
[B]Dalvik cache[/B]
[quote]Dalvik cache collects the information about the installed
applications and frameworks, and organizes them into a writeable
cache. Under this writeable cache, it stores the “optimized”
bytecode of the applications which is used by the applications
themselves later for a smoother operation. This dalvik cache can
grow as more applications are installed on your phone. It is safe
to wipe dalvik-cache. It will be rebuilt again when the phone
boots. This also explains why your phone takes ages to start up
for the first time. [/quote]
[B]/data partition[/B]
[quote]Also called userdata, the data partition contains the user’s
data – this is where your contacts, messages, settings and apps
that you have installed go. Wiping this partition essentially performs
a factory reset on your device, restoring it to the way it was
when you first booted it, or the way it was after the last official
or custom ROM installation. When you perform a wipe data/factory
reset from recovery, it is this partition that you are wiping. [/quote]
[B]Deodex(ed)[/B]
[quote]In Android file system, applications come in packages with
the extension .apk. These application packages, or APKs contain
certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application
that are optimized before booting. Doing so speeds up the boot
process, as it preloads part of an application. Deodexing is basically
repackaging of these APKs in a certain way, such that they are
reassembled into classes.dex files. By doing that, all pieces of an
application package are put together back in one place, thus
eliminating the worry of a modified APK conflicting with some
separate odexed parts. The advantage of deodexing is in modification possibilities. On the other hand, since the .odex files were supposed
to quickly build the dalvik cache, removing them would mean
longer initial boot times. However, this is true only for the first
ever boot after deodexing, since the cache would still get built
over time as applications are used. [/quote]
[B]EFS folder[/B]
[quote]This is a VERY important folder. It contains phone-specific
information, like IMEI (encrypted in the nv_data.bin), wireless
devices MAC addresses, product code (also in the nv_data.bin)
and more. I advise you to make a backup of this folder, and keep
it safe. Remember, backup BEFORE flashing anything. Use [url=http://forum.xda-developers.com/showthread.php?t=1138873]this tool from forum member Borky_16[/url]. [/quote]
[B]Init.d[/B]
[quote]Init.d is very useful because it runs scripts that you can
just delete or replace in the /system/etc/init.d folder. The scripts
are also very flexible and can be used to call other scripts or set
a variety of system settings. [/quote]
[B]G-apps/Gapps[/B]
[quote]A long time ago, in a galaxy far far away, there was a
developer. And he used the Force for developing something called
CyanogenMod. For the happiness of the other folks in the galaxy,
he included some applications from Google. But the Emperor…
oh, sorry… But Google didn’t agree with him including these
proprietary apps, so they sent him a cease and desist letter.
Long story short, the Google Applications are provided separately
via a flashable .zip file. This is the case for pure AOSP ROMs,
and theoretically this is how it should be done. Theoretically. [/quote]
[B]Host File[/B]
[quote]Located in the /etc/ folder, it is used to block ads.
Most ROMs come with a “blocks ~95% of ads” statement. You
can also manage it with apps from the [url=https://market.android.com/search?q=ad+block&c=apps]market[/url]. [/quote]
[B]Logcat[/B]
[quote]The Android logging system provides a mechanism for
collecting and viewing system debug output. Logs from various
applications and portions of the system are collected in a series
of circular buffers, which then can be viewed and filtered by
the logcat command. You can use logcat from an ADB shell to view
the log messages.[/quote]
[B]NANDroid[/B]
[quote]When you take NANDroid backup, it means you are
backing up entire ROM. It’s basically a picture of the ROMs’
state . So when something goes wrong, you have the
chance to restore your phone to the backup state using the NANDroid. [/quote]
[B]NSTools[/B]
[quote]An essential tool that manages tweaks like BLN,
BLD, BLX, Liveoc, OC, CPU Governor, Deep idle and so on.
Written by arifhn, available in the [url=https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result#?t=W251bGwsMSwyLDEsIm1vYmkuY3lhbm4ubnN0b29scyJd]market[/url] and on [url=http://forum.xda-developers.com/showthread.php?t=1333696]xda[/url],
this is a must have application for managing these various options. [/quote]
[B]Odex[/B]
[quote]These ‘odex’ files are actually collections of parts
of an application that are optimized before booting. Also explained at deodex(ed). [/quote]
[B]Power Menu[/B]
[quote]A multiple choice menu that appears when long pressing
the power button. In stock, these are critical options,
such as powering down the device. Developers have also
added options for taking snapshots,
rebooting normally/into bootloader/into recovery and so on. [/quote]
[B]Radio[/B]
[quote]The radio controls basic low-level functions like
network connectivity, Wi-Fi, and GPS. It comes as a radio.img file,
and generally, developers try to leave this out of their
ROMs because different areas require different radios. Pay attention
to this when choosing to flash a new ROM. There is a reference
thread with all the radios [url=http://forum.xda-developers.com/showthread.php?t=1116884]HERE[/url]. [/quote]
[B]Ramdisk[/B]
[quote]Ramdisk.img is a small partition image that is mounted
read-only by the kernel at boot time. It only contains /init
and a few config files. It is used to start init, which will
mount the rest of the system images properly and run the
init procedure. A Ramdisk is a standard Linux feature. [/quote]
[B]Recovery[/B]
[quote]Recovery mode in Android provides an environment for
users to wipe cache, data, factory reset the phone or update
it with a .zip file. There are custom recoveries like [url=http://www.clockworkmod.com/rommanager]ClockworkMod[/url] or [url=http://forum.xda-developers.com/showthread.php?t=1399565]TWRP[/url], which provide additional functionality,
and are very popular for this reason. [/quote]
[B]RTL[/B]
[quote]Short for Right-to-Left and refers to support for languages requiring this type of writing. [/quote]
[B]SetCPU[/B]
[quote]An application built by coolbho3000, which allows CPU speed tweaking and management, allows overclocking, and sets CPU governors. Available on [url=http://forum.xda-developers.com/showthread.php?t=505419]xda[/url] and the [url=https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.]market[/url] (try to buy from the market if you want to support his work). [/quote]
[B]SIM Toolkit (STK)[/B]
[quote]Now if you live in the States, you might not even know what
the STK is, so a bit of explaining is in order. Put simply, the STK
allows carriers to load a simple set of menus and 'applications' on
your SIM card. Earlier versions of Android, up to 1.6, actually
included a rather rough, but functional Sim Toolkit application, but
at some point it was dropped. [/quote]
[B]/system Partition[/B]
[quote]This partition basically contains the entire operating system,
except the kernel and the bootloader. This includes the Android
user interface as well as all the system applications that come
pre-installed on the device. Wiping this partition will remove Android
from the device without rendering it unbootable, and you will
still be able to put the phone into recovery or bootloader mode
to install a new ROM. [/quote]
[B]Unsecured Boot.img[/B]
[quote]Used for adb remount, gets you root by default on a shell. (ro.secure=0) [/quote]
[B]V6 Supercharger Script[/B]
[quote]A more technical explanation could be done here, but
the bottom line is that this is used to make your phone run
faster, by better management of memory. [/quote]
[B]Zipaling[/B]
[quote]Zipalign is an archive alignment tool introduced first
time with 1.6 Android SDK (software development kit). It
optimizes the way an Android application package (APK) is
packaged. Doing so enables the Android operating system to
interact with the application more efficiently, and hence has
the potential to make the application and overall the whole
system much faster. Execution time is minimized for zipaligned
applications, resulting is lesser amount of RAM consumption
when running the APK. [/quote]
Kernels​
(Kernel: provides the most basic level of control over all of the phone's hardware; consider them a link between the hardware components and the ROM)
With kernels it’s a little bit easier. At least this is how it may seem. Right after rooting the device, many choose to first flash a kernel (including me) mostly because it gives the opportunity to flash something while not modifying the appearance of the phone. Furthermore, it gives you the ability to change things like CPU clock speed, internal and ARM voltages, and also have different patches and mods designed to prolong battery life/improve speed/provide stability.
Kernels are abundant for the NS, so I’ll be naming the most popular:
GLaDOS
ICUP Kernel Edition
*Matr1x*
SG-NS-ICS - 14-01-2012 - 11UV|Voodoo|BFQ|BIGMEM|BLN|BLD|BLX|TW|Lazy|3.0.15
Netarchy Nexus
NS+4G Trinity (E)UV and OC CM9 + m(any) roms
Click to expand...
Click to collapse
Many users ask around about which could be the best kernel. For this, xda member bedalus decided to set up a thread where he benchmarked ICS kernels (accurately enough). This should give you an idea where to start from.
Also, there are terms which appear frequently in the features list of kernels, so here’s a very basic list of the most common terms found in our kernel threads:
Code:
[B]BFS[/B]
[quote]A Brain F**ked Scheduler will perform better on CPU intensive
process, which usually cause them to get higher benchmark scores.
However because it only dedicates minimal CPU to background
processes you may experience lag when switching quickly between
different tasks. [/quote]
[B]BLD[/B]
[quote]Backlight Dimmer provides an option for the lights of the
touchkeys to be turned off after a certain period. This can be
tweaked from NStools. [/quote]
[B]BLN[/B]
[quote]Backlight Notification is a mod developed by neldar,
which converts the touchkey backlights into a notification led. [/quote]
[B]BLX[/B]
[quote]Battery Life eXtender, from Ezekeel, manages the maximum
percentage to which the battery is being charged. By default,
the Nexus S is charged to about 95% capacity. [/quote]
[B]CFS[/B]
[quote]A Completely Fair Scheduler is more suited for multitasking.
You may notice performance issues when using CPU heavy
activities like HD games because it is trying to keep the other
processes in the background equal to the one that is hogging the
CPU. It should also be noted that, as designed, this type of
kernel should handle going from listening to music to sending a
text to surfing the web with minimal lag. [/quote]
[B]Deep IDLE[/B]
[quote]Another mod by Ezekeel, which allows the phone to
enter a “deep idle” state while performing tasks when the screen is
off. For example, listening to music with the screen off and
Deep Idle turned on, you should get better battery life than
without Deep Idle. [/quote]
[B]Governors [/B]
[quote]There is a much to be said here, and this would stretch
this dictionary too much. I recommend reading [url=https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt]THIS[/url], a very good explanation of
governors—from CyanogenMod. [/quote]
[B]OC (Overclock)[/B]
[quote]An overclock is usually one of the first things users
figure out after gaining root access on a new phone. If you
want to push your smartphone's CPU to run more clock cycles,
you have to know that extra power isn't coming from nowhere.
However, it is generally considered good practice, but it
depends on your handset. Some phones may be able to support
overclocking to 1.4 GHz, while others may never get past
1.2 GHz. Just proceed with caution. [/quote]
[B]Touch Wake[/B]
[quote]Yes, yes, Ezekeel again. This mod allows the user to
wake the device after a set amount of time, just by touching
the screen or the capacitive buttons. The time after which the
screen no longer responds to a touch is set with NStools. [/quote]
[B]UV (Undervolt)[/B]
[quote]This refers to lowering the voltage to conserve power while
still achieving the same performance, assuming your settings
remain stable. Both SetCPU and NStools allow the user to change
voltages. Like overclocking, this is also a trial and error process,
because each phone is different. The benefits are low energy
consumption and less thermal output. [/quote]
Tools & Mods​
So you have a rooted phone. Maybe even a custom Kernel or ROM, whatever works for you. But you still want to be a tad different from the other guys using the same configuration as yours. So here's a small selection of mods and apps developed by members of the community, enough to get you started. Feel free to experiment, and remember: read before flashing, search before asking and you should be alright!
Mods for AOSP+ Rom
[BOOTANIMATION] Plain, Simple & Colorful + color variants
Nova Launcher
Flavours for stock OTA ICS 4.0.3
Search key to ICS recent apps [add CM9 version]
[NS][NS4G]FaceLock for ICS 4.0.3
Enable on-screen buttons in ICS roms
Click to expand...
Click to collapse
NOTES:
I am hoping this little survival guide is useful FOR BEGINNERS in understanding the basic terminology used here in the Nexus S sections. As the title suggests, it was made with beginners in mind, so I don’t want posts of so called “experts” saying how they already knew this.
IMPORTANT: I do NOT guarantee the explanations written here are completely accurate or complete, FOR NOW. I will keep working on this, correcting mistakes as I continue to read.
If you find something that you think is not correct, or consider something must be added, please post here, together with a link to a credible source.
All of this came from sources off the internet, so please bear with me. Also, sorry for any typing mistakes. If you see any, please be sure to signal them
If I have helped you in any way, or if you appreciate the work invested in this (now and for the future), press the THANKS button.
Thank you! (Hoping to see this stick) And many thanks to all the great devs working on ROMs and Kernels for us. Keep up the great work!
W O R K - I N - P R O G R E S S
(I will be sure to notify you when I believe this is complete)​
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
ljordan2 said:
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thank you! I'm just worried it is a little bit long... but in the next couple of days I will be making it more reader friendly
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
nice thread! thanks
Hey great post, i still haven't rooted my nexus s but you just made me flash a kernal. I was tkinking about it but never too serious.
thanks!
Love it!!! Cleared so much up (you recieved my first Thanks button click!)
Just wanted to clarify something about the Kernel. My Rom is stock 2.3.6 that was received OTA when I unboxed the phone (Nexus S GSM i9020A, I'm in Canada). The bootloader is unlocked, phone rooted with CWM recovery via one click (QBKing's Video). Am I able to flash a custom Kernel to a stock Rom? Reading the above seems to lean towards the "yes", but wanted to make sure first.
Also, do not use the one click method on the Nexus S GSM if you want to easily return to stock. The one click stock only supports the 4G, which is extremely silly and inconvenient IMO. I'm currently still trying to figure out how to return to stock, incase something does happen and the phone needs warranty work. Let's just say, I'm not making much progress and this is extremely uncomfortable ATM..
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Thanks so much for taking the time to do this
Sent from my Nexus S using XDA App
Harbb said:
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Click to expand...
Click to collapse
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
very useful for us newbie, thanks for sharing
heX79 said:
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
Click to expand...
Click to collapse
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
great post OP
Nice thread! Great Work ,Thanks
Hey thanks! Happy to see good feedback on this.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
Great beginners guide, and thanks for the link!
For kernel benchmarks and more, see here: http://goo.gl/mpeHI
Thanks very much! I will give it a try shortly, just to confirm if I recieve any issues. I've also installed the recommended CWM version for my model, not sure if it makes a difference, but I flashed 5.0.2.0 anyway as the version I was getting an error with had a higher build number.
Right now I'm enjoying AndroidME 1.2.3 with Speedy 6 kernel and have no complaints so far! (Kernel updated this morning from Speedy 5)
I will report back with any issues once I have some time to do a Nandroid backup and test the stock Rom.
Thanks for your help!
It's nice to know there's a way to revert back to stock, should anything need servicing! I've also started reading up on Odin
flodb113 said:
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
Click to expand...
Click to collapse
You're welcome! Looking forward to an update with your stock flashing situation. I also used ClockworkMod 5.0.2.0 a long time. I'm now on 5.0.2.3 only for the better menu layout.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
just one question...
can i install more than one kernel at a time...
for eg.like one i installed for battery usage and othr for sound..
can i do tht

[Q&A] Task650's AOKP (AT&T)(SGH-I337)

This thread has been created strictly for
Questions and Answers​
[SIZE=+2]Dealing with[/SIZE]​
AOKP JB/KitKat ​
{
"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"
}
[SIZE=+2]This thread has been created for people to share issues and question they may encounter while using this version of AOKP[/SIZE]​
[SIZE=+1]Please Do not clutter the Development thread with non related development chatter[/SIZE]​
PLEASE make sure to thank task650 for his dedication to this body of work​
Thanks to all the members of XDA and Task's threads, credit goes to everyone as I have just taken info from users input and located it to one place. Thanks to you all for helping us learn everyday
.
Please read the OP in dev thread carefully on latest update, it has some very important info in it.
​
BUG REPORTING: Very minimal at least read the thread from the date of the update you are running. If you see a couple posts about a paticular bug then consider it noted by devs. They do read these. Remember if they can't duplicate the problem then they sure as hell can't fix it. IF you are going to report a bug - include the necessary information or it will be ignored.
thanks for understanding that after a few bug reports are made and i acknowledge them, that the unecessary 100 that follow are ridiculous. Task
Always read the OP. If it says full wipe then do a full wipe. If you don't follow the OP please don't post problems. This isn't helping anyone. Full wipe isn't a big deal. You can backup and restore your launcher settings with Nova or Apex, Backup and restore apps with Titanium backup(pro has the batch feature and is worth the money) and you can backup and restore most of your AOKP settings with AOKP backup. ***AOKP BACKUP can cause issues when restoring. If you have errors after restoring with AOKP BACKUP try the process again without using it.*** Using these three methods takes about 10 minutes. This is barebones backup/restore. If you have a lot of tweaks and kernel changes it will take you longer. So as stated in the OP if you have problems do a full wipe before you report any problems.​
Read the change log. This will answer a multitude of questions.
This is for the AT&T version of the Galaxy S3. This rom may work on different variants of the phone, but as for now Task and Ktoon do not have the time to support other versions. If you are on a different version of the Galaxy S3 and report a bug please understand that this ROM is AT&T supported only.
This is just to help Task and Ktoon keep repetitive questions out of there thread. If any information in this post conflicts with Task and Ktoon's OP or ROM thread then ALWAYS follow their information first.
Below is am alphabetized list of FAQ, bugs, known issues and tips.
This is just a collection of answers that have been posted in the thread. Use as a guideline not as a rule of thumb. Always follow the OP.
Read this>>>>>>>http://forum.xda-developers.com/showpost.php?p=38843439&postcount=24316
Annoying (small issues) repeatedly posted about
AOKP BACKUP
App FCing, freezing or causing reboot or just not working properly
2g Toggle
Black screen/Phone locked up/Can't wake​
Battery life
Bug Reporting
BlueTooth
BenchMark Scores
Canadian LTE
Capacative Buttons
CM10
CRT animation
Data working
Data connection speed symbols
Error 7 in recovery
POST 2
External SD card
Facebook​
FAST CHARGE​
Faux Sound​
Flicker​
Full wipe per task/Weird ****.​
Gapps​
Google Now/Google​
GPS​
Home Screen/Home Button​
Inverted Gapps​
IRC channel for task - ##Task650_AOKP​
Kernel​
LED​
Links/External Links for ROM/Gapps​
LTE​
Modems​
OTA Update/Recovery​
OLD/OUTDATED versions of this ROM​
Performace settings​
Requests​
POST 3
Ribbons
Ringtone​
ROM control settings​
Rom Manager​
Screen shot​
Signal/WIFI colors​
SMS/MMS​
Sound/Volume​
Swag (Pink Hat)​
Themes​
Toggles​
Touchwiz​
Voicemail​
WiFI/Tether​
WIFI/Signal colors​
Useful links​
Annoying bugs/glitches reported
Bluetooth Connectivity issues
Allow device to disconnect then turn off bluetooth
Gapps has been changed - make sure you flash the newest in OP and update google search through play store.
msm_otg wakelock usually happens while rebooting and plugged into a power source - remove power source and reboot while on battery only should fix this.
Disable touch sounds to avoid sound weirdness while listening to music or on the phone.
Phone freezing/black screen-try raising your minimum speed or just revert to a rom before the new 3.4 kernel was implemented. Try the 3-13 build.
cLock weather not updating - Either yahoo API change or a weather station down.
AOKP BACKUP
AOKP BACKUP is a great app for restoring most of your settings, but may cause some issues.
Third party app not working properly
This ROM has nothing to to with 3rd party apps. You would need to contact the developer of those respective apps to get support for them. You also need to understand that not all apps support the Jellybean 4.2.x OS yet and need to be updated by the developers in order for them to work correctly. task650
Trying clearing data for that app
If you used TIBU to restore app, clear cache and data and delete the app and download it fresh from the Playstore.
Some people are reporting third party camera apps not working correctly and/or causing stock camera problems. This could be true for a number of third party apps that could be conflicting with system apps.
If any given app/process is giving you problems or fc'ing- try clearning data for that app and/or fixing permissions.
Make sure you have the app updated to latest version. The existing version may not be up to date for 4.2.X or whatever version the ROM is.
If your app won't sync or no notifications - try logging out and then back in. Or try deleting the account and add it back.
2g toggle
If you can't get your phone to wake up-
Hold down the power button for up to 30 seconds - it will restart. You should not have to pull the battery after using this step to restart. It does work and may take a few times for you to get it right.
BATTERY LIFE:
We all at some time have been proud or dissapointed in our battery life, but please keep battery stats out of the development thread.There are threads for this and the Development threads are not one of them.
There are way too many variables that influence battery life to be concerned with in a DEVELOPMENT thread. This has been stated daily by the Developers.
Install betterbatterystats and figure out if the problem could be something causing a wake lock keeping your phone from entering deep sleep.
Go here to discuss BBS wakelocks and read the how to in the app. It is very beneficial.
It is a known fact that it may take a couple charge cycles for your battery to calibrate and settle in. Also it should be known that these batteries do not need the data cleared for them. THEY WILL CALIBRATE THEMSELVES.
If you are getting over 3 hours of on screen time on a single charge that is nothing to complain about. IF you do see a post in the development thread about battery life, ignore it. Once again, no one uses their phone the same and their set up is probably not going to influence your phone significantly.
Sometimes an app or process is just sticking and a reboot will help.
You could possibly see battery showing charging when not plugged in or a dramatic change after a reboot. Once again this is just the battery fuel gauge recalibrating itself. This is normal.
http://forum.xda-developers.com/showpost.php?p=20972167&postcount=3
For some good tips on fixing battery drain go HERE.
Bugs/reporting
Bug reports should contain a logcat or information that would help. saying this doesn't work or this is happening doesn't help us at all and at that point belongs in Q&A. task 650
Some bugs are being reported by a few that Task, Ktoon and others are not seeing. Follow avidmovies notes below on trouble shooting/comprehensive reflash and Task's suggestion above on weird sh!t. Stick to the basics and see if problem is there still - such as stay with kernel that is included with rom, skip restoring anything with titanium back up, other words just try the basics and if a certain app has been giving you problems download it from the market instead of TIBU and see if problem still persists. Some apps have been reported to make ROM features malfunction.
If you had a spontanious reboot, we need the file last_kmsg from the /proc folder.
If you have n FC on an app, thats when we want a logcat
Guide on how to logcat. http://forum.xda-developers.com/showthread.php?t=1726238
All In One Android Logger > AIOlog
Catlog - https://play.google.com/store/apps/detailsid=com.nolanlawson.logcat&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5ub2xhbmxhd3Nvbi5sb2djYXQiXQ..
If you do not have the latest update of this rom consider it unsupported. This is why they update- to get rid of the bugs that we may be having on older versions.
BUG REPORTING: Very minimal at least read the thread from the date of the update you are running. If you see a couple posts about a paticular bug then consider it noted by Task. He does read these. Remember if he can't duplicate the problem then they sure as hell can't fix it. Bug reports without a logcat or a random reboots without a last_kmsg will be ignored.
"Thanks for understanding that after a few bug reports are made and I acknowledge them, that the unecessary 100 that follow are ridiculous." Task
Just follow this practice and you will be golden.
If you see a bug reported once - go ahead and report it again with a LOGCAT or proper info.
If you see a bug reported twice and you are seeing it consider it a known bug and the following will probably happen-
Task has the same problem or enough info from LOGCATS provided and will fix it or
Task is not having the problem and can do nothing about it unless a LOGCAT is given
Point here is Task can't fix problems with out the proper information.
"Be patient for the galaxy s3 settings to be fixed." Task --- Some stuff is taken out, left out or temporarily removed for good reason.
If you are going to report a problem, include some details. Kernel, UC/OC, circumstances, etc...
Once again TALKING about a bug without the proper info including either LOGCAT or last_kmsg is nothing but A WASTE OF TIME.
Read THIS posted in the development thread by Task.
HOW_TO_PROPERLY_REPORT_A_BUG
BLUETOOTH
If your phone switches to vibrate when you connect to bluetooth. Check here
Settings>Rom Control > Bluetooth A2DP connected action
No action
Vibrate Mode
Silent Mode
Benchmark Scores
The devs have stated many times that these scores are BS. If you run a benchmark and want to discuss it, there are threads that are purely for discussing these random numbers. The development thread is not one of them.
CAPACITIVE BUTTONS
For instructions to disable capacitive buttons go HERE!
CM10
This is not a CM10 ROM nor is it based off one.
Comparing the two makes no sense. This is based off Google as is CM10. Other than that there is NO comparison. Please understand this. If something works or is in one rom doesn't mean it will work or is in the other.
If you want to compare CM10 and Tasks AOKP take it to the general section. A development thread is not the place for it.
CRT animation
If you put your animation speeds below .75 CRT will not work.
There are now toggles and more options for CRT - familiarize yourself with them.
DATA CONNECTION/SPEED
If you have no data after a flash, dont freak out.
Try rebooting
Make sure you have data toggle turned on.
Try toggling airplane mode
Check APNs.
If you have no APN's make sure your SIM card is in good and reboot.
If SIM card is not detected during a reboot - your APN'S will/could be blank.
DO you have your IMEI intact?
DATA SPEED PROBLEMS
Data speed can vary greatly depending on user traffic and distance from towers.
SpeedTest app is not a reliable source of accurate data speed
The ATT APN is being phased out by ATT. You need to use the ATT LTE APN - task650
Just because your stock ROM said 4G doesn't mean you actually had 4G/LTE. ATT roms report H/H+ as 4G where as this ROM gives you true data connection.
DATA Symbols
I flicker between H and 3g. AOKP shows true connection where as stock roms just show 4G. Also this rom controls data connection and kicks it down to 3G when not using data and kicks to H+ when you need it. This is a feature to save battery.
Blue symbols means you are connected to google servers - gray means you are not
Symbol equals>
G=GPRS
E=EDGE
3G=3G
H=HSDPA/HSPA
H+=HSDPA+/HSPA+
4G=LTE
You must have I337 recovery to flash this ROM or you will get error 7. task650
This is usually caused by a corrupt download, or bad file signature. Re-downloading (or re-signing) the ZIP will usually fix this - check MD5 sum.
Update or try a different recovery.
Remove the build assert in the updater-script.
Below is am alphabetized list of FAQ, bugs, known issues and tips.
This is just a collection of answers that have been posted in the thread. Use as a guideline not as a rule of thumb. Always follow the OP.
External SD card
Facebook​
FAST CHARGE​
Faux Sound​
Flicker​
Full wipe per task/Weird ****.​
Gapps​
Google Now/Google​
GPS​
Home Screen/Home Button​
Inverted Gapps​
IRC channel for task - ##Task650_AOKP​
Kernel​
LED​
Links/external links for ROM/gapps​
LTE​
MD5 sum​
Modems​
OTA Update/Recovery​
OLD/OUTDATED versions of this ROM​
Performace settings​
REQUESTs​
​
SD CARD
there is a known issue with apps being unable to write to the external card. Symptoms: you may be able to copy files to the external card or create folders using a file explorer, but apps (TiBu, Dolphin browser, camera, others can't use the external card as a save location, and you can't change properties or delete files/folders. You can still read files (i.e. restore existing backups from TiBu, play music) without problems. This is an issue with the JB build and they're working on fixing it. This does NOT affect CWM - you can still nandroid to the external card alacrify
Here is a guide for formatting external SD card without reader are here.
Guide_to_format_external_SD_card_without_reader.
Here is another way to format SD card http://www.online-tech-tips.com/comp...ive-to-fat-32/
My SD card is not working. Try this. EaseUS
Will my 64 gb sd card work? Except it works fine with a 64GB card. http://rootzwiki.com/topic/28124-doe...card-standard/ The SGSIII is the first phone to support exfatl, but the support is Kernel based, some people are having trouble with the replacement kernels and exfat support. The solution is to force it to format in FAT32. http://www.online-tech-tips.com/comp...ive-to-fat-32/ I know, because I've done it. --- Don't respond without actually doing research. I have no problem spoon feeding information, especially when the information you put out there can increase misinformation. The SGSII also supports a 64GB card as well. http://androidforums.com/samsung-gal...ing-sgsii.html
http://teamw.in/exFat
Facebook won't sync. Try Friendcaster or facebook_contact_sync.
FAST CHARGE
Storage options will not work with fast charge on.
FAUX SOUND
Faux_sound_in_Playstore
Task has added patches to be able to use this. It is worth the money.
Disable HW to stop flickering
Disable HW tick will not stick after reboot. This is the way it is suppose to be. This will still help with any type of flickering, usually.
If you are having some weird sh!t going on.
Redownload rom and gapps
Wipe data factory reset
Wipe dalvik and cache
In mounts and storage select Format System
Then flash rom and gapps
Reboot task650
Gapps
You must flash Gapps AFTER every flash of the ROM.
Use the Gapps in Task's OP or don't bring any problems caused from other gapps to his ROM thread.
Sometimes you may have to flash Gapps twice - they have been notorious for not taking the first time.
Read the OP to see if a new version of gapps is required.
Google now
Phone language has to be set to english for google now to work.
My google apps are working correctly. If it was just the play store force closing all you would've needed to do is reflash gapps. gapps is notorious for not taking the first try. but you always have to flash gapps after a rom install and make sure to clear cache and dalvik. no issues should occur if those steps are taken. Task. Make sure you are using the correct gapps!
Task and Ktoon do not support google wallet. There are fixes available but don't ask Task or Ktoon to fix it.
You can't remove the google search bar with default launcher but you can with nova or apex.
GPS
GPS not working correctly isn't always the ROMS fault. Sometimes its the satellites.
Make sure you have internel GPS selected.
Try flashing original stock and then come back to this rom if you have flashed a TW based rom.
To change your number of home screens
You must use Apex or Nova launcher, possibly some other third party launcher. But the default launcher will not allow you to do this.
You must use Nova or a third paryt home screen to disable search bar.
If you flash other things like inverted gapps or change things from the original packaging of this rom and something goes wrong or doesnt work. Think about it. We cannot support those issues here. This thread is for this rom and gapps that are posted in the OP. Thanks. task650
Inverted gapps are awesome but not supported in Tasks thread.
If you are using inverted gapps and having problems - full wipe and reinstall rom and gapps in the OP and see if problem still persists.
Go here for support of inverted gapps. > http://forum.xda-developers.com/showthread.php?t=2138156
IRC
Task has started and IRC channel for his rom. ##Task650_AOKP
KERNEL:
If you are using any kernel other than the one packaged with this ROM please post questions and problems to the appropiate kernel thread.
you need to understand that all devices are NOT created equally. one kernel might work awesome on my device while at the same time it may work horrible on your device. so to say that Ktoonsez says it works awesome, that means it works awesome for him. It has nothing to do with how it will work for you. If the symptoms that you're talking about are happening with that kernel it's obvious that your device doesn't like that kernel. Easy fix. Use a different one.
If you are using Ktoon's awesome kernel and experiencing problems, try reflashing with the kernel included with this ROM and see if the problem still persists. This may help understanding if the problem is kernel or ROM related and will help benefit development of both.You can full wipe and reflash rom and gapps to be back on original kernel.
If you wish to run another kernel other than what comes with the rom, Task suggest loading rom with included kernel, set up phone, then flash the kernel you want.
Governor/IO scheduler
Change these in performace control in settings
If you do not tick set on boot they will revert upon reboot.
This is a safety check in so you can try settings out before you make them permanent.
Last report in Feb is that Task uses row and interactive as his settings.
LED
LED charging works exactly as it should.
0%-%10 = Red
%10-%90 = Yellow
%90-100 = Green
You can't change the colors for LED Charging unless you download the source and rewrite that portion of code.
You can only change the colors for the Notification LEDs not battery indication color.
Make sure you have "pulse notification light" checked - uncheck to turn LED notification off.
Some colors will not work. Test LED color before relying on it.
Go here for some LED color talk. http://forum.xda-developers.com/showthread.php?t=1890774
DO NOT USE LIGHTFLOW WITH THIS PHONE - DOESN'T WORK WELL. LED CONTROL WORKS FINE ON ITS OWN.
To set LED for miss phones calls>>
choose Activities>Contacts>Phone/ activities.CallLogActivities
Please do not post links for Task's ROM or gapps. He wants to keep count of downloads. Thanks.
If you don't have LTE in your area it's not draining your battery.
AT&T is phasing out the old non LTE apn either way so we will all be using the same "LTE" apn. Network mode has nothing to do with you if your on AT&T service. That's only for the Canadians.
Also see 14 and 15 in FAQ post 1.
MD5 sum is located in goo.im via download link.
MODEMS
This ROM does not include a modem. You will have whatever you had.
Modems are location based. Try this and see which one works best for you.
Any modem questions should go HERE.
OTA Updates
OTA updater is a convienence. If you have problems using the OTA update just flash manually through CWM or TWRP.
CWM 5.5.0.4
cwm flashable
http://www.mediafire.com/?8rs5rq2a0ldhgut
TWRP X.X.X.X
http://forum.xda-developers.com/showthread.php?t=1793224
Read this >>>> http://teamw.in/androidmultiuser
Old/out dated versions
Go here> http://goo.im/ to get old/outdated versions of this ROM.
See Kernel for performace control
Task has added a slight OC/UC feature.
Use VOLTAGE_CONTROL for stable reliable control of these features
Task has stated this many times that it is what he uses.
Last report in Feb is that Task uses row and interactive as his settings.
REQUESTS AND ETA'S:
Do not ask for requests, ETA's, features or changes.
Donations are for if you appreciate his work. He will not turn this into a job.
DO NOT ASK FOR ETA'S. THIS IS ANNOYING AND ONLY HINDERS DEVELOPMENT.
Ribbons
Ringtone​
ROM control settings​
Rom Manager​
Screen shot​
Signal/WIFI colors​
SMS/MMS​
Sound/Volume​
Swag (Pink Hat)​
Themes​
Toggles​
Touchwiz​
Voicemail​
WiFI/Tether​
WIFI/signal colors​
Useful links​
RIBBONS
If you can't delete the icons in ribbons just use the menu and reset them.
Ringtones​
There is not a repeating ringtone on this rom(AOKP). Get a longer ringtone if you want more notification.
More RomControl Settings added
It will take some time to get all the rom control settings back in, be patient.
If you see a major update as in a new kernel, some items will take some time to be added back.
ROM CONTROL: This is a very customizable rom, please spend some time and learn the many features it has.
ROM MANAGER APP
It is advised not to use ROM MANAGER APP. Notorious for causing problems.
SCREEN SHOT
To take a screen shot hold volume down and power button at the same time.
You can add screenshot option to the power menu.
Changing the color of Signal and wifi only changes the color in text mode.
SMS/MMS
MMS not downloading
Some suggestions offered that have helped people with MMS.
Add "hipri" in your APN type and save. This has been reported by several people to help.
This is being seen on several phones with different roms and even iphones. Call ATT.
Try auto retrieve on.
Set Authentication type to "none"
In text client make sure "auto retrieve" is checked in all boxes.
This ROM does not having a problems sending MMS. It is most likely an ATT problem. But you can double check your APN to make sure it is not on your end.
If you are using a third party app to SMS/MMS it is not supported by Task.
If you want to use the quick reply option make sure you have it checked in settings.
SOUND/VOLUME
If you are not getting sounds on something check your quite hours.
Make sure you have not accidentally toggled silent/vibrate.
Take a look at THIS in the play store. It's awesome.
Swag Pink hat - It's a joke. Either you have it or you don't. As cool as Task makes this phone he can't actually help you in this area.
Themes
If you are having graphical glitches and using a theme, try removing any theme and see if it still persists.
CM10 themes should work on this rom but if you encounter problems do not bring it to the thread.
Go HERE for themes.
Toggles
Are located in ROM control
The toggle for DATA is called SIGNAL
TOUCHWIZ FEATURES:
This is an AOSP rom, touchwiz(sammy) features are not incorporated into this rom. Reason you ask? Framework!!!
Chances are something you want from TW is probably in the app store.
Voicemail number missing. Use your call forwarding number.
Try this for ATT visual voicemail.http://forum.xda-developers.com/showthread.php?t=1641981
If your wifi won't stay on while phone goes to sleep check settings to keep on during sleep.
If your phone sometimes drops wifi check settings and uncheck avoid poor connections.
These are found under advanced settings in WIFI.
If you are having problems connecting or using tethering try changing your SSID and try unsecured.
Most of the time lack of WIFI connectivity is usually cause by router settings or router itself.
ROGERS WIFI TETHER
Tether will not work on 4G/LTE unless you use a third party app.
Task can not test/fix since he obviously doesn't have a rogers phone.
Changing the color of WIFI/signal colors only changes the color in text mode.
Useful LINKS
BETTER_BATTERY_STATS]
AOKP_LED_COLORS
FIXING_BATTERY_DRAIN_ON_YOUR_S3
Titanium_Backup_User_Guide
Guide_and_Q&A_AOSP_LTE_ ​How to Update (Always follow OP directions)
Make sure you have CWM and/or TWRP Recovery
MAKE A NANDROID
Boot into recovery
Wipe data/factory reset, wipe cache, and wipe dalvik cache, then go into mounts & storage and format system!!!
(If already on AOKP JB/CM10 you should be able to just wipe cache & dalvik. If you have ANY ISSUES, FULLY WIPE BEFORE POSTING IN THIS_THREAD!!!)
Flash ROM
Flash Gapps
Reboot
Troubleshooting/Comprehensive Re-flash
(Optional, but recommended) Back up any apps you may want restored (Titanium Backup's batch mode (a PROfeature) makes this painless! Set TB batch filters to User type only. DO NOT RESTORE SYSTEM DATA! Hell, don't even back them up.
Re-download the latest version of the ROM and Google Apps (even if it's the same version you have) from the OP. It's possible you may have a corrupted download.
Reboot into recovery. Follow the process below exactly, and there should be no NEED for a kernel cleaning script.
Wipe cache partition
Advanced > Wipe Dalvik Cache
(Optional, but recommended) Mounts and Storage > mount /system & /data
Install zip from sdcard > choose zip from sdcard (wherever you saved the download) > Flash [ROM] AOKP Task & Ktoonsez Run a Train (version)(TGFY ONLINE!!!).zip
(Optional, but recommended) Mounts and Storage > mount /system & /data
Install zip from sdcard > choose zip from sdcard (wherever you saved the download) > Flash gapps-jb-(version)-signed.zip Jelly bean version only
Reboot
PS. Sometimes all that is needed is a reboot again. Doesn't hurt to try it.
Test ROM, BEFORE restoring *any data* (if you did a full reset). DON'T RESTORE SYSTEM DATA! You have been told twice!
Fixing permissions in CWM/TWRP helps fix MANY *random* glitches.
If you still encounter problems, do a FULL reset ( Recovery > Wipe data/factory reset) & follow the steps again. THEN, you can report issues!
You may have to redownload ROM and/or Gapps. Sometimes you can get a corrupt download that will cause issues. It happens.
Thanks to avidmovies for the above instructions from S II AOKP FAQ. (with small modifications)
Just in case i need more room....
Another just in case....
Pretty much everything is working great on this rom. Very fast and smooth and I like it a lot. I had one "issue" in that the google play store wont let me install Dungeon Hunter 4. It says it is not compatible with my device. I have tried resetting the pixel density and clearing the google play store cache, but that did not seem to fix it. Would anybody be able to check to see if it is available to download on the latest release? I already set everything up and was hoping to not have to wipe.
I'm having an issue with the volume of music I play in Google Play Music using AOKP and Underwear kernel.
Occasionally when listening to music, the volume will decrease somewhat, such as when an alert is going off. The problem is the volume will remain decreased when the event ends. The only way to get the volume to return to normal is to stop playback, kill the app, then start the music again.
I've tried wiping and reinstalling the recent release but the problem persists. I'm not sure if this is a problem with Google Play Music, or the Faux sound built into the kernel.
My status bar seems to have shrunk or shifted a bit since the update. The battery with center text has been shifted off. Any others seeing this? I feel I may have to wipe :/
Sent from my SGH-I337 using Tapatalk 4 Beta
fastblack said:
Pretty much everything is working great on this rom. Very fast and smooth and I like it a lot. I had one "issue" in that the google play store wont let me install Dungeon Hunter 4. It says it is not compatible with my device. I have tried resetting the pixel density and clearing the google play store cache, but that did not seem to fix it. Would anybody be able to check to see if it is available to download on the latest release? I already set everything up and was hoping to not have to wipe.
Click to expand...
Click to collapse
I'm still running stock, but rooted. Dungeon Hunter 4 also not compatible here.
vintagepimpage said:
I'm still running stock, but rooted. Dungeon Hunter 4 also not compatible here.
Click to expand...
Click to collapse
That's weird. I was running stock before and had it installed.
Sent from my SGH-I337 using xda app-developers app
spectrumfox said:
I'm having an issue with the volume of music I play in Google Play Music using AOKP and Underwear kernel.
Occasionally when listening to music, the volume will decrease somewhat, such as when an alert is going off. The problem is the volume will remain decreased when the event ends. The only way to get the volume to return to normal is to stop playback, kill the app, then start the music again.
I've tried wiping and reinstalling the recent release but the problem persists. I'm not sure if this is a problem with Google Play Music, or the Faux sound built into the kernel.
Click to expand...
Click to collapse
I have the same problem. It's not limited to Google Play Music as it happens when using Sound Cloud as well. I haven't looked around much to fix it as it doesn't bother me much...
Dyaus said:
I have the same problem. It's not limited to Google Play Music as it happens when using Sound Cloud as well. I haven't looked around much to fix it as it doesn't bother me much...
Click to expand...
Click to collapse
I have a strong feeling that Task's ROM is responsible for it, but I don't have much of a chance convincing him of it.
spectrumfox said:
I have a strong feeling that Task's ROM is responsible for it, but I don't have much of a chance convincing him of it.
Click to expand...
Click to collapse
If there's an issue, and you submit a logcat, and if it's a problem he can fix, he will. If it's a third party app that doesn't play well, he STILL might fix it because he does that. Have you done anything to troubleshoot and provided the information needed for him to look at it?
spectrumfox said:
I have a strong feeling that Task's ROM is responsible for it, but I don't have much of a chance convincing him of it.
Click to expand...
Click to collapse
I've had the issue since the first release of Task's ROM and I haven't tried any other ROM. I'm not too inclined to try out other ROMs to see if it's a ROM issue as the ROI is pretty low for me... But you should try out another ROM and report back.
So I realize in the OP it mentions TW features not working because of the framework. Does this include the camera? Is that a no go? I couldn't copy the camera.apk over and have it work? I've become a fan of the drama mode feature of the camera. Perhaps there is a camera app on the Play store that offers similar functionality? Either way I'm leaving the awfulness that is TW, but having the camera as part of an AOSP ROM would be a nice perk.
Audio Issue logcat
Here's a logcat grab from when the audio issue occurs. This is only the relevant portion of the logcat. The fillbuffer messages are generated during streaming of music so those can be ignored.
Battery with center text is still not aligned correctly after wipe
Sent from my SGH-I337 using xda premium
spectrumfox said:
I have a strong feeling that Task's ROM is responsible for it, but I don't have much of a chance convincing him of it.
Click to expand...
Click to collapse
Please stay on topic which is this ROM. Your personal opinions do not belong here. This is all open source. If you don't like something you are more than welcome to dig into the code and change whatever you like. I'm not a magician. I can't fix something without info.
pejhod said:
Battery with center text is still not aligned correctly after wipe
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
Yep. Its because of the status bar commit that was recently made. Its a work in progress.
spectrumfox said:
I have done all that for previous issues that I've encountered while using his ROM that he immediately shut down and started to blame on other apps I had installed on my phone. Honestly, his overall attitude and aire of superiority turn me off in doing real legwork to help him out with his ROM. Why should I make the extra effort to help point out an issue to him if he's just going to make excuses?.
Click to expand...
Click to collapse
From here on out I'm asking you to stop posting in my threads. You are the exact type of user that has no place in a development and/or support thread. You contribute absolutely nothing and all you seem to want to do is place your expectations of what you think I should or shouldn't do. Its not my job to fix everything for you dude. Its also up to you as the user to do you part. I gave you suggestioms of what needed to be done on your end and you seemed to refuse like you knew what that problem was from the beginning. Your personal opinions do not matter to me and I hope it shows. I'm not here to impress, do work for, or hold your hand through these things. If you don't want to contribute, don't. But don't post in any of my threads. Thanks.

[Q&A] [ROM][CM12][5.0][Lollerpop][KANG] Grouper nightly kangs

Q&A for [ROM][CM12][5.0][Lollerpop][KANG] Grouper nightly kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM12][5.0][Lollerpop][KANG] Grouper nightly kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will not flash
I keep trying to flash this rom and all I get in TWRP is Error executing updater binary. I was able to flash other 5.0 AOSP roms but I am having trouble with this one.
BSZAospLP v1.1 flashed fine as well as an older build of your rom. The last 2 builds will not flash at all. Same error. TWRP and MultiROM are updated to current versions.
My rom shows a camera installed when I go to manage apps, but it doesn't show in the app drawer and I can't access it. Stock launcher no hidden apps or anything
dcwiker05 said:
My rom shows a camera installed when I go to manage apps, but it doesn't show in the app drawer and I can't access it. Stock launcher no hidden apps or anything
Click to expand...
Click to collapse
For me this issue existed already on KitKat. I think the camera app is kinda hidden because the N7 camera isn't designed to take pictures. But some launchers allow you to create an activity shortcut to the respective activity of the camera app to launch it. This works fine for me with action launcher.
First off, I do know that this is a work in progress, and so far, it has been an excellent release. But, I want to know if anyone else is noticing the following issue below or if it could just be my device.
Has anyone noticed if their keyboard response is slow within games, such as Game of War? I'm noticing severe lagging in the keyboard when I'm attempting to chat, send email or do searches. Anything that requires keyboard entry is slow.
I've noticed this as well in other games. I also am running CM12 on my Droid RAZR HD (XT926) and keyboard response is fine. It only seems to be with this build on my Nexus 7 (2012) WiFi, so I can't tell if it's just because Grouper Nexus 7 is just not up to the task of running this, or if it's just the ROM is still early.
I've tried both the stock keyboard that comes in CM12 as well as my default that I use, Swiftkey. Again, on my phone (XT926), Swiftkey works great in the games.
Outside of games on my Nexus, the keyboards work fine. It's only within games that I see the severe lagging. And by severe lagging, I mean that I will select into the input box to start typing and then the keyboard may not show up for 15 seconds. One time, it took over 30 seconds. And then, once the input box has focus, typing on the keyboard appears to do nothing and then maybe another 15 to 30 seconds later, it starts to show up, one type at a time, with seconds of lag between types. Sometimes, it eventually clears up for a bit, but if I start to type longer, it can then start to lag again like before.
Just curious if anyone else has noticed this. I've done a clean wipe. I'm running 11/28 build with f2fs on the data partition, and I'm running it with the MKernel-a72 kernel.
Thanks!
UPDATE:
Okay, downloaded the 12/01 image and the keyboard issues appear to have been taken care of.
for me too the 20141205 build is not booting
it is checked. I am trying
pie control
How far are we from setting pie control, either slim pie or paranoid pie. In a lolipop release? This is the most important feature for me.
jasius said:
How far are we from setting pie control, either slim pie or paranoid pie. In a lolipop release? This is the most important feature for me.
Click to expand...
Click to collapse
I think CM discarded Pie control, they didn't include it in CM11. I put my hopes in SlimLP, since Slimkat had a decent Pie implementation.
Problems
Hi,
thanks for the ROM. I have a few questions, problems for which I would like to ask for help:
data and cache partitions are mounted without the discard options. Is this normal? Can this be added?
GPS is not working: E. g. the GPS status app (or Google Maps) does not see a single satellite.
I cannot copy files from the Windows Explorer or by adb push to the (emulated) sdcard/internal memory: error message of adb: failed to copy 'xxx' to '/storage/emulated/0/xxx': Read-only file system
Thank you for your help
Ok answering myself: With the latest build (141222) (part ?) of the GPS problem and the copy problem have gone:
The GPS status app can now find the satellites. Also in one map app (OruxMaps) the location is shown. Unfortunately, it still does not work with google maps.
For whatever reason it is now possible to copy files and directories with the Windows Explorer to the "internal memory". But not with adb push?!?
jmozmoz said:
Hi,
thanks for the ROM. I have a few questions, problems for which I would like to ask for help:
data and cache partitions are mounted without the discard options. Is this normal? Can this be added?
GPS is not working: E. g. the GPS status app (or Google Maps) does not see a single satellite.
I cannot copy files from the Windows Explorer or by adb push to the (emulated) sdcard/internal memory: error message of adb: failed to copy 'xxx' to '/storage/emulated/0/xxx': Read-only file system
Thank you for your help
Click to expand...
Click to collapse
Is mtp not working on the latest build as of yesterday?
It's not showing up under Device Manager at all so I can't browse for drivers. I've tried disabling and reenabling debugging but I get nothing. When I go to Storage and try to select USB Computer Connection, I get no options or drop down.
It does charge however.
Black screen upon boot
I just flashed the latest nightly after converting it to F2FS using the Windows tool. I also did a full wipe and manually checked to make sure system, data and cache were in f2fs. The ROM boots and 'optimises' apps just fine but then I just get a backlit black screen, only the power button works.
What might be my mistake?

[ROM][AOSP][SM-T705] Android 7.1.2 NZH54D (2017-09-12)

AOSP - Android Nougat - 7.1.2 - NZH54D
​This is a pure build of AOSP Android 7.1 Nougat, the goal is to have a pure AOSP rom for Samsung T705, so it is not the objective of this project to include any functionality that is not native to Android AOSP.
Download:
ROM: Mega, AndroidFileHost
Modem(OJ1): Mega, AndroidFileHost
Gapps:
OpenGapps: http://opengapps.org/
Choose ARM platform
Root:
SuperSU: http://www.supersu.com/download
Credits:
Kernel is based on LineageOS's Exynos5420 kernel, device tree is based on @Schischu, @deadman96385 and his Exynos5420 team's marvelous works.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
Code:
2017-09-12
  - Latest AOSP (NZH54D) Android 7.1.2_r33
  - Screen rotating glitches fixed
  - New Bluetooth HAL, distortion fixed
  - Rework RIL, more stable phone calling and receiving
  - IR blaster fixed with new IR HAL
  - This might well be the last Nougat release, I will work on Oreo from now on
2017-06-19
  - Latest AOSP (NJH47B) Android 7.1.2_r17
  - Some kernel tweaks
2017-06-14
  - AOSP (N2G47O) Android 7.1.2_r8
  - Kernel 3.4.113
  - Baseband version OJ1 (see download link above for modem file)
  - Fingerprint disabled, everything else work, [B]including mobile data[/B]
Flashing instructions:
Flash TWRP 3.0.2 or higher
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Go into install menu
Select and flash rom file aosp-XXX.zip
Select and flash SM-T705_OJ1_MODEM.zip if needed. You might need to change the file name to modem.zip
Wipe cache/dalvik cache and reboot to system. Due to some bugs, we can't flash opengapps alone with this rom
After the successful first boot, boot back into recovery and flash gapps and supersu.
Reboot to system
Contributors:
@scubajeff
Source Code: https://github.com/scubajeff/
ROM OS Version: 7.1.2 Nougat NZH54D
ROM Kernel: Linux 3.4.113
Based On: AOSP
Status: Stable
Created: 2017-06-14
Last Updated: 2017-09-12
Reserved.
UI Screenshot please
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
maz izaackovich said:
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
Click to expand...
Click to collapse
Of course I will maintain this build and I'm planing for a Android O update in the near future.
scubajeff said:
Of course I will maintain this build and I'm planing for a Android O update in the near future.
Click to expand...
Click to collapse
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Ssanmai man said:
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Click to expand...
Click to collapse
Distortion happen on your side or the other side can't hear your voice clear enough?
Sent from my Samsung SM-T705 using XDA Labs
maz izaackovich said:
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Click to expand...
Click to collapse
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
scubajeff said:
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
maz izaackovich said:
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
Click to expand...
Click to collapse
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
scubajeff said:
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
Yeessss.. Thats right.. Sorry for my bad english
maz izaackovich said:
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
Click to expand...
Click to collapse
I can reproduct this one, seems to me it's an long overdue bug of Google's implementation of MTP, related to media rescan. It happened under many circumstances, see this bug report --> https://issuetracker.google.com/issues/37071807
Sadly, Google refuse to acknowledge it as a bug.
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
ypmud said:
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
Click to expand...
Click to collapse
I ever had that issue, when i unisntalled google stock contact "Contacts.apk and ContactsProvider.apk" to replace with "zenui dialer and contact"
I guessed your issue it's related with, that your stock contact isnt installed properly
Try to flash these two .apks (Contacts.apk and ContactsProvider.apk) taken from your rom thru trwp or cwm recovery . It's solved my problem.
is there a way i can disable both phone and contacts ?
I am not on a rooted device
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
ypmud said:
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
Click to expand...
Click to collapse
Yes, if you are coming from other ROM, it's really, truly, absolutely important to WIPE ALL before flashing.
scubajeff said:
Distortion happen on your side or the other side can't hear your voice clear enough?
Click to expand...
Click to collapse
First, I confirm that my side distorted.
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
simonjonnemeth said:
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
Click to expand...
Click to collapse
I have to admitted that I didn't test the IR at all. Will give it a run asap. Sorry.
Sent from my Samsung SM-T705 using XDA Labs
I can now say I can only just make a phone call with this ROM. It's echoey and almost unmanageable when it does work, but it doesn't always work (no sound, normally causes the phone to lock up and force reset upon hanging up). I really want a non-stock ROM that works, preferably Android Nougat 7.1.2 but everyone seems to get the half finished, get fed up and leave us in the dark, and then finally after 6 months mark it as discontinued (cough cough LiquidDeath). I hope you don't do that because this ROM is promising.
Edit: The locking up may have been my fault for overclocking too high.

Categories

Resources