Related
I just fresh flashed to EaglesBlood
WiFi calling seems to be stuck. It says "enabling" but it's stuck on this forever.
I did a reset (just in case) - didn't fix it
any thoughts?
Thanks!!!
Wifi calling is notoriously bad. It will work fine for some and barely ever work for others. My completely stock 2.3.3 had the same problem time and time again, as does my phone in its current setup. I believe the problem is external.
Sent from my LG-P999
e4e5nf3nc6 said:
Wifi calling is notoriously bad. It will work fine for some and barely ever work for others. My completely stock 2.3.3 had the same problem time and time again, as does my phone in its current setup. I believe the problem is external.
Sent from my LG-P999
Click to expand...
Click to collapse
Thank you. That's so odd, during the night (did you notice XDA was down for maintenance?) i switched to Weapon ROM and the WiFi issue persists. Yet my wife's phone, the Vibrant, stock rom of course, does the WiFi thing every time and right on the money. Damn it LG!
I think I remember reading that it was having trouble switching DNS servers when needed or something along those lines. I found plenty of feedback on these forums if you want to do a quick search and see if you can dig anything up.
(Yeah, I noticed the forums went down for a bit. I was in the middle of something at the time and really needed links!)
e4e5nf3nc6 said:
I think I remember reading that it was having trouble switching DNS servers when needed or something along those lines. I found plenty of feedback on these forums if you want to do a quick search and see if you can dig anything up.
(Yeah, I noticed the forums went down for a bit. I was in the middle of something at the time and really needed links!)
Click to expand...
Click to collapse
Thx!
Tsugi ROM solved this it's no working!
(yes I am on a ROM chase - I have some free time so I decided to not give up until I make this device owned!
So to sum it up, I don't personally have a skyrocket, but I have a friend who looks to me for custom roms, root, etc for his skyrocket. I've been doing the ROM flashing thing for like 3 years and I've never had issues. Yet it seems every time I flash something to his phone I'll get a call a month or so down the road saying its unbearably slow or that it takes minutes to make a phone call. Is there some step that I've been missing? How does this always happen? I realize they're different phones, but I've flashed countless roms for multiple periods of time on my Xoom, Gnex, and Eris without any issues. Can anyone shed some light on this? Its been driving me crazy.
Thanks for any help,
Ryan
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
So to sum it up, I don't personally have a skyrocket, but I have a friend who looks to me for custom roms, root, etc for his skyrocket. I've been doing the ROM flashing thing for like 3 years and I've never had issues. Yet it seems every time I flash something to his phone I'll get a call a month or so down the road saying its unbearably slow or that it takes minutes to make a phone call. Is there some step that I've been missing? How does this always happen? I realize they're different phones, but I've flashed countless roms for multiple periods of time on my Xoom, Gnex, and Eris without any issues. Can anyone shed some light on this? Its been driving me crazy.
Thanks for any help,
Ryan
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Can you expand on what is slow? If it is just apps MOT UISNG internet, then his process memory/cache/whatever is gettiing full. Does he ever reboot the phone? Restarting the phone clears memory and will do wonders.
If he is using any app like Task killer or Task manager then he is screwing things up. With the the SGS II, there is no need to kill processes, since that only worsens things.
If he restarts phone, does it recover its speed? Can u check that?
EDIT: If it is internet - i do not see how that could be related to making a call, but still otherwise - then he is being throttled.
Thanks I'll text him and see what I can find out. As of now I think he's running the modified leaked ICS roms that came out like a day after the leak. We live on opposite sides of the state so I rarely see him.
**Edit: there's no way he's being throttled. He's the most data conscious person I know. Barely used 300mb of his 2gb the last few months.
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
Thanks I'll text him and see what I can find out. As of now I think he's running the modified leaked ICS roms that came out like a day after the leak. We live on opposite sides of the state so I rarely see him.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The very first ROMs of the ICS leak had a lag problem. The newer ones quickly got rid of that.
This is a copy paste of his response asking what was wrong:
"I'm not using a task manager at all. First off, the phone freezes every so often and it shuts down by itself when it freezes. That aside, I've rebooted the phone literally dozens of times because it starts acting funny...like, apps will randomly stop working, the home button won't work, etc. Then adding to that, the phone feature is soooooooooo slow. If I tap on the phone to make a call, it takes about 5 seconds to open. Then any numbers I punch in take about 4 to 5 seconds each to appear. If I want to call somebody out of my call history list, it will take at minimum 5 seconds to open, and then selecting the person to call can take up to 10 seconds to respond. Finally, the home screens lag somewhat when I scroll between them and the lock screen is always on, no matter how many times I turn it off. Lol kind of a lot of problems huh?"
So new ICS ROM seems to be the general consensus? Thanks again guys.
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
This is a copy paste of his response asking what was wrong:
"I'm not using a task manager at all. First off, the phone freezes every so often and it shuts down by itself when it freezes. That aside, I've rebooted the phone literally dozens of times because it starts acting funny...like, apps will randomly stop working, the home button won't work, etc. Then adding to that, the phone feature is soooooooooo slow. If I tap on the phone to make a call, it takes about 5 seconds to open. Then any numbers I punch in take about 4 to 5 seconds each to appear. If I want to call somebody out of my call history list, it will take at minimum 5 seconds to open, and then selecting the person to call can take up to 10 seconds to respond. Finally, the home screens lag somewhat when I scroll between them and the lock screen is always on, no matter how many times I turn it off. Lol kind of a lot of problems huh?"
So new ICS ROM seems to be the general consensus? Thanks again guys.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is his current data very important to him? Looks like a sub-optimal flash. It happened to me before - the exact symptoms. Since he is far off from you, he can do the following:
1. Reboot to CWM recovery.
2. Wipe data/factory reset.
3. Wipe dalvik cache.
Of course his favorite apps will be gone......
The more sure way is to reflash, but this time do the above steps along with Mounts&storage>>Format>>system, data, cache
Then reflash the ROM. Of course again his favorite stuff will vanish,
To avoid this he can do a nandroid backup, or Titanium bakup, but then replacing those apps back MAY re-corrupt his system.
Will check back later.......
EDIT: ALso, in some ROMS if you flash radio, kernel and ROM separately, the order matters.
I can figure out a way to back his apps up if I tell him how to use TiBu right? I'll be skyping him later thus weekend to try and figure it out. If he wipes this way it won't erase EVERYTHING on the internal storage right? As in camera pictures will be saved correct? Ill try to walk him through a CWM flashing, shouldn't be too difficult. Any ROM suggestions you have currently for me, prioritizing stability over most everything? Thanks again.
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
I can figure out a way to back his apps up if I tell him how to use TiBu right? I'll be skyping him later thus weekend to try and figure it out. If he wipes this way it won't erase EVERYTHING on the internal storage right? As in camera pictures will be saved correct? Ill try to walk him through a CWM flashing, shouldn't be too difficult. Any ROM suggestions you have currently for me, prioritizing stability over most everything? Thanks again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Screw backing up his apps. There is issues with restoring apps and ICS. He should reinstall the ROM or download a new one. And no, pictures and media won't be touched. And I recommend the latter.. Embryo 2.1 is amazing and silky smooth and I have zero issues with it. Had a few that I quickly fixed
Sent from my SAMSUNG-SGH-I727 using xda premium
Are you implying there's issues restoring for ICS and the skyrocket? That would be understandable maybe, but I know for a fact there isn't for just ICS in general. Thanks for the ROM btw, I'll look into it. If it means anything, he's using AT&T.
Sent from my Galaxy Nexus using Tapatalk 2
Pm me maybe we can find someone in between who can get it going for him im in jackson.
Lol im similar i have a rocket with no issues using smooth ice and really tried most of the other roms but i have a friend who also has one and when i put roms on his phone he's always having issues a few days later. I know he's doing something dumb that is slowing him down but still he blames me and says just put it back to stock
Sent from my SAMSUNG-SGH-I727 using xda premium
droid512 said:
Lol im similar i have a rocket with no issues using smooth ice and really tried most of the other roms but i have a friend who also has one and when i put roms on his phone he's always having issues a few days later. I know he's doing something dumb that is slowing him down but still he blames me and says just put it back to stock
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Glad I'm not the only one in that boat. I swear I have no idea what happens to other peoples phones once I flash stuff on them. Mom and sisters nook color is running fine still. Flashed a ROM on an OG Droid for a different friend a few months back and within two weeks he had me fix it because *I* messed it up (How the hell he managed to delete the launcher and google framework packages is beyond me :what: ). Guess there's a reason root is disabled when you purchase a phone . Although I still don't understand how problems arise weeks if not months later and the fingers are always pointed back to me. /rant sorry.
I'll be checking out the two ROMs suggested here shortly then making a detailed email out to him. Thanks again everyone.
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
Glad I'm not the only one in that boat. I swear I have no idea what happens to other peoples phones once I flash stuff on them. Mom and sisters nook color is running fine still. Flashed a ROM on an OG Droid for a different friend a few months back and within two weeks he had me fix it because *I* messed it up (How the hell he managed to delete the launcher and google framework packages is beyond me :what: ). Guess there's a reason root is disabled when you purchase a phone . Although I still don't understand how problems arise weeks if not months later and the fingers are always pointed back to me. /rant sorry.
I'll be checking out the two ROMs suggested here shortly then making a detailed email out to him. Thanks again everyone.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Haha, let them figure out how to modify their own devices. It will only help them to know what they are doing and you will have less problems.
You are most correct. For the most part, unless its a close friend I will refrain from doing anything. I've had too many instances where people don't understand what I'm telling them. For example, the mere installation of juicedefender on a colleagues phone caused "me to be unable to get Facebook messages or words with friends notifications instantly unless I turned the screen on and I had to take it to the store to get repaired" :banghead: WELL YES. What did you think I meant when I told you your data services would be suspended to save battery while the screen was off? TLDR: Family only or I'll make you learn yourself (or sign a waiver )
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
You are most correct. For the most part, unless its a close friend I will refrain from doing anything. I've had too many instances where people don't understand what I'm telling them. For example, the mere installation of juicedefender on a colleagues phone caused "me to be unable to get Facebook messages or words with friends notifications instantly unless I turned the screen on and I had to take it to the store to get repaired" :banghead: WELL YES. What did you think I meant when I told you your data services would be suspended to save battery while the screen was off? TLDR: Family only or I'll make you learn yourself (or sign a waiver )
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I have learned to be very selective in helping people run roms and such. If they don't understand what it means to clear cache, dalvik, fix permissions, etc.. they are gonna have problems. They need to understand the basics of custom roms, rooting, and the like before they can even consider using anything but stock. They simply have no business running a custom rom, and some are buggy, which makes it far worse. Our ICS leak needs some TLC and some knowledge to keep it running and debug when problems arise. This is something a "buddy" with no knowledge is not gonna be able to fix, and he will have problems. Even Gb customs have issues which require basic knowledge to fix. Our "buddies" need to read the forums and equip themselves with some knowledge before doing or running anything other than stock.
I guess I'm just used to having phones with a larger development community (Nexus, Eris, OG Droid, Nook). The one here is stellar, don't get me wrong, but I've had numerous android devices with flash and forget ROMs that I may have incorrectly assumed all phones had these. My apologies to anyone who takes that offensively, it wasn't intended to be. There are tons of great devs here who continue to impress me, but the population of this dev forum compared to the GNex for example, is much smaller.
Tldr again: I incorrectly assumed most phones had flash and forget ROMs. Is there anything close to stock I can just flash and root for said buddy? Ideally a stock rooted ROM would be best I think.
Sent from my Galaxy Nexus using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1486480
http://forum.xda-developers.com/showthread.php?t=1426590
I used both of these for while. Both were rock solid. The second is just a more themed version. Both are GB, but not stock. rooted, deodexed, zipaligned, etc
xcrazydx said:
http://forum.xda-developers.com/showthread.php?t=1486480
http://forum.xda-developers.com/showthread.php?t=1426590
I used both of these for while. Both were rock solid. The second is just a more themed version. Both are GB, but not stock. rooted, deodexed, zipaligned, etc
Click to expand...
Click to collapse
Thanks a bunch. I'll say its safe to assume there's no stable ICS yet? I don't mind GB at all, I just foresee issues converting said friend to use GB since he's asked me most every day up till the leak about when ICS was coming.
Sent from my Galaxy Nexus using Tapatalk 2
crimson12 said:
Thanks a bunch. I'll say its safe to assume there's no stable ICS yet? I don't mind GB at all, I just foresee issues converting said friend to use GB since he's asked me most every day up till the leak about when ICS was coming.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, I consider it stable with both seanz's ucld2 sky ics and nexusmods beta 7, but there are a couple bugs. If your buddy just needs a rom that runs and doesn't need fixing every now and again he should probably stay on Gb.
Sounds like a good plan.. is there anything in particular I need to do to go from the leak down to GB?
Sent from my Galaxy Nexus using Tapatalk 2
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
neonflash said:
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
Click to expand...
Click to collapse
The most likely issue is the fact that it is running a dual boot and your SD card is messing up. I never advise dual booting as things like this can happen. I would reflash a stock rom. Then go from there. Also might find more help in the captivate section.
Thread closed
Sent from my SGH-I777 using Tapatalk 2
I have not met a more destructive rom than the d2vzw MIUI port.
When I first flashed it a month ago, it was so unstable that I had to re Odin.
But that was nothing compared to the past 12 hours.
I tried a newer build. Still buggy. Wipes my MIN.
I spend the rest of the day zero-bar roaming and throwing every CDMA tool available at the problem.
Nothing worked until I wrote my efs.sbn backup to the phone. It was the last thing I was going to try before going to Verizon and and I never thought I would have to use the backup. I'm glad the MEID loss scare got people serious about backups.
Stay away from MIUI. Not all AOSP is created equal. Backup your efs. You will need it.
Disappointed to come in here and read that your phone wasn't bricked & that miui didn't get your phone wet.
Sent from my Galaxy SIII
I love miui, been using it for a few weeks on this phone and before this one I used it almost exclusively on my other three phones. I too lost my data and EIME, had backup thankfully but spent a few hours trying to get the darn thing working again. Ended up using nvrestore as a last resort and thankfully it worked. Miui is awesome, I can't wait for the kinks to get more ironed out.
No rom works the same on every phone. Sorry you had a bad experience with MIUI but there are many others on here who are using it as a daily driver with no problems.
Sent from my SCH-I535 using xda app-developers app
josh995 said:
No rom works the same on every phone. Sorry you had a bad experience with MIUI but there are many others on here who are using it as a daily driver with no problems.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
LLStarks said:
I have not met a more destructive rom than the d2vzw MIUI port.
When I first flashed it a month ago, it was so unstable that I had to re Odin.
But that was nothing compared to the past 12 hours.
I tried a newer build. Still buggy. Wipes my MIN.
I spend the rest of the day zero-bar roaming and throwing every CDMA tool available at the problem.
Nothing worked until I wrote my efs.sbn backup to the phone. It was the last thing I was going to try before going to Verizon and and I never thought I would have to use the backup. I'm glad the MEID loss scare got people serious about backups.
Stay away from MIUI. Not all AOSP is created equal. Backup your efs. You will need it.
Click to expand...
Click to collapse
I've been a little flash happy lately. I had not tried MIUI but had read about it. Watched the little vid clip. Why not? I generally scan the entire thread on a new rom so I was surprised when I found no app drawer. I thought it was broken. So I waited a couple of days and tried the Official drop. I was playing around with it (still no app drawer of course) looking for Titanium BU when I noticed something on the notification bar. I pulled it down and touch it. something about roaming. I looked through it and the locations were all overseas. Did I miss something? Nothing in the post said anything about a potential bomb built into this thing. After I let it go, I noticed my connection was gone. Nandroid backups did not help. I picked around and got my data back, but only 3g. I ended up calling Verizon and told them I *228'd my phone and they reprogrammed my SIM. All is well now, but I'm going to be more careful and I too am avoiding the MIUI roms.
I've never seen the appeal of MIUI. Sure, it's cute, fun, and different - but I lost interest after about 3 days on my OG droid.
Sent from my SCH-I535 using Tapatalk 2
User error, replace user...
PaulG1488 said:
Disappointed to come in here and read that your phone wasn't bricked & that miui didn't get your phone wet.
Sent from my Galaxy SIII
Click to expand...
Click to collapse
the point is none of the aosp roms are near complete and still cause alot of headaches.
As the Android Turns...
I thought flashing was at your own risk? Anytime I flash I assume I am using my phone as a chip on the blackjack table. Though the odds are in my favor, it's still a gamble. Don't flash if your not up for dealing with a worse case scenario.
I do appreciate the update on your experience, but to deem the rom essentially as a virus is a bit off the mark. Not knocking your post, but your post may scare alot of people away from that developers hard work. All phones, and more importantly all users are different and your experience WILL NOT be everyone else's.
I love the MIUI interface and many of its features, but I have never been able to fun a stable version on any of my phones. Too bad, there are always bugs needed to be worked out in MIUI roms it seems, specially with data.
I got a replacement because of miui killing my 4G about a month ago
Sent from my SCH-I535 using xda app-developers app
LLStarks said:
I have not met a more destructive rom than the d2vzw MIUI port.
When I first flashed it a month ago, it was so unstable that I had to re Odin.
But that was nothing compared to the past 12 hours.
I tried a newer build. Still buggy. Wipes my MIN.
I spend the rest of the day zero-bar roaming and throwing every CDMA tool available at the problem.
Nothing worked until I wrote my efs.sbn backup to the phone. It was the last thing I was going to try before going to Verizon and and I never thought I would have to use the backup. I'm glad the MEID loss scare got people serious about backups.
Stay away from MIUI. Not all AOSP is created equal. Backup your efs. You will need it.
Click to expand...
Click to collapse
They meid problem can happen with any rom so dont blame it on miui. I've used the lastest miui v4 and it works fine, earlier builds were very buggy though
---------- Post added at 06:31 PM ---------- Previous post was at 06:26 PM ----------
shawnten;33391ot a replacement because of miui killing my 4G about a month ago
Sent from my SCH-I535 using xda app-developers app[/QUOTE said:
You flashed it so you killed Your 4g.
You should have fixed it also
Click to expand...
Click to collapse
The problem is common with all AOSP roms which is why I stick to the TW ones for now. MIUI is a fantastic rom, I really miss it after using it for years on my Evo.
It all comes from proper prep. There are so many instances of aosp causing issues for users, but they stem from coming from tw/or back to it. Our friend above (prdog) gave me a wonderful education on cleansing before flashing, and I have yet to have an issue. Learn and understand your system, the partitions created and how they are/are not affected by certain wipes, and know that tw/aosp are very different and need to be treated as such. Don't be lazy, treat going from one to another as a new phone and let titanium be your friend. Always format your system regardless of what others may tell you, even on a dirty flash. It's insurance and pays off in the end.
shawnten said:
I got a replacement because of miui killing my 4G about a month ago
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That was your fault. You should have fixed it yourself
Via my Google Galaxy S3 running magic beans
I remember on the Synergy thread they released a script to I think help prevent the IMEI missing. I know there was one to back it up n I think one to help prevent it from being lost. I'm not exactly sure. I know I ran it n I never had IMEI issues. I will wanna try MIUI on the S3 but after a few reports about the IMEI, I dunno now :/
Sent from my SCH-I535 using Tapatalk 2
droidstyle said:
As the Android Turns...
Click to expand...
Click to collapse
lmao I caught the reference
chip.hughes said:
I've been a little flash happy lately. I had not tried MIUI but had read about it. Watched the little vid clip. Why not? I generally scan the entire thread on a new rom so I was surprised when I found no app drawer. I thought it was broken. So I waited a couple of days and tried the Official drop. I was playing around with it (still no app drawer of course) looking for Titanium BU when I noticed something on the notification bar. I pulled it down and touch it. something about roaming. I looked through it and the locations were all overseas. Did I miss something? Nothing in the post said anything about a potential bomb built into this thing. After I let it go, I noticed my connection was gone. Nandroid backups did not help. I picked around and got my data back, but only 3g. I ended up calling Verizon and told them I *228'd my phone and they reprogrammed my SIM. All is well now, but I'm going to be more careful and I too am avoiding the MIUI roms.
Click to expand...
Click to collapse
If you read about the ROM at all, you would know that MIUI doesn't have an app drawer... There are mods to put one it, but by itself there is none...
xXJay_RXx said:
I remember on the Synergy thread they released a script to I think help prevent the IMEI missing. I know there was one to back it up n I think one to help prevent it from being lost. I'm not exactly sure. I know I ran it n I never had IMEI issues. I will wanna try MIUI on the S3 but after a few reports about the IMEI, I dunno now :/
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Whatever MIUI does, it's recoverable. I too lost data on one of the earlier ones and was able to recover it without too much hassle.
i never saw the fascination with miui but that's just me.
Brian Gove said:
lmao I caught the reference
If you read about the ROM at all, you would know that MIUI doesn't have an app drawer... There are mods to put one it, but by itself there is none...
Whatever MIUI does, it's recoverable. I too lost data on one of the earlier ones and was able to recover it without too much hassle.
Click to expand...
Click to collapse
As for reading about the ROM, where? I looked again, can't find it. I'll allow that the app drawer might be my own fault but that wasn't what distracted me for 4 hours and then the call to Verizon. It was the "roaming bomb". That was not mentioned either. Why would a U.S. ROM contain that? I know flash at my own risk and I do. I've never complained before and I really don't think I'm complaining now. I saw this thread and agree is all. This one wasn't ready for prime time.
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Of course you can. Head over to the thread Nardholio started in the Development section.
http://forum.xda-developers.com/showthread.php?t=2405310
The first post has links to: the official CM site and to the Apex Github. The CM site has a changelog for nightlies. On the Apex Github, they maintain a list of known issues.
It's all there.
I caution you on expectations here. Android 4.4 was just announced with a very unfortunate name. I think Jelly Bean 4.3 has about 60 days to live. It would be silly to expect 10.2 to be stable by then. After 4.4 hits Nexus devices, I bet the Apex guys will shift their focus to 4.4 and we will repeat some of this process...
NavarroCol said:
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Click to expand...
Click to collapse
it will probably never happen.
android 4.4 is just around the corner, so i guess the focus will be swapped on that, as it was for 4.3 and 4.2 before
CyanogenMod will do a final "release" build when 10.2 is EOL which will be the most stable we can make it. We also have a last 10.1 build we consider mostly stable, although it is unofficial. Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Nardholio said:
Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Click to expand...
Click to collapse
I have random freezes/reboots all the time on the official nightlies -- even the ones people claim are stable. The lockscreen freezes quite often too. Are these known issues or am I just a lucky one? I am running CWM and followed the installation instructions on the Cyanogenmod wiki.
I just installed alogerec and hopefully something will show up to troubleshoot my issue.
Problem with 10.2 nightly as well
I have a problem with the 10.2 nightlies I have tried (all from this week) that I emailed Narholio as he requested.
But since I am a n00b and cannot post to development threads yet I could not post details there. I have not done extensive testing because the screen stays black even though the buttons light up when I try to unlock the phone. I can usually get it to display by pressing the lock button again to lock it, then pressing it again to unlock it right away. This also seems to happen only after the phone has been locked for greater than 20 seconds. If the screen timeout happens, or if press the lock button to lock it, the display almost always works if I unlock it again before 20 seconds is up.
I have not noticed any reboots or other problems, but have not used it extensively because of the black screen problem.
Try http://ls.infernix.net/jenkins/job/apexq-staging/ build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
I flashed build 336 last night and still have my phone lock up when trying to unlock it. This doesn't happen every time but when it does it either shows the back and menu buttons illuminated with a black screen or an unresponsive lock screen. In either case it will eventually reboot.
Sent from my SGH-T699 using xda app-developers app
Same problem
Nardholio said:
Try build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Good idea
DOMF said:
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Click to expand...
Click to collapse
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
computerinfo21 said:
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
Click to expand...
Click to collapse
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
computerinfo21 said:
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
Click to expand...
Click to collapse
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Plenty of free memory
croogrog said:
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
Click to expand...
Click to collapse
Yep, did wipe each time I tried multiple recent nightly versions which all do the same thing. The only one I've tried that works correctly is the 20130309 version.
DOMF said:
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Click to expand...
Click to collapse
I generally keep a tab open to this Relay forum so I can watch what's happening, but not many tabs. Also happens immediately after flashing, without even running any apps, much less installing any.
orange808 said:
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Click to expand...
Click to collapse
I really haven't installed any. And when testing different nightlies I just flashed and it happens right away, didn't install a thing on them.
I decided to stay on a version for a while, so have had 20130920 since Friday, and I've used it long enough to know it is consistent. I have found another way to make it happen: incoming phone calls. When phone wakes that way it almost always happens as well. Today it finally showed the screen when I received a call, but 3 or 4 other calls the screen has just been black so I can't tell who's calling.
I discovered another thing since using this ROM for 6 days. Sometimes I get lines/bars/tearing on screen that won't go away until I lock and unlock the phone again.
I have some other phones that are broken, if I can fix one of them I might consider sending this one to a dev to temporarily play with since it seems to be the perfect test case for this problem. The screen is cracked (I got it used in this condition), which I would normally suspect to be the cause of the problem, however since it does not have either problem with stock ICS, stock JB, or the 20130309 CM I'm pretty sure it's related to something in CM10.2. Just new enough to Android I'm not sure how to track it down.
Thank you all for your help!
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
I also have a rev0 cpu phone, and I had a few lockup/reboots since I finally dove in last Monday (9/30) with Staging build 341. However, without me changing anything (still on the same build), they seem to have stopped. Last one I got was 10/2.
Edit: until just now. *facepalm*
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
I got sick of stock so I tried CM again. After flashing the 10.2-20131014-NIGHTLY-apexqtmo nightly I have not had one reboot or lockup in days. YMMV
Edit: Still haven't had a lockup on wake or reboot.
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
Hmm... I'll have to try again
Hmm... Sounds like I need to try again then. I tried one released after that and still had issues, but I will try to make some time later to try it. It is fantastic other than that problem.
newer nightlies
Anyone else having issues with the newer nightlies? I have been flashing one a week for a while now and I'm coming from the 14th. tried flashing the 21,22,and 23 all of them are giving me a boot loop at the samsung screen. I have dirty flashed, cleared cache and dalvik, updated recovery. none of them are working for me. Am I missing something? they don't work so i reflash the 14th and everything is good again.
tried in
CWM 6.0.3.7
CWM 6.0.3.8
CWM Touch 6.0.3.8
all with the same errors any help would be appreciated