yashsingh1/xdaforums huggingface dataset:
[Droid Eris General] Lemcott:
average folks working for free in their spare time are going to take a lot longer then a group of 20 or so software developers at htc being paid full time. so... really chill out, the devs are doing the best they can.

it still is good news though, once it's released i dont think the devs will have any problem at all porting it over.

EDIT: okay, i might've jumped to the wrong conclusion after re-reading your post. I'm just so used to so much bad mouthing and drama that I guess I got carried away.

Anyway, Verizon is really slow at sending out updates. they constantly check and recheck and tell the companies to change so many things that it's really complicated to get them out as quick as t-mobile does. if HTC is making one for the MT3G (hero), there is absolutely no doubt in my mind that they're working on one for the eris as well, they probably just havent announced it because they are waiting for verizon to greenlight it.
[Droid Eris General] Vonrottes:
I think Verizon will roll out the 2.2 by the end of Q3 seeing as the just popped the official 2.1 out(which from what i have seen is very buggy)

Even if they dont, when the official Froyo for 1.2/Fender is OTA'd the Eris port will fallow VERY shortly(since the 1.2 is basically and Eris in a Magic case)

BTW Hero CDMA=Sprints version of the Magic

Hero GSM= is Tmobile UK "G2"

Just sayin'
[Droid Eris General] Sheen160:
Yeah I wasn't badmouthing. I hate all the drama in these forums lately. :rolleyes: I know the devs are working on a 2.2 port, but I was just stating that if the MT3G can get it what's stopping us from getting it? I'm hoping Verizon will greenlight it if they are working on a 2.2 update. And if they aren't we'll always have a dev who will make a rom for us. ;)
[Droid Eris General] Marisa:
2.2 will probably be available for rooted Eris within hours of source being posted, though I do hope Verizon doesn't drag their feet for the sake of those unwilling or unable to root.
[Droid Eris General] Sheen160:
Agreed. Plus I would think it'd be better to have the 2.2 that was made for the eris to make the rom, rather than just porting it so everything will work. Although it may be just as easy for some people.
[Droid Eris General] DS36:
I smell version 5 version 6 leaks coming soon from peoplethat work for htc

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

Sent via the XDA Tapatalk App
[Droid Eris General] fox_dye:
From some articles I have read I'm pretty sure we will get an official 2.2 update. It was stated that the jit that is used in 2.2 will actually help to speed up older devices such as ours. So I'm going to keep my fingers crossed and if not then I hope that we get root for leak.
[Droid Eris General] crax0r:
Will it be able to root from 2.1? Maybe get the leaked users out of the gutter?
[Droid Eris General] Lemcott:
it's a real good chance that the hboot for a 2.2 rom will be a higher number, so IF verizon/htc go forward with a 2.2 update for the eris, and we can get it rooted? leakers might be able to root.
[Droid Eris General] orkillakilla:
Lets hope so. I would so love to root my phone. No more jumping the gun for me. I'll be waiting for an official ota or root. No more leaks for me.

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

Sent from my HTC Droid Eris using Swype. Gone Google!
[Droid Eris General] refthemc:
HTC Sense is stopping it. Number one reason why I cried when I found out the Nexus one wasnt coming to Big Red
[Droid Eris General] pkopalek:
Incredible users will get 2.2 soon enough, just like HTC EVO users.

SenseUI will be just fine with 2.2. Will JITs be modified or adapted for it?

Time will tell.

JIT's are exactly what make it so fast
[myTouch 3G Slide General] sh!mon:
Why on my G1 could I select to only see those Google contact who are in "My Contacts" but on the MTS I can only select all of my Google contacts which is like over 900 people.

I only have my Google contacts selected. I have no other contacts checked. I tried the whole facebook thing, but it was just too much with the contacts!

I think the whole linking thing is ridiculous. Just give me my Goolge My Contacts and we can call it good!

