yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] Unrelashade:
Ok guys, I am looking for an ICS ROM since I love ICS and to be up to date with Android stuff. So I had a look at which ROMs are there and found these:

(Ordered in last activity of its thread in the development section)

1. |-ROM-|-4.0.4-|-AOKP-B39-|-CM9-|-6/15/12-|-WildchildIcE-v0.9b-|-Nightlies-|

2. [ROM]HTC Doubleshot ICS 4.03(Sensation XE Sense 3.6)app2ext 5-5-2012

3. [ROM][Official]MyTouch4G Slide CyanogenMod 9 Alpha 5 (06/27) - 4.0.4

4. [ROM]CM9 Unofficial KANG [SEMI-NIGHTLY]

5. [ROM][6 March 2012][Alpha]Pyr-O-Ice FUTUREAL 1.0.0 (Sense 4.0,Android 4.0.3,OC1.5Ghz)

6. [ROM][Mar 7 2012] Pyr-o-Ice Sense 1.1.1 (Android 4.0.3 ICS, Sense 3.6, 1.5GHz OC)

7. - ?. Are there others that are not on XDA?

Let's collect basic information at first and see which ones are in development.

I will come back soon. Also I will keep this post (original/ first post) up to date with stuff you guys post here.

And I have a question. I don't understand why there are so many different ROMs. Do developers just like to have their own and see what they can achieve? Or do they have differing interests? Sense will of course be one, I guess it can't be just added on top of a working ICS ROM? Wouldn't it be more fun, rewarding and forward thinking for them to all work together?

Thanks for every feedback.
[T-Mobile myTouch 4G Slide] AgentCherryColla:
Most ICS Roms are by one Dev. Tbalden, he just made Roms to do it. All the bugs are outlined in the "Not Working" section. All ROMs based off 2.6 Kernel have simular issues (Wifi Tether, 1080p not working) All Sense 3.6 Roms have the same issues, with minor UI bugs that won't be fixed. Why? Nobodys using them. Most AOSP/CM9/AOKP bugs kernel wise are the same. Then UI wise varys from ROM to ROM. I can tell your new to here, I don't feel this thread should be here Xo All the bugs are outlined. As you can see CM9/AOKP are the most used. On Rootzwiki there's two ICS Roms by Tbalden. Virtuious Inc, and Virtuious Prim. Virt Inc with the 3.0 kernel seems to be the most "stable" out of all ICS Roms as of now.
[T-Mobile myTouch 4G Slide] Unrelashade:
Thanks guys!

AgentCherryCola: I'm not new to the XDA Forums and I also had some looks around the ROM threads of the MT4GS forum. I know they all have lists for their bugs and I appreciate that very much. However, I still think it is useful to have a thread who sums it up and compares the ROMs and their issues. Thanks for your summary!

WeekendsR2short: Happy to see someone likes my idea :) I appreciate your reviews very much. And yes I could just try every ROM and I think I will, at least some of them. But probably only for some minutes, because once I have all my data, apps and stuff set up right, which takes quite some time, I don't want to do it all over again. That's one reason I'm asking for experiences of ROMs and their advantages and disatvantages. But yeah maybe I am overcomplicating things... But it's still fun and useful for newcomers :)

BTW back then on my G1 it was pretty complicated... a lot of ROMs were pretty fast at the beginning and once you installed some apps and used the phone a bit it got really creepily slow... But I suppose I don't have to worry about that with a phone that is about 6 times as fast :D
[T-Mobile myTouch 4G Slide] blackknightavalon:
There are some early ICS ROMs by undeadk9 over on rootzwiki, but he stopped developing for the Doubleshot. For a few months, he was the ONLY dev working on this phone.

Sent from Spaceball One.
[Samsung Galaxy Nexus] funkdified:
The i9250 only allows MTP mode when connected to the PC via USB.

My phone is rooted and I would like the ability to transfer files back and forth. Is there an app to allow this?

