yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] :
Actually, no changes at all. I was hacking around with the camera sources jaybob posted on github but couldn't get it working. Until I tried the obvious. Just download https://github.com/rapmv78/android_hardware_qcom_camerahal.git and put it in your device tree. I then ran "mmm device/htc/hero/libcamera/" and it worked. Too bad that it's got major memory leaks, but it's better than nothing. :)
[Droid Eris Android Development] MongooseHelix:
Hmm, that's odd. The camera.msm7k.so that gets built is using rapmv78's source...wonder what jaybob and I both have done that gives a broken preview. Might be due to the prebuilt libcamera we are using. Guess I'll play around some.
[Droid Eris Android Development] jaebond:
Can't wait!!
[Droid Eris Android Development] MongooseHelix:
Some exciting news, at least to me...

I finally got a .35 kernel build that compiles, boots, and seems to be mostly functioning :D

Some things I know are not working yet:

* proximity sensor

* physical keys - pwr, send, vol up/down (screen buttons work fine - home, menu, back, search)

* bluetooth (at least seeing errors about it though which helps)

* audio jack

* usb mass storage
[Droid Eris Android Development] roirraW "edor" ehT:
Awesome news! It's progress!
[Droid Eris Android Development] roirraW "edor" ehT:
Good news regarding auto-brightness, although I wasn't positive you might've already indicated this, that maybe it only misbehaves once the Notif toolbox starts to get used? I re-flashed Test 2 and am taking the minimalistic approach so far, not installing anything I don't absolutely need. One of my "musts", however, was not having the issue where I have to swipe from the Notif toolbox to my actual notifications, so I'm using Notifications Toggle. I used it to switch my brightness to Auto many reboots ago and it's stuck, so that parts good.

Of course, with that file push, camera preview now works. The camera itself is still slow and I'm not positive if it might eventually hang because I get tired of waiting each time and either pull battery because the phone becomes unresponsive (not just the camera app), or the phone has sometimes crashed and rebooted under some circumstances like this.

Just reporting, I still prefer the GPS being stable to the camera at this time. :)

Thanks for the hard work!
[Droid Eris Android Development] roirraW "edor" ehT:
You got the physical keys to work? GREAT!
[Droid Eris Android Development] 1ceb0x:
guys, down at GSM Hero we have a question. We port your version and it works ok so far, but how can we set the APN for our carrier's internet connection? The internet connection is not locking up although we have gsm signal and the calls are working. any hint/idea?

PM me please! Thank you for the port :)!
[Droid Eris Android Development] roirraW "edor" ehT:
I'll put this in public and I'll PM you in case someone else has the same question.

I don't know 100% if this'll work but it's fixed this for other people who had similar problems sometimes in the past.

1. You'll have to restore/flash a ROM that the internet worked on your phone.

2. Once you did #1 and boot it, go to Google Play (Market) and install "APN Backup & Restore" http://goo.gl/KYN59.

3. Run that app and backup your APN files to your SD card.

4. Flash/restore the port of this ROM that internet wasn't working on.

5. Install APN Backup & Restore on this ROM.

6. Run it and restore the APNs you backed up from your other, working ROM onto your SD card.

7. Keep those APNs around on your SD card for future use should you have the same problem again with this or another ROM.

I don't know if a reboot is necessary. Try it without and with to see.
[Droid Eris Android Development] 1ceb0x:
Thanks man but it was a build.prop thing.

I didn't have the required lines to have "APN" shown in settings.

Now the only thing is when searching for another network I get "Error when searching for another network".
[Droid Eris Android Development] MongooseHelix:
Yeah, the problem only occurs when the brightness widget is chosen to be used in the notification toolbox. Assuming I remember to fix that piece of code, the next build won't have that issue.

This is due to the memory leaking which is even worse when "fixes" for barcode scanning and panorama are included which I believe are built in to the HAL that gives a working preview. I haven't looked into why the HAL getting compiled during the ROM build isn't giving a working preview but once I do, not using those fixes should hopefully cut down on some of the lag/OOM killing/crashes.

