Which JB 4.2.2 ROMs don't have the bluetooth/dialer lag issue?
I believe this is a bug in CM 10.1, from what I've read. I'm just wondering if anyone has been able to fix it...
Sent from my SGH-I777 using xda app-developers app
DarthSudo said:
Which JB 4.2.2 ROMs don't have the bluetooth/dialer lag issue?
Click to expand...
Click to collapse
Tasks latest ROM. Had to use the dialer in call this morning, did not notice much lag, if any. ( but then it was just a one digit press going through the VM menus)
T
Sent from my Nexus 7 using Tapatalk 2
tedkunich said:
Tasks latest ROM. Had to use the dialer in call this morning, did not notice much lag, if any. ( but then it was just a one digit press going through the VM menus)
T
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I can attest to the opposite - it's there and it's obvious. ROMs for the i777 stem from one of two sources, Samsung or CM variants. ATT only released 4.1.2. to the i777 a few days ago, and Samsung to the i9100 before that. CM is on 4.2.2 but as you mentioned, that is where the bug originates. Therefore the CM derivatives, i.e. AOKP, all fall prey to it.
audiophan said:
I can attest to the opposite - it's there and it's obvious. ROMs for the i777 stem from one of two sources, Samsung or CM variants. ATT only released 4.1.2. to the i777 a few days ago, and Samsung to the i9100 before that. CM is on 4.2.2 but as you mentioned, that is where the bug originates. Therefore the CM derivatives, i.e. AOKP, all fall prey to it.
Click to expand...
Click to collapse
That's what I was afraid of... that's the most difficult bug in the 4.2.2 ROMs for me to deal with. I guess I can use a wired headset for conference calls, etc...
I'm sure there are people much smarter than me looking into this, but maybe I'll have to dig in and see what's going on in the code and see if I can contribute anything...
Thanks!
DarthSudo said:
That's what I was afraid of... that's the most difficult bug in the 4.2.2 ROMs for me to deal with. I guess I can use a wired headset for conference calls, etc...
I'm sure there are people much smarter than me looking into this, but maybe I'll have to dig in and see what's going on in the code and see if I can contribute anything...
Thanks!
Click to expand...
Click to collapse
I'm in the same boat as you. With a wired heatset I still experienced call stuttering but I love 4.2.2 for daily use. I've made do by swapping to a trusty Nokia e71 for critical calls - only two a week so I get by. Best of luck!
DarthSudo said:
Which JB 4.2.2 ROMs don't have the bluetooth/dialer lag issue?
Click to expand...
Click to collapse
Task put out the newest AOKP today. If you upgrade, let me know how BT performs.
Related
Does any of the rom's have a mic working?
I've just installed S-voice and want to test it.
Thanks
No. It's a hardware/driver issue across the board.
Sent from my rezound
try use the webos
adder101 said:
Does any of the rom's have a mic working?
I've just installed S-voice and want to test it.
Thanks
Click to expand...
Click to collapse
Some of the CM7 roms had limited success with the mic but CM9 isn't ready yet
And S-voice won't work in webos lol
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
rkaede said:
try use the webos
Click to expand...
Click to collapse
s-voice for ics only, even then it had to be modified as its exclusive for Samsung s3.
If it worked in gb even if it was not that good, surely it could be made to work in ics.
Though the installation of s-voice was without any problems.
x000x said:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
Click to expand...
Click to collapse
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
x000x said:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
Click to expand...
Click to collapse
BIGSimon said:
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
Click to expand...
Click to collapse
Exactly what BIGSimon said. CM9 is still ALPHA. Meaning some things will not work. Not everything that is released is perfect right away. Developing ROMs isn't always an easy task. What they have done in 5 months is pretty damn great.
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
x000x said:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
Click to expand...
Click to collapse
There's a big difference between Android 2.3.7 gingerbread and Android 4.0.4 ice cream sandwich which meant everything had to be re-written to work Android 5 jelly bean is more of an evolution of ICS so drivers will carry over, all the work that's been done now will mean that when JB is released the touchpad will get it a lot faster with everything working
Sent from my HTC Wildfire using Tapatalk 2
x000x said:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
Click to expand...
Click to collapse
JellyBean will be a minor update, it will have a version 4.1, it isn't as huge step as going from 2.3 to 4.0.
Anyway, sound is surely being worked on (developers (partially, maybe) have gotten rid of bad screen-off sound issue last week), and we will see some progress in a time. If you want a tablet with all features working out-of-the-box, i guess, you should buy another device.
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
+ 1 ;-)
BuffMcBigHuge said:
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
Click to expand...
Click to collapse
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
jsgraphicart said:
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
Click to expand...
Click to collapse
I was able to get it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=1667046
Works wonderfully with the new audiolib!
Is there a flashable audiolib somewhere?
--update--
Found it
http://goo.im/devs/jcsullins/cmtouchpad/testing
Sent from my SGH-T989 using Tapatalk 2
Izeltokatl said:
Is there a flashable audiolib somewhere?
--update--
Found it
http://goo.im/devs/jcsullins/cmtouchpad/testing
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Nighlyy 0620 has everything mic needs already included.
There are so many varied and out of date opinions on this and then so many people that are just guessing, so I have to ask.
Are either 4.1.2 or 4.2.1 completely stable? I'm getting that NONE of the 4.2s are stable at all and that they're experimental at best. Is this true? If so, is 4.1.2 the only stable ROM right now? I don't get a kick out of the phone FCing on me when I try to edit a photo or something.
Thanks for any clarification.
tinpanalley said:
I'm getting that NONE of the 4.2s are stable at all and that they're experimental at best. Is this true? If so, is 4.1.2 the only stable ROM right now?
Click to expand...
Click to collapse
are you talking about Samsung ROMs? then yes
I'm talking about Samsungs OR AOSP. Either one.
Sent from my GT-I9300 using xda app-developers app
tinpanalley said:
I'm talking about Samsungs OR AOSP. Either one.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Samsung - stable
AOSP - not 100% because lack of sources, but OK for a daily driver.
Sent from my washing machine using xda premium
AOSP ROMs will never be as stable as Sammy-based ones
Ok, I think my question got a bit misconstrued. I get that a Samsung ROM is always more stable since it's the base of this phone's OS.
But therefore...
- 4.1.2 and 4.2.1 BOTH stable on Samsung.
- neither stable on AOSP because of lack of sources
Is that correct, then?
And by stable, I mean that I just want a camera that works with all features, can save to the SD card, no weird crashes from using basic phone menus and functions (volume, notifications menu, etc)
tinpanalley said:
Ok, I think my question got a bit misconstrued. I get that a Samsung ROM is always more stable since it's the base of this phone's OS.
But therefore...
- 4.1.2 and 4.2.1 BOTH stable on Samsung.
- neither stable on AOSP because of lack of sources
Is that correct, then?
And by stable, I mean that I just want a camera that works with all features, can save to the SD card, no weird crashes from using basic phone menus and functions (volume, notifications menu, etc)
Click to expand...
Click to collapse
Camera is working but the picture quality is a bit worse than on the stock camera. Pictures can be saved on SD card
Sent from my washing machine using xda premium
tinpanalley said:
Ok, I think my question got a bit misconstrued. I get that a Samsung ROM is always more stable since it's the base of this phone's OS.
But therefore...
- 4.1.2 and 4.2.1 BOTH stable on Samsung.
- neither stable on AOSP because of lack of sources
Is that correct, then?
Click to expand...
Click to collapse
no, samsung 4.2 is not stable, like I said.
by your definition of stable, AOSP 4.2 is stable
Ok, I see. In which ways do AOSP 4.2 ROMs fall short then? I know they obviously don't have Samsung apps like S-beam, smart TV functionality, NFC, etc. But is there something that's always 'broken' on AOSP ROMs?
Sent from my GT-I9300 using xda app-developers app
Some don't like MMS. Some dont like camera.
I use camera fine though, Not bothered about SMS
Ok cool, like I said I just don't want something stupid like you can't play a game and then send an email because the whole phone crashes. :silly: Or a ROM with TERRIBLE battery drain.
tinpanalley said:
Ok cool, like I said I just don't want something stupid like you can't play a game and then send an email because the whole phone crashes. :silly: Or a ROM with TERRIBLE battery drain.
Click to expand...
Click to collapse
then AOSP have been stable for a loong time
rootSU said:
Some don't like MMS. Some dont like camera.
Click to expand...
Click to collapse
Well, then that's not my idea of stable. I guess I'll stick to Samsung ROMs.
Jelly Bean stable?
I recently bought a galaxy s3 and had flashed the 4.2.2 jellybean update. it worked great, no crashes and ran smooth. On monday it notified me that there were two stable updates. I updated both one at a time with TWRP and flashed. It seemed ok all night. In the morning when i plugged in my USB flash drive with my OTG cable the screen just went black. Now it doesnt do anything. It wont even go in to download mode. So i guess i the 4.2.2 was ok but the updates werent.
tinpanalley said:
Well, then that's not my idea of stable.
Click to expand...
Click to collapse
That's because you don't know what stable means.
Stable means... Does not reboot constantly. Does not freeze constantly. It runs stable.
You are talking about broken features. Camera is easily fixable. MMS, well if you want MMS, go back to Smasung ROMs.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
janicans said:
I recently bought a galaxy s3 and had flashed the 4.2.2 jellybean update. it worked great, no crashes and ran smooth. On monday it notified me that there were two stable updates. .
Click to expand...
Click to collapse
There is no official 4.2.2 for the S3.
rootSU said:
That's because you don't know what stable means.
Stable means... Does not reboot constantly. Does not freeze constantly. It runs stable.
You are talking about broken features. Camera is easily fixable. MMS, well if you want MMS, go back to Smasung ROMs.
Click to expand...
Click to collapse
Ok, well that's true, that's why I'm asking these questions.
So do 4.2.1, 4.2.2 AOSP have the same level of stability?
Is 4.1.2 considered something that's MUCH more stable at this point?
tinpanalley said:
Ok, well that's true, that's why I'm asking these questions.
So do 4.2.1, 4.2.2 AOSP have the same level of stability?
Is 4.1.2 considered something that's MUCH more stable at this point?
Click to expand...
Click to collapse
Its hard for me to Quantify.
I only used Smasung 4.0.4, 4.1.1, 4.1.2, 4.2.1 Then AOSP 4.2.2
I dont use MMS so the fact it doesn't work properly is no big deal for me. It force closes when I try to attach a picture. I am not sure about receiving MMS (As I say I dont use it).
For me, AOSP - everything works great. More stable to me than Samsung ROMs (less bugs) except MMS which i do not use. Actually I find AOSP faster too.
I do not use the stock AOSP camera. I never had problems with it but some users did. But i replace mine with the camera that has more functions...
http://forum.xda-developers.com/showthread.php?t=1746611
What I would say is, If you think you can live without MMS, give it a try. Dont mess with overclock / undervolt and see for yourself how fast and stable it is.
If you really need MMS, Maybe it is not worth the test. I am not sure how apps like Go SMS handle it.
In conclusion, I find AOSP faster and more stable than sammy. But I dont use MMS.
I hope this helps somewhat
Yeah, it does help. I can find another solution for MMS (GoSMS Pro, etc) but I don't want basic things being broken. Like I just found out there's no mute on this ROM for audio. Somebody mentioned something about not being able to silence their ringer. That's something I can't be flexible about. I guess I'll look for an AOSP other than temasek.
I like paranoid android myself. Definitely silences
Sent from my GT-I9300 using Tapatalk 2
Any thoughts from anyone on MIUI?
So wife has a note i717. Prevents me from flashing 800 ROMs a week to try different options. Took me a year to convince her to root.. Would like to know what date cm changed code and got the echo. Was it at the 4.2.2 release? Read somewhere that it happens in April. Does black star suffer the same issue? Does black star offer lockscreen shortcuts if it doesn't? What about cm9.
mavpts said:
So wife has a note i717. Prevents me from flashing 800 ROMs a week to try different options. Took me a year to convince her to root.. Would like to know what date cm changed code and got the echo. Was it at the 4.2.2 release? Read somewhere that it happens in April. Does black star suffer the same issue? Does black star offer lockscreen shortcuts if it doesn't? What about cm9.
Click to expand...
Click to collapse
I am not a developer, but I think codes can change quite regularly. I don't think the echo is due to the code, I think it is limited to a ROM or 2 and last I check, the OP stated the in the list of problems. not sure of solution, I think most suffered from it with speakerphone on.
4.1.2 was a release........4.2 is pretty much a tweak of a release merging several different sources together. the ROM's which have the echo issue are 4.2 ROM's and use a CM Kernal. that may be where the issue is. the 4.2 ROM's are AOSP. many have had fixes to various problems by flashing an alternate Kernal.
go to the thread for what ROM you are running, you didn't say, but I can guess. any alternate Kernal may be ROM specific, so consult your thread. reading your post is leading me to think your not reading yourself.
THE 4.1.2 ROMS are Touchwiz and do not suffer echo
good luck
Blackstar jelly beta doesn't seem to have any bugs been running a few weeks no issues what so ever if you want a reliable phone stick with 4.1 I seem to not be able to find 4.2 quite there yet
Goodluck
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
That's to bad. It seems that the only problem with cm10.1.2 was the hw overlay thing and the speaker echo. I love that Rom on my HTC rezound. Seems some of the devs leave out known bugs.
Thanks for all the help.
Sent from my ADR6425LVW using Tapatalk 2
All CM and AOSP based ROMS have had this problem for a while. This is another big reason why I switched back a TW based rom...everything works. I use speaker phone often and the distant end parties would complain that the speaker audio was unusable....
Really sux!
So forgive the ignorance but is it that only one mic is working and not noise cancelling the echo like it should? They found a solution for that on my phone. Just not sure if the fault is the same.
Sent from my ADR6425LVW using Tapatalk 2
Still no solution I guess?
rickneworleansla said:
Still no solution I guess?
Click to expand...
Click to collapse
Not that I've heard. About to give cm9 a try though.
Sent from my ADR6425LVW using Tapatalk 4
It's been a year and this still hasn't been solved??
Sloogle_Flugelmann said:
It's been a year and this still hasn't been solved??
Click to expand...
Click to collapse
As far as I know it hasn't. I've been looking everywhere for a solution. I'm going back to ICS until I can get a new phone.
rickneworleansla said:
As far as I know it hasn't. I've been looking everywhere for a solution. I'm going back to ICS until I can get a new phone.
Click to expand...
Click to collapse
I found a 4.2.2 ROM that does not have the echo. It's the ParanoidKANGdroid ROM: http://forum.xda-developers.com/showthread.php?t=2216645
Download the Previous Release from April 13th. That was the older CM kernel before the echo.
The only real problems I found were that the Apollo and Camera/Gallery apps sometimes crash.
I just took the Gallery2.apk from CM 10.1.3 and it fixed it. I'm about to try to take the Apollo.apk from it as well.
Okay, I have been on Jelly Beans ROMs since practically build 1, it seems. I have never tried out another ROM on this device. Something here lately has really gotten my attention though, and that is the "Halo" usage from ParanoidAndroid ROMs. I spent almost an hour last night reading through the bazillion pages on the Original Android Development tab for this ROM (PA). There were so many mixed reviews about what works and what doesn't on the latest release that I am not sure what to think.
My question is, ultimately, is there a build of ParanoidAndroid for VZW Note 2 that is "mostly" bug free (GPS, graphical issues, etc)? I even looked at JellyBam, but there is even less of a clear message with that ROM. I need something for a daily driver and really don't want to have to do work arounds for the things I typically do on my device (Phone Calls to Netflix and all between).
Anyone have any ideas? Like I said, the only build of Paranoid I could find was the newly released one that looks to be built off Android 4.3 (Cyanogenmod, I assume). If that is the case, from what I have read, there are a few things that aren't tied up completely on it. Older build of Paranoid maybe? (Where do I find that?)
Thanks for the help guys.
Kenobi
You can try the 4.2.2 version of paranoid android if you want to be conservative. I think it was 3.68 or something
Sent from my SCH-I605 using Tapatalk 4
kenobi112 said:
Okay, I have been on Jelly Beans ROMs since practically build 1, it seems. I have never tried out another ROM on this device. Something here lately has really gotten my attention though, and that is the "Halo" usage from ParanoidAndroid ROMs. I spent almost an hour last night reading through the bazillion pages on the Original Android Development tab for this ROM (PA). There were so many mixed reviews about what works and what doesn't on the latest release that I am not sure what to think.
My question is, ultimately, is there a build of ParanoidAndroid for VZW Note 2 that is "mostly" bug free (GPS, graphical issues, etc)? I even looked at JellyBam, but there is even less of a clear message with that ROM. I need something for a daily driver and really don't want to have to do work arounds for the things I typically do on my device (Phone Calls to Netflix and all between).
Anyone have any ideas? Like I said, the only build of Paranoid I could find was the newly released one that looks to be built off Android 4.3 (Cyanogenmod, I assume). If that is the case, from what I have read, there are a few things that aren't tied up completely on it. Older build of Paranoid maybe? (Where do I find that?)
Thanks for the help guys.
Kenobi
Click to expand...
Click to collapse
I'm running build 3.99, have been for a month now. Out of 10 I give it a..... 10. There's really no bugs at all, I hardly get graphical issues but they do exist. I got a GPS lock and you can by getting a lock in a tw ROM in maps, then immediately flashing as you would a normal rom. But honestly this is my favorite ROM I've had on all my android phones so fast and stable and great battery life. Hope this helps.
Sent from my SCH-I605 using xda app-developers app
wtoj34 said:
I'm running build 3.99, have been for a month now. Out of 10 I give it a..... 10. There's really no bugs at all, I hardly get graphical issues but they do exist. I got a GPS lock and you can by getting a lock in a tw ROM in maps, then immediately flashing as you would a normal rom. But honestly this is my favorite ROM I've had on all my android phones so fast and stable and great battery life. Hope this helps.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I think I am going to go with to go with a 4.2.2 ROM just for overall stability.
In regards to gapps, is the general rule of thumb just to use the most recent?
kenobi112 said:
I think I am going to go with to go with a 4.2.2 ROM just for overall stability.
In regards to gapps, is the general rule of thumb just to use the most recent?
Click to expand...
Click to collapse
Yeah basically. Just make sure you download the one for 4.2.2 not a 4.3 gapps
Okay, got version 3.68 installed and proper gapps. Haven't had time to really dive in to get everything set up. Everything is running smooth and quick. The only issue I have at the moment is that I can't get a 4g connection.
Any ideas?
Thanks for all the help thus far.
Kenobi
HEY GUYS!!
So im super new to XDA forums, but i came here to get some help. So ive never flashed a custom ROM before but ive read on it extensively and have an idea of the terms and what-not. i recently flashed my s2 i9100 to the latest cyanogenmod rom using their app and desktop aid. i really loved the new look and feel on my s2 and i was positive Sammy wouldn't be rolling out any future updates on this hardware.
After the honeymoon period was over i came to notice the grating little issues that made me switch back to official jellybean TW. The cyanogenmod firmware they flash with the app is 10.2, so its jelly bean 4.3. It was a "stable" firmware, so they say. Heres a list of the problems.
1. YouTube became very very pixelated and i did some searches and couldnt find a fix.
2. Games like Temple Run 2 performed much worse than with the stock OS, lots of frame skipping could be seen, which makes a game like TR2 unplayable.
3. There were alot of crashes on the stock cyanogenmod launcher, especially after installing apps.
I really appreciate the work cyanogen does but i posted these issues on their forums and i feel like im an isolated incident being that noone has posted on it.
SO IF THERE IS ANYONE OUT THERE WITH THE SAME ISSUES AS ME OR WITH ADVICE, PLEASE HELP ME OUT, IT WOULD BE REALLY APPRECIATED.
CM for i9100 are only nightlies.
Nightly means that the firmware is every (not anymore) day/night getting updated, why? Because of bugs. Nightlys are oftne minor bug improvments compared to the one before.
There are no stable CM roms, except CM 9 so i've heard, just Nightlies.
Hope this clears it up.
PS. Maybe you can try other roms that have CM base..
I am using cyanogenmod 10.2 nightlies right now in my I9100G, and i don't have any problems, wouldn't go back to stock. Games work much better for me because this ROM is lightweight and uses ram better, i never used the desktop aid so i can't comment on that but maybe you should flash from recovery, there might be bugs with that aid, and which cyanogenmod are you using? If you are trying to use kitkat, there will be lots of bugs its only natural because it's been 2 weeks since kitkat went out, try 4.3.
TheGovernment said:
CM for i9100 are only nightlies.
Nightly means that the firmware is every (not anymore) day/night getting updated, why? Because of bugs. Nightlys are oftne minor bug improvments compared to the one before.
There are no stable CM roms, except CM 9 so i've heard, just Nightlies.
Hope this clears it up.
PS. Maybe you can try other roms that have CM base..
Click to expand...
Click to collapse
Oh thanks for the repl. I didnt know that the firmwares were nightlies when using the official app. i thought the app description was that it flashes the latest stable cyanogen build. Just a question, being that ive flashed it twice to try and mitigate the issues to no avail, (ive wiped dalvik and cache and formatted) whats my next step? i really liked it but those issues are pretty disappointing/
Dakura said:
I am using cyanogenmod 10.2 nightlies right now in my I9100G, and i don't have any problems, wouldn't go back to stock. Games work much better for me because this ROM is lightweight and uses ram better, i never used the desktop aid so i can't comment on that but maybe you should flash from recovery, there might be bugs with that aid, and which cyanogenmod are you using? If you are trying to use kitkat, there will be lots of bugs its only natural because it's been 2 weeks since kitkat went out, try 4.3.
Click to expand...
Click to collapse
I would try it the "old" way but im a little afraid. do you think that the fact that you are using the G variant would make a difference?
the only way to make youtube better was to loas previous version. and the games didnt necessarily have a constant lag, it seems more like a frame sync or clipping issue than a frame chugging/ lagging issue. The cyanogen build i was using was 10.2. so it was 4.3.1. thanks for your reply.
cquallo89 said:
I would try it the "old" way but im a little afraid. do you think that the fact that you are using the G variant would make a difference?
the only way to make youtube better was to loas previous version. and the games didnt necessarily have a constant lag, it seems more like a frame sync or clipping issue than a frame chugging/ lagging issue. The cyanogen build i was using was 10.2. so it was 4.3.1. thanks for your reply.
Click to expand...
Click to collapse
Sorry, can't help you further, since i'm still on a stock sammy based rom
cquallo89 said:
I would try it the "old" way but im a little afraid. do you think that the fact that you are using the G variant would make a difference?
the only way to make youtube better was to loas previous version. and the games didnt necessarily have a constant lag, it seems more like a frame sync or clipping issue than a frame chugging/ lagging issue. The cyanogen build i was using was 10.2. so it was 4.3.1. thanks for your reply.
Click to expand...
Click to collapse
Might be a unique problem for you. You can try this: http://forum.xda-developers.com/showthread.php?t=2532929
If it doesn't work, don't use cm and try other roms, as i said there might be a unique problem with your device.
I'm not going to make any recommendations because that's against XDA rules, but it stands to reason that the 10.2 builds won't be as 'polished' as the 10.1 builds purely because they haven't been under development for as long. If you don't like the bugs in 10.2, try something 'older'..........
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
keithross39 said:
I'm not going to make any recommendations because that's against XDA rules, but it stands to reason that the 10.2 builds won't be as 'polished' as the 10.1 builds purely because they haven't been under development for as long. If you don't like the bugs in 10.2, try something 'older'..........
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
Click to expand...
Click to collapse
Thanks for your replies guys,
im wondering if i should just wait for an official kitkat build.
but either way ill try your suggestions. looking forward to positive results.
just a heads up though i found another poster on a cyanogen forum that describes the same youtube problem. so maybe its not just me after all
There will be issues with the 10.2 builds for some time to come.....no disrespect to the developers, they've done /are doing a fantastic job to help keep the S2 alive. All custom ROMs go through this process and as they progress, the bugs become less and less.........
And as far as official KitKat.......not going to happen.....Samsung ended official support for the S2 with Jellybean....
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
keithross39 said:
There will be issues with the 10.2 builds for some time to come.....no disrespect to the developers, they've done /are doing a fantastic job to help keep the S2 alive. All custom ROMs go through this process and as they progress, the bugs become less and less.........
And as far as official KitKat.......not going to happen.....Samsung ended official support for the S2 with Jellybean....
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
Click to expand...
Click to collapse
Well overall the ROM is fantastic. I love the look and feel and added functionality. What I meant about waiting for official kitkat is an offcial rom from cyanogen based on kitkat. Im sure that support for s2 will continue so long as the hardware is capable.