yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] TomLeeDesire:
2 cents tips from a serial flasher :

# be s-off

# get your sd-ext yourself with gparted only

# never trust rom manager, just do the simple job yourself

=> never had all of your problems :D

Usb brick ? (had some, quickly fixed)

=> http://androidforums.com/desire-tips-tricks/365476-guide-usb-brick-fix.html

" Note-If you usb bricked on s-off device then try this fastboot command to solve this

fastboot oem enableqxdm 0(unblock your sd-card)

fastboot oem eraseconfig(fix misc partition) "

Everything's fine for me on 0.3.9 with camera zip flashed.

Will quietly wait for full hwa :D

(will that bring a functional flashlight app, or is this absolutely not related and there is another way to get it working ?)
[Desire Android Development] hello247:
Use a 3rd party app called teslaled.
[Desire Android Development] TomLeeDesire:
...when I said serial...

I had no need, but wanted to check if 0.3.10 really brings all those promising problems ;P

Well... none !!
[Desire Android Development] lenny_kano:
Have to agree. Reading properly and doing things properly, I've never had 99% of the issues users complain about.
[Desire Android Development] :
Thanks, fixed my USB brick. and my terminal works now. :D

YOU'RE AN ANGEL.
[Desire Android Development] MattSid:
I don't know if I going to keep this Beta, with the 0.3.9 I had too many annoying Problems: sudden Restarts with the camera, pinch to zoom with problem (with Google Navigation for example) problems with the GPS recognition, Google Calendar disappearance and apps with incopatibility...

I can understand how much could be hard to work on this beta and I would like to thank all the people behind this project, but for everyday use I think that I will come back to Gingerbread with Sense (ugly UI in comparison but works)...how I could reinstall it?

Of course in the future I would like the reinstall the ICS, but only when it will be full-grown :)
[Desire Android Development] TomLeeDesire:
You're kidding, right?

How could you be trying this rom and asking how to install another one???
[Desire Android Development] MattSid:
Nope, I'm simply newbie and I this was my first Rom ;)
[Desire Android Development] DroidRevenge:
Newbie?

I am revealing an incredible secret to install ANYother ROM: there is a magic box called "SEARCH". Try it! It will bring to you in a fantastic new world!

I am kidding....

Just look into development thread and install the ROM with fit your desires! :D4

If you has installed this ROM you will be able to install other ROMs too...
[Desire Android Development] Sage:
You flash an old ROM the same as you did ICS. Put the update.zip on your SDCard. Boot to Recovery and flash it. Remember to wipe data/cache and dalvik first.

If you are going back to gingerbread (which i have considered too i might add) try Oxygen 2.3.2 no sense though so much better with Launcher Pro (has the same widgets).

can get it at oxygen.im

good luck.
[Desire Android Development] MattSid:
Thanks Droid! Just another few question before looking other threads:

I have done the formatting in ext4, this could be a Problem if I want reinstall the old gingerbread?
[Desire Android Development] jozef710i:
No if u dont restore Rom nandroid backup with ext3 pertition. When u install new Rom it will be OK
[Desire Android Development] MightyBen:
Custom HBOOT for Androdid 4 (Ice Cream Sandwich) - 222 MB for Apps

Hello!

I've made an alternative HBOOT with 222 MB for Apps

The partition layout is:

/system

210 MB

/cache

5 MB

/data

222 MB

MD5: a85c40255d7afe43293a1e39c253f13d for the img file

and:

MD5: 05c18805a6eeea59ad5c7f08f27d9794 for the ZIP file

Check those hashes carefully.

And you need a symlink to SD Card due to small cache partition

All Credits go to _thalamus for his HBOOT Patcher
[Desire Android Development] twics:
I messed with my phone had to do a full wipe, now running 0.3.10 all good but lost the use of xdata:o

When I type xdata in terminal I get

/system/bin/sh: xdata: not found

127app_58@android:/ $

anyone know what im missing?
[Desire Android Development] guy_smiley:
Intelligence, the search function, the OP?

