Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Delnar_Ersike

  • Rank

Profile Information

  • Your Current Device(s)
    Acer Liquid A1
  1. I recently flashed this ROM and noticed that its LiquidParts app did not contain SVS (over/undervolt) settings like in the ROMs this one is supposedly based off of; you wrote that you disabled it because "the ROM already comes pre-tweaked with optimal voltages". However, I would still prefer tweaking them myself, especially since every device is different in how much it can handle at certain voltages, and I know for a fact that I'm one of the luckier ones (e.g. it can easily handle 1036MHz on stock voltage). Also, if I were to restore my backup copy of the app from the previous ROM, could I still safely set SVS settings? I know you might be getting a lot of suggestions, but here's one that I'm surprised nobody has mentioned yet: AppWidgetPicker. It's a tiny (about 100kB) app that, when placed in /system/app, makes selecting widgets MUCH more organised. Here's the link to the XDA thread; I've been using it in every ROM I've tried for the past 2 years.
  2. Don't be so dramatic, you didn't "lose him forever"; just check out the thread he recently posted. Keep in mind that the older the Liquid gets, the more people will move on to newer and better devices. Anyway, AFAIK, all code is available via GitHub, so nothing is technically stopping anyone from picking up the project from where thepasto left off and fixing the stuff themselves; if it isn't, you're still probably only need to ask thepasto via email and he'll happily forward everything to you.
  3. Switch to SmartAssV2 governor, it's pretty much what the ondemand governor was intended to be. Also, you could try decreasing the lower clock level to 128 Mhz, since this ROM lets you do that, and don't forget to tinker around with a custom SVS if you're up for it: lowering the voltage on certain frequencies might create instability, but it will also save on power if your phone can take it. Still, you will have the occasional bugged frequency, so the moment you feel your device burning in your pocket, take it out and remove the battery ASAP, let it cool for a while, then put it back it. I've had my phone do this about 7 times in total over the past 2 or so years. and I was using a different ROM each time, though I was always overclocked to 998MHz.
  4. Reinstalled the drivers, didn't work, did it again, didn't work, did it one more time, third time was the charm: ADB is now working. It would be nice to have the ADb notification turned back on, or at least have the option to enable it. I use ADWLauncher mainly because in my experience, it is the launcher that gets killed the least. Ie. when I was using the "non-final" version of CM7, it rarely got killed, but in this ROM, it's getting killed a lot more frequently. I know from experience that my phone can take 1036Mhz at default SVS, and I know it can take 1036Mhz on this ROM as well (I tested it to make sure). However, it can only take 1113Mhz with my custom SVS, so I think the issue is that the ROM sets custom frequencies before setting the custom SVS. Changed maxfreq in cmstat's xml file to circumvent the issue. Ooh, this bug is really getting on my nerves. I pretty much have to pull settings.db, edit it to disable my lockscreen, then push it back whenever I reboot my phone. Not cool at all... PIN works fine if I simply wake my phone from sleep, it's the reboot that kills it.
  5. I generally like this version of CM7.2, but I do have a couple issues: For some reason, ADB just will not work for me. It is enabled in the Settings, but I neither get the notification when I plug the phone in, nor is my phone listed when I run adb devices. I have ADWLauncher, I uninstalled GoLauncher, and I have Lock Home in Memory checked, yet the launcher is still killed plenty of times, even though I am not even close to running out RAM. Rebooting the phone is a giant pain: most of the time, it will freeze at the lockscreen. It usually will not accept the PIN I enter, even though it is the exact same PIN I used to unlock the phone 2 minutes beforehand. Oh, and it will also lock up if I have it plugged in as well. This means that a normal, ~1 minute reboot will turn into a 15 minute ordeal. I am using a custom SVS with overclocked frequencies that are only stable with the voltages of the custom SVS, and I only swapped out libsurfaceflinger.so for LiquidNext's.
  6. This issue is not tied to any ROM. These are the possible culprits that came to mind: Decrease the sensitivity by increasing sensitivity value. Yeah, it sounds weird, but your sensitivity value should be above 20, mine is at 25. Increase the noise value. I keep mine at 50, you should probably keep yours around that value as well. Check your phone's temperature. If your phone gets too hot, you'll get a lot of "ghost" touches. I forgot what the phenomenom was called, but IIRC, once a conductor becomes really hot, charged particles on the conductor will occasionally jump off and onto other, nearby conductors; in turn, your touchscreen will catch these charged particles and register them as touches.
  7. You removed the CM Themes, CM Backgrounds, the Dev Tools app, the Email app, the DSPManager, GoogleTalk, the Spare Parts app, and the TTS options from the ROM; maybe you should make this clear in your ROM patch notes. Also, ADW Launcher Ex is a paid app; you are not allowed to include it into your ROM for free unless you have explicit permission from the app's creator. Yeah, it might be faster, but stay in the legal side of things, will you? It would be a shame to have your ROM removed for being a source of piracy... The ROM itself does seem a little smoother, though I've only had about an hour or so to play with it. I'll check back later
  8. Not to sound egoistical or anything, but... It got buried in the CM9 thread between all the complaints of lagging and freezing, and only now some people think about using it with CM9... :( But, just as before, I'm curious to see the results.
  9. Yes, the reboots are definitely not caused by swap; if anything, they could be caused by a lack of swap usage, as running out of RAM can cause a soft reboot, and not using swap will result in the device running out of RAM very fast. The V6 SuperCharger does change the way Android's autokiller works, which is why I previously asked if anyone tried using it with this ROM on an A1 device.
  10. Has anyone tried using the new, ICS-compatible V6 SuperCharger with this ROM? I am especially curious as to how well it works on A1 devices, but I can't test it myself, seeing as I'm going to need my phone to be stable in the following days (flashed back to CM7.2 for this reason). It's available here: http://forum.xda-developers.com/showthread.php?t=991276
  11. Reset your battery stats (from within recovery) and make sure your CPU governor is set to Smartass or SmartassV2. However, judging by your 15% problem, I think battery stats are the culprit.
  12. Yes, you should most definitely install a Gingerbread ROM if you want a fast and stable ROM. There are many to choose from, but the three most popular are LiquidNext 1.9.2, MIUI, and CM7.2. Of the three, I'd recommend CM7.2, though honestly, I've never tried an MIUI ROM (never liked the feel of MIUI). Follow the advice written in all the other posts (use a lightweight launcher, don't use compcache, set your autokiller values high, etc.), but I do have one thing to add: if you ever play games or use apps that *might* have high RAM requirements (CAD apps, most games released after December 2010, Gameloft games, etc.) or if you want to be on the safe side, always have a 256MB swap partition on your SD card, but set swappiness to a low value (10). This will ensure that swap is rarely used (which is good, since using swap is a lot slower than using RAM) unless it is really needed. Also, don't forget to overclock (and tweak with voltages if you want higher speeds, just don't forget to stress test before you tick "Set on boot") and set your CPU governor to SmartassV2. If you're feeling like experimenting, you can always try the CM9 beta for an ICS ROM. Note however that it requires a LOT of tweaking to be usable on an everyday basis, and even then you will get the occasional random reboot or freeze. It's speed (after tweaking) is debatable: those who say it always runs slower didn't tweak the ROM properly IMO. It'll sometimes be slower, but other times be faster than the previous ROM I used (LiquidNext 1.9.2), and my benchmark runs also agree with me (some will give higher scores, others will give lower scores than the ones I got on LiquidNext). Also, as of now, Beta4 does not play well with the Liquid A1, so stick with Beta3 if you can.
  13. Alright, I think I'm done tinkering with the ROM, here's what I've found (this is all on an A1 with 256MB swap): Besides the default Trebuchet launcher, there are two free launchers with ICS aesthetics on the Play Store: Nova Launcher and Apex Launcher. Of the two, Apex Launcher runs faster IMO and it has a built-in hard-to-kill option as well (it works, too!). I'd recommend immediately downloading Apex Launcher and removing the built-in Trebuchet launcher (via TitaniumBackup) as soon as possible for any A1 user. Forcing GPU rendering does not affect performance in any way, at least according to my tests. The difference in benchmark scores (I used all three SmartBenches and NenaMark1) was minimal at best (<0.1%) and I did not see any difference when running proper apps (both benchmark and perceived performance was unaffected). Chainfire3D's driver causes graphical artifacts and constant hard reboots, DO NOT INSTALL IT! Your device will run noticeably slower for a few minutes after every boot. Be patient, let it "warm up" a bit, and it'll start running smoothly. I really have no explanation for this, other than the system moving a whole lot of stuff over to the swap partition after boot (reading and writing to SD swap is slower than reading and writing to RAM). For some weird reason, AutoKiller settings will occasionally seem to reset after a reboot, but the program will freeze up the device and after another reboot, settings will go back to normal. That being said, AutoKiller settings do make a difference: set them to the Aggressive preset (or high performance gaming, or whatever) and make sure you have all 10 kernel tweaks turned on (that is, if you are using the AutoKiller Memory Optimizer app to set AutoKiller settings). Just remember to make your launcher hard-to-kill. As I suspected from experience with previous ROMs, zRAM (or Compcache) is a bad idea: enabling it creates a significant drop in both benchmark and perceived performance. Though on paper, it should increase your available RAM, this does not translate into better performance in the real world; rather, because your RAM is compressed, any reads or writes to it will take longer. You should only enable zRAM if you don't have a large enough Swap partition and/or you plan on running an app with huge RAM requirements. Even if you do enable it, try to set it to the lowest possible setting: the higher the compression, the bigger the hit on speed. IMO, Best CPU governor is SmartassV2. Lagfree comes close, but SmartassV2 doesn't have a "warm-up time". Only choose Scary if battery life is more important to you than performance (it delivers the same battery life as Conservative, but with a smidgen of better performance). This ROM doesn't like you rebooting it while it's plugged into a PC. Might be a bug or something, but rebooting the device while plugged into a PC frequently caused the device to freeze soon after, while rebooting the device without plugging it in never did such a thing. I could still mess around with Swappiness, but I've gotten tired, so here's what I've found out: setting it to around 50 caused noticeably slower performance, while setting it to around 10 caused certain background apps to die more easily. In the case of a foreground app that uses a lot of RAM, even the hard-to-kill launcher died when Swappiness was set to 10. I recommend people experiment on their own if they want to, but otherwise, set it somewhere between 25 and 35. Remember, too high swappiness causes general slowdown, while too low swappiness causes background apps to be killed faster, as well as increasing the possibility of a foreground app dying or a soft reboot happening. Obvious tweaks I'll only mention without description because people have mentioned these before me: set your SD Readahead to at least 1024 (mine's at 2048), have a Swap partition of 256MB if you're on an A1, set touchscreen sensitivity to 25/50 (sensitivity/noise; this one only increases perceived performance, as it will increase apparent touchscreen responsiveness), enable custom SVS and set the values to the suggested ones (if you know what you're doing, you can mess around with the settings), make sure to set SVS to apply at boot, decrease animation scale in the developer options (will increase animation speed), set your launcher's minimum animation speeds to a setting that seems smooth, but still flashy (perceived performance). In the Performance options, disable Surface Dithering, enable 16bit transparency, check both boxes in Memory management (but leave zRam disabled!), and change your governor and your Maximum CPU frequency based on personal preference/experience (with the suggested custom SVS, the most frequent highest clock speed is, AFAIK, 1113 Mhz, but make sure to test it out before checking the Set at boot option). One more thing: there are certain apps (like DSP Manager or Google Talk) that automatically run services, even if you aren't running the apps themselves. This means that as long as you have the app installed on your device, in most cases, its service will be running in the background along with other services (it's kind of complicated, to the point where even I don't understand it fully). Though in most cases, these barely affect overall performance, certain poorly written apps' services consume a noticeable amount of RAM and/or processing power, thereby slowing down your device simply by being installed. And there is a certain, very poorly coded (IMO) app out there that is also extremely popular, and I know from personal experience that uninstalling it will noticeably speed up your device. Go ahead, uninstall the Facebook app, you'll see what I mean... TL;DR: zRAM sucks, Swappiness between 25 and 35 is good, SmartassV2 is best CPU governor, avoid Chainfire3D, Force GPU Rendering does nothing, Apex Launcher is the best ICS launcher ATM, set the AutoKiller settings to Aggressive, don't reboot with your phone plugged into your PC, let your phone sit idly for a minute after a reboot, and uninstall the Facebook app if you have it. @JustinChasez If you're getting reboots, it's probably due to your Memory settings. Yes, you pretty much need a 256MB Swap if you're running on an A1, but check your Swappiness, your Memory management settings (disable zRAM if you have it enabled!), and your AutoKiller settings (if you have an app to check them; if you don't, I recommend AutoKiller Memory Optimizer). Though I did get some hard reboots when automatically restoring apps via TitaniumBackup Pro, I haven't had any since, and I've been using my device quite a bit.
  14. To all A1 users out there wanting a hard-to-kill launcher, or any user who wants a faster launcher overall, download Apex Launcher: it has a hard-to-kill option that actually works (unlike Nova Launcher) and as an added bonus, it isn't as buggy as the default Trebuchet Launcher. At the moment, I'm still tinkering with certain settings to see how I can squeeze the fastest performance out of this ROM. Though it is usually quite fast, certain apps seem to run slowly, especially after transitioning between apps (must be a Swap thing). Compcache (zRAM) does actually result in an overall slower system, so I disabled it. I'm currently experimenting with Force GPU rendering settings, AutoKiller settings, Swappiness settings, and Chainfire 3D.
  15. Yes, you can create an Ext2 partition on your SD card, but you'll also need a ROM that supports A2SD (apps to SD, not to be confused with Android's built-in move app to SD card function) in order to save space on your internal memory. To get an Ext2 partition, the easiest way is to format your SD card from within your recovery (both CWM and malez give you option of creating an Ext2 partition), but don't forget to backup everything on your SD card first. Next, you'll need to enable A2SD from within Android; the method varies from ROM to ROM, so you'll need to read up on how to do it with your ROM. Once that's done, you can move your /data partition (all user installed apps and all apps' data), your dalvik cache, and/or your /cache partition to the Ext2 partition on your SD card, just make sure your Ext2 partition in big enough (the total size of all internal memory on a Liquid device is about 512MB AFAIK, so set the size of your Ext2 partition accordingly). There are also other methods of freeing up space. For example, you can move certain apps to your SD card using Android's built-in function (though remember, only the apps' resources will be moved, so while a 30MB game might be 1.5MB after moving it to your SD card, a 16MB maps app could be about 5MB, as the code of app needs to stay on the internal memory of the device) or, if you have a ROM that lets you do this or if you use TitaniumBackup, you can move any app (even ones that don't allow it normally) to your SD card this way. You can also try cleaning the caches of your apps: you can do this manually, or download an app (like CacheCleaner NG) that does it all in one go. And then, of course, is the easiest way to free up storage space: delete any unused apps and/or the data of apps that you don't use often and that use a lot of space for data storage (for example, I know the Orbot, the Tor client for Android, uses about 6MB for its data, even though the app itself is around 1MB in size). EDIT: Oh, and if you're really up for it, you can repartition your internal memory, but seeing as you asked about how to create an Ext2 partition on your SD card, I don't recommend you mess around with your internal partition layout.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.