I got my A510 a couple of days ago and I'm experiencing screen responsiveness issues at certain scenarios...
The tablet will not respond to touch when laid on a table or in bed. But once you hold the back with your hand (Or even with just a finger), the sensitivity goes back to normal.
I'm confirming that toggling the sensitivity does indeed fix it (as I saw in another forum). However, you will need to toggle it again after a restart (Or sometimes while in use, it happened to me once when I enable/disabled by BT). I have a generic screen protector installed.
My question is... Is anyone else experiencing this? Or does anyone have a permanent fix?
Common issue, no permanent fix per say, if you searched you would most likely find that you can go to settings, switch your sensitivity o either high or low, switch it back to the original and that will reset your screens touch settings, which will last until you rat your tablet. Hope that helps
Sent from my A700 using XDA
Screwedupsmitty said:
Common issue, no permanent fix per say, if you searched you would most likely find that you can go to settings, switch your sensitivity o either high or low, switch it back to the original and that will reset your screens touch settings, which will last until you rat your tablet. Hope that helps
Sent from my A700 using XDA
Click to expand...
Click to collapse
Yeah, I did search. I just thought that there's maybe a fix that I missed. Thanks bud!
Screwedupsmitty said:
Common issue, no permanent fix per say, if you searched you would most likely find that you can go to settings, switch your sensitivity o either high or low, switch it back to the original and that will reset your screens touch settings, which will last until you rat your tablet. Hope that helps
Sent from my A700 using XDA
Click to expand...
Click to collapse
Reboot you mean? Ratting out a tablet, that could make you an unpopular person in tablet jail
would this be fix if CM9 is ported ?
do you think it's linked to some Acer bloat or badly implemented ICS ?
BENETNATH said:
would this be fix if CM9 is ported ?
do you think it's linked to some Acer bloat or badly implemented ICS ?
Click to expand...
Click to collapse
It's definitely a software issue.
So yes, I think an update from Acer, or any ROM would fix it. CM9 should also be able to fix it, if and when it will be released.
as we have got the kernel sources,
is CM9 possible to be build ?
noob question but i don't know what is required to build CM9..
BENETNATH said:
as we have got the kernel sources,
is CM9 possible to be build ?
noob question but i don't know what is required to build CM9..
Click to expand...
Click to collapse
We need a dev.
I didn't come from a previous Iconia. So maybe someone with experience building for the A500 can help us out. (Assuming he also gets the A510.)
P.S. I didn't know that we already have kernel sources for the A510. That's good news then.
yep :
there :
http://us.acer.com/ac/en/US/content/drivers
into 'Document' sheet
don't know if it's complete but at least it's mentioned "kernel source code (for Android 4.0.3 Ice Cream Sandwich)"
In addition, there are already some git :
https://github.com/Dees-Troy/android_device_acer_picasso_m
Same bug here.
Waiting for a "definitive" fix.
CWN recovery + nothrill rom might be an option to consider
Should you decide to try it, use the Optimized A510 rom. I had that issue before, and the Franken700 rom has that same issue.
I believe it should be gone with the 1.099 stock rom (which is the optimized A510 rom by NoThrills.
Removing my screen protector + installing the latest nothrill ROM fixed it for me.
remove your screen protector if you have one.
remove screen protector
http://forum.xda-developers.com/showthread.php?t=1887688 as posted in this thread, i would suggest to remove the screen protector too, if you have one. Fixes the responsivness bug for me. Stock A700.
Yeah, I used my tab for a week without the screen protector (regardless of what ROM I use), and it did remove my screen responsiveness bug.
However, I'd rather live with that bug than to have a scratched screen in a few months.
salisbury_steak said:
Yeah, I used my tab for a week without the screen protector (regardless of what ROM I use), and it did remove my screen responsiveness bug.
However, I'd rather live with that bug than to have a scratched screen in a few months.
Click to expand...
Click to collapse
Last update .
On the bring of returning it for a Prime, I tried installing NoThrill's yesterday's release of a ROM. The usual prodecure, data/factory wipe, then install from SD card NoThrill's today release.
Upon booting, the response seemed slightly better; I went into the settings, and the responsiveness had defaulted to low.
I set it to high, rebooted and had no more problems.
Whether it's grounded, or not it works perfect.
I pushed my luck and also installed my screen protector again. It once more works perfect. Super sensitivity.
I strongly suggest installing yesterday's Nothrill ROM. I had the 5th of september one, and there was no fix. The 19th did it.
Many thanks to Nothrills. Saved me from spending 150 more pounds needlesly
+1 on the Sept18 build. (I posted it in NoThrill's optimized rom thread yesterday.)
For all we know, it might have been the kernel that fixed it.
Related
I am trying to get a rom that doesn't do this, has this issue been resolved? I can lay my device down at random times and I will come back to the device at the Asus screen locked up. Thanks in advanced tried the search filter maybe my keywords weren't correct. Thanks to all.
Found? lol no no one has 'found' one..lmao
We don't 'find' ROMs here, we develop them (or rather THEY do, I don't yet).
The reboot issue seems to be related to the kernel, and all the ROMs use the Asus kernel (with the exception being blades' new kernel, but it still suffers reboots). So there isn't a solution yet. A few workarounds, preventative measures or wive's tales that 'remedy' or make them 'less frequent', but no solutions.
buffalosolja42 said:
I am trying to get a rom that doesn't do this, has this issue been resolved? I can lay my device down at random times and I will come back to the device at the Asus screen locked up. Thanks in advanced tried the search filter maybe my keywords weren't correct. Thanks to all.
Click to expand...
Click to collapse
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
geenius said:
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
Click to expand...
Click to collapse
Same here, no instances of any of the reported problems and I even bought my TF101 as a refurb.
b1lk1 said:
Same here, no instances of any of the reported problems and I even bought my TF101 as a refurb.
Click to expand...
Click to collapse
Wonder what applications are running in your TF. The same thing here with my TF. No reboots, no SODs...
However, after posting in several threads about my luck..
here they come... reboot.... reboot... reboot... simply by opening market...
The only thing I like?... no battery drain!
Just accept it until xda devs will figure out the best solution!
Cheers!
Hi
I flashed the Android Revolution 3.1.0 on Friday and have had 1 freeze up and 2 times file manager didnt run after I installed mxvideo player. But otherwise all good.
Sent from my Transformer TF101 using XDA
luna_c666 said:
The reboot issue seems to be related to the kernel, and all the ROMs use the Asus kernel (with the exception being blades' new kernel, but it still suffers reboots). So there isn't a solution yet. A few workarounds, preventative measures or wive's tales that 'remedy' or make them 'less frequent', but no solutions.
Click to expand...
Click to collapse
This is the situation, there is not definitive solution yet, people gets different results with same or different ROMs, its purely luck if you don't have Reboots or freezes, the solution should be something kernel related, most probably tegra2 drivers (as it has been tweeted by gnufabio few weeks ago)
geenius said:
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
Click to expand...
Click to collapse
This is just an example of users happy with their ROM without issues, but it is just luck.
AOKP and CM9 with cornerstone never rebooted on me. With the Blades kernel I had a few reboots but nothing serious.
Then again I don't have any nvidia tegra gaming stuff installed.
Sent from my Transformer TF101 using Tapatalk
I run a pretty full range of apps. I use the GPS a fair bit, lots of web surfing with flash as well as email. I do lot of games including a handful of Tegra 2 games. Only issues I have right now is Angry Birds Space freezing, but that is common accross all platforms as well. DOes not cause reboot.
I can go from using it all day to leaving it idle for 3-4 days. I never power it down and have left it off the charger for days in a row. I do tend to leave it on the keyboard dock nearly all the time, but it does see some time off dock.
One thing to add, when I first flashed to Revolver ICS, I foolishly flashed an OC kernel for HC. Needless to say I bricked it. Took me 1/2 a day to get it going again after flashing back to stock HC, then stock ICS and finally Revolver ICS. Been up ever since then and that was over 3 weeks ago, more likely 4+. Only time I get a reboot is if I initialize it. No sleep/freezing issues other than the noted single instance.
I call this luck of the draw and likely as to why ASUS can't figure it out since this problem seems like a some have it and some don't thing.
And yet I got a random reboot on a brand new install of pure stock 9.2.1.17 that I had nvflashed within 12 hours, and with blades kernel forget about it.. every hour reboot, and then on pure stock again I got splash screen boot loops..
I have never been experiencing the reboots either, but I only tried Android Revolution HD and CyanogenMod.
For some reason however, I will experience sleeps of death soon as I configure the Wi-Fi to shutdown when the screen is off.
geenius said:
I'm running revolver 1.3.1 and havne't actually had a single reboot, force close of bad experience, perfect so far and its been running since the release!!!
Click to expand...
Click to collapse
Same here. Was running a stock rooted version of ICS with Revolver 4 flashed over the top (I know this wasn't recommended, but I did it one night by accident, and it solved the other issues I was having with Revolver.
I moved on to CodeName Android after the other ICS ROMs pulled ahead. I haven't had the issue there either.
I don't know what the deal is.....but I'm thankful I don't have the issue! And even if I did, I only consume media on my transformer. So I can't say that it'd be a big deal.
1 and 1/2 days without a reboot
Turned off face unlock..... guess I'm not handsome enough to wake up my tablet. But I have wifi on as well. I will report but it seems to be running better.
Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.
Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts
I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.
I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?
dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.
I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2
Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks
Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.
For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2
Hey guys,
I have a VZW HTC One M8 with the following version details:
Cyanogenmod 11-20141112-snapshot-m12-m8
Unlocked bootloader
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0222
OPENDSP-V26.2.2-00538-M8974.0106
OS-
eMMC-boot
This phone came to me with a clean Cyanogenmod install on it. I wiped it anyway to be sure. I have an S3 that I've been running CM11 on up until I got this phone so I'm no stranger to Cyanogenmod.
My issues appear to be randomly occurring and I cannot seem to pin down what is causing it or when it actually happens. Here are the various issues I'm seeing:
1. Screen fails to reorient when being turn - this happens system wide, even the home screen fails to reorient. Perhaps a problem reading the gyro sensor?
2. Lux values get stuck, usually at 45. Ambient light sensor?
3. Double tap to wake stops working - need to use the sleep/wake button to turn the screen on. Can still double tap the status bar to turn the screen off
4. Incorrect battery reporting - The battery appears to drain normally and at a consistent pace, however if the phone is shutoff or rebooted I will sometime see a huge drop when the phone boots back up.
I have a screenshot from the phone this afternoon but cannot post it (attachments fail to upload on this forum). I can probably PM it to you though.
I noticed if the phone gets to 5%, sometimes ~15% it will just turn off because the battery has actually died but the OS thinks differently.
The first 3 issues fix themselves after reboot.
Oh and I've noticed that the profiles feature doesn't work properly. If the ring mode is set to vibrate on the work profile, it will stay in vibrate even when it switches back to the default profile which is set to ring mode. The phone will not let me set custom notification sounds with Profiles enabled either. Example: Hangouts uses the notification sound as set by the default in Settings. I cannot change this. I can turn off Profiles and I can change the notification tone on Hangouts all day long.
Not quite sure what I should be looking at here so any guidance or suggestions would be much appreciated. Let me know if you need any more details.
You answered the question yourself in the second sentence of your post.
beaups said:
You answered the question yourself in the second sentence of your post.
Click to expand...
Click to collapse
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
cstokes86 said:
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
Click to expand...
Click to collapse
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
beaups said:
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
Click to expand...
Click to collapse
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
cstokes86 said:
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
Click to expand...
Click to collapse
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
beaups said:
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
Click to expand...
Click to collapse
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
cstokes86 said:
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
Click to expand...
Click to collapse
If you are looking for stability, flash a sense based ROM. Its just the way it is.
beaups said:
If you are looking for stability, flash a sense based ROM. Its just the way it is.
Click to expand...
Click to collapse
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
cstokes86 said:
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
Click to expand...
Click to collapse
Yes you should update that firmware. There's an emmc controller firmware update amongst other things included you should have. Have you tried gpe or stock with some of the xposed modules now available?
I saw a new "nightly" has been pushed out for the Relay. Based on the changelog (fixing integer overflows and underflows), this looks like a fix for Stagefright.
I've updated from within the 20150607 nightly, and so far, everything looks good. My GPS and camera still work fine, and I didn't bother toggling any settings before updating.
At least I have ONE phone with a Stagefright fix. It's kind of ironic that it's the oldest of my Androids.
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
So I guess it's time to bite the bullet and do the double-twist-and-backflip GPS fix. Let me go over this for a moment, to get it straight.
I need a new CWM recovery, latest'n'greatest.
I need and old 10.1 or maybe 10.2 ROM image.
I need the old baseband firmware to go with the old ROM image.
Is this the full list?
There have been numerous links to all three of these, but I tried last week, and at least some of them have gone stale. Does anyone have a current and working set of links for them?
My wife's Relay is still at CM11M8, and really it's about time I got her properly flashed forward, especially now with Stagefright and Freak both fixed. We've locked out on Stagefright so far because we have voice-only through PureTalkUSA, only do data on wifi, and therefore don't do MMS.
GPS fix:
You need a CM10.1 build (Only ones ever produced were 'experimental'), the ICS stock baseband (modem) and the JB stock baseband. Recovery doesn't particularly matter, so long as you can flash images, but I still recommend the CWM that has been around for a while (I've tested it, it works fine even with upcoming Images)
Procedure:
Boot into recovery, run a full backup on your device.
flash ICS baseband
Flash CM10.1 Image
Factory Reset
Boot into system (Not sure if this is needed, but I always do.)
Once system boots up, shut system down.
Open phone, pull battery.
Wait ~30 seconds, replace battery.
Boot phone.
Once system boots up, (If you have a way to test it, GPS should work now). Reboot into recovery.
Flash JB baseband.
Restore your system backup.
Reboot into system. Your GPS should now work with your current system.
I posted a reply into a thread, there was an up to date link with just the modem... I can confirm that running on CM nightly (june something) I have no issues with GPS, wifi 2.4ghz band doesnt work with bluetooth enabled though
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
phred14 said:
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
Click to expand...
Click to collapse
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
dzl said:
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
Click to expand...
Click to collapse
I got my Relay about a year and a half ago for Christmas, mostly as a learning vehicle, but also for the convenience. The plan from the get-go was to put Cyanogenmod on it. For a while it was wifi-only, then a few months later my wife decided she wanted one, and I found the Family Flex Plan at PureTalkUSA that let us have two phones for the the cost of a Virgin Mobile and TracFone. (What we had before) It's also one of the few ways to get voice-only, and use wifi for data.
The Relay is getting a bit long in the tooth, and perhaps most discouraging "aging" side of it is the ramp-down here. However anything I get will be CM-ready from the get-go.
Flashed the latest CM11 nightly today. No major bugs so far with moderate use throughout the day. So much faster than my Xperia with the stock firmware, actually enjoying Android again.
Sent from my SGH-T699 using XDA Free mobile app
20150823
I had been running M8 since it came out until last weekend. Decided to do a complete wipe and try for the newest nightly to fix the Stagefright bug. Things went real smooth. GPS is working faster than ever.
Everything runs like a dream... except the adaptive light sensor. Adaptive brightness is not working at all. I've check the sensors and the Lux sensor is working fine. If I turn on adaptive brightness, and then adjust, the settings crash. Anyone else experiencing anything like this?
Yeah that is one thing that I have noticed as well, the auto brightness doesn't work. Can't say I've attempted to diagnose it at all though.
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
TPMJB said:
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
Click to expand...
Click to collapse
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
phred14 said:
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
Click to expand...
Click to collapse
I would like for updates to CM12, but we only have unofficial versions of CM12. I am a noob at compiling and I hear it is an arduous task to get it working.
Magamo said:
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
Click to expand...
Click to collapse
Some time between then and now (some time in September, I believe) the stagefright fixes were backported to the omni-4.4 branch. I have a build from this running on my relay right now and Zimperium gives it a clean bill of health.
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
kodimagnyl said:
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
Click to expand...
Click to collapse
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
i have a rooted stock rom, can i move to the latest cm11 nightly build?
phred14 said:
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
Click to expand...
Click to collapse
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
kodimagnyl said:
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
Click to expand...
Click to collapse
Can't reach the second link, but I've already got a copy of the current modem, the old one is what I've been missing. Things are starting to get busy, so I don't know how soon I'll be able to try it.
BTW, I've been told to do a "nandroid backup", then wipe and load the back-level stuff, do the GPS fix, then a "nandroid restore". I'm going to presume that the backup / restore doesn't handle the modem, and on my way back from back-level, I'll first have to use heimdall to reload the current modem?
Thanks