News

Slim6

I found some time to update Slim6. Applied all updates for 2017-06-01 security patch level. The Update will be available for following devices:

• Galaxy Tab2
• Galaxy Nexus
• Oneplus One

SlimKat

SlimKat updates for 2017-06-01 security patch level. The Update will be available for following devices:

• Galaxy Tab2

Source can be found here in case you wan’t to compile yourself.

Slim6

New Slim6 builds are up for Galaxy Nexus, Galaxy Tab2 Family (reuploaded with portrait camera fix) and Oneplus One. Android security patch level 2017-05-01.

General

After 6 Weeks i got my LG G4 back again… now waiting for the bootloop again (i am sure it will happen a 3rd time)… on vacation i never felt that bad using a phone like this time, running a backup of my photos every evening because i don’t feel secure using that phone…

I pushed some new AnyKernel for Galaxy Nexus and Tab2 Family which fix/workaround an security issue of LineageOS SU binary, besides that i am still not back to development.

Slim7

New Slim7 builds are up for Galaxy Nexus, had to test if latest translations compile fine - no device specific changes, only latest Slim7 Source + Translations.

LineageOS 13

Flashing official LineageOS 13 addonsu causes error4 in recovery. It’s a known issue, but LineageOS hasn’t updated the addonsu yet. Selfcompiled addonsu was added to Tab2 LineageOS page.

Hey together!

Some of you might know already about the problems i currently have with my LG G4. My LG G4 was my daylie driver and i really need it because i am doing most stuff on my Phone.

Just as an information for you, why i am not having much time for android at the moment - i am wasting time:

• 01.02.2017: bootloop, lost all my data. I contaced LG and they repaired it in about 1 Week.
• 01.04.2017: again bootloop, lost all my data again. I contaced LG how it can be the issue appears again. They told me they are sorry and i should talk to the shop where i bought the device in hope they replace it or refound me. I went to the shop and the owner told me that he needs to talk to LG again, he’ll call me. 3 days later, no one called me back, i asked again how we can solve the problem. The shop owner told me LG said they need to send it to a repair center again.
• 04.04.2017: shop takes the phone and send it to the repair center. I told him i need it back in 2 Weeks. He said i can’t tell him a time he has to repair it - i am by law (§ 439 BGB), but i don’t have too (i would be stupid if i don’t). He don’t like to accept it, i had to send him an email once i am home saying the same again i told him already in the shop.
• 18.04.2017 & 22.04.2017: asking the shop again - still in the repair center.
• 26.04.2017: i visited the shop again - it is still in the repair center! (WTF?!) He’ll contact LG and call me back - he never did.
• 29.04.2017 & 02.05.2017: Asking about the status via email or if we can find a different solution (different phone?) - until today no answer.
• 03.05.2017: I send him a letter saying he has to repair it until today (10. May), else he should give back the money.
• 06.05.2017: You guys know, i am a friendly guy, i called him again asking if he’s interested in finding a solution both of us can live with. I left a bad review on Facebook and on Google for his shop, he said he don’t like to talk to me because of that.. i told him i’ll update it if we find a proper solution. We talked a littlebit about what went wrong etc. and he finally decided to talk to LG and the repaircenter again. He’ll call me back on Monady (8. May).
• 08.05.2017: The shop called me (i never thought he did, but he did), the repair center is waiting for new mainboards and he asked me if i can give him some more time… i am a friendly guy, i said ok because i really liked the phone and would love to get it back.
• In the meantime i talked to LG many times, they said they can’t do anything, my G4 wasn’t send to the LG repair center it must be in a different repair center (WTF?!).
• 09.05.2017: I asked LG again if they can try to speed things up in the repair center, my G4 is there for almost 5 Weeks now. They said they need to know the repair center.
• 10.05.2017: i visit the shop again, asking for the repair center. He don’t like to tell the repair center…

Looks like i have to wait for my G4 a little longer but i can’t…. i need a good phone as my dd and really need a good smartphone camera because i use it often…

All my work on android is discontinued until my G4 is back or until i bought a new phone.

UPDATE 01 May 2017

Reuploaded all Slim6 & SlimKat builds to fix CVE-2016-10244.

Slim6

I found some time to update Slim6. Applied all updates for 2017-04-01 security patch level. The Update will be available for following devices:

• Galaxy Tab2
• Galaxy Nexus (also added ffmpeg codecs)
• Oneplus One

SlimKat

SlimKat updates for 2017-04-01 security patch level. The Update will be available for following devices:

• Galaxy Tab2

Source can be found here in case you wan’t to compile yourself.

General

Hey together! There have been some silent from my side, i spend a lot of time looking into android 7 for tab2 and tuna with success. It took some days until i got one major bug fixed: the device rebooted once it connected to wifi.

