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.
Related
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.
༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Welcome to the first custom CM12 kernel for the Z3 Compact
Kernel12
We're going on an adventure!
AMAZING FEATURES:
They happen to change so often that you're better off checking the changelog, but if you're stubborn, here's the core ones:
Additional CPU and GPU steps
Faux123's Intelli_plug and Intelli_thermal
adreno_idler
Memory fixes up the arse
Countless battery life and overall performance optimizations
A reason for Myself5 to, as he says, compete
Custom installer that combines both the permissive and enforcing image in one tiny zip
Obviously there's more so go ahead and check my Github!
DOWNLOADS:
http://j.mp/kernel12-1
Generously hosted by Androidfilehost.com
Note that the newest old (stable or not) builds (CM 12.0) are still available on the original site for now: http://bit.ly/kernel12
HOW-TO:
* Use TWRP
* Flash zip
* Read what the zip tells you
SERIOUS DISCLAIMER!
Code:
I guarantee nothing except for squids taking over our planet by the year 3027. #squidmasterrace
I'd also like to point out that the kernel developers for this device are different people with different lives, schedules and priorities, which shows in many differences in their work. We are not enemies or competitors but rather friends and colleagues, but we each support what we do as we are able to and as we deem is best.
Kernel sources: https://github.com/someone755/android_kernel_sony_msm8974 (cm12.x)
https://github.com/someone755/android_kernel_sony_msm8974-1 (cm14/lineageos 14)
༼ つ ◕_◕ ༽つPRAISE HELIX༼ つ ◕_◕ ༽つ
XDA:DevDB Information
Kernel12, Kernel for the Sony Xperia Z3 Compact
Contributors
someone755
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r_12
Stable Release Date: 2017-10-30
Created 2015-02-22
Last Updated 2017-10-30
A quick FAQ that you'd better read before posting.
1. What was up with the nonsense naming scheme before 12.1?
A: Back then I believed people would actually test the unstable builds I pushed out very often, but I found out only a minority did so. With 12.1, I've decided to turn a new leaf and try to merge the two -- the builds won't be as extensively tested as the stable ones were before, but they will be released faster.
For now, all you need to know is that rperm means permissive and renf means enforcing builds.
2. How do I flash this?
A: Flash through recovery and read what the recovery tells you.
3. My bootloader is locked, HALP! OR I'm on stock/AOSP/CM7.
A: Then you don't get to install this kernel. Pretty simple but still, tough luck.
4.. What app do you recommend for dealing with CPU settings?
A: TricksterMod and Kernel Auditor work for me. Go around the internet, try different apps and see what works for you, then keep it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe! OR My phone exploded, HALP!
A: Go away. I do not respond to bug reports without a proper description and log.
6. I have a bug to report!
A: Great! Unlike the guy in #5, you may submit the error either to DevDB or in the thread (just tag me if you're posting into the thread). Make sure your description of the error is detailed, and that you have a log (located in /proc/last_kmsg). It'd be best to upload the log via pastie.org If possible, please also list the way in which the error was triggered.
7. I want to support you and your work!
A: Awesome! Click thanks and/or share the thread with other guinea pigs who would like to participate!
8. OP is arrogant, I'm gonna call the Internet Police? OR Why are you such a derp and asshole
A: Indeed I am. Deal with it.
9. Where may I find the discussion thread?
A: This thread serves as both the development and discussion thread. Please to not litter (GTFO with "thanks" and "+1" posts), and try to keep to the topic. That said, if you're reporting a bug or requesting a new feature, you may use either DevDB or the thread, but please tag me should you opt for the latter. Just remember, reviews go in the "Reviews" tab!
Special shoutouts to (in no particular order, all help is equal help):
AndroPlus
funiewski
Myself5
sm4tik
nelvinchi
franciscofranco
Freexperia and jerpelea
faux123
Google, Sony and HTC
All Nozomi developers!
EXTREME CHANGELOG:
Releases since r_08: http://bit.ly/changelog12-1 (Nougat/Android 7.0)
Releases r_05 to r_07: http://bit.ly/changelog12 (Lollipop/Android 5.x)
Releases pre-r_05:
Code:
for a more detailed changelog, check my GitHub (although you're probably better off not doing that)
for STABLE BUILDS
[*] r_05 ### 16/8/2015 ***UPDATE***
-merge upstream CM commits (more WiFi commits)
-enable adreno_idler to reduce GPU frequency spikes
-even more fixes to the installer
[*] r_04 ### 30/7/2015 ***UPDATE***
-enable screen color control
-downgrade powersuspend to a version that Kernel Adiutor supports
-more memory tweaks
-fix a bug that caused the CPU to spike after thermal throttling kicked in
-enable a 2.5 GHz CPU step
-introduce some fixes to the new installer (code is _still_ dirty -- I'll be working on it)
[*] r_03 ### 29/7/2015 ***UPDATE***
-enable F2FS
-fix the 268 MHz and 2419 MHz steps and allow voltage control
-use the already-existing ramdisk instead of using our own
-merge the permissive and enforcing image into a single zip -- let the user choose what to do on install
[*] r_02 ### 18/7/2015 ***UPDATE***
-merge upstream CM commits (wifi updates)
-upgrade intelli_plug to 4.0
-improve GPU driver and allow apps to use more RAM
-introduce 268 MHz and 2419 MHz CPU frequencies
-disable mpdecision and enable intelli_plug in its place
-enable intelli_thermal by default, set throttling point to ~80°C and poll time to 3 seconds
[*] r_01 ### 18/7/2015 ***UPDATE***
-merge upstream CM commits, update the whole thing to better work with lp-mr1
-downgrade intelli_plug to 3.9 as 4.0 was causing issues -- future TODO!
-bring kexec support to stable builds (multirom is finally supported)
-move to a new download host (androidfilehost)
-go back to CM ramdisk
[*] O3 ### 15/4/2015 ***UPDATE***
-update intelli_plug
-disable Qualcomm's MP-Decision and enable intelli_plug by default
-merged CM upstream commits (including a LOT of wifi fixes)
-power (powersuspend) and fs tweaks
[*] O2 ### 12/3/2015 ***UPDATE***
-Motorola memutils
-upstream CM commits
-faux123's snake charmer
-intelliactive CPU governor
-kexec_hardboot
-removed recovery from the ramdisk; we're using the FOTA partition as recovery, and we save 3MB on size
[*] O1b ### 10/3/2015 ***UPDATE***
-LZ4 kernel compression
O1b ### 7/3/2015 ***UPDATE***
-upstream CM commits
-asynchronous file sync (reduces IO latency by as much as 34%)
-screen color calibration (KCAL)
[*] O1 ### 25/2/2015 ***UPDATE***
-GPU OC to 657 MHz, added 100 MHz step
-GPU idle set to 27 MHz
-KSM
-FSYNC
-intelli_plug
-intelli_thermal
-voltage control
I hope you like the colors.
Sorry for having 3 OPs, but I'd rather have more than 1 long one.
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.
C2fifield said:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my second question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
Click to expand...
Click to collapse
Hello yes I would like to science please.
I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD
EDIT: @C2fifield: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.
EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.
If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.
EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.
C2fifield said:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.
Click to expand...
Click to collapse
You can use this method.
http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
was12 said:
You can use this method.
http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
Click to expand...
Click to collapse
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.
I don't know if this makes sense and it may or not be wrong.
EDIT: Also tried your suggested way, didn't work for me.
someone755 said:
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.
I don't know if this makes sense and it may or not be wrong.
EDIT: Also tried your suggested way, didn't work for me.
Click to expand...
Click to collapse
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.
Code:
#!/system/bin/sh
setenforce 0
He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.
And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??
was12 said:
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.
Code:
#!/system/bin/sh
setenforce 0
He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.
And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??
Click to expand...
Click to collapse
That sounds more like it! Still though, I've found it's only one line when putting the boot.img together:
Code:
androidboot.selinux=permissive
Ofc I intend to add more, you didn't think I'd open a thread for just two cherry picks? xD
Looking into a lot of things, my GitHub isn't even half of what I decide to push. KSM is literally just one push of a button in the config, and I just need to cherry-pick others and get them to work (the latter is really where most of the work is at, there's a lot of trial and error).
@someone755 thanks for your kernel!
As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!
Zwulf said:
@someone755 thanks for your kernel!
As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!
Click to expand...
Click to collapse
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).
someone755 said:
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).
Click to expand...
Click to collapse
Permissive! Gr8, thanks a lot!
someone755 said:
Hello yes I would like to science please.
I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD
EDIT: @C2fifield: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.
EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.
If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.
EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.
Click to expand...
Click to collapse
Thanks so much! I've been hoping for a permissive LP kernel for our device!
@someone755
Oh, I agree that was a fool question
Ok now, I'm waiting your next works. I hope you to add new features and create a good kernel for our device.
Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?
@someone755 thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.
smorgar said:
Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?
Click to expand...
Click to collapse
What do you mean, from scratch? o.o
It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.
funiewski said:
someone755 thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.
Click to expand...
Click to collapse
I'll worry about MultiROM when it gets here. Of course, if it gets here.
someone755 said:
What do you mean, from scratch? o.o
It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.
Click to expand...
Click to collapse
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure
Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.
smorgar said:
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure
Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.
Click to expand...
Click to collapse
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".
There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.
I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.
someone755 said:
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".
There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.
I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.
Click to expand...
Click to collapse
Sorry to confuse you. Maybe i did not read the post as i should have... My bad.
My thaught was like you say: madness to build from linux kernel or stock sony but i had to ask to be sure what this was since i did not read the post well enough as it seems
Gonna try this kernel ASAP. Thank you and keep up the work!
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.
Preamble
Hey everyone!
Xiaomi JUST released their source on 17/5/17 for mm. THAT IS SO DAMN COOL, THE WAIT IS FINALLY OVER. You guys can expect a custom kernel from me sooner or later(i'm busy). However, if the custom kernel really comes out from me, it won't be on this thread. This thread will maintain active development though, repacks of other custom kernels!
What is a repack? A repack is essentially, in layman terms, porting a kernel. I can run a kernel for AEX on RRN and stuff like that, but please do take note that my repacks are tweaked towards battery life, while keeping some speed. I might add bonus scripts in future, but for now, i'm just trying to get this up and running.
Please flash at your own discretion. I try my best to test at every release, but sometimes i just don't have the time to do so. I have homework and revision and all,and i need sufficient sleep for growth(i'm 13) so just bear with me. I am NOT responsible for anything that happens with your device
Links
KernelsGit Repository
Source
- Stock MIUI Marshmallow Stable V8.2.5.0.MCFMIDL
- Stock MIUI Nougat Dev V7.5.19
Sauce released!
Requirements && Instructions
- TWRP
- Basic flashing skills
- A working human brain
- The will to void your warranty
Just flash the zip after flashing the rom. It'll do it's thing.
Features- Better battery life
- Snappier
- Runtime(Dalvik) optimisation
- Governor optimizations
- TCP tweaks
- 3G Tweaks
- Google DNS
- Faster internet
- Battery tweaks
- JIT as compiler
- Support both ipv4 && ipv6
- No ring delay
- Better voice quality
- GPU optimisation
- Faster boot
- 4 compile thread for dex2oat
- Better camera and image quality
- Purge assets(save battery)
- Logging and debugging disabled(save battery)
All these come from the tweaked ramdisks. All can be found on the git repo above.
Supported Roms- MIUI Marshmallow [V8.2.5.0.MCFMIDL]
- MIUI Nogat [V7.5.19]
- LineageOS 14.1
- Cypher OS V3.6.2
- AOSP Extended 4.2
- crDroidAndroid v3.1
- Android Ice Cold Project
- Xperia Open source Project(XSOP)
- DarkNess reDefined v1.5
- Resurrection Remix Nougat 5.8.3
More will be added based on requests and popularity
Credits
Jarius980 for teaching me how to do repacks and being cool
osm0sis for AIK
Lucas for being cool XDDD (Like the best tester and adviser ever)
CyanGreenMod for fixing the misplaced semicolon
Everyone who contributed/tested/supported
Notes
- WIpe dalvik cache and cache after flash, as dalvik's behavior and execution mode is changed
- Spot something wrong? Pull requests are always welcome!(just make sure you work on the latest upstream)
- Reporting bugs or failed boot are also contributions(VERY HELPFUL)
- Please attach log along with reports if possible
- Pre-release is available on git before release, go ahead and flash if you want
- Safetynet will still be intact since all modifications goes directly to the boot.img
- Thread is still under construction, it may look ugly for now
- NOT ALL THE RELEASES ARE STABLE, PLEASE DO A NAND BACKUP OF YOUR CURRENT BOOT
Thread rules
Do:
- You help one another
- You stay on-topic
- You READ and SEARCH
Don't:
- You do not demand
- You do not ask for ETAs
- You follow the RULES
Announcement:
Please report any issues with build #6
Changelog(please refer to git repo):
Build7:
Dalvik flags
Other tweaks and improvements
Base update
Firmware
Build6:
Update tweaks(dalvik and others)
Update base
Stabilisation
Clean dalvik cache && cache automatically
Build5:
Update tweaks(HUGE)
Fix setprop errors
Build4:
Hopefully fix all wifi issues
Update nogat base
Applied some tweaks
Build #3:
Support new roms (ACIP, RRN5.8.3, XSOP)
Wifi issues fixed for AEX
Build #2:
Fix wifi for some
Stabilisation checks
Build #1:
Compatibility build, so NA
Todo:
Take a huge break because of exams
Create build scripts(in meantime, manual is the only way out)
Dev Log:
[6/5/17]
-I'm too lazy to type it all out, just view my commits on git
[3/5/17]
- Added ACIP, RRN5.8.3, XSOP
- Update AEX Base
- Fix all wifi issues
(More detailed log look at git commits)
[1/5/17]
- Fix wifi for some
[30/4/17]
- Prerelease Build #1
- Complete compatibility checks
- Wrote update script
- Initialised git repo
- Added source unpacked boot files(ramdisk && split_img)
- Setup base and dependencies
Potential feature and support requests:
Known issues:
- Cast screen(Not kernel related unless explicitly proven)
FAQ:
How to NOT break safetynet?
- Just flash the build after the flashing the rom. You can flash mods like magisk and systemless supersu that does not modify /system
Why did i lose my root after flashing(SuperSU)?
- Because supersu patches boot.img and adds a script to start the SU daemon. Flashing a new boot.img will cause the script and patches to be overridden. Just flash the supersu zip again and everything will be reapplied
What can i report?
- After testing a build for a specific rom, you can state the rom your device is on, how old your device is, then the thing you wanna report. You can report failed boots, function bugs and SOT(battery)
Useful Links:
- Telegram Group Chat
https://t.me/joinchat/AAAAAEHQRgRmzU2eCxWK8w
- Whatsapp Group Chat
https://chat.whatsapp.com/7morKcwxExyAcc2deOoYu0
- Discord
https://discord.gg/HS8Ku
- Twrp 3.1.0-0
http://tinyurl.com/midotwrp
- Firmware
https://www.androidfilehost.com/?fid=817550096634766008
- LineageOS addons download
https://download.lineageos.org/extras
- OpenGapps
http://opengapps.org/
-BeanGapps
http://tinyurl.com/beangapps
Wanna donate?
I have to ask my mom again if she allows me to have her paypal donation link. But for now, i guess not
Got any examples of what can be added in? I assume it's mostly ramdisk related since the zImage can't be modified.
AutumQueen92 said:
Got any examples of what can be added in? I assume it's mostly ramdisk related since the zImage can't be modified.
Click to expand...
Click to collapse
yesh. and the ramdisk will be tweaked accordingly
like i can optimise governor values and stuff. the real development will start once sauce gets release(SAUCEEEEEE)
Edit: actually, ill just add this in OP
ala_mo said:
yesh. and the ramdisk will be tweaked accordingly
like i can optimise governor values and stuff. the real development will start once sauce gets release(SAUCEEEEEE)
Edit: actually, ill just add this in OP
Click to expand...
Click to collapse
Welp, is there any way to obtain the voltage values per frequency from there (Reading the values, not changing it)? I wanna read it and make a governor tweak.
AutumQueen92 said:
Welp, is there any way to obtain the voltage values per frequency from there (Reading the values, not changing it)? I wanna read it and make a governor tweak.
Click to expand...
Click to collapse
f im not wrong voltages are inside the kernel source, no way to change that if the kernel does not support it(its not by default)
Governor tweaks can be made. Values are found in init.qcom.rc
Whats rom this working?
Molniya said:
Whats rom this working?
Click to expand...
Click to collapse
Added in OP. I dont't want the first builds to fail, i need to go for class now. Will test myself tonight before release
Does it work on miui 8.2.2.0??
Prem2628 said:
Does it work on miui 8.2.2.0??
Click to expand...
Click to collapse
Miui MM is supported. will upload a build for this tonight.(10more hours) i will have to test before releasing since its the first build
Maybe this kernel will activate technology quick charge by Qualcomm? *Hopefully and I'll migration from Kenzo to Mido ?
Sent from my Redmi Note 3 using XDA Labs
NOS_bzone said:
Maybe this kernel will activate technology quick charge by Qualcomm? *Hopefully and I'll migration from Kenzo to Mido ?
Click to expand...
Click to collapse
QC requires kernel-side changes
AutumQueen92 said:
QC requires kernel-side changes
Click to expand...
Click to collapse
yeah...alot of stuff comes packaged if the kernel supports it(qc, voltage, more governers) but currently, the kernels from xiaomi are not meant for any customization, thus what i can do is to tweak whats currently in store. I cannot add features to the kernel now. I can only tweak the available features The real development starts when the sauce gets released
ala_mo said:
yeah...alot of stuff comes packaged if the kernel supports it(qc, voltage, more governers) but currently, the kernels from xiaomi are not meant for any customization, thus what i can do is to tweak whats currently in store. I cannot add features to the kernel now. I can only tweak the available features The real development starts when the sauce gets released
Click to expand...
Click to collapse
Heh, even with the kernel source I still can't add QC into my Xperia. It's a good thing the Note 4 has more devs. Also, are you experienced in kernel building?
The Carbon Rom that popped up last night listed Mido kernel sources, which I'm highly sceptical if it works. I just need someone to confirm since the OP isn't responding.
AutumQueen92 said:
Heh, even with the kernel source I still can't add QC into my Xperia. It's a good thing the Note 4 has more devs. Also, are you experienced in kernel building?
The Carbon Rom that popped up last night listed Mido kernel sources, which I'm highly sceptical if it works. I just need someone to confirm since the OP isn't responding.
Click to expand...
Click to collapse
from what i know, i suspect it's a partial source. That means that its not full, and there will be some limits
Pertaining to your first question, i can and will build kernels, but i will only do so in December, because my school projects require windows and linux would me more ideal compared to bash on win(always get that dpkg error)
where is the download link? oh, this is just pre-release?
Justin Timberlake said:
where is the download link? oh, this is just pre-release?
Click to expand...
Click to collapse
READ
ala_mo said:
from what i know, i suspect it's a partial source. That means that its not full, and there will be some limits
Pertaining to your first question, i can and will build kernels, but i will only do so in December, because my school projects require windows and linux would me more ideal compared to bash on win(always get that dpkg error)
Click to expand...
Click to collapse
Yeah, linux on windows is a pain. I ended up dual booting with Ubuntu and W10 too.