yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] irrenhaus:
There is the open street maps project. For a maps alternative could that be used.

Well, since we are going to build a lot on our self and since the whole thing here shouldn't be a quickshot I think that we should not fear writing the applications we need. Creating own applications and making it open sourced is more the thing I would like to see than a mod which just replaces the google things with other thing that aren't really under our control.

That is a point which needs thinking about imho. If we would write our own apps... Well imagine a sync thing which can sync with as many sources as possible. In fact my next project will be a thing which is a lot like the motoblur interface (I thought about it without knowing motoblur so its a little frustration that they are doing it :) ). The plan was to implement plugin ability so simply any social network could be used. Something of this kind for syncing would be great. I now have all my contacts on google so why should I change it? Really not just because they overreacted and claimed on their rights. But opening it in that way that it isn't a must use thing to sync the contacts with google I think we eventually could get more users :)

So a combination of both would be the best imho.

How about just writing service providers for syncing with different things and letting the user choose the one he desires?

Ah, for real, I would like to see a community made, open sourced system which is not just some kind of patchwork which consists of some "random apps". We would also have the great advantage of apps which can work together rather don't knowing each other.

:)
[G1 Android Development] amlwaycooljr:
So your idea for contact syncing would involve an api or sorts that would allow other people to create ways of syncing various communities and social sites? Meaning people could make extensions that tie in with the common contact backbone?

I agree I'd love to see this become a very well developed community made open sourced phone OS. That would involve alot of teamwork and/or a common method for apps to talk to each other but it can be done.

Edit:

I forgot to mention that Cyanogen mentions that he will release a "bare bones" ROM that includes only open source material. We might be able to use that as the cornerstone and build upon it.
[G1 Android Development] irrenhaus:
I only think that's the perfect way ^^ If it can be done and if it makes sense to do it - we will see.

It will take a lot work for shure. But look at this community. When this can't be done by this community then I don't know who can do it.

For shure it will take a lot of time. But you know - one thing I learned by using open source is to be patient and frugal ;)

As I said this needs a lot of discussion imho.
[G1 Android Development] jubeh:
The setup-wizard is not that complicated, I was going to make one for my AOSP build, but my java being so lacking, I didn't really try hard. All you basically do is change ro.configs. The APNs are handled by the Network Provider, which is part of AOSP, so that's not a problem. The issue I came across was how to launch the setup process. I'll look inside the code for the SDKSetup and see if I can whip a simple setup wizard
[G1 Android Development] Metal_Hurlant:
This is the right approach.

Absolutely everything here must be open-source.

It's the only way to be secure the future of community-based Android firmwares

So be careful when you suggest Market app X or IM client Y as replacements for Google apps. Are they truly open-source? If not, they are a stop-gap at best, with no real guarantee that this situation won't happen again in the future.

In my humble opinion, this is a blessing. Keeping closed-source apps around made us lazy and complacent. "Oh, those apps have been taken off the market? Oh well, I suppose we have to live with that."

And yes, one obvious side effect is that those open-source apps will have a much lighter dependency on google. This is not to spite anyone, but simply to give users more freedom, which is what this is all about.

So, this is pretty exciting.

PS: We need a place for projects to get defined, twiki pages to be written and code to be stored. google code or github come to mind. no preference here.
[G1 Android Development] :
Now what do we do...

I know this thread is for OAA but just wanted to ask a quick question.

Since Google Has decided No More ROMS, at least the None Hero ones, what do we do, I have the 4.11.1 installed on my phone, do i uninstall?? Basically what can we while the devs materialize their ideas. I hope i'm not being an annoyance, by asking this question here, I didn't want to just start a whole thread all over again?
[G1 Android Development] roadrunnerx7:
not sure if this is correct, so correct me if im wrong...

lets think outside the box. we could all technically make our own roms. the phone and the stuff the phone came with is ours because we bought it. however we cant distribute it. so, technically cyanogen could continue to make his roms, just not distribute them. he can do it because he bought the phone and google decided to put the apps in with the phone so the apps are his also. paid for. with the phone. so now the problem is cyanogen continues developing just isnt distributing.

