yashsingh1/xdaforums huggingface dataset:
[Fascinate General] Boushh:
I don't think the why matters really. If you want to learn from from someone, typically you have to do it I'm their terms. You think Steven Hawking makes housecalls to anyone that wasn't some of his smarts? No. Same goes for the android devs here, they prefer teaching in real time. Also, they are doing it CONSTANTLY. Just get a client at home and read the logs when you get home, like the other 100+ people that do nothing but lurk in that Chan.

Also, bringing age into a discussion/fight/thread troll is pretty amateur considering the only persons age you know is yours.

Finally, this thread is proof that XDA is no longer a straight developer community. It is now full of consumers and people that demand things because they donate (not calling you that, just stating a fact). That isn't a good or bad thing, just what it is. But you've got to expect the devs to go somewhere for some solitude and to remind them why they started hacking/deving in the first place. That place as you can imagine, is no longer here. Check any forum here and it will be the same.

Sent from my SCH-I500
[Fascinate General] CNemo7539:
That's what I do - I talk about myself. My age, my vision of the problem and my situation. Are you talking on devs demand?

You are kind of confused, I guess. What is the difference between reading forum and IRC logs? It's not interactive. I've clearly expressed my opinion up to why I do not want ask questions there. Let leave IRC for devs. If you notice, I even didn't posted it into development forum, because it is full demands "Do not ask this or this"! But, I still think it would be cool if forums regain some former status!

I'm not pulling anybody here to post answers. Everybody does it at his own will.
[Fascinate General] CNemo7539:
Would be following of any interest?

http://code.google.com/p/demonstratortool4/source/browse/trunk/android2.1_init/hard_ril/rild/rild.c?r=13

What exactly is referred as "AOSP rom"?

Also, arynalyne mentioned that htc and moto published their RIL sources.

FAQ says opposite.

http://android-dls.com/wiki/index.php?title=Android_FAQ#Platform_Hacking_and_Development

Than more I dig, than more I hope it must be reusable between version of android, given that on the same phone.
[Fascinate General] adrynalyne:
I never said they shared the source to their RIL.
[Fascinate General] imnuts:
Try this and then think of a rom based on it. (ie. vanilla rom)
[Fascinate General] CNemo7539:
#47

Sorry, I might misinterpret it.

According to this pic Samsung proprietary part must be separate .so file.

http://www.kandroid.org/android_pdk/telephony.html

What I got from this discussion is that if I:

1: Take source from here http://source.android.com/source/index.html and build it.

2. Put binaries on top of what I currently have in my phone

It's not going to work. Solely because of RIL and initial settings? So, Samsung didn't provided settings as well? What else is missing?
[Fascinate General] J Shed:
Interesting thread. I'm gonna have to figure out how to view IRC logs (I've been working in the IT field for well over a decade, but I never hopped on the IRC train... odd) because I'm curious about the development going on.
[Fascinate General] CNemo7539:
Oh man! Again and again! One is so smart and bright, rest of us are dirt.

Source != binary

