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

Search This thread
By:
Advanced…
koala990

koala990

Senior Member
Feb 4, 2011
234
277
26
Patna
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​
 
Last edited:
  • Like
Reactions: hi_mam, Koahar84, noob&noob and 144 others
Deopolos14

Deopolos14

Senior Member
Jun 21, 2013
123
14
Ankara
koala990 said:
ROM is in initial stage and an Experimental build has been released on jenkins, need testers to test this.. http://jenkins.androidarmv6.org/view/All/job/android-experimental/908/
Click to expand...
Click to collapse

Are you kidding me!! OMG thanks for this news

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------

I can help to test but is this build needs kernel ?

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi
 
koala990

koala990

Senior Member
Feb 4, 2011
234
277
26
Patna
Deopolos14 said:
Are you kidding me!! OMG thanks for this news

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------

I can help to test but is this build needs kernel ?

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse

As we can see, it has a kernel inside.. But its not installing.. Obviously it wont, its initial build, all the other devices of androidarmv6 branch had this problem including my galaxy mini, we'll have to wait for a SELinux enabled recovery for totoro, better waiting, btw devs can work for the revovery
 
  • Like
Reactions: dadziokPL and Deopolos14
Deopolos14

Deopolos14

Senior Member
Jun 21, 2013
123
14
Ankara
koala990 said:
As we can see, it has a kernel inside.. But its not installing.. Obviously it wont, its initial build, all the other devices of androidarmv6 branch had this problem including my galaxy mini, we'll have to wait for a SELinux enabled recovery for totoro, better waiting, btw devs can work for the revovery
Click to expand...
Click to collapse

