Related
I've been trying my hardest contacting many people to get development started with this phone. Since not many Experienced Devs would be looking the way of this phone i've been trying to reach out.
I Contacted AndroidSpin as well and they are very well known android news site (which i check everyday) and managed to get an article out about helping with development with our phone (awsome, thanks AndroidSpin!) See the Article Here
Hopefully in the Near future we will have a working recovery and ROMs/Mods/Themes Rolling out. A Very experienced Dev has Contacted me Back Saying he is Willing to Help but nothing is promised as he doesnt have a Sidekick 4G at hand. But he is willing to make a working recovery for us so lets see what happens .
He will Definitely need testers.. i will be one ofcourse hope others are interested in seeing development stir up over here aswell !
nice to hear about.....i have been checked this 4rum everyday to looking for a news but still......hopefully something will come out soon....:x im willing to be the tester for this as well.....
I just want to say thank you to all of you working on this. As a former Hiptop user and open-source enthusiast, I took issue with the closed platform that Danger had installed on it and ended up ditching it. When I heard the new Sidekicks would be running Android I jumped at the chance to have one, only to find out that development was lacking interest due to the stigma of the old Hiptops as phones for teenagers. It's wonderful to see more people getting interested in this and I hope to help as much as I can in the future. Thank everyone again and happy hacking to you all!
willing to help
I'm very interested in getting development going for this phone as well, I don't have the time or the skill set to cook roms myself but I am more than willing to test and give feedback. I know a lot of devs aren't interested since they spent last year with the galaxy s line of phones and there are new dual cores to play with, but I think this phone is really unique and could definitely have a big following because of the fact that it is soo different than the sea of slabs out there. I hope development picks up, there are plenty of custom roms out there already built for the galaxy s line that would only need to be tweaked to work with this device so hopefully that picks up soon.
I'm very interested in helping with development, came from the G1 and had fun with that. I was trying to figure out how to compile ClockworkMod but because Samsung uses initRamFS rather than a regular makefile, I was unable to figure it out. I'm very open to testing and trying to help as best I can with developing on this phone, feel free to e-mail me if anyone has any need to test anything, I'm always checking my e-mail. sduvick AT gmail.com. For those who understand the compiling of clockworkmod, I would suggest working from the Vibrant version, as the buttons are all mapped right, we just need to add the storage driver so that the sdcard can be mounted.
I would love to be a tester please keep me posted.
Sent from my SGH-T839 using XDA Premium App
+Thanks.
I'm still stock and would be willing to help some dev's
I really like this site because of all the great folks that are steady working to improve our devices whether it be a phone or a tablet.. that being said, dudes, if someone wants to ask the community for help to create an ICS rom there is no need for flaming. Cm7 has been done a million times by many of folks, why folks tripping because someone is trying to create a functional ics and is asking the community for help? That's the beauty of xda, we all help each other to accomplish a common goal, to improve android as a whole for us all! Stop being dickheads and cooperate instead of hating on ol boy. Have a great day.
ROMS or mods with libusb installed.
Do any Viewsonic Gtablet Android 3.0.1 based ROMS exist that have libusb installed so I can use the java hooks to communicate with a USB HID device?
I've heard many things, all great, about CM since the beginning of time (...well, close to it.). Frequently, before a real android phone was obtainable via the average pathways here in the U.S. of A, and the iPhone was the only real option for a smartphone, I found myself pulled towards CM-even though I had no way of actually using it at the time. The open-source, power-to-the people feel has always appealed to me...and my journey, starting from the age of 12, when I started crashing my parents computer so I could spend more time with the boutique builder that would fix it, later fixing it myself, then exploring the down-and-dirty innards of my gadgets-- this journey, has always felt like home to me.
My personal tinkering with phones and the like started with my sisters HTC Tilt, which I skinned to look like an iPhone for her. This was one of the first phones with Wi-Fi (Ha!), and trying to get it work was just as fun as using it.
Moving on, I received, for my birthday, a palm PDA (one of the first with a camera and a color screen...the device itself was blue), but I had to return it due to an exploding display.
Finally, a couple years ago, I got my first smart-phone. An iPhone. And within an hour after getting it, I had it jailbroken and themed. But the innards were still off limits. While searching under terms lie? "Hack phone" and "tethering, I always came across posts speaking of Cyanogenmod...In fact, I'd say that an astounding 50% of my searches relating to customizing or modifying--in some way or another, led to a post or thread--sometimes a whole article, on how to do something with android, and specifically CM. This proved fruitful for my later endeavors.
When I was doing better financially, I bought my first android device, and have never felt so empowered, and have never had such a strong ownership of my devices. That device was the Transformer.
Again, after just an hour of owning the device, I was looking up terms...and searching XDA for every bit of relevant information I could find. Some of the questions I had: What is Clockwork Mod? What is Clockwork Mod Recovery? What's the difference? NVflash? What's a B70 serial number mean for my prognosis? What's a Nandroid? How do I choose a ROM?
Although there was a metric ten of terminology I needed to learn to know what I was doing--and even though there was almost a complete vacuum of centralized information--- at least authoritative information (any questioned asked in forums led to me being booted and marked as a noob), things eventually worked out.
I learned about the Boot loader situation for the transformer, the status of honeycomb as a sort of non-open-source open source operating system, and about the battery issues....about kernels, and speaker mods, about modules and root apps-and along the way I learned almost the full metric ton of terminology, and had a metric ton of fun...with you guys.
Which brings me to today...I own a brand new galaxy note, but am once again in the dark. Only this time, its far worse...because my questions pertain to CM, the gold reference when it comes to running a custom rom, and its structure...that is to say, the structure of the ROM, the team that builds it, and the community that helps support it...all relevant to understanding the dearth of work and choice that we find in this very forum. And because its been around for so long, the staple that CM has become, assumes that all things and all people know what's happening.
Which brings me to my real questions....which I've searched, and searched, and searched again for answers to, but have found no conclusive, or concise and relevant answers. I've searched the cyanogenmod site, the forum, this forum, and Google. And while I found half-answers, and although I'm confident I can root any device I, or my friends can buy, and I can install custom roms, edit props, change permissions, dump radios, flash pre rooted kernels and other kernels, and backup and edit every settings app and image I can find, I still find myself lacking a fundamental understanding of Cyanogenmod and Cyanogenmod work, official, and unofficial--information that would make my life complete, and help me bear the fruit of this journey I'm on.
That journey ends with a device that I own...one with cyanogenmod on it...specifically...a device in the near future that runs a version of CM that I helped contribute to-either officially or unofficially to.
And the beginning of the end to that journey, and the desired end game--developing, begins here. With my ASUS Transformer. And my questions.
Note: I illustrated this story in-depth, for a reason. To let you know that I've searched long and hard for clear answers, and that I plan to contribute significantly in the future to Android, and to XDA. I just need a teeny bit of help...a little direction. And so do a lot of us. I haven't found anywhere, a discussion of this subject--a significant one when it comes to understanding our community, our choices, and how to contribute...that subject is the structure of Cyanogenmod: the ROM, the team, and the community that constitutes them. The following questions are relevant to, and seek to address this fundamental lack of understanding.
Since the release of IcS, we've seen an explosion of CM in the Transformer forum. And while I understand how to read a change log, and a list of "what's working" and "what's not working", and can rely on a search find out what "Cornerstone" is, its still damn near impossible to define the relationship that constitutes all of the CM builds that are available. It might be clear, after a search, what the term "Kang" is, but what isn't clear, is what this means for the end-user. Its not clear what's official, what's parallel work, and what makes up the night lies that we can find on the CM repository. Is it one man aggregating work from forums like this, and throwing all of the features and fixes into a centralized build? Are the ROMs that we find in the Development section of the Transformer section off-shoots of CM to be worked on and differentiated in the future? Because where it stands now, I don't see a ton of differentiation. Maybe its because there's just been a new release, and I'm seeing the beginning of a process here. But I'm still unaware of what makes up a CM team. Its not clear how these things work-- if there is one man from the team working on the transformer, another working on the Epic 4g...and so on, or if everyone works on the same thing, and the feature or fix is distributed by a magic machine, or if each person on the team works on the same thing, and then a designated person ports it to his device. It's context like this that makes an informed overview of the current situation possible. And without that context, I'm stuck.
Most know that nightlies come before the release candidate(s), and that a stable release follows. But what I don't know, is why I never hear about an actual release, and almost always hear people speak of night lies, and in general, they're almost categorically excited.
So, if we were to examine my complete and utter lack of knowledge together, wed conclude that it's impossible for me to understand where XDA, and the ROMs that are available in the development section fit in to the grander-scheme of things. Is it better to get a nightly from CM? Is the nightly made up of the very fixes and developments we find in the various ROMs here in the development section?
How does someone go about deciding which of the dozen ROMs to install? Because the threads for ROMs don't explain anything when it comes to explaining an end goal, and a developers intent for the ROM, and the reasons why he/she is making one, I find myself stuck in the quick-sand of change-log after change-log, feature list after feature list.
Give me the 411. Explain to me what I'm missing in my Rosetta stone of the big picture..the grand scheme of things. Maybe I'm looking at this all wrong...maybe I'm just an idiot. Maybe you'll rage at me. But maybe, just maybe, I'm missing only, one small, key, piece of information here, and I spent a couple pages typing on the touchscreen of my transformer for thirty five minutes to find the answers that I badly need.
I'm sorry if I wasted your time. Thank you very much for reading this.
If you have a problem with my post, or a suggestion, attack, or complaint, please Private Message it to me...unless it pertains to the questions I posed...in which case I would very, very much appreciate your comment, your input, you sharing your knowledge, or even a question of your own.
Thanks.
Seriously? All that wall of text to ask the same question that everyone else asks?
This is how you divide up the custom ROMs to make your choice easier:
Do you want cornerstone or no?
If you want cornerstone, you pick between Team EOS or CM9
If you don't want cornerstone, you have these to pick from(in no particular order):
Revolver
Android Revolution HD
Codename Android
AOKP
CM9 no cornerstone version
Just try them and see what you like. I don't understand why people are so cautious before picking a ROM as if it's a permanent choice that can't be reverted.
If you don't like it, you can quickly flash a different ROM.
It's better for you to make your own decision based on your own experience with the ROMs rather than rely on someone else's recommendation whose needs and personal preference might not match yours.
Thank you, actually a nice read, there is also official cm support for our tf, on the cm website, last i seen there were 3 nightlies, since ics iv flashed the official cwm modded rom, then revolutiin, then team eos, then cm9, back to revolution, then codename android, now back on krakd hc rom until jcarrz releases his ics rom.
Sent from my R800i using xda premium
You gotta keep in mind that all ICS development now is in an early stage. Every rom is new, we don't have a solid stable one. Even stock asus have problems with rebooting, dock integration and so on.
CM is fragmented in 2 or 3 builds, and what diferentiates then is only the commits from CM repository and some dev preferences, like cornerstone or full support for the dock.
All roms that aren't Asus based (AOSP) suffers from some aditional issues, like:
- Dock won't be fully working, except on CM9 by ricardopvz and Codename Android. The touchpad still works different from stock asus.
- Some Wi-fi and GPS issues, probably driver related
- Screen rotation have a lag issue (all AOSP roms)
- Dock battery info missing, even with widget.
- Battery drain issues.
I have tested almost all roms and can say most of then is pretty usable. But if combined with overclock kernel, you can certainly expect problems.
[noobquestion]What is this cornerstone everyones talking about? lol [/noobquestion]
Im personally running team EOS nightly build (no cornerstone) with blade's OC kernel running at 1.4Ghz.
I think the ROM works very well. It hasnt really given me any issues except 2 random reboots and 1 semi-freeze (all on the same day lol). Its been running perfect for 3 days now though.
Don't worry about hondroid he is kind of a troll no hard feelings
I have not used CM for quite some time but here is my understanding from having worked with the captivate and transformer for over a year now.
Cyanogen mod is based off of the true source code of andorid taken directly from google and with no OEM's getting their greasy little fingers over them and polluting them with bloatware and skins. From there cyanogen set up a git repository where they have the main android tree as pure as it is and then branches for each device. Then there are plenty of devs working directly on the tree optimizing the core android and adding features which can then be accepted or regected by the otehr devs. Then there is a smaller team of devs on each "Branch" which normally consists of a certain type of processor or chipset. Ex Hummingbird or Tegra 2
The job of the devs there is to integrate that to make it work smoothly and they have the same peer approval system. There are also smaller branches which contain the drivers for most pieces of hardware (Speakers, Screens ect). Then finally there is the device dev there are normally about 5 from my experience but once all the work is done the team can be cut to 1 or 2. They are the people that get it up and running on the device writing missing drivers fixing device specific bugs ect. And once they are done there work they can compile it all together and there we have our nightly.
Then if there is a change in the core all the device devs have to do is recompile and build the rom and there is your next nightly.
The RC happens when they hit a stable nightly or when development has slowed enough that all of the bugs have been fixed
Hope this is helpfull
Thanks to all of your for your responses. I think this is a beautiful conversation that isn't happening enough. All of you have provided great information, that when combined helps to depict the structure of the community we have all grown to love.
Where can you find this grey area,where WP7 owners are meeting with Linux/Ubuntu developers to wrap up this dualbooting issue for once and for all?
Take a look at the Project HaRET thread -
http://forum.xda-developers.com/showthread.php?t=1483377
xdrc45 said:
Take a look at the Project HaRET thread -
http://forum.xda-developers.com/showthread.php?t=1483377
Click to expand...
Click to collapse
If you must have droid and WP on the same device this is probably the most sensible option and more likely to be usable on a number of devices. Dual Booting will mean the need for a new bootldr, HaRET does not, just full unlock or perhaps even WP7 Root Tools v.12 beta will do the job, assuming it can be made to work
if, theoretically, the linux kernel has been run on the HD2/HD7 hardware, it stands to reason that anything from 1stgen wp7 and up should be kicking ass and taking names in terms of running the Ubuntu mobile version. Take that fact, add it to fact that having a first gen device means that youre too old to upgrade and too powerful not to upgrade. Warranties have expired and are therefore moot. Each device should have a HaRET section tucked away somewhere.
Vukile said:
if, theoretically, the linux kernel has been run on the HD2/HD7 hardware, it stands to reason that anything from 1stgen wp7 and up should be kicking ass and taking names in terms of running the Ubuntu mobile version. Take that fact, add it to fact that having a first gen device means that youre too old to upgrade and too powerful not to upgrade. Warranties have expired and are therefore moot. Each device should have a HaRET section tucked away somewhere.
Click to expand...
Click to collapse
the HD2 was a very unique device though, in terms of dual booting it was only because we had the HSPL update and the secondary bootloader MAGLDR that gave us any hope at all in doing it, both of those are tightly controlled and we dont have access to adapting them to other devices and perhaps more importantely we dont have the knowledge base to do it ourselves. IRC, HaRET worked fine on the HD2 but only after a huge amount of work by some of the brightest members on the forum and a large community that was able to support them
Then we had the Android Boom, which diluted the talent base, simply put, we now have two problems
A, Many of the big names have gone to android and couldnt care less about WP
B, The people left here are largely unable to help, not for want of trying but because many of us dont know how we can help
Thats not saying we dont have any talented people here, far from it, in fact i think we have some of the best, BUT even the best need help and if the community isnt able to support them, then their struggles will be that much harder.
For HaRET we need someone who knows what they are doing to "Manage" the project, to direct and teach others. That is a very time consuming roll and i wouldnt blame anyone for saying they wouldnt have the time to do that.
Personally i couldnt care for Android on our devices but that isnt the point of what xda is about, development is what its about
And you could use the HTC Sensation XL software for example the HTC Titan (same hardware (minor differences))
I want Linux Ubuntu on my device, that's the bottom line. Years ago I started a thread about running Win 98 on WM6.1 devices using the Bosch emulator,three years later, I'd like to think the rhetoric has changed. The people who have any real info on the matter aren't saying anything definitive,that's hacker talk for ' We know something,but we can't state it officially'. I'm gonna 'leave' the matter alone now. Great ROM btw ,Sianto. Can you recommend a backup program that won't leave me in the dust? Last time I backed up I couldn't recover the files.
Vukile said:
I want Linux Ubuntu on my device, that's the bottom line. Years ago I started a thread about running Win 98 on WM6.1 devices using the Bosch emulator,three years later, I'd like to think the rhetoric has changed. The people who have any real info on the matter aren't saying anything definitive,that's hacker talk for ' We know something,but we can't state it officially'. I'm gonna 'leave' the matter alone now. Great ROM btw ,Sianto. Can you recommend a backup program that won't leave me in the dust? Last time I backed up I couldn't recover the files.
Click to expand...
Click to collapse
Well, I tried to backup with a lot of tools. But I didn't find a proper working onen yet. However, uploading your pictures to skydrive is one. Reïnstaller takes a while but wurks fantastic. And my rom should have some backup features build in as well.
I actually have spend some time building the sensation xl rom for the titan, but it didn't work out
Regards
Sianto
So, have you stopped already? I really want to help, and one of the reasons is to make things even with MS. So tell me what I need to do! HTC Titan user!
1. HTC first Gen has a good hardware environment.
2. There are ways of accessing the memory.
3. There are means of creating virtual kernels, partitions,etc.
4. There are OS's designed to run in these environments.
5. WP7 has a deadbeat dad.
And this means??
It means all the ingredients are in place to create a brand new subforum and niche market. Not unlike finding a new OS to port to an "old" device.
So do that. And your phones will be legends!
Any news?
Seen the Ubuntu article in the portal? Hmmm....
No, whats it about?
With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)
frap129 said:
With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)
Click to expand...
Click to collapse
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.
chongbos said:
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.
Click to expand...
Click to collapse
I assume by transplant you mean just try to flash a rom for another device with simmilar specs? (Same MSM8655 CPU, Same amount of ram, etc)
Kitkat would be awesome!
I'll test whatever you throw up here.
That's about all I'm good for. Sorry.
you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:
Ive contacted a few members who have experience with either porting or the thunderbolt, none of wich have responded as of yet.
her you can try :
http://forum.xda-developers.com/member.php?u=4310221
http://forum.xda-developers.com/member.php?u=4471805
http://forum.xda-developers.com/member.php?u=4395946
hope they reply...
guinzo said:
you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:
Click to expand...
Click to collapse
Santod was the reason why I loved my thunderbolt. I still have it but rarely use it. Sadly the screen is cracked but it was always a reliable phone.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk
TtWEAK said:
I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There definitely are, but the difficulty of getting data on AOSP for this device, coupled with the age, current ownership/userbase, and developer interest translates to probably not. It's okay though, it was a great ride while it lasted.