Search This thread

Davedog

New member
Apr 11, 2008
4
0
CyanogenMod settings causes an error

Getting a weird error, please help. Have run Fix Permissions several times.



Sorry!
The application Settings (process com.android.settings) has stopped unexpectedly. Please try again. Force close


3.2.0.1 recovery
4.4.07 ROM manager
2.6.32.9 kernel
09202011 CM7
 

zombieflanders

Senior Member
Mar 19, 2011
262
59
If I flashed a brand-new card with the new market (i.e. never had the older market installed), do I need to reflash with an older version, or can I just use the method that clears all data?
 

greenzee

Member
Oct 3, 2007
16
1
I was mucking about the Status Bar tweaks section of the CM7 settings yesterday after installing nightly #199 and I unchecked "Battery Percentage". When I rechecked it, it came back, but with a friend. The cell signal strength icon. I don't know how to get rid of it now. I can change it from signal bars to signal text (it reads -1), but can't get it completely gone. What am I doing wrong?
 

ianPhillips1

Senior Member
Sep 11, 2007
406
84
Hampstead NC
I was mucking about the Status Bar tweaks section of the CM7 settings yesterday after installing nightly #199 and I unchecked "Battery Percentage". When I rechecked it, it came back, but with a friend. The cell signal strength icon. I don't know how to get rid of it now. I can change it from signal bars to signal text (it reads -1), but can't get it completely gone. What am I doing wrong?

Happened to me once a while back, a few reboots took care of it. It's a random bug.

Ian

sent from my ereader
 

runhopskipjump

Senior Member
Dec 20, 2010
208
45
Wow. The the 160 lcd density change fixed SwiftKey tablet x, keyboard for me. It displays all the keys in landscape mode now and made the keyboard bigger in portrait mode. The numbers also now appears in landscape mode along with finally functional space keys. This is how this keyboard was meant to be used.

So you could now get yourself a copy if you were holding off on purchasing SwiftKey due to these issues. The I am assuming that the keyboard relied on the current lcd density of screen to display properly. Before the change it displayed like SwiftKey x for phones; with same keys and a mangled landscape mode. Cheers to all.
 
  • Like
Reactions: Arbelzapf

excarnate

Senior Member
Nov 4, 2010
113
6
Wireless off on boot

I searched as far back as May, and didn't see anything about this.

When I boot my Nook Color (running from a card) wireless is off. I believe this used to work but it has been broken so long I'm not sure if I'm misrememberating that. This is on recent nightlies, before and after the hiatus. Currently 09222011.

I asked in Q&A and was told this was a problem in recent nightlies. Any chance for a fix so on boot it respects the state of wireless before rebooting/shutting down? Or if nothing is planned, hey! Please fix it! :)
 
  • Like
Reactions: whale2

oldman_58

Senior Member
Jul 13, 2010
1,190
276
Sunny Florida
I searched as far back as May, and didn't see anything about this.

When I boot my Nook Color (running from a card) wireless is off. I believe this used to work but it has been broken so long I'm not sure if I'm misrememberating that. This is on recent nightlies, before and after the hiatus. Currently 09222011.

I asked in Q&A and was told this was a problem in recent nightlies. Any chance for a fix so on boot it respects the state of wireless before rebooting/shutting down? Or if nothing is planned, hey! Please fix it! :)

From Terminal window

Type:
su

then copy and paste the following
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db

delete from system where name = 'airplane_mode_on';
.exit

exit
exit
reboot and see if that fixes the problem.
 
  • Like
Reactions: excarnate

akenis

Senior Member
Dec 22, 2007
805
84
Google Pixel 6
Google Pixel 7 Pro
Well I downloaded LCD density like people have been talking about. Not sure what to set for the reboot option, but now I can see movies in market.

But the my apps screen is all dorked up? Its like a split screen.....

And my calendar pad pro 4x1 widget won't scale to fit my screen with zeam launcher. I have workspace set to 6x8. Normally Zeal will ask and I tell it to try to fit the widget to 6x2.

