Database Info

[TIPS & TRICKS] Common ICS problems

Common ICS Problems
If you plug in USB while your tablet is asleep you will have a SOD​
Installation Problems
Install tips from tlb1961 here and lyricalpapa in post #3
Try not to use any backup's as they cause many problems.
Make sure your using CWM 5.5.0.4 Beta 15 (comes with the nvflash in TeamDRH ICS thread)
On your first boot let it sit for 30-60min (the longer, the better) and then reset.
If all else fails try this
Th3DmaN's G-Tablet Tools for anyone who is having trouble connecting and flashing their G-Table
Speed Problems
Different launchers such as Apex or Nova or any compatible launcher may or may not increase smoothness. There is no problem with installing them on top of the stock launcher as only one launcher runs at a time.
Battery and Power Problems
Your tablet went to sleep and wont wake up, try pushing the power button a couple of times and wait 5 seconds inbetween presses.
Your tablet has completely frozen, try pushing the power button for 30+ seconds. If that doesn't do it, you can leave your tablet alone for a couple hours and try again (may or may not work) or you can wait till the battery dies or if your impatient you can open the tablet up and press the internal reset, it looks like this. Here are some helpful pictures and a video for opening it up. If you have no reset button you will need to disconnect the battery, here's what it looks like. If you do get a SOD do this to help the developers.
Connection & Browser Problems
WiFi not working, try to "forget" the WiFi and re-enter your password. Also can try resetting your router or changing the security. Some say ICS does not like high channels.
If your having market errors, try force closing and clearing the cache in settings\apps\all. If that doesn't work then find every market reference and force close then clear the cache and reset.
Your computer doesn't recognize your tablet, you will need MTP drivers read the ICS rom page again. For Windows XP you need to disable debugging. For linux try Th3DmaN's guide.
Adhoc does not work with this build.
Stock browser seems to lock up after a bit. Possible fix is to disable java. Thanks plastikman
Screen and Sound Problems
1080p on H/W? Use Handbrake and import this profile. Here's the high profile settings for 720p, for those wanting the best quality.
Videoplayers such as MxVideo player, can play H/W video but the sound will need to be changed to S/W.
Icons and text too small? Try using this guide. CAUTION Changing the DPI really messes with the Market.
DSP Manager has been causing slowness/audio problems. Try stopping it to see if that's the problem. You can delete it safely if causing problems.
Game and Apps Problems
Alot of games and apps are not updated for ICS yet so they won't work correctly.
Hulu flash hack here. It should work. Anyone with Hulu can you post your results.MAY NOT WORK ANYMORE
Bypassing Exchange Security Policy try this
Connecting the ICS Mail app to Microsoft's Cloud hosted Exchange services check here
Gamepad support - follow jazzruby's guide here
Miscellaneous Problems
Errors popping up constantly, you need to reinstall again and make sure this time you erase everything.
Nandroid backups, you need to follow this guide
Important Notes
The SOD (sleep of death) we talk about is when the device goes into a sleep mode and there is absolutely no other way out but by pressing the internal reset. This is also called a kernel panic.
We are always talking about roms on Bootloader 1.2 unless specified.
When installing or removing things from the system, it is always a good idea to reset and clean the cache, clean the dalvik cache and fix permissions.
USB problems sometimes are caused by your own computer, you may have to restart/change USB port/change USB cables/check your USB drivers
Windows 7 is the implied OS most are working on, if you have different then ask.
IF I'M MISSING SOMETHING PLEASE LET ME KNOW

Stuff that WILL cause a SOD (sleep of death) causing you to push the internal reset
DON'T DO THESE
If you plug in USB while your tablet is asleep you will have a SOD
If you do get a SOD please do this so the developers can help.
Use the reset button
Don't power the tablet off at all, just use the internal reset button
Don't touch the tab or do anything but logging into adb.
If for some reason you can't open adb, you can use terminal on the rom
At the prompt type:
Code:
su
Hit enter and then
Code:
cat /proc/last_kmsg
If this doesn't work, the easier way is to access it is with a root explorer by going to /proc and then copy last_kmsg to /sdcard (rename to last_kmsg.txt or zip it up in a file).
Copy and paste the results to a paste bin and post the link. If you don't know pastebin then just post the last 10 lines or so.

