Develop Bugs

[KERNEL][5-10-2011]PeanutButta Jelly Time

This is a custom kernel for the Continuum. It's based off of the DL17 source provided from Samsung, but should work on DJ20 as well. There are a lot of changes to the stock kernel though, and I'll try to list them all.
Features
init.d support, from Adrynalyne, also requires busybox with run-parts support
Voodoo Sound (v9), from supercurio, use Voodoo Control App to adjust settings
Voodoo Lagfix, from supercurio and the Project Voodoo team, applies only to files labeled with voodoo5
Undervolted
Updated CPU scaling to reduce lag
Battery fix, from SirGatez, allows for the use of non-oem batteries
USB Mount fix, from SirGatez, prevents phone from mounting as a cd-rom drive
ThumbEE Support
Removed almost all debugging
Optimized compiler flags
Updated in 0423
Simple IO Scheduler
SDCard Read Fix
Tweaked TCP settings
Tweaked CFS
Updated in 0510
Voodoo Sound V8
Disabled custom boot animations (for real this time)
Switched to Linaro Toolchain for cross compiling
Removed shutdown animation from zip
Made flash script CWM 3.x compatible
Disable CD-ROM Mount (maybe?)
Voodoo Lagfix <-- FLASH WITH CAUTION
Updated in 0529
Voodoo Sound V9
Voodoo Lagfix should no longer convert /cache which caused market download problems
Known Issues
Video issues on boot, works fine after the system boots up though. Will work on fixing it, if I can find out the root cause.
Naming convention
novoodoo - kernel does not have Voodoo Lagfix
voodoo - kernel has Voodoo Lagfix, create /sdcard/vodooo/disable-lagfix to prevent filesystem conversion
Thanks goes to DroidXcon, TrailBlazer102, Logan302, dfgged, and crazyknight
.zip files can be flashed with CWM Recovery, see here
If you like my work, feel free to donate to me. Alternatively, sign up for Dropbox via my referral link Also, remember that none of this would really be possible without the generosity of DroidXcon, so you could donate to him as well.
If you would like to develop your own kernels, visit my Github
If you have any questions about how to flash the files, ask before flashing, not after. I have only attached the novoodoo version of the kernel to this post due to issues in the past with Voodoo on the Continuum. If you would like to test out the Voodoo version, PM me and I'll send you the kernel with voodoo. Be warned though that in the past, there were issues with people using voodoo lagifx.

Just flashed the one with standard voltage with voodoo lagfix., Works good.
Edit: Never mind i see you uploaded that lol.

Ok for some reason i cant download anything from the market. It says your item is downloading and then just stops and says nothing.

CrazyKnight122 said:
Ok for some reason i cant download anything from the market. It says your item is downloading and then just stops and says nothing.
Click to expand...
Click to collapse
This happens sometimes. If its a large item, disable voodoo from voodoo recovery, and then let it convert back. Then install the large item (over 20mb seems to be an issue). Then convert back.

adrynalyne said:
This happens sometimes. If its a large item, disable voodoo from voodoo recovery, and then let it convert back. Then install the large item (over 20mb seems to be an issue). Then convert back.
Click to expand...
Click to collapse
SOunds good ill give it a try.

adrynalyne said:
This happens sometimes. If its a large item, disable voodoo from voodoo recovery, and then let it convert back. Then install the large item (over 20mb seems to be an issue). Then convert back.
Click to expand...
Click to collapse
It's a problem with the cache being converted to ext4. When apps are being installed from the market they are downloaded to the /cache partition and then installed to /data after fully downloaded, however if there isn't enough space in /cache, due, here, to the fact the ext4 journal takes up quite some space, then it can't download the app or game to the cache to install it, and it errors out. I've talked to supercurio about it and he states he's working on it.

Yeah i tried disabaling it and downloading something and it still doesnt work.

Try clearing cache from within recovery and see if that helps.

Tried it and didnt work.
No big deal really i can wait for a fix lol.

