Related
Can a dev port it over?
http://forum.xda-developers.com/showthread.php?t=686893
We don't want to be behind the CDMA Hero...
now that would be great, but tbh we've been behind the CDMA hero for ages lol
Arrgh! At villainrom they're almost ready to release a 0.1 version of Froyo for GSM Hero! But...COME ON! They keep saying they can't get the mic working...When on CDMA EVERYTHING works except for GPS and Camera (the same problems we had with the first 2.1 cooked roms). I really hope they decided to release an ALL-WORKING version...Otherwise...I don't know what to think...
No Devs want to work together.
So they always can not get everything working at the sametime.
>EDIT<
rm post
Froyvillaino.1 we have been waiting for since just after robin ported n1 FR50...Prepare to wait a whil elonger i think!
I am working on a Cronos Froyo build also. Fully compiled from the 2.2 sources.
I, I, I...Guys I really don't want to shoot out advices...But it wouldn't be so bad if you all share your efforts to create a unique solution a.k.a. ROM! I really believe in the team-work!
Check that:
http://forum.xda-developers.com/showthread.php?t=704561&page=6#post6972487
Teamwork!
mardurhack said:
I, I, I...Guys I really don't want to shoot out advices...But it wouldn't be so bad if you all share your efforts to create a unique solution a.k.a. ROM! I really believe in the team-work!
Click to expand...
Click to collapse
I completely agree. It would be much better to work together in getting the hardware working and then to split off to do your own roms based on that.
Lots of devs = lots of features!
42turkeys said:
I completely agree. It would be much better to work together in getting the hardware working and then to split off to do your own roms based on that.
Lots of devs = lots of features!
Click to expand...
Click to collapse
I second that
can i install this cdma rom on my gsm hero, without breaking it and use it in the netherlands?
samm000 said:
can i install this cdma rom on my gsm hero, without breaking it and use it in the netherlands?
Click to expand...
Click to collapse
The rom it links to is FOR CDMA HEROS.
Your Hero is A GSM HERO.
DO NOT FLASH IT!
Never flash a rom if it's not for your phone. Sorry to shout but this is the No. 2 cause of bricking (Behind impatient users during radio flash)
42turkeys said:
The rom it links to is FOR CDMA HEROS.
Your Hero is A GSM HERO.
DO NOT FLASH IT!
Never flash a rom if it's not for your phone. Sorry to shout but this is the No. 2 cause of bricking (Behind impatient users during radio flash)
Click to expand...
Click to collapse
thnx a lot!!!
i'm happy you shout becouse i have be warned now
Here's hoping this will have the answer to getting the mic working...
42turkeys said:
I completely agree. It would be much better to work together in getting the hardware working and then to split off to do your own roms based on that.
Lots of devs = lots of features!
Click to expand...
Click to collapse
Teamwork means NO competition. Here its all about competition - who will be the 1st to release most stable, coolest, capable ROM on xda. Its like a gang wars.
edit: and I like it, have more ROMs to try
whitealien said:
Teamwork means NO competition. Here its all about competition - who will be the 1st to release most stable, coolest, capable ROM on xda. Its like a gang wars.
edit: and I like it, have more ROMs to try
Click to expand...
Click to collapse
I like the competition, what I'm taking about is devs getting together to get froyo running, then splitting off to make their own roms.
I think the devs can better work alone and share their work so other devs can play with it and make things better. We're saying that a community rom is better, but we havent seen one? There are tons of official 2.1 roms here, who needs all those. A froyo rom is much more interesting and as you can see, the cdma guys are really far, and maybe you, devs, can port it. Good luck.
thing is - if nobody has gotten the mic working yet, then nobody will get it working if they sit together and try to figure it out.
I would think it's like that anyway.
I know that more minds working together are better than fewer. however the mic not working cant' be a simple problem if nobody has worked it out yet. I know that not all rom builders are actually programmers - many are just really comfortable with computers and with the linux os and so on. but still, with source code available, a programmer who's comfortable with that source code (and I acknowledge that I'm not - and I'm a middle aged senior software developer... but much of the android source I've glanced through so far is unreadable to me LoL...).. anyway, so if a programmer who's comfortable with that code could peruse it for a while they might well be able to solve the problem. But what I really expect is that it will take google releasing a working mic library for froyo for hero gsm piece of the puzzle somehow - maybe an internal google person building it for the community and releasing it anonymously, that has happened in the past I would guess.
so it could take time.
but maybe some genius with the android source like cyanogen will take the time and have the know how to solve the mystery. surely the hero is the #1 android phone still out there...
judging from the community here it seems really popular still.
and to think, I just got a hero a few months back (and one for my wife) because they were only $25 at future shop when we renewed our accounts and we wanted iphones but couldn't afford them LoL
if I'd known anything about android then I'd have been all over these babies without a second thought - instead I had to research and took a leap of faith that the future shop guy was steering us in the right direction (thank you future shop guy - or I mean, former future shop guy (he doesn't work there any more)!
cheers
Hey folks,
This is a very basic DL17 rom. It has been debloated, debinged, rooted, deodexed, and zipaligned. Does NOT include radio or kernel.
Download link:
http://www.mediafire.com/?wdv53fbgl18988i
This should serve as a decent base for folks to build their future roms.
Credit to bubby323 for providing me the DL17 system dump.
credit to Logan302 for testing in IRC.
Patch
------
http://dl.dropbox.com/u/2056318/update-template/email_continuum.zip This should fix email issues.
http://dl.dropbox.com/u/2056318/update-template/social_apps.zip Social apps.
use at your own risk. I am not responsible for anything you do to your device!
DD
Tested it, and it worked absolutely perfectly my market its even working again xP bonus
Thank you so much for your time and effort! xD
Thanks for sorting out the issues with the syslinks.
Sent from my SCH-I400 using XDA App
Flashed this, This morning and it works awesome. I also flashed the test kernal you provided a week or so ago and its working great together.
Thanks for this.
Well just noticed some sort of bug on my phone at least.
When i try to add a facebook account to my ticker it fails and when i click on adding an email to my ticker it locks up my phone and i have to pull my battery. It doesnt even get me to a enter email and password screen.
Honestly to me its not a big deal im not a big facebook or email guy so it doesnt bother me.
Also i was wondering if you knew if any of the themes for the fasinate will work for this? I doubt it just wondering.
Fascinate themes must be ported. I'll look into the facebook and email issue fi possible.
Patch added for email.
adrynalyne said:
Fascinate themes must be ported. I'll look into the facebook and email issue fi possible.
Click to expand...
Click to collapse
Any idea how i would go about porting them?
There are theme porters out there. I'll get some input from others.
CrazyKnight122 said:
Any idea how i would go about porting them?
Click to expand...
Click to collapse
adrynalyne said:
There are theme porters out there. I'll get some input from others.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=932856
the theme porters that are out there...well they most just copy images with the same (or very similar) file names over one another...the post i linked above is my horribly incomplete but still useful attempt at helping people get into themes for the fascinate.
all the tools neccessary are linked in the posts there.
since the fascinate dj05/dl09 update appears very similar to dl17 porting our themes shouldnt be difficult image wise...however there are several xml changes that must be made (especially for black menus)
if anyone is really interested in starting to theme for the continuum look through the above thread and feel free to pm me here with questions or hop into the fascinate irc...im usually in there during the week throughout the day...or others im sure can help too
i had briefly thought about throwing a theme together for the continuum for fun right before dl30 (froyo) leaked...but now i have too much on my plate reporting stuff
While posting an Android ROM, can you guys PLEASE mention what Android version it is? Is this Eclair or Froyo? 2.1, 2.2, 2.2.1...which version? DL17 might explain everything to a developer but not to a user who just wants to flash a ROM on his system and needs to know what Android version it is before actually flashing it.
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Hey, you guys made the news...
http://www.androidcentral.com/samsung-continuum-sees-its-first-custom-rom
Sent from my SCH-I400 using XDA App
adrynalyne said:
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Click to expand...
Click to collapse
Thanks for your response and the clarification and with all due respect, the standard naming convention for Android operating systems is in the format of Android <version number> <dessert codename>. I have been flashing ROMs to several devices before there was any Android and have been doing so on a dozen or so Android devices that I have for the past 6 months as well as guiding others in doing so by writing about it - I write about these for a living.
However, one can't be expected to know all about these non-standard or manufacturer-specific ROM naming conventions for all the Android devices out there and unfortunately, I do not have every single device available to test the ROMs on before I write about them. That is why just a few words by the developer in the OP mentioning what Android version it is make things a lot easier for many of us, plus there are several users who are just starting at the flashing business and it makes things more clear to them as well on what they are getting into. Simply saying that if one doesn't know about these non-standard conventions, one shouldn't be trying these things out is similar to saying if one doesn't know how to swim, one shouldn't be getting into the swimming pool. No offense intended. =)
All that being said, keep up the good work - I really appreciate all the hard work you guys put into what you do. Please don't take my comments as a flame - they are just my views on how things can be improved for a lot of us just by a tiny bit of effort from you guys. =)
It is well known that the continuum only has 2.1. Therefore unless there was a 2.2 leak for it (which would be noted) it can be assume by any reasonable person that its a 2.1 rom.
nitsuj17 said:
It is well known that the continuum only has 2.1. Therefore unless there was a 2.2 leak for it (which would be noted) it can be assume by any reasonable person that its a 2.1 rom.
Click to expand...
Click to collapse
Agreed but 'well known' can be relative =) What's well-known to the developer community for a particular device might not be well-known to many who are coming across the flashing scene for the device in question for the first time, despite their prior experience with other Android devices. And as leaks are not out of the question either, just adding two words about the Android version just makes things a bit more clear for everyone, that's all I meant to say.
Coverage
Here's some more coverage for you:
http://www.addictivetips.com/mobile/install-clockworkmod-recovery-on-samsung-continuum/
&
http://www.addictivetips.com/mobile/install-dl17-clean-rooted-android-2-1-rom-on-samsung-continuum/
HQRaja said:
Agreed but 'well known' can be relative =) What's well-known to the developer community for a particular device might not be well-known to many who are coming across the flashing scene for the device in question for the first time, despite their prior experience with other Android devices. And as leaks are not out of the question either, just adding two words about the Android version just makes things a bit more clear for everyone, that's all I meant to say.
Click to expand...
Click to collapse
That goes back to this:
adrynalyne said:
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Click to expand...
Click to collapse
If you don't know what OS your phone is already running, or how they're doing the naming convention, you are likely going to cause yourself massive problems soon. If someone can't figure out About Phone to compare build versions, they likely can't figure out how to get CWM on their phone to even flash this, so it doesn't matter if the OS version is in the title. Once Froyo drops, then it may be different, but until then, you have a very thin argument at best, regardless of how many ROMs you may or may not have flashed in the past.
imnuts said:
That goes back to this:
If you don't know what OS your phone is already running, or how they're doing the naming convention, you are likely going to cause yourself massive problems soon. If someone can't figure out About Phone to compare build versions, they likely can't figure out how to get CWM on their phone to even flash this, so it doesn't matter if the OS version is in the title. Once Froyo drops, then it may be different, but until then, you have a very thin argument at best, regardless of how many ROMs you may or may not have flashed in the past.
Click to expand...
Click to collapse
In my experience, not knowing the device-specific naming conventions has never bricked any of the dozens of devices I have flashed, as long as I have known that it is a ROM meant for the particular device in question. However, knowing what Android version the ROM is based on without having to ask only makes sense. This isn't about this one device in particular - the Android scene isn't similar to the iPhone scene where there is just one developer (Apple) rolling out just one OS for all the devices on the market. Android is quite fragmented and I believe simply mentioning the Android version with the ROM regardless of whether any other version is out *yet* or not only makes sense as one never knows when a newer version or a leak might be available.
It is all for the purpose of keeping things as clear to someone at first glance, as possible. Now I do know that no other version but this one has been out for the Continuum but that has been after this discussion. All I am requesting is that the OPs should consider mentioning it with the post so that even a newbie wouldn't have to ask for information as basic as this.
What I fail to see here is why this simple, rather humble request should be seen as such a debatable topic by you guys, when it doesn't even require much effort. Heck, all it requires is typing 'Android' followed by the version number. Is it asking for too much?
Okay, this is getting really off-topic and degenerating fast. There are plenty of other threads saying what DL17 is so just hopping out to the Android Development forum would have answered your question. That said, Android ROMs do often include the version, but not always.
It's not that big of a deal. Let it go.
Sent from my SCH-I400 using XDA App
Looks like im getting involved earlier than I planned. But other than compiling a stock kernel from source. The guides for our phone never really got finished. Looks like the international guides as well as android kernel guides in general will lend some guidance.
So if anyone can point me in the right direction. Maybe even help when i get stuck.
Guides I found for our phone:
http://forum.xda-developers.com/showthread.php?t=1291122
http://forum.xda-developers.com/showthread.php?t=1442870
http://forum.xda-developers.com/showthread.php?t=1494804
I realize the problem with leak kernels on our phone other than not having source is with recovery being part of the initramfs. After reading up on the initramfs scheme one would think we can extract modify the files and repack it into the kernel like steady has been doing.
A quick google turns up a guide for the international gs2 which i hope will help me. http://forum.xda-developers.com/showthread.php?t=1294436
Then there is things like adding init.d support which i might be able to bug sfhub about. Most importantly building cwm to be packed into the initramfs. Also learned root was a part of the kernel but had i known zimage was the kernel partition I probably would have figured. But i have yet to look at either of these since I only decided yesterday to do this.
Im going to have this phone another 1.5 years so if were losing people I mind as well shuffle my projects and do this one now. I am not looking to create and maintain a custom cwm or anything.
Ive been a pascal programmer for 14 years. I can read and translate C syntax languages. I studied C++ but never having practiced it I can not write fluently without a reference in hand. I am a bit of a linux noob i mean i have compiled kernels and drivers even a from scratch gentoo install but that was all from instructions. Its one thing to do something its different to understand it.
I wrote this from my cell phone so sorry for worse than usual spelling grammar and lack of punctuation.
Also figured in my searching looking at threads started by formerly active devs might turns up some stuff.
Chris41g had a thread in the OG Epic section perfectly titled "To the people wanting learn to code kernels and roms for the Epic" http://forum.xda-developers.com/showthread.php?t=1177076
Edit - Having some time to read before i pass out that third guide that sweetwater did for our phone is rather complete up to date and he is still hanging around.
good luck man, i hope you get up and running with this. thanks for taking the challenge. the community is lacking in the kernel area and any support is greatly appreciated, by me anyway. thanks again.
Rain can you pm me?
RainMotorsports said:
Also figured in my searching looking at threads started by formerly active devs might turns up some stuff.
Chris41g had a thread in the OG Epic section perfectly titled "To the people wanting learn to code kernels and roms for the Epic" http://forum.xda-developers.com/showthread.php?t=1177076
Edit - Having some time to read before i pass out that third guide that sweetwater did for our phone is rather complete up to date and he is still hanging around.
Click to expand...
Click to collapse
Both of the E4GT guides will work no problem and are actually pretty simple, anyone here can do it. I promise that. There are some issues though. Our EL29 source is a little funky so building with the first E4GT guide will get you a booting CWM kernel but wifi will break. After A LOT of testing we found the problem in the init.d file and the fix is in Sweetwaterburn's github source. There were several of us who built kernels(even EL29 with CWM, which is weird that everyone still uses EL26 to flash AOSP but anyways...) and a few like interloper and agat who were able to incorporate various governors. That was around the time all of the leaks started so then the kernels just kind of fell of the map because why waste the time?
Now onto the ICS stock repacks.....There is a ton of risk in testing those. Look how many bricks steady and the team rogue had not to mention team troll and random users. Why not just wait a little till source drops? Once source drops building kernels will be a ton easier. Also Calkulin and the new guy(can't think of his tag) have built unsecure stock kernels so that should satisfy all of the needs for leaks.
Here is one Agat built: http://forum.xda-developers.com/showpost.php?p=22463351&postcount=265
here is another EL29 I built: http://forum.xda-developers.com/showpost.php?p=22461146&postcount=264
Thanks DTM. I read on Steady's G+ he is definitively moving away from the E4GT as he has given it to his wife.
The amount of activity and the people involved in SweetWaterBurns thread surprised me and now that I know that I don't think people should be too worried. I mean we already know part of this is a bit of impatience.
I will still be learning for the long run. Hope to see some good things with the community thread when the ICS kernel source is out.
RainMotorsports said:
Thanks DTM. I read on Steady's G+ he is definitively moving away from the E4GT as he has given it to his wife.
The amount of activity and the people involved in SweetWaterBurns thread surprised me and now that I know that I don't think people should be too worried. I mean we already know part of this is a bit of impatience.
I will still be learning for the long run. Hope to see some good things with the community thread when the ICS kernel source is out.
Click to expand...
Click to collapse
I encourage everyone to attempt a kernel. I have no formal computer training and I just dual booted my laptop, next thing you know I was churning out kernels. We definitely need some variety in our kernel selection, I just don't advise it for the leaks unless you can afford some bricks. Because we have beast "big brother" in the international SGSII community it is pretty easy porting over some of their modifications to our source code via winmerge or copy and paste. It is also a lot less risky than messing with leaks.
the long waited tegra 2 ics is now available so means the drivers to put HWA into function is available too...is it mean that a full working CM10 (or jellybean) rom will be developed soon seems all the crucial drivers are available now...
but 1 thing i found that there are less strong or experienced developers are using the glide as their phone and cause us have less power custom roms and kernels...
maybe we need to promote our phone to those optimus 2x and galaxy r developers...they have strong devs there...cause the devs were using those phone which is much popular and familiar than the glide, but they have lower hardware spec, no keyboard and with 512 only ram...and the devs did a good job on optimized them...
i believe our phone will be freaking STRONG if there are numbers of devs willing to optimized it...
jamez.tankh said:
the long waited tegra 2 ics is now available so means the drivers to put HWA into function is available too...is it mean that a full working CM10 (or jellybean) rom will be developed soon seems all the crucial drivers are available now...
but 1 thing i found that there are less strong or experienced developers are using the glide as their phone and cause us have less power custom roms and kernels...
maybe we need to promote our phone to those optimus 2x and galaxy r developers...they have strong devs there...cause the devs were using those phone which is much popular and familiar than the glide, but they have lower hardware spec, no keyboard and with 512 only ram...and the devs did a good job on optimized them...
i believe our phone will be freaking STRONG if there are numbers of devs willing to optimized it...
Click to expand...
Click to collapse
Yes but people are usually interested in the hardware they have purchased. So how do you get someone who does not have the hardware interested in helping us out? Please recall even DMan had someone lone him a phone for him to help out. The glide is a great phone but unfortunately has not sold as much, as other popular phones.
dudejb said:
Yes but people are usually interested in the hardware they have purchased. So how do you get someone who does not have the hardware interested in helping us out? Please recall even DMan had someone lone him a phone for him to help out. The glide is a great phone but unfortunately has not sold as much, as other popular phones.
Click to expand...
Click to collapse
maybe we can gift a GLIDE to devs like owain94 from optimus 2x or arcee...they are strong devs and they have a real good base knowledge on tegra 2 device...
We have dman workng on a rom as we speak... this should of been posted in the general section to btw
I suspect he is but has dman said he is working on a new ROM? I'm curious if he is making his own ROM or porting CM. I think Inception was just a stripped down official version of 2.3.5. I would love to see a CM 10 port and not just a repacked stripped ROM.
Oh my gosh with all the discussions about this. BE PATIENT. You all have no idea how much time it takes. Take a look at Inception. It took 1 week just to theme. If you want a stable, JB rom for bounty, the Collective doesn't release half ass working JB builds. Take a look
dman3285 from the Gnote thread said:
Jellybean will be coming soon.. but only when its stable.. no need to release a half ass working build.. just an update.. we are known for stability, not for being the first to the finish line, quality is our goal...:thumbup:
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Please forgive me, I'm sorry for being harsh but I've seen so many threads about this in such a short period of time. Dman and his team the Collective dev for 4-5 devices. I've been learning dev for 6 months and so far all I can do is basic tweaking to apks and decompiling them, as well as putting them in a zip.
Seriously. Just be patient, some of you. Reported for moving, btw
P.S:
This is not a port. It's compiling from source. 10 times harder and time consuming. But less chance for bugs.
P.P.S:
Inception was made without the device. It would've been near impossible to build AOSP blindly. (AOSP is pure, vanilla, Android)
P.P.P.S:
This is not an opinion poll. The devs make it how they like it, you're lucky they post it for you. They could just keep it to themselves. Feature requests are always good, but not "I like CM but I don't want a stripped modified ROM"
Thanks
After having spent the past 5 hours flashing various kernels/ROMs in my gf's xperia x10 mini pro due to various bugs, I will have to agree - in the end, stability is a must, and I am certain dman is working his magic as we speak, no need to get impatient
Aquethys said:
...
Click to expand...
Click to collapse
Everyone is being patient. Were thankful to have any devs working on this device. I just havent seen any posts directly from dman about what he's working on for the Glide. I could have missed the post, thats why I asked. But it would be cool to see a post directly from him about it and not just speculation.
Thread moved
No matter how patient everyone is being, these types of threads still keep getting started in Development. They do not belong there. They belong in General. Keep them in general. Thank you for your cooperation.
Please, everyone, just take a sit, grab a drink, and wait for dman to do his magic
I'm all for quality over a rushed job. Dev'ing is hard, especially for an under-popular device like our own. Fewer fellow devs to help out and carry the load, and more people putting the pressure on because they're impatiently excited.
Give the devs their time, it will be alright. I'm still happy with INCEPTIONv1, more so than the leaked ICS.
Sent from my SAMSUNG-SGH-I927R using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1940677
CM10 Beta for Samsung Captivate Glide
OP update the post!!!!
Hi guys,
So for the past week I think I have at least wiped/flashed/Odin'd different ROMs for my new Captivate Glide at least a hundred times. I've finally settled on thegreatergood's LiteROM 0.9.0 and it's working great for me. Not only the one ROM though as I've had to find many workarounds for different things. Flashables/kernels/apks you name it. Although I have no regrets and I'm really proud of how It's like a beast in my pocket, I am quite bothered by one thing which is that the whole thing feels like a big piece of patchwork..
Coming from a HTC Desire Z running CM7 serving me loyally for many years, I miss that officiality (<-- oops, red snakes.. not sure that's a word. Whatever. Shakespeare made his own words too right? ) and the stability that CM7 offered.
I'm a humble man, and possibly carry the apologetic traits of a typical Canadian. Instead of whining and/or nagging some senior developer to hurry up on their ICS or JB development I've decided to build my own CM instead.
However some thought, I think the reason why the JB based experimental CM 10.1s for the Captivate Glide have been a difficult task is because it's probably quite a challenge to build something from something that's not currently very well understood, namely the JB. So I thought, why not just build I nice and stable ROM based off of GB and if it does well it could probably officiated as a CM7 port for the Captivate Glide.
I have a feeling that this is a very plausible task. But I have no way to do it alone.. I have zilch experience in development in anything, had to drop out of my C++ course and have been doing nothing but lurking and leeching since I started modding when I was eleven. All I have is a vision. If someone could point me in the right direction or even form a development team with me, I would be very grateful.
And if this goes well, I will have gained some long overdue experience
So.. Anyone?
P.S. I guess this goes in this forum too. But my phone gets real angry when I flash certain things onto it. The biggest issue currently is that it will freeze and crash (more specifically the screen will freeze and fade into white lines..) whenever I try to use ClockWorkMod Recovery.. I dunno if the crappy 1500 mAh China battery I got ripped off with is an issue but I'm waiting on an OEM one in the mail..
Post in general not development bub...
And were on cm 10. Why fall back?
Sent from my SGH-I927 using xda app-developers app
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
hey bud im with you ... though I think CM9 would be better as ICS has been released, stable, and has a few more tweaks and features that CM7 didn't ... things like in JB where we have a transparent notification pull down, control over the dpi of certain apps etc.
First thing you should do is readup on the compile cm10 from source thread, get your feet wet there it'll get you all setup with a development system .. Linux is a must so I hope that you're savvy in the *nix shell or things will be antagonistic right off the start ...
I installed the CM9 recently and radio etc didn't work .. Guaranteed there is tonnes of information across all devices on xda-developers and even in general development threads.
Scroll through these forums, find the github links and learn how to setup your own, download the sources for the kernels from the other devs (theres a couple CM10.1s out there).
CM7 .. while I appreciate where you're coming from as i LOVED having CM7 on my Galaxy ACE - everything just worked... battery was great, it looked cool, and it was just off the stock enough to be unique and rub in iPhone users' faces
If I had the time I'd take it on with you .. chart your work and links that have helped you as you go along.
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
lorddavid said:
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
Click to expand...
Click to collapse
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight to CM7 : http://forum.xda-developers.com/showthread.php?t=1273718
Another one for CM9 : http://forum.xda-developers.com/showthread.php?p=20844007
.... maybe I should just build a linux VM and give it a go in my spare time .... we're so starved for developers for our glides even amateur contributions can't hurt .... in the 2nd link the guy said it took him 11 months to learn how to mod for ICS from no experience so ..... depends on how much you want to commit to it ..
yohan4ws said:
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight : http://forum.xda-developers.com/showthread.php?t=1273718
Click to expand...
Click to collapse
yes, i know that, and i was thinking that a cm9 (because there is a ics fully working in the glide) can be a good option, but not sure
This doesn't belong here, please, some mod, move this to General. Thanks
chrisyjwai said:
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Flagged to be moved to general. If this turns into a dev thread, then you can flag to move it to the dev section, but you only post in the dev sections if you actually have a product or are actively working on something.
Your intentions seem great, but never wait for someone else to help you, otherwise it will never get done. No one is going to carry you through learning this.
There's a ton of guides out there on how to build, port, cherry pick CM commits, etc. etc. Go find them and start learning. Ask SPECIFIC questions if you have any.
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc. There's a lot of steps in between. So go and get started.
gtmaster303 said:
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc.
Click to expand...
Click to collapse
That doesn't make any sense.... lots of people show up to college and say that, and then enroll in the courses to do that ..