Database Info

Complaining to the right People at T-mobile

Hi Everyone,
Ive been on a bit of a mission with T-mobile and have been in touch with the directors office, they are under the impression that nothing has been locked down on the phone in rc7/rc30 that would limit the use of the phone from a development standpoint.
Ive given them a few examples of things that cant be done but they refuse to do anything (other than cancel my contact if i want) as im only one person who is complaining.
I know everyone runnning rc30v1.2 and rc8v.12 is ok atm, but could EVERONE please send a little email of complaint. Just explaining that you are unhappy that they have locked down the phone and denied us root.
cl&[email protected]
They say that if they get more complaints then something will be done
ITS WORTH A SHOT ISNT IT?
PS... If anyone wants to cancel their contract in the uk because of the lack of access, call 01707 315000 and ask to talk to Leah within the Directors team about your G1 problem. I explained that i couldnt get my apps working because i couldnt edit/add files to system directories.
They should offer to cancel it, it worked for me

Yeah, it's worth a shot, although from past experience with T-Mobile this may be akin to trying to extract blood from a stone

I tried doing the same thing after I got my G1 (before anyone figured out the hole in RC29). I found the people over at T-Mobile USA are just as clueless. As soon as you mention the words Android or G1, they instantly transfer you to a different support queue. I tried to explain what root access was and they didn't have a clue what I was talking about.

I found that here in the UK also, these people work in the directors team and so far have not fobbed me off.
They dont claim to be technical but are at least talking to the T-mobile developers about this. They have raised my concerns with the UK G1 manager, i think my case just needs a little more oomph from others complaining.

I've already called HTC, G1 support, and the PDA/Smartphone support ppl. None of them were willing to even try to understand the issue.

T-mobile have just called me and have advised that we should expect a statement about the issue by the end of the week. The issue is now with board members apparently
Maybee they are actuclly starting to understand??

You should have them email. At least that way it leaves a paper trail.

SGTDavePwnage said:
T-mobile have just called me and have advised that we should expect a statement about the issue by the end of the week. The issue is now with board members apparently
Maybee they are actuclly starting to understand??
Click to expand...
Click to collapse
That's very interesting that T-Mobile is even considering the idea of allowing root access, to the point where it would be an executive decision by the board members. Do you have any other information on this aside from your first post? Can anyone else confirm this?

i phoned tmobile uk today and asked why i couldnt get root on my tc5-rc8.
and i had a long talk with the guy and he said he had a email about this issue
and went throught a few things with me on my phone. and then he said he would phone me back tomorrow with someone that new more about the g1 then the tec support staff. and he would be able to give me more answers about it.
qtronix