I've asked just to be sure that we are talking about source from Google, not something else. People are free to modify it, am I right? Who knows that was tried...
[Fascinate General] imnuts:
I searched for "aosp rom", and based on the search results, I could have easily figured out what an "aosp rom" was, without any previous knowledge of it...
[Fascinate General] jt1134:
At this point, RIL is the main issue. There are some open source parts for ril within aosp, but some of the needed parts (so's) are proprietary and must be pulled from a working build. You basically have a few binaries (rild/pppd_runner/etc), that you may or may not have source code for. Also, there is RIL code in the android (aosp) framework. These things must all cooperate with eachother.

Since I've screwed around with this immensely, I can tell you that Samsung absolutely HAD to have modified the android framework to suit their RIL so's. If you compile aosp and mix it up with the proprietary libs, you can watch the logs and see that the information provided by Samsung's RIL libs are not what the framework is expecting. So, a bit of reverse engineering is required, so that you can hack the framework to work correctly with the proprietary libs.

For an example of some of the things needed to fix these issues on the GSM I9000, look here. Those fixes are for GSM, and the Fascinate uses CDMA, so it doesn't help as much as we would like, and to date, no one has stepped up to hack in the appropriate fixes to the framework to get everything working with CDMA. Frankly, I've given up on it until Froyo drops. At this point, the only radio functions we have been successful with are outbound calls and sms. The phone always shows no signal, and data does not work, because of the previously mentioned issues with the android framework.
[Fascinate General] CNemo7539:
Thanks!

That explains why people were talking about porting from other phones.

Google has compatibility program now. I'm curious why Samsung was allowed to do such a bad thing as changing API. Feels like Google at fault too, at least partially.

I've mentioned punk.kaos before. May be as a developer you might have heard something about it. Seems like it was just a rumor. I cannot believe that that breakthrough didn't resulted into rom.
[Fascinate General] RacerXFD:
I would like to say that this is a very insightful thread a to why there is so much difficulty currently.
[Fascinate General] CNemo7539:
It might do good for stopping similar questions about froyo and such.

What do you think people?

I apologize if I've stepped on someone nerves. So sad that it took us so long to get to this point.
[Fascinate General] imnuts:
It sounds more like Samsung had a RIL working for 1.5/1.6 and didn't feel like making a new one, so they took the pieces the RIL needed from 1.5/1.6 and hacked them into 2.1 along with some other junk put in place to make the old RIL work with the new system. Maybe they're having their own RIL issues now that they did this and that's what's causing some of the delay with 2.2, along with Verizon not accepting buggy releases.
[Fascinate General] CNemo7539:
I guess it will be stupid thing to ask, but I'll anyway. Just for history. :-)

Over few threads scattered that DJ05 has some changes to modem and GPS. I guess GPS is separate chip. What about modem? Never heard that it has something in RIL department. Any luck?
[Fascinate General] Boushh:
That is the modem.bin, it is seperate from the RIL.
[Fascinate General] ivorycruncher:
Sorry, but I need to step in here in defense of punk.kaos. He is as real of a developer as any. He has created a masterpiece in KaosFroyo, arguably the best Froyo ROM available for the Droid Eris, and is now working on a Sense UI Froyo ROM and stock Gingerbread ROM for it, and is starting to work on other phones as well.

Somebody donated a Fascinate to him, but it had a hardware defect and failed shortly after he got an extremely rudimentary build of Froyo running on it, and he's never gotten a replacement to move forward with it (somebody gave him an EVO instead). What he had was not usable in any normal fashion, so it was not worth releasing.

Speaking of Gingerbread, kaos already has a booting Gingerbread ROM for the Eris, which he manually built from code straight out of the SDK. I'm not sure how he's able to do that if this RIL code being talked about isn't available, but he did. If he had a Fascinate in hand, he would probably be working on a Gingerbread ROM for it right now. I would love to donate one, but I simply can't afford to do that.

Anyway, please don't speak poorly of kaos, as he is one of the best devs on XDA, period.
[Fascinate General] CNemo7539:
That's interesting unfold!

First of all there wasn't any intend to say anything bad about kaos.

Let me ask you people - is it really my language? I do my best, but as mentioned before English isn't my native tongue.

I've posted link here and mentioned his name in hope that it was something real. A spark of hope. And if he managed to work it so some degree, may be it is possible to improve or something.

So, it was true, at least to some extent?
[Fascinate General] CNemo7539:
Now, when we know that Nexus S is pretty much same hardware may be someone has contacts in Google to ask if they did something in GB to support CDMA better?

May be they helped Samsung a little bit to fix their old crap and pass compatibility tests.
[Fascinate General] J Shed:
Pretty sure the Nexus S is a GSM device.
[Fascinate General] CNemo7539:
Sure enough! But GSM not a single radio standard. Even more are coming next year. And Google needs to be prepared for them.

Fragmentation was a high pitch noise all across the net. And looks like Samsung with VZ are great contributors. Did it happened because lack of support from platform side? Maybe?
[Fascinate General] J Shed:
Verizon is going to want to carry as many handsets as possible, and you can't really blame the carriers for wanting their own device. If you want to blame someone for the Fragmentation, it's probably gotta be Google, they opted to release the OS without a hardware standard (or even a specified button layout). That pic over at Engadget (Visualized: The Real Android Fragmentation) cracks me up.

That said, for the sake of THIS discussion, GSM devices are a moot point, regardless of how many radio bands they use. If we could use 'em, the devs would be cranking out AOSP builds. We're on CDMA, so we have to wait.

I'd be interested to see how things are going with our GSM bretheren, they have Froyo builds for Canada, wonder if the frequencies are the same.
[Fascinate General] imnuts:
Odds are, he (or someone else) created a working RIL for Froyo, and had the files and knowledge of what needed to be fixed/changed to get it working. Also, if HTC did a better job of creating the initial RIL, it may have needed much less tweaking to start with compared to our phone, at least based on jt's comment. I feel like RIL hacking is probably an acquired skill, similar to HSPL development, and there are a handful of people that are good at it. Sure, others can try, but it's not something that every Android developer is going to be able to tackle it. Either way, I'm sure that once Froyo is actually released, our devs will figure it out and we'll have all the custom ROMs and kernels we can handle.
[Fascinate General] gjmcmanus:
I have an idea, for all the people that are too impatient to wait for the official froyo to drop. Why don't you all get together and buy punk.kaos a fascinate, or donate money to him so he can get one.
[Fascinate General] ivorycruncher:
Back on post 63 you asked if he really had a working build or if it was just a bluff, which to me sounded like he was being accused of lying about it. Sorry, but I tend to take exception when my favorite dev is being accused of lying. Anyway, no hard feelings, all is forgiven. ;)

