yashsingh1/xdaforums huggingface dataset:
[Nexus S General] supercluver:
Disconnects as in the phone is literally not connected via bluetooth anymore or just skips in the audio?

I have an '08 Fusion and my Nexus S 4G works perfectly. I had an Epic 4G prior and it was terrible. Audio skips all the time, it would forget it was paired to the car frequently, and sometimes the bluetooth wouldn't turn off or on and I'd have to reboot the phone.

Anymore info you can provide?
[Nexus S General] dus10young23:
Same here w/ me/mine&my Sync/navi in my 2010 GT500!
[Android] Maryushi3:
Is it better to wipe from phone settings or from recovery menu?

What are the differences?

I want to wipe phone, because I installed too much crap and some of it can't be uninstalled and some apps I don't use some apps that I've installed because "maybe they come in handy".

S5830 Galaxy Ace - Tapatalk
[Android] simon_lefisch:
I like to wipe from recovery
[Android] dastin1015:
Wiping from settings will delete all third party apps and data on the phone without any user error in the wiping process. Within recovery you may choose what to wipe but may accidentally wipe something such as your SD card by accident.

Sent from my Hero that never dies! ;D
[Android] nprussell:
Just to be awkward, I'm going to throw a third option at you:

From a Samsung phone, you can dial :

*#*#7780#*#*

To perform full wipe/factory reset.

It is important to note that using this, or selecting reset from the menu is effectively the same thing as using recovery anyway, as all it will do is boot into recovery and wipe the data/cache.
[Droid X General] sk8rboy1491:
i just recently installed the gingerale rom on my droid x using the d2 bootstrapper. i love this rom so far, it is very snappy and quick compared to the beta of gingerbread that i was running. the beta was kind of laggy so the gingerale is a welcomed change. there is a bug that i found in it tho. whem you pinch to zoom all the way in on a picture in the gallery, the vibration is WAYYYYY too long. to the point to where its overkill. same with zooming out. it only happens when you hit the max zoom in/out. i would really like this problem to be addressed. i would have like to have posted on the developers area to tell the guy that made it about the bug but i guess on here should be good enough. please try to get this one fixed guys :( :confused:
[Droid X General] Jmoney47:
Pm the dev.
[Desire General] Chiller89:
Hi all :-) firstly I just wanna say thanks so everyone that develops and creates amazing stuff for our phones on this site. Right to on to my question, I got my HTC desire a couple months ago, rooted it basically as I got it, with unrevoked, however, I'm still busy considering going s-off and I have a big question, I currently am running cm7 nightly, and clockworkmod 2.5.0.7, which got flashed during the unrevoked process, so my question is, is it safe to s-off with this? Or should I run an ruu first, and if it is safe, should I let alpharev install its custom recovery or not?

I did look around the forums, and couldn't find anything directly related to this, so any help is greatly appreciated :-)

Thanks so much

Not sent from an IPhone of any sort
[Desire General] expza:
I had such a mission trying to S-OFF - eventually, after asking around, I realized that the most common problems when trying to S-OFF come from two things:

A) S-OFF when a Gingerbread ROM is installed.

B) S-OFF in a rom that uses Apps2SD or Data2SD.

Eventually, I just downloaded a 2.2 RRU that had Root and S-OFF'd from that. Worked like an absolute charm. Don't worry, once you're S-OFF you can then flash a Gingerbread, Apps2SD ROM - but prior to this, rather use a stock, 2.2 rooted ROM. Unfortunately I can't remember where I downloaded it from, but it was from XDA. The filename was Bravo_WWE_2.29.405.5_v5.zip

Don't forget to familiarize yourself with Android SDK and Fastboot. Cyanogen have a fantastic Wiki on it: *can't get the full link, Internet is being lame. http://wiki.cyanogenmod.com/ and search for Fastboot.*

edit: Found the link in my Download History - http://www.multiupload.com/SAEPLNMOG7
[Desire General] Chiller89:
ok thanks, quick thing, RUU's erase your current recovery right?

and with that, did you let alpharev install its custom recovery?

Thanks so much
[Desire General] expza:
Uhm, good question. I never really had the opportunity to tell. I told AlphaRev to install CWM-AlphaRev recovery, and there's no where between starting the S-OFF process and it being done and dusted to tell if the recovery layer is removed.

