yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Themes and Apps] derekwilkinson:
Peep doesn't work anymore anyway.... Twitter changed their security settings. Yeah I know it's stupid.

What are you looking for in the app? I find the official Twitter app works quite well.
[Hero CDMA Themes and Apps] SirRipo:
Full time line view similar to Peep and update from the widget. I'm using Twicca at the moment, but I wish the widget was not just a shortcut bar.

Sprint said no Froyo for Hero, I said eff that.
[Hero CDMA Themes and Apps] SirRipo:
Or at the very least an expanded timeline view, more than the single tweet that the official app

Sprint said no Froyo for Hero, I said eff that.
[Droid Incredible Q&A, Help & Troubleshooting] jdmba:
On 2.1, using the Trackball to wake (instead of the overused and more delicate power button) was worked out by taking qwerty.kl, and changing the trackball_center (or whatever) to WAKE instead of WAKE_DROPPED.

I tried this on 2.2, and it does NOT work. I also believe that people who were hacking around found that whatever else they did, stopped it from working in ClockWorkRecovery, which is a bad thing.

Anyone have success in getting Trackball to Wake on Froyo without disabling the trackball in recovery?

Thanks!
[myTouch 3G, Magic General] Shadowafs8:
Hey guys, I have an American G1 that has CM 5.0.7 using the script method (found here: http://xdaforums.com/showthread.php?t=717874) after installing CM 5.0.7 I'm getting all sound going through where the top speaker, where all voice calls come through. If I try to play music, I have to make it like I'm talking to somebody on the phone to hear the music. For some weird reason, no sound is playing through the main speaker. Whether I try to play music from the media player, through a radio program, or just put it to speaker phone, it still goes to the top where the notification lights go. Any explanation why this is happening and how to fix this?
[myTouch 3G, Magic General] smokestack76:
First off why you posting here? I would try that thread first. Other than that could be alot of things
[myTouch 3G, Magic General] Shadowafs8:
I posted it here because I don't think it's a problem with the script, unless somebody else thinks otherwise I'm not really sure...what could the problems be?
[myTouch 3G, Magic General] DonJuan692006:
He's saying why are you posting an issue with your G1 in the mytouch 3G forum.
[myTouch 3G, Magic General] Shadowafs8:
Yeah sorry my bad...I have a myTouch but this problem is regarding to my cousin's G1. I accidently mixed those two up lol, sorry.
[Android Software/Hacking General [Developers Only]] gomeazy:
Can someone please help me with finding the factory rom for mytouch g3 slide? My phone messed up after the update that was supposed to help my phone.
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeeJS:
First, some background:

I've had the S for 2 months now and about a month ago I applied JG5/Modaco r2 and Mimocam lag fix. All was well, 1800+ benchmark figures and no lag at all. That was until a few days ago....

As I was reading on the device, a number of errors started to pop up, force closes, etc. It stopped responding completely so I took the battery out and rebooted. Straight away I was hit with multiple force close and 'process stopped unexpectedly' messages. Basically, it was an unusable brick.

When I took the SD card out the errors were different so, figuring it was related to the Mimocam fix, I decided to undo it. I removed the symlink to the sd card and copied everything to the local data directory.

That didn't work, so I did a hard reset. Which also didn't work. Worse than that, I now can't get the phone to connect in any way to the PC so can't reflash and I can't access any settings on the phone because the error messages keep appearing and obscuring the screen.

Last thing I tried was repartitioning the SD card to see if the ext3 partition was corrupt and that hasn't helped either.

Which is where I am now. What I really want to do is wipe the internal SD and effect a total factory reset but I can't think of any way to do it. I can't access the phone through adb (device not found), Kies (keeps trying to connect but never does) and I can't do it through the phone. I also can't send it back because it has 'flashed rom' written all over it, especially when a root request pops up in the background.

I'm all out of ideas, short of trying to degauss it somehow.

Help! Please!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kilack:
You cant get it into download mode ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] adirtymonkey:
Or recovery mode: format sd card, clear cache etc ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] sturmeh:
Turn the phone off, hold Home + Vol -, then press Power.

