poll - HTC Jetstream

Best rom for this phone

abbasgholami said:
Best rom for this phone
Click to expand...
Click to collapse
I use El-Diablo ROM, but the pickings are pretty slim. There isn't too much that can be done to differentiate ROMS given the following two reasons:
Google didn't release Honeycomb (Android 3.x) as open source.
HTC never supported the Jetstream beyond Honeycomb.
Without being able to access the source code, a ROM chef/cook has fewer options.

Related

ROM recommendation for Google Maps navigation

Hi All,
I'm much more familiar with WM ROMs, but I'm dealing with my wife's HTC Hero and trying to make sense of the Android World. Her phone is running Orange UK stock firmware 1.5, build 2.73.61.5. My first instinct was to upgrade to the latest firmware available (2.1 I guess) but it sounds like these ROMs are still a bit experimental, which isn't going to go down well
Could someone with a good broad knowledge of the available ROMs please recommend the latest ROM which is going to be stable, feel complete and not result in complaints of 'it was better before'? The main aim is to run the version of Google Maps necessary for turn-by-turn navigation. I guess there are a few extra steps to get this working in the UK, but I heard this was possible.
Thanks!
It is possible, but you'll need 1.6 or above.
As 1.6 isn't available, you're looking at one of the experimental roms. The downside is, most of them don't work with Google Nav in the UK. The one that does seems to be Kagudroid, but it's an AOSP. No Sense UI at all... no facebook sync, no automatic backlight, no fancy time widgets. You get my drift?
I'd recommend either you wait until late feb (after HTC release official 2.1 rom), then there'll be a host of excellent ones up for grabs. In particular, from Modaco/Lox/Benhaam.
I imagined that there would be a few mature ROMs based on 1.6 because it's been out for so long. If there are, is there any reason not to install one of these then unlock Google Nav separately (like showthread.php?p=5122811#post5122811). [Sorry, not allowed to post links with my account!]
alphie said:
I imagined that there would be a few mature ROMs based on 1.6 because it's been out for so long. If there are, is there any reason not to install one of these
Click to expand...
Click to collapse
nprussell said:
As 1.6 isn't available
Click to expand...
Click to collapse
yeah, reading IS an art...

Why use custom roms? [relatively] new to Droid

