Related
Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?
Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.
Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?
I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?
One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...
For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms
Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.
For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
OK, after following the well worn mantra of "If it ain't broke, fix it until it is", I have found myself in an odd position.
My phone only lasted in stock format for around 45 minutes when I bought it about 8 months ago. It was rooted and flashed straight away and has been working well ever since. However, last night I decided to fiddle about with a few things and found myself in a bit of a pickle where I was S-On with the **security warning** error at boot. After a few heart stopping moments and 5 minutes of reading I was able to resolve this and revert my phone back to stock running 2.3.3 and Sense 2.1. To be honest, this had been where I'd been planning to get to but not quite by the route I took but hey-ho, I got there in the end.
Anyway, I know I can simply re-root my phone etc and flash a new rom etc but I wanted to play with the phone in stock format for a while so I could get some comparisons against what I was familiar with in custom roms.
After the usual boot up and adding in gmail account details etc, everything was up and running. I launched Market and expected things to start happening but other than getting a handful of updates to stock items nothing else happened - more specifically, Market did not update to Google Play. No matter how many times I went in and out it stayed as the very old Market.
I then tried to get any OTA updates (of which I know for a fact there is at least one) but my phone reports that it is up to date and no updates are available.
So, while I know I can go back to custom roms I still want to have a play with a truly stock phone - but not quite such an old one. Does anybody have any suggestions about how I can kickstart my phone to get it to the state it 'should' be in with the latest version of GB and Play?
mr nick said:
OK, after following the well worn mantra of "If it ain't broke, fix it until it is", I have found myself in an odd position.
My phone only lasted in stock format for around 45 minutes when I bought it about 8 months ago. It was rooted and flashed straight away and has been working well ever since. However, last night I decided to fiddle about with a few things and found myself in a bit of a pickle where I was S-On with the **security warning** error at boot. After a few heart stopping moments and 5 minutes of reading I was able to resolve this and revert my phone back to stock running 2.3.3 and Sense 2.1. To be honest, this had been where I'd been planning to get to but not quite by the route I took but hey-ho, I got there in the end.
Anyway, I know I can simply re-root my phone etc and flash a new rom etc but I wanted to play with the phone in stock format for a while so I could get some comparisons against what I was familiar with in custom roms.
After the usual boot up and adding in gmail account details etc, everything was up and running. I launched Market and expected things to start happening but other than getting a handful of updates to stock items nothing else happened - more specifically, Market did not update to Google Play. No matter how many times I went in and out it stayed as the very old Market.
I then tried to get any OTA updates (of which I know for a fact there is at least one) but my phone reports that it is up to date and no updates are available.
So, while I know I can go back to custom roms I still want to have a play with a truly stock phone - but not quite such an old one. Does anybody have any suggestions about how I can kickstart my phone to get it to the state it 'should' be in with the latest version of GB and Play?
Click to expand...
Click to collapse
Here is the latest WWE GB 2.3.5/Sense 3.0 RUU
http://bit.ly/HlnQ0J
tpbklake said:
Here is the latest WWE GB 2.3.5/Sense 3.0 RUU
Click to expand...
Click to collapse
OK, I'm downloading this now and will give it a whirl. I'd still like to try and figure out why my phone won't update from its current state. It is a Virgin AU phone and I used their RUU to flash it so it is essentially back to the state I got it out of the box.
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Cabtn said:
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Click to expand...
Click to collapse
Did you make any mods?
Also, are you using any new apps you didn't before flashing CM10?
Did you factory reset when you flashed CM10?
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Cabtn said:
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Click to expand...
Click to collapse
Which version of Semaphore did you flash? Also, are you on CM10.1 or CM10?
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Cabtn said:
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Click to expand...
Click to collapse
Alright, that's CM10.1. Just wanted to make sure you were using the right version of Semaphore for it.
You could try changing your governor and scheduler (I think I used SmartassV2 and noop on my cappy). If nothing works, flash back to stock after a good backup is probably the best solution (Odin KK4 without bootloaders). Start fresh from there.
Thanks! I'll give it a try
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Cabtn said:
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse
Odin KK4 without bootloaders: http://hotfile.com/dl/137871658/d25...O_Bootloaders_Re-partition_Full_Wipe.zip.html
Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Note 4 sucks after this MM update it is worst than any other small budget phone.
anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
So you'd recommend going back to stock kitkat?
SamC95 said:
Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Click to expand...
Click to collapse
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
robmeik said:
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
Click to expand...
Click to collapse
Thanks for you reply.
Seems like a nice ROM, would want to flash it, but seems like I'm not going to be able to flash new ROMs (due to the problem described above.
I had the same problem. you must have the newest version of odin.
DrQuestion said:
I had the same problem. you must have the newest version of odin.
Click to expand...
Click to collapse
Seriously? Is it that simple lol? I'll try that, thanks.
EDIT: Turned out it wasn't that simple, got the message 'There's no PIT partition.'
anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
I've been running Marshmallow on my N910C since it was released for my device, and I haven't experienced any major problems with it. Other than not getting the official OEM spare battery to charge correctly on it. Everything is work just fine.
I've been running the MM PaulPizz Rom for a few days and it's been rock solid so far. Not a single crash or error.
SamC95 said:
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Click to expand...
Click to collapse
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
SamC95 said:
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
Click to expand...
Click to collapse
I always use 3.11.1 straight from Sam mobile site. Here http://dl.sammobile.com/Odin3-v3.11.1.zip
Never had a problem with it.
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
After trying myriad of roms(Almost all roms from Snapdragon section) + kernels, I prefer Stock rom for it's batterylife + stable performance. I haven't rooted after returning to stock. But i will return some sort of custom rom soon as my phone looks so boring without ported apps, multi dpi compatible apps, etc. If u prefer stable performance move to pure stock, If u need assortment of features use one of the ported note7/S7 roms, If u want slick and fast roms use AOSP/CM based roms but as far my experience goes they are not much stable while compared to touchwiz.
Currently running latest MM stock on 910G.
Stonewolf said:
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
Click to expand...
Click to collapse
Using Odin 3.11 to downgrade from MM to KK works just fine. I just did 2 days ago.
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Stonewolf said:
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Click to expand...
Click to collapse
Have you tried 3.12? It's the only one that worked for me.
back to lollipop .......... one of the best Note 4 ROM ever build ...........
Been using Nameless ROM V7 ............
aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
This did the trick, thanks a lot! I finally got to flash TWRP and ended up installing Alexndr ROM (thanks for the tip @robmeik) but sadly I'm still having random reboots