Related
I'm just wondering why the development community for the Photon has been so slow. I am not complaining, and am extremely greatful for everyone's work on the projects that keep us modders happy. I'm simply curioius as to whether or not there's a specific issue (an unreleased SDK, just a difficult phone to develop for, etc) as there have been several phones that have come out since the MoPho and already have more roms/kernals/etc. Again, this is simply out of curiosity. Thank you for any answers that you guys can provide.
Ive asked the same thing for a long time i still dont get it
It's the working mans phone, plus its not plagued with issues
Sent from my MB855 using XDA App
I'm just glad we have come this far...
Slow?.... we have miui and cm7 with jokers skinny rom and even sockmonkey....over 10+ oc/uv gpu enhanced kernels up to 1.5giggityhurtz ....
Only other thing I can see being modded is our pos pentile screen.....
Every optimized or enhanced android setting I come across that seem possible to port to our kernels/roms I send it jokers way cause he knows best if its worth a look or not.
So any suggestions that adds to our current awsomeness..by all means say so....
Sent from my MB855 using XDA App
A working unlocked bootloader for 2.3.5
Custodian said:
Slow?.... we have miui and cm7 with jokers skinny rom and even sockmonkey....over 10+ oc/uv gpu enhanced kernels up to 1.5giggityhurtz ....
Only other thing I can see being modded is our pos pentile screen.....
Every optimized or enhanced android setting I come across that seem possible to port to our kernels/roms I send it jokers way cause he knows best if its worth a look or not.
So any suggestions that adds to our current awsomeness..by all means say so....
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Are those not still in Alpha phase though? Maybe I'm just nitpicking, but I was talking about full releases. However, I could be just not looking hard enough or am looking over the obvious, which with me, is entirely possible.
Well considering everything software wise should be considered beta(perfect software will never happen). Im pretty sure my stuff is safe. When i release a kernel, i upload from that kernel. I cant guarantee no bugs because not even stock isnt without bugs. I use alpha to scare away people that will brand all my stuff crap. Once a kernel goes stable its the same kernel just tested by more than just me.
Evilsj said:
Are those not still in Alpha phase though? Maybe I'm just nitpicking, but I was talking about full releases. However, I could be just not looking hard enough or am looking over the obvious, which with me, is entirely possible.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Evilsj said:
Are those not still in Alpha phase though? Maybe I'm just nitpicking, but I was talking about full releases. However, I could be just not looking hard enough or am looking over the obvious, which with me, is entirely possible.
Click to expand...
Click to collapse
Although listed as alpha, they work very well. Give them a try.
Sent from my MB855 using Tapatalk
I'm using MIUI alpha and is pretty solid. Has its share of bugs but very promising.
Sent from my MB855 using Tapatalk
I wish I knew the answer to this as well. In fact, I asked the exact same question about a month ago and all I was told was that it's due to poor marketing by Sprint?
http://forum.xda-developers.com/showthread.php?t=1345073
All I ever hear from everyone is how much of a kickass phone this is, which I totally agree with. You would think that for a phone with such a solid platform to work off of, the development would be insane. Unfortunately, it's just the opposite.
i have to agree with jay
ferretman61 said:
i have to agree with jay
Click to expand...
Click to collapse
Have you done any development for it? No? That's why it's slow.
Sent from my Motorola using Tapatalk
Go home troll
ferretman61 said:
i have to agree with jay
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Instead of asking why there isn't enough development, why not state specifics on what you are looking for that is missing?
Sent from my Photon 4G using Tapatalk
honestly no offence to you but this can be pretty insulting to our developers who are highly skilled and working all their free time into getting this going, talk to Motorola for locking the bootloader and not releasing they're kernel if u want to make things faster and easier for the developers.
Sent from my MB855 using xda premium
Not too many developers have this device. If this device was on Verizon, we would have development up our a**es, but Sprint is not too popular of a service provider for Android developers, other than the Samsung Galaxy Epic Touch...
deedscreen said:
Not too many developers have this device. If this device was on Verizon, we would have development up our a**es, but Sprint is not too popular of a service provider for Android developers, other than the Samsung Galaxy Epic Touch...
Click to expand...
Click to collapse
I don't think this is entirely true. I came from the Evo 4G, and development/roms were plentiful from the dev community for that phone.
While it is a bit disconcerting to see the lack of development for my new Photon, it is important to remember that developers do this on their own time. However, as others have said, this device is far and above, even with Motoblur (which is awful, btw), what most other devices have to offer. There are, obviously, some other highly spec'd Sprint phones, like the SGSII, Evo3d, and the Nexus S 4G. And with the now impending release of the new Nexus on Sprint, I would assume development for the MoPho will likely drop altogether.
All that said, I do wish I had a stable AOSP ROM to put on this phone, with a nice guide on the most up-to-date rooting method(s). I only got this phone yesterday, so it'll be a few hours of fishing through hundreds of pages of forums before I'm ready to start rooting (I'm on 2.3.4)...my concern is what to put on my phone AFTER I'm rooted. :-(
Anyways -- thanks to all the devs that have put something together for us. Joker, it seems that your stuff is at the forefront, while some people are apparently still using the CM7 build from Cybik. Maybe I'll try it all!
Just to give a little perspective regarding software, when the company I work for goes to update an existing device with new code it takes a fair amount of full time software developers and testers (at least 3 or 4 of each) and a couple of months to get something out in a fairly stable state when they are familiar with the code that are updating.
What the developers here are doing is makes updates to code they did not create or develop and lord knows if there is one thing developers hate to do is comment code. So it makes it even more difficult for anyone to first understand what the code is doing in order to make that changes let alone someone who has a separate full time job.
I know your not complaining about the slowness, only asking why so I thought I would give me 2 cents.
Yeah jokers cm9 is running great! You should try it out. The only reason not to use it is the camera doesn't work so if that is important to you just wait. I barely use the camera so doesn't bother me.
I have a NS4G, and am switching from Sprint so I'll need a new phone. I'm looking into either the Amaze 4G, Sensation, or Galaxy S II. I want a phone that has a good developer community, as the two previous phones I had were fairly active in that regard.
I saw that the Amaze 4G Dev forum is looking like all the roms are Sense based. Is this an temporary thing or is the dev support just not there? (Or is the phone locked down enough to make it difficult?)
Anyway I would greatly appreciate some I put on this!
Sent from my Nexus S 4G using Tapatalk
Go for the sensation. I have a galaxy s two and the amaze and the dev community is almost non existent. Had a sensation and they got lots of stuff over there.
Sent from my HTC_Amaze_4G using xda premium
Hello, I am new to the forum but do have the HTC Amaze 4G. While HTC does provide the tools for unlocking the bootloader, they do not allow for S-OFF (Security OFF). And it is because of this (for the most part) that developing for the HTC Amaze is limited ATM.
mrmylanman said:
I have a NS4G, and am switching from Sprint so I'll need a new phone. I'm looking into either the Amaze 4G, Sensation, or Galaxy S II. I want a phone that has a good developer community, as the two previous phones I had were fairly active in that regard.
I saw that the Amaze 4G Dev forum is looking like all the roms are Sense based. Is this an temporary thing or is the dev support just not there? (Or is the phone locked down enough to make it difficult?)
Anyway I would greatly appreciate some I put on this!
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
the amaze is not for u then.
mrmylanman said:
I have a NS4G, and am switching from Sprint so I'll need a new phone. I'm looking into either the Amaze 4G, Sensation, or Galaxy S II. I want a phone that has a good developer community, as the two previous phones I had were fairly active in that regard.
I saw that the Amaze 4G Dev forum is looking like all the roms are Sense based. Is this an temporary thing or is the dev support just not there? (Or is the phone locked down enough to make it difficult?)
Anyway I would greatly appreciate some I put on this!
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Temp - hopefully.
Dev support - we only have one developer that actually has the phone. To top it off he's only 16 and still in high school.
We have the source but not the entire kernel source (thanks to HTC and their technicalities)
Still don't have s-off so we can't flash kernels via recovery thus makes flashing roms that much more difficult.
So if you want a good phone to use as a daily driver and don't care about tweaking and boosting... this is the phone for you!
If you immediately want fully working ICS, Sense 3.5, CM9, AOSP, etc then go with another device.
Do we see this happening in the future? If more developers were to pickup the device then maybe. But not anytime soon.
Bottom line if you want a device that has a HUGE selection of roms that you can do pretty much anything with... this isn't the phone for you. Not yet anyway.
Anyone know if there's any word on whether S-Off is coming? I thought I heard HTC announcing the days of S-On being forced are over.
I'd rather get the better phone. Hope that dev support comes.
Sent from my Nexus S 4G using Tapatalk
Agreed with Binary.
From what you've posted this doesn't sound like the phone that will suit you. However, in the long-run it could suit you better maybe?
I doubt this forum will ever pick up. Most people who wanted a phone like this bought the sensation, and this phone is not a big enough of an upgrade from that. So most will just wait till the next gen.
Thanks for the responses. I think I am going to go with the Amaze after all, and deal with Sense. Apparently it'll get ICS at some point regardless, which will be nice. I am pretty good with Linux so I might work on my own development if I get some free time (going back to college to finish up my bachelors degree so I'm not so sure about that part).
xsteven77x said:
I doubt this forum will ever pick up. Most people who wanted a phone like this bought the sensation, and this phone is not a big enough of an upgrade from that. So most will just wait till the next gen.
Click to expand...
Click to collapse
I definitely agree. Everyone that I know that bought this phone after having the Sensation ended up having buyers remorse. The phones seem very similiar to eachother and we all expected them to be pretty much the same. However we later found out that they are nothing alike on the inside. Different partitions, different software, different securities, etc. This phone is actually kind of a PITA for developers despite how HTC claims to be "developer friendly" and all that other nonsense.
If you stick with the Amaze then try beast, its pretty damn close to AOSP, or at least as close as we can have for now
Binary100100 said:
I definitely agree. Everyone that I know that bought this phone after having the Sensation ended up having buyers remorse. The phones seem very similiar to eachother and we all expected them to be pretty much the same. However we later found out that they are nothing alike on the inside. Different partitions, different software, different securities, etc. This phone is actually kind of a PITA for developers despite how HTC claims to be "developer friendly" and all that other nonsense.
Click to expand...
Click to collapse
This is the first phone where I had to use the htc unlocking method and am SHOCKED that is not as open as they made it out to be. Keeping s on? What the hell was the point then? I can see where it would benefit developers, but as far as supporting xda type communities, its an epic fail while giving us false hope in all those press releases how they "heard" the enthusiast community and wanted to be more open.
Sent from my HTC_Amaze_4G using xda premium
i hated always have 150mb of RAM or lower, but your ns4g has 2xxmb less so you are probably used to it.
Yeah I have been less of an enthusiast lately since the dev community sorta dried up on the NS4G the past couple weeks.
Its fine. I have less free time now than I used to anyway
Sent from my Nexus S 4G using Tapatalk
well i think we will be getting aosp ics with the team of people im working with its just a matter of when
xboarder56 said:
well i think we will be getting aosp ics with the team of people im working with its just a matter of when
Click to expand...
Click to collapse
as borat would say:
high five!!!! i like!!!
xboarder56 said:
well i think we will be getting aosp ics with the team of people im working with its just a matter of when
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=Dqf1BmN4Dag&feature=related
Felinos11 said:
http://www.youtube.com/watch?v=Dqf1BmN4Dag&feature=related
Click to expand...
Click to collapse
hahaha
/10char
xboarder56 said:
well i think we will be getting aosp ics with the team of people im working with its just a matter of when
Click to expand...
Click to collapse
Excellent news! I saw that almost all the active development threads are by you, you're keeping mighty busy it seems! Looks like a lot of work, that's really cool of you.
mrmylanman said:
Excellent news! I saw that almost all the active development threads are by you, you're keeping mighty busy it seems! Looks like a lot of work, that's really cool of you.
Click to expand...
Click to collapse
That would be because he's the only developer that has the phone.
Sent from my HTC Amaze 4G using xda premium
I am closing my thread because this has turned into nothing but bickering about gsm vs cdma.. Nothing ROM related.
Thanks you.
But we are not at DroidRzr, there is a lot of gsm users here.
You can say it is only for CDMA users.
I think we need more CDMA roms over here at XDA. I love droidrzr, but I feel like the development here is dead for the cdma razr...
Went from x, x2, thunderbolt, razr, g nexus. All romed minus the razr and I was most impressed from the performance gain on the x2 running an eclipse rom. The razr ran pretty snappy stock I bet this is gonna be one monster razor rom. Keep up the good work nitro if I had a razor Eclipse would be the first on my list.
Sent from my Galaxy Nexus using XDA App
Too good to be GSM one =(.
Anyone try this yet? I expected this thread to have more activity.
I've yet to try a new rom on my Maxx, so curious if I switched to something like this, would I be missing out on DLNA stuff? (i like to view movies on my tv streamed wirelessly from my phone).
ROM for GSM phones please...
silvercat said:
ROM for GSM phones please...
Click to expand...
Click to collapse
Yes...because the development section needs more GSM versions... /sarcasm...
You have ICS, go play with that and let us CDMA users play with the few ROMS that these wonderful developers have taken time to make.
Great Rom
Great ROM. Any way I can get the Quick Contacts widget back?
josiahb217 said:
Yes...because the development section needs more GSM versions... /sarcasm...
You have ICS, go play with that and let us CDMA users play with the few ROMS that these wonderful developers have taken time to make.
Click to expand...
Click to collapse
Have you not been to droidrzr.com or rootzwiki? Heaps more CDMA support there, XDA is the exception in offering more GSM ROMs & themes, et cetera. Plenty of CDMA ROMs to choose from between the various sites, nice to see more of them make their way here - especially from well respected devs. GSM support for this ROM would be very welcome, though I can understand why it's not a priority at present.
For the record, the GSM ICS leak is only worth playing with for about five minutes until it freezes or reboots or drains the battery flat, so I'd not be too quick to hold it up as an advantage.
Sent from my XT910 using xda premium
josiahb217 said:
Yes...because the development section needs more GSM versions... /sarcasm...
You have ICS, go play with that and let us CDMA users play with the few ROMS that these wonderful developers have taken time to make.
Click to expand...
Click to collapse
You are not serious...
How many do we have Rom for GSM ?
And look how many do you have rom for CDMA http://www.droidrzr.com/index.php/forum/32-droid-razr-roms/
Is it a CDMA vs GSM war or what? stop flamming this thread with useless comparaison beteween gsm rom and cdma rom and start feedback on this one...
Now i understand why droidrzr.com have more dev than XDA for the razr.
Anyway, great work nitro, i'd love to try it if you manage to port it on gsm one day, really.
thanks for your hardwork.
You are right, it is neither constructive nor productive for users and for devs.
Would this also be compatible to install with Safestrap?
Listen up, please don't post useless comments. And if people do, don't flame them for 5 pages because of it!
I am not an expert, but this is what I have pieced together. I know this is rather long but this will roughly explain Kernels, S-Off, and why Development is lacking.
Here is the way I see community android development. There are themers, Rom chefs, kernel builders, and coders. Themers make most of the visual changes. Rom chefs take a little of everyones efforts and actually puts the Roms together. Kernel builders make the custom kernels for sense, aosp, and miui. The coders are the ones who really understand the code and make the complicated things work (S-off/Root Access/Incomplete drivers/new bootloaders/things like that). Now really everyone works together and there is some crossover in people's abilities but a community really needs all of these in order to fully develop.
Kernels/Drivers:
Think of it this way, the hardware talks to the drivers/kernel and the drivers/kernel talks to the Os. The drivers/kernels are like the translator between two different languages. The problem is that our current kernel made by Htc only knows how to translate from our hardware to Sense. We have to make custom kernels that can translate from our hardware to Aosp Gb, Aosp Ics, or Miui.
The problem:
Faux is extremely talented but here is what he has stated as the problem in making these custom kernels:
Amaze WiFi driver is a modified TI WiFi driver. The major problem is we don't know what HTC did to the WiFi driver for the Amaze.
Click to expand...
Click to collapse
Now I have talked to Htc and they said that they won't be releasing the full source code that includes the wifi drivers because of proprietary issues. My guess is that TI is the company that owns the original drivers and they don't want them released. Faux:
TI drivers are designed to work with OMAP Chipsets not Qualcomm chipsets, so HTC had to do some major hacks to make it work with Qualcomm chipset. It is NOT IMPOSSIBLE to reverse engineer what HTC did, it's very time consuming and tedious.
Click to expand...
Click to collapse
The Solution
I don't have a solution but that is what this thread is for. We need to brainstorm ideas to make this happen.
Here is a link to Htc Dev if you would like to bug them about it (though I'm not sure this would help)
http://htcdev.com/contact
The other solution is to focus on Coders that can reverse engineer the Wifi drivers. We don't need S-OFF yet! S-Off simply allows users to flash things like a kernel and radio directly to the phone through recovery. THAT IS ALL! It will not help bring Aosp faster! Here is Faux's opinion:
IMHO, S-Off at this stage does very little if at all at this moment. Having a working WiFi source is far more important and will increase development for Amaze than S-Off... S-On is just a minor annoyance...
Click to expand...
Click to collapse
I hope that this helps to clear up why development is so slow. We don't have anyone that wants to jump in and build the Wifi drivers so that Faux and Xboarder can make the Kernels for the Aosp Roms to run upon. Xboarder is still at work hacking and slashing at the code to get it working but I think we need someone with years of experience and knowledge to join the efforts. Xboarder is extremely talented but he isn't a code guru yet. Go to the forums of previous phones you have had and look around for people who have re engineered Lib files and phone drivers. Talk to some of the other Kernel builders to see if they are interested in building the driver. This is where we need to focus effort and money in order to stimulate development.
Wifi Driver
From Squish099:
@htcdev Amaze 4G needs missing wifi driver from /platform//hardware/ti/wlan/wl1283 and /wl1283_softAP. Both are missing from Amaze source.
Found it in an old tweet faux sent to htc just after thanksgiving.
Click to expand...
Click to collapse
craigtut said:
Listen up, please don't post useless comments. And if people do, don't flame them for 5 pages because of it!
I am not an expert, but this is what I have pieced together. I know this is rather long but this will roughly explain Kernels, S-Off, and why Development is lacking.
Here is the way I see community android development. There are themers, Rom chefs, kernel builders, and coders. Themers make most of the visual changes. Rom chefs take a little of everyones efforts and actually puts the Roms together. Kernel builders make the custom kernels for sense, aosp, and miui. The coders are the ones who really understand the code and make the complicated things work (S-off/Root Access/Incomplete drivers/new bootloaders/things like that). Now really everyone works together and there is some crossover in people's abilities but a community really needs all of these in order to fully develop.
Kernels/Drivers:
Think of it this way, the hardware talks to the drivers/kernel and the drivers/kernel talks to the Os. The drivers/kernels are like the translator between two different languages. The problem is that our current kernel made by Htc only knows how to translate from our hardware to Sense. We have to make custom kernels that can translate from our hardware to Aosp Gb, Aosp Ics, or Miui.
The problem:
Faux is extremely talented but here is what he has stated as the problem in making these custom kernels:
Now I have talked to Htc and they said that they won't be releasing the full source code because of proprietary issues. My guess is that TI is the company that owns the original drivers and they don't want them released. Faux:
The Solution
I don't have a solution but that is what this thread is for. We need to brainstorm ideas to make this happen.
Here is a link to Htc Dev if you would like to bug them about it (though I'm not sure this would help)
http://htcdev.com/contact
The other solution is to focus on Coders that can reverse engineer the Wifi drivers. We don't need S-OFF yet! S-Off simply allows users to flash things like a kernel and radio directly to the phone through recovery. THAT IS ALL! It will not help bring Aosp faster! Here is Faux's opinion:
I hope that this helps to clear up why development is so slow. We don't have anyone that wants to jump in and build the Wifi drivers so that Faux and Xboarder can make the Kernels for the Aosp Roms to run upon. Xboarder is still at work hacking and slashing at the code to get it working but I think we need someone with years of experience and knowledge to join the efforts. Xboarder is extremely talented but he isn't a code guru yet. Go to the forums of previous phones you have had and look around for people who have re engineered Lib files and phone drivers. Talk to some of the other Kernel builders to see if they are interested in building the driver. This is where we need to focus effort and money in order to stimulate development.
Click to expand...
Click to collapse
Good post lots of info, s-off really isn't that much of a big deal. Interesting. The WiFi drivers really are important sucks how HTC handled the amaze, I'm really hoping they're more open with the HTC one thanks for the info.
Sent from my HTC_Amaze_4G using xda premium
I was able to flash kernel through recovery?
Sent from my HTC_Amaze_4G using XDA
knifeproz said:
I was able to flash kernel through recovery?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Uhh no...?
Sent from my NRGized Amaze...
via xda premium
HTC really messed up, and they call them self dev friendly,
same people that has got s-off on the sensation had tried to do for the amaze but they backed off,
but as you made a point s-off isnt really the problem here, the problem seems to be the drivers that htc wont realease
really the only person we have working hard on this device is Xboarder and binary100100 is doing what he can.
and he has done a really good job, and noobs had got on his nerves. We can not afford to lose him.
i really wish this phone have more developers working on getting things right, like that saying says two brains is better than one
i really love my phone but in the other hand i love roms. and as this phone its not a worldwide phone like the sensation i can understand the lack of developers
as you all know that the sensation have 40+ roms,themes,radios,kernerls,tweaks
sometimes i regret of getting rid of it, but specks says this is a better one,
had you guys ever though about asking for help on the android development forum? we might get lucky and find somebody that is willing to help.
but anyways thank you for saying it like it is and get us understand more of the situation, and me as i think all of you, would do anything to help..
I'm no dev, but i have done something
I HAVE PMED TWO KERNEL DEVELOPERS , TO LOOK INTO THIS THREAD TO GIVE A GLANCE , IF THEY CAN GIVE ANY INPUT ABOUT IT..
If there is any reply from them , i'll let the community know..
I think this is one of the important thread, we should probably have it in Development section and should be made sticky.
Mafioso said:
I think this is one of the important thread, we should probably have it in Development section and should be made sticky.
Click to expand...
Click to collapse
Lol good luck finding an active moderator to do anything in this Amaze forum besides handing out infractions. Binary bounced
Sent from my Energized HTC Ruby using XDA-Premium or Tapatalk
glacierguy said:
Lol good luck finding an active moderator to do anything in this Amaze forum besides handing out infractions. Binary bounced
Sent from my Energized HTC Ruby using XDA-Premium or Tapatalk
Click to expand...
Click to collapse
yeah, you will have more luck if you are looking for trolls flaming moderators indeed
Anyway,we cant stick everything in development, but i will see what i can do
Edit: oké, i will make a sticky collection thread.
So we will have less thread's sticked.
One or two sticked with all important info
This thread should be priority one in the Amaze forum.
Max Krivonos has Wifi working on his CM9 build for Amaze. Once he gets everything else working (which is limited to the rest of the radios, camera, and USB charge detection), I imagine the source will be released for use.
Accophox said:
Max Krivonos has Wifi working on his CM9 build for Amaze. Once he gets everything else working (which is limited to the rest of the radios, camera, and USB charge detection), I imagine the source will be released for use.
Click to expand...
Click to collapse
agreed. football usually drops a leak well ahead of the time ota goes live. either way, once we get the ics kernel, im rocking cm9 for good
mrmako777 said:
agreed. football usually drops a leak well ahead of the time ota goes live. either way, once we get the ics kernel, im rocking cm9 for good
Click to expand...
Click to collapse
Official ota will help but I don't think it will work for aosp. It will still only work with the sense until faux does some of his magic to it.
Sent from my HTC_Amaze_4G using XDA
Once cm9 comes out ill use it till aosp is out. I wasn't a huge fan of cm9 for hd2 but might change for this device!
Sent from my HTC_Amaze_4G using XDA
craigtut said:
Official ota will help but I don't think it will work for aosp. It will still only work with the sense until faux does some of his magic to it.
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
dont quote me, but i think max said once he got a hold of the ics leak, he could use the wifi drivers from there...or something to that effect
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
gypsy214 said:
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
Click to expand...
Click to collapse
If I was a Dev I would take any help I could get =\
Sent from my HTC Amaze 4G using XDA
Xxxpachaxxx is a kernel developer for dhd..he is looking into it but he wants to know what is the driver number for HTC amaze ...
Can some1 pleease tell me what it is ASAP!!
Is it bcm4329 ?? Fast please
Sent from my HTC_Amaze_4G using xda premium
dullhunk said:
Xxxpachaxxx is a kernel developer for dhd..he is looking into it but he wants to know what is the driver number for HTC amaze ...
Can some1 pleease tell me what it is ASAP!!
Is it bcm4329 ?? Fast please
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I don't know what it is but you could pm Faux123 for the info.
gypsy214 said:
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
Click to expand...
Click to collapse
He's working with a dozen other CM devs on MSM 8x60 devices. He just doesn't care for XDA. And with what this forum is turning into, I don't blame him.
Sent from my HTC Amaze 4G using xda premium
Will the issues with RIL keep us from getting AOSP ROMs on this device or is it something that Devs can overcome?
Sorry for the noobish question, but I've been reading this may be an issue that can't be solved.
I don't think this will be a problem if developers makes aosp for ICS and not for jellybean. This is a big problem for Resound aosp since developers wanted to fix RIL for ICS aosp but we still haven't gotten ICS officially and HTC never released ICS source. Plus side is Samsung released their source for gs3 on att and T-Mobile so we sld see it soon for verizon
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
killerT721 said:
I don't think this will be a problem if developers makes aosp for ICS and not for jellybean. This is a big problem for Resound aosp since developers wanted to fix RIL for ICS aosp but we still haven't gotten ICS officially and HTC never released ICS source. Plus side is Samsung released their source for gs3 on att and T-Mobile so we sld see it soon for verizon
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I'm confused though, I thought the RILs were only a problem when devices shifted from Gingerbread to ICS due to how different they are. I would imagine actual hardware drivers are probably the same between ICS and JB, but I could be wrong.
killerT721 said:
I don't think this will be a problem if developers makes aosp for ICS and not for jellybean. This is a big problem for Resound aosp since developers wanted to fix RIL for ICS aosp but we still haven't gotten ICS officially and HTC never released ICS source. Plus side is Samsung released their source for gs3 on att and T-Mobile so we sld see it soon for verizon
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
They only released kernel source. Not the ril, from what I have seen. With the exception of the gnexus which we have the source for, no Samsung device has working aosp and 4g on Verizon. That's not saying we won't try, but I wouldn't expect cm9 this week...
sent from my devil unicorn
RIL will be a huge issue preventing AOSP ROMs. But this should be in the Q&A or general discussion section.
tekhna said:
RIL will be a huge issue preventing AOSP ROMs. But this should be in the Q&A or general discussion section.
Click to expand...
Click to collapse
I think it's fair to say it will be our only issue. There will be many many peeps working on it though.
sent from my devil unicorn
Sorry about the wrong forum. I saw the Q&A one after I posted here.
Sent from my DROIDX using xda app-developers app
With all the variations we have of this device on AT&T, Sprint, T-Mo and Verizon utilizing the same chipset there is a definitely a possibility RIL will be cracked. I would imagine once it is figured out for a device on a specific carrier, it would be due time until that fix is ported to others.
With all the Devs I see who have picked up this device I have faith RIL will be cracked but obviously it will take time.
Pardon my ignorance of exactly how RIL works, but how different is each one for each carrier variation on a phone like this? Say someone in the Sprint community actually does the low-level dirty work and reverse-engineers their RIL line-by-line in smali. What would that mean for us? How different is a Sprint CDMA radio interface from a Verizon one on the same SoC? Obviously LTE would be a different story.
With the incredible number of people that are about to be behind this flagship phone, I have no doubt the RIL issue will be overcome regardless. This ain't no Droid Charge.
stiltzkin said:
Pardon my ignorance of exactly how RIL works, but how different is each one for each carrier variation on a phone like this? Say someone in the Sprint community actually does the low-level dirty work and reverse-engineers their RIL line-by-line in smali. What would that mean for us? How different is a Sprint CDMA radio interface from a Verizon one on the same SoC? Obviously LTE would be a different story.
With the incredible number of people that are about to be behind this flagship phone, I have no doubt the RIL issue will be overcome regardless. This ain't no Droid Charge.
Click to expand...
Click to collapse
Probably not interchangeable, some parts of it maybe.
And Steve did you get a gs3. Sending this from aokp on your builds for fascinate
Sent from my SCH-I500 using xda app-developers app
Marcismo55 said:
With all the variations we have of this device on AT&T, Sprint, T-Mo and Verizon utilizing the same chipset there is a definitely a possibility RIL will be cracked. I would imagine once it is figured out for a device on a specific carrier, it would be due time until that fix is ported to others.
With all the Devs I see who have picked up this device I have faith RIL will be cracked but obviously it will take time.
Click to expand...
Click to collapse
The other carriers use gsm their ril will do nothing for us.
tonu42 said:
Probably not interchangeable, some parts of it maybe.
And Steve did you get a gs3. Sending this from aokp on your builds for fascinate
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
It's in route should be in my hands by Saturday or Monday. I will not use touch wiz and be happy about it. At some point you will see aokp on this device. One way or another.
sent from my devil unicorn
Stephen.k.spear said:
The other carriers use gsm their ril will do nothing for us.
It's in route should be in my hands by Saturday or Monday. I will not use touch wiz and be happy about it. At some point you will see aokp on this device. One way or another.
sent from my devil unicorn
Click to expand...
Click to collapse
You just made my day
Sent from my SCH-I500 using xda app-developers app
tonu42 said:
You just made my day
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
+1
Thank you for the correction about RIL as well.
Stephen, will the RIL be the same for Sprint and US Cellular?
I hope the work is shareable across CDMA carriers.
LLStarks said:
Stephen, will the RIL be the same for Sprint and US Cellular?
I hope the work is shareable across CDMA carriers.
Click to expand...
Click to collapse
US cellular possibly, Sprints lte not wimax maybe.
sent from my devil unicorn
wrong forum this is for q and a
Stryker1297 said:
wrong forum this is for q and a
Click to expand...
Click to collapse
No, this is more or less apprpriate for this forum, during launch people would like to be able to see the status of development right away.
So you can take your 31 posts and go whine somewhere else.
I am going to be returning my iPad to get this phone outright. It has better get CM9 or AOKP.
I do wonder though concerning the LTE side how different the actual coding is per the different carriers. So like said before, for LTE, if someone cracked sprints, or AT&T's LTE coding, if it could be translated to Verizon.
Tell me if I am wrong, but don't all three carriers have identical phone hardware? All three have the same LTE chips, just set to run on different freq bands?
Forgive me if I sound skeptical, but why would the S3 be special?
Were the Strato and Charge simply not popular enough to get a healthy dev scene for RIL cracking?
LLStarks said:
Forgive me if I sound skeptical, but why would the S3 be special?
Were the Strato and Charge simply not popular enough to get a healthy dev scene for RIL cracking?
Click to expand...
Click to collapse
No, cause they were all basically rebadged phones. Charge was essentially a fascinate with 4g.
Strato was a repeat epic 4g, when the droid 2/3/4 had the reigns of keyboards already.