[ROM][2.1] Eclair Strikes Back v2 [2011.06.23]

Search This thread

JiroPrinz8

Senior Member
Apr 20, 2011
1,257
285
Island city of the South
Hah! Finally got enough posts to be able to post here, (a lot of fun in the off topic section.. LOL) Anyway, i'm running Mioze's Eclair Strikes Back and haven't encountered any issues as of yet, Maps is working fine, so is Gmail, will see if it lasts, only on for 3 days and counting.
 

syrenz

Senior Member
Nov 21, 2010
695
56
Haven't had any issues with gmail, haven't really tried maps much though.

I knew you'd never make it a month on one ROM :p. I think my record is like a week maybe a week & a half before I just gotta flash sumfin else.

Hi my name's Chuck & I'm a flash-a-holic. (Currently eye-balling the final MIUI build) :D

lol, I've flashed ROMs about 7 times last week. Haven't flashed anything yet since going to ESB, though I might try the final MIUI once Khal or someone makes something of it.
 

Woody

Retired Admin - Vacationing in Nanda Parbat
Nov 18, 2010
8,842
16,519
Immersed in Dark Matter
So snappiness of app opening is a hot issue here but my question is why IS it snappier on 2.1 than it is on 2.2? What makes it this way and why can't we pull that part out of the 2.1 rom and plug it in the 2.2? Believe me I know it isn't that easy to do, but there are quite a few people in this thread alone that pull and pick apart roms. If that could be fixed, I would love my 2.2 a lot better, but really that is the only thing I would want fixed on 2.2, in addition to the FM radio.
 

Mioze7Ae

