Related
OK, here's my first real contribution to the Android community... and I owe all credit to the amazing cooks out here...
I take no credit for anything, other than the fact that I kanged Paul's, Pershoot's, Cyangen's, intersectRaven's, Ivan Dimkovic's and Termana's work...
PLEASE READ THIS WHOLE POST BEFORE DOWNLOADING AND FLASHING. I SUGGEST U READ THE POSTS OF THE ORIGINAL KERNEL AUTHORS AS WELL.
This is a mod of the Desire Camera R2 port by Paul.
I just pushed the changes to various kernel mods including the stock CM506 kernel.
This should work on any stock version of CyanogenMod... tested on CM 5.0.5.x & CM 5.0.6... These mods should work with other ROMs as well, but I have not tested any. Try at your own risk.
Instructions:
1. Pop the zip file onto your SD card.
2. Reboot into Amon RAs recovery.
3. Do a nandroid backup [VERY IMPORTANT IN CASE YOU FACE SOME PROBLEMS!].
4. Select "Flash zip from SD" and select this zip.
5. Reboot.
Note:
This will flash a modified Pershoot's OC/UV kernel boot.img and replace the camera app. Flashing the boot.img is necessary since this mod requires a change in init.rc. Flashing another boot.img will cause the Desire camera to FC. If you want to flash another kernel, flash the zImage and push the wlan ko. Please use at your own risk (but, no this will not brick your phone).
Known Issues:
You might encounter FCs if you use NexTheme Goodies add-on.
Update (4/26):
Using Pershoot's UC/OV & UC/OV Xtra kernel mods
Using intersect Raven's AVS kernel mods
Using Ivan Dimkovic's AVS & AVS OC kernel mods
Using Termana's .34rc3 kernel mod
Update (4/27):
Using Pershoot's UC/OV & UC/OV Xtra 33.3 kernel mods - 4/26
Using intersect Raven's AVS 33.3 kernel mods - 4/27
Using Ivan Dimkovic's 800mv AVS 33.2 kernel mods - 4/26
Update (4/29):
Using intersect Raven's 800mv AVS 33.3 kernel mods - 4/29
Using Termana's OC/UV 34rc5 kernel mod - 4/28
Update (5/2):
DIY kit and How-To document added (Desire-Camera-R2-DIY).
Update (5/3):
Using intersect Raven's 800mv & 925mv BFS & CFS AVS 33.3 kernel mods - 5/3
Using Ivan Dimkovic's 800mv & 925mv OC & Non-OC AVS 33.3 kernel mods - 5/2
Using Pershoot's UC/OV & UC/OV Xtra Old Wifi & New-WiFi 33.3 kernel mods - 4/30
Using Termana's OC/UV 34rc6 kernel mod - 5/2
Download Folder
MD5 Checksums:
d6358ed5fc703ba90887c83637a814dc Desire-Camera-R2-CM506-signed.zip
c4ab1b086aa8109d0ffba0dbb8bb7862 Desire-Camera-R2-intersectRaven-800mv-BFS-05.03-signed.zip
667d4d9706790be904ad730d2b3a1c64 Desire-Camera-R2-intersectRaven-800mv-CFS-05.03-signed.zip
834c4e9981c253a1db66b40c9d6ae2e8 Desire-Camera-R2-intersectRaven-925mv-BFS-05.03-signed.zip
89d44934cac30476dcda704c9d6d18fa Desire-Camera-R2-intersectRaven-925mv-CFS-05.03-signed.zip
83bf81f254bf2ad54ec4b2dc795816ac Desire-Camera-R2-Ivan-800mv-Diet-hybridAVS-05.02-signed.zip
a9a7c4de52d79627ceb3a56bce40021d Desire-Camera-R2-Ivan-800mv-Diet-hybridAVS-OC-05.02-signed.zip
f1493e367513c577dc1f5360aed3f347 Desire-Camera-R2-Ivan-925mv-Diet-hybridAVS-05.02-signed.zip
5681838cfcaab3c2bfe6c2c8da061972 Desire-Camera-R2-Ivan-925mv-Diet-hybridAVS-OC-05.02-signed.zip
5e82cbeb57ba21f99bdb3d0de4053d3f Desire-Camera-R2-Pershoot-OC_UV-04.30-signed.zip
09109216cd0f7e9b636b0a0077a7b613 Desire-Camera-R2-Pershoot-OC_UV-NewWiFi-04.30-signed.zip
91e035eb60e06069623331cb98f388c5 Desire-Camera-R2-Pershoot-OC_UV_Xtra-04.30-signed.zip
78a04c5ae08f5d31ad13c6552e90933e Desire-Camera-R2-Pershoot-OC_UV_Xtra-NewWiFi-04.30-signed.zip
848a556b8cde374a47b2c73ca62f1ea1 Desire-Camera-R2-Termana34rc6-OC_UV-signed.zip
If you encounter any problems like FCs, please post a logcat.
Have fun!!!
Um... maybe also include the steps to install it?
Foxy Roxy said:
Um... maybe also include the steps to install it?
Click to expand...
Click to collapse
Download it and flash it via Recovery console..
Huey85 said:
Download it and flash it via Recovery console..
Click to expand...
Click to collapse
Don't forget the nandroid BU. =) Flashing this now. Thanks!
Huey85 said:
Download it and flash it via Recovery console..
Click to expand...
Click to collapse
Lol I know how to do it, but I'm just asking him to make it noobie friendly.
I consistently get "Your SDCard is Full" message when trying to take the pic.
GNja said:
I consistently get "Your SDCard is Full" message when trying to take the pic.
Click to expand...
Click to collapse
That strange. It works fine for me when I take pictures. Hopefully someone can help you with that issue. :S
Btw, thanks Craig I'm so glad that I can use the desire cam again ^^ I miss it so much ~~~
Reflashed the Kernal update and it works now...I had been using CameraZoom, but think I'm going to uninstall it now as I never really used the plugins.
Thanks!
It works Thank You
Um nevermind... I take back what I said about the fact that it's working properly... it actually isn't.
The camera occasionally closes on me. Sometimes it also restarted my phone when I try to open it too.
Why there is a need to install it together with boot image ? Isn't it just a regular system application with additional libraries ?
If this is a case, is it possible to remove the boot image from the package - this way it can be used by anyone who want to run a different kernel and it won't be any need to reflash the kernel after installing this?
Foxy Roxy said:
Um nevermind... I take back what I said about the fact that it's working properly... it actually isn't.
The camera occasionally closes on me. Sometimes it also restarted my phone when I try to open it too.
Click to expand...
Click to collapse
Try Wipe Cache and Wipe Dalvik-Cache and Reset Battery stats... for me it help.
dimon1983 said:
Try Wipe Cache and Wipe Dalvik-Cache and Reset Battery stats... for me it help.
Click to expand...
Click to collapse
Ok I'll try that right now and see if it helps.
... Nope, does not help for me.
Oh well. Reverting back to my backup ~
Foxy Roxy said:
... Nope, does not help for me.
Oh well. Reverting back to my backup ~
Click to expand...
Click to collapse
strangely...
Try Wipe Cache and Wipe Dalvik-Cache and Reset Battery stats and then flash this Camera\Kernel mod
Or try separately flash Kernel and then flash Camera\Kernel mod... I was the flashing of a kernel before flash this mod and no doing Wipe
Sorry for my English
dimon1983 said:
strangely...
Try Wipe Cache and Wipe Dalvik-Cache and Reset Battery stats and then flash this Camera\Kernel mod
Click to expand...
Click to collapse
That's what I did ^^;
You should probably mention that by using this, one also overwrites the current kernel.. No good if you use another kernel that the one supplied with this .zip.
Nice work!
Is there a way to change the default names of the pic?
"date_time.jpg" would be nice so they are ordered correctly in gallery..
Pochemuchka1977 said:
Why there is a need to install it together with boot image ? Isn't it just a regular system application with additional libraries ?
If this is a case, is it possible to remove the boot image from the package - this way it can be used by anyone who want to run a different kernel and it won't be any need to reflash the kernel after installing this?
Click to expand...
Click to collapse
Actually, this has changes in init.rc (to initialise the htc framework) which can only be changed by flashing the boot image. So no, there's no way to get it working without flashing the boot
Update to the universal overclock. I've tested it working on several ROMS... seems to be better than my first one. Based off dumfuq's latest OC kernel for CM5 which is based off the latest cyanogenmod. Instructions are the same as below. Let's set some G1s on fire!
EDIT WIFI FIXED NOW
UNIVERSAL OVERCLOCK VERSION 2.01 WIFI FIXED
This can be flashed right over what you have now
EDIT IT DOES WORK ON 1.5-1.6 ROMS !!!!!
Below you'll find a link to an overclock update.zip ... all you have to do is flash it, regardless of your ROM and use set cpu to tweak your settings. It will allow you to clock the CPU up to 825mhz!!! Anything over 768mhz locks up the phone so you may want to set a max value via userinit.sh. 652mhz seems to be stable for me
WARNING: Overclocking can shorten battery life and kill the PROC on your phone. I'm in no way responsible for your phone getting hotter than the sun and exploding.
NANDROID BEFORE FLASHING THIS
I'm not a DEV... i just like to tinker. All I did was notice this and throw it all together--------CREDIT GOES TO Dumfuq, Koush and Pershoot for making this possible
Instructions:
----------------------
INSTRUCTIONS HAVE BEEN CHANGED
*Download and install setcpu.
*Select auto detect (ensure it is set at 528mhz) make sure "set on boot" and "ondemand" are selected
*Download and flash THIS update.zip up to 652mhz Stable or this stable 576mhz overclock from Pershoot from recovery and reboot
*Go back into setcpu... hit "menu" and select autodetect again ...you'll notice you now have frequencies for up to 825mhz
*Configure min and max frequency to your liking (652mhz seems to be best for me) (you may want to set a sleep profile of 245min/245max since you won't need OC while you aren't using the device)
*Enjoy
TESTED AND WORKING ON Cyangenmod 5.0.7 / KingKlick's ERIS2G1 / ZXHero 1.5 / ZXHero 2.1 / KingKlick's Legend2G1 / NoSense 1.5 / HTC CLay's Superfast / ALL CSDI ROMS !
ive been waiting on something like this thanxxxxxx
but installation aborted it said something like E: kernal
mccurt29 said:
ive been waiting on something like this thanxxxxxx
but installation aborted it said something like E: kernal
Click to expand...
Click to collapse
What ROM are you flashing this on top of?
Agreed, the zip isn't signed correctly. Here's a working version.
Might want to thank Koush and Pershoot for the kernel script too.
This sounds awesome, it could make many sense roms much more usable as a daily!! Will flash and test later tonight when I get home from work. Thanks!
carl2990 said:
i get
E: Wrong digest:
Kernal/zImage
E:Verification failed
using cannon v2.0
Click to expand...
Click to collapse
Sorry for the confusion I did not sign the zip properly. SHOULD BE WORKING NOW.
Would you be willing to talk about how this works and how it can work on any Rom. I would be interested in knowing that.
EDIT ... Actually I found some info in the overclock thread. Thanks.
billquinn1 said:
Would you be willing to talk about how this works and how it can work on any Rom. I would be interested in knowing that.
Click to expand...
Click to collapse
Uses Anykernel.zip created by Koush
updater-script runs and extract the boot.img from your current ROM.
It unpacks the boot.img into kernel and ramdisk.
It repacks newboot.img with the new kernel and the same ramdisk.
It flashes the newly created boot image.
I got the source HERE
infinitybiff said:
Uses Anykernel.zip created by Koush
updater-script runs and extract the boot.img from your current ROM.
It unpacks the boot.img into kernel and ramdisk.
It repacks newboot.img with the new kernel and the same ramdisk.
It flashes the newly created boot image.
I got the source HERE
Click to expand...
Click to collapse
This is very clever. Thanks.
0o koush's anykernel from github nice thinking
sunsean said:
This sounds awesome, it could make many sense roms much more usable as a daily!! Will flash and test later tonight when I get home from work. Thanks!
Click to expand...
Click to collapse
makes Eris2G1 fly!!!!!!!!!!
So if I'm reading this right, your using koush's anykernal method (which pershoot uses on his kernals) with dumfuq's patch. Good ****.
You might want to let people that dumfuqs kernal defaults to 8xx at boot, so a lot of people won't boot if they don't set default boot after flashing. This can be done with userinit.sh or in /system/banner or something like that if u don't have an ext partation w/userinit.sh. its explaind how to push the line in other theard. Id copy and paste here, but I'm driving right now, lol.
You also might want to give pershoot xtra kernal a shot also. It maxes at 576, but also has other optimasations included and if stable on all g1's.
fastludeh22 said:
So if I'm reading this right, your using koush's anykernal method (which pershoot uses on his kernals) with dumfuq's patch. Good ****.
You might want to let people that dumfuqs kernal defaults to 8xx at boot, so a lot of people won't boot if they don't set default boot after flashing. This can be done with userinit.sh or in /system/banner or something like that if u don't have an ext partation w/userinit.sh. its explaind how to push the line in other theard. Id copy and paste here, but I'm driving right now, lol.
You also might want to give pershoot xtra kernal a shot also. It maxes at 576, but also has other optimasations included and if stable on all g1's.
Click to expand...
Click to collapse
Thanks for the heads up. I've edited the instructions to install set cpu first so when they flash the update it will still boot up at 528 and they can change accordingly
Can we use an alternative other than SetCPU?
flexnix said:
Can we use an alternative other than SetCPU?
Click to expand...
Click to collapse
I'm pretty sure you can set the max speed via userinit.sh.... something like
"#!/system/bin/sh
echo 633600 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq"
in other news i just got this to work on a 1.5 sense ROM!!!!!!
Thanks, I'm about to test this out
Thanks bro!
Does anyone know if I can just flash this ota with just my phone? I downloaded the zip ota, and astro shows that it's on my sd card, but when I go to recovery to flash zip, it's not showing up...?
Just impatient to try this cuz it sounds sweet, lol, but I know if I can't do it ota I can do it later tonight at home...
sunsean said:
Does anyone know if I can just flash this ota with just my phone? I downloaded the zip ota, and astro shows that it's on my sd card, but when I go to recovery to flash zip, it's not showing up...?
Just impatient to try this cuz it sounds sweet, lol, but I know if I can't do it ota I can do it later tonight at home...
Click to expand...
Click to collapse
move the file to the root of your sdcard if you downloaded OTA its probably in sdcard/downloads or something
hi
I clean flashed cromi-x 5.4 and ran the quadrant benchmark and get around 5000.
according to the screenprints of results here, I should be getting 7500ish.
can anyone explain or help?
the tf is unusably slow. at least 5 second lag before it responds to anything.
in twrp mod, it flies though. any ideas???
azreal8 said:
hi
I clean flashed cromi-x 5.4 and ran the quadrant benchmark and get around 5000.
according to the screenprints of results here, I should be getting 7500ish.
can anyone explain or help?
the tf is unusably slow. at least 5 second lag before it responds to anything.
in twrp mod, it flies though. any ideas???
Click to expand...
Click to collapse
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
You are running Quadrant in performance mode, are you?
Did you choose to install with fsync off?
Try data2sd but that lag is not normal even with fsync on....
Tons of widgets on your home screens? Tell us more about your setup.
hi..
no widgets but for one (asus weather).
my microsd port is not working so i can't use data2sd.
i did a wipe and clean install of cromi-x 5.4 with the extreme tweaks bunds and selected to disable the fsync and my quadrant standard edition results are still "poor".
my concern is more WHY my devices frezzes and takes at least 5 seconds to even respond after i launch and app or even press the settings button despite a new rom and kernel.
doesn't that suggest something else is amiss?
berndblb said:
You are running Quadrant in performance mode, are you?
Did you choose to install with fsync off?
Try data2sd but that lag is not normal even with fsync on....
Tons of widgets on your home screens? Tell us more about your setup.
Click to expand...
Click to collapse
azreal8 said:
hi..
no widgets but for one (asus weather).
my microsd port is not working so i can't use data2sd.
i did a wipe and clean install of cromi-x 5.4 with the extreme tweaks bunds and selected to disable the fsync and my quadrant standard edition results are still "poor".
my concern is more WHY my devices frezzes and takes at least 5 seconds to even respond after i launch and app or even press the settings button despite a new rom and kernel.
doesn't that suggest something else is amiss?
Click to expand...
Click to collapse
That is really strange and unusual and certainly a PIA. But let's make sure we are on the same page:
Define what you mean by 'clean install'
Post your bootloader and recovery versions please.
yes has me baffled so am here for help
when I am in twrp, I press install and along the process i'm asked if I want to wipe which is the recommended option. I select this option.
is that the correct way?
side point/question, what does it mean if when going thru aroma installer, the TF flies but is unusable when running a rom, stock or otherwise?
azreal8 said:
yes has me baffled so am here for help
when I am in twrp, I press install and along the process i'm asked if I want to wipe which is the recommended option. I select this option.
is that the correct way?
side point/question, what does it mean if when going thru aroma installer, the TF flies but it unusable when running a rom, stock or otherwise?
Click to expand...
Click to collapse
So you never did a clean install
The option in the installer only wipes cache and Dalvik. You HAVE to wipe /data before installing a new rom.
Boot into TWRP.
Go to Wipe
Just swipe the button
That will wipe all your apps but not your personal files like pictures etc.
Then reflash the rom, select _that's kernel, select fsync off, select the two GPU options and everything else you desire.
Once the Aroma installer finished it's your choice if you want to try CROMi-X as is or flash LMK's tweaks right away.
Once you reboot, you will have to go through the setup process again, reinstall all your apps but I can almost gurantee: It will be worth it!
What is wrong with your microsd card slot? This could be causing other issues if the device thinks it has to keep polling for something that isn't there.
thanks!
wiped properly and just did the install.
let it settle for a while and quadrant score was 6600 so im happy with that. i ran it earlier and it varied from 3500 to 4500. is that odd?
the result is still less than the 7500+ though. ideas? i'll have to look up these LMK things you mentioned....im a newbie.
seems like the freezing has been solved such that the tablet is usable...fingers crossed it stays that way.
berndblb said:
So you never did a clean install
The option in the installer only wipes cache and Dalvik. You HAVE to wipe /data before installing a new rom.
Boot into TWRP.
Go to Wipe
Just swipe the button
That will wipe all your apps but not your personal files like pictures etc.
Then reflash the rom, select _that's kernel, select fsync off, select the two GPU options and everything else you desire.
Once the Aroma installer finished it's your choice if you want to try CROMi-X as is or flash LMK's tweaks right away.
Once you reboot, you will have to go through the setup process again, reinstall all your apps but I can almost gurantee: It will be worth it!
Click to expand...
Click to collapse
sbdags said:
What is wrong with your microsd card slot? This could be causing other issues if the device thinks it has to keep polling for something that isn't there.
Click to expand...
Click to collapse
all of a sudden the microSD slot doesnt work.
the slot on the keyboard however does. is that weird?
quite disappointing. also as i've unlocked, ive lost my warranty.
azreal8 said:
thanks!
wiped properly and just did the install.
let it settle for a while and quadrant score was 6600 so im happy with that. i ran it earlier and it varied from 3500 to 4500. is that odd?
the result is still less than the 7500+ though. ideas? i'll have to look up these LMK things you mentioned....im a newbie.
seems like the freezing has been solved such that the tablet is usable...fingers crossed it stays that way.
Click to expand...
Click to collapse
6600 is very respectable for the TF700 and it should feel quicker. 7500 is extreme - I doubt most users will get that - I never did on ET either
sbdags said:
6600 is very respectable for the TF700 and it should feel quicker. 7500 is extreme - I doubt most users will get that - I never did on ET either
Click to expand...
Click to collapse
Haha, you never get up to 7500... My average on the latest ET is around 7800ish and pass 8000+ on the high end.. BTW, if you would like to try out the new ET, please give the .9 a run because I am be able to have an extra one hour comparing to the .8 without performance loss. The average battery life on my daily usage on .8 is about 4+ hours and the .9 is about 5+ hours. Please give some feedback if you try it, thanks..
LetMeKnow said:
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
Click to expand...
Click to collapse
newbie question..
just trying now...where is the init.d folder ? i looked using root explorer and dont know the path.
cannot see a systems folder.. thx
azreal8 said:
newbie question..
just trying now...where is the init.d folder ? i looked using root explorer and dont know the path.
cannot see a systems folder.. thx
Click to expand...
Click to collapse
It should be under /system/ect/init.d..
If you flash my zip file, everything should set up properly for users to use...
LetMeKnow said:
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
Click to expand...
Click to collapse
Got 5800 Max with this one.
I'd like to try another cromi-x which has scores in the 9000s.
It needs bootloader version 10.
How do I get this? Newbie qn I know..
azreal8 said:
Got 5800 Max with this one.
I'd like to try another cromi-x which has scores in the 9000s.
It needs bootloader version 10.
How do I get this? Newbie qn I know..
Click to expand...
Click to collapse
That score seems like you were running balance mode which is set 1.4GHz for CPU and 520MHz for GPU. My balance mode is around 6000+. You could try to run the quadrant in Performance mode and should be easy getting 7500+ on your current setup...
I don't think there is a 9000+ score for Cromi X unless you are running ART on Crombi kk. There are only two users running Cromi X with the score 8000+. One is lucius.zen who set the CPU with 1.9GHz and GPU with 700MHz on Hund's kernel. The second user is set the CPU with 1.8GHz and 700MHz with GPU on Hund's kernel... If you can get that 9000+ on Cromi X, then you are the first user who is achieved the best score out of this tf700 forum, good luck....:fingers-crossed:
If you want to update the bootloader to .10, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=2688891
I hope that helps...
LetMeKnow said:
That score seems like you were running balance mode which is set 1.4GHz for CPU and 520MHz for GPU. My balance mode is around 6000+. You could try to run the quadrant in Performance mode and should be easy getting 7500+ on your current setup...
I don't think there is a 9000+ score for Cromi X unless you are running ART on Crombi kk. There are only two users running Cromi X with the score 8000+. One is lucius.zen who set the CPU with 1.9GHz and GPU with 700MHz on Hund's kernel. The second user is set the CPU with 1.7GHz and 700MHz with GPU on Hund's kernel... If you can get that 9000+ on Cromi X, then you are the first user who is achieved the best score out of this tf700 forum, good luck....:fingers-crossed:
If you want to update the bootloader to .10, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=2688891
I hope that helps...
Click to expand...
Click to collapse
Cool. Was wanting to try this one..
http://forum.xda-developers.com/showthread.php?t=2672751
skimmed the link but couldn't see how to change to .10.
I tried saving the Asus firmware to an SD and renaming but my tf didn't detect and update..
azreal8 said:
Cool. Was wanting to try this one..
http://forum.xda-developers.com/showthread.php?t=2672751
skimmed the link but couldn't see how to change to .10.
I tried saving the Asus firmware to an SD and renaming but my tf didn't detect and update..
Click to expand...
Click to collapse
Oops, it is my bad.... You could follow the Cromi X first page to update your bootloader but you may want to update your twrp after that because it is an old version of the twrp, good luck....:fingers-crossed:
LetMeKnow said:
Oops, it is my bad.... You could follow the Cromi X first page to update your bootloader but you may want to update your twrp after that because it is an old version of the twrp, good luck....:fingers-crossed:
Click to expand...
Click to collapse
cool. was trying to flash the asus .10 version with twrp and it failed.
can someone pls confirm if i have done something wrong?
this is what i did:
1 boot into twrp
2 clicked install button
3 selected the asus extracted zip file ( renamed to this to EP201_768_SDUPDATE.zip as apparently its a trick) which i saved on my internal drive
4 swiped to install
result - got failed message.
azreal8 said:
cool. was trying to flash the asus .10 version with twrp and it failed.
can someone pls confirm if i have done something wrong?
this is what i did:
1 boot into twrp
2 clicked install button
3 selected the asus extracted zip file ( renamed to this to EP201_768_SDUPDATE.zip as apparently its a trick) which i saved on my internal drive
4 swiped to install
result - got failed message.
Click to expand...
Click to collapse
What does the failed message say - it probably tells you what failed?
Also extract the recovery log from TWRP after.
@zephiK , I installed the VomerTweaks on top of Mahdi rom and Franco kernel from your signature. I flashed it via TWRP , but dont know if its installed or is successfull etc. Can you let me know what exactly this tweak does and any way of finding if its active / installed ? Is there a option which appears in settings ? Thanks !
You didn't have to make a new thread for this.
To verify that the settings indeed have loaded, you need to use a kernel tweaker app (e.g. FKU, Trickster)... if you see that the maximum (fixed) CPU frequency is 1.2GHz then its loaded. A lot of the questions you asked are answered https://192.227.135.147/get/vomertweaks.txt (ignore the warning)
# What is it?
VomerTweaks is a tried and tested set of custom settings and power modes for your device!
The aim is to enable your device to have insane battery life without losing performance (all of us love da juice!)
We develop and test multiple configurations (for different "user types") & share them with the community.
Click to expand...
Click to collapse
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
shapethelola said:
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
Click to expand...
Click to collapse
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
zephiK said:
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
Click to expand...
Click to collapse
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
You need to reinstall Franco if it's supported yet that's all
dayanandgp said:
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
Click to expand...
Click to collapse
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
You need to reinstall Franco if it's supported yet that's all
Click to expand...
Click to collapse
No, flashing a newer/older version of Franco does not touch this script at all.
zephiK said:
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
No, flashing a newer/older version of Franco does not touch this script at all.
Click to expand...
Click to collapse
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
shapethelola said:
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
Click to expand...
Click to collapse
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
zephiK said:
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
Click to expand...
Click to collapse
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Check this post for download links:
http://forum.xda-developers.com/showthread.php?p=55150676
Sent from the One
dayanandgp said:
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Click to expand...
Click to collapse
I removed it since the links were just all over the place. Refer to nikzDHD's link above ^^.
To uninstall, just flash vt_uninstaller.zip
@zephiK sorry to ask this here, but is it possible for someone to build chroma rom for oneplus one? would be great right?
Hey guys and gals.
So I got myself a new/old HOXL and immediately flashed a Candy5 ROM on it with all lollipop and CM12 bells and whistles. To keep things even more interesting, I threw a nice package of google apps on top of it and enabled Google Now.
Guess what I found out immediately after my phone booted
My phone was sloooooooow. Like, it was fast for 1 hour or so after reboot and then it started to drag. After a day of moderate usage it became barely usable; sometimes I would miss a phone call because it wouldn't show me the bloody dialer and let me answer.
My phone was sucking battery like a thirsty camel in an oasis in the middle of Sahara desert... ok, ok, just don't throw that tomato at me. Anyway, I was losing 10-15% of my battery per hour.
So, I started messing around with the phone and found out several interesting things. I think it's worth sharing and discussing. In the next posts, I will share my findings with you. Please share yours.
My goal is pretty obvious: fast, smooth experience on CM12 and decent battery life. I was getting 2 full days of moderate usage on my good ol' HD2, so that's my current target with HOX. I also want Google Now working, at least to some extent. I especially like the feature when it shows me my parking location and things around me, so disabling locations altogether is not an option.
First step to smoothness: swap and OOM
DISCLAMER. The script below plays with your system settings. It might cause bootloops, brick your device or start nuclear war. Please use at your own risk.
So, first thing I noticed was that the phone was getting slow because it didn't have enough memory to run. I figure that CM12 and lollipop in general is probably optimized for 2GB RAM, whereas our device has only 1GB. So I tried to play with OOM values, but didn't get the desired results. So I went and enabled swap. Guess what? Works like a charm.
Here's how I did it:
1. install SuperSU from here .
2. open it and let it install its su module. this part might be tricky; for me, doing this via recovery didn't work and regular install didn't work either. i ended up having to open ADB terminal and setting SELinux to permissive manually, like so:
su
setenforce 0
and only after that did it succeed to push its su module to system/xbin.
3. go to SuperSU's settings and make sure you have checked the following:
a. Enable Superuser
b. Enable su during boot
c. Trust system user (this is not mandatory; however, if you don't check this, you will be flooded with requests to grant su to system apps)
4. after you have everything set up, reboot to recovery and install the attached zip like you would install a ROM.
5. reboot and enjoy your new silky smooth HOX
This script enables swap on data and cache. The files are pretty large, too: 250MB on data and 250MB on cache. I saw that even with this I still have plenty of room on data and cache to keep rolling. This gives me 0.5GB of swap, virtually enlarging my RAM to 1.5GB. This seems to be enough for all my needs.
The script also sets swappiness to 50, sets OOM to the values that work best for me at the moment and brings over several optimizations from my HD2 ROM. Feel free to edit the values and share.
EDIT: uninstalling script attached
EDIT2: scripts updated to reflect my latest changes.
EDIT3: reduced small (small_swap.zip) attached for those who want to use swap with ZRAM
Second step to smoothness: kernel
This step proved to be extremely important for smoothness. For some reason, stock CM12 kernel appears to be severely underoptimized... or the kernels that our devs generously made available for us are heavily overoptimized
To my best knowledge, currently there are only two kernels that work with LP and support swap: Torched Kernel v1.4 and Frosted Kernel.
IMPORTANT: if you are going to flash Torched kernel, be sure to flash LP version 1.3 or 1.4. Previous versions break swap, thus hurting speed and stability
IMPORTANT: if you are going to flash Bricked kernel, you ABSOLUTELY MUST flash the voltage table (see this post). First flash the kernel and then the voltage table. Not following this procedure can damage your phone.
I am currently using the Bricked kernel and the results are extremely impressive.
Third step to smoothness: Ext4 optimizations: disable journaling, enable dir_index
This step helps quite a bit if you decide to stay with ext4 for now. But even if you don't and want to switch to F2FS (see step 4), it's worth doing it on the /system partition.
WARNING. Journaling slows your system down quite a bit but it also adds stability. Please beware. You may lose your data or may even have to reflash your ROM in some extreme cases.
I never experienced any problems with non-journaling systems, but be aware that google enabled it for a reason.
Note: Your system might became unstable only if you forcefully shut the device down by long-pressing the power button or if you run out of battery. In case of normal work and normal shutdowns/restarts, everything will be fine.
1. Flash the attached zip (no_journal.zip).
2. Profit! Your cache, data and system partitions have no journaling now.
Fourth step to smoothness: F2FS
It took me some time to figure out this one, but it proved to be extremely helpful in terms of speed and general smoothness. Stability is yet to be tested, but I have it for ~24 hours now, and everything looks fine so far.
0. You need a F2FS-enabled TWRP. Luckily, we have jrior001 with us, who took care for that. Grab it from here (please thank jrior001 in his thread).
1. Install Torched kernel 1.4. (Bricked supports F2FS too, but for some reason, the performance is degraded and the stability is much worse than with Torched).
1a. If you had Bricked installed, remove undervolt script from /system/etc/init.d
2. Install attached zip (evita_F2FS_conversion_v2.0_pav.zip). This will enable you to work either with ext4 (with some extra optimizations) or with F2FS, so you can always go back without having to remove it. (note that you'll have to flash this zip each time you install a new kernel)
3. In TWRP, go to Backup, select data and cache and unselect system. I also disabled compression, just in case. Start the backup and wait for it to finish.
3a. STOP! Check that backup returned no errors. If there were errors during the backup, don't go any further or you'll lose your data!
4. Now connect your device to the PC. On PC, browse to Computer\One X\Internal Storage\TWRP\BACKUPS\<number of your device>\<latest backup>
5. You will see a bunch of files whose name contains ext4. For example, data.ext4.win.md5
6. Go ahead and change ext4 to f2fs for each file. The names should now look as follows: data.f2fs.win.md5
7. Back in TWRP, choose Restore -> your latest backup.
8. Sit back and relax while TWRP reformats your data and cache partitions as F2FS and restores all your data.
9. Reboot and enjoy!
10. If you'll ever want to go back to ext4, just go to TWRP, connect your device to the PC, on your PC, restore the original names of the backup files (rename f2fs to ext4), in TWRP choose restore and you're back to where you stated
First step to battery life: wakelocks
1. Go to Settings -> Privacy -> Privacy guard.
2. Scroll down till you reach the word Google.
3. Enable privacy for everything that starts with the word Google, including (!!!) Google Play Services.
4. Long-tap to enter each row and disable "keep awake" and "wake up" wherever applicable
Also, I use ServiceDisabler (from Play Store) to enter Google Play Services and disable Google Analytics
Second step to battery life: WIFI
Settings -> WI-FI -> three dots on top of the screen -> Advanced.
Disable "Keep WIFI on during sleep" (set to never) and "Scanning always available"
Third step to battery life: build.prop
Attached is my modified build.prop. It is derived from the stock build.prop, with some important tweaks that I brought over from my HD2 ROM. The measurements here are not that objective, but I felt that I could squeeze ~30% more juice from a single charge.
Of course, uninstall script is attached as well, just in case.
Fourth step to battery life: data usage
1. Head to Settings -> Data usage.
2. Scroll down till you see Google App.
3. Click on it and enable "Restrict app background data".
4. Go back and scroll further down till you find cLock.
5. Enable "Restrict app background data" as well.
for me
another one for me
last one for me
Cannot end a call by pressing the red button.. After unswap everything is normal again.. Can you please check it?
Nice work!!!!
How did u unswap ?
My phone was kinda cool.... Until I flashed this, my phone lagged the more.
Nice work BTW.
I want to unswap please!
Flash unswap.zip.. But i just notice that despite unswapping problem still persists.. Maybe it.s a cm12 bug.. I dont know
flashing unswap.zip should remove any traces of what swap.zip has done. if the problem persists after you flashed unswap, then the problem is elsewhere
I downgraded firmware from 2.18 to 2.15 and now i can terminate the calls.. I also install your swap file in latest cm12 02.19 nightly and seems to work fine..
I flashed Candy 5 and noticed that even after installing Torched kernel and overclocking, optimizing, etc, my phone would slow to a crawl by the end of the day and it definitely wasnt a memory problem as I had plenty free. What I found was that randomly my IO settings reset to 128Kb read-ahead and the scheduler resets to ROW. Changing back manually to 512Kb and FIOPS and suddenly the performance is back to what it was. This has happened twice in two days and I'm not sure if this is a Torched/CM/Candy/or Lollipop bug but at least I figured out what was causing it....
Hi thelonewolf_pav,
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work? I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now. I hope torched can figure out what the problem is. Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps. One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Thank You,
Hi harpin,
harpin14789 said:
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work?
Click to expand...
Click to collapse
nope. it starts alright, but it's never actually used
harpin14789 said:
I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now.
Click to expand...
Click to collapse
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
harpin14789 said:
Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps.
Click to expand...
Click to collapse
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
harpin14789 said:
One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Click to expand...
Click to collapse
very simple. run terminal from the phone or start ADB. then type:
free
Click to expand...
Click to collapse
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
thelonewolf_pav said:
Hi harpin,
nope. it starts alright, but it's never actually used
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
very simple. run terminal from the phone or start ADB. then type:
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
Click to expand...
Click to collapse
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
harpin14789 said:
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
Click to expand...
Click to collapse
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
harpin14789 said:
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
Click to expand...
Click to collapse
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
thelonewolf_pav said:
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
Click to expand...
Click to collapse
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
harpin14789 said:
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
Click to expand...
Click to collapse
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
thelonewolf_pav said:
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
Click to expand...
Click to collapse
ok, thanks