yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Themes and Apps] arnonrgo:
The Galaxy S has a built in one

Settings -> Location and Security -> Mobile tracker

Arnon
[Galaxy S I9000 Themes and Apps] lgkahn:
yes but i cannot find any instructions on how to use the built in one and i dont believe it has gps tracking.. in addition the app i recommended has a fuction to ring loud when called from a certain number so you can find phone if you drop it somewhere.. (even if on silent) and also gps tracking if you leave gps on.
[Galaxy S I9000 Themes and Apps] Ramsey:
I think mobile tracker on our phone has to do with Samsung Dive but I am not sure as I don't think it's fully implemented yet:

http://www.samsungdive.com/index.do

Click on: About.
[Galaxy S I9000 Themes and Apps] Seifer1975:
With the mobile tracker, you can also register an online account with Samsung, which allows you to remotely track the phone, wipe the contents etc. But yes, I agree that there's not much info available.
[Galaxy S I9000 Themes and Apps] lgkahn:
yes i tried to use the built in one .. .said i needed country code for number so

i put 1-areacode-number (i am in the u.s.) and still got the same error.
[Galaxy S I9000 Themes and Apps] daenney:
Try Prey. I also use it on my computers.

http://preyproject.com/

http://www.cyrket.com/p/android/com.prey/
[Galaxy S I9000 Themes and Apps] dan 6a:
The custom ROM comes loaded with Wavesecure which looks like the creme della creme of this kind of software but after I registered it told me it was just a trial :(
[Galaxy S I9000 Themes and Apps] Benjamin Dobell:
Did you put +1 or just 1. I'm from Australia and just wrote +61[Phone number] with no hyphens, +61 being the country code for Australia. I'm fairly certain the leading plus is a requirement.
[Galaxy S I9000 Themes and Apps] down8:
Lookout Mobile is good.

https://www.mylookout.com/

-bZj
[Galaxy S I9000 Themes and Apps] Prufrock:
I also use Lookout Mobile - it also allows you to send a "scream" to your phone, which causes the phone to make a loud siren-like noise for about 2 minutes, which cannot be turned off by the person with the phone (unless they take the battery out, of course). I also use Anti Theft Droid...nothing like double the protection. ;)
[Galaxy S I9000 Themes and Apps] waygeekierthanu:
I use:

https://www.mobiledefense.com/

Free and great.
[Galaxy S I9000 Themes and Apps] craptag:
BAK2u .com?

I've used them when I was still using win 6.5.
[Galaxy S I9000 Themes and Apps] bobloblawsum:
you can only use the built in tracker if you're in the UK or Germany.

Anyone from there want to try it out and see how it is?
[EVO 4G General] dmoses1969:
My videos recorded on the phone do not play worth a crap after the update. Way too much lag. Sound keeps playing but video stops. Anyone else having this issue?

Sent from HTC EVO using Tapatalk
[EVO 4G General] donatom3:
Just tested mine seems the same as before
[Touch CDMA Android Development] dlepage:
This is libcamera for Eclair. It won't work under Ion, Donut, Froyo.

RLS2

This release supports froyo kernel with the additional available memory and is also backward compatible with previous kernel.

Tested under Bell's Vogue running Vanilj Eclair RLS6 under both zImage-froyo-15-07-10 (RAMSIZE 0x07300000) & zImage-01-07-10 (RAMSIZE 0x08000000).

Backport dzo libcamera changes from froyo. Now works with both eclair & froyo kernel

Add support for jpeg quality setting

Only reports Auto WB. The other WB settings are not supported by the driver/kernel at the moment

RLS1

Fix FC in Settings with standard Eclair Camera Application

Should now work on Kaiser too

Not working

Video Recording
[Touch CDMA Android Development] incubus26jc:
very nice work bud. Thanks for your contributions:)
[Touch CDMA Android Development] JabbalSingh:
I can confirm it working under Kaiser. Good work.
[Touch CDMA Android Development] deadpig:
libcamera RLS1 kaiser test

Hi!

Just4Info: I just want to note that following apps now work on my Kaiser device:

* Standard camera

* Google Goggles (Wohoo :))

* Camera 360 (Free)

(Tested by taking 1 picutre with each app)

Only thing i noticed is that the "post"-views... the picture shown after taking a picture is disorted (camera/camera360), but god thanks :D the saved picture is ok.

