Related
As I suspected early on the issues boil down to corruption within the User Data or Cache partitions, less often on the system partition due to an unexpected shutdown of the device. Shut on these devices need to follow the proper shutdown routine as any linux environment. Following this best practice will ensure that all data is written out to its corresponding file system by flushing all cache, unmounting the file system, etc..
Here are the culprits of why we see so frequent random Force Closes, Market Resetting, etc. ultimately resulting in an unclean shutdown, corrupting some data.
1. The button we use is also a forced off button. Typically if you hold it down too long you are powering off the device.
2. Some times when in sleep mode you see the Viewsonic logo upon starting - that means that the system shutdown (most likely crashed).
3. If your running Vegan your hitting the reboot.. I dont know for sure but I suspect this is NOT performing a clean shutdown... (I dont have a copy of the source)
Anyway... wanted to pass this on... as last night my data partition became corrupt after using the Reboot function on the Poweroff menu of Vega 5.1..
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
roebeet said:
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
Click to expand...
Click to collapse
I have been on stock since I got the device just moving to the newer versions when they come as OTAs and have never ever had to mess with my partition, so I don't THINK the issue is in the stock software. In fact, the only problems I've ever encountered were when I used the enhancement pack, in which case my screen started to become unresponsive and the calibration.ini I was told to try did not work. Since then I went back to 3389 and the device has been perfect ever since.
I could be wrong though and just very, very lucky....here's to hoping. Another thing to consider is maybe the memory is going bonkers for some reason. I've had flash memory that lasted forever and I've had flash memory that has gone wacky over a period of 6 months....even a wipe by the utility designed to do it doesn't fix it properly. I don't know how CWM wipes or partitions the memory, I do know there's supposed to be a special way to do it.
If it's not faulty memory off the bat, then that leaves something in the 'extras' being put into these ROMs. Maybe some of the newer tegra drivers or some coding to make the ROMs faster - I'm just saying, can't leave any stone unturned.
Has anyone that has stayed loyal to stock encountered these issues? We have to ask that question I think. Then we ask how many of the people playing with ROMs are seeing the issues, this would include people that have used CWM to partition and mess with their mounts initially.
I can say I've never seen data disappear from my internal memory or my SD and I can also say I've never seen multiple FCs except after putting in the enh. pack (keep in mind I got my tab on Dec 20something, so I had 3053 and then 3389 soon after).
The first sign of anything being 'corrupted' on it's own at stock and I'll be sending mine back. As an owner of Android since Android's been around, I've never had my G1 or MT4G (or any smartphone before it) become corrupted due to not being shutdown or reboot properly and while this is a tablet I think the fundamentals should be the same. Pampering 'faulty' memory is a risk. You can wipe and re-do all you want, but if it's faulty it's going to stay that way.
Ive done that but I guess you can say unfortunately I have had only clean shutdowns since then... The last corruption I had I formatted my data and cache partitions before I ran logcat.... Of course thought of that afterward....
Generally if any has FCs, etc. etc. run a logcat and post it here... we will be able to confirm this...
We could change the way the partitions are created and add a sync which will further reduce chances BUT will take a performance hit...
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I reviewed the out of the box framework source on the google GIT and technically if a reboot command is given a clean shutdown is performed via the framework... but the widget on the shutdown screen I suspect is not calling the method properly or is not being called at all... All speculation at this point... But for sure there is corruption occurring..
Since the last corruption I switch over to pershoots kernel... Even though his kernel seems to be a little slower he seems to have included the latest drivers which other items relate to data integrity (im reading into the release notes).
NEO: The first thing I did when I got my device install CW, Vegan... Updated Kernels also... Never had an issue until the first time (yes about a day ago) I used the reboot feature of Vegan. That corrupted my user data. I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
But again.. between the wrongly placed power switch, the unprovoked reboots (ie viewsonic screen showing when trying to wake up the device) and the reboot button possibly not performing a proper shutdown will sure increase the chances in a wider distribution of users. So it may not be a CW issue and just some poor design.
When I have time today I will verify if the reboot function performs a clean shutdown... if anyone has the time please post the logcat... Im going to be running around today and will try to get to it..
watson540 said:
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
Click to expand...
Click to collapse
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
Click to expand...
Click to collapse
AFAIK they're running yaffs ATM. Next move is to ext4...
Read some articles about this several weeks ago, apparently many apps do not properly flush file caches. One of the articles was a Google developer post about file corruption along with their API method which did a cache flush prior to a close, then a bit later was the Google indication that they were planning to move to ext4 FS to further help alleviate the problem.
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
Click to expand...
Click to collapse
That's my point. How many times since we've had our Android and smart phones have we had situations where they are turned off or rebooted without the proper procedures? Power drains till they die, they drop and reboot, we clog them up with stuff or some app drives them nuts and they reboot or shut off....Yet you rarely if ever hear about a phone's data being 'corrupted' with stock software. Sure it may happen with official OTAs etc, but never just off-the-bat like what's happening with the G-Tab. But it's not happening to everyone either so I'm just looking to see if there's a pattern.
Even since the G1 and newer phones, you don't really hear about or see file corruption issues on stock software with these phones. It's when users start going to ROMs that you hear of issues cropping up. That's not to say it doesn't happen at all at stock, I just think we're seeing it in a more concentrated fashion here because of all the formatting, re-partitioning, etc. At first you hear, 4GB is a great partition size, then you hear there are problems so move to 2048, then you hear 256MB swap, then no swap since Android doesn't use it. Then dataloop for speed, then no dataloop because of critical issues. Rules and instructions change almost on a daily basis. I think it's more than these poor flash drives can take I find sometimes it's good to keep it simple.
I owned a Vibrant for a while...decided it was a PoS when at stock I was seeing bad lag (because of Sam's terrible FS). People said...do the speedhack, it'll be fast!, but what was the caveat? Having to reboot the phone almost weekly, sometimes several times a week, and people were seeing what? Data corruption. That's not for me. Give me something that is lag free (doesn't have to be a bullet train, just don't skip on video or audio and make sure my live wallpaper and drawer animation is fluid and I'm happy!). Point being....keeping it simple may help to alleviate some of the issues. If people are seeing these problems with stock, then you're absolutely right and it would be a point of contention that the failsafe isn't working right.
Otherwise it seems the stock OS on these things are able to self correct in most situations and it may just be some of the many tweaked features in these ROMs doing something it shouldn't - or, I may just be very lucky indeed.
I'm still dying to get the OTA - I haven't seen one since 3899 yet.
Hi,
I've come to believe that my TP2 phone's internal memory has some bad sectors, and am wondering if there is a utility that can scan for these and mark them so that they will not be used with future flashes. I've searched fairly extensively on this site, as well as on PPC Geeks, and haven't found anything that could accomplish this yet. It doesn't seem like task29 would do this (and I've used it, yet still have problems arise), and I can't seem to get more info on this around the CustomRUU or HardSPL forums.
Initially I used the stock ROM, and it worked quite well for a few months. After a while, it developed problems with a key executable in the OS. A hard reset solved this problem for another few months, when it arose again, with the same executable causing the problem. I soon unlocked my phone and flashed a custom ROM on it, and all key components worked fine. Interestingly, it seemed to be the section of the ROM storing the ringtones that was unreliably stored, and the phone would revert to silent mode after being unable to open the files (replicated by trying to manually open these files, or preview them in the sound preferences section). Occasionally these files would work, just as occasionally the faulty executable would work in the stock ROM. The easy work-around for this was to have a ringtone on the SD Card, which is what I've done for the last few months.
I would like to be able to flash future ROMs without wondering which areas of the OS would fail (and am wanting to root the phone to run the android NAND build, which is now quite mature). Is there an application somewhere that can do this? Is there a good website or resource that you can point me to that deals with this?
Thanks for your help!
I have a Rhodium 400 (Telus, CDMA) fully unlocked & with Hard SPL installed. I'm running WM5 (Energy ROM), with XDAndroid FRX04 running via haret off of the SD Card.
Doesnt sound like a chip issue. It might be something with your program that you are using. Besides, OS tends to go corrupt after a while, so a Hard Reset every couple of months, is not a bad deal.
If you have a bad chip, then you wont be able to load a OS at all.
Not a chip issue? It sure seems to be why an OS would 'go corrupt after a while'. I don't imagine it's an all-or-nothing issue, but that some portions of a chip may contain bad sectors (or whatever the equivalent is for nand).
Regardless, I hear your assertion that this type of experience is common enough. If anyone else has some insight into how this corruption may be avoided or delayed, I'd appreciate it.
Thanks.
(FRX05 on NAND will be on my Rhod 400 soon enough)
I am one of the many who have been experiencing the random reboots. I have seen talk about it, but have not seen anyone really looking into why this is happening. Some people claim it happens only when docked, or when SD card is in etc. Yet others post that they still get the reboots without doing those things either.
I have been monitoring my reboot problem very closely. I have yet to determine the cause other than it only happens when the device is put into sleep mode manually or automatically, and I am looking for some help from some of the DEV's around here.
When our TF's do this reboot, it is a system crash. When this happens, a ROMDUMP file is placed on the internal "sd card".
These can be viewed with a simple txt editor, like windows notepad. I myself can not read the code and understand what info it is revealing to me. According to an Asus tech on the phone this file can tell you what went wrong and made the device reboot. However the buggers won't tell you crap over the phone and want me to send the device in with the ROMDUMP files.
When I try and read the files, I do see one thing in common, in 99% of them, right near the end of the file, or the very last line before the crash, this line is present,
Kernel panic - not syncing: Fatal exception in interrupt
<2>[ 162.985309] CPU1: stopping
If our reboot issue is kernal based, which would indicate it's a firmware issue;
I was thinking one of the talented DEV's around here could fix us up.
Hell maybe even just a reflash of the current firmware would fix the issue.
Anyway, if a DEV around here want to or willing to look into this, I have some ROM dumpfiles they can look at, just send me a PM.
For reference,
I have a B60K modle
Stock 3.1
GPS 1.3.1
Wifi 5.1.42
BluT 6.17
Kernal 2.6.36.3-00001-gf377a2b [email protected] #1
Build HMJ37.US_epad-8.4.4.5.2-20110603
Thanks.
I don't have any more dumps recently, deleted them so I can't pull up and see what mine said to give you, but wanted to just say I was having these multiple times a day every day and it started once I bought an AData 16GB SDCard for the dock. Then I ended up removing that card and bought a MicroSD 16GB card instead and it has quit doing the random reboots, so definitely seemed to be something with my SDCard in the dock.
Post your whole log here (as .txt or .zip) and I will look at it.
I've had these once or twice but have always deleted the file.
The Kernel Panic is the kernel's way of telling you that something unrecoverable has happened and the integrity of the whole OS is in question. Think of a kernel panic like a BSOD on Windows.
I've never seen that specific one before, but a quick Google search indicates it may be a problem with I/O operations - like bad RAM or a bad SD card.
sassafras
Thanks for the response. I have included 4 RAMDUMP files. I find these 4 special because they all happened in quick succession. Four separate reboots all within 8 mins of each other without any interaction of the device myself. I never touched the device, I just sat there and staring at the device rebooting 4 times in 8 mins. On the final reboot the device never came back on. AT this point I picked up the device and had to hold the power button down for over 10 seconds for the device to come back on to an Asus splash screen. This was mins after I did a fresh factory reset via the OS options internally then a hard reset using the hardware buttons.
...It's a bug alright...
It doesn't seem to be caused by the same problem though, just that the watchdog program invokes a kernel panic and reboots. Weird. I'll backtrace it later and see what's up.
sassafras
went a whole day without a reboot. I did have an odd lock up/freeze at the lock screen where i couldnt unlock the device or get it to rotate the screen. It was locked up tight. Held hte power button down for 20 secs before it shut down. Rebooted, no new RAMdump created. No issues since.
sassafras_, Did you have any luck reading those ramdumps?
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
sassafras_ said:
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
Click to expand...
Click to collapse
Is there any progress on this issue? I bougth a brand new tf and during day random reboots maybe 50 times. And that romdumps are appeared on my internal storage. I dont have external sd by the way. Im stuck.
Hi.
Im having a same problem with my Transformer. Its a week old B60 and its reboots probably 50 times a day and give me log files.
Also im using Honeycomb 3.2
I really want to find out what is going on
i guess its a hardware issue or something.
i'm going to give back my TF today and take back a new one.
if i get same errors, i'll let you know.
I posted a workaround that helps immensely for rooted tablets somewhere around here. I can't find it tonight, but it's in one of the other 'random reboot' threads.
sassafras
sassafras_ -
Did you ever find anything with this issue? I am on my second TF and it is exhibiting the same random reboot while sleeping issue as the first. I know you have a post on another thread indicating how to tell the kernel to ignore "oops" conditions - have you received any feedback on how that is working? I assume this requires root access, I haven't yet rooted my device.
I have collected a few ramdump log files, but as of now only one out of 6 shows a kernel panic. I am new to Android, and I am trying to make sense of the dump logs. It appears that these dumps are maintained in a ring buffer, so the last entries are usually somewhere in the middle, is that correct? All of them also have some garbage at the end, but I assume that is just another effect of the ring buffer strategy.
Like I said, I am new to Android, but I am a long time embedded and real-time programmer, and pretty handy in Linux. It seems to me that the log files aren't providing enough information, but I'm not sure how to debug kernel/system crashes in Android. If anyone could point me in the right direction of where I should look next to get more information on these crashes, perhaps we could get to the bottom of this problem.
From what I can tell via the logs, when the TF is sleeping, it wakes up from time to time for various reasons, then suspends when it is done. It looks like it is during this wake/suspend cycle that something occasionally goes wrong and causes the tablet to reboot.
I am hoping that this is a software/firmware issue (or a hardware issue that can be worked-around with software), because I really like the TF platform and this issue makes keeping apps like IM or email running while it the device sleeps kinda iffy.
Any help from the awesome experts here at XDA would be greatly appreciated, and I look forward to learning more of the gory details and inner workings of Android.
I have had the same issues. Configuring the kernel to ignore oops only helped a bit. The tf would still freeze in standby eventually (once a day or so). My supplier (i.e. not Asus) replaced it and my new tf (a SBK v2 one, unfortunately) has not rebooted once in 2+ weeks. So my guess is that it was a hardware issue (memory, something not coming out of backup mode properly, ...?). Not sure if one could work-around it in software.
Now, this was probably not very helpful but I thought I'd share my experience here. And possibly my tf suffered from an entirely different defect, although the symptoms were the same (ramdump logs from random reboots in standby, independent from wifi on/off, sync on/off, and lots of other settings I tried).
flipflipflip -
Thanks for your reply! I was hoping that it wasn't a hardware issue, and since I got two in a row with the identical problem I was thinking that maybe a software fix could get around it. After reading about your experience, I went ahead and returned it and ordered another one from a different source. Hopefully the third time's a charm!
I'm keeping my fingers crossed that this one is not an SBK v2, but I'll be happy just to have one without sleep-apnea!
This did give me a chance to load up ADB and poke around a bit under the hood of the last one, so if nothing else it is a learning experience. Hopefully I will have something to contribute to the community once I get my hands on a working device.
I know it's been a while (had a big work-related headache), but just wanted to post and let people know that I finally received a TF101 (B50!!) that seems to be working just fine - so I guess it was just a combination of bad luck and a hardware issue after all.
The only issue I have now is that sometimes when it is sleeping, it loses its internet connection (it still seems to be connected to the AP) - but I think I can work around that.
Cheers!
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.
I only got this phone as a second one to perform very miniscule tasks. One of the main ones is simple Mistplay games. Slots, Solitaire etc.
I realized I was going to be in trouble when the "Display over apps" feature was actually disabled on the phone. I did locate a Reddit (they prolly found it here) that fixed that issue
so I have gotten Mistplay installed and running. The problem seems to be the moment I actually try playing anything, the phone closes Mistpla so the time isn't tracked, and therefore
I am not rewarded. I have to assume this is due to the whopping 1gb of RAM and it being Android 11go. There is no way a custom recovery would be written for this phone so I assume
pushing a different mod is out of the question. I did think that maybe Memory Locker might do it but I am unable to root this phone. Magisk needs that boot.img and no idea how to get that.
There may be a way to manually set that oom_adj priority without the app, but that is beyond my abilities.
I figured with root access I could do one of two things, try that app and see it that works, or setup my 120gb microsd as a swap file option to increase the memory but all roads seem to point back to rooting this. I tried 3 or 4 of the one click piddly options for root, all failed.
I would appreciate any ideas and sorry so long but I wanted to try and address the questions ahead of time.