Discussion Thread for CyanogenMod 11/12 (Android 4.4.x KitKat & 5.0.x Lollipop)

Search This thread

TheFixItMan

Senior Member
  • Jul 8, 2012
    7,774
    3,978
    London
    @psyke83


    Iv tested the build with gerrit changes 7204 and 7209 and here are my results

    I have attached a logcat of making a call and trying to activate the loudspeaker


    Data
    Works - no need to edit build prop for me (I tried it with the old build.prop from the 4th july nightly and ril fails so ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock breaks the ril)


    Headphones
    Works


    Front speaker during calls
    Works - can hear the other persons voice


    Mic during calls
    Half works - You really have to speak loud and directly into the mic to hear your voice on the other phone - mic sensitivity needs working on


    Hanging up during call
    Works


    Accepting incoming call
    Works


    Loud speaker
    Doesnt work - as you have said switching to loud speaker during call doesnt work


    edit logcat removed as problem solved
     
    Last edited:

    psyke83

    Inactive Recognized Developer
    Mar 29, 2011
    1,267
    3,959
    @psyke83


    Iv tested the build with gerrit changes 7204 and 7209 and here are my results

    I have attached a logcat of making a call and trying to activate the loudspeaker


    Data
    Works - no need to edit build prop for me (I tried it with the old build.prop from the 4th july nightly and ril fails so ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock breaks the ril)


    Headphones
    Works


    Front speaker during calls
    Works - can hear the other persons voice


    Mic during calls
    Half works - You really have to speak loud and directly into the mic to hear your voice on the other phone - mic sensitivity needs working on


    Hanging up during call
    Works


    Accepting incoming call
    Works


    Loud speaker
    Doesnt work - as you have said switching to loud speaker during call doesnt work

    Thanks for testing. I may have found a better way to implement routing and volume control, but it will take some time to analyse and adapt the code.
     

    kundancool

    Senior Member
    Jul 1, 2010
    331
    413
    @psyke83

    Just tested this build

    Data - works without problem for me
    Mic - seems good no issue while in call

    BUG
    SIM PIN - this build doesn't unlock SIM PIN please check logcat
    it stays on
    Unlocking SIM card...
     

    Attachments

    • boot-simlock.txt.zip
      30.8 KB · Views: 8

    kaushikb.1996

    Senior Member
    Mar 28, 2013
    606
    213
    Hyderabad
    I am on the test build right now and tested

    Data - works without an issue

    WiFi - works

    Calls -

    Incoming are now able to be received and can hang up , mic works perfectly for me and even the earpiece , outgoing also working

    Headset - working
    @psyke : salute to your awesome work !!

    Sent from my GT-S5360 using XDA Free mobile app
     

    kaushikb.1996

    Senior Member
    Mar 28, 2013
    606
    213
    Hyderabad
    Psyke has managed to fix routing and volume control while in-call. started OTA build so


    New Ota build started http://jenkins.androidarmv6.org/job/cm-ota/390/


    Bugs fixed in this ota

    1) Incoming call
    2) headset,earpiece,volume controls in calls

    The only bugs left

    1) Wifi and Usb tethering
    2) Camera
    3) hardware encoders and decoders (that means cant watch hd videos properly )



    Sent from my GT-S5360 Using XDA mobile app
     
    Last edited:

    psyke83

    Inactive Recognized Developer
    Mar 29, 2011
    1,267
    3,959
    Yes, the OTA builds are in progress that will include fixed routing. I actually cancelled the builds at the last minute, thinking that I broke the microphone. I was wrong... I just didn't realize that the headset mic was working correctly ;)

    See: http://forum.xda-developers.com/showpost.php?p=53962317&postcount=76

    @psyke83

    Just tested this build

    Data - works without problem for me
    Mic - seems good no issue while in call

    BUG
    SIM PIN - this build doesn't unlock SIM PIN please check logcat
    it stays on

    For radio errors, it's better to send me a radio log. See the link above.
     

    KnightlyNinja

    Senior Member
    Sep 11, 2012
    719
    441
    Biratnagar
    Victory

    Finally the devs have done an almost impossible job. Almost all major bugs are now fixed. Now i think Next job need to be done is to make rom stable and smoother(not mean to say fix camera and decoders) means to fix the force closes that happen in almost apps like gallery,newly installed apps and kill the laggy lag. And then CONCENTRATE on remaining camera bugs and all.

    HATS OFF
     

    TheFixItMan

    Senior Member
  • Jul 8, 2012
    7,774
    3,978
    London
    @psyke83

    Just tested this build

    Data - works without problem for me
    Mic - seems good no issue while in call

    BUG
    SIM PIN - this build doesn't unlock SIM PIN please check logcat
    it stays on

    Yes, the OTA builds are in progress that will include fixed routing. I actually cancelled the builds at the last minute, thinking that I broke the microphone. I was wrong... I just didn't realize that the headset mic was working correctly ;)

    See: http://forum.xda-developers.com/showpost.php?p=53962317&postcount=76



    For radio errors, it's better to send me a radio log. See the link above.


    The sim unlock screen doesnt appear because

    ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock

    was removed from the build prop -

    however if you include that in the build prop now it brakes the ril

    I dont know what would happen if you just put
    ro.telephony.ril.v3=facilitylock
     
    Last edited:

    Mixotico

    Member
    Jun 27, 2013
    48
    11
    Maybe it's not an important bug, but when you're listening to music and you turn wifi on, the music automatically stops.
    It's the first time that I install this rom on my phone, so if it was mentioned before, just ignore my message.
     
    Last edited:

    vivimilan

    Senior Member
    Aug 21, 2013
    144
    14
    35
    Tirane
    I have one problem. i have wireles but i can't connect because i have it with pasword and pasword is with 5 characteres but this worm need for connect to wifi with 8 characteres . The problem is i can't change the pasword of the wireles

    Ps: Sorry for my english.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 147
      Samsung-Galaxy-Note-8-0-Users-Get-a-Taste-of-Android-4-4-Thanks-to-CyanogenMod-11-414700-2.jpg

      For Samsung Galaxy Y GT-S5360 (totoro)

      Code:
      * Your warranty is now void.
       * Me / CM / AndroidARMv6 Team are 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 any of us for messing up your device, we will laugh at you.
       * Collectively, and at the same time.

      Hello everybody.. Our lovely Galaxy Y S5360 (totoro) has been added to official AndroidARMv6 branch and is now running CyanogenMod 11, Android 4.4.4 KitKat. Samsung stopped any further updates for this device and now the devs will develop it further.
      The ROM is stable enough for daily use, this thread is created to have discussions related to CM11 totoro.
      Thanks to all the devs for developing this, lets build together for this device!

      About CyanogenMod:

      CyanogenMod is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices. Get more information on CyanogenMod Wiki.

      Brief Information:
      The ROM is stable enough for daily use. Most of the bugs have been sorted out, but some are yet to be fixed. Me and other devs are regularly working on it so don't ask for ETAs and don't ever think of writing to Fix this or Fix that. This thread is only for information and discussion about the ROM. So, it depends on you whether you choose to flash the builds or not. The ROM is now OTA supported and Nightlies are being released.

      Whats working, Whats not?:
      If you came here, its your prime duty to go through all the posts and check out whats working whats not OR you can check the DEV thread here.

      Links:
      Recovery: ClockWorkMod Recovery v6.0.5.3
      ROM: Latest OTA supported totoro builds.
      Gerrit Code Review: AndroidARMv6 code review.

      Installing Instructions: (Its highly recommended to strictly follow the below given instructions to avoid any problems during installation of ROM or Recovery)
      • Download the Recovery from above provided link. Either .zip Or .tar.md5. Your choice.
      • Download the Full OTA build from above provided link.
      • Boot into Stock Recovery and flash the recovery you downloaded (.zip). Or if you have problems with .zip package, you can manually flash the .tar.md5 package via Odin.
      • After flash, reboot into New Recovery.
      • Perform a Full data and cache wipe.
      • Now flash the OTA ROM package, then Reboot.

      Version Information:
      OS Version: Android 4.4.4 KitKat
      Based On: CyanogenMod 11
      ROM Status: NIGHTLY

      If you liked my work or I have helped you in any way, please press the 'Thanks' button below. :D:D:D
      28
      I see a lot of flaming going on here, so I feel that some clarification is needed.

      First of all, this talk of "not having permission" is nonsense. Any code that I have submitted inherits the license of the parent project, and I have not changed any licenses for projects that I forked. I am not withholding anything, and I am not trying to prevent anyone from having access to the code. The androidarmv6 project is a collaborative project in which anyone can participate and contribute.

      What I actually requested - as a courtesy - was for users not to test the Jenkins builds yet.

      The Jenkins build server is owned by my friend @erikcas (one of the original androidarmv6 founders), and he graciously allows its use by myself and the other core members of the team. The server is used to provide stable builds for supported devices to the public, but it is also used by developers to test code changes (i.e. the android-experimental or submission-test builds). Normally, these builds are usually focused on testing only one specific change. The build can be completely broken apart from the one change that needs to be tested... and for a developer, that's no problem. We know what to expect from a particular build - what should work and what shouldn't. However, when random users start flashing these builds, without any knowledge of the functional status the build has, things can be chaotic.

      It takes >3 hours to run a build on my laptop (and my machine becomes practically unusable during that time). Jenkins can do the same job in forty minutes... and this greatly helps me with development. But what I don't like is that it exposes all of those builds (that are clearly not ready for wider usage) to the public.

      If I didn't explain it well enough, here are some more reasons not to flash builds from Jenkins:
      • Because you'll piss me off. This is my hobby... something done in my free time for a bit of fun (and practice with programming). When you start ignoring my instructions/requests, and start spamming my PMs or development topics with silly questions, it just makes me want to stop working on the project altogether. Have some respect for your developers, please.
      • You're wasting Jenkin's server bandwidth. The test builds are only supposed to be downloaded once by the developer to test a specific change.
      • Builds are extremely unstable and not ready to be used. Even if you get it working and it doesn't damage your phone, you will be severely disappointed in performance and features.
      • Basic features are not working, such as telephony and audio. Someone once tried to blame me for not being able to call an ambulance in an emergency situation (they had flashed one of my alpha builds for another device in which I specifically warned that the microphone was broken).

      Having said all that, I'm not going to lose sleep if people ignore my requests and test the builds - as long as such talk is kept here in the general thread.
      26
      A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.

      Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.

      There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
      18
      You better buy Galaxy Ace 3. The price is dropped. My sister bought the phone for $150.

      Sent from my GT-S5830i using Tapatalk 2

      I would agree with this sentiment in general. Nobody should willingly buy an ARMv6 device, especially considering that you can get newer budget devices with ARMv7 chipsets for reasonable prices. $150 still seems too expensive to me, though. Perhaps it's harder to get bargains on prepay phones in the USA compared to Europe. As an example, Vodafone were selling their Vodafone Smart III for €40 recently (and I missed that offer, unfortunately).

      I didn't even buy the Galaxy Y that I use for development - it was left abandoned in a field! My sister happened to stumble upon it, and later gave it to me. When I managed to get it working (as it originally refused to turn on or charge, possibly due to water damage) I decided to develop CM11 on it just for a bit of fun.
      17
      News: tonight's OTA now includes the new wifi driver (with further stability improvements over the version that was in the experimental build). If you're still testing the experimental build, I recommend that you switch back to the regular OTA build.

      Please keep an eye on wireless functionality and let me know if there are any problems with the new driver. Thanks.