Related
USE THIS AT YOUR OWN RISK.
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
Very slight speed increase in bootup, possibly in other areas
Support for init.d script parsing on bootup
A real busybox (with proper links) installed to /sbin (and therefore available to the system)
Undervolting and minor overclocking support (via SetCPU)
android ram_console support (useful for post-mortem of crashes.)
standard boot animation support
quicker charging with iphone chargers
Voltage and Clock Adjustments:
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://forum.xda-developers.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
Known Issues:
Probably not compatible with stock firmware updates. (won't fix.)
NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
Flashing Instructions:
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.
Change Log
20120128:
Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
20120123: (actually posted on the 24th)
Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
20120107:
disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
20120105:
added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
20120102:
added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
20120101:
undervolting and overclocking support (only up to 1.4GHz)
If you decide that you want to overclock or undervolt your tablet, you are 100% on your own. You can easily fry your tablet's processor by messing with voltages and clock speeds. If you have issues with this kernel, remove all overclocking and voltage adjustments before you even bother posting on this thread.
Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://forum.xda-developers.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
20111231 (initial release):
build compatible with stock ar6000.ko module
init.d script support
busybox in /sbin
cleanup of kernel config to remove excess debugging (when possible)
Frequently Asked and Anticipated Questions
Q: Will this work with the GT-P6200, GT-P6200L, or SGH-T869?
A: No
Q: Can you make a kernel for the GT-P6200, GT-P6200L, or SGH-T869?
A: I probably could if I had the hardware to test with. Without a sample of hardware, I can't even begin to guess if what I've done already will work, or what it might take to make it work. If you really want me to do one of those devices, please feel free to send me one. (Making a recovery kernel is quite a bit easier as it doesn't have to work with the ethernet, sound, modem or any other drivers.)
Q: Why doesn't this kernel include CWM Recovery?
A: On the GT7+ devices, the recovery boots from a completely seperate partition than the normal boot. When the device boots recovery, the normal boot kernel isn't ever loaded (and vice versa.) Therefore, it doesn't make sense to package them together.
Q: Why is the sky blue?
A: Please refer to: http://www.sciencemadesimple.com/sky_blue.html
reserved for even more future use
Nice.... I installed just fine. Will Play around and let you know. Thanks further kernel....
Sent from my GT-P6210 using xda premium
Nice to see! Now have a good reason to install clockwork recovery! Thanks Gary!
PLEASE IGNORE THE SIGNATURE!
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
PLEASE IGNORE THE SIGNATURE!
Click to expand...
Click to collapse
Wow, that actually made me laugh out loud. (My wife just ran in to ask if I was alright.) Thank you.
I've got a new and improved signature modified especially for you! Glad to have made you laugh! Happy New year Gary and fellow community members! I wish you and your families happiness and good health!
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I know kernels can have an effect on colors. Gary does your kernel improve color and if not could you possible hack that part of the kernel to improve in future releases, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update? I know that we have to odin back before we can update in kies but not sure about the other two questions, any help would be appreciated, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update?
Click to expand...
Click to collapse
Probably, but I didn't try it. Let us know how it works out.
Thanks Gary! Recovery is up and running and even made a nandroid. I located it to make sure everything worked (took a really long time). I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel? Thanks for your development! Much appreciated
Sent from my GT-P6210 using xda premium
Just flashed and it feels very smooth so far thanks!
Sent from my GT-P6210 using xda premium
mike216 said:
I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel?
Click to expand...
Click to collapse
What framework are you referring to? I try very hard to make the stuff I do "self contained", so if a cache should be wiped, it either gets wiped automatically, or there's a message displayed telling you to do it manually.
In context of this thread, there's no need to wipe any caches before installing this kernel.
Perhaps your question is in reference to something in another thread?
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
The framework zip I was talking about was the flashable zip you put together for the theme here in the development section.
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
A kernel is not a ROM, two totally different things and you don't need to wipe to install one. An easy explanation of the difference is a kernel is what runs the hardware (cpu, memory, etc.) and a ROM is just a UI (user interface).
With ROMs the general concensus on wiping is you need to do a full system wipe as well as wipe the dalvik cache if you are switching between ROMs, say from ROM A to ROM B but do not need to wipe if it's just an incremental update say ROM A to ROM A.1 unless advised to do so by the dev.
Awesome work Gary. If I had the knowledge to do this I would. Tab feels great.
Just glad to see some little development finally kicking off.
Sent from my ICS'd themed Galaxy Tab 7+
Glad you finally got things working.
Closed-source modules piss me off... Module versioning enforcement can get even some of the best devs (netarchy and I kept missing each other on IRC, it took a week before we figured out why his Infuse kernels wouldn't boot.)
Samsung is good about releasing kernel source in a timely fashion, but they SUCK at fixing broken source releases.
(Edit: WTF? They included BCM4330 source code in your release but NOT the Atheros 6k drivers?)
Edit: This might be useful, not sure - http://linuxwireless.org/en/users/Drivers/ath6kl
After lots of testing I do find its a little quicker! Don't know if its placebo but it sure feels fast. Nice work Gary. Recovery working great but the only odd thing I noticed was how long it took to do a nandroid backup. For a minute there I thought it froze up. All is good thought
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
ThrillsKernel for the Acer Iconia TAB A510
version 2012-11-18, built from source
Here it is, the first ever non-stock kernel for the Acer Iconia TAB A510, dubbed the "ThrillsKernel"!
What's in this kernel:
Comes in two flavors: V2 for ICS ROMs and V3 for JB ROMs
Removed 'Samsung EMMC brick' bug: This prevents your internal memory from becoming corrupted.
CPU Governors: Interactive, conservative, ondemand, powersave, userspace, performance, SmartassV2 and lulzactive.
I/O schedulers: Noop, deadline, CFQ, Simple I/O, V/R and BFQ.
Removed Acer mount security: Now you can mount system as r/w.
NTFS, CIFS, and MD4 support
Tegra3 optimizations
Various other performance tweaks
Installation:
Step 0:
Check this thread to see if you can help the community before you let us help you!
Step 1:
If you don't have it already, install my CWM-Based Recovery.
Step 2:
Download the kernel from this post, extract the .RAR files and put the .ZIP file on your internal or external SD Card.
Step 3:
Start Recovery by powering down your device, holding the Volume down (**) button and turning it on again.
Step 4:
Make a Nandroid Backup. I can't stress this enough. Select backup and restore and choose one of the backup options.
Step 5:
Install this ROM by choosing install zip from sdcard and then choose zip from sdcard or choose zip from external sdcard.
Step 6:
Wait for the installation to finish (this takes a few minutes). Spend your time reading the text below these installation instructions!
Step 7:
Select wipe dalvik cache from the advanced menu, thenreboot system now, and enjoy!
Please read the following carefully before installing this kernel:
I am not responsible for anything you do to your tablet. Whatever you do, you do it at your own risk!
Which version should I install?
ThrillsKernel2 is built on the 2.6.39 linux kernel and intended for A510 tablets with a ICS ROM installed. That's Android version 4.0.0, 4.0.1, 4.0.2, 4.0.3 or 4.0.4.
ThrillsKernel3 is built on the 3.1.10 linux kernel and intended for A510 tablets with a JB ROM installed. That's Android version 4.1.0, 4.1.1 or 4.1.2. There is no support for 4.2+ yet.
FAQ:
Want to use ThrillsKernel in your own ROM? Go ahead, make my day.
Need ***** added to the kernel? Let me know, and I will try!
Want to remove the kernel from a NoThrills ROM? Although it's not recommended, it's possible. Check the instructions in the respective ROM thread.
Want to give me your first born baby? I'd rather not have that, but if you really want to give me something: Either click the 'Donate to me' button on the left, or simply hit the 'Thanks' button on this post.
Changelog:
The ThrillsKernel has the date as version number, e.g. version 20121118 is November 18th, 2012. You can check the status (or changelog, whatever you will) of the kernel by visiting the commit history of my github page:
Click here for updates to ThrillsKernel2
Click here for updates to ThrillsKernel3
Just check what the date of the ThrillsKernel is, and you can simply look at the dates of the commits to see if it's included in the kernel or not. Example: With the version from November 18th, any commit up untill that date is included in the kernel. With the 20120917 version, every commit up untill September 17th is included in the kernel.
Downloads:
The kernel is not released on its own yet, because I haven't been able to test it on many ROMs. If you want it, install any of my ROMs:
NoThrills A510 WorldWide optimized Stock ROM
NoThrills A510 "Franken700" Stock ROM
NoThrills A510 Unofficial CyanogenMod 10
ThrillsKernel is included with these ROMs as of 2012/09/17. Developers, feel free to extract the kernel and use it in your own ROMs.
Great new!
NoThrills said:
[*]Removed Acer mount security: Now you can mount system as r/w.
Click to expand...
Click to collapse
So it was Acer who was messing with remounting system RW?
Suggestion- maybe switching to TinyRCU is a good idea? It has a lower memory footprint and performs faster
gen_scheisskopf said:
So it was Acer who was messing with remounting system RW?
Click to expand...
Click to collapse
yep, great catch by nothrills, i should have seen this one
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
It might be, never looked into it as I have used Screen Filter since forever
kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
I used to use rootdim on my thrive to get it so low I could use the tab as an alarm clock with the screen on and facing me all night.
But trying the same on this a510, the backlight just goes completely off if I try to set it any lower than default. So I wonder if it is a hardware limitation.
It would be nice though. This thing makes my eyes hurt in the morning on the bus to work.
Overclock possible please? Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
I would absolutely love this feature. I dont like apps messing with my system...
Working A510 CIFS at last!!!
NoThrills said:
ThrillsKernel for the Acer Iconia TAB A510 version 2012-09-17, built from source
[*]NTFS, CIFS, and MD4 support
The kernel is not released on its own yet, because I haven't been able to test it on many ROMs. If you want it, install any of my ROMs:
Click to expand...
Click to collapse
I'm currently quote happy with the stock ROM apart from the lack of CIFS so I took the modules from /system/lib/modules [NoThrills A510 WorldWide optimized Stock ROM] and copied them to my stock (but rooted) A510.
CIFS works perfectly!
Thanks!:good:
Feedback:
I've tried Smartass v2 and Lulzactive and they seem to eat up more juice.
I then checked System Tuner Pro for my CPU times, and I noticed that my CPU would only go from inactive to 1.3 or 1.4GHz. It doesn't use the values in between.
I then switched to Interactive, and I can see the CPU clocks like 400+ and 600+ used again.
Not sure if it's just me though, but I'm putting it out there for everyone to test. Nevertheless, I love this kernel, I love the optimized A510 that you released as it fixed my screen responsiveness issue entirely. Take that Acer!
Another question, what's the best app to tweak the CPU governor? Or I guess... what do you use NoThrills?
salisbury_steak said:
Another question, what's the best app to tweak the CPU governor? Or I guess... what do you use NoThrills?
Click to expand...
Click to collapse
I'd say NoFrills CPU Control- works fine on ICS/JB
Other one is SetCPU but last time I used it there were problems on ICS (January/February)
I've used SetCPU without problems myself. I do however have the purchased version, which is different from the free version that can be found on XDA. That one doesn't seem to be updated anymore.
I've posted about my touchscreen problems in some games in the Optimized ROM thread.. but no answers there. The problem is only there when I use the NoThrills kernel... the stock kernel works good. Have you got any idea what the problem can be?
I had the same problem with some games too ... so I came back to stock kernel
another bug I noticed: battery can't charge to 100%, always blocking at 99%
meldrak said:
I had the same problem with some games too ... so I came back to stock kernel
another bug I noticed: battery can't charge to 100%, always blocking at 99%
Click to expand...
Click to collapse
I just charged to 100% yesterday, it worked.
Did you try to restart your tablet, then charge again?
salisbury_steak said:
I just charged to 100% yesterday, it worked.
Did you try to restart your tablet, then charge again?
Click to expand...
Click to collapse
I didn't reboot just after being blocked at 99%
but between 2 charges I rebooted it and in both case blocking at 99
I came back to stock kernel so I can't test it again
Aaargh, I hate all this touch problems with this f#@$ tablet. Games only playable with the stock kernel, but a piano app is not usable because it doesn't always detect your fingers. Sometimes it's perfect, you can press up to 10 keys at the same time, and sometimes it doesn't recognize two fingers. So I probably need the custom kernel for this.. but I don't want to flash a different kernel for different apps.
This is really the worst device I've ever bought, I hate this piece of crap. I hope this annoying problem will be solved in some future kernels but untill now there isn't a perfect one out there which solves all the problems. No offence to anyone, I know it's all in your spare time, but it's a rant to Acer. A device of about €450 which is soo bad, that's some really bad engineering!
Maybe this new file format would be considerated (or not ) ?
http://www.muktware.com/4485/samsung-creates-new-file-system-f2fs-linux-good-news-android#.UHPclVFKSVh
How to implement
https://lkml.org/lkml/2012/10/5/205
some benchmark results post by the F2FS author : http://www.mail-archive.com/[email protected]/msg318439.html
1. iozone in Panda board
- ARM A9
- DRAM : 1GB
- Kernel: Linux 3.3
- Partition: 12GB (64GB Samsung eMMC)
- Tested on 2GB file
seq. read, seq. write, rand. read, rand. write
- ext4: 30.753 | 17.066 | 5.06 | 4.15
- f2fs: 30.71 | 16.906 | 5.073 | 15.204
2. iozone in Galaxy Nexus
- DRAM : 1GB
- Android 4.0.4_r1.2
- Kernel omap 3.0.8
- Partition: /data, 12GB
- Tested on 2GB file
seq. read, seq. write, rand. read, rand. write
- ext4: 29.88 | 12.83 | 11.43 | 0.56
- f2fs: 29.70 | 13.34 | 10.79 | 12.82
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Serkenar said:
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Click to expand...
Click to collapse
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
x3maniac said:
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
Click to expand...
Click to collapse
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Serkenar said:
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Click to expand...
Click to collapse
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
x3maniac said:
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
Click to expand...
Click to collapse
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Serkenar said:
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Click to expand...
Click to collapse
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Thank you for your work on this
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
thelangosta said:
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
Click to expand...
Click to collapse
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Cool
x3maniac said:
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Click to expand...
Click to collapse
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
thelangosta said:
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
Click to expand...
Click to collapse
openelec(rasbery pi)
if you want it to look nice then enlightment e17. for a light weight DE they make it very pretty with all the effects like compiz
or lxde
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Serkenar said:
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Click to expand...
Click to collapse
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
x3maniac said:
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
Click to expand...
Click to collapse
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Serkenar said:
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Click to expand...
Click to collapse
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
x3maniac said:
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
Click to expand...
Click to collapse
Strange, but there's no /etc/X11/xorg.conf
I tried creating it with `Xorg :1 -configure`, but I get "No devices to configure. Configuration failed."
I also tried creating /etc/X11/xorg.conf with the following content
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
but touchpad wont' work.
Like I said, there appears to be no apparent reason for those freezes The only things they had in common are the following:
(as far as I can remember)
-I had a cifs share mounted
-pen drive was plugged in
-chromium was opened
I understand that isn't helpful at all, but atm I can't reproduce those freezes myself. They occur kind of randomly.
I hope linux4tegra kernel does boot after all
Thank you for your work
EDIT: 30 minutes without freezes, I hope they're gone for good! :laugh:
djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 Totally agree
djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Serkenar said:
+1 Totally agree
Click to expand...
Click to collapse
as far as i see it, you guys are helping me get a working version. user/tester are as important as the devs making them. or else dev's would be out of the job. lols that's how i see it
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Serkenar said:
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Click to expand...
Click to collapse
i'm guessing jhanti's kernel is not stable. i was starting to use it more and got a random freeze. cpu1 went to sleep and wont wake up. looking into that.. i might just take nvidia's kernel 3.1.10 and try to get that working.
I see there's this new CM11 going, and thanks to @Hashcode who solved most of the complex problems already, here's my first stab at CM11 on our Nook HDs that installs into internal memory (EMMC).
The install is a lot similar to how it was done in CM10.2 days, but you will need a new recovery image (and a new sdcard image for those doing initial install):
So, For Nook HD+: Initial ovation sdcard image (cwm) | ovation recovery image (CWM)
For Nook HD: hummingbird Initial sdcard image | hummingbird recovery image (CWM)
I did some light testing and things seems to be working for whatever light loads I came up with, but still there are probably tons of problems that I have not yet noticed. Please write in the comments about what's broken and I'll try to fix it. Once it's good enough, I'll try to get official nightlies going for CM11 as well, I guess.
Latest CM11 EMMC images are now available as CM11 nightlies at:
For Nook HD+ get ovation builds
For Nook HD get hummingbird builds
There also might be experimental builds available referenced below in the history section.
(Also for completeness, For Nook HD+ sdcard image cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook
For upgrades from CM10.x (the only tested are 10.2 and 10.1). If you have any problems after upgrade - you'll need to do factory reset to clear /data:
Download recovery zip and CM11 install and place it on the nook
Reboot into recovery you already have installed
Flash the recovery zip you just downloaded
reboot into recovery again (This is important! Failure to do this will botch your upgrade and you'll need to wipe /data) so that the new recovery is started.
Install CM11, install other stuff you need like gapps
reboot
enjoy
Note: After upgrade you will need to reenter all of your wifi passwords.
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (usually only needed on official CM builds, as otherwise you can use Quick Settings panel): USBHostSwitcher.apk
Known problems:
- attempting to reformat external sdcard from android crashes volume manager - seems to be upstream problem of some sort. The sdcard is left in some strange state, so don't do it. (if you did, reformat the sdcard on your PC, all data will be lost either way)
Changelog:
2014/11/297 - Bring sdcard build to current source version:
* cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
2014/08/17 - Bring sdcard build to current source version:
* cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip
2014/01/18 - Fixed 1080p movie playback on Nook HD+:
* cm-11-20140118-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140118-UNOFFICIAL-ovation-sdcard.zip
2014/01/17 - Fixed headset mic issue
* cm-11-20140117-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140117-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140117-UNOFFICIAL-ovation-sdcard.zip
2014/01/15 - Switched to TI wpa supplicant, should fix a bunch of wifi-related issues
* cm-11-20140115-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140115-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140115-UNOFFICIAL-ovation-sdcard.zip
2014/01/09 - Fixed inability to write to sdcards.
* cm-11-20140110-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140110-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140110-UNOFFICIAL-ovation-sdcard.zip
2014/01/08 - Misc updates: autodetect sdcard format, not just vfat. fuzzy touch patch courtesy of D Marble, bt-pan services that reportedly fix bt tethering for some people.
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip
2014/01/06 - Initial release
* cm-11-20140106-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140106-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
The screen kept flickering like a tube light few times.
Thank you! Welcome back
Sent from my BN NookHD+ using xda app-developers app
Welcome back, you've been missed greatly. I kept telling everyone not to panic, you would be back.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks dude. I was hoping you'd start building it. Downloading now!
Working well so far. Thanks for making it and glad to have you back.
for those who need gapps you could see below (Be sure to choose 4.4.2 gapps.)
Link for PA gapps : http://forum.xda-developers.com/showthread.php?t=2397942 <MINI MODULAR PACKAGE 121 MB>download link http://goo.im/devs/paranoidandroid/roms/gapps-mini/pa_gapps-modular-mini-4.4.2-20131230-signed.zip
My personal favorite is BaNK's gapps : http://forum.xda-developers.com/showthread.php?t=2012857 <core gapps only, 17MB>download link http://www.androidfilehost.com/?fid=23269279319195954
Thanks for starting the work again -- I can't wait for official nightlies. And welcome back.
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Nice to see this, I've used Bokbokan's eMMC build off his blog with TRIM support by default (MAG2GA ver06 10/2012), and I've used yours with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
It would be interesting to know if it presents visible differences from CM 10.2 regarding responsiveness, especially with ART enabled. It's the last fort to be conquered with our nooks (trim+art). Sadly my nook is not back yet so any reports would be welcome.
Awesome
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
jjjooonnn said:
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
Click to expand...
Click to collapse
It should be updatable via the settings once it's an official built. Right now, all of the builds are unofficial ones, so they have to be fully downloaded and flashed.
verygreen is the official device maintainer for CM though, so once he "approves" of the build, it will be built nightly by the CM servers, and then it will be fully integrated into their update mechanism (or CyanDelta if you use that). Just like the 10.2 builds.
TeutonJon78 said:
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Click to expand...
Click to collapse
It's on the todo list, but cwm was easier to make at first (as in, next to zero effort)
jjjooonnn said:
Does this build come with TRIM enabled?
Click to expand...
Click to collapse
Yes, this has TRIM-enabled kernel, though I have not decided if I should do it for the official releases.
Have there been any more bricks with the trim-fixed kernels in the past couple of months?
Will this be updatable via CM updates in settings?
Click to expand...
Click to collapse
I guess yes, once there are official nightlies again. But I want to make sure it's at least of adequate quality before enabling that.
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Good job!
I can't speak for anyone but didn't see anything from a quick search in the post: TRIM FAQ. I can attest that mine works and I believe it should be one of the bad eMMC (MAG2GA ver06 not ver05).
I did test TRIM (vdc fstrim dotrim) no issues, and found the CM11 under updates (after I updated to CM11) so I can attest to that much!
Thanks for the reply
Darrian said:
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Click to expand...
Click to collapse
I would say they are about same smooth. Succulent's build has some nice framework and more option in performance settings. But just from system ui or user experience they are almost the same. Not could I tell the difference in app opening or transition.
Stock launcher Does lag when press the app drawer butter from home screen. But I use Nova launcher to solve the problem.
No find significant performance inprovememt over cm10.2 yet. Maybe Kitkat just does more job in UX polishing rather then performance.
Hopefully we could find some Performance MOD to use in KitKat.
It may very well be due to the fact that I upgraded from CM 10.2 and did not do a clean install, but for me Succulent's build was extremely laggy, many apps froze frequently, and when too many apps (more than like 3) were open it would reboot itself. I have none of those problems with this build, it's super smooth and fast and I haven't had any apps become laggy or crash or reboot my tablet. And this is upgrading from CM 10.2>Succulent's KK>Verygreen's KK; I still haven't done a factory reset and don't plan to unless it becomes necessary later. I use Nova as well. I'm not saying Succulent's build is bad, I thought it was bearable enough to use and was planning on using it long term, updating with each new build until it got to where I thought it should be, but then I installed this build and the difference is staggering. If I reflashed Succulent's build and wiped my data partition I might have a better experience, but now that I have this I don't see any need to.
this is great, glad to see you're back =)
my nook is currently being borrowed, i was wondering if anyone could quickly benchmark it?
thanks
Thank you Verygreen for this new build.
I will try it today.
I have 2 questions about CM11 and Nook HD+ hardware:
- did the HD+ have a bluetooth low energy (BT 4.0) chips?
- did the HD+ have a Low-power audio playback (kitkat new feature) capable chips?
If yes, is it included in this new CM11 build?
Thanks
Edit:
I found that Nook HD+ has wl1271l chip and uses wl12xx driver. That chip is BT 4.0 and BLE. See here http://www.rfm.com/products/data/wls1271l.pdf
But this thread show that BLE isn't activated in CM.
verygreen said:
久しぶりでした
(Also for completeness, For Nook HD+ sdcard image cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
Click to expand...
Click to collapse
Thanks verygreen. Great to see your are back in action.
The SDCARD image link is downloading emmc image. Here is the correct like if any one is looking.
cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
This thread is a direct continuation of @Hashcode's work for porting to Lollipop. Because of his and @verygreen's heavy lifting, porting to CM12.1 happened almost painlessly, for which I'm grateful. Their contributions compelled me to share something back. Thus, I'm uploading personal builds of CM12.1 for HD and HD+ in this shared Box folder. While I do not own a hummingbird, sister builds are generated more or less concomitantly.
Some of the important device-specific changes from KitKat/CM11 are described in Hashcode's thread. The goal is to keep as close as possible to CM upstream, and integrate whatever fixes and enhancements we find over time. More progress information will be added here gradually, as I have time. A lot of useful discussion happened on the CM12.0 thread, and the status of things is available to anyone willing to search. Hunting for possible bug fixes, understanding how to actually boot a newer kernel are some of my current priorities. I am not a developer, and the usual disclaimers apply.
Recovery Information
Up to date eMMC TWRP images are included in the respective device folders. Personally, I've had a good experience with TWRP, and do not plan on looking at other recovery distributions. Now, there have been (very) sporadic reports of broken partition tables, soft-bricked devices, etc, blamed on recovery. Although recovery is usually not the actual culprit, here are some ways you can rescue a completely unresponsive device:
It's a good idea to keep a microSD card around, with verygreen's external recovery image from here.
Once booted off the external recovery, you can easily fix whatever is broken (ADB is your friend here). There's no need to re-install CM11, as re-flashing recovery and/or boot will most likely fix your issue.
Recovery partition: dd if=<path to recovery image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
Boot partition: dd if=<path to boot/kernel image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
Afterwards, you should at the very least have a working internal recovery. I don't recall any instance where /system and/or /data became corrupted because of recovery, but you can certainly fix them now.
I've never tested this part, but I believe that you may be able to install an eMMC CM12 ZIP with verygreen's external CWM, even if /data and /cache are F2FS (assuming you copied all ZIPs onto the external card). My understanding is that only /dev/block/platform/omap/omap_hsmmc.1/by-name/system (always ext4, mountable by any recovery) is touched during installation, so you may even bypass TWRP completely.
P.S. If you broke you bootloader by flashing the wrong recovery flavor, despite all images being clearly labeled as hummingbird or ovation, well, no sympathy for you… Still, you can bring your device back to life within minutes as described above.
Progress towards Official CM12 Nightlies
As of now, most things are ready for turning official nightlies on, including official TWRP images and SELinux Enforcing support, albeit with this proviso:
My HW composer changes described in post #3 and #602 are not included upstream, since the plan was to fix upstream for all devices using CyanogenMod/android_hardware_ti_omap4.
The stumbling block with SELinux Enforcing had been remounting /system upon each new install, to write the customized WLAN NVS BIN. I'm avoiding this step by modifying the scripts to store the Wi-Fi calibration data in /rom now, with the added benefit that it only needs to be generated once. These changes are also not captured upstream, and may never be. If someone figures out an upstream-approved way of writing to /system upon first boot under Enforcing, then we'll probably switch back to the old fix-mac script.
On a personal note, posting on my threads is pretty tricky business... My builds were never intended for general consumption, but rather a way to move porting and development forward, and I often debate only keeping the GitHub repositories for people to build themselves. Obviously, that would upset hundreds of people at this point, so I make an effort to upload reasonably bug-free builds, as well as help even with trivial non-problems whenever I can. Nevertheless, low quality, or badly written posts (and I don't mean bad English) are a sure way to get ignored, and my memory is pretty long term Basically, I won't police content here, but I also don't want to deal with the the kind of stupidity and entitlement so prevalent in real life.
In conclusion, no need to thank (unless you really want to), or ask about donating, etc, but do reassess the limits of your current understanding before making bold claims, as I do too. Nothing worse than having to fix a trail of misinformation... Also, comparisons to other people's work (unless constructive), complains about the state of things, or simply starting with "no offense" and such, will make your problem much less likely to be solved by me.
XDA:DevDB Information
UNOFFICIAL CM12.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
amaces, Hashcode, verygreen, Jon Lee
Source Code: http://github.com/airend
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Testing
Created 2015-04-16
Last Updated 2015-09-14
All Things Kernel
The information below (branch names, kernel progress, etc) is slowly becoming out of date (post #2 in the Marshmallow thread has more details). Although it feels pretty archaic at this point, I'm leaving this information here, mostly for historical reasons.
My primary focus has been and continues to be an even better kernel. Instead of opening a separate thread, I will be using this space for kernel updates and related information, in a sort of log format.
Since making any of the fancier OMAP-specific kernel trees work properly is a huge headache with limited benefits, I just merged the linux-3.0.101 patches, mainly for testing (the d-3.0 branch). These patches may help with the ARM core, not so much with OMAP parts, and certainly no change to any of the Nook-specific systems. Subjectively, the normal kernel still feels marginally more stable, but hey, everything still works.
It's mid May, and for the past couple of weeks, branch g-3.0 has slowly become my default kernel. It contains additional merges from the Google 3.0 OMAP kernel, the .101 commits, plus cherry-picked changes from various sources. Hopefully, all these make for a better kernel, although the holy grail remains K3.4…
I've been experimenting with improvements upon KSM; UKSM and PKSM are supposed to better recover duplicated/lost RAM (the former in the default g-3.0 branch, the latter in p-3.0). As with KSM, they need to be enabled (and optimally tuned) through the sysfs interface (echo 1 > /sys/kernel/mm/[up]ksm/run).
A significant number of patches were added for LZ4 support, and to make zram/zcache actually use it. I think it makes things snappier, but we'll have to wait and see. Also, it turns out that good old KSM is better after all; PKSM creates instability, and UKSM is a lot more CPU hungry, very much undesired on an already underpowered device.
Another exciting week for K3.0… @Hashcode uploaded a bunch of LMK/low RAM/etc optimizations for some AMZ/OMAP44xx variants, which I'm stealing for the HDs. As I'm better understanding the use of MFLAG/QOS for frame prioritization, I ported some of these changes from K3.4. The most exciting however, is the DMA-buffered K3.0 that I have working (branch dma-buf). It definitely feels better, although figuring out how to completely switch away from memory carveouts, fix the communication with OMX/Ducati for HW accelerated video, is complicated. This branch will remain an experimental project till K3.4 is up and running.
Just for testing, I'm rebasing most of my changes on top of the official CM12.1 kernel, and made the new iosched branch default for a while. This branch contains many changes to the block layer, cherry-picked from @faux123's tuna kernel. We now have newer I/O schedulers, such as FIOPS, ROW, and eventually BFQ. The current default elevator is ROW with 256 KB readahead. A few other interesting patches popped up, mainly related to unaligned access on ARM, and related optimizations.
Since July, all changes are grouped into feature branches on top of the upstream kernel, which are finally merged into the cm-12 branch, the default for the foreseeable future. This way of doing things is easier to maintain, and makes these changes easier to read, when deciding what to keep/discard for upstream.
HW Composer Issues & Fixes
The goal, and probably one of the base requirements to have these devices included in the CM12 nightlies, is to have a stable ROM with normal HW accelerated overlays. As of now, we achieved this by mostly reverting to the HW composer in CM11, although understanding why the newer code in hardware/ti/omap4 creates these underflows is equally important. Post #602 contains more information about this issue.
Starting with the July 14th builds, disabling HW overlays shouldn't be necessary any longer.
Before mid-July, we were using the upstream HWC in CyanogenMod/android_hardware_ti_omap4. As discussed ad nauseam, that combination of upstream K3.0/PVR modules/SGX DDK binaries/HWC runs into serious GFX buffer underflows. With five or more composer overlays, the panel attempts to reset constantly, which causes display flickers, followed by reboot (dumpsys SurfaceFlinger|grep -A 10 type will show how consistent this bug is).
In the meantime, a poor workaround was to disable HW overlays in Developer options. To make it stick across reboots, you could use this /data/local/userinit.sh:
Code:
#!/system/bin/sh
(while :
do
sf=$(service list | grep -c "SurfaceFlinger")
if [ $sf -eq 1 ]
then
service call SurfaceFlinger 1008 i32 1
break
else
sleep 2
fi
done
) &
First!!! Great to see you start your own thread. Thanks for all the great work
ac-t660 said:
If I have the 3/24 ROM already installed, should I dirty-flash the 4/8 version or do I need to reset and fresh install it in order to properly get the changes?
And like everybody else has said - thanks amaces and hashcode, incredible job!
Click to expand...
Click to collapse
Doh! I must have been typing my question as you were creating this new thread. Moving it since you and everyone using your builds are moving over here. Thanks again!
Based on this, I'd say that should be possible soon, if not already. However, that wasn't the case with the initial builds. I'd say no harm wiping just /system, and maybe /cache, flashing a CM12.1 ZIP, plus the proper GApps, and see how it goes.
Thanks!
I've flashed your 8 Apr build, and it (mostly) looks good. I still get the occasional forced reboots after some flickering. The flickering tends to occur when changing from portrait to landscape and pulling down the settings bar.
I very much look forward to see some progression.
Can you provide some instructions with installing TWRP on the HD+? I have Cyanoboot installed and flashed your build using CWM recovery.
Thanks.
In response to this post in the 12.0 thread.
amaces said:
The changelog would basically be the CM12.1 one
Click to expand...
Click to collapse
Great, so can you point to the latest CM12.1 commit that you've included when you make a release? Knowing the date doesn't pin it down completely.
amaces said:
About the ovation kernels, those images were for CM12.0, and while they may work with current builds (for reasons stated above), they don't provide any benefit anymore.
Click to expand...
Click to collapse
So we should use our original boot/kernel images?
Thanks!!
Hey amaces,
Thanks so much for the 12.1 builds. On the 4/4 build and will be testing out the 4/8 build over the weekend.
Thanks!!
shdware said:
Can you provide some instructions with installing TWRP on the HD+? I have Cyanoboot installed and flashed your build using CWM recovery.
Click to expand...
Click to collapse
Flashify can do that for you inside the ROM, or you could dd if=recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery inside adb shell or terminal. Also, current TWRP allows flashing of boot/recovery images directly.
MossyTC said:
Great, so can you point to the latest CM12.1 commit that you've included when you make a release? Knowing the date doesn't pin it down completely.
Click to expand...
Click to collapse
Sure, can do, although that kind of tagging needs to be thought out. I could simply append the CM review change number, but that's not very useful since most changes are in repositories that don't affect our devices. I'll look if anyone found a good way to do it (frankly, I don't recall seeing it done).
MossyTC said:
So we should use our original boot/kernel images?
Click to expand...
Click to collapse
The ROMs come with their own kernel. Those independent kernels were simply testing a few patches for the buffer underflow/flickering issues, and were meant for easy swapping within compatible CM12.0 builds.
Hi amaces,
I had done the 5.0 build, what do I need to do in order to pull in the 5.1?
TIA
andtron said:
Hi amaces,
I had done the 5.0 build, what do I need to do in order to pull in the 5.1?
TIA
Click to expand...
Click to collapse
I think it's better to backup your apps (I use titanium), do a full wipe and then install the 5.1 rom and gapps.
I am running the 04/08 and it is working fine except one major problem that is the bane of Android everywhere since kitkat...
It keeps telling me I have insufficient storage space to do anything, update apps or install new apps, and there are hardly any apps on the device.
When I go to Settings -> Storage it says total space 12.67GB but "Available" is only 700MB, which doesn't add up and doesn't agree with the graph.
I have:
Apps 0.92GB
Pictures, videos 5.62MB
Audio 296KB
Downloads 1.20GB
Cached data 1.24MB
Misc 1.65GB
Adding that up is just under 3.8GB total so I should have about 8.9GB free, but it only reports 700MB.
Something is wrong with the free space calculation. Any help here? This wasn't a problem on the previous CM12.
BTW I did a clean install (full system wipe) before installing the CM12.1.
Any help is appreciated. I am at my wit's end on this issue.
Thanks Tschumi.
My question is more on how to pull the sources and build the 5.1 myself.
mr72 said:
I am running the 04/08 and it is working fine except one major problem that is the bane of Android everywhere since kitkat...
It keeps telling me I have insufficient storage space to do anything, update apps or install new apps, and there are hardly any apps on the device.
When I go to Settings -> Storage it says total space 12.67GB but "Available" is only 700MB, which doesn't add up and doesn't agree with the graph.
[…] Adding that up is just under 3.8GB total so I should have about 8.9GB free, but it only reports 700MB.
Something is wrong with the free space calculation. Any help here? This wasn't a problem on the previous CM12.
BTW I did a clean install (full system wipe) before installing the CM12.1.
Any help is appreciated. I am at my wit's end on this issue.
Click to expand...
Click to collapse
That must be… frustrating. So, you're saying this happened on CM11, then CM12.0 was fine, and now the bug is back on CM12.1? There are a couple of unusual/puzzling issues that people report, including the reboot-instead-of-poweroff bug. Never having experienced these, it's hard to figure out the cause, but I'll keep it in mind.
andtron said:
My question is more on how to pull the sources and build the 5.1 myself.
Click to expand...
Click to collapse
These days, it's very easy; you simply upgrade your LP5.0/CM12.0 sources with: repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
mr72 said:
I am running the 04/08 and it is working fine except one major problem that is the bane of Android everywhere since kitkat...
It keeps telling me I have insufficient storage space to do anything, update apps or install new apps, and there are hardly any apps on the device.
BTW I did a clean install (full system wipe) before installing the CM12.1.
Any help is appreciated. I am at my wit's end on this issue.
Click to expand...
Click to collapse
I think it has something to do with updating from stock to cm. Go to 'terminal emulator' app, type 'su' then 'df'. Let us know what is the output.
Also, backup all your data. Do you mind clean install again? Which recovery are you using? If you convert your data partition to F2FS I'm sure it'll fix it. Not because F2FS will fix it, but because converting it to F2FS will format the entire /data partition (including the virtual /sdcard). There might be old files downloaded when you used stock rom.
extrem0 said:
...If you convert your data partition to F2FS...
Click to expand...
Click to collapse
Quick question, how does one go about converting the partition to f2fs on the ovation? I've done a couple searches but can't find anything definitive such as which recovery I should have installed and if it is a zip that I would need to flash.
Thanks!
J-Pod said:
Quick question, how does one go about converting the partition to f2fs on the ovation? I've done a couple searches but can't find anything definitive such as which recovery I should have installed and if it is a zip that I would need to flash.
Thanks!
Click to expand...
Click to collapse
I did it using twrp recovery 2.8.6.0 built by amaces. There's an option that allows you to convert some partitions to f2fs. Remember, it will erase all your files in your nook. Do a backup of your files before converting to f2fs.
J-Pod said:
Quick question, how does one go about converting the partition to f2fs on the ovation? I've done a couple searches but can't find anything definitive such as which recovery I should have installed and if it is a zip that I would need to flash.
Thanks!
Click to expand...
Click to collapse
Using @amaces TWRP, go to Wipe, check the data box, select "advanced wipe then it's something like " repair file system". I'm sure you can figure it from that.