Okey I`m understand

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi
 
P

psyke83

Inactive Recognized Developer
Mar 29, 2011
1,267
3,959
Hi,

Just to make it clear, the developers (i.e. me) didn't ask for the builds to be tested. I'm running the Jenkins builds to help troubleshoot major issues and finish the initial stage of development more quickly. The builds are not yet bootable, and even have the possibility to brick your device at this stage. Please don't try to flash any builds yet.
 
  • Like
Reactions: PuYaU, Hari1595, amitahuja and 9 others
Deopolos14

Deopolos14

Senior Member
Jun 21, 2013
123
14
Ankara
psyke83 said:
Hi,

Just to make it clear, the developers (i.e. me) didn't ask for the builds to be tested. I'm running the Jenkins builds to help troubleshoot major issues and finish the initial stage of development more quickly. The builds are not yet bootable, and even have the possibility to brick your device at this stage. Please don't try to flash any builds yet.
Click to expand...
Click to collapse

Thanks but can we do SELinux supported recovery like TWRP or other things

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi
 
  • Like
Reactions: Hari1595
koala990

koala990

Senior Member
Feb 4, 2011
234
277
26
Patna
psyke83 said:
Hi,

Just to make it clear, the developers (i.e. me) didn't ask for the builds to be tested. I'm running the Jenkins builds to help troubleshoot major issues and finish the initial stage of development more quickly. The builds are not yet bootable, and even have the possibility to brick your device at this stage. Please don't try to flash any builds yet.
Click to expand...
Click to collapse

Thanks for your kind response psyke83, we'll be following your intels.. This thread was created to inform users about your fabulous work.

Thank you
 
koala990

koala990

Senior Member
Feb 4, 2011
234
277
26
Patna
Deopolos14 said:
Man CM11 works little buggy on galaxy 551 i think on our device CM11 run near to stable
Click to expand...
Click to collapse

See, what I believe is.. Galaxy Y is a good device, it has 832 MHz CPU and VideoCore IV GPU and all.. But the problem is, despite of having these capabilities, it lags even n the stock ROM. It was a new device in the last ARMv6 devices of Samsung, it should have been better than others like Galaxy Mini and Galaxy 5, in some matters it is better like in memory and other.. But still, we did'nt had any Stable CyanogenMod for this device, nor 7.2 nor 9.1 or other.. But WHY?? Its a good device then WHY?..

The answer is.. Broadcom.. Yes.. You see, Broadcom is not a Developers supporting organization like Qualcomm which support developers in all the way it can.. If you notice, (Sorry, if you know all these, this might be helpful for all the other readers) all the other ARMv6 devices running CM11 including S5570, S5830, LG P500 etc. are Qualcomm powered. Qualcomm had released the drivers for those devices and have helped the developers in all the way. This case is not same with Broadcom, after a lot of petitioning, it released some partially working drivers for Galaxy Y and other BCM21553 (Its the hardware of Galaxy Y, Galaxy Ace S5830i and other) on which developers worked hard and made us taste CM7.2 and a little bit of CM9.1. This is the reason of slow development of our device. Personally, I hate Broadcom and love Qualcomm..;) If some of you have probably noticed, most of the Qualcomm ARMv6 devices run smoother, faster and have a very high responsive touchscreen as compared to our Galaxy Y and other BCM21553 devices (Worst touchscreen responsiveness). But now things have changed, even I was surprised to see that totoro was added to AndroidARMv6 branch. This means we can think of a better future for this device and when psyke83 is developing it, we dont have to worry, just help him in all the way we can. And believe me, this is a good device!
 
  • Like
Reactions: mariocanales, thedeadfish59, qkpw and 12 others
Deopolos14

Deopolos14

Senior Member
Jun 21, 2013
123
14
Ankara
koala990 said:
See, what I believe is.. Galaxy Y is a good device, it has 832 MHz CPU and VideoCore IV GPU and all.. But the problem is, despite of having these capabilities, it lags even n the stock ROM. It was a new device in the last ARMv6 devices of Samsung, it should have been better than others like Galaxy Mini and Galaxy 5, in some matters it is better like in memory and other.. But still, we did'nt had any Stable CyanogenMod for this device, nor 7.2 nor 9.1 or other.. But WHY?? Its a good device then WHY?..

The answer is.. Broadcom.. Yes.. You see, Broadcom is not a Developers supporting organization like Qualcomm which support developers in all the way it can.. If you notice, (Sorry, if you know all these, this might be helpful for all the other readers) all the other ARMv6 devices running CM11 including S5570, S5830, LG P500 etc. are Qualcomm powered. Qualcomm had released the drivers for those devices and have helped the developers in all the way. This case is not same with Broadcom, after a lot of petitioning, it released some partially working drivers for Galaxy Y and other BCM21553 (Its the hardware of Galaxy Y, Galaxy Ace S5830i and other) on which developers worked hard and made us taste CM7.2 and a little bit of CM9.1. This is the reason of slow development of our device. Personally, I hate Broadcom and love Qualcomm..;) If some of you have probably noticed, most of the Qualcomm ARMv6 devices run smoother, faster and have a very high responsive touchscreen as compared to our Galaxy Y and other BCM21553 devices (Worst touchscreen responsiveness). But now things have changed, even I was surprised to see that totoro was added to AndroidARMv6 branch. This means we can think of a better future for this device and when psyke83 is developing it, we dont have to worry, just help him in all the way we can. And believe me, this is a good device!
Click to expand...
Click to collapse

You are true if I`m say stupid things I`m sorry

e-tab4 cihazımdan Tapatalk kullanılarak gönderildi
 
NightRaven49

NightRaven49

Senior Member
Sep 13, 2013
777
306
most likely at home
Xiaomi Redmi 1S
Xiaomi Mi 5s
GSculerlor said:
Will androidarmv6 make lib for BCM21553 ?
Click to expand...
Click to collapse

No, I guess they have to adapt the current libraries to work on our devices. As you already know, Broadcom only released drivers for the C/GPU and we had to adapt these libraries for CM9.1. As for the audio and other stuff they were not from Broadcom but rather ALSA and Samsung, and needed to be adapted from other sources, like for example the Nexus S, if I remember correctly.

I do have a question though. Shouldn't we work on CM10 as well? Or is it pretty much based on CM9 so once we get CM9 stable enough we can also get CM10?

btw you can't reverse engineer libs
 
Last edited:
  • Like
Reactions: GSculerlor
You must log in or register to reply here.

Similar threads

R
[GUIDE] (02/Aug/12) [ROOT]/[UNROOT]/[CWM]/[UNLOCK] Samsung GALAXY Y S5360
Replies
228
Views
353K
S
spike1970
The-Captain
  • Locked
Off-Topic Thread (Strike 3 You're Out)
Replies
12K
Views
373K
Woody
Woody
T
[GUIDE][GB] (Android 5.0) Android L Theme
Replies
138
Views
80K
Nobbienoob79
Nobbienoob79
nikufellow
[REF]Terminal Emulator Commands ! (Android shell command reference)
Replies
45
Views
283K
TheRealModder
TheRealModder
krishna_nirvana
Root and other Apps for Samsung Galaxy Y S5360
Replies
111
Views
298K
R
reshabhraj

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 147
    koala990
    koala990
    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​
    View
    28
    P
    psyke83
    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.
    View
    26
    P
    psyke83
    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.
    View
    18
    P
    psyke83
    yusrilramadhan said:
    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
    Click to expand...
    Click to collapse

    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.
    View
    17
    P
    psyke83
    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.
    View

New posts