Thanks
[Samsung Galaxy Nexus] Wolfbeef123:
What do you mean?

My nexus mounts as an MTP device also. and i can copy files to and fro just fine :confused:
[Samsung Galaxy Nexus] funkdified:
Weird

Ok, you can bin my post. I dunno why I could only browse media folders before I rooted, now I see everything. Thanks
[Samsung Galaxy Nexus] Wolfbeef123:
Not a problem my friend,

trust me, weirder things have happened to me...

thats why i got the repulsion cannons installed on my Gnex :)
[EVO 4G Android Development] v5HMeca:
I've had a few folks message me with requests for guidance on how to add 4G WiMax to CM7-based ports. I figured I would go ahead and write up this quick guide on how to do it for LeWa OS. This should be very similar with other ROMs.

Let's start with the easy part.

- Copy /system/app/CMWimaxSettings.apk.

- Copy /system/framework/wimax-api.jar.

Decompile /system/framework/framework-res.apk

Edit ./res/xml/bools.xml

- change config_wimaxEnabled value to true

Edit ./res/xml/strings.xml

- change config_wimaxServiceJarLocation value to /system/framework/wimax-api.jar

- change config_wimaxManagerClassname value to com.htc.net.wimax.WimaxController

- change config_wimaxServiceClassname value to com.android.server.WimaxService

Edit ./res/xml/arrays.xml

- in networkAttributes element, add <item>wimax,6,6,2</item> (I add it after wifi)

- in radioAttributes element, add <item>6,1</item> (I add it to the top)

- in config_tether_upstream_regexs element, add <item>wimax\\d</item> (I add it to the bottom)

Now somewhere (probably Settings.apk), you'll want to add a link to it.

Example from my LeWa OS port:

<com.android.settings.IconPreferenceScreen android:title="@string/wimax_settings" android:key="wimax_settings" settings:icon="@drawable/ic_settings_wifi">
<intent android:targetPackage="com.android.settings.wimax" android:action="android.intent.action.MAIN" android:targetClass="com.android.settings.wimax.WimaxSettings" />
</com.android.settings.IconPreferenceScreen>

.

That should be it.

PS-

While you're in arrays.xml and looking at config_tether_upstream_regexs, you should also look for something like wlan\\d (if it's there, it's probably the second item) and change it to eth\\d if you see it. This will fix tethering.
[EVO 4G Android Development] ZzHacks:
I appreciate this guide shall use this on my aed ios port
[EVO 4G Android Development] monty_python:
Stupid question, so why are developers not including this did in there work?
[EVO 4G Android Development] v5HMeca:
I'd first like to emphasize that this guide is primarily targeted at developers of "CM7-based ports," i.e., taking a ROM that is based on CM7 from one device and bringing to the Evo 4G.

Now to answer your question: It's because device from which they are taking the ROM does not support WiMax and/or is not an HTC phone.

As an example, the version of LeWa OS that I use is made for a Chinese phone (U8800X) that doesn't have built-in WiMax support (and it is not made by HTC). The ROM should not be expected to support WiMax out of the box and certainly shouldn't be expected to use HTC's WiMax API. The developers that are porting the ROM are then tasked with having to shoehorn WiMax support into the ROM. This is a breeze when the ROM is based on CM7 (not nearly as easy when the ROM is, for example, MIUI) because it's just a matter of changing some settings, as demonstrated in the first post.
[EVO 4G Android Development] monty_python:
Ok, that makes more sense.. thanks for your letting us in on your mod...
[EVO 4G Android Development] kz6fittycent:
So...any ideas about the MIUI roms? I have been trying to get 4g to work forever. Gave up, and now I'm back at it. I'm using the kitchen btw. I tried including all the libs, jars, etc. from c7 and the phone booted normally, but I got nothing as far as wimax. There was no toggle present so I DL'd one from the market. It stated that my phone wasn't 4g capable. Back to the drawing board.