I don't see how you can get error messages there...
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeeJS:
Doesn't work, I can't get it in to recovery mode. Neither vol up or down work using the 3 button hold. I've tried repeatedly and it just boots as normal, although the animation doesn't display while it boots but it does play the audio.
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeeJS:
So I take it I'm f***ed then?
[Galaxy S I9000 Q&A, Help & Troubleshooting] iqbalbaskara:
bumping this up and subscribing. I hope you find a solution soon, man.
[Galaxy S I9000 Q&A, Help & Troubleshooting] trancelated:
if you know what your firmware was, get it from samsung-firmwares, get odin, and flash your phone. maybe that will solve your problem.

Keep in mind that I wont be responsible if your phone gets bricked if you mess up the procedure (however the chances of it being bricked is very less if you follow the instructions properly).

search the forum for flashing via odin.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kilack:
He said he cant get it into download mode so would be quite hard to flash with odin then...
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeeJS:
No, I've tried over and over and d/l mode doesn't work. The phone just reboots.
[Galaxy S I9000 Q&A, Help & Troubleshooting] hardcore:
Try the Vol + Recovery mode. The timing is a bit tricky.

On my phone, if I keep Vol+, Home and Power button held down, the phone goes into a reboot loop (it keeps showing the logo, blank, logo, blank). After the logo appears the 2nd time, wait 1 second then release the Power button. Then it goes into the Recovery mode.

If you can't get it to work, try it without the USB/power plugged in as well.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ickyboo:
Tried settings/sd card and phone storage/unmount internal sd/format? Or u could do settings/security/factory reset
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeeJS:
I can't really try that because, as I said, I can't get past any of the error messages that pop up on the phone.

Have had to bite the bullet and take it in to T-mo for a repair and hope they don't notice :(

Will find out in 28 days.
[Galaxy S I9000 Q&A, Help & Troubleshooting] solipsism:
I had a similar problem with JPC. After a while both the internal and external sd cards crapped out. After pulling the external sd and many tries I was able to boot into recovery mode where it says something like E: cant mount etc.

After pulling the ext sd card I was able to get into download mode and downgrade to JM7 with odin. After formatting with odin. It took two tries.

I still don't have access or storage on both the int and ext sd. I have roughly 2gb storage on the internal non-sd memory of the phone (i am not sure what it is but its enough to run android and I can make calls).

I can't install apps use the camera or anything that uses either of the sd cards for storage.

I did try a new sd card that was installed on the phone when it was stock FW but it doesnt work either.

I have a thread posted about it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
am wondering, did your phone ever work with the three button mode to enter download/recovery ? or did you always flash using "adb reboot recovery" ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] mkurzum:
Did you ever find a solution to this problem?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Electroz:
It is posted in several threads in all of the 19000 forums that there is no fix for this. Your only option is to send it in for repair.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
it would be nice if there was a way.

I agree with Electroz.

there is a new software out by Samsung

new PC Studio, it comes with a feature to "Emergency Restore"

you can try that, and see if that does anything to the internal SD

links are on the SGS wiki, click my link
[Galaxy S I9000 Q&A, Help & Troubleshooting] mkurzum:
I'll give it a shot, downloading now.

I'm not sure where to send my phone in, I called samsung, they sent me to bell, but I bought my phone from best buy and I'm with fido...
[Galaxy S I9000 Q&A, Help & Troubleshooting] mkurzum:
It sees both drives, but that's about it, when I try to click on them it just says "insert the disk into drive ..."