I agree that I believe there is more that can be done than is being done, but the right individuals need to be involved and dedicated as there are roadblocks to overcome, and right now the combination needed just isn't there. If Froyo ever gets released before the Fascinate effectively becomes obsolete, then there should definitely be more development efforts, but from what I understand, the time it would take to build a fully working ROM from scratch would be longer than the time it takes for the official Froyo build to become available, which will be much easier to build custom ROMs off of. Of course, I'm hoping we can actually skip Froyo and go straight to Gingerbread now, but I'm not holding my breath.

I just want any upgrade I can get right now, because the apps I can't run because I don't have Froyo are really starting to pile up, and I'm getting increasingly frustrated. I'm mad at Google, in part, for refusing to continue supporting Eclair with the updates to the Google apps. If 70-80% of the Android phones in use were running Froyo, then it's not as big of a deal, but last I heard, at least 70% of Android phones in use today are still stuck on Eclair, and it doesn't seem very smart to alienate the majority of your client base by refusing upgrades. Now I'm afraid that by the time I get Froyo, Google will cut off support and will only support Gingerbread for updates. Will the vicious cycle ever end?

I'm wondering if the biggest problem is that the OEMs are not used to having to do this type of development work, pre-Android, the only real cross-OEM mobile OS was Windows Mobile, and it was rarely updated. Now we have Google churning out new versions every few months. They probably have no clue how to efficiently write and test new code, or don't have adequate staff to do so, and from what I hear, good developers are in high demand and short supply as of late. Almost makes me wish I was a developer, but I just don't have it in me. I get headaches staring at vbscript code sometimes, even though I enjoy writing scripts for administrative functions. I'm more of a creative problem solving guy. In other words, I fix what doesn't work, as opposed to creating something new that inevitably won't work, which will then require somebody like me to fix. :D

EDIT: Oops, I just realized I went waaaay off topic here. Sorry guys.
[Fascinate General] ksizzle9:
RIL Hmm. I think I'll get one. This debate has been a good read. Thanks to all
[Galaxy S I9000 Q&A, Help & Troubleshooting] Mr Woolf:
I always remove any lagfix and tweaks when flashing themes, clocks or fonts with cwm recovery - am I being overcautious?
[EVO 4G Q&A, Help & Troubleshooting] Adam1422:
Why cant you play avi file types on the evo? Do I need to get a special media player?

EDIT:

1. is there a file type I can convert them to?

2. if so what software can I use to convert them?

Thanks in advance!
[EVO 4G Q&A, Help & Troubleshooting] sitlet:
You can play most avi's with Rock Player, however it depends on what codec the file is. If you want to play with the stock media player, you need to convert to an mp4 with h264 baseline codec. You can use handbrake to do this, there are guides everywhere. Heres one:

http://www.knowyourcell.com/htc/htc...deos_and_transfer_them_to_the_htc_evo_4g.html
[EVO 4G Q&A, Help & Troubleshooting] Adam1422:
Thanks again!

EDIT: Were do I get rock player, is it in the app market or do I need to find the apk?

EDIT2: Found it! Thanks again!
[Touch Pro, Fuze General] Timmetjuhs:
I would like to use my Touch Pro as a Bluetooth dongle since my laptop does not have bluetooth. I really need to update my parrot ck3100 carkit.

Is there any way to do this?

Thanks!
[Gen8, Gen9, Gen10 Accessories] wes_s:
Edit: I am selling these tablets, would anyone like one or both of these cases? First come first serve, you pay shipping.

Made a couple cases, one for the wife's 101 and one for mine. Posted this over at archosfans but I am pretty darn proud of my perserverance :) Almost a whole roll of duct tape went into this project.
[Gen8, Gen9, Gen10 Accessories] opendave:
Nice work. Duct tape rocks.
[Gen8, Gen9, Gen10 Accessories] BGMArchos:
I agree those are really great looking A101 cases.
[Gen8, Gen9, Gen10 Accessories] cajl:
see that

