Related
Latest Thread update
This section is to alert returning readers to new sections or information as they are added. New readers, please start at "Introduction"
17th Jul 2013 - Added Googy-Max. I thought this thread was dead
21st Jun 2013 - Request: Please don't ask if x.x.x (new release) has SDS fix. See "***" at end of post 1.
19th Jun 2013 - Added Official CWM Link in safe recoveries (Please only use links provided)
18th May 2013 - Revised "Stock section" to be more succinct
13th May 2013 - Added Devil kernel to safe list
3rd May 2013 - Added more about SDS v half SDS in the "What do we think we know" section
12th Apr 2013 - tried to distinguish between Fix 1 and Fix 2
6th Mar 2013 - Added ICS boaotloader to "Other links"
25th Feb 2013 - Added "Other Links" section at end of post 1
26th Jan 2013 - Update on bootloader requirement, courtesy of AndreiLUX
Previous: Added Speedmod K2-5 Test 1 Kernel
Previous: Added quotes around the fixed items for visual prominence
Introduction
Hi All,
I am seeing a lot of Buzz about the Sudden Death issue and recent fixes identified by AndreiLux and implemented into his Kernel here:
http://forum.xda-developers.com/showthread.php?t=1691401 so please take a moment to thank him.
Unfortunately as there seems to be some uncertainty about what is or is not covered by the Fix, I have put this thread together to eliviate some of the many off topic questions posed by members in development threads, which is unfair on the developers.
So what do we think know?
Please be aware, this is not related to the Exynos Memory security issue.
The "Sudden Death" issue is caused by firmware on the (16 GB) VTU00M, revision 0xf1 eMMC (Embedded MultiMedia Card or internal memory if you like). Samsungs Kernel Source Code (Update 7) has been identified as the fix. There is still no evidence that the latest sboot bootloader addresses this issue.
Although we are still not quite 100% Certain this will prevent all S3's suffering the SDS (Predisposition to the fault etc), to the best of our knowledge it does. Even if it does not fully fix it, its closer to a fix and safer than older versions, so if its within your means to do so, an update would be advised. Please don't panic. If it's going to happen, it's going to happen and that's that. It will be repaired under warranty. I had to use a Bold 9000 for 7 days whilst mine was repaired
SDS seems to manifest in 2 distinct ways.
1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced
* Being on Charge is NOT the cause. This is a writing to memory issue and it is more likely to happen when teh device is awake rather than in deep sleep. When the S3 is on charge, it holds a wake lock (so remains awake) throughout the entire charging period, meaning SDS is more likely to occur when on charge This does not mean you should avoid charging your phone. If it's going to happen, it's going to happen
2) Half SDS as it has not-so-affectionately become known. This tends to be more of a boot loop of the Samsung boot splash. the eMMC is partially wiped out. You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.
One problem Half SDS has is that the information download mode uses to show the status as "Official" appears to be wiped out by the bug, leaving your status as "Custom". This can leave you in a precarious position as this is what Samsung uses to establish warranty validity. You may also see your product field is blank.
Please help me maintain this list by identifying fixes as and when released, Please post the Link and Version number of anything with this fix implemented
How do I check my eMMC?
Using the EMMC check app from play, you can see if your eMMC is the VTU00M 0XF1 (affected chip).
Please note:
1) We only need this app to check the version.
2) Nothing you see in this app will change once you apply a fix. It simply gives you the version. If you expect 0xf1 to change to something else, you are mistaken. Only replacing the motherboard will do that.
What do I need to be "Safe"?
The "Fix" is actually a preventative measure. It cannot revive a "dead" device. It has to be applied before failure.
To be 100% safe, you need:
A bootloader with fixes**
[*]A Recovery with a fixed kernel
[*]A Fixed kernel to run Android
If you are a normal user only using official releases (no custom ROMs, Kernels or recoveries) then we treat you as "Stock" - read on.
Lets get to it... Where is it fixed?
Stock:
All 4.1.2 official releases (stock) include a Kernel, bootloader and recovery with the Update 7 "Fixes" (or newer) applied. If you have 4.1.2, officially consider yourself "Safe".***
Stock (but rooted):
If you rooted a 4.1.2 stock ROM, you will still be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections to ensure your kernel or recovery are listed as safe.
The below official kernels were tested, but we no longer need to test. All 4.1.2 (stock) kernels and newer have fixes.
XXELKC
XXELL1
XXELL4
XXELL5
XXELL6
XXELLA
XXELLB
XXELLC
Fix v1
Please note, you may experience freezes and /or reboots using a Fix v1 ROM (Well actually kernel that is included in this ROM). Essentially any Stock 4.1.2 ROM between:
LKC and MA2
Which means:
2012 November revision 12 and 2013 January Revision 2
...may experience freezes due to the way the fix works. This is annoying but better a freeze than a motherboard replacement.
Fix v2
From what appears to be Update 8 sources (MB1 onwards), the fix seems to be much better with far fewer freezes. I haven't included the MR* vodafone ROMS because who knows? They don't follow the standard naming convention. All I can say is MR2 came out when MBx was around (B = February) but is still only fix v1
People who have never rooted need not read any further. Essentially, if you have an official, never rooted 4.1.2 ROM, you're "safe"
Click to expand...
Click to collapse
-------------------------------------------------------------------
Custom ROMs which include a ROM specific and dedicated kernel (including fixes):
These are custom ROMs that have their own kernel that is not flashable separately. This means it is not packaged with a kernel from the "Custom Kernels" section. If you have the version specified or newer, you are "safe"
Any 4.1.2 (or newer) TouchWiz ROM with a repacked, stock kernel - no need to list them all.
HydRx-D v2.2.1r1 (TW)
CM 10.1 Nightly 20130109 (AOSP)
Tamasek's Unofficial CM10.1 v32 (AOSP)
ReVolt JB Nightly 20130111 (AOSP)
Click to expand...
Click to collapse
Custom Kernels:
These kernels include the update 7 fixes (or newer). If you are rooted with a custom Kernel that is older than (or doesn't match) the versions below, you are not considered "safe"
Perseus Alpha31+ (i9300 TW)
Boeffla 2.6 Alpha1 (i9300 TW
Speedmod K2-5 Test 1 )i9300 TW)
Yank555.lu 3.0a (i9300 TW)
Siyah 1.8.7 (i9300 TW & AOSP)
Devil ALL Versions (i9300 TW & AOSP)
Googy-Max ALL versions (i9300 TW & AOSP)
Yank555.lu 1.4 (i9300 AOSP)
Click to expand...
Click to collapse
Custom Recoveries:
Since the recovery uses a kernel too, to be "safe", the recovery's kernel must also be fixed.
PhilZ Touch 4.00-b04 (i9300)
Siyah 6.0.1.4 (Siyah Kernel users only)
TWRP 2.3.3.1
CWM.img from clockworkmod.com CWM.tar from mskip (6.0.3.2)
CF-auto-root (stock recovery supplied with this)
Click to expand...
Click to collapse
Please be weary of CWM. It can be compiled by anyone which means we cannot guarantee all versions have the latest fixes. Please only download from the links posted above
Obviously, rooted users are probably more familiar with what to do. I don't really want to recommend non-techy people flash official firmwares if they are not comfortable doing it. There will be a fix on its way to you all soon anyway, so the worst that will happen is you are affected and you have to get your phone repaired...
For those who are technical but would prefer to follow an Odin flash guide for official firmware, read the appropriate section here:
http://forum.xda-developers.com/showthread.php?t=1671969
Recap
So to recap, if you checked you have VTU00M 0xf1 with EMMC check , you need to ensure:
If unrooted (never rooted / modded), you are on one of the "Stock" ROMs listed above
If rooted, you have one of the "Custom Kernels" OR "Custom ROMs including kernel" OR rooted "stock" with original kernel AND one of the "Custom recoveries" from the lists below
**Bootloader note
Download mode uses a bootloader packaged micro-kernel
It will only affect those who use download mode. Personally I am rooted so I don't use it so i'll be sticking with one that doesn't mess with the flash counter, however anyone who does use download mode should consider updating. Those who care more about flash counters and will stay with older bootloaders should avoid flashing anything in download mode
*** Please do not ask if newer builds (either not mentioned here, or newer than 4.1.2) include the fixes.
Samsung have a single repository of kernel source code. They continue to develop this code. When they add a fix, it's there forever in every new kernel built after the fix is added. Every fix is in new kernels automatically. They do not have a list of fixes they must add every time.
The only way a new kernel does not contain a fix is if it is manually (and specifically) removed from the source code. Can you think of any logical reason why they would do that?!
Other Links
Ultimate Unusual Freezing thread (The fix causes Freezing, possible solutions)
Ultimate SDS thread (Further discussion of the SDS issue)
ICS Bootloader for those who want to keep custom counter at 1
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Yank's kernel has the fix too, I think.
Two questions:
1. When boot into Download Mode- is it safe?
2. Someone said about charging the phone when it is off and off the wallsocket. How about the fix/security then?
Glebun said:
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Click to expand...
Click to collapse
Could the failure process already have started? I'll put a caveat next to that....
rootSU said:
Could the failure process already have started? I'll put a caveat next to that....
Click to expand...
Click to collapse
As far as i know he had siyah kernel installed
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
yahyoh said:
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
Click to expand...
Click to collapse
Thanks. Signed off my Andrei today so I assume that appears in tonights nighty?
#
Sorry guys, ran out of thanks today
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
theslashy said:
As far as i know he had siyah kernel installed
Click to expand...
Click to collapse
That would make sense as its the kernel not the rom that has the fix. Has anyone got a link please?
mjb said:
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
Click to expand...
Click to collapse
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Great thread. Hope for news regarding the recovery.
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
PhilZ Touch 4.00-b04
Download:
- odin: http://www.mediafire.com/file/3g6ke58rsvs3j8y/philz_touch_4.00-b04-i9300.tar.md5
- cwm: http://www.mediafire.com/file/m6z7wwrd20pd9ln/philz_touch_4.00-b04-i9300.zip
This version wouldn't have been pushed as I did not plan any updates of the binary before 4.00 Final. But since we needed a repack with XXELLA kernel and the code was ready for these changes, I pushed it.
Changes:
- Repack with XXELLA kernel supposed to be SDS safe
- Fix romname added to nandroid backups: now build.prop will be parsed instead of reading system properties
- Custom rom.zip scripts completely revised to add a bit of process progress (beta and will be completely revised in Final build)
Click to expand...
Click to collapse
I do not feel like it is so much of a risk to flash via odin. Unless you are a noob. I am a noob but I usually read a lot before doing anything on my device.
montage mahal said:
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes indeed but ts a real issue even if you never flash anything.
rootSU said:
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Click to expand...
Click to collapse
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
mjb said:
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
Click to expand...
Click to collapse
Yep no worries. I have reworded the OP a little more to reflect. Please feel free to help me phrase it
I think that best solution is to flash PhilZ Touch 4.00-b04 as is based on XELLA (secure) and using XELLA reom with kernel or Perseus. PhilZ recovery works with exfat - Yank kernel not - so is for me useless
Great news! I hope with this recovery we can avoid SDS issues!.
Thanks for your help and effort
Thanks rootSU for all your support (sorry, out of my 8 thanks as always)
Just an edit to the op: stock recoveries: instead of none, maybe add XXELLA
Bye
Hello there,
I'm looking for a way to mount nfs shares of my NAS and (debian wheezy) server in the filesystem for access of my media files.
I thought for long that it would be the most natural thing to do for my (linux based) mobile devices in a linux server environment, but it seems I'm far off.
So far I have been unable to mount these nfs shares of mine to the Nexus 7 (grouper) device running a Carbon ROM 4.4.2 Nightly Build from march this year (CARBON...20140302-0433.zip) with CifsManager, most likely due to its lack of kernel support (version 3.1.10--g90cc2cb1 bigshotrob...).
May one of you recommend a kernel that supports nfs, cifs and utf-8 for this build? I restrain from updating it as it is running smoothly and without problems (Remember? Never change a...) and I don't like to invest much time for the reconfiguration and other related stuff.
I know there is M-Kernel (http://forum.xda-developers.com/showthread.php?t=2168787) out there that claims to have exactly the requested support and compliance to the CarbonROM series. But I'm unable to sort out what version of the kernel would match my build of the ROM.
I understand that the most actual release is for versions 4.4.4, but the changelog and >200 posts I've browsed do give no hint which release was compiled for 4.4.2 ROMs.
Please note, I would ask directly in that respective thread in the development section if I could, but owing to the (imho pretty stupid) 10 post restriction of newcomers I am unable to post there.
Edit: Not necessary anymore, got my postings ...
Accordingly, my second question would be, if someone with more than 10 posts would be so kind and ask the following questions for me in the given thread?
Namely:
What version of the kernel would fit my 4.4.2 CarbonROM Build and where could I obtain it?
Does anyone had success to mount nfs shares with it (or cifs, if not) ?
Edit end
That and any alternative ways/hints to get nfs going would be highly appreciated!
Thank you very much,
Nix
Specs Summary:
Nexus 7 2012 Wifi only
Carbon ROM 4.4.2 Nightly Build (CARBON...20140302-0433.zip)
Kernel 3.1.10--g90cc2cb1 bigshotrob...
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Edit
http://vp-zp.com/snuzzo/kernels/grouper/
Forgot my link lol
Snuzzo said:
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Click to expand...
Click to collapse
Thank you for the reply snuzzo,
would you mind to give some details where to learn more of its features and where to find it?
Then I'll have a look at it.
EDIT:
Thanks for the link! But exactly what version do I have download for my Carbon ROM build above, if I'd decide to use it that is?
Presumably .../kitkat/Funky...??
BTW, are there some feature lists or such things? I'll probably browse the forum a bit, I suppose?
Cheers, Nix
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run. You will want 1.6.2 or 1.6.1.
Snuzzo said:
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run.
Click to expand...
Click to collapse
Sounds great, although most of it are books with seven seals for me
What about nfs support? And its definitely for 4.4.2 based ROMs?
Thx again,
Nix
Yes to both. It has NFS and CIFS support.
And v.1.6 is the one you'd suggest?
Nixblicker said:
And v.1.6 is the one you'd suggest?
Click to expand...
Click to collapse
Yes.
Snuzzo said:
Yes.
Click to expand...
Click to collapse
One more question, please - do I have to activate or load those modules manually or will they be loaded at bootup by default?
Where may I find them to insmod/modprobe them manually, if not?
Thanks for the help once more,
Cheerio,
Nix
They will load by default.
This thread will be about changes i have made to the device trees for the t700,t705,t800,t805 which should in the long run make maintaining the variants a lot easier the primary changes i have done are combine all 4 of the variants into 1 kernel source as well as make a common device tree so they can inherit everything that is the same across devices.
Kernel Changes:
The Base kernel from Cyanogenmod supports klimtwifi (T700) and klimtlte (T705) to add support for chagallwifi (T800) all that is needed is to add its defconfig which is this file
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
To add support for the Chagallte (T805) it was a little more complicated for to do but very simple for you guys for a little background T805 is exactly the same chipset as the other Galaxy Tab S's except for whatever reason Samsung decided to put a different gpu (Midgard_wk04) everyone else uses a mali_t6xx.
The stuff developers actually need to support Chagalllte are the following:
Defconfig:
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
The GPU addition commit:
https://github.com/LiquidSmooth-Dev...mmit/c8e96e86c902cbc2b13d34e7e7158623eacf5d84
Bam that was easy now any kernel can support all 4 main variants of the Tab S
Device tree and vendor repos
First part i want to place links to all of the stuff that's needed to make a rom for each device in one place.
(Disclaimer the trees will be LiquidSmooth but it is very easy to convert them to any rom)
Klimtwifi (T700):
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtwifi
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/klimtwifi
Klimtlte (T705)
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtlte
https://github.com/schwabe93/vendor_samsung_klimtlte
Chagallwifi (T800)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagallwifi
https://github.com/diego-cr/android_vendor_samsung_chagallwifi
Chagalllte (T805)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagalllte
https://github.com/Andrewt12/android_vendor_samsung_chagalllte
WIP Common Device Tree:
When bringing up support for LiquidSmooth for these devices i noticed that they are all pretty much copied each other (which makes sense) but because of it there was tons of duplicated code between the devices so i decided to make a common device tree so any future code changes could be placed in one place instead of over 4 device trees. This is still a WIP because i do not have all the devices so i can not test them all in my eyes they should all work fine. The common device tree will also hopefully will be rom independent so no changes would be needed on a per rom basis. I can for sure say klimtwifi and chagallwifi work with my common tree, Chagalllte and klimtlte need to be tested still.
Common Device tree repo:
https://github.com/LiquidSmooth-Devices/android_device_samsung_exynos5420-common
Common device tree migration commits
Klimtwifi:
https://github.com/LiquidSmooth-Dev...mmit/444b4fc08f82eeeabe8e0a533539fe0c2fadd723
https://github.com/LiquidSmooth-Dev...mmit/cdf5f06c8a29bb237b964d5ee602d151c6323677
Klimtlte:
https://github.com/LiquidSmooth-Dev...mmit/8570d466e2b5b88c316c7f1576bf8ea9051c5e2a
Chagallwifi:
https://github.com/LiquidSmooth-Dev...mmit/5be51eb30283355109c65513ea209dd1d6855ff2
Chagalllte:
https://github.com/LiquidSmooth-Dev...mmit/5ff21d73a9cad3f7f9cf7f79b29bdbab0d8b2b1e
One more improvement that myself and @diegocr made was finally made a pernament fix to Chagallwifi's (T800) wifi issue he made a custom release tool in the device tree to make it so you would not have to manually patch it every time. I then took that and fixed the root of the issue which was that the vendor repo was not putting the files in the right spot. (My orig commit also did egl but that was not needed) the commit that did it is this:
https://github.com/diego-cr/android...mmit/1fc5135eda985ddc159f8465ee114e67aa5dfcae
Now into the features of my Deathly kernel
XDA:DevDB Information
[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1], Kernel for the Samsung Galaxy Tab S
Contributors
deadman96385
Kernel Special Features:
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-21
Deathly Kernel
I have had a deathly kernel on most devices i own the goal of it is to get as many options and features into a kernel but still be stable. For the Tab S i took the aosp cm base and have updated it against kernel.org from 3.4.105 too 3.4.108 along with pull in a bunch of features from other exynos 5420 devices
As you read above i have made a common tree which changes the ramdisk so i have to provide two zips one with the new format one with old format currently the only rom that i personally have built with the new version is the latest klimtwifi and chagawifi all other roms will boot loop with it so use the old version
Currently i only have flashable for Klimtwifi (T700) i will generate the others once i get back from my trip.
New Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/New_format/
Old Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/Old_format/
Features of the Deathly kernel:
Will support all 4 main tab s devices (will add support for the US carrier variants if aosp is brought up)
CPU Voltage Control
CPU OverClock/UnderClock
GPU Voltage Control
GPU OverClock/UnderClock
MIF/INT Voltage Control (I will not show how to configure this if you know how too then you can)
Wolfson Sound Control Thanks to oloendithas for fixing it for stereo out
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot (WIP)
Android Logger disabled by default can be enabled over sysfs
Exynos thermal exposed to sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Details how to configure all of the features i will add the rest once i come back
GPU Configuration:
To configure the max or min gpu frequency you would go to either of the following files in a root enabled file browser and change the value inside
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu
The allowed values for the files are as followed:
667, 600, 533, 480, 420, 350, 266, 177, 100
T800 owners the default min gpu freq is 100 on all roms if that causes issues raise the min freq to 266 you will probably not notice a battery decreases if that still does not work let me know i'll take a look at the code.
Reserved
Reserved
Thanks, working great on CM12.
Thank you man.. Im glad someone finely separated the device tree... And specially Happy about a new kernel that I can use in my Project Roms.
With all Credits going to you of course.. thanks again.
Hey mate, thanks for this!
I'm a little unsure about the new and old ramdisk thingy.
Running aicp on my klmitwifi, new ramdisk is cool?
Will try anyway, but let me know please!
Edit :
just checked, didn't stupidly before, Looks like the kernel is baked in your AICP rom.
Thanks again for your hard work!
Edit edit:
tried the v02 on the rom mentioned, had to revert cause I was having many ui fc.
Used new ramdisk version, could be that or I should have done a clean flash maybe?
Thanks for this, hopefully if fixes the lag issue for me on CM12 with the T800.
Thanks for all the hard work, grid .1 and .2 both worked perfect on bliss rom
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
SkOrPn said:
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
Click to expand...
Click to collapse
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
deadman96385 said:
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
Click to expand...
Click to collapse
OK, thanks. Hope your enjoying your time off... :good:
I'm going to backup your kernel and try ashyx's new build released today. Its closer to stock but has F2FS support also. Then I will test yours once its updated. Loving this new tab of mine, almost forgot how much fun it was trying to find the sweet spot on a device, lol. My Nexus 7 found its sweet spot a long time ago and now its just a plain ole boring tablet. hehe
diegocr said:
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Click to expand...
Click to collapse
...Slim LP, for t800 maybe, where to find it?
m.
meduza2 said:
...Slim LP, for t800 maybe, where to find it?
m.
Click to expand...
Click to collapse
In SlimRoms Builders Collective
diegocr said:
In SlimRoms Builders Collective
Click to expand...
Click to collapse
...nice Do you intend to make an own SLIM LP thread?
m.
meduza2 said:
...nice Do you intend to make an own SLIM LP thread?
m.
Click to expand...
Click to collapse
Great idea, but now I have no time to keep updated
diegocr said:
Great idea, but now I have no time to keep you updated
Click to expand...
Click to collapse
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
meduza2 said:
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025
Hello Guys,
These are my Unofficial builds of MetalliumOS for Find5
Spike Laboratory - Metallium
ABOUT Spike Laboratory - Metallium
Spike Laboratory - Metallium >>SPLM is an after market firmware based latest "Android Lolly-Pop 5.X.X. This firmware is designed By Spike Laboratory .This firmware suits specially for those people who like,Multitasking performance,optimum speed. In-addition to This the firmware has Inbuilt options and settings to make customization of your Device the way you like.
Features , changelogs and screenshots can be found on Spike Laboratory - WEB
SUPPORT FOR SPLM RELATED ISSUES :
We spend an astonishing amount of time developing this firmware.
We can't spend much time on XDA as a result, so if you need support, please try the following:
Ask a question in your device forum in XDA. Someone will no doubt try to help you.
Our device maintainers are going to help you so pm them.
Any bugs or any other issues report to the device maintainers.
If you want to contribute or join to the device maintainer team contact either team leaders or device maintainers.
We expect that users help each other, well xda is a ll about it.
OFFICIAL LINKS & INFORMATIONS :
Official Web-Page
SPLM ROMS
Recommanded gapps
DOWNLOADS
(Please do not mirror Download links or Mention Link in any of your posts )
INSTALLATION STEPS:
Minimum Requirements To Install SPLM:
Your Device Should be Rooted with Unlocked Boot-loader & Latest Custom recovery Installed.
Recommended Custom Recovery TWRP : Click Here to View TWRP Offical supported devices
Installation Procedure:
(A)If you are making a Fresh Installation(or coming from any other rom other than SPLM) :
Boot Into Recovery Mode
Wipe Data,System,Cache,Dalvik
Flash provide latest SPLM ROM Zip
Again Wipe Cache and Dalvik
Reboot To System
Now again Reboot into Recovery Mode
Flash latest G-Apps
Wipe Cache and Dalvik....and Reboot To System.
Have always this zip in your sd in case od sim unlock issue Find5 is exeperiencing since Lollipop, just flash it in recovery if needed.
Click to expand...
Click to collapse
(B)If you are already Running SPLM Rom But you want to update with latest version:
Boot Into Recovery Mode
Flash provided Updates of SPLM ROM(latest weekly)
Again Wipe Cache and Dalvik
Reboot To System.
Click to expand...
Click to collapse
SOURCE:
SPLM ROM SOURCE
SPLM DEVICES SOURCE
Kernel Sources
CREDITS:
ALL SPLM team
CM
AOSPA-L
SlimRom
CrDroid
DU
Omnirom
Click to expand...
Click to collapse
WHO ARE WE AND WHAT ARE WE DOING?:
TEAM SPIKE LABORATORY
XDAevDB Information
Metallium OS, ROM for the Oppo Find 7
Contributors
Schneiderle, a1krab
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-09-14
Created 2015-09-14
Last Updated 2015-09-15
reserved
reserved
New build
Hello Guys,
First release is available :
metallium_find5-1.0-20150914.zip
Download:
https://www.androidfilehost.com/?fid=24052804347815860
Next builds will have changelog.
Enjoy & Cheers
jejecule said:
Hello Guys,
First release is available :
metallium_find5-1.0-20150914.zip
Download:
https://www.androidfilehost.com/?fid=24052804347815860
Next builds will have changelog.
Enjoy & Cheers
Click to expand...
Click to collapse
Feedback are really appreciated
Sent from my Nexus 6 using XDA Free mobile app
New build Metallium
Hello new build is up: see op download link to basketbuild or normal way: https://www.androidfilehost.com/?fid=24052804347817647
Cheers
Here comes the feedback:
- Autorotation doesnt work. Maybe kernel related.
- Some lag and instability but this could very (most definitely) well be the bidji kernel. (Havent tested on stock kernel)
- Everything else works fine.
- Betterylife is fine, nothing crazy.
- Botton backlight works
Will test tomorrow with stock kernel a few minutes to confirm sone issues maybe. But I like the battery life of bidji kernel too much to not use it.
What does this rom do different compared to other cm like roms? I couldnt really find any major pros or cons. Just very cm like but not from cm I guess. I really hate that they have edited the default launcher with their own ugly app drawer icon and removed the launcher options. Luckily we have an appstore with other launchers. I will change rom to DU again probably because of the auto rotate (but button backlight doesnt work there if i recall correctly).
Still really loving all your builds to test compare and tinker with. And the new bidji kernel makes the tinkering and fiddling even more interesting . Hope this feedback helps.
Verstuurd vanaf mijn Find 5 met Tapatalk
boertjeg said:
Here comes the feedback:
- Autorotation doesnt work. Maybe kernel related.
- Some lag and instability but this could very (most definitely) well be the bidji kernel. (Havent tested on stock kernel)
- Everything else works fine.
- Betterylife is fine, nothing crazy.
- Botton backlight works
Will test tomorrow with stock kernel a few minutes to confirm sone issues maybe. But I like the battery life of bidji kernel too much to not use it.
What does this rom do different compared to other cm like roms? I couldnt really find any major pros or cons. Just very cm like but not from cm I guess. I really hate that they have edited the default launcher with their own ugly app drawer icon and removed the launcher options. Luckily we have an appstore with other launchers. I will change rom to DU again probably because of the auto rotate (but button backlight doesnt work there if i recall correctly).
Still really loving all your builds to test compare and tinker with. And the new bidji kernel makes the tinkering and fiddling even more interesting . Hope this feedback helps.
Verstuurd vanaf mijn Find 5 met Tapatalk
Click to expand...
Click to collapse
Ik dank je voor uw feedback!
Autorotation: well still a mistery only DU is working, kernel is the same, so frameworks must be the culprit.
For the rest, I just jump into this project cause I found it interesting and different from others but i'm slowly think I was wrong.
Anyway,yes it not cm but device trees are so, bugs will remain mainly the same .
To be honest, not sure I'll keep on long time with this one except if users are happy
At least om my AFH I have some 30 downloads, in their basketbuild, 0...
Een prettige end of weekend!
Jeje
Sent from my Nexus 6 using XDA Free mobile app
(I lolled a bit because of you typing Dutch )
Tested again on stock kernel, same issues as before with auto rotate. Something to add why this is different compared to other roms: it is not so much in options but everything that is there is done well. Like all icons and stuff are all good and done and there are no wierd looking menus. So it is a very slick experience IMHO (except the boot logo ugh).
Cheers
Hello Guys,
With Metallium team members, we decided to make those builds "unofficials". This won't change anything for you, builds with remain the same with same quality and improve progressively.
This is a good team and i'm proud to build for them, last post from my dutch mate proves it.
Reasons why this change: i prefer to keep my liberty, to build myself, to post my builds where i used to post it, and so on. Furthermore, i'm official member of crDroid team and it takes me lot of time, and i want to keep the same quality for them too.
So expect new Metallium build at least weekly.
I wish you a nice evening.
Cheers,
Any signs of lvm support on the ROM?
Sent from my X9076 using Tapatalk
New Find5 Metallium
piyush7243 said:
Any signs of lvm support on the ROM?
Sent from my X9076 using Tapatalk
Click to expand...
Click to collapse
Only one chinese mate is doing it without publishing his sources, so really difficult.
By the way: new build is up: metallium_find5-1.0-20150921.zip
Download: https://www.androidfilehost.com/?fid=24052804347820446
Cheers
jejecule said:
Only one chinese mate is doing it without publishing his sources, so really difficult.
By the way: new build is up: metallium_find5-1.0-20150921.zip
Download: https://www.androidfilehost.com/?fid=24052804347820446
Cheers
Click to expand...
Click to collapse
I think the sources are here
https://github.com/feelingfree-me/android_device_oppo_apq8064-common/tree/5.1.1-lvm
Sent from my X9076 using Tapatalk
piyush7243 said:
I think the sources are here
https://github.com/feelingfree-me/android_device_oppo_apq8064-common/tree/5.1.1-lvm
Sent from my X9076 using Tapatalk
Click to expand...
Click to collapse
i will check then guys!
I suppose some special twrp are required too?
Cheers
There you go. This is support LVM
https://www.androidfilehost.com/?fid=24052804347760547
piyush7243 said:
There you go. This is support LVM
https://www.androidfilehost.com/?fid=24052804347760547
Click to expand...
Click to collapse
Thanks mate, appreciated, i will try a build today, hope you'll test it, don't worry i'll test it first
Cheers
The TWRP works fine and can unify the storage. The CM build posted on the oppo forums seems to work no worse than any other CM-derived rom. An LVM aware build of Dirty Unicorns would be awesome. I'm happy to test things because my Find 5 isn't my primary device anymore so I don't rely on it.
jejecule said:
Thanks mate, appreciated, i will try a build today, hope you'll test it, don't worry i'll test it first
Cheers
Click to expand...
Click to collapse
I am already running a CM version having LVM and its good apart from Auto rotate which seems to be a bug in CM12.
But another ROM with proper support would be awesome and feel free to get back to me to test the same
P.S: enabling selinux enforce by default seems to be a but flaky
piyush7243 said:
I am already running a CM version having LVM and its good apart from Auto rotate which seems to be a bug in CM12.
But another ROM with proper support would be awesome and feel free to get back to me to test the same
P.S: enabling selinux enforce by default seems to be a but flaky
Click to expand...
Click to collapse
Unfortunately, CM12 has the autorotate issue in all my builds except DU. So what i propose is, first make a test on metallium to see if LVM works then try to adapt to DU, new DU version should come within one day or two.
Thanks for your support.
Cheers
Guys,
If you wanna test a lvm compatible build: go there: metallium_find5-1.0-20150923.zip
https://www.androidfilehost.com/?fid=24052804347821013
Cheers
Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.
I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^
Awesome!
I'm eager to hear about your endeavors in this!
L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant
L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.
@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule
Here is the screenshot I mentioned in my previous post.
I forgot to include it ...
Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?
I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first
31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Xperia z1 has carbon Android pie and gapps link
This may help you.
Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.
No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning
Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.
Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?
I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.