There has to be a way to format the internal card with a third party application. I'm gonna keep looking.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Electroz:
I spent 2 days looking for a way to do it, as have many other people on these forums. Good luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Ash88:
I am in the same situation...Bell phone on Rogers network, no internal or external SD Card access (won't mount) all of a sudden. I am able to get into recovery and download mode and have flashed several (SEVERAL) times now trying to fix it...nothing has worked yet.

I'm open to any ideas as calling Bell to repair is low on my list of things I want to do as I'm sure I'll hear about not having a bell account.

Thanks all
[EVO 4G Q&A, Help & Troubleshooting] tw1n2nak3s:
i noticed that whenever i unlocked the screen to one of the home screens there is a very noticeable flicker, like an entire page refresh or something. there's no flickering when i unlock to an app or settings menu etc., only to one of the 7 home screens. is anyone else with this otherwise awesome rom having/seeing this issue?
[Vibrant Q&A, Help & Troubleshooting] MonteCristo22:
I'm a pilot and I use flight mode a lot. I've noticed that when in Flight Mode on the lock screen, in the upper right hand corner under the status bar it says. . . "Searching".

My question (s): Is the phone indeed still searching for a signal? If not what is it searching for? Or is this just a software glitch?
[Vibrant Q&A, Help & Troubleshooting] Monsi:
Its a software glitch, The last month i traveled and the phone does the same yo me
[Vibrant Q&A, Help & Troubleshooting] nguyenmd:
Anyone knows how to re-installed GOGO app on the vibrant. My phone is rooted and lagfix installed. But now when I open GOGO it open up the web and gives me an error message "... invalid device ". other than this, the phone works flawless. However, I travel occasionally, I like to have this feature works. Thanks.
[EVO 4G Q&A, Help & Troubleshooting] guitarjockey:
I donated and got fresh 3.2 rom. I noticed in all the screen shots it should have the default android lockscreen but mine has the sense lockscreen. Am I missing something or is there something I need to change?
[EVO 4G Q&A, Help & Troubleshooting] dglowe343:
Sounds like you may have to enable Launcher Pro.
[EVO 4G Q&A, Help & Troubleshooting] koricua74:
It's a tweak in the Fresh Updater go here http://geekfor.me/faq/how-to-use-fresh-updater/ to set up; I recommend the Vanilla + Clock - World Clock and if you don't want or need HTC Music then use the Vanilla Lock + Vanilla Apps - World Clock. Good Luck!!!!!
[EVO 4G Q&A, Help & Troubleshooting] dglowe343:
Oh yeah. I forgot. duh :p
[EVO 4G Q&A, Help & Troubleshooting] guitarjockey:
Yup that was exactly what I needed to do. Thanks for the help.
[EVO 4G Q&A, Help & Troubleshooting] sdsoundguy:
You need to use the fresh updater need to enable the Vanilla Lock under Tweaks it will require a restart when you are back up you have the Vanilla Unlock screen.
[EVO 4G Q&A, Help & Troubleshooting] chaser33:
i loaded 3.2 and got the fresh updater working right but it doesn't bring up any themes in the tweaks section. only lists one patch. any idea's???
[EVO 4G Q&A, Help & Troubleshooting] smallheadz:
tap the tweaks tab, then tap the anchor says fresh updater fix read changelog! then you should see all the themes tap one and follow directions
[EVO 4G Q&A, Help & Troubleshooting] chaser33:
saweet!! thanks man!
[EVO 4G Q&A, Help & Troubleshooting] fmedina2:
Just did this and now my phone is stuck at an android screen with an exclamation. I have no idea how to do this I didnt root my own phone... :confused: How do I get out of this. Battery pull got rid of it. Is there a simpler way to install this lock screen, or maybe an idiot proof DIY?
[EVO 4G Q&A, Help & Troubleshooting] _MetalHead_:
I just use adb to do it, it takes 30 seconds. This just renames the Sense lockscreen .apk so the system can't find it, making the Vanilla lockscreen the default.

adb remount
adb shell
mv /system/app/HtcLockScreen.apk /system/app/HtcLockScreen.old
reboot

To get the Sense lockscreen back:

adb remount
adb shell
mv /system/app/HtcLockScreen.old /system/app/HtcLockScreen.apk
reboot
[EVO 4G Q&A, Help & Troubleshooting] fmedina2:
How exactly do I do that? Like I said I did not root my phone so I dont know how to do any of these things. Sorry. :o
[EVO 4G Q&A, Help & Troubleshooting] _MetalHead_:
You need the Android SDK. In the SDK there is a folder called Tools- just open a command prompt from that folder and copypaste those commands. It's very easy.

Assuming you don't have the SDK, you can download it here.

You need to make sure USB debugging is enabled to do this.

menu > settings > applications > development > check the box next to USB debugging.
[Galaxy S I9000 Android Development] japperrrr:
http://xdaforums.com/showpost.php?p=7975002&postcount=4

A few days ago I flashed to JPC, but in my opinion it has way to much bugs so I flashed to JM7. I followed the guide to recover the orginal product code and, for as far as I know, it worked succesfully. But... After that I installed some applications and flashed the the voodoo lagfix to my device. I also tried to flash the OC-kernel but that didn't work, probably because the voodoo lagfix uses zImage too, so my phone didn't boot anymore. I went to download mode and flashed JM7 again. After that I flashed the voodoo lagfix to my phone and then I wiped the data and cache using the recovery mode. When I booted up my phone, the apps I installed earlier(eBuddy, Root Explorer) were still installed on the phone. I thaught it would be no problem, but when I tried to install some other applications from the market they didn't download. Then I tried to connect my phone to my computer to check the product code in Kies, but my computer didn't recognize my device, neither did Kies. I flashed to JM6, hoping that would fix the problem, but after following the same steps as I did after I flashing to JM7(applying voodoo,wiping data) and booted my phone, the applications were still installed and my phone was still not recognized by my computer! So now I can't connect my phone to my computer and I can't wipe the data and cache, although it seems to work when I'm in recovery mode. Can somebody please help me? I really don't know what to do now..

Thanks in advance,

Jasper
[Galaxy S I9000 Android Development] trenje:
Do a factory reset in Settings > Privacy.
[Galaxy S I9000 Android Development] japperrrr:
Doing right now, I'll post the results in a moment.

[Update]

The applications have been removed, but my computer does still not recognize my phone. Any advice?

[Update]

Flashing to JM7 at the moment, maybe it'll work now.

[Update]

I can connect my phone to my computer now. Thanks :)
[Galaxy S I9000 Android Development] japperrrr:
Bump!

