yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] billard412:
And while you may consider this a "mod" most (including myself) do not as this was the way the camera was originally designed. Sprint took it among themselves to cripple it. and while you cant walk into a sprint store loaded with modifications and expect to recieve sympathy for your problem this will most likely go unnoticed and even still does not raise the status of the system from normal/official or trigger the odin mode count/triangle so theres nothing to indicate modification to the device.
[Samsung Epic 4G Touch] jasonsf:
Can you clarify what this does? It appears that it flashes the system partition with the same GB27 that is available via Kies but with the mentioned xml file modified. Is that correct? Does the data partition remain intact? Will this work after putting stock GB27 on via Kies or does it need to be applied to the current OTA?

Thanks for this. I'd love to have the camera shutter option for my wife's phone and she doesn't want me to mess with rooting/unrooting her phone.

Jason
[Samsung Epic 4G Touch] mmark27:
It does exactly what you want. Doesn't mess with anything except adds the shutter sound toggle. Data and everything remain the same. This is not a complete Rom, just adds the toggle. You don't even have to tell her you did anything. :)

Sent from my Fre3-ed out GS3
[Samsung Epic 4G Touch] yudancha:
This did not work on my phone. My camera app is ver. 1.5 I applied the changes in the features.xml file using ES File Explorer, verified the edits and rebooted (complete shutdown) the phone. I am rooted with the GB27 ROM. An ideas as to why this change didn't take effect?
[Samsung Epic 4G Touch] billard412:
ES screws the permissions up. If u have terminal emulator or adb set up u can remedy this by running

su

mount -o remount rw, /system

chmod 777 /system/csc/feature.xml

and if u have gb27 u shouldn't have this but just in case check the build.prop and make sure this line of text is not in it

"ro.camera.sound.forced=1"

If its in there the 1 needs changed to 0
[Samsung Epic 4G Touch] bill9999:
I followed the instructions below but the Shutter sound option is still not there. I double checked the file and it is set to true. Any ideas?

What you have to do is use an app like root explorer and change the following lines in /system/csc/feature.xml

Edit the following:

<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>

Change the "false" to true. Save the changes and exit.

Reboot your phone and now you can toggle if you want shutter sound in options.
[Samsung Epic 4G Touch] yudancha:
Thanks Billard. I simply used ES and changed the permissions to rw-rw-rw to resolve.
[Samsung Epic 4G Touch] YoColdRain:
ok, so i cant get billard's solution to work. Im rooted and used ES file explorer as well as terminal, and my feature.xml changes are set to true. I restarted phone and changes are still there in feature.xml but i simply do not see option under camera settings. My version is 1.5 does that matter?

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

editing my above post

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

so i ended up opening build.prop and adding below line, line wasnt there. and now after restart i see Shutter sound option and it works. So not sure if second restart is what fixed billard's solution or build.prop needed the line.

ro.camera.sound.forced=0
[Samsung Epic 4G Touch] Kruxoli:
I followed the following directions:

What you have to do is use an app like root explorer and change the following lines in /system/csc/feature.xml

Edit the following:

<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>

Change the "false" to true. Save the changes and exit.

Reboot your phone and now you can toggle if you want shutter sound in options.

Worked PERFECTLY for me after one reboot.
[Samsung Epic 4G Touch] xpanmanx:
This. Thank you.
[Samsung Epic 4G Touch] oscarthegrouch:
Knowing nothing about this, but purely guessing, odin can only do partitions, not individual or multiple files? A cwm flash could replace files because the information inside the zip tells recovery where to put the contents inside the zip? Am I understanding it correctly?
[Samsung Epic 4G Touch] billard412:
Exactly.
[Samsung Epic 4G Touch] mattweed9:
Thanks for this, worked as said.
[Samsung Epic 4G Touch] crucian4:
I am rooted. I previously changed the names of the sound files for the camera following some instructions from a much older thread. It worked on the videocamera and camera shutter but the focus beep remained. I followed the instructions above using root explorer and text editor after long pressing on the file. The option was there after reboot. It's near the end of the settings menu. My camera is now silent and I changed the option a few lines down to use the camera while on a call to true as well and that is also working.

Thanks guys.
[Samsung Epic 4G Touch] jtsv:
Awesome! Been enjoying being stock GB27 but hated the shutter sound and the 3rd party cameras didn't seem to be as good. Found this today and loving it! Thanks!
[Samsung Epic 4G Touch] RECD Designz:
Haven't messed with my stock phone in a while now so this is probably a stupid question, but, I assume the phone will pretty much be wiped clean, correct?