http://www.jbmm.fr/2010/12/09/photos-housse-archos-10-1-de-newmp3technology/
[Gen8, Gen9, Gen10 Accessories] KrewKracer:
Just ordered one, too!

A review and more pics can be found here! Sounds really good.

Under the pics at the link cajl posted a 10% discount code for newmp3technology.com can be found!

//EDIT: They have similar cases for the other archos ITs, too!
[Gen8, Gen9, Gen10 Accessories] cajl:
i wait all archos gen 8 cases for a review
[Gen8, Gen9, Gen10 Accessories] chrulri:
Dito! :cool:
[Gen8, Gen9, Gen10 Accessories] MoonPhantasm:
Same, already ordered one. That's too nice looking to pass. Although more will probably come out with cheaper price... ^^
[Gen8, Gen9, Gen10 Accessories] izrephyl:
Didn't find any case that was worth spending my money on so I decided to make my own temporary case

materials used:

Book cover

cardboard

duct tape

velcro

padding that came with the archos box
[Gen8, Gen9, Gen10 Accessories] caseym:
Wow those are really nice! Good job. So if I send you some duct tape, you'll make me one?! :)
[Gen8, Gen9, Gen10 Accessories] vypyr:
I love it. ^^
[Gen8, Gen9, Gen10 Accessories] deliverywong:
It looks nice~~~ love it
[Gen8, Gen9, Gen10 Accessories] wes_s:
Thanks guys :)
[Gen8, Gen9, Gen10 Accessories] wes_s:
I'm selling the Archos tablets. Does anyone want these cases?
[Gen8, Gen9, Gen10 Accessories] sasaborg:
i would like black/green one :)

i've also made some cases, but not even close to yours.

how much it would be to send it to bosnia?
[Gen8, Gen9, Gen10 Accessories] wes_s:
Im afraid shipping to Bosnia would be cost prohibitive for a free case. It would be around 40 to 50 USD.
[Gen8, Gen9, Gen10 Accessories] sasaborg:
when i ordered fully boxed archos from uk, royal mail delivery was 9 pounds. i guess the postage for the case would be no more than 3-4 pounds.

thanks anyway, nice cases :)
[Wildfire General] seamon:
Just wondering, but since Gingerbread is out now: I would love to know if:

a) it can be configured to run on the Wildfire?

b) how/who/when can do it, to make it happen?

c) if there are plans to build cyanogen mod on Gingerbread

Thanks and looking forward to it :-)
[Wildfire General] bpye:
You'll have to wait a few weeks as it hasn't been put on AOSP yet meaning the source isn't available. You might see a port of the emulator image on the nexus one as that has been done before with froyo. Once we have source it should(afaik) be a case of modifying the vendors that adeadrat and Jacob are using now to accommodate for the new build.prop etc.
[Wildfire General] Sympnotic:
everything you're asking is already answered

there's no point answering people who's flooding this developement forum
[Wildfire General] seamon:
warm welcome ...

well: I guess that wasn't the warmest possible welcome into the developing world. Hope for you guys that it's not all too rough out there ... I really have fun trying out the different custom ROMs that there are. I would even report bugs, as that's about the only thing I could contribute ...

still am excited to see how the work in Gingerbread for Wildfire is going, since I suspect it will be the last major release that can be run on the wildfire.

PS: This thread may not be completely lost if some folks who are into developing post any announcements on Gingerbread for Wildfire here ...

... have a happy Gingerbread Season!
[Wildfire General] HCDR.Jacob:
http://www.youtube.com/watch?v=e6blPgPp9OM
[Wildfire General] bpye:
Im guessing nothing further than screen is working atm?
[Wildfire General] HCDR.Jacob:
screen and buttons

testing a new build now with potential fix to allow me to make calls etc. :)
[Wildfire General] Sympnotic:
This topic perfectly answers your questions : [Q]Gingerbread for Wildfire?

I'm not saying anything against you, and you're a new comer, the least would have been to read some topics.
[Wildfire General] verbuyst:
Damn you already ported the gingerbread?! Nice work, How is it? Does it run smoother then 2.1/2.2 or is gingerbread more for tablets then this budget phone.
[Wildfire General] bpye:
What features do you want functional before release, calls, wifi?
[Wildfire General] aaddii9944:
I know it is a bit much but is there any chance we will hame a cyanogen rc3 built on 2.3?
[Wildfire General] Mtl Evan:
Jesus, guys. Give him some time.

