I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
shieldsit said:
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
Click to expand...
Click to collapse
I found that the automatic updates in Market screw up the latest manual nooter. Here's how I fixed the problem.
*IMPORTANT* You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
1. Wipe the device (8 failed boots) and clean the memory (press and hold n while booting and keeping the power key depressed).
2. Complete the B&N registration process.
3. Upgrade to the latest B&N firmware (I tried 1.2 manually)
4. Use CMW and manual nooter by following this http://forum.xda-developers.com/showthread.php?t=1054027&page=1 to root your Nook Color.
5. Use the Market to download Terminal Emulator (see https://market.android.com/details?id=jackpal.androidterm&hl=en for details)
6. type
$ su -
# pm disable com.android.vending.updater
Check out
http://forum.oxygen.im/viewtopic.php?id=919 for more on this.
You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
I'll go through these and see what happens, but I wouldn't call what's happening to mine a boot loop. Nothing shows on the screen at all unless I boot from SD card.
And thank you for replying and trying to help me. I'm lost without my Nook. If I get it working I'm not risking rooting it again.
HI everyone, i'm a Noob here sooo here goes:
I don't know why - but I installed CM9 Alpha 2 on my HP Touchpad and my wireless was working at the time of installation. After using it for a while then turning it off, and on again the wireless stopped working. I can see the wireless signals but when i click to connect it says "Connecting" then back to the wireless name and never connects. It came back, stayed on for a while...then when i reset it again this time to see if it would go off again - it hasn't come back since.
My question: Does anyone know what is going on? Am i missing something or doing something?
Thank you
Im having the same problem...
nightly 3/17
FWIW I have had the same problem occasionally when installing different builds but what seems to help is going into the WebOs and turning the WiFi off then on and then rebooting into whatever Android version I was using at the time. There is also a long thread covering this in the development section with thoughts on how to fix the problem.
bob
"I don't know why - but I installed CM9 Alpha 2 on my HP Touchpad and my wireless was working at the time of installation. After using it for a while then turning it off, and on again the wireless stopped working. I can see the wireless signals but when i click to connect it says "Connecting" then back to the wireless name and never connects. It came back, stayed on for a while...then when i reset it again this time to see if it would go off again - it hasn't come back since.
My question: Does anyone know what is going on? Am i missing something or doing something?"
No, you've done well...wifi has been a persistent issue with almost everyone. There are several ways to go about resolving it.
1) (from terminal emulator): enter su (hit return) then type the following....
rm (space) -rf (space) /data/misc/wifi (space) && (space) reboot
(Or if that doesn't work...)
(from root explorer): access /data/misc/wifi folder then long press wpa supplicant folder and select delete...confirm delete and reboot
Either of those methods from #1 should allow you to restore wifi but you'll probably have to repeat the process upon each reboot/restart of your TP. A more permanent resolution has been proposed by #2 below.
2) You can also look up Rohan's Supreme Mods v 1.3 (for CM9 Alpha 2) and flash that zip file over your current rom, but be sure to reboot into recovery and make a Nandroid backup before flashing the mod package.
:[MODPACK][3/10][NEW]SUPREME Mods v1.3 [Faster, Smoother, Faster Wifi, Better Battery]
http://forum.xda-developers.com/show....php?t=1519161
Make sure you select the mod package that matches your current DPI setting of your Alpha 2 rom and follow his install instructions to the letter.
Good luck!
flash these drivers. should do the trick if you're having wifi issues with the disconnect reconnects.
http://rootzwiki.com/topic/18332-new-wifi-driver-ath6kl-from-compat-wireless/
download the file and flash via Clockworkmod, do a nandroid backup first just in case something goes rogue.
another quick fix, toggle airplane mode. usually gets you back going again. As for rohan's mods, try this first. His mods won't help if you can't keep a stable wifi connection.
I'm having this problem also. Very frustrating! I will try all of this tomorrow and report back. Thanks.
Sent from my Kindle Fire using Tapatalk
This thread has a lot of useful fixes which might help.
Hi everyone! I have updated two days ago my ROM from gingerDX v28 to v28b, and since then I have noticed my phone has started to reboot too often, most of the times when trying to change the network configuration between 2g and 3g through the buttons on the status bar, but also when opening heavy apps. It sometimes reboots from the alfs kernel screen and other times from the gingerDX animation. I have latest alfs kernel, and the alfs addon pack installed. It started also with reboots on the "insert pin code" screen, but that was solved with a full wipe. Does anyone know why can this be happening? May it be an overclock issue? I have the cpu set between 122 and 729 Mhz, and I don't think it's too much because i have had that configuration for a long time and it has never caused reboots. Anyone can help? Thanks in advance.
Edit: solved. It was finally a problem of too many apps installed and running in background causing many low memory situations and lots of errors. B.Jay adviced me to do a full wipe, and now i have installed just the apps I need. Now there are no reboots and the user experience has been improved a lot.
Yes...overclock problem.. disable overclock!
Sent from my E15i using xda premium
maybe low ram is causing the problem..
Try swapping ur SD card..it might help u.
harshitgroup said:
maybe low ram is causing the problem..
Try swapping ur SD card..it might help u.
Click to expand...
Click to collapse
No, in alfs no problem with ram..only for stock
danygarss said:
most of the times when trying to change the network configuration between 2g and 3g through the buttons on the status bar
Click to expand...
Click to collapse
Yes, there is some weird "crash-and-burn" problem when the phone runs 2G ... yarik2720 reported it already (he has a single "blind spot" in the city where he lives where the phone reboots when it falls back to 2G).
Now, to solve the problem it would be insanely helpful to have a logcat from when it happens so I can try and help eagleeyetom to fix it up ... no logcat, nothing we can really do to track down the root of the problem (can't replicate it as I only have 3G (HSDSP, HSUPA, HSPA) all around me - no old-fashioned 2G anymore).
Get a logcat from when it happens it, post it to pastebin, put the link here or PM it eagleeyetom so it can be investigated.
B.Jay said:
Yes, there is some weird "crash-and-burn" problem when the phone runs 2G ... yarik2720 reported it already (he has a single "blind spot" in the city where he lives where the phone reboots when it falls back to 2G).
Now, to solve the problem it would be insanely helpful to have a logcat from when it happens so I can try and help eagleeyetom to fix it up ... no logcat, nothing we can really do to track down the root of the problem (can't replicate it as I only have 3G (HSDSP, HSUPA, HSPA) all around me - no old-fashioned 2G anymore).
Get a logcat from when it happens it, post it to pastebin, put the link here or PM it eagleeyetom so it can be investigated.
Click to expand...
Click to collapse
Thanks for the fast response! I really would like to help with the feedback since gingerDX is a ROM I have been using for 8 months or more, and somehow I have a debt with doixanh and of course the whole new gingerDX team wich has improved it's ROM so much. Sorry for the noob question, how can I have that logcat you talk about? I will try to give feedback next time it reboots. Thanks again!
danygarss said:
Sorry for the noob question, how can I have that logcat you talk about? I will try to give feedback next time it reboots. Thanks again!
Click to expand...
Click to collapse
Get yourself adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll (if you haven't installed the SDK) and put the three files into, for example, C:\Windows. You can obtain the files by downloading the Platform Tools ZIP directly from Google.
Enable USB-Debugging on the phone and connect it to your computer (you need the SEMC drivers installed apparently).
Open the command prompt, type:
adb logcat > C:\Users\<your username>\Downloads\logcat.log
Force the error.
Once it crashed let it boot up ... then press CTRL+C to terminate adb.
Copy/Paste the WHOLE contents of logcat.log to pastebin.com and paste the link here or PM it.
B.Jay said:
Get yourself adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll (if you haven't installed the SDK) and put the three files into, for example, C:\Windows. You can obtain the files by downloading the Platform Tools ZIP directly from Google.
Enable USB-Debugging on the phone and connect it to your computer (you need the SEMC drivers installed apparently).
Open the command prompt, type:
adb logcat > C:\Users\<your username>\Downloads\logcat.log
Force the error.
Once it crashed let it boot up ... then press CTRL+C to terminate adb.
Copy/Paste the WHOLE contents of logcat.log to pastebin.com and paste the link here or PM it.
Click to expand...
Click to collapse
Thanks! Now I know how to get logcats! I have tried it, but today it didn't reboot, bad luck... i have tried changing the network configuration lots of times and forcing to send-receive data by using self messages through whatsapp in both 2g and 3g mode but everything worked fine... maybe it was something related to a network incidence that my carrier (movistar) had here in madrid last days (2g data EDGE network wasnt working), I reported it and they called me this morning to advise everything is now fixed, I tried and now 2g data works. I didn't think that a disconnection from the carrier was related to reboots on my phone's system, so i dindn't mention it in the thread, but since the reboots have stopped the same time as the connection is fixed from the carrier I don't know what to think... Thanks anyway! If this happens again I will try to get another logcat and send to you. I am sending you anyway the logcat of this non-rebooting sesion for if it helps you anyway. Thanks for the hard work and your wonderfull ROM!
Cool, it has solved my problem thanks!:laugh:
Hi, I have SGS I9000 for over 2 years now, and today, I unlocked it and it just started to reboot, by itself. As far as the start goes is moment when it needs to switch between "starting aplicatios" and home screen. Then he goes again into starting android mode (it doesn't turn off completly, just android reeboting). It worked fine before seconds before.
I have MIUI android V4 and I've tried everything, wiping, restoring, but main problem is that I have some unsynced contacts and sms that I need but I can't access them. Can you help me please? (only way I can access internal storage is boot/mount/mount USB, because of the restarting thing)
something must be segfaulting everytime it comes to load the UI, what does adb logcat say?
Could you please tell me how to check adb logcat? I don't know much about phones but I'm willing to learn
unzip the adb package below, open a command prompt in that directory and type adb.exe logcat
you need Android Debug Bridge drivers installed, windows should do the job for you, unless you're on crappy vista
if it gets stuck on - waiting for device - you don't have those drivers
Tank you SuicideFlasher on your replies but I managed everything by my self :victory: I flashed my phone with Odin and got semaphore kernel, but it got stuck in a boor loop again. I then copied restore folder from my computer to internal storage (that i previously saved there), reinstalled CWM with Odin and restored the system that worked (I backup ed all data) and now I completely formated my phone to start over. Congrats if any of this makes any sence but it worked for me :good:
it's good to see beginners trying to fix stuff by themselves :good: you have good probabilites of becoming a dev one day imo
anyway, by using logcat you would just have watched the phone freak out in that bootloop while seeing in detail whatever the log could tell you, but i think that log would have frightened the hell out of you if your knowledge is really that minimal atm
The gnss hwbinder patch have been incorporated into the Aug 25 17.1 builds.
Please take 10 minutes to read all of post #1 and #2. DO NOT USE this thread to report any other problems, it's only for troubleshooting random reboots or reboots into TWRP for S2 exynos5433 tablet users. If this is unreasonable, then stop reading. Thank you.
If you cannot provide the logs below, please do not participate in this thread. Thank you.
I will take a look at all logs uploaded. The more the better to help find root cause or causes.
At this point, I have no solution to fix random reboots, but gathering data that might help narrow down which app or process is causing this.
Instructions
1. If you are experiencing random reboot or reboot into TWRP, you MUST supply tombstone logs. It's super easy and simple to do. Connect your device to PC using micro usb cable.
Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
Bash:
adb root
adb shell
cd data/tombstones
ls -al
# if you see files tombstone_00, tombstone_01, etc then
exit
mkdir t
cd t
adb pull data/tombstones/
Zip all the files and upload here. Alternatively, you can send me the zipped logs via xda PM.
2. The better log would be adb logcat of the problem (random reboot, stuck at boot animation due to random restart) that just happened or happening.
Bash:
adb logcat > crash.txt
# wait 30 seconds then hit ctrl-c to stop capture
Please zip the .txt file before uploading. For some reason, I cannot see .txt files here.
FAQ
Q1. When will this random reboot be solved?
A1. Set your expectations that it will never be solved. At this point, I'm only gathering data to try and help. There may never be a fix if it's due to a proprietary Samsung blob that can never be updated. DO NOT ask when or if this can be fixed. It is not productive and I will completely ignore the question. Thank you.
Q2. Will you provide updates?
A2. I will only provide updates if I think we have found a solution. Otherwise, assume I'm not working on this problem because like you, I have other responsibilities and interests in life.
Q3. What will you do with the logs?
A3. I will look at every uploaded log and try to find a common pattern among them. If I find something that I think it's worth reporting, then I will post it here. If I need more information, I will revise the instructions and ask for more.
Q4. Why are you doing this?
A4. Let me be clear. I'm not experiencing any random reboots myself, I'm just trying to help if I can. The more logs you can provide, the more likely we can narrow down the problem. No logs from the commuity means the random reboot problems will never be fixed.
Let me be clear again, DO NOT ask when or if this can be fixed. Thank you.
Reserved.
Hi @retiredtab,
thanks for your offer to analyze the crash-logs!
I'm using a T810 Tab (gts210wifi) and are experiencing random reboots since updating to lineage-17.1 (ripee).
The reboots itself are of different types:
1) Stuck at bootanimation - only exit by three-button-reset.
2) Reboot to unlock-screen, but after unlock-code endless other unlock-screens come up - only exit by three-button-reset.
3) Reboot to unlock-screen, but after unlock-code the screen is empty and after some time (few minutes) it resets and ends in the same sequence - only exit by three-button-reset.
4) Reboot to unlock-screen, everything ok after unlocking.
For most of the reboots it was my observation, that there was an event, which did wakeup the tablet from deeper sleep (plugin to charger, switching on the screen, alarm, ...).
That caused me to write a small Tasker-app profile, which is pinging my dns-server all 2mins (to prevent a deeper sleep). With that profile active I did not experience any reboot for at least 2 months. Before that I had about one reboot per day.
To support your analysis, I disabled that Tasker-profile and the reboots are back.
During the last 24hours I had two reboots of type 4, and I was capturing the logcat and tombstones afterwards.
Looking into the captured data I got the impression that it might contain sensitive data (found my server-names, calender-events and so on) so I'm unsure if it can contain even more sensitive data like login-information or wifi-passwords.
So I'm hesitating to upload them to this public forum.
Would you agree to receive the zipped logs by PM instead?
Yogi555 said:
I'm using a T810 Tab (gts210wifi) and are experiencing random reboots since updating to lineage-17.1 (ripee).
The reboots itself are of different types:
1) Stuck at bootanimation - only exit by three-button-reset.
2) Reboot to unlock-screen, but after unlock-code endless other unlock-screens come up - only exit by three-button-reset.
3) Reboot to unlock-screen, but after unlock-code the screen is empty and after some time (few minutes) it resets and ends in the same sequence - only exit by three-button-reset.
4) Reboot to unlock-screen, everything ok after unlocking.
For most of the reboots it was my observation, that there was an event, which did wakeup the tablet from deeper sleep (plugin to charger, switching on the screen, alarm, ...).
That caused me to write a small Tasker-app profile, which is pinging my dns-server all 2mins (to prevent a deeper sleep). With that profile active I did not experience any reboot for at least 2 months. Before that I had about one reboot per day.
To support your analysis, I disabled that Tasker-profile and the reboots are back.
During the last 24hours I had two reboots of type 4, and I was capturing the logcat and tombstones afterwards.
Click to expand...
Click to collapse
Hi, @Yogi555.
Your reboot types 2 and 3 are interesting - I haven't seen them happen with my device. I only get types 1 and (occasionally) 4.
And type 5: reboot to TWRP. On my device this has happened more often than type 4, but both are much less common than type 1.
It does sound like the device waking from deep sleep could be triggering these events. Certainly, my device most often goes into type 1 when it's been left alone for a while, such as overnight (so my workaround has been to turn it off at night).
But I've also seen it drop into type 1 while I was actively using it, so waking up mustn't be the only trigger.
Hi, @Ipedia,
Maybe types 2 and 3 are somehow related to the individual homescreen app - I'm using Nova Launcher. Only guessing here.
Regarding type 5: Yes I did see it as well sometimes - but I'm not sure if it is a type of it's own. If I remember correctly type 1 - 3 are rebooting itself after some time of stalling. And - not sure here - after some unsucessful reboots in sequence we end up in TWRP. (In the embedded business where I'm working, it is the desired behaviour to jump to a flashing-bootloader after a number of resets within a certain time).
I've seen the reboots while busy using it as well some time ago, rare, but it happened - but when I activated my described tasker-profile, they were gone as well. I've no explanation for that.
At the moment I'm only facing type 4 resets. I did many changes, since I saw type 1 - 3 (update to latest 17.1 linageos, latest Magisk, exchange of the wifi-blobs) so not sure if any of this solved these reboots, or if they are yet to popup ...
Yogi555 said:
Would you agree to receive the zipped logs by PM instead?
Click to expand...
Click to collapse
@Yogi555 , you can send zipped logs using PM. Thank you.
can you help me to get logs? I receive this error message
Code:
c:\adb>adb root
c:\adb>adb shell
gts210ltexx:/ $ cd data/tombstones
gts210ltexx:/data/tombstones $ ls -al
ls: .: Permission denied
Max_C said:
ls: .: Permission denied
Click to expand...
Click to collapse
Maybe have a look how my adb root problems were solved in this thread: https://forum.xda-developers.com/t/...-version-of-andriod-10.4308193/#post-85353551
Worth a try, but maybe your issue is different
Yogi555 said:
Maybe have a look how my adb root problems were solved in this thread: https://forum.xda-developers.com/t/...-version-of-andriod-10.4308193/#post-85353551
Worth a try, but maybe your issue is different
Click to expand...
Click to collapse
i see, my device not rooted. I need install Magisk first, then enable rooted debugging. I have no rooted debugging in developer options
Magisk is hiding the option - without magisk you should see it - even with an unrooted device
Yogi555 said:
Magisk is hiding the option - without magisk you should see it - even with an unrooted device
Click to expand...
Click to collapse
oh. i see. I have no "rooted debugging" option in my developer settings in Havoc OS
another problem is i have old Android SDK on my PC. I installed latest one, and got this
Code:
c:\adb>adb root
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
I had exactly the same issue with magisk being the one hiding the setting. Are you sure that you are not having magisk installed? Don't know Havoc ...
Max_C said:
oh. i see. I have no "rooted debugging" option in my developer settings in Havoc OS
Click to expand...
Click to collapse
Boot into TWRP then. You can get the same data/tombstones from TWRP using the same commands.
If you have the SM-T710, you will need my TWRP in order for adb to work. The official ones posted on twrp.me don't work with adb or mtp.
retiredtab - Browse /SM-T710/TWRP at SourceForge.net
sourceforge.net
Mine works, but it takes 10 seconds before mtp and adb work after the TWRP home screen is shown.
retiredtab said:
You can get the same data/tombstones from TWRP using the same commands.
Click to expand...
Click to collapse
thanks! got it, please check attached
I have downloaded them, but will examine tomorrow. It's been a long day and it's 12:40 AM. Time for sleep.
After 17 days of gathering data and troubleshooting, we think we may have solved the random reboots. Huge thanks to @lpedia, @CuckooPenguin and @Yogi555 for testing the various gnss patches until we finally figured out the hwbinder solution.
Details at
https://github.com/universal5433/android_device_samsung_gts2-common/pull/4
If you are one of those people who experienced random reboots, it's not too late to submit your data/tombstones or check them yourself for the error message that I listed above. In particular, you are looking for
Code:
#0 pc 00056baa /system/lib/[email protected] (android::hardware::gnss::V1_0::BsAGnssRilCallback::requestSetIdCb(unsigned int)+450) (BuildId: 30ee8b14270ae2b3ae675a7f9b4de136)
#1 pc 0000e8dd /system/vendor/lib/hw/[email protected] (android::hardware::gnss::V1_0::implementation::AGnssRil::requestSetId(unsigned int)+32) (BuildId: d0033c7cb8d0d1a2c99f977719d0d967)
#2 pc 0000fb05 /system/vendor/lib/hw/gps.default.so (broadcom::GpsiClient::marshal_agps_ril_request_setid(broadcom::IpcIncomingMessage&)+160) (BuildId: fe39be024fc2f98450c8d2fc07cda956)
Once the git pull requested is approved, this patch should make it into the next August security patch build for all flavours of the tab S2 including all the variant OS.
Finally, a huge thanks to @ananjaser1211 for tips, suggestions, code and acting as a sounding board for ideas.
retiredtab said:
this patch should make it into the next August security patch build for all flavours of the tab S2 including all the variant OS
Click to expand...
Click to collapse
sorry, I'm not sure i understand how it works... Should I wait when my HavocOS ROM will be updated in this thread? Or there is another way how to apply the patch
Max_C said:
sorry, I'm not sure i understand how it works... Should I wait when my HavocOS ROM will be updated in this thread? Or there is another way how to apply the patch
Click to expand...
Click to collapse
We tried modifying the manifest.xml directly, but the results were inconsistent. On my t710 the instructions below worked, but 2 people with the t810 it resulted in a system not booting properly. These 2 had to reflash the rom to get a working system back. On the t810, the below changed had to be compiled into the code.
If you want to try, backup your data first and be ready to reflash the old rom in case it fails. If it fails, you will have to wait for a new Havoc build or build it yourself.
Bash:
# Turn off gps in OS before booting into TWRP
# boot into TWRP
adb root
# touch mount, system
adb pull /system/vendor/etc/vintf/manifest.xml
# use a text editor and look for this section of code
<hal format="hidl">
<name>android.hardware.gnss</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>IGnss</name>
<instance>default</instance>
</interface>
<fqname>@1.0::IGnss/default</fqname>
</hal>
# change passthrough to hwbinder like so
<transport arch="32">passthrough</transport>
to
<transport>hwbinder</transport>
# save text file
# now push file
adb push manifest.xml /system/vendor/etc/vintf/manifest.xml
# verify that line manifest.xml has changed in the gnss section
adb shell cat /system/vendor/etc/vintf/manifest.xml | more
# Important. Wipe dalvik/art cache and cache
# reboot into OS, enable GPS and make sure GPS works
# Note you may have to go into your setting, apps and wipe cache data as well if GPS doesn't work.
retiredtab said:
We tried modifying the manifest.xml directly, but the results were inconsistent. On my t710 the instructions below worked,
Click to expand...
Click to collapse
Thanks, on my SM-T815 all working fine, I followed your instructions, pushed revised manifest.xml, GPS is working fine. I will test if it helped to solve the problem and leave message here with result in several days.
Max_C said:
Thanks, on my SM-T815 all working fine, I followed your instructions, pushed revised manifest.xml, GPS is working fine. I will test if it helped to solve the problem and leave message here with result in several days.
Click to expand...
Click to collapse
Well, I'm surprised it worked on the t815 when it failed on the t810. That's why I stated it was inconsistent.
So if you were getting daily random reboots due to gnss crashing, then the gnss hwbinder fixes that. We have now had 2 testers go > 150 hours uptime with this patch. Before, they were getting daily reboots/crashes due to gnss (as shown in adb logcat and tombstones).
At first, we thought going 72 hours without a reboot would qualify as a successful fix, but we decided to extend it > 100 hours.
Again, the data/tombstones and adb logcats will show you which process/app is crashing. That's why it's important to view and share them otherwise we would have never figured this out.
Please report back if/when your device reaches 100 hours of uptime.