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

Search This thread
By:
Advanced…
NightRaven49

NightRaven49

Senior Member
Sep 13, 2013
777
306
most likely at home
Xiaomi Redmi 1S
Xiaomi Mi 5s
koala990 said:
Well.. The Good News is.. CyanogenMod 12 will also be coming to our device. People who suspect, I wanna ask them "WHY"?? Why do they suspect? Remember the days when even thinking about ICS was a dream, then KitKat came. It was like Impossible for our device. But things changed, psyke83 made everything possible and other ARMv6 Devs too. Lollipop would surely boot on our device as the source code is even lighter than KitKat and also has the support for Dalvik Runtime. All it needs is optimizaton for the ARMv6 chipset. Regarding the size, it won't the problem as this can also be optimized. Just as the same we did KitKat. I'm regularly checking this thread and the gerrit and I can say its the same as we had with KitKat. I know all the CM12 stuff currently is a WIP. All this thing is a matter of time, it might require hell lot of time, or maybe just little. Have patience and let Sir psyke83 do his fabulous work. Still, I can't guarantee it but I strongly feel it ;). Lets hope for the best, Our device would never die..:D:D:D
Click to expand...
Click to collapse

LOL you posted this 8 months ago:
http://xdaforums.com/showthread.php?p=53898134
Then again attitudes may have changed.

That is why I don't believe L will run on BCM21553.
 
  • Like
Reactions: Guddu
noturbru

noturbru

Senior Member
Jul 14, 2013
392
109
luqman98

luqman98

Senior Member
Nov 23, 2012
3,894
594
Pasir Mas, Kelantan
Xiaomi Redmi 4X
Asus ZenFone Max Pro M1
luqman98

luqman98

Senior Member
Nov 23, 2012
3,894
594
Pasir Mas, Kelantan
Xiaomi Redmi 4X
Asus ZenFone Max Pro M1
P

psyke83

Inactive Recognized Developer
Mar 29, 2011
1,267
3,959
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.
 
Last edited:
  • Like
Reactions: leoetlino, thedeadfish59, Aryan000 and 23 others
mohamedrashad

mohamedrashad

Senior Member
Nov 15, 2012
1,087
618
26
ismailia
psyke83 said:
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.
Click to expand...
Click to collapse

off-topic question, why can't we get 3.0 kernel for our device? can you explain why please.. i want to know :D
 
  • Like
Reactions: thedeadfish59
P

psyke83

Inactive Recognized Developer
Mar 29, 2011
1,267
3,959
mohamedrashad said:
off-topic question, why can't we get 3.0 kernel for our device? can you explain why please.. i want to know :D
Click to expand...
Click to collapse

It's too much work to port a newer kernel. Making the 3.0 kernel port for galaxy5 (or any msm7x27 devices) was easier due to the availability Code Aurora Forum's kernel source which is targeted for Qualcomm devices. Despite msm7x27 being deprecated in that branch, a lot of code was still present to make the porting job easier.

Samsung's 2.6.35 Broadcom kernel source is too much of a mess, it has too much diverged code (e.g. an almost completely rewritten USB stack), and I honestly have no interest in trying to update the kernel on my own.
 
  • Like
Reactions: mirhl, thedeadfish59, Ansh2000 and 5 others
Aptony

Aptony

Senior Member
Dec 7, 2013
83
18
Hello sir @psyke83 ,
In the latest nightly, cooperve users got two major bugs:
-Camera force close and
-When we try to call someone InCallUI start to force close all the time until the call end or enable airplane mode.

i will attach logcat from these issues.
Thanks for your work and attention.
 

Attachments

  • Camera2.txt
    18 KB · Views: 41
  • IncallUI.txt
    211.7 KB · Views: 28
P

psyke83

Inactive Recognized Developer
Mar 29, 2011
1,267
3,959
Aptony said:
Hello sir @psyke83 ,
In the latest nightly, cooperve users got two major bugs:
-Camera force close and
-When we try to call someone InCallUI start to force close all the time until the call end or enable airplane mode.

i will attach logcat from these issues.
Thanks for your work and attention.
Click to expand...
Click to collapse

Both problems are caused by the camera failing to initialize. I recently moved the custom CameraParameters out of frameworks/av and into the device repo (to make frameworks/av less cluttered), but I missed a parameter needed for cooperve.

The fix has been committed and will be available in the next build. I can't trigger a new OTA build for cooperve until tomorrow.
 
  • Like
Reactions: Ansh2000, prabhatrai, momojuro and 3 others
P

psyke83

Inactive Recognized Developer
Mar 29, 2011
1,267
3,959
Aptony said:
Hello sir @psyke83 ,
In the latest nightly, cooperve users got two major bugs:
-Camera force close and
-When we try to call someone InCallUI start to force close all the time until the call end or enable airplane mode.

i will attach logcat from these issues.
Thanks for your work and attention.
Click to expand...
Click to collapse

Today's cooperve OTA build should have fixed these issues. Please let me know if everything's ok (and if not, another camera log would be helpful).

To the people asking about cm12 - don't be lazy or rude and read what I've written on the subject. Look at my post one page back: http://xdaforums.com/showpost.php?p=57583132&postcount=3947
 
  • Like
Reactions: Ansh2000, prabhatrai, Souroking and 4 others
Aptony

Aptony

Senior Member
Dec 7, 2013
83
18
psyke83 said:
Today's cooperve OTA build should have fixed these issues. Please let me know if everything's ok (and if not, another camera log would be helpful).

To the people asking about cm12 - don't be lazy or rude and read what I've written on the subject. Look at my post one page back: http://xdaforums.com/showpost.php?p=57583132&postcount=3947
Click to expand...
Click to collapse

Sir,
I just tested 21/12 OTA : Camera and calls work good like before c:
Thank you, regards.

Sent from my GT-S5830i using XDA Free mobile app
 
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