What freq/governor have you set? Looks a great result
1.2 is the clock. And using interactiv
[ROM] [NIGHTLY] [GSM] CyanogenMod 9
- Thread starter imfloflo
- Start date
-
- Tags
- development
1.2 is the clock. And using interactiv
These commits (even the merged ones) haven't made it into a nightly yet.
http://review.cyanogenmod.com/#/q/project:CyanogenMod/android_kernel_samsung_tuna,n,z
Typically the CM kernel has always been the best performer for me on CM9, CM7, and derivatives. Not to say there's not potential for there to be hiccups along the way.
Edit: Derp, the merged ones from April 29th that is.
Last edited:
You can try setting min to 729 too, that deffinetly might help, the only difference from what I know between IMM76D and IMM76I is the Kernel fix, supposedly the voltage parameters are causing "some" users to experience a signal loss in the 4.0.4 76D build while screen is off. All current custom Kernels should have the new source merged, thus eliminating the problem. Again, every person might have a different outcome.
I've b een reading though the tread a couple of times with the help of search but could not find a devinitive answer. I see above that= imm76i should have been merged, however in the details in the settings I still see that the build number is imm76d. now the issue is obviously not the number, but the fact that I still have the bug that was apparently solved with imm76i, is still present in the build I install as of the 29th. In this case I'm refering to the issue that when coming from a sleep state the phone wakes and has issues in reconnecting to wireless networks (specifically bluetooth).
in my case this now is that when the Phone wakes the bluetooth state is on, but it can no longer find devices. turning on and off BT doesn't work. only thing that does help is a reboot....
any ideas if the above is indeed solved with imm76i and if that should now be in the buils of CM9 as of the 29th?
thanks in advance,
Patrick
Looking forward for the next nightly. Hope someone will hit the build button soon
Sent from my Galaxy Nexus using Tapatalk 2
Ok now for a stupid one (hope the previous one wasn't ;-)
which Kernel is this? this is not part of the CM9 zip you download from the CM website right (http://get.cm/?device=maguro).
I always though the Kernel needed to be installed seperately... how do I do that, and where to get the CM kernel you refer to (also what is different witht the CM Kernel versus the standard Nexus one?)
I fix the Bluetooth by unpairing and reconnecting. As opposed to a full reboot.
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Ok now for a stupid one (hope the previous one wasn't ;-)
which Kernel is this? this is not part of the CM9 zip you download from the CM website right (http://get.cm/?device=maguro).
I always though the Kernel needed to be installed seperately... how do I do that, and where to get the CM kernel you refer to (also what is different witht the CM Kernel versus the standard Nexus one?)
Each nightly comes with a kernel, so those commits make it into your phone.
As for differences, someone more knowledgeable will have to field that one.
Did you try flashing a custom kernel on top of CM to see if the BT issue would be resolved? Pretty much all the current kernels have the code merged , I'd suggest Franco or Trinity , and give it a test run. As far as signal drops after coming out of sleep, is that resolved?
Sent from my Galaxy Nexus using Tapatalk 2
Looking forward for ir too but I'm a bit confused. AFAIK it's not possible to use fast charge and mtp mount at the same time. So when I was using Franco kernel I usually switch a toggle on his app. So if this change is being committed to cm kernel maybe we'll need to wait they add a control on UI to use it.
Sent from my Galaxy Nexus using Tapatalk 2
You are right that fast charge permits no USB data connection.
There is a control implemented in one of these changes,
http://review.cyanogenmod.com/#/c/15422/,
as a checkbox in GNexusParts
The knob works, when active, on the next USB connect the device reports being AC-charged, and does not appear in lsusb on the host side. Deactivating and plugging out and in again, reverts the action.
EDIT: the USB fast charge change was merged, but then reverted again, because of safety concerns. So don't hold your breath for them to appear in the next nightly...
Last edited:
Gentlemen,
I'm on AOKP m3 with franco kernel and would like to give the CM9 nightly a whirl. Is there a a feature/tweak list for Cyanogenmod 9 so I can know what to expect?
All the other ROMs usually have the feature list in original post. Google doesn't give me much results at all. The original post gives 3 links that lead to things about building etc etc. I don't understand any of that
Help please....
BTW when everyone is talking about wiping, do they mean a cache wipe and then Dalvik cache wipe using clockworkmod? or are they saying factory reset? or is it both? Never really understood what this wiping business is about
I'm on AOKP m3 with franco kernel and would like to give the CM9 nightly a whirl. Is there a a feature/tweak list for Cyanogenmod 9 so I can know what to expect?
All the other ROMs usually have the feature list in original post. Google doesn't give me much results at all. The original post gives 3 links that lead to things about building etc etc. I don't understand any of that
Help please....
BTW when everyone is talking about wiping, do they mean a cache wipe and then Dalvik cache wipe using clockworkmod? or are they saying factory reset? or is it both? Never really understood what this wiping business is about
Nope, the kernel is included in the CM9 update.zip and installed anew whenever you install that.
Since a short while, when building CM9, the kernel is completely built anew from source, as part of the overall building process.
You can view the kernel source and all changes, both through gerrit and behind the scenes, by looking at https://github.com/CyanogenMod/android_kernel_samsung_tuna
(branch ics) which is the life repository which is used when building CM9.
The exact configuration used, is
https://github.com/CyanogenMod/andr...s/arch/arm/configs/cyanogenmod_tuna_defconfig
It should be possible (haven't tried recently) to just git-checkout the kernel tree, and build it separately.
---------- Post added at 08:23 PM ---------- Previous post was at 08:15 PM ----------
There is no feature list. The ROM is not even released yet.
It's great however. Try it out.
If you come from a different ROM, do a data wipe, i.e. complete factory reset.
If you just upgrade between successive CM9 versions, just... install it. I don't even cache wipe any more.
I know it's not released yet, but a snippet of the features would be nice. A short summary of the major ones for example.
Dumb question....a complete factory reset does a cache and dalvik cache wipe? Also does it clear my sdcard contents?
A data wipe / factory reset wipes /data, i.e. the place where apps keep their app private configuration and whatever private data they have.
No wipe ever touches /sdcard, where pictures, video, music, Titanium backups, clockworkmod backups and other personal stuff is kept.
D
Deleted member 2044343
Guest
New build is cooking
Sent from my Galaxy Nexus using Tapatalk 2
Done
Gesendet von meinem Galaxy Nexus
Done
Gesendet von meinem Galaxy Nexus
F5'ing
i guess its uploading to mirrors now
Its up
http://download.cyanogenmod.com/get...pdate-cm-9-20120501-NIGHTLY-maguro-signed.zip
Last edited:
Same here, CM kernel is pure butter and has the best battery life.
Would like to add check and see what is using your CPU real time in Developer options. I saw Facebook eating it alive so I uninstalled and battery increased.
Sent from my Galaxy Nexus using XDA
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
