yashsingh1/xdaforums huggingface dataset:
[Gen8 Android Development] Javierinnn:
What is the point of this thread. If you want AC3 just pay for it. I did and I think most of the 101 users did. It´s 15€ common.
[Gen8 Android Development] JasonOT:
I have AC3 playback just fine with RockPlayer, thank you.

The point of this thread is to get back the smooth 720p capabilities with which Archos shipped the player.

The point of this thread is that I refuse to pay to restore functionality that has been removed via software update.
[Gen8 Android Development] Manthis:
Thanks, I'll give it a try, but from what I remember another drawback of using Rockplayer is that the Search/Home/Back/Options menu (on the right of the screen) does not disappear while playing videos. Is there any chance you'd have a solution for that, too?
[Gen8 Android Development] elmerohueso:
To whine. OP is upset that the Eclair firmware could play AC3 but the Froyo firmware can't without the plugin. The OP either 1) knew that it was always Archos' plan to require an additional plugin to play AC3 as this has always been noted on the specs page and he assumed the plugin would be free (and he just found out what assuming does), or 2) didn't bother reading the mentioned specs and assumed that the Archos would always play AC3 (see note on assuming).

It might be good to note that the plugin wasn't for sale when the Archos tablets initially went on sale (though the specs page still did say an additional plugin would be needed), which is probably why the plugin was built in to the Eclair firmware. That way we didn't have to go without AC3/MPEG2.

I think this thread should be locked as the OP has now sufficiently carried out his whining and empty threats on at least 2 different forums.
[Gen8 Android Development] hurrpancakes:
Rockplayer has a hardware decode option.
[Gen8 Android Development] JasonOT:
...that doesn't actually do anything on the gen8 tablets.
[Gen8 Android Development] JasonOT:
Everything you've just described fits the definition of bait-and-switch fraud.

If you'd like to XXXX Archos for defrauding you, please do it at the other crapfest forum sponsored by Archos.

MOD EDIT: Watch your offensive language. First and final warning
[Gen8 Android Development] elmerohueso:
and...scene.

That's a wrap people.

Can we close this thread now?
[Gen8 Android Development] JasonOT:
How about you just troll somewhere else?
[Gen8 Android Development] Javierinnn:
OK JasonOD, had enough of this.

Give me your bank account number, I will transfer the 15€ myself under 1 condition: Stop whining for God´s sake, how old are you????

Best regards,

Mecagonto Loquesemueve Jr.
[Gen8 Android Development] elmerohueso:
You just made my morning!
[Gen8 Android Development] ExploreMN:
Considering they released the source code for the OS to the public...I would say yes.
[Gen8 Android Development] JasonOT:
If you want to PayPal me, be my guest.
[Gen8 Android Development] BrockAtkinson:
Not meaning to cause harm by ressurecting this thread, but I assumed that AC3 playback on 2.1 was like a trial, anyway. Once you'd used to trial, you upgraded to the full version, and it was how it originally intended.

I'm going to buy the cinema codec anyway. Just when I have the money (I'm a poor, poor student). It does seem a tad expensive for 800 kb, but I'll do it to support Archos anyway, in the hopes they'll make an even better Gen9 series.
[EVO 4G Q&A, Help & Troubleshooting] lmasieri:
On stock messaging the LED notification will shut off after 5 minutes, in Handcent it will keep blinking until you check the message... Is there any way to take this off? I mean I want the LED but just for 5 minutes, not until I read the message.

Any thoughts?
[Vibrant General] Damonkashu:
I would like to tinker with it and add options for selecting the tone for the timer mode.
[Vibrant General] Damonkashu:
hrmm does no one use this app at all? I just came from an iphone 3G and this app pretty much replicates the experience with some minor set backs.

Is there a better clock/alarm/timer app out there?
[Captivate General] reno55:
I have read some of the other threads posted and well my gmail is showin an unread count of 4 and when i go to gmail on my computer it shows none unread...I dont know how to fix this
[Captivate General] justmde:
Clear the data of the app should help. To do that in tibu goto the app and select it and wipe data. Of in setting go to app then manage the select app and clear data
[Captivate General] reno55:
Triedthat it did not fix it
[Captivate General] nahrah:
Try going to all mail label in Gmail app and delete it from there. Happen to me sometimes I would delete mail but still showed I had one or two.
[Captivate General] boborone:
Happens to me from time to time. Always works itself out. Not sure how, but it just does. Give it time.