Cool
Sounds like my insessant *****ing at T-mobile support might have gotten us somewhere?
At least techies are not fobbing people off at the moment.
Could you please concider sending an email to the address i posted, just so they are aware that others are miffed.
******This is a copy of the email i sent to the directors team******
Leah
Many thanks for your call....
As t-mobile dont seem to see/understand the problem I have given the contact details of the director team to a group of developers so that you can hopefully get a few more calls about this. Please believe me that I am not the only person who has these concerns, but when people call tech support about this they are simply fobbed off by people who are not trained/do not understand the issue.
I would like to point out an error with t-mobiles response that they have in no way locked down the phone so that it is detremental for putting developed software onto the phone.
Please see a few examples of how the new RC8 Software limits Developers :-
1. Say I wanted my screen to automatically rotate without wanting to open the keyboard, this is simply a matter of editing offset: 1104724 within /system/framework/framework.odex to 0x0F001246.
I could do this on the old software but not on the new RC8
2. Say i wanted to update the web browser to do the same, this would mean editing the origional browser source code released by Google and putting it on my phone. Again, this was possible with root access on RC7 but has now been made impossible on the new RC8.
3. Say i wanted to make a tethering application that allows me to use my G1 as a modem to my PC (i know this would cost me money on my contract for data transfer) but I might want to do it so that i can connect to my workplace vpn to fix something. This was Doable on RC7, but now is not.
4. The G1 currently has no way of clearing cache for the marketplace, this again was doable on RC7 but not on RC8
5. The G1 has a limited ammount of space to install applications. It would be a good idea if we could install applications to our SD memory Cards, but again we cant do this because of the new software.
The above examples are just some simple things developers are working on that would benefit the phone, but we cant develop them and put them on the phone.
Basically anything that means editing a system file / writing a file to a system directory is now impossible.
Please understand that developers are not trying to take over the world or ruin the phone. We are simply trying to make the phone do what we want / improve the features.
This is how OpenSource works. Everyone has access to the Source code so that it can if neccecary be customised/edited to improve things for everyone.
The new software has made it impossible for programs that interact with the main system files or require extra files to be put in a system folder, to work.
Developers understand why the phone RC7 software was unsafe in the way it ran commands, we understand why you fixed the command running problem, but instead of fixing the issue properly you have just locked down root access?? Why??
If the new software in no way limits what developers can do, then why when you search on the net are so many people “Jailbreaking” their phones to get the access they require.
http://arstechnica.com/news.ars/post/20081105-android-liberation-t-mobile-g1-jailbroken.html
Can i draw your attention to
"In contrast, the G1 has been developed by the Open Handset Alliance project. It's extremely unlikely that this alliance, which is committed to an open platform, will engage in the same kinds of protective shenanigans that Apple has resorted to. The Android philosophy states that "anyone can contribute to Android and influence its direction. That means that anyone can download, build, and run the code needed to create a complete mobile device."
So why jailbreak an already-open device? One big jailbreak advantage is that it allows you to bypass the G1's internal storage. Until now, you were limited by the G1's built-in memory for installing and running programs. With the jailbreak, you can install applications onto a local SD card and run them from the card. Running low on memory? Just swap cards in and out.
Jailbreaking also allows you to use low-level tools that run in the background. Want your G1 to call home and report your location every 20 minutes? A simple Unix process, called a daemon, can handle that for you. You can set daemons up to remind you of appointments, to scan for nearby wireless devices and more. The world of handheld computing doesn't begin or end with graphic interfaces. There's an enormously rich world of possibilities available through command line processes.
Most importantly, jailbreaking gives you complete control of your system from the bottom up. It lets you stop thinking of your phone as a handheld gadget and start using it as a fully-capable Unix platform. "
Please could you explain how T-mobile are of the opinion that they have not limited developers with the above examples in mind.
The G1 is being sold as a Developer friendly OpenSource Phone. How can you claim this is developer friendly when the software severely limits what developers can do?
Are T-mobile saying that the phone was never supposed to allow users this access and that the RC7 root access was a mistake?
Eagerly Awaiting your response..
******

Well written, although I would have DEFINITELY left out the part about tethering the phone.

vr24 said:
Well written, although I would have DEFINITELY left out the part about tethering the phone.
Click to expand...
Click to collapse
I did think about that, but then i reconcidered as we already have tetherbot which works without root.
Suppose we will just have to see if anything comes of it

SGTDavePwnage said:
I did think about that, but then i reconcidered as we already have tetherbot which works without root.
Suppose we will just have to see if anything comes of it
Click to expand...
Click to collapse
you can always call t-mobile and say that after you updated the phone it is now:
constantly feezing, apps are running slow, and at times you can not connect to internet.
also tell them that you tried a factory reset and it did not help (make up a story that you have friend that has a lot of app and his phone runs faster than you phone with no apps installed)
if you have insurance they will send you one for free, you just have to return your old phone,
i believe they are still sending out rc29 for replacements as of now.
friend and cousin tried it and it worked.
might be worth a shot

Just got this in my inbox:
"Thank you for letting us know of your concerns with the 'open source' and 'root access' on your G1 mobile phone. We really do appreciate your comments about this.
We're aware that there are concerns in relation to this and our leadership teams in the UK and the USA are currently reviewing your comments and our position. We plan to provide you and other customers with similar concerns, with a response early next week, which should answer your concerns. I'll be in touch with you then.
Your comments are extremely valuable to us Mr * and I'm grateful for your patience while we look into this. I'd like to thank you personally for your co-operation.
In the mean time I hope you enjoy your weekend.
Kind regards
Leah Young
Directors' Office Co-ordinator
T-Mobile (UK)"
Of course, their answer could be anything from "f*ck off" to "yes, we'd love to embrace the openness of android with both arms, here everyone, have root!" so we'll all have to keep our fingers crossed 'til monday.

Well I just hope they release an update with options that allow us to turn off all background services (myfaves) and unwanted datatraffic (or actuall prevent overriding options when roaming).