tlb1961 install guide
Howdy all,
Glad to hear most are having good luck with this newer revision. To those seeing odd issues after install, I would suggest start over from scratch and clean out the gTab prior to reinstall including repartition the internal SDCard. Run the ROM for a bit before installing anything else. If you have a lot of media files on an microSD card then let it sit for a little while. Once the ROM is running smoothly you should then apply the latest the3dman GApps package.
I know it's tempting to try and hang onto old configs and settings, but it will give you a better experience in the long run if all old data is cleared.
Click to expand...
Click to collapse
lyricalpapa installation essentials
Here's some things I do that work for me:
1. Give my tablet time to boot - let G-Mail, Google Maps, and the other apps load in, talk to the mail server, etc. I watch the activity in the "broadcast" symbol and wait for the browser widget to display its bookmarked pages.
2. Follow the dev's install instructions and @serialplague's FAQ - goes without saying.
3. Have Patience - I give the cache driver's balancing and optimising routines time to do their work after I load a ROM, plus any time I add/remove apps or any time I make changes to the settings. Remember this is a Beta Test ROM and not a snapshot image of a fully tested, optimised, and balanced ROM that you would get if you were to buy a new ASUS Transformer or whatever.
4. Use the apps the Dev's gave us with the Beta ROM - I use the Elixir app regularly to check if the CPU and I/O activity levels have dropped down to near 0% for both. I check them after installing my ROM's, etc. (I also now use the Diagnosis app thanks to @oldtimer)
5. Remember the G tablet only has 512M DDR-2 RAM on board and was built to run with a 2.2 Froyo ROM, a cadged 2.6.32 kernel, and slow generic drivers. Google's minimum published specification for a system running Honeycomb or newer is a Nvidia Tegra-2 processor and 1G of RAM. So the challenge is to modify and tune the 2.6.39 kernel drivers and the ICS ROM to live within the available 512M RAM.
6. edit-no longer needed
7. Killing unnecessary apps sometimes frees up enough memory to stop the CPU and I/O churning. But I have to be careful which apps I kill using an app like Advanced Task Accelerator - it can shut down necessary services - although Android will usually restart them automatically (and kick up the CPU and I/O activity while doing so)
8. Remember that Google Apps come with a high overhead price - the standard Viewsonic set-up for the G tablet does not include GAPPs, and it runs very fast. The same for many other tablets that don't have a Tegra-2 and 1G of RAM. Game players might want to experiment with not loading GAPPs. In the past I've done this by downloading all the apps that I was interested in from GAPPs, then copying them all out to my PC using the "adb pull" command ("adb remount" to get in as root). Then I wipe and reload the ROM without GAPPs, and use "adb push" to put the apps in the right directories. Then on my G tablet, I find the apps using Root Explorer and "click" on them to install them.
Lyricalpapa
Click to expand...
Click to collapse

How do I stop my tablet from downloading every app I have ever owned or used from the market when I log into my android account.
I suspect I am doing something wrong because the tablet is very laggy with ICS.

When you first install it will ask you if you want to use your backups, just uncheck that. Or you can let it sit for awhile, 30min to an hour, it sucks but once everything calms down its much better.

Android Keyboard
Good men of this forum,
It seems that with the new ICS rom, I am having issues with my android keyboard. If my tablet is vertical, I have the dialpad-looking keyboard with what seems to be Japanese characters on a few buttons. When my tablet is in the horizontal orientation, the keyboard disappears completely. I have searched the popular forums here and with Google. I'm terribly sorry if I have missed a tip somewhere.
I used the flashing procedure on the TeamDRH website to the letter, and I am no stranger to flashing custom ROMs to android devices. The keyboard continues to work beautifully under Froyo and Gingerbread ROMs, as well as the earliest beta of ICS. I only seem to have an issue with this version of ICS.
I'm also getting frequent Google Apps errors about the services stopping. After signing in with my account, Market crashed and disappeared from my apps menu altogether.
It seems that I have a fairly unique problem. I'm a linux sysadmin and I'm very handy with the command line if you need dmesg or kernel output.
Thank you in advance.

I've heard a couple of people are having problems with the GApps, have you tried installing with the lite 7b GApps?

No Luck
Thanks for the reply!
I have tried both the full and lite versions of 7A and 7B for this ROM with no luck. When I perform a first-time boot of the tablet after a ROM and Gapps, the very first message I encounter is "Unfortunately, the process com.google.process.gapps has stopped" for any version of Gapps, and it continues to pop up every several seconds that the tablet is in use.
I have also tried installing the ROM without Gapps at all and the keyboard is still nowhere to be found. Odd that the keyboard works in the first beta (1E), but this ICS (2B) is much faster than the old one
If anyone has a link to download the ICS Preview 2A instead of 2B I would be interested in trying it out, the links on TeamDRH's website all point to 2B now.
Other useful info: I know for certain that I am running the 1.2 bootloader and I'm using the newest Clockworkmod v5.5.0.4 Beta 15. I like to re-format before every flash to ensure a clean start.