Mucho thanko for your work+fix!
[Touch CDMA Android Development] hockeymike:
Google Goggles does not work on my vogue running Myn's Warm Eclair RLS1 at 320x480 with the nbh from 6/27/10. The standard camera works just fine, and barcode scanner works as well. Any ideas?
[Touch CDMA Android Development] thoughtlesskyle:
im not sure but i always thought it uses the camcorder API for google goggles to work
[Touch CDMA Android Development] deadpig:
Hmmm... I just can say that i just re-tried Google Goggles with a "Hansaplast" (Ouch... *g*) carton and it worked a second time :)

1st libcamera version did work for pictures but settings FC'ed and Google Goggles FC'ed.

2nd libcamera version didn't FC, but had broken images (wrong resolution thingy) on Kaiser devices

3rd libcamera (aka current RLS1) has working cam and not FC'ing settings and Google Goggles.

My setup:

Device: KAIS130

Display resolution: 240x320 with 104dpi

SD-card installation (Booting via HaRet)

Myn's Warm Eclair RLS1

Self-odex'ed

Actual git-kernel (selfcompiled) as of yesterday (2010-06-29)

libcamera RLS1 installed via androidupdate.tar

Greetings!

*oink*
[Touch CDMA Android Development] dlepage:
Distortion / Noise on preview screen when taking shots

Anyone else noticed that the noise issue with the CAM isn't random?

I am referring to the temporary still image in the preview area following a shot.

On my Vogue running VaniljEclair RLS6, the top part shows the current 'shot' but the bottom part is from the previous shot. It is systematic except for the first shot following a reboot in which case, the bottom part is random noise.
[Touch CDMA Android Development] l1q1d:
I confirm that on polaris with eclair and with froyo
[Touch CDMA Android Development] scooter66:
I have a Kaiser running latest Myn's Warm Eclair. Very glad to have to camera working! My problem is that all pictures are out of focus. Is autofocus working? How would I configure it? The camera app doesn't seem to have any menu.
[Touch CDMA Android Development] scooter66:
focus - never mind

I found out that the focus is manual using the jog dial.
[Touch CDMA Android Development] kallt_kaffe:
This may be a stupid question but how do I compile the library once I've done a git pull to get the source? I've only compiled the kernel and also done the full automated Froyo build. I suppose the Froyo building means I now have all the necessary stuff and I somehow should use the ndk to do this.
[Touch CDMA Android Development] dlepage:
Once you've done your Froyo build according to dzo instruction here, libcamera.so should be located under out/target/product/vogue/system/lib/ or something similar. I am not in front of my dev computer at the moment, so I can't check.

libcamera.so should be >200kb. If it is much less than that, it is probably the 'fake Camera' from the default/emulator build. If your build did indeed target our phones, your should also have libhtcgeneric-ril.so in the same directory.

I don't think you need ndk unless you want to develop a new applications that includes native (C,C++,asm, anything else than Java) code. For sure, you don't need to do anything special with ndk to build Android for any platform...
[Touch CDMA Android Development] mnjm9b:
any ideas as to what might need to be fixed for camera in eclair

to work with the new froyo zImage?
[Touch CDMA Android Development] kallt_kaffe:
But if I want to build just the lib and for a specific Android version? Like if I'd like to try to apply the 11Mb-extra-memory change to the Eclair version of the libcamera.so? I also may want to try stuff in libgps in the future and I very much like to try building a fake sensor lib that uses the GPS bearing to fake a compass sensor (some GPS apps assumes there is a compass available).
[Touch CDMA Android Development] kallt_kaffe:
Propalby just do the same changes as dzo did in the froyo branch and compile it for Eclair. Should be just a matter of copy'n'paste once you know how to compile it.
[Touch CDMA Android Development] dlepage:
After you've build at least once, you can modify some parts, like libcamera and then, make -j xxx again from the AOSP root directory. It will just rebuilt the parts affected by your changes.

As for switching between different Android release, I don't know yet. It looks possible with git (as is with most Revision Control System) to switch between branches/tags/releases/whatever but since Android is build from multiple git repositories, I don't know.

Myself, I just init / sync in a seperate directory using the other release manifest file.
[Touch CDMA Android Development] dlepage:
I am planning to do it. It's just that eastern north america is in a heat wave at the moment and I don't have Air Conditioning at home.

Sorry, but I don't feel like powering the computer and sitting in front of it when the temp. is ~33°C and sweat is pouring down my eyes...

Hopefully by the end of the week, things will be back to normal.
[Touch CDMA Android Development] kallt_kaffe:
Thanks, I suppose building for Froyo may be enough since I see no reason not run Froyo now. But maybe you could try dzo:s changes to the Froyo camera libs in Eclair that should make the current Froyo kernels compatible with Eclair and also enable 11Mb extra RAM for Eclair users aswell. Currently that's all I see needs to be done right now but I'd like to have a go at a "fake" compass sensor when/if I get time.

EDIT: Just noticed that you wrote that you planned to do it.
[Touch CDMA Android Development] mnjm9b:
Don't be sorry...

it is this kind of stuff that entices novices like me to try and learn how to fix it myself.

although for some reason I cant get the repo to work on my laptop (works on my slow desktop)

1@q1-laptop:~$ ~/bin/repo init -u git://androidhtc.git.sourceforge.net/gitroot/androidhtc/manifest -b froyo
Traceback (most recent call last):
File "/home/q1/bin/repo", line 595, in <module>
main(sys.argv[1:])
File "/home/q1/bin/repo", line 562, in main
_Init(args)
File "/home/q1/bin/repo", line 181, in _Init
_CheckGitVersion()
File "/home/q1/bin/repo", line 210, in _CheckGitVersion
proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
File "/usr/lib/python2.6/subprocess.py", line 633, in __init__
errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1139, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
[Touch CDMA Android Development] kallt_kaffe:
I used this guide to make sure I hade all that that I might need installed: http://xdaforums.com/showthread.php?t=704561
[Touch CDMA Android Development] mnjm9b:
Thanks for that...

I was using a guide that was for openeclair.

I was also missing sun-java5 in lucid repos.

this should get me going again.
[Touch CDMA Android Development] dlepage:
And if you try with this instead?

repo init -u git://androidhtc.git.sourceforge.net/gitroot/androidhtc/manifest.git -b froyo

I am not at my dev computer at the moment, so I can't check, sorry.
[Touch CDMA Android Development] dlepage:
Sorry, I didn't noticed you had it working on another computer.
[Touch CDMA Android Development] mnjm9b:
its pulling that right now.

I tried this at first and was running into the initial errors.

so I reverted back to my eclair instructions and that didn't help either.

the instructions in that link got me past the errors. (I was missing stuff)

and now I am running dzo's short commands.

my new question is...

I assume that I will need to still incorporate the htc stuff,

is there anything else I should be changing to it before I 'make'?

and do I need to 'make' first before I change camera?

edit: Crap...I just realized I need to be doing this for eclair's camera....
[Touch CDMA Android Development] mnjm9b:
OK I finally finished building. following dzo's instructions

the libcamera.so is only 30.5kb

so I assume that it is the 'fake camera'

how do I get the non-fake camera?

I do have the libhtcgeneric-ril.so in that directory also.
[Touch CDMA Android Development] dlepage:
Oh wait. I think one of the changes between Eclair and Froyo is that libjpeg is now a shared lib instead of static lib, or at least Dzo is linking libcamera.so with the shared lib version libjpeg. If this is the case, libcamera.so should a lot smaller under Froyo. You were building Froyo, right?

I think you should give it a try.
[Touch CDMA Android Development] mnjm9b:
ya, I built for froyo. but I was trying to fix the eclair camera problem with the new kernel.

in my excitement for getting my new laptop setup for compiling I pulled for froyo instead of eclair. ( I realized this about halfway through the pull)

so I built it anyway just to be sure it was all functioning well.

all worked fine.

however, now I am back to needing to build for eclair and I wont have time for that for a few days now...
[Touch CDMA Android Development] hussmanne:
Pardon my ignorance,

But what is this libcamera project trying to achieve? Doesn't the camera function in Donut/Eclair/Froyo now? Or is there something else?

Thank you.

Hussein
[Touch CDMA Android Development] mnjm9b:
the problem is more my own doing...

I am using froyo on NAND but copilot only works in eclair.

so I dual boot eclair in partition but...

eclair's camera is broke using new froyo nbh's

while this won't be a problem for eclair users using older eclair kernels

I think any future kernels will be a camera issue for anyone still using eclair.
[Touch CDMA Android Development] kallt_kaffe:
We will propably still be compiling kernels from Eclair for some time more but what's more important is that the changes would give Eclair users the benefit of the extra 11Mb RAM and a working camera. At the moment you can't have both.
[Touch CDMA Android Development] dlepage:
Now you can. See first post.
[Touch CDMA Android Development] kallt_kaffe:
Excellent. Well done.
[Touch CDMA Android Development] scooter1556:
Don't know if i'm doing something wrong but on my kaiser running the 07/07/10 build of Froyo with the latest DZO kernel and the last one K_K compiled, android doesn't load with rls2 of libcamera.so, the kernel gets stuck after detecting device type continually showing,

>android: power wakeup 0>0

and then an initialization failed message.

I noticed that the libcamera.so in the build i am using is only 80kb compared to the 200kb + of the libcamera.so in rls2.
[Touch CDMA Android Development] Prowess:
Same here for Bell Vogue.
[Touch CDMA Android Development] dlepage:
This libcamera is for Eclair, not Froyo. You can't swap libcamera libs between Android release.