How did that dead horse like the beating?

Perhaps a dead horse. Could it be that Tmo has now figured out that with root access, it won't take long for people like the coders at XDA to fully jailbreak the device to the point that voIP will be easy for any user to obtain? Are they just trying to protect their ability to profit off of voice traffic?

rynosaur said:
Perhaps a dead horse. Could it be that Tmo has now figured out that with root access, it won't take long for people like the coders at XDA to fully jailbreak the device to the point that voIP will be easy for any user to obtain? Are they just trying to protect their ability to profit off of voice traffic?
Click to expand...
Click to collapse
Hummm... I think ALL wireless providers are threatened by VOIP but the main reason root access was blocked was due to bad press mainly by tons of articles stating that there is a huge security risk and a flaw was found with Android which could let remote users attack someone's device...blah blah blah and so forth. That pretty much scared T-Mobile and Google which hated to have bad press so close to the G1 just being released and were forced to correct this issue. The only problem with that protection came with closing alot of freedom for the G1 and may happen to alot of more Android-based devices in the future, I'm afraid... Maybe Google will realize that there are other ways to protect mobile hijacking (which is extremely rare anyways) by creating some type of built-in firewall software instead?

rynosaur said:
Perhaps a dead horse. Could it be that Tmo has now figured out that with root access, it won't take long for people like the coders at XDA to fully jailbreak the device to the point that voIP will be easy for any user to obtain? Are they just trying to protect their ability to profit off of voice traffic?
Click to expand...
Click to collapse
Root is not necessary to build a voip app. Fact is, G1 launched with a skype-compatible voip app called iSkoot. Look it up.

SGTDavePwnage said:
Cool
Sounds like my insessant *****ing at T-mobile support might have gotten us somewhere?
At least techies are not fobbing people off at the moment.
Could you please concider sending an email to the address i posted, just so they are aware that others are miffed.
******This is a copy of the email i sent to the directors team******
Click to expand...
Click to collapse
i wont quote the entire email because its big. but you sir are very well spoken, great email!

Non-market .apk file database proposal

Hello everyone. I've a sort of proposal for the developers here, but before I get into that let me first briefly introduce myself:
I'm a communication designer for print, user interface, and illustration that completely advocates everything Android. I've been lurking the Dream development forums here for quite some time, trying to keep up-to-date with the latest ROMs, apps, etc., etc and I fully appreciate everything that goes on here and the endeavors that you devs put yourself through. Amazing stuff, really.
One thing I've noticed is that there are a slew of third-party / beta apps all over these boards, and other places on the internet as well. More often than not, I find myself scouring the cloud just to find a link for these non-market apps, and I usually get referred to them via some obscure site through another site. Despite getting the .apk file or ROM in the end, the process can get to be a bit tedious; especially for incoming users and those new to the Android platform.
My proposal is this: A website with a simple and clean user interface that has direct and succinct navigation with the purpose of consolidating and listing third-party / beta non-market applications into an easy access database. This website database would link these applications and have them be easily downloaded and installed via the Android browser, without having to mount the device.
I've actually come up with a fully-functional concept site, did the branding and everything for it, and also registered a short domain name for quick access while on your G1 or whatever Android device.
Navigate to: http://anda.pk to see what I had in mind, and how the overall layout/concept of the site would work.
I uploaded several .apk files I had backed up as examples for you to see how the database section would function. I also took into account the resolution of most Android phones and made the .apk application database section fit perfectly in the Android browser when in portrait mode right when you the load the site to ensure the best possible user experience when installing these third party apps. When you scroll to the right, you'll see info on what the site is about, and in the footer there are links to the FAQ, the about section, contact, etc.
I had also noted in the about link in the footer that the applications hosted on the download section are in no way accredited to the site, and that credit goes to their rightful developers. My being a communication designer has had the idea of peer collaboration engrained, and as such I give credit it where credit is due.
That said, I hope you guys here and the developers collaborate with me on on this site, possibly help contribute apks, and agree to them being hosted. If anything, I do hope you just embrace the concept, which originally was just going to be a reference for myself and my friends whom I've turned away from the iPhone, S60, and WinMo in favor of Android. I figured since I know the Android community is only going to get bigger, this website concept of mine could be a decent resource to have bookmarked.
Appreciate you reading this wall of text! Do hope to hear some feedback, so let me know what you guys think. Thanks!
Cheers.