So what's new in the 200 build. Is 160 resolution default?

Sent from my NookColor using XDA Premium App
 

koopakid08

Senior Member
Jun 24, 2011
891
239
Well I downloaded LCD density like people have been talking about. Not sure what to set for the reboot option, but now I can see movies in market.

But the my apps screen is all dorked up? Its like a split screen.....

And my calendar pad pro 4x1 widget won't scale to fit my screen with zeam launcher. I have workspace set to 6x8. Normally Zeal will ask and I tell it to try to fit the widget to 6x2.

So what's new in the 200 build. Is 160 resolution default?

Sent from my NookColor using XDA Premium App

Yep default dpi is 160.

Sent from my NookColor using Tapatalk
 

excarnate

Senior Member
Nov 4, 2010
113
6
From Terminal window

Type:
su

then copy and paste the following
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db

delete from system where name = 'airplane_mode_on';
.exit

exit
exit
reboot and see if that fixes the problem.
Someone on my original Q&A thread suggested Android Assistant, which showed airplane mode being on. Of course airplane mode was off in the Preferences.

This is something that shouldn't require a special program, or fancy database commands. I assume this is a bug and is on the list to fix? If not, why not?
 

oldman_58

Senior Member
Jul 13, 2010
1,190
276
Sunny Florida
Someone on my original Q&A thread suggested Android Assistant, which showed airplane mode being on. Of course airplane mode was off in the Preferences.

This is something that shouldn't require a special program, or fancy database commands. I assume this is a bug and is on the list to fix? If not, why not?

My understanding is if you set Airplane mode 1 time the Nook programming does not have the ability to unset Airplane mode, the scripting will prevent that from happening while you are on that particular build, it is a flaw, that has been around since the beginning, if you run the DB commands it will fix your problem.

You may do as you choose, this is a proven method to resolve your issue.
 

ianPhillips1

Senior Member
Sep 11, 2007
406
84
Hampstead NC
My understanding is if you set Airplane mode 1 time the Nook programming does not have the ability to unset Airplane mode, the scripting will prevent that from happening while you are on that particular build, it is a flaw, that has been around since the beginning, if you run the DB commands it will fix your problem.

You may do as you choose, this is a proven method to resolve your issue.

If you put an airplane toggle on the desktop you should be able to turn airplane mode off

Ian

sent from space
 

excarnate

Senior Member
Nov 4, 2010
113
6
My understanding is if you set Airplane mode 1 time the Nook programming does not have the ability to unset Airplane mode, the scripting will prevent that from happening while you are on that particular build, it is a flaw, that has been around since the beginning, if you run the DB commands it will fix your problem.

You may do as you choose, this is a proven method to resolve your issue.
I'm sorry, I have to disagree. This is a proven method to work-around a bug until the next time a build (nightly?) is flashed, and is by no means an excuse to leave a bug in the source. Not pointing my finger at you, certainly. I appreciate your excellent and clear instructions.

My question, which still stands, is: Is someone going to fix this? It certainly won't be me, I'm not a programmer, and it would be unwise to have me mucking around with code :)

This problem only exists, AFAIK, on the Nook Color. It doesn't happen on my glacier, it doesn't happen on my wife's shadow.

To answer ianPhillips1's suggestion to put an airplane toggle widget on the desktop, I'll try it, but I note that in the Preferences it showed airplane mode as unchecked, which is why the Android Assistant was recommended (elsewhere).

