yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] blastik:
its better than criticise with "wtf" and all this sh**. developers do this as a hobby so chill out man. It's a experimental rom. It says it very clear.

btw.i have built in keyboard included
[Desire Android Development] rex1825:
re:

Hello,

I am using your rom on my desire, and I encountered a lot of slowdowns. I know this is due to the system not being made for our old phones :p but isn't there a way to fix this?

There is also big problem with applications, donno if other have same problems, but sometimes, from nowhere phone hangs, and stays so for a minute or more, then runs normal again, ...but sometimes it must be hard-reset.

And one suggestion, donno if it is possible, but the old cam from 2.X.X is working just fine with this device, isn't there a possibility to get those drivers/apk or whatsoever to run on 4.X.X? Like replacing original ICS/JB with old Froyo/Gingerbread apk? That would fix the cam problem for sure...

Tnx and keep up the good work, cheers...
[Desire Android Development] HorzaSe:
Any chance for an updated Bluetooth stack?

Was having problems with some Bluetooth-hardware and Desire and I'm following this ROM eagerly.

Is there any possibility of updating the Bluetooth stack to the latest LINUX one or is ICS already updated?

http://www.bluez.org/download/

And also which Kernel is this ROM running atm?

Keep up the good work!

Sig:

I'm running he standard rooted gingerbread ROM atm, haven't dared switch to ICS Beta yet ;).
[Desire Android Development] Drunken-Monkey:
Loool.... C'mon man you can't be serious!!!!! If it would be this easy, don't u think that would have been done in the past???!!!

The problem is related to the drives of the CAM. Android 4.x.x has changed a lot in the architecture and thus, the drives of GB can't be used in ICS or JB!!
[Desire Android Development] mardiie:
If you are having stability problems go to rom version 0.16.0 it works perfectly.

After i updated to 0.16.1 i suddenly had crashes/slowdowns.

Hope to see a new version soon!
[Desire Android Development] Kremlin987:
Try checking the md5 checksum of the ROM zip file to make sure the download isn't corrupted/completed properly. Try installing with different options or custom install. You also wiped sdext and boot, right? Not just a "factory reset" wipe?
[Desire Android Development] rex1825:
re:

...srry m8, did I insult someone? I just asked, and made a suggestion... am I doing something wrong? Just asked if there is possibility to swap drivers...

Cheers...
[Desire Android Development] Tuborg68:
Hi! What is the advantage, if any,whith int2sd over stock a2sd?

Skickat från min HTC Desire via Tapatalk 2
[Desire Android Development] Tones1971:
Im also getting stuck at he android screen. Tried all above options but still wont get any firther.
[Desire Android Development] akhillad:
no ad2sdx in v0.16.1

Ad2sdx not working in latest version... can't fit all my apps in any other storage options...

Liked this from but have to revert back to gb...
[Desire Android Development] blastik:
is someone using foursquare with the ROM's last version? behaves quite odd with the 3G connection. :eek: at least the first checkin makes the 3G connectivity drop.

i'm using the last Radio version.
[Desire Android Development] maglassop:
I to had issues installing 16.1, did a full wipe, factory reset, davlik wipe and fix permissions in a few different combinations but the phone would not get out of the setup wizard after booting it just kept giving me BSOD.

I fixed this by formatting and repartitioning my memory card from recovery. Once I did this it installed fine and has run smoothly ever since and I am using the new int2sd option. The only problems I now have is the data connection dropping out as previously mentioned by myself and others.

I have been using this ROM since 0.2 and for a beta have had very few major issues along the way. Keep up the good work guys!!! :cyclops:
[Desire Android Development] invisible132:
Hello. Does anyone have a problem with video camera? Video recordings are very laggy.
[Desire Android Development] blastik:
i think its a limitation from the ROM. check out the change log.