Hello!!
I have just purchased a Galaxy 2 and it should arrive Friday or Monday.
I have been using the N900 for around 18 months and absolutely love the FREEDOM of a full Linux stack (Maemo).
Got too old and slow.
Upgrade time. SGS2 time!
Now. Rooting looks relatively easy, but why do you guys install custom roms?
Also, if anyone here can help with a small side question, the N900 has a FULL xterm with all available commands (/bin).
How do I go about getting such commands under android?
On Maemo it was as easy as "apt-get install //missing-command//"
I installed bash on my NItdroid (android on n900) but there are a few commands not available. Nothing special, just things like "history" and Possibly "nano" etc.
I had virtually zero commands on my old Xperia X10 (rooted), which is why I went back to N900. I'm a terminal geek!
Im used to having full Linux repo's.
I can build custom kernels for N900 and other Omap 3 and Omap 4 devices, but they are u-boot kernels, so I have to start learning again!!
Also, is there a terminal program which is green text on black background?? I can only find white on blue! YUCK! not nearly nerdy enough!
More often than not custom ROM's offer much better battery life and are faster and have many many added features which stock ROM's do not have, also most custom ROM's will not have Samsung bloatware in them which again will save you much battery,you can if you wish apply some themes on custom ROM's,the list is endless.
kingoddball said:
Hello!!
I have just purchased a Galaxy 2 and it should arrive Friday or Monday.
I have been using the N900 for around 18 months and absolutely love the FREEDOM of a full Linux stack (Maemo).
Got too old and slow.
Upgrade time. SGS2 time!
Now. Rooting looks relatively easy, but why do you guys install custom roms?
Also, if anyone here can help with a small side question, the N900 has a FULL xterm with all available commands (/bin).
How do I go about getting such commands under android?
On Maemo it was as easy as "apt-get install //missing-command//"
I installed bash on my NItdroid (android on n900) but there are a few commands not available. Nothing special, just things like "history" and Possibly "nano" etc.
I had virtually zero commands on my old Xperia X10 (rooted), which is why I went back to N900. I'm a terminal geek!
Im used to having full Linux repo's.
I can build custom kernels for N900 and other Omap 3 and Omap 4 devices, but they are u-boot kernels, so I have to start learning again!!
Also, is there a terminal program which is green text on black background?? I can only find white on blue! YUCK! not nearly nerdy enough!
Click to expand...
Click to collapse
How's it going? I was on the N900 as well (still use it as my music player) and have recently moved on to the SGS2. speed wise it is miles apart! even thouse the Maemo repos have excellent apps, you do notice the lack of commercial apps for Maemo when using Android
i'm not sure if i have all the answers you require... a simple way to compare custom and regular ROMs:
http://forum.xda-developers.com/showthread.php?t=1219612
Rooting your SGS2 isnt as easy as typing "root" on the N900... you'll have to use CF Root with CWM (i think):
http://forum.xda-developers.com/showthread.php?t=1103399
and a list of useful Root/ROM links at Android Forums:
http://androidforums.com/galaxy-s2-...guide-updated-12-00-pm-bst-jul-03-2011-a.html
i hope this helps
Thank you both. I'm not really a commercial app/program person.
I'm an active open source user. I love to modify and help with programs. I don't really like apple style control over programs.
I'm going to check those links. Thanks!
I hope I can try bring some of the work I made for Maemo over to android.
Most (90%) is terminal based, seems like droid users love the GUI stuff. Hehehe!
Well I will differ from Post 2. A custom ROM will bring more juice from battery? I don't believe it. It can definitely fix some bugs what the Stock one has, but nothing more than that. Also keep in mind there will be some glitch here and there in a Custom ROM.
I, personally, will never use a Custom ROM.
Regards.
kingoddball said:
Also, if anyone here can help with a small side question, the N900 has a FULL xterm with all available commands (/bin).
How do I go about getting such commands under android?
On Maemo it was as easy as "apt-get install //missing-command//"
Click to expand...
Click to collapse
nope, in general this doesn't exist. you have a linux kernel with busybox (assuming you install this along with su), but afaik, that is the limit of what you might expect from a distro. All the apps are running in the android environment, unless you wanted to chroot into something like ubuntu. Whilst I suspect there are some distros that are close to running on an android phone (or netbook, like the ac100) you're no longer running android then.
Try
SL4A (Scripting Layer for Android) as a terminal emulator (shell python etc) and it is fully open source.
ithehappy said:
Well I will differ from Post 2. A custom ROM will bring more juice from battery? I don't believe it. It can definitely fix some bugs what the Stock one has, but nothing more than that. Also keep in mind there will be some glitch here and there in a Custom ROM.
I, personally, will never use a Custom ROM.
Regards.
Click to expand...
Click to collapse
so then you, personally, will never know the difference between custom and stock. and yes, you can get better battery life with a custom rom. even a customized stock rom. with my infuse on infused 1.5 i got about 10-15% better battery life over stock.
boondoc said:
so then you, personally, will never know the difference between custom and stock. and yes, you can get better battery life with a custom rom. even a customized stock rom. with my infuse on infused 1.5 i got about 10-15% better battery life over stock.
Click to expand...
Click to collapse
You answered by yourself.
That's what I meant anyway.
Regards.
there wasn't a question at hand to be answered...
Bit like why do people buy different cars .
Custom rom may add something or remove something from the phone is the basics .
jje
I found from flashing HTC Desire, that the cries of better battery life and performance on custom ROM's were generally over exaggeration or complete nonsense, as I tried loads of custom roms and the battery and performance remained the same throughout.
For this phone, my battery life is awesome anyway, and performance is awesome also. I also seem to be pretty much bug free, also
As for the technical questions and what not in this thread it's also gone over my head lol!
I for one will vouch for better battery and performance for custom roms. It only takes one disabled service/application to improve both categories.
Custom ROM's also add features you won't find in stock ROM's and arguably enhance existing features.
For example there is no reboot function on a stock ROM, but this is just one example. CM7 has a plethora of enhancements that simply rock, on the flip side there is still a few kinks it needs to work out, but with Cyanogen joining the samsung team it wont be long until a production phone comes out with CMx running on it.
You can just install 'Advanced Power Menu' for Reboot feature on a Stock ROM.
Altimas said:
I for one will vouch for better battery and performance for custom roms. It only takes one disabled service/application to improve both categories.
Custom ROM's also add features you won't find in stock ROM's and arguably enhance existing features.
For example there is no reboot function on a stock ROM, but this is just one example. CM7 has a plethora of enhancements that simply rock, on the flip side there is still a few kinks it needs to work out, but with Cyanogen joining the samsung team it wont be long until a production phone comes out with CMx running on it.
Click to expand...
Click to collapse
I am interested in all of the benefits of using a custom ROM (especially theming) but what about the drawbacks? Don't you lose the optimizations that take advantage of the CPU/GPU?
What else would I be missing out on? I've been trying to find a thread dealing with this topic but am still searching.
.Arkham said:
I am interested in all of the benefits of using a custom ROM (especially theming) but what about the drawbacks? Don't you lose the optimizations that take advantage of the CPU/GPU?
What else would I be missing out on? I've been trying to find a thread dealing with this topic but am still searching.
Click to expand...
Click to collapse
Their is no thread as their is no custom rom but many custom roms all with different features .
Why would you lose optimizations unless the custom rom developer decided to remove them and that would not really make sense .
The benefits of using a custom rom are that you can choose one with the features you required .
jje
JJEgan said:
Their is no thread as their is no custom rom but many custom roms all with different features .
Why would you lose optimizations unless the custom rom developer decided to remove them and that would not really make sense .
The benefits of using a custom rom are that you can choose one with the features you required .
Click to expand...
Click to collapse
I know there's no single thread, what I meant was that it was hard to get the info about what the tradeoffs are of using various ROMs.
E.g. some do not have hardware acceleration (browser, video), and others don't let you use the stock app, etc... I've seen that some of the ROMs have made headway and do have hardware acceleration, but that seems to be the exception to the rule.
The only real alternative ROM is Cyanogenmod anyway. Any other rom is just some settings changed with notepad and some icons changed with photoshop.
.Arkham said:
I know there's no single thread, what I meant was that it was hard to get the info about what the tradeoffs are of using various ROMs.
E.g. some do not have hardware acceleration (browser, video), and others don't let you use the stock app, etc... I've seen that some of the ROMs have made headway and do have hardware acceleration, but that seems to be the exception to the rule.
Click to expand...
Click to collapse
Yeah you wont lose a thing, just gives you a chance to add more try leomars revolution rom, it got its own kitchen apo in market so you can install tweaks and themes from the app !
Sent from my GT-I9100 using Tapatalk
You use custom roms if you think your cellphone isn't amazingly fast enough or if you think four buttons at the lower panel is to iPhone-ish. I personally love Samsung bloatware...

