[ROM] ACE ROM v2.0 (No Further EC05 Development)

[anon(214110)]

I saw the updated Genocide. It is backwards EB13 compatible. I'll flash it and report back (but I'll stay away from any overclock/undervolt mods).

 

[GSF1200S]

I saw the updated Genocide. It is backwards EB13 compatible. I'll flash it and report back (but I'll stay away from any overclock/undervolt mods).

I would say the undervolt is 9/10ths the reason to use the new Genocide kernel. Baked Snack kernels are prolly better on battery life without using the undervolt program (Voltage Control). Its pretty easy..

The overclocking is literally install Voltage Control and enable all the way up to 1.4 Ghz..

 

[anon(214110)]

I would say the undervolt is 9/10ths the reason to use the new Genocide kernel. Baked Snack kernels are prolly better on battery life without using the undervolt program (Voltage Control). Its pretty easy..

Thanks for the good insight.

I've installed Genocide, and been through my typical heavy load day. No real issues (fc's, boot problems, etc.), but frankly I'm kinda underwhelmed. Performance/speed is nothing to shout about, and battery life is not noticeably different. As you said, it's probably because I haven't done any uv/oc mods, and thus making a poor use of the essence of the kernal. Since it's a fresh install, I'll try the Voltage Control program and see how low I can take it before it dumps and measure battery performance.

Otherwise I'm gonna flash the Baked Snack 1.2 or 1.26 kernal.

 

[anon(214110)]

Just to report back.

Flashed the updated Genocide kernal with the ACE. Everything was fine. As reported earlier, nothing really synergistic in terms of enhanced performance and battery life was still poor, so I decided to OC to 1.2ghz and UV with voltage control.

