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

Would you like to see the CIQ Removal in the next release of ACE?


  • Total voters
    0
  • Poll closed .
Im going to flash the twilight kernel tonight for the keyboard improvements, has anyone tried this yet with ace? Anything I should know beforehand?

Worked fine for me when I tried it. The biggest bug is that you cant charge the phone while its turned off as it causes the phone to freeze.

This kind of disappoints me actually- it seems like people are too fast sometimes to own up to there own bugs and instead pass the buck. The Syndicate ROM is exceptional, but the above bug is annoying. To make matters worse, they are saying its CWM 3.0.6, which is simply not true. Running ACE with genocide 0.3a kernel, this bug simply doesnt exist (on CWM 3.0.6), and it does exist on Synicate with Twilight Zone kernel. Why are they saying its a CWM bug if CWM works fine with other ROMs?

Again, im not complaining- Syndicate, like ACE rom, is fantastic in its own way. I certainly cannot complain especially when 2 devs (and more in the case of Syndicate) put forth so much of their own time to give me and others something for free. All im saying is that the path to a bug-free incarnation of any software entity is lighted and created by honesty instead of passing the buck. Am I missing anything?
 
Worked fine for me when I tried it. The biggest bug is that you cant charge the phone while its turned off as it causes the phone to freeze.

This kind of disappoints me actually- it seems like people are too fast sometimes to own up to there own bugs and instead pass the buck. The Syndicate ROM is exceptional, but the above bug is annoying. To make matters worse, they are saying its CWM 3.0.6, which is simply not true. Running ACE with genocide 0.3a kernel, this bug simply doesnt exist (on CWM 3.0.6), and it does exist on Synicate with Twilight Zone kernel. Why are they saying its a CWM bug if CWM works fine with other ROMs?

Again, im not complaining- Syndicate, like ACE rom, is fantastic in its own way. I certainly cannot complain especially when 2 devs (and more in the case of Syndicate) put forth so much of their own time to give me and others something for free. All im saying is that the path to a bug-free incarnation of any software entity is lighted and created by honesty instead of passing the buck. Am I missing anything?
Meh, minor annoying bugs come with the modding territory. I'm sure that this will be fixed in a couple of weeks
 
I did a quick search but didn't see anything, so if this is somewhere else in the thread I apologize. I'm running the delivered email program through an exchange activesync and anytime I try and do an attachment the email program force closes. I click on attachment, then click file and boom, force close. Anyone else seen this, I've reapplied this rom a couple of times to try and fix it (with the usual multiple wipes). I've even odin'd back to eclair then rooted, etc back to ACE and boom, happened again.

Have to say, other than that I love this ROM, great battery life. With TER on 28 I'd maybe get till 5 PM with 5% battery, now I'm at 6PM with about 45%.
 
I did a quick search but didn't see anything, so if this is somewhere else in the thread I apologize. I'm running the delivered email program through an exchange activesync and anytime I try and do an attachment the email program force closes. I click on attachment, then click file and boom, force close. Anyone else seen this, I've reapplied this rom a couple of times to try and fix it (with the usual multiple wipes). I've even odin'd back to eclair then rooted, etc back to ACE and boom, happened again.

Have to say, other than that I love this ROM, great battery life. With TER on 28 I'd maybe get till 5 PM with 5% battery, now I'm at 6PM with about 45%.

This must be something that is a product of the email client or the exchange activesync your using, I have not changed any of the applications that shipped with Froyo EB13 they are all stock.
 
Worked fine for me when I tried it. The biggest bug is that you cant charge the phone while its turned off as it causes the phone to freeze.

This kind of disappoints me actually- it seems like people are too fast sometimes to own up to there own bugs and instead pass the buck. The Syndicate ROM is exceptional, but the above bug is annoying. To make matters worse, they are saying its CWM 3.0.6, which is simply not true. Running ACE with genocide 0.3a kernel, this bug simply doesnt exist (on CWM 3.0.6), and it does exist on Synicate with Twilight Zone kernel. Why are they saying its a CWM bug if CWM works fine with other ROMs?

Again, im not complaining- Syndicate, like ACE rom, is fantastic in its own way. I certainly cannot complain especially when 2 devs (and more in the case of Syndicate) put forth so much of their own time to give me and others something for free. All im saying is that the path to a bug-free incarnation of any software entity is lighted and created by honesty instead of passing the buck. Am I missing anything?

