[NIGHTLY][ROM][4.4] CyanogenMod 11 for Samsung Galaxy S

Search This thread
By:
Advanced…
F

freakymod2120

Senior Member
Jun 26, 2013
717
185
Hi,

same here with latest nightly 09022014 ...but i have this behaviour since using first CM11-versions, maybe our device is getting to old ...

Issue stays with another kernel (e.g. Sema-Kernel)...i tested it ...

everb00b said:
Open stock dialer app, click dialpad, does it open correctly or you have a half blank white pad?

I clicked back and press dialpad again to get get the numbers and pad

Can anyone reproduce this issue?

FwDdhVG.png
Click to expand...
Click to collapse
 
AndroidBR

AndroidBR

Senior Member
Nov 7, 2010
590
271
Kansas City
everb00b said:
Open stock dialer app, click dialpad, does it open correctly or you have a half blank white pad?

I clicked back and press dialpad again to get the numbers and pad

Can anyone reproduce this issue?
Click to expand...
Click to collapse
I tried to reproduce this but thankfully my phone opens dialer normally without any delays.

The biggest problem when people call me: the phone rings but it can take up to 6 seconds for the phone to wake up, turn on the display for me to see who's calling and answer the phone. Sighs...

The phone feels slow when opening apps, switching between them and even when I select recent apps switcher, it first shows that I have no recent apps, so I back out of it, 2 seconds later if I select the recent apps switcher it displays my recent apps properly...

I'm considering going back to Jelly Bean... Phone felt a lot faster and smoother back with CM10.1...
 
Last edited:
ioannis_m

ioannis_m

Senior Member
Nov 18, 2013
239
44
freakymod2120 said:
Maybe i should try a "clean" install with some of the next nightlies to see that the phenomen will be solved ...the others here had no prob with their dialer app..

Did you a full clean install???
Click to expand...
Click to collapse

Get a full backup from your data and rom and then factory reset /dalvik/cache and format system.
Then go to advanced restore and restore only data and try to reproduce.;)
 
  • Like
Reactions: freakymod2120
G

guijarrelson

Senior Member
Dec 11, 2010
762
115
Spain
I see this build cm-11-20140211-EXPERIMENTAL-ignorecolor-calibration-galaxysmtd.zip in the official download page. Did you see any notice about this test build?
 
F

freakymod2120

Senior Member
Jun 26, 2013
717
185
Hint for the Installation.Ifnos on first page...

Hi @pawitp...

i found this on CM-Homepage, maybe it could be helpful while getting "set_metadata_recursive":

One last final note, if you receive a message in recovery reading along the lines of “set_metadata_recursive: some changes failed” when attempting to flash CM11 builds, it means your recovery is out of date. Flash a newer recovery via your tool of choice and you should be all set.
Click to expand...
Click to collapse


---------- Post added at 08:58 AM ---------- Previous post was at 08:51 AM ----------

It is a test-build from pawitp ...look here:

http://jenkins.cyanogenmod.com/job/android/58662/parameters/

==> here is a hint of gerrit-changing-id 59420

When you fill it in the link http://review.cyanogenmod.org/#/c/59420/ ==> http://review.cyanogenmod.org/#/c/59420/

guijarrelson said:
I see this build cm-11-20140211-EXPERIMENTAL-ignorecolor-calibration-galaxysmtd.zip in the official download page. Did you see any notice about this test build?
Click to expand...
Click to collapse


---------- Post added at 09:15 AM ---------- Previous post was at 08:58 AM ----------

Everything done and nothing changed ...the first click on the dial-pad does not open, with the second click it works ...hmhh i don`t know whats my fault ...:confused::confused:

ioannis_m said:
Get a full backup from your data and rom and then factory reset /dalvik/cache and format system.
Then go to advanced restore and restore only data and try to reproduce.;)
Click to expand...
Click to collapse
 
  • Like
Reactions: guijarrelson
G

guijarrelson

Senior Member
Dec 11, 2010
762
115
Spain
Did anyone use Telegram app? I don't receive notifications about this app. It's installed in the internal mem, and in other phones, it works well with the same config.

Tapatalked from SGS CM 11
 
P

pawitp

Inactive Recognized Developer
Oct 30, 2010
3,928
21,276
Bangkok
guijarrelson said:
I see this build cm-11-20140211-EXPERIMENTAL-ignorecolor-calibration-galaxysmtd.zip in the official download page. Did you see any notice about this test build?
Click to expand...
Click to collapse

It's a build which ignores the color calibration data not written properly in some Galaxy S devices (the original driver does not read them). What do you think about the effects on the color?

freakymod2120 said:
Hi @pawitp...

i found this on CM-Homepage, maybe it could be helpful while getting "set_metadata_recursive":
Click to expand...
Click to collapse

Does not apply to our device where recovery cannot be upgraded separately. The instruction to deal with that error has been in the first post since forever ;)
 
  • Like
Reactions: tetakpatak, Turtuga, pjdpinheiro and 1 other person
G

guijarrelson

Senior Member
Dec 11, 2010
762
115
Spain
pawitp said:
It's a build which ignores the color calibration data not written properly in some Galaxy S devices (the original driver does not read them). What do you think about the effects on the color?
Click to expand...
Click to collapse

In my device, color calibration works fine in the default setting. I can set all colours without problems. I don't have or I don't see any color bug in my screen.

Do you need any test in this experimental build?

Tell me, and I can do a easy test, if you want.
 
Last edited:
F

fran_xda

Senior Member
Dec 28, 2011
168
31
pawitp said:
1) Bug report format
2) Logcat
3) Video of the issue
Click to expand...
Click to collapse

What is your--
Phone model: Galaxy S GT-i9000
Radio (baseband): I9000XXJVU
CM version: 11-20140210-SNAPSHOT-M3
CM Download url: OP link
Gapps version: OP link

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
ART Runtime: No
other modifications: No

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

video of the issue: http://www.youtube.com/watch?v=7lY6UV1Yy7E

Not really apreciated in video, it is worse if you see in real. If bluetooth is on=choppy deploy of status bar/ bluetooth is off= smooth deploy. It only affects to status bar, other transitions and apps seem to be smooth in both cases. This has been happening since the first time I installed CM11 and in every nightly. Changing kernel to Semaphore haven't solved the issue either. Sometimes I get opposite behaviour (BT on=smooth/BT off=choppy), but never smooth in all situations.

*wipe: Although I actually haven't wipe before the installation of M3 I did in previous version (1-26th) and checked the issue rigth after flashing, without any settings or apps modified, the issue was exactly the same to the linked video.

Thanks for your effort.
 

Attachments

  • btoff_bton_logcat.txt
    62.3 KB · Views: 10
  • Like
Reactions: need4steer
P

pawitp

Inactive Recognized Developer
Oct 30, 2010
3,928
21,276
Bangkok
fran_xda said:
What is your--
Phone model: Galaxy S GT-i9000
Radio (baseband): I9000XXJVU
CM version: 11-20140210-SNAPSHOT-M3
CM Download url: OP link
Gapps version: OP link

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
ART Runtime: No
other modifications: No

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

video of the issue: http://www.youtube.com/watch?v=7lY6UV1Yy7E

Not really apreciated in video, it is worse if you see in real. If bluetooth is on=choppy deploy of status bar/ bluetooth is off= smooth deploy. It only affects to status bar, other transitions and apps seem to be smooth in both cases. This has been happening since the first time I installed CM11 and in every nightly. Changing kernel to Semaphore haven't solved the issue either. Sometimes I get opposite behaviour (BT on=smooth/BT off=choppy), but never smooth in all situations.

*wipe: Although I actually haven't wipe before the installation of M3 I did in previous version (1-26th) and checked the issue rigth after flashing, without any settings or apps modified, the issue was exactly the same to the linked video.

Thanks for your effort.
Click to expand...
Click to collapse

While I see the issue, I believe it is very minor but very hard to debug and won't be solving this issue. Of course, any other developer is free to solve it and submit a patch. A work around is to use your finger to drag the bar all the way down to open it and you won't notice the issue.

And starting from the 20140211 nightly, you have the option to force enable graphics acceleration for the status bar at the expense of RAM in Performance Settings.
 
  • Like
Reactions: tetakpatak, hertzschi, didhiy and 2 others
R

rhaaa

Senior Member
Apr 3, 2011
56
15
pawitp said:
It's a build which ignores the color calibration data not written properly in some Galaxy S devices (the original driver does not read them). What do you think about the effects on the color?
Click to expand...
Click to collapse

I have a noticeable yellowish tint with the experimental build. I'm not an expert at color calibration, so that might well be equivallent to my eyes accustomed to a blueish tint with the non experimental build :)

All I can say is that the experimental build is quite warmer than the non experimental build.

I take the opportunity to thank you so much for your continued work on our old beloved device :)

Ty,
--
Rémi
 
You must log in or register to reply here.

Similar threads

P
[NIGHTLY][ROM][4.1.2] CyanogenMod 10 for Samsung Galaxy S
Replies
12K
Views
4M
jupiter5700
jupiter5700
codeworkx
[NIGHTLY][ROM][2.3.7][GWK74] CyanogenMod 7 for Samsung Galaxy S
Replies
23K
Views
4M
DerTeufel1980
DerTeufel1980
P
[NIGHTLY][ROM][4.0.4][IMM76I] CyanogenMod 9 for Samsung Galaxy S
Replies
6K
Views
2M
S
shysoul64
P
  • Locked
[ROM][ICS][IML74K] teamhacksung's CM9 ALPHA for Galaxy S (BUILD 17) BUG REPORTS ONLY
Replies
15K
Views
6M
P
pawitp
P
[NIGHTLY][ROM][4.2.2] CyanogenMod 10.1 for Samsung Galaxy S
Replies
6K
Views
2M
christo_tj
christo_tj

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 393
    P
    pawitp
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), 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 build: http://download.cyanogenmod.org/?device=galaxysmtd
    Google Apps: http://wiki.cyanogenmod.org/w/Gapps

    Installation

    - First time flashing CM11 to your Galaxy S (or coming from another ROM)?
    (Note: a more detailed instruction for first-time install is available on CM Wiki: http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd)
    1. If you're on a ROM prior to 2.3, upgrade to 2.3 is recommended.
    2. Root your device and install ClockworkMod Recovery (e.g. Semaphore_2.7.4.tar from http://www.semaphore.gr/downloads).
    3. Reboot into Recovery using 3-button-combo
    4. Do a Nandroid backup!
    5. WIPE (wipe data/factory reset + wipe cache partition)
    6. Install the ROM from internal sdcard using ClockworkMod Recovery
    7. Optionally install the Google Addon
    - Upgrading from CM7/CM9?
    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 CM10/10.1?
    1. Do a Nandroid Backup!
    2. Install the ROM from internal sdcard using ClockworkMod Recovery
    3. You will finally see a "set_metadata_recursive" status 7 error. That is normal.
    4. Reboot back into recovery (the reboot is required)
    5. Install the ROM again from internal sdcard using ClockworkMod Recovery
    6. Optionally restore /data from Nandroid Backup (the update will wipe your /data)
    7. Optionally install the Google Addon
    - Upgrading from CM10.2?
    1. Do a Nandroid Backup!
    2. Install the ROM from internal sdcard using ClockworkMod Recovery
    3. Optionally install the Google Addon
    - Upgrading from another build of CM11?
    1. Do a Nandroid Backup!
    2. Install the ROM from internal sdcard using ClockworkMod Recovery
    Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
    Note: The partition layout of CM11 is the same as CM10.2.

    Known Issues
    Please do not report bugs if it is already listen in the list of known issues
    • Some CyanogenMod features a missing - please do not file bug reports for those.
    • Cannot set value via custom brightness "Edit" menu
    • No account selected for Backup (gapps problem?)

    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.

    REPORT BUGS IN THIS THREAD ONLY

    • 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)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    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. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.

    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):
ART Runtime:
other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    FAQ
    Why is there no transparent status bar/lockscreen widget/"OK Google"?
    Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.

    Does this ROM support FM radio?
    I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.

    TL;DR: No built-in FM radio except if someone else does it and submits a patch.

    Why aren't configurations with more than 368 MB used?
    Kernels with more than 368 MB have to sacrifice high-bitrate HD playback ability. The current memory configuration has been designed for maximum compatibility.

    Wi-Fi AP does not work after restoring /data with CWM
    CWM does not handle SELinux very well yet. Run this in a root shell to clear all wifi data and reboot.

    Code: 
    rm -rf /data/misc/wifi

    Changelog
    A rough changelog is available here:
    http://changelog.bbqdroid.org/#/galaxysmtd/next or http://www.cmxlog.com/11/galaxysmtd/

    For previous unofficial releases, see here

    The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
    View
    100
    P
    pawitp
    Need more RAM?

    Need more RAM?

    Using CMA, memory usually reserved for hardware (camera, video encoding/decoding, jpeg encoding) can be freed for use by applications when they are not in-use. All features, including 720p recording, high-rate video decoding, etc. will still work as before.

    This is a WIP. No ETA. There are still a lot of problems with it and it might not be released at all if I don't have time to fix all the issues. Please don't ask to test either, if I need testers, I'd post it in this thread.
    View
    65
    P
    pawitp
    20131203
    • Added TV Out in Settings -> Display -> Advanced Settings
    • Prevent back button from being pressed in incoming call screen
    • Fixed Browser FC in Advanced -> Website settings
    • Fixed Quick Access Ribbon gone when switching from Quick Settings
    • Fixed 2G/3G Quick Settings toggle
    • Fixed stuttering FLAC music playback
    View
    39
    P
    pawitp
    About RAM mode

    Due to an oversight, this build wasn't shipped with low RAM mode enabled. If anyone wants to try, you can add "ro.config.low_ram=true" to your /system/build.prop.

    This will disable several features such as translucent status bar, lock screen widgets.

    Future builds will ship with this option enabled. (This is actually mandated by the Android CTS. Those that prefer the effects over low memory usage must manually remove the config from build.prop. Before anyone asks, it won't be configurable from Settings.)
    View
    35
    P
    pawitp
    20131118 uploaded.

    This should provide better performance if you use zRAM (Settings -> Performance -> Memory Management). Please try the various settings and report back how it affects your experience.
    View

New posts