• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[DEV] CM7 Developers Thread

Search This thread

derekr

Senior Member
Mar 1, 2011
176
21
Boston
Haven't installed yet, but for those with SD card problems, I have found similar problems each time I upgrade to a new nightly. A reboot fixed it each time. I'm not saying that's the problem this time, but it's worth a shot.

___________________
- Derek
 

ziggy34

Senior Member
Sep 2, 2010
1,147
272
SE Michigan
Would some one go to the Android Market and try to download and install the Free version of Aldiko Book Reader.

When I do, I get Installation Error.
Couldn't install on USB storage or SD card.

When I updated to the 7.1 last night, when I rebooted, Aldiko which had a shortcut on the home screen just showed a Generic Android Icon and would not launch and when I tried to reinstall last night, it said App was already installed and did I want to replace and it would not install, I did a full wipe and reinstall of 7.1 and now it just gives the above error on install.

thanks.
 

Gin1212

Senior Member
Jan 26, 2011
344
34
Since others are claiming a snappier kernel then the original .29 kernel that was being used. Would love to see some quadrant scores so we know what to expect when we start seeing OC kernels.
 

MedLine

Senior Member
Feb 27, 2011
197
29
running CM7 2.6.32.9 test build.

maybe just me, i think my nook not entering deep sleep. this is based on observed standby battery drain (still 1%/hr), looking at battery history in spare parts, and report from CPU Spy app by storm717 (http://forum.xda-developers.com/showthread.php?t=1011497), attached screenshot after 4 hours standby with wifi off.

will wipe and reinstall, try again with sleep.

what is intended "level" of sleep with test build? is the wakelock still in place?

otherwise everything works except same USB SD card issue.

EDIT: format system/data/cache, flashed test 2.6.32.9, booted virgin build no gapps, still no deep sleep. great build otherwise, whereas with 042411 OC kernel power felt extravagant everything here feels SMOOTH. thanks for letting us test the builds and kernels.
2nd EDIT: played around with it bit more, wanna emphasize how SMOOTH this test build is. disagree with other posters, when CM7 2.6.32.9 deep sleeps would prefer this over any OC.
 

Attachments

  • screenshot.jpg
    screenshot.jpg
    19 KB · Views: 347
Last edited:

12paq

Senior Member
Aug 16, 2010
1,155
367
Colorado
www.DonAshcraft.com
Haven't installed yet, but for those with SD card problems, I have found similar problems each time I upgrade to a new nightly. A reboot fixed it each time. I'm not saying that's the problem this time, but it's worth a shot.

___________________
- Derek

Yup, the first things I tried after seeing the SD app problem were to reboot, reinstall and flash back to the current nightly and back to the test build. I tried reinstalling the apps via Titanium Backup to sd and no go. I can see the sd card via a file explorer on the Nook, but the apps are not showing as installed and will not let me install them to sdcard. I have also checked in settings to allow apps to be installed by location tried all that...

I know to check everything I know before I post here, you guys don't miss a thing! ..and I do, lol.

Dalingrin posted in the op about many potential unknown issues, maybe this is one? But he wanted to here fromus wifi problem guys.

On the plus side, still rocking solid wifi with no drops or reconnect issues like I had to some degree on all kernels but far more frequently with the latest oc test kernels 4/11 - 4/24. With this test version nobdrops at all so far.

Edit: just had wifi turn spontaneously on its own. Not the normal drop with wifi signal icon unchanged I was experiencing in the past, this just shut wifi off by its self. I manually turned it back on and alls well. I will monitor it more and see if this was an isolated event.

Edit 2: The performance and responsiveness is very impressive at only 800 MHz. foreshadowing of things to come... ? :)
Wifi still solid, major difference in reliability and connection.

Edit 3: Changed my router to AES cipher mode and wifi dropped. Could not reconnect at all, forget networks, reboot, all tried.
See Logcat attached.
 

Attachments

  • alogcat.2011-05-01-11-48-25-0600.txt
    61.3 KB · Views: 9
Last edited:

JoshMiers