I am forced now to take a break from android to look for a payed part time job to buy a new device which fits my needs.

I currently own a LG G4 which is affected by the well known bootloop problem… It got repaired in February already, but after 2 weeks of use the issue was back and I lost all my personal data a second time. The G4 is still in the repair center, since 3 weeks… Researching makes sure: the issue will never be fixed properly by LG and I will loose all my data again, sooner or later, once the device is back… Sad about it: the shop where i bought the G4 won’t refund… they can’t even tell me how long it takes to repair the device…

Absolutely no go and never ever LG again!

• LG is Being Sued Over LG G4 and LG V10 Bootloop Issues
• LG Bootloop Lawsuit Adds Nexus 5X, and the LG G5 and LG V20 to the Case

Galaxy Tab2

• New TWRP 3.1.0-0 uploaded. Official changes until 76958ae head from OmniRoms TWRP source (android-7.1 branch)
• New SlimKat 9.6 (Security patch level: 2017-03-01)
• Initial LineageOS 11 (Security patch level: 2017-03-01)

Samsung Galaxy Nexus

Thanks a lot to all donators! I received my maguro yesterday!

SlimRoms

• Initial unified (maguro & toro & toroplus) Slim6 Build available!

Galaxy Tab 2

I am still moving and unboxing my stuff, but i found some minutes to apply our latest improvements on Omni6

• some omap4 specific updates (e.g. HWC 1.1)
• latest Omni6 source

Galaxy Tab 2

SlimKat update (SlimKat 9.4) for espressowifi and espresso3g

• Applied a lot of security fixes on SlimKat Source (Android security patch level: 2017-01-01)
• Latest Kernelsource to adress a lot of security issues.

SlimLP update (SlimLP 0.18) for espressowifi and espresso3g

• Applied a lot of security fixes on SlimKat Source (Android security patch level: 2017-01-01)
• Latest Kernelsource to adress a lot of security issues.

Omni 4.4 & 5.1 for espressowifi and espresso3g

• Only device specific updates (get inline with our changes to improve Tab2 builds last couple of months)
• Latest Kernelsource to adress a lot of security issues, there is no rom specific security fixes applied.

Galaxy Tab2

• AOSP Page has been updated
• New TWRP 3.0.3-0 uploaded, it is now possible to flash roms which use experimental 3.4 kernel (This new TWRP is required for AOSP 7.1!!!). Official changes until f2e3f0c head from OmniRoms TWRP source (android-7.1 branch)

General

Some of you noticed that i am not quite active at the moment. No, i haven’t sold my devices, but private life counts more atm and i have a lot of other stuff to do because i am moving. Hopefully from february i’ll be more active again. I hope all of you had a good start into 2017!

Galaxy Tab2

CyanogenMod is discontinued, i guess all of you noticed the rebranding to LineageOS (at the end user should only notice the name change).

Unoffical LineageOS testbuilds for espresso3g and espressowifi might be up sometimes this week! Clean flash reqiured!

Galaxy Tab2

espresso-common TWRP 3.0.2-8

• Official changes until f3c1b2f head from OmniRoms TWRP source (android-7.0 branch)
• Fixes image flashing

CM 13 espresso3g and espressowifi get official nightly builds!

• espresso3g (P3100 & P5100)
• espressowifi (P3110, P3113, P5110, P5113)

Galaxy Tab2

SlimLP - Security Update

• Patched SlimLP source until 2016-10-01 security patch level
• Fixed a lot of CVE on our kernel
• Fixed screencast

Omni6 Security-Update

• 2016-11-05 security patch level
• Fixed a lot of CVE on our kernel
• Fixed screencast

Galaxy Tab2

CM 13.0 Update

• latest CM 13 source)
• Fixed screencast

CM 12.1 Update

• latest CM 12.1 source
• Fixed screencast

Slim6 Update

• latest Slim6 source
• Fixed screencast

Galaxy Tab2

SlimKat update (SlimKat 9.2) for espressowifi and espresso3g (no device specific builds)

• Applied a lot of security fixes on SlimKat Source (Android security patch level: 2016-10-01)
• Fixed a bunch of security issues on our Kernel

Galaxy Tab2

Kernel Update

• We re-enabled MMC_CAP_ERASE on our kernel source because of following reasons:
  • “moviNAND VHX 4.41 DISCARD feature” is (and always was) added to our kernel which should prevent MAG2GA eMMC (used on most 16GB Tab2 devices) from damage (official Samsung patch)
  • even with MMC_CAP_ERASE disabled some Tab2 with MAG2GA eMMC got read only (the reason is an issue in the eMMC firmware - besides MAG2GA eMMC is faulty/bad by default)
  • without TRIM emmc lifetime is shorter, it’s now possible again on supported eMMC
