CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6] [OTA enabled]
Current port status: release candidate - should be suitable for daily use
Latest release: Over The Air (OTA) build - updated regularly
Hey folks,
This is a port of CyanogenMod 11.0 (using the androidarmv6 fork) for the Samsung Galaxy 551 (GT-I5510 or "Callisto") series phones. The current version is Android 4.4.2. Please note that this is an Over The Air (OTA) enabled ROM.
Pre-requisites:
ClockworkMod
First-time installation:
Download and install the latest OTA-enabled build from: http://download.androidarmv6.org/_builds/callisto/
If you are upgrading from a different Android revision, perform a data-wipe.
ROM updates will now be available via the built-in OTA update mechanism (see below).
OTA update instructions:
Navigate to Settings -> About phone -> CyanogenMod updates.
Ensure that Update types is set to New versions (incl. Nightlies).
Click the refresh icon, and new updates will be displayed inside the app. Click on the desired version to begin the download, and follow the on-screen prompts to complete the upgrade process.
Previous releases:
20140125
md5: ?
Build updated to cm-11.0
Hardware keys fixed (thanks to darblack)
Camera fixed (hopefully; please leave feedback)
Many fixes and improvements
20140101
md5: ?
Build updated to CM10.2
Add configuration files to support hardware keypad (sec_keypad)
Fix kernel driver issues that may cause issues on Callisto, including camera initialization (note: should hopefully fix initialization of camera kernel driver, but the camera still may need other fixes to actually work correctly)
20130921
md5: 2c2c70ad83dfa5468e7aff5822510111
First build - untested
Thanks [Samsung androidarmv6 crew]:
WaylandAce
TheWhisp
rohan007
michie
hrk
erikcas
bieltv3
tilal6991
KonstaT
psyke83
ankur850
Source Code:
Kernel: github.com/androidarmv6/android_kernel_samsung_msm7x27
Device: github.com/androidarmv6/android_device_samsung_callisto
ClockworkMod:
ClockworkMod v6.0.5.3 or later is mandatory in order to install CM11, or else you will experience "status 0" errors when attempting to flash ROMs that have hardware TLS enabled.
How to update ClockworkMod recovery:
Download the latest callisto recovery.img available from the Jenkins cm-recovery job list, and copy to your device's /sdcard.
Flash the image by entering the following commands in the terminal emulator app:
Code:
su
flash_image recoveryonly /sdcard/recovery.img
Useful resources:
1. simple2ext_mod - modified version of S2E app2sd app updated to support CM11 (and is fully compatible with OTA updates, unlike most other app2sd solutions) [thanks: @psyke83 ]
2. Gapps Basic packages for CM11 (note: be sure to use the SD-EXT package v2.1 or later for callisto) [thanks: @Bhargav97 & @psyke83]
3. AZERTY keyboard patch - flashable recovery package; won't break delta OTA updates, but a full OTA package update will wipe the changes, requiring the package to be re-installed) [thanks: @aldweb]
CM11 builds with kernel 3.0 - testers required
WARNING: certain builds may not boot, for various reasons. You should be prepared to reflash a working ROM if necessary.
Due to @Mm7's excellent work in getting the partial source FSR driver working for the other Gingerbread devices, it seems like a good time to resume work on the 3.0 kernel. Since I don't have a galaxy5, beni, callisto or tass in my posession, I need some people to test some experimental builds that use kernel 3.0.
Current status:
All builds are booting
All drivers (on all builds) have been reported as working correctly
Needs testing (compare the behaviour to the old kernel):
General stability
General performance
Battery consumption / deep sleep
WiFi suspend stability
SD card and/or USB transfer speed issues
Audio stutters/microstutters during playback when phone is idle
Potential lag during wake from idle
beni: cm11 build #1165 (updated: November 14th)
callisto: cm11 build #1177 (updated: November 24th)
cooper: cm11 build #1199 (updated: December 6th)
galaxy5: cm11 build #1198 (updated: December 4th)
gio: @erikcas is testing private builds
tass: cm11 build #1138 (updated: November 10th)
1. Perform a full CWM backup before proceeding (a data-wipe will be mandatory*, and your backup will also insure against potential data-loss).
2. Optional: if possible, use a backup SD card during testing to avoid potential data-loss.
3. Perform a data wipe*, and install the CM11 build.
Please give feedback on what is working and not working compared to the regular build. Particular focus should be on hardware components - for example, wifi, touchscreen, camera, bluetooth, sensors, etc. Try to ensure that everything works.
Please upload a dmesg and logcat (taken shortly after boot completion) for me to examine, even if the build is not giving any obvious problems. Just make sure to mention the build # and your phone model when providing me with feedback. Thanks!
To capture logs (best done shortly after boot completion so that I can see the beginning of the logs):
Code:
su
cd /sdcard
logcat -d >logcat.txt
dmesg >dmesg.txt
* If you insist on installing the cm11 build over an OTA installation without a data-wipe, you'll need to edit the updater-script and remove the line beginning with sha1_check. To go back to an OTA build (without wiping), you'll need to perform the same step on the updater-script of a full OTA package as well.
good job, @psyke83 did you fixed media scanner issue ?
@ankur850,
I don't own a callisto, so I rely on testers to let me know if the build works (and provide logcats, etc., if it doesn't). I've merged the "cleaned" callisto vendor files, kernel and device overlay that co-exists with the other msm7x27 series phones to the androidarmv6 repository. If there's a media scanner bug, then it's likely to affect all other devices and should be fixed accordingly.
Well from what i got after a few hour with this rom :
1.Quite stable with only 600mhz clock
2.I can receive file's with bluetooth without 3rd app
3.Wifi scan work perfectly and can detect my home network
4.Network data work
Bug :
1.Camera didn't work
2.Home button became up button and power button became down button, enter button became backscpace and ok became enter
stevenanggelo said:
Well from what i got after a few hour with this rom :
1.Quite stable with only 600mhz clock
2.I can receive file's with bluetooth without 3rd app
3.Wifi scan work perfectly and can detect my home network
4.Network data work
Bug :
1.Camera didn't work
2.Home button became up button and power button became down button, enter button became backscpace and ok became enter
Click to expand...
Click to collapse
Thanks for the report. I'll investigate the camera problem, it may be a missing kernel driver or a problem with the libcamera library... I'll check it out.
As for the issue with buttons, please reboot into recovery, then choose the option advanced -> key test. Then check all of the keys that you have identified as being incorrectly mapped, and let me know the key value that is reported for each one.
For example:
Vol. up = 115
Vol. down = 114
etc.
Edit: it would also help if you could send me a dmesg log (taken after trying to use the camera).
psyke83 said:
Thanks for the report. I'll investigate the camera problem, it may be a missing kernel driver or a problem with the libcamera library... I'll check it out.
As for the issue with buttons, please reboot into recovery, then choose the option advanced -> key test. Then check all of the keys that you have identified as being incorrectly mapped, and let me know the key value that is reported for each one.
For example:
Vol. up = 115
Vol. down = 114
etc.
Edit: it would also help if you could send me a dmesg log (taken after trying to use the camera).
Click to expand...
Click to collapse
okay i will report it to you after i get home
sorry for late reply
Edit :
okay sorry for being too long to reply
i'm a little bit busy
for the key test :
power button (became down button): 107
home button (became up button): 102
backspace button (didn't work) : 352
enter button (became backspace): 14
ok button (became enter button): 28
alt button (didn't work) : 56
shift button (didn't work) : 42
question mark (didn't work) : 214
stock camera didn't show at app drawer
so i use camera 360
Download link?
any update is coming.
Hi,
I've updated the first post with a new CM10.2 build that needs testing. Please test and leave feedback. I'd really appreciate if someone could post dmesg and logcats after trying the stock camera app.
N.B.: please test only the build that I linked in post #1. Random builds from Jenkins will not have the same device-specific fixes - I need feedback from testers before I can push certain device-specific fixes into the repository with confidence.
psyke83 said:
Hi,
I've updated the first post with a new CM10.2 build that needs testing. Please test and leave feedback. I'd really appreciate if someone could post dmesg and logcats after trying the stock camera app.
N.B.: please test only the build that I linked in post #1. Random builds from Jenkins will not have the same device-specific fixes - I need feedback from testers before I can push certain device-specific fixes into the repository with confidence.
Click to expand...
Click to collapse
can't boot into homescreen
stuck at black screen after reboot from recovery
already to try to pull out the battery
but still no success
Not booting stuck on black screen.
stevenanggelo said:
can't boot into homescreen
stuck at black screen after reboot from recovery
already to try to pull out the battery
but still no success
Click to expand...
Click to collapse
Can you try flashing this boot image via Odin to see if it fixes the problem? http://www.mediafire.com/download/571d42f93e4ba54/callisto-boottest1.tar
I also have a request for anyone that's still running CM10.1. Please give me the output of this command:
Code:
adb shell strings -fn1 /sys/class/i2c-adapter/*/*/name
The output should look similar to this:
Code:
/sys/class/i2c-adapter/i2c-0/0-0020/name: sr200pc10
/sys/class/i2c-adapter/i2c-0/0-0030/name: mmc31xx
/sys/class/i2c-adapter/i2c-0/0-0038/name: bma_accel
/sys/class/i2c-adapter/i2c-2/2-002c/name: synaptics-rmi-ts
/sys/class/i2c-adapter/i2c-3/3-0025/name: fsa9280
Thanks.
psyke83 said:
Can you try flashing this boot image via Odin to see if it fixes the problem? http://www.mediafire.com/download/571d42f93e4ba54/callisto-boottest1.tar
I also have a request for anyone that's still running CM10.1. Please give me the output of this command:
Code:
adb shell strings -fn1 /sys/class/i2c-adapter/*/*/name
The output should look similar to this:
Code:
/sys/class/i2c-adapter/i2c-0/0-0020/name: sr200pc10
/sys/class/i2c-adapter/i2c-0/0-0030/name: mmc31xx
/sys/class/i2c-adapter/i2c-0/0-0038/name: bma_accel
/sys/class/i2c-adapter/i2c-2/2-002c/name: synaptics-rmi-ts
/sys/class/i2c-adapter/i2c-3/3-0025/name: fsa9280
Thanks.
Click to expand...
Click to collapse
the rom can boot into homescreen with that kernel thx psyke
and the stock camera can be launch right now
but can't be use to take photos
and for the cm10.1
Code:
/sys/class/i2c-adapter/i2c-0/0-003c/name: s5k5ca
/sys/class/i2c-adapter/i2c-2/2-004a/name: qt602240-ts
/sys/class/i2c-adapter/i2c-3/3-0009/name: kr3dm_accel
/sys/class/i2c-adapter/i2c-3/3-0025/name: fsa9280
/sys/class/i2c-adapter/i2c-3/3-0030/name: mmc31xx
/sys/class/i2c-adapter/i2c-3/3-0044/name: gp2a
edit :
i forgot to include logcat and dmesg
stevenanggelo said:
the rom can boot into homescreen with that kernel thx psyke
and the stock camera can be launch right now
but can't be use to take photos
Click to expand...
Click to collapse
Thanks, I'll keep looking into the camera problems. There are also camera issues on the Mini and Gio, so this is probably the same problem.
Are the hardware keys now working properly?
psyke83 said:
Thanks, I'll keep looking into the camera problems. There are also camera issues on the Mini and Gio, so this is probably the same problem.
Are the hardware keys now working properly?
Click to expand...
Click to collapse
i didn't test the all of the hardware keys but the home and menu button now working properly
i forget to test it all
but i read at the facebook group, the previous build at jenkins has a microphone bug.
after 30sec of phonecall the mic turn off
i didn't know if the bug is persist in your build
i'm gonna test it when i'm have some spare time
Edit :
almost all the hardware key working
but the alt,shift,and enter button not working
and the ? button became '
here i include you the stock gingerbread keylayout and ankur cm10.1 keylayout
Download
and i already test the microphone for call about 1 minute and the microphone is working perfectly :good:
I want to test this also but i cannot find the DL link. Will wait for the next build.
Thanks for the dev.
marniel647 said:
I want to test this also but i cannot find the DL link. Will wait for the next build.
Thanks for the dev.
Click to expand...
Click to collapse
http://jenkins.androidarmv6.org/job/android-experimental/627/
I tested it with that boot.img via odin and on first boot proximuty incall was working but bluetooth doesnt work, after reboot proximity dont work but bluetooth now work
EDIT
attached logcat
EDIT2
after attaching logcat proximity start working but sometimes wont work
Wytapatano z Galaxy Nexus CM 11
Related
STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
Flash with the following adb commands:
Code:
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img
If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
Mirror 1: Download (Goo.im)
BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.
STEP 2: DOWNLOAD A BUILD OF CM11.0:
DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM
NIGHTLIES:
http://download.cyanogenmod.org/?device=otter
GAPPS (Use Version "CM 11" row):
http://wiki.cyanogenmod.org/w/Gapps
Older builds are found here:
http://goo.im/devs/Hashcode/otter/cm10/
http://goo.im/devs/Hashcode/otter/cm10.1/
http://goo.im/devs/Hashcode/otter/cm10.2/
GAPPS (For Android 4.3/CM10.2 builds):
http://goo.im/gapps/gapps-jb-20130813-signed.zip
CHANGES:
[05/15] More audio updates to fix low-power states (screen off / background music)
[11/25] Released updated build for cm11.0
[08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
[07/30] Updated to CM10.2 build
[05/26] Backlight driver update to help w/ SODs
[05/24] Sensor updates (includes light sensor now usable in Android OS
[05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix
CURRENT KNOWN ISSUES:
The headphone MIC input is not functioning correctly yet. Work in progress.
KERNEL FEATURES:
[08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
[01/06] WLAN Firmware R5.SP3.06
[11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom)
[11/07] WLAN Firmware R5.SP3.03
[09/05] Updated to SGX/IMG DDK [email protected] for Android
Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
Many bugfixes pulled down from TI's omapzoom sources.
RESERVED FOR NOTES
XDA:DevDB Information
Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-01
Last Updated 2014-05-21
UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1
DEVELOPER BUILDING:
Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
Patch 1: http://review.cyanogenmod.org/#/c/53917/
Patch 2: http://review.cyanogenmod.org/#/c/54562/
And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
Won't get a decent build till that's all done.
KNOWN BUGS:
1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
6. Headset recording via the MIC input jack doesn't work
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 10.2)
repo init -u https://github.com/CyanogenMod/android -b cm-10.2
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter
FINALLY!
I'll see if I can help with power button LEDs.
*out-of-topic note: 3rd post!
1. The backlight doesn't sync up well with the screen. Meaning that sometimes when you bootup you won't see anything but a black screen. Once the boot is done, you can hit the power button a few times and eventually the screen and backlight will sync up and you'll get a picture.
Click to expand...
Click to collapse
I can't even get a picture.
animefun135 said:
I can't even get a picture.
Click to expand...
Click to collapse
Power button four or five times, and it'll pop up.
Edit: not having the sync issue in HC, hash, do you have the log posted on your site regarding the back light issue? I know its kernel related but 3.2 is a lil more cumbersome, so it could just be OS lag. Are we using 4.0.3 or 4.0.4?
Sent from my MB860 using XDA
Power button four or five times, and it'll pop up.
Click to expand...
Click to collapse
I tried 30+ times.
Nice job Hashcode.
Sent from my PG86100 using Tapatalk
I don't have time at the moment to pull down the sources and poke around for myself, but it sounds like #4 is a script issue of some sort.
Either one of the scripts that needs to fire for shutdown is hanging up, or the output isn't returning properly so that the master script can continue and finish pulling it all down.
If I get a chance tonight, I'll grab the sources and poke around a bit.
I deal with hanging/incorrectly-terminating script **** at work all the time, so now I might even be able to contribute, yay!
Reserving this for a complete description of the backlight driver/issue and related sources for research.
Sent from my DROID4 using XDA
Hey Hash I wanted to let you know that the charger does work for me. I don't have to boot back into twrp. Don't know if its just me or what but it works.
Edit: Didn't see that you had put its not working well instead off not at all, I'll do some more testing to see if it will give me problems. So far plugged it in about 20 times and its registering the charge.
Sent from my Amazon Kindle Fire using XDA
Let me be the first to say "Does Netflix work with this?"
Just kidding, things are coming along it appears, wish I knew more about hacking kernels, last time I did anything with a kernel I ran "make xconfig"
i just get a lit up black screen 0.0??
symbiiote said:
i just get a lit up black screen 0.0??
Click to expand...
Click to collapse
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
isaiahhhhh said:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
Wait, are you talking about things like large grey rows of pixels appearing on the screen? Sometimes I see gradients of monochromatic tones in addition to this. They only appear as the backlight is shutting off.
isaiahhhhh said:
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
your right, sorry, as for the rom, i noticed when i flashed hashcode's rom then reloaded rom over it youtube worked in HD, and that got me thinking, you think we can get a Flashable ZIP of the kernel?
is this the kernel that everyone was waiting for? 3.0?
@shahabk818
YES!
But it's still in development, so not for daily use!
TuikS2 said:
@shahabk818
YES!
But it's still in development, so not for daily use!
Click to expand...
Click to collapse
so this will fix the hardware acceleration problem, right?
shahabk818 said:
so this will fix the hardware acceleration problem, right?
Click to expand...
Click to collapse
So you can't read the title, right? [WIP][KERNEL][DEV-ONLY] 3.0 Kernel Development for Kindle Fire [04-10]
DEV ONLY!
OK, so compiled an aosp last night from the CM9 tree... I'm still not having a back light issue? Can't adjust brightness, but no sync issues. Could it be the ROM?
Sent from my MB860 using XDA
About OmniROM
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Click to expand...
Click to collapse
Info from omnirom http://omnirom.org/general/android-l-omnirom-progressing/
Disclaimer
Standard disclaimer applies, your warranty is void, this may eat your dog or burn your house down, delete all your pictures, etc.
This is an early stage release so many things are broken since many patches and fixes haven't been imported from old branches yet.
How to install:
Reboot to recovey
A backup is Recommended, you're gonna loose all your data
Wipe data
Flash rom
Flash SuperSU 2.19 2.40 or up just after the rom
http://download.chainfire.eu/supersu -> This is IMPORTANT
Flash Netflix fix if you need it -> Download
Reboot
Around 5 minutes are required for the first boot
Reboot again to recovery
Flash Gapps (See below)
How to update from a previous version:
Reboot to recovey
Flash rom
Flash SuperSU 2.40 or up just after the rom http://download.chainfire.eu/supersu -> This is IMPORTANT (not needed anymore)
Flash Netflix fix if you need it -> Download
Reboot
Gapps download:
Check http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693
How to report a bug
Use the search function, if the bug has already been reported and I or another person has answered do NOT report it again. I'm tired of writing ten times the same thing.
A bug report function is embedded in XDA forum look at the top there's a section called "Bug Reports". Use it
Provide a logcat and/or dmesg. Search on XDA if you don't know how to get a proper log
Always provide which model you are using and other information that you think could be useful to solve the bug
Downloads:
This is an early preview with lots of bugs and not usable as a daily driver. You have been warned. Flash this only if you are sure about what are you doing.
Download folder: https://www.androidfilehost.com/?w=files&flid=21696
Starting from 20150506 I'm uploading automated builds: this means that they should be treated as nigthlies (I won't create a new one every 24 hours though). All the new files will be placed in the "Download folder" automatically, so, if no new changes from my part, I will NOT update the changelog. These builds will include all the updates and commits from official Omnirom repos plus my commits not yet merged for our tablets. Good luck
Commits: -> Updated to 5.1.1_r2
Necessary commits
In frameworks_native: https://gerrit.omnirom.org/#/c/13068/ and https://gerrit.omnirom.org/#/c/13069/
In frameworks_av: https://gerrit.omnirom.org/#/c/12528/, https://gerrit.omnirom.org/#/c/12529/ and https://gerrit.omnirom.org/#/c/12530/ (in this order)
In kernel_samsung_smdk4412: https://gerrit.omnirom.org/#/c/12223/ (SELINUX to permissive) , https://gerrit.omnirom.org/#/c/13055/ (Kernel compression)
Optional commits:
Enable Stylus pointer toggle: https://gerrit.omnirom.org/#/c/13606/, https://gerrit.omnirom.org/#/c/13650/, https://gerrit.omnirom.org/#/c/13651/
And finally, if you want to test and/or help:
Netflix experimental codecs fix: https://gerrit.omnirom.org/#/c/13716/
Other commits not made by me:
Nothing here as of now
If you wish to have a kernel with overclock and other features, you can find the kernel sources for my custom kernel "mm_alpha" at https://github.com/marco9333/android_kernel_samsung_smdk4412 . See branch mm_alpha_lollipop for the working and updated version working with this rom (and other lollipop roms). I can share a compiled version, PM me if interested
Screenshots -> Click here
Donations:
Many thanks to Heide Ruehle and @Rand_
Thanks to:
Omnirom core devs
@iofthestorm(ported omnirom 4.4 and made it official for our devices)
@humberos (various patches and asked for an official new android-5.0 branch)
@lirokoa (for his advices on wifi and camera hal)
I forgot someone ???
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note 10.1
Contributors
marco9333
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-23
Last Updated 2016-11-13
Status of things:
Broken:
Charging off mode isn't working
Using torch tile causes a forced reboot, use torch app instead
Wi-fi tethering isn't working
Screen recording causes an hard reboot (Now it just does nothing or System UI crashes and restart)
I haven't tested other things yet....
Report if you found something new to add here
Notes:
Using a proxy in APN settings doesn't work. Thanks to @farinjini for pointing this out -> I don't know if this is working now or not
Changelog:
Older versions changelog
20141123
Initial release
20141125
Fixed stylus (S-PEN input)
Fixed graphical glitches in screenshots and while rotating screen Thanks to @lirokoa
Upstream changes -> updated to android release LRX21V and other "under the hood" changes
20141126 for N801x
Solved bootloop problem, I hope (not booting kernel)
20141130 for N8000
Partially working RIL (this has been really hard )
20141204-05
Upstream changes -> updated to android 5.0.1 LRX22C
Gps fixed. Thanks to @humberos
Added Performance control and Advanced in settings as in omnirom 4.4.4 (thanks to omnirom core devs)
Mobile partially fixed (need to run a script to make it completely work) (only N8000)
20141207 for N8000
Mobile data completely fixed
20141218
Upstream changes
Added advanced reboot (normal reboot, reboot to recovery and reboot to bootloader)
Fixed the problem with keyboard (need to disable physical keyboard from settings)
Fixed forced reboots caused by Youtube and G+
Minor fixes about technical things
20150108
Switched to android 5.0.2_r1 LRX22G
Upstream changes
Random reboots should be fixed -> see https://gerrit.omnirom.org/#/c/11024/ and https://gerrit.omnirom.org/#/c/10997/
20150206
Upstream changes -> See https://gerrit.omnirom.org/
Lots of code cleaning -> Better stability (I hope)
20150326/27
Switched to android 5.1 LMY47D
Upstream changes
20150401
Upstream changes
Switched to android 5.1_r3 LMY47I
Youtube, G+, firefox, etc. reboot fixed (experimental fix please report if problems)
20150407
Upstream changes
Netflix fix (experimental.. please report)
Properly "keyboard not showing" fix
20150506
Upstream changes
Android 5.1.1 LMY47V
New DRM vendor libs (Report if they "work miracles" with netflix)
20150510
Upstream changes
Pointer disabled by default when using S-Pen (Can be re-enabled in Settings see screenshot at #372)
Reintroduced keyboard fix (sorry about that)
20150519
Upstream changes
Android 5.1.1_r2 LMY47X
Netflix codec fix -> See https://gerrit.omnirom.org/#/c/13716/
20150628
Upstream changes
Android 5.1.1_r5 LYZ28E
20150928 or 20150927
Upstream changes
Android LYZ28J
Stagefright fixes
20151104
Upstream changes
Video playing fixed (Sorry guys and girls )
Chrome is now working
You need to enable the showing of keyboard after first boot: go to settings, language and input, current keyboard and enable Hardware(Show input method)
20161110
Untested build
Upstream changes
Android LYZ28N
Reserved
Workarounds and advices
Smoothness: Go to settings, about tablet and press repentantly Build_number until it gives you that you're now a developer, Go back, press on Developer options, scroll down and set Window animation scale, Transition scale and Animator scale to .5x
Toggle stylus (S-pen) arrow pointer:
Go to Settings, Language & input, put a tick or not on "show icon when using stylus" option
marco9333 said:
Status of things:
Working:
Boot
Bluetooth (switching on and scanning)
Rotation
Suspend/Resume (need to keep wifi on though)
Audio
Root (flashing SuperSU from recovery)
Gapps install and start (I've tried CM Gapps but login in is impossible)
Vibration
Hd videoplayback (tested youtube)
I forgot something ???
Partially working:
Screen -> Rotation causes graphics glitches
Video playbackaudio is working, decoders too but black video
Wifi (something wrong with this module, suspending the device with wifi off causes an hot reboot)
Broken:
RIL (phone calls, 3g and so on) for n8000 -> I'll try lirokoa advice -> need to import samsungRIL from android-4.4 tree
Camera (videos) -> Imported opensource camera hal -> taking pictures is fine but video are completely broken
Gps ->I 've waited enough and no position found -> some error regarding this in the logcat
I haven't tested other things yet....
Click to expand...
Click to collapse
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
lirokoa said:
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
Click to expand...
Click to collapse
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
marco9333 said:
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
Click to expand...
Click to collapse
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
LastStandingDroid said:
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
Click to expand...
Click to collapse
It's working I've just tested with a 720p video
marco9333 said:
It's working I've just tested with a 720p video
Click to expand...
Click to collapse
i'll see if it'll work for me i've never got it working with any build
LastStandingDroid said:
i'll see if it'll work for me i've never got it working with any build
Click to expand...
Click to collapse
I'm in the same boat as you, stuck with the leaked N8000 bootloader on my N8010, and youtube works great for me on last CM 11 build.
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
TheMorpheus said:
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Click to expand...
Click to collapse
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
mysarasaid said:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
Click to expand...
Click to collapse
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
marco9333 said:
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
Click to expand...
Click to collapse
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
lirokoa said:
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
Click to expand...
Click to collapse
I'll give it a try because when I tried to merge RIL from omnirom 4.4 I've got an enormous amount of conflicts. Thanks maybe them will speed up the fix
Sent from my Nexus 5 using XDA Free mobile app
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
marco9333 said:
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
Click to expand...
Click to collapse
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
lirokoa said:
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
LastStandingDroid said:
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
Click to expand...
Click to collapse
I've written quite big in the third post that you need to flash supersu beta just after the rom or you won't be able to boot into recovery: you've been warned. I'm working on merging the fixes for graphics issues.
By the way I've fixed the stylus input which is working ok now. New version soon....
New version 20141125 out
I've just uploaded a new build. See OP for download links and second post for changelog. Before signaling a bug or something that isn't working, please read the third post, too.
Another bug I've found is in charging off script, please recharge your tablet while on until next release
On my n8013, every time I flash the ROM, then gapps, then superSU, I get a boot loop, never makes it to Omni logo. I tried to redownload all files from the OP, and still no luck. Tried 4 times now
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOTE:
THIS IS A DEVELOPMENT THREAD.
BUILDS ARE INTENDED FOR ADVANCED USERS, SO THEY CAN TEST AND GIVE FEEDBACK.
FEATURE REQUESTS WILL BE IGNORED, THIS IS PLAIN CYANOGENMOD.
Also, there are sister threads for working on pollux, yuga and dogo.
Changes:
- Jan 30: Initial release
- Feb 5: kernel updates, audio HAL modernization
- Feb 9: WiFi updates
- Feb 13: volume rocker wakeup, sdcard hotplug, camera focus changes, cleanups
- Feb 16: new call fix
- Feb 27: F2FS support
- Mar 1: audio update
- Mar 3: smooth boot animation
- Mar 6: more audio updates
- Apr 3: first 12.1 build
- Apr 20: radio fixed
- Apr 22: Android 5.1.1
- Apr 27: tons of cpu and gpu governor updates/fixes, wifi updates
- May 1: gpu gov and wifi updates
- May 7: app2sd fixes, selinux updates, fixed power hal, OSS THERMAL MGMT, wifi fixes
- May 10: plethora of core kernel and platform updates, init changes
- May 22: scheduler and platform updates, reworked kernel configuration
- July 7: lollipop blobs, init update, new sensor drivers, kernel updates
- July 11: fix booting into recovery by toggling volume keys, fixed wlan&bt mac config, fixed off charging mode
- July 20: fixed gps problems under certain circumstances
- July 30: lp kernel updates, als adjustments, led color configuration from ui, gps problems fixed, leds in offline charging mode
- Aug 6: row io scheduler, open source gps hal, fix sd card access and thermal config, update sepolicy and power profile
- Aug 20: minor init updates, thermanager config
- Aug 26: backlight fix, thermanager updates
- Sep 10: io schedulers: include fiops, bfq - use it as default
- Sep 17: sony 5.1 blobs, init changes, performance management in recovery
- May 9: initial CM13 release
- Jul 5: loads of kernel changes, audio hal, and probably plenty of stuff i forgot
All builds are synchronized with the latest CM tree. For the specific updates to fusion3 and yuga, see the source link below!
Download:
For the brave CM13 DEVELOPMENT BUILD:
cm-13.0-20160707-UNOFFICIAL-odin.zip
Dirty-flashing on existing 12.1 upgrades normally to CM 13. Beware you will need compatible GApps though!
Nightlies are now available:
Official download site
This thread will however remain the prime location for testing new stuff and support on yuga.
Installation:
If you have anything other than CyanogenMod 12.1 on your device, do a full wipe, and get Android 5.1 compatible gapps!
F2FS support: take a look here
Testing:
Some very important "rules" for this:
- Run unmodified versions (no FOTA recovery, no modified kernel, no Xposed framework, etc.)
- Please dont post "X isnt working" or "random reboots" - provide LOGS for each report you post here. This thread is actually meant for users who are capable of gathering and providing logs, so after a reboot, provide last_kmsg, and for all other problems, dmesg and logcat at the very least.
- If you can reproduce your problem, you might want to increase the logging level before posting it here, which will increase chances of me finding the problem.
I will have to ignore all other "problem reports" as they are essentially useless.
Source:
If you are willing (and able) to help, check out the patch sets, test them for the respective projects (fusion3 is also pollux, odin, and so on).
http://review.cyanogenmod.org
W o W
Hi, Qsnc.....
permission to try your build...
thanks to develop Lollipop for our great ZL :good:
Hi,
whats the Different to the other CM12.1 Thread?
My Problem is, that in all Android5.x.x Versions for Odin, Soundhound is not working, and in Whatsapp call the other hears me very bad, or only a cracking.
I believe, that this is the same issue.
shufuking he has been building cm for odin for a while now why switch? Im curious why you too are building cm for odin now?
i am the device maintainer for fusion3 devices these days. so why use this? because i don't just build from sources, i contribute to them. this thread is meant to help me find errors BEFORE i merge changes into the official cm source tree. and to get feedback and logs on builds i provided - i do not attempt to fix bugs on untrusted builds.
so in short: feel free to use "daily builds" from other sources. if it turns out that i do not get feedback on these builds, i'll just leave these devices behind, and focus on pollux and yuga instead.
qsnc said:
i am the device maintainer for fusion3 devices these days. so why use this? because i don't just build from sources, i contribute to them. this thread is meant to help me find errors BEFORE i merge changes into the official cm source tree. and to get feedback and logs on builds i provided - i do not attempt to fix bugs on untrusted builds.
so in short: feel free to use "daily builds" from other sources. if it turns out that i do not get feedback on these builds, i'll just leave these devices behind, and focus on pollux and yuga instead.
Click to expand...
Click to collapse
Thank you for trying to maintain Odin, qsnc. Question: Isn't Yuga essentially the same as Odin internally? Which means if you decide to continue Yuga, you might as well support Odin.
Baron1971 said:
Hi,
whats the Different to the other CM12.1 Thread?
My Problem is, that in all Android5.x.x Versions for Odin, Soundhound is not working, and in Whatsapp call the other hears me very bad, or only a cracking.
I believe, that this is the same issue.
Click to expand...
Click to collapse
Ok, i quote myself....
Can you do something about the cracking, and the not working Soundhound? What logs you need?
thanks for this. will give feedback soon
Want to install this and give it a full workout, but does it have a working CWM recovery ? Last time I tried ( with an FXP build ) it didn't, and had to flash a TWRP one or I'd have had no working recovery on the device.
Thanks for this ROM. Great Rom!
Baron1971 said:
Ok, i quote myself....
Can you do something about the cracking, and the not working Soundhound? What logs you need?
Click to expand...
Click to collapse
these problems only happen in those apps? are they reproducible? do others have the same problem(s)?
Ultramanoid said:
Want to install this and give it a full workout, but does it have a working CWM recovery ? Last time I tried ( with an FXP build ) it didn't, and had to flash a TWRP one or I'd have had no working recovery on the device.
Click to expand...
Click to collapse
you tell me, thats what this thread is for.
qsnc said:
these problems only happen in those apps? are they reproducible? do others have the same problem(s)?
you tell me, thats what this thread is for.
Click to expand...
Click to collapse
For me, it is reproducible! I have these Problems, since i use Lolipop, and i read here, that other People here have the same Problems,
Gapps doesn t works...
cmndst said:
Gapps doesn t works...
Click to expand...
Click to collapse
yo are you clueless? what is anyone supposed to do with this post, how could they possible help you... please read more topics on this forum before posting again thanks!! search how to get good logs or something man geshhh!
Ultramanoid said:
Want to install this and give it a full workout, but does it have a working CWM recovery ? Last time I tried ( with an FXP build ) it didn't, and had to flash a TWRP one or I'd have had no working recovery on the device.
Click to expand...
Click to collapse
It has working CyanogenmodRecovery (not CWM), but is only accesible over advanced reboot options activated in developer Settings and not through key Combinations.
Whatsappcalls and Soundhound are working flawless for me, like everything else withs this rom. :good:
qsnc said:
you tell me, thats what this thread is for.
Click to expand...
Click to collapse
sonar21 said:
It has working CyanogenmodRecovery (not CWM), but is only accesible over advanced reboot options activated in developer Settings and not through key Combinations.
Click to expand...
Click to collapse
Thanks.
I wouldn't say it is a working recovery; can't make backups, can't install GApps ( chokes on signature... ), etc. So one is forced to try to stick TWRP in FOTAKernel. I'm not sure what the purpose of CM's recovery in its current state is.
Edit : Managed to flash GApps but still, really spartan recovery with almost no options, I'd definitely warn users about this.
Edit 2 : With TWRP recovery in FOTAKernel I've been using the ROM as daily driver on this device; no difference or remarkable bug in what I use compared to newer devices I already had on 12.1. Of course it's an older build and lacks features from more recent nightlies, but seems pretty solid so far. Thanks for making this available.
new build available. been off on holidays for a while, and working on pollux and yuga.
what is the status quo of this release?
qsnc said:
new build available. been off on holidays for a while, and working on pollux and yuga.
what is the status quo of this release?
Click to expand...
Click to collapse
Dirty flashed an FXP build over your last one, now dirty flashed this build over FXP's and all's well. In fact these unofficial builds for the ZL work better than the official ones for the Z2, I have to say. Can't find a bug in anything I use on this device.
Ultramanoid said:
Dirty flashed an FXP build over your last one, now dirty flashed this build over FXP's and all's well. In fact these unofficial builds for the ZL work better than the official ones for the Z2, I have to say. Can't find a bug in anything I use on this device.
Click to expand...
Click to collapse
+1
Ultramanoid said:
Dirty flashed an FXP build over your last one, now dirty flashed this build over FXP's and all's well. In fact these unofficial builds for the ZL work better than the official ones for the Z2, I have to say. Can't find a bug in anything I use on this device.
Click to expand...
Click to collapse
Sorry if I'm missing something, but where is the FXP CM12.1 for ZL?
CyanogenMod is discontinued.
This ROM is continued as a LineageOS ROM.
Check the G800F LineageOS ROM for more info.
This is a CyanogenMod 13.0 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y) by CTXz and hennymcc.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Internal Root
Brightness slider
Option to use soft keys
Additional settings (Buttons menu in settings)
HW accelerated GUI
Camera (pictures+video: Back+Front)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Lock Screen
Sound
SMS
Initiate and receive calls
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Multi-Window support (new experimental CM setting, can be enabled via developer settings)
Fingerprint scanner
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
The newest CM 13.0 releases as well as the latest TWRP can be found here:
https://aykevl.nl/android
-Credit and thanks to @ayke
CM 13.0 ROM for G800F/M/Y (Android File Host)
Google Apps (contains Google Play, ...) for Android 6.0, one of the following two is recommended:
Open GApps Project, Platform:ARM, Android:6.0, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 13.0.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 13.0 ROM zip-package
Install the GApps zip-package
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
25/03/2016:
* USB OTG disabled by default for improved waterproofness (can be re-actived via Advanced Settings App)
* how to enable USB OTG:
* start the "Advanced Settings" App
* open the "USB-OTG Mode" setting
* select "Powered (Not waterproof)"
* add support for call recording
* how to record a call:
* start/Receive a call with the CM Dialer App
* During call open settings (icon: three vertical dots)
* Select "record call"
* (if you get an error message that recording failed, try to enable developer settings and enable root access for apps+adb)
* how to playback recorded call:
* open the call history in the Dialer app (icon: clock symbol)
* open details of recorded call
* in the detailed calling list, click on the play button for the recorded call
* removing fingerprints works now
* updated some stock libs with LP versions
* support for F2FS (needs new TWRP recovery)
* updated TWRP recovery (with F2FS support)
* synch with latest CM sources
22/02/2016:
* Fixed lock-screen freeze
* Fixed Infrared support
* Fixed search for mobile networks (search will take ~1min until results are shown)
* Updated some libs with LP versions
* Initial support for a fingerprint scanner
* Sync with CM sources
16/02/2016:
* Fixed camera problems with WhatsApp
* Fixed preferred radio family settings (LTE/GSM/...)
* Added default long-press actions for home and app-switch buttons (DJSteve)
* Switched to LP kernel (G800FXXU1BOL4)
* libsensors: replaced with open source implementation (fixes light sensor which is needed for auto-brightness)
* Preliminary (and very inaccurate) support for heart-rate sensor
* Update to TWRP 3.0 (TWRP 2.x will still work)
* Sync with CM sources
30/01/2016:
* Fixed BT calling problems (only noise)
* CM Camera replaced with CM Snap Camera
* better image quality (check picture quality settings), resulting in image file sizes of > 1MB instead of 200KB
* Saving images to SD card supported (check settings)
* Improved RIL support
* Use stock soft-key layout (left capacitive button is app-switch instead of menu now)
* Key-layout can be configured via button settings.
* Fixed adb root problem (root permissions were lost after reboot)
* SamsungServiceMode app works now
* Sync with CM sources
14/01/2016:
* Add soft keys option under settings > buttons
* Fix crash after hanging up call
* Sync with newest CM sources
31/12/2015:
* Receiving calls works now
* psyafter: SD-Card can be used as internal storage (new Android M feature).
Can be used to store photos on SD-Card.
IMPORTANT: the SD-Card will be formatted if you activate this feature.
* GPS works now
* Sensors work now (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter).
Light and Pulse sensors do not work yet.
* Youtube/Screencast crash fixed
26/12/2015:
* Wifi and Mobile Data work
20/12/2015 Hennymcc :
* Audio Fix
- Audio is now working (Still a bit quiet though)
- Making Calls is now working
14/12/2015 Hennymcc, CTXz :
* 6.0.1
- Updated to Android 6.0.1
- Fixed reboot when locking phone
- Fixed Internal Root in developer options not working
30/10/2015 CTXz :
* Added 'Buttons' settings
- Integrated Buttons/Capacitive Keys menu into settings
- Double tapping or holding button to open camera now works (In CM12 it didn't work)
- Power Menu is added under buttons menu
- Minor fixes
-!- NOTE : Setup Wizard may have some issues/crashes with this build. I will exclude it in the next one
29/10/2015 CTXz :
* Synced to newest sources
- Ugly looking Google search box removed
28/10/2015 CTXz :
* Changed from eng to userdebug
- No more red frames flashing
- Fixed Browser crashing
- Fixed crash after first boot
- More user friendly
- No additional boot.img flashing required
28/10/2015 hennymcc:
* First CM 13.0 test-build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz for his awesome work on getting Marshmallow to the G800F
Thanks to spookcity138 and ayke for providing new builds of this ROM.
Thanks to Psyafter for some patches and working on the G800F.
Thanks to Unjustified Dev from Team Regular for the initial work to get the G800F ready with CM.
XDA:DevDB Information
[G800F/M/Y][ROM][6.0][MHC19J] CyanogenMod 13.0 for G800F/M/Y [Beta 25/03/2016] [eol], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, CTXz, spookcity138, psyafter, Unjustified Dev, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-10-28
Last Updated 2017-01-26
If you already flashed stock LP, you will get the following message on boot:
KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
If you wait for some seconds (or press some buttons) the message text turns blue:
KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
and after some seconds (or buttons presses) CM will start.
Reserved
You (both of you) are making a great job !
Envoyé de mon SM-G800F en utilisant Tapatalk
$wap said:
You (both of you) are making a great job !
Envoyé de mon SM-G800F en utilisant Tapatalk
Click to expand...
Click to collapse
Ditto!
Sent from my SM-G800F using XDA Premium HD app
I don't see the point in cm13 when we didn't even get official Lollipop required to make cm12 better, "legit". Can someone enlighten me...?
Is it supposed to have the same bugs as cm12 or will there be more of them? Is Marshmallow statistically faster than Lollipop on other phones?
hennymcc said:
This is just a test build.
At the moment you have to flash the following boot.img with Odin after installing CM 13:
https://www.androidfilehost.com/?fid=24052804347848059
CM 13 may reboot after the initial configuration and may not be able to start again. I wiped the data partition and started again. This time it worked without a reboot (I also choose English as language and did not configure Wifi).
Click to expand...
Click to collapse
Updated the link with the boot.img build in
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
n3n00 said:
I don't see the point in cm13 when we didn't even get official Lollipop required to make cm12 better, "legit". Can someone enlighten me...?
Is it supposed to have the same bugs as cm12 or will there be more of them? Is Marshmallow statistically faster than Lollipop on other phones?
Click to expand...
Click to collapse
CM13 is for people that enjoy its minor speed boost, smoother animations, cool new features and less Android related bugs over Lollipop. If you want a, well... almost bugless experience (Cough cough touchwiz) then use the stock rom.
CTXz said:
Updated the link with the boot.img build in
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
CM13 is for people that enjoy its speed and less internal bugs. If you want a, well... almost bugless experience (Cough cough touchwiz) then use the stock rom.
Click to expand...
Click to collapse
Hi, so you think it will be easier to make a CM13 version with less bugs than the unfinished CM12 (Yes / No) ?
I enjoy to use a rom for every day not just having the last version to amaze my friends...
Depends. What I know for sure is that bugs related to Lollipop will be fixed. However we are hoping to get it as stable as cm12 if not more
Screehots
Screenshots with phone frame
Screenshots within Android
What‘s the current status of the mobile-data-connection in this build? Is it working?
In the first build of CM12.1 is was not working.
My experience was that this feature was always a problem in the beginning-time of every CM-build. Even with the official CM-builds.
WarStars said:
What‘s the current status of the mobile-data-connection in this build? Is it working?
In the first build of CM12.1 is was not working.
My experience was that this feature was always a problem in the beginning-time of every CM-build. Even with the official CM-builds.
Click to expand...
Click to collapse
We didn't build the correct RIL yet but it should be working in hopefully only few builds
New update
Download link has been updated
Changed from eng to userdebug
- No more red frames flashing
- Fixed Browser crashing
- Fixed crash after first boot
- More user friendly
- No additional boot.img flashing required
Also for anyone asking if there are really some differences in Marshmallow compared to Lollipop. Yes, the animations are allot smoother. There are some new native features. It has cleaned the mess of Lollipop's Android related bugs and is what Lollipop should have been from begin on. It is snappier than Lollipop and I can see/feel that. You may have realized that gingerbread-ish google toolbar. This is CM13 related since the official CyanogenMod 13 source is still in beta. However we no longer have the problem that the toolbar is laggy, instead it has a smooth animation when selecting it.
Could you please give some information when the RIL is done? Thank you in advance.
WarStars said:
Could you please give some information when the RIL is done? Thank you in advance.
Click to expand...
Click to collapse
It's on our priority list so hopefully soon
You know I have both the G800H and the G800F (the camera bug on the G800H prompted me to get the G800F), and now I don't know which one I should get rid of... I know, I know: "hard problem there KC... ya bloody wanker"
CTXz said:
It's on our priority list so hopefully soon
Click to expand...
Click to collapse
Awesome job so far, guys!
Sent from my SM-G800F using XDA Premium HD app
New update
Download link has been updated
Synced to the newest CM13 sources
- Ugly looking Google search box removed
CTXz said:
New update
Download link has been updated
Synced to the newest CM13 sources
- Ugly looking Google search box removed
Click to expand...
Click to collapse
Working features from page 1 still the same for this new build?
Sent from my SM-G800F using XDA Premium HD app
Mobile connections working now?
This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.
Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384
Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.
Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)
Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785
Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming
Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card
Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now
Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano
Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).
Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key
Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now
Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.
Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911
Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Reserved - why do all people do this?
chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.2 - but most likely not all.
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!
Just flashed it and it works! Thank you so much! (although instructions how to create such a rom would be nice for me )
EDIT: some answers to your question:
I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store
Missing security patches: Stagefright CVE-2015-6602 is not fixed.
Thank you very much!
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://forum.xda-developers.com/showthread.php?t=2615613
So in this case:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code:
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?
aaaand
Sound and bluetooth seem to work fine, didn't test more so far.
Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today.
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
fredflegel said:
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse
You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
ccxxx said:
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
Click to expand...
Click to collapse
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
chrmhoffmann said:
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
Click to expand...
Click to collapse
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
ccxxx said:
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
Click to expand...
Click to collapse
You should then upgrade. It's much nicer with a single partition... And as you can see, I don't support the old storage layout any more
Chris
Upgrade to 4.4.4. available
See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.
Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.
Chris
It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.
After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92
edit: And so does the 4.4.2 image that has worked before.
*sigh*
edit 2: Formatted a few partitions and tried again - now 4.4.4 works.
0.2 released.
It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).
It should also make less CTS tests fails.
Still uploading... Edit: Uploaded.
Chris
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
jogri said:
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
Click to expand...
Click to collapse
Yes, the last security patches break xposed. https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
See e.g. here: https://plus.google.com/114407246718577124209/posts/BwiPxSu84bD
Chris
z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse
This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).
Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases
Chris
Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)