Thats very odd it sounds like the download may have been corrupted. I've seen it happen a couple of people.
I still have 2A and some previous ones, kinda a catalog lol, just PM if you want to go that way.

I'm a newb
Thank you very much for the help you've provided me.
I tried downloading 2B a few more times with the same issue :/ so strange. Unfortunately for me, I am below the 10 post minimum to allow PMs. It's kind of ironic actually, I've been a member for years and always found my answers without having to ask because xda is wonderful about providing info
Thanks again.

Sent ya an email
simplyphp has a great writeup on an installation method you could try his way

SUCCESS!
Using the simplyphp method you referred me to, not only does the 2A ROM work, but the newest ROM and Gapps as well! I must admit that I'm a little embarrassed that I can't actually identify the original problem, but I believe it has something to do with my installation of Clockworkmod. I got it from a forum here that is trustworthy, but it didn't seem to work exactly as I needed it until I installed it with nvflash. I also had a strange problem with the first flash (out of the two that I am supposed to do) in that it wouldn't boot all the way into the TnT factory OS and was in an endless reboot. I simply turned it off, booted into APX mode once again, and continued with the listed steps and it worked flawlessly. I would thank simplyphp but I can't post on development threads yet!
So thank you and have a "Thanks!", I hope I've contributed to your wealth of knowledge on troubleshooting.

Hellfire 1.9 install report

Well it appears I don't have enough karma to post to the relevant thread so I'll just drop this here. Hopefully the folks over at
http://forum.xda-developers.com/showthread.php?t=1501667&page=1
will see it....
Et all,
I would like to step out of my normal lurking to post some feedback. Firstly, I'm not a dev. Like most of you I'm just an avid consumer of ROMs who is technical enough to keep up with them. I've installed the 1.9 HF release and am mostly pleased. I know people complain about install issues and BB issues and etc so let me throw out a recommendation for a clean install:
1) Assume nothing. You will lose everything. I don't even work off a backup really although I do sync with Google like a good boy.
2) READ THE ENTIRE FORUM THREAD. Yes. It hurts. But it hurts less than a bricked phone or a lousy experience. And you don't end up asking questions that have already been asked. I'm always please with how polite folks can be. Sometimes I just want to lean close into my monitor and yell "RTFM or RTFP!" but that's probably why I keep a lower profile. You also catch the glitches that might give you that bad experience. Like the baseband concern(s) that have been posted.
3) I did everything I could thru the proper LG update tool first. Tmobile G2X P999DW. This got my BB up to 3-11-2012 before I started anything.
4) Get all your backups and get them completely off your phone.
5) Get the LATEST CWM first.
6) Go thru the usual wiping out of your phone. One comment I have on this part is that I always completely wipe my phone. Meaning, in addition to the usual "wipe data / factory reset" | "Wipe Dalvik Cache" | etc. I also clear out the battery stats and completely format the external SD card. Silly? Dunno. My complaints seem less than others.
7) Once the phone boots let it sit. Uncheck syncing with google and just let it warm up. Seriously leave it for like 20 minutes just sitting there. Absence makes the heart grow fonder.
8) Play around with the default apps. Default settings. Default functionality. Audio? Data? MMS? USB tether? Is everything working? Is everything reasonably responsive? Basically the goal here is to have a "sign off" on the upgrade process and the installed ROM at this point. Before you add your apps and your settings back. Make sure that the ROM is solid at this point.
9) Decide at this point if (and what) you want to restore from backup. I do have titanium backup and do use it sometimes but I often find that simply pulling my relevant apps back down from the store and reconfiguring my preferences keeps things a little more stable and I also maintain an understanding of the ROM settings if I manually navigate things myself.
Result? My install went clean and the ROM seems very solid. I've reloaded my apps and widgets back and customized everything in my preferences and I am happy. I am experiencing what I believe is being referred to as the data drop issue. I have noticed several times a "network unreachable" type error (depending on the app) when I know my coverage is good and I can often retry a few times and it'll work again. Looking forward to seeing some progress on this. Other than the data drop the ROM is everything the positive feedback hypes it up to be. Seemingly solid. Fast. I love the interface. Definitely extends the life of my G2X.
Thank you everyone who contributes either as a dev or as a consumer to these threads. You keep the culture alive.
-Psychopuff