I think this is a fabulous idea...automated version control would go over very well -- i.e. yum update
you should post up bits that you need help with and have folks contact you.
also..I love the logo!
question: do you propose a rating system or a review prior to listing type of approach or something new to keep this resource trustworthy?

Been following this on SA and twitter and it's a great idea.
Having the devs here on board would be a fantastic way to get something solid on the go. It's the kind of thing that can really help android become more hackable and useable for the average user...and it just make things easier for the rest of us.

Sounds good to me.
thelilliandivide said:
the applications hosted on the download section are in no way accredited to the site
Click to expand...
Click to collapse
Credit and accreditation are different things. To be accredited is to be given credentials or official approval. I think you meant "credited".

Sounds like a GREAT idea.
My opinion: The color scheme hurts. Love the logo.

i like the logo and the idea. I think the site should be more mobile friendly, or even better, an application for android that can work like the official market. I could help with that part if an application is going to be built.

camalot said:
i like the logo and the idea. I think the site should be more mobile friendly, or even better, an application for android that can work like the official market. I could help with that part if an application is going to be built.
Click to expand...
Click to collapse
i second that.. it should also have update checks if possible

I was going to complain that I didn't like your site layout, but in portrait mode you only see the left side which lists the apps. I like it.
One thing you might have to be leary of is dealing with apps that are considered warez unless your going to spend the time to verify every app that is uploaded or there has to a method in place.
As well there should be some kind of version control in place. You know what works on 1.1 and what works on 1.5. Obviously almost everybody within the next few weeks/months should be on 1.5, but will all the older apps run on 1.5 or does it really matter or does anybody care? The downloader will care.

CBowley said:
Sounds like a GREAT idea.
My opinion: The color scheme hurts. Love the logo.
Click to expand...
Click to collapse
Seconded. The text is much too light. A darker charcoal shade would be much better.
If the site gets an apk wrapper (a la FBook) version checking would be rather easy. Set up the directory tree something like this /downloads/WiFiTether/1.2.3.apk and just have the apk compare filenames. If the file names don't match, it needs to install the update.
EDIT: Now following your progress on twitter.

Some solid input. I'll play around with the color scheme and make some changes later this evening once I get back from class. And I actually do plan on making a mobile wrapper eventually, but as it stands as far as the concept layout goes, the site is best used when in portrait mode for easiest functionality. The rest of the site is to be considered supplemental. I do however, have a lot of things I eventually want to integrate; application tags, search, possibility of user uploaded apk files, etc. But for right now, I'm trying to keep the general site as simple as possible to make the workload on my end less stressful (graduating in 2 weeks).
bahnburner said:
If the site gets an apk wrapper (a la FBook) version checking would be rather easy. Set up the directory tree something like this /downloads/WiFiTether/1.2.3.apk and just have the apk compare filenames. If the file names don't match, it needs to install the update.
EDIT: Now following your progress on twitter.
Click to expand...
Click to collapse
Did not know how that version checker worked. Thanks. I'll re-work the apk directory scheme akin to that later tonight for when I do eventually get the wrapper up.

thelilliandivide said:
Did not know how that version checker worked. Thanks. I'll re-work the apk directory scheme akin to that later tonight for when I do eventually get the wrapper up.
Click to expand...
Click to collapse
That's not necessarily how most version checks work, but that's the simplest method I could think of, and probably one of the easiest to implement.

alapapa said:
I think this is a fabulous idea...automated version control would go over very well -- i.e. yum update
you should post up bits that you need help with and have folks contact you.
also..I love the logo!
question: do you propose a rating system or a review prior to listing type of approach or something new to keep this resource trustworthy?
Click to expand...
Click to collapse
Thanks! And I feel I might need some help in the future as far as implementing the features that I want to get working. But I'm not quite sure I understand your question. Are you referring to how I choose which applications get posted onto the site?

