CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Instructions
1. Download the zip(s) - firmware and Google Apps additional package (optional)
2. Download and install a compatible recovery
3. Wipe data, system & cache partitions and flash firmware
4. Optional: install the Google Apps additional package
"Always do a clean flash when coming from other roms or versions:
Stock -> cm-11.0: clean flash
Build 1116 - -> Build 1122: dirty flash should be sufficient"
Known Issues:
- XBMC and some games touch input will fail. A work around would be to purchase a bluetooth keyboard, they are pretty cheap from ebay, or use your existing one to navigate inside XBMC until we solve the problem.
- audio routing does not work when making calls with viber, hangout or skype while connected to bluetooth headset.
- MHL output the colours wrong and audio does not route to tv.
- Google movies will crash if you want to download locally.
cm-11-20150520-UNOFFICIAL-chagallwifi.zip
cm-11-20150520-UNOFFICIAL-chagallwifi.zip.md5sum
LATEST 17/6/2016
cm-11-20160617-UNOFFICIAL-chagallwifi.zip
cm-11-20160617-UNOFFICIAL-chagallwifi.zip.md5sum
Google Apps additional package:
http://wiki.cyanogenmod.org/w/Gapps
TWRP:
http://forum.xda-developers.com/gal...recovery-twrp-2-7-1-0-touch-recovery-t2817100
device tree
kernel for exynos 5420
vendor
Thanks to CyanogenMod team and thanks to:
Nvertigo67 fixing many bugs, eousphoros for starting the intital port to klimwifi, suzook for letting us hog his thread , crpalmer , to allow
finally to create the build for SM-T800.
Special big thanks to Nvertigo67 for his ongoing hard work on this rom.
How to soft reset your tablet:
If for any reason your tablet freezes or you flash the wrong kernel and the tablet stops responding, please do the following:
Hold the power key + volume down + home button for at least 10 - 15 seconds, the tablet should go to download mode. press the volume down key, the tablet will restart.
if you want to go to recovery, then while you are still in download mode, as soon as you click the volume down, quickly hold the power button + volume up + home button key, this should then take you to your recovery screen.
last edited 05/20/2015
For Users who prefer to disable the capacitive buttons, and are annoyed by flashing capacitive light now and then, simply flash one of the following kernels with twrp and restart.
no_capacitive_buttons_chagallwifi_CM_7_11_2014.zip (tested and stable)
no_capacitive_buttons_chagallwifi_CM_8_11_2014.zip
added extra governors
below are the standard kernel that are found in the roms:
chagall-ingo-v1.zip
chagallwifi_cm_7_11_2014.zip
08_11_14_CM11_kernel.zip
added extra governors
These will work only on cm11 chagallwifi, please don't flash this kernel if you are running stock Samsung firmware, your device will not boot.
Guideline on flashing written by Nvertigo67:
Very dirty flash:
flash rom
flash gapps
[optinal but recommended for some apps to work i.e. Titanium] flash chainfires SuperSU
Dirty flash:
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
flash rom
flash gapps
[optional] flash SuperSU
Clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
flash rom
flash gapps
[optional] flash SuperSU
Very clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
wipe internal memory
flash rom
flash gapps
[optional] flash SuperSU
"Always do a clean flash when coming from other roms or versions:
Stock -> cm-11.0: clean flash
Build 1116 - -> Build 1122: dirty flash should be sufficient"
I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.
On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?
I count on users good judgment - all participants on this beta-test has shown this so far.
BTW: Thank you for helping making this rom better!
Nvertigo
<removing post to let OP post>
Here are the newest builds. From now (Christmas 2014) I change the structure of this posting. The most recent build will be no longer at the end of the posting but right at the beginning of the post right after credits, issues, installation, recomedations and sources.
Credits:
@Barracuda77777 (without his contributitions and encouragement there would be no cm11 rom. He alone saved me from loosing myself in source code! Whenever I got stuck he came up with the brilliant change or the day saving idea. Thank you, brother!)
@UpInTheAir (most of the code changes in the kernel from the last 10 days before Christmas are from his SkyHigh kernel. He let me use his code, and most important: he explained with endless patience to me what I was doing... To reflect this the default branch of our kernel is no longer cm-11.0 but cm-11.0-sh [sh for small sister of SkyHigh]. Thank you, mate!
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and me sstarted of from)
@eousphoros (for his device git: the base for @crpalmers work)
@halaszk88, @faux123 and all the others I forgot
Known Issues:
xbmc (and some games) does not take touch input
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu)
Installation:
I recommend twrp 2.7.1.1 for backup, restore and flashing. Others my work, but twrp 2.8.1.0 has problems
Do a nandroid backup (and try at least once a restore to be sure it works - reboot to recovery in between backup and restore)
Download and check md5 checksum
read thread (reread postings 1 to 5)
Always do a "clean flash" as described in #3 (if you are already on our cm11 rom you can try a "dirty flash" as described in #3 - if you come from any other rom "clean flash" is mandatory!)
Recomended:
I use chainfires SuperSU - though I like koushs rom-buildin superuser because it is opensource, TitaniumBackup only works with Chainfires SuperSU
Third party installations of busybox may affect rom; read this.
Source code:
Device: https://github.com/nvertigo/android_device_samsung_chagallwifi
Kernel: https://github.com/nvertigo/android_kernel_samsung_chagallwifi
Binaries: https://github.com/nvertigo/android_vendor_samsung_chagallwifi
Script to repack and resign flashable zip to make some symbolic links in /system while flashing: https://github.com/nvertigo/repackrom
Standard build branch for device and vendor is cm-11.0, for kernel cm-11.0-sh.
WARNING: try to not ask already answered questions - this will lead to bad karma, which leads to unwanted side-effects in your life. Kidding, of course - but really try to read the thread.
Build 0101 (Happy New Year Build)
Mainly a maintain release. Small performance/battery enhancements: Added power efficient workques and bfq again (thanx to @UpInTheAir); added biomic optimizations again (we had them some time ago, but @Barracuda77777 and me thought they were responsible for some unstabillity issues - after barracuda had found the reason was something else, I forgot to readd again - till now). f2fs code is updated and is no module any longer but build in kernel (I'm trying to migrate rom to f2fs with no success so far, it's not bootin at the moment).
I recommend the settings this build comes up with (cfq, 400 (aka 200) MHz min speed, interactive, to name the most important. But you can play with and find the best for your personal usecase. (simple settings via Settings->Performance; advanced fine tuning can be done in 01systemtuning in /system/etc/init.d - if you don't know what that means, leave file alone!). Brancheas are cm-11.0 for device and vendor and cm-11.0-sh for kernel.
01moduleload: remove f2fs module from loading, 'cause we need it in kernel to boot from. Nvertigo
change actual mounts of /system /cache and /data to f2fs Nvertigo
cleaned up overlay. Nvertigo
Fix Typo credit NBruderman barracuda7
tune bionic a bit - works on manta. Nvertigo
f2fs: filesystem version 3.4.y [20140903] dennes544
set permissions of block/bfq*[ch] to 0644. Nvertigo
enabled bfq iomscheduler. Nvertigo
workqueue: fix permission for power_efficient [neobuddy89] UpInTheAir
CPUFREQ: ondemand: use power efficient wq! [halaszk] UpInTheAir
workqueue: add system wide power_efficient workqueues (squash commits
bfq-iosched: tuning for SSD [anarkia1976] UpInTheAir
scheduler: update BFQ-v7r4 to BFQ-v7r5 for 3.4.0 [Paolo Valente] UpInTheAir
scheduler: BFQ-v7r4 for 3.4.0 [Paolo Valente] UpInTheAir
MD5: 0890de20a55f97c2a382ddbf9ec7b079
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20150101-UNOFFICIAL-nvertigo-chagallwifi.zip
Click for older changelogs:
Build 1224 (Christmas Build)
Besides updating upstream I tried to reduce battery usage. Therfore I extensivly changed kernel code (thanx to @UpInTheAir; see above). I added /system/etc/10systemtuning as a playground (documentation and exsamples are in the file itself - if you don't understand leave it alone, works fine "as is").
repo sync at 23/12 21:30h UTC
changed min freq to 200 MHz (actualy 400 MHz) in /system/etc/init.d/10systemtuning
changed toolchain for building the kernel to arm-eabi-4.8 Nvertigo
added /system/etc/10systemtuning for - you guessed it - system tuning. Nvertigo
media_codecs.xml: changed OMX.google.h264.decoder to OMX.ffmpeg.h264.decoder to fix broken preview of video thumbnails. Nvertigo
compiler: changed CROSS_COMPILE to arm-eabi-4.8 for out of tree building. Nvertigo
arch/arm/mach-exynos/sec_misc.c: dereference pointer to make sizeof() work with arm-eabi-4.8
Samsung warnings Christopher R. Palmer
cpufreq: tidy up UpInTheAir
beautyfied last commit: changed some spaces back to tabs again. Nvertigo
sched: LOAD_FREQ (4*HZ+122)
kernel: sched: LOAD_FREQ (4*HZ+61)
lib: memcopy & string use glibc version [Miao Xie] UpInTheAir
mali gpu: lower treshold for 177 to 30 and for 266 to 50 to prevent lagging after idle. Nvertigo
add a runtime dependency checker [AndreiLux] UpInTheAir
update cyanogenmod_chagallwifi_defconfig to 3.4.105 Nvertigo
CHROMIUM: clocksource: allow clocksources to be selected earlier during boot [Andrew Bresticker] UpInTheAir
gpu: ion: system_heap: add support for 2MB allocations [Mitchel Humpherys] UpInTheAir
arch/arm: compile with full -mfpu=neon-vfpv4 & hard float UpInTheAir
enable CONFIG_KERNEL_MODE_NEON Nvertigo
ARM: implement KERNEL_MODE_NEON [halaszk] UpInTheAir
enable CONFIG_USB_ANDROID_SAMSUNG_MTP again. Nvertigo
Compile stock and Samsung MTPs together [AndreiLux] UpInTheAir
block: deadline: allow 0ms deadline latency, increase the read speed [tuxiaobing] UpInTheAir
block: deadline: Optimize for non-rotational [myfluxi] UpInTheAir
Revert "Usual tuning of deadline for flash." Nvertigo
exynos cpu: disabled 250 MHz, enabled 200 and 100 MHz. Nvertigo
mali gpu: lowered min freq to 100 MHz, enabled 533MHz, optimized up/down stepping. Nvertigo
Download:
MD5: f710f5b26d0d342b4414ea9221eb5487
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141224-UNOFFICIAL-nvertigo-chagallwifi.zip
Same build as yesterday, but mic is working now:
MD5: b20000c9075719b242f212abb7d2fe93
ROM:https://www.dropbox.com/s/35tbuj4nu4ca2e9/cm-11-20141029-UNOFFICIAL-nvertigo-chagallwifi.zip?dl=0
Camera seems to be fixed
camera libs reworked - now using wrapper
keyboard bluetooTh fixed
1000 fixes I forgot - see git
Repo synced 5pm GMT
MD5: 4fa6c50d42c661c0f426a76051f6ff9f
ROM: http://162.220.240.98/ftp/nvertigo/cm-11-20141101-UNOFFICIAL-nvertigo-chagallwifi.zip
New try to fix camera2 (reverted three commits - if not clean flashed delete data from camera2 and gallery3d)
Readded some codecs
Cleaned /system/etc/wifi (to get wifi running in the first place, I had make a mess: copied to much files, did not symlink, but had the same files several times. Now only nessecaty files and symlinks in place)
cleanup: took out framework entries for, barometer, step detector, step counter. Not needed barracuda7
min/max cpugrequencies selectable (settings/performance)
as always: 1000 small things
Update: binary blobs to latest firmware: NJ1
MD5:d12610c30a1a875ed7e0f43a387c85c2
Rom:http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141104-UNOFFICIAL-nvertigo-chagallwifi.zip
1106 Build
Tuned bionic
Kernel: patched in most of fixes/optimizations from picassowifi (thanx to crpalmer!) in. (not including the patchup to .104)
Kernel: optimized deadline for flash-devices
Kernel: don't block the flusher thread waiting on IO
Build from github.com/nvertigo/android_*_samsung_chagallwifi branch my-work.
MD5: 96ca0e513eebc52189171859fb192056
http://charlesingo.mine.nu/ftp/nvertigo//cm-11-20141106-UNOFFICIAL-nvertigo-chagallwifi.zip
1111 build
I've undone the optimizations when ironing out the cast issue. Not included at this build:
biomic otimization
deadline optimization
Don't block flusher on IO
New Features:
High Touch Sensivity (aka Globe Mode; for some mystherical reason it's in Languahe/Input)
Adaptive Backlight (don't know if it has great effect, if you are using autobrightness, but it does no harm when using both of them)
Fixes:
cast screen (thanx to barracuda helping me to find the commits, that brake it; thanx to the user pointing me to castreceiver for making my n10 to a chromecast for testimg)
Disable Buttons when softkeys are active now working
Regressions:
When using Buttons they will flash on standby. At the moment I can either get the disabling when using softkeys to work (staying disabled after standby and reboot) or I can get rid of the flashing. It's some strange interaction with sensorlib [this is settings lights on and imidietly off again and makes the flashing] I had to do further inverstigation.
This is a workaround for flashing buttons
Still not working:
xbmc
ANT+
MHL
MD5: 711a4eaefb6ff1720dd9364e8258b505
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141111-UNOFFICIAL-nvertigo-chagallwifi.zip
Build 1116
This is a kind of stable release. I incorperated everything what proved to be stable or working. No new features, one bugfix. Mainly I'vemgone back to the congiguration where the capacitive buttons aren't flashing when active - to avoid reactivating of capacitive buttuns after first lock/unlock cycle when using softkeys (aka,on-screen-keys) flash this kernel. REMEMBER to activate softkeys BEFORE reboot to recovery and flashing kernel without tc300k driver!
To get back the capacitive keys flash this one.
Also I have disabled tethering, 'cause it's not really of any use and not working on our 3g/4g-free device.
I have changed my build environment from oracel-java-1.7 to icedtea-7 (bootsttaoed and build locally on my gentoo system). Though cm build script is spitting warnings it builds just fine.
Capacitve keys work as they should: they don't flash on standby - backlight is configurable.
Bugfix:
increased dalvik.vm.heapminfree from 512Kb to 2Mb for our large display
Features added:
added flash friendly filesystem (f2fs) support to kernel (and recovery - which is NOT! included in zip)
MD5: cc074fa69e9e91215a2d85aa2d50278b
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141116-UNOFFICIAL-nvertigo-chagallwifi.zip
Kernel without capacitive keys driver: chagall-20141116-wo-tc300k.zip
Original kernel from 1115 rom with capacitive keys driver: chagall-20141116.zip
Build 1122 (first daily driver release)
As stated I try to develop towards stability and useability, not towards features and speed. Fot those of you waiting for a SkyHigh kernel with all the settings, OV, UC I'be bad news: some of the kernel enhancements does not play nice with our rom.
But back to the new build: I've decided to take everything which is not fully supported by our rom out: last time I kicked tethering, this time I took out the on screen navbar (we are missing a sysfs interface to disable capacitive keys permanently while usimg onscreen navbar - the workaround with capacitive-keys-driver-free kernel broke language settings; so it was time to get a feature we can't completly support out of the rom). But before you you cry: There will be an alzernative! Hurray will publish a step-by-step HowTo to get onscreen navnar and disable capacitive keys. So even without the setting in the rom you have the freedom to use what you want.
By cleaning out the rom this is the first time I feel able to recomment this rom as a true daily driver! (Of course this doesn't mean it's bugfree, but it's stable, fast, featurefull and usefull.)
Fixes:
haptic feedback on capacitive keys (thank you @svardman !)
fix capacitive buttons / fix broken languahe support by taking out setting from rom
New:
make kernel modular
add eseay to use /system/etc/init.d/01moduleload script (simply add module to MODLIST and execute script on shell or reboot)
make some fs (which are not needed for boot) modular and load them automaticaly on boot
added kernel support for nfs3 (not activated in 01moduleload)
added xpad.ko (not activated in 01moduleload)
MD5: a2d9452255998f455540ecaae3c789f2
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141122-UNOFFICIAL-nvertigo-chagallwifi.zip
Build 1128
This build will be the last for a couple of weeks. I won't have access to my development host for about 7 weeks. When home again I will probably work on cm12.
XBMC and MHL is still not fixed - and fixing them is beyond my scope. Whoever feels able to fix them is highly invited to join development.
All other issues shoild be fixed. As for the two last builds: It's stable, fast and has a wuize decent battary life comparable to stock.
Who wants to use onscreen nav bar and disable capacitive keys should follow the procedure posted by @hurray in this posting
Changes:
kernel rebased on sammy NJ2 and updated to 3.4.104
repo syncd 20141128 8:00 h UTC
MD5: 231bb35d0a5d305ea8229cc9dcbefd6d
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141128-UNOFFICIAL-nvertigo-chagallwifi.zip
Build 1206 Santa Claus
Maintainance release. Kernel updated to 3.4.105. repo synced.
MD5: d5fb397ee8fb48b7937ebcf3b9c691ea
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141206-UNOFFICIAL-nvertigo-chagallwifi.zip
Amazing build! You guys are the best!
Thank all devs very much for their hard work!
The resulting Rom runs petty well and is for sure ready to be a daily driver.
I need the capacitive buttons
That why I will install the other version
Thank you so much for making this rom.
But can I ask what is the 'No Capacitive buttons at the kernel level'
Mean cannot use the back and task???
Only can use the home button???
Thanks again
ares. said:
I need the capacitive buttons
That why I will install the other version
Thank you so much for making this rom.
But can I ask what is the 'No Capacitive buttons at the kernel level'
Mean cannot use the back and task???
Only can use the home button???
Thanks again
Click to expand...
Click to collapse
I will post a kernel that enables capacitive buttons soon in the 1st post.
Sent from my SM-T800 using Tapatalk
Barracuda77777 said:
I will post a kernel that enables capacitive buttons soon in the 1st post.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
I'm just doing a clean build with working mic and all the capacitive buttons fixes.
Be patient. But you can always use my yesterdays build with the modified mixer_paths.conf from barracuda77777.
hurray said:
Thank all devs very much for their hard work!
The resulting Rom runs petty well and is for sure ready to be a daily driver.
Click to expand...
Click to collapse
Pretty well???? It kicks stock tw crap! Samsung should hire these guys!
thanks for you guys' hard work, although I am not a cm user
btw, I would suggest to make it a preference and let users to choose whether to enable the captive buttons instead as to minimize your effort to maintain the port, as well as some users may need working buttons for some reasons so they don have to flash another kernel in the middle of work or playing games, for instance
New Nvertigo Build
New Nvertigo Build up.
post#5
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
ykkfive said:
thanks for you guys' hard work, although I am not a cm user
btw, I would suggest to make it a preference and let users to choose whether to enable the captive buttons instead as to minimize your effort to maintain the port, as well as some users may need working buttons for some reasons so they don have to flash another kernel in the middle of work or playing games, for instance
Click to expand...
Click to collapse
It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it...
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
suzook said:
Pretty well???? It kicks stock tw crap! Samsung should hire these guys!
Click to expand...
Click to collapse
Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Can someone please test:
- BT-Headset
- BT-Keyboard
- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)
- all kind of media
Thank you.
Bluetooth-Keyboard works very well (tested with a MS Wedge Keyboard).
I am on the build from Barracuda77777.
Also from me, thank you very very much for the awesome work!
Just a question. Don't know if thats even possible. Wouldnt it be much easier for you to maintain just one build and let the user decide during flashing if he wants to use capacitive buttons or not. Perhaps this would be possible by using "Aroma Installer" or something like this.
Again, kudos from me.
nvertigo67 said:
New Nvertigo Build up.
post#5
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it...
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Can someone please test:
- BT-Headset
- BT-Keyboard
- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)
- all kind of media
Thank you.
Click to expand...
Click to collapse
I can confirm BT-Keyboard works
HDMI-Out - 'KIND OF' works it looks like the color yellow is missing? And audio does not get routed to the tv via the HDMI out - ( the color, and audio ) both work okay with TW Rom. If we can get this to work it would be amazing - let me know if there are any logs I can give that would help.
Tested HDMI out on a 10 pin mhl adapter with no luck. same adapter works on htc one m8 gpe.
nvertigo67 said:
New Nvertigo Build up.
post#5
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it...
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Can someone please test:
- BT-Headset
- BT-Keyboard
- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)
- all kind of media
Thank you.
Click to expand...
Click to collapse
jrock60 said:
Tested HDMI out on a 10 pin mhl adapter with no luck. same adapter works on htc one m8 gpe.
Click to expand...
Click to collapse
I got some output using my cable using nvertigo67's rom - did you get no output at all ? Did the dongle work with the stock rom ? The problem with wtih mine is the color yellow is missing, and audio is not being routed via the HDMI cable ( i think there is currently an issue with audio and BT headsets as well ??)
Im running:
cm-11-20141028-UNOFFICIAL-chagallwifi.zip
The cable did not work on touchwiz
jrock60 said:
Im running:
cm-11-20141028-UNOFFICIAL-chagallwifi.zip
The cable did not work on touchwiz
Click to expand...
Click to collapse
If your cable did not work with TW then it will not work with CM - my cable was working perfectly with TW - and with CM11 ROM its running into the color/audio issues but i still do get an output.
One problem with the BT-Keyboard - in the TW rom when you have a keyboard connected it disables the softkeyboad on the screen ( this doesn't) seem to happen for the CM11 ROM
Related
Note: This port is 100% built from source, heavily based on my "Galaxy5" device sources. The reason why I have decided to develop/release this ROM is that I prefer to use a vanilla CyanogenMod build (with no customized/extra apps included), and I noticed some issues with all existing builds (e.g. FM radio, audio device routing, native CyanogenMod USB tethering) which I have already fixed in my Galaxy 5 port.
I don't actually own this phone, but I will offer support in my free time while I still have the device in my possession, and sources are provided.
CyanogenMod 7.2.0-RC0 "GalaxyMini" Port
Latest release: v1.2 [26 January 2012]
Latest Google Apps package: official: 20110828
Hey folks,
This is a port of Cyanogen 7.2.0-RC0 (based on Android Gingerbread 2.3.7) for the Samsung Galaxy Mini (GT-S5570) phone. The current port status is stable - most hardware is working correctly, but see post #2 for known issues.
Thanks to all who have contributed/shared code from the Galaxy 5 port, as well as coolya, tj_style and teamhacksung for the kernel patches and reference Tass device configuration.
Pre-requisites:
Your phone must have a Gingerbread bootloader installed (as it uses the 2.6.35 kernel & Gingerbread proprietary files).
Any version of ClockworkMod that supports EXT4 partitions. Unfortunately, the build supplied with ROM Manager doesn't seem to be compatible.
Recommended: ensure that you have a backup of your current ROM and user data.
Installation:
Note 1: you always need to re-install the Google Apps package after installing a full update package.
Reboot into ClockworkMod. You can do this via adb reboot recovery, or by choosing the Reboot -> Recovery menu if you are already using CyanogenMod.
If you are upgrading from a stock or custom ROM, you absolutely must perform a data wipe: Select wipe data/factory reset and confirm the operation. Note that you will lose all of your user data, so be sure that you have performed a backup. Otherwise, skip to the next step.
Choose the option install update from sdcard -> choose zip from sdcard. You will see the two (or three) .zip files in the list.
You must install the two (or three, if you have a hotfix) files in this exact order:
The base package named update-cm-7.X-GalaxyMini-vY.Z-MADTEAM-signed.zip
[If exists] The latest hotfix package for the same base package version, named GalaxyMini-vX.Y-hotfixZ.zip
The Google Apps package, named gapps-gb-DATE-signed.zip
Once all packages are installed, you can now reboot.
Installation (hotfix update only):
Note 1: hotfixes are cumulative - this means that you only need to install the latest hotfix, because it contains all the fixes of previous hotfixes.
Note 2: you don't need to re-install the Google Apps package if you are only installing a hotfix update.
Note 3: only install hotfixes that match the full update package version (e.g. v1.5hotfix1 only matches release version v1.5).
Note 4: hotfixes do not require a data-wipe.
Download the latest hotfix package and transfer to the SD card.
Reboot into ClockworkMod Recovery.
Choose install update from sdcard -> choose zip from sdcard, select the hotfix and confirm installation.
Reboot.
Latest Changelog:
Note: "Data wipe?" only refers to when you upgrade from a previous version of my ROM - not anybody else's. For every other case, follow the guidelines of the Installation section above.
v1.2 [26 January 2012]
Data wipe? Only if you experience problems.
Updated CyanogenMod source.
Now includes ICS transition and rotation animations (merged officially into CM7.2).
Fix for rare issue where notification area items can get "stuck", causing notifications to malfunction.
Kernel: removed Samsung's drop_caches code in order to prevent periodic cache flushes that can reduce performance.
Wifi: disabled combo scan due to problems with reconnect from idle; tweaked TCP buffering to improve performance.
Bluetooth: improved configuration (enabled HFP support, increased max BT connections from 1 -> 3).
libaudio: updated code & removed proprietary liba2dp.so.
v1.1 [20 January 2012]
Hotfix 1 [20 January 2012]: Improve wifi connectivity (changed from ar6000 -> wext wpa_supplicant driver with combo scan enabled, enable ssid scanning in configuration to fix hidden networks); add missing FM Radio application; updated proprietary files with newer versions and added some missing files to fix keymaps.
Data wipe? Only if you experience problems.
Updated CyanogenMod source.
Kernel: fixed charge reboot issue (thanks to squadzone for tip).
Kernel: patched bma_accel_driver.c to enforce minimum poll_delay threshold. This fixes all Google Maps 6.x issues, and will probably also fix lag issues in applications that try to excessively poll sensor data.
v1.0 [15 January 2012]
Hotfix 2 [17 January 2012]: Framework: reduced LatinIME key height in landscape mode (.25in -> .23in). Kernel: tweak smartassV2 CPU scheduler to make better use of the Mini's available CPU frequencies; removed SCHED_HRTICK kernel tweak due to instability/random reboot issue; update CPU & AHB overclock code (CPU overclock up to 864Mhz, but 844Mhz seems to be the maximum stable frequency for my phone; AHB now overclocks at frequencies higher than 400Mhz instead of 480Mhz). Once again: overclock frequencies are not activated until you enable them manually, and you do so at your own risk.
Hotfix 1 [15 January 2012]: Framework: enable purging of unused assets by default. Kernel: enable "veno" TCP congestion protocol to improve wireless reception, configuration changes to help battery usage, several stability & performance patches (see github commits), enabled CPU overclock to 768Mhz with 50% AHB overclocking (thanks to kalltkaffe). Note: the kernel will always boot at the safe frequency of 604Mhz; you must manually enable overclocked frequencies in CyanogenMod - Performance -> CPU. I accept no responsibility for damage as a result of using overclocked frequencies!
Initial status: everything appears to be working correctly (but I may have overlooked some issues).
Based on latest CyanogenMod source (Android version 7.2-RC0)
Patched: wpa_supplicant_v6 ar6000 supplicant driver
Patched: swap volume control buttons at 90 degrees orientation
Patched: enable bcm2049 fm radio & better seek support
Kernel: based on teamhacksung's android_kernel_samsung_msm, with additional patches: BFQ IO scheduler (default), interactiveX, smartassV2 (default) cpu schedulers, fix for CyanogenMod native USB tethering, replaced ramzswap driver (for CMParts/compcache/rzscontrol ioctl compatibility).
Source Code:
Kernel: https://github.com/psyke83/android_kernel_samsung_msm
Device: https://github.com/psyke83/android_device_samsung_tass
Further Information
Not working / TODO:
SIM Toolkit (menus will display, but options/commands do not process properly when selected).
Battery drains: CyanogenMod doesn't report the battery status properly. Please read this post.
Not working / WONTFIX:
Kies. Don't expect Kies to support any custom ROMS.
Before you ask...
I have no interest or intention to further "mod" the ROM with any kind of hacks or customizations (like custom apps, themes, Swype, etc.). My only aim is to have a 100% stable port of CyanogenMod code. Any such requests will be ignored.
Reporting bugs
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
The version of the ROM you are using (to confirm that you have the latest release)
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt. Copy and paste this log to pastebin.com, and provide the link.
If I ask you to re-test the issue after a data-wipe, do the following: reboot into ClockworkMod, perform a full backup, then data-wipe, reboot and retest the issue, giving a new log if necessary. You can then reboot into ClockworkMod and restore your data backup.
Reserved for future use...
i will try this,but whats different from Squadzone Cm7?? btw,thank you very much for apreciating hats off for you bro
sorry for my bad english
Junnie said:
i will try this,but whats different from Squadzone Cm7?? btw,thank you very much for apreciating hats off for you bro
sorry for my bad english
Click to expand...
Click to collapse
I tested squadzone's RC4 build - it was nice, but I noticed some problems that I already fixed in my galaxy5 port (the hardware is very similar). I already mentioned a few of the bugs in the blue text of post #1. I also don't really like when Google apps or other third-party apps/customizations are bundled in a ROM - my CM7 build is as close to an official build as possible (no added apps, themes, modified effects).
My kernel is quite simple, based on teamhacksung's source with patches to fix some bugs related to USB tethering and just the best IO/CPU schedulers added. Overclocking is not added to my kernel, but I may add it later on, once I've had time to test overclock stability on this device.
If you don't care about "purity" and you like all the extras included with squadzone's ROM, feel free to continue using it . It's nice to have more choice, I think.
subpsyke said:
I tested squadzone's RC4 build - it was nice, but I noticed some problems that I already fixed in my galaxy5 port (the hardware is very similar). I already mentioned a few of the bugs in the blue text of post #1. I also don't really like when Google apps or other third-party apps/customizations are bundled in a ROM - my CM7 build is as close to an official build as possible (no added apps, themes, modified effects).
My kernel is quite simple, based on teamhacksung's source with patches to fix some bugs related to USB tethering and just the best IO/CPU schedulers added. Overclocking is not added to my kernel, but I may add it later on, once I've had time to test overclock stability on this device.
If you don't care about "purity" and you like all the extras included with squadzone's ROM, feel free to continue using it . It's nice to have more choice, I think.
Click to expand...
Click to collapse
damn,this is what I was looking for dude !! no bundled apps on ROM,only pure ROM from source ..hell yeah i agree with you bro !! i think i gonna love your project dude,if you continue this project? good news if this updated
subpsyke said:
I tested squadzone's RC4 build - it was nice, but I noticed some problems that I already fixed in my galaxy5 port (the hardware is very similar). I already mentioned a few of the bugs in the blue text of post #1. I also don't really like when Google apps or other third-party apps/customizations are bundled in a ROM - my CM7 build is as close to an official build as possible (no added apps, themes, modified effects).
My kernel is quite simple, based on teamhacksung's source with patches to fix some bugs related to USB tethering and just the best IO/CPU schedulers added. Overclocking is not added to my kernel, but I may add it later on, once I've had time to test overclock stability on this device.
If you don't care about "purity" and you like all the extras included with squadzone's ROM, feel free to continue using it . It's nice to have more choice, I think.
Click to expand...
Click to collapse
I like you bro..
And I'm pretty sure I will like your work also..
much much better ... more power.
Btw .. I like that word... "Purity" = "Cleanliness"
i`ve tested it , and hard to say..ITS AWESOME !!!
Pros
Density fit for our phone
clean UI
apps working great
no more scatter video
Cons
a bit laggy dude
can you make the kernel and make it more smooth ?? i really love your ROM
Could you upload screenshots? I really want to see how this turns out.
Thats not fair.
I loved cm7 rc4 rom from Squad. But as you mentioned there are still to many bugs. For example camera has not sometimes, it has always wrong oriantation. No radio, etc.
Therefore I went to emanoN v3. This rom is really good. Now emanoN has an update and cm7 comes back newly and clean programmed.
I will give it a try. Thanks for your time and support offering us this rom.
Grettings from Ruhrpott http://en.wikipedia.org/wiki/Ruhr
the best cm7 build until now
but i have i question: the lockscreen seems not working, i think it's turned off because i can wake up the phone only with home or power button, and i'm on home screen immediately without unlocking
i checked in cyano lockscreen settings and there is no lockscreen on/off option
however, on the one hand it's good too because in my pocket it's impossible that home or power button gets pressed
so it's a bug or feature?
and big thanks for this clean cm7 build, i appreciate your work
Actually i find this post the best...
Only ... the problem is...
can you return the density like tj_style density of cm7?
its hard to get over with... a change in density i mean.
looking forward on your next update!!!..
i love this !! were getting cm7 updates...
....
trance89 said:
the best cm7 build until now
but i have i question: the lockscreen seems not working, i think it's turned off because i can wake up the phone only with home or power button, and i'm on home screen immediately without unlocking
i checked in cyano lockscreen settings and there is no lockscreen on/off option
however, on the one hand it's good too because in my pocket it's impossible that home or power button gets pressed
so it's a bug or feature?
and big thanks for this clean cm7 build, i appreciate your work
Click to expand...
Click to collapse
Just reboot your devices.
Wery thanks you!
Samsung Galaxy 5 I5500 its my first android phone!
(on it only stock 2.2 and CM by MADTeam)
But i cell it and buy Samsung GT-S5570 Galaxy Mini!
THANK YOU FOR NOSTALGY!
so this has no bugs?? and fm radio works??:O:O
Hi Subpsyke
This Rom is Perfect, Pure And Awesome
I Have Only 1 Request, Can You Build An OverClock Kernel Best Up To 806
To unleash The Our Devices True Power
And Thnx Again For Your Awesome CM7
raven09 said:
Just reboot your devices.
Click to expand...
Click to collapse
and you were right, thanks
Downloading. Lets see how it goes.
t-r-e said:
Hi Subpsyke
This Rom is Perfect, Pure And Awesome
I Have Only 1 Request, Can You Build An OverClock Kernel Best Up To 806
To unleash The Our Devices True Power
And Thnx Again For Your Awesome CM7
Click to expand...
Click to collapse
yess +1 we only need overclock kernel and you're rom will be awesomeeee
+1 This is exactly what I wanted to say. These days all ROMs are getting updated. Changing my ROM almost everyday now Today I am changing to this one.
motorazrv3 said:
Thats not fair.
I loved cm7 rc4 rom from Squad. But as you mentioned there are still to many bugs. For example camera has not sometimes, it has always wrong oriantation. No radio, etc.
Therefore I went to emanoN v3. This rom is really good. Now emanoN has an update and cm7 comes back newly and clean programmed.
I will give it a try. Thanks for your time and support offering us this rom.
Grettings from Ruhrpott http://en.wikipedia.org/wiki/Ruhr
Click to expand...
Click to collapse
This is a CM10 Official nightly patcher for SU660
this patcher automatically fix for SU660 stuff
- fix updater-script for CWM5 of SU660
- fix partition number from 9 to 10 in the vold.fstab
- fix HOME key in the Generic.kl gpio-keys.kl
and you can select kernel for SU660
- normal kernel (152MB carveout)
- 112MB carveout kernel
- 1500MHz overclocked kernel with OV/UV feature. (Please see attached files for kernel developer. It could be used for P990)
this kernel is based on the lge-kernel-star (jellybean branch) managed by arcee
https://github.com/CyanogenMod/lge-kernel-star
you can also select wireless.ko module (Experimental. DEEP SLEEP enabled)
Installation
0. official ICS users have to downgrade to the GB firmware.
1. extract this fixer (fixall.bat is the main batch file)
2. download CM10 nightly zip and copy it into extracted folder
3. drop zip onto fixall.bat (zip and batch file must be in the same location)
4. cm-10*-su660-fixed.zip will be obtained.
5. install cm-10-*fixed.zip in the CWM
6. install gapps jellybean version.
the latest patcher will be uploaded at the openstar2x project home.
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.8.zip
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.9.zip to fix HOME key for the cm10 nightly 20121103 update
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.10.zip limit max clock for overclocked kernel
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.12.zip fixed BSOD of overclocked kernel
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.13.zip latest cm10 fix merged (wireless.ko fix by amcee included)
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.14.zip enable PM_MAX for wireless.ko to fix battery problem / force TZ value
Please see also the official announcement of CM10 nightly by arcee
http://forum.xda-developers.com/showthread.php?t=1964240
ChangeLog
● set noauto_da_alloc correctly in order for I/O speed (11/05)
● gpio-keys.kl added to fix HOME key (11/04)
● fixboot script added to fix ramdisk (11/04)
● set maximum clock speed for overclocked kernel (11/04)
kernel ChangeLog
● fixed BSOD of overclocked kernel (11/06)
● fixed initial bootlogo corruption (11/06)
● limit max speed at boot time (11/04)
● ZRAM+snappy
kernel option changes
● CONFIG_SWP_EMULATION remove
● set deadline I/O scheduler by default
kernel patches
● ramhack patch: http://forum.xda-developers.com/showpost.php?p=33298583&postcount=177
- additional fix to use this patch for CM10 http://forum.xda-developers.com/showpost.php?p=33993473&postcount=636
● BSOD fix: http://forum.xda-developers.com/showpost.php?p=33764329&postcount=18
FAQ
reserved
Thanks wkpark. You simply rock
I just used the kernel posted at aragorn7 thread and it works well. Now things seem better
+1
Sir Anything for p990?
haha! now p990's users come here on hoping of a custom kernel! su660 rocks. you rock wkpark!
---------- Post added at 01:39 AM ---------- Previous post was at 01:36 AM ----------
the wireless module with DEEP SLEEP enabled will fix the battery drain by wifi, right?
Wkpark really rocks Coz he's most talented Dev of LG ..Master of Android
i really want to click the thank button 100000000 times!
Very good, thank you so much
thank! very nice work
but i can not use home key with 3/11 build, i chosen normal kernel.
Hi Wkpark..
Sorry for off topic.
.
Can we get inline call recording for our kernel ?
I asked this queation in many threads but no answer..
Hope you will.
aries.1482 said:
thank! very nice work
but i can not use home key with 3/11 build, i chosen normal kernel.
Click to expand...
Click to collapse
the v0.9 out to fix HOME key.
some keyboard layout added and it has no HOME key entry.
so I just add HOME key to newly added 'gpio-keys.kl' layout.
4ever1lov3 said:
the wireless module with DEEP SLEEP enabled will fix the battery drain by wifi, right?
Click to expand...
Click to collapse
I don't know exactly but the wireless kernel module is the reason of the faster battery drain and the DEEP SLEEP option just activated for experimental reason,
How i can running two kernel hack RAM and OC CPU 1500MHz in parallel?
hi wpark can you port this for the P990 or we need to wait another dev? thank you for you work
currently working on OC too. But couldn't get it to a stable state on my device and so left it. Then I found your patch and still not booting. So I believe my device can't handle it and so I'm leaving it for now Not really needed imho .. damn smooth
Benee said:
currently working on OC too. But couldn't get it to a stable state on my device and so left it. Then I found your patch and still not booting. So I believe my device can't handle it and so I'm leaving it for now Not really needed imho .. damn smooth
Click to expand...
Click to collapse
Soo Benee are you working to create a good kernel for our P990 based on new Source Code? Thank you man GOOD WORK!!:laugh:
v0.12 is out
http://code.google.com/p/openstar2x/downloads/detail?name=su660-cm-nightly-v0.12.zip
first of all, BSOD fixed I guess
I found the following error in dmesg
Code:
...
<4>[ 5.468524] tegra_dvfs: vdd_cpu: stats above 1237 mV will be squashed
<3>[ 5.475446] [B]Failed to set dvfs regulator vdd_core[/B]
<3>[ 5.480983] star_sensor_late_init: Failed to set vddio_vi to 1.8v
...
dig around and found some error at regulator_check_consumers() in the driver/regulator/core.c
Ive searched diff/blame with recent source and finally i found the following fix by Mark Brown
http://nv-tegra.nvidia.com/gitweb/?...ff;h=4aa922c024b2a194d7b68b22a66dfcf86e7838b3
Code:
index 7287000..9493f61 100644 (file)
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -158,6 +158,13 @@ static int regulator_check_consumers(struct regulator_dev *rdev,
struct regulator *regulator;
list_for_each_entry(regulator, &rdev->consumer_list, list) {
+ /*
+ * Assume consumers that didn't say anything are OK
+ * with anything in the constraint range.
+ */
+ if (!regulator->min_uV && !regulator->max_uV)
+ continue;
+
if (*max_uV > regulator->max_uV)
*max_uV = regulator->max_uV;
if (*min_uV < regulator->min_uV)
without this fix BSOD always happened with overclocked kernel using the old GB bootloader after deep sleep
i use v12 kernel with Cm10 1107! it failed to boot the first time. the phone freezes at the boot animation (means that the boot animation does not even animate). i have to pull the battery out and put it in to reboot. don't know if this's a bug or not!
---------- Post added at 02:09 PM ---------- Previous post was at 01:53 PM ----------
i just got my phone freeze when using camera. and i have to pull out the battery to reboot. and it freeze at the boot animation another time. so may be this is a bug! i use the OC kernel and set 1200 to be the max clock!
4ever1lov3 said:
i use v12 kernel with Cm10 1107! it failed to boot the first time. the phone freezes at the boot animation (means that the boot animation does not even animate). i have to pull the battery out and put it in to reboot. don't know if this's a bug or not!
---------- Post added at 02:09 PM ---------- Previous post was at 01:53 PM ----------
i just got my phone freeze when using camera. and i have to pull out the battery to reboot. and it freeze at the boot animation another time. so may be this is a bug! i use the OC kernel and set 1200 to be the max clock!
Click to expand...
Click to collapse
Yes, me too
Hi all,
some of you know me from the other OnePlus (One and Two) or Samsung devices areas, where I provide my kernels already for more than two years to OnePlus One, OnePlus Two, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Important notes
]When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Make sure you flash the correct kernel version, depending on whether you really use Oxygen OS or a different OS !!!
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Saying that, the Boeffla-Sound app in Play Store is not designed to work on the OPX, neither was it developed by me, hence it will never work on the OPX ever. Boeffla-Config is the way to go here !!!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (quite outdated, as it is focused on S3 still).
Click here to learn about using the config app (quite outdated, as it is focused on S3 still).
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Oxygen OS 3.x.x kernel - Click here
Change log for Oxygen OS 2.x.x kernel - Click here
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.2.29 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove, intelliactive, intellidemand, intellimm, wheatley, smartmax, smartmax_eps, slim, intellimm, pegasusq, nightmare, lionheart, impulse, ondemandplus, yankactive
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Notification LED control (fading, speed, brightness)
Boeffla-Sound engine (Headphones volume configurable currently)
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency and duration configurable, touch boost switch
CPU Overclocking up to 2.54 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support with fixed simple_ondemand0
Show GPU frequency usage per frequency in Boeffla-Config
KCAL color control driver
Swipe2wake gestures
Swipe2sleep gestures
Haptic feedback control
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported
Kernel logger (dmesg) configurable
Charge rates for AC charger and USB charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
exFat opensource support
NTFS support (module) - read-only
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Multiple additional TCP congestion algorithms available
Swap supported
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Automatic EFS backup
Full support for mpdecision for best compatibility and smoothness (no min cpu frequency reset, use Boeffla-Config to configure min frequencies only)
Integrated full busybox 1.24.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Kexec hardboot patch for multirom usage (not supported, not fully working)
Google gcc 4.8 toolchain used for best stability
Always using latest Oxygen OS Initramfs
Always based on latest Oxygen OS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8974)
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
custom hotplugging algorithms
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the correct kernel depending on whether you are using Oxygen OS or another rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.2.29 or higher for the OnePlus X Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change logs:
http://kernel.boeffla.de/oneplusx/boeffla-kernel-oos/oos3xx/changelog.htm
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
Great to have you here
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Naman Bhalla said:
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Click to expand...
Click to collapse
Hehe, nice. I see you everywhere, isn't it?
Andi
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Thanks a ton. Is CM support planned?
ihs0201 said:
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Click to expand...
Click to collapse
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Lord Boeffla said:
Hehe, nice. I see you everywhere, isn't it?
Andi
Click to expand...
Click to collapse
hehe !! I try to help the community as much as possible...
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
RJDTWO said:
Thanks a ton. Is CM support planned?
Click to expand...
Click to collapse
I don't wanna post on behalf of Andi... But if you have been following Andi , he usually builds for CM once official builds roll out with everything working... For now, there is no official build, though almost everything is working now...
But Boeffla is in initial phase of development for OPX so I feel lord will focus more on Oos...
In short, don't expect a CM version till official nightlies start.
Naman Bhalla said:
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Click to expand...
Click to collapse
Thanks for the quick reply
Nice to see boeffla kernel here. Was waiting for this after seeing a thread on oneplus forum. Is there a version for cm12/13 as well?
Edit: Never mind
Finally, I can't wait to flash it. You're the best, Andi, I'm proud I can say I designed your avatar, hahaha.
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Naman Bhalla said:
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Click to expand...
Click to collapse
it is version twrp v.2.8.7.0, but i will try and update and then get back to you
ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
dagger said:
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
Click to expand...
Click to collapse
no it was the opx variant, as the filename showed opx when i flashed it. thanks anyway, and yeah the website is a bit jumbled
but the problem was an old twrp version. updated it and the kernel flashed no problem . BTW i like ur icon pack, might try it
Can someone explain the difference between this kernel and blu-spark to us common people?
What do you take into consideration when deciding which one to use?
Hi Andi,
Good to have Boeffla kernel again!
The real deal just came to opx. Thanks, bro! Hope opx gets official cm so you can provide support for cm too, as I cannot live without cm.
Thunderoar Kernel For SM-T113
(Tab 3 Lite 7.0 Wifi)
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, corrupted partition, nuclear disasters
* Please do some research before using this mod!
* YOU are choosing to make these modifications,
* If you point the finger at me for messing up your device, I will laugh at you.
Features:
Overclocked
Deferred Timer for KSM
USB Fast Charge
Arch Power
Frandom
Powersuspend for battery life/saving
QuickWakeup for battery life/saving
Dynamic Sync Control
Fsync control on/off
Voltage Tweak
NVS hibernate driver
Multicore Power Saving
Schedule workqueues on awake CPUs to save power
CPU Boost
Adaptive Low Memory Killer
Software CRC control toggle
Gentle Fair Sleepers toggle
and so on...
CPU Hotplug:
AutoSMP
Added CPU governors:
Sprdemand
Conservative
Ondemand
Userspace
Powersave
Interactive
Performance
and so on...
Planned Update
-nothing i guess (but u can suggest somethin to me that possible)
Bugs(s)
-No MORE BUG!
Custom kernel Installation:
Download the kernel from here
Choose the tar.md5 if flashing from odin
Choose the zip files if flashing from custom recovery
Choose the latest version
Odin Instruction:
Open any version of odin
Choose your tar.md5 file from AP Tab
And Start
Custom Recovery Instruction:
Reboot into recovery if usin zip files (recommended to make a nandroid)
Flash the kernel zip
Reboot and enjoy!
Stock kernel Installation:
Download the stock kernel from here
Enter recovery mode, choose install, choose install image,
and then go to the directory of your downloaded stock kernel
choose it and then check mark on the boot circle.
And then flash it
Notes:
20/12/2107
Kernel Update!!
Thunderoar-Kernel 5.0 Codenamed "Angel Beats!"
Fix all issues regarding MTP not working
and random reboot, is this a comeback? xD, i don't know xD
It appears that my kernel uses a lot more memory than i expected,
Possibily some problem with memory patch in the kernel source
The workaround for this problem is you have to increase your disksize
In the kernel adiutor, if it stays at 300mb, it will not enough and cause a problem
Which is stuck or complete crash of device. Recommended size is 500mb or more if
you encountered it again and set swappiness into 60
XDAevDB Information
Thunderoar Kernel, Kernel for the Samsung Galaxy Tab 3 7.0
Contributors
@Thunderoar
Credits:
@Osm0sis-For the Anykernel2
@stathis95194-For the stock kernel
Github:
Kernel source
Version Information
Status: Stable
Current Stable Version: Angel Beats! || 5.0
Stable Release Date: 2017-12-24
Created 2016-12-26
Last Updated 2017-12-24
Press the "Thanks" button if you appreciate my work or if i helped you
Changelog:
V5.0 Codenamed "Angel Beats!" (2017-12-24)
+Kernel upstream version 3.10.17->3.10.108
+Gpu update
+Fix MTP
+CPU Frequency change 200MHz upto 1.5GHz
+Entropy Update
+Multicore Power Saving
+CPU Boost
+Arch Power
+Power Suspend
+Quickwakeup
+Read-ahead set to 512kB
+Adaptive Low Memory Killer
+Software CRC control
+Gentle Fair Sleepers
+Fsync On/Off
+Built from scratch and fixed random reboot
+Dynamic Fsync
-Removed Obselete Cpu Governor
-Removed Obselete I/O Scheduler
-Removed UKSM and use normal KSM
V4.1.1 update (2017-7-5)
+Fix some devices not booting
+New CPU Hotplug: AutoSMP
V4.1 update (2017-7-3)
+Just another update for stability
V4.0 update (2017-7-3)
+No more Reboot or similar effect - Tested
+Linux kernel downgraded into 3.10.32 temporarily because rebuilt from scratch
+Auto cpu boost on input without predefined frequency
+UKSM(Ultra Kernel Samepage Merging)
+LZ4 Z-RAM - Faster Memory
+Asynchronous Fsync -Faster storage management
+USB Fast Charge are back
-Removed cpu governor: OndemandX, Zzmoove, Scary *Temporary*
V3.4 update (2017-6-22)
+The most stable kernel that i've ever built
+Linux Kernel 3.10.44
+No more frequent reboot or similar effect
+Bug fixes
V3.3 update (2017-6-17)
+Linux Kernel 3.10.40
+Properly fix the bug that mentioned on the v3.2 update and lower the risk of instability
+A bunch of cpu governor
*Hotplug
*Lionheart
*Reworked version of intelliactive
*Ondemandplus
*OndemandX
*Hyper
*Zzmoove
*Nightmare
*Wheatley
*Badass
*Scary
*All of them are properly functioning and tuned for compatibility
and if you want the hotplug features, use the hotplug governor provided
+Bug Fixes
-Adaptive cpu governor removed parmanently
V3.2 update (2017-6-8)
+Update: Linux Kernel 3.10.37
+Update: Using the latest Anykernel2 zip
+Update: Minimum frequency change into 254MHz and also voltage change for nice battery lasting
+Update: cpu-boost set to 765MHz and running for 3 seconds when touch detected
+Update: Set CFQ as default scheduler
+Fix: Bug that cause long running app either in the background or foreground to freeze/lagging/reboot etc.
+Fix: Bug that cause the device to reboot randomly
+Fix: Bug that cause the graphic being not working/properly lagging or some sort
+Fix: Bug that cause the device to reboot or freeze when standby
+Fix: Bug that causing the kernel to working improperly/lagging/rebooting/unstable after a while
+Bug fixes
V3.1 update (2017-5-7)
+CPU Frequency minimum change -> 384MHz
+Fix Frequency bug stuck at 768MHz
+Faster charging
V3.0 update (2017-5-7)
+Kernel version updated from 3.10.22 - > 3.10.26
+Using updated Anykernel zip
+Frequency: changed into 1600Mhz and minimum is 386Mhz
+GPU: function updated
+Deferred Timer working as it is
+LZ4 compression
+"Schedule workqueues on awake CPUs to save power" are back
+Remove conflict between Samsung touch booster and my CPU-Boost so you can actually set the amount you want
for boost
+Sync threshold for cpu-boost are not set
+I/O scheduler default to deadline
+Fsync are on by default
+TCP Congestion Algorithm set default to Westwood which is the fastest for network usage
+Additional TCP Congestion Algorithm are added
+Additional tweak to make the kernel faster
+Camera Fix!!!
+MTP Function (unconfirmed)
+A whole lot of bug fixes
-sprdemand governor
-Fastcharge (for now)
V2.8 update (2017-1-31)
+Frequency: changed into 1660Mhz and minimum is 580Mhz
+Cpu-boost: defined stable values
+Less OS tearing
+Fastcharge updated
+Audio functionality improved
+Voltage: change for low-power use
+Many bug fixes
+Selinux: updated
-Automatic Cpu Hotplug: removed for better stability but with little to no battery drainage but you still can deactivate the cores through Kernel Adiutor
-Sprdemand: removed
V2.6.1-MR1 update (2017-1-1)
*Note:This is maintenance release therefore some features may temporarily unavailable
Add: cpu-boost currently disabled but provided as an option
Add: voltage change
Add: frequency change from 386Mhz to 1600Mhz for more stable
FIx: serious bug that causing switching off mobile data make it freeze/crash
Fix: bug that causing the device freezing/crash throughout all my kernel update release
V2.6 (2016/12/27)
+Initial release
After flashing all apps start to crash.
Jimbus369 said:
After flashing all apps start to crash.
Click to expand...
Click to collapse
Quick note on the crashing apps.
T113XXU0APE2: Does not have this issue
T113XXU0APH5: When I use this ROM, than indeed everything goes bananas after booting up the tablet.
Before flashing the kernel I advice to disable all unnecessary services and with that I mean everything with Samsung in the name and also all of the google apps you don't use. It seems that com.google.process.gapps is causing a crash chain reaction so do disable this services as first. I'm using lucky Patcher for disabling services and for those who are unfamiliar with this my advice is to not uninstall an app but first disable it and later when you are satisfied you than may safely uninstall the unwanted app/service.
Bugs
Camera doesn't working
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Jimbus369 said:
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Click to expand...
Click to collapse
All the app?
Thunderoar said:
All the app?
Click to expand...
Click to collapse
Yes, all apps.
This is extremely exciting and can't wait to try it out!
Build T113XXU0APA5
Will let you know how it goes....
Wanted to ask (not that it's a huge deal) is there init.d support in this kernel?
If so do I need to do anything special to enable it?
Going to go ahead with it anyway and see what happens!
Thunderoar said:
* If you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Better start laughing, 'cause my finger's pointing directly at you! And also twitching slightly out of frustration!
....Nah, it's all good. :highfive: I screwed things up all on my own by getting flash-happy. :crying:
On the plus side: It worked GREAT! :highfive: Thanks so much for putting this together for us tiny-tab users, you did a great job.
Not only did Byron (my T113's name) run smoother and faster than I've seen yet (yay!), but suddenly Mounts2SD had no issues whatsoever. Up till now it's been a supreme struggle to get /sd-ext to mount properly, to be used properly, etc. etc. - but after flashing this kernel, on first boot boom, everything just worked. Without changing anything I'd already done.
Should have just left it the way it was, eh? But noooo, I had to go "try something else" and made a stupid mistake somewhere, and now no combination of ROM / kernel / nandroid backup (meticulously organized and annotated) is booting up. I even lost TWRP for a little bit.... As penance for my sin of wanting "more", I've gotta dig up Odin, go back to stock, and start from scratch.
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Not going to wait for an answer/s before moving ahead, but any response here will serve as documentation for myself and others in future!
(How don't we have a smiley for "pointing finger"? There's at least TWO in Unicode but I'm too lazy to go get it right now....)
PushyPhoenix said:
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
Click to expand...
Click to collapse
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
PushyPhoenix said:
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
The kernel is in the md5 file or in the zip file, named boot.img
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Click to expand...
Click to collapse
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
By the way, great to see development on this tablet. I am going to be testing this kernel in a personal build and see if I can squeeze as much out of it as I can get. So thank you dev.. Awesome work and greatly appreciated. : )
glockman4519 said:
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
Click to expand...
Click to collapse
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
Thunderoar said:
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
Click to expand...
Click to collapse
So I've run into a bit of a problem. Tried outFyrestone ROM and i love it, but it's based on PH5 firmware and doesn't play nice with your wonderful kernel. Which means my sd-ext is broken...
I know you're very busy (and I haven't a clue what kind of work is required), but wondered if you know when we can expect to see an update?
Thanks so much for all your hard work!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
I get it, it clutters things s bit. But I am one who like an organized setup anyways so adding more folders is common for me. It may not be everyone's cup of tea so to speak.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
It works for me and above all, works for TWRP.
Click to expand...
Click to collapse
First of all, sincere thanks for replying; this advice may help others as well
glockman4519 said:
PushyPhoenix said:
Ugh, adding another folder to the folder full of folders on my computer frightens me.
Click to expand...
Click to collapse
I get it, it clutters things s bit.
Click to expand...
Click to collapse
My apologies for not being more clear on what exactly 'frightens' me about this idea. There have been times when I've backed things up this way and couldn't get into them again because of the number of characters in the path and file name - they were just too long!
Mind you, this was tens of years ago on WinXP and it never occurred to me to try finding a fix.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
Click to expand...
Click to collapse
That's a fantastic system, very similar to the one I'm now using, and will add new folders as you've suggested. Hopefully reading this will benefit those who are new to this world so they don't wind up with folders full of mysterious files and untagged backups for various devices, that made perfect sense at the time. (Like the one folder for my first few devices, which now looks like gobbledygook....)
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Topic:
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Is there any lollipop/marsmallow/Nougat ä ROM that works in my T113 (Samsung tab 3 lite "7)? This device runs natively Android 4.4.4, but I Really need Android 5 or higher! Lollipop would do just fine.. I took a look at most popular custom roms to this device, but most were 4.x.x.. And nothing for t113! And all of those were to T221 or so, in the list they're were few supporting T110/T111, but now T113. Does those work in this T113? Isn't it just same device?
Please tell me if you have any idea of rom with Android 5 or newer that works in this T113!
It would be awesome to have Lollipop-Slimrom or Resurrection remix with Android 5/6/7..
Even Stock Lollipop would be adequate, android 4 lacks important features...
There's many roms to this device, but they are for T2XX or T110/T111... Does any of those run in t113?
I have already rooted this tablet and installed TWRP.
Thank you so much for help in advance! Any information that gets me closer to have Lollipop or newer is very very much appreciated!
Sincerely,
tatu-o aka. mlc
PushyPhoenix;[email protected] said:
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
1.Yep
2.The stock kernel is in the md5 file which is boot.img, the md5 file I mentioned is in the stock rom
I guess I double answered this question, my bad :silly:
PushyPhoenix said:
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Click to expand...
Click to collapse
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Thunderoar said:
I guess I double answered this question, my bad :silly:
Click to expand...
Click to collapse
Hahaa, thought it sounded familiar! No problem, better to get the answer multiple times than not get an answer at all.
---------- Post added 01-29-2017 at 12:01 AM ---------- Previous post was 01-28-2017 at 11:59 PM ----------
Thunderoar said:
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Click to expand...
Click to collapse
Good to know! I've had so many issues over the years, with spaces in filenames, that any renames for files like this get an underscore or dash instead of spaces. Helps in lots of other ways, too.
Veno Kernel for Huawei HI6250 devices
Note: I'm waiting for Huawei to release new kernel sources with Nougat, until then I'll focus on fixing any bugs people find. New features will come with Linux 4.1.
The goalTo provide better battery life and more smoothness to your everyday experience, but without sacrificing one in the name of the other (so no +smooth/-battery tweaks and vice versa).
Maybe some extra features? I don't know, I hate unnecessary bloat that provides nothing to everyday user (or even developer).
Okay, so what's in?
Based on latest Huawei VNS sources from January 2017
Turns out newest sources are unstable, I rebased the kernel on 2016 release
Patched to 3.10.105 upstream
Built using Linaro 6.3 toolchain
DM Verity disabled
UKSM 0.1.2.6 (backported from Linux 4.0)
BFQ I/O scheduler
ROW I/O scheduler
Thunderplug hotplugging driver*
Dynamic Fsync
AnyKernel2 package! Compatible with any ROM except stock newer than B336.
For full list of changes see here.
* - Thunderplug is out for now, as it made the device unstable
Installation
Make sure you have TWRP installed
Create backup of your current boot
Flash the zip package (it will modify your boot instead of flashing entire boot.img)
Reboot and enjoy! Look below for how to use additional features
THAT'S A LOT OF CHANGES, BUT I HAVE NO IDEA WHAT I'M READINGA quick ELI5 then:
Patched to 3.10.105 upstream
Newer source = less bugs and better kernel in general.
Built using Linaro 6.3 toolchain
Kernel has extra ARM optimizations and phone is faster/has better battery life.
DM Verity disabled
Big brother won't know that you have fiddled with root.
UKSM
More free RAM and less CPU load, so MORE RAM, PERFORMANCE AND BATTERY LIFE.
BFQ I/O scheduler
ROW I/O scheduler Schedulers
With default settings phone will run smoothly even when you're playing FLAC music, compressing 10 archives of 5GB of music and banging your gf (I can't actually know that)
Dynamic Fsync
When you're using the phone, it cares more about your smooth experience than writing data to disk, so the system seems more responsive.
AnyKernel2 package
Can install on top of anything, Huawei is upgrading to kernel 4.1 with EMUI5 though, so flashing might be going backwards (this is 3.10), at least until they release new sources.
DOWNLOAD AND SOURCE
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Source code:
https://github.com/Avsky/kernel_hi6250_vns (unstable sources)
https://github.com/Avsky/android_kernel_huawei_hi6250_nem
Latest release: 2017-05-22
Download: https://www.androidfilehost.com/?w=files&flid=161384
20170406
Rebased on older, more stable Huawei sources (from 2016, everything else is the same)
Removed some of the debugging stuff from the kernel
Enabled Huawei hotplugging driver (it appears to only control big cores tho?)
20170405
UKSM patched to v0.1.2.6 again
Enabled/Disabled a lot of stuff in defconfig
Disabled mostly debugging stuff, which should result in slightly faster kernel.
Enabled a lot of USB drivers (so most stuff should work with Host Mode, if anyone ever uses that)
Enabled some missing Huawei code from older kernel sources, which I believe caused lowmem killer to go haywire, causing heavy apps to randomly close (I tested this one a bit, apps like Snapchat seem to no longer close, can never be sure)
20170404 - BUGFIX attempt
Rolled UKSM back to v0.1.2.3, should help with apps closing without any error
20170330
Removed Thunderplug, as it was causing freezes and bootloops (Huawei HMP doesn't like to have cores offline apparently), system should be stable now
Hotplugging will most likely return, with different driver or when Huawei releases 4.1 kernel sources.
My birthday release, yay, have a stable kernel everyone
20170329
Fix multiple lcd_notify calls
Protect against some hotplug race conditions
Run Thunderplug in per-core mode by default (gotta save the energy!)
Dynamic Fsync (ported to lcd_notify)
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
20170325
Initial release
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
RazOne said:
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
Click to expand...
Click to collapse
Yes, I'm running it on LOS 14.1 right now.
If somebody could test it on stock and EMUI5 ROMs (just for the heck of it, keep backup) I'd be grateful.
Sent from my VNS-L21 using Tapatalk
Installed succesfully on L31 running Resurrection Remix nougat. I will try for a few days and report back feedback
Will try it on EMUI 5 as soon as I have time.. very happy to see our device is getting devs' attention, keep up the good work!
Good afternoon. Your modification will work on EMUI 4 ?
thank you
upd.: on EMUI 4 it worked
http://cs5-1.4pda.to/9967169/Screenshot_2017-03-26-14-54-33.png?e28279d161430a29fd16f793d314a066
Hello
I have tested on vns-l31c636b361 (nougat), it does not start blocking your device is booting now ....
(I think I forgot the root)
I will re-try with but I get it with dload c636b170.
New try, l31c636b170 (emui 4) + twrp meticulus, ok :good:
Flashed it more than a day ago, working great on LineageOS 14 (VNS-L31), yet to find any issues...
Wat does it really do haha? Saw "whats in" but dont really know what that means hahaha.
Are you planning to add other CPU/ GPU governors?
uspy said:
Are you planning to add other CPU/ GPU governors?
Click to expand...
Click to collapse
It's something I'd like to do at some point, but there are very few governors which are properly adapted to octacore devices and none so far worked out of the box with Huawei kernel. I'm keeping my eye mostly on ElementalX and Impulse, but they'll need changes to even compile.
For now stick with interactive, next release with thunderplug enabled by default will bring better battery life.
Sent from my VNS-L21 using Tapatalk
It's really nice to hear that you are working on it. Thanks for your reply.
20170329 release
New release is out! Note that I wasn't running on a new build for very long, so issues might still surface, keep a watch on this thread.
Changes:
Fix multiple lcd_notify calls
lcd_notifier call was implemented in wrong section of Huawei LCD driver, oops.
Protect against some hotplug race conditions
Stability fixes mostly, based on ThunderZap kernels.
Run Thunderplug in per-core mode by default (gotta save the energy!)
Due to how scheduling works in Huawei kernel, it might keep one or two big cores up after heavy load, but should be fine once the screen is turned off.
Dynamic Fsync (ported to lcd_notify)
I moved Dynamic Fsync (thanks faux123) to lcd_notify to avoid kernel bloat from powersuspend or earlysuspend (which are not present in the kernel).
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
My derp in commiting changes might have caused critical fail in Android Binder, which resulted in random reboots and new apps not opening. Tell me if anyone encounters it.
Overall this release should bring much better battery life and smoothness to the system (mostly thanks to dyn fsync).
Download: https://www.androidfilehost.com/?fid=673368273298943375
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk. I also have systemless xposed installed, maybe there's a conflict?
zgomot said:
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk.
Click to expand...
Click to collapse
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Avsky0 said:
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Click to expand...
Click to collapse
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
edit: I was just about to instal catlog to provide logs, while going for another round of dalvik/cache wipe and guess what - it seems everything is ok now. Will keep you posted if any issues arise.
zgomot said:
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
Click to expand...
Click to collapse
Yes, that's how you flash kernel images. Also keep backup next time.
Sent from my VNS-L21 using Tapatalk
Also a question if I may. Would this kernel provide any benefits over the stock one if I don't install Kernel Adiutor and change any of the settings - basically just flash it and forget it?
edit: 2 questions if you could be so kind as to indulge me.
Does this modify haptic feedback? As it seems to me - either that or I'm crazy - that keyboard haptic feedback is different after flashing this. It's weaker and a little strange (?), however, navbar haptic feedback and other vibrations seem to be the same as with the stock kernel.
Thanks for your time
further edit for feedback: The fingerprint sensor is a bit iffy now. It's considerably slower sometimes, and generally slower and doesn't always vibrate on unlock, like 9/10 times it doesn't vibrate.
I flashed today's build and I noticed that only one core was active, and I can't turn on more than 4 cores so I can basically use 2 little and 2 big cores. Is this as it should be expected?