From a phone
[Touch CDMA Android Development] Josue_181:
Which is the best ROM Android according to you for our beloved HTC Vogue taking into account the following: drums, interface, stability and speed.

I remember having seen a topic well here but it seems I am far behind so best is to create a more updated where their votes will have a reference for users wishing to change their WinMO by Android and don't know which is the best ROM today.

Best regards.

Sorry for my bad English (translator online).
[Touch CDMA Android Development] cacapee:
scooter's

However you have to make sure to update all the apps manually. I'm really happy with the response and stability
[Touch CDMA Android Development] Josue_181:
Taketh into account your suggestion, then I install this ROM this in the thread called: Scoot CyanogenMod 6.1 (RLS5a) [01/12/1910]?
[Touch CDMA Android Development] Does_It_Matter:
Try Scooter's ROM and also try this one:

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

Fat Free release 5 Froyo

works best with the 10-31-10 2.6.25 Vogue Kernel

If you use the Scooter Rls 5a rom - you have to use a 2.6.32 kernel

Both are good roms as far as speed and stability.
[Touch CDMA Android Development] Josue_181:
The ROM Fat Free Froyo [ODEX'd RLS5] is the that I have installed but with Kernel 2.6.32 and I think that is why me to so many problems.

Scooter Rls 5a install after.

Best regards.
[Touch CDMA Android Development] hom.hom:
So to conclude Scoot's build is the best, most stable and fastest build for vogue out there....

Even better than fresh froyo which i am currently very happely using. Would a transfer be worthwhile??????????
[Touch CDMA Android Development] Does_It_Matter:
Depends on your usage.

I never had an issue with Scoot's or Fat-Free Froyo

However, with Scoots - you need the 2.6.32 kernels

The Fat-Free Froyo's can use the 2.6.25 kernels

When using USB - I was only successful on getting reliable USB connects with 2.6.25 kernels

So - if you do a lot of USB transferring, you probably want to stick with 2.6.25 kernel,

meaning you'd be stuck using the Fat-Free Froyo version.
[Touch CDMA Android Development] cacapee:
Kinda a noob question, other than sd card not working, why would one want to use the 2.6.32 kernel?
[Touch CDMA Android Development] Josue_181:
I think that you question is because used the kernel 2.6.32 and if you read the previous messages is by works better with this kernel USB connection and for the ROM Fat Free Froyo is the should be used.

Exact, I use much the USB connection and so far the only one what worked is Fat-Free Froyo that thing and installed again with the kernel that I recommended up.

Thank you all for your answers ;)
[Touch CDMA Android Development] Does_It_Matter:
Well, like stated above - it depends on what ROM you want.

The Scoot ROM's require 2.6.32 to function correctly, but I could never get USB sync to work correctly, so I don't use the Scoot ROM's

I stuck with Fat Free Froyo and the 2.6.25 kernel (10-31-10) dated one

Works for me and the USB sync also functions
[Touch CDMA Android Development] hom.hom:
As I am in no need of connecting my phone to my pc, the criteria of chosing a Android build is purely based on its stability and speed..:rolleyes:

So who is the victor then?:)

Of these builds,

http://xdaforums.com/showthread.php?t=819081: [Android] Fat Free Froyo [ODEX'D RLS5] 11/4

http://xdaforums.com/showthread.php?t=712310: Incubus26Jc's Super FroYo 2.2.1 [Deodexed] [RLS16] [10/2/10] All Languages

http://xdaforums.com/showthread.php?t=738612: [ROM] SagaROM Froyo Ultralite [RLS5] [12/4/10] with Data App Replacements

http://xdaforums.com/showthread.php?t=868584: CM6.1 Barebones "Gingerbones" RLS5.1 12/12/2010 + 4.55 Re-release

I also have a question about the different kernels, does the 2.6.32 kernel has any speed improvements towards the 2.6.25 kernel..And if it's not too much of an hassle I would like to know the diffence between the kernels (maybe a changelog to be found somewhere, cause I couldn't find one).

