So I just read a thread asking users that are running the new MR2 if they are still seeing reboot issues. It appears that many people that had reboots before running MR2 are still having reboot issues AFTER MR2. The ONLY people that aren't seeing reboot issues are ones that didn't seem to have the problem before... This leads me to believe that this still could be some sort of hardware issue.
My question is.... Is there anybody that was able to eliminate reboots with a new phone? If new hardware fixes the issue I am ready to go down that route because there sure doesn't seem to be a guaranteed software fix out yet.
Comments anyone??
From what I've been reading, some of the reboot issues may be with the way people have their systems configured for under/over volting and clock speed.
Since every phone is a bit different, so some can handle more extreme setting than others can.
Might be something else causing your issues, but a lot seems to point to the settings.
Related
So what are the pros and cons.... I know about the partition. Are they any other issues with the conversion? If you came back from N4 what made you come back? Cos after the SD card, NFC and LTE fix what else was broken? Thanks in advance.
Googler_1976 said:
So what are the pros and cons.... I know about the partition. Are they any other issues with the conversion? If you came back from N4 what made you come back? Cos after the SD card, NFC and LTE fix what else was broken? Thanks in advance.
Click to expand...
Click to collapse
My main reason for doing the conversion was to get hybrid ROMs like Rootbox or PACman (which weren't available natively on LGOG at the time). To me, really the only pro is a larger selection of ROMs. This isn't necesarily a better selection, just bigger - it depends on what you are specifically looking for in a ROM as to whether this makes it worth it or not.
With the available fixes already posted, there really aren't any huge cons either - GPS works, camera works, you get full internal storage and external SD support. However, there were cases I ran across where I couldn't get certain fixes working with certain ROMs - things like touch key lights not working and the like. I'm sure they are fixable in these cases, it just takes someone smarter than me to figure out how.
I think the main reason the conversion is frowned upon is that there isn't a compelling, across-all-ROMs improvement or feature that would be available on a converted device that isn't available on the 'native' track. So why risk a brick monkeying with partition layouts and potentially dangerous N4 install scripts (apparently some of them flash using partition numbers rather than names, and this will kill ya dead - gotta read carefully. I never ran across one).
I had minimal issues when running converted ( I think I was running that way for 3 weeks or so maybe?? Can't remember). Most of the issues were things that were more annoyances, rather than real usage problems. However, as my main reason for converting was to get a hybrid ROM, once houstonn brought Rootbox to the LGOG natively, I decided to come back. I'm usually a little short on time, and it was getting difficult to keep up with all the LGOG threads, plus all the N4 ROM threads, plus figuring out how to fix the ROMs for use on the LGOG. It's easy here, a one stop shop for LGOG learning, if you will...
I suspect with the native 4.2.2 stuff running around here now, there will be a steady decrease in the amount of 'development' on conversion stuff - it seems quite a bit quieter now than it was a month or 2 ago. I'd rather stay where the action is, as that's usually where the little remaining issues get solved first.
FWIW, I had no issues either converting to, or back from, N4. The threads here do a good job of spelling out the process - it's just a matter of reading through them enough times to understand what is going on and what to expect at each step.
Thanks for writing up your experience... The main reason I asked this question was... Some of the (if not all of them) AOSP Roms have major issues like if GPS works something else will be broken and if something else worksworks other is broken. But I did not see that in N4 conversion. (At least to my knowledge) I'm just talking about just pure aosp Roms. ..is this a trurt statement I'm making? Thanks in advance.
Googler_1976 said:
Thanks for writing up your experience... The main reason I asked this question was... Some of the (if not all of them) AOSP Roms have major issues like if GPS works something else will be broken and if something else worksworks other is broken. But I did not see that in N4 conversion. (At least to my knowledge) I'm just talking about just pure aosp Roms. ..is this a trurt statement I'm making? Thanks in advance.
Click to expand...
Click to collapse
I can't say for certain - most of these 'tradeoff' issues, at least from what I've seen, seem to revolve around which modem you choose to run. I believe, at the moment the only 100% no issue setup is and ICS ROM with ICS modem. I believe these issues persist whether you are on N4 conversion or native LGOG setup - but I could be wrong here.
Here's the basic breakdown - somebody correct me if I'm wrong on these, I haven't run most of these setups personally:
If you run ICS modem on JB ROM, you get broken GPS.
If you run .33 N4 modem you get good GPS and Data speeds, but occasional data drops. Also, apparently you can't make outgoing calls in LTE coverage. You can fix the data connection by toggling airplane mode. This isn't a huge issue for most people, but is for me as I use Google voice and IM apps for messaging (rather than SMS) so if I don't notice the data drop and toggle, I'm missing messages.
If you run ATT JB modem on JB ROMs you get working GPS, decent data speed, and working LTE calling. All Outgoing calls drop to a background process after initiation, so if after hitting dial you need to interact with the call, you have to open the notification drawer and then click on the call to foreground it. Does not impact actual functioning of the call. Network name is reported as 'maritime' rather than AT&T.
I think there's another N4 modem that will work with LTE (.27 maybe - somebody jump in here) so that might be another option...I haven't tried it. there is one N4 modem that breaks LTE support.
I've been almost exclusively on houstonn's RootBox since coming back to native setup - so I may have missed issues with other ROMs - I do try to keep up with all the threads though. Hopefully someone else on one of the others can chime in with other issues, if there are any, that I missed. FWIW, I have never lost GPS on my device...I'm not sure why some have and some haven't...
http://forum.xda-developers.com/showthread.php?t=2270319
One stop shopping for all your radio needs.
Thanks again both of you... t I wanted to know why and I think I got what I was looking for.. Anyway, I guess I will stick with my rooted stock JB for now till some of these issues get resolved. Thanks again for all your time.
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
my wife and I both have i777's, and I keep them rom'd similarly always, although I do a lot more experimenting with my own.
I recently found a few behavioral differences inbetween hers and mine, even though the most recent installs were after rom-wipe scripts, and TiBU restoraton of user apps only.
when I nfc-beam photos to hers, hers does not ask any permission, and the beam always completes successfully.
when I nfc-beam from hers to mine, It starts, then I am asked permission, and it fails after I grant permission.
the issue occurs whether we are on the same (cm) or different kernels
The only thing that I truly recall doing grossly differently with mine, is that I tried out a 4.3 rom recently, and then went back to cm10.1.3.
Once I noticed the issue, and couldn't correct it with a cleaning and re-rom, I even Odined back to stock, then started the whole process over, but still the NFC-beam/bluetooth issue remains.
currently we are on cm10.1.3 stable, I've googled the hell out of it, but others' issues don't seem to be the same, and their resolutions didn't help me.
any ideas?
Sorry, cyril, like you I've never heard of this. The best I can do is offer a few thoughts...
- The first culprit would be the CM nighty you're both running. Has your NFC problem always existed, or just since you installed CM?
- Do you both have the same battery, or is one different than the other? Specifically, are they OEM?
- Do you have anything remotely related to NFC turned off via autostart or something similar?
As you can see these are all guesses, hopefully whatever trouble you're having will correct itself.
Sent from the i777
I don't mess with cm nightlies at all; we both went from 10.1.3 rc2 to stable. I didn't notice when the issue began, because I really don't use the feature very often, and didn't even try it until installing cm.
Same battery? No clue, I haven't replaced them, I expect that they're OEM, but I'll pop them from their cases later to verify.
Nfc feature Turned off? I'm not sufficiently android savvy to have done anything intentionally, but I'll look up "android autostart" and see where it leads me...
No, don't worry about the autostart. I was referring to using a 3rd party app to control what starts up at boot; there's no way that's the cause if you're not familiar with what I was suggesting, because it's something you have to do manually.
Sent from the i777
My dad (who uses an iPhone) and a few other people have been complaining that whenever they call me, they get really bad static or sometimes even echoed feedback during phone conversations. I've tried multiple different ROMs and he says it still happens sometimes. What confuses me is that its kind of random when it happens because other times it'll work perfectly. The mic isn't broken or damaged because recording apps don't have this problem. Is it something in my settings and/or the ROM causing this? Any feedback is appreciated.
I'm currently using the latest shoshock ROM and have in the past been using tasks AOKP, which is where it first randomly started.
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Phalanx7621 said:
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Click to expand...
Click to collapse
I used the default one that was in the flash able zip. Unlike most ROMs, it was an all in one package so nothing else was required.
First, you want to know if this is an intermittent hardware issue. The troubleshooting test for that is flash back to stock and observe. If the problem is still present, then it is very likely to be a hardware issue.
If not, then the problem is most likely in firmware somewhere. Since this is not a common problem, and since you have had it on multiple roms, it would probably not be due to the kernel or system firmware, so you would have to look at applications to see what might be interfering.
I would have posted this in CDMA dev, but I don't have enough posts yet. First, ROMS like dastin's CM11 ROM usually list "Standard CM11 Issues" under issues. However, I've never been able to find a comprehensive list of "standard" issues for CM release since CM only has wiki entries for supported phones (which does not include CDMA 3D/V 4G). I'm running Angrybean CM10.1/AOSP/AOKP, and only vaguely knew "standard" CM10.1 issue for this phone usually meant no MMS. I only discovered that issue by happening upon a thread post skimming through a lot of threads. So, is there a place where "standard" issues gets documented, or is this one of those "if you read a lot of posts in this forum, you'll understand what 'standard' is"?
Also, ever since Gmaps 7 came out, I've had flickering/glitching/screen tearing issues that some people seem to have. I've tried a lot of the recommended fixes, which usually include disabling HW overlays, forcing GPU rendering, reinstalling, or downgrading to Gmaps 6 (not a solution in my eyes). Just wondering if anyone has found a definitive answer as to why this happens, and what the solution is, because I see the same issue has popped up in dastin's CM11 ROM. I'd love to flash CM11, but the flickering is driving me crazy.
Thanks for any info or help you can give me.