RLS2 allows you to use the camera with an Eclair build under either an Eclair or Froyo kernel (zImage). But you can't use an Eclair libcamera under Froyo nor a Froyo libcamera under Eclair.
[Touch CDMA Android Development] preardon:
This should probably be made clearer in the first post.
[Touch CDMA Android Development] scooter1556:
Right i get it, makes sense now, it totally slipped my mind that you had compiled this for eclair! Are the other fixes in rls2 compiled for Froyo yet?
[Touch CDMA Android Development] dlepage:
This thread is called "libcamera Eclair"... But OK, I'll modified the first post.
[Touch CDMA Android Development] dlepage:
I don't think so.

I've push the changes to the camera git repository but Froyo is on a different branch now. Should be easy to pickup and apply to Froyo branch.

Anybody knows if there a "define" available to identify the Android platform when compiling? As far as I know, the only difference now regarding the camera between eclair and froyo is:

* A few includes that changed path

* static linking of libjpeg for eclair vs shared linking for froyo

At this point, I think it would be easier to deal with a single code base with a few #ifdef #else #end if than have two different branches.
[Touch CDMA Android Development] f_hugh:
I'm curious if this work can be applied to make video work, or is there some other magic and hand waving that would make the video workable?
[EVO 4G Q&A, Help & Troubleshooting] appzattak:
Hey all,

I have an Exchange 2003 server, and just need the EVO connected to it. I have all the setting correct but it constantly gives me an error stating my username and password are not correct. I know for a fact they are correct. So this evening I borrowed a friends HTC Incredible and went to setup the account just like I did and the EVO, and BAM! it worked, no problem or hesitation.

I have a customer also with an EVO, stock with the latest update that supposedly fixes an Exchange issue, but still no joy. There is defiantly something going on differently with the EVO when it sets up the account, I just have no clue as to what.

So has anyone successfully got their EVo synced with Exchange???

--Steve
[HD2 General] richawkeye184:
Hi guys

Need some help keep getting this message up on my screen and not sure what to do as I don't what to do a hard reset:mad:until a last thing. so was hoping for some help on what I need to do to clear it up:confused:

Have a pic so you can see what I mean.

thanks.
[XPERIA X10 General] BluechipJ:
Leaked: http://blog.se-nse.net/xperia-x10-2-1-update-leaked/
[XPERIA X10 General] Findee:
Those screenshots are really old.
[XPERIA X10 General] wrongfeifong:
yea what so special about 2.1 beside "animated" screen capable.... and nicer colour.
[XPERIA X10 General] mezo9090:
And more ram.....
[XPERIA X10 General] k1sr:
Right... So an OS can increase RAM now....??
[XPERIA X10 General] thedinks:
1.6 was limited in the amount ram it could use 2.1 let's you use all of it.
[XPERIA X10 General] ddewbofh:
I sound like a total a-hole when saying this but I couldn't possibly care less about 2.1, the big winner for me will be 2.2. Hear me out:

The amount of colours displayed isn't a major issue for me, even with 16-bit the X10 performs well enough. The increase in ram will be nice but again, the updated stock image performs very well even with a limited amount.

The reason I'm looking forward towards 2.2 is mostly the JIT improvements in Dalvik. Even if it's marketspeak to say that there's a 400% increase in speed there has to be atleast some truth to it. Even a 100% change (which is very doable) would be awesome, so it finally feels like I have a 1ghz Snapdragon. :)

The current speed is like running with lead shoes, it will get you there but that's about it. 2.2 replaces those shoes with running shoes.

Ok, retarded analogies, but you get the point.
[XPERIA X10 General] hiraj_panosian:
Don´t forget about flash man!
[XPERIA X10 General] bavelb:
OK, where are the instructions on how to update? Can we do the same update for the froyo?
[XPERIA X10 General] iead1:
How to update instructions:

1. Turn on your phone

2. Use it normally

3. Wait until September for SE to release the 2.1 update.