Got the UV stable at decent settings (1200ghz-50uv, 1000ghz-75uv, 800ghz-75uv, 600ghz-25uv, 400ghz-75uv, 200ghz-100uv), but battery life was at still poor (losing 10-12% every hour with very moderate to little use). The 1.2ghz OC obviously improved performance but not noticeably (I'm a heavy business apps user, not a gamer). Eliminated the OC (back down to 1.0ghz), but still no improvement with battery life with the UV.

This kinda pissed me off, so I went hunting for what was eating the battery. Used Spare Parts to discover two things with consistently excessive readings under the "Battery History":

1. Gallery app was reporting very high usage of the Sensor function.
2. An unspecified app (simply designated "0") was reporting very high usage of the Network. As I said, I'm a heavy business app user so I have several push email accounts, calendars, and task managers. The "0" app reported quadruple the Network bandwidth as these apps that are typically associated with battery drain. It was almost twice the demand of the whole Android system use of the Network.

RESOLUTION

I eliminated the Gallery app / sensor issue by wiping the caches through CWM, and have not seen it return.

ISSUE

The "0" app issue with excessive demand on the Network remains unresolved. I've searched Android Central, Xda, and other forums. There are a lot of reported cases of finding this same "0" app with excessive Network demand, but no one has come up with an answer for what it is. Nor has anyone been able to conclusively determine that it's a significant battery drain (but given the comparative network use time as reported by Spare Parts, versus all other system functions that regularly access the network (push email and calendar through Outlook, polling RSS feed, polling task manager, etc.), it's hard not to conclude the "0" app is very likely a significant battery drain.

What's known (based on the info I've aggregated) is that the "0" app is related to the root. Here is the info from a mod in the Cynoagen forums:

"In android, all apps have their own UID, (see fix_permissions on the wiki); so when the battery stats sorts the list by app, it's really sorting by UID. UID 0 is root. When you click it, it tries to look up the (shared) UID information for this UID and FCs because there isn't any app associated with the ID."

I can partially verify that this issue seems not to be caused by a 3P app because I've stripped everything out of my system except for essentials. But if its related to the root, what the hell would almost continuously be accessing the Network that's a rooted function/app? Spare Parts shows separate levels of Network usage for typical network related apps like email, calendar, phone, tasks, GPS, etc.

What blows is that when you attempt to get additional info on the "0" app through Spare Parts, you always get an FC. Everyone who has this condition reports this issue (for the reason why, see the quote above).

Thought it might be a function/app controlled by the kernal, so after wiping the caches 3x, flashed the updated Baked Snack 1.28 kernal. Result? The "0" app is still using the Network at the same incredibly high level.

At this point, I'm considering Odin to Eclair and re-root (with new download of root files). If only selective people have this problem, maybe it's a "bad root" and re-rooting would solve it?

If this doesn't work, my only guess is that maybe its related to rooting, because if I understand correctly, after rooting you can no longer update your Firmware, Profile or PRL. Maybe the phone is continuously accessing the Network due to the fact that these attributes are no longer up-to-date? This is probably a total "noob analysis." Whatever ... I'm pissed.

I'm no expert, and have little time or knowledge to investigate much further. But with all the folks reporting this issue across various platforms, phones, carriers, ROMS, kernals, etc. ... it seems perplexing that someone has not found a definitive answer to what the hell the "0" function is, and why it's almost continuously accessing the Network. Or alternatively, that this a non-issue despite all the evidence to the contrary.

 

[anon(214110)]

Way off topic, but related to my last post. If you're looking for info. on what android system apps/process/functions are using your battery as reported by Spare Parts, here is a cross-reference of UID # to android process:

#define AID_ROOT 0 /* traditional unix root user */

#define AID_SYSTEM 1000 /* system server */

#define AID_RADIO 1001 /* telephony subsystem, RIL */
#define AID_BLUETOOTH 1002 /* bluetooth subsystem */
#define AID_GRAPHICS 1003 /* graphics devices */
#define AID_INPUT 1004 /* input devices */
#define AID_AUDIO 1005 /* audio devices */
#define AID_CAMERA 1006 /* camera devices */
#define AID_LOG 1007 /* log devices */
#define AID_COMPASS 1008 /* compass device */
#define AID_MOUNT 1009 /* mountd socket */
#define AID_WIFI 1010 /* wifi subsystem */
#define AID_ADB 1011 /* android debug bridge (adbd) */
#define AID_INSTALL 1012 /* group for installing packages */
#define AID_MEDIA 1013 /* mediaserver process */
#define AID_DHCP 1014 /* dhcp client */
#define AID_SDCARD_RW 1015 /* external storage write access */
#define AID_VPN 1016 /* vpn system */
#define AID_KEYSTORE 1017 /* keystore subsystem */

#define AID_SHELL 2000 /* adb and debug shell user */
#define AID_CACHE 2001 /* cache access */
#define AID_DIAG 2002 /* access to diagnostic resources */

/* The 3000 series are intended for use as supplemental group id's only.
* They indicate special Android capabilities that the kernel is aware of. */
#define AID_NET_BT_ADMIN 3001 /* bluetooth: create any socket */
#define AID_NET_BT 3002 /* bluetooth: create sco, rfcomm or l2cap sockets */
#define AID_INET 3003 /* can create AF_INET and AF_INET6 sockets */
#define AID_NET_RAW 3004 /* can create raw INET sockets */
#define AID_NET_ADMIN 3005 /* can configure interfaces and routing tables. */

#define AID_MISC 9998 /* access to misc storage */
#define AID_NOBODY 9999

#define AID_APP 10000 /* first app user */

 

[GSF1200S]

Thanks jpmorris123; good info to have on hand. While my battery life has been very good, process 0 is listed at the top of my network usage too despite a good bit of browsing on dolphin. Im currently studying for midterms so I cant really look into it, but ill post back here if I find anything out.

I never even noticed it :-[

 

[thebullfrog]

I see 0 on my list, but its networ usage is almost non-existent. Its 1 spot higher than Android System (but just barely), but it's still barely a sliver on the graph, both Opera and Pulse (especially Pulse...ouch) use up many many times the amount of network. I do find it odd that "root" would be usng any network at all, but i would have to uninstall Pulse and stop using the web at all for it to wind up being anything close to a significant drain (comparitively)

 

[svx]

Ok, I am starting to see odd behavior with the GPS. Some apps like GasBuddy are almost 1.5Mi off, Sportstracker by up to .5Mi off. Others are spot on such as Cardio Trainer and Google Maps. I was thinking about flashing he EC05 modem with ACE to see if there were any improvements. Few questions:

*First: what are others seeing? If you upgrade, do you see improved GPS/BT performance, etc?

*Second: Will it wipe my settings? I always CW backup on top of My Backup Pro, but need to know what to expect when I flash it.

*Third: I take it this is an Odin flash? By all accounts it is.

*Lastly: where can I get it? Bonsai used to have it posted, but I no longer see it on their site.

Sorry if repetitive. Thanks in advance.

 

[Paul627g]

Ok, I am starting to see odd behavior with the GPS. Some apps like GasBuddy are almost 1.5Mi off, Sportstracker by up to .5Mi off. Others are spot on such as Cardio Trainer and Google Maps. I was thinking about flashing he EC05 modem with ACE to see if there were any improvements. Few questions:

*First: what are others seeing? If you upgrade, do you see improved GPS/BT performance, etc?

You may or may not see improvement in speed.

*Second: Will it wipe my settings? I always CW backup on top of My Backup Pro, but need to know what to expect when I flash it.

Flashing the modem in Odin will not erase anything. Make a backup just incase..

*Third: I take it this is an Odin flash? By all accounts it is.

See above

*Lastly: where can I get it? Bonsai used to have it posted, but I no longer see it on their site.

Two options...

EB13 Modem (Flash in Odin.. Place in PDA slot, click Auto Reboot and Start)
EB13 updater (Flash in CWM3)

Sorry if repetitive. Thanks in advance.

No problem man...

BTW, no promise but I have been toying with a EC05 update for ACE.. Nothing is concrete yet but I have been playing around.

 

[svx]

BTW, no promise but I have been toying with a EC05 update for ACE.. Nothing is concrete yet but I have been playing around.

W00t! I will keep my fingers crossed. No intention of leaving this ROM anytime soon for sure.


Again, thanks for the hard work and dedication to the community. Definitely appreciated!

 

[Darkshneider]

So... um... since apparently EC05 is the last version we get from Sprint thats Froyo... um... maybe, like... we can get a version of Ace thats based on it .

 

[DaveInFL]

+1

Would love to have an EC05 version of ACE

 

[Darkshneider]

Cmon Paul, waddaya say?

 

[GSF1200S]

Paul627g,

I too would just like to say that IF you decide to cut a new version of ACE, I will be installing it immediately. No matter what ROM I try, it always ends up with at least 1 bug that is really annoying. ACE is not this way. Some new things (camera battery enable at low batt life, etc) have come out that make ACE a little dated, but Im pretty sure I speak for many when I say that ACE would be at least greatly appreciated should you decide to release it..

Flashing Syndicate because Midnight has a supremely annoying MMS bug

 

[Paul627g]

I will see what I can put together over the weekend. I have been playing with something and its relatively along the same as I did with EB13. Remove the bloat, try and incorporate some of the latest bug fixes and throw a small bit of theme on it and leave the rest up to you guys how you want to further customize it. Seeing how a lot today has to do with what kernels you use that will basically control the final product that you put together. After the last few weeks of my own problems with ROMs I have learned the less you play with the with customizing the better off you are. As good as they are today they are also very tempermental.

Give me a few days and I'll see what I can do.

 

[Darkshneider]

Yay! Yesssssssssssssssssssss!!! Thanx.

 

[GSF1200S]

Sounds good

Ill default to your judgement as to what should be included on ACE, but I will say the only reason im not on 1.7 is because of the low battery lock on the camera. Itd be cool if you included that If not im sure I can find a flashable somewhere that will take care of it. I agree about not going too excessive; the only rom ive flashed without issues was ACE 1.7 so you must be onto something. Also, you might consider using an AOSP mms apk instead of the awful MMS client that comes with Froyo (from Samsung). Not a big deal to me- i just use root explorer to put it in /system/app upon flashing a new ROM. I agree with CIQ removal as per the poll- big battery saver.. I dont mean for all of this to sound like Im telling you what to do or that you should heavily tweak the rom; just bringing things up in case it sounds like something you want ACE to have..

I will say that the other roms do a great job of pioneering features that can eventually become stable, but as a daily driver they leave me feeling like my phone isnt going to work when I need it. To give some examples of issues Ive had:

1) Receiving a voicemail would cause the phone to reboot.
2) Wasnt notified of a voice call.
3) Phone wouldnt ring from a voice call (but would show up on screen and all other notifications worked).
4) Text messages wouldnt send about 25% of the time, and upon resending the receiving party would get each message twice.
5) Phone would randomly reboot.
6) Force closing on all keyboard options (had to use hardware keyboard for everything).
7) Camera would force close randomly.