Yep yep. Makes it much easier to turn the screen on and off among other things haha.
[Droid Eris Android Development] MongooseHelix:
I can't say that I'm at all familiar with GSM phones or porting a ROM but do you need to replace the /system/etc/apns-conf.xml file to one that has info for your carrier? Also possibly the eri.xml in frameworks-res.apk so the carrier info is displayed correctly on the lockscreen and such.
[Droid Eris Android Development] :
Preview won't work without the panorama fix for some reason. Barcode fix seems to be the biggest memory leak anyways.
[Droid Eris Android Development] MongooseHelix:
Oh ok, thanks for figuring that out. That also clears up why the HAL that gets built with Evervolv doesn't give the preview. I'll add that in to our qcom/camera repo with an ifdef so the other devices we build for won't also need to include it. Thanks again!
[Droid Eris Android Development] superbeak:
So heres my question....is it reasonably fast?
[Droid Eris Android Development] roirraW "edor" ehT:
Whoops, I accidentally "thanked" your post. :) Anyway, no problem, glad you're getting it worked out. Hopefully along with the information MongooseHelix gave you will get it all the way.

No sweat, I know you have bigger fish to fry. :)

LOL!

---------- Post added at 09:39 PM ---------- Previous post was at 09:24 PM ----------

It's not too bad once I switched to Zeam launcher, which is insanely small and fast with reasonable (to me) launcher capabilities. The stock launcher is kinda slow. I resisted switching from stock anything for as long as I could since I wanted to test as much of the stock stuff as possible. I also switched from the stock dialer to Dialer2. I usually use Dialer One, but Dialer2 is much smaller and I'm trying to only go for apps that I can't do without while keeping the memory usage (running and internal storage, but mostly running) as low as possible. I converted Zeam into a system app.

If you try this remember to get SD Booster from the market to increase your SD cache to 2048KB, which will give faster access to apps and anything else that you move to/store on the SD card.

FWIW I also prefer Notification Toggle to the built-in Notif Toolbox so far, but that will probably change in time since if I can get by with something a ROM includes, I prefer to keep things simple. I also converted this to a system app.

I may move the media files from the root/system/media folder to my SD card, to make more room for some of my most important apps.
[Droid Eris Android Development] superbeak:
I'll most likely be trying this tomorrow then. Thanks friend. :cool:
[Droid Eris Android Development] roirraW "edor" ehT:
You're welcome, if you need or want any other advice, just ask.
[Droid Eris Android Development] MongooseHelix:
The plan was to have a new test builds yesterday, one with & one without the alpha .35 kernel but had a bit of an adventure instead :)

https://twitter.com/#!/MongooseHelix/status/197532716114255872

https://twitter.com/#!/MongooseHelix/status/197535825788026880

So I'm going to work on getting that done now to have out tonight.
[Droid Eris Android Development] roirraW "edor" ehT:
LOL! Sorry to hear about your adventure! I'm excited to test the new stuff when you have the time, looking forward to it. Thanks!
[Droid Eris Android Development] MongooseHelix:
New test builds - the kernel is the only difference between these two

ROM (.29 kernel)

Test3-oldKernel

MD5sum: f7b3017b020bc4dcc1a8dc600c07e81d

ROM (.35 kernel)

Test3-alpha35kernel

MD5sum: e87b93ee0eb2759ac643e21ee9d62a9e

This kernel is in alpha so don't be surprised if some things are broken.

Refer to the next post for what I've notices isn't working and what needs tested.

----------------

*Gapps not included! Flash the following zip after flashing the ROM*

04-23_small

MD5sum: 27cfa7dd000555b2a3c751656c3c59c8
[Droid Eris Android Development] MongooseHelix:
.35 Kernel Info
[Droid Eris Android Development] roirraW "edor" ehT:
Woot! I probably won't get a chance to flash the .35 one until tomorrow afternoon. You were working late on this. :)
[Droid Eris Android Development] DowneyJM:
I got the chance now to flash & test so ill post back in a couple hours with word on calls/data/text and hopefully it'll be somethin useful for ya, good work, as always and thanx