i'm a graphic designer and web designer, i'll throw in a helping hand if you want, pm me or whatever.
(think about an android based layout to bring it to the phone like Cough*cydia*cough

very cool and much needed
Xda-dev is great, but there is alot of stuff thats not on the market and they have shown to bow down to the tmobs pressure(ie: tether app) so another place to get apps would be great, and your weppage is beautiful and looks like it would be very finger friendly on the g1, but there is a basic model in linux of repositories(which is about what ur doing) and a simple app to d/l them maybe somebody could just make a market.apk with a modded addy, depending on how much is known about the market and its inner workings... it would be nice to do it as it has been always done....but as I stated above your webdesign is very nice and would work well in the native browser(im heading there now on my g1)
bhang

not a bad idea. I think this is great for all verified apps that are pulled from market...

I really like this idea. Go for it.
Just one (stupid) remark about the logo... it's like it has a big nose and a :-| expression... sorry

apetit said:
I really like this idea. Go for it.
Just one (stupid) remark about the logo... it's like it has a big nose and a :-| expression... sorry
Click to expand...
Click to collapse
Haha, I just noticed that actually. Now it's all I see. But yeah, I'm hoping to have a few more apps to upload by the end of next week. Revisions to the site are imminent once I get out of this last class.

I love the idea. One bookmark to check up on all the good non-market apps will be much easier than having several bookmarked threads.
Some applications may benefit from having tags such as [beta], [stable], [experimental], [contains-ads], etc.
As others have mentioned once/if user uploads are implemented an app approval system will be crucial to keep the spam at bay. I can see this really taking off.

im a supporter

zgmf-x322a said:
im a supporter
Click to expand...
Click to collapse
+1 this sounds like a great idea, there was something like this for apps for the dash,mda & sda.

New standard of xda-file uploading/downloading ~ READ

THIS WOULD BE A FREE SERVICE, OFFERED TO ALL XDA-MEMBERS
alright, while sitting in the xda IRC somebody complained about everyone using rapidsahre links, them dying, and the need for a new XDA posting service.
this coupled with the completely empty XDA ftp, we got to talking. Chainfire suggested using usenet for the roms/files/whatever. he said he attempted to get it more widely used years ago, but nobody really cared.
now, my thought is i setup a webUI frontend for the xda usenet group, and make it alot like the current xda-ftp stucture is. simple uploading, simple downloading. no real knowedlge of usenet needed to do it, and the files would be good for at least a year on the servers.
maybe even write a FTP frontend for the group.
what are your guy's thoughts on this. no download limits, no YOU HAVE TO WAIT 9HOURS TO DOWNLOAD ANOTHER ROM, no YOURE ALREADY DOWNLOADING A FILE LOLWAIT, no random deletions of files, uncensored content uploading(you can figure what that means), and super-fast downloading of ROMs, with a que.
we need your thoughts on this project.
edit:
usenet is a pay service, however the concept of this is to provide a free frontend for the usenet posts to the xda community. IT WILL BE FREE.
IT WILL BE FREE

I'm pdbogen, and I approve of this message.

/me is in favor and would love to help make this happen somehow.
posting in an epic thread

i believe this is a genius plan. I SHALL HELP MAKE IT HAPPEN!

I'm all for faster file transfers and less "LOL YOU BETTER WAIT BECAUSE YOU'RE A NOOB" messages.
Who would be supplying the servers? And how much would it cost to set up?

between me and turbzy, we have enough resources/servers to handle a good 3 mirrors of the setup, so we're good on the money/servers.
we just have to write the webinterface and get people to use it.

if you and the freenode crew whip up something good and badass, i will aggressively promote it on my heavily-trafficked websites
(bumping thread)

very nice idea indeed, just what xda was missing =]

This sounds awesome, I say go for it!

me and turbzy will start work on this as soon as we get a few uploaders/chefs willing to use the new system in place of rapidshare.
it's toomuch work to just write and then have wasted because nobody uses it.
the idea is, we're going to maybe write a built in FTP server. so as far as uploading is concerned to upload a file you'll
a) go to the site, and be presented with a upload form. just select the zip/rar and press upload. it'll upload to the multiple backend servers, and give you a direct link. OR possible upload it to a few other options, im thinking maybe add a rapidshare+mediafire+multiple FTP mirrors.
or b) connect to our custom FTP server and upload the file that way. after the file is completed, it will upload it to the other servers and give you the direct url. i'll make a more simplistic description later.
all in all, everyone i've talked ot about the idea thinks its genius. help us get people on board=

oh also, i'm thinking there may be a registration system needed for uploading. it's unfortunate we couldnt just sync it with the XDA login system, but it'll be needed to post verified files. it'd be better for file organization and whatnot.
then again, we may be able to sync with the XDA userdatabase if it gets big enough.