I will flash to ACE as soon as you release I cant wait.

 

[Paul627g]

Sounds good

Ill default to your judgement as to what should be included on ACE, but I will say the only reason im not on 1.7 is because of the low battery lock on the camera. Itd be cool if you included that If not im sure I can find a flashable somewhere that will take care of it. I agree about not going to excessive; the only rom ive flashed without issues was ACE 1.7 so you must be onto something. Also, you might consider using an AOSP mms apk instead of the awful MMS client that comes with Froyo (from Samsung). Not a big deal to me- i just use root explorer to put it in /system/app upon flashing a new ROM.

I will say that the other roms do a great job of pioneering features that can eventually become stable, but as a daily driver they leave me feeling like my phone isnt going to work when I need it. To give some examples of issues Ive had:

1) Receiving a voicemail would cause the phone to reboot.
2) Wasnt notified of a voice call.
3) Phone wouldnt ring from a voice call (but would show up on screen and all other notifications worked).
4) Text messages wouldnt send about 25% of the time, and upon resending the receiving party would get each message twice.
5) Phone would randomly reboot.
6) Force closing on all keyboard options (had to use hardware keyboard for everything).
7) Camera would force close randomly.

I will flash to ACE as soon as you release

Yes alot of what you mentioned is just Froyo in general. Unfortunately unforeseen problems arise and sometimes out of the control of any dev. I can't promise that I can resolve those issues but I feel if I stick with a close to stock build and stay away from a lot of customizing then things should work out. MMS app I'm all ears if you know of something. I personally haven't had any issues with the stock app other than the size limitations of pics but that doesn't really bug me for the limited amount of pics I send via messaging.