So I'll have to re-download all my apps?

What will I need to backup (texts, pics, etc)?
[Samsung Epic 4G Touch] billard412:
No this will not wipe anything. All data will stay intact
[Samsung Epic 4G Touch] SoundwaveRumble:
I followed this and was able to get the toggle, but the shutter sound remains no matter if I have it toggled OFF or ON. Any ideas?
[Samsung Epic 4G Touch] billard412:
Open the build.prop and near the bottom find this line:

"ro.camera.sound.forced=1"

Change the 1 to a 0 and save. Then reboot
[Samsung Epic 4G Touch] SoundwaveRumble:
Thanks, shutter sound now toggles on & off.
[Samsung Epic 4G Touch] BIGSAMDA1ST:
I know it's been a while since anyone last posted on this thread,but I just finished using this thread to get the shutter option on to my daughters phone, and I must say it was a breeze. Big thanks to you Mr.Billard412.. :thumbup::thumbup:
[Samsung Galaxy W I8150] threefour:
Hi guys, new to the forum.

I've replaced the digitizer on my galaxy w, after the old one broke, with a cheap one from ebay.

Its now either hyper sensitive or not sensitive enough, i've read through this thread ( http://xdaforums.com/showthread.php?t=1976299&highlight=digitizer ) and flashed the zip mentioned in there but it still basically renders the phone unusable.

Is there anything else i can do to fix this problem? Or can anybody recommend a better supplier for digitizers?

Running cm9 if this makes a difference.

Sorry about the long winded first post, it's getting on my nerves though.

Thanks
[Galaxy Note II Q&A, Help & Troubleshooting] aukhan:
I am planning to buy a note 2 for my friend he said he wanted 1 as i use 1 currently so started to find the best deal came across this

Korean made AHD Samsung Galaxy Note 2

http://waveshopping.co.in/index.php?route=product/product&product_id=65

Cost 24,000INR which is 442.15$

This is the link is this real or some Fake ?
[Galaxy Note II Q&A, Help & Troubleshooting] drdino:
Fake. :D

