Database Users

Face Recognition Software for PPC

anyone thought of this ? with all the smart developers here I'm sure it';s very doable.
like the Lenovo laptops have the VeriSign sofware. something similar for our ppcs. it would be pretty cool. sorry if it was already discussed maybe.
if it was maybe you can point me in the right direction. thanks

android has a free program something wallet that uses the camera to look at your eye before unlocking. great program if you dont want anyone looking into ur phone

jaygriggs,
I've searched all about xda-developers for the program you mentioned.... do you know where I can find it? Thanks

pclight said:
jaygriggs,
I've searched all about xda-developers for the program you mentioned.... do you know where I can find it? Thanks
Click to expand...
Click to collapse
i'll bet if you get ahold of a g1 you'll find it
hey if your in luck GOOGLE may even have something on it.... not like they have lots of information cataloged, or that they at all had a hand in the android operating system.....

biowallet
ask and you shall receive
http://whyandroid.com/mobile-news/205-biowallet-secure-your-device.html

But biowalett is for G1 and android only, is there an alternative for windows mobile?

BioWallet isn't even available yet. From the web site:
Availability
Many of you have shown interest in BioWallet these months and have asked us about the availability of the product. We really appreciate it.
Some of you even have got a T-Mobile G1, the first public Android device and want to install BioWallet in it.
The bad news is we haven't been given the possibility to get one and we don't want to release a product that hasn't been thoroughly tested on real hardware. We think it wouldn't be neither professional nor fair for you.
The good news is we keep working hard to deliver a software that meets your highest quality expectations. We will try to get a device somehow in the next few weeks and then our intention is releasing a version through the Android Market and other distribution channels.
If you want to be in the loop just subscribe to the list of BioWallet News and we will keep you posted!
By the way, once we complete the initial tests we want to start a beta program to test BioWallet in as many Android platforms as possible. So if you have an Android device and want a free BioWallet copy to help us to test it, just subscribe to the list of Beta Testers and you could be selected!
* - We respect your privacy and we won't share your data with anybody.
Last Updated ( Wednesday, 29 October 2008 22:53 )

Revisiting Chameleon !

I know your wondering why didn't I put this in the original thread. I felt that that post had had it's run & this would be extremely valuable to a lot of people even folks who hadn't read the original. This is an extensive interview with the developer & gives a very insightful overview of the tablet industry. I would really appreciate all of your thoughts/views on it.
Thanks,
Bob W
http://untether.tv/2012/gabor-vida-teknision-chameleon/

w w w.kickstarter .com/projects/gaborvida/chameleon-a-better-home-screen-for-your-android-ta
^take out the spaces @ www and .com^
mmm I wonder what happened, just saw this checking the kickstarter:
Funding Canceled
Funding for this project was canceled by the project creator about 3 hours ago.

Either they sold it to someone else, or they went bust, or they realised they couldn't pull off their promises.

And it's none of the above
Sent from my Iconia A500 using Tapatalk 2

They had the member of their team in charge of the amazon payment account leave, so they have to re-open the kickstarter account under a new name, supposed to happen in a few days, below are the updates they gave supporters.
Hi Kickstarters,
What a strange week it has been. We went from a giant high to what might be a big low. Kickstarter is an amazing platform but a really difficult one for anyone outside of the United States. In order to set up a kickstarter account, you have to use Amazon Payments and in order to use Amazon Payments you have be an American citizen. Luckily for us, we had that covered. At least we did until today. As with any team, you can't expect all the members to stay part of the team forever. One team member's departure meant the departure of the Amazon Payment account. We are currently setting up another account and should have that done within a day and we are doing our best to contact Kickstarter to ask that we simply switch Amazon Payment accounts. As of the time of writing this post, I'm not sure if that will work. The worst case situation is that the project gets suspended. Suspended projects on Kickstarter are never renewed.
So, I am sending out this update in case the project gets suspended. If it does get suspended, please contact us at: http://www.teknision.com/chameleon-news. We are fully committed to launching Chameleon. Nothing will stop us from taking it to market. We still plan on honouring you, our backers, who have made this possible. I can only be honest in what is going on and promise to do our best to make everything good.
Keep the faith, fingers crossed and stay tuned.
Hi Everyone.
After speaking with the good folks at Kickstarter, we can now confirm that they will not be able to switch our Amazon payments account - it is simply not possible to 'swap' when you are dealing with credit card processing and authorizations. While it is disappointing, we understand these protocols are there for good reason. To protect your financial information.
Unfortunately this means we will have to manually 'close' this project, and your pledged amounts will not be charged. We are very sorry for this inconvenience -believe me, this is not the kind of customer experience we wanted to deliver.
There is some good news however. Kickstarter have told us we are allowed to initiate a new project and can accept your pledges there!
The only catch is that once we have the new project live, you will have to go and re-pledge on the new project (we will give you the new project link when it becomes available). We understand the inconvenience this may cause, which is why, for your time and patience, we will be upgrading all of the rewards with an additional 5 Chameleon backgrounds. We are aiming to have the new Kickstarter project live by early next week.
I hope you understand, and bear with us as we get over this hurdle. If you are disappointed with us, I understand that too. As I stated before, we have every intention of delivering world class software to our customers. We love the passion that Chameleon has sparked and we intend to develop long lasting relationships with our customers.
Stay tuned for new instructions next week, and thanks for your patience.
Hi everyone!
Today we are working on closing the current Chameleon project. While Kickstarter and Amazon payments have been very helpful and supportive, based on our discussions with them, the best solution is to start a new project. By closing the current project, there is no question about our intentions with your current pledges. You are also free to cancel your own pledge.
We are working to get the new Chameleon Kickstarter project up for next week, so stay tuned.
Even with this project being closed, we will still be able to share the link to the new Kickstarter project. Don't forget, your existing pledges will not be charged. Expect an update next week.
In the meantime, we have included a development update for everyone. With some surprises. So enjoy!