You can do exactly the same for Froyo! No need to thank me!
[XPERIA X10 General] Karooluss:
Where are cooked ROMs:-(
[XPERIA X10 General] im_iceman:
@iead1 - Man you're on a roll... that's funny!!..
[XPERIA X10 General] cue_32:
Ive had the pleasure of using both 2.1 and 2.2. Used 2.1 on Milestone/Droid and on a Nexus One. And of course, 2.2 on the same Nexus. I was amazed by how a simple 2.2 update can change a phone's usability.

Just to give you an idea:

At 2.1, the browser speed of the Nexus One was practically the same as my iPhone 3GS.

At 2.2, the Nexus One finished loading the page just as the iPhone was at it's halfway point.
[XPERIA X10 General] kishen80:
in two days.goin to get x10.hope i like it.. now using x1....
[XPERIA X10 General] tuxStyle:
Why is he a troll?

that's the pure truth.... for now at least.
[XPERIA X10 General] mtechfan:
No, not troll. He said "he was on a roll" which means, full of funny commentary in a good way. It's an English expression. :p

Reading must be very difficult for you eh? :rolleyes:

That's about the only excuse that would be forgivable for posting that question.
[EVO 4G General] dmoses1969:
What's the chances that Sprint's delaying Froyo and creating rumors of an update just to keep everyone hanging on until they are locked in?

Sent from HTC EVO using Tapatalk
[EVO 4G General] crpercodani:
Blasphemy.
[EVO 4G General] geekykid:
this thread is useless. Mods, please move this thread to general or delete it.
[EVO 4G General] 702DROID:
Why is this in the development section ???
[EVO 4G General] Krandor311:
Really? Froyo has been officially out for 1 day and you're gonna start complaining about the Evo not having it when every other Android phone on the planet that's not a Nexus One doesn't have an official Froyo yet either?
[EVO 4G General] Vandam500:
First the thread title is extremely deceiving... and second, like others have said, this is indeed in the wrong section.
[EVO 4G General] tjleeland:
My first post

I would like to use my very first post in this forum to say: You're an asshole. Learn how to punctuate your sentences. If you're asking a question, write it as a question.

What are the chances that you're too stupid to properly communicate?

100%
[EVO 4G General] jedil1c1ous:
I thought that the thread title was a factual statement with a link to an article within but instead it was a complete waste of my time. Please move or delete.
[EVO 4G General] Aridon:
Wrong forum and terrible title.
[EVO 4G General] beesneazy:
hah wooooow
[EVO 4G General] firemedic1343:
Terrible title, wrong thread....I'm a noob here, but I think this thread should be deleted.
[EVO 4G General] mrono:
I think it's possible but the backlash they would receive wouldn't be worth it.

also, silly OP
[EVO 4G General] psych2l:
Don't feed the trolls lol.
[EVO 4G General] davebu:
Sprint Rep over the phone told me 2.2 was coming on the 25th, idk if hes right or not though.
[EVO 4G General] dmoses1969:
It really amazes me how places like this end up with people like you. So, I forgot to put a ? at the end of the title so that you would know that it was a ? and not a statement or a link to a story.

Do you feel good after calling me an asshole? I hope so, people like you get your rocks off talking crap on forums like this. Big and Bad behind that little computer monitor of yours "aint" ya :eek:.

I am requesting to have the thread closed.
[EVO 4G General] boomer30:
Somebody needs to kick this guy in the ballz !!!
[EVO 4G General] gessin64:
thanks for wasting my time
[EVO 4G General] jabbawalkee:
Can you say, DOUCHEBAG!?
[EVO 4G General] dmoses1969:
I have never seen some many cry babies in my life......LMAO

Mods, Please remove the thread so all the cry babies can get back to spending time with momma. I have wasted too much of their time.
[EVO 4G General] beesneazy:
At least you tried ... ?

oh and LOL at requesting them to close it ... HAH
[EVO 4G General] a2k:
I don't believe this dumb @$$ question has two pages worth of comments!
[EVO 4G General] beesneazy:
Make it 3!
[EVO 4G General] Bukem75:
In before delete.

OP, please learn punctuation. Specifically, the question mark.
[EVO 4G General] steb0ne:
Thats exactly what I was thinking
[EVO 4G General] EtherealRemnant:
Sprint told me that Froyo is on schedule for the Evo by August 1st. They apparently already have internal documentation - she wouldn't give me the exact date but said that it is in the system and should be August 1st at the latest. This was a manager in advanced tech.
[EVO 4G General] booyakasha:
Douche Chillll....

EDIT:

In case (God forbid) you're not an Arrested Development fan, this could come off as me calling you a douche and telling you to chill. Tobias Funke's version is much better: :D

The Original Douche Chill (Youtube Link)
[EVO 4G General] BAleR:
Don't mess with my head man!:D
[EVO 4G General] 1wingangel:
Blah blah blah blah I'm an a hole wasted space wasted space jdjfjcdjebcicicicjdjdidickcixjxjcxjdjsjebaksockcbdkxxjsbskxcjdbdbhkgh

Hahahaha dodadoda

WHAT? Everyone else is doing it.:D
[EVO 4G General] 1wingangel:
THANK MOD.