p.s. Damn squirrels!! Gimme a follow back....
[Droid Eris Android Development] roirraW "edor" ehT:
Well, so far the Test 3 with .35 kernel seems snappier than before. Haven't gotten further than adding my Google account yet, kinda multi-tasking at the moment.

When I received a text, the trackball light pulsed (as it's been doing on all of these that I've tried so far), so that's good.

Swiping between the regular notifications and the Notif Toolbox seems to be consistent and faster.

Calls working fine so far!

Mute still doesn't work.

I've enabled KSM, don't know how to know if it's working yet.

Is it possible to enable 787 and 806 MHz speeds eventually? The Test 1 and 2 both had them, so the .29-based Test 3 probably still does. My phone handles 806.

I like it so far! Seems to be a general improvement from Test 2, even with the few setbacks.
[Droid Eris Android Development] MongooseHelix:
Glad to hear calls, texts, and notif light all seem to be working and I'll have to look deeper into the mute stuff sometime, not a high priority right now though. KSM probably won't really be noticed whether it's working or not. I'll need to try it out after remembering/looking up where to get the running info. As for the cpu frequencies, it shouldn't be much problem to add them and while I knew they were slightly different, I hadn't realized that the higher ones weren't included.

Some great news for the .35 kernel...the gsm hero .35 kernel guy, riemervdzee, has offered to help out. I need to talk with him some and get my modified source up on github but then it will be very nice to have an experienced kernel dev looking things over.
[Droid Eris Android Development] MongooseHelix:
Might have to be a little more specific like by telling me here or there who you are on the other. I have enough trouble keeping track of myself on all the various sites ;)
[Droid Eris Android Development] roirraW "edor" ehT:
That is great news, cool!
[Droid Eris Android Development] MongooseHelix:
I'll make a separate thread for the .35 kernel at some point but for now, I'll link to my source here for those interested. I got it pushed up to github with proper commits today and it can be found here:

2.6.35 github repo
[Droid Eris Android Development] roirraW "edor" ehT:
I used the SmartAss v2 governor for several days, but I've now switched to OnDemand (and lowered the minimum CPU to 245) under the .35 kernel, and everything is even more responsive than under Test 2 (with the .29 kernel).

I'm still having some trouble using Dropbox on this ROM. It remembers my logon now but when I tried downloading a file I waited at least five minutes and it didn't look like it made any progress at all. I was trying to use the Downloader for Dropbox, too, and it had trouble as well.
[Droid Eris Android Development] whoshotjr2006:
i hope the phrase "imitation is the sincerest form of flattery" rings true for you guys. a massive thanks to all of you guys over here on the eris forums for all you do. this rom is great.

and its starting to look like over at the heroc forums we may have to start riding your coattails with ics, as the eris has way more going on for it than we do. your future work will be much appreciated also
[Droid Eris Android Development] jaebond:
We are very lucky to have Mongoose on our side.
[Droid Eris Android Development] jaebond:
Has anyone else been getting groups of text messages all at once?
[Droid Eris Android Development] roirraW "edor" ehT:
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.
[Droid Eris Android Development] roirraW "edor" ehT:
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.
[Droid Eris Android Development] 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
[Droid Eris Android Development] roirraW "edor" ehT:
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.
[Droid Eris Android Development] lemonoid:
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.
[Droid Eris Android Development] roirraW "edor" ehT:
Thanks, lemonoid, I'll try it out sometime.
[Droid Eris Android Development] roirraW "edor" ehT:
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.
[Droid Eris Android Development] roirraW "edor" ehT:
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!
[Droid Eris Android Development] 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?
[Droid Eris Android Development] roirraW "edor" ehT:
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?
[Droid Eris Android Development] jaebond:
Yep, I am a Columbusian as of last summer. :)

I fixed the link. I forgot to add on the /services.jar at the end. I have never tried using the new services.jar without supercharging first. I guess if the system doesn't know what to do with the changes that get made, it could cause problems.

If you would rather get the services.jar from the source, here is the website they made up that patches it: http://android.mimic.ca

Yeah, I get the trackball flashing other times too. Most recently, right after my phone booted this morning, the trackball was doing the flashing just like when you get a call.