Is there a custom kernel available, such as Franco, that works with CM Alpha 3.5 for Touchpad?
Coming from a Nexus S, I can't stand staring at the screen anymore. I need a kernel to optimize its performance and to calibrate the screen.
Related
hi i was wondering what kernel would best suit my vibrant no internet on it mainly used for texting and games please and ty i am on cm7
dpends on what type of gb rom you're running.
i have no experience with samsung based gb roms, but i do know that if you're running cm7, glitch v11 is a great kernel! insane uv, voodoo color (the nexus s version), voodoo sound, 1.7GHz OC.
yes i am running the current nightly cm7
then try glitch v11 for vibrant.
If you ever get the need to flash something different from cm7 try miui, its a nice change and is even more theme-able then cm7 but if texting is all you use your phone for try edt's trigger since it has superior battery life so you can text all day and night
I am using a custom 4.1 ROM on my Galaxy Nexus. This ROM is quite stable, and usable.
I tried many 4.1 ROMS on my Galaxy Tab 10.1, but all of them were too unstable to use. For example, Wi-Fi device is not responding after waken up from long sleep, system halt after waken from long sleep, random reboots, screen glitches, system UI crashes, camera not working, hardware decoding not possible and so on. Now that Samsung officially abandoned support for GT 10.1, will there any chance that there would be a usable, stable 4.1 custom ROM comes out for GT 10.1?
Well, I will probably move on to Samsung Nexus 10 unless it has serious disadvantages, but just wanted to know this.
CM10 is very stable, very fast and I don't have any problems on my 10.1 3G :good:
typingcat said:
I am using a custom 4.1 ROM on my Galaxy Nexus. This ROM is quite stable, and usable.
I tried many 4.1 ROMS on my Galaxy Tab 10.1, but all of them were too unstable to use. For example, Wi-Fi device is not responding after waken up from long sleep, system halt after waken from long sleep, random reboots, screen glitches, system UI crashes, camera not working, hardware decoding not possible and so on. Now that Samsung officially abandoned support for GT 10.1, will there any chance that there would be a usable, stable 4.1 custom ROM comes out for GT 10.1?
Well, I will probably move on to Samsung Nexus 10 unless it has serious disadvantages, but just wanted to know this.
Click to expand...
Click to collapse
No, unfortunately it will be a mystery until the end of time. It's really tragic that with all these talented devs no one will ever find out how to stabilize a custom build.
(Try task ICS with Yoda kernel.)
Dude if you run preshoots cm10 with A1 kernel, overclock to 1.6, flash it via cwm 6.0.1.5, and install the bootloader via Odin your good I'm running it right now and it seems completely stable
Sent from my GT-P7510 using xda app-developers app
http://droidbasement.com/db-blog/?p=2860
I think this says enough.... i'm using cm10 since the first build came out, and never had any problems
Yeah I gotta say I've been running cm-10-20121017-EXPERIMENTAL. All day and as far as I've seen its rock solid bar a few bugs with the camers but that's just doing you a favour stopping you looking like a plank taking photos with a tablet.
Sent from my GT-P7510 using Tapatalk 2
RUN AOKP
typingcat said:
I am using a custom 4.1 ROM on my Galaxy Nexus. This ROM is quite stable, and usable.
I tried many 4.1 ROMS on my Galaxy Tab 10.1, but all of them were too unstable to use. For example, Wi-Fi device is not responding after waken up from long sleep, system halt after waken from long sleep, random reboots, screen glitches, system UI crashes, camera not working, hardware decoding not possible and so on. Now that Samsung officially abandoned support for GT 10.1, will there any chance that there would be a usable, stable 4.1 custom ROM comes out for GT 10.1?
Well, I will probably move on to Samsung Nexus 10 unless it has serious disadvantages, but just wanted to know this.
Click to expand...
Click to collapse
Run the AOKP build with A1 kernel, its quite smooth, actually smoothest among all builds I have tried recently and added with AOKP goodness
I've been using Clean ROM. Just curious to see what other people are running.
Sent from my Nexus 10 using xda app-developers app
I used stock from N10 release up until a couple of days ago when i changed to aokp. I must be honest, there are a few things in aokp which are nice, but well, for my usage, it doesn't make any difference, nothing in the rom to convince me that it was worth the change, could happily have stuck with stock jellybean without an issue.
I use Eos with trinity kernel and it's great
AOKP PUB with ktoonz kernel. Perfect for my needs.
Sent from my Nexus 10
Stock with KTManta kernel, I actually like it. Don't need it any other way. I used to think I'd want PA but in the end, I don't mind being stock. Same for my N4, very happy with stock and Nova Launcher
Aokp pub - mr Robinson with Ktmanta . ( but i like the progress work of morific on his trinity kernel. I swap them from time to time )
Sio with ktkoonservative .
Without ktweak app . ( instability , crashes with it )
Sent from my Nexus 10 using xda app-developers app
After a month of crack flashing just about every ROM there is for the Nexus 10, I've settled on Rasbeanjelly + Trinity kernel.
SentinelROM 4.10 + KTManta (Governor settings: ktoonservative with zen and in ktoonservative settings changed "disable_hotplug" to 1 instead of 0)
The only instability I noticed is with OTG connected storage. The N10 sometimes reboots when the OTG cable plus storage is plugged in and if I did not unmount the OTG storage before unplugging.
One missing capability that I need is native CIFS share support for those apps that do not have their own such as Power Amp. This is due to multi-user support changes in 4.2.2. Besides cifs.ko (which is supplied in KTManta) the two additional modules md4.ko and nls_utf8.ko are required.
The missing modules prevent apps like CIFSManager from working. Apps such as ES Explorer and XBMC which have built in CIFS support can access your network shares without issue. The author of KTManta already has the addition of the two modules on his very long to-do list.
eos as is
Lately, EOS or RasbeanJelly + Trinity kernel
Rasbeanjelly pub + Trinity...
CleanROM with stock kernel.
Anyone who knows how I contribute to XDA wouldn't be surprised to learn that all my devices run stock, unrooted ROMs. haha
AOKP Pub + trinity Kernel
Awesome combination
MrRobinson's AOKP PUB 4.2.2 rom with KTManta kernel.
vogonpoetlaureate said:
After a month of crack flashing just about every ROM there is for the Nexus 10, I've settled on Rasbeanjelly + Trinity kernel.
Click to expand...
Click to collapse
Same combo for me too. Although I'll likely give franco.Kernel a go once it gets updated.
Cm10.1 and Trinity Kernel (OnDemand + ROW).Works like a charm, no lag no reboots or whatsoever, great battery life. I'm in love whit my tab
Not sent from an iOS#!t device
I'm loving Carbon. The thing I love most it that is has the speed and stability of CM10.1 but the awesome PIE from PA. I also love Trinity kernel
Sent from my Nexus 10 using Tapatalk HD
EOS
Arcano said:
MrRobinson's AOKP PUB 4.2.2 rom with KTManta kernel.
Click to expand...
Click to collapse
Same for me, I recently switched to it though. I used CM10.1 and Slim ROM's before that. I always come back to the same kernel though.
What is the difference between paulicat's aosp ,houstonn's aosp and samuazcona's aosp...
Also what is the differnce in faux and adreno kernel..
Also am getting very good battery life on paulicat's aosp but it lags while playing games..please guide me ..i am new to the forum...
Hey guys, I've searched the forum and googled but can't find anything on it. Any of latest lollipop Roms but phone only has one core running. And by that I mean, the hotplugging works just fine and turns of all four cores. I've let all Roms settle for a couple days. Stock based based Roms, early cm 12.1 builds and cm 13 Roms have two running at all times, which makes for a smooth experience. I want to use cm 12.1 for its stability but only having one core running at all times makes for a choppy experience until the hotplugging turns on the second core and so on. Happens with 777 and nebula kernal too. Wondering if it was just me because I don't see anyone else posting aabout this problem.