Senior Member
Feb 4, 2010
58
85
When I updated to the 7.1 last night, when I rebooted, Aldiko which had a shortcut on the home screen just showed a Generic Android Icon and would not launch and when I tried to reinstall last night, it said App was already installed and did I want to replace and it would not install, I did a full wipe and reinstall of 7.1 and now it just gives the above error on install.
thanks.
I have the same issue with Aldiko.

maybe just me, i think my nook not entering deep sleep.
Same here. Spare Parts still shows the Nook as running 100% of the time. I checked /sys/power/wake_lock and there isn't the "1" value hack that was there on previous kernels, so something else is preventing it from sleeping.
 

Slack3r

Senior Member
Feb 17, 2009
266
53
Just flashed the test build, no problems so far. HQ videos on youtube play with no issues, and everything else I've tried seems pretty smooth so far, lack of an OC kernel aside :p

I'm using the flash player from the 1.2 update, not sure if that would affect playback or not.
 

MACLUIS1

Senior Member
Jan 12, 2011
88
10
The weird thing. I had not been able to play the opening video of Hero of Sparta from gameloft on any of the builds nor kernels, and now on this kernel (.32) I can. Can't play the game yet, though.

Sent from my NookColor using XDA Premium App
 

ziggy34

Senior Member
Sep 2, 2010
1,147
272
SE Michigan
Yup. I have trouble with other apps that have been installed to sd such as angry birds as others are reporting as well, maybe your Aldiko was installed to sd somehow?

Sent from my NookColor using Tapatalk

Not sure what's going on, On a clean wipe and install of CM7.1 I get the following when I try to install Aldiko

Installation Error.
Couldn't install on USB storage or SD card.

Unless I am missing something in settings, I never install apps to SD, there is more than enough internal memory for apps.
 

MedLine

Senior Member
Feb 27, 2011
197
29
ironic.

been waiting all this time to punch that SOD in the face.

Same here. Spare Parts still shows the Nook as running 100% of the time.

now it won't deep sleep.

EDIT: this is frustrating. since i already wiped and flashed i went ahead and wiped again and flashed Stock 1.2 update.zip (nemith) + MN 4.4.28 (GabrialDestruir). using CPU Spy i measured CPU activity for 10 minutes of standby with wifi on (screenshot_1) and 10 minutes of standby with wifi off (screenshot_2). stock neutered B&N 1.2 froyo with 2.6.32 kernel only spends 1/3 of time in deep sleep with wifi on, but with wifi off goes straight to deep sleep and stays there. probably why standby battery life so strong. in my heart i feel that CM7 SOD a thing of the past :mad:, just need to get to deep sleep to prove it. i mean, come on, this is what we've all been waiting for.
 

Attachments

  • screenshot_1.jpg
    screenshot_1.jpg
    20.1 KB · Views: 216
  • screenshot_2.jpg
    screenshot_2.jpg
    19.8 KB · Views: 203
Last edited:

Nburnes

Senior Member
Sep 4, 2010
1,327
976
Not sure what's going on, On a clean wipe and install of CM7.1 I get the following when I try to install Aldiko

Installation Error.
Couldn't install on USB storage or SD card.

Unless I am missing something in settings, I never install apps to SD, there is more than enough internal memory for apps.