One, it doesn't appear you are SU as your prompt is $ not #, try typing in su then enter. The command is not "xdata", it's "a2sd xdata".
[Desire Android Development] twics:
Thanks alot for your help:) for the record though I do search/read and did type SU, but thought I had to do that once not everytime I use terminal was'nt paying attention to $/#, mybad, :o now iv got all my space back.

Many thanks again.

Intelligence???
[Desire Android Development] googleroid:
anybody know how to user chrome beta for android in this rom?
[Desire Android Development] Sage:
So is the general consensus that full wipe is needed to go from 0.3.9 to 0.3.10?

Or just dalvik?
[Desire Android Development] TKG26:
just downloading now.. Do we have to xdata through the terminal with each version upgrade we flash? Ill fire up the terminal anyway, but its an extra step i missed the first time i ran the earlier version of this rom..

ITs my daily driver now.
[Desire Android Development] xelra:
OMG, dude! The answer to your question is on almost every f4%@& *% page of the last 20 pages of this thread!

Are you guys serious or is this a conspiracy to be a pain in the a$$? :banghead:

P.S.: no flame war now please. :cool:
[Desire Android Development] TKG26:
Your response and now mine as well are worse time and space waster then the guys question.

Why not just ignore the guys post if it annoys you that much... ?

No flame war intended. :)
[Desire Android Development] redrum781:
Well flashing camera.zip or 0.3.10 without full wipe makes phone almost unresponsive using camera.

I don't feel like full wiping again just for barcodes or panorama shots.

Sure, all you need is full hwa (not included) :p
[Desire Android Development] KiCR:
I had the same problem. Taking 2 pictures, went back to app drawer und phone was very slow and rebooted. Go to app settings > Camera and delete data. Took a few pictures and it seems to work.
[Desire Android Development] Wekkel:
Had the same experience. Now 0.3.10 with full wipe/factory reset and cam/vid still giving trouble.

0.3.9 seems more useful.
[Desire Android Development] LaizyJumper:
I confirm that. It works until you use the camera. Camera gets closed without any notification. After that the phone is completely unusable. I checked logcat, all different processes got "died" and then restarted. All widgets and apps shortcuts in launcher disappeared and then reappeared, several times, until rebooted.

And it is weird that there are no FC messages, processes just get killed without any notification. And then restarted.

It does not matter if you wipe (full incl. dalvik) before flashing or not. I tried both ways.

Finally flashed back 0.3.9 and everything is stable. :cool:
[Desire Android Development] Lothaen:
aw that's sad - I was going to wipe and flash 0.3.10 this morning - its the recommendation to go to 0.3.9 now if you want camera to be stable?
[Desire Android Development] Nakebod:
Maybe a stupid question, but I want to be sure if this is correct:

I flashed a clean ICS 0.3.10 yesterday, wiping all data before the flash. Enabled a2sd before installing apps, rebooted, and started installing apps. The internal memory was still getting filled up, cleaning dalvik-cache did work, but when installing new apps the internal memory was running low again. So I saw some people mention xdata, looks promising so just tried that and ran 'a2sd xdata', and everything is looking fine now, I have free space, and still running fast on my class4.

Now the weird thing, for me.. :confused:

Settings > Storage shows 0.94 GB total space: 436MB apps and 201MB available space. I was expecting over 500MB free space. If I look at Settings > Apps it shows 738MB used, 223MB free. So there is a 300MB difference between "storage" and "apps".

I don't need the "missing" space, I have all my apps I used to have in my previous ROM, and everything seems to work perfectly. But I'm just wondering if this is normal?
[Desire Android Development] Akarim47:
Not available for all countries
[Desire Android Development] MatDrOiD:
Wasn't posting in a recovery-thread enough for you:

http://xdaforums.com/showpost.php?p=22376582&postcount=903

It really seems you need the money....
[Desire Android Development] shankly1985:
reported for spam, you have now posted this in all the big roms section. when they is a app section for this.
[Desire Android Development] shameete:
i don't have a calender app anymore, so my pure calender widget isnt updating anymore...