also I would advise you to tweak the CPU/RAM performance in the toolbox
[Desire Android Development] Tones1971:
Hmm i have tried this too.Will give it another try when i get back from work, and if i have no luck its back to GB :(

I have a CM HBoot installed, but i take it thats ok as its for all hboots?
[Desire Android Development] smithbill:
Freezes on Removing a Widget

I flashed BETA 0.16.1 (mainly stock stuff selected + Nova launcher, Supercharger, stock dialer, not T9). I did a2sd with YNY.

Whenever I remove a screen widget it completely freezes the phone, cant do anything, have to remove the battery and reboot and then it updates my Apps and puts them back to non a2sd mode.

Is there something I can do to fix this as i'd like to use this ROM but i cant if it keeps freezing.

smithbill
[Desire Android Development] smithbill:
I've flashed about 4 times now with all stock stuff and still freezes when removing widgets. I tried using Apex Launcher and Regulare a2sd but still the same. I reformatted and made sure I have 1Gb ext4. Happens every time.

smithbill

---------- Post added 19th August 2012 at 12:23 AM ---------- Previous post was 18th August 2012 at 11:46 PM ----------

Any ideas why the HOME hardware button stops working? I'm sure it worked on one of my previous flash attempts but now I'm using Apex Launcher it doesnt seem to do anything?

(sorry if these are newbie questions which may have already been asked - i have tried searching this thread, other threads and various Google sites but no real resolution).
[Desire Android Development] olive127:
We now all know that version 0.16.1 is fully bugged, I still don't know why it's not written in the first post.

I switched back to 0.15.0.1 and all runs fine.

Good luck to the developer.
[Desire Android Development] Kremlin987:
I had the same problem with apex launcher (posted a few pages back). My solution was to switch to nova launcher, with which I've had no problems.

There seems to be a problem with the Adreno drivers. Has something changed with them between 0.13 and 0.16.1? Possibly related to the video recording functionality? One of my apps that previously worked now crashes on startup without an error dialog (draw something).

Other than those small hiccups, 0.16.1 is working perfectly for me. Thanks, Sandvold!
[Desire Android Development] hearliam:
thanks, love it.
[Desire Android Development] poeartpl:
which type of T9 dialer is in this ROM?
[Desire Android Development] Kremlin987:
It's basically the same as the stock dialer, but on the keypad tab, you can search for contacts quickly by typing the number associated with the letters (2=ABC). However, in the latest release, many people have had errors with the t9 dialer, which cause android.process.acore to crash.
[Desire Android Development] MidnightDevil:
Wasn't there a flasheable T9 somewhere along these posts? Would it fix the latest issues with android.process.core due the new t9?
[Desire Android Development] yigal66:
Do someone have problem with Waze ? I have it successfully installed , can open main screen but when try to open settings or enter address - application just close itself even without FC message. With 0.15.1 it did work fine. Any ideas ?
[Desire Android Development] williamj1:
Hi all, two quick questions.

1. For init2sd, am I correct in thinking I should be on CM7r2?

2. How do I set up init2sd? will it give me options upon recovery install?

Thanks for any help :)
[Desire Android Development] dunmow_dan:
This is because 0.16 and 0.16.1 are using an old version of build.prop. There's an entry in there that breaks Waze, and I believe other satnav apps. Either go back to 0.15, or get the build.prop out of an old version and update in 0.16. I posted a few pages back the actual entries that are wrong, on holiday at the moment doing this through a wireless tether, which seems to be working OK? Don't know if that's effected by the build.prop entries too, as I've changed them to get Waze working?
[Desire Android Development] Kremlin987:
Wireless tether works fine with stock build.prop.
[Desire Android Development] yigal66:
Do you suggest to replace entire file or just remark wrong lines ?

I run compare on both files and there are few differences that I don't know how will affect phone behavior .
[Desire Android Development] starcaGAvari:
Right version ICS

Hello to all!

Do you know when it will come out the right version of ICS?

ty.

Best Regards!
[Desire Android Development] c0nfuser:
Suggest or Not?

Hi guys!

I was using the Runnymede ROM some months now and I am very satisfied with that. Now I am thinking to switch to ICS but I am afraid a bit because is still in BETA version. I just want a ROM with stable Wifi+GPS and which the Apps will be stable enough to run from the SD card(system ext partition). Do you suggest me to install this ROM?

