Database Users

[Q] Lockscreen Reboot Issues

I've been having lockscreen reboot issues with the last few Fission roms, and a couple of Matt's. Has anyone else had this problem and resolved it?
I followed the installation instructions and even formatted my SD card. I'm going to try to SBF before I install the next Fission, is there anything else I can do to completely clean out my phone? Such as wiping some system files in recovery or something.
The only data I have left over from other ROMs is backups I made of a few games like Angry Birds.
Any suggestions are appreciated, I've been trying to fix this issue for awhile!

Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?

mikeyinid said:
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
Click to expand...
Click to collapse
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?

kdog349 said:
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
Click to expand...
Click to collapse
I never sign into google until after the hard reset. But I dont know if that matters. Next time you flash a rom, try wiping data and cache in recovery, after flashing, but before you reboot. And, are you overclocking or undervolting?

I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.

kdog349 said:
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
Click to expand...
Click to collapse
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...

mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!

mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!

Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.

mjones1052 said:
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
Click to expand...
Click to collapse
Personally I had a Droid 1 for 6 months and don't remember having any lockscreen reboots, at least not at the frequency of 2-3 a day that I'm having now. Could run the phone for a week without rebooting.
There were a couple of D2 roms that didn't have the reboot issue for me, but most do so maybe it is an issue with the phone like you say. I Don't understand their persistance with motoblur either At least take out eFuse if you're going to throw on motoblur

I've been trying lockbot free to solve my reboot issues. You can basically set it to be exactly the same the normal lockscreen, and so far it seems to be working for me.

I had this problem. Random, intermitten soft reboots during slide to unlock. Ran multiple roms, always had the problem. But I was always removing the same things after sbf. I had found one Dev to seem to find this to follow the music.apk file. So this time I left it on. On my last sbf, I left that in there. Havent had a problem since. Before that I had tried what I thought to be everything, multiple sbfs, multiple roms, completely formatted sd card, and re-sbf'd again. But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!

But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
Click to expand...
Click to collapse
Which music.apk is this? Is it the D2's original application or the google music app? Because I've never taken the music app that's been on the phone or came with any ROM and I've had a few not a big number but a few.
Sent from my DROID2 using XDA App

Not sure what the google music one is, but the file is named music.apk

Please clarify this lol. Mine was working great until I installed that damn black theme for fission rom.

I've had a droid1 and I have never had reboot issues with roms before. I think it may just be a d2/x problem
Sent from my DROID2 using XDA App

Yeah the same thing happens to me. I'm pretty sure the dev's for Fission know about it, so hopefully 2.2.1 from them fixes it.
Sent from my DROID2 using XDA App

I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.

Im just curious, are you guys only experiencing these reboots with the non-blur roms, or have you experienced them with other roms also? I have only had one reboot, and that was running fission 2.2.1.

tonorice said:
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Click to expand...
Click to collapse
Was it the "Android_Music.zip" or "D2_Music.zip"?

internet/data issue due to different rom?

Anyone here seeing some data issues on the D2 running Fission? I am in a major city, and it seem like I am kind of having some data issues since I starting running Fusion, specially when browsing the web. The internet seems to lag a bit, and connection seems a bit slow(good bit slower than normal). I got a message few times relating to the data connection. I want to say this could be a network issue, but my sister with a Droid Inc, says here data is fine? Any ideas?

Called VZW today up asking if there was an issue on their end, and they said no. Tech then told me to take out the battery for 10-15 seconds and they try the internet when back on. Tech said it could be due to the phone not properly switching from one tower to another. It did work, but about 2 hours latter I was having the same connection issue where pages would no open up, and data was a bit on the slow side. Did the same method again, and that worked. I didn't have this issue on the stock D2 rom, or with my Eris(well that always dropped 3G reception, this is full bars with connection problem). Could this be due to me being on Fission 2.2.2, or is it whole different matter not due to being in Fission? Thanks

