I wanted to ask, witch Roms are stable and support all features of Kenzo.
It seems that in several Roms there are different Problems,
from wakelocks and Battery drain,
over Wifi Problems
to missing Fingerprint or VolTE support.
Is it a Problem with Android 6.0 or also with 5.1 based Roms?
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
jimakos98 said:
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
Click to expand...
Click to collapse
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
DarkAlucard said:
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
Click to expand...
Click to collapse
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
jimakos98 said:
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
Click to expand...
Click to collapse
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
DarkAlucard said:
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
Click to expand...
Click to collapse
Well, if you are going to flash this rom you are going to have to flash the appropriate firmware too, since CM is based on it. If you flash the rom without flashing the firmware, you might end up with missing options in settings (I tried this and the "fingerprints" tab was missing). As soon as I flashed the firmware everything got fixed. Also, an official rom means that it is developed by a member or a group of members that have created the original project, while unofficial roms can be built by anyone. For example I can take a CM build and customize it the way i want and then release it to the public. This makes it an unofficial rom, since I'm not a member of the CM development team. But if a rom or an update releases on the CM website, then it is considered to be official.
By the way about the VoLTE support, quoting from OP Q&A:
Q) Is VoLTE supported? (Also useful if you have GApps related problems).
A) No. We use all proprietary blobs from MIUI Marshmallow alpha 'leaked' builds and those builds itself do not have it working. So we'll have to wait until Xiaomi fixes it in their marshmallow builds in future. Also we can't fallback to old LP radio blobs/libs and are not suited with current setup. #blamexiaomi
Click to expand...
Click to collapse
I guess you'll have to wait for Xiaomi to release a stable working MM build if you want voLTE support. :/
Related
"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.
Fantastic News! Will get round to trying it shortly, thanks for the link!
While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...
In before "no build for xxxx?!?!?!?"
Anyone know how to port a d802 rom to d800?
Ready to try it out and see what happened..??
his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !
Can anyone port the Nexus 5 ROM?
Updating this thread later today if nothing gets in the way.
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
For all those who aren't yet ready to upgrade to Lollipop but would like to close this vulnerability on their device, I have built the latest CM11 i9100 source as of 9/1/15 (since CM11 nightlies for this device are no longer released for download). This build is unofficial but I have not modified it in any way**. It includes all StageFright fixes that the CM development team has implemented.
All required downloads are located here.
Works well as a daily driver with Lanchon's i777 Crossflash Kernel on my device.
Installation instructions can be found on CM's website or on Lanchon's kernel thread (above).
I recommend wiping cache/system/data prior to flashing (dirty flash with only a cache wipe did not work on my device when upgrading from the last public nightly).
Good luck!
** I did manually modify the updater-script to allow this ROM to be flashed on any device (because i9100 ROMs refuse to flash on the i777/S959G). Flashing this ROM on anything other than an i9100/i777/S959G WILL brick your device.
XDA:DevDB Information
CyanogenMod 11 [UNOFFICIAL] for i777 with Stagefright Fix, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
dimoochka
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-08-31
Last Updated 2015-08-31
Apparently the crossflash kernel is incompatible with this build (not sure why - was working ok on my device). A compatible version was rebuilt by Lanchon on 9/4/15 (can be found on his thread or in the download link in the first post).
Very considerate, and good of you to take the time to present this. Cheers, and build-on!
-Cyril
Stagefright bug still present
Flashed it yesterday.....all works fine.....except bug isn't fully patched
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
I just started a rebuild. Will try to upload when it's finished tonight - maybe that vulnerability has been patched since the last time I built this (months ago).
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
dimoochka said:
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
Click to expand...
Click to collapse
i just dirty flash it. right?
mmystere68 said:
i just dirty flash it. right?
Click to expand...
Click to collapse
If you're coming from a prior version of CM11 dirty flash should be fine.
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Edgarhighmen said:
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Click to expand...
Click to collapse
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
dimoochka said:
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
Click to expand...
Click to collapse
Thanks dimoochka, i'm probably going to give it a go this weekend.
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Rhaegon said:
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Click to expand...
Click to collapse
Glad this helped! Just so you're aware I haven't rebuilt this ROM for a good 9 months (and I am not even sure if the CM team is still patching old bugs in versions 11/12). If you're unable to get CM13 on the i777, I would definitely suggest buying a newer device for the sake of security. Nexus devices are basically the only option I'm aware of here since none of the other manufacturers actively maintain their ROMs. I retired my i777 in leiu of a Nexus 5X about 6 months ago.
Best of luck!
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.
I recently did a full wipe, installed the latest miui Dev ROM for Kate and then did a clean lineageos install.
However, battery performance is terrible, roughly 4 hours sot under similar conditions that I got 9 hours sot a few months ago.
Basically I want to know if installing an old MIUI Dev ROM will roll back my firmware?
There is very little discussion of "firmware" for the phone. Does anyone know of a log or different versions and changes ? Is "firmware" the same as baseband ?
dn* said:
I recently did a full wipe, installed the latest miui Dev ROM for Kate and then did a clean lineageos install.
However, battery performance is terrible, roughly 4 hours sot under similar conditions that I got 9 hours sot a few months ago.
Basically I want to know if installing an old MIUI Dev ROM will roll back my firmware?
There is very little discussion of "firmware" for the phone. Does anyone know of a log or different versions and changes ? Is "firmware" the same as baseband ?
Click to expand...
Click to collapse
Yes, the miui roms include firmware so it will overwrite.
Did you try custom kernels? There's an unofficial LineageOS by Umang96 with radon kernel build in.
I am currently on resurrection remix with stock kernel. I figured out that most of my battery drains because of bad 4g reception. In resurrection remix there's a setting to turn on 2g when screen is off, that saves me a lot of battery.
Hi John
Honestly I find kernels a bit of a placebo. Too much tinkering and I've never really seen any big benefits from a custom kernel. That said I just installed Radon to see how things go.
I'm going to backup and install an old miui Dev and then do a clean lineage install I think.
Would be good to find or start developing a resource that has info on the miui "firmware". I have zero clue on the differences. Presumably a lot of changes are simply miui changes - I dunno what will change when I move across to lineage
dn* said:
Hi John
Honestly I find kernels a bit of a placebo. Too much tinkering and I've never really seen any big benefits from a custom kernel. That said I just installed Radon to see how things go.
I'm going to backup and install an old miui Dev and then do a clean lineage install I think.
Would be good to find or start developing a resource that has info on the miui "firmware". I have zero clue on the differences. Presumably a lot of changes are simply miui changes - I dunno what will change when I move across to lineage
Click to expand...
Click to collapse
You can't do that, lineage won't work with older firmware, so when you start from old global dev, you need to flash the newer firmware from the LineageOS thread (OP #2). Complete waste of time.
Capt. John Yossarian said:
Yes, the miui roms include firmware so it will overwrite.
Did you try custom kernels? There's an unofficial LineageOS by Umang96 with radon kernel build in.
I am currently on resurrection remix with stock kernel. I figured out that most of my battery drains because of bad 4g reception. In resurrection remix there's a setting to turn on 2g when screen is off, that saves me a lot of battery.
Click to expand...
Click to collapse
Capt. John Yossarian said:
You can't do that, lineage won't work with older firmware, so when you start from old global dev, you need to flash the newer firmware from the LineageOS thread (OP #2). Complete waste of time.
Click to expand...
Click to collapse
Yea it suggests to be on the latest firmware but I don't see why it won't work on a firmware from a couple of months ago. Realistically, someone who installed lineageos a few months ago will have just been installing weeklies and never bothered getting a newer miscellaneous firmware from the thread though, right ?
dn* said:
Yea it suggests to be on the latest firmware but I don't see why it won't work on a firmware from a couple of months ago. Realistically, someone who installed lineageos a few months ago will have just been installing weeklies and never bothered getting a newer miscellaneous firmware from the thread though, right ?
Click to expand...
Click to collapse
Everyone on LineageOS without issues is on firmware from OP#2. The new nightlies are built by devs using this firmware, and you should be on it too to ensure everything is working properly.