Thank you
[Desire Android Development] Coempi:
Been using this ROM for a month without any problems. Have 40 user apps installed at the moment (don't need more), GPS and WiFi are working fine. I'm really satisfied with this ROM.
[Desire Android Development] mattmanwrx:
The reason the beta tag is still there, is that the rom isn't surely "stable"... It could randomly reboot and there could be done bugs... However, I had used this rom for a long time from the beginning and had no real worries...
[Desire Android Development] xwishmasterx:
Hi bro's :good:

Great rom !!!! Coming directly from miui - unfortunately it was unstable.

Is it possible, to make this great rom with d2ex?

Secondary: my hboot is D++ with 4 ext (1,5 GB). I tried over terminal emulator to put a2sd. But by given comands I receive folowing error message:

10apps2sd is either missing or not executable

Aborting

What does it mean? I don't know how to install now the other apps:(
[Desire Android Development] Souldrinker:
Yes, I was running this rom for quite a while since I switched from runnymede and never looked back. You might want to install haxsync if you want good Facebook integration with highres contact images.

Regarding wifi I never had any issues and a2sd worked fine. I had over 100 apps installed using the a2sd script on cm7r2 hboot.

Gps worked fine most of the time, but sometimes after not using the phone for a while (like overnight) it couldn't find any sats, but briefly starting the gps status app from the play store fixed that and then it worked fine for the rest of the day.

I did have some issues with waze when I accidentally choose the wrong build.prop option in the aroma installer that was mentioned just before your post. But reflashing making sure to select 0 for the value there fixed it.

My son is using the phone now, so even if I keep flashing the new versions I haven't tested them so thoroughly, but from February since Seb stopped developing his runnymede rom (February?) up to June this was my daily driver, so I could recommend it.
[Desire Android Development] Guse:
I'm having a problem with chrome. When installing after download I get some error message, saying that there isn't enough space... that's weird because app2sd works perfectly.

I'm having also a problem with swiftkey3. ROM just reboots everytime I tried to configure it.

Anyone can help?

Thanks in advance.
[Desire Android Development] Bojan155:
Chrome hogs about 30 MB I believe and it forces itself on internal memory it doesn't move to sd-ext. (check in app settings, you'll see the exact size)
[Desire Android Development] MidnightDevil:
I don't know why I can't go further then the Android loading screen lol.

cmr2 hboot with INT2SD, selected standard dialer and flashed T9 after and flashed also latest drewis kernel (I think its the latest).
[Desire Android Development] Kremlin987:
The Android screen means the bootloader has loaded and it is trying to load the kernel (once the framework starts loading on top, the other flashscreen kicks in). So I would suggest trying to reflash without using the latest kernel - it sounds like it is having a problem loading the kernel at all.
[Desire Android Development] jamaniek:
Try Mount2SD intead. And also make you ext partition 0,5GB smaller. I hope it helps.
[Desire Android Development] Co.Tibi:
Does anyone know what happened to Sandvold?
[Desire Android Development] xwishmasterx:
Thank you, bro. ut why smaller? I thought and red 1,5 GB is ok?

Secondary, know you the app rom toolbox pro? you can configure apps2sd - I done it and it functions. Only in the statusbar I read even not enough memory (I see the symbol of it). How get this off?
[Desire Android Development] Thrackan:
Finally got the beta running here. (0.16.1)

Problem 1:

installer detected CM7r2 HBOOT where Oxygen HBOOT was used. (as provided by Alpharev.nl)

Symptoms:

bootloop after install

Solution:

flashed Data++, wipe, reinstall

Problem 2:

bugs and freezes (1%S stopped responding, dismissing it freezes the system for a while)

Symptoms:

crashes in random input fields

"1%s stopped responding"

Solution:

stock launcher / apex launcher replaced by Nova Launcher for the moment

Problem 3:

infinite booting time after moving apps to SD with a2sd (answered YYY iirc)

Solution:

reflash. just formatting sd-ext didn't fix the problem.

That's it for now! Currently perfectly happy FINALLY having ICS on my Desire GSM :good:
[Desire Android Development] dunmow_dan:
- Duplicate removed-
[Desire Android Development] blastik:
seriously guys, anyone is having problems when switching to 3G from Wifi ? I've read a couple of people talking about this. all the rest is really cool!!
[Desire Android Development] ahmad598:
Hi

just wanted to mention that i still have the wifi scan problem, although you've said in the changelog that it has been fixed for this version (0.16.1). these are what i've done to fix it:

wipe cache + data + dalvik before installing the rom

wiping them after intalling the rom

trying the alternative option for wifi included in the aroma installer

factory reset from the settings menu

and here is the dedicated topic for it: http://xdaforums.com/showthread.php?t=1781541

any ideas are appreciated ;)
[Desire Android Development] smithbill:
I had this 1%S stopped responding issue on 0.16.1 but re-flashing with Nova Launcher instead of Apex made no difference.

I reverted to 0.16.0 and it works fine.

Bill
[Desire Android Development] grongo:
The problem is related with T9 dialer. You've to flash with the stock dialer and if you want the T9 dialer, you'll have to downloaded from xda and flash it after a reboot with the stock dialer.