tbaker077 said:
Called VZW today up asking if there was an issue on their end, and they said no. Tech then told me to take out the battery for 10-15 seconds and they try the internet when back on. Tech said it could be due to the phone not properly switching from one tower to another. It did work, but about 2 hours latter I was having the same connection issue where pages would no open up, and data was a bit on the slow side. Did the same method again, and that worked. I didn't have this issue on the stock D2 rom, or with my Eris(well that always dropped 3G reception, this is full bars with connection problem). Could this be due to me being on Fission 2.2.2, or is it whole different matter not due to being in Fission? Thanks
Click to expand...
Click to collapse
Im running 2.2.2 and im not having that issue. My girl has a D1 and she gets the same crappy service i get i really dont think its the rom. And i dont think there is enough of a difference between 2.2.1 and 2.2.2 to have one get different reception than the other
Shot from my level 60 crossbow of awesomness!

Maybe it just my phone then? I guess will see what I can do.

Have your tried a root reset with a reinstall?

I have been having this problem, Data will just stop working all together. Text messages won't get sent or delivered. The 3G icon just shows uploading and not downloading or stops showing anything at all. I can't fix it unless I turn on Airplane Mode then back off or reboot the phone. Right now I'm running Fission 2.1 but I ran into Data issues with the default R2D2 rom.

volcanomike said:
I have been having this problem, Data will just stop working all together. Text messages won't get sent or delivered. The 3G icon just shows uploading and not downloading or stops showing anything at all. I can't fix it unless I turn on Airplane Mode then back off or reboot the phone. Right now I'm running Fission 2.1 but I ran into Data issues with the default R2D2 rom.
Click to expand...
Click to collapse
So the issue your having is not related to a fission rom...

So, I may have solved the issue. I started clean again; cleared all data and status and stuff, then reinstalled 2.2.2, and then hard rested. Only thing I did different was not install the black status bar and all seems fine, and data seems normal.

tbaker077 said:
So, I may have solved the issue. I started clean again; cleared all data and status and stuff, then reinstalled 2.2.2, and then hard rested. Only thing I did different was not install the black status bar and all seems fine, and data seems normal.
Click to expand...
Click to collapse
I hate to say this man, but from my experience, the more "stuff" you throw on top of a rom, the more bugs your gonna encounter. And youll never have the same bug twice...

Why is that?

Mackattack said:
Why is that?
Click to expand...
Click to collapse
Why is what?

The issue may have arisen again, but I was on the market, so it not clear if that was the market issue many people are facing or it was a data issue.

mikeyinid said:
Why is what?
Click to expand...
Click to collapse
More stuff you put in the more bugs you encounter.

Mackattack said:
More stuff you put in the more bugs you encounter.
Click to expand...
Click to collapse
Im not a dev or anything, but here is an example. I was having problems with a rom i was running last night, reboots and such. The very first thing the dev who made the rom asked me was if i was running a theme. Now, im not saying you shouldnt use custom themes or addons with these roms, but every device is different and will react different. And when your flashing 3-4 different themes over a rom trying to find one you like, or flashing addons then trying to undo them your gonna create some issues. Of course, and i remind you again that im not a dev, this is completely based on my experience, and opinion

I guess with themes that can make sense. I wonder what team defused has to say about this?

Odd Problems with HTC Hero CDMA

I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?

rjhall said:
I have this weird problem, and I can't figure out the cause.
And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.

rjhall said:
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?

