Ok, there are these types of roms:
i9000 Roms which have first call broken and hdmi
stock gingerbread leaked roms which have broken video without stock kernel
gingerbread roms from rogers that lack hdmi (is that all?)
froyo roms (everything works)
and aosp right? What is limited on the asop roms and what are some examples of these roms?
and fill anything that I am missing...Im just trying to get an overall grasp on the differen type of roms / limitations.
thanks
oh...and what are roms that are based on jvt?
Don't forget jqt. I've seen that mentioned.
AOSP makes sense to me as being an open source project ROM. I've tried to Google JVT and JQT but so far haven't really seen a good explanation.
JV* (JVQ, JVR, JVT, etc) are i9000 based roms that are essentially using Hellraiser as a framework to port them over to the Infuse. They all suffer from the first call issue.
Any ROM that is not Froyo, or ATT Gingerbread leak based will have issue with HDMI, including i9000 and AOSP based ROMS.
CM7 is AOSP based, and has broken Bluetooth audio bits (headsets pair but no audio/mic, A2DP skips). Since MIUI is ported from the CM7 base, it also will suffer from this. I hesitate to call MIUI AOSP though because the full source is not available.
LinuxBozo said:
JV* (JVQ, JVR, JVT, etc) are i9000 based roms that are essentially using Hellraiser as a framework to port them over to the Infuse. They all suffer from the first call issue.
Any ROM that is not Froyo, or ATT Gingerbread leak based will have issue with HDMI, including i9000 and AOSP based ROMS.
CM7 is AOSP based, and has broken Bluetooth audio bits (headsets pair but no audio/mic, A2DP skips). Since MIUI is ported from the CM7 base, it also will suffer from this. I hesitate to call MIUI AOSP though because the full source is not available.
Click to expand...
Click to collapse
thank you for the explanation.
I dont use bluetooth for anything, and very seldomly use hdmi if at all...so I guess most roms would be ok for me.
I do use video, so flashing modded leaks gave me problems...even when I went to stock kernel, then lost external sd...and I know all of this is fixable, but I dont want to have workarounds on major things like video and external sd.
Related
Just a question for all the developers out there, what would you recommend most for building a stock based rom on, an image built from AOSP or from an OTA update? I am thinking of eventually making some major mods but to start with it is basic stuff, so would it be better to have the full source?
Any benefits/disadvantages for the two types? Other than the lack of gapps in AOSP which is easily fixed.
Just finally an idea for the extent of the changes, think of closer to MIUI in scale of changes compared to CM7 etc. Major ui and system changes, possibly even behaviour of the OS changes.
Thanks for any help! Also if anyone wants to help out with anything, let me know and I will see what can happen.
Sent from my Nexus S
AOSP will be cleaner. You could use CM7 as a base as well which uses AOSP as a base.
zephiK said:
AOSP will be cleaner. You could use CM7 as a base as well which uses AOSP as a base.
Click to expand...
Click to collapse
I'm leaning towards aosp currently actually, that way I have full control over anything if I wanted to modify and change etc.
Just a question with stability, would aosp be less stable than an ota base? I've noticed it sometimes on CM7 although it is expected because of the beta nature and also the extra features.
Sent from my Nexus S
From as far as I can tell, as soon as an ASOP Rom gets ported to the G2x in full, then we will have an explosion in development and roms.
· MIUI
· and others
Discuss, gentlemen.
Faux's AOSP and CM7 are both AOSP ROMs.
I think the devs are waiting for gingerbread source code.
regP said:
Faux's AOSP and CM7 are both AOSP ROMs.
I think the devs are waiting for gingerbread source code.
Click to expand...
Click to collapse
CM7 isn't waiting for it. They have basically fixed all of the G2x's problems, I'd highly recommend the CM7 nightlies now.
I meant all the other g2x devs lol..
No A2DP
No A2DP yet in the nightlies afaik, this is what has been haging me up on CM7. Been on CM ever since I had my OG G1. Things got way better when I got the Nexus One(still the best phone ever imo), and Im hoping the same is to come for the G2X. The A2DP is a deal breaker for me though because I hate wires when Im working out and listening to music. Thought it was something I could deal with but I just got some BT headphones and I wouldn't go back to wired buds for anything now.
Can someone point me towards the best CM7 rom there is? I know they aren't really developed anymore, but I think they work best. I'm currently using SuperSensation, which seems to have a battery issue. (as far as I can tell) I tried downloading the original CM7 rom, but it doesn't seem to be up anywhere anymore!
So what would be the most recommended CM7 rom? Let me know, thanks.
This is probably the best of the bunch as far as I'm concerned:
HyperSensation:
http://forum.xda-developers.com/showthread.php?t=1302969
Alternative download link: (The main link may be offline)
http://www.mediafire.com/?b36vja8imy63wtb
You will not find many CM7 builds, because Sensation was not an officialy supported CyanogenMod Device at the time.
I believe only Alpha builds were released, due to CM9 approaching.
Cheers.
Well thanks, do you suppose it'd work better than the ROM I am using?
http://forum.xda-developers.com/showthread.php?t=1265946
I know that it is only alpha, but it is A LOT more stable than the CM9 Nightlies out there. The audio routing going on with ALL of the roms for CM9 is just where I draw the line.
I've been using CM7 and I love it. Never found an issue.
I'll download this rom and check it out for the sake of curiosity.
Sensation CM7 SelfKang Alphafied Number 10 (11/1) - 2.3.7
You can try this one. Used it before I went to CM9.
http://forum.xda-developers.com/showthread.php?t=1258543
ClipTy said:
Well thanks, do you suppose it'd work better than the ROM I am using?
http://forum.xda-developers.com/showthread.php?t=1265946
I know that it is only alpha, but it is A LOT more stable than the CM9 Nightlies out there. The audio routing going on with ALL of the roms for CM9 is just where I draw the line.
I've been using CM7 and I love it. Never found an issue.
I'll download this rom and check it out for the sake of curiosity.
Click to expand...
Click to collapse
Audio routing has been fixed on the latest Open Sensation
If you're only looking for the CM experience but don't mind the HTC base being used for that but only stripped to achieve that, you can also try HyperNonSense. It doesn't have driver issues as the base is HTC's. I do have to say I haven't use CM in a while so it might be all bugs are eliminated with respect to WiFi, tethering and bluetooth eg.
GPU
Does anyone know why the GPU performance
is considerably worse on gingerbread ROMs
compared to ICS?
Could be because of the drivers, the 213 and 218 difference, see this thread for more information on the drivers. In short, 218 seems to be a lot faster than 213. There were some issues related to the drivers however, eg. Skype and Istagram were troubling. Not sure on the current status on that though.
So do the drivers work with gingerbread too?
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
sandys1 said:
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
ImagioX1 said:
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
Click to expand...
Click to collapse
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
sandys1 said:
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
Click to expand...
Click to collapse
What hardware compatibility do you mean? I don't know whether a bounty is going to work, the devs we have working on these ROMs are already doing their absolute best to bring us the best software possible. Also, some of these issues are caused at an upstream level and are completely out of their control.
Sent from my Evita
I really liked the call recorders available on many TouchWhiz roms on here, for example Wicked Sensations has a call record button built in to the call menu while you're on the phone. Both ends of the line get recorded with no problems.
But I like AOSP roms much more. Like Liquidsmooth, Paranoid Android, Slimrom etc..
I can't find a solution for these roms. What are my options? I checked out a few from the Play Store and they only record my voice; I would need to have speaker on to record the other person. Supposedly it's a hardware issue but if that was the case then TW wouldn't be able to do it..
Any Suggestions Would Be Appreciated!!!
I'm using Liquidsmooth 3.0 d2lte Kitkat at the moment but willing to downgrade for a working solution.
kaslopis said:
I really liked the call recorders available on many TouchWhiz roms on here, for example Wicked Sensations has a call record button built in to the call menu while you're on the phone. Both ends of the line get recorded with no problems.
But I like AOSP roms much more. Like Liquidsmooth, Paranoid Android, Slimrom etc..
I can't find a solution for these roms. What are my options? I checked out a few from the Play Store and they only record my voice; I would need to have speaker on to record the other person. Supposedly it's a hardware issue but if that was the case then TW wouldn't be able to do it..
Any Suggestions Would Be Appreciated!!!
I'm using Liquidsmooth 3.0 d2lte Kitkat at the moment but willing to downgrade for a working solution.
Click to expand...
Click to collapse
My understanding of the situation is that this is one of the features of the S3 that Touchwiz ROMs can use, and AOSP ROMs can't, because Samsung has kept the inner workings of the phone's hardware secret and not published details on them. The drivers that make those functions work are locked away inside the software included in Touchwiz, so only TW ROMs can use them. Another such feature is MHL output via the USB port, AOSP ROMs can't do it on the S3, TW ROMs can. If you want to use the phone's built-in call recording, you have to use a TW-based ROM. That's the only reason I'm still on TW.
Jacquestrapp said:
My understanding of the situation is that this is one of the features of the S3 that Touchwiz ROMs can use, and AOSP ROMs can't, because Samsung has kept the inner workings of the phone's hardware secret and not published details on them. The drivers that make those functions work are locked away inside the software included in Touchwiz, so only TW ROMs can use them. Another such feature is MHL output via the USB port, AOSP ROMs can't do it on the S3, TW ROMs can. If you want to use the phone's built-in call recording, you have to use a TW-based ROM. That's the only reason I'm still on TW.
Click to expand...
Click to collapse
Thank you for the explanation! Makes perfect sense.
If you could recommend a TW rom that would be great.
kaslopis said:
Thank you for the explanation! Makes perfect sense.
If you could recommend a TW rom that would be great.
Click to expand...
Click to collapse
I'm still on BoneStock v3.4: http://forum.xda-developers.com/showthread.php?t=2275376, it's been rock-stable for me since it was released 7 months ago. The AOSP theme gets it close enough to an AOSP look for me. There should be a new version coming out in the near future based on the most recent software for the GS3.