Me personally I'm awaiting the next release of the Genocide kernel which should have the keyboard lag fix in it and everything else up to date. Don't take me the wrong way, I like the work ACS has done with Syndicate and the CIQ removal but this CIQ removal has been the cause of many of these problems to creep up. I tried adding the CIQ removal to ACE and was meet with FC's and problems so I removed it. I was going to release v1.7 with it implemented but after having the FC problems I decided against it. Plus on top of that they have something going where only ACS supported themes seem to work with the ICQ removal, so there must be something in their permissions/file signature that stops any non-ACS supported theme from working and that is not something I choose to have in my ROM. I want to provide freedom to my users to flash and customize things as they choose and not have to conform to specially made themes/add ons.

I support the work they are doing at ACS, they are talented developers and I believe once the bugs are worked out the CIQ removal should be a good thing but right now it seems to be problematic and not something I want to deal with at this time.
 
Just as an update, Flashing the twilight kernel ontop of ACE 1.7 gave me zero issues and brought a fully functioning keyboard!!!! Why samsung wasn't able to do this originally is beyond me. The keyboard fix has seriously given my phone a second life.
 
Just as an update, Flashing the twilight kernel ontop of ACE 1.7 gave me zero issues and brought a fully functioning keyboard!!!! Why samsung wasn't able to do this originally is beyond me. The keyboard fix has seriously given my phone a second life.
Agreed! The keyboard fix made me enjoy my Epic a lot more. Let Sprint bring their Nexus S, devs will just port the OS because its the only thing that will be different from our phones.
 
This must be something that is a product of the email client or the exchange activesync your using, I have not changed any of the applications that shipped with Froyo EB13 they are all stock.

That's what I was afraid you were going to say. I am going to go to stock EB13 to give it a shot later tonight. Hopefully that will work. Good time to do this anyways as I screwed up all my contacts and whatnot so I'm going to erase those and start over with those too.
 
Holey Hell think if you had some kind of virus that called on this IQ data and transmit your data I know most of us will never have to deal with this but still its possible ya know this kind of crap really pisses me off... Do all android phones have this or just Sprint android phones?


Thanks Royce

Taken directly from the ACS Syndicate thread:

What Is Carrier IQ? Why Should We Care?

Put simply - and bluntly - Carrier IQ is a software package buried deep within Android by Samsung at the behest of Sprint. It has been in active use since the time of the Moment, if not before. The company that develops it, also known as Carrier IQ, bills it as "Mobile Service Intelligence". In their own words,

[T]he combination of the MSIP and IQ Insight lets you move seamlessly from broad trend data across many users, through comparative groups down to diagnostic data from individual devices. Now, not only can you identify trends, you have the power to drill down to specific instances, giving you the insight your specialists need to make a difference.

On its own, that description can vary from harmless, to worrying, depending on how you look at it. It's not until one drills deep down into the system and ferrets out every piece of the software that one truly knows what it contains. As some of you might remember, ACS took the first steps toward disabling the Carrier IQ software with the release of SyndicateROM and Xtreme Kernel 1.0. That, however, didn't even scratch the surface.

Carrier IQ's native libraries are plainly visible - libiq_client.so and libiq_service.so in /system/lib. During every boot, this service is launched - you can see it in Settings > Applications > Running Services as "IQAgent Service". These native libraries are called by non-native (Android application) libraries located in ext.jar (the client) and framework.jar (the service). Removal of these (rather obviously-named) libraries alone, be it the .so files or the libraries in framework or ext, will, obviously, break boot. So I - k0nane - had to dig deeper. To make a long story short, reference to the IQ Service and IQ Client were littered across the deepest portions of the framework, and some of the most basic functions of the Android system as we know it.

Carrier IQ as a platform is designed to collect "metrics" at any scale. What I found it to hook into is far beyond the scope of anything a carrier needs - or should want - to be collecting. Carrier IQ sits in the middle of, and "checks" the data of, SMS and MMS messages. It listens for and receives every battery change notifications. It hooks into every web page you view, and every XML file your device reads. It receives every press of the touch screen. It 'sees' what you type on the physical keyboard. It reads every number you press in the dialer. It can track which applications you use, what 'type' they are, how often, and for how long. It hooks into data sent and received.

