[DEV] Atrix : Voodoo Sound similar method / Its a WM8993! - Atrix 4G Android Development

Hello all,
According to my depth researches, I'v summed up bits into a package:
- Atrix MB860 does have Wolfson WM9803L DAC chip. (1-?) (Even though all Tegra 2 AP20H should have the same SoC, but after a lot of questions, AP20H {Ventana} stands out for handheld performance (CPU, GPU), power only) Update: Wrong!
- The Asus Transformer uses Tegra 2 T20 , Wolfson WM9803L chip. Does have Voodoo sound support. Based on V1 voodoo drivers.
- I'v got into the same confusion about the 'L' in 'WMxxxxX'; The DAC is based on 2 revisions, both ends with L. Useless
- They both use same SoC implementation, very similiar drivers, nearly same headers. (Based on my own research.)
- Supercurio did not support the Atrix 4G, due its locked bootloader based on the V1 driver date of WM8903L. (So, he might not look back, Wolfson's WM1811 on the road) Update: Atrix 4G = Optimus 2x/Galaxy R
I know I might seem like asking questions, but it should also be considered as a dump project based on both devices. Plus, opening opportunities on other Tegra 2 hard/soft-ware porting.
I don't agree with the idea ignoring 1+ yr old phones with such capabilities...
I consider it just like the fame of the Gi9000, <<<Voodoo = major plus.
P.S. : Supercurio once stated that, Atrix 4G has a diff implementation... Though, after chatting over the IRC, he stated that he do not touch locked bootloader based phones. Thats totally different story. Diff implementation means indirect hardware access, using NVRAM i2c communication (registers)
Big thanks for supercurio, making our phones more valuable. Not anymore... -__-
Thank you all
I will appreciate any help/comment/feedback/correction/response.
Click to expand...
Click to collapse
Thats Bla bla bla above...
Conclusion: Voodoo sound is communicating with #? low level registers with the DAC. Same as what ALSA mixer do when modifying STdac (ICS leak). Unfortunately, Atrix uses OSS on GB, or barebone ALSA thought thats not a problem.
Project STATUS:
Found the right DAC, its WM8993!! Developers/Anyone try Optimus 2x Voodoo sound driver using the patch, patch it to the kernel (WIP)... Loading Voodoo Sound Plus modules didn't work :/
Alternative to Voodoo app coming soon for Atrix/Optimus2x/GalaxyR Tegra 2 Ventana
Workaround for ICS Leak kernel and Kernel 3.x (that includes tiny-ALSA), install AlsaMixer from Play, modify STDac Only While listening to music (be sure not to leave the head/earphones on) to 15. Now you can drive 300 ohms headphones (Though its still limited, shows 10db but not exact) Note: When you remove the earphones or stop music for 5 secs, settings will revert.
List of the confusing/wrong info about Tegra 2 DAC links:
http://forum.xda-developers.com/show....php?t=1124198 Those guyz heard from Androud forums lol
http://www.head-fi.org/t/549644/moto...-sound-quality That guy heard from xda! ^
http://androidforums.com/motorola-at...ola-atrix.html Those are the guilty ones (kidding ), they referred to Tegra 250, thats Harmony used in Tablets not Vantanna 250. :silly:

Having Voodoo sound on the Atrix would be great! I had a Samsung Vibrant before my Atrix, and Voodoo sound was pretty nice! I really like how it sounded and all the settings that it had.
One that i miss for sure is the ability to make the sound mono. I haven't found how to do it on my Atrix yet.
Keep the good work dude! Hope to see it done soon! If it can be done.

I'll be glad to see voodoo sound capabilities on my atrix.Wish you can port this without any problem.
MB860 cihazımdan Tapatalk 2 ile gönderildi

WOOOOOO!! YESSSS!! FINALLY!! I know its not ready, but thank you for looking into it!

djluis48 said:
Having Voodoo sound on the Atrix would be great! I had a Samsung Vibrant before my Atrix, and Voodoo sound was pretty nice! I really like how it sounded and all the settings that it had.
One that i miss for sure is the ability to make the sound mono. I haven't found how to do it on my Atrix yet.
Keep the good work dude! Hope to see it done soon! If it can be done.
Click to expand...
Click to collapse
Mono can be done as a software wise.
Use Poweramp, it has the mono DSP feature.
Good luck.

As stated guys, still haven't got my Atrix, and wish me a luck getting it .91 bootloader :/

bets of luck!! and it will be one hellova feat if u can pull this off ... i have used sgs, nexus s and sgs2 with voodoo ( yes i have purchasrd it from market )... and it makes them a formidable music player rival... i'd really really love to see it for ATRIX also

My friend had this on his Samsung Galaxy Tab and I have been jealous of him ever since lol. I was hoping someone would port it but had given up. I'm glad to see someone is on the case!
Sent from my MB860 using xda app-developers app

Guys, I need your help.
Test this: https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en
Or at Play store: Z-DeviceTest
I wan't an info about the DAC. Since i still don't have my Atrix 4G.
Just curious about the WM8903, this info was based on some rumors, a confirmation surely helps, since most tegra 2 ap20h are based on WM8990
EDIT: My Atrix is comming after 2 days...

what to check with that app ?
plus i found some things that u might want to read..( or already read it )
http://forum.xda-developers.com/showthread.php?t=1124198
http://www.head-fi.org/t/549644/motorola-atrix-sound-quality
http://androidforums.com/motorola-atrix-4g/265304-wolfson-audio-hub-hd-motorola-atrix.html

I have downloaded that app but i can't find anything about the DAC...

raghul said:
what to check with that app ?
plus i found some things that u might want to read..( or already read it )
http://forum.xda-developers.com/showthread.php?t=1124198
http://www.head-fi.org/t/549644/motorola-atrix-sound-quality
http://androidforums.com/motorola-atrix-4g/265304-wolfson-audio-hub-hd-motorola-atrix.html
Click to expand...
Click to collapse
Yes I already read it
However, the last link was a guess before the Atrix release i guess, though, what they said is about the Tegra 250 T20 not the A20HP...
All T20 has the WM8903L, while all the A20HP has the WM8990. Thats the confusing part, however, when i get the Atrix, Ill be analyzing the implementation they are using... Might be indirect driver, but i dont think so (Inside a SoC=Direct)
Confusing topic also: http://www.androidtablets.net/forum/shenit-com/18404-tegra-t250-vs-tegra-t20-same-thing.html
What also worries me about the Moto X2. It does have Tegra 2 Ventana. No voodoo sound support, or at least DAC lookout. I don't think there is any A20HP with WM8903 (Does moto play with the sound layer? It should be strict since its a SoC)
I'm not sure between an implementation fault, or lack of support (VoodooSound author). (Though the GS is old)...

Dude, tell me if there is any way i can help you. This is something i really want to help with this project.

Now this is the way for the diff. between T20/T2 ...
http://www.toradex.com/Products/Colibri/Modules/Colibri-T20
And guys, this thread is leaning towards dumping, which clarification can be simplified by yes or no (nothing new), due to poor documentation etc...
And please, can anyone test this https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en
It only shows the DAC name on SoC based systems...
Worked with Galaxy R. Result: WM8990 ...
Can't wait to get the Atrix. I'm eager about it...
Plus, I won't lean to the software part, only hardware.
In case it needs to be re-developed, I will work only on the driver. (More to C orientation / kernel...)
Edit: okay, thanks Night Walker! ! For testing the app

Okay guys,
Anybody owns one of these devices except the Atrix:
T2-A20HP:LG Optimus 2X, Motorola Atrix 4G, Motorola Droid X2, Motorola Photon, Samsung Galaxy R, Samsung Captivate Glide
Other: i9023, i9000, Galaxy Tab.
If yes, try the same app above, seems the only app that shows the chip info through alsa...
O2X uses different implementation, thats why supercurio gave a deep shot supporting it, even though, it only supports bits of the original voodoo capabilities...
Can't wait for the new Kaudio driver, might work with the Atrix with no SoC mods.
Just another sound driver made specifically for voodoo. (LG uses its own implementation to the DAC, its driver)

Here is a screen shot of the sound section of that app on my atrix running paranoid android 1.9.5

r3xx3r said:
Here is a screen shot of the sound section of that app on my atrix running paranoid android 1.9.5
Click to expand...
Click to collapse
Same as yours on neutrino 2.8.
MB860 cihazımdan Tapatalk 2 ile gönderildi

K, the Atrix 4G has a different driver...

Tpr0,
I'm unfortunately not a dev, but is there any way I can help with this project?

Guys, sorry for the delay, got ill. And yes, I know your intentions towards support...
I still haven't got my hands 'tight' on the project, got distracted by setting it up... (the Atrix kernel compilation errors)
Anyways, thanks guys, it certainly needs a (low level dev. me) I'm not a high-level programmer, more into hardware level (intermediate) But this project doesn't seem hard to accomplish, but poor documentation does it... ( IT is based on low level programming )

Related

Android 2.3 port from Nexus S to Galaxy S?

Hey guys,
what do you think, is it possible to port the Android 2.3 Gingerbread from Nexus S to our Samsung Galaxy S. Because it has a similar hardware!
/Discuss
You're fast , just wanted to ask this. Hope some legend dude will do this.
Theoretically it should be very simple to port the software. The only difference I can see from a hardware perspective is the NFC chip which simply needs to be disabled in software, and the missing search button which will need to be mapped to a menu long-press.
I did some work on the NITDroid project back when I had an N900, and neither of these is particularly difficult to do.
For nexus S info:
http://googleblog.blogspot.com/2010/12/introducing-nexus-s-with-gingerbread.html
http://www.google.com/nexus/#!/tech-specs
http://www.google.com/phone/compare/?phone=nexus-s&phone=samsung-galaxy-s
will the iNAND be a problem?
Supercurio says the devices use different types of memory.
Might be a bit of a problem
i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways
Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
yea the Nexus use the 16gb iNAND...
Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress
It must be far easier than a sense port or even cyanogen port.
Sent from my GT-I9000 using XDA App
One thing that also caught my eye was, that the video recording isn't HD... probably to not throw away boatloads of RAM for the camera...
Arkanius said:
Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress
Click to expand...
Click to collapse
I wouldn't bet on that. If Sammy released 2.3 in short order for the SGS it would cannibalize Nexus S sales. The aftermarket community is still the best bet.
binary110 said:
i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways
Click to expand...
Click to collapse
GPS is the same! Both using A-GPS Chips. The NFC Software must be Disabled, Bluethooth Updated to 3.0, Nexus S has only 2.1 and Video Recording Updated to 1280x720, Nexus S had 720x480
Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
Thats the biggest problem, I think. SuperCurios Tweet to iNand Tweet
Leandros
This a premature thread. Once a dump or aosp is released only then can we begin to do something about it. Till then this is a discussion thread and not related to development. IMHO
What about rfs? Im sure google is not using it. We will have to work that out as well.
2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!
Mycorrhiza said:
2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!
Click to expand...
Click to collapse
Everything is virtually the same.
I call up one the powers of the all powerful XDA to port the N:S for all the SGS's that are out there, so we can forget about samsung roms and use a normal google one
The Nexus S doesn't seem to support an external sd card. Likely another problem?
bigriot said:
The Nexus S doesn't seem to support an external sd card. Likely another problem?
Click to expand...
Click to collapse
Maybe... but I can live without an external SDCARD for now...

Android 4.0 Source

Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
I was wondering the same thing. if this is possible I might not even update it to GB cause it wouldnt make sense. Hopefully its possible.
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
thank your for you input on this matter. Can you please tell me which Galaxy S II is better i777 or the i727 because I am thinking of returning my LG Thrill 4G for the Skyrocket?
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
kleeman7 said:
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
That's the only difference in data speed. That's also the only area the i727 is better. In EVERY other way the i777 is better.
They have the same screen resolution, but because the 727 screen is bigger, so the pixel density is lower, most people won't notice, but its worth mentioning.
The processor in the 727 is a qualcomm chip oc'd to 1.5 GHz, vs a Exynos chip at 1.2 GHz. People say the qualcomm chip is inferior, and choppy. Most people won't notice it, but it is there. The exynos can be oc'd higher than the qualcomm chip. The qualcomm chip is the reason it won't get i777 or i9100 ROM ports. With the i777 and i9100 running the same chip you can port any i9100 ROM really easy.
I don't know specifics on GPU, but its widely accepted the i777 has better graphics and 3D processing.
The 777 is thinner and lighter.
They both have disabled nfc on board. Att to possibly unlock at a later time, maybe at ICS rollout.
If you have LTE coverage you need to think about the choice, if you don't have LTE, there is absolutely no reason to get the 727. I talked a little about other differences in your other thread.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
Did you check the TI site and read the 4460 documentation? The processors are almost identical. The 4460 is just a little more capable. Its still in the OMAP4 family with the exact same architecture. We'll have the LG gingerbread drivers shortly as well as the galaxy nexus ICS drivers which will get us started there. Kernel shouldn't be too big of an issue as again, same architecture on CPU, same exact gpu. Yea its gonna take a lot of time to get everything working but we don't need LG to do it. GB was more of a shot in the dark for this phone than ICS will be. Zero omap4 devices released with GB but it still got ported to a couple Motorola devices. ICS released for two devices, both omap4.
Sent from my LG-P925 using Tapatalk
I said this about GB too. I hope I'm wrong for all of your sake's. When people were saying GB was around the corner (in September), and I said December, people said I was being too cynical. Well ... here we are, December is right around the corner, and the GB port is not flashable in CWM, nor is it complete. I over-cynicized a little, but not much.
I think it's all great on paper, just like building a AOSP GB build for the phone looked simple, did that ever actually get off the ground?
As I look in the past, I use that to forecast the future. My guess is that there is no where near a functional daily use ROM for the Thrill until a ICS build comes from LG (I would guess no sooner than July). If the the Nexus S and Captivate running the exact same hardware (CPU/GPU plus lots of others) both made from the same company, cannot share ROMs with lots of dev support, I just find it hard to believe that a phone with a similar chip, packaged with other chips (WiFi, BT, USB, Power, comination unknown) by another OEM is not going to provide useful drivers for the small dev community here. Again, I would love to be wrong, but ...
To be honest I think the Thrill is more Thrilling (rim-shot) because it's an underdog, and it feels like a start-up, ground-floor opportunity to build and jury rig everything and frankenstein it together. I think it would be fun, and I would have loved to have been involved had I stayed. But, I moved on, as many others have. I can't wait for months for something like this when I will only have that phone for a year. I don't hang on to old tech, I sold my Captivate and it paid for my Galaxy S II, talk about the circle of life.
The Thrill is definately an underrated phone, but it's also not the highest end phone. As I said before, as it stands it's definately the best AT&T phone for less than $100, it's the king of the mid-range offerings. Unless you can get the i777 for $50 or less, like many places have advertised for Black Friday.
I wish everyone the best of luck with the Thrill, but the reality train is leaving the station, and I feel my welcome may just be wearing thin here.
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Demonface said:
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Click to expand...
Click to collapse
it'll be about 3-8 months before other devices will recieve ics. samsung has the same problem. they still haven't updated the charge, fascinate, captivate and infuse.
tampaboy1984 said:
Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Trekfan422991 said:
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Click to expand...
Click to collapse
This is after all the reason why I got this phone cuz of the chipset and the fact that ICS is designed for it
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Thats very good news , Hopefully it gets released soon. Instead of using GB I would go straight to ICS when its released. Does anyone have the link to the video because I cant seem to find it.
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
seriously i know your trying to help us keep a grip on our excitement.. but its starting to get annoying seeing your comments pop up here all the time after you switched weeks ago.. and they are all how the thrill has potential but im so happy with my choice... like we cant even get our hopes up because your too afraid of our dreams getting dashed to pieces... we should all follow your example. i know thats not what you mean but it feels that way...
like many others i choose this phone based off the hardware specs... so i will be sticking it out for a few months at least if not for a few years.
we know the decision you made to switch and that you have support for the thrill and knew it to be a good device.. there is no rule about posting in forums for phones you dont have.. but please... please ease back a bit on clarifying all the realities for us...
there is nothing wrong in wishing.. we had no development for ages, it feels like, and now we have some things to look forward too, thats all!
so give us our hopes please... *tears up* its all we have!
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Wait wait wait...
You mean AT&T doesn't give super fast firmware updates to their phones?!
Here's what I will say about this phone so far...
I like it. It's treated me better than any Samsung phone I've had. It does everything I need it to.
I can't really remember ever saying "I wish this phone could..." that I wouldn't say about any other phone.
I hear people talk about how fast this phone is and that phone is and how fast the GSII compared to the Thrill. But how much faster is faster? The web browser pops up a second faster? A file is downloaded 10 seconds faster? I don't really think a lot of that is that big of a deal. It almost reminds me of the Crackberry forums when they were talking about not going to Android because the email isn't push (which isn't true) and so you got your emails a whole 30 seconds later. I mean, c'mon, how many of us are in a position where if we don't get that email 30 seconds faster our entire corporation loses billions?
I think it'd be cool to get 2.3 or above right now because there are a couple of games I'd like to play that are on 2.3 or above. But considering I have 25 games already installed and over 1/2 of those I ahven't touched, it's okay.
I've had a few Samsung phones and everyone of them I had had a lot of issues. I went through 8 Captivates. Now I did have to return one Thrill and exchange it but every Samsung phone I've had, I've had to get replaced at least twice. I keep saying I want a Note but then think about how bad I've had it with Samsung phones.
Phone technology is crazy. The thrill came, then the GSII, then the GSII skyrocket and the HTC Vivid, then there are three new Galaxy devices coming to AT&T in the next 2-3 months, and whatever awesome quad core devices, and then pretty soon we'll have the hologram phones in which you tell the phone to contact someone and they pop out of the phone like in Star Wars.
Honestly, I think I need a couple more pairs of shoes more than I need a newer phone.
CallMeAria said:
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I won't get drawn into a pissing contest regarding dev support of the Optimus 3D vs the Galaxy S II (i9100).
But, I will respond.
I'm sorry I over estimated and called that port half functional, you are right: its not a half functional port.
The build status of CM9 for the phone that half the Cyanogen team was given months ago is unknown to me. I made no claims on timelines, just forecasts based on the past and opinion.
There is indeed a very similar ICS ROM built for the i9100 (and by extension the i777) from the source that just dropped, but I cannot comment as to whether or not it was put together by a "legit cm dev."
I am not a developer, no. I am just an observer, an observer that tends to be realistic with expectations, and generally accurate.
I don't accuse the community here of being ignorant or naive. I can see that some people here do have realistic expectations.
I too was once an Aria, Captivate and Thrill fanboy. Today I am a GS II fanboy. I picked my team, as you have too. I don't think there is anyone on xda that isn't passionate about their phone.
I will not dignify further condescending comments from you with a response. This is the last time you will see me on the Thrill forums. Do not take my future lack of response as an admission of your perceived superiority. And do not take my comments to imply I believe I am better than you. I know you built a ROM, and were the first to share how to port O3D ROMs. Just because I never used your contributions I will not be so arrogant to say they don't exist.
And with that, I will be on my way. Again, best of luck to every one with a Thrill.
Sent from my Galaxy S II (i777)
Just checked out the optimus 3d thread about ICS and it seems that Ricardo is getting a lot of progress done and it seems like its getting done quickly. So hopefully it gets released before Christmas
. BTW I know that's still a long wait still but it would all be worth it.

Which phone to choose guys?

Guys I am planning to buy a new phone. I want your suggestions about choosing the right one. I am relying on good battery life and phone which has a good amount of development going on (custom roms, kernels, miui, cyanogenmod, ics etc.) coz I love to fiddle with devices a lot. My current choices are :
Samsung galaxy R
Samsung galaxy S plus
HTC Desire S
HTC Incredible S
These are my options but senior members can suggest me phone in range of 23000 INR ($475).
Thanks in advance guys
Sent from my MIUI powered I9003 via Tapatalk
I came from the I9003, and I am pleased with the development of IncS, the Desire S might have more development. Samsung S+ and R both have the same level of development as the I9003.
Other impressions are: the sound quality of the earpiece of the IncS is not so good compared to the I9003. Music playback using headphone from the IncS is virtually unlistenable to me, the quality is too f***ed up for me, even worse than the I9003 which is not so good by my standard. Although this is kinda biased considering my audio setup on my PC is about a grand and my headphone setup is around 600$. Otherwise I'm more pleased with HTC firmwares and AOSP development here compared to Samsung.
whats wrong with your current phone? Your "upgrade" path seems to be a step sideways.
None, if I got a new phone on a budget, Id get a Sensation or Galaxy s II, the prices will really drop as the new phones are released in the next few months. They both have great developer support, and are dual core
Both those Samsungs dont have great developer support, and the HTC's mentioned are not cutting edge tech.. just my two cents
When I upgraded it was a mere 25$ spent, but yes now that you mentioned it, it is kinda a sidegrade that you only should do if you can do it cheap or you are fed up with the development of the I9003, which I did.
Nonverbose said:
whats wrong with your current phone? Your "upgrade" path seems to be a step sideways.
Click to expand...
Click to collapse
I am planning to gift this phone to my brother. Had bought this phone something like 1 month ago. So hunting for new handset
Sent from my MIUI powered I9003 via Tapatalk
markj338 said:
None, if I got a new phone on a budget, Id get a Sensation or Galaxy s II, the prices will really drop as the new phones are released in the next few months. They both have great developer support, and are dual core
Both those Samsungs dont have great developer support, and the HTC's mentioned are not cutting edge tech.. just my two cents
Click to expand...
Click to collapse
Thanks for the great info. Now I am in a fix. Might be my brother will have to bear with his old phone. Sheesh!
Sent from my MIUI powered I9003 via Tapatalk
bigeyes0x0 said:
When I upgraded it was a mere 25$ spent, but yes now that you mentioned it, it is kinda a sidegrade that you only should do if you can do it cheap or you are fed up with the development of the I9003, which I did.
Click to expand...
Click to collapse
Hmm. Will have to get a better deal on galaxy s2 maybe or sensation
Sent from my MIUI powered I9003 via Tapatalk
ashzoomerintrack said:
Hmm. Will have to get a better deal on galaxy s2 maybe or sensation
Sent from my MIUI powered I9003 via Tapatalk
Click to expand...
Click to collapse
The htc Evo 3d is well within your price range, its got a larger screen, dual core processor, more powerful gpu and better dev support as well as being 3d.
Also the Droid razr is another high end phone that I have read many good reviews about. The price has dropped somewhat, and you could find one within your budget if you looked hard enough.
It really depends on what your criteria is, I personally have mixed feelings about the IncS and probably HTC phones in general. I also own a very low budget device, a huawei u8180 and I am actually 10x more satisfied with that than what I am with this phone. There's really only one dev with one rom/kernel worth using, but he is absolutely amazing, and constantly updating and improving his work, squeezing every last drop of performance out of such a low end budget device.
I could go on, but I don't want to upset the few devs who thankfully haven't forgotten that we still exist.
ashzoomerintrack said:
Guys I am planning to buy a new phone. I want your suggestions about choosing the right one. I am relying on good battery life and phone which has a good amount of development going on (custom roms, kernels, miui, cyanogenmod, ics etc.) coz I love to fiddle with devices a lot. My current choices are :
Samsung galaxy R
Samsung galaxy S plus
HTC Desire S
HTC Incredible S
These are my options but senior members can suggest me phone in range of 23000 INR ($475).
Thanks in advance guys
Sent from my MIUI powered I9003 via Tapatalk
Click to expand...
Click to collapse
Samsung R is the way to go. Because it is basically a stripped down version of the Galaxy S2. But the things is, it isn't available any more in india in many shops and THERE IS NO CYANOGENMOD FOR IT! Not official at least.
The second choice would be the Incredible S
Reasons:
1. Cyanogen mod 7. Official
2. better screen than the Desire
3. Better camera than any of the mentioned phones
4. SRS audio is amazing. And add to that, if you root it, you get DSP manager and trust me, after DSP, there isn't anything better than this device.
5. Overclocks up to 1.5 GHz. That's more than the amount on the Galaxy
6. 768MB ram
7. The softkeys can be completely made to disappear. Once rooted though.
jhon101 said:
Samsung R is the way to go. Because it is basically a stripped down version of the Galaxy S2. But the things is, it isn't available any more in india in many shops and THERE IS NO CYANOGENMOD FOR IT! Not official at least.
The second choice would be the Incredible S
Reasons:
1. Cyanogen mod 7. Official
2. better screen than the Desire
3. Better camera than any of the mentioned phones
4. SRS audio is amazing. And add to that, if you root it, you get DSP manager and trust me, after DSP, there isn't anything better than this device.
5. Overclocks up to 1.5 GHz. That's more than the amount on the Galaxy
6. 768MB ram
7. The softkeys can be completely made to disappear. Once rooted though.
Click to expand...
Click to collapse
I had encounters with Samsung phones and I'm very disappointed in them , I'd go with a HTC and between Desire and Incredible definitely go for the Incredible S , I just gone from desire to incredible myself and its quite a jump , much much much better performance not laggy nor choppy , much more dev , love the S-LCD nice colored screen , the firm shape and the 8mp camera is just an overkill ^^
Jhon101 , how do you hide the softkeys? o.0 in cyanogenmod?
Imp0stoR said:
I had encounters with Samsung phones and I'm very disappointed in them , I'd go with a HTC and between Desire and Incredible definitely go for the Incredible S , I just gone from desire to incredible myself and its quite a jump , much much much better performance not laggy nor choppy , much more dev , love the S-LCD nice colored screen , the firm shape and the 8mp camera is just an overkill ^^
Jhon101 , how do you hide the softkeys? o.0 in cyanogenmod?
Click to expand...
Click to collapse
It's a script. The lights are based on an LCD display and aren't like the ones on Galaxy phones where the logo just gets lighted up and it's there even when the phone is off.
Here's the Method:
1) Download and install GScript Lite from Android Market. Its free
https://market.android.com/details?i...riptLite&hl=en
2) Download the attached gscript.zip file and extract the two files buttonledON.sh & buttonledOFF.sh to SDCard/gscript (make "gscript" folder in root of sdcard if not present already)
3) Run Gscript Lite. Allow root permission .Click Menu >Add Script.
If u have placed the two script files in correct folder, they will appear. Open and save them both. (dont edit anything other than the Name..you can change it to LED ON/OFF... Run one to turn off led light, other to turn on back to norma)
4) Two icons of script will be there to let you turn on/off those led lights.
Here's the link of the two files : http://forum.xda-developers.com/attachment.php?attachmentid=744519&d=1318170330
You just got to be rooted that's all.
And mine doesn't switch on and off on will but is actually controlled by the baclklight settings. Eg: At lowest light, the Softkeys won't be viewable!
But of course you can access them. And they're brightest when you make the backlight the brightest. more convinient this way!
All credit goes to: jjdoctor for coming up with the script!
Make sure to hit thanks if I helped.