I've posted the xda link to 4.0.4 contacts e few pages back.
[Desire Android Development] poeartpl:
I'm asking, because, I'm looking that flashable dialer for quickly typing numbers(=letters), what is very, very useful for me, and some others ROMs haven't that....
[Desire Android Development] MidnightDevil:
There's a link somewhere a few pages back. Search the thread for t9 flashable you'll find it. Didn't solve the error for me though.
[Desire Android Development] dunmow_dan:
You should just be able to comment out the lines its basically what I did.
[Desire Android Development] Thrackan:
I flashed using the stock dialer.

Also, I didn't reflash for the Nova launcher, I simply installed it.

Error happens on input fields and popups, for now I can say they are usually in the launcher or the Play Store.

I could try to reinstall the Store and see what that does.
[Desire Android Development] smithbill:
I tried that - still got the same issue. I tried stock everything and still the same issue until I went back to version 0.16.

Bill
[Desire Android Development] Geordie Boyo:
Considering trying out ICS. just a couple of quick questions

Can this be used as an everyday rom?

Does it come bundled with the Google Apps? If not, a link to download them?

Does this rom work with CM7r2 hboot successfully?
[Desire Android Development] Thrackan:
1: depends on your definition of everyday ROM.

I can make calls, use apps and interwebs, but sometimes things crash and you need a reboot. For me, that is heavily outweighed by having ICS running on my phone, but then again, all my phone data is backed up somewhere.

2: Play Store, Gmail and Calendar work.

3: it *should* Oxygen HBOOT will not work however.
[Desire Android Development] rickiri69:
Feedback on 0.16.1

I came from the 0.15.

I updated on Tuesday directly on 0.16.1.