To elaborate:

ClockWorkMod, flash RRU.

Boot into RRU, start S-OFF.

S-OFF completes, CWM-AlphaRev is installed as recovery.

No where to tell if ClockWorkMod was removed :)
[Desire General] Chiller89:
Ok so you just flashed your stock Rom from recovery and went from there? You didn't go through the whole pc ruu/fastboot process? Sorry for all the questions :-)

Not sent from an IPhone of any sort
[Desire General] expza:
Yup - ClockWorkMod, Full Wipe, install ZIP from SDCard, Bravo_WWE_2.29.405.5_v5.zip, Reboot phone in ROM, enable USB debugging, start the S-OFF Process.

I did need to use fastboot to flash AplhaRev Oxygen once S-OFF, as that's the partition sizes I wanted.
[Desire General] Chiller89:
Ok thanks so much :-)

Not sent from an IPhone of any sort
[Galaxy S II Themes and Apps] bgx:
Someone has an working black themed gtalk V3 here?

And somebody has an fully working black gmail for me? That black one I have FC when I try to attach a file! :-(
[Galaxy S II Themes and Apps] the_Calen:
a gmail black theme would be nice, trying to change most of my apps to black themed ones, looks nicer and save some power
[Galaxy S II Themes and Apps] vanahaim:
I found somewhere on internet - it isn´t my work I have only modded some pngs ( to match with black theming like gtalk mobile indicators etc. )

Edit: a bit edited new version of Gmail added - full blacked from this post http://xdaforums.com/showpost.php?p=12885065&postcount=1

Enjoy!
[Galaxy S II Themes and Apps] arii1986:
How do you install these? Do you have to replace them with root explorer?
[Galaxy S II Themes and Apps] vanahaim:
Yes :) Replace by RE, or push via adb commands.. (adb remount, adb push..)
[Galaxy S II Themes and Apps] bgx:
Thx that gtalk work! But it isn't the version with videocall ! Somebody has v3 black themed?

EDIT:

