Well, the story goes:
My wife´s SGH-i474 (AT&T) had 4.1.2 installed, crappy reception, launcher buggy (it created more desktops everytime she wanted to delete one), and overall the phone felt laggy. She plays just 3 games, Farmville 2 CS, Candy Crush and Clash of Clans (she´s actually pretty good this one). Not too long ago, since the phone was only rooted to install greenify and link2sd to freeze the bloatware, she found out that it was possible to update the phone to a newer release; and I saw that there was an official OTA to 4.4.2, but since we are overseas, the stock update won´t go (it said that the phone was updated).
I dived into google and I saw that here on xda there was a method to get it into 4.4.2. And me, being the android guy and wanted to get lucky I tried it and succedded, but with one detail...
You see, I mentioned the games for a particular reason, 2 ouf of 3 work, Farmville for some reason doesn´t load (it gets to the loading screen and stays there at 0%). I left it overnight, with the option of leaving the screen on while charging, so that the phone won´t "sleep" to see if the game need to download a file and it was taking a long time, but no, 10 hours later it was still at 0%.
After that, I decided to install Logcat to see what was going on while the game at launch time. Surpringsinly, logcat was unable to save the log to the "sdcard". , another dive into google revealed that there was indeed a bug on the sdcard permissions (never knew that this kind of thing would happen to the gigantic Google, OMG ), and there were several fixes available, which I tried, even manually (just to see that the apps did indeed what they advertised, but to be true, the stock rom that I used had this fix already installed, thank you Mr even... or who ever went into the trouble of making all those files and instructions that helped me get into 4.4.2, I just don´t recall the nickname, but I do remember he has a beard )
Back to the point, I find it odd, that logcat was unable to write to the sdcard, and more odd that just a game was unable to work, because it worked before the update, but logcat doesn´t show anything related to "permission denied" to the Zynga app, nor to logcat itself when it wanted to write to the sdcard.
Since I am just a poweruser, I already wiped to stock and nothing changed, I tried another logcat application with the same result, so what I believe is that maybe the apps have something wrong, because I didn´t find anyone complaining about the stock rooted rom that I used. Besides that it was stock, and just rooted, I just wanted to know if anyone happened to have this problem and if they were able to fix it or have a workaround it.
Just to clarify, the phone works perfectly, and all the 51 apps that has installed (yep, she´s kinda a tech girl herself) work, except FV (which won´t go past 0% at the loading screen) and those to logcat applications that I used. (Catlog and Logviewer Lite, which can´t save logs to the sdcard), even the camera works and saved pics to the sdcard withouth problem (one of the things I saw reading is that maybe the camera would stop working but nope, just fine).
If you have any ideas, please, express yourself.
The kitkat update for google did in fact make it to where nothing could be written to sd. Google trying to get rid of sd cards for some stupid reason. Anyway, if the phone is rooted, try the xposed app with the external sd modules. Took care of my problems with that, not on my S3 because enewman17 is so damn awesome with his S3Rx rom that he took care of that, but on my Note 10.1 and Tab 4 fixed it right up
I see, could you be more specific about the xposed app, the name in fact, a search rendered quite a few, an I am not native english speaker.
I mustbe cursed hehe, I found the "app", is a framework, but guess what? I am unable to install because it is unable to write to the sdcard hehehe, I will give a try to the custom rom.
To mr Enewman, you sir, you deserve a cold beer, my wife is now happy, just a little glitch with the google keyboard at the first boot but after that excellent.
XDADoog said:
To mr Enewman, you sir, you deserve a cold beer, my wife is now happy, just a little glitch with the google keyboard at the first boot but after that excellent.
Click to expand...
Click to collapse
It is an outstanding ROM for sure. Glad it's working.
Related
Hi all,
I have as strange issue in regards to apps on the SD card. I'm rooted, S-off on 3.29 stock. I installed installLocationMod, which enabled me to move any apps, even those not necessarily programmed, to be moved on 2.2 to the SD card. I basically moved everything that's not system, gapp, or widget related.
Everything works great, until I have to reboot, or I attach the phone to a PC as a hard drive. Basically, the apps don't come back after the phone comes back up, or its disconnected from the PC. I have to spend many hours doing reboots, battery pulls, dalvic cache wipes, etc, and then seemingly randomly, they pop back up.
When they're missing in the app list, the settings / app manager shows that they're there, but they're always "computing" when I select one to read the properties. Also, the market installer gets stuck, and I can't uninstall anything either.
Recently, I've read threads about partitioning the card before moving apps to SD.. is that still necessary with 2.2? Is that why this is such a pain? I'm thinking maybe the only solution is to move everything back to where they came from, and only move those apps that are specifically programmed to be moved on a non-rooted phone, and get rid of the modlocationinstall program altogether. That's a drag because I don't have room for all the apps, so I'll have to lose some... which is one of the reasons I rooted to begin with.
Any ideas? BTW, this is the second SD card that does this. The card is good.
Thanks,
Mike
Hey, I found this elsewhere on the forums in the LimeMOD rom in regards to mod install location:
"important !!! after a reboot you need to stop LauncherPro in the running applications menu to reload all sd installed apps !!! "
Could Sense be the reason for the missing apps issue? Is there a way to 'postpone' it on reboot?
Thx,
Mike
I've been having ever same problem
Sent from my PC36100 using XDA App
futuristicstyles said:
I've been having ever same problem
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm thinking I might try stopping the Sense service after the reboot and letting it restart and see if they come back. I'll try it if I have to reboot again.. I'm actually avoiding rebooting at all cost now since it takes hours of frustration to get back to working order again.
Another thing I noticed.. alot of programs have that I moved have hidden services that are listed in a start-up auditor I installed just to see what the system was doing on boot up. I originally thought I'd be safe moving them since I didn't have widgets associated with them, or they didn't seem system related. Now I'm beginning to realize that I might have to be more careful what is moved, since I don't always know how they'll behave on boot. I suppose that's another reason why its best for non-techies just to rely on devs to build the default 2.2 a2sd behaviour into their programs, rather than forcing them there with stuff like mod install location.
Oh well... I'll keep you all updated when I know more. I'm rather surprised though, that more people aren't experiencing this...
Restarting Sense doesn't do anything. It seems still to be completely random.. usually after 4 or 5 hours of me continually manual rebooting. Nobody has any input at all?
greyopaque said:
I'm thinking I might try stopping the Sense service after the reboot and letting it restart and see if they come back. I'll try it if I have to reboot again.. I'm actually avoiding rebooting at all cost now since it takes hours of frustration to get back to working order again.
Another thing I noticed.. alot of programs have that I moved have hidden services that are listed in a start-up auditor I installed just to see what the system was doing on boot up. I originally thought I'd be safe moving them since I didn't have widgets associated with them, or they didn't seem system related. Now I'm beginning to realize that I might have to be more careful what is moved, since I don't always know how they'll behave on boot. I suppose that's another reason why its best for non-techies just to rely on devs to build the default 2.2 a2sd behaviour into their programs, rather than forcing them there with stuff like mod install location.
Oh well... I'll keep you all updated when I know more. I'm rather surprised though, that more people aren't experiencing this...
Click to expand...
Click to collapse
update:
After several unsuccessful reboots, I was able to get back the apps by going into settings / phone storage and unmounting the card, and remounting it, with no reboot. I've tried that in the past and just had the phone lock up, but this time it worked. FWIW, modinstalllocation was set to auto, and debug was off. I don't know if its repeatable, since I don't relish having half my phone unavailable for half the day to test it, but next time I lose everyting, I'll try it again and update the thread. I realize that judging from the lack of responses, most of you all don't really care, but since one guy did say he had the same problem, and to prevent someone in the future from going through all this aggravation, I'll keep on top of this. It will be my little contribution to the forum...
UPDATE: Had to finally do a reboot, and all the SD apps came back! I'm thinking the card dismount/remount did the trick
Mike
it's been almost 4 days now
everything on the phone runs great until i restore that mysterious app from backup.
problem is having over 500+ apps/games makes it extremely difficult to pin point which particular app is causing the hot reboot
hot reboot = not full reboot, it just crashes everything and reload the OS
my current suspect some of the many plug ins for Go Launcher EX or IM+
Go Launcher EX runs great on the phone, but then once i restore all those plug ins, it appears to cause the problem
same with IM+
there are other apps i suspect as well like SD card speed increase, or Dual USB
or if not something to do with the Keyboard
at one point the keyboard selection got locked out, and i was unable to choose another keyboard or language
anyways... back to the haystack to find the needle...
Have you tried hooking it up to adb and running a logcat on that bad boy?
Edit: If you run logcat and reproduce the hot-reboot it may show you what is causing the problem. And if that doesn't work there is also a command you can call to get the last kernel message before the reboot. I don't remember what that's called though. Kmsg I think, idk.
-We do what we must because we can. For the good of all us, except the ones who are dead.-
lol perhaps i should, i was too lazy to do that, don't really have the time, but after spending 4 days trying to track down the app... i guess it's about time to go about it the smart way
AllGamer said:
lol perhaps i should, i was too lazy to do that, don't really have the time, but after spending 4 days trying to track down the app... i guess it's about time to go about it the smart way
Click to expand...
Click to collapse
If the simple method doesn't work the first couple of times don't try it repeatedly, it won't ever work effectively.
-We do what we must because we can. For the good of all us, except the ones who are dead.-
i've actually narrowed it down to ICE Music 4.0x or IM+
everything else working great since the last wipe & restore, excluding those 2 apps
AllGamer said:
i've actually narrowed it down to ICE Music 4.0x or IM+
everything else working great since the last wipe & restore, excluding those 2 apps
Click to expand...
Click to collapse
Freeze one and test it out.
-We do what we must because we can. For the good of all us, except the ones who are dead.-
The command is: adb pull /proc/last_kmsg
Sent from my Juggernaut SGSII or Galaxy Tab 10.1 now "In Paris"
in the end the problem was caused by the USB / Media Scanner
AllGamer said:
in the end the problem was caused by the USB / Media Scanner
Click to expand...
Click to collapse
That kinda makes sense as to why you thought it was music then but why im+?
-We do what we must because we can. For the good of all us, except the ones who are dead.-
both of them were caught doing something and then crashing everytime it happened
in the end it was because both were trying load up stuff from the SD card which was being hogged by the media scanner, and apparently that didn't share well among those apps and the system itself, and kaboom!
((if this is in the wrong place or has been covered before, I apologize...))
Hello all.
I just became the new owner of a family member's Samsung Galaxy S3 (AT&T). Already owning and tinkering with two xperia Ion's I wanted to have a little more freedom and experience Kitkat on the GS3.
I had no experience in unlocked bootloaders and all that, so I figured that I would let the Cyanogenmod Auto-Installer do the work for me and install CM11 on my device.
It worked great initially! No problems whatsoever aside from minor glitches here and there. As soon as I started installing some more apps and Xposed modules, I noticed that things were getting odd.
Eventually, my phone wouldn't connect to google's play services whatsoever. Despite countless resets of the phone itself and my modem/router, nothing seemed to help. Flushing the cache and dalvik didn't help either, nor did a factory reset. The issue kept coming back.
Thinking that perhaps another rom wouldn't have the problem, I installed C-Rom (which was based on 4.4.4 KK). It ran BEAUTIFULLY! It is sure one hell of a rom. But then, not too long after I had everything installed and running the way I wanted it to, it had the same errors as before.
I don't know how to explain the error other than the phone just generally messing up. I don't recall it ever having those issues on stock, but then again, it wasn't my phone on stock, and the first thing I did upon receiving it was put a custom rom on it.
But the error can only be explained as a general f***-up of the entire OS. Commands run brutally slow (I will launch the flashlight and it wont turn on until seconds, even minutes later. Alternatively, text messages take eons to send and receive, which I am positive is not an error on the AT&T side of things). Then, whenever I try to download or install an app from the play store, the application will download partially and then stall for what feels like eons. Some of the applications just stop there, and some I will find installed on the device some 30 minutes later. Not to mention that the signal icons on the quick setting tiles are all turned orange for some bizarre reason. Another bizarre issue is that no matter what, I can never launch the terminal to execute an htop, logcat, or anything! The terminal just stalls and eventually crashes, while it worked fine before.
I've checked online for errors similar to this, but haven't found anything that has helped the phone. Anyone out there who is willing to give this a crack or just point me in the right direction?
Thanks in advance.
benhofb said:
((if this is in the wrong place or has been covered before, I apologize...))
Hello all.
I just became the new owner of a family member's Samsung Galaxy S3 (AT&T). Already owning and tinkering with two xperia Ion's I wanted to have a little more freedom and experience Kitkat on the GS3.
I had no experience in unlocked bootloaders and all that, so I figured that I would let the Cyanogenmod Auto-Installer do the work for me and install CM11 on my device.
It worked great initially! No problems whatsoever aside from minor glitches here and there. As soon as I started installing some more apps and Xposed modules, I noticed that things were getting odd.
Eventually, my phone wouldn't connect to google's play services whatsoever. Despite countless resets of the phone itself and my modem/router, nothing seemed to help. Flushing the cache and dalvik didn't help either, nor did a factory reset. The issue kept coming back.
Thinking that perhaps another rom wouldn't have the problem, I installed C-Rom (which was based on 4.4.4 KK). It ran BEAUTIFULLY! It is sure one hell of a rom. But then, not too long after I had everything installed and running the way I wanted it to, it had the same errors as before.
I don't know how to explain the error other than the phone just generally messing up. I don't recall it ever having those issues on stock, but then again, it wasn't my phone on stock, and the first thing I did upon receiving it was put a custom rom on it.
But the error can only be explained as a general f***-up of the entire OS. Commands run brutally slow (I will launch the flashlight and it wont turn on until seconds, even minutes later. Alternatively, text messages take eons to send and receive, which I am positive is not an error on the AT&T side of things). Then, whenever I try to download or install an app from the play store, the application will download partially and then stall for what feels like eons. Some of the applications just stop there, and some I will find installed on the device some 30 minutes later. Not to mention that the signal icons on the quick setting tiles are all turned orange for some bizarre reason. Another bizarre issue is that no matter what, I can never launch the terminal to execute an htop, logcat, or anything! The terminal just stalls and eventually crashes, while it worked fine before.
I've checked online for errors similar to this, but haven't found anything that has helped the phone. Anyone out there who is willing to give this a crack or just point me in the right direction?
Thanks in advance.
Click to expand...
Click to collapse
It sounds like you're the modules you're installing are crashing your system. I'd suggest you do a clean flash of w/e rom you wanna rush (you seem to like C-rom) and run it clean for a few days. You can install apps and such but don't restore system apps and don't install modules.
If it runs fine after a few days, you can cherry-pick the modules you wanna use (make sure they're made for the sammy phones). Install one or two, test for a couple days and so on. You'll eventually find which one is messing with your system (if that's actually what's causing the problems).
All seems to be well now. I've isolated the problematic app after slowly restoring all my app data one at a time. I have since moved to a different rom (SOKP) and everything is going running smoothly! Surprisingly, it wasn't Xposed causing the issue, but a market app that displays system info similar to conky on Linux computers. Once I installed it, the system just crapped out. Signals dropped, the terminal froze, and none of my apps seemed to work properly. But once I uninstalled the app and reset my phone, all was well.
Thanks for pointing me in the right direction!
Hi everyone,
I'm the new owner of an unlocked T-Mo D851, and will be using it on AT&T. I bought the T-Mo version instead of the ATT version due to the unlocked bootloader and better Dev support. Love those Devs!
I figured I'd post a thread with the things I learn along the way, to help others that might benefit, particularly since I'm joining the G3 community long after the novelty has worn off. Folks like me that join have a lot of past experience to review here, and so much is out of date it can be intimidating, particularly when our new device acts a lot different from our old one. I hope this thread helps someone, but at minimum it will serve as documentation for me to refer back to, should I need that. I'll include links where appropriate.
I'm an intermediate level flasher, having worked with maybe 6-8 other phones/tablets. So, I know enough to be dangerous, but not enough to have an ego to bruise. My most recent phone was a T-Mo Galaxy S4. But I dropped it, and cracked the screen, just a few weeks after getting it all settled in with a nice 5.1.1 GPE ROM. Sigh.
I got the phone a few days ago but have just gotten around to working on it.
On day 1 I charged it up, skipped setup (touch corners, upper left, upper right, lower right above the softkeys, lower left above the softkeys... took 10 tries or so!), and connected the wifi (no sim card inserted yet). It immediately found update 20E (it shipped with kitkat). I let that update, but was surprised it didn't find the current 20G update. I want to make sure I start with the latest firmware/modems etc. installed.
In this thread, helpful user @mitbit2k3 pointed me to the online LG site that lets you download the LG Mobile Support Tool. It also gives instructions for installing the PROPER PC connection driver for the phone which works, versus the default Win7 driver that doesn't work for the purposes of the update. With proper driver installed, and with USB connection in the right mode (follow instructions to set the phone USB settings), I got up to 20G stock.
I exercised the phone a bit (still without SIM card) and made sure everything worked... cameras, GPS, wifi, etc.
Then I figured it would be time to install TWRP and take it from there. Much to my surprise, you need to root this thing FIRST. Even with an unlocked bootloader, you can't just fire up ODIN and flash TWRP.
I did my research on the forum and through Google... with all the versions of software since release there were numerous descriptions of how to root the thing, some of which were outdated. For me, on 20G software (5.01 Android), this worked fine:
https://www.reddit.com/r/LGG3/comments/3n0nk1/new_super_easy_oneclick_way_to_root_g3/
it references back to XDA of course:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
From this I learned to review the top level LG G3 subforums, not just the T-Mobile XDA subforums!!
OK, that rooted me just fine and installed SuperSU. I was able to use the "first way" which is super simple.
With that done, I was able to install TWRP. I went straight to the source for it:
https://twrp.me/devices/lgg3tmo.html
I used the "dd" method which involves running ADB on the PC. I use a version that is a "Minimal ADB and Fastboot" that works fine... I used it to mess around with my Shield tablet previously, so I was familiar with it. Basically you run the minimal ADB through a desktop icon, and it loads a command line interface. You type ADB Shell after plugging in the phone to the USB cable (it has to be on, developer options enabled, debugging enabled). Then you type the commands listed on the TWRP site. Pretty soon TWRP is installed.
Next I had to figure out how to get into download mode. Yeah, yeah... power plus volume down... been there done that, but on the LG you have to boot with power/down, then when the LG icon comes up you release for a second, then press the two keys again, then at the next screen tell it you want to wipe the phone, and confirm this again on the next screen. THEN it finally boots into TWRP. Kinda scary. And getting the keys right takes some practice.
Once in TWRP, I backed everything up (including EFS partition) to an external SD card, just in case I messed something up. I had previously erased the SD card from within the phone's SEttings/Storage mode, to make sure it would be able to be accessed. No problem.
So now I've got a rooted phone, with TWRP installed, and the next step is to figure out what I want to do ROM wise. I wish there were a 5.1.1 GPE stock + LG Camera ROM. But I haven't found one. I like plain ROMs. The default stock ROM, even if it were debloated, its a bit annoying to me (and just 5.0.1) so I'll probably move to BlissPop or Slim something, but I will research around.
It's time to stick my SIM in and see how the phone does on AT&T. I'd like to get a baseline before I go ROM-hopping.
I will say that on stock ROM, with no SIM but WIFI on, the standby power drain on this thing is incredible. It went overnight (7 hours) and was still reading 100%. A whole 24 hours in, it was only a few percent lower. Of course, I hadn't attached any Google accounts, so the phone was truly idle, but it's very impressive nonetheless.
Stay tuned. I'll be updating this as I go along.
OK, I'm a few hours in.
No problem with my ATT SIM card in the phone; the phone was purchased unlocked and everything hooked up fine as soon as I entered in the APN information for ATT (which you can get from here).
The phone gave me a warning about WIFI Calling invalid SIM; I went into the settings and turned off WIFI calling, since I'm on ATT and only T-Mo offers it.
One other problem I haven't sorted out yet is that I get a text each time I reboot the phone, apparently my phone is sending a text to a very long address 060504071000004163.... and the text I get back is an error message that this isn't a valid number. Not sure how to turn this off. Annoying, but once per boot won't kill me until I figure it out. Google will likely be my friend. EDIT: I think this relates to T-mo visual voicemail. I went into the T-Mo Visual Voicemail app and I immediately got another one of these texts. Time to remove this app...
Meanwhile I notice the WIFI reception of this phone is much stronger than the S4. On the other hand, it seems less likely to drop a weak WIFI in favor of a stronger one... I have several access points around my house, and I've found I've needed to switch them manually now and then. Haven't had to do this on the S4.
I'm also struggling to get restores to work from my Backup Your Mobile app. I moved the backup onto an SD card in the G3, but the app isn't recognizing it. Uh oh. That's got my MMS/SMS/Call log backups. So, I've still got things to work on.
I gradually entered my various Google accounts, and let Play Store download the updates needed for all the apps. I've got about 75% of the apps I use re-downloaded.
I've got one "serious" problem in that the Play Store says the ATT Visual Voicemail app, which is a cornerstone of how I use the phone (because it transcribes voicemails into readable text), isn't compatible with my phone. That's crap. It worked fine on my T-Mo S4 (running a generic GPE edition). I'll probably have to sideload the app, but it's annoying that it's locked out.
Making progress.
I still couldn't download the ATT Visual Voicemail app from the Play Store, and went stir crazy trying to find it on my S4 (which is rooted, so I should be able to find it, but...). I went haring off in lots of directions, including making a full apps backup with Helium, but then the G3 won't restore without using the PC app due to changes in 5.0... which is weird because my S4 (which is running a 5.1.1 GPE ROM) restores fine. I don't have the PC app installed so I tried using Backup My Mobile... but then eventually figured out that on the S4, with ES File Explorer, I not only had Root Explorer OFF (didn't know I had to turn it on), but it's easy to find apps with the APP Library. Once I found the app there, I uploaded it to my Google Drive, then downloaded it from there onto the G3. It installed fine.
I used System App Remover (which requires root) to get rid of all the T-Mobile specific apps and that annoying Lookout security program. Bah! This cured that spurious text message I get with each boot. It was definitely due to the T-mo visual voice mail. Problem solved!
In using the phone, I'm a bit bummed because it didn't occur to me that a big part of my bigger screen as compared to the GS4 would be taken up by the softkeys on screen. The S4 has a physical home button and capacitive keys to either side. So, my screen isn't effectively much bigger, when I account for dedicating some of it to the buttons. You can make the buttons autohide, apparently. One issue is I use my phone in landscape much of the time, and the buttons don't rotate to the new "bottom" of the screen when I rotate. Gotta figure that out.
This morning I installed the PC Helium App so I could enable backup/restore access on the G3. That worked fine, but Helium on the G3 still doesn't detect my external SD card, in order to restore from it. I could manually copy files over to the internal Carbon folder, and restores from there worked fine. Still, I'm not sure why I'm having so much SD Card angst. I know things change each version of Android wrt SD cards... maybe something is fixed in 5.1.1 (as I had on my S4) that is broken in 5.01 on the G3.
So, I've got some tweaking to do from here. The phone is basically set up and working fine except for some straggler apps that I won't bother with until I need them, with one major exception: I need to go in and set up Light Flow. That app is a big part of how I manage notifications on any phone...
If you rooted your phone, then download and run the SDFix app from the Play Store. Apps will then have the ability to write to the external SD card...
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dsd+card+fix+kitkat&pcampaignid=APPU_1_bJMtVsTJBoKajwP4noeABw
... and yes, it also works w/ Lollipop.
redduc900 said:
If you rooted your phone, then download and run the SDFix app from the Play Store. Apps will then have the ability to write to the external SD card...
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dsd+card+fix+kitkat&pcampaignid=APPU_1_bJMtVsTJBoKajwP4noeABw
... and yes, it also works w/ Lollipop.
Click to expand...
Click to collapse
Thanks. I'll give this a whirl!
EDIT: WORKED LIKE A CHARM. Thanks again! And thanks for the link, because there were several SDFix apps. The link made sure I got the one you intended.:good:
OK, I'm in a pretty good place after making some changes. Still plenty to tweak though.
First, I decided to abandon the stock Home launcher. It was a bit annoying with little UI tweaks LG made that make it just not how I expect it to look, but the kicker was that in landscape mode, the titles of the icons were not readable... they were mostly cut off. I use Rotate (Ultimate Rotation) so pretty much every screen including home is rotatable. But LG Home maintains in landscape mode the little dots representing the various home screen pages... these take up just enough room so that things get squished a bit and the titles cut off. Couldn't figure out how to disable that, so just bailed and installed Google Now Launcher which fixed me right up. That fixed the look and feel of the home screen, the apps drawer, and even reverted settings to the normal views I'm used to.
The only problem is that it kills double tap to sleep... or at least reduces the footprint of the double-tappable area to the notification strip at the top. Sigh. In another thread someone mentioned using Greenify to fix it. I'll try that when I get a chance.
Another weird thing I've got going on is that when I connect via Bluetooth to my car, it starts playing music. See this thread. That's pretty annoying... for now I deleted the default music that was playing, and with an empty directory nothing plays.
I put on a screen protector last night. I got the 0.2mm iCarez one. I performed the application in a steamy bathroom after running the hot shower for a bit, per some tips over in the Accessories thread. I left the backing on, positioned the glass on the screen, taped one side for the "hinge method" after getting it perfectly aligned and accounting for the eventual loss of thickness of the plastic underbacking, cleaned everything one last time with the alcohol wipe, peeled the backing, and plopped it on starting in the center. Got it perfectly positioned and no major bubbles. There were a couple of "spec sized" non-uniformities but they were gone by morning.
I'm gradually setting in... Still lots to play with.
I've noticed the WIFI, while it gets good reception, is a bit sluggish to drop a weak connection in favor of a strong one. Anybody got a tweak for that?
Frankenscript said:
I've noticed the WIFI, while it gets good reception, is a bit sluggish to drop a weak connection in favor of a strong one. Anybody got a tweak for that?
Click to expand...
Click to collapse
Try this app for WIFI management. I have tried several and this is the best I have found. https://play.google.com/store/apps/details?id=org.kman.WifiManager I agree completely that the wifi in the phone is very slow to drop a weak signal and grab a stronger one. But with wifi manager you can play with the sensitivity. Good luck.
Will do. Thanks for confirming it's not just me. Also on another note I just found the LG keyboard has lots of settings for customization. Not bad. May keep it!
Sent from my LG-D851 using Tapatalk
I'm running stock AT&T 4.0.4 ROM, rooted with CWM. Google Play Services just updated to version 9.2.56 (034-124593566), and it's sucking my battery dry and making the phone run hot. I have a spare phone and brought it online, and the same thing happened as soon as Google Play Services updated. It is running anywhere from 50% to 80% of my battery when the screen is below 10%. Yep, it's using more than 10x what the screen requires. Battery that used to last 18 hours now lasts 2 to 3. Others have posted similar comments in the Play Store (like that's going to do any good). Common theme is it's older OSes.
I have tried disabling everything and it doesn't do any good. Too many things break if Google Play Services is removed. Going back to an old version is futile -- it self-updates within minutes. I tried GServiceFix and it works for few minutes, then the usage creeps up again.
I sent Google an email, but I expect nothing less than the run-around. So, I turn to XDA Developers.
First, is anyone else here still running stock, and did the same thing happen to you? How about on other ROMs (please specify)? Did you find a fix?
Assuming Google will do little to help, I need to do something to make my phone work right. So if there is a ROM where this is not a problem, I guess it's time to jump in. Problem is, some of the links in this forum are broken. I've found (or already had) most of what I think I need except a version or EFS Professional that works on our phone. I can find no working links to an older version that will do the job. I do have a Nandroid backup (also stored on my NAS), which I believe can restore the EFS, but I'd like to get just the EFS in case I need to load it to the system after flashing. None of the tools available in the Play Store seem to work on the Glide -- I end up with an empty backup directory.
My plan, assuming there is a Jellybean ROM without this issue, is to flash twrp-2.8.4-flashable.zip, since I understand TWRP is required for JB, then do another Nandroid backup with it, then flash whichever ROM is suggested to get over this. I've looked at Bubor's CM10.2, and it looks like it will fill my needs unless it also suffers this problem. If there is a reason I should update the Kernel, please let me know. I have not seen anything that makes me believe I need to.
Man, I wish one of the manufacturers would come out with a similarly sized new phone with a slide-out keyboard and AT&T compatible. I'd gladly upgrade, but there is nothing out there that meets my needs. Samsung S5 mini with slider -- I'm in.
Hi,
its one year later...
I'm with the same problem. Do you still have a solution?
Other ROMs have issues with camera and BT...
https://productforums.google.com/fo...rce=footer#!msg/play/uX3Xqk2gi_k/LurezyxjAgAJ