**Offtopic: There isn't an Android build with multitouch support for our devices, since the screen is resistive, is there? (the reason why I ask is because the new google maps has the function to see 3d buildings:eek:, but our phones also don't pack enough graphic power do they?)**
[Touch CDMA Android Development] Josue_181:
The new Google Maps this very good but for terminals of last generation and obvious that Vogue it is not JAJAJA.

And you working properly the camera? As indicate works me well USB connection but the camera has some bugs when you zoom and switch to video mode closes and install the kernel you mention 2.6.25 kernel (10-31-10).
[Touch CDMA Android Development] hom.hom:
As for the camera functions I have the same problems, but I don´t really use the camera and the usb to pc connection. I only care about the stability and speed of a build. I only use the phone for calling and internet.:)
[Touch CDMA Android Development] quartapound:
kind of a useless poll.... obviously FROYO is the best... because its the newest and has the most fixes, features, ect.... and when Gingerbread comes out (and is stable...) It will be the best ROM to have.... yet again because its the newest.

Why would donut (ie the oldest, most outdated rom) ever be the best?

A more accurate Poll would be compare separate dev's roms (two people who have made a Froyo release).... but that isn't very nice, as someones feelings will always end up getting hurt.

This poll cannot be done properly
[Touch CDMA Android Development] Josue_181:
Ok just wanted to be sure that not only happened to me and I do not use my camera much but it would be better to have all 100% operational.

If you do not like the survey simply NO VOTE no because it is newer something mean better.
[Touch CDMA Android Development] thoughtlesskyle:
i disagree, donut was the most solid. it was stable, and it was the first and last time Everything (except mass storage on windows) worked.

mms didnt work either (sending receiving on sprint works fine) and if you use the one RIL update even that works (another users tested and found it)

camera AND camcorder worked (with older kernels)

it didnt have data corruption issues

vogue battery consumption was great

it ran on the old 2.6.25 kernels without any sort of sleep screen of death

ran on haret just fine

just because its not the newest version of android means it gets forgotten, esp with new people starting with froyo and not knowing the history thats there. by your statement your saying that vista was better than xp just because xp was older, even though it had poor memory management and was a resource hog. your statement is exactly the reason why people forget how soild donut was.

and no froyo doesnt have the most fixes on native devices yes froyo and gingerbread will be better, but on the vogue it has just cause more problems the newer version we go. i personally used froyo but its obvious you weren't here for the progression to froyo
[Touch CDMA Android Development] mrkite38:
Well, you might wait for dzo's gingerbread port... ;)
[Touch CDMA Android Development] Josue_181:
Better not could you have said thoughtlesskyle as I said in my previous comment it mas not new is always better and which not like this survey simply not vote and thus avoids inconvenience.

Best regards.
[Touch CDMA Android Development] challa.ani:
Fat Free Froyo all the way!

Definitely fat free froyo (odex RLS5). I have tried every other release on my vogue and nothing has been as smooth as the Fat Free Froyo. SuperFroyo is probably the next best thing, but the Rom takes up a lot of space and finally I'm left out with only about 19Mb or something after I install three or something other applications. And also it lags a lot and freezes and crashes more often. Fat Free Froyo is refreshing, the new theme that is.. and I've had it for over 2 weeks now and it hasn't frozen and I didn't need to restart my phone so often. There are some bugs in it , with the Voice search widget and the android keyboard for example, but thats a really small price to pay for the quickness and stability it offers.
[Touch CDMA Android Development] thoughtlesskyle:
i dont use the build much but supposedly my galaxyS build is pretty stable too, i dont use it much though since i kind of did it because i could

http://xdaforums.com/showthread.php?t=827008
[Vibrant Q&A, Help & Troubleshooting] jim@dicrescenzo.com:
I have been having trouble with my Bell Vibrant for the past few days, with a black screen after the 'S' Tried several things out there to resolve this issue, nothing seemed to work.

In desperation I tried the Odin3 one-click, not noticing its for the captivate. I successfully flashed and am now in a reboot loop with the AT&T logo screen. I can't get into recovery mode. or download mode to re flash with different ROM.

Any ideas????
[Vibrant Q&A, Help & Troubleshooting] s15274n:
Describe how you are getting into download mode ....
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
isnt there still a download mode for the captivate?

UHHH

you should try posting this in the captivate section aswell, since most people in vibrant don't have captivates. they have vibrants. ;)
[Vibrant Q&A, Help & Troubleshooting] jim@dicrescenzo.com:
I am currently not getting into download or recovery. I attempt both with the following

