Related
Hi, I'd post a reply here http://forum.xda-developers.com/showthread.php?t=883175&page=75 or http://forum.xda-developers.com/showthread.php?t=938200&page=18 but this is my first post so I cannot post a reply
Here were my steps to get it all together. For reference, here is the link in the dev section (that I can't respond to).
Background: The 1.1 update installed without my knowing on a rooted 1.0.0 NC. It would go to the intro animation and would stall and restart in an infinite loop. I decided to take the plunge to Nookie Froyo on the eMMC.
I had also installed Customized Nookie Froyo 0.5.9 on a Patriot Class 10 card and it was painfully slow and market was not working. When I did this with the latest version to the eMMC it was fast and did not have any problems in either regard.
Steps:
-- Burning the image --
I unzipped and followed directions for my Mac OS X system: http://nookdevs.com/Nookie_FroYo:_Burning_a_bootable_SD_card
I booted off the SD Card, literally turn it on with the new MicroSD in there, this is the Clockwork Recovery
I went into "mounts and storage" Formatted boot, system, and data in that order. The volume keys are navigation, N button is select, and power is back. After formatting "boot" I had to restart by holding down the power key for some reason (non-responsive), but it was fine.
I then went to Wipe my Cache BEFORE restoring. I know the instructions place it last, but think about it. You want to clear everything before hand rather than after you've re-imaged it.
Then I restored the zip. You will have to select the zip.
Twiddle your thumbs. When it's done writing, you'll know cause it'll say done. Now you can take out your SD card. Go back to the Main Menu of CWR and select reboot. It'll pop you out to Nookie FROYO!
First things, first. Unlock, and then re-lock, this gets rid of lag.
Set up your Wireless, then set up an Account for Gmail in Settings > Accounts.
I then went into "Settings->Applications->Manage Applications-> Google Services Framework -> Clear Data" There was no Cache for the Market at this point.
I let it sync everything, while I set other things up (e-mail acct, time, and etc)
Then I went into Market to get Appbrain. Success!
When I synced with Appbrain I still couldn't "see" certain apps in the Market. So I went into:
Settings->Applications->Manage Applications-> Market->Clear Cache and
Settings->Applications->Manage Applications-> Google Services Framework -> Clear Data
AND REBOOT
I then saw a lot of the other apps, but couldn't find Angry Birds :-(
Finally, wanted to see how it performs as an eReader, but when I stuck my SD card in there. Crap, couldn't see it at all
Had ADB installed which is necessary and run these commands with these vold files found here ( http://dl.dropbox.com/u/313036/volds.zip ): http://forum.androidcentral.com/bar...ion-install-nookie-froyo-internal-memory.html (as well as on xda-net.
Couple of things with ADB, the screen must be on, otherwise the device goes offline and you're get protocol errors. The reboot never happened on its own, so I did it manually. SD card is recognized!
Couldn't be happier. Works very well. It's speedy without the 1.1Ghz kernels.
Those were my experiences. It's rather straightforward.
Oh forgot to mention one CAVEAT. My Power button is really really sensitive now. Like a capacitive charge turns it on (I am putting absolutely no pressure on it). Any workarounds for this?
I am enjoying the 0.6.6 flashable Nookie Froyo experience. But, I haven't yet figured out how to get the Market App on the device. Am I missing something obvious?
you should be able to find the apk in the dev section, install via adb
I'd recommend installing CUSTOMIZED Nookie Froyo as opposed to Nookie Froyo which is very vanilla whereas the customized version has a lot of things already set up -- such as the Market, Google Apps, Softkeys and SuperUser.
where does one find this CUSTOMIZED version. i assume not on xdda becaue it includes gapps>?
cray1000 said:
where does one find this CUSTOMIZED version. i assume not on xdda becaue it includes gapps>?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=938200
I am using 0.6.6 and made the updates you see in the first post
Updated my SD card to CM7.0.3 and want to use an overclock kernel.
Which one is best to use from the downloads available here do you just use the latest 040411 or are some of the test builds good?
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
findmike said:
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
Click to expand...
Click to collapse
how is the battery usage when overclocked?
When I first set up my SD card the following instructions were in the thread concerning overclocking
5a. *Optional* If you want to run an overclock kernel you need to choose and download a compatible kernel for SD (not eMMC).
5b. Move the uImage file from the SD card to your pc as a backup.
5c. Rename the oc kernel you have downloaded uImage copy it to the SD card.
Can I simply take the zip file for the 042411 kernel open it and swap the uImage files. I saw in another thread about flashing it.
Had lots of trouble getting the 7.0.3 update to take, timing the hold the n and power buttons trick.
Also I saw something about using setcpu to overclock, can someone fill me in on that, is it software or somewhere in the CM7 settings?
s52m3 said:
how is the battery usage when overclocked?
Click to expand...
Click to collapse
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
RASTAVIPER said:
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
Click to expand...
Click to collapse
Are you talking about this app
https://market.android.com/details?id=com.teamwin.kernelmanager.free&feature=search_result
Battery life seems to be pretty good right now but I understand the latest CM builds have some fixes that help increase battery life. I don't think the overclock really effects battery life all that much since the vast majority of the time it doesn't need to kick into high speed.
For the install of the kernel, I normally just flash that when I flash the OS and Gapps. If you are running CM7 off your SD card, I can't help much there except to say that it's SOOOO much easier to run off eMMC since I can just use the built in Rom Manager App to jump into Rom Manager and update things without having to have a bootable card or modifying any files.
Regardless of SD / eMMC install, you don't need to use SetCPU with CM7. If you get the kernel installed, just go into Settings / CyanogenMod settings / Performance / CPU settings and you can change. Most people use the OnDemand performance governor with 1300 max and 300 min and set on boot checked.
I leave Set on Boot off in case something goes goofy. I just reset the overclock to 1300MHz when ever I reboot with a new build.
I could never get the 424 OC to load on my Nook (always got the "expected ) error) so I just swap the OC kernel and system folder into each new build. It's a few extra steps but at least it works.
I'm running N67 at 1300MHz from a Sandisk Class 4 16GB card. Works great!
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
GTT1 said:
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
Click to expand...
Click to collapse
You're running CM7 off an SD card, unless you want to mess up whatever you have on internal eMMC, don't go changing scripts or flashing things which don't apply to your install. Whichever way you got your CM7 installed, stick to the original instructions and follow up on the original threads instead of grabbing bits and pieces here and there. You'd save yourself and others a lot of confusion.
Hey guys, I'm loving my new N1, but I keep running out of room for applications, and I wanted to know if I could implement Apps2sd ext2/3/4 or w.e to make more room. I like to use Cyanogen Mod, but I'm not sure how to implement it. If someone could help me, that'd be great! Thanks!
Ditto.
Sent from my Nexus One using XDA App
Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...
danger-rat said:
Try S2E or Link2ext in the market, our go look up Darktremors. Depending on what you want, the apps should be more than sufficient...
Click to expand...
Click to collapse
When i use darktremors, it doesn't work, but if I type in a2sd reinstall, it says location is read only
Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...
danger-rat said:
Try to fix permissions via ROM Manager. Also, try flashing DT before you flash gapps...
Click to expand...
Click to collapse
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting
Try the DT thread... xD
isikh said:
I tried that; it didn't work. Also, when I run a2sd reinstall, and reboot, its stuck on rebooting
Click to expand...
Click to collapse
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.
zero2cx said:
Not been my experience. Strange that. What works for me...
Boot to recovery of your choice.
Do multiple wipes, both cache + dalvik-cache. Though just one wipe each is likely enough, IMO. Also wipe sd-ext.
Write your CyanMod of choice.
Write your gapps.
Write your DarkTremors. Go with the latest, OR, as others are insisting, stay away from that and go with the previous stable release. Latest works great for me.
Reboot device.
Wait a good minute after arriving at lockscreen and reboot device from lockscreen, OR find Quick Boot in app drawer if your power button is gorked (you'll need a working power button to reboot from lockscreen).
After reboot, wait a good minute at lockscreen. Then Proceed to open terminal session and start playing with a correctly installed (hopefully for you) DT2ext.
Lots of experts out there, but this has always worked for me. If you still need guidance, search in DarkTremor's thread to be advised about your partitions.
Click to expand...
Click to collapse
Thank you, I figured it out.
DT is the best choice, but S2E is simpler than DT, it's avaliable in market
Q&A for [Kernel][CPU OC][GPU OC][F2FS] CroPol kernel
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
doesn't work
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.
vietnam131 said:
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.
Click to expand...
Click to collapse
Afaik it doesn't support 4.3.x ROMs. Try any 4.4.x ROM.
Ok, I will try. But if you can make this kernel for previous versions of Android, it would be nice.
i cant get 1150/2000 mhz
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.
snakeboy1011 said:
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.
Click to expand...
Click to collapse
Try pegasusqplus+sioplus.
mauam said:
Try pegasusqplus+sioplus.
Click to expand...
Click to collapse
what should i put as the min frequency?
snakeboy1011 said:
what should i put as the min frequency?
Click to expand...
Click to collapse
100 or 200. You need to try by yourself
what ROM do you use as I don't think CyanogenMod supports 1150/2000mhz?
mauam said:
100 or 200. You need to try by yourself
Click to expand...
Click to collapse
Sorry for your time
deep sleep bug? reboot bug? voltage limits? persistent config by userinit.sh?
Hello!
I got several questions regarding the usage of this kernel's voltage and clocking/voltage options:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
3. I noticed 1200MHz not being completely stable on my device. So I wanted to increase the voltage for step9.
In /sys/kernel/liveopp/arm_slot09 i saw the default hex value for VARM was 0x3f. So I tried increasing this to 0x40 and 0x41, but the voltage shown in this file didn't increase anymore.
3a) So is the voltage capped at 1362,5000mV or is it just not displayed correctly?
3b) Will increasing Varm to more than 0x3f do anything at all?
Also I've seen the voltage called Vbbx (default value for step9: 0xff)
3c) What exactly is this voltage, and how does it go together with Varm?
3d) Is there a way for increasing voltage any further than 0x3f for Varm and 0xff for Vbbx?
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Many thanks for patience and help!
Elmarigo said:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
Click to expand...
Click to collapse
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Elmarigo said:
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
Click to expand...
Click to collapse
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Elmarigo said:
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Click to expand...
Click to collapse
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09
xhhb said:
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Click to expand...
Click to collapse
Hello!
I'm using Carbon Rom by novafusion. There's an update from 27.10. now, and I'll see later if this helped against this particular problem!
xhhb said:
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Click to expand...
Click to collapse
In Carbon there's an option for applying saved values on boot. I used these and I also tried CoCoreManager, but both didn't apply my saved config although I had enabled this setting.
xhhb said:
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09
Click to expand...
Click to collapse
Ok, I will try this. Is userinit.sh being executed as root by automatic?
Thank you!
Ok, i found multiple bugs in my script and corrected these.
The script currently is like:
Code:
#!/system/bin/sh
echo set_volt=1 > /sys/kernel/liveopp/arm_step09
echo varm=0x41> /sys/kernel/liveopp/arm_step09
The commands are working from terminal/SSH, but playing them in /data/local/userinit.sh doesn't change anything after reboot. (file is marked as executable!)
So can anyone help please how to make this working?
I still believe it's maybe because of the script not being executed with root permissions, but I'm not sure about that and I don't know how to work around this without a sudo command.
Also I still could use help with my remaining questions from my older post: http://forum.xda-developers.com/showpost.php?p=56343298&postcount=10
Thank you!
PS: this 10message restriction for 'new users' doesn't seem like a working way for keeping the forum's content at good quality.
I'm forced to writing in Q&A-Thread, while the creator and the other most experienced users of original thread don't even seem to look here.
Aswhile, the 'more experienced' users, having more then 10messages, in original thread are keeping the most experienced users busy, asking questions that are even way more basic than mine, but regarding the same topic (persistent undervolting). So I can't help these users and no one from that other thread can help me
Not working on miui
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!
chaudhary1122 said:
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!
Click to expand...
Click to collapse
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Nope, I guess not. So I'll give it a try now!!! Thanx!!!!
Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!
wifi and bt not work
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks
chaudhary1122 said:
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!
Click to expand...
Click to collapse
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
LaInfluenza said:
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks
Click to expand...
Click to collapse
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.
Elmarigo said:
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.
Click to expand...
Click to collapse
The fact that the kernel is pretty good, I loved it but I need the wifi I use it all day and does not serve me well beyond virginity v14 rom that I really like, I tried it on the newest cm11 but I do not really like this rom I hope for the next update will fix this kernel as serious buenisimo roms have oc in stock or stock -based.
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