[ROM] [DEV] [ICS 4.0.4] *7/1* Evervolv's Aosp TexasIce Cream Sandwich

Search This thread

pigous

Member
Nov 26, 2007
47
2
reboot factory reset

Hi,

I had twice that the phone rebooted and every installed apps disappeared, the lock screen missed, and the home button didn't work. Anyone can let me know why this is happened?
Thanks
 

orgler

Senior Member
Oct 2, 2007
249
62
Were you overclocknig. its been pointed out to me that oc produces reproducible lockups with the new kernel.

even without oc i had 2 lockups within 15min of each other, no idea what happened. im still experimenting with kernel changes, but like i said before its almost impossible for me to debug this. and since these lockups only seem to happen to me once ever 2 weeks at the most its super slow.

Me too suffered from the "sleep to death" last night. I'm on dk_zero_cools rom for my desire but using your kernel cayniarb-stock-ics 8x50 (2.6.38.8).


I'm not overclocking in any way, using the ondemand-governor with 245mhz to 998mhz (everything default).


Regards,
Johannes
 
  • Like
Reactions: texasice
D

dolphin77

Guest
RE: Google Chrome finaly usable

The red rectangle while starting Google Chrome beta is gone with the latest update from Yesterday. Looks it was a bug in the program and is not related to HWA by texasice.

Another issue - it was quite laggy for me, so had to revert to stock browser which looked flying compared to Chrome. And looks like most issues are fixed now, so Google Chrome is working very fast for me on this ROM.

PS all the bugs were within the Chrome.

EDIT: Saw red rectangle once again. But speed is OK.
 
Last edited:

oligambit

Senior Member
Dec 21, 2010
95
9
Chartres
My market (on the nexus) is unable to locate chrome beta, even in my apps!! I tried several other location with market enabler without succes. I would be nice if someone could post the new chrome apk on the forum? Thanks
 

Xialis

Senior Member
Mar 28, 2010
96
25
39
Me too suffered from the "sleep to death" last night. I'm on dk_zero_cools rom for my desire but using your kernel cayniarb-stock-ics 8x50 (2.6.38.8).


I'm not overclocking in any way, using the ondemand-governor with 245mhz to 998mhz (everything default).


Regards,
Johannes

I set "Minimum CPU Frequency" to 384. No SoD since this change...
 
  • Like
Reactions: onerider

andynx1

Senior Member
Sep 1, 2010
476
149
Carlisle
Redmi Note 10 Pro
Help!!!

Hi all,

Following the instructions...

Installed blackrose, then the texasice custom blackrose.

In the booloader, it says blackrose and texasice. And the new partition scheme is displayed, so far so good.

Boot into recovery (4ext) and get a message that 'system' is not available. Message suggests formatting 'system' from within 4ext, which I try and do...

But, 4ext hangs whilst trying to format system! I can pull the battery and start again, but I can't format the system partition, and I can't proceed until then!

er... help!!!

Ta!

Andy
 

altruistic666

Senior Member
Jan 18, 2011
356
81
Brussels
Hi all,

Following the instructions...

Installed blackrose, then the texasice custom blackrose.

In the booloader, it says blackrose and texasice. And the new partition scheme is displayed, so far so good.

Boot into recovery (4ext) and get a message that 'system' is not available. Message suggests formatting 'system' from within 4ext, which I try and do...

But, 4ext hangs whilst trying to format system! I can pull the battery and start again, but I can't format the system partition, and I can't proceed until then!

er... help!!!

Ta!

Andy
Try re-partitioning your sd card and then a clean install.. There is absolutely no problem with the rom, it runs well. And maybe flash the script for partitioning internal memory from BR again..
 
G

GuestX0019

Guest
@Andy

Not sure where you are at now and if this will help, but you can erase your system thru fastboot
 

texasice