psychopuff said:
Well it appears I don't have enough karma to post to the relevant thread so I'll just drop this here. Hopefully the folks over at
http://forum.xda-developers.com/showthread.php?t=1501667&page=1
will see it....
Et all,
I would like to step out of my normal lurking to post some feedback. Firstly, I'm not a dev. Like most of you I'm just an avid consumer of ROMs who is technical enough to keep up with them. I've installed the 1.9 HF release and am mostly pleased. I know people complain about install issues and BB issues and etc so let me throw out a recommendation for a clean install:
1) Assume nothing. You will lose everything. I don't even work off a backup really although I do sync with Google like a good boy.
2) READ THE ENTIRE FORUM THREAD. Yes. It hurts. But it hurts less than a bricked phone or a lousy experience. And you don't end up asking questions that have already been asked. I'm always please with how polite folks can be. Sometimes I just want to lean close into my monitor and yell "RTFM or RTFP!" but that's probably why I keep a lower profile. You also catch the glitches that might give you that bad experience. Like the baseband concern(s) that have been posted.
3) I did everything I could thru the proper LG update tool first. Tmobile G2X P999DW. This got my BB up to 3-11-2012 before I started anything.
4) Get all your backups and get them completely off your phone.
5) Get the LATEST CWM first.
6) Go thru the usual wiping out of your phone. One comment I have on this part is that I always completely wipe my phone. Meaning, in addition to the usual "wipe data / factory reset" | "Wipe Dalvik Cache" | etc. I also clear out the battery stats and completely format the external SD card. Silly? Dunno. My complaints seem less than others.
7) Once the phone boots let it sit. Uncheck syncing with google and just let it warm up. Seriously leave it for like 20 minutes just sitting there. Absence makes the heart grow fonder.
8) Play around with the default apps. Default settings. Default functionality. Audio? Data? MMS? USB tether? Is everything working? Is everything reasonably responsive? Basically the goal here is to have a "sign off" on the upgrade process and the installed ROM at this point. Before you add your apps and your settings back. Make sure that the ROM is solid at this point.
9) Decide at this point if (and what) you want to restore from backup. I do have titanium backup and do use it sometimes but I often find that simply pulling my relevant apps back down from the store and reconfiguring my preferences keeps things a little more stable and I also maintain an understanding of the ROM settings if I manually navigate things myself.
Result? My install went clean and the ROM seems very solid. I've reloaded my apps and widgets back and customized everything in my preferences and I am happy. I am experiencing what I believe is being referred to as the data drop issue. I have noticed several times a "network unreachable" type error (depending on the app) when I know my coverage is good and I can often retry a few times and it'll work again. Looking forward to seeing some progress on this. Other than the data drop the ROM is everything the positive feedback hypes it up to be. Seemingly solid. Fast. I love the interface. Definitely extends the life of my G2X.
Thank you everyone who contributes either as a dev or as a consumer to these threads. You keep the culture alive.
-Psychopuff
Click to expand...
Click to collapse
I too am just like you. I did the same as you but lost audio now I am not complaining this rom works amazing but just trying to revert back to see what went wrong getting bacm to Oem is the problem I am having

Brothers! We almost have the same story here. I did not have many data problems from what I remember on the stock Hellfire ICS 1.9, but my battery would hardly last 12 hours. Even if I did not install any background apps. Do you guys have this type of battery drain?
Anyways, I flashed the Harsh non-OC kernel over the ROM. My phone got smoother and the battery is almost as good as stock. But...I started having in call audio problems. This really confused me but it sure sounded like a BB problem even though I have 21y. So started over, cleaned, did ROM, did kernel, did new baseband fix just to see what would happen. Let the phone sit for a bit, then did a few reboots to see what the results were. So far so good. *crossing fingers*
EDIT: OK, I still do have some call issues, but it took longer. 14 minutes into a call, the audio audio cut out but still showed connected. After looking over my phone I discovered that it was unable to get a data connection again, the antenna bars showed nothing, and airplane mode would not function. But I could still receive a call, only to have the audio cut in and out after 15 seconds. WiFi would still work though. Very strange.
EDIT 2 Hardware fix, ROM works fine. http://forum.xda-developers.com/showthread.php?t=1808262