Gmail work also, but only the select section of mails are black, email is with white background; the version I have here the mail ist also black but when i try to attach an file I get FC with my version! :-(
[Galaxy S II Themes and Apps] cheekystew:
Should they not be zip files to use root explorer?
[Galaxy S II Themes and Apps] bgx:
Just open the rar and move the apk file inside to system/app ...
[Galaxy S II Themes and Apps] vanahaim:
Try new added version!
[G2 and Desire Z Q&A, Help & Troubleshooting] Scann69:
Is there a way i can have the keyboard light always on the minute i access the keyboard? currently it's running on the light sensor which turn the keyboard light on and off depending on the brightness of the area. I would like to keep it on...anyway to do that?
[G2 and Desire Z Q&A, Help & Troubleshooting] dirtytotoi:
Yup....i'm using the Z as a spare phone and would also like to have this option. Seems like it's not something doable :confused:
[G2 and Desire Z Q&A, Help & Troubleshooting] sergio_alireza:
i can't understand your mean exactly(my english is bad:( )anyway if you want light's of keyboard be allways on you should use other rom like CM 9 or ...
[G2 and Desire Z Q&A, Help & Troubleshooting] noneabove:
That depends.. are you rooted atm ? And if so what ROM?
[G2 and Desire Z Q&A, Help & Troubleshooting] 9m2bal:
Yes, that depends on rom.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Someone asked what the point of the new .39 kernel is, well here's a new feature I've coded up that was made possible due to the more modern kernel.

I have modified the touchscreen driver in the kernel so that the zoom bar is now working, and it sends signals to Android that make it think you're sending a multitouch pinch-to-zoom.

I've got it set so that it sends an input from the center of the screen. As you slide right, the driver tells Android two fingers are moving apart from the center. As you slide left, the driver tells Android two fingers are sliding from the sides towards the center. The net result is that the zoom bar works in any app that supports pinch to zoom.

I've uploaded a video showing it in action:

http://www.youtube.com/watch?v=GRWUzPveU14

I'm going to submit this patch soon, and I'd like it if some people would try it out and give any feedback before I do so. I suppose things to pay attention to would be any increased wonkiness in the touch response, as well as boundaries for the zoom bar. Also, if you have a better idea on how this should work, it's now or never.

Unfortunately, this is a modification of the new .39 kernel, which means that a lot of things are not working on it, and this test kernel will most likely not be suitable for daily use if you like wifi and the other things that don't work on .39 yet.

In order to install you must do the following:

1. Replace your zImage with the one attached.

2. Use the .39 haret (included in the zip for your convenience) with the .39 startup.txt line (set initrd_offset 0x00a00000)

3. Place the included android.hardware.touchscreen.multitouch.xml under /system/etc/permissions. I tried bind-mounting it from conf, but for some reason that did not work for me. If you don't do add this permission file, the multitouch points will still be sent to Android (and will show up in the app Multitouch Test), but Google's own apps like Browser will ignore them.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Amazing.

First time, I can use this since ages.

Unfortunately, my phone has become very sluggish with this test kernel.
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
I totally agree with that!

Rhod100_nl

Nice work!
[Touch Pro2, Tilt 2 Android Development] fortunz:
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?

Impressive. Thanks for the vid. :D

I'm planning to give the .39 kernel a quick test run, hopefully this weekend. There's some software that crashes on me on open now and I'd like to see if its any different with .39. I'll try to give this a whirl then.

As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
[Touch Pro2, Tilt 2 Android Development] LinoX:
well that bar has been designed to be a zoom bar. you can do whatever you want with it but always a zoom bar remains :D using it as a "virtual button" is possible but on the phone you will always have the magnifying glasses printed :D

What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing) :)
[Touch Pro2, Tilt 2 Android Development] fortunz:
All I suggest is flexibility. I'm not trying to steal your zoom ;)
[Touch Pro2, Tilt 2 Android Development] LinoX:
All you are actually suggesting is complexity, indeed. A "soft" array button must be handled properly by the kernel / os / applications and it is a lot more than "one hack" for a function that will be probably not used because the zoom is a bit more important than a button :D
[Touch Pro2, Tilt 2 Android Development] fortunz:
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks

like

soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
[Touch Pro2, Tilt 2 Android Development] Starfox:
It's "controversial" because you are asking for a strip of capacitive touch to turn into buttons. As the OP indicated, implementing this requires not only a new kernel+touch, but files in system.ext2, so the system _thinks_ you have p2z when you still have a resistive screen. So what you are asking for is to make that "flexible" when the base feature has barely been coded+tested.

If you truly want capacitive soft buttons, look at the DIAM or RAPH. Back way then (2.0ish), the LED on the bottom button-panel/scroll would light up on finger contact (not pressed) when running xdandroid. It was more of a "wow it's cool" thing because it was a strip of capacitive touch with 5+ LEDs. I don't remember if the p2z worked with the center scrolly or not...

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Alright, settle down children.

I think you're looking a little too far ahead fortunz, but that's just my opinion.

To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.

But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
[Touch Pro2, Tilt 2 Android Development] fortunz:
Bu... but... even with the bold starfox still couldn't get it :p Nevertheless, I am reaching out for my zen.

Fair enough. I was just trying to avoid any potential "now or never" deadline issues. :)
[Touch Pro2, Tilt 2 Android Development] manekineko:
Yeah, after I got the .39 kernel, it took me like 30 minutes to get it working for the first time, and then a bit more time to clean up the code to look nicer.

Whereas I'd spent hours banging my head on the wall with .27, never quite sure where the problem was, since I thought I was sending all the right events in the driver. Now I know I was sending the right events (because it works in .39) which means that the problem must have been something in the kernel not passing along the multitouch sync events (I know it's that event missing from debugging the userland). That narrows things down quite a lot, but I don't think I really want to go back and spend the time fixing things up in the obsolete .27 kernel though.
[Touch Pro2, Tilt 2 Android Development] Serren:
Awesome work Manekineko!

I think the zoom bar code will be a fun addition to future cooks. It will be fun to see what uses people come up with. Be it soft buttons or just a zoom bar. Either way, cool stuff.
[Touch Pro2, Tilt 2 Android Development] Starfox:
There never is and will never be a "now or never" with Android. If you want a feature and it can be coded, take the source and run with it. You may run into walls, and there will be many, but at least you can try - that's the beauty of open source.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] manekineko:
Yes it does :D