How do Canadians contribute?

Well, that sounds like a massively annoying situation to be in. For someone to leave that suddenly too, doesn't seems like it was amicable...
I hope they can sort out the problems without too many more difficulties.

Open source miui

If you follow any miui.us developer chances are you have over heard some talk of a open source Miui project.
You may ask yourself what does it matter if Miui is closed or open? A lot of the community is happy with stopping by their particular fansite each week, grabbing the new release and moving on.
Well from a developer stand point Miui being closed source has been a huge burden. There are very few developers outside of China have access to beta builds through out the week. Even with them it does nothing more then give us the opportunity to see what may be coming down the pipe on Friday.
We translate the officially supported devices and port these to unofficial devices. With no real communication as to what they have done code wise week to week. When bugs exist the experienced developers scramble to try to figure out a fix or band aid to get through to the next week. The truth is that it is not always easy and sometimes builds will suffer
FULL ARTICLE HERE
http://www.miui.us/content.php?272-OPEN-SOURCE-MIUI-PROJECT

YES

[Q] Some essential documentation badly needed

I read @Entropy512 write somewhere "we are more in need of developers than of testers at the moment"
To that effect I want to make an appeal to @maxwen @XpLoDWilD @Entropy512 @pulser_g2 and all other people who started the initiative to properly document out a few things
1. If a device maintainer wants to get his device added to omni ROM what should the steps be ?
2. To set up a omni ROM - compliant device tree what are the prerequisites. As in omniROM trees have been seen to be using a format of aosp.mk+custom.mk device makefiles where aosp.mk makes it AOSP-compliant and custom.mk is the omni additions. How custom.mk is to be made (a template maybe ?) should be be documented. In fact I would go out to say a device/custom/sample tree should be made as an example
3. Are there any guidelines as to how much the hardware side codes can be hacked with to make the devices supported ? (Many groups of developers have forks of hardware/qcom/* repos that are pretty liberally spread with #ifdef's and makes them break CTS/CDD in a huge way). How much will these hacks be supported ?
4. Obvious point, what are the fields in which you need help most badly as of now. That is to say ril/telephony experts are highly needed right now or are features the topmost priority or is the highest concern to make the hardware repos tip-top so that devices are completely stable
Also publishing some guides on how to get sources and build the ROM would be good too, but since you are looking for "Developers" right now, it can be assumed that they will figure that much out on their own at least

This documentation will be done.
Actually one of the key goals of omni is to properly document things.
Bear in mind exactly how early this is in the process - it was only yesterday we even made the links available for github...
Documentation will be a large part of going forward and it has been ongoing for a while. Currently that's the biggest task actually, much moreso than the actual development.
Developers don't only write code, they also write docs
To that effect, http://docs.omnirom.org is going to be the home

Among other things I want to do is a "patches for a given feature" document so it's easier to find out how a given feature (such as status bar brightness) was implemented.
I really want to do it before I have too many patches to put in there, but I also have tons of stuff to fix!

Entropy512 said:
Among other things I want to do is a "patches for a given feature" document so it's easier to find out how a given feature (such as status bar brightness) was implemented.
I really want to do it before I have too many patches to put in there, but I also have tons of stuff to fix!
Click to expand...
Click to collapse
What do you think about this idea? These common kernel patches could also fit into that document.

pulser_g2 said:
This documentation will be done.
Actually one of the key goals of omni is to properly document things.
Bear in mind exactly how early this is in the process - it was only yesterday we even made the links available for github...
Documentation will be a large part of going forward and it has been ongoing for a while. Currently that's the biggest task actually, much moreso than the actual development.
Developers don't only write code, they also write docs
To that effect, http://docs.omnirom.org is going to be the home
Click to expand...
Click to collapse
if I can be of any help let me know,
I would love to see this project start off right from the beginning with proper documentation about EVERYTHING
also +100 to @Entropy512 's idea. documenting each feature and how it has been added is really important
I strongly urge that submissions via gerrit should be enforced to have a well written description in the commit message too. (it is so much easier now with gerrit 2.7+ we can do it right inside our browser after the patch has been uploaded too)

championswimmer said:
if I can be of any help let me know,
I would love to see this project start off right from the beginning with proper documentation about EVERYTHING
also +100 to @Entropy512 's idea. documenting each feature and how it has been added is really important
I strongly urge that submissions via gerrit should be enforced to have a well written description in the commit message too. (it is so much easier now with gerrit 2.7+ we can do it right inside our browser after the patch has been uploaded too)
Click to expand...
Click to collapse
Yup. I've always tried to have a detailed commit message in anything I create, but I think we may need to start enforcing it so everyone does it.

Is there any kind of current features / bugs / patches list on the official build? Or even just a changelog?

orangekid said:
Is there any kind of current features / bugs / patches list on the official build? Or even just a changelog?
Click to expand...
Click to collapse
There are no official builds yet. Too early for that.
so much work to do.

Entropy512 said:
There are no official builds yet. Too early for that.
so much work to do.
Click to expand...
Click to collapse
Oh, I was under the impression there was a compiled "official" version for the N4, N7, etc...
No worries, in due time I'm sure. Be looking forward to the Nexus 5 build..

orangekid said:
No worries, in due time I'm sure. Be looking forward to the Nexus 5 build..
Click to expand...
Click to collapse
give us the device first

I follow Omni for the Nexus 5. Nightlies have started since Monday so I'd like to know if there's a general Omni changelog now or a specific one for each device.

I'm a developer without much ROM/Android development. I'd love to give a hand wherever possible, but like @championswimmer said, it's kind of overwhelming to jump in and help. I'm totally cool to be relegated to documenting things if that helps, but I also understand the interruption that it would cause for you guys to slow down long enough to explain what I need to know.
What I do have experience with:
Java
Jenkins
Minimal app development
Other crap that might or might not be helpful

-IMPORTANT UPDATE!- Petition to LEECO for source code release, now in change!

If developers have source code, they will make 100% functional roms. I try sending multiple times emails to LeEco asking for this, but the server always give me spam reply. Because of that I've created a thread in LeEco forum.
Please help doing a coment and voting in the poll.
This is the link to the thread: http://forum.le.com/in/index.php?threads/source-code-for-lemax2.14951/
Regards.
IMPORTANT UPDATE! Now we have a petition in change.org to do the max press possible to the brand. And the signs are for ALL the devices with Qualcomm processors.
Here it is!: https://www.change.org/p/leeco-letv...ents_action_panel_wrapper&utm_medium=copylink

great specs but the development is not so good. if they only release the sources.

Someone mentioned that they are releasing sources in September.

sanke1 said:
Someone mentioned that they are releasing sources in September.
Click to expand...
Click to collapse
Yup, in the official forum, but who knows if is true or a fake...?

I read that they are selling these phones at less than cost as a loss leader to sell people their content services. If so, I very much doubt they are interested in supporting the dev community as that makes it easier for people to get rid of their apps and services from the devices.

We need to achieve that fast!!

Did you get source code from Le? Why don't you share for us?

Anyone has updates about the source code questions?
I didn't find any update on the change.org site.
BTW' we need more votes!!

I sign!
More people need to sign!!
does anyone confirm source code release soon???

i signed.

Signed.

I got response but still no plan for releasing...
https://twitter.com/LeEcoGlobal/status/782992367280422913

I have not (yet) bought the phone b/c there will be no proper development in the absence of a source code release. I will probably go for the Axon 7 although I would like to have a bigger screen. (I will also not buy the Le Pro 3 although it is an interesting phone. Developer-unfriendly phone companies like LeEco are an absolute no-go for me. So sad ... )

Signed

Every tweet they post about their USA launch should get a comment about how their crappy source code policy is...

I doubt they will release the source code

Do not purchase le Max2. Most of the phones have finger print sensor issues.
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app

mikeysteele said:
Every tweet they post about their USA launch should get a comment about how their crappy source code policy is...
Click to expand...
Click to collapse
Yup, do it guys. I will put it in my petition, that people send tweets with that.

Do you have new news about letv's codes? Why didn't share with us about it?

Maybe the US launch change something I really like the phone my fingerprint has no issue except some times unresponsive but I only had it for a month LOL so fingers crossed
Maybe they'll release the source code and the worth of this phone will double