Download: vol down + home + power

Recovery: vol Up + Home + power.

I was able to get into either mode before this flash.
[Vibrant Q&A, Help & Troubleshooting] s15274n:
Open Odin

USB to pc

power off phone

Hold both volume buttons

Keep holding and plug USB into phone

Download mode?
[Vibrant Q&A, Help & Troubleshooting] tazman171:
Have you checked your thread in the Captivate Q&A section? A few posts are in there for you. :cool:
[Vibrant Q&A, Help & Troubleshooting] jim@dicrescenzo.com:
Resolved!

Posted solution in captivate forum

http://xdaforums.com/showthread.php?p=9846016#post9846016
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Hey everybody, I'd appreciate your help here since my phone is completely unusable and I don't have another one to fall back on at the moment...

So today I was using my phone and the battery was low when I put it in my pocket (I think something like 8%). By the time I took it out again it was dead so I assumed that it had turned itself off. When I get back home a few minutes later and plug it in and turn it on, to my dismay it gets stuck on the white bootloader with the Android guys on skateboards and gets no further in the boot process (at least visually). Sometimes the white screen will be on for only a couple seconds and it will turn itself off. Most of the time it takes a few minutes before it will turn itself off. It never gets to the Android boot animation and never shows up on ADB so I haven't been able to run anything on it. I tried taking out my MicroSD card and this changed nothing.

Next I tried to boot into recovery and was even more horrified that the phone stalled in the same way it does when I try to do a normal boot. I can get into the bootloader screen by holding the volume down key during the boot, but unforunately my bootloader is still S-ON so when I try and flash the recovery image via fastboot I get the following:

$ fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... FAILED (remote: not allow)
finished. total time: 0.001s

Also, when the bootloader menu is loading the following briefly flashes on the screen (had to take a picture of it in order to read/write down):

SD Checking...
Loading...[PB00DIAG.zip]
No image!
Loading...[PB00DIA3.nbh]
No image or wrong image!
Loading...[PB00DIA2.nbh]
No image or wrong image!
Loading...[PB00DIAG.nbh]
No image or wrong image!
Loading...[PB00IMG.zip]
No image!
Loading...[PB00IMG.nbh]
No image or wrong image!

If I try to go into recovery from the bootloader menu (instead of holding up during boot) it fails in the same way. I'm really regretting not going through the effort to get a S-OFF bootloader now. :(

Anyways, at this point I'm at a bit of a loss for ideas. Is my phone totally bricked?
[Droid Eris Q&A, Help & Troubleshooting] CCCP4ever:
Since you can't flash S-OFF obviously through recovery try this method. Download the file here than:After you download the file, do not unzip it but just place it on your sd card. Make sure its not in any folder. Do not rename the file. Turn off your phone, hold vol down and power phone on. It will scan for the file for a minute. After it is done it will have some options where one of them is to install the file. Remove battery cover before you do that and prepare to pull the battery. Hit the install option ( hit vol up button) it will start the install. Once the screen goes black and boots back up pull the battery. Presto you have S=OFF bootloader. =) hope it helps. And im assuming the only way you can get the file on sd is micro sd adapter.

After you get s-off you can flash custom recovery and hopefully new rom.
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Ah I had no idea it was possible to flash the S-OFF bootloader straight from the stock one... I'll try that soon, but could you possibly post the md5sum for the file? Given that the bootloader is seemingly the only uncorrupted bit of my phone right now I'd like to make sure I don't mess it up. ;)
[Droid Eris Q&A, Help & Troubleshooting] CCCP4ever:
I dont have md5sum as im not author of file. its regular rom with s-off when you flash it as PB00IMG.zip first thing it flashes is the bootloader, thats why you pull the battery later, unless you want or need the rest. but you really dont need md5sum.
[Droid Eris Q&A, Help & Troubleshooting] roirraW "edor" ehT:
I found this MD5 at http://www.thefuzz4.net/home/AndroidPhones/Eris/HowToRootYourHTCEris.aspx for a rooted PB00IMG.zip if the file is exactly the same, of course:

