Related
Just want to know if anyone is actively working on Android for the Titan. I found the stuff for the Vogue, but it's still a bit buggy on the Titan. I'd like to get in contact with someone about testing their builds. I do not have the knowledge to program unix/linux myself, but want to help get this project accomplished. Thanks!
make that two
ditto.
I've got pretty decent experience with linux, but am not really a programmer by any means. If there's anything I can help with I'd be up for it.
all i know is that android was just made open source a few days ago, so hopefully that means somebody will get their hands on that and do whatever it is they do to make it function on our 6800's. and that is all i know...
i'd like to know more though, just dont know where to really look or who to ask as its only been worked on for the vogue- as far as i know.
I wish I had the time to fully take on this project but a current robotics project has me tied up. However, if anyone does find a project, I'll glad to help. While I'm usually a C guy, especially for embedded development I'm fairly familiar with java byte code.
i have booted the vogue version successfully on my 6800, but it's extrememly sketchy. seems to run well, but screen doesnt function 100%, buttons do not work more than I'd say 10% of the time (if at all), sound non functional, no hardware keyboard, etc...
however! i did successfully recieve/make a call. exciting, i know lol
but yeah, there's news and videos all over the net of Android on the TItan, but nothing even close to being functional. not to mention it's still just a skin over winmo. you cannot boot directly into android from a reset.
here's what is extrememly exciting though: I can get 24/25 megs of ram free and can boot into android no prob. what if winmo wasn't running in the background?? there would be so much more free ram! there's roughly 40 megs of ram that winmo is using, plus whatever android consumes, i'd say if someone can get android to boot without winmo in the background, we'd have ~50mb free ram. that's would make this phone run sooo much smoother and more seamless.
I'm convinced that a major reason the screen is buggy on the titan is that it's set up for the vogue, which has a wider screen. I didn't notice this until the last release where the android logo goes off the side of the screen. I don't think it would take much tweaking to get it working well, unfortunately like others, I just don't have the time until the semester's over. If no one has it done by the end of the semester (I hope it happens much, much earlier!) then I would have plenty of time to devote to this project.
n8thegr8 said:
If no one has it done by the end of the semester (I hope it happens much, much earlier!) then I would have plenty of time to devote to this project.
Click to expand...
Click to collapse
The semester has less than 2 months left!!
shapiror06 said:
i have booted the vogue version successfully on my 6800, but it's extrememly sketchy. seems to run well, but screen doesnt function 100%, buttons do not work more than I'd say 10% of the time (if at all), sound non functional, no hardware keyboard, etc...
however! i did successfully recieve/make a call. exciting, i know lol
but yeah, there's news and videos all over the net of Android on the TItan, but nothing even close to being functional. not to mention it's still just a skin over winmo. you cannot boot directly into android from a reset.
here's what is extrememly exciting though: I can get 24/25 megs of ram free and can boot into android no prob. what if winmo wasn't running in the background?? there would be so much more free ram! there's roughly 40 megs of ram that winmo is using, plus whatever android consumes, i'd say if someone can get android to boot without winmo in the background, we'd have ~50mb free ram. that's would make this phone run sooo much smoother and more seamless.
Click to expand...
Click to collapse
Wait.. I was under the impression that haret wiped WinMo from memory entirely, thus requiring the soft reset. Anyway, I'm also interested. You can go to #htc-linux on freenode irc; I hear that work is being done there.
I got it to boot, but not functional
I also have had the same experience described here by other users.
q on the keyboard = menu to unlock the screen.
The camera button pulls up the virtual keyboard but didn't close it for me.
Any other keys people know about?
madsuse said:
I also have had the same experience described here by other users.
q on the keyboard = menu to unlock the screen.
The camera button pulls up the virtual keyboard but didn't close it for me.
Any other keys people know about?
Click to expand...
Click to collapse
I've been able to use the power button to close applications (not the end-end keypress that some users have tried and found working)
My camera button opens and closes the on screen keyboard on an all-or-nothing basis (meaning if it opens, it closes - IF it opens at all)
The OSK is actually the only way I've found to unlock the screen.
Other than that, send and end seem to work as normal for making/ending a call
Still very sketchy though, as I've said
hahaha... yes we are working on it...let me point you to the correct thread...
http://forum.xda-developers.com/showthread.php?t=341903
It has a working keyboard now... Go to page 14 I have posted instructions on getting it working...
Mods, if possible can you merge this thread.
wasupwithuman said:
hahaha... yes we are working on it...let me point you to the correct thread...
http://forum.xda-developers.com/showthread.php?t=341903
It has a working keyboard now... Go to page 14 I have posted instructions on getting it working...
Mods, if possible can you merge this thread.
Click to expand...
Click to collapse
Very nice! When I get a free minute I'm going to read through this thread!
First off, F off if people get mad for me pulling up an old thread. Its a stupid reason to get mad. Starting a new thread would make it MORE confusing.
My main point: there are active communities attending to the adaptation of android to their devices, vogue, kaiser, etc. Where is the titan scene.
there doesnt seem to be any one spearheading this for the Titan, is the person hiding or not existent?
Second point: i'm ready to start with this can some one reach out and point me in the right direction, the closest i can find to an active project is this:
http://cs-alb-pc3.massey.ac.nz/vogue/
Magikster (I probably got the username wrong) always seemed to have the best Android build for Titan back before I got my ADP1... I haven't used anything since early January, but it looks like he just released a new build today
http://magister.ipsys.net/projects/android-for-titan/
Good luck
taspankya said:
First off, F off if people get mad for me pulling up an old thread. Its a stupid reason to get mad. Starting a new thread would make it MORE confusing.
My main point: there are active communities attending to the adaptation of android to their devices, vogue, kaiser, etc. Where is the titan scene.
there doesnt seem to be any one spearheading this for the Titan, is the person hiding or not existent?
Second point: i'm ready to start with this can some one reach out and point me in the right direction, the closest i can find to an active project is this:
http://cs-alb-pc3.massey.ac.nz/vogue/
Click to expand...
Click to collapse
Actually Magister works with dzo. His kernel changes are in dzo's git (on that webpage). In essence this means that you can use dzo's builds starting from March 11. (http://git.linuxtogo.org/?p=groups/...it;h=aaac085b22894e0ba27fd740f920dbc7cc366cf1)
For the adventurous, this means using nightly builds from http://www.androidonhtc.com/kaiser/latest_builds . Sadly the screen flipping in the wrong direction is present in those bundles.
thanks for the info guys, are either of you working on android development too?
Hey guys,
I am really curious as to what it takes to build a custom ROM. I am very interested in building my own and want some pointers on the best places to start so I don't waste my time. Any advice will be useful, books, websites, w/e.
Thank you,
r3xx3r
get ready cause this one's going wayyy over your head.
Its one of those things where if you have to ask, you'll never know.
spitefulcheerio said:
Its one of those things where if you have to ask, you'll never know.
Click to expand...
Click to collapse
I really hate this mentality. People have to start somewhere. Sure they could spend years figuring everything out on their own. Or you could save them a year by pointing them in the right direction. There is such little discussion about this and it's honestly just annoying and a huge negative aspect about the development community.
EDIT: This is for HTC and I haven't watched it, but it might get you started: http://www.youtube.com/watch?v=94Az1kcQvc4
Also, you should definitely look through the source code for open source ROMs. I'm not a ROM developer so I can't really help you more than that, but I hope a real dev gives you an answer.
first and foremost, learn how to use ADB. if you cant use ADB without some kind of script/batch file to do it for you, then stop right here!
personally the first thing i learned was how the updater-script (at the time, we didnt have edify scripting, so it was plain-jane update-script) worked. have a look in a rom's zip file and learn the layout.
learn how to edit apks (decompile/compile) with apktool.
get comfortable with linux (this is just an opinion, as you CAN build roms in windows, but i have found it much easier on my dev laptop with ubuntu 10.10 64bit)
apkmanager is a good tool to have if you are on windows (there is a linux/osx version too, but i havent used it)
learn what zip-aligning means and what it does for your rom
learn what deodexing means and what it does for your rom
different devices benefit from different tweaks within your /system/build.prop . learn which ones work best for your rom (this requires a lot of flashing and testing on your own device)
this whole process is very time consuming and takes a ton of effort on your part. be prepared. while it is a lot of work, it is a lot of fun learning.
once you get proficient at building and tweaking roms, you can start learning how to edit smali
Pirateghost said:
first and foremost, learn how to use ADB. if you cant use ADB without some kind of script/batch file to do it for you, then stop right here!
personally the first thing i learned was how the updater-script (at the time, we didnt have edify scripting, so it was plain-jane update-script) worked. have a look in a rom's zip file and learn the layout.
learn how to edit apks (decompile/compile) with apktool.
get comfortable with linux (this is just an opinion, as you CAN build roms in windows, but i have found it much easier on my dev laptop with ubuntu 10.10 64bit)
apkmanager is a good tool to have if you are on windows (there is a linux/osx version too, but i havent used it)
learn what zip-aligning means and what it does for your rom
learn what deodexing means and what it does for your rom
different devices benefit from different tweaks within your /system/build.prop . learn which ones work best for your rom (this requires a lot of flashing and testing on your own device)
this whole process is very time consuming and takes a ton of effort on your part. be prepared. while it is a lot of work, it is a lot of fun learning.
once you get proficient at building and tweaking roms, you can start learning how to edit smali
Click to expand...
Click to collapse
This is good information. I, personally, build Aura completely on windows with minimal assistance from cygwin. I use batch files for the common things I use on ADB and the like but I built the scripts myself, so it isn't like I can't do it manually I just don't wanna.
It is both easier and harder than it looks. Aura is the first rom I have built.
One thing, though, is to not accept the current ways as best. Things can always be improved. I have two common mods in my rom that are done completely differently in my rom, without either database editing through scripts or modifying smali inside apk's (the hotspot entitlement check and the 1 signal bar fix). No other roms for the Atrix (I haven't check other phones...) do it this way, not even Darkside which is based somewhat no Aura.
If you are building a rom through the Rom Kitchen... don't use the garbled updater-script it puts out. It mostly works, but it is trash and you won't learn much from it.
Experimentation!
Diviance said:
This is good information. I, personally, build Aura completely on windows with minimal assistance from cygwin. I use batch files for the common things I use on ADB and the like but I built the scripts myself, so it isn't like I can't do it manually I just don't wanna.
It is both easier and harder than it looks. Aura is the first rom I have built.
One thing, though, is to not accept the current ways as best. Things can always be improved. I have two common mods in my rom that are done completely differently in my rom, without either database editing through scripts or modifying smali inside apk's (the hotspot entitlement check and the 1 signal bar fix). No other roms for the Atrix (I haven't check other phones...) do it this way, not even Darkside which is based somewhat no Aura.
If you are building a rom through the Rom Kitchen... don't use the garbled updater-script it puts out. It mostly works, but it is trash and you won't learn much from it.
Experimentation!
Click to expand...
Click to collapse
Thanks for the input. I love hearing from other devs and the methods they prefer.
Sent from my Inspire 4G
this thread died quickly.
too bad because I want to do some studying up on it and creating some coolness myself eventually.
I know with iphones a lot of development was done right from the phone itself especially for app development, is there the same concept here?
and one other question, do you guys make any money off of these things at all? Im always looking for side work...
supermerkin said:
too bad because I want to do some studying up on it and creating some coolness myself eventually.
I know with iphones a lot of development was done right from the phone itself especially for app development, is there the same concept here?
and one other question, do you guys make any money off of these things at all? Im always looking for side work...
Click to expand...
Click to collapse
you can create scripts, push and pull files directly from the phone, so in a sense, yes you can work straight from the phone.
as for money...LOL...dont look to this for a secondary income by any means.
i have made all of $28 for my work on the inspire, and nothing from my work on the captivate
Pirateghost said:
you can create scripts, push and pull files directly from the phone, so in a sense, yes you can work straight from the phone.
as for money...LOL...dont look to this for a secondary income by any means.
i have made all of $28 for my work on the inspire, and nothing from my work on the captivate
Click to expand...
Click to collapse
Hey 28 bucks is 28 bucks, granted I made 40 per screen when I used to replace iphone digitizers but money is money you never have enough.
Thanks for the info though!
Sent from my MB860 using xda premium
I spend a lot of time flashing my Rom when I am working on it. I usually don't push and pull from the phone since most users aren't doing that and I want to emulate what they will be doing.
As for money... Yeah, not a method of reliable I income if you intend to use it as such. I have probably had around... $125 donated to me by some incredibly awesome people.
If you intend to become a Rom dev, be friendly and responsive. People really appreciate someone who is willing to answer questions and give help where needed. Being standoffish like some I have seen is a sure way to get labeled with some bad words
Thank you guys for the responses. This is something I've been wondering as I've taken the plunge into modifying my Atrix. To say it's been addictive is an understatement. I started toying with the idea of putting my own ROM together pretty early on, so basic info like this is much appreciated.
Like someone said early on in the thread, everyone has to start somewhere so even seemingly small bits of info are always welcome.
The biggest hurdle is understanding adb commands and when to use them. Then, how to view the individual file strings inside the /sytem/build.prop and apks AND actually understand what it means. I have spent hours wandering around in root explorer look in folders and seeing what is inside. Pulling something with adb actually removes it from the phone right? Then I have to adb push back into the folder I pulled from. Should I use Ubuntu on my Win7 pc? I tried eclipse, installer r13, and I do have apkmanager but have yet to figure out how to actually use it.
I learn by doing what someone is telling me so reading it sometimes doesn't make sense since I can't "see" it and what it's supposed to look like. WIsh someone lived nearby to just to help get me started.....Beers and food on me LOL. Or at least had some time over the phone even.
Thanks Diviance (again) and to you PirateGhost for your help.
no adb pull does not remove it from the device. it copies to your local machine
as far as using windows vs linux. use whatever will make you more comfortable. i can assure you a lot of tutorials, and howtos are written with linux in mind, but if you can understand the basics, you will be able to translate it to windows. not to mention once you get into tearing down APKs, jars, dexes, etc....its all the same code inside no matter what tools you are using to get to them. i find linux easier to work with when it comes to stuff like this, some people think windows is easier.
If I were to get linux on my PC, would adb work within the linux evironment...meaning can I adb from linux and compile/decompile etc from there?
Phoneguy589 said:
If I were to get linux on my PC, would adb work within the linux evironment...meaning can I adb from linux and compile/decompile etc from there?
Click to expand...
Click to collapse
well you would compile/decompile directly on the phone unless you were using the sdcard....it wouldnt be pretty
you adb pull /system/file modify it, then adb push /system/file
it works the same in windows as it does in linux from that aspect. i just find working in linux easier.
here, this should help get you started somewhere, its not exactly like this phone, and the guide should be used as a reference and not a manual.
http://forum.xda-developers.com/showthread.php?t=915435
if you are technical enough, just by looking at that thread, you will understand a good portion of whats going on.
Thanks for all the help. Im getting bored flashing other peoples work and would like to help tweak things. And develop some stuff.
Thanks bro.
This is a re-post of a question posed by naddie in the development forum. I was curious about something similar, and received some indication that the dev forum was the wrong place to get the question answered. Any thoughts over here?
"I'm starting to learn how to compile Android ICS from source, and thanks to Shen's tutorial, I'm starting to "get it".
So I do have a few questions before I get started.
1) Does the Nexus S and the Samsung Vibrant use the exact same hardware?
2) Can I use the Nexus S binaries listed here (http://code.google.com/android/nexus/drivers.html) for the Vibrant if question #1 is a "yes"?
I was going to buy a Nexus S or GNexus just for the purpose of learning, but if my Vibrant is basically an Nexus S, I say why not use it? It's not my daily phone.
FYI, it already has ICS Passion v9.2 on it, and has an FFC (I added it). I would just like to get started in compiling my own ROM for the sake of learning, starting a new hobby, and hopefully able to contribute to the Android community in which I have already benefitted as a ROM-flashing enthusiast."
Yep, that'd be me. Posting to automatically subscribe.
I went ahead and followed the steps of Shen's guide and currently compiling into an OTA package.
I built it as if it was for a Nexus S. Would I brick my Vibrant if I flash it?
If so, what do I have to do to make it a Vibrant specific ROM, assuming the binaries for the Nexus S works for the Vibrant?
Right now I'm thinking there's no way it will work just like that. Otherwise ICS for the Vibrant would have been a trivial thing for the more seasoned developers.
Even if it's something I can't do on my own, I'd like to learn how it's done. Anyone who can chime in on this, please do. Thanks!
*bump*
Anyone?
Dude, I think you and I are alone on this one... :E
the devices are a little different but what you could do is track down all the specs of the vibrant, chip set and everything and figure out what is the same between the 2, then you wouldnt have to port over as many binaries, also we have 3 ics ports currently so you should be able to take everything you need from those roms and build for the vibrant
I am fairly certain there is a way to do it on your PC to compile all the binairies, libs, modules,...and flash it through a type of dummy phone set up on your PC without ever touching your physical phone. It was in another forum that I am a member of. If you want more info on it, I can PM a buddy of mine about it. Not sure if it was a github type thing or some other repository and then you build your source on your PC and if it works great you can transfer to phone. If not, then no harm no foul and you find the problem.
You can pull up basic specs on NS and Vibrant on GSMarena side by side. That is how I decided on picking the Vibe instead. I am kind of a media whore and like the external sd slot. 14+gb on internal and 32gb sdcard is supreme storage.
I decided to do it proper, and found that the CyanogenMod github has the binaries:
https://github.com/CyanogenMod/android_device_samsung_vibrantmtd
However, in the step where I run ./extract-files.sh (which requires the phone to be jacked into the PC and recognized by ADB), it copied files over, but had complaints of missing files.
Upon running lunch, it said it did not find a config file for the SGH-T959.
Here's the post I did on the Tutorial thread. No answers yet.
I appreciate the responses here, though.
http://forum.xda-developers.com/showpost.php?p=21025049&postcount=89
Hey!
A while ago I got the idea of learning how to cook roms.. I made some research on it and I found some helpful stuff on xda. Well, I tried but quiet didn't understand and manage to be successful in doing what was told there..
I've read lots of stuff like "The hardest part of developing roms is getting started". So I guess this is the part where I need the most help
Whatever, the reason why I opened this thread is that I wanna hear some developers. Their ideas on developing; How to get started, their short story on how they started developing...
Basically I wanna learn where/how to start from those people who experienced and managed to become a developer..
I mean, I wanna know your stories as I really think they will help me, they will be examples to me...
Well, not only me, to anyone who reads them.. I'm hoping that this thread will help other newbies like me...
Thanks!
My first android phone was the g1, didn't install CM until the myTouch on t-mobile. I started writing scripts for android phones. Little ones, like LCD Density script or apk removal. Then worked on a theme. Didn't really go anywhere. Fixed a bug for Salvagemod for the Evo, then started working on SalvageMod. Evo needed a kernel after support was said and done, I figured out how to compile it, looking at other commits, I was able to make changes successfully to the Freedom Kernel for the Evo. Then decided that I wanted to work on some gui application. Cmcompiler came about.
While there are many many more details from start to finish. Point is really, that no one is going to teach this to you. You have to want to learn, and you simply have to do it. Its hard work. I have spent hours and hours of messing with things to get them to work correctly. Trial and error is a great way to learn android. Sadly "Android" isn't the only thing you have to learn when it comes to development. You need to learn the tools that come with the development, like packaging or install script if you have a local gui application, or git/svn/bzr for version control systems. Most importantly, you need to have fun learning. If you are not having fun. Quit.
I do not feel attracted when you ask devs to answer, but still.
I started with XDAs kitchen.
No development ofcourse, but a good place to start.
I felt XDA kitchen was not enough, so I started to learn BASH - the scripting language in wich Kitchen is written.
I started with opening the "menu" file out of the kitchen.
After a while, I neede batch-resize, as I wanted to become a themer.
I made it together with my dad.
After I saw that some themes contain more items then another, I made CopyFrom.
AndroidCentral was my next idea - a combination of all home-made tools.
Just like lithid, I felt a GUI was needed.
But I started to work on it for cross-platform usage.
Conclusion: writing scripts is a good way to start. Google is my best friend, as I am new to scripting also.
Good luck
Sent from my Galaxy Nexus using Tapatalk 2
To echo the sentiments of the two previous posts by lithid and mdroid, I also started by writing simple scripts and small projects. Android Utility was my start up project.
My first real projects involved Rosie (HTC Sense launcher) and theming it. Then it become modding the apk to do other things (remapped, 4x5, 5 column app drawer, transparency, etc). The process of learning how to theme and mod one apk really helps you learn.
My recommendation is to pick one particular aspect of your device/Rom and learn as much as you can about it. You will find quickly that by doing so you inevitably have to learn how to use the Android tools, scripting, BASIC programming fundamentals, and a general idea of how everything works.
And yes, Google is your friend. Also stackoverflow
Sent from my PG86100 using Tapatalk 2
I also wanna to start developing. Thanks the infos. Can you write a few standard dev-tools name?
Sent from my ZTE Blade using XDA app
After creating this thread and reading the opinions of developers I followed this tut and tried this kitchen.. Helps in modifying a ROM.
And as I already had Cygwin installed using the way shown in the above tutorial I tried this tool for modifying the boot.img..
And if you want to modify apps you can give a shot to this tool...
These tools are basically really easy to use and efficient. Especially for a newbie like me.
oh, and these words of cyanogen would be really helpful..
start developing is not easy...but if you really want it and can dedicatebtime and patience all will just be fine... it's not recommended that u try to do all at first...maybe just a mod can be ok for you or anyone starting here...try modding a rom,changing stuff,adding tweaka and playing with build.prop as well...then if all goes right u can think on modding more stuff like apjs,themes,including simo comex apks...those who needs extra settings,etc... you'll gain xperience as long as time goes on and will fibd lot of interesting stuff u'd like to invlude on builds...so don't rush...good roms need time and patience
Sent from my MB860 using XDA
Thanks! when I read your ideas, telling me to play around with a rom and all that. I feel that Im really lucky. I've already been playing around with the ROMs I've used so far.. like editing build.prop, basic theming, editing apks, I once edited framework-res.apk to enable the navigation bar, etc...
Yesterday I tried porting MIUIv4 on the cm9 for for my device following some tuts on xda.. I did everything right, but no luck I get stuck in boot logo... Whatever I'll not give up!
I'm planning to study those kitchen stuff more for now, I'll give a shot to the tutorial mentioned on the portal today..
Whats your device?
My next plan to modding a ROM. I read also the MIUI porting thread, that's not hard. A long time ago, with my previously phone, the Xperia X8 (miss you...), i tuned up the stock ROM and modified a cooked ROM for myself - without XDA. I registered after here.
Sent from my ZTE Blade using XDA app
LG GT-540 optimus
I know. Its really easy. Plus I tried to port MIUI by mikegapinski on cm9 by miroslav_mm.. both roms are developed for GT-540.. I do everything right but I get stuck...
I don't what to mod, I mean I don't have any ideas... so Ill try porting MIUI
Hey bro. My advice? Do some heavy softmodding first (Take lets say tejas rom and add themes, adjust framework, add tweaks, add custom animations.custom this custom that basically add what you think is nice and yeah after long you will get more and more weird ideas )
We bought a ton of Kyocera Brigadiers for my work, as we needed something rugged and durable, and there really isn't anything on the market that's stronger than these things.
But, of course, being a VZW device that gets no love, the UI is god-awful-ugly and there's so much bloat looking at the thing feels like watching a Richard Simmons video.
So, of course, I began working to root/debloat/customize the device, or at the very least, make our process of setting these up as corporate shared devices a whole lot more streamlined.
This process did not have it's issues, and resultingly, I've softbricked two of these babies.
Now, of course, we have a working TWRP we can use to do some stuff (fix borked system partition). Plus, I've got a dump of the stock recovery, as well as a backup of the debloated system image we're now using. This stuff is invaluable in fixing the two phones I've killed...but totally useless until I can use the buttons to force the phone into bootloader so I can get around.
Which brings me to my base query - does anybody know the magic keypresses required to kick these things into bootloader mode? It *has* to exist, as I can get into it via adb reboot bootloader. Kyocera support won't talk, and Verizon support is just stupid.
Also - mods - why doesn't this device have it's own section? It has kernel source, root, and a custom recovery. I know the russians are just gaga about these things - perhaps if XDA had a dedicated section, it would see more development than it currently has. I know if there is a section, I will personally offer up the dumps I've made thus far, and probably a custom ROM at some point in time.
I know I for one would love a look at the working rooted product. Did you use the kingroot method, and did you follow up with the SU switchover?
Looking for a similar fix, have you had any luck?
Have you had any luck with this, i've gotten to the bootloader but i have nothing to go from from there. If you have any suggestions i would sure love to hear them