yashsingh1/xdaforums huggingface dataset:
[General Topics] justmpm:
Sorry...I had to close this thread. There is already a thread for discussing computer hardware issues. Please feel free to repost your question Here.

Thanks!
[T-Mobile, Samsung Galaxy SIII] Cruze808:
I can't connect to klink for some reason. When my phone is connected klink sees it but says its offline,usb debugging is checked. Same problem as this but im not familiar with sdk lol. Any help or direction to the right thread I did search official thread and Q and A thanks sorry if its been addressed.
[Asus Transformer TF700] spinaldex:
Whenever i type on my TF700 keyboard dock it only types in what looks like Chinese or Korean to me. This is after I applied CleanRom last night.

Changing the keyboard language in settings doesn't help.

Any ideas?
[Asus Transformer TF700] mrlakadaddy:
I had that, fixed it with a full wipe and install.
[Asus Transformer TF700] sbdags:
I had this once before as well. No ideawhy. Re-install fixed it :good:
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
Hi everyone, this is my first thread :)

I recently rooted my 16gb WiFi only nexus 7. After installing 3 different roms (touchwiz, cyanogenmod 10, and xenon HD) I didn't like touch wiz or cyanogenmod, and I'm currently running xenon HD. However, when I opened my storage today, of said I had 3.6gb remaining. I thought it may have been all the apps, so I factory reset it, reset the partition, and deleted all data via recovery mode. That gave me about 1 more gigabyte. I opened ES file explorer and deleted everything there. I still have only 4.6 gigabytes usable. Anyone else have this issue?

Thanks :)
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
Well, I deleted some old backups and now I have 7.5 gb of storage, which should do for now. But I still have that 6 GB leftover, anyone know whats wrong?

Thanks :)
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
OK. Now I mucked around in the mounting/unmounting stuff, and now it won't boot. It's stuck at the Google screen. Someone help please???
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
You are not the only person who has experienced this.

Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard

Either the "format data" option in TWRP, or using fastboot.

fastboot erase userdata
fastboot format userdata

I've had the latter create short file systems - and also not create short file systems.

Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. :o Ugh - I hope your luck is better than mine.

Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.

Long boring thread, but related.

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

good luck

Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
I basically have nothing I need on my tablet, so I'm fine deleting everything on it, if that's what you mean. I'll try, but thanks:good:
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
Wait, is that for getting back the storage or actually letting it boot up? Because right now the storage is the least of my concerns.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
What I described is for getting back lost space (by recreating from scratch the ext4 filesystem in the userdata partition).

As it doesn't touch either the boot partition or the system partition, your tablet should certainly be able to boot. If you don't do a restore of /data from a backup, the result will be like a factory reset of whatever rom you had on the tablet.

Just make sure to check the size of the data partition before you start re-customizing or restoring data from backups to make sure that you got the full size of the partition.
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
Ughhh its still not turning on...
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Please re-read this quote from your 2nd thread in this fiasco.

If you screwed around with your system partition and it wouldn't boot before, then with a freshly formated and empty /data filesystem, of course it still will not boot. The instructions I provided in this thread only involved the userdata partition!

But you didn't say "I did such and such and it still hangs during the initial boot phase where the X logo is flashing on the screen"; instead you said:

"Ughhh its still not turning on".

WTF? Has your problem now morphed into a dead battery problem, or is the language you are using just incredibly imprecise?

Anyway, Flash a new ROM using the custom recovery. Any ROM - you pick. Maybe not that Xenon ROM or whatever it is called. See if the new ROM boots. And then immediately after it boots, check to see what size the /data partition is.

And if you come back into this thread anymore please be specific about what you are attempting and exactly what symptoms you are observing.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
OK. I tried to install a new rom, but I can't because I have USB debugging off, which I can't turn on
[Nexus 7 Q&A, Help & Troubleshooting] upichie:
Thank you, bftb0!

I was looking around for this after I discovered my lack of space. I read about it before, but couldn't dig up the post. Thanks for informing us! Enjoy the thanks! :)
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
ADB is available in the custom recovery... so long as you have the right drivers installed on your PC. And that is NOT controlled by some setting in the most recent ROM that you flashed - it is always running in the custom recovery.

One of the quirks about ADB in the recovery with the Nexus7 is that it claims a different USB address than "ADB Composite Interface" that the regular OS does. This might mean that ADB works correctly with the regular OS booted, but not when the custom recovery is booted, depending on what drivers you have installed. Yes, you need yet another driver installed even though they are both "ADB" connections. But that is a Windows driver issue, not a problem with the N7.

You can also use an OTG cable and a USB drive with TWRP if that is easier. Put your ROM on the memory stick and then use TWRP's "external memory". To be most compatible, make sure the USB stick is formatted in a FAT format. (I don't know if TWRP can handle NTFS).

I wonder if I can I trade them in for some coupons or something :D
[Nexus 7 Q&A, Help & Troubleshooting] Nico_60:
@bftb0, I was not able to use adb while in TWRP but i found THIS and it was the solution, what do you think about this "fix"?
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
Holy crap I forgot about the OTG cables. Thanks, I'll try it!
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
Thank you so much. That did it.

First problem fixed through XDA developers

Enjoy my thanks :)
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
The ADB daemon - "adbd" is definitely sitting there running inside the custom recovery. Even if you can't communicate with it because of a lack of a driver, you should nevertheless be able to see it as an unknown device in the PC's device manager.

I have done the same hack - hand editing the .INF file - with both the Google SDK drivers and the Asus drivers, and in both cases it worked fine (one driver for everything: ADB in the OS, ADB in TWRP/CWM, and fastboot with the bootloader).

I have also used the Google SDK driver without modification plus the XDA Universal Naked driver. That means using the Google driver for fastboot and ADB when the OS is booted, and the XUN driver for custom recoveries only.

At the present time the ONLY driver I have installed is a hacked version of the Asus drivers.

Win 7 complains about signing when doing this (for the Asus drivers for sure, I can't remember if the Google driver is signed or not).

As I mentioned, Win 7 Pro x64. I suppose the whole "violated signing" might make life even more difficult with Win 8 though.
[Nexus 7 Q&A, Help & Troubleshooting] upichie:
bftb0, did you personally experience the problem of losing space on the internal memory? I tried your advice, but it didn't work. I'm on PAC(man) ROM. I booted into TWRP, did the data wipe (not factory reset, the full wipe that wipes the everything) but I still only have 13 gb available (on my 32 gb Nexus 7). I rebooted into TWRP and did a factory reset AND wipe data, but I am still missing half of my internal memory.

Do you need to do this on the stock ROM for it to work? Any other tips would be greatly appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Yes, it really did happen to me.

After it happened I took the trouble to download 4 different versions of TWRP (2.4.1.0-2.4.4.0), and I re-created the ext4 filesystem with:

- each of the different versions of TWRP and

- fastboot format userdata

after each, I did a "e2fsck -f -n <block-device>" on the (unmounted) userdata partition to see that they were clean, and I also dumped the output of "tune2fs -l <block-device>" to a file for comparison. Other than things that I would expect to be different (e.g. partition UUID identifier strings and timestamps), I noticed no differences. And also, I couldn't reproduce the problem for the life of me.

:(

Above you mention full "data wipe". In TWRP (v2.4.1.0), this is presented as a separate button in the "Wipe" sub-menu where it (the last button in the first column) is labeled "Format Data". I suppose this is what you mean, but thought I would be explicit to avoid any confusion. (The "factory reset" procedure in the two custom recoveries - both CWM and TWRP - can not possibly re-create the ext4 filesystem in /data, as the /data/media/0 SD card files are in there. But the "Format Data" button does destroy & recreate the whole filesystem).

If you press on this button and at the same time capture the output of the "ps" command, you will see that TWRP recovery invokes the /sbin/make_ext4fs in the following way

make_ext4fs -l -32768 /dev/block/mmcblk0p<PARTNUM>

(CWM probably uses a different external command as it does not seem to have a "make_ext4fs" command in it's ramdisk. Probably mke2fs with ext4 options on the command line)

Anyways, I can't say I have my finger on exactly how to resolve the problem as I can not re-created it. But it did happen to me.

One thing you can try rather than using TWRP's "make_ext4fs" command (underneath that button "Format Data") is to reboot into the bootloader from TWRP, and do the file system formatting in fastboot instead of TWRP, as in:

fastboot format userdata

(noobs: caution, this is a full userdata wipe)

and then bop back into the recovery and check things with "tune2fs" report

tune2fs -l /dev/block/mmcblk0p<PARTNUM>

My 32G N7 shows a total block count of 7503608 (x 4k/block = 29.3 GiB) doing this.

As I mentioned before, it's a good idea to check to see you have the right size before you start restoring stuff to avoid wasting time. You can do it above with "tune2fs -l", or because TWRP seems to want to mount /data and /sdcard when it boots, just run

adb shell df -k /data

to get a report of total and used size.

Sorry this isn't more definiitve. I would have spent more time looking at this, but it is tedious as you need to unload the whole d*mn SD card in order to experiment. Thank goodness my 30GB partition only has about 10Gigs of stuff on it.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] upichie:
.

I'm a total command prompt beginner here, so could you explain where I'm doing the fastboot format command? In a terminal on the device? Using adb on my windows machine? I tried all that I could think of, but none of it worked. No form of wiping the device (yes, via "format data" in TWRP) seems to work. I'm still missing half of my storage.

EDIT: Okay, so I ran the command--I had to have the device in the bootloader, duh. Unfortunately, it still did not work. When recreating the file system, it said there was a total of ~3.5 million blocks--half what I saw reported in the other thread. Not surprising, since I'm missing half of my storage. How come this is working for other people but not me? I tried doing both at the same time, but to no avail. This is getting stupid.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Arrgh. Did you do the "fastboot erase userdata" first?

Here's what the fastboot format looked like on my device when I did this last (3/13):

$ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.974s]
finished. total time: 4.979s

$ fastboot format userdata
erasing 'userdata'...
OKAY [ 4.454s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 30734811136
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7503616
Block groups: 229
Reserved block group size: 1024
Created filesystem with 11/1875968 inodes and 161774/7503616 blocks
sending 'userdata' (139197 KB)...
writing 'userdata'...
OKAY [ 33.733s]
finished. total time: 38.194s

As I said, I was unable to reproduce the problem even though I tried. But it almost seems like the creation of the new filesystem is inferring something from somewhere (but where?) about the userdata partition size which is incorrect. Almost like it happens because of something it sees in the prior filesystem (which is being destroyed). So it becomes irreproducible unless you can recreate the same starting condition.

There's other mysterious crap going on here too. See the output above? The part where it says "sending 'userdata' (139197 KB)" ? It will say this no matter where you run the command from, and there is no 139 MB "userdata.img" file in the folder it runs from!!! 139 MB? For a filesystem which is empty when you mount it?

I don't know. Here's one more thing to try, though. In addition to doing the "erase" & "format" commands, perhaps you could actually flash the userdata image from the stock ROM

fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img

and then when you boot to the custom recovery, perform a "factory reset" - or try doing the "Format Data" thing in TWRP after (or before?) the above steps.

If none of this works, I suppose you could try the equivalent sorts of things with CWM and see if you get a different result.

You don't need to permanently install CWM with a hard flash - you can just soft-boot it for a single session:

fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img

Sorry this is so vague, but you know how it goes - you stumble into a problem, start fooling around until it gets fixed - and because you weren't really expecting the problem in the first place, you haven't written down the exact conditions and steps. Like I said, I tried to re-create the problem a variety of ways - but failed at that effort.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] upichie:
Well, found my problem after I saw my internal memory cut in half again, thinking it was at a quarter now. I pulled out the box, checked the model number, and sure enough it says "1B16" for 16 gb. The salesman sold me a 16 gb for the price of a 32 gb. What a nice guy!

Oh well, my problem is solved. And luckily I learned how to use ADB in the process! Thanks for all your help, btfb0! Much appreciated!
[Nexus 7 Q&A, Help & Troubleshooting] nicetaco:
http://www.youtube.com/watch?v=sdcrmqeVUoE

This guy had that problem too. I'm sure if you complain to them they'll give you a 32 gb version. If you bought it at staples, their customer service is really good.
[AT&T Samsung Galaxy Note II] Ashialeigh:
Galaxy note 2 does anyone know if there is a miui rom for it
[Samsung Galaxy Nexus] MBQ_:
Hello all!

My name is Kyler, aka MBQsniper.. and I present to you..

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

| Project-M |

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

Features:

-All CyanogenMod features based off the latest build

-Linaro optimized

-Built from source

-Cherry picks from other ROMs

-Some custom theming

-Customized text

-Tons of string edits

-More

∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵

Info:

Based off of CyanogenMod

∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵

Changelog:

Beta 1.1:

-Based off of Beta 1 (for now)
-Added in some audio tweaks
-Added in Bravia
-New bootanimation
-Added in Galaxy S3 sounds
-Added in extra media (thanks Vicino)
-Replaced Launcher2 with Apex
-Added in ES File Explorer and removed CMFileManager
-Added in an HD Youtube app
-Added in GooManager (foreshadowing)
-Added in a neat app called 'Flipboard'
-Fix permissions on boot

∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵

Releases:

Device:

Toro

Version: Beta 1.1

Download link: http://d-h.st/B5V

MD5: 72b9176fb9cbc5d7647f515e2c7e134f

ROM size: 200.41MB

∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵

Google apps: http://goo.im/gapps/gapps-jb-20130301-signed.zip

MBQs Modified GApps package:

Inverted: http://d-h.st/tZv (v4)

Non-inverted: http://d-h.st/u5j (v4)

∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵

Thanks to:

The CyanogenMod team

Google

Anarkia1976

Dreamsforgotten

something15525

IT_blackbelt

UBER

Mazda

SavocaFTW

The Crossbones team

DaxMax

The Xylon team

And anyone else who has helped me

(If I missed someone, please let me know)

∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵∴ ∵

Disclaimer: I am not responsible for anything that may go wrong when flashing, or using this ROM.

Feel free to chat in this thread, just avoid getting yourselves in trouble. Enjoy! :)

I kindly ask that you rate this thread 5 stars,​
[Samsung Galaxy Nexus] teddyearp:
Screenshots please? And stupid question but is this a 4.2.2 ROM?

Thx.
[Samsung Galaxy Nexus] MBQ_:
Yes its 4.2.2

screenshots: http://xdaforums.com/showpost.php?p=39509062&postcount=308
[Samsung Galaxy Nexus] Testingchip:
Re: [ROM] Project-M [3/24/13] [Beta 1]

Downloading now. Almost hate to mess with my xylon I have but can't resist. I've been on your xylon so long I've almost lost the urge to flash new ****. :)
[Samsung Galaxy Nexus] nitsua98:
Re: [ROM] Project-M [3/24/13] [Beta 1]

Wtfff is up with all those dots in the op they're making me eyes hurt
[Samsung Galaxy Nexus] hexto:
Re: [ROM] Project-M [3/24/13] [Beta 1]

I've been slacking on flashing lately and I hate the mms on my current ROM. I have a newborn so mms is a must these days. Can anyone confirm sending and receiving mms is working well please?
[Samsung Galaxy Nexus] Testingchip:
Re: [ROM] Project-M [3/24/13] [Beta 1]

Can't swear receiving works but sent successful. I really don't think you will have any MMS issues. Give it a go.
[Samsung Galaxy Nexus] hexto:
Re: [ROM] Project-M [3/24/13] [Beta 1]

Thanks. Downloading now.
[Samsung Galaxy Nexus] qendadar:
Re: [ROM] Project-M [3/24/13] [Beta 1]

Wooohoooo downloading now!
[Samsung Galaxy Nexus] Testingchip:
Re: [ROM] Project-M [3/24/13] [Beta 1]

No issues so far. Doesn't feel much like a beta.
[Samsung Galaxy Nexus] Alpha_wolf:
the s3 sounds to feel like they fit in on this
[Samsung Galaxy Nexus] MBQ_:
Yep. Trying something a little different. :good:
[Samsung Galaxy Nexus] Alpha_wolf:
sry mis typed im doing like 20 things the dont feel like they fit.. im all for new things but idk its a stock rom with touchwiz sounds lol idk i flashed the stock sounds.
[Samsung Galaxy Nexus] hexto:
So far it doesn't fell life a beta after 12hrs since flashing. Very fast and stable and I used it lots today. Only things I've found not to work are Opera and Dropbox which don't work even after the new update. I even deleted the data for both and fixed permissions. Ended up uninstalling both via Titanium.

Still a daily driver in my book. Bluetooth and MMS are both deal breakers for me and both work great.

PS

Any chance of including the fast torch feature? Saw it on another ROM and it allows the flashlight took be enabled by holding the power button from screen off status
[Samsung Galaxy Nexus] scotty1825:
I wiped, flashed the ROM and your inverted gapps. After setup I keep getting the message" invalid int: project m beta 1.1". Did I do something wrong?
[Samsung Galaxy Nexus] Alpha_wolf:
i get that to
[Samsung Galaxy Nexus] MBQ_:
Common error. Don't worry about it. :good:
[Samsung Galaxy Nexus] MBQ_:
Sure thing
[Samsung Galaxy Nexus] Alton (Halo 2):
Im going to try this one out :) I'll let you know what I think
[Samsung Galaxy Nexus] Alton (Halo 2):
Wow... Its a shame... Its a shame that I haven't downloaded this earlier ! Thanks for this ROM found my dd. :)

---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------

Hey MBQ... How can I see my ram in task killer? If its not in the ROM can u add it in the next update? That would basically make this ROM for me , thanks again
[Samsung Galaxy Nexus] MBQ_:
Ill see what I can do :D
[Samsung Galaxy Nexus] Alton (Halo 2):
I keep getting a message on my screen saying invalid int. Project-M 11. Wat is this ?
[Samsung Galaxy Nexus] MBQ_:
Not sure. It has been mentioned alot recently, and will be fixed next update
[HTC Sensation] majdi313:
Hey guys

I have a HTC Sensation XE and it has ICS 4.0.3. I want Android Revolution HD on it, so I really wanna downgrade it to 2.3.4 or 2.3.5. Can someone please tell me what to do ?
[HTC Sensation] Shree.bhagwat:
For ARHD roms you do not need to downgrade your phone

Unlock your bootloader from htcdev.com

Flash a recovery , install su.zip

N your done you can install ARHD

Hit thanks button if you find me helpful

sent from amazing HTC sensation using xda premium
[HTC Sensation] majdi313:
It's the stock rom. Bootloader is unlocked and can I get a link for ARHD?
[HTC Sensation] ridder215215:
http://lmgtfy.com/?q=htc+sensation+arhd
[HTC Sensation] Shree.bhagwat:
:D
[HTC Sensation] malybru:
Hi,

If you want to downgrade your firmware,you need to be s-off.

Look HERE

Downgrade using 1.17 firmware.

Then,you can install GB ROM.

Look HERE for ARHD GB ROM

ARHD does do an ICS version of the ROM as well.

:)
[MDA, XDA, 1010 General] McNugget:
Hi there,

I got my own XDA yesterday and everything just worked fine,

During night I disabled the radiopart 'cause I dont want any singls in ma' head while I sleep :D

Next morning, the system seems to be angry, I tried to re-enable the radio. Nothing happens.

Again... nothing.

Well after two hours of working and testing with differens SIM-cards the radio starts to work. I was not able to understand why all this ever happens!!

Any ideas?

McNugget
[MDA, XDA, 1010 General] cruisin-thru:
How are you disabling the radio, you need only to tap on the antenna pic at top right of screen, then "turn off phone".
[MDA, XDA, 1010 General] McNugget:
I did exactly that! And to reactivate I did the same...

Well I'll not deactivate the phone for some time :D

McNugget