This ROM is in early stage and some functions aren't working just yet. Currently this is unstable, buggy and not recommended for daily use.
This is for i9105P (with NFC support), but should work fine on a non-NFC version of S2 Plus(?).
Flashing this ROM is in your own responsibility. It is recommended to make a backup before flashing this! (Backup EFS).
(wipe, data (not internal storage), system, cache, art/dalvik cache. In TWRP Recovery > "Wipe" > "Advanced Wipe")
Download 12 Jan 2017 (latest build)
What's working:
Audio playback (buggy)
Bluetooth
Camera
GPS
Microphone
NFC
RIL
USB OTG
WiFi
Sensors
What's not working:
*
SELinux is set to permissive until all the important functions gets fixed.
Audio won't work if SELinux is set to enforcing, because libSamsung_Resampler.so have text relocations.
Bugs:
Audio playback doesn't work correctly.(?)
Screenshots and app thumbnails are blank (Will be fixed, when there's proper fix for it).
OpenGLRenderer: Switches and input box lines are not visible...
Browser (webview): Video playback doesn't work properly. Use Chrome browser for properly working video playback.
To flash this ROM, use Mm/N compatible recovery.
Sources:
ROM side sources:
https://github.com/Dreams-Nougat
Vendor:
https://github.com/manumanfred/proprietary_vendor_samsung_galaxys2plus-common
device: https://github.com/manumanfred/android_device_samsung_i9105p
https://github.com/manumanfred/android_device_samsung_galaxys2plus-common
Kernel:
Currently using GHsR's [URL="https:...xys2plus-common"]kernel (branch: android-7.1)
Thanks to:
@GHsR - for keeping this device alive, making Android stable and for his sources, etc.
pawitp - for his patches,
@Ziyan - for helping me every time I needed help with something
Google
CyanogenMod
Carlos_Manuel said:
This is for i9105P (with NFC support), but should work fine on a non-NFC version of S2 Plus(?). This ROM is buggy, unfinished and unstable, so this is not for daily use.
Flashing this ROM is in your own responsibility, make a backup before flashing this! (Backup EFS).
It's recommended to wipe, data (not internal storage), system, cache, art/dalvik cache. In TWRP Recovery > "Wipe" > "Advanced Wipe"
Download AOSP Nougat (2016-09-09)
What's working:
Audio playback and recording
(Works only in a permissive SELinux mode, recording may not work correctly)
lib_Samsung_Resampler.so has text relocations and I can't find any compatible replacement library for it...
Bluetooth
Camera (taking pictures works fine, but video recording not)
(may not work correctly, if switching to video recording and re-opening camera2.
NFC
RIL (calling, mobile data and SMS)
USB OTG
All the sensors should work
What's not working:
WiFi
GPS
Video recording?
This is using webview built by pawitp (v.47), sine my built webview v54 doesn't work for some reason.
SELinux is set to permissive until all the important functions gets fixed.
Some of the patches aren't applied just yet, that's why screenshots will be blank and rotation animation is abnormal.
The reason you see ds_i9105p in the build number is, because this is based on my Dreams ROM project, but currently has no other changes than AOSP and device related fixes/workarounds/...
glgps crashes because of my hex editing, that can be fixed later by modifying glgps-compat(?)
To flash this ROM, use Mm compatible recovery.
I use TWRP 3.0.2.0
Sources:
ROM side sources:
https://github.com/Dreams-N
Chromium webview (v47):
https://github.com/manumanfred/android_external_chromium-webview
Vendor:
https://github.com/manumanfred/proprietary_vendor_samsung_galaxys2plus-common
device i9105P: https://github.com/manumanfred/android_device_samsung_i9105p
device SII Plus common:
https://github.com/manumanfred/android_device_samsung_galaxys2plus-common
Kernel (Based on Ghsr 3.0.101 cm kernel):
https://github.com/manumanfred/android_kernel_samsung_galaxys2plus-common
Thanks to:
@GHsR - for keeping this device alive, making Android stable, for his sources, etc.
pawitp - for his patches,
@Ziyan - for helping me every time I needed help with something
Google
CyanogenMod
Click to expand...
Click to collapse
Offtopic:
I've got Wi-Fi working on AOSP 7.0 (but for GT-S7582)
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
Offtopic:
I've got Wi-Fi working on AOSP 7.0 (but for GT-S7582)
Sent from my GT-S7580 using Tapatalk
Click to expand...
Click to collapse
no_name also have WiFi working on trend plus. I'm not 100% sure what is breaking WiFi on this device.
Carlos_Manuel said:
no_name also have WiFi working on trend plus. I'm not 100% sure what is breaking WiFi on this device.
Click to expand...
Click to collapse
Does video playback work on this ROM?
Sent from my GT-S7580 using Tapatalk
Thank you so much for this fast made ROM. Going to install now:good:
Does recent apps still look a bit weird?
Btw for anyone having problems flashing Gapps you can only flash Pico OpenGapps,all of the other ones will give a bootloop
DodoGTA said:
Does video playback work on this ROM?
Sent from my GT-S7580 using Tapatalk
Click to expand...
Click to collapse
I've only tested playing the screen record videos. I have to make more testings on Monday.
Dinkec27 said:
Does recent apps still look a bit weird?
Btw for anyone having problems flashing Gapps you can only flash Pico OpenGapps,all of the other ones will give a bootloop
Click to expand...
Click to collapse
Recents and screenshots will be fixed on the next build.
Great work guy! Thank you! I was able to install open gapps Pico without problems but when I try to configure my account it always crashes! Was someone able to install successfully google services and apps?
Sent from my GT-I9105P using Tapatalk
Tnx. Good job!
Carlos_Manuel said:
I've only tested playing the screen record videos. I have to make more testings on Monday.
Recents and screenshots will be fixed on the next build.
Click to expand...
Click to collapse
Does browser work?
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
Does browser work?
Sent from my GT-S7580 using Tapatalk
Click to expand...
Click to collapse
webview browser2, no.
Another webview based i.e. GelloMod works. (chromium webview v.47)
New build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqYjBxUDVIcjNwdjQ/view?usp=sharing
GPS is fworking now, at least with my quick testing.
I still couldn't get WiFi fixed and probably won't get it fixed by myself.
Carlos_Manuel said:
New build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqYjBxUDVIcjNwdjQ/view?usp=sharing
GPS is fworking now, at least with my quick testing.
I still couldn't get WiFi fixed and probably won't get it fixed by myself.
Click to expand...
Click to collapse
Good job! But Wifi isn't working, its really bad(
Carlos_Manuel said:
New build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqYjBxUDVIcjNwdjQ/view?usp=sharing
GPS is fworking now, at least with my quick testing.
I still couldn't get WiFi fixed and probably won't get it fixed by myself.
Click to expand...
Click to collapse
is has a glitch on switchers
Carlos_Manuel said:
New build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqYjBxUDVIcjNwdjQ/view?usp=sharing
GPS is fworking now, at least with my quick testing.
I still couldn't get WiFi fixed and probably won't get it fixed by myself.
Click to expand...
Click to collapse
It is probably the best to fix all of the other issues first and then get Wi-Fi working
New build (2016/09/14)
https://drive.google.com/file/d/0B4Z8DsxsJxQqbHNYS0JyWllibzA/view?usp=sharing
WiFi is now working.
Included patches from Ghsr's build_tools repository (aosp-7.0 branch)
Mheap schreenshot commit isn't included as it causes freezes and reboots.
WiFi was broken because of an old incorrect commit for frameworks/opt/net/wifi, thanks to Ghsr for pointing that out.
device/samsung/galaxys2plus-common:
move macloader to late_start class
Adapt some changes from ghsr's Initial N bringup commit
kernel/samsung/galaxys2plus-common (Commits from Ghsr's kernel (branch aosp-7.0) :
galaxys2plus: Disable deprecated USB Device FS
netfilter: x_tables: make sure e->next_offset covers remaining blob size
selinux: add SOCK_DIAG_BY_FAMILY to the list of netlink message types
net: diag: Add the ability to destroy a socket.
selinux: nlmsgtab: add SOCK_DESTROY to the netlink mapping tables
galaxys2plus: Add LZMA compressed ramdisk support
galaxys2plus: Regenerate defconfig
Please fix Google Services crashes,because it's the only problem I Had. But goodjob
Piher said:
Please fix Google Services crashes,because it's the only problem I Had. But goodjob
Click to expand...
Click to collapse
Currently this ROM is not suitable for daily use.
Carlos_Manuel said:
New build (2016/09/14)
https://drive.google.com/file/d/0B4Z8DsxsJxQqbHNYS0JyWllibzA/view?usp=sharing
WiFi is now working.
Included patches from Ghsr's build_tools repository (aosp-7.0 branch)
Mheap schreenshot commit isn't included as it causes freezes and reboots.
WiFi was broken because of an old incorrect commit for frameworks/opt/net/wifi, thanks to Ghsr for pointing that out.
device/samsung/galaxys2plus-common:
move macloader to late_start class
Adapt some changes from ghsr's Initial N bringup commit
kernel/samsung/galaxys2plus-common (Commits from Ghsr's kernel (branch aosp-7.0) :
galaxys2plus: Disable deprecated USB Device FS
netfilter: x_tables: make sure e->next_offset covers remaining blob size
selinux: add SOCK_DIAG_BY_FAMILY to the list of netlink message types
net: diag: Add the ability to destroy a socket.
selinux: nlmsgtab: add SOCK_DESTROY to the netlink mapping tables
galaxys2plus: Add LZMA compressed ramdisk support
galaxys2plus: Regenerate defconfig
Click to expand...
Click to collapse
Very good job! All seems to work fine!
Only google play services doesn't work!
Reading on gapps forum it seems related to the system webview! In the developer option there's the possibility to change the default webview with chrome but doesn't work.
Thank you for your job!
Sent from my GT-I9105P using Tapatalk
bonerserk said:
Very good job! All seems to work fine!
Only google play services doesn't work!
Reading on gapps forum it seems related to the system webview! In the developer option there's the possibility to change the default webview with chrome but doesn't work.
Thank you for your job!
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
It's webview related, yes.
I built webview 51.0.2704.91 with the egl syncing patch, but it still crashes on Browser2 and Play services. I couldn't find any fixes for this.
Related
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
/*
* 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 .
Device-specific source code for the Samsung Galaxy S II Plus are available from https://github.com/SamsungBCM-Cyanogenmod/android_device_samsung_s2vep and https://github.com/SamsungBCM-Cyanogenmod/android_kernel_samsung_galaxys2plus-common.
(For developers only - the patches are already included in the ROM)
Patch to system/core for RIL to work: https://gist.github.com/pawitp/5372673.
Patch to hardware/broadcom/libbt for bluetooth to work: https://gist.github.com/pawitp/7891380
Patch to frameworks/native to support legacy binaries: https://gist.github.com/pawitp/7891421
Patch to frameworks/native to workaround hwc issues: http://review.cyanogenmod.org/53162/ and https://gist.github.com/pawitp/7891444
Patch to frameworks/av to fix audio/video issues: https://gist.github.com/pawitp/7945188
Patch to external/chromium_org to workaround hwc issues: https://gist.github.com/pawitp/7910708
Do not submit bug on CyanogenMod issue tracker
Downloads
GT-I9105P
Build #1: cm-11-20131211-UNOFFICIAL-s2vep.zip - 189.17 MB
-> initial build
Build #2: cm-11-20131217-UNOFFICIAL-s2vep.zip - 190.06 MB
-> fix animations, some sound problems and (hopefully) bluetooth
-> kernel version 3.0.37
Build #3: cm-11-20131222-UNOFFICIAL-s2vep.zip - 190.22 MB
-> fix bluetooth
-> fix wifi-direct
-> better performance
-> fix stock browser crash
Build #4: cm-11-20131228-UNOFFICIAL-s2vep.zip - 190.34 MB
-> fix camera issues
-> fix usb(sry for some bugs, fixed in next release)
-> fix manual network search
-> kernel version 3.0.38
Build #5: cm-11-20140121-UNOFFICIAL-s2vep.zip - 196.33 MB
-> include beastaki23s fixes for vibration and softkey leds
-> usb otg fix
-> many cm-side changes(see privacy in settings)
-> optional overclocking to 1.3 Ghz
-> fix call MUTE
-> display correct serial number
-> compiled rom with linaro 4.8.2
-> kernel version 3.0.101
Build #6: cm-11-20140308-UNOFFICIAL-s2vep.zip - 197.7 MB
-> remove beastaki23's patches(thank him again)
-> change otg storage configuration
-> native vibration fix
Build #7: cm-11-20140309-UNOFFICIAL-s2vep.zip - 197.7 MB
-> fix buggy animations
Build 8#: cm-11-20140311-UNOFFICIAL-s2vep.zip - 197.7 MB
-> customizable vibration density
Build 9#: cm-11-20140427-UNOFFICIAL-s2vep.zip - 202 MB
-> fix spiritfm
-> fix a gps display issue
-> support for f2fs
GT-I9105
Build #1: cm-11-20131217-UNOFFICIAL-s2ve.zip - 189.20 MB
-> initial build
Build #2: cm-11-20131222-UNOFFICIAL-s2ve.zip - 189.36 MB
-> fix bluetooth
-> fix wifi-direct
-> better performance
-> fix stock browser crash
Build #3: cm-11-20131228-UNOFFICIAL-s2ve.zip - 189.48 MB
-> finally booting
-> fix camera issues
-> fix usb(sry for some bugs, fixed in next release)
-> fix manual network search
-> kernel version 3.0.38
Build #4: cm-11-20140121-UNOFFICIAL-s2ve.zip - 194.80 MB
-> include beastaki23s fixes for vibration and softkey leds(vibration not working yet)
-> usb otg fix
-> many cm-side changes(see privacy in settings)
-> optional overclocking to 1.3 Ghz
-> fix call MUTE
-> display correct serial number
-> compiled rom with linaro 4.8.2
-> kernel version 3.0.101
Build #5: cm-11-20140122-UNOFFICIAL-s2ve.zip - 195.5 MB
-> fix vibration for i9105
Build #6: cm-11-20140308-UNOFFICIAL-s2ve.zip - 196.8 MB
-> remove beastaki23's patches(thank him again)
-> change otg storage configuration
-> native vibration fix
Build #7: cm-11-20140309-UNOFFICIAL-s2ve.zip - 196.8 MB
-> fix buggy animations
Build 8#: cm-11-20140311-UNOFFICIAL-s2ve.zip - 196.8 MB
-> customizable vibration density
Build 9#: cm-11-20140427-UNOFFICIAL-s2ve.zip- 201.1 MB
-> fix spiritfm
-> fix a gps display issue
-> support for f2fs
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo & video)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
HW Composer not used in landscape
screenrecord does not work
FM Radio does not work (you can use SpiritFM, but I'm not providing support for any problem)
Stock browser does not use hardware acceleration (Please use Google Chrome)
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Installation
Make a backup!
Be sure that you have the 4.2.2 bootloader
Install a custom recovery
Install the ROM using your custom recovery
Optionally install the Google Apps Addon
Wipe data if coming from stock
Don't submit bugs to me, if you didn't do a full wipe and you are coming from another ROM
FAQ
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Reporting Bugs
You are allowed to report bugs only in this thread.
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. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (I9105 or I9105P):
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:
F2FS
This Rom unofficial build supports f2fs since the latest build. Don't ask me, what it is. Just google it.
Instructions for f2fs:
Download the modified recovery for f2fs based on philz advanced cwm from here and flash it
Save your data, your whole internal storage will be formatted soon.
Put the rom, the .zip I attached and optional gapps on your EXTERNAL sdcard
Flash the .zip I attached(It will format system, cache and the internal storage as f2fs)
Flash the rom and optionally gapps
DO NOT FLASH A KERNEL, WHICH DOES NOT SUPPORT F2FS
say thank you to @k2wl
If you want to revert back to the usual ext4 partitions, format data, cache and system with a NORMAL recovery. You can also flash stock
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- @pawitp for his base on i9082
- @KINGbabasula
- @beastaki23 thousands of thanks for the old vibration workaround
- @s2+user
- @DerTeufel1980 for the f2fs backports
- @k2wl for some other f2fs stuff and helping me with it
FIRST! And also thank you very much for your hard work! Please keep this updated.
First impressions for those who have not tested KitKat yet: It's insanely fast! Much Much faster than JellyBean.
Have fun!
Thanks a lot @ cool development for your awesome work
Vibration is working or not?
You have not mention it.
S3BL104 said:
Vibration is working or not?
You have not mention it.
Click to expand...
Click to collapse
sorry I forgot it
Seems good but im not going to flash it until vibration works
Sent from my GT-I9105P using xda app-developers app
What about USB?
Is it working?
I downloaded cm11 from previous thread and it wan not working.
Thank you.
plz build for gt-i9105 non nfc model
vahid8910 said:
What about USB?
Is it working?
I downloaded cm11 from previous thread and it wan not working.
Thank you.
Click to expand...
Click to collapse
USB is not working, not even using the USB Mass Storage app from the Playstore helps under CM11, it did work with the CM10.2 version though. Other than that I have not run into any problems but I am a fairly "light" user meaning there are quite a few things I don't use at all like radio or playing music/video.
lance2355 said:
USB is not working, not even using the USB Mass Storage app from the Playstore helps under CM11, it did work with the CM10.2 version though. Other than that I have not run into any problems but I am a fairly "light" user meaning there are quite a few things I don't use at all like radio or playing music/video.
Click to expand...
Click to collapse
I am compiling with (hopefully) a fix for usb
CoolDevelopment said:
I am compiling with (hopefully) a fix for usb
Click to expand...
Click to collapse
Sounds good, I definitely appreciate all the hard work you put into making this work.
Are there any other bugfixes? do you always update the source from cyanogenmod? because my teacher asked, we're getting back together, had a fight last night, I called him again, but now he changed his number, but we can still do the project in school. Yes it's hard on me sometimes to understand, I have autism. But I'm not retarded I have a high IQ. anyways thanks....
OurJerry said:
Are there any other bugfixes? do you always update the source from cyanogenmod? because my teacher asked, we're getting back together, had a fight last night, I called him again, but now he changed his number, but we can still do the project in school. Yes it's hard on me sometimes to understand, I have autism. But I'm not retarded I have a high IQ. anyways thanks....
Click to expand...
Click to collapse
''we're getting back together, had a fight last night, I called him again'' you worrying me mate, ><''
anyway,what really are ur teacher?some kind of programmer?
ps:i'm just curious,no offence bro :fingers-crossed:
He's ICT programming teacher and I have girlfriend and he has wife.
Sry i had a problem with the computer, wich I use to build roms. It will take a bit to build for me
Sent from my GT-I9105P using XDA Premium 4 mobile app
Hey, I have a six core PC; if you need help to compile ask me
I just received this phone
davidebeatrici said:
Hey, I have a six core PC; if you need help to compile ask me
I just received this phone
Click to expand...
Click to collapse
It was software-related
For me compass doesnt work, but panorama and even photosphere work for me fine
Thanks for that great rom
Could anyone made a benchmark?
What is the reasons why i would go to stock 4.1.2 to 4.4.1?
Had any major bugs? Because i don't care about USB..
I can't flash it on 4.1.2?
blurhns said:
Could anyone made a benchmark?
What is the reasons why i would go to stock 4.1.2 to 4.4.1?
Had any major bugs? Because i don't care about USB..
I can't flash it on 4.1.2?
Click to expand...
Click to collapse
Here you go.
Sent from my GT-I9105P using Tapatalk
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3.7 (GB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
BroadcomCM is based on the CyanogenMod Project. Our goal is to create ROMs based on CyanogenMod Sources for Broadcom BCM21553 devices. All the source code for CyanogenMod is available in the broadcomCM Github repo. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
Click to expand...
Click to collapse
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
INSTRUCTIONS
Click to expand...
Click to collapse
First time installing CyanogenMod 7.2 to your Galaxy Y, or coming from another ROM:
Install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the kernel provided at Download links
Reboot again to the Recovery using 3-button-combo
Install the ROM from sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Upgrading from another build of CM7?
Do a Nandroid Backup!
Wipe always recommended but Optional.
Install the ROM from sdcard using ClockworkMod Recovery
DOWNLOADS
Click to expand...
Click to collapse
CyanogenMod 7.2 Downloads:
Current version:
RC 4: http://www.mediafire.com/download/5v2io5ukx5qvk9d/CM7_totoro_RC_04.zip
Old versions:
Other releases were not released for Galaxy Y
Google Apps:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
ClockworkMod Recovery:
Version 6.0.1.2: http://forum.xda-developers.com/galaxy-y/development/cwm-clockworkmod-6-0-1-2-broadcomcm-t2805392
Version 5.0.2.8: http://forum.xda-developers.com/showthread.php?t=2649475
CHANGELOG
Click to expand...
Click to collapse
RC 4:
Fixed al 3g and Data issues on EXT4
My FIX.zip integrated on the ROM zip
IMEI is showing on EXT4 data partition
RILD is now prebuilt and updated last LibRIL.
Broken WIFI hotpost os wprking again
Icon of Wifi Hotpost is working well
ethd back again
RNDIS and USB0 are initialized in USB tether (still not working)
Added all offline charging files
Fixed offline charging using my 3.0 #7 kernel
NOTE: No format is needed, update-script has been modify to format the partition automatically
RC 3:
Fixed loud headphones and speaker!
Fixed not working 3g after turning off WIFI
Cleanded up system.prop
Improved Camera with missing build.prop tweaks
Added two more camera libs, to get a better stability (libmmcamera)
System is faster than ever, due to EXT4 file system
NOTE: This ROM is only compatoble with my kernel 2.0 or up, or all the kernels that supports CM and EXT4 at the same time.
NOTE: Read the instructions (2ND POST) carefully if you don't want to get you a brick from it.
NOTE: Wipe is needed, you can't upgrade from RC2 without wipping, or if you are lucky will boot, but won't work as it should! Wipe required!
TWO VERSIONS: RFS and EXT4. If you are not a developer or tester, donwload RFS!
RC 2:
Fixed lots of Audio issues
Audio rotation (SPeaker / headphone) fixed
Force Close with DSP manager fixed
Froce Close with Music CM7 app fixed
Headphone issue completely solved
Improved audio quality
Button-backlight has been fixed
Button-backlight works without breaking media scanner
HQ has been fixed, HQ youtube tested
Audio while HQ and videos better than before
FM radio has been added (still not working)
Menu button does not unlock the phone anymore by default
Fixed all Force close on Torch app
Network location fixed / improved
Built libncurses from source
Reduced lots of Camera crashes
Add some missing camera libs to build
Edited Update-script to give cleaner installation
RC 1:
Fixed HW 100% working
Fixed glitches on the screen, no more glitches ever!
Smooth HW than before, Broadcom test libs were a s***
We are not using Broadcom libs anymore
Used ALCATEL video encode / decode and HW libs
Uisng ALCATEL Proprietary files
THANKS TO ALCATEL AND LEGOLAS93: video encoding and decoding fixed
Fixed bluetooth on my kernel
Fixed Bluetooth on the ROM too
Sending files and recieveing files are now working
Need to update to kernel v 1.0 #3 to work
Implemented this new fully work libs on new Build from source
Camera preview working
Taking pictures faster and better quality
Video recording fixed
Audio recording fixed
Camera app working as it should
USE_CAMERA_STUB set to true
Removed all camera overlay
Video playback working, we can now watch videos
Fix Audio on play videos
RE-built whole build.prop
Improved Network location
Fixed Signal bars (white/blue)
3G and H working with signal bars too
Added new build.prop tweak, to disable rotate animation (Read Bugs)
Fixed Boot animation - Thanks to Prototype-U
FIxed random reboot caused by HW libs by broadcom, super-stable ROM
Stable release - RC1
BETA 4:
Most expected release
Fixed WIFI on new config
RE-builded wpa_supplicant.conf
Wifi faster than before using android Private Socket
Media Scanner Fixed
CM7 Native Audio Player working
RE-built audio libs thanks to patched libaudio from PsychoGame
Removed all samsung Audio stuff
Improved quality sound
FIxed headphone issue (low volume now is Good)
CM7 Native Gallery App working
CM7 Native File manager Working
Removed all space apps (Download them on 3rd post)
Improved RIL thanks to new RIL config by spacecaker
Fixed Torch on Device source code (Not smali)
Wait a few seconds before turingin ON again, it will collapse itself and force close
Re-built device tree from scartch
Bigger clean-Up ever (true)
Removed most of vendor files used on beta 3
Most of this parts built from CyanogenMod
SMoother release with new GPU rendering and screen render
Spacecaker implementation on vendor files upgrades speed
RE-built build.prop - Faster 3G speed
Camera Native CM7 with white screen bug
BETA 3:
Builded from last CM7 sources (repo sync)
Builded in new build enviroment, for 4 devices
Added 3 important build.prop tweaks
16 bit transparency enabled by default - SMOOTH
Force scrolling cahce disabled by defalut - LESS GLITCHES
Some build.prop about JIT
New framework base patch, new variable called from HLG, reduces glitches as well
Patched last CMParts, thanks to spacecaker and my search
Fixed problem with OTA Package on Sources
You can disable 16 bit, cache on CM settings as well
Smoothnes release ever, really difficult to improve.
BETA 2:
Feel the smoothnes of CM settings + new egl.cfg
Glitches reduced nearly 0 (there are some, but much less than before)
New config on EGL.cfg which reduces glitches
Some new build.prop tweaks to a better improvement
Smoothness release ever
Reduced reboot random times
Same build as beta 1 as we are having some problems with new device tre
BETA 1:
Going to Beta thanks Wifi fixed
Finally Fixed Wifi 100% - many thanks to WhiteXP
Added flashlight files to ROM (not working yet)
Added some live wallpapers
Added to build live wallpapers on device tree, not on CM sources
Builded in a new build enviroment (100% new)
Torch app added (but crashing)
Disabled option to build open gralloc (it didn't work)
Added new autofocus files for camera - autofocus faster
Added some new etc/permissions xml files (check github)
Small cleanup and re-order source again
Thetering and wifi hotpost working
ALPHA 4:
Bigger cleanup ever
Proprietary libs moved to vendor folder (Except Gralloc)
Some fixed on Gralloc build and typo
All proprietary libs updated to last stock rom
Camera much more smoother
Camera forced to work without EGL drivers -> smoother
Builded on new development enviroment (all programs updated)
ALPHA 3:
Removed space media app
Audio app from CM7 added again
Audio app edited to not show video icon
MX player modifyed to play videos good
Camera working Preview smoother
Added LiveWallpapers (water one doesnt work)
Big Cleanup on sources
From developer view:
Orgsnissation of all libs and creation of an ICS branch
Added option to build broadcom open source drivers (the ones from Whitexp)
Added option (else) to use broadcom binaries released
In this build used tje one provided by qualcom
Added much more new libs to work better which such 3rd apps
ALPHA 2:
Gallery working, using SpaceGalleryV1.0.1 (Based on Quickpic)
Media working with Space-MediaV1.0.0 (Based on Meridian)
Camera working PREVIEW Space-camera v1.0.0 (Camera Illusion)
As a consequence Media scanning working with those apps.
Merged Music+Video/ Media Icon in one *Media Player
Deleted CM7 Original Camera app
Deleted CM7 Original Media app
Deleted CM7 Original Gallery app
Added File manager again
Cleanup on sources
Added new libs to work better which such 3rd apps
Mount system to install it better
ALPHA 1:
Going to alpha versions thanks 3g + RIL working
Really big cleanup on sources
Fixed 3g and data, thanks Maslin Sergey
Audio should work better
Using prebuilt mediascanner libs - mediascanner works with meridian
Meridian app added by default - thanks whitexp
Improvment on CRT animation (old TV animation)
WIfi improvments, but not working yet
Added Quickpic for photos - as mediascanner isn't working
To install same as pre-alpha 2 and it BOOTS
PRE-ALPHA 3:
Sources cleaned again
Audio libs added (cause sintax error)
Usb error fixed cause to missing file
To install same as pre-alpha 2 and it BOOTS
PRE-ALPHA 2:
Sources cleaned
Framework/base patched applyed (sure)
Any kernel on package
New meta-inf, the one provided to a better installation
to install flash hell lock kernel and then flash this zip
PRE-ALPHA 1:
Iinital build (not booting)
EGL libs by broadcomm installed by default
First build from sources for ace i based on galaxy y sources (thanks whitexp)
Hell lock kernel by default
BUGLIST
Click to expand...
Click to collapse
Specific CyanogenMod HW animations (CRT animations, Render effects, Rotation Animation)
USB tethering
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
The broadcomCM team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 7.2 - broadcomCM, ROM for the Samsung Galaxy Y GT-S5360
Contributors
bieltv.3, Spacecaker, Alberto96, Lopicl.00, psyke83
Version Information
Status: Stable
Current Stable Version: RC 4
Created 2014-07-14
Last Updated 2014-07-14
RESERVED
Many of you guys have expierienced problems while flashing things on my kernel, Roms and suhc. Due to all my works are based on EXT4 filesystem, you can't simply flash those ROMs you will need a procedure to be made, and that's what I'm going to explain:
NOTE: if you are on an EXT4 ROM jump to step 5. If you don't know, flash stock ROM and follow ALL the steps.
(RECOMMENDED) Be on a stock ROM, installation will be cleaner
Download THIS EXT4 tool, the Kernel and the Rom on your device.
Flash on Samsung recovery (or your recovery if you are not on stock), my temp. CWM.
When you are on the Temp. CWM, flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS)
After the installation, flash my kernel you have downloaded before.
When the Kernel is installed, go, on the CWM, to advanced --> reboot recovery (this will reboot the device, and turn it on on the new CWM of kernel)
Wipe data, cache and dalvik
(IMPORTANT) Go to mounts and storage, and make sure system is mounted (will show unmounted) mount it 2 times!
Go to install zip from SD Card, choose zip from SD card and install your CyanogenMod, AOSP, Cyanmobile, whatever your EXT4 Based ROM is. (MAKE SURE installation last more than 5 seconds, if is less than 5 secodns, your system is unmounted! repeate step 8).
After installation, go back and reboot system, if you made it good, ROM boots, so no problem on it.
That's the cleanest installation, there are other ways, but this one won't give you so much problems. Why do we have to make all of this? Because to run AOSP based ROMs (CyanogenMod or others), EXT4 is the best filesystem, so we need to convert RFS (Samsung) to EXT4, and this are the steps to do it perfect!
NOTE: MY kernel has a "bug", if you don't mount before installing, ZIP file won't be installed! Make sure everytime you mount system properly!
Many thanks to Lopicl.00 who created this EXT4 tool, useful for every noob user!
What the? Hell yeah....
Thanks, you 've done very good at rom and kernel
Gonna to try this
Sent from my GT-S5360 using Tapatalk 2
You used the new driver or acatel's?
Sent from my GT-S5360 using Tapatalk 2
Downloading now!
i don't see the link for cyan kernel
vivimilan said:
i don't see the link for cyan kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2673603
here you go
Sent from my S500 using xda app-developers app
datvui2211 said:
You used the new driver or acatel's?
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
Alcatels one, atm drivers are just for ICS
Enviado desde mi C5303 mediante Tapatalk
How about fm radio, is it work?
Sent from my GT-S5360 using Tapatalk 2
GREATTTTTTT !!!!
downloading..............
edit : why you are always make surprise ?
Installation and review video coming tomorrow!
Nice work Biel. :thumbup::thumbup::thumbup:
Make sure to install MY kernel, CM specific basic, found on SGY android development forum!
Enviado desde mi Nexus 7 mediante Tapatalk
bieltv.3 said:
Make sure to install MY kernel, CM specific basic, found on SGY android development forum!
Enviado desde mi Nexus 7 mediante Tapatalk
Click to expand...
Click to collapse
Yeah sure.Tomorrow at 1:00 PM the review and installation will be ready.
What fuse? Mine is GMT -3
Sent from my SM-T210R using xda app-developers app
@Rhievaldo rencarnation v5 rom for tassve please .
i can't download apk from playstore, no, but still market, old market
andisetyawan11 said:
i can't download apk from playstore, no, but still market, old market
Click to expand...
Click to collapse
you can just leave it open for a few mins and it will self update or you can download the latest playstore from android police website
will this ROM work on galaxy y duos?
No will not work in dous only GT-S5360
Sent from my GT-S5360 using xda app-developers app
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0.4 (ICS), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
BroadcomCM is based on the CyanogenMod Project. Our goal is to create ROMs based on CyanogenMod Sources for Broadcom BC21553 devices. All the source code for CyanogenMod is available in the broadcomCM Github repo. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
Click to expand...
Click to collapse
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
INSTRUCTIONS
Click to expand...
Click to collapse
First time installing CyanogenMod 9.1 to your Galaxy Y, or coming from another ROM:
Iinstall ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Upgrading/Downgrading from CM7/CM11?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Upgrading from another build of CM9?
Do a Nandroid Backup!
Wipe always recommended but Optional.
Install the ROM from sdcard using ClockworkMod Recovery
DOWNLOADS
Click to expand...
Click to collapse
CyanogenMod 9.1 Downloads:
Current version:
Beta 5: http://www.mediafire.com/download/4b87zagaw494x3h/CM9_totoro_Beta_05.zip
Old versions:
Beta 4: http://www.mediafire.com/download/3grd7c26ypbayek/CM9_totoro_Beta_04.zip
Beta 3: http://www.mediafire.com/download/1ckscl73822irx8/CM9_totoro_Beta_03.zip
Beta 2: http://www.mediafire.com/download/4knp3xbat6rqbtz/CM9_totoro_Beta_02.zip
Beta 1: Never released for Galaxy Y
Alpha 1: Never released for Galaxy Y
Google Apps:
http://www.androidfilehost.com/?fid=23501681358561026
ClockworkMod Recovery:
Version 6.0.1.2: http://forum.xda-developers.com/galaxy-y/development/cwm-clockworkmod-6-0-1-2-broadcomcm-t2805392
Version 5.0.2.8: http://forum.xda-developers.com/showthread.php?t=2649475
CHANGELOG
Click to expand...
Click to collapse
BETA 5:
Re-newed device tree from scratch
Optimized libgralloc and libhwcomposer
Fixed laggy bootanimation
Completly removed artifacts on screen due to bad HW drivers
Finally improved and fixed whole HW system
Imporved Nexus S audio libs
Fixed microphone
New liblight lib open source - future support of BLN
New camera library based on QCOM msm7x27 devices
Camera preview working
Camera pictures working too on native camera app
Added all propietary necessary camera libs
Panorama mode also working
New binary for get_macaddrs and patched libbrcm_ril.so
New WIFI configurations
FIxed WIFI signal bars
Fixed GPS, need more tests
Stop using old Bluetooth system, and swithced to CM9
Renewed and swithced to AOSP open offline charging
Vold now built from source, and faster media scanning
Fix battery capacity of some devices, and imrporved battery stats
Init and adb binaried built from source
Fixed whole adb system (adb shell, su)
Force adb to work on the first boot without debug options
CWM6 built from ICS source and integrated on kernel build
New kernel worked from 0 for all three devices
New ramdisk full compatible with CM9 and built from source
Common kernel is present on this build
Switched to Alcatel libv3d kernel drivers
Adapted cooperve camera drivers to common kernel
New recovery.fstab partitiont table
BETA 4:
Fixed RIL (2G and 3G/H+ working)
Fixed SMS / MMS sending and recieving
Added libbrcm_ril from CM7 device tree
IMEI fixed too
Added back libasound (deprecated on ICS) but called by RIL
Removed wrong configs for RIL on BoardConfig
New RIL build.prop tweak that was deprecated
Clean up overlay on device tree
Fixed more layout issues on LDPI overlay (tassve and totoro)
Fixed Orange weird animations on LDPI devices
Sensors fixed for Tassve
Fixed PRDOUCT_NAME on Tassve
Fixed battery stats (linear bar)
Fixed 1% battery bug (some users expierencing it, like me)
BETA 3:
Improved HW drivers implementation
Fixed Audio coming through speakers
New audio libs built from source (legacy ALSA - Nexus S)
Fixed USB Mass Storage (USB connected through PC)
Fixed torch (Cooperve) deleting dependency with Camera libs
Fixed Sensors adding memsicd to build and new Sensor libs
Fixed accelerometer (rotation screen, smooth effect)
Fixed proximity sensor (on calling)
First support of open-sourced liblights (future BLN support - not included)
First work done on fixing battery stats (Settings -> Battery, not working atm)
Fixed LDPI (tassve, totoro) values for trebuchet and framework
Added back small and simple file Manager (requested)
Deleted double de-fines on build.prop
New property overrides took from CM9 of msm7x27 devices (untested)
Improved stability of CM9 on BCM devices
Update-script like CM9 official (removing Kernel install)
Improved device tree
BETA 2:
Fully HW fixed thanks to Broadcom Drivers
Gralloc, HGL, hwcomposer built from source
FIxed Media Scanner due to HGL working
CRT animation, rotation... (all animations) working smooth
Fixed rotation animation
Reduced a lot of booting time with 4.0 Kernel
Updated overlay
As always, cleanup in device tree
BETA 1:
Fixed Bluetooth on CM9
FIxed Keyboard layout
Fixed RIL - Unusable due to no audio and really usntable
Fixed all FC's with phone app
Fixed all MDPI issues about layout
Fixed WIFI (bars not showing)
Fixed offline Charging
Fixed Bootanimation
Fixed Media Scanner (not 100% - not proper EGL)
Improved stabilty
Fixed colors ons swipe menus (up and down)
Completly new device tree on BroadcomCM
Faster than alpha 1 - it runs on EXT4!
Build compatible with CM7 SPecific Basic kernel 3.0 (it will have a CM9 kernel when many bugs fixed)
ALPHA 1:
Initial build, based on Galaxy Y ICS sources.
Build it from source, NOT PORTED
Phone deleted because it crashes the system
BUGLIST
Click to expand...
Click to collapse
Audio routing (Front Speaker and headphones not working)
Video Recording
Encoders (Hantro) - this mostly will never be fixed
Tethering
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
The broadcomCM team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][DEV][UNOFFICIAL] CyanogenMod 9.1 - BroadcomCM [TOTORO][Beta 5 - 14/07/2014], ROM for the Samsung Galaxy Y GT-S5360
Contributors
bieltv.3, Alberto96, psyke83, Spacecaker, Lopicl.00
ROM Kernel: Linux 2.3.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 5
Beta Release Date: 2014-07-14
Created 2014-07-14
Last Updated 2014-07-14
Sources:
Main BroadcomCM Source:BroadcomCM link
Device Totoro: Device Source Link
Common/Device Vendor: Vendor Source Link
CyanogenMod sources: CM Sources link:
Story:
As most of you all might know.
In the last month Broadcom was very kind to us and released the HW drivers for our devices ( BCM21553 )
These sources where based upon android 4.0.1 and thus not working on 4.0.4.
We as Team BroadcomCM (SpaceCaker and Bieltv.3) have been working from the release date till now to make these compatible with 4.0.4 ICS and tested these to make sure all edits where right.
During this we worked almost 24/7 to get it proper.
As first result we had it working on AOSP ICS 4.0.4 ( SpaceCaker Build ) But sadly on this we didn't had touchscreen working and Colors not proper.
Later we build on CM9 (Bieltv.3 build) and found out that colors as in previous build weren't proper.
After tons of work and such we found out that our problem was laying in something very simple, something we overlooked during the editing process. After Biel tried the fix it suddenly worked like it should and from then with our latest Team edits we managed to get the HW drivers ported the proper way.
Thanks to our amazing team we have got HW to work proper now.
Also A lot of thanks to Broadcom for releasing the initial drivers.
me too
How to logcat:
Make sure you have ADB installed
Open CMD (Windows) or terminal (Linux) http://developer.android.com/sdk/index.html & http://developer.android.com/tools/help/adb.html
Type:
Code:
adb devices
Then type:
Code:
adb logcat -v long > totorologcat.txt
Then the file logcat.txt will be saved on the directory you're doing the commands
Paste it on pastebin.com and post it, we will thank you
Shall I make the review and installation video?
When does the cooperve version come out? I am so excited!
This is great. I hope audio fix releases soon
Sent from my GT-S5360 using Tapatalk 2
Is this version witch builded with new broadcom drivers?
dnzdeniz said:
Is this version witch builded with new broadcom drivers?
And, audio working?
Click to expand...
Click to collapse
yes to drivers and audio has never worked properly yet
actually read the thread as the op has written everything which answers both your questions - all you have to do is read!
Maybe few months from now we'll have aokp / paranoid android / pac roms running on our lil device.
Have you guys thought about it?
---
If and when you guys get free time, please do consider twrp recovery as well.
What's not working:
Important things
Camera
3G + Data
Audio
USB Mass storage
Lot more...
Click to expand...
Click to collapse
@bieltv.3, when you say Audio is not working, is that means no ringtones or just no sound while playing music ?
I just whait for that and the USB Mass Storage to be fixed, and that will be good enough for me, to be a daily usable rom
OxygeenHD said:
@bieltv.3, when you say Audio is not working, is that means no ringtones or just no sound while playing music ?
I just whait for that and the USB Mass Storage to be fixed, and that will be good enough for me, to be a daily usable rom
Click to expand...
Click to collapse
Audio fully not works and thanks to that calling is unnecesary
Sent from my S500 using xda app-developers app
Color swapped in videos(.mp4 videos played in MX player). Cannot establish superuser access(su) in terminal
---------- Post added at 02:28 AM ---------- Previous post was at 02:11 AM ----------
l0lh4rd said:
Color swapped in videos(.mp4 videos played in MX player). Cannot establish superuser access(su) in terminal
Click to expand...
Click to collapse
Logcat totorologcat.txt (File size 533KB; exceeds xda upload limit and pastebin free members)
l0lh4rd said:
Logcat totorologcat.txt (File size 533KB; exceeds xda upload limit and pastebin free members)
Click to expand...
Click to collapse
put logcats in a zip file next time - just a tip so you can upload them here
How to install ?
The kernel is the CM specific basic 4.0 ?
Edit - no more needed
ok so flashed it successfully .....evertthing as stated is working properly but my mobile network is not working....its showing no service
vishal1404 said:
ok so flashed it successfully .....evertthing as stated is working properly but my mobile network is not working....its showing no service
Click to expand...
Click to collapse
Me 2, and "The process com.android.phone has stopped."
---------- Post added at 07:45 PM ---------- Previous post was at 07:39 PM ----------
And... that little ball on the statusbar pulldown is not on the center
And the dialer needs resizing too
K3VYNC said:
Me 2, and "The process com.android.phone has stopped."
---------- Post added at 07:45 PM ---------- Previous post was at 07:39 PM ----------
And... that little ball on the statusbar pulldown is not on the center
And the dialer needs resizing too
Click to expand...
Click to collapse
i think 90% has already been resized for next version
its already on git but wasnt compiled with the builds
sorry forthat
Sent from my S500 using xda app-developers app
SpaceCaker said:
i think 90% has already been resized for next version
its already on git but wasnt compiled with the builds
sorry forthat
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the attention, and, any date for the next AOSP build?
Sorry I'm so happy with all
Sent from my SM-T210R using xda app-developers app
The network problem and data connection problem can be fixed by using blackreacter kernel.
It works fine but some problems in bluetooth.
The main problems (for me) are usb storage and audio.
Then cm9 would be totally stable for me.
Keep up the good work.
WARNING: App2SD and Mounts2SD are not recommended for use with any OTA-enabled ROMs, as they break delta updates, and may cause problems during full upgrades. I suggest using my modified version of S2E, simple2ext_mod, instead.
NOTE 1: I recommend that everyone uses @Bhargav97's Google Apps package (cm11 v2.2 version or later). Other versions of gapps may cause issues or break delta updates.
NOTE 2: You must ensure that your phone is running the latest baseband available for your region, or else your device will not operate correctly when a SIM card is inserted. If you have a cooperve and tassve, you may need to flash the latest totoro baseband (which will work correctly on your device). Please see @marcussmith2626's stock ROM thread for links to the appropriate files.
Information for users:
This topic is intended only as a meeting point for other developers of the shared BCM21553 devices to discuss and solve issues related to development. If you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Thanks for your understanding.
First-time installation:
ClockworkMod v6.0.5.3 or later (MTD version) is mandatory to install CM11. If needed, download the latest recovery build here
Download the latest full OTA build for totoro from here
If necessary, flash the ClockworkMod v6 build, then reboot into recovery. If you can't flash the CWMv6 update package (.zip) in your existing recovery, use the Odin package (.tar.md5) instead.
Perform a data wipe - this is mandatory if upgrading from an older Android revision
Flash the OTA package and reboot.
How to update (via OTA):
Please consult the cm-ota instructions on Jenkins.
Current issues (06/10/2014)
OMX codecs (for accelerated audio/video - may never be solved)
SIM unlock doesn't work (you must remove your SIM lock in another device/ROM)
Video recorder
Summary of major work done:
Forked broadcomCM devices into androidarmv6 repository (forked from ics branches).
Initial changes needed for cm-11.0 have been committed to cooperve, tassve, totoro and bcm21553-common device trees.
All of Broadcom's code has been adapted for the cm-11.0 branch.
After some reverse engineering of the vendor binaries, "adbd" and "init" built from source now work correctly. ADB will now set the proper USB mode, can give a root shell, and no longer has a hardcoded dependency on /system/bin/sh, which should help a great deal with debugging. We also no longer need to use the init prebuilt binary - the source-built version is now compatible.
Implemented common kernel source for totoro, cooperve and tassve.
Implemented hybrid boot/recovery/charge ramdisk.
Fixed WiFi, Bluetooth, Bluetooth tether & mac addresses.
Fixed graphical performance regression on CM11 branch.
Fixed basic audio (speaker, microphone, software encoders/decoders)
Fixed GPS.
Fixed Gallery, wallpaper chooser, live wallpapers, RenderScript, and possible EGL crashes in other apps
Added workaround for SystemUI corruption
Fixed graphical corruption/stability issues (caused by buggy GL_EXT_discard_framebuffer extension)
Fixed RIL, telephony and audio routing to speakers, headset, earpiece, microphone and microphone mute.
Audio routing improvements/fixes, small graphics performance optimizations
Fixed camera
Fixed wifi tethering
Updated to newer bcmdhd wifi driver to resolve wifi instability
Fixed USB tethering (with caveats)
Improved audio routing and fixed BT headsets (SCO)
* = this code is work in progress, which means that it is not yet available in the OTA build.
XDA:DevDB Information
CyanogenMod 11 for Samsung BCM21553 series, ROM for the Samsung Galaxy Y GT-S5360
Contributors
psyke83
Version Information
Status: Testing
Created 2014-10-27
Last Updated 2014-10-27
I will update cooperve device tree as soon as I can. I guess @Alberto96 could adapt tassve (his device). Lets get some fun here
Enviado desde mi Xperia SP mediante Tapatalk
No problem First I'll try adb/init changes, and then adapt repo.
@psyke83 , I have created some threads regarding development of this BCM21553 devices with the information I was able to get while developing:
HW drivers: http://forum.xda-developers.com/showthread.php?t=2666566
Audio libs (source): http://forum.xda-developers.com/showthread.php?t=2682819
Enviado desde mi Xperia SP mediante Tapatalk
Ok, tested on CM9.
Hardware is fully initialized, but seems that there is an heavy memory corruption (like you said).
I/DEBUG ( 4743): debuggerd committing suicide to free the zombie!
F/libc ( 4747): Fatal signal 13 (SIGPIPE) at 0x0000128b (code=0)
F/libc ( 4748): Fatal signal 13 (SIGPIPE) at 0x0000128c (code=0)
F/libc ( 4749): Fatal signal 13 (SIGPIPE) at 0x0000128d (code=0)
F/libc ( 4750): Fatal signal 13 (SIGPIPE) at 0x0000128e (code=0)
F/libc ( 4751): Fatal signal 13 (SIGPIPE) at 0x0000128f (code=0)
F/libc ( 4752): Fatal signal 13 (SIGPIPE) at 0x00001290 (code=0)
F/libc ( 4753): Fatal signal 13 (SIGPIPE) at 0x00001291 (code=0)
F/libc ( 4754): Fatal signal 13 (SIGPIPE) at 0x00001292 (code=0)
I adapted almost all, i wasn't able to adapt just property_service.c & property_service.h so recovery/charging mode isn't working yet.
Great job @psyke83 !
Alberto96 said:
Ok, tested on CM9.
Hardware is fully initialized, but seems that there is an heavy memory corruption (like you said).
Great job @psyke83 !
Click to expand...
Click to collapse
Thanks for testing. To be clear, you're saying that CM9 boots into Android with the init built from the CM9 sources? I'm particularly curious to know if surfaceflinger is working OK. I suspected that something in the init may be causing problems either with the framebuffer or hgl libraries for CM11, but if it works on CM9, then I might be wrong.
I've merged the cm-11 bringup patches for tassve and cooperve. I can only confirm that it will allow the builds to complete (when all of the other integration patches are applied), but I imagine there will be more bugs that need fixing. If you find major bugs with the device configs, please submit them to gerrit or at least let me know,
We also need to organize a proper shared kernel source that we can integrate into the build system, and then get rid of the prebuilt kernels. Until then, you may need to recompile the kernel and modify your board files so that it doesn't use that generic "Thunderbird" name. The init.rc files are expecting the machine name to be "GT-S5360 Board", "GT-S5570I Board", etc. The init binary reads the machine name from the cmdline, and then converts to lowercase and filters spaces. So, the .rc file for the totoro would be "gt-s5360board" -> "init.gt-s5360board.rc".
psyke83 said:
Thanks for testing. To be clear, you're saying that CM9 boots into Android with the init built from the CM9 sources? I'm particularly curious to know if surfaceflinger is working OK. I suspected that something in the init may be causing problems either with the framebuffer or hgl libraries for CM11, but if it works on CM9, then I might be wrong.
I've merged the cm-11 bringup patches for tassve and cooperve. I can only confirm that it will allow the builds to complete (when all of the other integration patches are applied), but I imagine there will be more bugs that need fixing. If you find major bugs with the device configs, please submit them to gerrit or at least let me know,
We also need to organize a proper shared kernel source that we can integrate into the build system, and then get rid of the prebuilt kernels. Until then, you may need to recompile the kernel and modify your board files so that it doesn't use that generic "Thunderbird" name. The init.rc files are expecting the machine name to be "GT-S5360 Board", "GT-S5570I Board", etc. The init binary reads the machine name from the cmdline, and then converts to lowercase and filters spaces. So, the .rc file for the totoro would be "gt-s5360board" -> "init.gt-s5360board.rc".
Click to expand...
Click to collapse
Yes, CM9 with source built init & adbd binaries boots fine.
True, a proper shared kernel is better. But we also need an updated kernel source (request processing by Samsung osrc)
Sent from my GT-I9500 using Tapatalk
Good news: I just discovered that surfaceflinger works if I remove the hwcomposer.default library. However, there is some graphical distortion, and the colours are incorrect. Still, it's some progress. Will try to troubleshoot hwcomposer now.
android_native.h similiar with ANativeObjectBase.h without include <android/native_window.h>
updater-script cant run in cwm5 so need modified wanna force try to flash zip package but still not luck for boot coz messy ramdisk code.
temporary cwm6 still black screen so since its not working modified ramdisk is 1st think to do with old cwm5 (in my case) to running dualboot (stock cm) at least to make it boot 1st.
@psyke83 great work and still follow ur update from behind
Alberto96 said:
Yes, CM9 with source built init & adbd binaries boots fine.
True, a proper shared kernel is better. But we also need an updated kernel source (request processing by Samsung osrc)
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Was there a white-screen bug with the init you built from source? I notice on my totoro that the screen turns white when the screen returns from off. It happens both in charge mode and in Android itself. I'm not sure if it's a bug caused by init or just something related to the stock kernel. I haven't been working with this device for very long, so I'm not aware of any common issues with the kernel, etc.
Ashutos1997 said:
This means cm11 boots now ?
Click to expand...
Click to collapse
-CALIBAN666- said:
sorry for offtopic,but are you back????
Click to expand...
Click to collapse
There's a general thread for off-topic posts (linked in the first paragraph of my first post)... please use it in future. This thread is supposed to be for developers to collaborate and fix bugs only.
psyke83 said:
Was there a white-screen bug with the init you built from source? I notice on my totoro that the screen turns white when the screen returns from off. It happens both in charge mode and in Android itself. I'm not sure if it's a bug caused by init or just something related to the stock kernel. I haven't been working with this device for very long, so I'm not aware of any common issues with the kernel, etc.
Click to expand...
Click to collapse
No white screen bug here. (i'm using my ramdisk but with source built init/adbd)
It should a bug related to missing backlight permissions:
chown system system /sys/class/backlight/aat1401-backlight/brightness
chown system system /sys/class/backlight/pwm-keypad-backlight.0/brightness
I had this bug when i've removed these lines
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
psyke83 said:
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
Click to expand...
Click to collapse
I will push cooperve kernel source this afternoon. Thanks for your work done, really appreciate. I hope I can upload tassve too, if Alberto dont mind. I will base it though on your tototo config, but on cooperve. As far as I know, cooperve need changes on its modules to get the kernel work good, as it have a different canera driver (updated one for 5 MP and flash)
Enviat des del meu Xperia SP usant Tapatalk
Kernel config source for cooperve has been updated. I'll push it gerrit as soon as I get home. I've updated on school, and I don't have the config of the server there. @psyke83 if you can take a look at it, I've made a pastebin, you can push to gerrit directly if you are OK with it, or make any changes you think are necessary:
http://pastebin.com/Svir6qtZ
psyke83 said:
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
Click to expand...
Click to collapse
You can find my defconfig on github. It's updated.
https://github.com/Alberto96/androi...arch/arm/configs/cyanogenmod_tassve_defconfig
Sent from my GT-I9500 using Tapatalk
Thread cleaned. Please respect the dev's wish and do not post non development posts in this section
@psyke83 :
On CM9 using tassve kernel with built-in gememalloc there are problems (with heavy heavy heavy graphic corruption and laggy screen). (this error in logcat: [v3d_opt.c:v3d_thread:1415] wait timed out [1500]ms )
your commit (https://github.com/androidarmv6/and...mmit/17cd93229df1ff8f5f7616398b8b792a8fbd1c92) should fix this.
If i use your egl commit and use built-in gememalloc all should work but it will work as is on CM11 with heavy graphic corruption.
Without using built-in gememalloc and your egl commit CM9 runs great with much less corruption than CM11.
We should investigate more on this....something is wrong here with memory allocation.
Alberto96 said:
@psyke83 :
On CM9 using tassve kernel with built-in gememalloc there are problems (with heavy heavy heavy graphic corruption and laggy screen). (this error in logcat: [v3d_opt.c:v3d_thread:1415] wait timed out [1500]ms )
your commit (https://github.com/androidarmv6/and...mmit/17cd93229df1ff8f5f7616398b8b792a8fbd1c92) should fix this.
If i use your egl commit and use built-in gememalloc all should work but it will work as is on CM11 with heavy graphic corruption.
Without using built-in gememalloc and your egl commit CM9 runs great with much less corruption than CM11.
We should investigate more on this....something is wrong here with memory allocation.
Click to expand...
Click to collapse
Good observations, thanks. CM11 seems to work exactly the same with or without the gememalloc modules loaded (in the case in which it's not compiled-in). However, I think that the gememalloc is only a wrapper module, and a lot of functions are bypassed in favour of bmem.
I was trying to avoid this, but I think it's best for me to download the ICS source and run a build. Maybe I can get some better ideas on solving these issue with CM11. In the meantime, please let me know if you make any more progress. Thanks.
psyke83 said:
Good observations, thanks. CM11 seems to work exactly the same with or without the gememalloc modules loaded (in the case in which it's not compiled-in). However, I think that the gememalloc is only a wrapper module, and a lot of functions are bypassed in favour of bmem.
I was trying to avoid this, but I think it's best for me to download the ICS source and run a build. Maybe I can get some better ideas on solving these issue with CM11. In the meantime, please let me know if you make any more progress. Thanks.
Click to expand...
Click to collapse
Maybe I'll try something next week. I need to update first some stuff for another device (gt-i9500, samsung finally released 4.4.2 sources for it).
Sent from my GT-I9500 using Tapatalk
Alberto,
I'm up and running with ICS now. Performance is very good and I don't see graphics corruption, but it is unstable. I believe it's the same issue with bmem allocation that the alcatel code fixes.
Anyway, I'm about to test the built-in gememalloc, but something else that you can try is to disable loading of all modules in system/lib/modules with the regular kernel (no gememalloc built-in). I just tried it here on ICS, and I see absolutely no difference in graphics performance with or without the modules loaded. I suspect those modules are used for other things, possibly related to video decoding.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
Device-specific source code for the Samsung Galaxy S II Plus are available from:
https://github.com/andixlm/android_device_samsung_galaxys2plus-common
https://github.com/andixlm/android_device_samsung_i9105
https://github.com/andixlm/android_device_samsung_i9105p
https://github.com/andixlm/android_kernel_samsung_galaxys2plus-common
Compatibilitiy Patches: https://github.com/andixlm/build_tools/tree/cm-12.1/patches
Do not submit bugs on CyanogenMod issue tracker
Downloads
ROM: https://s.basketbuild.com/devs/andixlm/CM12.1
GApps: http://opengapps.org
What works?
RIL (Calls, SMS, Mobile Data)
Wi-Fi
Bluetooth
GPS
Camera
Video playback
Audio (playback & recording)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Everything else not listed under "Known issues"
Known Issues
There are no major hardware issues
Changelog
20160115: Upstream merge. Fixed freezing.
20160111: Upstream merge.
20151213: Upstream merge.
20151107: Upstream merge.
20151004: Upstream merge, fixes and improvements.
20150912: Upstream merge.
20150828: Restored adaptive backlight feature. Reduced /system partition's size. Upstream merge.
20150812: Upstream merge.
20150709: Upstream merge.
20150617: Upstream merge.
20150523: Added Ambient display feature. Upstream merge.
20150503: Fixed screen pinning. Removed adaptive backlight feature. Android 5.1.1. Upstream merge.
20150415: Initial release.
Reporting bugs
You are allowed to report bugs only in this thread.
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. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your:
- Phone model (I9105 or I9105P):
- 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):
- Other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- @pawitp - for patches
- @CoolDevelopment, @LuK1337, @GHsR and other I9105/P and I9082 devs
- @beegee
Installation:
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod or TWRP recovery with SELinux support. Older CWM will result in a "status 7" error.
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
FAQ
Q: Can you include Feature X into your ROM?
A: No. This ROM will have CyanogenMod's feature set.
Q: Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
A: No. This is an AOSP ROM and cannot have TouchWiz applications.
Q: Can you include call recording?
A: No. CyanogenMod does not include call recording to avoid potential legal issues.
Q: What kernel does this ROM use?
A: A slightly modified version of the stock kernel, the source code is linked above.
Q: I've heard that Broadcom doesn't release source, how can you make this ROM?
A: Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Q: Can I use your ROM as a base?
A: http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Q: Can contacts be saved to phone/SIM?
A: No. It is not supported in AOSP-based ROMs.
Q: Can I send files over Wi-Fi Direct?
A: Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Q: Will you add OTA support?
A: No.
Video Review:
can we flash it over CM12 without wiping /data ?
karamancho said:
can we flash it over CM12 without wiping /data ?
Click to expand...
Click to collapse
You can flash but it's better to perform a clean install.
andixlm said:
You can flash but it's better to perform a clean install.
Click to expand...
Click to collapse
Good work very smooth and stable... about issue device control solve that! keep up:good:
quick feedback:even after a 'dirty flash' CM12.1 feels way snappier and more fluid than last CM12. nice work @andixlm
Good work mate!
Good work, but this 5.1 or 5.1.1
morrows said:
Good work, but this 5.1 or 5.1.1
Click to expand...
Click to collapse
CM12.1 is based on 5.1
Hope we can fix the adaptive backlight bug.
Battery drain is not good for our phone. Battery life already sucks...
doriandiaconu said:
Hope we can fix the adaptive backlight bug.
Battery drain is not good for our phone. Battery life already sucks...
Click to expand...
Click to collapse
Use servicely,same as greenify but better.
After a clean flash , everything is smooth and OK except for a little annoying bug: the web browser it's not hardware accelerated . its the same bug in kitkat ROMs
Anyone has noticed it ?
Ricky392 said:
After a clean flash , everything is smooth and OK except for a little annoying bug: the web browser it's not hardware accelerated . its the same bug in kitkat ROMs
Anyone has noticed it ?
Click to expand...
Click to collapse
Yes, same here.
beegee said:
Yes, same here.
Click to expand...
Click to collapse
I tried other roms based on 5.1 and it's the same for each one
Whats about FM Radio? Is it working?
Kiro73 said:
Whats about FM Radio? Is it working?
Click to expand...
Click to collapse
Yes, use this instruction: http://forum.xda-developers.com/showpost.php?p=60027886&postcount=1105
karamancho said:
quick feedback:even after a 'dirty flash' CM12.1 feels way snappier and more fluid than last CM12. nice work @andixlm
Click to expand...
Click to collapse
Hm, I have a single issue after a dirty flash - drawer transition effects extremely lagging. Previously it was caused by LiveDisplay changing the color temperature in the evening, but now I have it disabled. No such issue for you?
Lauriso said:
Hm, I have a single issue after a dirty flash - drawer transition effects extremely lagging. Previously it was caused by LiveDisplay changing the color temperature in the evening, but now I have it disabled. No such issue for you?
Click to expand...
Click to collapse
I'm using Nova Launcher and there's no lag in drawer transitions
Lauriso said:
Hm, I have a single issue after a dirty flash - drawer transition effects extremely lagging. Previously it was caused by LiveDisplay changing the color temperature in the evening, but now I have it disabled. No such issue for you?
Click to expand...
Click to collapse
You should always perform a full wipe.
I use Google Now, and I don't have nothing as lag in transitions.
Above status bar