Sent from my Note II using smoke signals.
[Galaxy Note II Q&A, Help & Troubleshooting] maynard14:
fake
[Galaxy Note II Q&A, Help & Troubleshooting] Gnarfsan:
So fake
[Galaxy Note II Q&A, Help & Troubleshooting] Nirak:
Def. fake...compare the specs to real on samsung site. dual core processor and just 1 gb ram :(
[Samsung Galaxy Nexus] bmg1001:
Hey guys, don't know where to post this so I figured here because you themers might know where this is. I'm looking for the png if this icon. The one that appears on the 4.2 lockscreen when a widget is maximized. I attached a screenshot for clarification. I've searched in the framework, but I couldn't find it. I don't know if I just didn't look hard enough. Help?
[Samsung Galaxy Nexus] mmegalodon:
/system/framework > framework-res.apk > res > drawable-xhdpi

Your icon should be there sorry for the the extra attachment

Sent from
[Android Q&A, Help & Troubleshooting] doeeyedbecky:
moved to different forum.
[Samsung Galaxy Mini] Cipul:
Whether anyone tried mihome launcher on CM10.1 (android 4.2.2)?

I've tried to install and open it but suddenly jump to the home screen (the other launcher), tried to push in system/app but same result. :(

Or it incompatible for cm10.1?
[Samsung Galaxy Mini] ivelramona:
try to install mihome launcher LDPI...

Just click thanks if i help u <
[Samsung Galaxy Mini] Cipul:
same result at Mihome Launcher LDPI...
[Samsung Galaxy Mini] Cipul:
Up up
[Samsung Galaxy Mini] Cipul:
Up again
[Sprint HTC EVO 4G LTE] gdrocks:
The screen on my evo is freaking out (digitizer malfunction, top left corner randomly activating) and I need to take my phone into sprint to get it fixed or replaced. Unfortunately my laptop is beyond repairs and I am running CM10.1 while unlocked with S-off, with the customizer used so it still looks like s-on and locked. Is there a ROM or some sort of flash able I can use to get to a returnable state?
[Sprint HTC EVO 4G LTE] premo15:
Flash the stock rooted rom:

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

They won't even know the difference. If it's a hardware issue, the fact that you're rooted/s-off shouldn't matter anyway, but I doubt they'll even check.

Sent from my EVO LTE
[Sprint HTC EVO 4G LTE] luigi311:
Yea I think ur good with just a stock ROM since its a hardware issue software should have no effect on it unless there's a bug on cm which I doubt since I'm rocking it to lol
[MDA II, XDA II, 2060 Accessories] Ian_Goulding:
I have been using a JABRA BT200 Headset with my XDAII and have always had the same problem, once the BT200 has been paired with the XDAII it works fine but once I put the headset into it's charging cradle and then remove it and try to use it again it always loses it's bond, the only way I can get it to communicate with the XDAII again is to pair it again.

I don't know whether the problem lies with the BT200 or the XDAII

Does anyone else have this problem ???

Thanks

Ian Goulding
[MDA II, XDA II, 2060 Accessories] Robson:
hey ian,

it was just recently that i was able to figure out the bt-xda2 bonding; thanks to some helpful chaps in the forum. in the process; i did some research within several topics and read something which may answer your query. when the headset is back in it's cradle; i believe it's "turned off" or is put into inactive mode. the forum message i read indicated that the bonding is lost once the headset is turned off; thus you have to bond again. yes, i have had similar experiences while figuring out the bonding issue. i just keep the bt200 i have out of the cradle; when the time comes to charge it i then holster it and repeat the bonding process once it's charged. i don't think it's a problem with neither devices; it's the default setting i believe. with luck probably the xda-developer guys will come up with a bug fix for this item. which could also include using bt for other than the phone function...like mp3....hint! hint! :D

cheers

robson
[MDA II, XDA II, 2060 Accessories] RedBull:
I've installed Towa's GPS BT patch and the Jabra works perfect.
[MDA II, XDA II, 2060 Accessories] Robson:
hey redbull,

what's the Towa's GPS BT patch and where can i find a link?

cheers mate

robson
[MDA II, XDA II, 2060 Accessories] louisk:
Towa's gps patch has nothing to do with this...

I'm not sure what you are talking about, but Towa's patch will not solve the Jabra BT200 issue. The more important question to look at here is what version of BT200 you have. If you look on your Jabra BT200 right next to the microphone, there is a combination of letters and numbers, what does yours say? I think the problem has to do with issues in the firmware in the Jabra that were fixed in later versions.

It's usually 2 numbers and a letter on the boom to the Microphone.

I have a 47A and it does not work at all. Also tested a 48A and it doesn't work either.
[MDA II, XDA II, 2060 Accessories] RedBull:
mine's a 48b. works fine.
[MDA II, XDA II, 2060 Accessories] louisk:
Cool, just so we are talking about the same thing, you can turn off the Jabra BT200, and turn it back on, and it still works with the phone? You can charge the headset in it's charger and pull it out and it still works? You can go out of range and then back in range and it still works? You can press the answer phone button on the headset when no call is in progress and then try to make a call and things still work?

Please try these various things and let me know.

I know that the A models are from 2002, and the B models are 2003. So it is possible if yours works with all these scenarios that they fixes or changed something in the 2003 models that allow them to work.

Thanks for your time,

LouisK
[MDA II, XDA II, 2060 Accessories] BarnOwl:
I recently purchased a BT 250 with nr. 44B and indeed it works with all the tests you described. (Don't need the BT GPS patch for that)

If only the advanced Headset Profile features would work with the MDA II I would be in heaven...........
[MDA II, XDA II, 2060 Accessories] louisk:
Ok, it seems based on feedback I've gotten from several people that any Jabra Freespeak that has a "B" as the last part of it's version number will work correctly, but the "A" models do not. The "B" models according to Jabra are the most recent, and thought they don't admit it, there must have been a change in the firmware that allows the "B" units to work correctly with an XDA2/MDA2/i-Mate that the "A" units don't support.

LouisK
[MDA II, XDA II, 2060 Accessories] jonburge:
I have a "B" on mine and the same problem of rebonding when Jabra is shut off. I experimented by turning off bluetooth on the i-mate and it still worked. Anyone have ideas of a good headset that will not need rebonding?
[MDA II, XDA II, 2060 Accessories] stryker:
I have problems with mine too and its a 16B. Turn the BT headset off and its rebond time again.....
[MDA II, XDA II, 2060 Accessories] Fais:
48B works fine for me... can't everyone else just use TOWA's patch... that fixed the problem for others
[MDA II, XDA II, 2060 Accessories] xdaguru:
16B is no good. I've been told that minumum needed is 19B. Below 19B is bluetooth 'handsfree' not 'headset'.
[MDA II, XDA II, 2060 Accessories] louisk:
Towa's patch has nothing to do with this. It will not help in this situation. It only applies to Bluetooth Serial Profile, of which the Jabra has none. I have talked to Towa via email to confirm this. For those that installed Towa's patch and said it works, more than likely they didn't have the problem anyway because of the version of Jabra they had.
[MDA II, XDA II, 2060 Accessories] mrg2003:
BT jabra 200/plantronic M3000

Jabra is model 45B, - no nead to repair, Plantronics M3000, no need to repair, but sometimes fails to answer call properly.
[MDA II, XDA II, 2060 Accessories] jimVmax:
Hi 2U all,

I have just purchased a BT200 off Ebay, the number on the boom is 20B. No problems works well :D , no rebonding problems. Just one wish, it would work with voice. But I will keep praying!

StayLucky Jim :wink:
[MDA II, XDA II, 2060 Accessories] Ian_Goulding:
EMAIL FROM JABRA RE-Bonding Problems with XDA-II

:roll: :roll:

Seems to me that without actually saying it, JABRA think that the fault lies with the XDA-II!

Regards

Ian Goulding
[MDA II, XDA II, 2060 Accessories] seanc:
question?? does the bt200 2.5 work with the imate and a i95c at the same time??

i have two devises an I95cl for nextel not blue tooth and the imate pc phone. i would like if possible to use one headset ?? the bt 2002.5 says it will work for bt phones also?? but will it work at the same time ?? hope iam clear...iam a baby here can you tell
[MDA II, XDA II, 2060 Accessories] leemrvnt:
15B, can it be upgraded?
[MDA II, XDA II, 2060 Accessories] Rayan:
Hello everyone...

I have an MDAII and a Plantronics M3000 BT headset and I have the same pairing problem.

I always have to repair the two divices for them to work... :(

Any ideas?

Best regards,

Rayan
[MDA II, XDA II, 2060 Accessories] ik8sqi:
Jabra 200 has problems, 250 is ok

I had all symptoms described in this thread with the Jabra BT200. As soon as my new BT250 arrived, it worked like a charm, not a single pairing/bonding problem with the 250.

Roberto
[MDA II, XDA II, 2060 Accessories] Pegasus:
Jabra T250

Hi you all

I have a new T250 headset with a serial number of 01C, all works fine whether the unity is turned off or moved away from my M1000.

Sometimes it is slow to transfer the phone call to the headset, pushing the answer button on the Jabra forces the link and it transfers the call.
[MDA II, XDA II, 2060 Accessories] Rayan:
You know? I think it has always worked fine, I think I was not waiting enough time for the BT to kick in or something. Now every morning I turn on the Headset and then activate the BT on my MDA2. I usually test the connection by dialing my own phone number and then I see the sound transfers to the headset successfully. But sometimes it takes a little bit more time to transfer.

Only a few times it fails. To fix that I just click the BT icon on the bottom task bar, click Bonded Deivces, click on my Headset device and then click OK. (If that fails I rename my current headset device and click ok).

Then the next time I use the phone it will transfer the call to the Headset.

I just make sure to hang up using the button on the Headset and this way it always works.

As a side note, Before I go to bed I always disable phone and BT by using Flight Mode.
[MDA II, XDA II, 2060 Accessories] Tommytello:
Jabra 200 BT bonding probs

Thanks Ian for that info on how to sort out the bonding problems, it seems to work with my BT200. Shame I dosent work 100% fault free but I'll just have to cope. I still have a week to send back my BT200 to amazon (£39.99) and I might get the BT250, does anyone think I should or just stick with the BT200, and the little fault that takes 10 secs to sort. :roll:
[MDA II, XDA II, 2060 Accessories] greenterp:
I recently bought the XDA II and also had the BT200 headset, but it did not work, as all you guys have said too. I returned it and exchanged for the BT250 - exactly the same problems! In fact it was even worse than the BT200 :cry: I took it back again and have exchanged for the Plantronics 3000 and so far, touch wood, it has worked ok. relief!!
[MDA II, XDA II, 2060 Accessories] Tommytello:
While getting used to the method explained above I have just realised there was nothing wrong with my BT200, the XDA2 does not connect to the BT200 just because the bluetooth is on, the headset mode must also be enabled. So to be clear there is not a fault, you just have to make sure the BT is on on the XDA2 and the headset mode is also enabled on the XDA2, of course make sure the BT200 is switched on!! My BT200s code is 03C
[MDA II, XDA II, 2060 Accessories] greenterp:
When using my Java 200/250 the headset option was always enabled but it still did not work, or if it did work it took so long for the call to transfer to the headset the voice mail had already kicked in :?
[MDA II, XDA II, 2060 Accessories] Tommytello:
It must be something to do with the latness of the headset and maybe the software version of the model od XDA2. Thanks for your input. Maybe people reading this should stay away from Jabra just in case?
[MDA II, XDA II, 2060 Accessories] RonnieFrown:
Other Bluetooth headsets

Hi Guys

I read through this forum carefully and the only headset that was looked at was from Jabra, accept the success described with the Plantronics 3000 headset. Does this mean all other blue tooth headsets on the market work fine with I-mate PPC Phone? Maybe some of the readers can tell us about other bluetooth headsets in the market that works fine with i-mate PPC phone. What should I buy??

Regards

Ronnie
[MDA II, XDA II, 2060 Accessories] BRosenow:
I believe all of the SonyEricsson BT headsets work correctly. I have an HBH-30 that I used with my old SE T68i and it has worked correctly since I took my i-mate out of the box. No re-bonding necessary (other than after ROM upgrades) no matter what process I use to turn on/off the headset itself, the BT stack or the headset profile. It just works!

I

highly

recommend it!
[MDA II, XDA II, 2060 Accessories] ironfin:
does anyone know which model of the Jabra BT250 work with no problems on the XDAII?

there seems to be alot of problems with them, but they look soo good :D
[MDA II, XDA II, 2060 Accessories] iissa69:
where can i get the towa's patch from

can someone tell me where i can download this patch from, it mentioned all over the place!

thank you.
[Galaxy S II Q&A, Help & Troubleshooting] albert7777:
I was installing the Build 6 AOKP rom on my already AOKP rommed phone. After installing both Gapps and the ROM, I realised I installed the GT-I9300 rom instead. Obviously the phone was bricked. CWM Recovery via the 3 key shortcut isn't working - it stays on the splash logo, but download mode works. From previous experiences ODIN doesn't seem to work, but I'll try it if necessary. I can't get a replacement from Vodafone (it's registered as a GT-I9100T but rommed as a GT-I9100) since its warranty is long gone. Is there anything I can do to get my precious phone back?

Thanks in advance.
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Get a Vodafone stock rom from Samfirmware, boot the phone into download mode, flash rom with Odin (search; how to Odin flash mentioned here thousands of times).

That's all you've got. You have no other way of fixing it (and even then you may not be able to).

If it won't work (phone & pc won't recognise each other), try the following troubleshooting steps:-

*Must run Odin as administrator in Windoze.

*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.

*Try different USB ports; you must be using a 'powered' or mainboard port.

*Try different USB cables (particularly the cable that came with the phone if you're not using it now)

*Try different versions of Odin (search on here/Google)

*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.

*Run Windoze Update.

*And if all these steps fail, try a different PC. And if it won't work first time on another PC, go thru the above steps on that PC. Still won't work ? JTAG repair or repair by service centre/authorised repairer.
[Galaxy S II Q&A, Help & Troubleshooting] albert7777:
Thank you so much, somehow ODIN decided to sense the phone spontaneously.
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Re: [Q] Installed incorrect ROM type.

Good for u..:)

Please add [SOLVED] to the title of ur post then.

"To err is human, to forgive is divine"

Sent from my SGS II
[Sprint Samsung Galaxy Note II] wizzlewizzle:
I've been looking for an app like this for a while and there are some that seem like they can but this is the solution!

https://play.google.com/store/apps/details?id=com.whitedavidp.keyboardmaster

it allows you to choose the keyboard you want for a specific app.

for instance I use SwiftKey. but when I use Polaris office I would prefer to use the Samsung keyboard. so now when I open Polaris the Samsung keyboard comes up when I open a different app SwiftKey opens(cause it's my default keyboard) it does it seamlessly. you can pay for the upgrade which allows for more than one app.

-Wizzle
[Sprint Samsung Galaxy Note II] Dmwitz:
Sounds promising :D