Best Gingerbread ROM?

Sorry I've been gone for a while, and my old thunderbolt is still running a Senseless version of Gingertheory (gingerbread) Rom, I would like to upgrade to a newer gingerbread rom now...what is the ASOP stuff? please enlighten me on which Rom I should run...I've got a replacement phone from Verizon, my text messages were all screwed up and not coming in properly. Anyways. I guess I should download clockwork mod on my new phone.
I don't need bloatware, just basics and a fast phone with good battery life.
NeoNxz said:
Sorry I've been gone for a while, and my old thunderbolt is still running a Senseless version of Gingertheory (gingerbread) Rom, I would like to upgrade to a newer gingerbread rom now...what is the ASOP stuff? please enlighten me on which Rom I should run...I've got a replacement phone from Verizon, my text messages were all screwed up and not coming in properly. Anyways. I guess I should download clockwork mod on my new phone.
I don't need bloatware, just basics and a fast phone with good battery life.
Click to expand...
Click to collapse
The best GB Rom is whichever one you like.
for sense it would be a theory rom. for aosp either liquid or theory.
I am currently running gingeritis3D and i love it. I have not ran any other GB roms but i dont feel the need to. This rom is kicka$$ and so smooth. Got all the sense 3.0 goodies and the only bug that i know of an issue with voicemail which i fixed by just using google voice. I really highly recommend it
I was also told that the latest version (VIII) i based of the latest GB leak so its very stable
So what is ASOP? Can someone explain to me? Is it Senseless??
NeoNxz said:
So what is ASOP? Can someone explain to me? Is it Senseless??
Click to expand...
Click to collapse
That's pretty clearly explained in my thread. Link in my sig.
NeoNxz said:
So what is ASOP? Can someone explain to me? Is it Senseless??
Click to expand...
Click to collapse
Written by loonatik78
"Sense ROMs: Sense ROMs are built from RUUs, either officially released or leaked. An RUU is the complete update file for a handset; including the bootloader, radio, and ROM. Currently, all Gingerbread Sense ROMs are based on leaked RUUs. Each RUU has a version number, for example 2.10.605.0. The higher the number, the newer it is. Newer is generally better. Devs will usually include the base RUU version number in their OP. I like to think of custom ROMs developed on a common base as a family of sorts. They're going to generally have some similarities. They can have major differences as well. Some things about them won't ever change though.
Sense ROMs come in many flavors; 2.1, 2.1/3.0 hybrid, 3.0. It's really hard to tell what you like until you play with some and get to know them.
AOPS ROMs: AOSP ROMs are not built from leaked or released RUUs. They are built upon code obtained through the Android Open Source Project and are custom built for the devices. HTC, and manufactures in general, don't support AOSP being developed for their device. As a result, AOSP devs basically have to figure it out for themselves which makes the ROMs much more experimental. These ROMs typically come out in 1 or more versions, usually identified by date of release if it's a final release version, or an RC (release candidate) version if it's still in beta testing. Think of the version number and RC/beta number like the RUU number of a Sense ROM. For instance, CM7.0.3 may have several release versions that are only very slightly different. Then you may have several CM7.1.0 Beta or RC candidates that may less stable, but being offered for real world use and user feed back. That's basically the picture for the dInc currently, not the Tbolt, so don't quote me. CM releases are generally going to all look and feel the same and carry the same group of features. OMFGB is going to be making a name for itself with different features and characteristics. You won't know which you like until you try them."
Mig1234 said:
Written by loonatik78
"Sense ROMs: Sense ROMs are built from RUUs, either officially released or leaked. An RUU is the complete update file for a handset; including the bootloader, radio, and ROM. Currently, all Gingerbread Sense ROMs are based on leaked RUUs. Each RUU has a version number, for example 2.10.605.0. The higher the number, the newer it is. Newer is generally better. Devs will usually include the base RUU version number in their OP. I like to think of custom ROMs developed on a common base as a family of sorts. They're going to generally have some similarities. They can have major differences as well. Some things about them won't ever change though.
Sense ROMs come in many flavors; 2.1, 2.1/3.0 hybrid, 3.0. It's really hard to tell what you like until you play with some and get to know them.
AOPS ROMs: AOSP ROMs are not built from leaked or released RUUs. They are built upon code obtained through the Android Open Source Project and are custom built for the devices. HTC, and manufactures in general, don't support AOSP being developed for their device. As a result, AOSP devs basically have to figure it out for themselves which makes the ROMs much more experimental. These ROMs typically come out in 1 or more versions, usually identified by date of release if it's a final release version, or an RC (release candidate) version if it's still in beta testing. Think of the version number and RC/beta number like the RUU number of a Sense ROM. For instance, CM7.0.3 may have several release versions that are only very slightly different. Then you may have several CM7.1.0 Beta or RC candidates that may less stable, but being offered for real world use and user feed back. That's basically the picture for the dInc currently, not the Tbolt, so don't quote me. CM releases are generally going to all look and feel the same and carry the same group of features. OMFGB is going to be making a name for itself with different features and characteristics. You won't know which you like until you try them."
Click to expand...
Click to collapse
Thank you...Given this I will go with an AOSP rom..which do you guys prefer?
NeoNxz said:
Thank you...Given this I will go with an AOSP rom..which do you guys prefer?
Click to expand...
Click to collapse
Highly subjective question, but i like cyanogen mod. The latest version is generally not posted for it on xda though. Have to go to rootzwiki to find it under their thunderbolt forum.
NeoNxz said:
Thank you...Given this I will go with an AOSP rom..which do you guys prefer?
Click to expand...
Click to collapse
Cm7 or omgb/omfgb are good. Can't really go wrong with those
Sent from my ADR6400L using Tapatalk
thunderstick 2.2 is great very smoth find it in rom manager.He also has some great mods to go with it
Im running SHIFTAO5P from DROIDTH3ORY. Its fast and awesome on battery life
Sent from my SHIFTAO5P using XDA App
chefmg said:
thunderstick 2.2 is great very smoth find it in rom manager.He also has some great mods to go with it
Click to expand...
Click to collapse
I went with thunderstick 2.2...read into the AOSP threads and saw the voice mail issue and don't want any problems now...so far so good! thanks guys
NeoNxz said:
I went with thunderstick 2.2...read into the AOSP threads and saw the voice mail issue and don't want any problems now...so far so good! thanks guys
Click to expand...
Click to collapse
The voicemail issues are with Sense ROMS... not AOSP. VM notifications actually work on AOSP.
Sent from my SHIFTAO5P using XDA App
I have tried most sense based ROMs, I keep going back to Gingeritis 3D. BAMF is a close second, all other ROMs I have tried I get FC issues, and other wierd **** where I will just flash back to 3D. Keep in mind, each phone is different, so results will vary. Try them all out, nandroid is your friend!