[Q] Über-crash = reformat? What to do? thx

Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.

When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."

jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)

Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*

I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.

JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.

devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.

jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.

Logs or it didn't happen.

Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.

I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...

Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.

[Q/A][Discussion] NEC Terrain general discussion

Hello!
This is a discussion thread for NEC Terrain.
The hardcore steps, which are bootloader unlock, rooting and even repartitioning have found their solutions and can be found in:
http://forum.xda-developers.com/show....php?t=2515602 for the discussion
https://github.com/x29a/nec_terrain_root for an apk which opens for you an ability to have the system area of the phone writeable
https://github.com/alex-kas/nec_terrain for the last ideas on how recovery and boot images should be and a list of stock apps to disable with explanations
So, all questions regarding all the above should be asked in that thread as they are off-topic here.
Currently we have to use this device with its stock components. You are welcome to contribute with workaround related to known oddities here.
Note that many questions were already asked in the above mentioned thread and some of them have answers. However, since that thread is supposed to for the rooting/unlocking, it is more than logic to separate the topics and discuss the end-user phone features here.
If you have a serious idea towards a new custom ROM then you should go here
http://forum.xda-developers.com/android/software-hacking/rom-nec-terrain-custom-rom-t3162061
That thread is dedicated for the developers of a new csutom ROM for NEC Terrain
Thanks for understanding the thread aim and welcome!

First exploration
You can find apps which can be disabled with some explanation why in
https://github.com/alex-kas/nec_terrain/tree/master/system
The speciall account should be paid to the following issues:
Why stock Contacts and Phone must not be disabled
Why apps with provider in their name should treated carefully
Current impossibility to activate a soft keyboard (if you need chinese, for example).
The latter question of a soft-keyboard for this phone has been asked before in
http://forum.xda-developers.com/show....php?t=2806270
and has no answer. There is further discussion on this in my github (see above)
On more oddity which at least my phone has: when I travers to
Settings->wrieless & networks->more...->Mobile networks
I see as the last option "network operators". This option i constantly greyed out. It is useful in roaming as often different orpeators have different prices. Also, near the borders of a country som eforeignn operators can be captured. This is bad. Anyone with ideas on this?

i was wondering if someone with a fully functional Terrain upload their /system/app folder and its contents, I've seemed to remove an essential app somewhere and now I can't do phone calls or terrain hotspot.

Daxiongmao87 said:
i was wondering if someone with a fully functional Terrain upload their /system/app folder and its contents, I've seemed to remove an essential app somewhere and now I can't do phone calls or terrain hotspot.
Click to expand...
Click to collapse
I can do this tomorrow. I am able to phone call, hotspot, etc. I've noticed that with me, sometimes the phone UI won't show up when someone calls me so I cannot answer the phone... If this happens, just do a Wipe Data on the phone apk and reboot.
Sent from my LG-D415 using XDA Forums

@jasonmerc much appreciated! My backup phone just isn't cutting it for me!

Daxiongmao87 said:
@jasonmerc much appreciated! My backup phone just isn't cutting it for me!
Click to expand...
Click to collapse
No problem man . Just curious, what is your backup phone?
Sent from my LG-D415 using XDA

My nieces phone for her upcoming birthday. The excuse I'm making to myself is that I'm "test driving" it. It's called the Xperia Tipo, she's only 9 and would be using it at more or less a little toy; no SIM card. I have better ones actually, HTC One and a Moto X (2013), the latter being my favorite phone without a hardware keyboard.

I'm wondering about 2 questions, guys:
1. @Daxiongmao87, what is the hotspot you are talking about?
2. @jasonmerc, can you provide to me the list of your apps, enabled and disabled? Or, if you just uninstalled them (so no disabled) then only enabled.
I want to see the list given in adb shell by
pm list packages -e -f [for ENabled with file-names]
pm list packages -d -f [for DISabled with file-names]
I'm curious about this can/cannot do phone calls. I had established some dependence but you have said you CAN do calls with attsettingsprovider disabled and even see contacts. Very strange to me and I want to find the truth I.e. Can I or not eventually get rid of stock contacts at all.
Thanks in advance.