Retired Recognized Developer
Dec 27, 2010
2,153
2,053
Queen City of the West
Google Pixel 7
I'm afraid I don't have an answer, but I have suspicions. Our 2.2 ROM is an unholy merge of at least three releases (Motoroi XT720 2.2, Milestone A853 2.2 leak, Milestone XT720 2.1, plus some other files of which Dexter can't remember the origin). I think there are some subtle incompatibilities between the parts that cause the pauses. Running the Motoroi 2.2 has broken sensors and has other issues, but it also seems smooth. If Cincinnati Bell releases a build that was targeted to our phone, we won't have to debug these incompatibilities. If we don't get that, I think we should go back to the Korean ROM and start a fresh port.
 
Last edited:
  • Like
Reactions: syrenz

3rdstring

Senior Member
Dec 19, 2010
2,221
1,082
Cincinnati
So snappiness of app opening is a hot issue here but my question is why IS it snappier on 2.1 than it is on 2.2? What makes it this way and why can't we pull that part out of the 2.1 rom and plug it in the 2.2? Believe me I know it isn't that easy to do, but there are quite a few people in this thread alone that pull and pick apart roms. If that could be fixed, I would love my 2.2 a lot better, but really that is the only thing I would want fixed on 2.2, in addition to the FM radio.

I think memory (RAM) is the major issue. I find that for the best results on the Dexter based ROMs you have to minimize apps that run as a service.
 

Woody

Retired Admin - Vacationing in Nanda Parbat
Nov 18, 2010
8,842
16,519
Immersed in Dark Matter
I think memory (RAM) is the major issue. I find that for the best results on the Dexter based ROMs you have to minimize apps that run as a service.

I agree. I am way more conscious of those now and am now diligently watching the ram and checking for memory hogs. If CBW is making an original build, that would be great and I hope they do, but we can only hope and wait.
 

syrenz

Senior Member
Nov 21, 2010
695
56
Hmm... how come I never realized we had a built in LED notification system... only blinks three times but still nice.
 

syrenz

Senior Member
Nov 21, 2010
695
56
I don't like MIUI either. It's smooth, but ugly.

I saw some vids of the newer 2.3 versions of MIUI. Still IOSy but they've distinguished themselves from it more than in our current build. I wish they'd branch completely away from the IOS stuff though as it's a good ROM... but I guess that is the appeal for some perhaps.
 

Mioze7Ae

Retired Recognized Developer
Dec 27, 2010
2,153
2,053
Queen City of the West
Google Pixel 7
I thought the whole purpose of it was that it was open and customizable. Maybe not...

I've read quite a few comments that MIUI is not only closed, but that they flagrantly violate the GPL by stealing GPL'd components from CyanogenMod. Aside from the fact that I'm fanatical about open-source, I'm not going to run closed-source software developed in China. I don't need the PRC's great firewall state-surveillance apparatus in my pocket. I'll take NSA over PRC. ;)
 
Last edited:

reverendkjr

Senior Member
Nov 7, 2009
891
849
Cincinnati, OH
www.youtube.com
I've read quite a few comments that MIUI is not only closed, but that they flagrantly violate the GPL by stealing GPL'd components from CyanogenMod. Aside from the fact that I'm fanatical about open-source, I'm not going to run closed-source software developed in China. I don't need the PRC's great firewall state-surveillance apparatus in my pocket. I'll take NSA over PRC. ;)

There ya go....

Just another reason to stop playing around with MIUI stuff. We have got to get back to our roots.
 

JiroPrinz8

Senior Member
Apr 20, 2011
1,257
285
Island city of the South
There ya go....

Just another reason to stop playing around with MIUI stuff. We have got to get back to our roots.

Go back to our roots indeed, in this case, the CBW Froyo release, until then, I think I'll check out the final version of khals miui, should be out soon, hey, I mean I could always go back to eclair strikes back (which is awesome btw) if miui doesn't work for me.. :D

Sent from my Milestone XT720 using XDA App
 

gn01222116

Senior Member
Nov 15, 2010
93
10
Just tried eclair strikes back.
it seems to be faster than the original one, and much more convenient than using RSD lite.
Just wondering would it be possible to introduce swap on this rom, may be the best mixture of those roms now lol
Anyway, thanks for your share~!
 

JiroPrinz8

Senior Member
Apr 20, 2011
1,257
285
Island city of the South
Just tried eclair strikes back.
it seems to be faster than the original one, and much more convenient than using RSD lite.
Just wondering would it be possible to introduce swap on this rom, may be the best mixture of those roms now lol
Anyway, thanks for your share~!

It is faster, the only issue I have is that my ext3 partition is useless in this rom.. would love to have that functionality here, games eat up a lot of the internal memory..

Sent from my XT720 Powered by Mioze's ESB
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    Since there's been some interest in comparing the 2.2 ROMs with the 2.1, here are some stock eclair nandroid images based on the Cincinnati Bell 2.1 ROM that can be used in OpenRecovery without flashing SBFs. You can use these to switch between 2.1 and other 2.2 ROMs without bothering with RSD Lite/sbf_flash.

    Of course gallery key, camera and FM radio work well on these. Although, I've been having market problems (paid apps fail to download). Hopefully that will resolve itself if/when market decides to self-update... In the interim, I recommend using something like Titanium Backup to migrate your paid apps.

    Eclair Strikes Back v2 (2011.06.23)
    This is a tweaked version of CBW_eclair_STR_U2_04_1E_1.zip with some tricks we've been using in 2.2 (expanded apns-conf.xml, JIT from FrozenEclair, memhack to move dalvik-cache to /cache, egl.cfg hack to disable software rendering).
    Changes since v1:
    • ext-partition support compatible with the stock221-derived ROMs*
    • Automatic swap support for fjfalcon's fastboot kernel
    • Automatic support for link2sd (either FAT extra partition or stock221's /sd-ext/link2sd method)
    • Additional cpu governors (conservative, interactive)
    • Market upgraded to 2.2.7
    *dalvik-cache on /sd-ext is not supported by default on this ROM.

    Previous release: Eclair Strikes Back v1

    Stock 2.1 (Cincinnati Bell)
    This is a rooted version of Cincinnati Bell's STR_U2_04.1E.1 with OpenRecovery support pre-installed.
    2
    Okay, bug with V2 that I think I've found. Milestone OC is not keeping it's setting and defaults to 550 on boot even though I have it at 1000 with autoload on boot.

    Anyone else having this issue?

    Ah, yes. I was just about to fix this by porting the overclocking script I wrote for stock221, but looking at it, there are some things I want to reconsider first. The 05_overclock on stock221 reads the main sdcard partition, and I want to avoid touching /sdcard. I think the "right" way to fix this is to see if Milestone Overclock can be improved set the clock rate when told to even if it didn't insert the module itself (I think probably what's happening is MO tries to insert the module and does nothing if insmod fails. In this case, insmod fails because the ROM has already loaded it before Milestone Overclock has a chance)

    In the meantime, a work around is to let Milestone Overclock load the overclock module instead of the ROM. To do that, edit /system/etc/init.d/00insmod and delete or comment out this line:
    Code:
    insmod /system/lib/modules/2.6.29-omap1/overclock_milestone_21.ko omap2_clk_init_cpufreq_table_addr=0x$adr
    2
    Beta for next ESB

    Here's a tentative next release of eclair-strikes-back. This adds:
    • Includes updated market
    • Swap support for fjfalcon's fastboot kernel
    • ext-partition support compatible with the stock221-derived ROMs*
    • Automatic support for link2sd (either FAT extra partition or stock221's /sd-ext/link2sd method)
    • Some additional cpu governors (conservative, interactive)
    I've rewritten the ext partition scripts, and I've tested them in simple configurations that I think are common. I *hope* factory reset isn't necessary when coming from the previous eclair-strikes-back, but it is a possibility. Please make nandroid backups of system and data before testing. Better safe than sorry.

    http://www.multiupload.com/Q8B3U8EXWF

    For those interested in details, these now use the ext4.ko to mount the ext partition (but I've only actually tested with ext2 so far). They also use bind mounts now instead of symbolic links.

    *dalvik-cache on /sd-ext is currently disabled while I test the new scripts further. (I haven't fully explored what happens when the sdcard is absent at boot for the /sd-ext/dalvik-cache case--the details get a little hairy once you factor in the default memhack uses /cache/dalvik-cache and the fact that you'd probably only move dalvik-cache to /sd-ext because it's already grown too big for /cache...) I may just decide not to build that support into ESB.
    1
    I've finally successfully downloaded and installed a paid app from the market now on Eclair Strikes Back. Market is still old one though... not sure why it's taking so long to update to new one. When I did a factory reset on stock 2.1 soon after I bought the phone the market updated itself pretty quickly IIRC.

    Still, this feels so smooth and fast....

    EDIT:

    And don't seem to be having downloading issues with any apps, be it paid or free anymore. Maybe you'll have to manually replace the market.apk with the new one though, since I'm not sure it's ever going to self-update.