Paul (or anyone who knows)...
How close are you to a Beta version of your ICS port for the OG Transformer?
I think you have done more than anyone in trying to get this stable before Asus releases their version, and definitely offer a way to get Root on the TF101 ICS.
I really just wanted to start a thread that would allow for Version updates to your port, where people can see a status from the developer himself!
Thanks!
Jeff
--
"I've donated to Paul...Have you??"
It's probably close. What's supposed to work, works.
Sent from my Transformer TF101 using Tapatalk
If you are a gamer stay clear for awhile yet or atleast till official comes and devs can kang some parts
Sent from my Transformer TF101 using xda premium
gVibeR said:
How close is Paul Burton to Beta?
Click to expand...
Click to collapse
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
gVibeR said:
How close are you to a Beta version of your ICS port for the OG Transformer?
Click to expand...
Click to collapse
Oh right, the ROM. Beta is a blurry line, I may not even use it and just keep incrementally improving it until it feels like RC time (and when I say RC I mean a build I actually consider suitable for final release, not the linux "release candidate but we'd never actually consider releasing this" terminology). I think once I get libsensors & libcamera written the hardware support will all be there at least in a basic form and then polishing and fixing smaller things will improve it quickly. I'm hesitant to put a timescale on it - I can't spend the time of a full time job on this and the time I do spend on it is a little sporadic. I'd hope to have sensors working within the next week or so, if that helps. I'm also planning to look at doing OTA updates of some sort now that it's basically usable for common tasks (for some people), to keep people updated easier and perhaps lighten the load on my web host by doing deltas.
I apologise for the terrible joke above...
Without access to the full source code for the drivers, any ROM based off of generic Android will never be Beta or better...
Paul's ICS port is from the standard Google ASOP tree, with lashed in binaries from other sources. What Asus deliver will be built for the specific platform.
There is a HUGE difference.
My experience of Paul's ICS was quite good, the biggest gripe for me, was the REALLY choppy sound playback, which was a deal-breaker for me, and I went back to honeycomb.
im not to sure about the binaries just being ported in i think paul is writting a whole lot of his own stuff, i could be wrong tho. i read a txt where he talked about writting his own drivers for everything cuz asus code is sloppy, he said he would prefer write his own than just plug in binaries.
CrazyPeter said:
Without access to the full source code for the drivers, any ROM based off of generic Android will never be Beta or better...
Paul's ICS port is from the standard Google ASOP tree, with lashed in binaries from other sources. What Asus deliver will be built for the specific platform.
There is a HUGE difference.
My experience of Paul's ICS was quite good, the biggest gripe for me, was the REALLY choppy sound playback, which was a deal-breaker for me, and I went back to honeycomb.
Click to expand...
Click to collapse
Umm, with all due respect - you're wrong. Asus aren't necessary. The only things remaining as binaries are the graphics drivers and they're from nvidia.
paulburton said:
Umm, with all due respect - you're wrong. Asus aren't necessary. The only things remaining as binaries are the graphics drivers and they're from nvidia.
Click to expand...
Click to collapse
So Asus have released the sources for ICS Wifi, Bluetooth, Audio, Camera and sensor drivers?
That's news to me, or are using using the honeycomb sources and patching them up with sticking plasters to work with ICS?
CrazyPeter said:
So Asus have released the sources for ICS Wifi, Bluetooth, Audio, Camera and sensor drivers?
That's news to me, or are using using the honeycomb sources and patching them up with sticking plasters to work with ICS?
Click to expand...
Click to collapse
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
paulburton said:
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
Click to expand...
Click to collapse
Paul Burton, serving up wanton coding justice to non-believers like it ain't no thang.
Keep up the good work, but I do think you need to assign a cool name to this project.
paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
Click to expand...
Click to collapse
Too funny, lol. Keep up the good work, and thanks for the posts. Always informative.
paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
Click to expand...
Click to collapse
LMAO a good dev with a great sense of humor! Or great dev with good sense of humor, I can't tell which
paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
I apologise for the terrible joke above...
Click to expand...
Click to collapse
Don't apolgize, that's what i call the so famous british humour . Please keep developping and joking that way Sir Burton.
paulburton said:
People outside of asus can write code too
Click to expand...
Click to collapse
Awesome! !!!
You sir need a TARDIS. That was Brilliant.
paulburton said:
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
Click to expand...
Click to collapse
Just a side note (and I'm not I repeat not complaing about this thread) for those who are asking for updates (nobody asked for updates here) about Paul's releases you should find them when they appear. It does not make it easier for him to complete them if he has to answer a zillion posts about when it will be ready (still not complaining) for release. Think about this...... he could be watching tv or going to the pub or doing stuff that he really needs to do like school (still not complaining) instead of coding.
Again I would like to emphasize that I am not complaining about this.
Oh and Paul how were your exams?
Sent from my Infected Galaxy Y using Tapatalk
Dreamboxuser said:
Just a side note (and I'm not I repeat not complaing about this thread) for those who are asking for updates (nobody asked for updates here) about Paul's releases you should find them when they appear. It does not make it easier for him to complete them if he has to answer a zillion posts about when it will be ready (still not complaining) for release. Think about this...... he could be watching tv or going to the pub or doing stuff that he really needs to do like school (still not complaining) instead of coding.
Again I would like to emphasize that I am not complaining about this.
Oh and Paul how were your exams?
Click to expand...
Click to collapse
It's true, my life contains things other than writing this ROM. Fortunately for you guys I don't own a TV
Exams went well thanks, all are above 70% (so 1st class) and the one I thought went horribly turns out to be my best grade. Odd
What kind of student are you, Paul?
asdfuogh said:
What kind of student are you, Paul?
Click to expand...
Click to collapse
Read his profile.
http://forum.xda-developers.com/member.php?u=4421777
Hey Paul,
Just wanting to keep everyone up to date...
Could you give us a status of what still is not working with your latest release Spark?
Now that you have a name for your rom, and have replaced the original warning with your new one, would you say this release is usable for most things?
Thanks a ton for your work...who needs Asus, we got Paul !!
Related
seems to be a concern whether i should use original framework from Toshiba with its better hardware support, or make a Nvidia framework edition with less good support for speciifc parts of the hardware like BT and USB.
So question with this poll would be what is the preference here..
If you can pack all the supported stuff in there, better hardware support from toshiba should make it more stable, right?
btw. : Is this the Foliomod offtopic thread?
I'd like to rage about the toshiba forums somewhere.
Spikoror said:
If you can pack all the supported stuff in there, better hardware support from toshiba should make it more stable, right?
btw. : Is this the Foliomod offtopic thread?
I'd like to rage about the toshiba forums somewhere.
Click to expand...
Click to collapse
this was actually an incorrect post, sadly it got posted..
you find the "general" thread here for OT non-foliomod topic.
THX, you care like a mother ^^
Nvidia
Hi Dexter
I tried 1b but returned to v2 because it seems a fair bit more responsive.
My vote is for Nvidia and some wifi and bluetooth fixes.
Thanks again btw
iansykes said:
My vote is for Nvidia and some wifi and bluetooth fixes.
Click to expand...
Click to collapse
as Nvidia uses a different hardware, this is likely not going to work very well with toshiba hardware.
Dear Dexter_nlb
At first, I bring to you a thanks from more than 100 Chinese users. Your roms realy fix lot of prolbem for AS100.
I translated your question and post it at a most popular android forums in China Yesterday.
Until now, 9 people agree a Nvidia framework ROM, 3 people want still keep Toshiba framework.
In that post, all users hope can fix the gravity sensing's prolbem (the gravity upside down in some gam, and run the Bubble in landscape screen time)
3 users want keep app from Tosiba, like Tosiba market, FileMgr.
Just 1 user want keep the Tosiba Desktop.
Hope that infomation can help you.
sorry about my english not good, but i think you can read it.
gfpyc said:
At first, I bring to you a thanks from more than 100 Chinese users. Your roms realy fix lot of prolbem for AS100.
Click to expand...
Click to collapse
thanks for all your feedback!
i think the only way forward, is that i keep both editions alive..
having 0.2 being nvidia based moving forward from 0.2a ->
and Toshiba edition which personally i like, to move from a 1.0 state and forward.
i might just need to change name of one of them..
but yes, it seems somehow majority want a nvidia, with less hardware functionality (at least seen from 0.2) and maybe with BT fixes in future update.
and that i might just agree on IF i cannot fix paid apps download, which for 2 days has been really annoying. (i even got an account from a supporter with a paid app, so i could test this)
if time is available, i will try and make 0.2a grow with a 100% 360degree fix and hopefully a better BT fix.
Dexter_nlb said:
as Nvidia uses a different hardware, this is likely not going to work very well with toshiba hardware.
Click to expand...
Click to collapse
Oh~bad news, I'll go to the Chinese forum ask them again.
Dexter_nlb said:
thanks for all your feedback!
i think the only way forward, is that i keep both editions alive..
having 0.2 being nvidia based moving forward from 0.2a ->
and Toshiba edition which personally i like, to move from a 1.0 state and forward.
i might just need to change name of one of them..
but yes, it seems somehow majority want a nvidia, with less hardware functionality (at least seen from 0.2) and maybe with BT fixes in future update.
and that i might just agree on IF i cannot fix paid apps download, which for 2 days has been really annoying. (i even got an account from a supporter with a paid app, so i could test this)
if time is available, i will try and make 0.2a grow with a 100% 360degree fix and hopefully a better BT fix.
Click to expand...
Click to collapse
Thanks for you replay.
I just know the 0.2 editon from Nvdia framework. So I will posted a new thread with that point, for ask all guys again.
Because now they all using 10.b and think it's handy for use. (exclude someone fear of the risk of refresh ROM. XD )
But, our timezone now is 4:31AM, i guess maybe tomo can give you a feedback.
In my opinion it would be best to keep on devolloping the toshiba edition. I also think it would be cool if we could choose between a couple of launcers after te installation.
Also, why make versions with and/or withoud certain app's? (toshiba marktplace) Users can always add or delete these
killerbie said:
Also, why make versions with and/or withoud certain app's? (toshiba marktplace) Users can always add or delete these
Click to expand...
Click to collapse
? (0.2 is stock based, so no toshiba apps work well)
1.0b is toshiba stock firmware based with updates, so all their apps included as found in their release..
somehow, your question is understood..
I'm glad to see that some people share my concerns.
I've tested all the mod that you, Dexter have setup.
My conclusion is that Toshiba have tried to put some multimedia friendly stuffs in front of the scene but they partially failed on the finish line.
As we can experience this release can play movie in high quality but the UI freeze randomly. It's really difficult to setup a complete full media.
On the other side the nvidia release is fast, consumers cherry less and only tried to
prove the velocity of the hardware. I'm sure they are working hard on android since
as we can see tegra2 is coming to the smartphone tablet and other tegra is on the
way.
On the ToshMod(proposition) we can only integrate what toshiba is providing. Are they still working on the tablet after the folio selling fiasco ?
On the DextMod nvidia will provide for sure new release but we need to community and time to setup all goodies required for basic consumers. This release
is favored by developpers.
Since Dexter is working alone (until now) i think it's much more easy to continue on the toshmod to get results and new features. If we can get some more ressources then DexterMod based on nvidia would be more open.
It's just present conclusions, please share yours views
nvidia mod is better, more responsive and faster.
Hey Dexter, take a look to http://tegramid.com/wiki/Main_Page.
It seems they just published the whole gpl kernel source including toshiba frameworks and drivers.
I'm downloading it right now and cannot confirm the content.
roglio said:
It seems they just published the whole gpl kernel source including toshiba frameworks and drivers.
I'm downloading it right now and cannot confirm the content.
Click to expand...
Click to collapse
its good!, im using the kernel source right now to check functionality of all drivers.. but im unable to compile. seems debian is no good for this..
i probably need a VM install with different linux..
Android porting is a mess!!!!! If you follow all directions on android porting, nothing will work as google says! First of all froyo will compile only on a amd64 linux version, then you will discover that the recommended jdk5 is not requested...
grunt :S
I hate Android
I'm using ubuntu 10.10 amd64 (x64 is required for froyo) running into a virtualbox hosted by winxp and works like a charm.
I did also an hack to get raw access the hd without using virtual disk images.
Dexter_nlb said:
I probably need a VM install with different linux..
Click to expand...
Click to collapse
Anyone have an idea how hard it would be to port this tiamat kernel over to Transformer? built for XOOM and others, and the XOOM hardware is near identical right? Just a thought, this thread has the info and link to the github of the sources.
http://forum.xda-developers.com/showthread.php?t=978013
I posted in the thread if he could develop for us and everyone yelled me. I thought it'd be easy too. But I agree. I hope someone could port this because this kernel seems amazing.
Thunderbolt Rooted!
andrew53517 said:
I posted in the thread if he could develop for us and everyone yelled me. I thought it'd be easy too. But I agree. I hope someone could port this because this kernel seems amazing.
Click to expand...
Click to collapse
Yeah, I was going to PM him, but he has PMs disabled, and I wasn't going to post in the thread because people hate that, me included. There is nothing more annoying in a thread when someone else comes in asking to do this all to their device. While this is a situation where at least the device internals are pretty similar, still not a polite thing to do. The github of his work should be enough for any dev here to port the work over pretty easily I'd think. We'll see though.
crater said:
Anyone have an idea how hard it would be to port this tiamat kernel over to Transformer? built for XOOM and others, and the XOOM hardware is near identical right? Just a thought, this thread has the info and link to the github of the sources.
http://forum.xda-developers.com/showthread.php?t=978013
Click to expand...
Click to collapse
The hardware is fairly similar but they are based on two completely different OEM boards. Transformer=Ventana, Xoom=Stingray.
The Tiamat kernel modificationc could possibly be ported to the transformer kernel, but it isn't as straight forward and simple as you might think.
definitely would be sweet.. dual 1.6GHZ sounds pretty good
Hopefully we get some support soon.. I wish I knew how to do this stuff.
I'm not sure what it is but the forum for the Eee pad seem a bit dead tbh, is it just because of limited stock?
bigmo7 said:
I'm not sure what it is but the forum for the Eee pad seem a bit dead tbh, is it just because of limited stock?
Click to expand...
Click to collapse
I sure hope so. I know R2doesinc is ordering one, he is a great developer. So we have another one on board soon. But I think it is a combination between that and that there are so many choices out there. I hope it picks up soon..
I talk to brd all the time. He also hangs out in the asus-transformer irc channel. I spoke to him briefly about of a few weeks ago and he was going to look into it but got busy with tiamat
Sent from my LG-P999 using XDA App
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
egzthunder1 said:
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
Click to expand...
Click to collapse
Yeah, he hangs out in the irc channel too. Most of the devs do
Sent from my LG-P999 using XDA App
Now this all sounds sooo exciting!! I bet once the ball starts rolling there will be no stopping it!
Sent from my TF101
funnycreature said:
Now this all sounds sooo exciting!! I bet once the ball starts rolling there will be no stopping it!
Sent from my TF101
Click to expand...
Click to collapse
I actually think there are a few dev's working on kernel projects
egzthunder1 said:
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
Click to expand...
Click to collapse
Now THIS is refreshing to hear!
Sent from my HTC Eva 4G using Tapatalk
I just got this today.. rooted it.. and now I'm flashing a test OC kernel with modded ramdisk (took that stupid ntfs module out of /sbin/ and the insmod in the init.ventana script).... among other things...
so far so good.. yay.. I'm in!
yes!! that was f***n easy.. 1.2ghz... now for more speed..
Blades said:
I just got this today.. rooted it.. and now I'm flashing a test OC kernel with modded ramdisk (took that stupid ntfs module out of /sbin/ and the insmod in the init.ventana script).... among other things...
so far so good.. yay.. I'm in!
yes!! that was ****in easy.. 1.2ghz... now for more speed..
Click to expand...
Click to collapse
Thanks for sharing the kernel.
psicrest said:
Thanks for sharing the kernel.
Click to expand...
Click to collapse
there is some hardcore douchery going on with sku checks.. I'm chasing variables all over the place.. I give up for the night.. this is like the xoom source, but again fuse data screws us.. I never should've opened this god damn box.. i knew i'd hate it. I haven't used it all.. I prefer my gtab.. argh.. sorry its late.. late late. still want to frisbee it..
Can't wait for the ability to OC
I miss IRC.
And I hope we get some development on this soon. It'd be a shame to see people sticking to products like the xoom, just because the TF is so limited in its availability. We need availability to pick up for this product.
silenceforus said:
I miss IRC.
And I hope we get some development on this soon. It'd be a shame to see people sticking to products like the xoom, just because the TF is so limited in its availability. We need availability to pick up for this product.
Click to expand...
Click to collapse
Its not limited in just availability, its limited in 'mod-ability'.. It could just be the product maker following the guidelines for that particular board and making use of 'security' features specific to that board, but its still a pain in the ass. Work was put in to make the end user work harder to be able to customize.
I have the gtab (harmony), Xoom (stingray) , and eeepad (ventana). The gtab is the fastest, the easiest to mod, the hardest to brick.. and the heaviest with the worst screen. The eeepad is the slowest, the worst to mod and the lightest.. guess what .. best screen.
I am typing this on the gtab tho.. and I just got the eeepad today. It'll probably collect dust. Tried to play south park (originally avi/xvid/mp3) converted/muxed to mp4/xvid/aac and the Asus would play it... but volume control was not working it was full blast or mute. My gtab plays xvid avi/mp3 without a hiccup. Any other format I can throw at it too (sans multichannel audio and high profile h264). Its really surprising how far this has come. Since its oc'd every which way, it makes everything else seem very very slow. Only thing I haven't been able to get oc'd yet is emc.
Getting the ability and the clocks setup for the Asus was a breeze. Configuring/adjusting /making sense of all the bits and pieces of dvfs was not. speedo_id is a new one to me, and that seems to be the value that is read from fuse data and locks down max clocks
You guys got Blades and Netarchy on the case. You don't need me lol. I would LOVE to have Netarchy working on stingray.
Hi guys.
I tend to appreciate more and more the Transformer but there's still a deal-breaker for me concerning the graphic performance.
There's definitely an improvement in 3.1 in landscape mode. However any other rotation divide graphic FPS by 2 approximately.
As a result, web browsing one activity between many others is not much enjoyable.
By using the tablet, it seems kind of obvious that the graphic hardware is underpowered for this display resolution but is it really that or a driver optimization issue.
netarchy told me yesterday that overclocking the GPU didn't help noticeably, which leads me to the conclusion that the limiting factor is the GPU memory bandwidth.
Maybe we can affect its timings, overclock/overvolt the RAM itself? I'm sure LPDDR, optimized for the lowest power consumption has some headroom in this department.
Also, other graphic operation seems slowed down by the CPU, like panning through launcher's panel which becomes smooth with heavy CPU overclocking.
During 2011 I/O I remind romainguy (not 100% sure it was him) told he thought this issue was fixed in 3.1 for XOOM. Is it?
I'm sorry not having answers to all this today, maybe you know more than me and would like to share your thoughts on that?
supercurio said:
...
During 2011 I/O I remind romainguy (not 100% sure it was him) told he thought this issue was fixed in 3.1 for XOOM. Is it?
I'm sorry not having answers to all this today, maybe you know more than me and would like to share your thoughts on that?
Click to expand...
Click to collapse
I'm the one who asked that particular question related to Honeycomb's performance in portrait mode.
More than a time, and also on Android Issue Tracker, Romain guy said that it's a tegra2 issue and that it will be fixed in the next release: "The hardware can't deliver the same kind of performance as in landscape"
When replying my question, he said that "probably" the fix was released in 3.1 or if it wasn't, it will be in the next update.
As i heard, 3.1 didn't solved the issue so we should have to wait for a possible 3.1.x
Since it's tegra related, haven't you had a look at the latest driver available from nVidia? Maybe it's already fixed.
AlessandroIT said:
I'm the one who asked that particular question related to Honeycomb's performance in portrait mode.
More than a time, and also on Android Issue Tracker, Romain guy said that it's a tegra2 issue and that it will be fixed in the next release: "The hardware can't deliver the same kind of performance as in landscape"
When replying my question, he said that "probably" the fix was released in 3.1 or if it wasn't, it will be in the next update.
As i heard, 3.1 didn't solved the issue so we should have to wait for a possible 3.1.x
Since it's tegra related, haven't you had a look at the latest driver available from nVidia? Maybe it's already fixed.
Click to expand...
Click to collapse
Awesome, you definitely did well asking as it's an outstanding issue, thanks!
Also thanks to your detailed answer I think we can safely assume it will be fixed for us too at some point as romainguy is must be confronted to it pretty much everyday when working on his daily work.
Or.. they're already working on newer hardware, which is very probable and will ignore this issue like they ignore some other issues, assuming it's good enough as-is and must focus on future dev/products.
AlessandroIT, I guess now we can search for random commits here and there in NVidia related stuff ^^
supercurio said:
Awesome, you definitely did well asking as it's an outstanding issue, thanks!
Also thanks to your detailed answer I think we can safely assume it will be fixed for us too at some point as romainguy is must be confronted to it pretty much everyday when working on his daily work.
Or.. they're already working on newer hardware, which is very probable and will ignore this issue like they ignore some other issues, assuming it's good enough as-is and must focus on future dev/products.
AlessandroIT, I guess now we can search for random commits here and there in NVidia related stuff ^^
Click to expand...
Click to collapse
That's what i was refering to:
Goto 52:18
(Oh well..besides the FULL GPU written with CAPS, and kind of stupid question, the rest is great ..i was asleep when i wrote it in the morning
And
http://code.google.com/p/android/issues/detail?id=15958
I didn't found anything in tegra's repository related to portrait performance but i think that it won't be writter so clear in the commit.. so you should try to compile a kernel with the latest source available and, hope it works as it should
Wow, I couldn't agree more with what's written by daithi.j in http://code.google.com/p/android/issues/detail?id=15958 ^^
Spot on!
I'll try to catch romainguy on IRC or twitter and ask him.
supercurio said:
Wow, I couldn't agree more with what's written by daithi.j in http://code.google.com/p/android/issues/detail?id=15958 ^^
Spot on!
I'll try to catch romainguy on IRC or twitter and ask him.
Click to expand...
Click to collapse
Thank u for trying to investigate and find a fix for us. This is a serious problem for me aswell.
Yes, it's a very big problem. The first thing that I've noticed about the Transformer was the laggy homescreen, using adw launcher ex it's a little bit better , but nit perfect like my previous Ipad sadly. Good luck Supercurio
A little offtopic: all my Nvidia graphic cards were noticably slower in rotated mode (I had an LCD with pivot).
I also hope that You will release a specific version of voodoo app for our tablet, I loved it on my sgs and the sound quality of the Trasformer now is not as goo as it should be.
When You put it on the market i will certainly buy!
Thanks for your work and support to the community
supercurio said:
Awesome, you definitely did well asking as it's an outstanding issue, thanks!
Also thanks to your detailed answer I think we can safely assume it will be fixed for us too at some point as romainguy is must be confronted to it pretty much everyday when working on his daily work.
Or.. they're already working on newer hardware, which is very probable and will ignore this issue like they ignore some other issues, assuming it's good enough as-is and must focus on future dev/products.
AlessandroIT, I guess now we can search for random commits here and there in NVidia related stuff ^^
Click to expand...
Click to collapse
Does anyone with a fancy Samsung 10.1 know of the potrait frame rate drop is on that device aswell?
cowballz69 said:
Does anyone with a fancy Samsung 10.1 know of the potrait frame rate drop is on that device aswell?
Click to expand...
Click to collapse
From preview/review videos I saw it seems very well its the same.
I'll be able to tell in a week or so!
Are you getting one? Lol
HTC Thunderbolt & ASUS Transformer Rooted!
andrew53517 said:
Are you getting one? Lol
Click to expand...
Click to collapse
Yes Samsung US send me one
supercurio said:
Yes Samsung US send me one
Click to expand...
Click to collapse
Nice! That's so cool!
HTC Thunderbolt & ASUS Transformer Rooted!
Could this be why FBReader tends to lag on page turns? Seems likely.
deadman3000 said:
Could this be why FBReader tends to lag on page turns? Seems likely.
Click to expand...
Click to collapse
I guess so, yes.
Also I can confirm the issue is the exact same on Galaxy Tab 10.1
supercurio said:
I guess so, yes.
Also I can confirm the issue is the exact same on Galaxy Tab 10.1
Click to expand...
Click to collapse
So it's a Honeycomb issue, then? Why does it do that exactly, when it's just the orientation that's different and not resolution or something?
It's a Honeycomb + Tegra 2 issue methinks. Maybe an updated driver will fix it in future. Don't hold your breath though!
6/18/11
Clemsyn-Blades Overclocking kernel for 3.1 Experimental version 10...Here are the changes
1. Enabled NTFS (pls report if it works or not)
2. Increased tegra video memory for better performance (LMK how your experience is)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1109630
lost101 said:
http://forum.xda-developers.com/showthread.php?t=1109630
Click to expand...
Click to collapse
Still the same issue, potrait scrolling def hurts my eyes when scrolling
ICS ANDROID QUESTIONS GO HERE!!!!!
Quite frankly im sick of seeing a new thread or an old thread revised every 4 weeks. Basically from the point of a dev and a fan I am submitting this thread. I want to see every old or dev thread closed and all questions or suggestions pointed here.
I have personally exhausted most of my resources trying to fix the problems we have within our tegra g2x builds. This device is completely closed source rather like to admit it or not. blame it on all you want to.ether
The bottom line is lg and nvidia only releases source for their bottom line **** that makes tegra work, and we have done patched that in and made it work to some extents.
Yes Alot of us devs can make cm9 work and alot of us can make aosp4.0.3+ work. but they will not opensource their work. To the same extent we where stuck at with the vibrant and the gps issue.
All i can say is do not buy another lg device or another tegra device. Yes the transformer is bad ass, but if you protest to a level to where no one wants there work they will be forced as an oem to make there manufactures push their source and make it relevant to the point the oems do.....
Thanks for this, all the other ones seem really useless and never stay on track anyway. . I wonder how long it'll take before some guy trolls the hell out of this one. Lets try to keep this one only pertaining to AOSP ICS or CM9 development and/or progress.
This works...but at some point it will get off track...most of the people that are in the the other threads can't get a working build and since we don't have any builds to test anymore its tough to stay on topic with something you aren't using.
Sent from my LG-P999 using XDA App
Forget ics wheres the new weapon rom is wat im after!
kwes1020 said:
This device is completely closed source rather like to admit it or not.
Click to expand...
Click to collapse
Yea, that's crap, I mean, one of the things I like about Android is the open-sourceness. If only OEM's would realize that an open-source system will, in my opinion at least, get more and better support FROM THE COMMUNITY tahn a totally closed system. Take Windows for example, we all have have things to complain about and most can't do that much, even with third-party programs which can be used to correct problems or bugs or add features. On the other hand, there's a game series I follow where the Dev's explicitly made the games open for easy modification, the only "closed" part is the actual engine itself which was developed from scratch. And what resulted was a fan base who took initiative to correct bugs and add features, sure people didn't like the fact that the games had bugs initially but not only did the community take action but the devs even incorporated community fixes into official patches and credited the person who made the fix. Now the dev company has gone solo and publish their own games and are due to release a fourth in the series with a strong fan base. And here we have people who will refuse to ever touch, Nvidia and/or LG ever again, and not just because of bugs, but the fact that it's closed and we get crap for official releases and fixes and crap for support.
/end rant
Ok let's get on subject, what works and what doesn't work in the ics development for our phone? I don't have a twitter or facebook so I don't keep up with the news.
Sent from my LG-P999 using xda premium
moeahmad1995 said:
Ok let's get on subject, what works and what doesn't work in the ics development for our phone? I don't have a twitter or facebook so I don't keep up with the news.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
I just compiled the aosp 4.0.3 for G2x. I used the google's sources not CM9. However it doesn't boot. I was just wondering how did you guys got it to boot?
Also, the aosp source requires recovery as well to make the otapackage. Is there any way to make the otapackage without recovery? This is not a very big issue as i can manually make the otapackage.
booting up is the big hurdle. Any help is highly appreciated
Thanks
Mr. Apocalypse said:
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
Click to expand...
Click to collapse
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
PhantomRampage said:
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
Click to expand...
Click to collapse
Well CM has had perfectly working ICS build except camera since Thanksgiving. That was like 2+ months ago, maybe they've fixed camera by now who knows.
PhantomRampage said:
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
Click to expand...
Click to collapse
Right, unless CM got camera and data to work. And if all this is going to be open source anyhow, why the secrecy and lack of sharing? As far as I understand no one is making or going to make money off this so, what is it? Is it some petty game of who's the biggest baddest dev?
People can remember CM for being the first to release ICS for the G2x but only because they kept their work secret and didn't share or because they shared their work with others and others with them and they came out on top because they are better or they didn't because they aren't better, etc.
@moeahmad1995
Back on subject? It's a general thread which is all inclusive: "Ok all g2x ics stuff goes here!!"
Волк said:
Right, unless CM got camera and data to work. And if all this is going to be open source anyhow, why the secrecy and lack of sharing? As far as I understand no one is making or going to make money off this so, what is it? Is it some petty game of who's the biggest baddest dev?
Click to expand...
Click to collapse
I'd guess that there are many reasons for CM to keep their source closed for now, not the least of which is reputation. Also competition is one of the things that drives development. Open source is not just about giving hard work away for free.
Here's a great article that helped me to better understand the nature of open source.
Mr. Apocalypse said:
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
Click to expand...
Click to collapse
yeah every build I've made has the same issues as yours which is no working data sound and cam.
Sent from my Galaxy Nexus using xda premium
If there's anything I can do, let me know. I can't help much with development, but I have access to a large audience. For those who don't know, I'm a writer for ACSYNDICATE.NET and will help any way I can. Thanks for sticking with it devs, and thanks for all the new roms!
Sent from my LG-P999 using xda premium
Apparently sound has been fixed over on the O2x.
http://forum.xda-developers.com/showpost.php?p=22231818&postcount=448
Could this mean progress for us?
SefEXE said:
Apparently sound has been fixed over on the O2x.
http://forum.xda-developers.com/showpost.php?p=22231818&postcount=448
Could this mean progress for us?
Click to expand...
Click to collapse
Dammit, I was going to post that
IRASadPanda said:
Dammit, I was going to post that
Click to expand...
Click to collapse
Post it anyways!
It's a joyous occasion!
Well we need to know what they did so we can see if the fix would work on the g2x
Sent from my G2x XDA app cuz I'm stalking your mom....
http://forum.xda-developers.com/showpost.php?p=22200247&postcount=385
"
marsgod
Yesterday, 09:47 AM
# 385
I hope this help fix audio problem...
--------------------------------------------------------------------------------
Here is my fix for SU660 ICS audio...and it work for my ICS AOSP 4.0.3 (SU660 = KR version P990)
I think currently, we must use the libaudio from CM7/Stock rom.......
SO...
1. Modify star-common/BoardConfigCommon.mk
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_AUDIO_LEGACY := true
# Use dirty hack to allow froyo libaudio
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
2. Add audio.primary.p990 audio_policy.p990 into your star-common/star.mk. (This will use hardware/cm/audio. DONT USE audio.primary.tegra audio_policy.tegra!)
3. Use my hardware_legacy.tgz , extract it into star-common/include. The code is mainly from VorkTeam's github, thanks. I only made some fix in it.
4. Copy from CM7/Stock rom : libaudio.so, liba2dp.so, liblvvil.so
Audio should work now...
--------------------------------------------------------------------------------
Attached Files
hardware_legacy.tar.gz - [Click for QR Code] (5.7 KB, 12 views)"
Sweet!!!! Well we should have everything working but the camera? Ill test if anyone need be!!! Would be nice to start seeing some new alpha builds
Sent from my LG-P999 using XDA App
The GITHUB public activity pages are a great way to get a general idea of the work that is going into building the Thunderbolt JB kernel.
Here is a listing of the developers that are working on the Thunderbolt according to their GITHUB public activity pages. I didn't list developers that don't have ICS/JB activity (assuming they have retired from the TB). Click on each link to view their GITHUB public activity.
elginsk8r
Flyhalf205
jblack248
liquid0624
LoungeKatt (TwistedUmbrella)
MongooseHelix
santod
sbryan12144
ziggy471
A GITHUB public activity page does not show all the activity, so keep that in mind.
The developer listing is in alphabetical order based on their GITHUB userID.
A big thanks to all of the DEVs, and please correct me if I missed anyone.
Thanks!
Hey, this is a cool list. It's nice to know people are keeping us honest.
We recently started an organization on github to collaborate easier, so that should be the main place you need to look if you want to stay updated.
https://github.com/LiquidMecha
jblack248 said:
Hey, this is a cool list. It's nice to know people are keeping us honest.
We recently started an organization on github to collaborate easier, so that should be the main place you need to look if you want to stay updated.
https://github.com/LiquidMecha
Click to expand...
Click to collapse
Very Cool! Thanks!
jblack248 said:
Hey, this is a cool list. It's nice to know people are keeping us honest.
We recently started an organization on github to collaborate easier, so that should be the main place you need to look if you want to stay updated.
https://github.com/LiquidMecha
Click to expand...
Click to collapse
Hi jblack, I've been following the liquidmecha development? It looks like you and liquid have been working on the RIL code for jellybean.
Is the RIL code the last major component in the jb development? Or are we talking about major hurdles across the board?
Thanks!
Sent from my ADR6400L using Tapatalk 2
blackshoes said:
Hi jblack, I've been following the liquidmecha development? It looks like you and liquid have been working on the RIL code for jellybean.
Is the RIL code the last major component in the jb development? Or are we talking about major hurdles across the board?
Thanks!
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
You're correct; the radio is the last major component left to get working on JB. Right now we're trying to get baseband to work. I've been pretty busy lately, so Liquid and Santod have been the main guys working on the radio. disconnecktie ha been an incredibly helpful tester thus far, and he also has his own kernel going. Everything else has been reported to work, including the camera and camcorder (not 720p, though). The radio has been especially difficult.
blackshoes said:
Hi jblack, I've been following the liquidmecha development? It looks like you and liquid have been working on the RIL code for jellybean.
Is the RIL code the last major component in the jb development? Or are we talking about major hurdles across the board?
Thanks!
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Whats wrong with the RIL is the ramdisk permissions. The RIL should work, but without the correct ramdisk permissions, the radio itself wont power on, which is the problem we are dealing with now. Think of it this way, you have a pin # to unlock your phone but you have forgotten it, and now you need to try every possible combination you can think of until you land on the right one, and then your phone will unlock. Thats how the problem has to be solved basically.
jacobmacek said:
Whats wrong with the RIL is the ramdisk permissions. The RIL should work, but without the correct ramdisk permissions, the radio itself wont power on, which is the problem we are dealing with now. Think of it this way, you have a pin # to unlock your phone but you have forgotten it, and now you need to try every possible combination you can think of until you land on the right one, and then your phone will unlock. Thats how the problem has to be solved basically.
Click to expand...
Click to collapse
Ouch! That doesn't sound good.
Sent from my ADR6400L using Tapatalk 2
jacobmacek said:
Whats wrong with the RIL is the ramdisk permissions. The RIL should work, but without the correct ramdisk permissions, the radio itself wont power on, which is the problem we are dealing with now. Think of it this way, you have a pin # to unlock your phone but you have forgotten it, and now you need to try every possible combination you can think of until you land on the right one, and then your phone will unlock. Thats how the problem has to be solved basically.
Click to expand...
Click to collapse
Jacobmacek, thanks for the info. How big of an obstacle are we talking about? Could this potentially prevent the DEVs from getting the radio to work with JB?
blackshoes said:
Jacobmacek, thanks for the info. How big of an obstacle are we talking about? Could this potentially prevent the DEVs from getting the radio to work with JB?
Click to expand...
Click to collapse
Meh, depends on how you look at it, it's really just a matter of time
blackshoes said:
Jacobmacek, thanks for the info. How big of an obstacle are we talking about? Could this potentially prevent the DEVs from getting the radio to work with JB?
Click to expand...
Click to collapse
Since you included the word "potentially", yes, potentially it could prevent it
hallstevenson said:
Since you included the word "potentially", yes, potentially it could prevent it
Click to expand...
Click to collapse
"So you're telling me there's a chance"
Don't think to much into it people. Data will work it will just take time and lots of testing. Be patient and it will come.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Don't think to much into it people. Data will work it will just take time and lots of testing. Be patient and it will come.
Click to expand...
Click to collapse
It was a joke... Geez... It's like someone asking "is it possible that 'x' will happen by tomorrow?" and responding, "yes, it's possible" is 100% true.
Sorry if I sounded like a jerk. I wasn't trying to. Lots of time is being put into getting them to work. I will say that it's close. The radios turn on but are turning themselves off during the boot process.
Sent from my ADR6400L using Tapatalk 2
I also wasn't trying to take away anything in regards to the efforts involved in that either. I was simply playing on the hypotheticals that the person included in their question. I couldn't resist answering hypothetically as well !
disconnecktie said:
Lots of time is being put into getting them to work. I will say that it's close. The radios turn on but are turning themselves off during the boot process.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
You know, I really appreciate updates like this. It is so much easier to avoid laying around whining like a kid in the back seat on a road trip when we hear progress reports once in a while.
Sent from my NuSenSex Sense 4 Bolt using Tapatalk 2
I agree, it's nice to see progress is being made.
Once they get the radio working and fully functional JB roms start hitting the Thunderbolt, I hope that XDA's portal page will display the news. I was sorta surprised that the XDA homepage didn't at least give a one-liner when the ICS source was released by HTC. We all waited for so long and there were so many articles about how HTC was delaying the release, and then when the source was released....not one article or blurb.
I'm just hoping that the XDA portal page will give the Thunderbolt a little love when JB is ready. That may spark other news outlets to follow the fact that this older device is still being supported by the DEVs.
blackshoes said:
I agree, it's nice to see progress is being made.
Once they get the radio working and fully functional JB roms start hitting the Thunderbolt, I hope that XDA's portal page will display the news. I was sorta surprised that the XDA homepage didn't at least give a one-liner when the ICS source was released by HTC. We all waited for so long and there were so many articles about how HTC was delaying the release, and then when the source was released....not one article or blurb.
I'm just hoping that the XDA portal page will give the Thunderbolt a little love when JB is ready. That may spark other news outlets to follow the fact that this older device is still being supported by the DEVs.
Click to expand...
Click to collapse
Agreed. It would be awesome to see an article, and also recognition of the hard work of liquid, santod, jblack, and twisted.
I added Flyhalf205 GITHUB activity to the list.
I'm not all that shocked about the lack of Thunderbolt love on the portal. When the Nexus S 4G got ICS, yes.. a developer phone, they didn't say much either. One of the DEV's for that phone managed to get a working version of ICS built for it based off the SDK, which technically shouldn't have worked, but it did. They didn't even show love for that.
No need to worry though, the Thunderbolt community know where our bread is buttered. :laugh: