I've seen in Cyanogen's ROM there is a patch for more memory. How much more memory does it give? Does it degrade 3D performance such as on the G1? And most importantly, why doesn't Google just enable it by default in the first place?
The memory patch gives over 100MB of RAM. Unlike the G1 hack, this patch fixes a bug in the stock kernel, that doesnt recognize all the RAM available. It does not take or re-allocate any GPU RAM - the extra RAM is RAM that was previously unused.
Google has not yet fixed it but Swetland has said it should be fixed soon by a firmware update.
Melterx12 actually summed it up. Usually I answer the odd ball question, but this, I'm gonna say try the search feature. There are ton's of threads on this.
The reason that Google hasn't fixed it yet is that it isn't simply a bug fix, but a newer kernel with a new feature that allows them to use the extra RAM. Cyanogen is aggressive about bumping up to the new kernel, but Google is more conservative on that, though they have mentioned that it will be coming before too long - just not on the same bleeding-edge schedule as Cyanogen uses.
When the .29 on your kernel version becomes a .32 (in a future OTA) then it should be fixed...
flarbear said:
The reason that Google hasn't fixed it yet is that it isn't simply a bug fix, but a newer kernel with a new feature that allows them to use the extra RAM. Cyanogen is aggressive about bumping up to the new kernel, but Google is more conservative on that, though they have mentioned that it will be coming before too long - just not on the same bleeding-edge schedule as Cyanogen uses.
When the .29 on your kernel version becomes a .32 (in a future OTA) then it should be fixed...
Click to expand...
Click to collapse
The .32 Kernel also implements some new features that will be used with a newer radio as well (letting the battery drop to ~90% before resuming charging to prolong battery life for example) as well as removing the requirement for 1:1 mapping for memory. There's a post around here somewhere detailing it a bit (as explained by a google employee). Hopefully they get it sorted and distributed sooner rather than later.
flarbear said:
The reason that Google hasn't fixed it yet is that it isn't simply a bug fix, but a newer kernel with a new feature that allows them to use the extra RAM. Cyanogen is aggressive about bumping up to the new kernel, but Google is more conservative on that, though they have mentioned that it will be coming before too long - just not on the same bleeding-edge schedule as Cyanogen uses.
When the .29 on your kernel version becomes a .32 (in a future OTA) then it should be fixed...
Click to expand...
Click to collapse
Right.. They are still working the bugs out of the .32 kernel. I was able to backport the required highmem stuff so we can have it on a stable kernel for now. Google's efforts with the kernel are probably entirely based on .32 at this point.
Related
Drat.. dosen't seem to have any more ram free, 85.4meg before and after the update
From what I remember the memory update is in. 32 kernel and this is still the same .29 kernel so yeah it isn't but it will come, the phone hasn't been out a month yet.
That sux's The sooner the better for my N1
Was really hoping it would have it but multi-touch might make up for it
The phone still flies. Plus now we get to look forward to the ram update whilst we fiddle with multitouch an new version of maps!
I must agree the multitouch really does do its job to perfection. Good job Google I say.
I'm willing to bet there were other issues with the .32 kernel they still wanted to sort out prior to releasing. However I would much rather they release the update without, than hold it until they're happy with the newer kernel. The lack of full memory support currently is no real limitation (and even still much better than most other android phones).
So the multitouch is smoother than the implementation in Cyanogen's rom?
What are the differences between the two, and the advantages/disadvantages. I have been told its safer and better to use a stable, preferably 11 or 14, for whatever reasons, but i was never really told why. Anyone care to explain?
kobyjd said:
What are the differences between the two, and the advantages/disadvantages. I have been told its safer and better to use a stable, preferably 11 or 14, for whatever reasons, but i was never really told why. Anyone care to explain?
Click to expand...
Click to collapse
The stable kernels are the latest uncapped kernels running at 768 mHz with a standard CFS scheduler, which refers to how they schedule the queued tasks. The Brainfuct kernels are built on the BFS scheduler, which many people say is speedier, but it is slightly less stable, as in GPS may not work as well, and you may experience freezes.
Try out the latest Brainfuct kernel, and if you have instability problems, switch to the latest Stable release (currently 14 I think).
I've been having fc's with #14. ADW.process.acore or something to that effect when I wake my phone up. I'm just running the cm6 stock kernal, it is good enough for my needs.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!
user7618 said:
I've been having fc's with #14. ADW.process.acore or something to that effect when I wake my phone up. I'm just running the cm6 stock kernal, it is good enough for my needs.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!
Click to expand...
Click to collapse
True, the stock kernel may be your best bet.
So I've been read a few threads, but haven't found anything yet. Not to break "the golden rule" of CM7, but are we close/will we ever get stock-like battery life for CM7? It has greatly improved since the early days of CM7 nightlies, and I've seen mad-murdock various fixes. I also know that dalingrin is working on it, but would like to know with the new 2.2 OEM ROM coming out, what the haps is
Thanks all for the great work and great community!
We don't get stock-like battery because CM7 doesn't sleep. The current kernel (2.6.29 I think) panics when comming out of sleep, hence, 'sleep of death'. Dal says that he's solved the SOD problem in the new kernel (2.6.32) he's working on. It's just not stage ready yet.
There was talk last week about the new kernel possibly not being included in the first stable release of CM7. If I remember right, it's because they want to focus on getting a polished, bug-free, and stable version going on the current kernel (which has many backports from the new kernel, so we're not at a real big disadvantage) before completely debugging the new one.
woot1524 said:
We don't get stock-like battery because CM7 doesn't sleep. The current kernel (2.6.29 I think) panics when comming out of sleep, hence, 'sleep of death'. Dal says that he's solved the SOD problem in the new kernel (2.6.32) he's working on. It's just not stage ready yet.
There was talk last week about the new kernel possibly not being included in the first stable release of CM7. If I remember right, it's because they want to focus on getting a polished, bug-free, and stable version going on the current kernel (which has many backports from the new kernel, so we're not at a real big disadvantage) before completely debugging the new one.
Click to expand...
Click to collapse
Thanks for the complete and informative reply. I just like being in the loop
woot1524 said:
We don't get stock-like battery because CM7 doesn't sleep. The current kernel (2.6.29 I think) panics when comming out of sleep, hence, 'sleep of death'. Dal says that he's solved the SOD problem in the new kernel (2.6.32) he's working on. It's just not stage ready yet.
There was talk last week about the new kernel possibly not being included in the first stable release of CM7. If I remember right, it's because they want to focus on getting a polished, bug-free, and stable version going on the current kernel (which has many backports from the new kernel, so we're not at a real big disadvantage) before completely debugging the new one.
Click to expand...
Click to collapse
My only correction is that most of the 2.6.32 work has been done by Verygreen. I don't want to take credit for his great work.
Just want to say thanks for all the hard work, and I too am interested in this issue being fixed. It's the only thing holding me back from what looks like a great release in CM7.
Count me is as waiting for this.
For now I just shut down and reboot when I want to use it. Other then this issue, CM7 is great on the Nook.
Once SOD is solved, the nook color is going to really shine. Dalingrin, your 413a kernel is absolutely stunning. Keep up the good work devs!
dalingrin said:
My only correction is that most of the 2.6.32 work has been done by Verygreen. I don't want to take credit for his great work.
Click to expand...
Click to collapse
have you seen the issues with latest ALSA and kernel?
Seems we are all having crashes of hardware acceleration after a while of use. Only fix is a reboot
Any change to kink at this before next week?
Must say otherwise this kernel had been with smooth high performance on video and games.
From 1.1 Nook Color with 1.1 ghz overclock
Canadoc said:
have you seen the issues with latest ALSA and kernel?
Seems we are all having crashes of hardware acceleration after a while of use. Only fix is a reboot
Any change to kink at this before next week?
Must say otherwise this kernel had been with smooth high performance on video and games.
From 1.1 Nook Color with 1.1 ghz overclock
Click to expand...
Click to collapse
Dal said he was busy/away this weekend, so won't see anything til later. It is a beta test kernel, after all I flashed it but had some crashes, so I restored a backup I made right before.
That being said, I hate sounding like a whining brat (like a lot of people on here). I really am just curious with how things are (in an inquisitive manor, not a "I WANT IT NOW" one). Truth be told, the NC has come SOOOO far in the last few months, and I have been so stoked to be along for the ride.
I like to think I was the first person ON EARTH to load up Dal's kernel the day he fixed the hardware acceleration. I love the discussions on here, and (most) of the people. It is really a cool and special thing to be involved in a community like this. I know most devs may think that when I (and others?) say thank you, it's in a manor that may sound insincere, but really, you guys are awesome.
Due to all the development here, I started teaching myself Java and how to use the SDK to try and make apps that can benefit people on here in some way. I just wish I knew more about development of the actual kernel/rom. After this term I plan on dual booting to ubuntu on my x64 desktop to try and get into compiling/editing the source, but have to get through this term. CFD and incomp. fluid mechanics take up a bit of time
Really. Thank you all! You are all awesome!
/rant
Another perspective
Let me offer some perspective on this.
We used to have Motion LS800 WinXP tablet at work. It basically had standby SOD problem. Would not wake from sleep (power down, suspend to RAM). We ended up putting it in hibernation (power down, suspend to HDD) instead. Those of you who remember WinXP laptops may know what I'm talking about.
We went through updates, hotfixes, service packs, an entire upgrade to Win Vista. Nothing solved problem. Finally an upgrade to Win 7 allowed the LS800 to sleep properly. All in all, it took Microsoft 3+ years to give us a fix.
Going by that performance standard, CM7 should have Nook standby SOD issue solved sometime in the year 2014. Anything before then would be pure gravy.
EDIT: Actually, I hope I didn't offend CM7. It's not a standby "problem," it is a standby compromise, to allow development on other front.
Some PCs have sleep problems because of USB and ACPI quirks unfortunately. They are usually hardware and/or BIOS issues not related to the OS. I think MS tightened down the requirements for Windows certification since. But there are ways to get XP usually sleeping right (I've spent a lot of time on it lol).
swaaye said:
... problems because of USB and ACPI quirks ... usually hardware and/or BIOS issues ...
Click to expand...
Click to collapse
True, lab mainly rocking pre-Prescott p4 Dell-branded boxes, no reason to upgrade, but none can really sleep.
Regarding the LS800, same hardware, different OS, still counts as a software fix. How many thousands of engineers in MS Windows division? There's only three developers for CM7 Nook.
I'd say that merits cutting them some slack, not a lot, just a little, maybe expect fix by year 2015.
If you want sleep issues, try building a hackintosh! At least CM7 turns off the screen and then turns back on again. My hackintosh experiment ran great other than sleep, which left me frustrated to the point of selling off the hardware.
Anyway, I love CM7. Works great on all other fronts. While I appreciate the battery life of stock, everything else is just frustrating by comparison. I'd love to see a nice HC build someday, along with app-makers getting some tablet-compatible updates out (at least so the apps don't force quit). I'm so conflicted on what to run at this point that I dare not try any other ROMs. I don't want all my time on my NC to be in CWM.
iDidItAll4theNookie said:
If you want sleep issues, try building a hackintosh! At least CM7 turns off the screen and then turns back on again. My hackintosh experiment ran great other than sleep, which left me frustrated to the point of selling off the hardware.
Anyway, I love CM7. Works great on all other fronts. While I appreciate the battery life of stock, everything else is just frustrating by comparison. I'd love to see a nice HC build someday, along with app-makers getting some tablet-compatible updates out (at least so the apps don't force quit). I'm so conflicted on what to run at this point that I dare not try any other ROMs. I don't want all my time on my NC to be in CWM.
Click to expand...
Click to collapse
Ran a hackitosh on my eee pc 1000h. Worked fine. Now just dualbooting Win7 and Ubuntu with Burg
Sorry to bother you guys!
I was wondering if it was possible to overclock/undervolt Droid X on the new CM7.
Is there just a kernel to flash to unlock it in the built in CPU controls/SetCPU?
Poking around the web nets to find any article of someone that's done it but I may be a failure at searching -_-
Also, I know CM7 is blazing fast (I'm using it) but I wouldn't be a true android fan if I didn't OC everything I own...duh!
To be honest with you the only things I've read about CM7 on the Droid X was about the BETA release, which is basically a semi-working version so I don't think that CPU Control will arrive for quite some time untill they get the stable release out and about. But by that time I bet the bootloader will be unlocked which means it would just be faster and better to get the normal Android OS from Google.
shukero said:
To be honest with you the only things I've read about CM7 on the Droid X was about the BETA release, which is basically a semi-working version so I don't think that CPU Control will arrive for quite some time untill they get the stable release out and about. But by that time I bet the bootloader will be unlocked which means it would just be faster and better to get the normal Android OS from Google.
Click to expand...
Click to collapse
Actually even the initial release was very useable. Several fixes for broken items (GPS, Camera, etc) were very quickly found and now only a few minor annoyances remain.
CM7 runs on the stock froyo kernel, so overclocking is already avail. I've been using DroidX Overclock (I had bought it some time ago) to undervolt, etc.
There have been some reports of DX Overclock not playing nice with Cm7, but its working pretty well for me.
I've been on it for about 48 hrs now, and I must say it's far more useable than AOSP 2.2 or even 2.3 blur. Faster, and of course, better looking.
My camera is still a bit buggy but I'm not crying about it.
I guess I'll hold in there for CPU control implementation
For now, color me impressed by the CM guys and I highly, highly recommend doing it on your Droid X's.
I just SBF'ed back to 2.2, rooted it and installed the rom via Clockwork. Easy as pie!
Zaphod-Beeblebrox said:
Actually even the initial release was very useable. Several fixes for broken items (GPS, Camera, etc) were very quickly found and now only a few minor annoyances remain.
CM7 runs on the stock froyo kernel, so overclocking is already avail. I've been using DroidX Overclock (I had bought it some time ago) to undervolt, etc.
There have been some reports of DX Overclock not playing nice with Cm7, but its working pretty well for me.
Click to expand...
Click to collapse
I use it as well but it seems that the widget never refreshes. Also when i first tried it, it would just force close until I restarted my phone. So yes you can OC/UV CM4DX.
idk about you guys but the only thing i've really noticed not working is overclocking on boot, I've yet to actually have my settings actually stick on boot.
snwboard333 said:
idk about you guys but the only thing i've really noticed not working is overclocking on boot, I've yet to actually have my settings actually stick on boot.
Click to expand...
Click to collapse
Wait. What are you doing to OC?
It's not built into CM7, right?
use dx/d2 oc to fix oc on boot.
its not rummyd app, itd the less popular one.
been using it and set cpu for while with cm.
Zaphod-Beeblebrox said:
Actually even the initial release was very useable. Several fixes for broken items (GPS, Camera, etc) were very quickly found and now only a few minor annoyances remain.
CM7 runs on the stock froyo kernel, so overclocking is already avail. I've been using DroidX Overclock (I had bought it some time ago) to undervolt, etc.
There have been some reports of DX Overclock not playing nice with Cm7, but its working pretty well for me.
Click to expand...
Click to collapse
I can confirm this, before I jumped ship to the Thunderbolt I had no problems running JRummy's Android Overclock app. I had the "latest module" setting checked, I don't know if that had any effect or not...
faber78 said:
use dx/d2 oc to fix oc on boot.
its not rummyd app, itd the less popular one.
been using it and set cpu for while with cm.
Click to expand...
Click to collapse
Thank you, sir
That app works perfect. I undervolt for normal use then OC when I want to play a game! Wooo. Happy DX user now.
Side note: Is anyone else having issues with the "menu" button not working? It's killing me! Even recovered a previous CM7 when it was working and it refuses to work again. Had it working great yesterday
Hi there,
I was unsure if I should ask this in the Oppo Forum or here, if I am in the wrong place just tell me!
As for my question: I just wanted to know what kernel other user owning the Find 5 and running Omni Rom are using.
I was kind of unable to find a fit when i searched in the Find 5 Forum in "Android Original Development" (this was the right forum right?). So I am happy about any reply. If you could drop a few words on why you use this very kernel, even more!
If I was just plain dumb/blind asking this question cause it was answerd a thousand times before - please give me directions, I really didn't find what I was looking for.
chuSmu
Every oppo find 5 kernel for 4.3/4 is a custom one since coloros is still at android 4.2
Which is what oppo shares on their github.
For 4.3/4 there are AFAIK only two kernels
-based on the omnirom one
-from cfxe http://www.oppoforums.com/threads/a...-y-codefirexperiment-nightlies-weeklies.5630/
Dont know about CM
maxwen said:
Every oppo find 5 kernel for 4.3/4 is a custom one since coloros is still at android 4.2
Which is what oppo shares on their github.
For 4.3/4 there are AFAIK only two kernels
-based on the omnirom one
-from cfxe http://www.oppoforums.com/threads/a...-y-codefirexperiment-nightlies-weeklies.5630/
Dont know about CM
Click to expand...
Click to collapse
Ok, thanks a bunch - that explains it. I concluded from your post that 4.3 kernels work on 4.4 too? Is that correct?
But i thought that there were only two major differences between kernels for the same device and the same
android version - sense and aosp. Your words were "the only ones based on omni rom..." does that mean there are more
differences i have to look out for? Sorry.. i really still am a noob when it comes to kernels and stuff.
Keep in mind that modified system configurations (such as changing the kernel) are NOT supported by Omni.
If you are running a kernel other than the included one, your configuration becomes invalid for any bug reports.
Entropy512 said:
Keep in mind that modified system configurations (such as changing the kernel) are NOT supported by Omni.
If you are running a kernel other than the included one, your configuration becomes invalid for any bug reports.
Click to expand...
Click to collapse
Thanks for the info - I did not know this..it might actually keep me from installing another kernel. It was just that i wanted to toy a little around wih it (after reading some more ^^) simply cause I have never done it before and wanted to experience firsthand how it can affect performance and battery life.
chuSmu said:
Thanks for the info - I did not know this..it might actually keep me from installing another kernel. It was just that i wanted to toy a little around wih it (after reading some more ^^) simply cause I have never done it before and wanted to experience firsthand how it can affect performance and battery life.
Click to expand...
Click to collapse
Many of the tweaks that people install custom kernels for can be simply achieved by altering the tuning settings of their existing kernel.
For example, those who really like battery life may wish to choose the conservative governor and set aggressive up/down thresholds. (up threshold 90 and down of 60 is what I use)
Entropy512 said:
Many of the tweaks that people install custom kernels for can be simply achieved by altering the tuning settings of their existing kernel.
For example, those who really like battery life may wish to choose the conservative governor and set aggressive up/down thresholds. (up threshold 90 and down of 60 is what I use)
Click to expand...
Click to collapse
Yeah that's what I was looking for. Though i failed to realize that these options are provided ^^. It's kinda embarassing cause i only noticed
them when i wanted to switch apps with switchtr and pulled out the sliding bar by accident.
So yeah i had what i wanted all along .. Well anyways ... thanks for providing the settings you use. I'm gonna try them!
chuSmu