Thanks for the suggestion. I'm not going to be implementing it at this time, but the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.

When I was fighting with getting .27 working, I considered at one point simply turning the zoom bar into soft buttons. However, I was never able to come up with a practical use for soft buttons on the zoom bar. The thing that makes it hard is that the list of keyevents Android understand are extremely limited.

You can see for yourself here:

http://developer.android.com/reference/android/view/KeyEvent.html

Set the filter level to API level 8 to see what's available on Froyo. Unfortunately, really useful keyevents like button zoom in/out only became available in Honeycomb (API level 11).

I'm not sure that soft buttons for things like home or power or search would be very convenient when they're not visible on the physical device, are right next to the screen, and could instantly rip you out of what you're doing.

Just in case anyone happens across this that is interested in doing so, here is how you'd probably want to do it:

Android's KeyInputQueue.java, which handles inputs from the touchscreen (and everything else). Do a search for readVirtualKeys and see that it reads from /sys/board_properties/virtualkeys.tssc_manager. Edit the driver so that it generates the virtualkeys file in the format specified in KeyInputQueue, and disable all of the topaz/rhodium zoom bar code.
[Touch Pro2, Tilt 2 Android Development] fortunz:
Flexible structure is really the only thing I was after. Glad it was already in the plan. And thanks for laying out some possible paths to additional features as well. :)
[Touch Pro2, Tilt 2 Android Development] randomblame:
Thanks button activated! Great work!

whoops thanked fortunz accidentally -1 buddy :p
[Touch Pro2, Tilt 2 Android Development] manekineko:
If anybody could find an app that supports touch pressure on a regular kernel on XDAndroid, that would be really helpful. I need to check how much we support pressure to start with and make sure that still is the case with this patch.

I tried Crayon Doodle Lite from the Market, which claims to support pressure, but I'm not seeing any pressure on a regular no-zoom-bar build, so that's not working as a test. Or it may simply be the case that pressure touch has always been broken.
[Touch Pro2, Tilt 2 Android Development] LinoX:
+1

Developing in a way that MAYBE, ONE DAY, SOMEONE, WILL (or just will not) adds unuseful complexity to every software.

BTW: Great work manekineko :)
[Touch Pro2, Tilt 2 Android Development] teemo:
Good job, but....

Broke my internet (is zoom tested with gprs or is it CDMA only ?)

Kernel.39+RIL2+F22 is running fine on my R100. After drop in of the Zoom-zImage, connection died.

Without zoom with working connection (SMS error is my operator NOT android):

k39_no_sms_log(537).txt

Zoom added - go to line 552

k39-zoom_no_data(552).txt
[Touch Pro2, Tilt 2 Android Development] manekineko:
Nevermind, found an app called Z-DeviceTest that does the trick.
[Touch Pro2, Tilt 2 Android Development] manekineko:
That's quite odd, but it strikes me as really, really unlikely this patch has any effect upon your internet. All of the changes take place solely within the touchscreen driver.

Seems more likely this is just some .39 kernel bug rearing its head.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just got around to trying this out (I know, I'm a slacker :p) and it works freakin beautifully! But re: the bind mount issue. rpierce99 mentioned on IRC that if the file doesn't exist you must ln -s (symlink) which did work.

FYI folks, jonpry has pulled manekineko's patch into mainline .39. So far, for everyone I've talked to the code 'just works'. Kudos manekineko ;).
[Touch Pro2, Tilt 2 Android Development] BoominSVX:
Has anyone else using this lost touch screen response during a call? I noticed I couldn't hang up after the change. Is this a kernel problem, or does the issue reside between my keyboard and my computer chair? Just can't hit the red buttons.... either of them. I'm using the b4=home switch in the startup (for specifics) on my Rhod400.