il Duce said:
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
Click to expand...
Click to collapse
1. Yeah I know that. I hadn't had this problem until the last couple months. Until then, it was more or less okay. The problem is, it really is a completely fresh rom.
2. The Hero is kind of a low memory phone to begin with, so that's certainly a possibility. 2.2 and 2.3 aren't exactly kind on old hardware.
3. I don't have those settings in 6.1.0. I was using SetCPU for awhile with it at 480-7XX (Can't remember, I think 791, as that was max) and OnDemand. I had some screen off, temperature, and battery profiles too.
4. Any specific threads I should read you can suggest? I was lurking on the forums for awhile before I did anything to my phone (didn't want to brick it).
5. I'm currently using Amon RA 1.6.2. I considered clockwork, but some people said it has more problems. I've heard complaints that Amon RA requires signed packages, but frankly it hasn't been a problem thus far. It actually saved me from bricking my phone when I was new to this whole thing. As for what I wiped, I simply went through Amon RA and wiped data, dalvik, battery stats and rotation. Don't know what battery stats/rotation are, but I am familiar with the Dalvik cache.
6. As for saying I could have messed something up, when I was flashing my phone, it was something I'd never done before. It's certainly possible I mistyped something or screwed something up.
I was hoping someone could help me to completely wipe it and start fresh, since I'm sure it's had its share of problems.

I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?

also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.

Bierce22 said:
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Click to expand...
Click to collapse
Are you aware that the performance governor runs at the MAX CPU speed all the time? Seriously. Your battery life must suck.
sent from a series of tubes.

yea but otherwise my performance sucks lol.
most of the time on aosp and cm7 i cant even stream music without it freezing unless i set it to performance.

Houndog101 said:
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
Click to expand...
Click to collapse
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
oohaylima said:
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
Click to expand...
Click to collapse
I tried using RomManager to flash Clockwork, and it still booted to Amon RA recovery. I'm going to try to use ADB to do it, but I don't know that I'll be able to.
EDIT: Manually pushed ClockworkMod Recovery v2.5.0.7 onto my Hero.
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?

hmm thats very weird thats just about the only thing rom manager is good for now adays is installing cmr

rjhall said:
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
Click to expand...
Click to collapse
You will not brick, that is how you wipe. You should also wipe dalvik cache. Go to this site for really good instructions :
www.romrepo.info/wiki

But please note when u wipe u "wipe" lol you will loose all your market apps and anything else installed just make sure you dont wipe sd card then youll loose all your photos and music backups exc...

rjhall said:
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
Click to expand...
Click to collapse
So I downloaded the 2.1 update from the HTC website, ran it, and it completed with no problems. Phone booted up, and now I'm trying to go through the tutorial, lagging all the while. It's almost impossible to type.
Does this mean it's hardware related?

sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.

Bierce22 said:
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Click to expand...
Click to collapse
I had to start from scratch several times and my phone was pretty snappy when I first started it up after RUU. Also you stated your phone was fine and then just started running slow for no reason, was this after it took a bump?

are you talking to me or rjhall lol

Bierce22 said:
are you talking to me or rjhall lol
Click to expand...
Click to collapse
sorry, RJhall..

I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?

rjhall said:
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
Click to expand...
Click to collapse
Never had mine apart, maybe someone has and can help..

Okay so things have gotten increasingly weird. It used to be that squeezing the sides of the phone allowed the touch screen to work. Yesterday that stopped working altogether. Today, the screen stopped turning on at all. The LCD simply doesn't turn on. Pressing the red button turns on the phone (it vibrates when turning it on) and when the phone is on, pressing the red button lights up the keys (so I know it's waking the phone up). I took the phone apart (much simpler than I thought it would be) but I was unable to find anything that seemed out of place or broken. Does anyone have any ideas?

typing too fast; keystrokes not registering