I got it to work.
I flashed the 50 undervolt kernal and set up voodoo lagfix and worked perfect first time.
I was using the 100 undervolt kernal before. Also the 50 had the dancing bananna bootani and the 100 did not.

CrazyKnight122 said:
I got it to work.
I flashed the 50 undervolt kernal and set up voodoo lagfix and worked perfect first time.
I was using the 100 undervolt kernal before. Also the 50 had the dancing bananna bootani and the 100 did not.
Click to expand...
Click to collapse
They should both be the same minus the undervolt level

The 100 undervolt didnt have the dancing banana boot ani just the stock.

Can anyone test to see if there are video issues on boot with these?

imnuts said:
Can anyone test to see if there are video issues on boot with these?
Novoodoo
Voodoo
Click to expand...
Click to collapse
Ill give it a try.

just sat at the samsung screen for me.

CrazyKnight122 said:
just sat at the samsung screen for me.
Click to expand...
Click to collapse
I can confirm that they just freeze :|
Well, the novoodoo one does the video problems.. Then just like shuts off..

trailblazer101 said:
I can confirm that they just freeze :|
Well, the novoodoo one does the video problems.. Then just like shuts off..
Click to expand...
Click to collapse
hmm, something must be messed up in my source tree Will need to figure that out, but I'm guessing it happened when i was trying to get it all on Github.

hmm.. okay... Hopefully its not anything big
I posted a picture of what the video problems look like on the IRC for when you are done working

trailblazer101 said:
hmm.. okay... Hopefully its not anything big
I posted a picture of what the video problems look like on the IRC for when you are done working
Click to expand...
Click to collapse
Thanks I'm pretty sure I know how to fix the no-boot issue, shouldn't be to difficult, though it will prevent anyone from building off of my Github until I get it fixed.

ah, okay.. sweet
So, i would like to confirm that i have my own boot animations working on my phone now im so happy its working!

[ROM] ZN Custom Firmware - 1.014.00_ZN-v1.2

Hello. Here's the second version of our ZN Custom Firmware. It is created by ZeroNull and vdsirotkin (4pda.ru). The original post is here.
WARNING - If it works on your device, be careful, as with an unlocked bootloader you can brick you tab faster than you can imagine.
Installation:
1) You'll need to do everything, what is written here or here. If your bootloader is already unlocked, and recovery is installed - you can miss this point.
2) Download the firmware - http://depositfiles.com/files/smnuqxxei
3) Install it using CWM or TWRP
4) That's all!
Features:
Patched 1.014 ICS kernel. Now mounting of /system partition is unlocked
modded boot.img
Better battery saving in standby
Rooted
NTFS SD cards supported
Init.d scripts enabled
bind-dir with autorun support from init.d (not working with NTFS)
Superuser and AcerRing is integrated in system partition
All Acer's and some Google's apps removed
Packages included (in user partition, removable via Apps Manager in Settings)
Adobe flash player
BSPlayer Lite
GPS Test
ES File Explorer
Quadrant Standart
Quick Boot
QuickBoot
Titanium Backup
Touch Recalibrate
"DIGI Clock" and "Weather forecast" widgets
Custom build.prop integrated
Root mode for adb unlocked
AcerRing with corrected background picture
Battery in %
Custom bootanimation: Frosty-Boot [v.Acer] with GEARS for Acer Iconia Tab A100
Screenshots:

First . Anyways, some screenshots would be nice .

Theonew said:
First . Anyways, some screenshots would be nice .
Click to expand...
Click to collapse
And what would you like to see on them?

ZeroNull said:
And what would you like to see on them?
Click to expand...
Click to collapse
The Acer ring for one. Were any modifications done to the UI, or does it have the stock look?

There are no UI changes, all the changes are made "inside" of the firmware

is this just a custom boot image?
If you have changed ro.product.model to A500, the Acer recovery installer app (once I release an A100 version) will think its an A500.
Sent from my SPH-D710 using Tapatalk

no, it's not only the boot.img, there are some other changes.
Well, if someone have installed recovery to install this firmware, so he or she won't need to install it again. Am I right?