Good stuff Jacob, hope you get it up and running.
[Wildfire General] krazykat:
Amazing. Looking forward to it Jacob! =D
[Wildfire General] jawbraeka:
good work guys... please refine this rom and make the wildfire a great purchase for all people as it is a great little phone..

Also i don't know if this could be done but can something be done in regards to the resolution of the wildfire... please lol or is there a replacement screen for the wildfire? ......cause i really would like to get another screen and if anyone knows where that would be great.
[Wildfire General] verbuyst:
I only know for the resolution of the wildfire, that there is a pixel density changer (I have no idea if this is any good, but you could look into it if you really want to change it)
[EVO 4G General] CheesyNutz:
we all know its going to happen but how soon till we see the leaks
[EVO 4G General] Sirchuk:
Leaks? It's already officially out. Nexus One's are receiving the update as we speak. As for an EVO specific leak from HTC/Sprint, who knows..I'm sure the devs will have something out soon if there aren't any major hardware changes / requirements.
[EVO 4G General] CheesyNutz:
SDK is out NOT a working rom its no "leaked" pushed yet to the nexus 1
[EVO 4G General] apollooff320:
This update sucks for me if it doesn't fix the CPU problem of almost maxing out when scrolling which causes scrolling to be laggy. If they don't fix this by the time my next upgrade comes up I'm switching to a Windows phone. I want a smooth interface.
[EVO 4G General] Sirchuk:
I guess I'm not following.

According to Engadget, Gingerbread, 2.3, is running on Nexus One's. They've received the OTA update.

Although, they may have been wrong and pulled the article and didn't say anything, since

http://www.engadget.com/2010/12/06/android-2-3-update-now-rolling-out-to-nexus-one-owners/

no longer appears to be a valid link, but it was just a half hour ago.

I think this is what it said:
[EVO 4G General] CheesyNutz:
the latest ota pushed to the nexus was just a minor update i don't think it was 2.3
[EVO 4G General] BrianDigital:
That might have been an old link where the nexus one got a security update and people jumped the gun on calling gingerbread
[EVO 4G General] Sirchuk:
Looks like Engadget was wrong and pulled the story. Nobody can confirm that 2.3 is out it seems, though some have tried to get their N1's to update.

Way to go Engadget, wrong information with no clarification. At least post a "Oops, we were wrong" update or something.

The N1 forums are saying it will be out on/around the 16th.

Edit:

Think they heard me:
[EVO 4G General] donatom3:
One of the main guys on the Android team tweeted that no ota was released for the nexus one and that the source would be released in the "coming weeks". My bet is that the first rom with working Gingerbread on it will be Cyanogen and within a few weeks of the source being released.
[EVO 4G General] Award Tour:
Yup, for our EVOs CM is the best bet and that will be AFTER the source (not to be confused with the Nexus One OTA) is released.
[EVO 4G General] donatom3:
Any sense rom will have to wait till a 2.3 gingerbread source is released by HTC which could be a while, if ever. Cyanogen is already on 2.35.9 kernel which hopefully means that porting their work to 2.3 shouldn't be that hard to do.
[EVO 4G General] drmacinyasha:
10 characters.
[EVO 4G General] Award Tour:
Not sure if there's any confusion with what I think I read from your post but.. I'm talking about the AOSP source not the HTC source. That'll probably take a month or so after the Nexus One OTA to be released and then another month or so before CM releases a RC of CM7/2.3.
[EVO 4G General] craig198:
windows phone? are you on crack?
[EVO 4G General] phazen18:
I'm guessing you won't see a Sprint/HTC Gingerbread ROM until sometime next year. Rumor has the source code being released when the Nexus S ships which is allegedly on Dec 16. Expect AOSP based Gingerbread ROMs to start rolling out around then and an Official Sprint ROM after sometime well after that, after its been thoroughly QA'd.
[Legend General] ishan_rulz:
Nexus S:

http://www.youtube.com/watch?v=lxUXulxE5o0

Gingerbread:

http://www.youtube.com/watch?v=Jx3pdWBlZ34
[Legend General] TheLegendaryJay:
http://www.google.co.uk/nexus/#!/tech-specs

Hurrah!

Maybe time to sell the Legend? :D
[Legend General] ANtiHazarD:
i'm just buy it :-D
[Legend General] TheGrammarFreak:
No trackball?! No dual core?! NFC barely used in UK?! £550?!

I shan't be buying it.

No sodding SD card slot?! I certainly won't be buying it.