[Q] Anyone working on AOKP ICS for our phone?

I just bought this phone the other day, after having an HTC Inspire for over a year. I really enjoyed the benefits of it being a sister phone of the Desire HD, such as really phenomenal ROM development.
I know that there aren't any sources released for this phone, but after using LordClockan's Ice Cold Sandwich, I just can't get used to this TouchWiz.
If anyone has started a project, I can help out with anything that I can.
If not, would anyone here like to try & help out?
My ROM building knowledge is non existent, but I'm dedicated to get this going.
Sent from my SAMSUNG-SGH-I717 using xda premium
I sure hope so! I loved existz work on the Inspire!
one7dchevy said:
I sure hope so! I loved existz work on the Inspire!
Click to expand...
Click to collapse
Him, TwistedUmbrella, and LordClockan's teamwork is a testament to the wonderful community her at XDA!
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope it's comming!
Have you tried the ICS roms that we DO have? They're not AOKP; but they run the AOSP stock apps and they've been themed well enough to be pretty damn close -- all while maintaining full s-pen capability, which is something even the CM9 folks can't claim yet (they don't have button functionality)...
Need kernel source first!!
Sent from my SAMSUNG-SGH-I717 using xda premium
paleh0rse said:
Have you tried the ICS roms that we DO have? They're not AOKP; but they run the AOSP stock apps and they've been themed well enough to be pretty damn close -- all while maintaining full s-pen capability, which is something even the CM9 folks can't claim yet (they don't have button functionality)...
Click to expand...
Click to collapse
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
Stock apps will almost always work on ANY rom with little to no modification required, regardless of whether they are from an AOSP rom.
The current roms are heavily based on the leaked ICS rom with only small tweaks universal between nearly all roms, things like themes, lockscreens, sounds, animations, etc. are all pretty simple if you know what you are doing (something admittedly, I have not personally built a rom but Im very familiar with the process).
When Cyanogen (or possibly AOKP, Im not familiar with their roms and how they are developed) is released, we will begin to see true rom development begin to happen. Until there is source code from Samsung, we will continue to see roms with Touchwiz all over them.
To show you how easy this is, here is a link to have a bot build a rom for you for any of the Galaxy 1 or 2 phones.
http://romkitchen.org/
Click your phone choice (Galaxy 1 or 2 currently, the Note is NOT supported yet).
Click Generator in the upper right hand corner.
Use the six tabs across the top of the page to choose your Modem, Kernel, Theme, stock apps, etc.
Of course, this only gives you a base to work with, from there, its pretty easy to swap in or out what you want.
Think about it like this, I can give you a copy of Windows already pre-configured for your PC and them or customize it just by changing some registry entries and including the data files (wallpapers for example). The included drivers would be pre-built meaning that 'I' didnt actually write them, nor did I change much in Windows, all I did was provide the files containing the data and changed a few settings to link to the files.
Dsmforlife92 said:
Need kernel source first!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not entirely true. I know some ICS roms that have been hacked to death to get at least partial functionality.
I'm thankful that some devs have taken their time to do what they have done, but what I am looking for hasn't been done.
AOKP is like AOSP, but more tweaks are added.
[edit] As for myself, I could care less about S Pen support. I haven't even used it, nor do I think I ever will. I got this phone for the monster sized screen.
Sent from my SAMSUNG-SGH-I717 using xda premium
littlewierdo said:
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
Stock apps will almost always work on ANY rom with little to no modification required, regardless of whether they are from an AOSP rom.
The current roms are heavily based on the leaked ICS rom with only small tweaks universal between nearly all roms, things like themes, lockscreens, sounds, animations, etc. are all pretty simple if you know what you are doing (something admittedly, I have not personally built a rom but Im very familiar with the process).
When Cyanogen (or possibly AOKP, Im not familiar with their roms and how they are developed) is released, we will begin to see true rom development begin to happen. Until there is source code from Samsung, we will continue to see roms with Touchwiz all over them.
To show you how easy this is, here is a link to have a bot build a rom for you for any of the Galaxy 1 or 2 phones.
http://romkitchen.org/
Click your phone choice (Galaxy 1 or 2 currently, the Note is NOT supported yet).
Click Generator in the upper right hand corner.
Use the six tabs across the top of the page to choose your Modem, Kernel, Theme, stock apps, etc.
Of course, this only gives you a base to work with, from there, its pretty easy to swap in or out what you want.
Think about it like this, I can give you a copy of Windows already pre-configured for your PC and them or customize it just by changing some registry entries and including the data files (wallpapers for example). The included drivers would be pre-built meaning that 'I' didnt actually write them, nor did I change much in Windows, all I did was provide the files containing the data and changed a few settings to link to the files.
Click to expand...
Click to collapse
I appreciate the explanation, but you're not telling me anything I don't already know. I was just saying that our current roms have been themed/tweaked well enough to look like AOSP, so they're not that bad; and, you don't really have to deal with touchwiz annoyances anymore if you don't want to -- trebuchet, apex, and nova all work well.
CM9 or AOKP they're not, but they're exceptional given the single source-less leak we have right now... and they certainly blow away stock touchwiz GB! lol
littlewierdo said:
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
.
Click to expand...
Click to collapse
Pen apparently works in the CM9 build for the international note. Haven't looked at the source myself yet, but it is probably just the standard wacom driver.
zonyl said:
Pen apparently works in the CM9 build for the international note. Haven't looked at the source myself yet, but it is probably just the standard wacom driver.
Click to expand...
Click to collapse
AFAIK, they haven't gotten the button to work yet, but it's promising.
Its going to take a lot kf time and effort and prob a group effort to get aosp or aokp roms for our phone. I believe the reason skyrocket and 989 have it is because they have had a lot of devs working together for long time on it. I can get a booted aosp rom hut no sound no camera no data. So theres a lot of work needed to be done
Sent from my SAMSUNG-SGH-I717 using xda premium