@alex-kas hotspot meaning wireless tethering. There's a system app with the package name containing hotspot. I believe jasonmerc already provided me with that earlier along with the phone apk, but ultimately did not help fix my issue. My symptom for the two issues are as follows:
Wifi Hotspot (Tethering)
-Under the Tethering & portable hotspot menu, toggling Portable Wi-Fi hotspot reveals a subtext that reads "Failed to set transmit power"
Phone Calls
-My phone no longer notifies me whether or not I have a SIM card. No icon or any indicator at all. My signal icon always shows zero bars. attempting to make a phone causes Contacts to crash ("Unfortunately, Contact has stopped.") and haults the phone call process.
I hope this information helps a little bit. More than likely i'm missing a vital app that I carelessly removed upon tinkering.

Daxiongmao87 said:
@alex-kas hotspot meaning wireless tethering. There's a system app with the package name containing hotspot. I believe jasonmerc already provided me with that earlier along with the phone apk, but ultimately did not help fix my issue. My symptom for the two issues are as follows:
Wifi Hotspot (Tethering)
-Under the Tethering & portable hotspot menu, toggling Portable Wi-Fi hotspot reveals a subtext that reads "Failed to set transmit power"
Phone Calls
-My phone no longer notifies me whether or not I have a SIM card. No icon or any indicator at all. My signal icon always shows zero bars. attempting to make a phone causes Contacts to crash ("Unfortunately, Contact has stopped.") and haults the phone call process.
I hope this information helps a little bit. More than likely i'm missing a vital app that I carelessly removed upon tinkering.
Click to expand...
Click to collapse
Have you read my github?
https://github.com/alex-kas/nec_terrain/tree/master/system
If not, try to see there. I spent quite a time and I'm sure my phone IS working in both aspects you mention. Pay attention to: contacts, phone, attsettingsprovider and installation of "dw contacts". All of that is by purpose. Perhaps, my phone would not work w/o "dw contacts" but I just learned that a replacement (which joins phone app and contacts app, which are disintegrated once you remove attsettingsprovider) MUST be.
You will find there files: lists of enabled and disabled programs. Compare with yours. In adb shell:
pm list packages -d [gives disabled packages] -s [if only system]
pm list packages -e [gives enabled packages, all, system and 3-rd party] -s [if only system]
My lists contain ONLY system apps. 'system' are those who reside in /system/apk OR in /data but are upgrades to initial system apps. Hope this helps. If you have put there superuser - it is system now, for example.
I can also imagine that moving some app to sdcard makes the system buggy. I had no full skype autostart then it was moved.
hotspot in the name does NOTHING with tethering.

@alex-kas you should have a full list of apps I have installed already, I PM'd you a list a while back. About to do the /system/app dump, most likely I'll package it as a zip or 7z file and upload and share from Google Drive.
Also as a little update, I mentioned the GPL stuff in my ATT thread. Waiting for a response
Sent from my LG-D415 using XDA

Here's the contents of my /system/app folder. Apparently I don't have ATTSettingsProvider.apk, BUT I still have ATTSettingsProvider.odex if that makes a difference.
https://drive.google.com/file/d/0BxupjEjigG4taFZhWXl3RjVULTA/view?usp=sharing

alex-kas said:
Have you read my github?
https://github.com/alex-kas/nec_terrain/tree/master/system
If not, try to see there. I spent quite a time and I'm sure my phone IS working in both aspects you mention. Pay attention to: contacts, phone, attsettingsprovider and installation of "dw contacts". All of that is by purpose. Perhaps, my phone would not work w/o "dw contacts" but I just learned that a replacement (which joins phone app and contacts app, which are disintegrated once you remove attsettingsprovider) MUST be.
You will find there files: lists of enabled and disabled programs. Compare with yours. In adb shell:
pm list packages -d [gives disabled packages] -s [if only system]
pm list packages -e [gives enabled packages, all, system and 3-rd party] -s [if only system]
My lists contain ONLY system apps. 'system' are those who reside in /system/apk OR in /data but are upgrades to initial system apps. Hope this helps. If you have put there superuser - it is system now, for example.
I can also imagine that moving some app to sdcard makes the system buggy. I had no full skype autostart then it was moved.
hotspot in the name does NOTHING with tethering.
Click to expand...
Click to collapse
http://pastebin.com/1yRtvVhz
Thank you for your assist!!
And @jasonmerc thanks a bunch!! Giving it a shot now
EDIT: back online with wifi tethering and cell network thanks again guys
Edit 2: By the way, has anyone experienced unexpected reboots during high RAM usage? Games for example?
Sent from my NEC-NE-201A1A using XDA Free mobile app

@alex-kas after successfully applying your custom recovery and resizing my partitions i seemed to have lost my boot animation and sound. It just shows a black screen. Is this intended? Perhaps with the new build.prop?