i just saw it this morning when i had 0.3.9... after flashing it to 0.3.10 still no results.....

is there any way to get a calender app back? when i looked in /system/app i currently have calendargoogle.apk and calendarprovider.apk available.
[Desire Android Development] Salem24:
Same problem here.
[Desire Android Development] twics:
Had exactly the same issue now back to 0.3.9 too.
[Desire Android Development] Furma:
http://www.engadget.com/2012/02/09/htcs-first-ics-update/

any of those phones uses same hardware as Desire? would their code/drivers help in Desire ICS development?
[Desire Android Development] Lothaen:
adreno 205 i think not 200
[Desire Android Development] K900:
No. Galaxy Ace and Nexus One are most probable candidates.
[Desire Android Development] Furma:
didnt google already say nexus one is hardware limited for ICS so it wont be getting the update?
[Desire Android Development] VyrruS:
It bootloops on 0.3.10 (installed with darktremor's a2sd)
[Desire Android Development] silverback2:
on BravoC (CDMA) the home button doesnt work right. and when i say right, i mean when you press it in an app with anything scrolabole, it take you to the top of the list. and doesnt do ANYTHING other then that. also cant get into the new task manager. most things work belive it or not. anything with the radio works fine. but cant install from market, wont dl apps for some reason. headphone jack is a no go. and camra, as we all know does not work. i will try and remember how to find and post logcats here soon, although idk if i can on my MacBook Pro, (osx not windows)
[Desire Android Development] mattman83:
The bravoC build that was posted is not a supported build - so while you're welcome to test it, noone is going to be able to help much. The kernels in the GSM builds have been very carefully selected and modified to get the best compatibility - from what i read of the bravoc release, while a good effort by the poster, was a relative mashup of a few different kernels. To clarify - most of the issues you have are kernel related. Market issue may be due to bravoc having slightly different memory layout - something may have been messed up there.

While I can't speak for the devs and don't know their ultimate plans, I assume once we have a fully working build it'll be ported properly to bravoc.

M.
[Desire Android Development] tsiftsism:
While on twitter i read this link (www.xda-developers.com/android/how-to-disable-the-google-search-bar-in-ics/) and i wanted to share with you cause i don't remember that it's been mentioned before.

It's about disabling the google search bar on top of the homescreen which i found very annoying when i flashed a version of cm7r2 hboot.

I hope it's very helpful for you to. Just report back if it really works for everyone of us to know it.

Ps. Hope it's not wrong place to share with.

Swyped from my Sense 3.0 Desire using Tapatalk
[Desire Android Development] Sandvold:
1st way= the copying of libs to exiting ROM

LAST resort, this is just pasting in some working libs to our ROM. Something as we've seen have created many and rather bad errors. We've also been speaking to a few good DEVs who say it's a really bad idea. The ROM that's released is not made for it to work this way either so it's bound to create problems. If everything else fails we'll do it this way(I'll release a build with this method Sunday night, I'm away until then. If no other option is available before.) It's something we don't want to do cause it would be close to impossible to troubleshot the rest of the errors and flaws with the exiting ROM becaused of a clogged logcat. And when random things go bad it's quite hard to make a better ROM.

2nd way= using the same hack

It's based on using the hack the same way as it's done in the libs above. But just integreate them into the ROM at build + enable the build for HW acc. This is still a hack, but you can see several ROMs have been doing this(But it's not full HW as they claim it is). It's not ideal, but we're working on getting a build ready this way. So we're also using resources on this "fix". We don't think it's a good idea, but since nothing is sure about when we can expect a full working HW then we're using some of our time to put out a build this way.

3rd way = trying on the good old fully functional HW

We're trying a few different things here(I'm not capable or sure if I could explain what's being done). We have two different approaches to try sort it out. And according to logcat then we're getting closer. Will it work? I don't know.

But at least it's to this most of our resources is being located as we feel this is the best option.

We're also trying to sort out the remaining issues, but as I've stated; most our energy is spent on HW acc.

Hope that clears it up.

And it's no point asking for when to expect a new release. I don't think a single of the releases have been "hidden" for more then 2h. The same will be the case in the future. You'll have it pretty much the same time we have.
[Desire Android Development] silverback2:
thanks for the info. im going to try flashing another kernel, see what happens. wost off i will just have to start over! but if you or anyone else knows where i could dump a logcat or two for the devs to save up until the start a port let me know. and if you have a link on how to do them(been trying to remember all day and basically said screw it:D) but like i said, thanks again.
[Desire Android Development] guy_smiley:
Excuse my ignorance but I thought it was as simple as: adb logcat

(It is: http://wiki.cyanogenmod.com/wiki/Logcat )

And for more information: http://developer.android.com/guide/developing/tools/adb.html

Google works pretty well ;)
[Desire Android Development] jknvv13:
We also need hwcomposer.qsd8k.so for it.
[Desire Android Development] jknvv13:
If you delete the qralloc module, your rom will be faster.
[Desire Android Development] andQlimax:
Cyanogen annunced that will continue to support the QSD8250 series of devices such as the Nexus One and our Desire

so maybe worth to stay tuned on the future updates :)
[Desire Android Development] albertbm:
No, I just installed it and it popped up that it needed my account perms and worked :)
[Desire Android Development] mattman83:
That's great news. I have no interest in the CM roms themselves (i prefer a leaner rom), however it's good to know that such a large dev community will still be backing our devices - very handy for the bigger issues such as HW accell and camera.