how do we fix this? probably more than 1 way but ehres what im thinking.

he makes the biggest tutorial ever on how to make what he makes. that way were making it ourselves and nobody is distributing.

two, he just gives them out to "friends" on messengers or something.. or even by hand, then they just keep giving it to there "friends". its distributing, but noone can prove where it came from lol

3. he makes his roms without the google apps, puts up a tutorial on how to put them back in ourselves, and boom, we're back to normal.

remember the biggest problem is cyanogen does all the work, if we can solve that by us doing more of the work, we can continue the way we were. only thing i see is a lot less people will have the newest stuff because they cant figure out the tuts he would write.

of course this is all based on IF we can legally keep making roms for ourselves(except choice number two, thats just sharing, and spreading, without uploading lol. not sure if thats still illegal though)
[G1 Android Development] testing567:
Some may disagree with me, but I personally think that the market replacement must be closed source for it to succeed, especially if it plains on having paid apps in it's market place. I wouldn't trust entering my credit card information when someone could have altered the source to steal my info. Also, there would be a much higher risk that someone would just tweak the app so they could download all the apps for free. That could cause developers to turn away.

I think the key is to use a closed source market app with a free distribution license.
[G1 Android Development] bbutlerau:
Ok i might have found a way i can contribute hehe. I think as we are essentially replacing all the closed source google apps. The replacements should feel like they are all part of the package rather than a disjointed collection. I would love to help out with this process making icons and gui elements. This approach should probably be applied to the open source google apps such as the browser and calendar to make them fit. Regarding the existing apps on the market which could be used as replacements are any open source? If so we could always give due credit and then customise them to fit ino XDADroid (like the name?). I would love to begin app development for this project despite my limited experiance. Can anyone reccomend a good begginers guide to android development?
[G1 Android Development] amlwaycooljr:
I agree we cannot allow people to alter the market replacement all willy nilly. but the question remains who would you trust to develop it?? Who would you trust to maintain and update it??

Edit:

oh and i do agree with Metal_Hurlant we really need to make a wiki or twiki or something to throw ideas up at and once we pick a decent ROM to start with a good git server to host it on.
[G1 Android Development] BoxyD:
I looked but couldn't find this posted on this thread but if it is then pardon the double post.

This is what

Cyanogen

said on Twitter.

"I do plan to release a "bare bones" version of CM as 4.2, and the source code will remain available."

This should take care of the item about somebody posting a ROM w/o any of Google's stuff on it.
[G1 Android Development] irrenhaus:
Imho thats the point where os comes in. I for myself would trust an open source app (if there is a community of developers around) more than an app where I cant look at the code.

That is because when any developer writes crap - the others can see it immediately. And to make shure that the apk you get is the one you should get - md5 sums do this work. Thats why on all big os projects the md5 sums are distributed next to the file.

And that way everbody can compile it by hand and then check the md5 sum.

This procedure I would trust the most.

Beside that, if you plan to develop a market with paid apps, then you have to get the app developers to use your market. You would have to create a system that the app developers get the money. They have to trust you. And so on.

With this in mind I think the market is something where we should look for existent things. Or create one which is os and has no paid apps.
[G1 Android Development] :
All i can say is. Hell Yeah! real OSS can own google. but im drunk. i might take this back in the morning. but im a stupid anarchist. id risk my life for the rush of sticking it to a corporation.
[G1 Android Development] amlwaycooljr:
This makes alot of sense, I've never been one to trust a single person. That's just to much power for one person.

As for having/not having paid apps I'm still undecided on this. Having the option for paid apps would certainly entice more developers than an entirely free market but it would need alot of thought and work to develop a fully functioning market capable of paid apps.
[G1 Android Development] Metal_Hurlant:
I must strenuously disagree with the misconception that an application is more secure because nobody can see its source code.