Yeap, i disabled bootanimation. It seems to increase the boottime even more.
Sent on the go

Yes, I've experienced reboots when doing multiple things. For me it's usually just watching a video or something... Perhaps it overheats and that's what causes the reboot. On average my Terrain's CPU is somewhere in the 120°F range, and if I use it it can go up to 145°F at times. It will sometimes even get so hot that I get a notification stating the device is too hot to continue charging, and I need to try charging again in a few minutes. Is this normal?
Sent from my LG-D415 using XDA

jasonmerc said:
Yes, I've experienced reboots when doing multiple things. For me it's usually just watching a video or something... Perhaps it overheats and that's what causes the reboot. On average my Terrain's CPU is somewhere in the 120°F range, and if I use it it can go up to 145°F at times. It will sometimes even get so hot that I get a notification stating the device is too hot to continue charging, and I need to try charging again in a few minutes. Is this normal?
Sent from my LG-D415 using XDA
Click to expand...
Click to collapse
Hmm I thought I replied to this. I experience overheats as well, but mostly when using maps. However, I haven't been able to see a correlation between reboots and overheating. I have a feeling that when available memory gets too low the system becomes unstable and inevitably reboots. With the new partition size I was able to install hearthstone without any need for apps like Link2SD, but upon loading all of its assets to start an actual game session it reboots every single time. When not attempting to play that game, during times where the phone feels sluggish or unresponsive, it often follows with a reboot.

Daxiongmao87 said:
Hmm I thought I replied to this. I experience overheats as well, but mostly when using maps. However, I haven't been able to see a correlation between reboots and overheating. I have a feeling that when available memory gets too low the system becomes unstable and inevitably reboots. With the new partition size I was able to install hearthstone without any need for apps like Link2SD, but upon loading all of its assets to start an actual game session it reboots every single time. When not attempting to play that game, during times where the phone feels sluggish or unresponsive, it often follows with a reboot.
Click to expand...
Click to collapse
This is exactly what I have denoted as the kernel bug, see
http://forum.xda-developers.com/showpost.php?p=61915007&postcount=293
In addition to the info there: reboots happen if several not so big files (say, 50MiB each) are read in a row, not just a single file of > 500MiB. Loading a large set of game assets just confirms this.
I traced this bug and the point is that its origin is a mystery to me. It is in a part which I would never imagine was changed from the linux source. Just no need for this.
In short, the ext2,3,4 driver, reading data, then caches them (linux always caches, all it reads, as much as possible). At some point the cache request to allocate the memory just ignores the negative answer (i.e. no memory), it just does not check this answer at all and caches to NULL, i.e. start of the memory, where the memory map is. As it is the kernel, it has right to write there, writes, kernel panics - reboot.
How come? I have no idea. This code was already working in about 2005 ... and bug-free in about 2008 ...

@alex-kas you get what you pay for I guess...
Sent from my LG-D415 using XDA

jasonmerc said:
@alex-kas you get what you pay for I guess...
Sent from my LG-D415 using XDA
Click to expand...
Click to collapse
What exactly you mean? The phone is not that cheap. If new. Especially from att.

Why didn't my apps install on my new U11+ ?