• Updated P51XX Touch Firmware

What Roms include those changes?

• all builds and recoveries since 24.09.2016

NOTE: You might need to use TWRP 3.0.2-6 (uploaded already) to flash the new roms, on Android 4 and 6 old recoveries might work (but better update too).

Galaxy Tab2

espresso-common TWRP 3.0.2-5

• Official changes until 99af766 head from OmniRoms TWRP source (android-7.0 branch)
• Support eMMC 4.5. In the past our “new” kernel did not support eMMC 4.5 (some people seem to have newer EMMC). On TWRP it wasn’t possible to wipe or flash any files on devices with newer EMMC.

CM 13 update for espressowifi and espresso3g

• Support eMMC 4.5. In the past our “new” kernel did not support eMMC 4.5 (some people seem to have newer EMMC) - that’s why some people haven’t been able to boot latest builds and got a black screen only.

Galaxy Tab2

CM 11 update for espressowifi and espresso3g (no device specific builds)

• Fixed slow bootanimation
• Fixed GPS

espresso-common TWRP 3.0.2-4

• Official changes until 724c514 head from OmniRoms TWRP source (android-7.0 branch)

Galaxy Tab2

Notes about latest official CM11 nightly update

• Clean flash might be required because of the following changes:
  • a lot of device specific updates (e.g. a lot of OpenSource blobs we already use on Android 5.1 and newer)
  • kernel source got replaced with our omap based OpenSource kernel (full change history, a lot debloated)
• There might be a tiny delay between the Samsung logo and the bootanimation. This happens because we disabled the bootloader init (The bootloader init was disabled and the kernel resets everything on boot which is a good thing but delays bootup). Also your Tab 2 variant get detected by the kernel automatically (read out from bootloader).
• If you have issues to boot your tab after a clean flash, you might need to update your bootloader. I’ll provide the files and a tutorial sometimes later this week (maybe next week).

espressowifi / espresso3g:

New espresso-common TWRP 3.0.2-3

• Latest TWRP 3 Source

golden (GT-I8190):

New TWRP 3.0.2-1

• Latest TWRP 3 Source
• Added “length” on data to keep space for crypto footer. Encryption should work fine now TWRP side (If you have still trouble: it might need some changes on the kernel which comes with your rom).

espressowifi / espresso3g:

New unified SlimKat build

• Security updates until 01.08.2016 Android security patch level

espressowifi / espresso3g:

Official Slim6 builds started

• Official Slim6 alpha 0.9 available
• Official changelog can be found here

espressowifi / espresso3g:

Slim6 alpha 0.8

• Latest SlimRoms 6 Source
• Official changelog can be found here

Add “No All Apps button” to known Slim6 bugs and tell how to solve it.

S3 mini (I8190):

Initial TWRP 3

• “reboot recovery” option has a small bug, the device reboots ~4 times until it is back in recovery.

Slim6 alpha 0.7

• Latest SlimRoms 6 Source
• Official changelog can be found here
• Maybe (yes, only maybe) last test build before we can get official weekly support

CM 13

• Latest CyanogenMod 13 Source

Slim6 alpha 0.5

• Latest SlimRoms 6 Source
• Official changelog can be found here

Multi-Rom Updates for espressowifi and espresso3g

• Slim6 alpha 0.4
• SlimLP
• CM 13.0
• CM 12.1

• Omni 5.1

  What changed?

  • latest Rom sources
  • device tree cleanup and reorganisation inside the device tree
  • Some Kernel changes (clean up the display init sequence without bootloader init)
  • Enable dexpreopt with PIC
    (Our system partitions are relatively large (~1 GB), but our data partitions are relatively small (~4.6 GB on 8 GB variants).
    In this case, it makes sense to enable WITH_DEXPREOPT_PIC, saving at least 100 MB space on our data partitions.)

Note: Omni6 is official now! You can use official nightly builds now!

Initial Slim6 builds for espressowifi and espresso3g

• No “All Apps” button by default. Create a Widget -> SlimLauncher -> choose “All Apps” to solve it

New espresso-common TWRP 3.0.2-2

• Fixed low brightness after screentimeout

New OmniRom 6.0 for espressowifi and espresso3g

• Fixed sensor position on P31XX devices.
• Fixed SIM Pin issues on espresso3g

Initial OmniRom 6.0.1 builds for espressowifi and espresso3g available

• Latest official OmniRom source. Device specific changes are all visisble in OmniRoms device repos.
• Currently sensor position isn’t set properly on P31xx devices, but it will be fixed on upcoming builds.
  A temporary fix can be found here, you simply need to flash it after the Rom from TWRP.
