Database Develop

[Q] Help with Quadrant Standard

I DL the app from the market. It installs. When I try to run it, it hangs on I/O database writes. Waiting does not produce FC it just sits there (in excess of 5 mins waiting)
Stats:
CM7 RC4
Overclock Kernel 600/1100 (Tried 300/800 no diff)
SD speed boost at 2048 (pny 4g)
Any help is appreciated.

Are you using the most recent OC kernel? There was a problem with one of the older ones. You want to wipe dalvik-cache after flashing a new OC kernel.

Thanks, I have only downloaded 1, it was dated3/31.

Is it ok to wipe dev cache and regular cache with root explorer?

Allsack said:
Is it ok to wipe dev cache and regular cache with root explorer?
Click to expand...
Click to collapse
As far as I know, yes. Your system may freeze after clearing Dalvik-cache, it's a known bug. Just hold down the pwr-button till the nook turns off. Reboot, and you should be good to go.

[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]

[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]
Hello everybody!
I got inspired by mero01, who made similar tools for my previous mobile phone, the HTC Desire HD.
Imho a new version of an Android ROM should NEVER ever do a full wipe. Personally I prefer to wipe on my own AND to _personally_ have the option which file system is going to be used.
That's why I've created my own zip files, which do either a FULL_wipe or an easy_upgrade_wipe.
These zip files could work on multiple phones, but they are only tested and confirmed to be working on the LG Optimus 2x (P990). Just for the sake I've also implemented a check inside of them if that's the phone, which the wipe(s) are performed on.
**** !NONE WILL FORMAT YOUR SDCARD! ****
I DON'T TAKE ANY RESPONSIBILTY FOR DATA LOSS OR ANY DAMAGE CAUSED TO YOUR DEVICES. USE AT YOUR OWN RISK!!! UNDO IS NOT POSSIBLE!
PREREQUISITES:
* Clockworkmod Recovery (recommended version: v6.0.2.5)
INSTRUCTIONS FOR EVERY FILE:
Code:
1. Download the zip file you want.
2. Place it anywhere in your /sdcard/
3. Reboot into CWM recovery
4. Install zip from sdcard
5. CONFRIM --- CAUTION! THIS IS UNDO-ABLE!!!
6. done :)
7. Don't reboot, flash any rom you want
8. Flash it
9. Reboot and have fun! ;)
FULL_WIPES
This patch comes in two versions (EXT3 and EXT4) and needs to be applied prior to the flash of any ROM. It will WIPE your device and format all partitions either in EXT3 or EXT4.
Wipes performed:
* SYSTEM
* DATA
* CACHE (always EXT3)
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
EASY_UPGRADE_WIPES
These patches also come in the previous two versions (EXT3 and EXT4) and there is an additonal lite variation, which won't wipe your dalvik cache. Use the easy upgrade wipes if you DON'T want to remove your data (especially useful for ROM upgrades)!
Wipes performed:
* SYSTEM
* CACHE (always EXT3)
* non lite versions: Wipes the dalvik cache on DATA
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
NO_JOURNAL
This won't do any wipes, but will remove the JOURNAL(S) on your file systems. If it gets applied to EXT3 partitions it clearly results in EXT2 partitions.
You will get the fastest possible EXT* file systems if it is applied to the EXT4 partitions.
It can also be applied on already existing file systems, although I'd suggest to use a clean file system. Make a backup if you still want to perform it, because it can be dangerous!
Wipes performed:
* NONE
CHANGELOG:
Code:
[U]2014-06-23[/U]
- New LITE easy upgrade wipes available, which won't clean your dalvik cache.
[U]2012-12-10[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.5 (ICS versions only)
- Fixed system partition wipe.
[U]2012-11-27[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.4
- Fixed progress bars.
- Now available in two versions: one for the old (GB), one for the new (ICS) partition layout
- Easy upgrade wipes will now also clean the dalvik cache
- All full and easy wipes re-made from scratch, please use with care and eventually perform a backup before using them.
[U]2011-12-28[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.3
- First public release
************************************************************
[U]2012-12-10[/U]
NO_JOURNAL v0.3 (ICS version only)
- Fixed system partition converting.
[U]2012-11-27[/U]
NO_JOURNAL v0.2
- Fixed progress bars
[U]2011-12-28[/U]
NO_JOURNAL v0.1
- First public release
Have fun!
Greetings,
dr4go

Frequently asked questions (FAQ):
What is the difference between the o and n versions?
The o stands for OLD-, whereas n is an abbreviation for NEW-partitioning layout. Unfortunately LG changed the location of the data partition (from mmcblk0p8 to mmcblk0p9).

so what's the difference between the erase/reset data factory on CWM???

By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.

koboltzz said:
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
Click to expand...
Click to collapse
Exactly. Thanks for the answer koboltzz.
For the HTC Desire HD there was also an EXT4 version of CWM available, which changed the default algorithms of the "Wipe data/Factory reset" and the "Format" options to EXT4.
But with the latter possibility you loose the ability to format EXT3 partitions. That's also why I always used mero01's zip files to accomplish wipes.
Imho it's the best option, because if you REMOVE the formatting lines from the ROMs you want to flash it's absolutely no problem to also use an EXT3 designed ROM (like Hypnos2X for example) on EXT4 file systems (that's the operating system I'm currently on).
And I tell you also because I dislike the FULL wipes on nearly every ROM available for the LG Optimus 2X. If you have a problem and just want to reinstall the ROM without loosing any data there is no way to do that.
Yes, an easy wipe should always be done by the standard ROM zip itself - of course... but I've always also removed those lines, because that way you also get the freedom of the file system.
It's up to you...

sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
Using it and after that flashing Fr19 with ext4 Kernel (from modaco) -> no boot at all ->freezing
This will not happen, if you first do a fullwipe by cwm (ext3), then flash Fr19 and after that use the universal converter to ext4 from benee.
But this only changes data and system partition to ext4 by default.
There is definitely something wrong with the script, an other example:
First flashing 0-full_wipe_0.3_ext4.zip
after that Fr19 ROM (up to this point it would have been a bootfreeze, look above)
and after that flashing universal converter to ext4, phone will boot now, but will not be able to install any app 'there is insufficient space' (which is totally not true), most likely because cache partition is fu.cked up by 0-full_wipe_0.3_ext4.zip
Time for version 0.4

koboltzz said:
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
[...]
Time for version 0.4
Click to expand...
Click to collapse
I will look into it. Thank you for the additional information.

Delete this comment i guess i need to learn how to read im sorry!

dr4go said:
I will look into it. Thank you for the additional information.
Click to expand...
Click to collapse
Anything new to this?

koboltzz said:
Anything new to this?
Click to expand...
Click to collapse
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.

dr4go said:
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
Click to expand...
Click to collapse
hey dr4go got something weird here...
when i flash your ext3 zip everything is fine atleast the mount command say so
but then when i want to convert them to ext2 something really weirds occur the system partition becomes ext2 but the data and cache partition become ext4 according to the mount command using recovery 5.0.2.7R2

Here is the convert tool made by Topogigi, and slightly modified by me to include /system conversion.
/cache has not the same parameters it seems.

First (and second) post(s) updated.
And I'll promise you also to release something bigger next time. Guesses won't be commented.

ONly comment I can do is: Nice to see you my friend! How are you?

carburano said:
ONly comment I can do is: Nice to see you my friend! How are you?
Click to expand...
Click to collapse
Everything fine here! Nice to see you too. I finally found some free time and also motivation, because of the marvellously working CyanogenMod 10 on our phones. It's unbelievable... I was nearly freaking out when reading the notice.
And you? How are you? Hopefully everything is also great on your side?

Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app

maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea

spica1234 said:
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thank you. As you may have realized... a little busy as usual... otherwise totally fine. How is it on your side? Everything ok?

cojo11 said:
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
Click to expand...
Click to collapse
What exactly did you do? And which ROM did you try to flash afterwards? Imho the zips should be fixed now - I didn't encounter a single problem since using them.

i try it with ICS 28E and 28G for my Ghostrider Aroma Rom with new Partition Layout,but when i use ext3 or ext4 i got a Bootloop,i put the stuff in the Updater-Script,all runs with Aroma and lokks fine but when i reboot,i got the Bootloop

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.

Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium

I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.

the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351

Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?

funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2

I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.

Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...

funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2

hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?

funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?

funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended

Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?

funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.

hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!

Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...

omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.

[Q] Minicm7 and a couple of questions

Hi guys I decided to flash a new rom minicm7 and flash its latest kernel naa 13.
A couple of problems:
MY rom is minicm7 with naa latest version 13.
1.when I open the menu to access all my applications the scrolling feels laggy and if I were to scroll in settings file manager or anything else it's smooth any reason why?
2.Secondly which kernel suits you better for this rom (minicm7): Alfs? or NAa?
(I don't want comments like 'see for yourself' this question is based on your OWN invaluable experience)
3. for alfs 8acm7 i'm considering on seeing if it will workout for my device or not (minicm7). Before I do that:
Do I also need to flash chargemon on top of that? and does the flashing of chargemon straight after you flash any version of alfs kernel (except for the ones that already have it attached) apply to any rom regardless as well?
If so which chargemon do I flash? the v2 with the 17k downloads? (sorry im derping out)
4.Do I also need to flash anything else for naa just like how there was an extra file to flash for alfs?
5. I also installed tweaks 3 tweaks such as adre boost, odex, and e15 optimizer. Will these tweaks vanish if I flash a new rom + kernel?
6. Do you keep ANYTHING if you flash a new rom or kernel?
7. Do you lose anything of any sort if you flash a kernel?
8. How do you guys get such high scores in benchmark tests?
I have the same thing as a lot of people do but they seem to get 200 or even 300 higher. Could it because my sd card is filled with anime and music leaving only 5 - 6 gigs / 16gigs ?
I usually went by the rule of flashing 2.1.1.0 and rerooting my device and doing everything again just to stay safe
I don't know if these questions might be derp or not but I don't care please answer by putting a number first I really need answers.
Thank you once again

From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...

Lily48 said:
From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...
Click to expand...
Click to collapse
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?

Ftwisawesome said:
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?
Click to expand...
Click to collapse
You can use the recovery for creating SWAP but with Ext though...
[Ext is another partition for user apps and it's advantage is that you can use the apps on the partition while the sd is mounted on PC]
1. Back up everything on SD because it will be formatted...
2. Enter Recovery -> advanced -> Partition SD Card
3. Choose you Ext size -> Choose 128M Swap size... they said 256M is not recommended...
4. Reboot -> Terminal -> su (if required) -> free -> DONE!
If you want to use Ext, you may install Link2SD -> Choose Ext4 -> Reboot -> Launch Link2SD -> Start linking... DONE!... (Warning: sometimes it breaks app when the annoying error comes (I forgot))... I think you can also use the CyanogenMOD -> Performance -> A2SD (ext) but IDK how to use it...
See also Tips & Tricks To Increase Our Phone's Speed

Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?

Ftwisawesome said:
Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?
Click to expand...
Click to collapse
Swap is already done after partitioning... it's ready after reboot... the terminal is only used to check if it is mounted...
Only the Ext needs setup...
PS: I tried GingerDX and all Dalvik-Cache files went to the Ext without any setup ... Swapper makes mounting SD to PC very SLOW... SWAP Partition doesn't work with MiniCM9 3.0.2 but working on IScreamDX v004...

Ftwisawesome, learn to use the search function, most answers to your questions can be found when you show a little initiative.

My Hero freezes on Cyanogenmod 7.2 Stable- Possible CPU setting issue?

Hey guys,
I've had CM 7.2 Stable for a couple weeks on my phone. It was
working great until a few days ago when I tried to tweak the CPU
settings a little. Right now i'm using
Governor Smartass V2- Min 352 MHz, Max- 691 MHz
What CPU settings are you all using with CM 7.2???
Since I tweaked it from the default cpu settings I've been
experiencing screen freezes. Sometimes the trackball will work
sometimes it won't. It primarly happens when my phone has been
sitting idle for some time. I'll try to get it out of the lock screen
but it won't respond to my touch. I've tried rebooting, battery pull,
I've also tried lowering and raising the min and max settings. It'll
work periodically and then it will just freeze. Funny thing is I
don't know what the "default cpu settings" were set at. I've been
looking around a lot but couldn't find much.
Thanks!

I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2

kjjjjshab said:
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot for the input. I'll try to go back to On Demand. If that doesn't work then maybe I'll just re-flash the ROM.

Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE

laie1472 said:
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
Hi-
I looked at my list of apps to be sure and no extra overclocking app installed. I'm using the default "CyanogenMod Settings" to get to "Performance" and setting the cpu from there. I have not installed any extra lock screen apps or 'lock screen security app' other than what comes preinstalled on CM 7.2. I don't believe I have any app that effects the lock screen. All of the apps I have are fairly simple, mostly developed by google inc. and nothing that tweaks or alters the device (I have Maps, a Speedometer, Navigation.) I try to keep them all closed though with the Task Killer app I downloaded.
I have switched back to OnDemand. So far nothing has changed and it's still stalling up (even though it's only been about an hour.)
Thanks a lot.

Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE

Update
laie1472 said:
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.

That worked for ONE day
brentmxt said:
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
Click to expand...
Click to collapse
So that was short lived. Once I did the Full wipe around noon it worked almost perfectly until for about 12 hours. I think it froze right before I went to bed. I woke up and it was completely frozen at lock screen again. I did another full wipe and reinstalled cm 7.2 and it froze again. So I did a second full wipe and it is now working. I really hope it will accept my nandroid backup if it freezes again because it's A LOT quicker. Than doing a full wipe.
Hope this helps anybody who goes through the same thing.