M.
[Desire Android Development] dk_zero-cool:
Well its quite easy for them to say that now. Before they get started, these copy paste people, as someone called them in a previous thread, working on this ROM, will have sorted out most of the problems, propely even the GPU which where the reason that most "real" devs, again not my words, consideret dropping the support in the first place.

You are all really doing a great job here. Who needs "real" devs :p
[Desire Android Development] mattman83:
No denying that they are doing an awesome job, however some of these issues are massive tasks even for very experienced devs - the more heads working on ut the better.

M.
[Desire Android Development] Sandvold:
We've done that a long time ago:)
[Desire Android Development] redrum781:
Completely agree on that. It's nice to see our desires are still supported.

I think AdamG said desire will be supported on oxygen 3 as well.
[Desire Android Development] Mefistozisimo:
Good version for an alpha ..tnx a lot!!!
[Desire Android Development] frogfire:
USB Fix

frameworks/base/core/res/res/xml/storage_list.xml

<?xml version="1.0" encoding="utf-8"?>
<StorageList xmlns:android="http://schemas.android.com/apk/res/android">
<storage android:mountPoint="/mnt/sdcard"
android:storageDescription="@string/storage_internal"
android:primary="true"
android:emulated="false"
android:allowMassStorage="false" />
</StorageList>

init.herring.usb.rc

on boot
write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iSerial $ro.serialno
write /sys/class/android_usb/android0/f_mass_storage/inquiry_string "Google Nexus S 0100"
write /sys/class/android_usb/android0/f_rndis/manufacturer Samsung
write /sys/class/android_usb/android0/f_rndis/vendorID 18d1
write /sys/class/android_usb/android0/f_rndis/wceis 1

on property:sys.usb.config=mass_storage
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4e21
write /sys/class/android_usb/android0/functions $sys.usb.config
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state $sys.usb.config

on property:sys.usb.config=mass_storage,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4e22
write /sys/class/android_usb/android0/functions $sys.usb.config
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config

on property:sys.usb.config=rndis
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4e23
write /sys/class/android_usb/android0/functions $sys.usb.config
write /sys/class/android_usb/android0/bDeviceClass 224
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state $sys.usb.config

on property:sys.usb.config=rndis,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct 4e24
write /sys/class/android_usb/android0/functions $sys.usb.config
write /sys/class/android_usb/android0/bDeviceClass 224
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config

on property:sys.usb.config=mtp
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04e8
write /sys/class/android_usb/android0/idProduct 685c
write /sys/class/android_usb/android0/functions $sys.usb.config
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state $sys.usb.config

