Since I have not reached my 10 post limit, :/ I have to post here.
I have been trying the new CM10 4.3 alpha release and wanted the developer to know which bugs I encountered. I will upload logs when I am allowed to post in the "official thread" Not worth the time until then.
Issues I encountered: Sprint Voicemail, will not connect properly (I installed the apk) Is there a work around for it?
About every 30 minutes had the airplane mode glitch, as bad as LOS was on earlier alpha versions
Encountered random screen unlocks and reboots
Also will the rom ever include the ability to update PRLs?
As I said above I would love to be able to contribute to the development of the rom and I love the work the devs have been putting out, CM10 is amazing and I will try all versions for testing, can't wait for a stable release.
Keep up the good work!!
Back to ff18 until the next release
Sprint Voicemail, will not connect properly (I installed the apk) Is there a work around for it?
It's hit or miss with non TW ROMs
About every 30 minutes had the airplane mode glitch, as bad as LOS was on earlier alpha versions
Another hit or miss, I experienced it about every 2 hours
Encountered random screen unlocks and reboots
Random screen unlocks are due to wakelock which is a known issue and is being worked on
Also will the rom ever include the ability to update PRLs?
Most likely not....
Related
im running xdandroid BLAZN on my rhod210 and im using the latest kernal. And apps wont install anymore from app market or through apk installer. Even apps that are already installed if you uninstall them they wont reinstall. Anyone else having this problem?
also my home/power button still isnt doing its designated function of bringing me to home screen? this problem occured about 5 updates ago so shouldnt it be fixed? iv heard its literally a one line change to fix this.
And does any1 else think that stability has decreased in the latest kernal updates? if i play music so i can hear when it goes off, i get sleep of death every 3minutes when in sleep mode. Also android restarts to splash startup screen regularly which is annoyn as incoming messages are rejected when this happends.
Wow... Let's try to break this down. The home/power button switch was intentional... so it's not going to get 'fixed' as you say. See this thread if you want to revert the commits in question that change the button layout.
App/market issues are almost always fixed by deleting your data.img and starting clean - this will wipe all user data off of the phone, you'll basically be booting for the first time again as far as the system is concerned without a data.img.
Stability... it's like battery life - perception is everything. I wouldn't say the new builds are any more or less stable than the previous ones, no. In fact, I would say they're more stable, but that's just me.
+1 What arrrghhh said!
We're most fortunate to have arrrghhh.
I also find stability has continued to improve with most kernel, modules, & rootfs updates including the most recent.
I can only add that until Sov updates to the Froyo [2.2] [25-10-10] System.ext2 in his Blazin build USE his Reference build. And if you must overclock at least DON'T when your building a new data.img file.
I get considerably more SOD & other abnormalities when overclocking at any level.
tank you arrrghhh and LDgator.
My app installation problem started when i updated the kernal so i presumed that was the problem but if im the only one with this problem then its more than likly my data.img, i will move and rename my data.img have it create a new one to check of that is the problem and iv been using blazn because i presumed it would be updated soon after reference. But its been awhile now so yeah maybe i will switch to reference for the time being maybe will solve my stability issue's.
I am running the Blu Kuban, and have been having problems with talk failing and random reboots. I follow the Rom posts from devs pretty regurly. I have seen that Ruj, and others reccomend removing the themed version of talk, and installing the stock version that is availble in the Rom updater. I tried this about a week ago, but even after fixing permissions in the recovery my phone would keep restarting till I reinstalled the rom. I was working just fine after a fresh, and wiped out install up untill a few days ago. I am getting the messages again that my talk app is failing, or sometimes not responding. It was not untill I started messing around with goveners that I started having this issue. I had the default hyper after install, but switched it to wheatly. It was not untill I switched to hotplug two nights ago that I have been having issues with talk. I was having the same problem with the newset Kuban kernal with random reboots of the phone, and thought it was with govener, as that is all I have changed in Ex tweaks. The mods I have installed are; Blank pull down, No rotate/no landscape/no crt, In call sms notification, and finally no battery bar. My restarts of the phone have been random, they can be from anything from loading facebook, turning on wifi, adjusting phone volume, to even putting phone to sleep. I guess after my long rant of problems is there anything that I can do differently to make phone run better? I am not overclocking or underclocking. Have not played with voltages. I turned my screen off profiles off too. I am thinking that unless it gets worse, I will wait for Ruj, to release any new kinds update. Is it the kernel that is giving the problem? I saw someone posted to try older kernel version, is that very dependable?
Also I know this post is getting pretty long, but can someone please tell me if there is any sort of geographical list of modems that work best in certain area's? http://forum.xda-developers.com/wiki/Samsung_Epic_4G_Touch/Modems this showed me that there is a bunch to try, but I want to know which ones work best in area before I go messing around. Does Sprint use different ones in different locations is what I am asking about modems.
There is a talk fix in the 4th post of the faq.
As far as the modems, they are kind of a subjective choice. My phone is best on fg20 and my wife uses fe22. You just goes try them all until you get one you like. I currently use the latest Kuban kernel and do not have any reboot issues. If you keep having issues I would recommend a fresh install or setting extweaks back to the defaults, then making adjustments one at a time until you are happy with the setup.
Saw a few posting for other android items but none for the GN so here it goes:
Ever since upgrading to JB, my phone takes 2+ minutes to startup. The actual time is 2 minutes 46 seconds displaying the google logo, then about 15 seconds at the multicolor X.
I had tinkered around with a JB release from Vicious a couple months before Verizon rolled their 'official' release out. At that time I also noticed an extremely long startup time, but didn't have it loaded on the phone that long so really not an issue.
But now this startup time is just insane. I made a few laps around the grocery store before the phone actually was ready to use again.
If anybody has an idea on this, please post. I can't imagine people would consider this acceptable so I'm hoping there is some resolution.
Thanks
I have a GSM Nexus and it takes a little less than 15 seconds on the "Google" screen and then another 30 seconds on the multicolored X. 4.1.2
ok so definitely not a common issue. any ideas?
Yup had the same problem after upgrading to JB on both Jelly Belly and AOKP. I would flash the JB bootloader hoping that would help but it didn't. On CM10 now and it boots right up, it's FAST.:good:
I've heard the CM10 referenced before, could you tell a bit about that in comparison to the base VZW version?
militarymedic23 said:
I've heard the CM10 referenced before, could you tell a bit about that in comparison to the base VZW version?
Click to expand...
Click to collapse
CM10 is based on AOSP, so right off the bat it is going to be very similar in terms of look and feel. And then you open the setting menu and find out how many customization options you have, and you see the built in theme engine, and realize how smooth and fluent everything is.
Seems to be random. Sometimes I have no startup delay, and other times the phone hangs at the Google screen for several minutes. No rhyme or reason, just happens. However since rebooting is not all that necessary on a regular basis, I stopped thinking about it. And my phone still works just fine.
Sent from my Xoom using xda premium
Jellybean does filesystem check and repair on boot, so if you did a dirty shutdown or something which caused filesystem errors, that would explain the the extra time taken to boot.
I decided to bump this up to CM10. although on the first try at backing up the phone it actually wiped the thing. Not quite sure what happened there.
I am opening another thread on a display problem with double clocks on the main screen.
As far as I can recall, I've shut the phone down through the software. Once in a great while I force power it off but nothing recently.
Anyway, we'll see how CM10 works.
I bought my N7 (Flo) in early January and am loving it except for the random reboots. I did a factory restore and on the first boot got up to around 92hrs of uptime with about 50% battery usage before a crash. Subsequent boots aren't quite hitting that mark. As everyone knows it's hard to tell at exactly what intervals as it will crash while it is sleeping, not just in use.
Has switching to a custom kernel provided better stability for anyone?
Yes. I can only speak for CM11 but flashing Glitch kernel completely stopped the reboots and also the random buzzing noise from the speakers.
I didn't try the kernel on stock (also had reboots) but go ahead it might work. Make a nandroid first.
I really thought the reboots were hardware related but after going through three devices, 16 and 32gb models and 06, 07 and 08 build dates, they all randomly rebooted. Glitch has solved it (again at least on CM11). I'm sure it's a software problem now.
So, here's my experience with this. I bought my first nexus 7.2, at a best buy in north Dallas, in October. I experienced random reboots, right out of the box, about once a day, usually when I was browsing chrome, or when the tablet was sitting on the home screen without being touched. My gf bought a nexus 7.2 as well, at the same store in November, and she was not experiencing any random reboots, hers has always been stock, to this day (my suspicions began). I figured it was a software, or app problem, and waited for a fix from Google, or my app developers. Tried various custom Roms in the meantime (cm11, dirty unicorns, silmrom, and many more). I also tried various kernel's, in combination with said Roms (Franco, ElementalX, glitch, bulletproof). I had random reboots with all combinations of Roms and kernels. Did a factory data reset after every update from Google, and tried it for a week or so every time. Still experienced random reboots. I finally got fed up and took my table back in early January, to the same best buy in north Dallas. After receiving my second tablet, I kept it stock for a week, and then restored my preferred twrp backup, that I had taken with the rebooting tablet ( stock 4.4 krt16s, xposed framework, ElementalX 2.2 @1.7 and 450, with the motoX dalvik and bionic patches). With the new tablet, I have not experienced one random reboot, either with the stock software, or the custom software.
So, long story short, if your experiencing random reboots, if you have the ability to, I would take it back. Maybe you can fix it with software enhancements, but IMO it just shouldn't do this, stock or otherwise, and warrants a return.
Whatever you choose to do, I hope it works out for you, the reboots were personally driving me crazy, and I'm glad my second tablet doesn't reboot like its got a mind of its own.
thisguysayswht said:
So, long story short, if your experiencing random reboots, if you have the ability to, I would take it back. Maybe you can fix it with software enhancements, but IMO it just shouldn't do this, stock or otherwise, and warrants a return.
Click to expand...
Click to collapse
I also bought mine at a Best Buy but am a few weeks out of the return period. I'll give it a try and see if they'll take it back. I was really trying to avoid sending it to Asus. Thanks for your input.
I never had any random reboot issues however, it might have been due to having it running on CleanRom 2.6 and ElementalX Kernel since almost day 1. These two make the device so snappy I don't even care.
Hello all
I installed cm12 nightly and I'm stuck with a setup screen where I have to choose language and WiFi, I select them and then I have a 2nd select WiFi screen
How can I solve this ?
Thanks
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Well I can't skip through it because it gets stuck at the 2nd network detection, probably provider selection but I never get there.
It's the Cm account app, why they need an app for that is beyond me but if it is not solved soon I'll move along to another rom....
In the meantime i'm still looking for a fix
Thanks
apuntigam said:
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Click to expand...
Click to collapse