Anyone know how to deal with this or if this feature will be added back in the update?
[myTouch 3G Slide General] turboyo:
hit menu in the contacts app, view, put it to show only contacts with numbers
[myTouch 3G Slide General] sh!mon:
it's not the same as being able to use My Contacts because that way you get phone contacts and email contacts, but I can live with it cuz the MTS is so much better than the G1
[myTouch 3G Slide General] burch:
We're running into the same problem here. My wife just got the Slide yesterday, and I put her contacts from her old Blackberry into a Contact Group on her Gmail account. In the standard Contacts app, you can choose which Google contacts groups to display...hopefully can figure out something similar here.
[myTouch 3G Slide General] goodjob:
Google didn't automatically sync when I first started my phone. I had to log into gmail first from the phone. once i did that, then google contacts were there but they still didn't show. Like turboyo said, just go into contacts and hit menu. It will show a bunch of different options on which contacts to display such as phone, sim, google, facebook, and tmobile. For me, I only have it set to display google and facebook contacts.
[myTouch 3G Slide General] burch:
goodjob - yep, see that too. I'm looking for the ability to select individual Google contact groups to display (like on the G1 and N1, for example).
[myTouch 3G Slide General] fermunky:
Does anyone else's Contacts icon keep changing? When I first got the phone, it was Contacts. Then sometime earlier in the week, it was People at one point. Now it says Contacts again...
[myTouch 3G Slide General] sh!mon:
For people who keep saying to just select Google in the contacts section... this is not what this post is about. On my G1, I could go into Google contacts and select specific contact groups such as My Contacts so it didn't show ALL of my Google contacts. I don't want to just select people who have phone numbers because I email a lot on my phone and it's nice to have the contacts I want to see!

Anyway... I can live with it, but I think it's a step backward in terms of the contacts interface.
[myTouch 3G Slide General] fermunky:
We do understand that. And I guess to answer your question, it isn't an option anymore. However, this just seems to be because of the Sense UI having a different contacts interface. Hopefully either 2.2 changes that, or rooting will give us this option back because I also liked selecting the groups.
[G1 General] robuser007:
There are multiple SPL's: deathspl, dangerspl, hardspl, Engineering SPL,and others? Does any summery exsist that shows them all?

I can only use one of those at the same time ? (when flashing deathspl after dangerspl it erases dangerspl, right?)

Which one should I take ?

Is Amon Ra Recovery really needed? Can it influence spl,rom,etc when using (the wrong one)?
[G1 General] mejorguille:
You can probably get a better description with a quick search but i' do my best to sum it up:

-stock spl: comes with the phone

-engineering spl: from adp1/ion; allows use of fastboot

-hard spl: engineering spl with ability to flash foreign nbh files

-death/danger/haykuro(all the same thing)- from a magic. has more space on system and data and less space on cache. allows you to flash larger roms

You can only have 1 spl at a time. i personally use danger spl but I don't recomend you use it unless you know what you are doing. As the name implies, there are risks to using it. Amonra is not *needed* but it is the most common and is trusted to work.
[G1 General] robuser007:
Can I flash all those spl's without problems when switching spl's ( except the stock spl which needs root to flash another one)?

Radio: 2.22.23.02 is the most recent radio I guess?

Recovery: Amon_RA's 1.7.0.1: I'll better install engineering spl to install Amon_RA's (i've red that this is the most safe way) and then flash another one, like dangerspl (for CM 5.0.8test3)?

I think I first flash the enigneeringSPL for amon_RA's,then the radio (needs recovery) and then the SPL I Need for the rom (danger for CM).

Do I need a particural version of an (not stock) SPL for flashing the radio?

(some links for myself;)

http://xdaforums.com/showthread.php?t=566669

http://wiki.cyanogenmod.com/index.php/DangerSPL

*2.22.23.02 seems to get more bars for T-Mobile US customers, though non-US users might have better luck with 2.22.19.26i.

=> I'll think I use 2.22.19.26i as I live in Europe.

After flashing Dangerspl I cannot flash any older radio on the G1?

Are there roms that can't handle Dangerspl?

How can I see what's already installed and which version (like spl, recovery?)

What's the does Danger Spl & gapps-ds-ERE36B-signed.zip do?

A lot of questions I know.
[G1 General] lbcoder:
Those are the same thing... 1.33.2005 is the actual identificiation, and it is a FULL ENGINEERING SPL. Compatible with 2.x and 3.x radios.

What is typically called "engineering SPL" for DREAM is actually 0.95.3000. It is not a full engineering SPL, but does offer FASTBOOT.

This is a HACKED version of 0.95.3000, which identifies itself as 10.95.3000. The difference has something to do with flashing NBH files, which is actually something that once you have a [partial]engineering SPL installed, you NEVER WANT TO DO!!!

STOCK SPL 0.95.0000 -- this is an UNDESIRABLE SPL. There's NO FASTBOOT mode.

1.33.2003 is a nice one... it is a full engineering SPL and is compatible with 1.x and 2.x radios and has the same partition layout as the 0.95.x000 SPLs. There is no brick risk when going from a 0.95.x000 SPL --> 1.33.2003, and you benefit from having a FULL engineering SPL.

HACKED 1.33.2003 is an interesting one... it has the partition layout of 1.33.2005, but is compatible with 1.x and 2.x radios.

Note about radio compatibility:

0.95.x000 SPLs are compatible with 1.x and 2.x radios.

1.33.x003 SPLs are compatible with 1.x and 2.x radios.

1.33.xxxx SPLs, with the exception of 1.33.x003 are compatible with 2.x and 3.x radios.

See above.

Note about BRICKS:

The most common brick is the radio/SPL mismatch brick.

There are NO SPLs compatible with ALL radios.

2.x radios are compatible with ALL SPLs.

When you have a mismatched RADIO and SPL, and have the misc partition set to boot-recovery, you will have a brick on your hands. This often happens when using RECOVERY to install a new RADIO or SPL.

With the TRUE ENGINEERING SPLs, you can flash radio or SPL using FASTBOOT. Flashing with FASTBOOT is BRICK-PROOF.

You CANNOT fastboot a radio or SPL from a 0.95.3000 SPL.

You CAN safely flash 1.33.2003 via RECOVERY ***FROM*** 0.95.x000.

Then you can FASTBOOT the 1.33.2005 SPL safely.

If fastboot-ing in a radio or SPL results in a mismatched radio and SPL, ***FASTBOOT CONTINUES TO WORK*** -- assuming that you havent done something really stupid, like fastbooting in a NON-FULL-ENGINEERING SPL.

In general, the safe way to change radio or SPL on the device is to go from 0.95.x000 --> 1.33.2003, and then ONLY use FASTBOOT for switching SPLs or RADIOs in the future, and ONLY switch between 1.33.2003 and 1.33.2005.

Unless you have a wormhole intersecting your phone, this should be the case.

A part or full engineering SPL.

If you already have any such SPL, no need to change.

If you want to install a large system image, look up FIRERAT's nonedanger procedure.

