Originally Posted by jaebond

Has anyone else been getting groups of text messages all at once?

I haven't, I'm getting mine as normal. I'm with PagePlus, though, although they use the Verizon towers since they're owned by the big V. FWIW everyone texts my Google Voice instead of my real cell number, and I send through GV as well.

Does anyone else have a strangely behaving battery with any of these (Test 1, 2 or 3)? I don't know if it was the sheer amount of playing around I was doing especially under Test 1, but my battery life is strange and generally very short. This was including before Test 3 with the .35 kernel, in which the proximity sensor doesn't work.

Like I said, generally, the battery loses charge very fast (as I watch it if I play with it for a couple minutes). Even charging seems a little strange. One moment it's at one percent and then a seeming pretty short time later it's jumped much higher. Most recently this happened at 92% then I saw it at 99% a very short time later, but I'm pretty sure I've seen this behavior partway through the charge cycle, too.

If I have to, I can restore a backup I have of GSB 4.5 and see how it does then. I just hate even temporarily giving up the ultra-stable GPS this ROM seems to have.

FYI I bought this battery last year, and up until several months ago when my girlfriend knocked my phone out of my hand at the grocery store, I alternated between my new and original battery. The new one isn't an OEM, I got it from Batteries Plus I think; it's about the same mAH as the stock one, maybe 50 or 100 higher at the most.

Every once in a blue moon...
HTC phones have a wierd tendancy that over some time, or me not fully charging before flashing a new ROM, their battery stats get mucked up. There are some pretty in depth threads on recalibrating the battery, but I generally have (when this oddity presents itself), just fully charged and either: 1. Drop to a cwm recovery and wiped (battery) stats (I believe in advance submenu) or 2. downloaded Nemas app on the market (which probably does same)...
Don't know if those simple suggestions may help you but worth a try (if you haven't already tried them).
Edit: Flashing new ROM or reflashing same unneccessary (having same actually provides for better baseline comparison of battery life).

Regards,
Rob

Sent from my HTC_A510c using Tapatalk 2

Originally Posted by insink71

Every once in a blue moon...
HTC phones have a wierd tendancy that over some time, or me not fully charging before flashing a new ROM, their battery stats get mucked up. There are some pretty in depth threads on recalibrating the battery, but I generally have (when this oddity presents itself), just fully charged and either: 1. Drop to a cwm recovery and wiped (battery) stats (I believe in advance submenu) or 2. downloaded Nemas app on the market (which probably does same)...
Don't know if those simple suggestions may help you but worth a try (if you haven't already tried them).
Edit: Flashing new ROM or reflashing same unneccessary (having same actually provides for better baseline comparison of battery life).

Regards,
Rob

Sent from my HTC_A510c using Tapatalk 2

Thanks for your input. I did try a simple full charge and then wipe battery stats (I did in Amon RA, but I do use CWM for other things all the time). I forgot one other very good example of what I've experienced, probably the most extreme example. My phone was at 82% when I went to bed, and when I woke up (at the most 10 hours later) it was down to 4%.

I don't do that much on my phone other than practical, everyday things. I never leave 3G Data or WIFI on when I'm not using them. I don't have that many apps installed. Almost all are part of my standard restores via Titanium Backup after any ROM flash, and actually I have no more than half of the normal apps installed than I usually do in the interest of having this Beta ROM run as best as it can. The few apps which are relatively new to me: Dialer2, aCalendar, and Zeam Launcher; I installed instead of Dialer One, Jorte and Go Launcher or Nemus Launcher in the interest of finding replacement apps that take up way less memory and CPU cycles.

I will admit that I am currently using Notification Toggle but I had odd battery behavior when I solely used this ROM's native notification power widgets as well.

I've had the behavior when I haven't used the GPS for days, too.

I've been running without any home screen widgets since Test 3 came out, it seems to help with memory some. I normally have 45-80MB of RAM left.

In the past I had tried various methods of recalibrating the battery (other than the basic that you mentioned) with unknown results. One of another million authorities on the subject of Li-Ion battery life claimed it was bad to both charge it to 100% or let it drain out completely and that it was most efficient/effective to keep a phone battery between 40-80% full whenever possible or practical.

Too bad I don't think there's a way to tell a phone to stop charging when it reaches lower than 100% AFAIK.

NOW, on the other hand. Just now I did several things on my phone, took three screenshots, connected to WIFI, emailed the screenshots to myself, and surprisingly based on past experience, the phone never changed from 75% battery.

I don't really know if anything indicated in the reported battery usage is out of the ordinary. It doesn't appear like it is to me.