Dead

It seems to me that this phone has reached death. All the forums seemed to have died (here,droidhive,rootzwiki,android-den(which hasn't really taken off) and where ever else) and quite frankly I'm disappointed. There really hasn't been any steps forward in ICS since I don't even know when (hw codecs/bluetooth/whatever else). Unfortunately I'm still 9 months away from upgrading.
I don't mean to sound like I'm complaining because I really do appreciate all of the dev work thus far(Hashcode, sparkyman, and others are the shiz), but its like we've hit a brick wall. ICS isn't complete and won't be and gingerbread doesn't seem good enough. I am grateful of everyones work. I just wish more Could be done.
Sent from my XT862 using xda app-developers app
This was my first android phone and obviously a mistake. Not that I should have gotten an iprison(I am anti I everything). I hope progress can be made. At this point though I'm sure Motorola Was and Is a mistake and I should have known better previously owning a Q9C.
Sent from my XT862 using xda app-developers app
This should be in general
Sent from my XT860 using xda premium
Endoroid said:
This should be in general
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
why? It's about the development - the phone itself isnt dead.
But I agree. I was hoping to use this phone for 2 years (using 0.5 year now). I thought that eventually, we'd get ICS like we deserve. Guess not . I'm not sure how fast/supported this phone will be using gingerbread in 1.5 year
and except Droid 4 and RAZR MAXX..what other options we've got?!
galaxy no way (too big and overrated), and HTCs are all the same: big and no qwerty. nothing to get out of the crowd...like RAZR MAXX.
i used to be a fan of HTC, since S710 days..but now i'm bored by their lack of originality. no qwerty and no good processors for the small ones (<4" display).
not really dead everyone just faced the fact that ics will not happen for the d3 and blame the lack of ram for it..although we have proven that the d3 does and can handle ics and it does improve it no dev will continue to develop it due to the locked bootloader and the work involved to write all new kernals and bypasses fir it..there are 2 great gb roms in development..team haters (my fav) and mavrom{my 2nd fav}..both development crews hang out on droidforums stop by say hi and give their roms a whirl
Because its not development, its venting about our forgotten phone. And while I feel the same as you, its still not development
Sent from my XT860 using xda premium
I noticed the same thing but dont really mind.
Im on a ATT contract for another year and 4 months or so.
Ive always wanted a droid and got the droid 3 because it works on att. It has to be the best sliding keyboard phone out their, and beats using any virtual keyboard IMO.
Even if development isnt strong, we have got it better then a lot of other phones. We have stable gingerbread roms and we can overclock it.
The Droid 3 is still a good phone and i know il be getting a good year of use out of it. .. hopefully then keyboard phones come back to life...
But i never used to post really on these forums but seeing they are kind of dead, i decided to become as active as i can to help around.
Is the droid three dead? Yes, in a way. The phone's bootloader is locked. This is the ONLY thing that is stopping any major developments on the Droid 3. If Moto, or google at this point, decided to unlock the phone... We would have Ice Cream sandwich 100% working (provided that they released the source code as well), and we would be eagerly looking forward to Jelly Bean. I often go on the Google+ Google account and harass them, I know I won't win but I am always hoping for a miracle.
As it stands now, there is a large chance that I will leave Verizon when my contract is up. Their handling of this phone as well as their pocketbooks has left a bad taste in my mouth. After 6/28/2012 (my birthday of all things), any phone being upgraded via contract will LOOSE their UNLIMITED data. You will have to purchase phones off contract to be able to keep your unlimited plan (It's only like $400 for a good android phone). Not only that, you will be charged a $30 fee just to upgrade.
So in conclusion:
Our phone is on life support. We are getting by with such developers as TeamHaters, Maverick, and Hashcode (who's still realasing AOKP updates for our phones), who are doing an excellent job keeping our phones working the best they can with what they have. Until there is a cure for our Bootloader issue... Our phone is stuck in intensive care, and Patch Adams is their to annoy the hell out of it.
Does anyone think googles new PDK will help our device? its supposed to allow low level api for easier porting of android to hardware. Think this could bring around any fixes? Ofcourse the bootloader will be locked but it mite make the making of kernels not take 6-8 months as hash said and help him out.
Sent from my DROID3 using Tapatalk 2
jesusishere said:
This is the ONLY thing that is stopping any major developments on the Droid 3. If Moto, or google at this point, decided to unlock the phone... We would have Ice Cream sandwich 100% working (provided that they released the source code as well), and we would be eagerly looking forward to Jelly Bean.
Click to expand...
Click to collapse
*sigh* I hate to be the one that has to come in and burst everyone's bubble every time someone makes this argument, but the problem is not the locked bootloader. If the bootloader was unlocked, we'd be in the same exact position. Hashcode has stated this several times. We'd still be without hardware codecs, we'd still be having Bluetooth issues, we'd still have all the same issues because they're all a matter of hardware limitations or lack of documentation on certain parts of the proprietary hardware.
Pokelover980 said:
*sigh* I hate to be the one that has to come in and burst everyone's bubble every time someone makes this argument, but the problem is not the locked bootloader. If the bootloader was unlocked, we'd be in the same exact position. Hashcode has stated this several times. We'd still be without hardware codecs, we'd still be having Bluetooth issues, we'd still have all the same issues because they're all a matter of hardware limitations or lack of documentation on certain parts of the proprietary hardware.
Click to expand...
Click to collapse
It's the combination between the bootloader and the source code
Sent from my XT862 using xda premium
jesusishere said:
It's the combination between the bootloader and the source code
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
It's more of a "TI doesn't support hardware codecs for devices >1GB data". TI doesn't release source code for those binaries and isn't obliged to, so that's not really an argument that should be made. It's simply that our phone was cursed from release.
EDIT: And as of now I can no longer say "our phone" as I jumped ship to the Razr... goodbye, Droid 3 community, you will be missed...
When Ics gets released this year for droid it is getting better
Sent from my DROID3 using XDA
Nope, it's not, because ICS isn't going to be released to D3. This is it, for better or worse.
Rocking with my M3 and XDA app
AragornPE said:
Nope, it's not, because ICS isn't going to be released to D3. This is it, for better or worse.
Rocking with my M3 and XDA app
Click to expand...
Click to collapse
who cares. I had ICS on a device before and its not that different besides a different interface .. after using ICS i prefer gingerbread's layout..
Juicy555 said:
who cares. I had ICS on a device before and its not that different besides a different interface .. after using ICS i prefer gingerbread's layout..
Click to expand...
Click to collapse
ICS is majorly different from previous releases under the hood. It uses a different kernel; things have been made more efficient; the APIs have been updated to allow for more possibilities for app developers; certain parts of how the system overall operates have undergone drastic resigns; etc.. All of this came at the price of needing better hardware to incorporate new features, but I say it was well worth it and is a very large difference even without the interface changes.
Pokelover980 said:
*sigh* I hate to be the one that has to come in and burst everyone's bubble every time someone makes this argument, but the problem is not the locked bootloader. If the bootloader was unlocked, we'd be in the same exact position. Hashcode has stated this several times. We'd still be without hardware codecs, we'd still be having Bluetooth issues, we'd still have all the same issues because they're all a matter of hardware limitations or lack of documentation on certain parts of the proprietary hardware.
Click to expand...
Click to collapse
but anyway hashcode would be able to trial and error approach without deeming the device unusable (loading kernels, and modules and stuff)
it would certainly help to have an unlocked bootloader.
but without source of course it would be time consuming and without knowing when it would have success
bogdan_wrc said:
galaxy no way (too big and overrated), and HTCs are all the same: big ...
Click to expand...
Click to collapse
This thing is a brick in my pocket compared to galaxy line and most htc phones, check out the quad core HTC One X w/beats audio or the galaxy note etc for "originality" but seems like all manufacturers are using a very similar forum factor. I agree the qwerty is nice to have but it doubles the size of the phone as well(unless maybe desire z) so you kind of have to choose.
Willis111 said:
This thing is a brick in my pocket compared to galaxy line and most htc phones, check out the quad core HTC One X w/beats audio or the galaxy note etc for "originality" but seems like all manufacturers are using a very similar forum factor. I agree the qwerty is nice to have but it doubles the size of the phone as well(unless maybe desire z) so you kind of have to choose.
Click to expand...
Click to collapse
I came from one of those phones and dont mind the difference. In fact the keyboard is one of the best features ive had on any of my smartphones. And a 4" is perfect for me, coming from a 4.5" screen.

OpenGL issues?

Hi all, not sure if this is the right place but I'm having trouble with OpenGL on the Samsung Galaxy S/Vibrant.
Do any developers here know how the Vibrant differs from other devices in how it renders OpenGL? Particularly it doesn't deal properly with non power of 2 size textures, and it will not display two GLSurfaceViews at once. The Vibrant is the only device I've had these problems with among all the devices I've tested.
This is using OpenGL 1.1 with a modified version of min3d library.
enderx1 said:
Hi all, not sure if this is the right place but I'm having trouble with OpenGL on the Samsung Galaxy S/Vibrant.
Do any developers here know how the Vibrant differs from other devices in how it renders OpenGL? Particularly it doesn't deal properly with non power of 2 size textures, and it will not display two GLSurfaceViews at once. The Vibrant is the only device I've had these problems with among all the devices I've tested.
This is using OpenGL 1.1 with a modified version of min3d library.
Click to expand...
Click to collapse
No.. No .. this is Sparta!! Develop section .
Why bro.. I'm sorry but let the flamin' begin....Naaooooew
Lol and I was wondering why no one flamed yet looks like it might begin soon ;P
PS. This should be in the q&a section....sighhhh....
I was cutting him a break
1. He said he wasn't sure if he was in right section
2. I have no idea about his question.
Love this community!
No tickee, no laundry!

Categories

Resources