The kernel must match the radio in order to boot. Beyond that, the choice of what recovery image you prefer is your own business.
[G1 General] robuser007:
Thanks for the detailed answers, I think it should work without a problem (just thinking of which radio I should use).
[G1 General] robuser007:
I have spl 10.95.3000. (radio 2.22.19.26I) on the phone when it arrived.Any suggestions which spl I should flash next? (I'll use FR CM5.08test4).

DREA110 PVT 32B
[G1 General] robuser007:
CAN I safely flash 1.33.2003 (the old hardspl) via RECOVERY ***FROM*** 10.95.3000 too? (already on phone)

I'm a little bit uncertain, but I guess it should work.

Please confirm.
[G1 General] robuser007:
Found it finally.
[G1 General] ezterry:
Re: spl questions: solved

Just a small footnote: the hacked version of of 1.33.2003 in question identifies its self as '1.33.2003AF' on the spl screen. (The non hacked one is just '1.33.2003')
[G1 General] lbcoder:
Please unedit your first post. Howtos are not required and not applicable to this thread.
[Droid Eris Android Development] lostbytes:
Well here we go, this will revert your bootscreen to the Stock Verizon Android Bootscreen with Sound.

(Verizon animation then waving droids, followed by the HTC animation)

!!!! THIS IS FOR ROOT USERS ONLY !!!!

This has not been tested with any Non-Root ROM!

This HOW-TO was put together on a Windows Machine, Please adjust your syntax if you are using linux.

This has been tested on the Plain Jane ROM (Thanks Jcase!!) And confirmed working on Ivan's ROM (Thanks pkopalek)

EDIT [6/9/10 @ 3:39pm EST]: THIS WORKS ON Eris-based ROMs ONLY at this time. I will be experimenting with other ROM's and will post my findings.

This Bootscreen was pulled from the Downgrade.zip included in this post:

Android Fourms

Please give credit where credit is due. All i did was get all together and write this HOW-TO.

1. Download this zip ... bootscreen_Stock_Sound

And Extract to any location on you computer. You should have a folder named bootscreen with some xml,mp3,and gif files.

2. if you have pushed a bootscreen to /data/local, delete it.

adb remount
adb shell rm /data/local/bootanimation.zip

3 Enter the adb shell and cd to /system/media and list contents.

adb remount
adb shell
cd /system/media
ls

Back up the bootanimation.zip located here.

cp bootanimation.zip bootanimation.bak

or delete it.

rm bootanimation.zip

Exit shell

exit

4. Now to push the animation to /system/media

<your-save-path-here> is where you extracted the RAR. When extracted you will have folder named bootscreen_Stock_Sound with a nested folder named bootscreen.

I downloaded the rar to the desktop on Win 7 so my path would be:

C:\Users\Lostbytes\Desktop\bootscreen_Stock_Sound\bootscreen

NOT: C:\Users\Lostbytes\Desktop\bootscreen_Stock_Sound\bootscreen\

as this will nest the folders.

adb push <your-save-path-here>\bootscreen /system/media/bootscreen

Wait for it to finish.

EDIT:For those having problems with a black boot screen, please enter the following to set the permissions on the bootscreen folder.

adb remount
adb shell chmod 775 /system/media/bootscreen

5. To Test.

adb remount
adb shell
bootanimation

PRESS Ctrl-C to return to the shell.

Now a creative person with the inclination, should be able to modify the contents of the bootscreen xml file to use custom sounds and animations. Have Fun All

TO THE DEVS:

Thank you for all your hard work day in and day out. Without people like you, this scene would not exist.
[Droid Eris Android Development] lostbytes:
Have Fun

Have Fun Everyone!!!!!!
[Droid Eris Android Development] pkopalek:
I've been thinking about this bootscreen for a long time.

Thank you for this.
[Droid Eris Android Development] pkopalek:
And for what it's worth, with all the files in place,

my Evil Eris boot animation is just a blank, black screen.

Hmm..... I'm missing something.
[Droid Eris Android Development] bukada:
I thought this had to be in a ZIP format... :confused:

After downloading ..it is a RAR file...
[Droid Eris Android Development] lostbytes:
This is not the common Bootanimation.zip!!!

Please read the directions, this is the old Style bootanimation format. (using a XML instruction sheet, NOT the desc.txt file w/ png in zip format) This allows much more control. You mush first back up or remove any and all Bootanimations on your phone.
[Droid Eris Android Development] lostbytes:
Did you back up or remove the bootanimation in

/data/local

/system/media

also if /system/media already has a bootscreen folder delete it and replace it with the one from the RAR.

Bootanimation formats as far as i know are:

/data/local/bootanimation.zip

/system/media/booanimation.zip

/system/media/bootscreen/<XML,Gif,MP3 files>/

This bootscreen is the last format. It works on a ERIS running Plain Jane, Will post vid soon.
[Droid Eris Android Development] orcsbane13:
Same here. Followed the instrucations and only have a blank screen now during boot up. Is a step missing?
[Droid Eris Android Development] pkopalek:
All checkpoints check.

This is also pretty standard for all of Android, so I am baffled as to why we're getting black bootscreens!
[Droid Eris Android Development] lostbytes:
I will recreate the procedure from the beginning . All i did was pull the original boot screen from Android 1.5 and push to my phone, Maybe i missed documenting something.....But it is a simple operation. Will post again soon.
[Droid Eris Android Development] pkopalek:
Yeah, I see.

I even pulled apart downgrade.zip (which I have on my computer) and looked at it myself, just in case a file got corrupted or something.

I can't figure it out!

Maybe this needs to be turned into a bootanimation.zip for some ROMs?
[Droid Eris Android Development] lostbytes:
Its possible, I will look into it some more, What baffles me is that works for me!!! It may be ROM dependent but i am just recreating the file structure with no modifications from the original. So, in theory the ROM should not matter.
[Droid Eris Android Development] pkopalek:
I tried grabbing the /system/bin/bootanimation file from another ROM (so that the 'bootanimation' command would maybe work?) to see if that makes the difference, but it doesn't seem to.

It seems like something silly is missing! I even did a Root Explorer search for anything with the word 'boot' in it to see what could be causing the trouble, but I don't see anything at all! The only things with 'bootscreen' or words like it is in the /system/media/bootscreen/ folder that is there (because I put it there).

Baffling!
[Droid Eris Android Development] lostbytes:
Here are screens of what i did, I recreated the whole process and it worked fine for me. Again i am running the Plain Jane ROM (Thanks to Jcase) if that matters.

link To Screen

Hope this helps!!!
[Droid Eris Android Development] pkopalek:
I confirmed this DOES seem to work on normal Eris-based ROMs like yours (Ivan's 1.0, in my case)

but NOT on EvilEris.
[Droid Eris Android Development] lostbytes:
Would you like me to post the bootanimation file from /system/bin?

maybe replacing this file with mine might solve the issue...

File located here........... Bootanimation

Please let me know if this resolves the issue. If not i will install EvilEris and try to recreate.
[Droid Eris Android Development] pkopalek:
Same exact success rate.

I also had to chmod your 'bootanimation' to make it work, but that may or may not be related to me downloading/pushing it from a Windows machine.

Neither here nor there, just a black screen.

Blah.
[Droid Eris Android Development] lostbytes:
pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I thinks my code was nesting the files in a second bootscreen folder.
[Droid Eris Android Development] pkopalek:
Nope. Exactly the contents it should have.

android_audio.mp3, android_audio.mp3_, boot.gif, boot.mp3, boot_animation.xml, etc etc etc.

Certainly no folders in here. Exactly the contents it should have.

/system/media/bootscreen

same contents as C:\Documents and Settings\Administrator.PAULSTERM1\Desktop\android\downloads\bootscreen

which is where I extracted the bootscreen contents (twice, once from your download, once from my own downgrade.zip. same results.)
[Droid Eris Android Development] lostbytes:
This may be obvious, but make sure to check the permissions on the folder itself.

Try this, then reboot.

adb remount

adb shell chmod 775 /system/media/bootscreen

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

Sent via the XDA Tapatalk App
[Droid Eris Android Development] orcsbane13:
this didn't work on CyanogenELB but tried it on PlainJane and it worked perfectly. So is definatly Rom dependant.
[Droid Eris Android Development] pkopalek:
I exactly set the permissions on the folder itself.

Everyone (EVERYone) can read and write.

Set them with chmod.

Then set them with Root Explorer (checked all of the boxes). Same success rate. 0.
[Droid Eris Android Development] lostbytes:
Bootscreen Issue

Well here is my take on the problem. We have confirmed that it a ROM dependency. The first place i would like to check is the native running services at start up (init.rc). I have seen multiple different service calls for the for the boot animations and sounds. What I would like someone to do is:

EITHER

Run the code below and post the file for me:

adb remount
adb pull /init.rc C:\init.rc.<rom-name.here>

The file will be located on you C drive root.

OR

Navigate to init.rc using root explorer then view as text and check that you have these service definitions.

service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media

service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin

service bootanim /system/bin/bootanimation
user graphics
group system audio graphics
disabled
oneshot

The first service restarts media, the second is the media service, and the third is the boot animation service. All of these must match EXACTY. if it does not match it will require a modified init.rc (which will take ME (<wink> Jcase) some time) If yours differ please preform the shell commands and get me a copy of the file.
[Droid Eris Android Development] akipfer:
Works perfect on XTR 3.0.1.

Thanks!
[Droid Eris Android Development] toolittletoolate:
i run CELB 2.8. no sounds.
[Droid Eris Android Development] wecramer:
This is awesome...thanks!
[Droid Eris Android Development] Nikolai2.1:
Would love if someone could port this to Eris Lightning Bolt
[Droid Eris Android Development] semmtexx:
when I try to push the bootscreen folder to: /system/media/bootscreen, all I get is the list of debug commands. I don't have a bootscreen folder. All the steps up to this were successful...
[Droid Eris Android Development] Nikolai2.1:
It creates a bootscreen folder.

type "ls" in shell and you should see it there.
[Droid Eris Android Development] semmtexx:
That's my problem, though. It won push the files. When i enter the push command with the correct directories, it just keeps ging me the list of adv commands. I did go to shell and list the conents of media and nothing was pushed. I changed the bootscreen.bak back to a zip and i guess ill try again later. Oh BTW im using the latest xtr sense rom.
[Droid Eris Android Development] Nikolai2.1:
Rom shouldnt matter unless its not supported, but regardless it will push.

Did you do adb remount?
[Droid Eris Android Development] semmtexx:
Yup i did remount. It just doesn't make sense. I can go into the shell and make changes with commands like cp and rm, but i just can't push anything. What the heck.
[Droid Eris Android Development] Sjflowerhorn:
has anyone made a custom boot screen with sound yet? just figured i'd ask here lol
[Droid Eris Android Development] Nikolai2.1:
Idk man. But im testing evil eris 4 and it works but theres no sound