I, and the rest of ACS, ask Samsung and Sprint - why do you want this information? Why do you need it? Why is the capability in place?

The only saving grace - if there is one - to this nasty, ten-legged mutant spider is that its logs are off by default. During the investigation process, I was able to enter its UI. Below are two screenshots of it.


That being said, the question still must be asked - why is the service even running? Why does Sprint and Samsung feel the need to leave a dormant monster in every one of its most loyal customers' phones?

Here's the most important part (tl;dr): the Carrier IQ service is a drain on battery life and performance. ACS noticed a significant rise in Smartbench scores and overall system 'snappiness' after Carrier IQ's removal. In addition, with it removed, ACS team lead rjmjr69 saw 30 hours of battery life, with heavy use, on the stock battery.

Thanks for the long read!
 
I agree with you 100% on this issue It would be nice to be with out CIQ but i can wait for it to be stable :) Also being able to flash what ever theme you want is nice as well...

Keep up the good work...


Me personally I'm awaiting the next release of the Genocide kernel which should have the keyboard lag fix in it and everything else up to date. Don't take me the wrong way, I like the work ACS has done with Syndicate and the CIQ removal but this CIQ removal has been the cause of many of these problems to creep up. I tried adding the CIQ removal to ACE and was meet with FC's and problems so I removed it. I was going to release v1.7 with it implemented but after having the FC problems I decided against it. Plus on top of that they have something going where only ACS supported themes seem to work with the ICQ removal, so there must be something in their permissions/file signature that stops any non-ACS supported theme from working and that is not something I choose to have in my ROM. I want to provide freedom to my users to flash and customize things as they choose and not have to conform to specially made themes/add ons.

I support the work they are doing at ACS, they are talented developers and I believe once the bugs are worked out the CIQ removal should be a good thing but right now it seems to be problematic and not something I want to deal with at this time.
 
Just as an update, Flashing the twilight kernel ontop of ACE 1.7 gave me zero issues and brought a fully functioning keyboard!!!! Why samsung wasn't able to do this originally is beyond me. The keyboard fix has seriously given my phone a second life.

Can you tell me if blue tooth voice dial works with that Kernel?
 
Last edited:
Sorry for blolwing up your thred but just wanted to be sure on something befor I try some changes when you do a clockwork mod backup it backs up everything? Kernal rom and all?



Thanks Royce..
 
Sorry for blolwing up your thred but just wanted to be sure on something befor I try some changes when you do a clockwork mod backup it backs up everything? Kernal rom and all?



Thanks Royce..
It's cool, I actually don't use bluetooth so I can't comment on that, and yes, a clockwork backup should back up everything, kernel and all. Don't wipe before you flash twilight, just flash from zip on top of your current rom.
 
Ok thanks for the info I tried the kernel and my bluetooth voice dial still does not work I have no idea what's causing it or how to fix it lol but my keyboard is uber now...


It's cool, I actually don't use bluetooth so I can't comment on that, and yes, a clockwork backup should back up everything, kernel and all. Don't wipe before you flash twilight, just flash from zip on top of your current rom.
 
Last edited:
Thanks for all your help and advice I tried the kernel you aid to and its a no go still does not work what it does exactly is when i pres the voice dial button on my blue tooth it says speak now followed by a beep and then on the screen of the phone it says an error accord and it stops the voice dial but if i use it on the phone it works just fine so not sure what that cause is...


Royce


I would say its probably kernel related. Kernels are the key to everything, so it would be worth a shot to flash the Twilight Zone kernel while running ACE and see what effects that has.

The link to the Twilight Zone kernel will be in this section.
[Index] Froyo EB13 ROM's, Kernels, Themes, & Other Mods [Updated 3/4]
 
Thanks for all your help and advice I tried the kernel you aid to and its a no go still does not work what it does exactly is when i pres the voice dial button on my blue tooth it says speak now followed by a beep and then on the screen of the phone it says an error accord and it stops the voice dial but if i use it on the phone it works just fine so not sure what that cause is...


Royce

I have tried this on ACE with the Twilight kernel and it works fine. It works fine on the syndicate ROM too.. Hmmmm.. Perhaps an Odin back to rooted/deodexed/ext4 and reflash will help? Thats so weird..
 
