[ROM] [NIGHTLY] [GSM] CyanogenMod 9
- Thread starter imfloflo
- Start date
-
- Tags
- development
Fix permissions if that doesn't fix then redownload them.
Sent from my Galaxy Nexus using Tapatalk 2
Unfortunately my battery life isn't quite as good with the latest nightlies. The standby time isn't as good. My phone is sleeping correctly and all, but it seems there is a little more power draw while sleeping than previous nightlies. I'm still managing near 4 hours screen time though. I think if standby were a little better I'd break the 4 hour mark again. Anyone else notice standby not quite as efficient as it was?
M
mudferret
Guest
I posted a page or two back, but since the update to the 3.0.27 kernel I've been getting wlan_ctrl_wake wakelocks; 10 min/hour at idle. I'm temporarily on an alternate kernel, the discussion of which is outside the scope of this thread
I posted a page or two back, but since the update to the 3.0.27 kernel I've been getting wlan_ctrl_wake wakelocks; 10 min/hour at idle. I'm temporarily on an alternate kernel, the discussion of which is outside the scope of this thread
Yea I saw that. Does it show in the battery screen as your phone not sleeping when that happens? Cause when my screen is off, the phone sleeps nearly entirely.
M
mudferret
Guest
I go by Better Battery Stats; it was only happening on my home router. Have yet to compare the specs of my office router to my home one. You can compare your awake vs screen on time on your battery history history screen, but the resolution is coarse.
Deep Sleep was still 80+ % through the night, but that was down considerably from the 97% I was used to.
See my device woke once through the entire night according to battery history and it was a barely visible sliver. So I feel its sleeping the same amount of time.
I'm having a problem. I can't seem to download anything from any app. My phone is apparently "out of storage" but I have about 2.8GB free. Anyone know what I can do? I'm trying to keep a full wipe as a last resort move.
I'm on the April 7th build. I would go to the latest build but..well, I can't download it straight to my phone. :/
Sent from my Galaxy Nexus using XDA
I'm on the April 7th build. I would go to the latest build but..well, I can't download it straight to my phone. :/
Sent from my Galaxy Nexus using XDA
Possibly your ram is full. No where for app storage is all I can that i can think of off hand. What apps is this happening in?
Side note, anyone use 16 bit transparency? I just switched on, in some areas I notice a slight improvement. Nothing drastic though.
Last edited:
One good recommendation! Thank you!
I am really sad that I haven't tried his kernel before
Sent from my Galaxy Nexus using Tapatalk 2
I remember that discussion with CM7; chances are slim that this feature will ever be implemented. The problem is that your phone can become very unstable with certain voltages. Especially for noobs or people who don't know what they're doing this can be a real issue. If you want voltage control, you should try a different kernel (Franco's perhaps?), but if you experience any bugs, don't post them here.
G
--GNex--
Guest
If you try GlaDos Kernel you cant change the gamma settings anymore in the settings from CM9.
You have to change it with the app. CM9 Team takes care to be very stable and they recommend always their kernel. I wouldnt flash another one....
Sent from my Galaxy Nexus using Tapatalk 2
You have to change it with the app. CM9 Team takes care to be very stable and they recommend always their kernel. I wouldnt flash another one....
Sent from my Galaxy Nexus using Tapatalk 2
I've installed this rom within 1 hour of getting the phone. It's better than stock for sure, but the touch response is seriously annoying me so much. It keeps missing touches, most notably in the keyboard but also the soft buttons. It's incredibly annoying for me, I'm used to touch screens that work all the time(iPad and iPhone, sgs2 on GB). It seems to get worse when listening to music which I do a lot. I guess I'll try stock rom and see if it works better. Keep in mind that I didn't use stock for more than 1 hour so I can't say if it's just the way the phone is or it's something with the kernel.
Seems the issue is indeed too low touch sensitivity. It works 100% if I tap it harder. A light touch won't work at all most of the time.
Sent from my Galaxy Nexus using Tapatalk 2
Seems the issue is indeed too low touch sensitivity. It works 100% if I tap it harder. A light touch won't work at all most of the time.
Sent from my Galaxy Nexus using Tapatalk 2
Last edited:
Tbh I think touch sensitivity is fine, definitely not worse compared to stock or iPhone. Try stock, or maybe even reflashing. I hope it works and that you don't have a faulty device.
---------- Post added at 12:40 PM ---------- Previous post was at 12:39 PM ----------
Yeah, this commit explains it: http://review.cyanogenmod.com/#change,13394
So ..
You should have the folder Ringtones in SD, where we put in the ringtones you'll never miss ..
said this:
download the version of 04
With WinRar you with the right button: draw in update-cm-9-20120404-NIGHTLY-maguro-signed on the desktop, inside open your system and then into> media> audio .. inside you all the ringtones and notifications ..
all you do is copy those of your interest in the Ringtones folder of the SD that I told you before ..
vai here to associate your ringtones as you usually do
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
156This thread is reserve for nightly build of Cyanogen Mod Rom for Galaxy Nexus
You can report and discuss all issue you are having with nightly build here.
What are Nightly build ? : auto compil build from the CyanogenMod github, each time there are new corrections on it.
This version change each night, and aren't support officialy, if you find bugs/issues you can/must discuss here.
Warning: Not for new user, flash this build only if you know what you are doing !!!
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps from his roms,
after flashing rom don't forget to flash Google Addon package if you want it.
Lastest version: CM9...
Download: http://goo.gl/cYeZK
MD5Sum: check the md5 under the files named associate with your build version before flashing it
Google Addon:
http://goo.gl/Mc4wb >Check the lastest package available on top
MD5Sum: check the md5 of the files before flashing it
USEFUL
http://wiki.cyanogenmod.com/wiki/Barebones clean your rom to make space
CHANGELOG What's new in this version :
http://cm9log.appspot.com/?device=maguro
http://changelog.bbqdroid.org/#maguro/cm9/next
http://cm-nightlies.appspot.com/?device=maguro
http://review.cyanogenmod.com/#q,status:merged+branch:ics,n,z
http://jenkins.cyanogenmod.com/
http://goo.gl/mlTEQ Themes for CM9
If you have issue with this rom just WIPE ALL and try again.
>>>Please don't report bug if you don't use stock CM9 kernel!<<<
Have a question or an issue? Try this before asking something silly:27Repositories for all AOSP projects have been created on our github to alleviate any potential mismatches (branch is 'jellybean').
While Jelly Bean won't require a major rewrite of all the CM features, the source has been re-arranged and re-factored enough that a simple merge isn't possible. So we will proceed with manual merging (this was to be expected really).
The plan of attack will be to cherry-pick everything from CM9 and fix the merge conflicts and relocations. It’s tedious but the only way. Ideally the original patch authors will forward-port their changes, so if you are out there and want to help out, join us in #cyanogenmod -dev.
+ Trebuchet might be messy to rebase onto JB.
+ Theme Engine will be messy.
+ SystemUI stuff will need to be restyled.
+ Lockscreen stuff will need to be restyled.
+ The current UX of Settings is good, no reason to change anything there.
A manifest (Cyanogenmod/android.git) will be going up later this afternoon, so the masses will be able to sync directly from our source at that point as well.
This will be it on the updates (so we can focus on actually working). Next post referencing JB should be when the merge/cherry-pick process is complete.
-CyanogenMod Team19Why are some people coming in here like "why cm doesnt do it like aokp"?
Why do you think??? Because it ISN'T aokp.
I'm getting pretty bored about everyday i come in here, and mostly every post i read says "i have data drops with nightly X" "i have wifi drops on nightly X" "when cm releases a stable rc" "milestone"
Do you know what nightlies mean??? There are no bug reports, so all those complains will only be heard, basically when, you are running a RC and you get a logcat or kmsg to backup your claims. Otherwise, it's just user error.
So stop cluttering the damn thread and asking if this is good enough to be a daily driver. If you have to ask, then its not for you.
Go back to stock or aokp. Return your phone, you are holding it wrong. Buy a dumb phone.
Sent from my i925010Don't know if this has been posted but makes it easier to keep track of changes
https://play.google.com/store/apps/details?id=org.bbqdroid.log
Sent from my Galaxy Nexus using Tapatalk 2
New posts
-
-
-
General [OnePlus 12][ROM][OTA][BOOT][Oxygen OS] Repo of Oxygen OS Builds
- Latest: AmirulAndalib