Related
I'm not sure if this was asked already but, I was wondering If someone could fix the multi touch issues of the mytouch slide. It has the same exact problem as the nexus one/htc desire etc etc.
Problem -- http://www.youtube.com/watch?v=qzhUzq6bTPg&feature=player_embedded
The LG optimus one seems to have a work around for it and i was wondering if someone could bring that workaround to our phone. http://www.youtube.com/watch?v=5Ur9n9pQUAg
Same!!
Did you ever solve this problem. I'm having the same issue because I can't pull down the notification bar and also whenever I switch to another screen the notification bar comes down lol. But other have fixed this problems somehow with a kernel
tylert5 said:
Did you ever solve this problem. I'm having the same issue because I can't pull down the notification bar and also whenever I switch to another screen the notification bar comes down lol. But other have fixed this problems somehow with a kernel
Click to expand...
Click to collapse
I really wish i could solve it haha, and yea crazy stuff like that happens sometimes. Multitouch is definitely also a problem with 3d shooting games. I was actually hoping a dev try to fix this problem. If there is a fix/workaround for other phones, then its definitely possible on this phone.
Nothing you can do. It is the sensor in the phone. It was never meant for multi-touch
UberMario said:
Nothing you can do. It is the sensor in the phone. It was never meant for multi-touch
Click to expand...
Click to collapse
I'm not sure if you've clicked this link that was posted in the OP http://www.youtube.com/watch?v=5Ur9n9pQUAg, but it shows a clearpad2000 device with a mostly fixed multitouch axis. According to the OP in this thread, its done by inverting the inverted axis http://forum.xda-developers.com/showthread.php?t=933686
I was checking out those links. Seems that those fixes are only half working.
It really is a hardware problem. They're just recompiling the kernels to clean it up so that it looks like it works properly, but even in the videos it's evident that there's some messing up. If I'm reading right, our phone probably has the same controller as the G1 and N1. And newer phones don't have the problem because they have better hardware.
Yes I realize this is a hardware problem and that this is not a complete fix, but its better than not having any kind of fix at all.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I had the same problem, was really annoying when playing multitouch games like PewPew because it would sense your fingers opposite of where they were and the axis locked during multitouch which makes fine movements impossible. The newer 4 and 5 point multitouch screens perform way better.
I know it's been touched on here and there (I.E.), but I haven't found a dedicated thread to it, and I know I'm definitely not the only one who is plagued by the annoyance. It seems like some have been able to get around the issue with the international version of the phone, but the North American version appears to be quite the hurdle. Either that, or the devs for all our favorite SMS apps aren't from the good ol' US of A, and don't really care about that feature. Either way, It's annoying to have cutting-edge technology in the palm of my hand without any reliable and simple means to have something other than a solid red LED regardless of the notification it represents. On the thread linked above, I noted that some were able to get a blinking notification, I've had no such luck. Perhaps they weren't rooted. I do recall the day I got my phone, before anything had been modified whatsoever, that the LED would flash blue, but once I got GoSMS Pro installed, it changed my SMS to solid red, and has been such ever since. Nothing at all that I have tried will change it.
TLDR: Has anyone found a way to stay on a custom ROM and/or launcher, AND set different color LED for notifications (as well as blink intervals) within the realm of SMS?
disturbd1 said:
I know it's been touched on here and there (I.E.), but I haven't found a dedicated thread to it, and I know I'm definitely not the only one who is plagued by the annoyance. It seems like some have been able to get around the issue with the international version of the phone, but the North American version appears to be quite the hurdle. Either that, or the devs for all our favorite SMS apps aren't from the good ol' US of A, and don't really care about that feature. Either way, It's annoying to have cutting-edge technology in the palm of my hand without any reliable and simple means to have something other than a solid red LED regardless of the notification it represents. On the thread linked above, I noted that some were able to get a blinking notification, I've had no such luck. Perhaps they weren't rooted. I do recall the day I got my phone, before anything had been modified whatsoever, that the LED would flash blue, but once I got GoSMS Pro installed, it changed my SMS to solid red, and has been such ever since. Nothing at all that I have tried will change it.
TLDR: Has anyone found a way to stay on a custom ROM and/or launcher, AND set different color LED for notifications (as well as blink intervals) within the realm of SMS?
Click to expand...
Click to collapse
Its working great with cm9. You can set it up in the settings
Sent from my SGH-T999
Xcor3 said:
Its working great with cm9. You can set it up in the settings
Sent from my SGH-T999
Click to expand...
Click to collapse
I thought about doing CM9, but last I read it doesn't look to be a finished product? I kept up with the thread on it for a bit after its release, and it seemed there were still bugs.
disturbd1 said:
I thought about doing CM9, but last I read it doesn't look to be a finished product? I kept up with the thread on it for a bit after its release, and it seemed there were still bugs.
Click to expand...
Click to collapse
yes there are bugs. But i barely stumble to them at all. Im using it as my daily driver and its working great for me.
Xcor3 said:
yes there are bugs. But i barely stumble to them at all. Im using it as my daily driver and its working great for me.
Click to expand...
Click to collapse
Awesome, I will flash it tonight, and play around with it.
Still curious if anyone has found a workaround on any TW-based ROMs :good:
Lightflow seems to be actively trying to work on the problem.
Sent from my SGH-T999 using Tapatalk 2
Hello people!
I have not long been using AOKP for very long, but i can say overall i love it, i have a few issues though.
I am aware of course it is a unofficial ROM and to expect it to run perfectly would be ridiculous and i was hoping if anybody had experienced anything similar and had any solutions?...
- My headphone jack has 100% stopped working since installing is ROM, i even reinstalled an old backup of MIUIv4 and it was working fine so it defiantly isn't the hardware.
- Black screen notifications, if i received an IM like whatsapp or even a SMS my led would light up and the screen backlight will turn on but its just a black screen?
- Fail to unlock screen first time around, now this doesn't happen all the time, maybe 30-40% of the time, but ill press the unlock button... the backlight will turn on but again its just a black screen, so i have to re-lock and unlock again and it will 100% work the second time... its kind of annoying.
Other than that the ROM works fine for me, i really don't want to lose the JB OS... is there a stable alternative maybe? or hopefully a simple fix.
By the way is based on their latest build.
Thanks!
Moved to Q&A
Please post in the correct section next time
Sent from my Nocturnalized One XL using Forum Runner
the best for me
http://forum.xda-developers.com/showthread.php?t=1982411
the best ROM for me work perfect!!
xmixmaster said:
http://forum.xda-developers.com/showthread.php?t=1982411
the best ROM for me work perfect!!
Click to expand...
Click to collapse
thanks for that man... im gonna read a little more into but it seems like the best choice... will defiantly check it out!
UPDATE: ive given the ROM a go and i must say its a lot more stable than i thought it would be when its a "mishmash" of different ROMs put together.
i still have the headphone jack issue thought, i read a few other forums that people are experiencing using ROMs based on CM10... have you not had this issue?
I only just recently got my Note II and it has got ARHD on it, which I installed because it's a rom based on samsung software with no comptability issues and great battery life.
I also have a Galaxy Nexus and I noticed a few "problems" the Note 2 has and the older Nexus doesn't:
the browser on the Note 2 looks okay but the pointer precision is just very bad. To give an example: if you swipe your finger up or down vertically for a few centimeters, and then you start sliding diagonally (without having lifted off your finger off the screen in the meanwhile), it will only continue to keep scrolling vertically, it won't "follow" your left or right (or diagonal) movement. When you lift off your finger from the screen, retouch it and then scroll diagonal right away it will follow the movement. I find this very annoying, it prevents me of having a smooth browsing experience. My older Nexus with stock android 4.2.2 and stock browser is smooth as butter and follows my swiping movements 1 to 1..
I tested Dolphin browser, Maxthon.. all still bad pointer precision.. Chrome seems to be the least bad of all the browsers, but then on the other hand I find it very choppy.
PS. I already tried an AOSP/CM rom (Sentinel ROM), and there the browser was smooth, yet, non-touchwiz roms are not bugfree and the battery life is nowhere as good as with a samsung based rom.. And especially that last factor is really important to me. (Unless anyone can advise me a bugfree AOSP rom with batterylife that is as good as a samsung based rom).
SOLVED, SOLUTION IN POST #15
Then something else that annoys me quite a bit: when the screen is off and I press the wakebutton, it takes like 1 to 2 seconds until it actually wakes.. I've read I'm not the only one with this problem but I find it kind of unacceptable for a quad core phone with 2GB of ram.. Same problem when you are in an application and you press the homebutton to go to the homescreen, it sometimes takes like a second or more too.. Once again, stuff like that on my simple dual core nexus with half the amount of ram doesn't happen.
UNDERLINED PART SOLVED, SOLUTION IN POST #3 (thanks Kremata)
Then the good stuff has to be said too: homescreen-scrolling is insanely smooth, watching videos is awesome, the camera is great (so is the samsung camera app) and not to forget, the battery life is a revelation to me, I get through the day easily with hardcore use of the phone (that cannot be said of my old Nexus..).
I really like the Note II, but these few problems really crash the party for me.. Also I never thought I'd say it as a Nexus-fan but I generally find Touchwiz pretty cool and suiting on the Note 2.. So I'd prefer to stay on a samsung based rom like ARHD if possible.
Hope there's some experts here who can give me advise on how to handle these little problems.
For the record, I managed installing the AOSP browser, and the bug is still there. So it must be rom/kernel related, not app-related..
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
For the browser thing I don't know. I never felt it was a problem for me.
Kremata said:
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
Click to expand...
Click to collapse
One problem solved already, thanks for that!
I placed a video of the pointing precision problem on youtube. Btw I checked if the touchscreen is ok by using "show touches", and it followed my touches 100% perfectly, so it's not the phone, it's definitely some software problem..
This is the video
Could anyone with a samsung-based rom try to reproduce the above problem and see if it happens or not ? If not, could you tell me what rom + kernel you are using, would be much appreciated..
I repeat that when I tried an AOSP rom on my Note II, this issue did not happen.
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
whisky_ said:
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
Click to expand...
Click to collapse
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
wtr_dhd said:
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
Click to expand...
Click to collapse
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Kremata said:
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Click to expand...
Click to collapse
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
wtr_dhd said:
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
Click to expand...
Click to collapse
I just realized this problem. I'm using Crash ROM, and sometimes it will happen like in the video, but sometimes it work perfectly.
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
wtr_dhd said:
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
Click to expand...
Click to collapse
You must be more picky than most of us as I never noticed this before either.
Kremata said:
You must be more picky than most of us as I never noticed this before either.
Click to expand...
Click to collapse
You don't forget the good stuff of stock android! But the samsung rom has some pretty cool features too..
HOORAY.
With "Chrome Beta" the swiping "bug" is not present! /me happy
Now my Note 2 is "perfect"
I won't post the link here because I don't have permission to do so, but a couple of the developers from Cyanogenmod have been working on Alpha builds, and a new one (4.4.4) was released last night sometime. The following link is to the dev's G+ page so go ahead and find the link from there, not too hard.
https://plus.google.com/+TomMarshall/posts
Also, APN's are working along with LTE speeds, haven't tested out phone calls yet due to no vibration/sound anywhere in the device, so it's not really "usable" at this point. The newest SlimROM Gapps work just fine by the way.
Hopefully we can keep this thread as a central point for discussion since now there are multiple spread throughout the General and Q&A forums.
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
pside15 said:
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
Click to expand...
Click to collapse
Well, even if there is, that doesn't do any good for the casual user flashing this ROM, they won't hear/feel a phone call/message if the phone is in their pocket. Even if everything besides sound/vibration is working, I still like my phone to act like a phone, you know?
pside15 said:
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
Click to expand...
Click to collapse
I'm on the 09/07 build and I have sound through the earpiece, calls seem to work fine.
Edit: Headset sound works as well.
stevew84 said:
Well, even if there is, that doesn't do any good for the casual user flashing this ROM, they won't hear/feel a phone call/message if the phone is in their pocket. Even if everything besides sound/vibration is working, I still like my phone to act like a phone, you know?
Click to expand...
Click to collapse
Yeah, I understand. Was just wondering if I had read the info correctly before.
kchino said:
I'm on the 09/07 build and I have sound through the earpiece, calls seem to work fine.
Click to expand...
Click to collapse
That's all well and good, but I have to have a phone that notifies me of a call/text while it's sitting on my desk or in my pocket. I fully appreciate the fact this is an Alpha build and I'm not complaining in the least bit, I just can't wait until 5.0 hits the G3...or at least 4.4.4 stable with a good 5.0 theme.
If anyone is wondering this ROM is actually based off Slim as opposed to CM. It has Slims Recents, Quicktiles, Floating Window, Shake Events etc, which are all working.
kchino said:
If anyone is wondering this ROM is actually based off Slim as opposed to CM. It has Slims Recents, Quicktiles, Floating Window, Shake Events etc, which are all working.
Click to expand...
Click to collapse
This is what I don't get, given the fact that this is a PHONE, I would assume that the first thing to get working correctly would be any and everything relating to calls/texts.
Uh...well, everything gets tested and built from the ground up. So some things come along faster than others.
mzrdisi said:
Uh...well, everything gets tested and built from the ground up. So some things come along faster than others.
Click to expand...
Click to collapse
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
The "phone" part of the build does work correctly. The audio not working is a separate matter that has nothing to do with the "phone" part of the rom.
While audible notifications are most certainly a requirement for a daily driver, the reality is that these are alpha builds that are being worked on by a select few people. Everything will get worked out, it's just a matter of time. Been here in this very place several times with phones before the G3, unless you're in the know how, you just gotta play the waiting game
cvsolidx17 said:
The "phone" part of the build does work correctly. The audio not working is a separate matter that has nothing to do with the "phone" part of the rom.
While audible notifications are most certainly a requirement for a daily driver, the reality is that these are alpha builds that are being worked on by a select few people. Everything will get worked out, it's just a matter of time. Been here in this very place several times with phones before the G3, unless you're in the know how, you just gotta play the waiting game
Click to expand...
Click to collapse
Yea i know, been thinking about trying to learn how to go about compiling a CM build from scratch, or port from something similar, but that's a lot of time and effort.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
I'm not sure why you have a gripe at all? It's a very stable alpha build that is actively being worked on and provided to you for free! If you don't like the pace of development why don't you contribute? I understand that you opened this thread to discuss AOSP builds but contrary to your assertion that you are "not complaining" you've posted some inaccuracies about the 1st and only AOSP ROM and told us over and over how you need your phone to be a phone.
We get it. Go back to the LG ROMs until this one suits your needs.
kchino said:
I'm not sure why you have a gripe at all? It's a very stable alpha build that is actively being worked on and provided to you for free! If you don't like the pace of development why don't you contribute? I understand that you opened this thread to discuss AOSP builds but contrary to your assertion that you are "not complaining" you've posted some inaccuracies about the 1st and only AOSP ROM and told us over and over how you need your phone to be a phone.
We get it. Go back to the LG ROMs until this one suits your needs.
Click to expand...
Click to collapse
I'm simply responding to people here, I pointed out what works and what doesn't work with the TWO working Alpha builds. There is a third in the works by AICP but has yet to be released. My only gripe really is for a build to be released, although a test build, without the main functionality of the device working properly...that's it.
I am on an LG ROM at the moment.
The purpose of this thread is to discuss the builds as they come out and to have a central location for all prominent links.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
The thing is a lot of those things aren't phone specific so if they work on other builds they should work here.
For anyone who has tried this, does it get rid of the artificial sharpness?
GoogleAndroid said:
For anyone who has tried this, does it get rid of the artificial sharpness?
Click to expand...
Click to collapse
It looks fine, I mean I don't notice any over sharpening, but then again I don't have my face less than a few inches away from my eyes. Either way, the animation scale is set to .5 so it looks faster than it really is. Set the scales back to 1.0 and everything is really fluid with NO skipping/stuttering/whatever you want to call it.
Lack of vibration and sound across the board is really the only issue at this point. For day to day use, I mean.
Still waiting on the AICP build as that will probably incorporate the missing necessities that the other two builds are lacking.
stevew84 said:
This is what I don't get, given the fact that this is a PHONE, I would assume that the first thing to get working correctly would be any and everything relating to calls/texts.
Click to expand...
Click to collapse
Correct you don't get it. The source code for the ROM is already done, it already has their features. What they are doing is adding the device source and trying to get the drivers working. Its not like they think well lets go add 1% battery, its already in the source code. What they are working on is the device side not the feature side.
stevew84 said:
It looks fine, I mean I don't notice any over sharpening, but then again I don't have my face less than a few inches away from my eyes. Either way, the animation scale is set to .5 so it looks faster than it really is. Set the scales back to 1.0 and everything is really fluid with NO skipping/stuttering/whatever you want to call it.
Lack of vibration and sound across the board is really the only issue at this point. For day to day use, I mean.
Still waiting on the AICP build as that will probably incorporate the missing necessities that the other two builds are lacking.
Click to expand...
Click to collapse
I'm not sure why you continue to mislead based solely on your preference. I'm on the build right now, it is easier to state what doesn't work because this build is very close to beta:
1.2 09/07 build - Not working:
External Speaker (...On the back, Headset audio and earpiece audio are working fine.)
Vibration
Cameras & rear LED
External SD Card
Bluetooth
I haven't come across anything else that isn't working. Wifi, Mobile Data, GPS, incoming/outgoing calls have worked without a hitch. Also this is AOSP so there is zero of the text sharpening that is present in the LG ROMs. I've changed the governor to interactive by default it's set to performance and the cpu does not scale which will contribute to heat reports that initially popped up.
kchino said:
I'm not sure why you continue to mislead based solely on your preference. I'm on the build right now, it is easier to state what doesn't work because this build is very close to beta:
Not working:
External Speaker (...On the back, Headset audio and earpiece audio are working fine.)
Vibration
Cameras & rear LED
External SD Card
I haven't come across anything else that isn't working. Wifi, Mobile Data, GPS, incoming/outgoing calls have worked without a hitch. Also this is AOSP so there is zero of the text sharpening that is present in the LG ROMs. I've changed the governor to interactive by default it's set to performance and the cpu does not scale which will contribute to heat reports that initially popped up.
Click to expand...
Click to collapse
Mount to PC works for you? I mean internal storage.
Sent from my LG-D851 using XDA Free mobile app