Develop Bugs

[DEV] [ROM][2.2] Froyo - XDA Community

This is a temp. post till we get things sorted out and post the primary info about dev efforts.
If you're interested in helping out, msg nprussel or me.
1: As I mentioned in a previous thread, we gotta sort libhardware_legacy related bangs.
The base build is a hybrid of SDK, Nexus, Hero, Eris and Sprint.
Talk about a cocktail...
Not all of the latest Sprint drivers were compatible with the Hero, hence the mixture.
2: Devs with good experience will get contributor/commit access to the git branch.
3: Use pastebin for logcat and/or other logs/configs etc.
4: Use this url for bug tracking
- PLEASE keep this thread clean, with discussion pertaining ONLY to development/bugs/issues/ideas/successes.
- Flag the above (your remarks) as [MAJOR], [ENHANCEMENT], [CRITICAL], etc.
- We know you appreciate our work and would like to thank us, so no need to write a post about it.
- If you really want to thank us, each of the devs involved will be listed in one of the first posts, and you can PM him/her or donate.
Here's the git tree.
In order to avoid unnecessary questions, and cluttering the thread with useless posts, please read the README.
This will be updated later today or in the days to come, as patches make their way in.

/* .reserved */

/* .reserved_2 */

/* .reserved_3 */

Reserved ///

adwinp said:
nprussel's post kindda moved me.
This is a temp. post till we get things sorted out.
If you're interested in helping out, msg nprussel or me.
Click to expand...
Click to collapse
I dunno if you have FTP space for releases, but we have about 10 servers over at VillainROM that we can use for hosting a community release. Not sure if I've shown nathan how to use them all yet.

I initially proposed private git repos for binary rls hosting, but FTP might work well in the beginning phases.
Although git is immensely easier for commits.
If you have admin access, would you mind setting up git?
Anyway, we've already PMed each other, Nathan and I.
What I propose is thus:
We have to start with a unique codebase.
Upload one of our ports (I can up mine already), with a change description, create a git branch, and then start with the devving.

I've just PM'd you, however, something that I would like to add as well, is that I can also host a git server for you on my personal server (which is internationally hosted and very fast). Honestly, I am not using it to it's full potential at all, so I would rather put it to a good use like this.
Let me know,
Mr P.

Don't forget to set up a paypal donate site for this proyect, would love to provide you the beer needed to cool your brains
Which devs are already on this boat?

nesukun said:
Don't forget to set up a paypal donate site for this proyect, would love to provide you the beer needed to cool your brains
Click to expand...
Click to collapse
same here, as i am a noob regarding developing this would be the only way to support you a bit.

Just hope the devs can all work together and we dont want to end up with loads of roms like we have for 2.1
-------------------------------------
Sent via the XDA Tapatalk App