Take Firefox for example. Fully open-sourced. Many people trust it to do their online banking with it. Arguably many technical-minded people trust it more than popular closed-source alternatives.

Effectively, you are trusting whoever gives you the market app. If you were previously getting that app within a ROM distributed by Cyanogen, then you were explicitely trusting Cyanogen with your credit card when you typed it in the market app.

It is better for such an app to be open-sourced so that anybody can verify what it is really doing, rebuild it, compare the binary they obtain with some distribution's compiled binary, etc. (think of HTC_IME logging every keystroke for example. Being able to audit the source makes this kind of things and many other much easier to catch and fix.)

Ultimately, you put your trust in whoever packages and distributes that app, whether it is an open-source or a closed-source app.

It's just infinitely easier to verify that trust with an open-source app.
[G1 Android Development] irrenhaus:
It is possible. But I think we should first have a working market. Then we can add support for more.

If you think it can be handled and if you have ideas say it ^^ We still have to think about everything. Nothing here is decided.

Also jbqueru just had the idea: Let the closed apps on the phone. Don't overwrite it. That could work since then is nothing distributed thats not os.

We'll see :)
[G1 Android Development] enderx1:
Hi all, I'm a very beginning developer for android, but I learn quickly if someone can give me advise every now and then. For this project to really get off the ground though, I really think we need an outside website to manage the development. This needs to be done first.
[G1 Android Development] Evervoid:
I agree, how about we use a google site/blog just to rub it in ;).

All joking aside though, this project will need more organization than a single thread on XDA. Is there anyone that can help with this? I would be more than happy to participate in any way.
[G1 Android Development] zambezy:
Here is alternative to the market and I believe its not restricted...

http://twitter.com/slideme

Nice market I have been using it occasionaly.

There is one more market but I dont remember what it was..
[G1 Android Development] doooshty:
I think this is very exciting. We have a chance to great what I had hoped Android would be from the begining. I have time and money(more time than money, lol) that I can donate. I have no development skills or experience, but I will do anything needed.

Anyone interested in assisting in the starting of an OpenAndroid Website, please contact me. I want to make this a serious project to aide in the creation of a completely open source version or android. I also want it to be a place to continue it's evolution. I am looking for someone with experience in OSS to offer suggestions on the best way about this. As well as creation and design of the site

If interested hit me up on here or gmail

doooshty(at)gmail.com
[G1 Android Development] ttabbal:
OK. Now we're getting somewhere. Google sites would be a quick and dirty way to get a project page up, and Google Code is pretty nice for subversion and such. We need to get organized and get some groundwork done here. I'll start putting something together for that if nobody else minds. I also have a web hosting account I can use.

I'm currently downloading the 1.6 SDK and I'll sync Cyanogen's Git repo when I'm done with that and make sure I can build it.

To avoid duplication of effort, I propose we ask for volunteers to handle various projects as leader and anyone can contribute. That way we don't have just one person trying to run the whole show.

Please, let's not get into Google bashing. They are protecting their copyright, as much as we might not agree with how they are doing it. This project is about producing a full open source Android distribution. The idea is to allow anyone and everyone to build fully functional ROMs without infringing on anyone's copyrights. That is the only goal here, we are not out to "stick it to Google" or cause them any issues. No need to be negative, let's just do what Open Source does best, crank out some killer apps. :D
[G1 Android Development] miro.san:
It seems to me that the priority dictates everything here. If time is the most important factor, then the focus should be on getting a build out that can run without any of the closed source pieces in it. I would think that would include setup and some type of sync, that's it.

Even if the initial substitute applications weren't completely open source, they would hold over most users, and give devs the time needed to do their job right.

On the maps side, I've been looking into making an Android app and someone else mentioned it already, there's the openstreetmap project. Someone has already written a navigation system for iPhone with it (roadee):

http://wiki.openstreetmap.org/wiki/API_v0.6

There's also cloudmade, complete with an Android SDK:

http://www.cloudmade.com/