• Please note that OmniRom isn’t pre-rooted!
• Chromecast should still work on Omni 6.

New CM 13.0 builds for espressowifi and espresso3g available

• Latest CM 13.0 source
• Attempt to fix hotspot
• Ziyan fixed the random mac adress:
  The Samsung BCMDHD used to read the factory MAC address from /efs. Accessing the filesystem in-kernel is a very bad practice, but what can we expect from Samsung?
  We now calculate the MAC address based on the SoC Die ID: this is unique for all devices, and ensures that the same device will always have the same MAC address, not a randomly generated one.

Some updates on http://andi34.github.io

• Add Rom & Recovery Thread links to the rom pages
• Add Rom logos
• Add CWM and PhilZ Touch links for historical reason
• Fixed some small bugs, fixed navbar for better design and mobile view - thanks to @aykut78

New CM 13.0 builds for espressowifi and espresso3g available

• Latest CM 13.0 source
• Clean flash recommand because we switched to our new kernel for a final public test before it finally replaces our old, bloated kernel.
• NOTE: Booting takes some more time now - there’s a delay for up to 10 sec. betweeen the samsung logo and bootanimation (The bootloader init was disabled and the kernel resets everything on boot which is a good thing but delays bootup.)
• Many thanks to XDA’s Ziyan for the new kernel! He did the main part of it! (We worked together on it for almost 9 months now - where is the time?!)
• Kernel source will be available on CM’s github after this public test to be sure everything works as it should - please respect that the source won’t be public before
• Found a bug? Attach a logcat and dmesg on XDA.

espresso-common TWRP 3.0.2-1

• Official changes until 72c87ce head from OmniRoms TWRP source
• New kernel with last_kmsg support.
  NOTE: Booting TWRP takes some more time now. The bootloader init was disabled and the kernel resets everything on boot which is a good thing but delays bootup.

New SlimKat for Samsung S3 mini (GT-I8190) uploaded.
Includes a bunch of CVE fixes. Enjoy!

Updated TWRP for Samsung Galaxy Tab2 to v3.0.2-0 (Common TWRP).
Fixes encryption/decryption and some small other updates.

• New CM 13 builds for espressowifi and espresso3g uploaded, no device specific changes, only CyanogenMod upstream.
  For changes please check CyanogenMods Gerrit

• New SlimLP for S3 mini (i8190) uploaded, based on latest official Source, Global Menu added on top of it.
  Videorecording still half broken, only works if you don’t record Audio (you can use OpenCamera in that case).

• Added my work on S3 mini (i8190) on this page too.

Reworked my github userpage, special thanks to Ziyan!

Added Known bugs section (much more needs to be added, feel free to help)

Uploaded espresso-common TWRP 3.0.0-2 (updated recovery-kernel for proper last_kmsg support - makes debugging kernel issues much easier).

I also uploaded some new kernel for latest CM 13 espressowifi and espresso3g builds - please test if you have time! More information about it here on XDA.

CM 12.1 & Omni 5.1 builds and common TWRP are reuploaded (I missed to add a kernel change). Previous 23.03. builds have been removed so you can’t download the wrong files anymore.

CM 12.1 & Omni 5.1 builds and common TWRP will be reuploaded (I missed to add a kernel change). Current 23.03. builds have been removed. Fixed 23.03. builds and a fixed Common TWRP will be available soon (uploading already).

New CM 13 builds available.

Missed to add “espresso: fade off by default: This fixes orientation glitch on screen-off animation for 7 inch Tab2” - will be fixed on next build.

• libsensors: fix possible null pointer crash
• espresso: set hwrotation on init for 7 inch Tab2 variants
• some updates on kernel commonisation (might fix charging on P5113).

Those Tab2 user who are on “espresso-TWRP” please flash the latest device specific TWRP for your device or use the new Common TWRP to flash latest Roms.

• the “espresso-TWRP” won’t be able to flash Roms compiled after 22.03.2016,
• the new “Common TWRP” won’t be able to flash Roms compiled before 22.03.2017. I am sorry if it confuses some of you, but as i mentioned on 22.03.2016 we would conflict with HTC’s “espresso” device if we don’t do the renaming.

CM 12.1 & Omni 5.1 builds have been updated:

• libsensors: fix possible null pointer crash
• espresso: fade off by default: This fixes orientation glitch on screen-off animation for 7 inch Tab2.
• espresso: set hwrotation on init for 7 inch Tab2 variants

To avoid conflicts with with HTC’s myTouch 3G Slide T-Mobile (“espresso”) all upcoming unified builds for GT-P3110, GT-P3113, GT-P5110 and GT-P5113 will be called “espressowifi” instead “espresso”.