adwin / nathan: I'm a linux + C coding guru (Working with embedded devices at my job) but Android is still pretty new. I'm getting more and more interested since the 2.6.29-project has started to matter .
I'm more than willing to get my hands dirty, I just don't know how. Since porting from device A to device B probably means a lot of android-internals I don't think I'm much use.
But if you guys think I can help with something or speed things up (from scripting to writing commandline stuff, might even dive into writing Android apps if it's needed) don't hesitate to drop a note somewhere.

adwinp said:
I initially proposed private git repos for binary rls hosting, but FTP might work well in the beginning phases.
Although git is immensely easier for commits.
If you have admin access, would you mind setting up git?
Anyway, we've already PMed each other, Nathan and I.
What I propose is thus:
We have to start with a unique codebase.
Upload one of our ports (I can up mine already), with a change description, create a git branch, and then start with the devving.
Click to expand...
Click to collapse
Yeah. Git is good for the stuff using source code, and a good idea for commits etc.
If you are wanting worldwide mirrors for ROMs (I can't see end users wanting to download from git ), I can give you access to the mirroring software on VillainROM. To do that, I think you need a forum account, as all the security checks are carried out using forum logins. Not sure though...
It will mirror to UK, USA (several over there), Asia, Europe, Israel and Scandanavia. Might be more I've forgotten about.

i will provide beer also...

Good News
any more informations?

It would be great if all the Hero custom ROM developers would join their forces together and build one excellent Android 2.2 rom

stephenophof said:
It would be great if all the Hero custom ROM developers would join their forces together and build one excellent Android 2.2 rom
Click to expand...
Click to collapse
Same thing in my mind. Keep up developers it would be cool

adwinp said:
nprussel's post kindda moved me.
This is a temp. post till we get things sorted out.
If you're interested in helping out, msg nprussel or me.
Click to expand...
Click to collapse
which post?

It's great to see that at least some people here have the community spirit!
I really hope this ROM will be the best there ever was, because of the combined effort. We can show the world that this community can produce great things!
All the devs on this project have my support!

Full froyo boot logcat

Recompiling Dolfin and making changes.

The Dolpfin browser's source is available at http://opensource.samsung.com/reception/reception_main.do?method=reception_list&menu_item=mobile
Would it be possible to modify the source to include say, full screen browsing, updated webkit components and so on?

check this thread- http://forum.xda-developers.com/showthread.php?t=967180
adfree is trying to replace XXJL2's dolfin browser with that of XXJID. it might be useful to you.

sabianadmin said:
The Dolpfin browser's source is available at http://opensource.samsung.com/reception/reception_main.do?method=reception_list&menu_item=mobile
Would it be possible to modify the source to include say, full screen browsing, updated webkit components and so on?
Click to expand...
Click to collapse
Modify sources and recompile? Sure.
Load it on the Wave? No option at the moment and there might even be difficult to be done in the future.
Remember that open source means you are free to review the source, offer modifications and reuse the sources elsewhere (if in line with the license used), but that does not mean you can replace it.

Thank you very much himadri_sm.
But adfree is not smart enough to do this.
Dolfin is not standalone App like Facebook or Twitter for instance...
It is hardcoded into apps_compressed.bin and additional uses Exe/DLL00111104.DLL
About sabianadmin's idea.
This is tough job too.
As I know such project needs manpower... to make stable trusted Browser.
Nobody knows, if all parts in this source and if easily to port into bada App possible...
Maybe if Opera Developer would do such experiments, then more success.
If Hobby Programmer...
Best Regards

mijoma said:
Modify sources and recompile? Sure.
Load it on the Wave? No option at the moment and there might even be difficult to be done in the future.
Remember that open source means you are free to review the source, offer modifications and reuse the sources elsewhere (if in line with the license used), but that does not mean you can replace it.
Click to expand...
Click to collapse
:-/ not sure you quite get my meaning, im talking about using the Bada SDK to compile a modified version of the browser and creating a new browser based on the original Dolfin source, the source is just weird i was expecting .cpp and so forth but instead they have gone with microsoft standards like .dll and .bat . Is it me or are samsung new to this platform development thing...

Dolfin is not only for bada... Samsung used this for several platforms...
So its same... you have to port the source...
Look here for Example:
http://forum.xda-developers.com/showthread.php?t=1004193
Linked Browser is around 3 MB...
Better we start some easier project... for example TICTACTOE on JAVA with Bluetooth Support... NO JOKE
http://forum.xda-developers.com/showthread.php?t=999256
Here are the source code for bada...
We need someone who made JAVA Version for instance. Then you could play S8500 against I9000 user.
This source could also help to develop simple check... or other Multiplayer over Bluetooth.
Best Regards

Am I imagining things, or did Extended Controls use to be open source?

http://extendedcontrols.honoluluteam.net/
http://code.google.com/p/extendedcontrols/
Maybe I just saw the Google Code page and the Apache License and thought the source was available, but I could've sworn I had actually browsed through it at some point. Or am I nuts?

It looks like they're using Google Code for issue tracking only, and that it's not truly an open source project. If you wanted to get them kicked off Google Code, you could. Not saying you should do that, but I don't see evidence that they're really open source, and that is a clearly stated requirement for hosting a project on Google Code.

[CLIENT-APP] MetroPack - Cydia for Windows Phone 7 (desktop)

It is a desktop client (package management on the phone is another topic) that aggregates existing repositories (my own basic format - currently no APT or NuGet) and provides a way to distribute homebrew applications in a more convenient manner.

this looks great! but wheres the download file?
it said "This project has no releases."

As I said in the main post, the binaries are not there yet, but you can always compile the source code yourself. Binaries will be available this weekend.
Here is the latest changeset.

Looks really good.
Downloaded,compiled,ran,downloaded the test apps. IT WORKS!! Really nice concept. I do hope you make some documentation for it. For all I know, this could be the next big thing.

Thanks. Compiled it and ran it. Works.
What i'd like to see is some kind of
- rating.
- possible to not show only screenshots but maybe short videos to demonstrate app.
- possibility to upload also source code of the xaps, so developers can decide if they want to brew this app by themselves or install "unchecked" xaps
thanks so far. i think youre on a good way!
ps: i remember last year there were big discussions microsoft wanted allow homebrew and integrate this into marketplace. hello? chevron? hello? so hopefully youre work is not for nothing.

@amannigam @oOp thanks for the feedback! It works at a very basic level - many more improvements have to be made, but that's going to happen over the weekend.
What specific documentation would you need for it?
Also, ratings sounds like a good idea. The only thing is I need to think of is a way to write those to the repository the user is exposing. Or, I could simply create a central repo/pack-ID link database on my own server that will keep a record of app ratings (can cause some problems, but I am plainly thinking of a PoC now).
I appreciate the feedback!

mwang's post about the DFT 7220 release says that the ROM includes the ability to install XAP's over the net. Homebrew like this but on phone. Just thought you'd be interested in that.

Great concept! I'll have to join in on this. I'll be setting up a repository later on.

What I feel that this project can go a really long way. So try making docs for everything that is being added. So people never lose track of anything. Also info of how to create a repo and adding the repo to app will help them jump to it easy.

Looks great! c# WPF, nothing beats this.
1. The new Mango hack allows downloading and installing XAPS directly from the OS (without a PC connected). Maybe we can use the infrastructure of your PC app and make another mobile app?
2. How can I contribute?

snickler said:
Great concept! I'll have to join in on this. I'll be setting up a repository later on.
Click to expand...
Click to collapse
Awesome! Let me know what the URL is when it's ready.
amannigam said:
What I feel that this project can go a really long way. So try making docs for everything that is being added. So people never lose track of anything. Also info of how to create a repo and adding the repo to app will help them jump to it easy.
Click to expand...
Click to collapse
Will try to do that. I will put together a tool to automatically create a repo in the next hours and will make it available by tomorrow. It will be bundled as a part of MetroPack. Thanks for the feedback!
Thank you all!

yes, pls make it into a phone app

Also tell us how can we contribute to the project. Yes we will test it. But apart from that if you need any help in development or anything. Do tell us.

the weekend is almost over and still no release?
And you have my full support also

Coming this evening (Central Time). Have to do some late adjustments and bug fixes.

Got done with the repository builder tool. I decided to integrate it with MetroPack, so it's work in progress now - you can see it as RepoDev, I need to port the rest tomorrow (bindings and actual export).
For those who do not want to download the source code, the binaries will be available here. The current binaries are very raw (functionality-wise it is a PoC). Once I integrate the repo builder tool, I will make sure that packages are actually installed on the device.
Also, if you are creating a repo, make sure you read this first:
http://metropack.codeplex.com/wikipage?title=Creating a new repository
There is a breaking change related to the version format.

GREAT APP, cant wait till final build , I get force close error and cant use it for long , I want to donate some money , its not alot but all donations help.

it really has potential

I really appreciate your guys' feedback, but until there is a final release - no donations Thank you, though!
@confrontation - what were you doing to get a forced close?

ZeBond said:
I really appreciate your guys' feedback, but until there is a final release - no donations Thank you, though!
@confrontation - what were you doing to get a forced close?
Click to expand...
Click to collapse
I was just checking out all the fuctions of the app

Sage Advice from Cyanogen Still Valid Today

If you’ve spent any amount of time on XDA, you’ve heard of XDA Recognized Developer Cyanogen or the nearly ubiquitous CyanogenMod. In fact, chances are that at you’ve either run CyanogenMod on one of your devices at some point in the past, or you’re running it (or a kanged version) now. In many ways, CyanogenMod represented all that was good about Android Open Source Project (AOSP) and proceeded to go where the carriers and manufacturers were unwilling to take their devices. Along the way, Cyanogen inspired developers everywhere to reach for what was previously lacking in the Android community.
Cyanogen also saw an emerging trend which he wasn’t too happy about – the term “chef” being applied to the Android custom development scene, along with the emergence of the so-called “WinZip ROM.” So he created a thread back in 2010 to speak to this emerging trend and offer up some advice. The overriding theme was that contributing quality was far more important than contributing quantity on XDA.
He had this advice to offer for those looking to make their own Android ROMs:
Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works….. Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that s**t on your resume. There is a *ton* of information out there but any kind of “step-by-step rom cooking guide” is going to be a complete fail- it’s too broad of a subject.
As XDA has grown right along with the meteoric rise of Android, so has a desire of users to create their own ROMs, kernels, themes, and so on. Much of this work classifies as “original development,” but there’s been a growing trend to what many are calling “derivative development.” This category covers most of ROMs based on stock releases from the manufacturers, applying patches and scripts aimed at optimization, theming and/or removing stock applications, and using “kitchens” that run a stock release through a list of scripts and then repackage as a recovery-flashable update.zip. This is what Cyanogen was expressing frustration about—shortcuts being taken to achieve a product that differs only slightly from stock (derived) and pushed out instead of building from source and delving into the core of Android and making something truly original.
XDA-Developers exists first and foremost for developers. It’s at the core of who we are; it’s in our blood; and it’s in the air we breathe. There is a place for derivative works—they provide an entry to the scene which can help to introduce people to the wonders of Android. But let’s not stop there. Don’t be satisfied with just creating yet another derivative of someone else’s work. Instead, follow Cyanogen’s sage advice and learn about Android from the ground up, and create something truly original and innovative.
Here are some locations to help you on the path to learning about Android and contributing to the community as a whole:
Android Developer Guides
Working with Android Source
Downloading the Android Source
Git Tips and Tricks
Building CyanogenMod
Pro GIT Book
source : http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/
original source : http://forum.xda-developers.com/showthread.php?t=667298

Well put and a great reminder for all.
Side note - What is with all the "reserved" posts? This has to stop, its just spam. I will delete all posts on sight and repeat offenders will have their ability to post removed.
Sorry to divert the topic.

andyharney said:
Well put and a great reminder for all.
Side note - What is with all the "reserved" posts? This has to stop, its just spam. I will delete all posts on sight and repeat offenders will have their ability to post removed.
Sorry to divert the topic.
Click to expand...
Click to collapse
moved and cleaned...nice..
i was also curious of the so many reservations
anyway, the message is clear..
Dev = Creator(File Pusher)
Chef = Indirect Piracy? LOL
For the chef thing is my opinion since its just improvising, not really creating