cerjam said:
oh also, i'm thinking there may be a registration system needed for uploading. it's unfortunate we couldnt just sync it with the XDA login system, but it'll be needed to post verified files. it'd be better for file organization and whatnot.
then again, we may be able to sync with the XDA userdatabase if it gets big enough.
Click to expand...
Click to collapse
I doubt Flar and company would let you touch the user database. However, maybe they could host the front-end on their servers? For example: fileshare.xda-developers.com
That would then interact with all your middleman servers, etc etc.
So the XDA server would just be the front-end, but it would redirect the file to your servers... is this possible?
Or even better, have XDA auth the user (via login to the forums) and then have it redirect to your server with some fun authing stuff. Then you guys don't need the database, but it would still be secure.

yaaaap. that was my idea, just attempt login. much simpler and lord knows precious xda administration wouldnt dare have their hands on a project meant to..actually maintain the files produced by the community!
they won't help us. even if they offered, i think running them seperate from this site is better and safer.

bump because i actually care about the project.

just a thought and i didnt see it covered
how will the virus scanning be implemnted. will you put a system in place at you end so its get scanned after uploadthen accepted or will you be asking the uploaders to scan them.
just a note because im pretty sure the current FTP scans files and lets you know whether the threaten. but if you leave it multiple uploaders then maybe well get ton of viruses littering the database

i am unsure as to how to handle that. thats why im thinking a user database would be useful, somehow mark the legit uploads with a key of some sort. i'll think about that, but im sure we can handle that.

from what ive seen clamav is pretty easy to tack on to whatever system youre using
edit: as for user database integration, all we'd need xda to do is toss a small api on their server that lets us verify accounts and return a userid that we can associate posts with. we wouldn't need actual access to the database

all im saying is yes you can verify the user who uploads the stuff
but we can verify the stuff
there was a problem a while back with ppl adding cracked apps to the ftp and viruses aswell

i don't think we care about cracked apps. thats somewhat the point.

cerjam said:
i don't think we care about cracked apps. thats somewhat the point.
Click to expand...
Click to collapse
well I think you should. This isn't a warez site, nor should it be affiliated to anything to do with it.
It sounds more to me like you're trying to set up a new warez service based on the good name of xda-devs!

Collabertive Effort Community Update Application

Hi all,
I have a concept for a single update application that would be driven from the AndroidSPIN release database so all developers could use it for ROM, Themes, Applications and anything releases to devices.
If you wouldn't mind taking a couple of minutes to read this post, I would greatly appreciate it.
http://www.androidspin.com/forum/viewtopic.php?f=260&t=226
I'd really love to get a group together to collaborate and either help design this and/or write an application and back end to do it.
Let me know what you think.
Thanks
Simon

Sounds like an awesome idea, I'd love to help any way I can, but I dont fit in any of the needed positions for the post. Looking forward to see what develops though

Fantastic idea!
I only ever use XDA so god knows what I'm missing out on elsewhere and to be honest after searching the word android on google and trawling through one crap site after another becomes tiresome so hence the 'XDA only' policy.
Sorry I can't offer any programming skills but you have my support on this project whole heartedly, not that it counts for much I know buh MeH!
Hope you can get this off the ground.

As I mentioned to Simon already, I was thinking about building an update application for my ROM. I love the idea of having an on-phone ROM database, update capability, something that can easily be used by any developer in the community.
Some initial thoughts on functionality:
- Browse ROMs
- Download ROMs to SD Card
- Monitor specific ROMs for updates
- Monitor currently running ROM for updates
I'm willing to lend a hand on the Android side of things, but this will be a large undertaking and we will also need some people to contribute to the UI, server side of things, etc.

