Related
i have a motorola droid and it is rooted.i flashed a new rom and then i flashed sprecovery,i let it run its course and i disconnected the phone.when the phone turns on it starts up and then a red light comes on and my phone says please connect charger.it keeps saying android process is not responding and then the phone shuts itself off.ive tried to boot it into recovery mode and do a restore,it keeps giving me an error that says nandroid exited with status 20 and its also not reading my sd card.can somebody tell me whats happened and if it can be fixed???please and thank you
Well, seems as if you need to reflash or restore because of bad flash. If you try flashing again make sure you wipe data and cache. As far as not reading sdcard I have same problem not sure why but when I'm in recovery and I choose install zip which I used clockworkmod recovery, if it fails then it reboots automatically after couple seconds not sure if this happens with sprecovery. After sdcard mount fail it shuts down and reboots so before it reboots I pull the battery and wait a minute or two before trying again. It may take me 3 to 4 times of doing this but eventually it will mount sdcard in recovery. I recommend keep trying till it allows you to apply recovery file and then flash to either clockworkmod or sprecovery which ever one you not using and then flash back to the one you want. I'd also recommend try if after all this you flash rom again and same thing happens redownload it and try again. Good luck.
Sent from Droid using, Sapphire v1.0.0/ 928Droid Black Glass 2.2 Theme/ Sholes 1.0 Ghz 7 Slot Kernel.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
fadimck said:
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
[*]Auto Kill Level --> Safe
[*]Auto Kill Frequecny --> Every One Hour
[*]Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Click to expand...
Click to collapse
Okay, I didn't know this info as I've Milestone with stock OS 2.1
Sent from my Milestone using XDA App
Hey everyone.
As I spend some time on studying Ext4 for the Galaxy S devices, working on Voodoo lagfix, and based on what I saw in mount logs it's possible that the performances could be increased without altering data integrity nor filesystem integrity in case of crash.
On /data, noauto_da_alloc is not used.
This option activates a sort of Ext3 emulation mode, which force sync on write close without sync.
It also comes with a speed penalty for SQLite writes, and is unneccessary when hardware barriers are enabled.
Barriers allow usage of delayed allocations without risk. Delayed allocations are the key to performance for modern filesystems.
as root:
Code:
mount -o remount,noauto_da_alloc /data /data
You can count on me to cook a kernel with this mount option as default
PS: this option is already used in Voodoo kernels for Galaxy S devices / has been chosen after extensive performance and reliability tests.
Okay, kevin_teslacoil run quadrant:
before:
<kevin_teslacoil> 1676 for the full quadrant bench mark
after:
<kevin_teslacoil> interesting
<kevin_teslacoil> 2422 this time
<GuiPer> :O
<Ibanez33> wtf?
I'm not a fan of quadrant, but used as a tool, it can give some useful infos
Also, note that this dramatic change in benchmark result won't be as incredible in real life usage.
But still, it's a better choice of configuration, using the filesystem driver like it should be given the hardware parameters.
Can this be implemented in Voodoo for SGS?
Reference, from man mount.
auto_da_alloc|noauto_da_alloc
Many broken applications don't use fsync() when noauto_da_alloc replacing existing files
via patterns such as
fd = open("foo.new")/write(fd,..)/close(fd)/ rename("foo.new", "foo")
or worse yet
fd = open("foo", O_TRUNC)/write(fd,..)/close(fd).
If auto_da_alloc is enabled, ext4 will detect the replace-via-rename and replace-via-trun‐
cate patterns and force that any delayed allocation blocks are allocated such that at the
next journal commit, in the default data=ordered mode, the data blocks of the new file are
forced to disk before the rename() operation is commited. This provides roughly the same
level of guarantees as ext3, and avoids the "zero-length" problem that can happen when a
system crashes before the delayed allocation blocks are forced to disk.
Click to expand...
Click to collapse
I'm trying this now.
jaju123 said:
Can this be implemented in Voodoo for SGS?
Click to expand...
Click to collapse
It's already implemented in Voodoo
Okay thanks
Still at it I see?
We lose this whenever we reboot I'm assuming?
Quadrant scores:
Before: 1672
After: 2334
Cook this into some good 1.2GHz OC/UV
We already know the Hummingbird can potentially hit 1.6
Its late, nevermid
Preparing a kernel with this option activated as default.
Anderdroid said:
We lose this whenever we reboot I'm assuming?
Quadrant scores:
Before: 1672
After: 2334
Cook this into some good 1.2GHz OC/UV
We already know the Hummingbird can potentially hit 1.6
Click to expand...
Click to collapse
fstab
10 char
Could you please implement this new mount option in your Vibrant "voodoo" kernels? Much appreciated! Thanks for your hard work, Curio!
zimphishmonger said:
Could you please implement this new mount option in your Vibrant "voodoo" kernels? Much appreciated! Thanks for your hard work, Curio!
Click to expand...
Click to collapse
Already told. This is the default mount option for Voodoo, after extensive analysis for both performance and filesystem+data integrity
I am using the latest of the trasig OC kernel for JPO and tried this options with no changes in quadrant. (1720)
deleted...................
Does this work on the galaxy tab?
futuregerald said:
Does this work on the galaxy tab?
Click to expand...
Click to collapse
no.
go to the galaxy tab section
Lagfix
So does this revert upon a reboot? I tried it on my SGTab and nothing happened, just want to make sure there is nothing i need to "undo" other than just rebooting. Thanks!
cba1986 said:
I am using the latest of the trasig OC kernel for JPO and tried this options with no changes in quadrant. (1720)
Click to expand...
Click to collapse
Doesn't work for me either on Galaxy S with JH3 (stock Telstra ROM other than root). Quadrant score actually dropped (916 to 896).
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Very nice m8,
i'm using it on my CM7 Build #0, with much apps i have 156MB free..
cool man sounds orsum will have to add this to my new rom
Would you say this is better than the normal Froyo App2sd? is it any faster at loading the apps one the sd card loading from **** drive mode?
Froyo app2sd sucks, this one is heaps better as apps are stored on ext partition, so you save way more internal phone memory. And yea its fast.
Sent from my HTC Wildfire using XDA App
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
I have now installed this, how do i know apps are being moved to the sd card?
I would love to for those roms. I'll have to look at the roms. Unfortunately, I don't have a ZTE Blade, but I don't own most of these phones that Darktremor works on (I only have a Sprint Hero and a Sprint Evo).
The more roms, the better.
danne_jo said:
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
Click to expand...
Click to collapse
Run a2sd check. That will check the configuration and tell you if everything is setup correctly.
-Howad- said:
I have now installed this, how do i know apps are being moved to the sd card?
Click to expand...
Click to collapse
You can also just start "Titanium Backup" and check memory in the main screen
I installed Darktremor app2sd on Modaco custom rom (Froyo), and must say its excelent, I got internal memmory of 160 mb free, and now with 100 apps installed have 155 mb free. My ext3 partition is 512 mb and Dalvik cache is on ext3. With zipalign phone work well, no issues about stability, widgets work normal (its not case with Froyo a2sd).
Thanks Tkirton for this.
bump---new version available.
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
I want to know about that too. Can we flash the new version on top of the original one? Will it harm the installed apps?
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Just flash on top of it.
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
WackyWookie said:
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
Click to expand...
Click to collapse
Describe the steps that you went through in installing it, including any commands you ran after the install.
vilks said:
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Click to expand...
Click to collapse
tkirton said:
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
Click to expand...
Click to collapse
Ah good I was starting to doubt my phone's installation, good to know it's a bug...
Sent from my HTC Wildfire using XDA App
Hello all,
I just rooted my nook color using the ManualNooter 4.6.16 after updating my stock ROM to 1.3. Now I am trying to run the CPU OC using the Nook Color Tweaks. I am very Noob to this but am very tech savvy.
I know that I need to flash one of Dalingrin's OC kernel's but I really have no idea where to start. And since I am new to the forum I cannot post directly in one of those existing threads yet.
Can I get a step by step instructions on this and which kernel I need to download please? I searched high and low through all of the threads and cannot figure out which kernel i need and how I flash it?
Thanks
DO A FULL BACKUP FIRST
I used Dalingrin's OC kernels found here - http://forum.xda-developers.com/showthread.php?t=925451
There's a link that says 'All kernels hosted here'. Scroll down to the 090111 folder and pick the emmc file.
Throw it onto your bootable CWM card's root directory.
Boot into CWM
Wipe cache partition
Advanced
Wipe Dalvik Cache (mine locked up completely after doing this - just reboot the unit by pressing and holding the power button until it powers off, and then turn it back on.)
Install zip from SD card, select the kernel linked above, and voila.
After that's complete, remove your bootable card and select reboot.
thanks!
thanks for the directions, they worked perfectly. Now what do I do. I am able to get into the CPU settings through the Nook Color Tweaks, but I'm not sure how high I should be setting all the different CPU Stepping stages? Or is this pretty much trial and error? I've read that i can use SetCPU. Is that true or should I stick with the Nook Tweaks?
I could be way off here, but I believe it's already setup to be OC'ed compared to stock.
I have also installed SetCPU.
There are few settings out there on the thread for the kernel. Check out the later pages.
carbfrze said:
thanks for the directions, they worked perfectly. Now what do I do. I am able to get into the CPU settings through the Nook Color Tweaks, but I'm not sure how high I should be setting all the different CPU Stepping stages? Or is this pretty much trial and error? I've read that i can use SetCPU. Is that true or should I stick with the Nook Tweaks?
Click to expand...
Click to collapse
If you allow SetCPU to show recommended settings the app will show you suggested paramenters that should allow you to OC without digging into all the esoteric settings. I've always just used the slider bar to clock up a step at a time to find the point I like and is stable. For me, about 1.4 seems most stable for what I run.
another problem
ok, i was changing the settings in the Step 2 options under the Nook Tweaks app and must have messed something up. It was stuck in a boot loop. It would get to the Nook Color animation boot screen and then reboot constantly. It would boot into the O/S every once in a while but would immediately lock up and not allow me to change any settings or anything. I tried wiping the Davlik Cache along with some other suggestions but could not get it running again.
I ended up wiping it and going with the latest CM7 build that has the built in Dalingrin's app. Having issues with that but I will post another thread to get help with that.
Thanks for the suggestions!
NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk
Damn this looks complicated as hell haha. Good job OP
Very nice job
Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me
I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?
Did you disable APK signature checking?
elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?
Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works
Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?
For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.
My rom is stock 4.4.4
I will try again with disabled optimization.
kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference
Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.
I tried again but this time booted upto lock screen and rebooted.
I tried with new build.
after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english