I'm actually a .Net developer, but I would seriously consider pitching in to this effort to make an open Android build, I think it's an important project. Most of my background is web apps and web services, but I'm sure I could pick this up pretty quickly and be of some help.
[G1 Android Development] doooshty:
AGAIN this is not "stick it to google"

Sure, google opened people's eyes to just how closed android is, the community will fix that.

Google has no issue with us removing there parts, atleast they claim not to. Part of me think that they don't have a problem with it because it's not worth another companies time to do it. That is where he come in. It's worth our time.

I would love to see a future with various distro's of android, all OSS.

This could be a game changer...imagine "bare bones" smartphones sold unsubsidised and you can install your favorite distro.

Would it ever get there? Maybe, but the greater question is, would this be a step in the right direction? I believe so.

This isn't anti-google, it's pro-android
[G1 Android Development] IOmega666:
got no money, got no power of development . but here i am saying this is pretty cool, this kinda things were the ones i expected when i realize Android was my mobile device OS, and keep it up guys, hope this can be a rly great project .

good luck !!
[G1 Android Development] hotweiss:
I will gladly partake in this project, and incorporate it into the HoFo ROM.
[G1 Q&A, Help & Troubleshooting] flexnix:
Here's my issue. My keyboard a week ago started to have issue, some of the letters wouldn't work (the physical one). T-mobile will be sending me a warranty replacement. So I need to get unrooted.

I was going to use this method --> http://xdaforums.com/showthread.php?t=491350

Problem is the splash screen is the one for CM 4.0.4 ROM. So I can't type in the recovery console (CM 1.4). I need to get rid of that splash screen.

So some XDA'er's gave me an idea. My girlfriend has an unrooted G1. I loaded Flash Recovery (one-click root method). I did a backup of her perfectly stock 1.5 image. I took out the SD card, dropped it in mine. Loaded into CM 1.4 recovery, went to "restore latest backup" and I got a "Error performing restore! Try running nandroid-mobile.sh restore from console.". I'm stumped cause I can't use recovery console since some of my keyboard keys don't work. Can I flash thru Better Terminal flash_image to go back to unrooted stock 1.5, stock recovery and stock splash image? What's the exact command? What do you think I should do guys?

Thanks in advance.
[G1 Q&A, Help & Troubleshooting] Fingerlickin:
flash the 1.22 radio

flash DangerSPL

BRICKED!!!!!!! No evidence

HAHAHAHAHA damn that's evil
[G1 Q&A, Help & Troubleshooting] david1171:
if you have a second splash screen (splash2) then do this in fastboot

fastboot erase splash2

flashing the DREAIMG.nbh file will change everything else back to stock
[G1 Q&A, Help & Troubleshooting] david1171:
if you are referencing me in any way, what effort? to type a few sentences :p
[G1 Q&A, Help & Troubleshooting] flexnix:
EDIT: I just got ADB to work. Woohoo. Only @ work it works, lol.

I need to get rid of this splash.

So last night after I posted this, I looked at the recovery-backup.img that flashrec made. I thought to myself "damn that's a small 5MB file for the 1.5 OS". I went into Better Terminal and flash_image the image. Rebooted the phone into recovery mode and only that changed. I figured it was too good to be true from just a 5MB img file.

I'm installing adb at work now to see if I can get this damn thing to work.
[G1 Q&A, Help & Troubleshooting] flexnix:
I was wondering if I flash some early 1.5 rom (Haykuro ADP 1.5Hr3) would it bring back the old splash screen and then I can just reverse to stock via the unrooting steps?
[G1 Q&A, Help & Troubleshooting] flexnix:
typed:

fastboot erase splash2

and it says: "erasing 'splash2'....FAILED (remote: partition is not existed!)"

Maybe I should format my SD card and remove all the partitions? I don't think he has to do with that, but I don't know what else it could be.
[G1 Q&A, Help & Troubleshooting] supremeteam256:
You have the new spl which removes the splash2. With the new spl you only have splash1.
[G1 Q&A, Help & Troubleshooting] flexnix:
So what do I do then? fastboot erase splash1?

