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.
Related
Hi,
I managed to screw up just about really bad with my Defy+ after flashing it with Waikiui which i afterwards noticed doesnt work with the Defy+ so now im in some hard packed poo here.
I have come to the conclusion that RSD Lite should do the trick if im lucky but i need to find a good SBF to flash the Defy+ with. Originally this phone rolled with a Nordic (GB?) so im looking for either that or something else that could be a good exchange for it.
Would it be possible to flash it with for an example Cyanogenmod or something?
Regards.
//FlashTec80
On the CM webpage, under the Devices - > Motorola Defy it says says there is no official support for defy+ ... on the other hand on the CM forums there are numerous posts by people claiming it runs just fine, seems like some run into a bug where the battery doesnt charge to 100% or something, you might want to stick to a ROM thats officially approved for your device or do a little bit more reading before you take the plunge. I would have posted links to forums and official page but apparently I cant since Im a noob and I need at least 8 previous posts
Tried to run CM 7 in RDS Lite, but it said that files mentioned in the XML file was missing, is that normal?
You can't flash CM7 using RSDlite. RSDlite is used for flashing of .sbf files!
To get your phone back to life, follow this steps:
1. Phone off, battery out
2. Hold Volume Up and Power Button and put the battery back in while holding the buttons - phone will boot into it's bootloader - you will see some white letters saying Bootloader Version 09.10 etc..
3. Install latest USB drivers - found here - http://developer.motorola.com/docstools/USB_Drivers/
4. Start up RSDlite on your PC (you need version 5.3.1)
5. Use this sbf - link (put the .sbf file in root C:/ and rename it to something short (e.g. defy235.sbf)
6. Select that sbf file in RSDlite and press START
7. Wait until the process reaches 100%, by that time your phone will be completely turned on > it's alive again
Can't write more, need to get going to classes, but will help you with everything else, as well. It's easy, just be patient.
P.S. Ignorance killed your defy+, not awesomeness
Cheers!
niksy+ said:
You can't flash CM7 using RSDlite. RSDlite is used for flashing of .sbf files!
To get your phone back to life, follow this steps:
1. Phone off, battery out
2. Hold Volume Up and Power Button and put the battery back in while holding the buttons - phone will boot into it's bootloader - you will see some white letters saying Bootloader Version 09.10 etc..
3. Install latest USB drivers - found here - http://developer.motorola.com/docstools/USB_Drivers/
4. Start up RSDlite on your PC (you need version 5.3.1)
5. Use this sbf - link (put the .sbf file in root C:/ and rename it to something short (e.g. defy235.sbf)
6. Select that sbf file in RSDlite and press START
7. Wait until the process reaches 100%, by that time your phone will be completely turned on > it's alive again
Can't write more, need to get going to classes, but will help you with everything else, as well. It's easy, just be patient.
P.S. Ignorance killed your defy+, not awesomeness
Cheers!
Click to expand...
Click to collapse
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
FlashTec80 said:
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
Click to expand...
Click to collapse
Decompress .gz
And yeah i u get stuck at the Motorola Bootanimation pull the battery and goto stock recovery and wipe data that should boot it...
Sent from my MB526 using xda premium
FlashTec80 said:
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
Click to expand...
Click to collapse
Had a safe day Some bloody hooligans were on the bus home, though... Goddamn idiots. Anyway, on the brighter side of life...
You got your phone working again, mate? I suggest you stick with your stock ROM until tomorrow, then I'll walk you through the ROM's I've used and that'll help you make your pick and I'll help you with installing them, as well.
The fact that it's midnight here and that I get up at 6 for classes tomorrow is the reason you will have to wait for me
niksy+ said:
Had a safe day Some bloody hooligans were on the bus home, though... Goddamn idiots. Anyway, on the brighter side of life...
You got your phone working again, mate? I suggest you stick with your stock ROM until tomorrow, then I'll walk you through the ROM's I've used and that'll help you make your pick and I'll help you with installing them, as well.
The fact that it's midnight here and that I get up at 6 for classes tomorrow is the reason you will have to wait for me
Click to expand...
Click to collapse
Bloody hooligans should just go home and stay there
Yepp its working now but in a rush as i always is, its now running MS2Ginger 3.0, thought i´ll go that route till there is a proper ICS version of something out there
Thanks for all the help, with it i would for sure still be in pure panic mode
Know anything about overclocking the Defy+?
FlashTec80 said:
Know anything about overclocking the Defy+?
Click to expand...
Click to collapse
SetVsel
King_Rat said:
SetVsel
Click to expand...
Click to collapse
Ok i´ll try that, how high is it possible to go to still be stable?
FlashTec80 said:
Ok i´ll try that, how high is it possible to go to still be stable?
Click to expand...
Click to collapse
I'm glad you got to MS2G by yourself
I think the best way is to overclock in Recovery. You'll find the CPU menu when you open it and there you'll see 3 or 4 different settings. Every setting has a clock option and a vsel option. vsel sets the amount of electrical power that the CPU gets at a certain clock.
Best way to overclock would be to go step by step. Increase the highest clock setting by 50MHz, then reboot your phone and see if it works OK If it doesn't boot successfully or it hangs while you're using it - increase the vsel by 1. Then if it's stable, go on, another 50MHz+ and testing again...
Other than that, you can just set it to 1200MHz at once and increase the current vsel for that clock setting by 3-4, that would probably work as well
I have never overclocked mine, though Well, actually, the WIUI ROM come's with overclocked setting itself, it was at 1.1GHz, but it was slower than Pikachu at 1.1GHz So, overclocking doesn't help as much as a good ROM does At least that's my opinion.
P.S. CM9 (ICS) is wonderful But, you should wait for a couple more builds, while the things get even better. For me, CM9 and stock ROMs (including ms2ginger) are the best! You can always test, anyway I've come down to CM7 from CM9 and I'm truly sad
Defy+ stuck at boot amnimation
Hello everyone, my Defy+ stuck at Motorola boot animation. And I have the message below when Volume Up + Boot key :
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB
My sbf is :
DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTFR004.0R_PDS03C_USAJRDNGIBRRTFR_P020_A024_M002_Service1FF.sbf
With the others it just doesn't work.
Please help me.
Well, why don't you flash that sbf to get it back to life?
FlashTec80 said:
Ok i´ll try that, how high is it possible to go to still be stable?
Click to expand...
Click to collapse
I'm on 300 - 19, 700 - 33, 1200 - 54...
just don't set your tweaks @ boot until you've fully tested them ^^ yet a cache clear would rectify being stuck in b/l
That sbf is the only one to make at least my phone stuck in the boot loop.
The others just don't show me anything, I got a black screen.
Maybe the sbf isn't the good one ?
I have done a backup of my system before I used rsd lite. How can I restore it as it's not a sbf file but a directory with .img ... files ?
Good replies every1, i dont know if im doing anything wrong here.
I first installed SetVsel app and changed the values in there, then when running stabilitytest it said i had the value i had chaged to. Uninstalled the app and tried to change value directly in 2ndinit but now when running stabilitytest it sais i only have 1000Mhz, thou in 2ndinit it clearly sais that vsel4 is set to 1200, any idea?
Cheers and have a safe day every1
Edit: "vsel sets the amount of electrical power that the CPU gets at a certain clock", so how high is it possible to push it before i see smoke coming out of my phone?
FlashTec80 said:
Good replies every1, i dont know if im doing anything wrong here.
I first installed SetVsel app and changed the values in there, then when running stabilitytest it said i had the value i had chaged to. Uninstalled the app and tried to change value directly in 2ndinit but now when running stabilitytest it sais i only have 1000Mhz, thou in 2ndinit it clearly sais that vsel4 is set to 1200, any idea?
Cheers and have a safe day every1
Edit: "vsel sets the amount of electrical power that the CPU gets at a certain clock", so how high is it possible to push it before i see smoke coming out of my phone?
Click to expand...
Click to collapse
You need to enable overclock in 2ndinit or load all modules enabled for it to take effect of your changes..
farsight73 said:
You need to enable overclock in 2ndinit or load all modules enabled for it to take effect of your changes..
Click to expand...
Click to collapse
Good post
Could someone with an non overclocked Defy+ make some runs in Quadrant Benchmark, i only made one run before i started changing things
Would also be fun to see some figures on an ordinary Defy
Just two hours left of work this week, then Top Gear Live is the thing for the evening
I did solve my problem. Thanks to anyone
godbod said:
Hello everyone, my Defy+ stuck at Motorola boot animation. And I have the message below when Volume Up + Boot key :
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB
My sbf is :
DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTFR004.0R_PDS03C_USAJRDNGIBRRTFR_P020_A024_M002_Service1FF.sbf
With the others it just doesn't work.
Please help me.
Click to expand...
Click to collapse
go to recovery mode and wipe to the factory setting.
this happened because your phone is confused between the old and new firmware..
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 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).
This is the support thread for the Sprint variant of the StarKissed Note 4 kernel.
This kernel currently supports all North American carriers through the use of specialized release packages that will detect your device version and make appropriate adjustments.
Kernel Development Thread:
http://forum.xda-developers.com/showthread.php?t=2915824
Issues, Reports, & Configuration
Direct installation available via Flashify (for root users) - Android Apps on Google Play
Heimdall with the S5 patch is needed to flash from a computer. Odin cannot flash this kernel.
Additional information for Sprint variant:
Potentially Unavailable:
Potentially Unsafe:
Incomplete / Inactive:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
egodriver07 said:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Nothing. It's an issue with the policies. I will be compiling a new version shortly that should address it.
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
still no luck
twistedumbrella said:
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
Click to expand...
Click to collapse
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Thank you very much for the suggestions yesterday, but it looks like not using the _64 toolchain was the problem.
New problem, it boots to the download mode screen saying boot failed. I thought I'd start simple to troubleshoot. If I break apart one of your images (14 MB) and rebuild it with:
Code:
mkbootimg --kernel twisted-zImage --ramdisk twisted-ramdisk.cpio.gz -o boot.img
The resulting boot.img is 11 MB, whereas yours is 14 MB, and it fails to boot. I'm not sure why it's several MB smaller. I looked at your script, but the image generation is in another script it seems. Am I using an old mkbootimg or something? I don't know could account for 3 MB at the mkbootimg stage. I also tried using unmkbootimg to get the other flags shown below, but that didn't help.
Code:
--base 0x1dfff00 --cmdline 'splash=silent console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --pagesize 4096
Thanks again for any suggestions.
ffolkes said:
Thank you very much for the suggestions yesterday, but it looks like not using the _64 toolchain was the problem.
New problem, it boots to the download mode screen saying boot failed. I thought I'd start simple to troubleshoot. If I break apart one of your images (14 MB) and rebuild it with:
Code:
mkbootimg --kernel twisted-zImage --ramdisk twisted-ramdisk.cpio.gz -o boot.img
The resulting boot.img is 11 MB, whereas yours is 14 MB, and it fails to boot. I'm not sure why it's several MB smaller. I looked at your script, but the image generation is in another script it seems. Am I using an old mkbootimg or something? I don't know could account for 3 MB at the mkbootimg stage. I also tried using unmkbootimg to get the other flags shown below, but that didn't help.
Code:
--base 0x1dfff00 --cmdline 'splash=silent console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --pagesize 4096
Thanks again for any suggestions.
Click to expand...
Click to collapse
Kernels now use DTB. The other script handles that. You also may need a new mkbootimg if you have never dealt with DTB. Older binaries don't include the parameters.
In all honesty, most of these questions can be answered just by looking at the commits in the stockish repo. It doesn't contain all of the extra modules and modifications, but it has the same core changes to build it. If 50 commits seems like too much to dig through, you may not want to develop kernels. You will typically be wandering through kernels with 1K+ commits looking for one change.
twistedumbrella said:
A new version has been posted that should resolve the reset on boot.
One thing to keep in mind is that if you are using an app to handle your settings, allow the phone to fully boot before launching the app. Sometimes opening it right away will end up reading the boot settings and replacing the settings it was about to load with those. The startup settings are hard-coded into the kernel and changing them tends to cause a bit of instability that isn't worth introducing.
Click to expand...
Click to collapse
Still no luck with the new version.
fifapro23 said:
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Click to expand...
Click to collapse
fifapro23 said:
Still no luck with the new version.
Click to expand...
Click to collapse
Nothing was changed in respect to that issue as you have noted by replying to the same post both times.
fifapro23 said:
It still doesnt stick. I try to underclock the min and it still goes up to 1497600.
Click to expand...
Click to collapse
I just read this statement again and realized this is our first real case of PEBCAK
The minimum is the absolute lowest the cpu is allowed to drop.
The maximum is the absolute highest the cpu is allowed to increase.
It is a range, not strictly one or the other.
If you set your min to 268 and max to 2.5, it is not 268 or 2.5 only. It could also be anything between them, such as 1.5 or 422
Yankeractive tends to favor 1.5, but that is in the governor design. It's something that will eventually be adjusted during cleanup.
sorry
I reverted back to 20.47 from 22.12 because it was sticking at 1.4. Also for fast charge options, what does failsafe do? And do we just keep fast charge to disable or force ac?
ryanalan82 said:
I reverted back to 20.47 from 22.12 because it was sticking at 1.4. Also for fast charge options, what does failsafe do? And do we just keep fast charge to disable or force ac?
Click to expand...
Click to collapse
I haven't looked into failsafe. I used the defaults from the Note 3 for that since I never use it.
Depends if you use it or not. Disabled is will not boost USB or wireless charging. Force AC will boost them to emulate an AC charger.
Ok now having the 1.4 sticking on 20.59. Reverting to earlier today.
ryanalan82 said:
Ok now having the 1.4 sticking on 20.59. Reverting to earlier today.
Click to expand...
Click to collapse
The update was only posted about 5 minutes ago. It will show 1.4 when you touch it because that is the touch boost.
How do i download your kernel i csnt figure out how to find it.. it just keeps tskimg me to mega website????
shawn01 said:
How do i download your kernel i csnt figure out how to find it.. it just keeps tskimg me to mega website????
Click to expand...
Click to collapse
Installation Instructions:
Download the image file from Goo or Mega to install via flashify, rashr, etc
Click to expand...
Click to collapse
If you don't feel like looking back at the big discussion in the dev thread on issues with Mega, that is the alternative.
sorry im struggling here. I installed twrp and booted into recovery and now i cant boot my phone back it goes nack to twrp but something comes up saying kernel is not seandroid enforcing set warranty bit: kernel. I never fladhed anything but twrp. So im hoping to find stovk kernel zip so i can flash fro, twrp..
shawn01 said:
sorry im struggling here. I installed twrp and booted into recovery and now i cant boot my phone back it goes nack to twrp but something comes up saying kernel is not seandroid enforcing set warranty bit: kernel. I never fladhed anything but twrp. So im hoping to find stovk kernel zip so i can flash fro, twrp..
Click to expand...
Click to collapse
If it says warranty bit is kernel, that isn't booting back into recovery, that is a normal boot. You just have to be patient until it finishes. The downloads here are not the stock kernel anyway. Both versions are modified kernels.
It goes back to trwp recovery every time
**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930A_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930A_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Will it work for g935a? And does it fix lag?
Sent from my SAMSUNG-SM-G935A using Tapatalk
Awesome!
Ok how many folks have successfully flashed this?
It's still using eng boot? And will I be able to update super su script once installed? Also curious if maybe deodexed means I can get v4a running on this bad boy sorry for the question blast just excited to see the att s7 taking off into #root =D in Texas it goes "y'all got root?!"
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Can you fix the URL? I get a 404 when clicking it.
Thanks,
Aaron
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
smknutson said:
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
Click to expand...
Click to collapse
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
I think I am. It's either this Rom or the eng bootloader, but it runs hotter. It's running in interactive governor but cpu temperature is averaging idle at 45°c whereas on stock it felt much cooler. Something about this installation is causing this thing to heat up.
Carlos Terán said:
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
I'm not sure what lag you're referring to?
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
noobtxtech said:
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
Click to expand...
Click to collapse
Haven't tried v4a but Wanams modified Xposed is working and I have several modules operational.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
dirtydodge said:
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
Click to expand...
Click to collapse
Modified Odin for both EngBoot and this threads addon .zip
smknutson said:
Modified Odin for both EngBoot and this threads addon .zip
Click to expand...
Click to collapse
Ok thank you. Figured so but just wanted to make sure. I'm downloading the Rom now. Glad you found the fix and debloat from the Verizon thread, I seen that the other day and used it and his other guide on how to set up Greenify and amplify. My phone is running awesome on the stock rooted but I always like to grab muniz's deodex versions and run them.
Also, if you want to get rid of the Custom icon on boot and reset it to Official in status, use the XTouchWiz xposed module.
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
joe3681 said:
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
Click to expand...
Click to collapse
You have to be rooted prior to flashing this.
Clearly. I meant post flash
joe3681 said:
Clearly. I meant post flash
Click to expand...
Click to collapse
" To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy! " is copy pasted from the OP so that would imply that it isn't rooted until you root it, as for why you would want a deodexed Rom (which is a performance hit) without root is beyond me. From what I gather reading this short thread you will need root and possibly even xposed to get it running right. In order to do that you would have to do some more reading. Hope this helps.