By low battery lock are you speaking of the 20% cut off from using the camera/video?

 

[GSF1200S]

Yes alot of what you mentioned is just Froyo in general. Unfortunately unforeseen problems arise and sometimes out of the control of any dev. I can't promise that I can resolve those issues but I feel if I stick with a close to stock build and stay away from a lot of customizing then things should work out. MMS app I'm all ears if you know of something. I personally haven't had any issues with the stock app other than the size limitations of pics but that doesn't really bug me for the limited amount of pics I send via messaging.

By low battery lock are you speaking of the 20% cut off from using the camera/video?

Yes- under 20% it wont allow you to watch videos or use the camera.

Hmm.. let me look around and see if I can find the mms.apk im using from its native place.. Im using the one that came with Baked Snack which looked alot like the Eclair version, and it is infinitely better than stock... Ill upload here if necessary; it was listed on the Baked Snack thread as "Aosp mms." Thats cool on keeping it simple; all the users clamoring for another release pretty much agree with you I was just throwing out ideas just in case one jumped out at you (like the mms). Look forward to the release

 

[Paul627g]

Alright, I will have to look into what needs to be done to fix the 20% cut off but it shouldn't be hard to get resolved. I like that feature myself, although it can get you in trouble if you leave the camera on and throw your phone in your pocket. I did that the other day and in about 10 mins time it drained my battery to zero, had to wait to get home and get it on the charger for a good 15 minutes or so before she would even turn on.. LOL..

I'm also considering doing a dual version release if things work out. No journaling/journaling enabled. Just so you have an option for those who do better with one over the other.