[NIGHTLY][ROM][4.0.4][IMM76I] CyanogenMod 9 for Samsung Galaxy S

Search This thread

fipsib

Senior Member
Jan 16, 2011
589
785
Munich
I think I found something:
- Turn on auto-rotation via toogle in notification drawer
- Turn the phone in landscape mode and turn off the toogle
Now, the screen must turn to portrait but it's not. You must turn on the toogle to have a portrait screen again.
It's a small bug, not a big deal though

it's a feature, not a bug ;)
 

pawitp

Inactive Recognized Developer
Oct 30, 2010
3,928
21,276
Bangkok
What is your--
Phone model:i9000
Radio (baseband):JW4
CM version:update-cm-9-20120412-NIGHTLY-galaxysmtd-signed.zip
CM Download url:http://get.cm/?device=galaxysmtd
Gapps version:gapps-ics-20120317-signed.zip

Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes

Are you using--
a task killer: no
a non-stock kernel: no
CMSettings/Performance settings (other than stock): no
other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I was able to reproduce the problem.
without fix all is working fine...
but with fix it only works till u restart the phone. after restart navigation crashes. deinstalling and installing maps helps but again only till u restart ur phone.
also noticed that my statement from above saying it was working on previous nightly was false. right after I found that error on my phone with actual nightly my girlfriend with previous nightly called me to tell me that after a restart because of empty battery she's facing the same error.
on my phone I just havent recognized it before because between flashing fix and and newest nightly I havent restarted the phone.

nobody with similar problem?
latest nightly all stock

Please upload it elsewhere, XDA corrupted the attachment. (Seems to be doing that a lot lately.)
 
  • Like
Reactions: baba420 and barvna

MasterJam882

Senior Member
Jan 26, 2011
632
156
Frankfurt
started log and after that navigation.
app opened I entered destination and loading screen of navigation app started. then nothing happened and message came up:
app hangs wanna wait or quit.
when u choose wait nothing hapens and quit exits the app.
deinstalling and installing maps brings a temporaly solution till next restart.

that's all I can tell u for now since I don't use the fix on my freshly installed rom.
If u can tell me a way to delete fix and don't have to reflash the rom I will try the fix on actual rom again m8

this line in log is not the right one?
Force finishing activity com.google.android.apps.maps/com.google.android.maps.driveabout.app.NavigationActivity
I/ActivityManager( 193): Killing ProcessRecord{416a2520 2015:com.google.android.apps.maps:driveabout/10073}: user's request
I/ActivityManager( 193): Process com.google.android.apps.maps:driveabout (pid 2015) has died.
W/ActivityManager( 193): Scheduling restart of crashed service com.google.android.apps.maps/com.google.android.maps.driveabout.app.NavigationService in 5000ms
I/WindowManag
 
Last edited:

pawitp

Inactive Recognized Developer
Oct 30, 2010
3,928
21,276
Bangkok
started log and after that navigation.
app opened I entered destination and loading screen of navigation app started. then nothing happened and message came up:
app hangs wanna wait or quit.
when u choose wait nothing hapens and quit exits the app.
deinstalling and installing maps brings a temporaly solution till next restart.

that's all I can tell u for now since I don't use the fix on my freshly installed rom.
If u can tell me a way to delete fix and don't have to reflash the rom I will try the fix on actual rom again m8

this line in log is not the right one?
Force finishing activity com.google.android.apps.maps/com.google.android.maps.driveabout.app.NavigationActivity
I/ActivityManager( 193): Killing ProcessRecord{416a2520 2015:com.google.android.apps.maps:driveabout/10073}: user's request
I/ActivityManager( 193): Process com.google.android.apps.maps:driveabout (pid 2015) has died.
W/ActivityManager( 193): Scheduling restart of crashed service com.google.android.apps.maps/com.google.android.maps.driveabout.app.NavigationService in 5000ms
I/WindowManag

It's an ANR (Application Not Responding), not a force close, which is way harder to debug (amplified by the fact that navigation is not supported here), particularly when the application in question is closed-sourced. If you restore the original libsensorservice after it "breaks", does it work again?

Does clearing data of the Maps application help?

Does this bug affect anyone else?
 
Last edited:

zoolander87

Member
Aug 2, 2008
7
0
Hey guys, short question. Since today it doesn't prompt the usb mass storage anymore. It just doesn't do anything at all. It does charge but that's it. I enabled android debugging.

Kinda strange since it worked before.
Any tips ?
 

ego42

Senior Member
Feb 15, 2008
143
65
Hey guys, short question. Since today it doesn't prompt the usb mass storage anymore. It just doesn't do anything at all. It does charge but that's it. I enabled android debugging.

Kinda strange since it worked before.
Any tips ?

If it started all of a sudden it could as well be HW related. I've been having the same problem on and off for about four months now. Check whether your phone connects to Odin. If not it's almost definitely a HW issue.
 

wfm_de