Retired Recognized Developer
Oct 27, 2009
603
3,434
Austin
The red rectangle while starting Google Chrome beta is gone with the latest update from Yesterday. Looks it was a bug in the program and is not related to HWA by texasice.
Another issue - it was quite laggy for me, so had to revert to stock browser which looked flying compared to Chrome. And looks like most issues are fixed now, so Google Chrome is working very fast for me on this ROM.
PS all the bugs wre within the Chrome.
EDIT: try it out here: ftp://vt.dyndns-at-home.com/share/com.android.chrome-1.apk
Saw red rectangle once again. But speed is OK.
the rectangle is a strict mode debug thing that when an app takes to long to respond or complete a task it flashes a visual warning or the developer. im assuming chrome uses its own internal strict mode type thing to do this since its still beta, this will likely go away when its stable.
@Andy
Not sure where you are at now and if this will help, but you can erase your system thru fastboot
format system: fastboot erase system
you might also need to reflash recovery
Me too suffered from the "sleep to death" last night. I'm on dk_zero_cools rom for my desire but using your kernel cayniarb-stock-ics 8x50 (2.6.38.8).
I'm not overclocking in any way, using the ondemand-governor with 245mhz to 998mhz (everything default).
Regards,
Johannes
good tip. i am almost positive the sods are related to the ondemand gov (tiamat uses smartassv2) ive been experimenting with interactive but it seems to cause excessive battery drain.
@texasice
you mentionned in first post "working google backup/restore (RMerlin)", what does it cover exactly? Is it that the adb "backup"command described in
http://xdaforums.com/showthread.php?t=1420351 will now work?
i dont know i never tried that. basically working backup means your previously installed apps will show up under my apps in teh market.
 
Last edited:

Reaper82

Member
Jun 12, 2011
49
10
glad you got it

surprised 4ext didn't work though--very popular

4ext sometimes has a bug where it can't format system after a hboot change. I've experienced it myself but fastboot
erase system
works in that case. The dev is aware and looking into a fix but 4ext is still my favourite recovery manager.

a2 is running quite well can't find any real faults with it except the button lights are staying on sometimes when the screen is off. It used to happen on a1 but it seems to be more frequent. Still it's stable enough to keep using every day.
 

e.coli

Member
Jan 24, 2012
47
14
Calgary
  • Like
Reactions: oligambit
G

GuestX0019

Guest
4ext sometimes has a bug where it can't format system after a hboot change. I've experienced it myself but fastboot
erase system
works in that case. The dev is aware and looking into a fix but 4ext is still my favourite recovery manager.

a2 is running quite well can't find any real faults with it except the button lights are staying on sometimes when the screen is off. It used to happen on a1 but it seems to be more frequent. Still it's stable enough to keep using every day.

maybe that is why he recommends wiping system before flashing an hboot

but +1, I really like after 2 years of amonra which is great also
 

klaydze

Senior Member
Feb 5, 2010
254
21
Manila
a2 is running quite well can't find any real faults with it except the button lights are staying on sometimes when the screen is off. It used to happen on a1 but it seems to be more frequent. Still it's stable enough to keep using every day.


+1 on this too.

I thought upgrading from a1 to a2 will fixed the problem but still, softkeys are stay awake even my screen is off.
 

RMerlin

Senior Member
Jan 26, 2011
187
63
Montreal
asuswrt.lostrealm.ca
@texasice
you mentionned in first post "working google backup/restore (RMerlin)", what does it cover exactly? Is it that the adb "backup"command described in
http://xdaforums.com/showthread.php?t=1420351 will now work?

It means if you enable the option to backup your data, then stuff such as Wifi passwords, installed apps, and settings from applications that specifically support it will be backed up to Google's server. When you do a Factory reset, once you reconfigure your Gmail account, you can restore all this stuff automatically. This is the way it was working in Gingerbread, however AOSP ICS doesn't support it by default.

I can't confirm if the changes I provided will be enough to make it work on the Nexus One however. It did on the Motorola Xoom, however there were a few caveeats, such as some Gapps version didn't properly support it, or having to use adb to manually set the correct backup transport on devices that had already been configured pre-fix. I'm not running this ROM, so I can't test it myself, sorry.
 
  • Like
Reactions: oligambit