Do you have any ideas why this isn't working? You mentioned that your method wouldn't be as easy with MIUI. Why? I'm only asking because I'm seeking the education. My research has only rendered complaints from those who want it but can't figure it out. BTW, I'm not a fan of CIUI but I understand their reasons for the departure from MIUI altogether.

Thanks in advance!
[EVO 4G Android Development] v5HMeca:
Yeah, the reason none of this will work in MIUI (or any other ROM not based on CM7) is because these are all just configuration settings. The CM7 framework reads the value of config_wimaxServiceJarLocation so that it knows where to find the WiMax API, for example. MIUI framework would simply ignore that value because it's not programmed to interpret it.

I know fergie and the guys got WiMax working on MIUI on some other device(s). Last I checked, they were working on getting it to work with the Evo 4G as well.
[EVO 4G Android Development] the.emilio:
LOL I was gonna do this exactly for the JoyOS port. I saw the differences in Decks framework and the JoyOS framework and was like hmmmmmm. I put it off until I got everything else where I wanted it! Good looking out for those who need it for their ports or future ports!! ;)
[EVO 4G Android Development] kz6fittycent:
So basically I'd need to build a cm7 based miui rom from scratch to make it work...Jeeze.:what:

sent from my o.g.
[EVO 4G Android Development] T10NAZ:
Can I pop the link to WiMax in wireless_settings.xml?
[EVO 4G Android Development] v5HMeca:
I would assume so. That's where I put it in mine.
[EVO 4G Android Development] T10NAZ:
Cool just wanted to double check
[Galaxy S I9000 Q&A, Help & Troubleshooting] endrit9:
Hi i rooted and flashed 4.0.3 TEAMICS 2 days ago. Yesterday i flashed 4.0.4 TEAM NYX its really good and fast but RECORDING with camera is not working. Neither does playing videos I wiped cache, dalvik and factory reseted phone, still does not work. Someone told me to flash stock ROM but i don't know which files it is. I had 2.3.3 gingerbread XXJVO. Thanks for help

Am i supposed to wipe cache / dalvik everytime i flash a rom?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Fabiore81:
Try this:

http://xdaforums.com/attachment.php?attachmentid=976070&d=1333252725 (install fix from recovery)

If fix doesn't work try this method:

- go to recovery

- do all wipe

- format system (from mount and storage)

- re-flash rom
[Android Q&A, Help & Troubleshooting] Akhtar Ali:
hi,i have a HTC Explorer.not rooted.internal memory left is 5 mb now.i use 2g..edge network.i am unable to download apps that are lesser than 1 mb.An error saying "insufficient storage" pops up everytime.Please help.i would be really grateful. thanks :)
[Android Q&A, Help & Troubleshooting] monishvster:
Its bcoz, after installation the application's size expands.

I recomend u to root ur phone as low internal memry sucks. After root u will b free from this tension
[Android Q&A, Help & Troubleshooting] patedit:
You will be free from this tension if you have external memory and you install your applications on that external memory :p
[Android Q&A, Help & Troubleshooting] Avilove.Cullen:
Download App2sd free !

Try to clear cache with this app ;)

RuCk

FulEs!
[Android Q&A, Help & Troubleshooting] Akhtar Ali:
if rooting expands int memory ??

is it possible to expand ur internal memory after rooting.? if yes..by how much?:confused:
[Android Q&A, Help & Troubleshooting] patedit:
No, it does not expand the internal memory. It ables you to install apps in external memory, so internal memory will be less used.
[Android Q&A, Help & Troubleshooting] Avilove.Cullen:
Yeah there is a guide to increase internal memory by swapping memory to sd card :)

Si usted le da sentido a continuación, obtener el respeto .. Mi mente joven que ;)
[Galaxy S III Q&A, (US Carriers)] milleirish:
I rooted using http://xdaforums.com/showthread.php?t=1726960 the version of CWM that is in this method has the CWM that does not show the Ext SD card. I see now there is a new version of CWM that can see the Ext SD card. Can I update this CWM with out having to use Odin and install this version of CWM since I am already at #2 on my flash counter? Thanks for the information.
[Galaxy S III Q&A, (US Carriers)] dLo GSR:
you can just do it through adb.