Senior Member
Mar 31, 2011
75
20
Stein
Hey guys, short question. Since today it doesn't prompt the usb mass storage anymore. It just doesn't do anything at all. It does charge but that's it. I enabled android debugging.

Kinda strange since it worked before.
Any tips ?

Remove the battery, wait 5 minutes and boot again. That solved this Problem on my side.

Sent from my GT-I9000 using Tapatalk 2
 
Last edited:

MasterJam882

Senior Member
Jan 26, 2011
632
156
Frankfurt
It's an ANR (Application Not Responding), not a force close, which is way harder to debug (amplified by the fact that navigation is not supported here), particularly when the application in question is closed-sourced. If you restore the original libsensorservice after it "breaks", does it work again?

Does clearing data of the Maps application help?

Does this bug affect anyone else?

K m8 tested now everything:

clearing data of maps, wiping cache, and dalvik cache all brings no solution.
only deinstalling and installing maps brings solution - till next restart.

After removing fix and restoring old libs, maps/navigation is working fine again even when u restart. so for me this means that compass fix is not working properly.

I can reproduce this on my phone, the phone of my girlfriend and a friends one. wondering why no other user is complaining about this error. all ppl who installed navigation should restart their phone start navigation and try to navigate to a location.(just starting navigation app won't show error - u have to start a navigation process)

greetz
 

Top Liked Posts

  • There are no posts matching your filters.
  • 388
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0 (Ice Cream Sandwich), which is designed to increase performance and reliability over stock Android for your device.
    Code:
    #include <std_disclaimer.h>
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).

    Downloads

    Latest nightly: http://get.cm/?device=galaxysmtd
    Google Apps: http://goo-inside.me/gapps/

    Installation

    - First time flashing ICS to your Galaxy S (or coming from another ROM)?
    1. Root your device and install ClockworkMod Recovery.
    2. Reboot into Recovery using 3-button-combo
    3. Do a Nandroid backup!
    4. WIPE (wipe data/factory reset + wipe cache partition)
    5. Install the ROM from internal sdcard using ClockworkMod Recovery
    6. Optionally install the Google Addon
    7. WIPE again or Calendar Sync will not work.
    - Upgrading from CM7?
    1. Do a Nandroid Backup!
    2. WIPE (wipe data/factory reset + wipe cache partition)
    3. Install the ROM from internal sdcard using ClockworkMod Recovery
    4. Optionally install the Google Addon
    - Upgrading from another CM9 (or teamhacksung) Build?
    1. Do a Nandroid Backup!
    2. Install the ROM from internal sdcard using ClockworkMod Recovery
    3. Optionally install the Google Addon
    Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery.

    FAQ (Read here for Change log!)

    The FAQ is available on Teamhacksung's Wiki. Please read before asking any questions and please feel free to edit it.

    http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Frequently_Asked_Questions

    Known Issues

    Please check the list of known issues before reporting bugs.

    http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Known_issues

    Reporting Bugs

    You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.

    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.

    Code:
    What is your--
    Phone model:
    Radio (baseband):
    CM version:
    CM Download url:
    Gapps version:
    
    Did you--
    wipe:
     restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    CMSettings/Performance settings (other than stock):
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
    45
    When I need testers, I will publicly post the build in a new thread. Please do not clog this thread with testing requests.
    33
    Hi guys! What is this? cm-9-20120628-EXPERIMENTAL-galaxysmtd.zip ?? :confused:

    Just some builds I'm making while figuring out why the RC won't build.
    28
    You guys should do a full wipe with newest nightly since it swapped emmc and sdcard

    No, you don't need to.


    Frankly I don't know what is the meaning of swapping cards! Like I said I had nothing in my android_secure folder. I flashed without full wipe and everything working fine to me. I checked version it's new nightly.

    Now I have even inserted my micro sd card and it got detected without any issue. Files in it under the emmc folder.

    Explain me what is this swapped cards and how to check. I'll check and update...

    You'll have the option to use your microSD card as /sdcard in Settings -> Storage -> Menu -> Storage configuration. Android by default (as HTC started it) uses the microSD card as /sdcard and internal memory as /emmc. Samsung came along and uses internal memory as /sdcard and microSD as /sdcard/external_sd. We need to standardize in CyanogenMod, so starting with this nightly, we follow the standard HTC has set, but we also give users the option to swap them if they want. When it comes to Samsung devices, users expect internal SD as /sdcard by default, to the setting is set to swapped as default.

    TL;DR: Nothing changes.


    I did a full no-wipe install and a full wipe install today.

    If no wipe, the sdcard and emmc are mounted reversely by default.
    If full wipe, the sdcard and emmc are just as we have usually.

    If full wipe than switch kernel, the sdcard and emmc are mounted reversely again.

    There must be some misunderstanding...

    The nightlies are designed to be used with the kernels that come with it only. The default preference to swap is stored in the ramdisk in the kernel which is lost if you switch kernel (and so internal SD mounts as /emmc).