I can't figure out how to download this. I don't read rushian (or greek or whatever that is). I entered the captcha and then clicked the link that LOOKed like what I was supposed to and it starting download some file ending with .msi so I canceled it.
Usually, custom ROMs come with their own boot.img, so if someone installs then, then a custom ROM, then this gets overwritten. if they install this, on top of their custom ROM, it'll work, unless the custom rom had a custom boot.img that it was dependant on.
Can you tell me if ro.product.modelalias still says A200 with this patch?

Sorry, tomorrow i'll upload it to some other place. To download this file untick where it's written smth about Яндекс.Бар. And there won't be any .msi file. Or use Google Translate
You are right, there is a custom boot.img, and many features in the firmware depend on it. But boot.img is not the only feature of this firmware. That was what I wanted to say
In build.prop it's written ro.product.modelalias=A100.

ZeroNull said:
Sorry, tomorrow i'll upload it to some other place. To download this file untick where it's written smth about Яндекс.Бар. And there won't be any .msi file. Or use Google Translate
You are right, there is a custom boot.img, and many features in the firmware depend on it. But boot.img is not the only feature of this firmware. That was what I wanted to say
In build.prop it's written ro.product.modelalias=A100.
Click to expand...
Click to collapse
Got it, downloading now. The link dissappeared when I hit the Translate button. But unchecking the checkbox worked. Thanks!
I updated my code to look at both ro.product.model and ro.product.modelalias.
Thanks!

the slowed down cpu is for better battery life? might be installing later

You're right.

What impact would slowing the cpu have on the overall performance? Thanks

utctigers said:
What impact would slowing the cpu have on the overall performance? Thanks
Click to expand...
Click to collapse
Some tasks (especially heavier ones) will not be as snappy (only if the cpu is limited to the slower speed also depending on how slow it is set to). The battery life should be significantly better though.

thanks, any plan on adding USB host mode?

Theonew said:
Some tasks (especially heavier ones) will not be as snappy (only if the cpu is limited to the slower speed also depending on how slow it is set to). The battery life should be significantly better though.
Click to expand...
Click to collapse
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium

ptesmoke said:
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No, there is nothing stopping the integration of more governors into the kernel. If you do heavy usage on the tab with the cpu underclocked so low (and limited at that point), then yes, it will put more strain on the processor. One would want it set so low for conserving battery (and not really using the tab for anything e.g. While you're sleeping). I usually set profiles on my devices to lower the frequency and set the governor to conservative when the screen is off (never done it on this device though).

Raul77 said:
thanks, any plan on adding USB host mode?
Click to expand...
Click to collapse
Our hardware (motherboard) doesn't support it.
ptesmoke said:
is there a reason we cant incorporate smoothass governors etc into the kernel? limiting to 500mhz is pretty unproductive...if your require alot of processing itll take twice as long at 500mhz to accomplish its instructions...thus using the cpu twice as long as it would have if it was able to ramp up to 1ghz to take care of it.
lower cpu is only helpful in an idle state to conserve power...why on earth would we want to lock it at half its speed?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
The reason is called "kernel sources". Without 'em we can't do anything (overclock, add governors) with our processor.
If you look at the usage of frequences, you'll see, that 80% of the working time the frequence is 200 mgz. And while testing, I didn't meet any problems with 456mgz, all the programs and games work smooth, and still 80% of the usage time is on 200mgz.
If you don't like this slowing down, why on earth you can't disable is? everything is written in the 1st post

thx
Thx to you !!!
Il Will try it today.
Systèm in RW mod ?
The memory swap is integrated ?
Obligation of full wipe before installation ?
And the last question... have we to make a advanced restoration of the unlocked Boot with CWM after flashing.
THANK YOU in advance for your answers to my question.....

samco08 said:
Thx to you !!!
Il Will try it today.
Systèm in RW mod ?
The memory swap is integrated ?
Obligation of full wipe before installation ?
And the last question... have we to make a advanced restoration of the unlocked Boot with CWM after flashing.
THANK YOU in advance for your answers to my question.....
Click to expand...
Click to collapse
Yes, it's included in root access
If it's not written about memory swap, than it's not intergated
No, /data must not be wiped, and /system/ will be wiped automatically, but only in 1.XX versions. 1.XX.X are only a kind of small update to already installed firmware
No, recovery and bootloader are deleted from this package, so they will stay as they were.

[Q] Stock ROM or init.d performance script

I might be the owner of lazy WFS, because ROM's I tried only work with stock kernel.
I am currently using Wildchild 3.3. with stock kernel provided in the thread, but the problem is the wi-fi is not working at all.
How do I fix this?
I'm not giving up the idea of using other kernels - i found that there might be a way by using init.d performance script but I don't know how? I'd very appreciate if you could help me, I've tried most of the kernels I found there and the results were always the same - it's stuck at the HTC screen
So is there anyway around this? Am I able to use other kernels if I do some tweaking?
Thank you very much

Anybody?

You can try this : http://forum.xda-developers.com/showthread.php?t=1955673
BUT !
-do a backup before install this

I noticed that, but I think those are just performance scripts ... I need something that will limit the cpu to 600mhz ... but I don't know the ¨command and how to put it in, if the kernel doesn't work by itself?

Born2B said:
I noticed that, but I think those are just performance scripts ... I need something that will limit the cpu to 600mhz ... but I don't know the ¨command and how to put it in, if the kernel doesn't work by itself?
Click to expand...
Click to collapse
open the zip navigate to /system/etc/init.d/99WFStweaks
change this line to
Code:
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Code:
echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
And it will set your cpu to 600Mhz on boot. Would be nice if you could tell if its stuck on bootanimation or its stuck on HTC logo. Cuz if its stuck on htc logo changing the frequeencies wont work.
Also that stock kernel was made by me and i later realized i messed up the modules or something like that so thats why wifi doesnt work. :silly:
I can also provide a standalone performance script but im too lazy to make it flashable zip so if you know how to push files via adb or whatever i can upload that for you too

[Q] I have some strange Kernel issues !!!

Hello folks! As the title says I have quite a strange issue with some kernels (Franco,LeanKernel and STOCK!!). I flash the kernels after flashing a rom ,doing it clean(all the wipes) and the phone is working fine for couple hours or a day,after that it just going verry sluggish even in appdrawer or when switching desktop screens. I looked at the CPU frequencies and they change as they shouldn't,I can tell that somethig isn't right with the cpu...I have this issue only with those kernels. I tried stock roms,4.2.x roms,flashed even google images to be sure it's stock,tried them with AOKP 4.2 and 4.1 ,CNA and the list could go on...
Is someone else having the same issue??
Any fix for this? I really want to try franco's kernel!!!

1. Hmmm, are you running a live wallpaper?
2. Do you face the same issue while using Trinity Kernel?
3. Are you sure you do not have any app such as SetCPU which is controlling the speed of CPU?
4. If you set the CPU speed back to normal, does this fix the issue?
5. How much space is mostly left on your sdcard?
I hope the answers of these questions will help to identify your problem much bettER

I don't have the same issue with faux's and trinity kernels . I don't have any program,i don't use a live wallpaper, how I can speed back to normal the cpu?

calinoii said:
I looked at the CPU frequencies and they change as they shouldn't
Click to expand...
Click to collapse
I thought you have checked the CPU speed/frequency using an app like "AnTuTu CPU Master".
calinoii said:
how I can speed back to normal the cpu?
Click to expand...
Click to collapse
Using AnTuTu CPU Master, check the speed set for the CPU when the phone is sluggish and if it something other than the normal 1200 MHz then modify it back to normal. This is what I meant

The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them

calinoii said:
The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them
Click to expand...
Click to collapse
I think some background processes are causing this so the CPU is trying to respond to them.
I suggest that you do a full wipe, install a ROM and use Franco's kernel, but do not install any other application on your phone, only default ones installed already with the ROM, maybe Gapps as well just to have a usable phone for some time, then check after a day whether it is again sluggish although there are no applications at all or it is still running fine. At least we would be able to know that maybe one of your application is not compatible well with these kernels and causing this mess.
You may want to avoid wiping so try to force stop the applications running in the background (and cached processes as well) to see if one of them is causing this problem.
Good Luck

I did wipe the data and didn't install any application and I have the same issue :-s

calinoii said:
I did wipe the data and didn't install any application and I have the same issue :-s
Click to expand...
Click to collapse
Do you use any widgets?

Nope

I am not sure I have helpful suggestions anymore except to be sure that you are using the correct Franco kernel whether you are running a 4.1 ROM or 4.2 one.
I hope other members can solve this problem for you. Maybe you will get a bettER help if you discuss this with the Franco kernel users on the Franco kernel thread.

Thanks anyway,i'll post this issue on franco's kernel thread and hope for a fix...and be sure i flashed the correct version of kernel )