For those of you who feel a little.... slow...laggy...or definitely just feeling left in the dust with the co-first release of Android in the US, this will definitely help ICS feel more 'homey' on the Eris. I'm sure plenty of you have heard of V6 SuperCharger, used it, or are using it. Well if you used it on Gingerbread and now are using it on ICS, you know that for it to work properly you have to have a patched services.jar. And if you are on ICS, using it, and didn't know that, then I guarantee you didn't see any results from the V6. I'm not a partner of zeppelinrox or anybody involved with the V6, I just absolutely love its results. When the Eris was my every day device, I didn't really notice the effect, but when I switched to dual-core and started overclocking, I started to notice every bit of lag that did or did not happen. SO when I started compiling a new ROM today I'm working on for the Eris, I decided to boot it up and pull a couple of proprietary files from it, and noticed how horribly laggy it was. So I'm helping everyone out in keeping you from having to go into your phone, pull out the services.jar and have it patched by giving you the download link here, this is the services.jar file Now this should be patched for different ROMs, so if you switch to another ICS ROM, the smart thing to do would be pull its jar file and patch it. But this one is especially for Evervolv. This is isn't the flashable file, so read below for directions on how to correctly implement the patch. On the download page there is the option for a CWM flashable file, but this is just as easy and you don't have to go to recovery to do it.
Download and run V6 SuperCharger (if you don't want to have to reboot twice wait until after you do the next steps)
Mount /system as read/write
copy the patched services.jar file to /system/framework/ (use ADB or a root enabled file manager)
Type the following commands in a terminal/command prompt:
chown 0.0 /system/framework/services.jar
chmod 644 /system/framework/services.jar
Now reboot.

If you start to get laggy after a couple days, run the V6 script again and choose option 18, the System Flush. It really helps.
All credit goes to zepplinrox and OOM Priority Charger. And thanks to the Evervolv team for giving the Eris community an ICS build.

Thanks, lemonoid, I'll try it out sometime.

Originally Posted by lemonoid

For those of you who feel a little.... slow...

I'll double-check later to be sure, but I made a nandroid using CWM before trying to apply any changes to my services.jar. I downloaded both the flashable and the non-flashable versions. I used Root Explorer to copy the file over, replacing the old, but then the stock (this ROM) Terminal Emulator wouldn't work (it does normally), so I then further used Root Explorer to change the owner and permissions I believe correctly, the same as the terminal commands would've done.

I assumed a reboot would be necessary so I did, but it would never stop booting (I don't think it actually bootlooped, but I was busy driving at the time so... ) I left it for probably 10 minutes. So then I tried flashing the zip version, on top of what I already did because I figured it wouldn't make any difference that I wasn't flashing it over my non-customized services.jar since it should replace it either way.

That gave the same result, assuming it had actually done anything at all of course since you indicate that method might not work anyway.

Like I said, I'll double-check these results later, and I'll have a different Terminal Emulator installed so that hopefully I might be able to use it after I copy the services.jar file over. I will also double-check the MD5s., didn't have time to do that last night.

Camera is working under Test 3 with the .35 kernel!!!! The first time I loaded it, I wasn't sure. It was better than before but I didn't succeed in taking a picture. At first I tried the trackball but eventually I tried the screen button above the trackball. I was able to exit the Camera app just fine, though, and didn't have to reboot.

I just loaded it again and just tried the screen button and I was able to take 3-4 pictures reasonably fast and just fine! It might still have been slightly slower than with a non-beta ROM, but definitely useable.

Thanks, MongooseHelix!!!!! I'm assuming it was mainly the kernel that did it?

Edit: I just noticed that you said it doesn't focus, and I checked - you're right. Darn, I thought I saw the app focusing before it took the picture, and I couldn't tell from the thumbnail that it wasn't. Oh well!

I've been patching my services.jar and they have worked just fine. If anyone is interested, here is the one I downloaded:

services.jar

I used adb to switch the permissions. Also, be sure to run supercharger to make sure it worked (if you are "100%" supercharged).

By the way, my trackball occasionally flashes like I am getting a call. Anyone else?

Originally Posted by jaebond

I've been patching my services.jar and they have worked just fine. If anyone is interested, here is the one I downloaded:

services.jar

I used adb to switch the permissions. Also, be sure to run supercharger to make sure it worked (if you are "100%" supercharged).

By the way, my trackball occasionally flashes like I am getting a call. Anyone else?

Hello fellow Columbusian ???

Anyway, the link only takes me to an info page for yourself at OSU's domain. I'd be interested in trying yours, besides testing lemonoid's more thoroughly.

I don't have to have used SuperCharger yet before swapping the services.jar files do I?

My trackball flashes only when I get notifications for text messages or calls. I think emails, too. Do you get yours at other times?