Sent from my Galaxy S III
[Galaxy S III Q&A, (US Carriers)] milleirish:
I can try that, but I really suck at adb. I can never really get it to work.
[Galaxy S III Q&A, (US Carriers)] blacksheep242:
Where did you find the version of cwm that has sdcard support? Thanks
[Galaxy S III Q&A, (US Carriers)] milleirish:
If you go to Youtube and look up QBking77 he has a updated video. After he installs CWM and goes into it, it shows both SD cards. He is on sprint but the root and CWM he is using says universal for all S3 phones, other then verizon that he knows of.
[Samsung Galaxy Nexus] Doodsz:
Not sure if there is already a thread like this but I just found out something that I found was pretty freaking awesome!

Was listening to some B.o.B :D when I tried clicking the volume buttons on my earphones. ( Monster/Nokia purity) then boom the buttons act as a previous and next. For me the volume down is next and obviously the volume up is the previous :p

And just found out that holding the middle button activates the voice search :D
[Samsung Galaxy Nexus] moeahmad1995:
Do you have any other headphones that u can test with? You're positive that it didn't work on ics? If yes to both, I can't wait to flash jelly and try!
[Samsung Galaxy Nexus] Doodsz:
Yes to both.

But I have to find my other earphones :rolleyes:

If I find it ill get back to you :D
[Samsung Galaxy Nexus] The Jones:
I have headphones with a single button on them. Long pressing opens up voice search, single clicking while listening to music acts as a play/pause actions, double clicking moves to the next track and I hope triple clicking moves to the previous track.
[Samsung Galaxy Nexus] adrynalyne:
My Etymotic buds don't work.

The play/next track button just pauses, and volume buttons do nothing.
[Samsung Galaxy Nexus] thos25:
Triple click does not go to previous track. Single pauses/plays.

Double moves to next track.

Long press brings up Google now.

Haven't been able to figure out previous track yet.
[Samsung Galaxy Nexus] moeahmad1995:
I should get mine in 2 hours. I have Zagg smartbuds that I can try out. Also gonna try the apple headphones and see if those work too.
[Samsung Galaxy Nexus] player911:
I have a pair of Sony Wired with music and volume control. They seemed to work better on GB when using my LG G2x, but the ICS on the Nexus only registered the 1 main button (Previous, Skip, volume up and Volume Down did nothing). On the LG G2x, everything worked great except Volume which I read was a Apple exclusive.

I also have a A2DP BlueAnt Handsfree unit for calls, but has 2 Volume buttons and a main button. I'm curious to see how it handles it when playing music.

I'll give them a shot again tonight to see how JB handles it.
[Samsung Galaxy Nexus] android.vibrant:
confirm that it worked with a samsung earphone! :good:
[Samsung Galaxy Nexus] Wilsonium:
I can confirm my handset didn't burst into flames with an Apple headset and while the vol up/down buttons didn't work, long press on middle opened search and short press pauses/plays. I don't have any music on my GNex to try the next/previous tracks.
[Samsung Galaxy Nexus] moeahmad1995:
Ok good, I didn't want my nexus to explode. Thanks for being the Guinea pig
[Samsung Galaxy Nexus] LanderF:
I have bought the headset control app and noticed that the long press didn't let me control volume anymore :-( any idea how to disable or modify the controls mentioned above?

Thanks!
[Samsung Galaxy Nexus] Doodsz:
Theres jays headset control on the play store
[Samsung Galaxy Nexus] Drewmungus:
You guys have it backwards, my Jellybean rocking Nexus would make the apple headphones burst into flames!
[Samsung Galaxy Nexus] IAmAN00bie:
Unfortunately, JAYS headset control is overidden by Google's control. At least that's what happens to me...
[Samsung Galaxy Nexus] thos25:
Nice. I have several brands, but usually use zaggbuds. Triple click did not work with them.
[Samsung Galaxy Nexus] mpw3000:
Also if you have Apple earbuds you can double click the middle button and it will skip to the next track. This all works in ICS too.
[Samsung Galaxy Nexus] LanderF:
yup same with the app I'm using. Hope the devs can override the override.

a click+long click for google now would be my choice :)
[Samsung Galaxy Nexus] NCguy:
Media button router gave me access back to my third party bluetooth voice dialer on Jellybean. However to access google voice commands now I have to initiative them by touch instead of the center bluetooth button. After they are initiated the google voice commands work as they should on bluetooth.

Only thing left is to get the center BT button to distinguish between a long and short press so it can initiative either my 3rd party voice dialer or google voice commands. There is another app I have in mind to test for that. Here is link for media button router.

https://play.google.com/store/apps/details?id=com.harleensahni.android.mbr
[Samsung Galaxy Nexus] ArmanUV:
No it didn't work for me. Only pause/play and long press for voice worked.

Apple has patents on their implementation of 3 button controls. So any "Made for iPod/iPhone" headphones DON'T work on android. I doubt JB would change that. The only thing Google can do legal-wise is to natively implement double-press and triple-press for the main control button.

3 button headset made specifically for android are supposed to exist (Headset Droid supports them) but I haven't found any yet.

See this screenshot from HeadSet Droid:
[Samsung Galaxy Nexus] crazy_android:
i am using htc headphones which has next and previous buttons with pause and it works very well in my stock rom 4.0.4. i was guessing that htc headphones will work in jelly bean or not.
[Samsung Galaxy Nexus] NCguy:
My sony mw600 BT headset is a three button and it works great.
[Samsung Galaxy Nexus] adrynalyne:
BT is a little different.
[Samsung Galaxy Nexus] NCguy:
Oh sorry, is this thread only about wired 3 button headsets?
[Samsung Galaxy Nexus] adrynalyne:
BT is different because of the protocols used for headset control (AVRCP). Hence, I said it was a little different when referring to BT.

I have seen plenty of multi-button BT headsets work on ICS and GB.

If three button wired buds are working in JB (mine are not for volume or skipping/previous), that is something new.

Try to be less snarky next time, thanks. I meant no ill will, and don't wish for some stupid fight to break out because of some imagined feud in a thread.
[Samsung Galaxy Nexus] NCguy:
If you thought my remark was "snarky" then go back and read it again.
[Samsung Galaxy Nexus] nyijedi:
I thought it was a little snarky. Just sayin'...
[Samsung Galaxy Nexus] cmajpwc:
This works on my stock, unrooted ICS too with my Samsung headphones. I wanted volume control and couldn't find ones that weren't "made for iPod" that had the three buttons so I ordered an SGSIII headset off eBay for 8 bucks. Whether it's officially a Samsung product or not I neither know nor care because they sound just like the old headset I lost that came with the phone, but it was quite a surprise when I was able to change tracks without turning the screen on. Same configuration, too, volume up is previous volume down is next. I wish they acted as actual volume controls so I could get away with not having to use Headset Droid.
[Samsung Galaxy Nexus] NCguy:
This app is supposed to work on wired headsets and I've heard good things about it.

https://play.google.com/store/apps/details?id=com.kober.headset
[Samsung Galaxy Nexus] Cooperstar:
Thanks for the tip. Love the next option.
[Samsung Galaxy Nexus] NCguy:
NP, glad it worked out for you
[Samsung Galaxy Nexus] mrkristiansson:
Anyone found a solution for the long press google now override yet?

I would really like to be able to adjust volume through long press again.
[Samsung Galaxy Nexus] mrkristiansson:
Have anyone found a solution for this yet?
[Samsung Galaxy Nexus] androidHacks:
There may be a hack...

If you want more than one button, you can modify a three button apple remote like so:

Try looking at instructables.com /id /Galaxy-Nexus-and-others-headset-remote-with-medi [I apologize for the spaces breaking the URL, but the xda-developers forum spam filter as rejecting a properly formed URL]

But I am not sure how well this solution works with jelly bean, because the issue with JB is that Google voice search started effing with the zero-ohm microphone click (ie the button you didn't need to solder to get working).

I see mixed reviews here on the single-click issue, and I notice Jays pulled their app from Jelly Bean enabled devices. I jsut ordered a cheap switch to try with my expensive noise cancelling headphones... I may have more to report in a week.
[Samsung Galaxy Nexus] kenkiller:
Arrgghh....damn the Google Now overriding the long press function. Google...why oh why....?
[Samsung Galaxy Nexus] Doodsz:
I know. Sucks huh? :confused:
[Samsung Galaxy Nexus] invisibles:
well i posted this link so people can maybe vote for fix, but nobody is paying attention i guess

http://xdaforums.com/showpost.php?p=32863666&postcount=86

i spoke to Jays developer, and he sad nobody found a solution yet, so we are at google mercy
[Samsung Galaxy Nexus] kenkiller:
For those who are rooted, there's a solution to this. Managed to get it to work after some help from the dev Christoph Kober of Headset Button Controller.

Basically it involves changing the keymapping of the button so that it is recognized as the alternate button of a 3 buttons headset, then using said app to configure that button to accomplish the usual functions. Pros - we get the same old functionality back, long press is user defined. Cons - It's a paid app with a trial available, and you have to remember to replace those specific keymap files every time you update your rom.

First, install this app https://github.com/chrisboyle/keytest/downloads

When you are inside the app and press the headset button it should show scancode 226 recognized as HEADSETHOOK.

then using any file manager that can access root, go to /system/usr/keylayout and edit Generic.kl and sec_jack.kl, on 2 specific lines. Of course, make backups of those 2 files for safety.

Original would be like this

to this

Save the changes and reboot. Run the keytest app and press the button. You should now see scancode 226 recognized as MEDIA_NEXT. Now all that is needed is to use the abovementioned Headset Button Controller app from Store (trial version should work fine for testing) to configure the RIGHT button (in it's settings) for our usage.

I have no affiliation with the dev, and I'll be very happy if anyone can find a free app that can config the right button of a headset. Jay's app specifically doesn't play well with that option. :(
[Samsung Galaxy Nexus] jimmyco2008:
Perhaps someone could integrate this into a ROM?
[Samsung Galaxy Nexus] Doodsz:
Yeah I agree.
[Samsung Galaxy Nexus] ebguilbert:
OMG!!! Thank you very much!!! I really needed this. I was wondering if this could be possible but I got confused with the key codes.

It worked perfect on HTC One X :D

I think this should be on the general android developing thread. I've seen a lot of people with this issue.
[Samsung Galaxy Nexus] kenkiller:
No problem, glad it worked for you. :D

Well, you're welcome to post it there. I'm too lazy to deal with any questions so I'm just throwing it out there. :)
[Samsung Galaxy Nexus] woggy:
On One S with AOKP JB there is no sec_jack.kl file and to copy it there with the key mapping text won't work... :(

Any idea?

EDIT: I've modified the h2w_headset.kl ... and it work's like a charm! Big big thanks to kenkiller!! :)
[Samsung Galaxy Nexus] runwaypimp:
Thanks. This fixed it for me.

Google are Idiots for messing up the headset buttons.
[Samsung Galaxy Nexus] nelty:
I have an Optimus 2x with cm10. There is no "sec_jack.kl"-file in the mentioned folder.

Only editing Generic.kl makes no difference, long pressing the headset button still starts Google Search.

What do I need to do?
[Samsung Galaxy Nexus] gunswick:
a quick light script or app to try to automate this would be great!

also I don't have root access, so is there another way to achieve something similar?