Top Liked Posts

  • There are no posts matching your filters.
  • 284
    Evervolv is maintained by MongooseHelix, Preludedrew, and myself. Our goal is to bring ice cream sandwich to unsupported devices guided by the aosp philosophy, everything we do is opensource and transparent to the public. Visit our Gerrit or Github.
    We have a few customizations such as:
    • Androidian Theme
    • Battery percent
    • QwikWidgets
    • Six bar signal strength
    • Standalone power widgets
    • Tri State lockscreen with customizable actions
    • Trackball / Volume wake
    • Volume button music controls
    All of these can be turned off or set back to aosp apperance via our EVToolbox for those that wish to have a pure google look.

    I originally started porting ICS to my beloved nexus one the very same day google released the source back in November. I had very little knowledge and no experience porting android. It took 2 days to sort countless build errors and get it booting, only a few days later i was able to release my first alpha (where absolutely nothing worked) It has come a long way since then, with hundreds of hours invested on my part and undying support from this wonderful commutity, I am pleased to announce: as of 2.1.0p11 this rom is /almost/ stable. However it will remain in alpha/beta (whatever you want to call it) a while longer, but the majority of people will find this usable as a daily driver.

    For those of you not following this thread. You may not know my nexus died. As in the NAND finally gave out ((bootloader) rbchk: Total 1191 bad blocks!!). And I was able to get a replacement on ebay for $142.50 USD. Paid for entirely with your donations! Thank you to everyone who donated (i can't appreciate it enough). I look forward to bringing you the latest and greatest Ice Cream Sandwich to your n1's.

    I have spent many hours and sleepless nights on this. So if you like it please feel free to hit that donate button above that picture of me.
    Working: [person who helped fix it]
    • 3g (Radio: i use 5.08.00.04 - 5.12 reported working just as well)
    • Accelerometer/Compass [me][chrs2021]
    • Apps2sd [me]
    • Bluetooth [me]
    • Calling
    • Camera [rampv78] Preview [kushdeck] Video [mongoosehelix/me]
    • Fm (reported working with third party apps from market)
    • Gps
    • Hardware Acceleration [me] (p8 and up)
    • Headphone jack [zivan56]
    • Home button [MongooseHelix]
    • Init.d [MongooseHelix]
    • Led (TrackBall) Notifications
    • MMS
    • Network Stats and Quota [me]
    • Opengl support [me]
    • Screenshots
    • Sound [sean neeley][me]
    • Signal Strength [cm][me]
    • TouchScreen [dr1337] Multitouch (2 finger) [theomy]
    • Trackball (navigation) [me] (clicking) [jaybob413]
    • Trackball Wake [me]
    • USB Mass Storage (native now working)
    • Usb Tether (dk-zero-cool)
    • Wifi [cm]
    • Wifi Signal Strengh Icon in Status Bar. [preludedrew]
    • Wifi Tethering
    Not Working:
    • Gapps might not work properly (search the thread for fixes before posting issues)
    • wifi ad-hoc/p2p
    • Builtin alarm clock app doesn't work 100% of the time.
    TODO list
    • Fix omx video
    Short FAQ
    • Q:Screen wont come back on, the buttons light up but i have no screen?!
      A: Try taking out your sdcard. If it works you need to reformat your sdcard and whatever you do dont use clockworkmod!
    • Q: Im getting lockups and have to pull the battery to restart?
      A: Easiest way that seems to do the trick: Goto: Evervolv Toolbox -> Performance -> Processor -> change Min Freq to 384Mhz
      A: Or: change the governor from ondemand to smartassv2

    [STOP]
    You must install blackrose hboot before flashing ICS. Instructions.

    BlackRose
    You must increase the size of the system partiton to fit ICS to at least 210MB
    *4/14* I had previously recommended 210 system but am now changing that back to 220. The size of ICS and mainly Gapps is growing and with 210 system on the a2 release, after gapps there is only 6mb free space. That doesnt give me very much room to grow on and can cause problems with people who have bad blocks on the system partiton.

    RECOMMENDED: System 220MB Cache 10MB Data 206MB Download

    System 210 Cache 8 Userdata 218 Download
    (or make your own with the Blackrose installer).
    All past builds will work just fine on either layout 210 and 220
    Future builds might not fit on 210 as of a2 it is pushing it.
    If you are installing for the first time choose the 220mb system.

    Flash:
    Code:
    fastboot flash hboot hboot_brcrust_220-10-206-ICS.nb0
    fastboot reboot-bootloader
    fastboot -w
    If it flashed correctly: after the 'reboot-bootloader' command you will see TexasICS on the second line (under blackrose)

    Keep up with latest developments

    To build Evervolv
    Code:
    repo init -u git://github.com/Evervolv/android.git -b ics
    . build/envsetup.sh
    breakfast passion
    mka

    To flash the img files.
    Code:
    tar xjf <release name>.tar.bz2
    adb reboot bootloader
    fastboot -w
    fastboot flash system system.img
    fastboot flash boot boot.img
    fastboot reboot
    IRC
    Join us in #evervolv on freenode http://www.evervolv.com/chat
    My nick is drewis.

    Enjoy your TexasIce Cream Sandwich!!

    Screens from p9. (left lockscreen, middle notification toolbox, right phone info)
    More screens (from my g+) https://plus.google.com/photos/102710594547223731659/albums/5724901287546593969
    101
    CHANGELOG / Downloads

    CHANGELOG / Downloads

    ATTN: ALL BUILDS HOSTED ON GOO.IM WERE LOST.
    Here is the final version: http://ev-dl1.deuweri.com/Perdo/Evervolv-Perdo-2.2.0-Final-passion.zip

    GAPPS:
    • (latest are posted to mongoosehelix twitter page) or dl here 5-20-release (thanks TuSKan for the mirror)
    • Gapps are NOT included in the rom. Reasons for this is 1) smaller upload for me 2) Gapps seem to be the source of most peoples problems. This way you can flash whatever version or package you want/works best (or even make your own custom gapps package)
    A2SD
    • About the included apps2sd see: ->here<-
    STOCK KERNELS: (no need to flash, provided if you try another kernel and want to switch back)

    Evervolv-Perdo-2.2.0a6 (7/20)
    Unofficial build from lacus88: http://xdaforums.com/showpost.php?p=29127460&postcount=4273
    Includes the last few commits we submitted to ics before jellybean came out. that didnt make it into the last build.

    Evervolv-Perdo-2.2.0a6 (7/1) (final)
    • Request fill week:
      • Notification toolbox now QwikWidgets with easier widget reordering
      • Long press back to kill apps
      • Trackball Alert Patch to custom colors using lilhermits app
    • Toolbox and Themes removed from app drawer: now access through settings
    • Androidian theme is now mostly complete and usable.
    • Revert some linaro patches to try and fix some weirdness
    Rebuild (7/2)
    • Fix bootanimation
    • Cleanup to honeycomb lockscreen
    • finishing touches to androidian theme
    ZIP:http://goo.im/devs/evervolv/20120702/Evervolv-Perdo-2.2.0a6-passion.zip
    TARBALL:http://goo.im/devs/evervolv/20120702/Evervolv-Perdo-2.2.0a6-passion.tar.bz2
    AROMA INSTALLER:http://xdaforums.com/showpost.php?p=28230809&postcount=4174

    2 builds are available this time only difference is the toolchain
    MORE STABLE: STOCK GOOGLE TOOLCHAIN
    ZIP:http://goo.im/devs/evervolv/20120701/Evervolv-Perdo-2.2.0a6-passion.zip
    TARBALL:http://goo.im/devs/evervolv/20120701/Evervolv-Perdo-2.2.0a6-passion.tar.bz2
    EXPERIMENTAL: LINARO TOOLCHAIN (bluetooth is broke)
    ZIP:http://goo.im/devs/evervolv/cron/20120701-gcc-4.7/Evervolv-Perdo-2.2.0a6-passion.zip
    TARBALL:http://goo.im/devs/evervolv/cron/20120701-gcc-4.7/Evervolv-Perdo-2.2.0a6-passion.tar.bz2
    I put the wrong boot animation in a6.
    Here's the correct one : http://d-h.st/Heh
    Or the old one if you dont like it: http://d-h.st/nCg
    THESE ARE NOT FLASHABLE: push or copy to /system/media/bootanimation.zip with adb or root explorer.


    Evervolv-Perdo-2.2.0a5-passion (6/23)
    • main thing here is camcorder, native omx encoding is working but decoding is still broke so you can record videos but cant play them back. Issues: video is capped at 15fps so it is a little choppy, recorded video is rotated 90 degrees
    • usb tether support: not native, using the motorola usb app not included (push to /system/app then the toggle in settings will work) i'll probably never include this app in the build since it runs as a service and that bothers me
    • be sure to check out new options in the evtoolbox (lockscreen and interface) and the new evtips widget
    • and get the new gapps installer from bexton
    ZIP: http://goo.im/devs/evervolv/20120623/Evervolv-Perdo-2.2.0a5-passion.zip
    TARBALL: http://goo.im/devs/evervolv/20120623/Evervolv-Perdo-2.2.0a5-passion.tar.bz2
    AROMA ZIP INSTALLER repacked by bexton: http://xdaforums.com/showpost.php?p=27815448&postcount=4051

    Evervolv-Perdo-2.2.0a4-passion (6/8)
    • Forgot to bump the version so its still a4
    • probably 200+ new commits here. Vast majority do not concern n1. but thought it was worth mentioning
    • bump IMM76L
    • surfaceflinger hacks: make ui smoother (error in makefile prevented them from being turned on before)
    ZIP: http://goo.im/devs/evervolv/20120608/Evervolv-Perdo-2.2.0a4-passion.zip
    TARBALL: http://goo.im/devs/evervolv/20120608/Evervolv-Perdo-2.2.0a4-passion.tar.bz2

    Evervolv-Perdo-2.2.0a4-passion (5/28)
    • lockscreen 'wave' animations will follow the unlock around (not just go right)
    • 180 degree (upsidedown) rotation support
    • kernel updated: kgslv3.8, tiny rcu optimizations, autogroup, bfqv3r2, smartassv2, armv7 changes from caf
    • newer adreno libs: in combination with kernel updates should make ui noticeably smoother (note: not backward compatible with any pre a4 kernels including tiamat)
    • updated cli tools: htop v.9, busybox updated 1.20.1, a2sd cleanup: checkext should work better

    ZIP: Evervolv-Perdo-2.2.0a4-passion.zip
    TARBALL: Evervolv-Perdo-2.2.0a4-passion.tar.bz2

    Evervolv-Perdo-2.2.0a3 (5/7)



    Evervolv-Perdo-2.2.0a2 (4/13)
    • Bulgarian keylayout, Dutch dictionary added
    • working google backup/restore (RMerlin)
    • Volwake/music controls can now be used concurrenly
    • battery percent icon by default
    • lockscreen sound toggle icon now updates properly
    • bluetooth tethering (untested)
    • attempt to resolve auto button backlights being too bright in low light
    • audio files have been restructured. you might have to reset your ringtone / notification settings (not needed if you wipe)
    • kernel update sha/memcpy optimizations one ondemand gov update (per my wip19 branch)(been using for a week with no issues)

    ZIP: http://goo.im/devs/evervolv/20120413/Evervolv-Perdo-2.2.0a2-passion.zip
    TARBALL: http://goo.im/devs/evervolv/20120413/Evervolv-Perdo-2.2.0a2-passion.tar.bz2

    Evervolv-Perdo-2.2.0a1 (4/2)
    • merge android 4.0.4
    • finish merge for omx in framework (still not working, falls back to sw)
    • removed barcode patch from camera (more stable pictures)(so no panorama,video or barcode now)
    ZIP: http://goo.im/devs/evervolv/20120402/Evervolv-Perdo-2.2.0a1-passion.zip
    TARBALL: http://goo.im/devs/evervolv/20120402/Evervolv-Perdo-2.2.0a1-passion.tar.bz2


    For older builds look at Post#3.
    68
    About apps2sd:
    • rewrote for more awesomeness
    • more interactive, asking yes/no questions
    • no more symlinks! we are bind mounting everything now
    Notes:
    • Wont work with a2sdgui
    • a2sd install only needs to be run once. it will continue to work even after full wipes (as long as you dont format /sd-ext)

    This is the build in help menu:
    Code:
    Available commands are:
    install   : sets a2sd flag
    remove    : clears a2sd/dc2sd flags
    align     : runs zipalign on all apks
    fixapk    : runs fix_permissions on all apks
    partlist  : shows if ext[3/4] is supported
    diskspace : shows disk usage on /sd-ext
    cachesd   : sets dc2sd flag
    cleancache: clears dalvik-cache
    nocachesd : cleancache and clears dc2sd flag
    xdata     : bind mount /data to /sd-ext/xdata
    noxdata   : clears xdata flag
    formatext : format /sd-ext to ext4
    checkext  : checks /sd-ext for errors
    • most of the heavy lifting is done in the 10apps2sd init.d script a2sd mostly sets flags for 10apps2sd to pickup and respond appropriately
    • everything 10apps2sd does is logged to logcat (At the very beginning under the evervolv banner)
    • in some cases a2sd will ask if you would like to reboot now. This is just to give you time to read the output of the command you typed. you should always respond 'y' to this question.
    A few notes:
    • install: moves apps on internal /data/app to /sd-ext/app then removes them from /data/app to free up space and changes the mount point to /sd-ext/app. NOTE: even though the mount point is changed the /data size reported by android will not change. That is just how it is. If you want to see how much space you have type 'df' into terminal emulator and look for the entry /data/app. It will be identical to /sd-ext. (i.e)
      Code:
      Filesystem                Size      Used Available Use% Mounted on
      ...
      /dev/block/mmcblk0p2      1.4G    123.1M      1.2G   9% /sd-ext
      /dev/block/mmcblk0p2      1.4G    123.1M      1.2G   9% /data/app
      /dev/block/mmcblk0p2      1.4G    123.1M      1.2G   9% /data/app-private
      ...
      EDIT: moving AppData is now supported just choose y when asked.
    • remove: does not remove the apps on the /sd-ext partion nor does it move them back to /data it simply removes the a2sd/dc2sd flags so new apps are placed in /data/app instead of /sd-ext/app and the dalvik cache is placed in /data/dalvik-cache instead of /sd-ext/dalvik-cache. Why don't we move the apps back to internal storage? well if you are using a2sd in the first place it is because you had too many apps for interal storage so your /sd-ext/app directory is likely much too large to fit on /data. You will just have to restore the apps you want to use or reinstall them.
    • cachesd: mounts data/dalvik-cache to /sd-ext/dalvik-cache. most people will experince problems with this (i.e. no mic, random reboots). this is not a2sd's fault. dalvik-cache is used very often and doesn't like the lag of being on the sdcard. NOTE: all dalvik-cache commands (cachesd, cleancache, nocachesd) nuke the dalvik-cache and rebuild on reboot making the reboot take longer than usual (just the once after you run the command)
    • xdata: still highly experimental but basically mounts the entire /data partiton on /sd-ext giving you the entire size of your /sd-ext partition available to data. In this case android will detect the new size of the /data partition and report it correctly. NOTE: doing this will not result in any data loss the /data partition. it is simply cloned into /sd-ext/xdata (as well as any apps in /sd-ext/app) and then xdata is mounted ontop of /data (which just covers it up, preserving the contents). So there isn't too much risk in trying it. but i do warn significant performance loss will be noticed on ...well any sdcard. But high quality class6 or class10 won't be as nocitable.
    • noxdata: this will revert your phone the the way it was before you ran xdata. so any changes made to the phone while using xdata will be lost.
    • formatext: formats your /sd-ext partiton to ext4. this will erase everything on it!
    41
    I might have a preview available with full hwa by this weekend. I've got it partially working but also have a job now so have spent considerably less time working on android. the kernel is booting (at least) and i have a display. still some issues with gralloc to sort... plus power management for the gpu might be broke but im not sure about that yet.

    My goal is to have a 100% functional/full featured ics build for the nexus one by the end of the month.
    32
    pre-pre-alpha-8
    Massive update to kernel. Now built with proper ics opengl support
    Only for serious testers! Requirements. Adb installed and functional. You need to be able to read logcat and (at least attempt to) narrow down what is causing your problem.
    If you get a lockup or unexplained reboot please (turn phone back on) and do 'adb shell cat /proc/last_kmsg' then pastbin that to me. (It should have the kernel panic reason at the very end)
    Notably broke:
    auto rotation: sometimes phone locksup and requires a battery pull. so lets disable auto rotate. evtoolbox> statusbar> notiftoolbox> add widget> autorotate then use the notification toolbox to disable it (icon is broke so when you press it nothing happens but it is disabled) and when it works the screen is offcenter so statusbar is covered
    camera: preview is black but still takes pictures
    general: sometimes on transitions there is a weird screen 'stutter', somelive wallpapers stutter when scrolling screens, display off animation its enabled and everything but still not working for some reason. (EDIT: ok so i enabled the fade effect not the old tv style screen off animation)
    Notably working:
    wallpapers are centered and scroll, gallery seems to work better

    gapps not included (dl the latest from mongoosehelix twitter page)(http://goo.gl/fXET8)
    no flashable zips...fastboot images only
    dev-host removed their remote url upload feature (i've already complianed about it)
    so this is hosted on my google storage account
    http://commondatastorage.googleapis.com/evervolv/Evervolv-Perdo-2.1.0pre-p8-passion.tar.bz2

    im not updating the op with this since its for testing only

    please use the bugtracker and report issues. dont forget the logcat and dmesg!