Because the problem persisted through updates, I wonder if maybe the scripting might work for me until I (personally) erase entirely. Still, it doesn't help all the other folks with this problem.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 50
    In an effort to completely document the "Going to CM7 and Coming Back from CM7" experience for myself and my fellow rooters, I have compiled the following diary of install. Please let me know if there are missing steps or extraneous steps that can be removed. Remember please that I am trying to COMPLETELY document the process (at least as much as pertains directly to CM7) and the audience is for everyone, even real noobs who you know will be trying this and crying about some dumb mistake. Thanks for your feedback.




    Before beginning:
    1. Booted into Recovery
    2. Created new nand backup
    3. Removed and stored MAIN sd

    Using a new and different sd:
    1. created 4gb CWR_ext4_0.1 bootable SD [Followed process here: http://xdaforums.com/showthread.php?t=959240]
    2. moved flashable zip of CM7 to SD [edit: now using latest nightly found here: http://forum.cyanogenmod.com/forum/228-nightly-builds/]
    3. moved latest gapps to SD [Found here: http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
    4. moved latest Froyo/CM7 overclock kernel to SD [Found here: http://xdaforums.com/showthread.php?t=925451]
    4. insert into NC

    Installing
    1. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
    2. 'mounts and storage' --> format /system ; /data ; /cache
    3. back to main menu
    4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "latest_CM7_nightly.zip"
    5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "gapps-gb-20110120-signed.zip"
    6. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "update-1100mhz-froyo_CM7-emmc-cwm.zip" [if desired]
    7. 'mounts and storage' --> unmount sdcard --> remove sdcard
    8. reboot

    First Boot
    1. (got chills seeing that little cm7 droid boot animation)
    2. @ Welcome to NookColor --> waited full 5 minutes for system to settle (?)
    3. tapped Droid to begin setup
    4. waited for Notification Bar to show WiFi available --> dragged down to open
    5. Selected my router and logged in
    6. Used built in 'Back Button' in top right of notification bar to go back to setup
    7. @ Set up your Google Account --> signed in
    8. @ Market Apps Installer - IMPORTANT: Read This! --> OK
    9. @ Choose the apps to install --> preference i guess (gmail and google search were already installed - I added YouTube) --> ok
    10. above took me to YouTube install screeen from market, seleceted Install then OK
    11. @ Use Google Location --> i uncheck both since it's not a phone --> Next
    12. @ Back up data --> i uncheck again --> Next
    13. "Your Google Account is now linked to this phone" --> Finish setup
    14. now to set time prefferences --> personal preference here (set time zone and current time will adjust) --> Next
    15. WOOT! CM7 Home Screen!
    16. Open Apps --> Settings --> CyanogenMod Settings --> Lockscreen --> Style Options --> Lockscreen style --> change to Sliding Tab (this is because the Rotary wheel isn't sized right yet and is real hard to use currently)
    17. back @ Settings --> Applications --> check allow for Unknown Sources
    18. open Market --> downloaded Titanium Backup
    19. Ran batch restore to replace missing user apps
    20. Open and tested each user app (some worked, some didn't - but it's early)

    First Backup
    1. Power off NC
    2. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
    3. 'backup and restore' --> 'Backup' (this creates nand backup to the SD card of the installed system)
    4. 'mounts and storage' --> unmount sdcard --> remove sdcard
    5. reboot

    First Nightly Update
    1. Download latest nightly (http://forum.cyanogenmod.com/forum/228-nightly-builds/)
    2. Place new file onto the bootable ext4 SD
    3. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
    4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "latest_nightly.zip"
    5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "update-1100mhz-froyo_CM7-emmc-cwm.zip" [if needed, at this time the nightly will restore original clock speed]
    7. 'mounts and storage' --> unmount sdcard --> remove sdcard
    8. reboot

    Restoring a nand backup of CM7
    1. Power off NC
    2. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
    3. 'backup and restore' --> 'Restore' (select the backup you wish to restore - usually one with most recent date)
    4. 'mounts and storage' --> unmount sdcard --> remove sdcard
    5. reboot

    Reverting back to any other AOSP
    ********************************
    **This requires having a seperate SD card or overwriting the image of the ext4 card
    **All files needed are available as part of the
    ** "Monster RootPack/Clockwork Recovery 3.0.0.5 SD" [http://xdaforums.com/showthread.php?t=922870]
    ** "Nook Color Restore to Stock" [http://xdaforums.com/showthread.php?t=914690]
    **You will need the following files:
    ** CWR-removal.zip (both threads have a CWR removal file or two, take your pick)
    ** repartition-boot-with-stock.zip
    ** your most recent NON-CM7 nand backup -OR- your preferred stock recovery .zip
    ********************************
    1. Power off NC
    2. boot with bootable sd (original_CWR - ClockworkMod Recovery v3.0.0.5) [one made using the Monster RootPack thread]
    3. 'mounts and storage' --> format /system ; /data ; /cache (this is for good measure)
    3. back to main menu
    4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "CWR-removal.zip"
    5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "repartition-boot-with-stock.zip"
    *********************************
    ** If restoring to a nand backup, skip to step 9
    *********************************
    6. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "nook-complete-restore-1.0.x.zip"
    7. 'mounts and storage' --> unmount sdcard --> remove sdcard
    8. reboot (you should boot to stock and unrooted)(AND DONT DO STEPS 9-11) [you can now re-root with autonooter instructions]
    *********************************
    ** Only complete these steps if restoring a nand backup and NOT restoring to stock
    *********************************
    9. 'backup and restore' --> 'Restore' (select the backup you wish to restore - usually one with most recent date)
    10. 'mounts and storage' --> unmount sdcard --> remove sdcard
    11. reboot (you should be back to a working version, rooted and full of joy)
    43
    Signal bars
    Signal icon should be fixed in next nightly: http://review.cyanogenmod.com./#change,10233

    SOD
    Also, please test the kernel. This silly SOD problem is the bane of my existence because I cannot reproduce. Really need someone to give feedback on that kernel so I know how to move forward.

    ICS
    Work is underway to get legacy device(thats us) to work with ICS. These legacy hal changes will make it easier to support the Nook Color but we still need to either backport DSS and SGX drivers for update to a new kernel. Both of these options are a good bit of work and won't happen overnight so please be patient. =)
    33
    2.6.32 kernel for CM7 is mostly complete.

    + Sleep fixed
    + Able to build a new wifi module finally. *Should* fix wifi issues.
    - Hardware overlay does not work
    - No bluetooth yet. We are trying a completely different method to init and communicate with bluetooth. This will take a little time.

    No hardware overlay causes higher resolution videos to be a little choppy. I am going to continue to work on this tomorrow and hopefully have something to post.
    28
    QUICK FAQ - 2/19/11

    Q: WHAT IS THIS?

    A developer port of Cyanogenmod 7 for the encore device, which has been in development for about two months starting in early January and has only recently been deemed good enough for a wider range of developers to use.​

    Q: WHERE TO GET NEWS ON PROGRESS?

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

    We are usually in #nookie on freenode.

    You can always check the Cyanogen git@ http://github.com/cyanogenmod

    Q: WHAT WORKS AND WHAT DOESN'T?

    As of this writing, most things do work-- touchscreen, wifi, sound, accelerometer, etc.
    See the issue list here: http://xdaforums.com/showthread.php?t=960537

    Q: How do report a bug I find?

    PLEASE post logs to pastebin.com and include them in your report.
    To grab android logs you can run "adb logcat -d > log.txt"
    This will output the log to the log.txt file and can then be posted on www.pastebin.com

    Kernel logs can be had by running "adb shell dmeg > dmesg.txt"
    This will output the dmesg log to dmesg.txt for easy posting on www.pastebin.com

    Use this template to post a bug in this thread:

    --------------------------------------------------------------------------
    Which build are you running? Please mention any customizations:
    App or process having the problem:


    Steps to reproduce the problem:




    Describe the issue as well as you can:





    Relevant logs(logcat, dmesg)


    ----------------------------------------------------------------------------

    Q: WHO PORTED THIS?

    Cyanogenmod itself is the creation of thousands of developers.

    A vast team from around the world including members of Team Douche as well as unaffiliated individual developers have been collaborating for about two months on this port. Additional contributions continue to come from around the Internet. You are invited to help by contributing YOUR fixes.​

    Q: WILL CM7 RUN OFF OF AN SD CARD? OR DOES IT USE THE INTERNAL STORAGE OF MY DEVICE?

    The nightly builds are intended to run entirely off the internal storage device. Should you decide to install one of those .zip files, you should expect to overwrite whatever was installed in those partitions.

    It is critical to understand that CM7 is development software that may cause serious issues, loss of data, and/or other problems with your device and to your life in general. By loading and/or running the software, you must understand and accept full responsibility for your actions and all consequences and agree to adhere to the varied licenses and terms and conditions that comprise the software.

    Q: IS THERE AN SD-ONLY "BOOTABLE" VERSION?

    Not from the nighty builds. However-- should someone want to create such a bootable SD-- (warning: Slightly technical answer:) all it would take to create one is a new uRamdisk file with the partitions in init.encore.rc pointing to the correct partitions on the SD card.​

    Q: I AM AWARE OF THE RISKS AND ACCEPT RESPONSIBILITY FOR WHATEVER RESULTS. WHERE DO I GET THIS?

    Cyanogenmod 7 for encore is available as a nightly build. See the XDA dev thread for download and development discussion:​

    Q: WHAT IS "ENCORE" ANYWAY?

    Cyanogenmod has a fun little convention to name ports after the device's original project name.​

    Q: WHERE IS THE SOURCE?

    On Github.com.​

    Q: I'M A "TECCHY" PERSON-- WHAT KERNEL DOES THIS USE?

    A somewhat-modified version of the "stock" 2.6.29 source provided by Barnes & Noble (in accordance with the GPL). Changes to this kernel include a fix for a temperature bug, a fix to a cache race-condition resulting in kernel panics, ext4 support, and support for large block devices, among other things.

    A port to 2.6.32 is currently underway that may facilitate improved "deeper" sleep.​

    Q: IS THE KERNEL OVERCLOCKED?

    Just like the original stock kernel, the CM7 kernel runs at 800Mhz. However, you may overclock the default kernel to 925mhz through Cyanogenmod Settings. Cyanogenmod has a policy to not include voltage modified kernels. If you want a faster overclock see Dalingrin's 1.1 Ghz kernel: http://xdaforums.com/showthread.php?t=925451

    Use entirely at your own risk.​

    Q: WHAT ARE THESE OTHER VERSIONS OF CM7-BASED ROMS?

    Because CM7 is open-source software, people are free to modify it as they wish and re-release, provided they are compliant with the terms of the original licenses. The CM7 developers have nothing to do with these derivative releases, which may or may not be of decent quality.
    Q: WHEN WILL THE FINAL VERSION BE RELEASED?

    When it's ready. Please do not ask this, as it is considered the mark of a newb. In the meanwhile, nightlies are rolling out every evening with the improvements from that day, not only to the encore port in particular, but to Cyanogenmod in general.​
    16
    ooop sorry i meant a flashable zip with just the new driver and installable on existing cm7.1 release.

    thx.

    I created flashable zips that just installs the files needed to fix the signal bar issue and wifi driver to prevent SODs. I have shown the links below. Just install with CWM Recovery or ROM Manager. To install with RM, go to "install ROM from SD" and follow prompts. Be sure to choose "wipe Dalvik". These work with emmc installed CM7. I don't know if they work with SD installs.

    This zip is for CM 7.1 stable and recent nightlies that have the 2.6.32.9 kernel. (Look in settings/about tablet)

    Install zip (SOD fix only):
    http://d01.megashares.com/index.php?d01=8VPCE7N

    I am also including a zip for recent nightlies (234 and above) that have signal bar issues.

    Install zip (SOD fix and signal bar fix)
    http://d01.megashares.com/index.php?d01=KFyOSYg

    I am also providing the links for just the files if you want to install them manually.

    Wifi driver/module:
    http://www.mediafire.com/?61b1nzzt8kq62hx

    Signal bar fix:
    http://d01.megashares.com/?d01=ed8d5d9

    Thanks to Embedded and Keyodi for the original files.