I do iPhone UI design for applications now (I don't have an iPhone, but most of my contracts and clients are iPhone based), but let me know and I can whip up anything you guys need UI related.
Send me a PM and I can get the ball rolling on how the functionality can be laid out as well.

Even tho I know I wouldnt be able to help out with this. I know I would love to test this out if you needed it.
Its a great idea!!!

I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.

michinohatoresu said:
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
Click to expand...
Click to collapse
Well, we can reuse a lot of code from Cyanogen updater.

akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Well, of course.
If anything else needs doing, however, I volunteer what spare time I have.

akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Could be easily done, would require quite a lot of laborious work ripping out all the stuff you wouldn't need though.
I would take a look at this but unfortunately I have another Android project on at the moment which is taking all my development spare time.
@SimonNWalker What sort of backend having you got going? REST? SOAP?

Ups wrong theread

not that it matters (since i kept the source 100% open)....
you have my blessing to tear the cmupdater to shreds if it will give us a unified solution to all our ROM cravings
firefart has done a good job of keeping the code pretty clean so there shouldnt be too many issues with grabbing it
and the new code for the screenshots for themes could probably be used to the advantage of this project with ease

I'm not really interested in a rom updater, but a market replacement with an "upgrade all" feature (à la apt-get / yum) drawing from multiple repositories would be most exciting.

The Cyanogen updater could be used, it just needs some modifications. Stuff like sub-sections and update all
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.

willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
The only other method I would consider, besides JSON, is an advanced and well thought out web-based form that the developer is forced to complete upon uploading a ROM. This would place more burden on the server, but should be relatively easy to attach the provided ROM information to the rom database.
Think: Check boxes for firmware compatibilities, check boxes for device compatibilities, version number, change log, etc.

Maybe something a little like this?

Wow this would be/ is gonna be awsome!
I would suggest also that you can backup your sd card settings (and maybe also sms...) to an ftp server (or some other server you can install on your pc) from this app...
like (incremential) backup>partition>wipe>install update>boot>getbackupback
problem is to get the server adress back after wipe. maybe stored in web database and encrypted with phone imei number? or uploaded as google
whatever...
or just not wiping that single adress
just saying ^^

willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
JSON is just a file format. The CM Updater works via a static JSON file that gets updated manually. The way I'd design this (which is what I asked a couple of posts back) is a dynamic web service (probably REST based) which delivered JSON dynamically. Wouldn't be too difficult at all.
As SimonWalker said he's using PHP + MySQL I'm guessing that's already being done.
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.

senab said:
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
Click to expand...
Click to collapse
I know it is open and I don't need to give my blessing for people to use the source. I did so because a lot of people don't feel comfortable using other peoples code without permission, regardless of whether or not its 100% open source.
And as for the 'credit crap'... I don't see you asking for your name to be removed from the 'about' section of the app
I am not asking for any credit
Anyway, lets not get off topic...

Guys, before this becomes Android Open Alliance, the sequel (you all remember how that went), I think we better set up a way to work together first and then toss in the speculative stuff later.
How about starting simple; set up a wave?

Where to keep my data

Hi there guys,
Here's my story, I have this project I want to start working on, and it's suposed to be a running prototype in a month or so.
Anyway the app is going to be pretty simple, it is going to have users, that can be drivers, passengers or both, every user will have to have this info: name, surname, user ID, car which he/she is driving for now pictures are not neccesary(if you could point me in the general direction as to how I can do that, great), and users should be able to send(not instant) messages to each other.
I will also have a webpage in which you will be able to do all the things you can do with the app, so my question is
Where and how should i keep all of this data, all of the info?
I'm a real newbie in this, but I plan on learning a lot, so should I make a database and store all the textual info in there and link it with the app, or is there another way that you are supposed to do that. Where do I keep the pictures?
Any help would be wonderfull :3
Have a nice daaaay!

AzBahAJR said:
Hi there guys,
Here's my story, I have this project I want to start working on, and it's suposed to be a running prototype in a month or so.
Anyway the app is going to be pretty simple, it is going to have users, that can be drivers, passengers or both, every user will have to have this info: name, surname, user ID, car which he/she is driving for now pictures are not neccesary(if you could point me in the general direction as to how I can do that, great), and users should be able to send(not instant) messages to each other.
I will also have a webpage in which you will be able to do all the things you can do with the app, so my question is
Where and how should i keep all of this data, all of the info?
I'm a real newbie in this, but I plan on learning a lot, so should I make a database and store all the textual info in there and link it with the app, or is there another way that you are supposed to do that. Where do I keep the pictures?
Any help would be wonderfull :3
Have a nice daaaay!
Click to expand...
Click to collapse
You need a large server for this, and that has to grow larger by times as new members will start joining and this is going to cost you a tad..... A suggestion from me is that limit the size for each users content, like multimedia, let's say it's 1gb and one exceeded it and the older stuff got deleted