Ya I may need to try that i have it all backed up maybe just a simple re flash of the rom would do? try it see if that works if not i could oden back to stock and start over from scratch lol although in the thread here it did say it would break blue tooth... So i knew it would but i thought once i flashed a new rom that would no longer be a prob i guess it something to do with the EXT4? as stated I saw a link to a file called blue tooth fix some place over on XDA but there search is broken as of now so cant find it lol

http://forum.androidcentral.com/epi...al-froyo-eb13-w-optional-ext4.html#post634062



I have tried this on ACE with the Twilight kernel and it works fine. It works fine on the syndicate ROM too.. Hmmmm.. Perhaps an Odin back to rooted/deodexed/ext4 and reflash will help? Thats so weird..
 
Ya I may need to try that i have it all backed up maybe just a simple re flash of the rom would do? try it see if that works if not i could oden back to stock and start over from scratch lol although in the thread here it did say it would break blue tooth... So i knew it would but i thought once i flashed a new rom that would no longer be a prob i guess it something to do with the EXT4? as stated I saw a link to a file called blue tooth fix some place over on XDA but there search is broken as of now so cant find it lol

http://forum.androidcentral.com/epi...al-froyo-eb13-w-optional-ext4.html#post634062

It SHOULD work with the Twilight kernel- I dont think it has anything to do with ACE, but more with genocide0.3a kernel. It is listed on the XDA page for the Twilight Zone kernel as well as on the Syndicate ROM page that bluetooth dialing has been fixed. I would Odin to Stock EB13/rooted/deodexed +EXT4 + CWM 3.0.0.6 and flash Syndicate ROM (make sure to grab the updated 1.0.1 kernel of Twilight Zone), then try it. THEN, download ACE and flash it. Try it. If it doesnt work, flash back in the Twilight Zone kernel and see if that works.

I mean, youve already done most of this, but its not working so hopefully a reflash will help.. I can confirm it works with my motorola stereo bluetooth headphones (have built-in mic) on Syndicate and ACE with the Twilight kernel, as I have tried both literally an hour ago due to reflashing myself (Syndicate bug took out my FS- highly recommend ACE at least until Syndicate updates).

**EDIT** By working I mean: my phone is connected to my headphones and in my pocket. I press the call button on my headphones and I here a prompt to say who I want to call. I say "home" and shortly my home phone starts ringing. Just trying to be clear with everything so were on the same page :)
 
Thanks for the info i had worked on this quite a bit tonight and i have flashed the bonsai rom just for testing and blue tooth voice dial worked like a charm then i flashed genocide kernel and it still worked just as it should i then re flashed ace with genocide and went back to not working also flashed twilight kernel again so at this point i am thinking its something with ace or my hardware? not sure what else i should try at this point lol...

What do you guys think? Oden back to stock and it worked but as soon as i went back to ext4 and ace same thing...

Edit: I am thinking in this thread here http://forum.androidcentral.com/epi...al-froyo-eb13-w-optional-ext4.html#post634062 it says that ext4 kernel breaks some of the blue tooth so i am thinking is there another way to root and go over to EXT4? maybe the set up used in this thread causes this to happen ( not pointing fingers haha i am just simply trying to solve a problem) Maybe there is another method to getting over to EXT4 that will not cause this to happen...


It SHOULD work with the Twilight kernel- I dont think it has anything to do with ACE, but more with genocide0.3a kernel. It is listed on the XDA page for the Twilight Zone kernel as well as on the Syndicate ROM page that bluetooth dialing has been fixed. I would Odin to Stock EB13/rooted/deodexed +EXT4 + CWM 3.0.0.6 and flash Syndicate ROM (make sure to grab the updated 1.0.1 kernel of Twilight Zone), then try it. THEN, download ACE and flash it. Try it. If it doesnt work, flash back in the Twilight Zone kernel and see if that works.

I mean, youve already done most of this, but its not working so hopefully a reflash will help.. I can confirm it works with my motorola stereo bluetooth headphones (have built-in mic) on Syndicate and ACE with the Twilight kernel, as I have tried both literally an hour ago due to reflashing myself (Syndicate bug took out my FS- highly recommend ACE at least until Syndicate updates).

**EDIT** By working I mean: my phone is connected to my headphones and in my pocket. I press the call button on my headphones and I here a prompt to say who I want to call. I say "home" and shortly my home phone starts ringing. Just trying to be clear with everything so were on the same page :)
 
Last edited: