yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] dman3285:
Ugh!
[Samsung Infuse 4G] MaliciousIntent69:
Exactly what I said haha.
[Samsung Infuse 4G] JordanElliott:
Your vibrator broke. Lmao
[Samsung Infuse 4G] MaliciousIntent69:
I was trying my best to refrain from making that joke xD
[Samsung Galaxy Nexus] MohamadKarbi:
Hello,

The main Google ICS launcher as I noticed uses around 30mb of ram. However, GO launcher uses around 65mb. My question is if I used other launcher as default one (in my case GO launcher), will the main one keep working? I.e., will it be around 95mb of ram used?

Or, when I use one launcher as default one, the other will be inactive?
[Samsung Galaxy Nexus] martonikaj:
The amount of RAM the launcher uses is different for each person. For example, my RAM usage by the stock launcher is 47mb, and is usually around that 50mb point. But anyways...

You select one as the default and let it be your launcher. The other one is no longer running. When you reboot your device, GO Launcher would start automatically, and the default launcher would not.
[Galaxy Y GT-S5360 General] Fallen_Knight:
sir,,, can anyone share the link of creating custom rom for sgy? via cwm update or restore..
[Galaxy Y GT-S5360 General] bumslayer:
Go to the Android Development Section and look for the thread of qtu for brewing custom ROMS. Then, you can go from there.
[Galaxy Y GT-S5360 General] PG101:
What he said ^^
[Kindle Fire General] yeutinh:
After restore to original stock 6.2.2 from TWRP, my KF is stucked in Kindle Fire logo. ADB on but always face exec system/bin/sh failed so I already made factory cable and put KF into fastboot successfully.

I tried to install TWRP again successfully but when I tried to upgrade FFF to latest version by running

fastboot -i 0x1949 flash bootloader u-boot.bin

I got the message FAILED, partition does not exist.

To make clear my partition is ok or not, I repeated TWRP installation and let it stay in Install Complete phase to go to recovery with ADB.

I run the command

adb shell
~# parted /dev/block/mmcblk0

And the result is

GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)

next I enter

print

but nothing happen and it seem that print command stuck.

Anyone please kindly advise what I should do next in order to recover my bricked KF ? Thank you very much
[Kindle Fire General] b63:
maybe this helps:

http://xdaforums.com/showpost.php?p=22401099&postcount=2

follow the links also ...

good luck !
[Kindle Fire General] yeutinh:
Thank you for your advice, I tried to follow the link and tried to run

fastboot -i 0x1949 boot bootloader u-boot.bin

I get failed, cannot load bootloader

but if I run

fastboot -i 0x1949 boot u-boot.bin

The result is

C:\kfu\tools>fastboot -i 0x1949 boot u-boot.bin
creating boot image...
creating boot image - 219136 bytes
downloading 'boot.img'... OKAY [ 0.128s]
booting... OKAY [ 0.000s]
finished. total time: 0.128s

And when I tried to run oem format, it stuck.

C:\kfu\tools>fastboot -i 0x1949 oem format
...

I have no experience how long the re-partitioning takes, still wonder whether cancel this command or let it run T_T
[Kindle Fire General] b63:
would try the format command without -i 0x1949

the initialization is'nt needed with u-boot.bin ver.1.2 and the command is'nt designed to work with initialization
[Kindle Fire General] yeutinh:
I tried to run command but failed. <waiting device>
[Kindle Fire General] b63:
you have allready the hot booted fff loaded ?

give -i 0x18d1 a try at the format command

bradys had a simmilar problem:

http://xdaforums.com/showthread.php?t=1369405&page=10

follow the next 2 sites ...

hope this helps
[Kindle Fire General] yeutinh:
I guess not because fastboot -i 0x1949 boot bootloader u-boot.bin did not work and fastboot -i 0x1949 boot u-boot.bin either because after that command finishs, the fastboot oem format return <waiting device>, it means that fff 1.2 is not loaded successfully.

tried but <waiting device>

Thank you for your prompt support.

Not really, the symtoms are similar but in his case, the partition table still able to read but mine couldn't be. And he also has chance to rebuild partition mannually but I do not; I cannot run parted /dev/block/mmcblk0, this command return nothing as i mentioned above. T_T
[Kindle Fire General] b63:
your right about that - have also read it in an other thread - loads but don't reload itself

are you able to issue mklabel, mkpart and the other commands like here:

http://xdaforums.com/showpost.php?p=20880465&postcount=58

maybe give eldarerathis a pm - he's the guru on partitioning:

http://xdaforums.com/member.php?u=2676559
[Kindle Fire General] yeutinh:
Tried but failed, command stuck

Thanks for advice, already PM him.

cat /proc/partitions
major minor #blocks name

179 0 7553024 mmcblk0

All partitions gone T_T
[Kindle Fire General] eldarerathis:
Got your PM. I haven't seen anything quite like this before, so all I can really do is take something of an educated guess here. What it looks like may have happened is that the partition table got corrupted or erased, so parted can't read the partition list (again, just a bit of a guess).

Try doing this and post the output that you see:

Boot into recovery

Use adb shell to connect to your Fire

Run "fdisk -l /dev/block/mmcblk0" (that's a lowercase "L")

If (3) doesn't seem to work, try "fdisk /dev/block/mmcblk0". It should give you a little prompt kind of like parted does. Type "p" and hit enter at the fdisk prompt (then use "q" to quit).

If fdisk gives you something sane then your partition table is okay. If it blows up or throws back an error then it's toast, but you might be able to use fdisk to create a new (blank) partition table and then re-create the correct partition layout. Either way, it should get you some more information about what's actually going on with your disk.
[Kindle Fire General] yeutinh:
Thank you for your support, I appreciate that :)

~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': I/O error
~ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0

it means the filesystem on eMMC was accidentally broken down, correct ? :( But I wonder what make FS down :confused: because I did not do anything that impact to partitions, I think :cool:

and when I run mount, the result is

Already checked whether eMMC dead or alive http://xdaforums.com/showpost.php?p=13895268&postcount=48

~ # cat /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/name
M8G2FA

Returned name of eMMC

~ # cat /proc/kmsg | grep mmc0
cat /proc/kmsg | grep mmc0
<6>[ 2.438171] mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.456115] mmcblk0: mmc0:0001 M8G2FA 7.20 GiB

it means that my chip still alive :D Need your help to clear the messed FS
[Kindle Fire General] eldarerathis:
The I/O error from fdisk is concerning, and kind of makes it sound like the hardware up and died somehow. I was thinking you might be able to use fdisk to create a blank MSDOS partition table, then use parted to switch it to a GPT one (the Fire uses GPT and fdisk doesn't support that), but if it can't even read the disk then that won't work. The fact that FFF's 'fastboot oem format' isn't working also kind of lends to the hardware possibility, but I don't know exactly how it performs the format (you could try PM'ing pokey9000 and see if he'll explain it to you, maybe).

To be honest, I don't think I've seen a lot of recovery options for this sort of thing. The only stuff I can think of are all kind of Linux-geared, and Android is unfortunately lacking in some of the tools that it has available. For instance, one option on a Linux box would be to attempt to zero out the whole disk and then try to re-create everything, but I don't know how you'd handle things like the MBR on Android (or if you even need to). It still may be a possibility, but I have no idea if it would work and your data would all be lost. Worst case you'd end up with a permanently unbootable drive if the MBR/partition table are zeroed out and you can't re-create them, but I guess that's kind of what you have now, in't it? :(
[Kindle Fire General] yeutinh:
I think you are right T_T. Will look for workaround solution if any and after that will return to Amazon T_T
[Kindle Fire General] curiousGeorge:
You might as well try it.

dd if=/dev/zero of=/dev/block/mmcblk0

Immediately flash a complete system image after this (complete with everything from xloader to media).

If this command says can't open '/dev/block/mmcblk0': I/O error, the chip is probably toast. Unless it's some silly partition abstraction layer caused by twrp or something, in which case you can try to flash a cwm image via fastboot...

If even that fails, you can try to pin-mod that flash -- resetting it. But opening your kindle is probably the last thing you'd want to do if you have the chance to return it, heheh...
[Kindle Fire General] yeutinh:
I tried dd command already, it returned I/O error also.

Will consider pin-mod method, but could you pls advise more details hehe. It's better than return it to Amazon :D
[Kindle Fire General] yeutinh:
This afternoon I tried to play with KF again. I put it to recovery and

~ # echo /dev/block/mmcblk0 > /sys/dev/devices/platform/usb_mass_storage/lun0/file
echo /dev/block/mmcblk0 > /sys/dev/devices/platform/usb_mass_storage/lun0/fi
le

And come back to Windows to check whether OS can detect the usb_mass_storage of KF.

And when I open HP USB Format Tool, it can detect the usb_mass_storage of KF as Amazon Kindle Fire 0001 (7376MB). I tried to format it but the error return that write protected device. Anyone can explain me what is the problem of my eMMC ?

And when using with GParted
[Kindle Fire General] kostos:
what about mk2fs command via adb shell?

my mke2fs /dev/block/mmcblk0p11 brings to mk2fs: short write - what it could be?
[Kindle Fire General] chamnv:
Did you fix it yet? If fix, please intro for me. I have problem the same.
[Kindle Fire General] pentiumn:
a similar problem, someone has already solved it?
[T-Mobile Samsung Galaxy S II SGH-T989] avelasqu:
Very frustrating. I bought the Samsung OEM Navigation Vehicle Mount for the T989.

While docked, media (music and videos) play through the car speakers as expected. However, if a call comes in, the Call Audio only comes in through the phones speaker and not the car speakers.

From what I have been reading, it has to be fixed in the kernel somehow or baked in.

Currently, I am running Darkside Digital Warfare v2.4. I have tried all of the other roms including stock ones. I am open to using whatever rom has this fix or can flash the fix via kernel or whatever.

I am just requesting to see if someone has a fix. The purchase of the mount is very frustrating and annoying to use with the Call Audio problem.

Any help or point of direction would be greatly appreciated. You can reply here or PM.

Thanks for the consideration. ;-)
[T-Mobile Samsung Galaxy S II SGH-T989] rmarquez1974:
Have you tried any other kernels? There's faux's kernel, Mr X's stock based kernel...maybe one of those might adjust the issue you're experiencing.

Dfjcisnv
[T-Mobile Samsung Galaxy S II SGH-T989] jasontx:
this is how it works with the desk dock as well, regardless of having external audio checked in dock settings. It worked this way using stock ROM as well I believe so it's a "feature". It would need to be hacked to have it perform otherwise I think.

Oh, and I think this should be in general also? Idk.
[T-Mobile Samsung Galaxy S II SGH-T989] 18.4009:
Saw your post and it gave me a laugh! I was ranting about this very thing yesterday while taking a call in my car. You can barely hear the caller through the built in speaker! why would they do that? If anyone figures this out I also would be very appreciative to see a fix.

18.4009
[Galaxy Y GT-S5360 General] alaminip:
I have flashed my Y. But still showing problem.

When i pressed (Volume Down+ Power+Home) buttons to go to recovery mode then still show this message:

Warning!!

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

A custom OS can cause critical problems in your phone and installed applications.

If you want to download a custom OS, press the volume Up key. Otherwise, press the volume Down key to cancel.

Volume up: Continue

Volume down: Cancel (restart phone)

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

Now i can't root the device. I want to root my device but can't access the recovery area (Volume Down+ Power+Home)

Please any solutions for this problem?
[Galaxy Y GT-S5360 General] vEget7:
try volume up+center key and power botton simultaneously. not volume down..

.. or download quick boot from the market and try to boot into recovery..
[Galaxy Y GT-S5360 General] krishna_nirvana:
check this link http://xdaforums.com/showpost.php?p=23313767&postcount=7 :) :) :)
[Galaxy Y GT-S5360 General] alaminip:
Thanks all of my friendz i got that :)
[HTC Amaze 4G] jmhalder:
Update: 3/7/2012

Video: http://youtu.be/iTtq3xYYKGg

Status: http://bit.ly/z1GMuo

__________________________________________________________________________________

Max Krivonos (Scepterr on XDA) has updated a old "Amaze is now amazing" post of his on Google+.

https://plus.google.com/106544349933037831956/posts/1SMW3eVKk1d

Max is the current maintainer for the Amaze for CM9. He's had a number of small updates yesterday and today alone.

I'm quite optimistic with Max, I'm sure this will be a usable build before long.

Anyone else excited? I have been dying to run a AOSP rom on my phone since release of the device.

*edit: removed inaccuracy about Max being a maintainer for a different device, sorry, I don't honestly know why I thought he was. Added video, and G+ update.
[HTC Amaze 4G] adslee:
God yes, can't wait for an AOSP ROM for this phone
[HTC Amaze 4G] Double0EK:
Yes...but not like a giddy school girl..haha
[HTC Amaze 4G] fuego77:
Woohoo!!! Made my night!!!

*throws amaze in the air!!
[HTC Amaze 4G] craigtut:
I'm definitely giddy like a little school girl! This sounds like great news!
[HTC Amaze 4G] Jms122589:
XD well...this makes me happy i didnt sell my phone today...i may just have a celebratory beer or 3. i freaking miss cyanogen!
[HTC Amaze 4G] mrmako777:
Nice find. This is the best news I've heard recently!
[HTC Amaze 4G] tombeach22:
This makes me feel how I did when I choked out my first hooker! :D
[HTC Amaze 4G] RXDriv3r:
Finally! Having patience and waiting paid off! Went on G+ and saw this vid:

https://www.youtube.com/watch?v=iTtq3xYYKGg
[HTC Amaze 4G] gypsy214:
man this is great, he stopped working on cm7, do you guys think it will actually come?
[HTC Amaze 4G] glacierguy:
Yeah that looks pretty dope!

Why isn't he over here in our forum?
[HTC Amaze 4G] sanchitgrover:
the video stopped my heartbeat for a sec!!

love this guy !!

thanx op for the share .. nice find
[HTC Amaze 4G] knifeproz:
Is that ics!?!?!?
[HTC Amaze 4G] jmhalder:
CM9 is a fork of the android 4.0.3 operating system. So yes, it's ICS, derived from AOSP, with no Sense UI garbage.

http://bit.ly/zAuapn
[HTC Amaze 4G] improperburial:
This is probably the most exciting news I've seen on here in a while. Now the real question is, is CM9 for the amaze coming out before HTC send out their ics update for us? I'd be curious to see what HTC does for us, but if it comes out after CM9, then there's no way I'd even think of trying it out.
[HTC Amaze 4G] tanmack33:
Very Nice... Just came from the Evo3D on Sprint... Looking forward to this.
[HTC Amaze 4G] Spovik:
Thanks for this post. I've been pretty infrequent here lately due to the lack of S-OFF and all of the variations of Sense based ROMs and all the ICS-themed ones. I looked for xboarder's ICS ROM thread a while back but that looks like it was deleted so i thought there was no more progress. Faith has been restored!
[HTC Amaze 4G] adamboyd83:
This is pretty awesome. Cant wait to give it a shot.
[HTC Amaze 4G] knifeproz:
I'm happy. Iloveyou.
[HTC Amaze 4G] jmhalder:
This would be interesting, assuming CM9 is stable, I would definitely use it as a daily, even without a camera/BT/NFC/etc. However, I can imagine that the official release will be running on a 3.x kernel, as where I'm SURE that Max is using a 2.6.x kernel right now.... This all being said, I'm sure having the kernel source to the official release when available will help bring a 3.x kernel to the Amaze.

TL;DR

Assuming it's stable on a 2.6.x kernel, and most things work, I'd stick with CM9 regardless.

If it's (CM9) lacking a ton of hardware features, I could see running the HTC build till CM9 hardware support catches up.

Also, a CM9 alpha WILL be available before HTC releases/leaks anything, that is almost guaranteed.
[HTC Amaze 4G] dung8604:
Most, if not all cm9 builds have not been released because the necessary proprietary drivers and libs need to be released from the manufacturer (in the form of a dump or RUU or official OTA or something). 2.x kernels can be hacked to work with ics, but missing some functionality. This is why most cm9 builds, while mostly functional, are being held back because they are missing several key features (like camera drivers/libs).

It is possible, however, to port an unnofficial leak with most functionality (see pyro-ice, a port to the mytouch4g slide based on the virtuous unity build based on the international sensation leak). My guess is he will release cm9 as soon as there is a leak, or ota or dump. Also assuming the CM team allows him to do so.
[HTC Amaze 4G] rbaruch:
Holy crap this made me feel so much better about my amaze. Been feeling upset as hell I spent $500 for this phone only to have to sell it and recoup some money for the HTC One. Thank god for devs.
[HTC Amaze 4G] eggydrums:
Why did I have the feeling that no one was gonna give us a status on this Rom until it was already done?? Lol I just knew it

Sent from my HTC Amaze 4G using Xparent Green Tapatalk
[HTC Amaze 4G] stratax:
I thought your picture was of a bra then I looked closer hahaha
[HTC Amaze 4G] Braccoz:
sorry to ask a little off topic question but... can you point me to a link saying he is the new mantainer for the mt4gs? i couldn't find any indication (my fault maybe, it's late night here and i'm pretty tired)
[HTC Amaze 4G] brokenwatch:
Finally some progress!!
[HTC Amaze 4G] garveygibbs:
Read the comments pls

https://plus.google.com/photos/106544349933037831956/albums/5666803086660842097/5668444719763591970

read the comments on the side of the pic...he says its cm7
[HTC Amaze 4G] RXDriv3r:
Yea, in THAT pic. Take a look at this one, the one posted by the OP if Im not mistaken and look at the CM version on that one

https://plus.google.com/photos/106544349933037831956/albums/5666803086660842097/5716252117535901298
[HTC Amaze 4G] eggydrums:
Lol their a pair of ray ban wayfarers

Sent from my HTC Amaze 4G using Xparent Green Tapatalk
[HTC Amaze 4G] Double0EK:
So Max K. dropped his Amaze in the toilet. Hopefully its not borked now. Can we send him some positive vibes?
[HTC Amaze 4G] lonz358:
He said it still work but half of the back light is messed up.
[HTC Amaze 4G] :
I did that to my Samsung T-809 (last great Samsung device imo) about 3-4 yrs ago. It got stuck in the trap. I took my wifes phone to work that day. Every time her or my son flushed the toilet for the next hour I was getting a call... Smh. Sad day
[HTC Amaze 4G] eggydrums:
Where can I?

Sent from my HTC Amaze 4G using Xparent Green Tapatalk
[HTC Amaze 4G] Double0EK:
I follow him on G+
[HTC Amaze 4G] kazzxtrismus:
Wet spot for future reference
[HTC Amaze 4G] Accophox:
Max's Amaze is working, but the backlight is fubar. He says he should be able to finish up CM9 development though. Hopefully.
[HTC Amaze 4G] hamza arbeed:
you should check that the wifi is working

see https://plus.google.com/106544349933037831956/posts/4Lpyw9bPBCq

CM9 Amaze 4G Status Update

Updates in BOLD

Working:

2D/3D Acceleration

HW Video decoding(OMX)

Audio

Sensors(Accel, Gyro, Mag)

Internal/External sdcard

Backlight

Radio (WiFi)

Not Working:

Camera

USB cable detection(charge, adb)

Radios (RIL, BT, GPS)
[HTC Amaze 4G] starskyrob:
Github?
[HTC Amaze 4G] Accophox:
Not publicly accessible I'd assume. As long as they don't release a version to the public, I don't believe they need to open up their source code. And honestly, I'd rather they didn't until it's ready. There are already enough bad (re: half-assed) roms out there for our device, and I'd rather that they didn't give anybody something to work with until they themselves are happy with the quality of their product.
[HTC Amaze 4G] jmhalder:
Even once it's released to the public, they don't HAVE to release source. People confuse the GPL and the Apache license often.

Apache: Take and use for free, modify to your hearts content, releasing your modified source is up to you. AOSP falls under this.

GPL: Take and use for free, modify to your hearts content, if released as a binary, you NEED to publish the source code. Linux Kernel falls under this license.

*Worth pointing out that kernel modules aren't necessarily part of the kernel binary, thus the source doesn't need to be provided for a module.

The CM team makes the github available once it's in nightly status, or really whenever they feel like it, but so far, it's pretty common that it's not available till some sort of build is available. If you seriously can help the developer, you should contact him, and if he feels like it, he could provide it to you.
[HTC Amaze 4G] Accophox:
Yeah, forgot that AOSP was licensed under Apache. But, it'd be very much unlike the CM team to withhold source once binaries were available. Regardless, Max has basically said on G+ that he isn't looking for any other help in building support for MSM 8x60 devices.
[HTC Amaze 4G] LS1_01:
Keep up the good work! Can't wait! Will it have WiFi calling for TMobile USA?
[HTC Amaze 4G] Accophox:
Ask him yourself on G+. In all likelihood, it won't though. Not stock, at least.
[HTC Amaze 4G] Mafioso:
Any further updates on this :confused:
[HTC Amaze 4G] jimczyz:
Check him out on G+
[HTC Amaze 4G] Mafioso:
USB cable detection(charge, adb, mtp) is working now...Max updated today :D
[HTC Amaze 4G] the show stopper:
This is the current progress status. everything is working except camera and radios.

"Max Krivonos - Mar 22, 2012 (edited) - Public

CM9 Amaze 4G Status Update

Updates in BOLD

Working:

2D/3D Acceleration

HW Video decoding(OMX)

Audio

Sensors(Accel, Gyro, Mag)

Internal/External sdcard

Backlight

USB cable detection(charge, adb, mtp)

Radio (WiFi(messy hax))

Not Working:

Camera/Camcorder

Radios (RIL, BT, GPS)

Will update as progress is made."
[HTC Amaze 4G] :
I don't see any updates on his g+... Thanks for heads up
[HTC Amaze 4G] EclipzeRemix:
he updated the original thread, since you could edit statuses on G+
[HTC Amaze 4G] :
I'm still new to g+ (only follow 2 devs).
[HTC Amaze 4G] the show stopper:
:D
[HTC Amaze 4G] laggo:
No progress lately makes me a sad panda :(
[HTC Amaze 4G] starskyrob:
No reported progress isn't the same as no progress
[HTC Amaze 4G] :
Its here http://xdaforums.com/showthread.php?t=1599489
[TouchPad Q&A, Help & Troubleshooting] alias4ever:
I am looking for a theme or something similar that will allow me to change my icons on my desktop I guess you could say. :) Can anyone recommend anything or point me in the right direction please? Thanks! :D
[EVO Shift 4G General] MrLinky:
Hey all. I'm currently running SparksCo's v1.1 Stable rom (CM 7.2.0) and everything is great except the lag/stutter I experience when swiping between home screens.

After using ADW for months, I said enough is enough and I am currently using Zeam Launcher, but there still is a slight hesitation/stutter after exiting an app. Miui is buttery smooth 100% of the time and even various Sense roms seem to have consistently smoother transitions than anything i've experienced on vanilla/lightly modified CM roms.

So if anybody has any recommendations, i'm all ears (or rather, eyes). Thanks!
[EVO Shift 4G General] VICODAN:
Launcher Pro