Related
Hi,
after spending some fruitless hours trying to get better GPS performance from my p990 (cm7 nightly 60-64, baseband 0218, cm7 RIL), trying various tweaks to gps_brcm_conf.xml and even older versions of glgps, I've concluded (tentatively) that
- /data/gps/lto.dat is a file (containing ephemerals?) that's used for A-GPS
- my setup never manages to download this file.
Following this thread of thought, I tried the following (The URL is from a google search while I was digging about in gps_brcm_conf):
Code:
adb shell
cd /data/gps
wget http://gllto.glpals.com/7day/latest/lto.dat
chmod 777 lto.dat
I also did
Code:
rm gldata.sto
to remove (I think) stored orbital data from previous fixes to try to keep the results comparable.
Though measuring GPS performance is difficult due to constantly changing constellations and atmospheric conditions, I think this has made a difference in time-to-fix for me. Admittedly this might just be a placebo, so no guarantees.
If anyone wants to try this and post their results, it'd be great. And, if anyone knows anything about lto.dat, why its needed, and why it never gets downloaded, please post here so I won't be kept awake at night wondering
It might be that the Tegra2 setup doesn't use it, much like gps.conf.
Best bet would be to ask RC I suppose, although he's a bit tied up with some GPL stuff apparently.
Rusty! said:
It might be that the Tegra2 setup doesn't use it, much like gps.conf.
Click to expand...
Click to collapse
It's referred to in gps_brcm_conf.xml (the chip-specific config file), so I've assumed it's relevant to our setup. But yeah, it's possible.
Best bet would be to ask RC I suppose, although he's a bit tied up with some GPL stuff apparently.
Click to expand...
Click to collapse
Yeah, I'll hold off on that a bit.
Would be interesting to know if anyone actually has that file in /data/gps. I'll try to find time for a restore to stock (or at least modaco) to see if it gets downloaded in the standard setup. We'll see.
nrkabul said:
It's referred to in gps_brcm_conf.xml (the chip-specific config file), so I've assumed it's relevant to our setup. But yeah, it's possible.
Yeah, I'll hold off on that a bit.
Would be interesting to know if anyone actually has that file in /data/gps. I'll try to find time for a restore to stock (or at least modaco) to see if it gets downloaded in the standard setup. We'll see.
Click to expand...
Click to collapse
don´t have it on cm .64 either ...
Just created the missing file, and got a lock from stone cold, indoors pretty fast. Did that file help? Dunno lol
Will have to test more.
OK... here is my extremely unscientific test...
GPS Status without lto.dat: 43 seconds to lock.
GPS Status with lto.dat: 19 seconds to lock.
aGPS data was cleared before each test. Interesting, but far from conclusive.
Whooo! This is amazing!
Tried to lock inside without lto.dat, no luck at all after 70+ seconds... Copied the file into /data/gps, tested the same spot and got lock after cca 10 seconds!
This is amazing
nrkabul said:
Hi,
And, if anyone knows anything about lto.dat, why its needed, and why it never gets downloaded, please post here so I won't be kept awake at night wondering
Click to expand...
Click to collapse
This might be of interest then: http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf
nrkabul said:
Hi,
after spending some fruitless hours trying to get better GPS performance from my p990 (cm7 nightly 60-64, baseband 0218, cm7 RIL), trying various tweaks to gps_brcm_conf.xml and even older versions of glgps, I've concluded (tentatively) that
- /data/gps/lto.dat is a file (containing ephemerals?) that's used for A-GPS
- my setup never manages to download this file.
Click to expand...
Click to collapse
Good find. That file basically holds an analog to XTRA data; It doesn't quite help picking up satellites, but it makes locking onto them a hell of a lot faster once they're found.
TrymHansen said:
This might be of interest then: http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf
Click to expand...
Click to collapse
Ah. Yes, that explains it nicely. Thanks.
Sent from my Optimus 2X using XDA App
aremcee said:
Good find. That file basically holds an analog to XTRA data; It doesn't quite help picking up satellites, but it makes locking onto them a hell of a lot faster once they're found.
Click to expand...
Click to collapse
Indeed. That matches what I've observed.
Any idea why the download doesn't happen?
Sent from my Optimus 2X using XDA App
Download will happen for the next nightly, this is going to please a lot of people; top bombing.
This is truly awesome, hope it might have some small influence on apps keeping gps alive when screen is turned of too... Maybe a little too much to wish for, but..
Thanks send to nrkabul
It wont, that's just how Android works... my stock N1 was the same.
Endomondo excepted, that should be able to hold a lock, but doesn't. Run Keeper does it fine though.
Rusty! said:
It wont, that's just how Android works... my stock N1 was the same.
Endomondo excepted, that should be able to hold a lock, but doesn't. Run Keeper does it fine though.
Click to expand...
Click to collapse
I had stock rom, Gilgamesh and the first one WGLpoelstra posted, and Endomondo worked flawlesly on those roms, dont know what happened to GPS since then, but on CM7 i have to use My Tracks in the background to make sure that Endo records track.. Havent heard about keeper before, will check it out
Rusty! said:
Download will happen for the next nightly, this is going to please a lot of people; top bombing.
Click to expand...
Click to collapse
Ah, quick work by arcee. I'd already cobbled together an app to do it for me, but this will be a lot better. Fingers crossed for a usable GPS
Sent from my Optimus 2X using XDA App
another workarround: Install this https://market.android.com/details?id=net.canaryx.gpsaids&feature=search_result
and download lto file. open root explorer /data/gps and rename lto2.dat into lto.dat
ionhide said:
I had stock rom, Gilgamesh and the first one WGLpoelstra posted, and Endomondo worked flawlesly on those roms, dont know what happened to GPS since then, but on CM7 i have to use My Tracks in the background to make sure that Endo records track.. Havent heard about keeper before, will check it out
Click to expand...
Click to collapse
It's a pain, and odd the Endomondo can't do it, when others can. If they all couldn't it would be an obvious problem, but when it's just that one (the one I happen to use at that) it's frustrating.
Still, as you've noticed, there is a work around, this might be less hassle than having My Tracks going though: https://market.android.com/details?id=com.kaukovuo.android.trackerbooster
lto.dat works great for me !!
got a fix in my car in about 5 sec, some seconds later got 10 satelites fixed !
GPS works like it did on MCR Rom for me now !
great discovery !
Rusty! said:
It's a pain, and odd the Endomondo can't do it, when others can. If they all couldn't it would be an obvious problem, but when it's just that one (the one I happen to use at that) it's frustrating.
Still, as you've noticed, there is a work around, this might be less hassle than having My Tracks going though: https://market.android.com/details?id=com.kaukovuo.android.trackerbooster
Click to expand...
Click to collapse
I tried that app, and it didnt work for me, thats why i use My Tracks..
Sent from my Optimus 2X using XDA App
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
I just recently went from CM10 to CM10.1 (JB 4.2.2) on my Bionic and love it but noticed that when I insert it into the standard dock it doesn't sense it and go into a "Dock Mode". I am not sure if it's just my phone or not (I don't think so, it worked with CM10) and I am too new to post in the developers forum to let them know about it and it is still under development. Does anyone have any input how to get this to work and/or if you have access to post in the appropriate forum can you let them know about this?
I believe yes. if you go Setting>Display>Daydream you can get a clock or other options which can be triggered by the docks.
hackthis02 said:
I believe yes. if you go Setting>Display>Daydream you can get a clock or other options which can be triggered by the docks.
Click to expand...
Click to collapse
I found that and adjusted it and it still isn't triggered when docked. I booted back into stock ICS and CM10 (JB 4.1) and it seems to work then so I know it's not my phone. Are there any other settings to check?
I really love CM10.1 and really appreciate the work they do and know that it is still a work in progress but would like to submit it a bug report about it just so the dev's know. I would let them know myself but I can't post in that thread because I am a "noob" to this forum even though I have been using custom ROM's for a couple of years. Can someone help me out?
Dime-Baggins said:
I found that and adjusted it and it still isn't triggered when docked. I booted back into stock ICS and CM10 (JB 4.1) and it seems to work then so I know it's not my phone. Are there any other settings to check?
I really love CM10.1 and really appreciate the work they do and know that it is still a work in progress but would like to submit it a bug report about it just so the dev's know. I would let them know myself but I can't post in that thread because I am a "noob" to this forum even though I have been using custom ROM's for a couple of years. Can someone help me out?
Click to expand...
Click to collapse
I've been struggling with this too. It doesn't seem to work in either the latest Kexec versions of CM10.1 or AOKP. I suspect it has to do with something still needing to be merged into the kernel. I've tried restoring the different dock component apks from ICS, but that doesnt' help either. I sent a tweet to Hashcode yesterday asking if he knows how to get it working, but he hasn't responded yet. I'll let you know when he does.
I would not worry too much about it. CM10.1 is still in the nightly phase so a lot of stuff will not work, and they know this. I am sure it will be working once we hit RC.
I'm pretty sure that Daydream is set up to trigger with the screen timeout. Myself, I have mine set to 2 minutes, and once I'm docked, it seems to be about 2 minutes later that Daydream turns itself on.
irish_711 said:
I'm pretty sure that Daydream is set up to trigger with the screen timeout. Myself, I have mine set to 2 minutes, and once I'm docked, it seems to be about 2 minutes later that Daydream turns itself on.
Click to expand...
Click to collapse
Ya, for the life of me I can't get anything to happen when I dock it. Hopefully they get this fixed on an upcoming nightly. I'd even donate to get this one done because I use it for an alarm clock everyday. The thing I am doing in the mean time is to set the daydream "when to daydream" setting to "while charging" and then manually turn on the app "Dock Clock" when hitting the hay. It's a good work around but was a lot easier when it just triggered when docked. Thanks again to the dev's! They rock!! :good:
This is one the main issues I have with cm10.1. While the daydream setting works OK for my bedside dock, there is no way to differentiate between that dock and my car dock. So I can't launch a custom car launcher when in my car.
linuxgator said:
I've been struggling with this too. It doesn't seem to work in either the latest Kexec versions of CM10.1 or AOKP. I suspect it has to do with something still needing to be merged into the kernel. I've tried restoring the different dock component apks from ICS, but that doesnt' help either. I sent a tweet to Hashcode yesterday asking if he knows how to get it working, but he hasn't responded yet. I'll let you know when he does.
Click to expand...
Click to collapse
Have you heard back from Hashcode yet about the dock thing? I keep flashing nightly's hoping it'll be working but it's still a no-go. Today's nightly looks like it's gonna have a lot of changes/additions so I'll keep my fingers crossed.
FYI - I got a message back from Hashcode on twitter and he said "No dock features yet" :cyclops:
Any idea how the LapDock will respond? That's the sole reason i have stayed stock. I bought this dumb phone for LapDock...
ak110707 said:
Any idea how the LapDock will respond? That's the sole reason i have stayed stock. I bought this dumb phone for LapDock...
Click to expand...
Click to collapse
Same, that's why I haven't installed one of the custom ROMs on mine, because I love the lapdock functionality, which requires HDMI to be working. As far as I know, none of the non-Blur ROMs have working HDMI.
I love this ROM but I sure wish the dock stuff worked. I use my phone as an alarm clock on the dock and I switched over to liquidsmooth jellybean
yesterday to see if it's dock stuff worked (it doesn't). It was awesome but (even though the dock stuff doesn't work) until I got an FC for the clock when my alarm went off this morning so I am back.
On a separate note I installed yesterdays nightly and rebooted and my wifi was broken and i couldn't even turn it on so i reverted to the fixed version of the 3/27 nightly and was back in business. Hoping they get the dock up and going soon. :fingers-crossed:
Dime-Baggins said:
I love this ROM but I sure wish the dock stuff worked. I use my phone as an alarm clock on the dock and I switched over to liquidsmooth jellybean
yesterday to see if it's dock stuff worked (it doesn't). It was awesome but (even though the dock stuff doesn't work) until I got an FC for the clock when my alarm went off this morning so I am back.
On a separate note I installed yesterdays nightly and rebooted and my wifi was broken and i couldn't even turn it on so i reverted to the fixed version of the 3/27 nightly and was back in business. Hoping they get the dock up and going soon. :fingers-crossed:
Click to expand...
Click to collapse
My bad - operator error. I wiped and reflashed 3/27 the 4/4 and updated again and everything is peachy keen again.
So this may be a silly question, but is there any "light at the end of the tunnel" for Car dock mode in any of these JB ROMS?
We all thought that Root was unobtainable on the JB but that was proven wrong. Here's hoping that Car Dock mode is in the near future as its the one thing on my phone that i use consistently every day driving to and from work.
zetachi said:
So this may be a silly question, but is there any "light at the end of the tunnel" for Car dock mode in any of these JB ROMS?
We all thought that Root was unobtainable on the JB but that was proven wrong. Here's hoping that Car Dock mode is in the near future as its the one thing on my phone that i use consistently every day driving to and from work.
Click to expand...
Click to collapse
I was able to get the car dock mode to launch using the app below and the new Blurry ROM. No luck on CM10.1.
https://code.google.com/p/bionic-dock/
zetachi said:
So this may be a silly question, but is there any "light at the end of the tunnel" for Car dock mode in any of these JB ROMS?
We all thought that Root was unobtainable on the JB but that was proven wrong. Here's hoping that Car Dock mode is in the near future as its the one thing on my phone that i use consistently every day driving to and from work.
Click to expand...
Click to collapse
@Hashcode0f said:
I plan on supporting basic dock features and HDMI output (not webtop).
Click to expand...
Click to collapse
Source
Though I'm confused... is there something more "to" webtop/lapdock since the ICS version? AFAIK it's just leveraging the HDMI output for a higher resolution screen and attaching a USB keyboard/mouse. It hasn't been something "Special" since Gingerbread when it was Ubuntu based, right?
cixelsyddyslexic said:
Though I'm confused... is there something more "to" webtop/lapdock since the ICS version? AFAIK it's just leveraging the HDMI output for a higher resolution screen and attaching a USB keyboard/mouse. It hasn't been something "Special" since Gingerbread when it was Ubuntu based, right?
Click to expand...
Click to collapse
That confused me as well. I know there are some things like volume control that might not work (but I'm not sure they work on the stock JB ROM anyway) but people have modded all sorts of things to work with the lapdock (other phones, Raspberry Pi) by simply treating it as an HDMI display and a keybord/mouse. If a mod ROM even had that level of functionality I'd be happy with it, and I certainly don't expect a return of the original Ubuntu based webtop mode.
On a similar note, has anyone tried a mod while using the HD dock? That is supposed to do something similar, except I believe it comes with a remote control.
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.
I use milaq's nightlies, and for my needs, it's more than adequate.
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
flashroyal said:
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
Click to expand...
Click to collapse
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
stefan2012 said:
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
Click to expand...
Click to collapse
Logs?
JoinTheRealms said:
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Click to expand...
Click to collapse
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
flashroyal said:
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
Click to expand...
Click to collapse
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
JoinTheRealms said:
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
Click to expand...
Click to collapse
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
flashroyal said:
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
Click to expand...
Click to collapse
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
JoinTheRealms said:
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
Click to expand...
Click to collapse
I don't know why, but every time I tried to record screen, phone just reboots. I tried with various apps, every time same thing. I cant find built in app in beanstalk 4.4. I'll try stock again but cant before tomorow. Thank you for your time
Use beanstalk with grouper blobs, and press vol up and power simultaneously to record
Sent from my LG-P880 using Tapatalk 4