Source Code Request "Like" on FB

Hello All,
As you all know I've been part of Xda and assiting in a positive resolution from HTC in requests from Bootloaders to source codes. Well seeing we have a great device that seemed to be given EOL to early in its game.. in my opinion due to lack of marketing skills. Well I will be posting in HTC FB to get our voice out to them for the Source Code release for our device.
Please comment "Like" and comment to request this so we can continue development for the Flyer.
https://www.facebook.com/photo.php?fbid=10151213297764443&set=o.165420456859572&type=1&ref=nf
And Here:
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Um, source code of what? They release sources of Honeycomb, and there are no sources of ICS or Jelly Bean, so what's the whole point?
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
There is the kernel which is low level device specific, the kernel is mostly based on open source linux code, htc adds some board and device specific configuration on top of that.
Then there is the aosp which is also open source, an operating system provided by google that makes up most part of any ROM.
Then you have your aosp derivative like CM or AOKP, which provides board specific fixes and some customization. HTC's ROM is also based on aosp, but they add their own sense look and feel to it.
And finally and most importantly you have your close source proprietary drivers provided by chip manufactures like Qualcomm and TI. They control cameras, wifi, BT...etc. So in reality there is very little HTC could do as they don't have the rights to release these code. And that's is where most ppl run into issues.
So to create a ROM is not hard at all, anybody can download the source code and compile it to generate a ROM as most of the source code are all open source. What will be helpful is if Qualcomm releases the source code for their drivers, which I doubt they will ever do, otherwise they wouldn't be close source in the first place. The only thing we could do is try to reverse engineer the device base on logs and understanding of how each component should work and make educated guesses.
Due to HTC lack of effort on this device (No ICS - HC was slow joke) I will never buy another HTC product again, same goes for sony, though they did eventually update xperia x10i it was only due to huge pressure not because they wanted to.
I want to buy an electronic product that potentially remains relevant at least a year later otherwise forget it.
so i sent this letter to HTC
after reading this page where HTC discusses 4.1 upgrades i decided to drop them a line "
DIRECTLY FROM YOUR WEBSITE:
When will additional devices receive Android 4.1?
In addition to the HTC One X and HTC One S, we are actively reviewing our product portfolio to identify candidates to receive Jelly Bean. Our goal is to prioritize review for devices launched in 2012 with our numerous carrier partners across multiple regions and then consider our ability to provide updates to products from 2011.
What devices will not get Android 4.1?
We work hard to ensure each of our products has the optimal user experience and therefore some products will remain at their current version of Android. In general, devices with 512MB RAM or less will not be upgraded to Android 4.1. At present, these devices include the HTC One V and the HTC Desire C. As we identify other devices that will not be upgraded, we'll provide updated information.
What about a development version of Android 4.1?
For our developer community, we plan to make generic development ROMs of Jelly Bean available for both the HTC One X and HTC One S. As soon as the ROMs are ready, they will be posted to our HTCdev site (www.htcdev.com). We strongly recommend customers take the time to understand the limitations of the development software along with the terms and conditions on the site before downloading to their device.
REALLY!? have you listened to what your customers have asked/said about the HTC flyer at all?! where is OUR 4.1 DEVELOPMENT ROM! wtf! where are you for us!? I can tell you where... you are giving us 3.2 HC that takes away two very important features i bought the device for #1 GPS! completely broken by your newest update to HC. #2. Hardware Keys.... WHY?! i understand that HC introduced soft keys. so you say you "We work hard to ensure each of our products has the optimal user experience" BULL! you clearly weren't thinking about the end user when you pushed out that HC update for the flyer. Would have been smarter for you to leave us on working GB and go straight to ICS or JB when it was ready! this is lunacy! who ever is making decisions in your company needs fired. you are bleeding money from everywhere. why don't you bring it back to the old school HTC that CARED! ABOUT! IT'S CUSTOMERS! listen to what we are saying! hear our voice! we have signed petitions. we have pleaded on multiple forums. WE have poured over your FB and twitter pages asking for you to throw us a freaking bone here.... when is it gonna happen? ever?!
I still have my flyer and i love it dearly. but without updates it's falling behind the pack. I recently bought a 10.1 galaxy note. while i'm happy with it's speed and what not. it's not the form factor i want. which is what the flyer is for me. perfect. PLEASE DON'T GIVE UP ON US OR THIS DEVICE! PLEASE RELEASE A DEVELOPER ROM FOR OUR FLYER! "
this was their reply (you will want to read it for sure)
Dear Matt,
Thanks for contacting HTC!
We completely understand your concern and I thank you for your patience and am deeply sorry if this issue has caused you any dissatisfaction with HTC or its phones. I hope that it will not detract from your overall perspective of the device or the company. You are the most important part of the HTC Family.
We listen to our community and feedbacks like yours are the ones that make us revise our decisions, and try to find the correct balance between the device’s performance and usability. We cannot announce or say anything about the Flyer right now but what I can tell you is that we are, indeed, paying attention to the community´s feedback and opinions.
Should you require further assistance, please do not hesitate to contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a great day!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Carlos
HTC
I appreciate the passion here, but HTC left this device for dead along with the Jetstream and View shortly after releasing it. We received what would amounted to a Beta of Honeycomb then they closed up shop. You live and learn, and although I still use my Flyer and enjoy it I will not buy another HTC device
I completely agree with you .. HTC should give us ICS or JB for our Flyer as a good faith. We must keep GB because honeycomb is a joke..
I use my Flyer and i try as much as possible with the optimized news on GB .. and share with you.
Hoping for a good action on their part for JB!!
Fatal1ty_18_RUS said:
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
Click to expand...
Click to collapse
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
gersto said:
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
Click to expand...
Click to collapse
that the honeycomb kernel .
doesn't do you much good for ICS or JB
yncconsulting said:
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
.
.
.
Click to expand...
Click to collapse
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
DigitalMD said:
that the honeycomb kernel .
doesn't do you much good for ICS or JB
Click to expand...
Click to collapse
well they must be of some good since we have ICS/JB ROMs out there that are "mostly" complete, slick and usable, although slightly buggy, so obviously yeah i get that it doesn't solve all the issues we have, since some drivers are missing: as evident by the non-working FC, no hardware decoding for video, and semi-working BT
DigitalMD said:
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
Click to expand...
Click to collapse
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
DigitalMD said:
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
Click to expand...
Click to collapse
Thanks for clarification. So I was not wrong about the drivers, which are the device and vendor specific components. In other words if you can get the vendor to release their sources or make their chip/board manufacturers to release their sources is the only way to go. Seems a bit unrealistic though but who knows...
Sent from my GT-I9100G using xda app-developers app
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
freworld said:
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
Click to expand...
Click to collapse
+1

Categories

Resources