I just bought a U11+ as an upgrade to my U11 and am configuring it, which is taking longer than I expected because neither of the two backups I did (htc's and Backup Your Mobile) installed most of the apps (or their data). Also, I've had two System updates in the last two days.
I got my custom background, the Keep Notes app (plus its data) and Facebook; that's pretty much it.
What did I overlook?
Oh, yeah... I cannot find a setting to keep the display on when powered. Anyone know how to do that?

If you did a jump to a new OS version or device that may be why.
If you did any major firmware updates on the new device, it's factory reset time.
Otherwise clear the system cache.
Manually loading them may be your only option.
Welcome to the fking planet

blackhawk said:
If you did a jump to a new OS version or device that may be why.
Click to expand...
Click to collapse
That occurred to me when I (finally) checked the OS version and saw that it was 8.
I've been getting update notices for the last two days and the most recent one (the third) was the Android 9 OS (update # 2.19.401.2). Where can I check on official updates so I can get an idea when this will stop (because manually looking for updates this morning got me nothing, then I saw the update prompt a couple hours later).
Updated to 9, rebooted and verified that Google Drive is connected, but I'm still not getting Backup & Restore to work. Will have to experiment with the others.

Jeff in 92833 said:
That occurred to me when I (finally) checked the OS version and saw that it was 8.
I've been getting update notices for the last two days and the most recent one (the third) was the Android 9 OS (update # 2.19.401.2). Where can I check on official updates so I can get an idea when this will stop (because manually looking for updates this morning got me nothing, then I saw the update prompt a couple hours later).
Updated to 9, rebooted and verified that Google Drive is connected, but I'm still not getting Backup & Restore to work. Will have to experiment with the others.
Click to expand...
Click to collapse
I learned long ago that if your OS is fast, stable and fulfilling its mission, let it be.
I've been on Pie for 2 years, my last reload was 1.5 years ago, still fast and stable with minimum maintenance. What's not to like?
Unless you start screwing with the firmware and bring in new issues that need fixed.
Security generally isn't an issue unless you do something stupid.
There's no saving dumb bunnies... be careful what you load and download.

blackhawk said:
If you did a jump to a new OS version or device that may be why.
If you did any major firmware updates on the new device, it's factory reset time.
Otherwise clear the system cache.
Manually loading them may be your only option.
Welcome to the fking planet
Click to expand...
Click to collapse
I did a Factory Reset (but it stayed Android 9). I did this because I had 'restored' a lot of files from Backup Your Mobile's (aka BYM) work on my U11.
Two things are bothering me:
1) The HTC Transfer Tool is not working this time (it transfers the PIN Code, but never gets to CONFIRM. After repeated attempts following reboots, etc., I have noticed that the PIN Code sometimes flickers off and back on again; what's up with that?).
2) BYM transferred my SMS and MMS to my U11+, but clicking on a text message that includes an MMS just makes the message thread avatar flicker and stay on the message thread listing (not even a flicker of the thread is displayed).

You mean screen lock codes?
First I don't password lock devices. You're the most likely one to end up getting locked out.
If you do use one I wouldn't attempt to back it up and transfer it. If it gets corrupted what follows won't be fun.
Pie's a good OS.
Clearing the system cache never hurts to try when experiencing glitches.

blackhawk said:
You mean screen lock codes?
First I don't password lock devices. You're the most likely one to end up getting locked out.
If you do use one I wouldn't attempt to back it up and transfer it. If it gets corrupted what follows won't be fun.
Pie's a good OS.
Clearing the system cache never hurts to try when experiencing glitches.
Click to expand...
Click to collapse
No, I did not mean screen lock codes. The HTC Transfer utility worked the first time I tried it before the Factory Reset, but it's not working now. The PIN Code is displayed on the source phone, but it doesn't activate the confirmation button to do the transfer.
I have since learned that many of the apps that were copied over via Google Play's utility also transferred the data, but not all the apps were transferred.
More research to be done, it seems.

Jeff in 92833 said:
No, I did not mean screen lock codes. The HTC Transfer utility worked the first time I tried it before the Factory Reset, but it's not working now. The PIN Code is displayed on the source phone, but it doesn't activate the confirmation button to do the transfer.
I have since learned that many of the apps that were copied over via Google Play's utility also transferred the data, but not all the apps were transferred.
More research to be done, it seems.
Click to expand...
Click to collapse
My bad... I use Google search a lot and it doesn't need to be that specific model or OS version most times. Many of the issues are long standing. I even use solutions for other manufacturers models. Whatever comes in handy.
And/or just play with it until I work it out.
I haven't used that app. If you upgraded the firmware or are transferring data from another device these kind apps can screw up especially with app settings.
If you're doing a factory reset because of an issue or a crash they can inadvertently reload the root cause of the issue.
It's nice to save the homescreen, theme, icon setting on a reload using these though. Most apps I hand reload/configure or use the app's backup setting file like with Poweramp or DIGI Clock which are very intensive to set from scratch.
Critical data I save in a master backup folder(s) as files. Be ready to reload at any time as most crashes while rare give little or no warning. Redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Most times a factory reset is to give the device a clean slate. Looking over app settings while setting them up helps to spot things you may have previously missed. It helps a lot to be familiar with the nuts and bolts at the user interface level. Many times when troubleshooting this is where the answers lurk.
I consider my first load or two on a new phone trail runs. After which it's pretty well sorted out for a clean load. I do the same on PCs. Android's are very forgiving but poorly written apps or the user can still skew hidden user settings that are hard to find/access on a stock device. A stable, fast load is a pleasure to use and will run well for a long time with only simple maintenance on a stock Android.