Because I did that (splash1) and it says "erasing 'splash1' ... FAILED (remote: erasing error)"

I hope this has nothing to do with me switching back to the stock recovery using girlfriend image (flash_image) thru terminal. Should I go back to CM 1.4? Even though I'm in the bootloader?
[G1 Q&A, Help & Troubleshooting] supremeteam256:
Get the original T-mobile splash screen pic. It's on here a couple places and instead of deleting it just flash the original over your custom. And yes it will be splash1.
[G1 Q&A, Help & Troubleshooting] flexnix:
Now I'm confused. When I first boot up the phone, the T-Mobile screen comes up. Then a few seconds later it use to show the regular animated ANDROID logo when cupcake came out. But since I installed CM 4.0.4 it shows the other CM's ANDROID animated logo after the T-Mobile logo.
[G1 Q&A, Help & Troubleshooting] david1171:
What part of "flashing the DREAIMG.nbh will overwrite everything" did you not understand. To unroot your phone ALL you do is flash that file. stop making this so much more difficult. after you flash rc-29, wait for your phone to update.
[G1 Q&A, Help & Troubleshooting] supremeteam256:
Well what you wrote is confusing everyone else you should have stated that in the begining. The animated screen is not a splash screen. Splash1 and splash2 is what would appear before the animated gif. And just like david said flash RC29 and your done.
[Touch Pro2, Tilt 2 Themes and Apps] samarrai:
I used this application

http://www.freewarepocketpc.net/ppc-download-sms-delivery-receipt-fix-v2-0-0.html

to fix the delivery report bug which display the # instead of the name of the receipient

it was recommended in the thread ( Software worth installing on the TP2 )

SMSDR: Displays the contact name on each miscalled SMS that your receive. Soft reset after install. (freeware)

the problem is that it some time fails, and give no soft key tap saying delete, and so the notification remain in the task bar

and i cant remove that notification even by deleteing the notification from the inbox

the only way is a soft reset :(

is this casue its originaly was for Win 5 ?

either way

what is the solution now ?

is there another way to fix the delivery report bug using this application or any other way ? :confused:
[Touch Pro2, Tilt 2 Windows Mobile General] vilmos1:
I have the tmobile TP2 for two days and I have two major issues.

1. I can't scroll smoothly for the life of me. Flicking in the all people menu goes way far and slow scrolling seems impossible without turning into a tap. Same thing in the slide bar and pretty much any situation that involves gestures.The touch screen response seems exagerated/extremely sensitive for most of the time and other times lags or requires several taps. I calibrated the screen but don't see much improvement. Does anybody else have the same problem / is it the hardware or just a matter of learning curve on a very "touchy" screen?

Is there a way to adjust the scrolling speed and the screen sensitivity?

2. going online is extremely frustrating. most links in webpages don't work in either IE or Opera, not to mention excruciatingly slow load (I bounce between edge & 3g) and several attempts to open a website (screen turns white and freezes)

Is there a way to obtain a half decent web browsing experience without being tech savvy?

I really want to like this phone but it's becoming too frustrating/time consuming to accomplish some of these presumably simple tasks like the ones mentioned above.

thanks in advance for your response
[Touch Pro2, Tilt 2 Windows Mobile General] ohyeahar:
1. You're probably just used to using a capacitive touch screen like on the iPhone. When flick-scrolling on a resistive screen, you have to apply pressure. Don't apply so much that you are pushing down on the screen, but you shouldn't be brushing the screen with your fingers. That is probably what's causing the accidental taps you experience.

2. Don't know about anyone else, but here are my own tips to make my browsing experience extremely satisfying.

-disable java script and plugins. Most sites don't need them to work and this makes your pages load faster. Only turn them on when you absolutely need them.

-use your fingernails to hit links. Hit them once firmly and trust that the browser picked it up (it often does). Zoom in to small links to hit those.

-don't use IE

What sites don't work for you?