63eacc5ede3b179f95dc22d8ef585f94
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
If it makes you feel any better, you are not the first person to be in this situation as a result of operating the Eris in a low-battery condition. (You will find threads on this site that advocate that folks drain their battery all the way down to "calibrate the battery" - and a small number of unfortunate users have ended up with phones in the state yours is in by doing just that. It goes to show that the quality of advice you get here can be "uneven")

Flashing the root PB00IMG.ZIP ROM - md5sum 63eacc5ede3b179f95dc22d8ef585f94 ( as suggested by CCCP4ever and roirraW "edor" ehT ) will only succeed if the bootloader on your phone is not version 1.49.0000. You didn't say what bootloader version you had, but you can certainly find out by looking at your screen in Hboot mode, or, with the phone in fastboot mode

fastboot getvar version-bootloader

There is a trick that was discovered by SoSicWiTiT which utilizes that (root) ROM in combination with the "Official" 2.1 RUU which is claimed to bypass the checks that normally would cause the ROOT PB00IMG.ZIP ROM to not install using the HBOOT method - but it is apparently necessary to get the phone into RUU mode to do that if there is not a bootable O/S available.

e.g. in your case, with the phone in fastboot mode, first do

fastboot oem rebootRUU

Then, run the RUU Utility up to the point where it unpacks everything and is getting ready to do the install, and then:

- find the "rom.zip" file location underneath your C:\Documents and Settings\<your user name>\Local Settings\Temp folder

- delete that rom.zip file

- rename the Root PB00IMG.ZIP file to "rom.zip", and place the file in the above location, and then

- continue with the RUU install.

bftb0

PS Note that any flashing operations ought to be done with a well charged battery - leaving your phone in HBOOT, FASTBOOT, or RUU mode will rapidly discharge the battery even if it is plugged in. Don't let it sit in that state for a long time after charging the battery fully.
[Droid Eris Q&A, Help & Troubleshooting] semmtexx:
Wow. Does this basically mean that people that are rooted and using custom roms should not let their device go into low battery conditions? This is the first i have heard of this.
[Droid Eris Q&A, Help & Troubleshooting] CCCP4ever:
Shouldn't be a problem. I never had one. Flashing something when your battery is dying would be the only issue.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
It's very low risk - there have only been a few reports of severe problems that were associated with having a low battery condition. Probably it depends on handset to handset manufacturing variations in the rare cases where problems happens; it certainly is not a widespread problem.

When you consider how the phone is made, it becomes immediately apparent that 100% of the flashing occurs in a single 512 MB flash memory chip - it is just logically partitioned into many different contiguous slices. Everything is in that one chip - bootloader, radio, "nvram", as well as the more commonly recognized set of partitions {recovery, boot, system, userdata, cache, misc}.

When the phone is operating normally - that is, with the regular O/S booted - it is constantly writing to the /data partition, even when the battery is low (< 15%) - the same chip that has everything else stored in it, including super-critical things like the bootloader. So, right there, that implies that it is designed to run "well enough" at low charge conditions. But it is also absolutely correct to say that as the battery voltage decreases, the probability of a bad flash write operation is steadily increasing.

Now, if corruption were to occur in the /data partition on a stock phone, the phone could be rescued with a simple "factory reset" - assuming that the /data partition condition didn't cause a bootloop. Even the stock recovery boot has a means to perform the factory reset procedure, so really, you don't even need a working O/S to recover the phone from a write fault in /data with a stock phone.

What about a write fault into something more critical - like the bootloader, or misc partition? If the bootloader fails, there is no means of rescue; and we already know that the bootloader inspects various other partitions when it starts up. Moreover, we really don't know whether the bootloader is performing writes into flash memory when it is operating. So, the safest practice is to avoid writing to anything but /data when the battery is low - that certainly means avoiding flashing ROMs, but might even mean something we take for granted - rebooting the phone.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Hey everyone, thanks for all your help so far...

Luckily I had the 1.47.0000 S-ON bootloader so just using that update worked to get the 1.49.0000 S-OFF installed without the workaround. Now I can use fastboot to flash the recovery image, but this seems to change nothing! The phone still stalls at the bootloader (droids on boards) screen when I try to go into recovery. If I understand correctly, PB00IMG.ZIP contains a full rooted stock ROM, correct? Would it be worth it to try letting the boot loader install all the contents of the file, not just the bootloader? (I was trying to hold off on this in an effort to not wipe all my data... guess I should've been using an automatic Titanium Backup schedule :o)