That is automatically installing it to your SD. Market does that with some applications which is why you and I and other people are getting that error. Just have to wait for dal to look into the SD issue.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 97
    Please limit this thread to development comments and questions!
    The users thread is for all other posts.
    When in doubt, post in the users thread.


    After many long nights of banging our heads against keyboard, the CM7 port is finally shaping up.
    In addition to nightly releases, we may from time to time be releasing test builds here for your feedback and enjoyment. If you find issues please feel free to post here in this thread. Leave all other feedback for the user thread.

    Where to get progress news:

    I will tweet progress from time to time.
    Twitter: @dalingrin

    We are usually in #nookie on freenode.

    You can always check the Cyanogen [email protected] http://github.com/cyanogenmod

    Current Issues

    DO NOT FORMAT YOUR SD CARD IN CM7. DUE TO A VOLD ISSUE THIS WILL FORMAT YOUR /BOOT INSTEAD OF THE SD CARD!
    ****Should be fixed in nightly 13****

    -Standy battery life is not as good as stock
    Because of a kernel bug CM7 does not fully sleep. The result
    is ~1% battery drain per hour while the screen is off. With normal use I usually go
    1 - 2 days between charging.
    ***fixed in 2.6.32 builds***

    -A few apps do not scale to full screen
    In order to get Market and Maps to work fully the lcddensity has to be
    set to something other than 160 causing a few apps not to scale properly.

    -Wifi slow to reconnect at times
    ****fixed****


    -Video playback is slow
    ****fixed****

    -Default rotary lockscreen does not fit screen
    ****fixed****

    -Market partially works
    ****fixed****

    -Bluetooth does not work
    ****Update**** Bluetooth now works in CM7.
    Bluetooth is working seemingly perfect except for the range. Unfortunately, the range is terrible.
    Depending on the device you are paried with, the range is between 1-5ft. Any ideas on how to
    fix the range issue would be much appreciated.

    -Do not use SetCPU profiles
    If you enable SetCPU profiles it will become a runaway process eating 100% cpu.
    Setting your cpu clock can be done in Cyanogenmod Settings. Under Performance->CPU Settings

    -Internal storage partition is not mounted on boot and is not shareable via USB
    ****fixed****


    Download and Install

    MUST USE 3.0.1.0+ RECOVERY:
    This is installable ONLY with an ext4 aware Clockwork Mod Recovery.

    *** Also it is critical to be aware that installing CM7 will write to the internal emmc of your device. You are advised NOT to try it. But if you choose to do so, understand you do so entirely at your own risk. Read sections 15-17 of the GPL for the gist of this disclaimer. There is no warranty or claim of usefulness or fitness for any particular purpose. No one but you shall accepts responsibility for what may happen if you download or try to use this development software. ***


    Download for CM7:

    Nightlies
    :
    http://mirror.teamdouche.net/?device=encore

    Install instructions:
    http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
    30
    ENCORE 2.6.32 BETA QUICK FAQ
    ----------------------------


    WHAT'S THIS?

    Tonight, we can report to the American people and to the world, the CM7 team has conducted an operation that killed the "Sleep of Death" responsible for the senseless battery consumption of thousands of encore devices.

    Or put another way, the CM7 for encore team is proud to release a beta .32 kernel to play with. Try at your own risk.​


    WHO IS RESPONSIBLE FOR THIS?

    Verygreen, FatTire, and Dalingrin did most of the work on this update. Verygreen worked tirelessly on 2.6.32 and 2.6.35 ports of the kernel. An extra special thanks should go to him.
    We hope to use his work to eventually get newer 2.6.35+ kernels for the Nook Color.​


    WHY DO I CARE ABOUT THE .32 KERNEL? HOW'S IT BETTER THAN THE .29 KERNEL?

    It's .03 better, obviously.

    Beyond the sleep improvements, most benefits are "behind the scenes" technical fixes.

    Still, you may notice that the On/Off animation now works and that you experience subtle performance benefits that come from a new kernel. For a generic writeup of .32 features (much of which doesn't apply to the encore), see:

    http://kernelnewbies.org/Linux_2_6_32


    SO WHAT WORKS?

    * basic CM7
    * sound
    * accelerometer
    * backlight
    * wifi
    * EXPERIMENTAL bluetooth (uses new uim/kim method and .bts files)
    * video w/overlay
    * Screenshots
    * usb mounting to your computer
    * sdcard support


    WHAT DOESN'T WORK?

    * Sleep while while charging or connected to USB
    Workaround: Settings->Applications->Development->Stay Awake

    Maybe more, you tell us. Is it stable? Can you make it crash/reboot?

    Probably. This is a beta for a reason.​


    CAN I DROP THE UIMAGE KERNEL FILE INTO A 2.6.29 CM7 SYSTEM?

    No.​


    WHY NOT?

    There are several changes to the installation which make .32 incompatable with previous CM7 installations. Among them are:

    * The kernel's orientation is now native to the encore's screen. No android rotation is needed
    * The WIFI module is different
    * The method of installing BT is different.
    * The GFX (2D acceleration) drivers are different​


    IS THIS .32 KERNEL OVERCLOCKED?

    Not by default. The clock options are the same as the .29 kernel... for now.​


    WHAT ARE THE CHANGES TO BLUETOOTH?

    Bluetooth now uses the wilink driver with a "shared-transport" system that allows both bluetooth and the FM radio to work. Right now, the FM radio isn't enabled at all, as reports say the hardware support (antenna) is not connected. However, this new system makes it at least conceivably possible to use.

    Also, the new system utilizes Texas Instrument's .bts (bluetooth script) method for installing the bt firmware.​


    SO DOES THIS FIX THE BT RANGE ISSUE?

    This is all brand new-- Bluetooth range has not been extensively tested. That is for you to test.

    There are several versions of TI's bluetooth initialization script, called the "bts" script. You can get them here:

    https://gforge.ti.com/gf/project/wilink_drivers/

    The .bts files (such as TIInit_7.2.31.bts) may be placed in:

    /system/etc/firmware

    and will automatically be loaded when needed. Try different versions and experiment to see if some work better others. (Watch the log and dmesg to verify that the bts script is running properly)​


    CAN I MAKE THE FM RADIO WORK?

    The encore device is reported to not have a physical antenna connection to allow the FM radio to function.

    However, this is unexplored territory. If you are a developer and would like to experiment, you may notice that TI makes the following additional firmware files available:

    fm_rx_init_1273.2.bts
    fm_tx_init_1273.2.bts
    fmc_init_1273.2.bts

    These scripts are now potentially loadable into the wifi chip. To make CM7 believe that there is a working FM radio, add to the board file:

    https://github.com/CyanogenMod/android_device_bn_encore/blob/gingerbread/BoardConfig.mk

    the following line:

    BOARD_HAVE_FM_RADIO := true

    And recompile. Good luck!​

    IS THE BRAINFUCK SCHEDULER (BFS) INCLUDED?

    Not yet. We're investigating whether this would be worthwhile.​


    WHERE CAN I GET SOME OF THE KERNEL SOURCE FOR THIS BETA TEST?



    WHAT HAPPENED TO VERYGREEN'S 32 PORT?

    When BN released their .32 kernel, portions were migrated to Verygreen's in-progress .32 kernel source, which in turn was a modification of the .32 kernel from omapzoom.com. At the same time, fixes that were in verygreen's repository were migrated over to the BN source.

    Thus, the CM7 team ended up with *TWO* working versions of the .32 kernel.

    After some discussion, it was decided (for now) to use the source that originated from BN. This will hopefully free us to move to 2.6.35+ quicker.​
    17
    Some eye catching changes in CM7 as of late,

    Not entirely sure if these changes are what I think they are... hardware acceleration in Gingerbread?
    http://review.cyanogenmod.com/6831
    http://review.cyanogenmod.com/7062

    And an update to the Nook kernel, from Dalingrins twitter it seems it may only be one change having to do with USB support...

    http://review.cyanogenmod.com/6995

    any thoughts?

    We are in the middle of merging OMAPZoom framework changes primarily for OMAP4 device support(3D, new DSP, etc) but much of it affects the Nook as well. Media playback should improve somewhat for the Nook. Thus far I have new DSP codecs working but the overlay still needs some work.

    The kernel commit that was finally merged is just some kernel clean up to eliminate possible causes of instability and SOD. No new features yet.

    My 1st priority is to get the OMAPZoom framework changes merged because it affects multiple devices. After that I will focus back on the kernel hopefully figure out SoD and such.

    Longer term, TI has been working on an OMAP3 2.6.35 kernel finally and I would like to look into that for the Nook down the road.
    13
    Beta testers come free, I'm using Firefox 8.0 alpha1 as my primary browser just to illustrate and have participated in beta testing Windows Vista and Windows 7; As far as employing developers, the "upline" Cyanogen Mod team is made up of around 10 members plus about 5 maintainers for the Nook. I'd imagine that about 5-6 full time employed developers could handle that workload(someone correct me if I'm wrong) at about $90,000 a year per developer, that's about half a million a year for a team. B&N 2010 revenue was 6.92 billion dollars just for example, I think they can afford a few full time developers, not to mention the much bigger companies like Samsung and Motorola.

    Even with that said, Google does a good deal of the work, it seems companies must spend more time stripping out the features Google includes in AOSP than implementing useful features...

    Maybe I'm missing something, but it seems to me that these companies could be doing a much better job with their Android ports, considering what some hobbyist and skilled developers produce in their free time...

    One thing that I think the big OEMs need to change is how they organize their device development. If you look at how CM works, it is one source for all devices. All devices use the same branch. Instead of hacking up the Android framework to get feature X to work on device Y, we make it work in a device agnostic way. This is something that Samsung and others don't seem to always do. They have separate trees/branches for even the same devices(all the galaxy S variants). The end result is a mess and it makes it much more difficult to get timely updates to your devices. Additionally, some random person may decide to contribute a new feature to Android and with very little effort all CM devices reap the benefits(such as the recent boot speed up). Fixing problems at the device level can be more difficult than hacking the framework in the short term but in the long term it makes maintaining and improving Android much easier.

    I haven't been a part of CM for that long but I am definitely proud of how a small group of folks that work on something part time have been able to achieve what they have. While it can be aggravating that CyanogenMod gets kanged so much with little or no credit, I guess its better than no one wanting your work.
    11
    Developer Tips

    (Standard do-at-your-own-risk-and-responsibility disclaimers apply.)

    * For those developers building from source:

    In $OUT, you'll find a few files:

    recovery.img --> rename to uRecRam
    kernel --> rename to uRecImg

    Now you've got the ext4 clockworkmod for mmc built from source.

    * Also, there's also a script in $OUT called:

    sd_ramdisk_packer.sh

    Assuming this works, it should repack your $OUT/root (mmc ramdisk) into a uRamdisk that can be used with a bootable SDcard. The stuff in /system would go in the /system partition of the SD card (p2).

    The result: a bootable CM7 on SD. It may not be wise to distribute as Cyanogenmod for encore is a fast-moving target-- unless you plan to create a new one every day or something.

    * If you don't like the buttons at the top for some reason, there's the SoftKeys app as well as Button Savior.

    * There is a slightly-themed u-boot.bin in device/bn/encore/prebuilt/boot/. It is simply a recompiled u-boot from BN's source.​

    encoreboot.png


    Info about emmc geometry

    If your emmc is hosed and you want to start COMPLETELY from scratch, understand that the underlying geometry (before any partitions are created) of your emmc must be set up correctly on OMAP machines such as the nook before any partitions are created.

    You can read more about that stuff here. If you are booted into an "emergency" SD card and have a totally hosed emmc, you can use fdisk to format /dev/block/mmcblk0 to the correct geometry, and then create the partitions one at a time, with a vfat partition as your /boot partition (p1). Then put mlo, u-boot.bin, uImage, uRamdisk, uRecImg, and uRecRam in /boot (p1) and you should have a bootable system.

    Read the link above about SD/MMC formatting for OMAP3. Your nook is an OMAP3621, so you gotta get that geometry right, otherwise it won't boot. Luckily, the instructions on using fdisk are pretty good.

    More info:

    your emmc: /dev/block/mmcblk0
    your sd: /dev/block/mmcblk1

    Partition Info

    the partitions you should have created are at:

    /dev/block/mmcblk0p1 == /boot
    /dev/block/mmcblk0p5 == /system
    etc

    /boot, /rom, and /media are of type "vfat"
    /system, /data, and /cache are of type "ext4"

    /factory (p3) isn't used by cm7

    partition 4 is just there to allow you to create partitions 5-8

    Sample instructions for copying files from cm7 update.zip on local computer to emmc /boot

    You should be able to copy those four files simply by getting the lastest cm7, unzipping it on your computer, then once you boot into your bootable SD card, do:

    Code:
    COMPUTER> adb shell
    # mkdir /data/bootmountpoint
    # mkdir /data/systemmountpoint
    # mount /dev/block/mmcblk0p1 /data/bootmountpoint
    # mount /dev/block/mmcblk0p5 /data/systemmountpoint
    # exit
    COMPUTER> adb push mlo /data/bootmountpoint/
    COMPUTER> adb push u-boot.bin /data/bootmountpoint/
    COMPUTER> adb push uImage /data/bootmountpoint/
    COMPUTER> adb push uRamdisk /data/bootmountoint/
    COMPUTER> adb push  my/path/to/sdcard/system /data/systemmountpoint/