on property:sys.usb.config=mtp,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04e8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/functions $sys.usb.config
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config
[Desire Android Development] Mefistozisimo:
good news!!!
[Desire Android Development] danarama:
Anyone compiled successfully from this yet? Im not convinced about this source.

My compile from this source is 10MB smaller than alpha 0.3.5 and has in about phone Baseband "unknown".

Also the power menu has reboot to recovery etc that alpha 0.3.5 doesnt have.

I just want to work from the same source as everyone else....

I think this source is just nexus 1 source. Now your desire source.

To save more time, can someone please just upload me their local repository?
[Desire Android Development] chichoko:
I was just rummaging through the thread when my eye fell on this conversation... While I know I am late to the "party", I'd really like to point out quite a few facts..

First of all, none of the people who are puting an effort into this has ever claimed to be a so called "real" dev, as Sandvold pointed out, and nor will be since this is a project started by few and expanded to a "core" testing bunch of people, who were very happy to devote their precious free time in order to get the ICS build running as it should and ofcourse, share it with the community...

Second, they cant be arsed to wait for all the "big", "hardcore", "muthafuckin" devs to get their hands on the Desire, which is 2 years old, so they can taste the newest Android OS... they want it now! And if they can do anything about it, they will, and ofcourse, share it with the community...

Third, if you dont like the methods being used by them, dont even bother posting useless opinions which dont really matter to anyone but yourselves nor trying the rom at all, unless, you have something to add which can help their effort in any way.

Not every one of those big devs were born with the knowledge they have now... Maybe they even started like these people here have... examining someone elses code and trying to combine it with something different seeing whats going to happen... experimenting...

Its ridiculous how the community has turned here... we did have pretty good devs here, and we still have... But since some of the "big names" left the building, it seems that everyone has formed an opinion about what a "real dev" is and how noone else shouldnt in the slightest of the possibilities even think of starting up a project of his own just for the heck of it...

This might seem as a ranting wall of text, and I couldnt care less, so long as this whole madness that has started on XDA stops indefinately...
[Desire Android Development] Lothaen:
yep

hardware limited = low internal storage I can only assume.

The big problem I can see is that a lot of apps are taking up HUGE space on phones (not including sdcards obviously)

G+ is like 12-20MB

Gmaps is like 12mb

Angry Birds are all about 15-25MB a piece

Chrome was about 13-50MB?

if you have a phone that potentially needs the ability to be booted without an sdcard and expect to have a few apps installed and its full - it doesn't look good to a consumer.

obviously here we just use apps2sd and no problem - but in the big 'normal' world its not expected for people to 'hack' (read configure) their phones properly :)

we all know that gingerbread with sense/ICS without sense can happily fit on the phone's limited internal storage - but without a2sd you will have issues with low 'memory' errors pretty quick

that includes using built in Android Apps2sd where you move the APK to the FAT32 partition/..

---------- Post added at 12:15 PM ---------- Previous post was at 11:47 AM ----------

I wonder if we flash 0.3.10 with the camera from 0.3.9...
[Desire Android Development] shameete:
hepfully Sandvold can react on this.. i perform a clean install but the calendar is still not there... :(
[Desire Android Development] tsiftsism:
First time i tried to sent a mms since using Sandvold's roms, but wasn't successful. I asked him to sent me a mms but couldn't receive it too.

I can see the Download button inside his message on Go SMS, i can see arrows inside signal bars moving, but downloading is endless.

I also deleted apn settings (suppose they automatically created after 1st boot) and entered them manually from the list i found on my provider's site, but didn't help either.

Is there anyone else (Greek with Cosmote or not) who is facing problems with mms sending/receiving?
[Desire Android Development] Lothaen:
tried flashing this 0.3.9 camera over the 0.3.10 and it seems to be stable again. on 0.3.10

http://min.us/mdKpqT9ib#4o

obviously any camera tweaks/updates are removed though but any changes elsewhere to the rom are still in 0.3.10