Great job by the way! Loving the zoom!
[Touch Pro2, Tilt 2 Android Development] rpierce99:
The touch screen issue was reported to the mailing list yesterday, sadly manekineko is on vacation for a couple weeks so we won't be getting it resolved. It has been taken out of the main .39 tree until manekineko comes back and gets it resolved, so for now you may want to roll back to a standard kernel (or the .39 test kernel) until it's resolved.
[Touch Pro2, Tilt 2 Android Development] muziling:
kernel update to 3.2 , does this patch always in dev process or where can i found this unfinished patch?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
manekineko has been MIA for quite some time... Not sure where on GIT his patch would be, but I believe it is somewheres. I'll try to find it for you.

Edit, got it. Wasn't on GIT, t'was on the ML.

http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-June/000343.html
[Android Software/Hacking General [Developers Only]] mehdi_hz:
Hi to all,

I had samsung gio with middle east (persian support). I thought its version was S5660JPKB9. I updated my phone with odin to eurupe version and now it does not have persian and I want to roll back to my firmware. but now I couldn't find middle east firmware.:(

Please help me how to find and download middle east version of this phone?

Thanks.
[Android Software/Hacking General [Developers Only]] RiTCHiE007:
Yea, i believe the country settings are stored in the CSC file... but you can download most stock firmwares here http://www.samfirmware.com/fwandroid.htm

hope it helps you.
[Desire HD Accessories] kyleastley:
Just brought this case and have to say its the best case I have had on any phone I have owned. All buttons are easily pressed and the phone is very well protected best of all it only cost £14.99 on amazon

http://www.amazon.co.uk/Case-mate-Pop-Case-HTC-Desire/dp/B0047CQ0GA/ref=sr_1_1?ie=UTF8&qid=1307644791&sr=8-1
[Desire HD Accessories] The Specimen:
Yeah I've had this case for a while and absolutely love it. Looks awesome, fits the phone very tightly, good grip and great protection.

Only downside is that it kind of blocks the GPS signal so it can take longer to connect. Sometimes notice my reception bars are lower with the case on and occasionally get a drop out in weak signal areas.

Other than those things the case is perfect and I just can't bring myself to switch to an OtterBox Defender case that apparently doesn't have those signal issues.

Reception problems were rom related. Case is flawless for me.
[Desire HD Accessories] mrmad23:
I kind of like the case as well, even though I just realized how much smaller my desire HD is without it ...I think the case almost fits too perfect- it is real hard to take off. Other than that it is a good option if protection is really important to you

If interested you can get my full review over here:

http://www.mrmad.net/case-mate-pop-for-htc-desire-hd-1506
[Desire HD Accessories] telemachos:
Has a nice grip, adds a lot of bulk, is hard to remove, gets scratched veeery fast (and looks ugly). I dont use it anymore and would not recommend it.
[Desire HD Accessories] ohoppe:
I can absolutely recommend

www . case-mate . com /HTC-Desire-HD-Cases/Case-Mate-HTC-Desire-HD-Barely-There-Case.asp (remove whitespaces from url)

have it since month, no scratches, does not add to much to the normal surface, easy to remove if needed but also good attached without any big borders to the device.

Seen also the above mentioned one and didn't like the overall design and fitting at all.
[Desire HD Accessories] sageandonion:
http://www.google.com/url?q=http://...821541&usg=AFQjCNF97jynXV3AfgWXlUP8gSxJiJHYRQ

Otterbox all the way, far superior.
[Desire HD Accessories] bryantcraig:
Awesome case I love it. I gave up my otter box for it. Excellent buttons, perfect size, good grip. AAA
[Desire HD Accessories] fun5199:
the pop case is look very nice but it's a lil bit thick..
[Desire HD Accessories] ToneyEricsson:
It would of been good if case mate did a pop case in the same texture as the tough I think
[Desire HD Accessories] CuBz90:
I buy all my cases from eBay for £1 to £2. I drop my phone alot every single day as I have a habit of throwing it in the air, my phone is still in perfect condition, no scratches or marks, after over a year of use and bumps.
[Desire HD Accessories] Sogaard:
Maybe i should consider that, mine is getting a bit scratch as time goes. Not dropping it a lot - just normal "pocket use"
[Desire HD Accessories] chengjie89:
I dun use any case or covers, instead i chose to use a pouch.

Surprisingly, the HTC HD7 pouch fits in quite nicely.