Anyone? Please?

calinoii said:
I have some others with the same problem,but thisis the latest,no one could help me this far.I already did what you suggested me...I`m sure I did the clean wipes,just installed gapps and nothing else...when it was getting little hot the freezes were starting too,I think i did all I could,many people in this forums adviced me and still nothing,maybe franco's the only one who can help me with this...
Click to expand...
Click to collapse
Carrying on from here where we were in franco's thread. If you're flashing gapps then clearly you aren't using stock ROM like I told you to try. So, my suggestion to you for troubleshooting remains the same:
osm0sis said:
Well that's really peculiar. I'd try flashing stock again using fastboot. I'd fastboot oem lock, then fastboot oem unlock to wipe, then flash the entire image set as in efrant's thread just to make sure it all gets wiped. But unfortunately, like I said, if stock kernel doesn't work over a fresh fastboot flash of Google's factory image on your device there's still something very wrong, and it's likely wrong with the device itself.
Click to expand...
Click to collapse
osm0sis said:
Use the latest Google Factory Image for your device like I suggested, then you can see if you get the OTA immediately or you can flash it yourself. Do all this before you put any apps on, and don't let it put any apps on and see if you still have the issue with a completely stock setup.
Click to expand...
Click to collapse
Please report back only when you've followed that to the letter.

Tried both,the ones from the images,and the gapps on a stock flashed rom via recovery...I'm trying to resolve this for over 2 weeks now...
L.E : Ok,I will pm you when I manage to have some time for doing this again,thanks for your kindnes

I don't care how many times you think you've done it correctly before, I want you to try it AGAIN. And make sure you've completely wiped by using fastboot oem lock and unlock, then follow efrant's thread to the letter for flashing the entire image set. Factory Images ONLY, no stock-ish kitchen garbage.
I'm happy to help you but you've got to follow my instructions, since this is what I would be doing if I had this issue on my device.

Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?

calinoii said:
Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?
Click to expand...
Click to collapse
Yeah those are the commands. That's it. :good:
I think it's mentioned in efrant's post too, but no special guide necessary. Use the adb and fastboot that he attached too if you're new to fastboot.

I'm used to fastboot,I don't even need the guide to see the commands now,I think I used them like 100 times last 2 weeks )

Fair enough. Please follow the guide anyway though, and be sure to also flash userdata.img and recovery.img to be completely stock. You can fastboot boot cwm.img if you need it to flash your OTA afterwards. We just need you at 100% stock so we can try to figure this thing out. Also maybe hold off on adding your Google account so it doesn't start forcing apps onto your device. It could very well still be a rogue app issue so we need to try and keep your device as empty as possible to see if we can rule out hardware defect. :good:

Should I install any apps?
I did everything you said,now i'm waiting for it to boot up

[Q&A] [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)

Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.

temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..

Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app

lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out

Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.

total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.

bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.

arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.

bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option

arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!

bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...

HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.

flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!

spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.

This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.

spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.

chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).

I've haven't tried it but since it's a 4.4.4 rom they should work fine.

Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).