Hi,
is someone willing and able to port the Honeycomb touchscreen drivers to the current ICS build?
The current ICS drivers are seriously flawed, which can be seen in this video:
http://www.youtube.com/watch?v=LPjTyzsFYvU&feature=youtu.be
People in this are experiencing problems on ICS as well:
http://forum.xda-developers.com/showthread.php?t=1557635
It would be great if someone could fix this
I also experience the same problem. It's such a headache!!!!!
I am not a developer, but from what I know, it wouldn't work. It would require full rewrite, which wouldn't probably work as you want it to work.
Sent from my GT-I9100 using xda app-developers app
Related
is there? not CM7 themed like the rom from evogp, I mean a full ICS rom?
nope, there is only alpha version in here http://forum.xda-developers.com/showthread.php?t=1403372
We have to wait for CM9. And considering that ICS changes a lot of things such as how it interacts with the camera, the old drivers for some of our hardware aren't going to work unless they are able to port some stuff from other, similar phones. I wouldn't hold my breath for a 100% ICS ROM any time soon.
Sent from my Xoom using xda premium
So today I get onto the forums, and see that the fateful day has finally arrived. Jelly Bean. With Galaxy player in hand, I scour the many threads based on this topic. And then I get lost. So am I the only one having trouble with this? And to any devs reading this, maybe you could answer my questions with your magical genie powers?
1. Does the camera work that's been done on ICS transfer over to JB? Or do you have to redo stuff?
2. Can the fix for HW acceleration be ported back to ICS?
3. Does the Bluetooth patch work for JB?
4. Once one ROM is working on JB, is it easy to apply to others? (I love paranoid)
Thanks, blah, blah, blah.
Sent from my YP-G70 on ParanoidAndroid
Read first post here
http://forum.xda-developers.com/showthread.php?t=1868607
Consider it as JB 0.1
arceusg said:
So today I get onto the forums, and see that the fateful day has finally arrived. Jelly Bean. With Galaxy player in hand, I scour the many threads based on this topic. And then I get lost. So am I the only one having trouble with this? And to any devs reading this, maybe you could answer my questions with your magical genie powers?
1. Does the camera work that's been done on ICS transfer over to JB? Or do you have to redo stuff?
2. Can the fix for HW acceleration be ported back to ICS?
3. Does the Bluetooth patch work for JB?
4. Once one ROM is working on JB, is it easy to apply to others? (I love paranoid)
Thanks, blah, blah, blah.
Sent from my YP-G70 on ParanoidAndroid
Click to expand...
Click to collapse
1 probably not
2 possibly, I might have to try it.
3 no
4 easier, yes, but one isn't working yet.
Sent from my Galaxy Nexus using xda app-developers app
Although we technically have jb, there are still many bugs that need to be squashed so I might consider to keep using ics for a while until its optimized!
Is the Camera patch any help at all to get the camera on JB. Cause it would be a shame to waste all the devs hard work if you know what I mean.
I would honestly rather wait for either ICS or JB to be working completely before flashing either of them.
Newer but buggy OS < Older but more stable OS
I don't know. I think I'll stick with ics just cuz of all the stuff it offers. Despite camera and hwa, it really is (in my opinions) better.
Sent from my YP-G70 using xda app-developers app
Can someone port an ICS/JB ROM onto the Galaxy Player 4.2 (YP-GI1)? I really want to update my software, the 4.0/5.0 both have ICS on it and it would be great if my device could have it too, Thanks!
Development is still small. You are going to have to wait because I believe no one hasn't build a custom rom yet.
Sent from my Chip 1.5 ROM + Entropy512's Kernal Samsung Galaxy Player 5.0 U.S.
SerkTheTurk said:
Can someone port an ICS/JB ROM onto the Galaxy Player 4.2 (YP-GI1)? I really want to update my software, the 4.0/5.0 both have ICS on it and it would be great if my device could have it too, Thanks!
Click to expand...
Click to collapse
ICS porting worked chronologically:
The SGP 5.0 was the first to have working ICS ports and it took months before the Bluetooth bug was fixed.
Several months after 5.0 ports stabilized, some developers ported it to the SGP 4.0.
I suspect it worked this way, because there are a larger number of SGP 5.0 owners, hence leading to more output.
And, if my suspicions are correct, then it is going to be a very long while before the SGP 4.2/3.6 see any ports respectively, as I suspect that the number of people who own those devices is smaller yet.
It is feasible, but that would mean that a lot of our devs here who have done successful ports to the 4.0/5.0 would need their own SGP 4.2/3.6 to test their builds and ports on. And, I just don't see them spending money on an already under-supported device.
But, who knows? Crazier things have happened here on the SGP forums.
Is anyone working on this device? I have seen someone on the CyanogenMod Forums say that they have ICS on it but it's very unstable. Of course I can't believe that... But people got a root working using Odin3. If there is any developer that has this device and seeing this post, please.. reply! Thanks
Check this out
did it to my sons 4.2 player,he loves the rom. Check out this thread it has everything you need to upgrade-----http://forum.xda-developers.com/showthread.php?t=1884071--- READ and good luck!!
The thread you sent me just has rooted ROMs. I already rooted my device.
Sent from my YP-GI1 using xda app-developers app
ok so you want to upgrade, this is what i found.the roms are rooted and you flash them using odin.
Yeah but what does it upgrade?
Sent from my YP-GI1 using xda app-developers app
Yeah but what does it upgrade?
Sent from my YP-GI1 using xda app-developers app
Being rooted is a state of existence. You can add it or take it away at your disposal. Being rooted just means that you have the Super User binaries installed on your device. You un-root by uninstalling those binaries. Flashing a ROM with or without root simply means that the ROM you flashed has or doesn't have those binaries.
So, if you flash a rooted ROM over your currently rooted ROM, that's OK. That simply means you have older or newer binaries on your device. (And, yes. You can update Super User binaries.)
there is a rooted gingerbread stock rom, but I believe the dev that made it doesn't even have a 4.2 and had to rely on others to test it, even the 4.0 has a very small number of devs on it, and half the ones we've had in the past have moved on to newer devices. I doubt there will be any ICS/JB goodness for the 4.2 simply because there are no devs that actually own one, atleast as far as users on here go, maybe some guy somewhere might be working on it but they sure aren't here.
Yeah I used that exact ROM anyway to get the rooted gingerbread ROM but thanks anyway
Sent from my YP-GI1 using xda app-developers app
Does anybody know when developers might actually try a ROM for this device?
It would really be nice if somebody could port AOSP to Atrix, similar to this ROM, but 4.0.4. Could somebody please do this?
Any reason you want 4.0.4?
Epinter's CM10 port is already at 4.1.2
Sent from my MB860 using xda app-developers app
I think we should make ICS stable first before proceeding with Jellybean.
Sent from that Atrix.
I would rather have ICS because that's what the semiofficial drivers are for. I'd also rather have AOSP than CM.
nerfman100 said:
It would really be nice if somebody could port AOSP to Atrix, similar to this ROM, but 4.0.4. Could somebody please do this?
Click to expand...
Click to collapse
It would be nice that the leaked kernel was not that faulty as it is. (Batt Drain, stuff), there is a long queue of people waiting for that, then after that queue dissapears, maybe a 4.0.4 AOSP can be done properly.
Hey guys,
Could you explain to me in an accessible way, why the exynos source code is so important for the development of custom roms?
We have a multitude of rooms already, how were they build? If no official sources are available, are custom roms in any way inferior to Samsung stock android (eg lacking hardware video acceleration, heavier battery drain, non-functioning ports/radio, etc. )
Does the code have to be released periodically in a best case scenario by Samsung, ie. with any major android or firmware update, or is it a one-time thing?
And finally, can devs do something with the source code that was recently released by Samsung?
You probably will instantly recognise that I have no programming background, so apologies in advance if this sounds stupid
A simple way to understand is this..
Just how with every new update of windows you need updated drivers to get the graphics card, audio etc working same way we need certain drivers for the chips inside the phone. Since these are designed by Samsung they control the right to not allow others to know the design of these chips. That's why they won't make it open source instead release these drivers so that custom ROM builders can use it.
Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
Sent from my GT-I9100 using xda app-developers app
iamanoopmk said:
Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks- this really helps. So that means we have the official and fully functional drivers in CM9, but only through workarounds can the devs get them to work in, for example, Jelly bean based CM10?
They are doing the exact same thing in CM10 and CM10.1
They have used old ones and some fixes to compensate. That is why CM10 is smooth but not as much as original JB
Sent from my GT-I9100 using xda app-developers app