I just updated my post saying everything was working fine, but right after I flashed the Voodoo lagfix to my device the same problems occured again. Almost 100% sure Voodoo is causing them! Anyone else experiencing these symptoms?

Now I'm 100% sure. I connected my phone to my computer, turned my phone of and rebooted into download mode, flashed Voodoo onto it, rebooted and tried to connect again. Didn't work :(
[Galaxy S I9000 Android Development] eltommi:
you should join #project-voodoo on freenode ( IRC even on webchat.freenode.net )

as the developer says:

<curio_> forum is really innefficient for beta debugging kind of stuff
[Galaxy S I9000 Android Development] supercurio:
Ok, let's be clear.

Voodoo lagfix can't do harm to your phone.

Beta 1 meant to be a private beta, beta 2 will deal better with some stupid scenarios when you flash something and then something else etc.. :D

Voodoo causing problems connecting to computer and wiping data < WTF is this topic title :rolleyes:

I removed beta1 from the download site.
[Galaxy S I9000 Android Development] OrionTC:
very misleading title :(, im sure you could have picked some nicer words for it considering supercurio hasnt released anything yet and you used a private beta file which is private for a reason, its still being tested.
[Galaxy S I9000 Android Development] Zilch25:
I do have to say that I've had some issues with my computer connecting via USB. It only works through Kies- ADB gives me a device not found whenever I try to use it (Yes Kies is closed =P and it's in debug mode). I also have been unable to mount drives for mass transfer.

I had chalked this all up to running a Captivate with a I9000 kernel though- and it still might be, just figured I'd chime in since it sounds like someone has a similar problem- but what can you expect? It's beta 1 :D Just something to look out for curio in case it ISN'T just because of my unholy amalgamation of firmware pieces :)

No wiping of my data though =P
[Galaxy S I9000 Android Development] NeoXTC:
hmmm works fine here.

Although b4 doing all these I did do a full format of internal storage and factory reset. I did the hard reset through the service mode codes as well.

Everything's working smoothly and I do have the voodoo fix as well
[Galaxy S I9000 Android Development] carlocb:
Voodoo is in private beta!! You should not mention it on the forum I think, especially when discussing issues...someone should remove this thread asap! Issues with it should be discussed on irc only as per developer request (and better feedback also)! ...you should also apologize to supercurio who is working very hard for us all...
[Galaxy S I9000 Android Development] dckiwi:
Forum Fail.
[Galaxy S I9000 Android Development] jdrake001:
could you clarify the intention of your thread? this is a private beta, by downloading and installing it you are implicitly agreeing to be a tester, and report issues on the irc. This would cause unnecessary noise. mod should remove this thread.
[Galaxy S I9000 Android Development] g00ndu:
Well, if it cause you problem, then don't install. This is BETA release!!! It is absolutely ludricrous to give such a sweeping statement that xxx cause this or yyy cause that. There is a reason the dev has not released it here.

Just because it worked for others, and you can't get what you want, and just start ranting. This won't do, OP! Go figure....
[Galaxy S I9000 Android Development] distortedloop:
100% agree with others that this topic is totally out of line. It's a private BETA - report the issues to the dev in the appropriate place.

I have had issues connecting my SGS to my Mac via USB since day one out of the box. The drivers on the phone are flakey, in my opinion.
[Galaxy S I9000 Android Development] Zilch25:
Yeah that's also true, though it never manifested before this point. I never bothered to report this to supercurio because I'm not even using the hardware that's compatible with the kernel in the first place :) It's working fantastically anyway, I just figured I'd throw my 2 cents into the hat that it's worth keeping an eye out for just in case it *isn't* related to my cross pollination of firmwares.

Keep up the fantastic work supercurio :) I've nothing but good things to say about the project and the performance on my phone!

