Discussion Thread for CyanogenMod 11/12 (Android 4.4.x KitKat & 5.0.x Lollipop)
- Thread starter koala990
- Start date
I am happy that this phone after years will get proper support and we can run KK on our phone, that's amazing, hope devs fix CM9 audio (idc about camera) and make SGY CM11 stable (*_* )
This thread for CM 11 for CM 9 you can go to http://xdaforums.com/showthread.php?t=2677037 or go to Bieltv's blog
75% stable, in terms of performance and stablity its ok, just Headphones,mic and camera not working
wooow excited to see CM11 for SGY ..am waiting for the bootable rom .... i think they will make it soon ....
-CALIBAN666-
Senior Member
-CALIBAN666-
Senior Member
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
147
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.28I 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.26A 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
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.17News: 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.
