[ROM][M7][KK][4.4.4] CyanogenMod 11 Official Nightly Builds
- Thread starter tiny4579
- Start date
Or the latest here. I tested what I believe is the official twrp 2.8.0.2 so it should work fine.
http://techerrata.com/browse/twrp2/m7
ok, so since the latest snapshot and a couple of nightlies i have installed since then (namely yesterdays and last weeks), i have been getting random soft reboots every so often, usually once or twice a day. i can't seem to pin it down to what app is running in the background that may be causing this. have tried clearing data for google play, but then got another soft reboot just a few minutes ago..
to be honest, it's really driving me crazy as i am in for a stable ROM that doesn't soft boot on me during the day. it has also happened during a call, while using whatsapp and while writing a (very long) note in google keep that went to the trash...
Any ideas what could be causing this? options as to how to prevent it from recurring?
Thanks
to be honest, it's really driving me crazy as i am in for a stable ROM that doesn't soft boot on me during the day. it has also happened during a call, while using whatsapp and while writing a (very long) note in google keep that went to the trash...
Any ideas what could be causing this? options as to how to prevent it from recurring?
Thanks
Not sure of the cause but if you can connect your phone via adb and reproduce it you might be able to get s logcat.
Barring that try doing a clean install with only the apps you absolutely need or no additional apps installed. Then you can reinstall one by one and monitor for a day after each app. I know that sounds like a lot but its probably the only way to know for sure without logs.
Another option is see if it happens in safe mode (long press reboot for cm).
Have decided to wipe everything and install fresh for now. Will monitor and see if this makes any difference on 26/9 nightly. So far, 4 hours in, looking alright.
I've had a few reboots randomly also. Not near my computer to take a logcat unfortunately. Facebook & SalesForce both force close occasionally now in the last few builds also. If I can ever replicate and get a logcat I will.
There is one every month. I'd expect in the next few days or week after the maintainers validate. This usually happens about a week after the big merge into stable.
My m7vzw seems to be stuck in 3g mode. I'm running snapshot 10. I've tried to reflash to the stock ROM and updated the radio, but nothing seems to help.
The strange thing is that it will work perfectly fine with LTE if I go to Settings -> Mobile Networks -> Preferred Network Type, and choose "LTE". But, when that settings is in place, I can't make phone calls. If I change it back to "CDMA+LTE/EVDO", it goes straight into 3g mode. So, I don't think it's a problem with the radio being unable to use 4G, it seems more like a "preference" thing.
Any ideas?
The strange thing is that it will work perfectly fine with LTE if I go to Settings -> Mobile Networks -> Preferred Network Type, and choose "LTE". But, when that settings is in place, I can't make phone calls. If I change it back to "CDMA+LTE/EVDO", it goes straight into 3g mode. So, I don't think it's a problem with the radio being unable to use 4G, it seems more like a "preference" thing.
Any ideas?
This is for the gsm m7 though still check that you have the right version for your device. So its an issue with stock or does stock not fix the issue for cm?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10
Frankly if that's the attitude you have about Android development you should stay on stock because there's always the chance for something to break. Especially when you're talking Cyanogenmod nightlies. So take your bad attitude elsewhere it will not be missed.
Sent from my One using Tapatalk8Have just submitted my first patch. I have found little mistake in our amp code that made left channel not being played at all. Instead we had right channel played through two speakers.
http://review.cyanogenmod.org/#/c/57093/
Hope it will be merged
8
The speakerphone mic issue is subjective in the sense that people who rely on speakerphone say it's broken and those of us (like me) who rarely use it, except to listen to voice mail, say it works fine. My testing shows that only the rear microphone is used for speakerphone, so depending on how you hold the phone it's easy to cover the mic in a way that it doesn't pickup correctly and the remote party cannot hear you. It's flaky, at best.
Proximity sensor work fine on my device (screen goes off with my hand about 2" from the sensor), by I remember a bunch of tweaking on 10.2 because the correct values vary among devices and their sensitivity.
Haptic feedback does occasionally stutter since the switch to msm8960 kernel. I only have it enabled for hardware keys, but those that have it enabled for keyboard use notice the stutter more frequently.
Also, since msm8960 kernel the notification LED sometimes get stuck on solid amber vs flashing, unlocking the device gets it flashing again.
As for support, until M5 the stable builds were based on m7 kernel, so it wasn't possible to report these msm8960 bugs on JIRA.
Also, I'd say that it would make sense to frequent XDA more often if you are a device maintainer because 99% of the casual CM users are going to come to these forums to report bugs and resolve issues, most will never open a bug on JIRA or hop on the IRC channel.
I agree with @sabret00the regarding the development model for CM, it has worked in the past but there's much room for improvement if CM wants to make a move to a widely used product. A wide tester base that includes many casual users is key, so there needs to be a (user friendly) mechanism for those users to report issues on incremental builds. Maybe that means abandoning nightlies for weekly builds that are more stable and feature targeted so that users can report issues.
Maybe an app built into CM to report issues directly from the device, uploading logcat and last_kmsg and other state that's helpful to debugging the issues.
We do appreciate the work you and other's have put into CM on m7 to bring it to this point, but I'm sure you can see the frustration that exists from long standing issues which are known to the user base but the maintainers aren't aware of or have the appearance of being ignored.6
Yup, I'm working on a fix. Hopefully will commit in the next couple days.