OP: You might want to change the thread title to something a little less scary =P It kind of paints the project in a negative light, and most people won't read through the thread to see what's really going on.
[Galaxy S I9000 Android Development] Bhonka:
delete thread.
[Galaxy S I9000 Android Development] japperrrr:
The people who are blaming me for starting a topic to report a bug in the Voodoo lagfix should read my startpost. I was experiencing problems with recovery mode and connecting my phone to my computer, and could not find another topic about it. That's why I started this topic, not to report bugs in Voodoo. After I found out Voodoo was causing it, I changed the topic title to possibly warn other people who're using of planning to use it.
[Galaxy S I9000 Android Development] g00ndu:
Wow, you sounded so noble. :rolleyes: :speechless:
[Galaxy S I9000 Android Development] xan:
trash it!/change title/ erase post.

First rule of closed beta: you dont talk about closed beta.

Second rule of closed beta: you dont talk about closed beta.

Third rule of closed beta: you dont talk about closed beta.
[Galaxy S I9000 Android Development] japperrrr:
Didn't know it was a closed beta since I downloaded it from another forum where no one said it was.. Sorry? :confused:
[Galaxy S I9000 Android Development] RyanZA:
The fix is GPLed... Private beta or not, there is nothing wrong with talking about supercurios fix. That said, it is beta for a reason, and people installing it without understanding that deserve everything they get. :)
[Galaxy S I9000 Android Development] gusoldier:
Then why do we talk about samsung firmwares...? I'm sure most of them are also closed beta.
[Galaxy S I9000 Android Development] xmonkee:
It's like this: say, you are making a movie. This is going to be the best movie ever. You give the draft unedited copy to some of your friends to see how they like it. Then a guy comes along, downloads it, and starts complaining that the camerwork is aweful. That too in the ny times. Do you think that's right?

Tl;dr: delete it
[Galaxy S I9000 Android Development] japperrrr:
I do have quite some knowledge about flashing phones because I try things I don't understand. When it goes wrong, I can learn from that. As I couldn't find any other topic related to the problems I was experiencing I created a new one. I did NOT create this topic with the intention to complain about bugs. I didn't even know Voodoo was the problem :)

Do you think it's right to blame someone before reading the topic? A few posts ago I told that I didn't know it was a closed beta and I that I did not create this topic to complain about bugs in the Voodoo lagfix. I created it because I needed help fixing my device.
[Galaxy S I9000 Android Development] dakine:
First rule in closed beta: Don't put your files online for the world to see :D

Second rule of closed beta: Don't forget to tell your beta testers not to post links to said files :D
[Galaxy S I9000 Android Development] zerocoolspain:
relax...:D:D:D
[Galaxy S I9000 Android Development] Idan73:
and the pack mentality reaserts its dominance!!! wtf!!! making a guy apologise??? for what? testing? closed beta with public links??? "Do not talk about closed beta"? meaning if you develop a problem only cause it can paint the project in negative light. otherwise talk away (refer to jm7 thread pr capital for voodoo project)...dude you got nothing to apologise for and hope your phone is fine....closed beta dogs (please be courteous and try to help or)..pissoff.
[Galaxy S I9000 Android Development] Finguz:
Well said!