hey guys
does anyone else have a problem with their atrix, where if you type extremely fast (2-3 char per second), the atrix does not register the key?
i'm not talking about they normal keyboard lag (type and then then 3-4 sec later it shows up on the screen, got rid of that by turning off haptic feedback), my issue is that when I type fast, i can see the popup for a key, but it won't register on the screen.
for example, if i type happy, i would see the popup on the keyboard for each individual letter (H A P P Y), but it would only register H P P Y, almost like the multitouch isn't working properly.
the effect is very pronounced on aftermarket keyboards (i've tried a lot, ICS, GO, swiftkey), and they are all WORSE than the stock keyboard. the simplest fix is to type slowly, but that just ruins my train of thought.
can anyone help?

rp_guy said:
hey guys
does anyone else have a problem with their atrix, where if you type extremely fast (2-3 char per second), the atrix does not register the key?
i'm not talking about they normal keyboard lag (type and then then 3-4 sec later it shows up on the screen, got rid of that by turning off haptic feedback), my issue is that when I type fast, i can see the popup for a key, but it won't register on the screen.
for example, if i type happy, i would see the popup on the keyboard for each individual letter (H A P P Y), but it would only register H P P Y, almost like the multitouch isn't working properly.
the effect is very pronounced on aftermarket keyboards (i've tried a lot, ICS, GO, swiftkey), and they are all WORSE than the stock keyboard. the simplest fix is to type slowly, but that just ruins my train of thought.
can anyone help?
Click to expand...
Click to collapse
yeah I noticed this too, it seems like the multitouch doesn't work properly. What ROM are you using? I'm on WetDream 1.2 still. I don't know why it's this way but it makes me very sad. It's very annoying. Anyone else have this?

I have this problem as well. I went on a rampage downloading a million different keyboards, but to no avail.

I have the same problem. Could it be the digitizer?

Are you guys running any CM9 ROM? If so, that's your problem. Since these ROMs are using older drivers that are not made for ICS, you are going to face these problems until Motorola....more like MotoLOLa....releases the ICS drivers later this year.
Sent from my MB860 using XDA

TheMan0790 said:
Are you guys running any CM9 ROM? If so, that's your problem. Since these ROMs are using older drivers that are not made for ICS, you are going to face these problems until Motorola....more like MotoLOLa....releases the ICS drivers later this year.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I accidentally hit the "thanks" button when I meant to hit "quote" but anyways, I'm using cm7 and this problem happens on every different rom that I have tried. I have never had so much problems with a new phone before that I'm starting to think that motorola can't even make phones that work anymore.

Yes I believe the problem is poor implementation from Motorola.
IF you use the stock keyboard (the multittouch one) this problem goes away. Just figured this out this morning.
I am using a blur based stock rom (one of nottach's) so I still have that keyboard available. I think this will be enough to keep me on stock based roms or at least roms that will have that keyboard.

Atrix_Owner said:
I accidentally hit the "thanks" button when I meant to hit "quote" but anyways, I'm using cm7 and this problem happens on every different rom that I have tried. I have never had so much problems with a new phone before that I'm starting to think that motorola can't even make phones that work anymore.
Click to expand...
Click to collapse
That is very weird. When I was using CM7, I never faced any keyboard issues. It kills me that the Atrix's worst keyboard, IMO, was when I was using stock GB. Absolutely the worst thing ever.
Sent from my MB860 using XDA

bump for more attention.

I've always had this issue on every ROM with every keyboard I've ever used including the stock Motorola one. I just chalked it up to the multitouch not working since it doesn't seem to work correctly for anything.
Sent from my MB860 using XDA

I've only ever had this problem with the stock ICS keyboard on a CM9/ICS Rom, the 'solution' was to disable either the keyboard's or android's spelling correction. Can't say I've know exactly what's causing it on anything else, I'm afraid.

[Q] Phone locks up and restarts with navigation - overheat it seems?

I've been noticing this problem increase over the past few months. It started when I used navigation over longer trips like an hour. The phone would all of a sudden stop responding and then just restart. I noticed its really hot when this happens so I figure it's overheating. Recently it even happens on short trips.
I'm using triforce rom 3.1 which uses agat's kernel. I have not noticed any other restart or crashing issues aside from when I use navigation. I find it important to mention that this all occurs even if the phone is not plugged in or charging.
Has anyone else noticed something like this?
I thought about taking it to sprint since i have tep, but I figure they will either just tell me it's my fault since it's a custom rom or just offer to format the phone like they do with every other problem.
Any ideas are appreciated.

Not an expert, but sounds KERNAL related....try a differant kernal...
Sent from my SPH-L720 using XDA Free mobile app

chris-allen said:
Not an expert, but sounds KERNAL related....try a differant kernal...
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the tip. I'll have to find one that still works with my older version of the rom. If nothing else, I may just wait until I have a little more time and use a new or different rom all together and see if that makes a difference.

iivisionii said:
Thanks for the tip. I'll have to find one that still works with my older version of the rom. If nothing else, I may just wait until I have a little more time and use a new or different rom all together and see if that makes a difference.
Click to expand...
Click to collapse
I just wanted to follow up and see if anyone had more suggestions or a specific kernel to try. I tried 3 different ones with the following results:
KT-SGS4-JB4.2-TW-SPR-02.20.2014 - No navigation reboots, started rebooting randomly otherwise
AGAT_GS4_v0.5.1 - Still reboots/overheats during navigation
AGAT_GS4_v0.5.2 - Still reboots/overheats during navigation

Stock. I've never had good luck on custom kernels going back to the S2 (the same devs as currently).
Really, my devices have always ran worse and with significant issues, including the one you are describing.
If that's not an option, play with the governor settings, remove any overclock, and try other ROMs.