Related
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
This ROM features a stable enviroment [the most stable tested by me so far], with the least number of bugs (with 366BB), and probably one of the best performances.
Features: This ROM provides a default Portrait screen, it also has as the stock theme - TouchWizzedB (It looks like the Samsung ROM's, don;t know why i like it)
It features BeatsAudio, Bravia Engine and xLoud,
IIt provides a bootanimation and sound provided by Madhacker.
(if the bootsound is not on and you really want it, enter in terminal enablebootsound)
It also provides as the default launcher - GO Launcher Ex.
You can add [highlight]software[/highlight] capacitive buttons in the taskbar - thanks to nom051205 < Zip below
It was tweaked for daily use.
Skype has not been fully fixed, but i found a workaround, after rebooting, call someone, or a number like 444 then close, it should work, tested multiple times and it worked, i'm going to try and make a script to get rid of this step. (sometimes it works without doing a thing, so i think it is about luck )
Also, skype seems to leave the speaker on after singning out creating a huge battery drain, if you experience this kind of issue please remove your Skype and install this one, then go to advanced settings (in skype) > sound settings > disable sign-in/out sounds and Force speaker off after calls.
With those workarounds provided above, you should have a seamless experience with Skype..
FAQ:Q: Does it have USSD fix/Gapps/Phoenix Kernel?
Yes
Q: Is the WiFi stable?
With 366BB i have no problems with WiFi stability.
Q: Do i have to do a full factory reset if i come from other CM7 ROM?
No, just wipe dalvik cache, full factory reset is a must if you come from DSC/FroYo/Official 2.3.3.
Q: How do i flash 366BB?
You put your device in Fastboot, connect the USB and use a tool provided here or here.
Q: I can't install the ROM! Installation Aborted! (yeah, yeah, this is not a question..)
Open the zip file then you will see a folder, go into the folder, select all (meta.inf; system; boot.img) and re-zip those files and name it LXdroid 0.x.zip then flash it.
Credits to nom051205 for using his post almost copy-paste.
Q: What's wrong with Swype? It just FC's?
Install it manually, this should do the trick, you can find swype.apk in a link below.
Bootsound/Bootanimation Script Commands
Terminal commands for scripts:
enablebootsound - enables bootsound
bootsoundoff - turns bootsound off
bootsoundon - turns bootsound on after being turned off
newbootsound - /sdcard/android_audio.mp3 is copied as new bootsound
newbootanim - /sdcard/bootnanimation.zip is copied as new boot animation
(Probably you need to type su before those scripts, just saying...)
Credits go here.
Note: This is my first ROM, feedbacks and head-ups/tips would be welcomed in order to tweak it further.
--Added Screens for those who want to see something
You can upgrade to higher versions of LXdroid ROM without losing your data, just wipe Dalvik Cache!
LXdroid ROM 0.2 is provided as standalone flashable zip, it doesn't need 0.1 in order to work.
Download link: LXdroid ROM 0.2
Download link LXdroid ROM 0.1 (old, useless, not needed)
Download link swype.apk
Hotfixes for LXdroid 0.2 for Autobrightness FC and xLoud and Bravia permissions found here!
Quick tutorial aka Roadmap to a Custom ROM -Download ADB/Fastboot tools + Drivers from here. (You need to install the drivers before you begin).
-Download MultiRecoveryFlasher from here.
-Download MultiBasebandFlasher from here or download dsp and baseband flasher by n0p and StreakOwner from here.
-Download a custom ROM like DSC (most stable in my opinion), Longhorn or, the one provided here.
Now let's get started for real!
1-Install the drivers.
2-Put your streak in fastboot by turning the phone off and after that powering on by holding down volume + power button.
3-Open MultiRecoveryFlasher and flash StreakMod recovery. Reboot.
4-Put your streak again in fastboot.
5-Open MultiBasebandFlasher and flash 366BB or the script provided alternatively (does the job all by itself ). Reboot.
6-Enter Recovery by turning the phone off and then powering on holding up volume + down volume + power button.
7-Select "Software upgrade via Update.pkg on Sd Card"
8-A Dell logo and an attention will appear, press power button once to show the menu.
9-Hit advanced to mount sdcard via PC, so the SD card will appear in you PC via recovery.
10-Copy the ROM you downloaded to the sdcard (preferably to root).
11-Hit back in recovery, choose install sdcard updade.zip, then choose zip from sdcard, browse for your zip, and hit the camera button then select yes.
12-After the installation is completed, hit back to the main screen of the recovery, and choose wipe data/factory reset, then wipe cache partition, then choose advanced, wipe dalvik cache, wipe battery status.
13-(It is recommended to reboot again and do a factory reset from the dell recovery, White Letters)
14-The system will take some time to boot up, but you are done, enjoy your custom ROM.-------------------------------In my opinion the fastest and easiest way to get a custom ROM--------------------------------------------------
Disclaimer:
This ROM was made primarly for my personal use, it provides elements from all over this Forum, Credits section thanks personally all and i thank more of them that are not listed there, it is based on CM7.2 mdpi by hPa, it has elements from Longhorn and others, as always do a nandroid backup just in case, and don't blame me for ruining your beloved streak, although i don't think you can .
Credits:
The people/teams that inspired me to do this:
-DSC Team / n0p - Kernel and many Tweaks.
-hPA - For porting CM7 to streak.
-Tenorntex - Some tweaks imported from Longhorn, dialing screen theme.
-nom051205 - Soft-Buttons flashable zip
-Madhacker - Bootanimation and sound.
-xda Forum - For a great enviroment, other ideeas and tweaks.
-Google - Great search engine, thanks for the Android OS
-Others
--If you want credits for something i have in my ROM and i forgot about you, please let me know and i will update this --
Changelog:
0.3 - TBA
0.2 - 21 august 2012 - skype seems to be fixed, needs more testing, further improved performance, added BeatsAudio, Bravia Engine, xLoud, added stock Swype keyboard, bootsound enabled by default, disabled USB Debugging icon from Status Bar, (only the Icon, debugging remains enabled), maybe more - Kernel: DSC Phoenix Kernel Test 4
0.1 - 20 august 2012 - First release, good performance, things that work on all CM7 ROM's work on this one, things that don't work in all CM7 ROM's don't work in this one. - Kernel: DSC Phoenix Kernel Test 4
I guess it has fixed CM settings (like setting cpu frequency from within the settings and fixed lockscreen on 160 or 180 ??
jitin02 said:
I guess it has fixed CM settings (like setting cpu frequency from within the settings and fixed lockscreen on 160 or 180 ??
Click to expand...
Click to collapse
You can see the CPU settings, freq's and governors but you can't change them from the CM settings, i've included AnTuTu CPU Master Free in the ROM, and the locksreen it works fine on Ring and Lense, Rotary and Sliding Tab are small and aligned to the left. so i would say that no, it doesn't have them fixed as i didn't needed them, but maybe i will look into it.
Personally i use Ring Style at lockscreen and dial screen, with one ring only at lock and the default Freqs (128-998 mhz , Conservative).
Lexmazter said:
You can see the CPU settings, freq's and governors but you can't change them from the CM settings, i've included AnTuTu CPU Master Free in the ROM, and the locksreen it works fine on Ring and Lense, Rotary and Sliding Tab are small and aligned to the left. so i would say that no, it doesn't have them fixed as i didn't needed them, but maybe i will look into it.
Personally i use Ring Style at lockscreen and dial screen, with one ring only at lock and the default Freqs (128-998 mhz , Conservative).
Click to expand...
Click to collapse
if u can look into it i will be thankfull to u as i had to go back to froyo 351. b'coz of DSC wifi issue .
Thanks and is there no way to resolve cm settings frequncy issue:silly:
jitin02 said:
if u can look into it i will be thankfull to u as i had to go back to froyo 351. b'coz of DSC wifi issue .
Thanks and is there no way to resolve cm settings frequncy issue:silly:
Click to expand...
Click to collapse
You can use alternative software, as i mentioned, there is SetCPU or CPU Master Free, and CPU Master doesn't stay always on in RAM and you can set it to Set frequencies on boot
I think that CM frequiencies support must be added from the kernel, so i don't think i can do something about it
jamo59
Hello!
I like the ROM!
Only the Longhorn 2.9.1 Quadrant 2300 points for that!
The LXdroid only 0.1 points in 1408.
Well, it's a huge difference.
Test Battery, but the IGO primo 9 to be strong!
This looks like a very fast everything works properly (from my experience it!)
jamo59 said:
Hello!
I like the ROM!
Only the Longhorn 2.9.1 Quadrant 2300 points for that!
The LXdroid only 0.1 points in 1408.
Well, it's a huge difference.
Test Battery, but the IGO primo 9 to be strong!
This looks like a very fast everything works properly (from my experience it!)
Click to expand...
Click to collapse
I made this ROM without testing Quadrant,i never trusted that benchmark , i tested with AnTuTu Benchmark and it is not a big difference from Longhorn to LXdroid, i still need to tweak something more, but the overall feel is smooth as butter in my experience and the battery life is just great for me.
jamo59
Whew!
Now, I see no Google Talk?
Even I test!
jamo59 said:
Whew!
Now, I see no Google Talk?
Even I test!
Click to expand...
Click to collapse
You can download it from Google Play (Market), i don't use it so i didn't included it
jamo59 said:
Whew!
Now, I see no Google Talk?
Even I test!
Click to expand...
Click to collapse
I think you're really really fast IGO is not there!
Longer certainly really deserves a try!:good:
SKYPE ??
so what about skype, is it working ??
MadHaker said:
so what about skype, is it working ??
Click to expand...
Click to collapse
I'll tell you! I'm also interested!
Time!
MadHaker said:
so what about skype, is it working ??
Click to expand...
Click to collapse
I'm testing it now , i'l report back later.
EDIT: Not working...checking for a fix...
Lexmazter said:
I'm testing it now , i'l report back later.
Click to expand...
Click to collapse
Not ok! (skype)
Lexmazter said:
I'm testing it now , i'l report back later.
EDIT: Not working...checking for a fix...
Click to expand...
Click to collapse
i am sorry to say that any rom above 2.3.3 usually have problem with voip and there are no fixes for it at the moment...
deysmacro said:
i am sorry to say that any rom above 2.3.3 usually have problem with voip and there are no fixes for it at the moment...
Click to expand...
Click to collapse
Yeah, you said it, "at the moment"
jamo59 said:
Not ok! (skype)
Click to expand...
Click to collapse
Hello there!
If anyone has not read it, the good must be so skype has stopped working, that:
1, restart
2, the recording is started and is ready to.
3, visszahallgatod
4 to start the skype
5, a voice recorder pick up service.
6, to listen
7, glad it works!
jamo59 said:
Hello there!
If anyone has not read it, the good must be so skype has stopped working, that:
1, restart
2, the recording is started and is ready to.
3, visszahallgatod
4 to start the skype
5, a voice recorder pick up service.
6, to listen
7, glad it works!
Click to expand...
Click to collapse
Can you be more specific, i don't really understand what you are trying to say here
Lexmazter said:
Can you be more specific, i don't really understand what you are trying to say here
Click to expand...
Click to collapse
2nd that ;0)
Disclaimer: I will not be responsible if you brick your NT or your significant other leaves you for bricking theirs. As always, flash at your own risk.
Here is a full codefireX (cfX) ROM with 1.2GHz OC that is 5 touch enabled. You can use this with the 2 touch or 5 touch firmware, kudos to mik_os for the driver that does so.
codefireX is sort of a mixture between AOSP, AOKP, and CM10.
Here is their git: https://github.com/codefireX
Here is my kernel git: https://github.com/tonyp23/android_kernel_acclaim
Features:
Click HERE for a full cfX settings feature flowchart by BananaGranola (thank you)
NOT simply a re-named CM build
Built with a custom toolchain, strict aliasing, -O3 completely (including thumb_cflags), and other Linaro optimizations such as OOM/LMK changes.
Lots of extra settings in the codefireX settings panel
Please see this post on how to install the updated firmware if you'd like to have 5-touch. http://forum.xda-developers.com/show...9&postcount=75
With that said, many huge thanks to everyone who has put so much effort into making this awesome. If I forgot you, let me know!
Kuzma30, chrmhoffman, mik_os, fattire, Hashcode, Rebellos, demetris_I, Succulent, CelticWebSolutions, eyeballer, Bauwks, CM team, TWRP team, codefireX team, TI, BN
Here's general instructions on how to proceed
1. Update touch firmware if you choose
2. Install CWM 6.0.1.5 using fastboot
3. Wipe data/factory reset, wipe dalvik cache
4. Install ROM
5. Install newest gapps from goo.im
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip.md5sum
Reserved for future
It has a weird thing with the wifi icon, you may have to play with the codefirex settings and flick the 6 signal bars on then off again.
Nice! I'll give this a try.
Question, though. Any issues with apps disappearing due to sdcard issues? I know other roms have issues. Xda free is one app that I have issues with on the aokp build if I don't move it to internal.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati
liquidzoo said:
Nice! I'll give this a try.
Question, though. Any issues with apps disappearing due to sdcard issues? I know other roms have issues. Xda free is one app that I have issues with on the aokp build if I don't move it to internal.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
There's a lot of different code and drivers between this and the sgt7 builds, I have not had any problem with the sd card on it.
Sent from Outer Space
liquidzoo said:
Nice! I'll give this a try.
Question, though. Any issues with apps disappearing due to sdcard issues? I know other roms have issues. Xda free is one app that I have issues with on the aokp build if I don't move it to internal.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
I haven't seen a single sdcard issue yet
can you show us some pics please?
hi tony,
what is diferrent of this rom with your rom at other thread? thanks
http://forum.xda-developers.com/showthread.php?t=1966894
maxdown said:
hi tony,
what is diferrent of this rom with your rom at other thread? thanks
http://forum.xda-developers.com/showthread.php?t=1966894
Click to expand...
Click to collapse
The other is a build built with the sgt7 changes like demetris_i's builds, and this one is built off of the CodefireX repos with those extras.
Warren87 said:
can you show us some pics please?
Click to expand...
Click to collapse
I don't understand why people want pics so much, it's exactly the same appearance as all the other normal cm10 roms. It has simple multi-dpi interface compared to paranoidandroid, it has a different extra settings interface like aokp, other than those.. Nothing is different
Sent from Outer Space
Got a error message
got a error message "Warning: No file_contexts" when flashing with CWM 6.0.1.5 ,will re-download to see if that is the problem.
update: same error with new download file.
tonyp23 said:
Disclaimer: I will not be responsible if you brick your NT or your significant other leaves you for bricking theirs. As always, flash at your own risk.
Here is a full codefireX (cfX) ROM with 1.2GHz OC that is 5 touch enabled. You can use this with the 2 touch or 5 touch firmware, kudos to mik_os for the driver that does so.
codefireX is sort of a mixture between AOSP, AOKP, and CM10.
Here is their git: https://github.com/codefireX
Here is my kernel git: https://github.com/tonyp23/android_kernel_acclaim
Features:
Click HERE for a full cfX settings feature flowchart by BananaGranola (thank you)
NOT simply a re-named CM build
Built with a custom toolchain, strict aliasing, -O3 completely (including thumb_cflags), and other Linaro optimizations such as OOM/LMK changes.
Lots of extra settings in the codefireX settings panel
Please see this post on how to install the updated firmware if you'd like to have 5-touch. http://forum.xda-developers.com/show...9&postcount=75
With that said, many huge thanks to everyone who has put so much effort into making this awesome. If I forgot you, let me know!
Kuzma30, chrmhoffman, mik_os, fattire, Hashcode, Rebellos, demetris_I, Succulent, CelticWebSolutions, eyeballer, Bauwks, CM team, TWRP team, codefireX team, TI, BN
Here's general instructions on how to proceed
1. Update touch firmware if you choose
2. Install CWM 6.0.1.5 using fastboot
3. Wipe data/factory reset, wipe dalvik cache
4. Install ROM
5. Install newest gapps from goo.im
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip.md5sum
Click to expand...
Click to collapse
Vector2nds said:
got a error message "Warning: No file_contexts" when flashing with CWM 6.0.1.5 ,will re-download to see if that is the problem.
update: same error with new download file.
Click to expand...
Click to collapse
Which file are you downloading?
liquidzoo said:
Which file are you downloading?
Click to expand...
Click to collapse
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-c...AL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-c...aim.zip.md5sum
Downloaded both and put in sd. Seems to boot ok, already installed gapps 4.2. Besides the weird error at flash, the rom seem faster in titanium restore.
Vector2nds said:
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-c...AL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-c...aim.zip.md5sum
Downloaded both and put in sd. Seems to boot ok, already installed gapps 4.2. Besides the weird error at flash, the rom seem faster in titanium restore.
Click to expand...
Click to collapse
I also got the 'No File Context' warning when I flashed the ROM. I ignored it and it seems to not have caused any problems.
My experience also was that Titanium restore was *much* smoother and quicker with this ROM than with other CM10s for Nook.
It seems to be a nice, stable build so far.
I did get the error where the WiFi signal won't show up in the status bar. I've had no luck getting it to appear, but WiFi works just fine.
timpilcher said:
I also got the 'No File Context' warning when I flashed the ROM. I ignored it and it seems to not have caused any problems.
My experience also was that Titanium restore was *much* smoother and quicker with this ROM than with other CM10s for Nook.
It seems to be a nice, stable build so far.
I did get the error where the WiFi signal won't show up in the status bar. I've had no luck getting it to appear, but WiFi works just fine.
Click to expand...
Click to collapse
Yes you can safely ignore that error, confirmed by the main developer.
Also if you have the bizarre wifi bars bug you can still use the text meter
Sent from my Barnes & Noble Nook Tablet using XDA Premium HD app
Somethings that could interfere or not needed
I notice in settings>codefirex>theme tweaks>status bar ..."Show Brightness Toggleslider" if checked get in the way of status bar view and Show Wifi network is check then that just duplicates AP name what on the bottom of status slide down menu. I don't have Dual-pane view or Force tableUI checked, so it may look different if you have those checked. I didn't get any errors on wifi but I did edit Widget buttons in settings>systems>notification drawer>widget buttons... checked and uncheck the widget I want and don't want. There also a half blue line on right top of the navigation bar.,,strange...sometime there's little dots trailing from the right side of the screen to that blue line.
Update:
Toggle the check box back and forth for "Hide signal bars", this will show the wifi signal in the status bar. Make sure that "Six bar signal icons" check box is not ckecked.
I don't know if this a new feature or an old feature that I just didn't notice is the power button that you can set for on demand deep sleep in Navigation bar; button#, action & icons.
Ok that blue bar on the bottom right corner that I mention earlier that I thought was weird is called the battery bar. Three games that I had no success in the past now two works.
Major heating issue charging while in use (interactive mode) is now controlled where I don't have to change to "conservative mode"while in use. Excellent
I have to say this hybrid ROM is the BOMB!!!!! LUV UV UV it. ...............so far, still testing.
schmooth
How i can flash rom so dont change UDID .
My game online is gone ( . i must play again (
Deep Sleep Results Update
Ok , before anyone of yousse Doctors get snippy at me, I'm not debating if others have different results base on their own findings.
Here my Diagnosee..eee.eeee after deep sleeping the NT16 for more than eight (8) hours using the power button on the navigation bar to deep sleep on demand, it loss one (1) percent or less because I woke it four (4) hours before to check with cpu spy. I screwed up the first video recording and that why you don't see the wifi zero signal to signal on and sd showing mounting in process.
What do you think Doctors?, here the video of the results
Update: There is still a heat issue in interactive mode plugin power while in use but not as extreme where I had to put it in a freezer to cool off. I guess if come with OC territory.
ryan.nguyentran said:
How i can flash rom so dont change UDID .
My game online is gone ( . i must play again (
Click to expand...
Click to collapse
Titanium Backup (as long as it's installed before you change a ROM) will restore the UDID. I know the Pro version does this, not entirely sure about the free version.
App data usage
I notice that gapps was taken alot of the data memory so I froze both gapps and it services in titanium backup then defrost it to clear for more Free RAM showing. I'm hoping this would improve battery if I clear it Settings>Data usage ; apps listed. Is there any utilities in cm10 that would disallow apps to background in memory?
Ok, I found it while typing this message. Settings>Developer option>Background process limit . I wonder if I set it to No background processes would work and check Settings>Developer option>Don't keep activities work. Hopefully this will reduce battery drain.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
------------THIS IS AN UNOFFICIAL UNSUPPORTED BUILD-----------
This is my attempt at porting CyanogenMod 11 to the Galaxy Tab 4 10.1. I use a SM-T530NU, so that is the only device I have tested.
Any other device variations have not been tested and are at your own risk. I will not be able to support other variations as I don't own them for testing.
Special thanks to MetaIIica - I have been using his Alpha build of PAC-ROM KitKat since December. I studied the code for that, along with stock and some other ROMs before starting this port. This is my first time doing any work with Android, so I'm not sure if I'm technically doing things correctly or not.
I know CyanogenMod 12 is under development already, but I have decided to do a CM11 based build in hopes of a making a stable daily driver offering. I have fixed many of the issues present that were present in the PAC-ROM build. They can probably be backported to PAC-ROM easily if its built with my tree, but I prefer the plain CM-based offering myself.
You may get the source of my changes for this ROM on my github. If you'd like to help and submit a patch, feel free to open a pull request. You will of course be credited accordingly.
See below for instructions, what's working, and issues I fixed over the PAC-ROM Alpha.
For any bug reports or feature requests, please use the appropriate tabs at the top of the thread. Please include as much information as possible and if possible a logcat or other debug information in the case of bugs. Requests for supporting other device variations will not be honored - sorry,
Feedback and constructive criticism is always appreciated. I hope you enjoy using the ROM; if you use the ROM, please consider leaving a thanks, rating, and/or review
CURRENT VERSION:
DOWNLOAD LINK - 04/26/2015
OLD VERSIONS:
DOWNLOAD LINK - 04/20/2015
DOWNLOAD LINK - 04/19/2015
DOWNLOAD LINK - 04/07/2015
DOWNLOAD LINK - 04/05/2015
DOWNLOAD LINK - 04/04/2015
DOWNLOAD LINK - 04/03/2015
DOWNLOAD LINK - 03/29/2015
DOWNLOAD LINK - 03/24/2015
DOWNLOAD LINK - 03/23/2015
DOWNLOAD LINK - 03/22/2015
INSTRUCTIONS
- Install PhilZ Touch Recovery (recommended)
- Copy CM11 & GAPPS (Optional) ZIPs to your SDCard
- Boot into Recovery
- Do "Clean to Install a New ROM" (FULL WIPE REQUIRED INCLUDING SYSTEM, NOT JUST DATA/CACHE - even if coming from another CM-based ROM, as my device tree is different)
- Flash CM11 ZIP
- Flash GApps zip from SDCard
- Reboot
UPGRADING
-In general, you should be able to just flash over the previous build, but if you encounter any weird issues please clean using the steps above
Working that I've tested:
Audio: Speakers, Headphones, Bluetooth
Bluetooth
CIFS/NFS (Network File Systems - see notes below)
Front Camera
GPS
IR Blaster [SM-T530NU Only]
Magnetic Cover Sleep/Wake
MTP
Rear Camera
USB OTG
Video (w/ Hardware Decoding)
WiFi (2.4ghz & 5ghz)
NOTE ON BUTTONS: This ROM is configured to use the hardware buttons-- so you won't see the software buttons taking up space at the bottom of the screen, as they are disabled. This is not a bug. Use the hardware buttons, as they are the same. If you really want the software buttons for some reason, edit /system/build.prop, change qemu.hw.mainkeys to 0, save, and reboot. If you map the menu button to a long press of another button, some apps such as TitaniumBackup will count this as a hardware key and hide their soft menu button - but only after a reboot.
NOTE ON CIFS/NFS: Many of the mounting utilities on the play store are outdated and broken due to changes in the linux kernel. For best luck, mount using the command line. For CIFS, you can tweak CIFSManager into working - see this thread
CHANGELOG:
[04/26/2015]
-Fix reading MAC address from EFS
-Fix suspending charging while the device is off (special thanks to @sub77 for pointing out the right config option)
[04/20/2015]
-Enable physical keyboard menu for use with BT/USB keyboards. Auto hides soft keyboard & allows selection of layout.
[04/19/2015]
-Add support for magnetic cover sleep/wake
[04/07/2015]
-Roll back to using the Non-CAF Display HAL Fixes SurfaceFlinger constantly eating 100% CPU
[04/05/2015]
-Fix issues with reconnecting Bluetooth Devices after a reboot (if upgrading, break pairing and re-pair all devices)
-Fix mounting /efs
-Fix persistant Bluetooth MAC Address
[04/04/2015]
-Fix issues with detecting whether or not the device has a hardware menu button.
[04/03/2015]
-Fix the Time Service, allowing Date & Time to persist during a reboot without a wifi connection. Special Thanks: sub77 for pointing the discussion in the thread in the right direciton on this
[03/29/2015]
-Support Bluetooth Audio & AVRCP
-Support Consumer IR [SM-T530NU Only]
-Upgrade Display HAL to CAF Version
-Misc Bugfixes and Cleanup
[03/24/2015]
-Fix Missing Sensors HAL (Fixes Autorotate regression from the last build)
-Behind the scenes work for IR (need someone to test on plain 530 as IR is NU only). Does not actually work yet because its using the stub HAL, but the kernel drivers are loaded, and the IR service runs.
[03/23/2015]
-Fix lighting issues with rear camera
-Reduce some dependencies on vendor libs.
[03/22/2015]
-Added support for Front/Back Camera
-Added support CIFS/NFS
-Fixed 5 ghz WiFi
-Fixed Duplicate VSYNC spam in logcat
-Fixed issues with video decoding (YouTube HD, MXPlayer HW+ Video, etc)
-Fixed various Bluetooth issues
-Fixed wallpaper issues with Trebuchet
-Identify device correctly as MSM8226 chipset
-Use Hardware Buttons by Default
XDA:DevDB Information
CyanogenMod 11 Unofficial [TM-530NU], ROM for the Samsung Galaxy Tab 4
Contributors
starlightknight
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-03-29
Beta Release Date: 2015-03-22
Created 2015-03-29
Last Updated 2015-04-25
Congratulations ! :good:
Nice ROM, it installed fine on my T530 will test some more, thanks for the hard work
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Time for a new test, i'll test it in my t530 and report back the results.
Sent from my GT-I9300 using XDA Free mobile app
steve30x said:
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Click to expand...
Click to collapse
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
starlightknight said:
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
Click to expand...
Click to collapse
I always completely wipe everything before installing a new rom. Never wiping the tablet before installing a new rom might cause problems. I no longer have the rom installed. I will install it again and see if it was just a flike that it didnt work properly the last time. I also have Philz recovery installed because its the only one that has full brightness on the screen.
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! Glad to hear that it is working well for you. I believe the only difference between the SM-T530 and the SM-T530NU is the the NU has an IR blaster, which I haven't actually enabled yet. I need to figure out how to test that because I never use it. After i do that and post a build with IR, it will be useful if you check and make sure it doesn't break the regular 530. Those two from what I can tell are vary similar, its more of any celluar varients that I would be worried about, because this is build for wifi only..
Let me know if you find anything broken
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
steve30x said:
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
Click to expand...
Click to collapse
Glad its working for you now
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
starlightknight said:
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Click to expand...
Click to collapse
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
starlightknight said:
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
Click to expand...
Click to collapse
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Gustave17 said:
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Click to expand...
Click to collapse
The GAPPS package I modded is only 76MB. Its just the bare essentials
steve30x said:
The GAPPS package I modded is only 76MB. Its just the bare essentials
Click to expand...
Click to collapse
Oh ok, so it's what we need...
Y
steve30x said:
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Click to expand...
Click to collapse
I used an aroma based gapps. You can install only what you need. About using YouTube without gapps, i dont know if tubemate could do the trick. Use aptoide to install it if you dont like play store. Here is the link for the aroma gapps: http://forum.xda-developers.com/showthread.php?t=2547250
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Click to expand...
Click to collapse
It has something to do with the lighting detection or some other initial initialization that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
starlightknight said:
It has something to do with the lighting detection that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
Click to expand...
Click to collapse
Tested and working fine. Is a nice workaround. I dont mind about this bug as I only use front camera for Skype and such things, but im glad this workaround is pretty easy and fast
Sent from my GT-I9300 using XDA Free mobile app
Hi Everyone,
I updated the original post with a new build. This build should fix the lighting issues with the rear camera the first time it is used. After I debugged the mode switching with logcat I was able to find out what the issue was. I also am working on reducing dependencies on vendor libs where possible by getting more of the modules that can be built from source building from source.
I've started exploring IR blaster support for NU users and I am continuing to look for a solution for bluetooth audio, but I don't have either yet. Stay tuned for future updates
If you already installed the ROM most times you should be able to flash over it, but if you see anything weird after, try wiping to confirm if its a bug or weirdness after upgrading (you can always nandroid before wiping if you're unsure and roll back if its not related to upgrading).
Please let me know if you find any issues. Include model number and if possible a logcat as well.
Enjoy!
Congrats starlightknight!
Anyone tried this on the SM-T530?
This is a port of Cyanogenmod 13 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.
This ROM is stable enough to be my current daily driver, however please take note of the issues noted below. Feature are on par or exceeds my OMNIRom builds in terms of features and performance. However do note that CyanogenMod has a lot more features and brings about its own bugs as well.
Based off on Cyanogenmod 13 sources which is based on Marshmallow 6.0.1
Device Tree:
=========
Device: https://github.com/jedld/device_samsung_gtexslte.git
Vendor: https://github.com/jedld/vendor_samsung_gtexslte.git
Kernel: https://github.com/jedld/kernel_samsung_gtexslte.git
Update Jan 28, 2017
===============
New XTRM build released. Overview of changes:
* kernel and framework built with -O3 compiler flag for deeper linaro optimizations
* Video recording now works
* Added I/O scheduler support to the kernel
* reduced OC to 1.54 from 1.56 (actually faster at this clock)
Update Jan 16, 2017
===============
CM 13 Xtreme builds now available! See section below for details.
Update Jan 07, 2017
===============
A build with SELinux enforcing and support for F2FS in the data partition is now available. If SELinux security is important for you and if you want the Filesystem performance benefits that F2FS brings, I invite you to check it out the section below. Note however that a Data Wipe is necessary.
Update Dec 14, 2016
===============
- Fixed hardware acceleration for some videos (lower power consumption in YouTube etc.)
- Fixed crash when a call has ended
- ScreenRecorder/ScreenCasting now works.
- Added reboot menu options (Needs developer mode)
Works:
- Wifi/SMS
- Audio
- Graphics
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
- Bluetooth
- Camera (stills) - but video works in xtrm-20170128
- LTE
Bugs/Known Issues
*Unable to record video using camera* (Fixed in xtrm-20170128 build)
*FM Radio crashes*
*gps unable to get a fix*
*poor sound volume (can possibly be fixed by sound mod add-ons)
*speakerphone issues during call*
Other Notes:
- selinux permissive (There is a special build with selinux enforcing in the section below)
@Vagr9K has a fix for gps issues here: https://forum.xda-developers.com/showpost.php?p=71999226&postcount=42 thanks1
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 6.0.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. Or click here for the latest version.
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)
Finally if you enjoyed this ROM and like what I'm doing, hit the thanks button or better yet hit the donate button.
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.
Using the F2FS and selinux enabled version (WIPE Required)
-------------------------------------------------------------------------
Recommended to move over to the Xtreme build instead (01/17/2016)
1. Flash the custom F2FS version of TWRP for the SM-T285 here using Odin/Heimdall. If coming from another ROM or even a non F2FS version of CM you need to format your data partition to F2FS using this twrp so make sure you take the necessary backups.
2. Download an flash using Odin/Heimall CM 13.1 F2FS Edition here.
Other Notes: Antutu Scores for reference (6.0.1, F2FS) : Overall: 25830, 3D: 914, UX: 10397, CPU: 10606, RAM: 3913
Xtreme Edition Builds
=================
Xtreme Edition builds are aggressively optimized and possibly unstable builds (though I do test them for some time to ensure minimum stability). Warning this build is only for enthusiasts that want to tinker settings to achieve the best performance possible for this device (using Kernel Auditor is recommended). Speed should be noticeable especially when coming from stock or non optimized builds.
Feature List:
* Kernel and system files compiled with the latest linaro toolchain 6.2.1 with -O3 optimization
* Additional hotplug and CPU governors installed (tweak with your hearts content with Kernel Auditor)
* Max clockspeed slightly bumped to 1.54Ghz from 1.5Ghz
* Various speed optimization patches to the kernel
* Support for KSM (Kernel same page merging)
* Support for both Ext4 and F2FS for the data and cache partitions (Use TWRP to switch to your desired FS)
* SELinux enabled
* ExFAT and NTFS support built-in
* Improved doze and low power mode support
* Antutu Score 26325 (KSM disabled, IntelliPlug Enabled, F2FS data and cache partitions)
* USB Audio/MIDI support (untested)
* Added new I/O schedulers (row, bfq etc.)
* Other optimizations and fixes I can't remember
For GPL compliance please look at the github source above, kernel sources for Xtreme builds are under the performance branch.
Issues
-------
Known issues are the same with the standard build (e.g. video recording not working etc.) However due to aggressive kernel changes this build may not be as stable as the standard build.
Download & Installation
-------------
This build supports both Ext4 and F2FS filesystems so a wipe isn't strictly necessary unless you want to switch filesystems using TWRP. However I won't be responsible for data loss, so make sure you make the necessary backups.
Grab the latest build here
If you haven't updated TWRP, get the latest build with F2FS support and the latest kernel here.
Root and customization
===================
Cyanogenmod already comes with its own root mechanism, you have to enable it in developer settings though.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CyanogenMod 13 Samsung Galaxy Tab A 7 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld, @koquantam - for pioneering the work on spreadtrum devices
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-12-12
Last Updated 2017-01-28
awesome work jedid...this is so fast...the omni feels slow
speakerphone still does not work but not a big deal at the moment
theme manager too! and it works!
checked data, calls in and out , sms, mms, wifi (of course you had already said it works..just 'reporting')
thanks!
mac231us said:
awesome work jedid...this is so fast...the omni feels slow
Click to expand...
Click to collapse
Must be a good thing if it makes Omni feel slow
Love your work jedld !!
jedld said:
Must be a good thing if it makes Omni feel slow
Click to expand...
Click to collapse
one thing-theme manager crashing (clearing its cache and data did not help) but this started only after installing one theme and then switching over-wish there was a simpler list view vertical rather than the horizontal intensive scroll view-anyway it crashes and keeps resetting the view to the first default theme when I go in (try to scroll sideways and it will not as it crashes and comes back to the first system default theme)-resetting to default system theme did not stop the crash reports..popups of it stopping keep coming and am not able to do anything with the theme chooser....not sure I downloaded too many themes or what-will remove some themes to see if it changes anything
lte/h+ icon in status bar varies in its presentation-will sometimes show up sometimes won't even when on mobile data (and the data works)...thought at one point I saw both that and the wifi icon showing (wifi was on then) (changing clock position did not help)
When adding a contact, and choosing a photo the screen changed automatically to automatic live display mode (when I had it turned off)..the color shading changed completely of everything indicating a filter of sorts (which is what the live display does I think among other things)
not sure if these are consistent but will try again (maybe even resetting and starting all over-unless you know of any of these or have any insight into them) thanks!
also like omni...process phone stops sometimes on ending a call not a big deal but just reporting
how to extract system
how to extract system.img iam tried ext4 extrctor and tool can,,t extracting.. i want port it my device
muralivijay said:
how to extract system.img iam tried ext4 extrctor and tool can,,t extracting.. i want port it my device
Click to expand...
Click to collapse
system.img is a sparse ext4 image. You need to use simg2img and mount it as an ext4 filesystem. What device do you want to port it too? This works only for the SM-T285 right now.
Xolo era 4g sc9830 spreadtrum
muralivijay said:
Xolo era 4g sc9830 spreadtrum
Click to expand...
Click to collapse
I see. Though you probably need to be able to build a new kernel and boot image for this to work though, I doubt just flashing the system image would just work.
Though I'm surprised this spreadtrum phone is still at android 5.1 this december 2016 when clearly we can go up to 6.0.1 with minimal problems
jedld said:
I see. Though you probably need to be able to build a new kernel and boot image for this to work though, I doubt just flashing the system image would just work.
Though I'm surprised this spreadtrum phone is still at android 5.1 this december 2016 when clearly we can go up to 6.0.1 with minimal problems
Click to expand...
Click to collapse
my phone already updated to marshmallow .. and cm 13 is marshmallow based rom. so my marshmallow kernel will work . iam know some porting guide for spreadtrum ....
muralivijay said:
my phone already updated to marshmallow .. and cm 13 is marshmallow based rom. so my marshmallow kernel will work . iam know some porting guide for spreadtrum ....
Click to expand...
Click to collapse
I see. If you want a guide on extracting system images, you can refer to this one I made here.
jedld said:
I see. If you want a guide on extracting system images, you can refer to this one I made here.
Click to expand...
Click to collapse
iam already by your guide extracted thanks .. i needed help . i have compiled twrp from cm 13 and omni 6 source twrp not going to ui (not booted ) .... i got my log "fb swap active fail: invaild aruguments " help please .. how to fix it ... and i want custom recovery for my device
muralivijay said:
iam already by your guide extracted thanks .. i needed help . i have compiled twrp from cm 13 and omni 6 source twrp not going to ui (not booted ) .... i got my log "fb swap active fail: invaild aruguments " help please .. how to fix it ... and i want custom recovery for my device
Click to expand...
Click to collapse
There seems to be a thread about that here. Might going off-topic though just PM me for if you need more help.
jedld said:
There seems to be a thread about that here. Might going off-topic though just PM me for if you need more help.
Click to expand...
Click to collapse
tried patch still i got this error in my log
mac231us said:
When adding a contact, and choosing a photo the screen changed automatically to automatic live display mode (when I had it turned off)..the color shading changed completely of everything indicating a filter of sorts (which is what the live display does I think among other things)
Click to expand...
Click to collapse
Not sure if it is a cyanogenmod bug or mine. I've updated again with the latest nightly maybe it will be fixed.
also like omni...process phone stops sometimes on ending a call not a big deal but just reporting
Click to expand...
Click to collapse
That crash, should now be fixed in the latest build.
ROM is actually usable for me now as a daily driver and have since switched from OMNIRom.
jedld said:
Not sure if it is a cyanogenmod bug or mine. I've updated again with the latest nightly maybe it will be fixed.
That crash, should now be fixed in the latest build.
ROM is actually usable for me now as a daily driver and have since switched from OMNIRom.
Click to expand...
Click to collapse
awesome! thanks..downloading now (the theme chooser crash occurs now and then when switching between themes but no big deal-there are some themes that have issues but that is a different matter nothing related to this excellent rom...it seems switching back to the base theme creates issues but not trying this anymore for fear of getting stuck-backups always are useful)
jedld said:
Must be a good thing if it makes Omni feel slow
Click to expand...
Click to collapse
One thing though about the CM ROM (versus the OMNI)
If on call, the person at the other end will hear his echo
I tested this myself, knowing this issue from CM/AOSP/Resurrection etc from Tabpro 8.4 etc devices (all of this tablet phone types where the speaker/microphone arrangement placement I believe is different from regular smartphones)
on Tabpro and this was on 4.4 and 5.0.2, I had to adjust some values in an audio mixer file (not just the gains as lowering gain would reduce in-call volume too but actually turned one microphone off to use another) (top microphone versus the lower one but turn on gain so person at other end could hear..something like that if I recall correctly from early 2015..nothing was perfect though)
Here on Omni and CM I reported the speakerphone as not working. However, and this is more evident in the CM rom, the caller's voice at the other end is unusually loud and moreso does not sound like coming from the internal in-call speaker but from the external speaker, albeit at a very low volume. (like the Xperia Z3 Tablet compact that does not have a separate speaker for the call and uses the regular media speaker at a very low volume, though folks have said it is loud enough that other people can hear what is being said by the caller (to your phone). This sounds like that on the CM ROM...and therefore this is picked up by the microphone that then is heard as an echo for the caller (hearing his/her own voice). In the OMNI, this is not there i.e. I do not hear echo on my 'caller' phone (once I move suffiicient distance away from the device with my 'caller' phone)..on the CM it does not go away...when people are speaking rapidly they will not hear the echo usually but if they pause and say things slowly or say single words they could hear echo of their voice.
I am restoring the OMNI backup I had to check it again and copy out the system/etc/audio files to see if there is any difference with the CM
I think something can be changed in the audio files to make use of the speaker and microphones correctly (may also fix speakerphone issue)
This is a perennial issue on almost all CM/non-stock ROMs for Samsung tablet phones (think even the tab S had this issue with CM and so did the T235)...even OneplusOne (which used CM on some of its models) though there I am surprised the users had this issue
..although like on Note 1, Note 2 I never had this issue...suspect it is because of tablet phone differences in the speaker and microphone layout
maybe I am not wording or describing this properly or just that I could be wrong but thought I'd post this
EDIT: Yes tried the OMNI again and it works just fine..no echo
EDIT2: I swapped the OMNI etc folder audio files for the CM and now the echo has gone (so just like Omni...had 2 long calls today-one caller I know is very audio-sensitive and picks up the echo quickly-no complaints!) still trying to understand why this 'worked'
mac231us said:
One thing though about the CM ROM (versus the OMNI)
EDIT2: I swapped the OMNI etc folder audio files for the CM and now the echo has gone (so just like Omni...had 2 long calls today-one caller I know is very audio-sensitive and picks up the echo quickly-no complaints!) still trying to understand why this 'worked'
Click to expand...
Click to collapse
Glad to see that someone is actually using this device for making calls, I use the SM-T285 as a secondary device so i don't use it for calls as much. I appreciate that you are taking the time to test this things. Interesting find on those etc files, I'll try to perform a diff to find out, unfortunately CM makes much more tweaks to stock android than OmniRom does and it makes it hard to figure out where the bugs are coming from.
jedld said:
Glad to see that someone is actually using this device for making calls, I use the SM-T285 as a secondary device so i don't use it for calls as much. I appreciate that you are taking the time to test this things. Interesting find on those etc files, I'll try to perform a diff to find out, unfortunately CM makes much more tweaks to stock android than OmniRom does and it makes it hard to figure out where the bugs are coming from.
Click to expand...
Click to collapse
well...something else..on CM only not OMNI there is a quirk...say I put the phone on call forwarding it will show a call forwarding icon in the status bar which is what is expected...however on reboot that icon may disappear...I missed couple of calls having put the device on call forwarding to my work phone (as it gets a certain carrier coverage Verizon in some work areas where my personal provider ATT does not have)...then forgot about it, put it on mute, and was using the Tab not knowing it was on call forwarding (as sometime during the day I had rebooted and the icon had disappeared)
Further, this also happens like say I am on call forwarding on omni or stock and then went to twrp and restored a cm backup...when the phone comes back on restored with the cm backup the call forwarding icon may have disappeared (does not happen say with call forwarding established on cm, then restored omni backup..the icon remains in omni)
what is disconcerting is if I go into call forwarding it shows that I am not on it (although I am) and actually allows me to turn on call forwarding! (and then turn it off i.e actually disable it if I want to)
also it seems another 3 times I have missed calls on CM...seems the signal drops off more on CM (maybe a rendering thing on signal bars but in checking the signal db and band it does seem weaker)
so for now going back to Omni..although I miss the theme manager and the font changing with your own fonts (not like inbuilt in some font app like fontser) (manual replace of Roboto-regular.tff in system/fonts works to change the font in Omni)
mac231us said:
well...something else..on CM only not OMNI there is a quirk...say I put the phone on call forwarding it will show a call forwarding icon in the status bar which is what is expected...however on reboot that icon may disappear...I missed couple of calls having put the device on call forwarding to my work phone (as it gets a certain carrier coverage Verizon in some work areas where my personal provider ATT does not have)...then forgot about it, put it on mute, and was using the Tab not knowing it was on call forwarding (as sometime during the day I had rebooted and the icon had disappeared)
Further, this also happens like say I am on call forwarding on omni or stock and then went to twrp and restored a cm backup...when the phone comes back on restored with the cm backup the call forwarding icon may have disappeared (does not happen say with call forwarding established on cm, then restored omni backup..the icon remains in omni)
what is disconcerting is if I go into call forwarding it shows that I am not on it (although I am) and actually allows me to turn on call forwarding! (and then turn it off i.e actually disable it if I want to)
also it seems another 3 times I have missed calls on CM...seems the signal drops off more on CM (maybe a rendering thing on signal bars but in checking the signal db and band it does seem weaker)
so for now going back to Omni..although I miss the theme manager and the font changing with your own fonts (not like inbuilt in some font app like fontser) (manual replace of Roboto-regular.tff in system/fonts works to change the font in Omni)
Click to expand...
Click to collapse
What file would I tweak to make this ROM louder?