-> Too much freezes and battery is draining much more than before.:(

I revert to 0.15.
[Desire Android Development] grongo:
Did you full wipe before?

With me it solved the problem.

Full Wipe -> Aroma Stock Dialer and Nova Launcher -> a2sd (yny) -> Reboot -> Installed 4.0.4 Inverted Contacts with T9 from recovery
[Desire Android Development] Thrackan:
Full wipe, installed with Apex, stock a2sd and v6 script (otherwise defaults) on Data++

synced my account, found that Apex was bugging, installed Apex update, didn't help, installed Nova and deinstalled Apex updates

it's not constantly happening, but it most often happens in the Play Store search input field, with other apps on the background.

note that Apex bugged right from the first boot, regularly not even showing its face.
[Desire Android Development] marko.samiric:
I had lockups in PlayStore search field and when trying to access Messaging settings....and somewhere else but can't remember. Using cm7r2 or stock hboot didn't make the difference. Problem has been solved by adb push build.prop from 0.15.0.1. Google Now also working after unpacking it from 0.15.0.1 build (GoogleQuickSearchBox.apk) and adb push to /system/app.

bulid.prop from 0.15.0.1 solved lockups, but it seems like there is drop in gpu performance, UI is not so smooth as with 0.16.1 build.prop.

so...step by step (stock hboot)

-reboot to recovery

-full wipe

-stock install (0.16.1)

-mount /system folder

-adb push build.prop /system (from 0.15.0.1)

-adb push GoogleQuickSearchBox.apk /system/app (from 0.15.0.1)

-reboot

-a2sd install (going YNY route)

Hope that this helped someone.
[Desire Android Development] smithbill:
That's interesting because I think that's what it did to me.

I decided to retry v0.16.1.

I did Full Wipe -> Stock everything except aGPS -> cleared DalvikCache & Battery stats immediately after flash -> a2sd (yny) -> Reboot

Using stock Launcher (no Nova, no Apex).

I installed CoPilot from an .apk on my microSD and a collection of Apps by using the Google Play webpage on my laptop.

Everything appeared fine.

I then decided to install MXPlayer Codec (ARMv7) using Google Play on my laptop and whilst that was installing I opened the Google Play (Android Market) App on my phone and tried to Install aCar ...and crash ...I got the %1$1 thing with no way out (no button pressing worked).

I took the battery out, waited 10secs, put it back in and rebooted.

It then did the 'Upgrading Apps' thing and when I got back in all my installed Apps had disappeared leaving unusable shortcuts on the main screen (it says App not installed if I click them). I guess its lost the a2sd thing and everything installed onto my ext4 partition has gone???

Is there a way to flash the ROM and then upgrade (or downgrade?) the Google Play app to one that might not have this problem?

Bill

---------- Post added at 01:52 PM ---------- Previous post was at 12:55 PM ----------

I tried your instructions Marko - downloaded 0.15.0.1. Took the build.prop file from the /system folder. Went into Recovery mode. Used adb on my laptop to push build.prop which reported a few Kb written. Rebooted the phone and everything seemed okay. How do I confirm the right build.prop is in there?

I dont know how to test if your suggestion worked but I tried starting up CoPilot so there was an App running in the Status bar and then went to Google Play on the phone, searched for aCar App, installed it okay and everything seemed fine.

I then went into Settings -> Apps and was moving some Apps to SDcard when bang... "Unfortunately the process %1$s has stopped". No way out. I left it sat there with the error on screen whilst I typed this post but my phone has just decided to reboot itself.

On rebooting it seems to have lost my Apps again (shortcuts left but "App is not installed"), but i've found that if I just reboot it manually it recovers the Apps.

Bill
[Desire Android Development] MidnightDevil:
Did the same, still got the same error.
[Desire Android Development] Thrackan:
I'm no expert whatsoever, but what could be the reason that the exact same configuration works on one Desire and not on another?

Is there actual difference in hardware?
[Desire Android Development] marko.samiric:
Settings -> About phone -> Mod version

there should be Beta_0.15.0.1 since pushed build.prop hasn't been altered.

why moving apps to SD card that way if you are using a2sd :eek:

ext4 sd-ext partition is enough. Move apps back to phone. If you did a2sd install, apps will be in sd-ext, instead in phone's nand flash.

Don't know...reboot into recovery and make dalvik+cache wipe for now...:confused:
[Desire Android Development] mattmanwrx:
Yes and no... All should be the same... However, the chipsets will be different (some can be overlooked higher)... Also on the older pvt4 devices the "something.or another, cant actually remember" was different... With koush having to create a separate recovery for it..

@Bill, can you replicate the error? If so, maybe run logcat while replicating the error and it could tell u what the error is...?
[Desire Android Development] marko.samiric:
maybe damaged/worn out nand, but that is something that happens mostly to developers . I had major phone malfunction recently due bad SD card. It would boot nice, but would stall frequently afterwards...
[Desire Android Development] Thrackan:
Oh yeah, I came across the PVT1 to -4 terms recently. That might be the answer to my question.

If so, I would advise everyone to post their PVT-version!

My Desire is a PVT-1
[Desire Android Development] smithbill:
I used Excel to sort the two build.prop files from v0.15.01 and v0.16.1 and then Word to do a compare on them. I can see these values changed and some assorted ones removed. Would these make a difference to the '%1$1' problem?

Bill

com.qc.hardware=1

dalvik.vm.lockprof.threshold=500

debug.enabletr=true

dev.pm.dyn_samplingrate=1

ro.build.date.utc=1343214465

ro.build.date=on. 25. juli 13:07:45 +0200 2012

ro.build.host=sandvold-laptop

ro.build.romversion=Beta 0.16.1

ro.build.user=sandvold

ro.build.version.incremental=eng.sandvold.20120725.130541

ro.com.android.dataroaming=true

ro.config.alarm_alert=Scandium.ogg

ro.config.notification_sound=Merope.ogg

ro.config.ringtone=Pyxis.ogg

ro.kernel.android.checkjni=1

ro.max.fling_velocity=6000

ro.modversion=Desire Beta 0.16.1

ro.telephony.ril.v3=signalstrength,singlepdp,skipbrokendatacall

wifi.supplicant_scan_interval=45

windowsmgr.max_events_per_sec=120
[Desire Android Development] mattmanwrx:
It shouldn't actually make a difference... It's just different hardware... As long as the rom has been flashed, it has been flashed...
[Desire Android Development] Thrackan:
Yes, but since ICS relies on HW acceleration, couldn't minor hardware changes be the difference between stable and buggy?
[Desire Android Development] smithbill:
I'm still getting "Beta 0.16.1" showing in the Mod version, yet my adb push build.prop /system reports 707KB/s (3634 bytes in 0.005s) so i had thought that meant it had written it successfully. I just tried a 2nd time and its still Beta 0.16.1 (and I checked its the right build.prop file). Any ideas how i get adb to push the build.prob in successfully?

Could I just open the ROM zip file, switch the 0.16.1 prop file for the 0.15.0.1 file, save the zip file and reflash the ROM?

Ah - I did wonder about that! I thought to myself: "aren't I just moving Apps from SDcard (ext4) to SDcard (FAT32)!?"

When using a2sd I'll leave my Apps on 'phone' in future. Thank you for your help Marko!

Bill