Hey guys,
I recently switched over from Slim Beans because my battery was getting too hot and it was killing my battery way too fast.
I just got the Nov. 1st nightly PAC ROM and everything seems fine except for two things..
One, I have a lot of empty space on my screen.. and I can't put apps or anything like that, it's just a big empty space and it bothers me a little bit.
The second problem is the front screen seems to be lagging? Whenever I exit out of an app, the screen is completely empty and after couple minutes all the things start showing up again. I know it's a nightly so there might be some minor problems and I heard that 10/21 is really stable, but it seems like the nightly ends at 10/25.
Should I go back to an older version of PAC ROM? I like it a lot so far and I would love to use it in the future if I can fix the problem
Thank you!
Related
Hey fellas,
So I have came upon the dreaded lag of death. I was opening up my messaging app and the phone froze and said "messaging has stopped". So I hit ok which should close the application, instead it sent me into a spiral of issues that amounted to "System Process Failure" which in turn forced the phone into a bootloop and now it has begun to stay at the HTC screen. I flashed the .312 radio a few weeks ago so I am thinking thats the underlying issue but I do not know. I am running the PAC rom safe version due to this same issue I had on kangdemnation v.5.
Appreciate the help in advanced fellas.
I don't have a fix, but here are a few notes. (currently using 320 radio and Evervolv rom, other roms may act differently but I've used Evervolv since it was available)
I always get Lag of Death within 24 hours after I overclock. I have gone weeks or months without any issues then I OC and I get Lag of Death
Whenever I get Lag of Death I reboot into recovery (4ext currently) make a nandroid Backup, SuperDuperWipe, then Restore the nandroid and everything works. Sometimes I will get Lag of Death one more time, but usually it works without a hitch.
I'm now on the 2/23 Evervolv Nightly and it works great and I will not be overclocking
I have no idea how to OC haha I just installed the PAC with aroma tweaks and thats the one I love to use but keep getting this damn issue.
Lol, that endless boot loop ended up killing my DInc2. Hopefully your phone doesn't end up like my DInc2.
Sent from my Xperia Z
I was running the SGH-i747M with CWM 6.0.4.7 and testing out some 4.4.2 ROMs, I got another phone to play with now and I gave this one to my girlfriend but she doesn't like nightlies so I was trying to install a 4.2.2 or 4.3.1 stable ROM and they won't work. I read online that it might be due to the CWM being too new because it's support is for Android 4.4.x. So I downgraded CWM and that didn't work either. I ended up convincing her that nightlies aren't that bad and shes currently running Carbon but she hates flashing the new nightlies so I do it for her every few days or so. I've noticed though that this phone is acting up really weird since I tried to downgrade CWM and then install the current one again. Sometimes it reboots at random, I gave the phone to her with BAM 2.0 RC2 (I know, shame on me), and that was horrid, so I tried CyanogenMod and that was "okay" but she said it's boring and she wants more features, so I switched it to Carbon because that's what I'm running on my SGH-i317M and she seems to like that, but it's still acting really weird.
When I was using the SGH-i747M while I was waiting for the new display to come in the mail for my SGH-i317M, I was running BAM and the only thing was it was a battery hog, and ocasionally I would get a "blame tyler" error for some things but it was never repeatable, I switched to Carbon and I was running completely stable on the nightlies, I used it for my day to day and not one problem, after switching over to my SGH-i317M now running CarbonROM, still flawless, not a single problem, fast, good battery life, signal strength is always good, but the phone I was on, running the same ROM, is now glitchy as hell and she's talking about getting an iPhone 5S now.. guys you gotta help me here, I just got her to give up her iPhone 4 for this S3 I gave her, I need this phone working, it is a critical situation lol.
The camera app will take one picture, then the screen will freeze and when I close the app, it opens right back up with the same picture, when I completely close the app, it opens up saying can not conect to camera and the only solution is to reboot the phone. It randomly reboots on it's own some times, the battery doesn't last more then a few hours (between 2 to 3 hours depending on use and when I was using it on Carbon, I got 30 hours off of a single charge once, but the average was around 20 hours of use before it would die) and she was telling me while she's on high brightness but never full brightness, the phone gets really hot so there's something wrong from when I flashed an old CWM using Odin, and then flashed it back to the current one.
So how can I do some kind of full wipe everything and make everything better procedure? Does this exist yet? Is it a real thing?
I'm thinking some kind of recovery wipe, completely wipe everything except the boot loader so I can install a fresh copy of CWM using Odin, and then some kind of AOSP ROM that's stable but I think she likes Carbon now so we might just stick with the nightlies as long as these random force closes and random reboots stop, and the camera works, I mean, you can't instagram without a camera, so that makes this phone nearly useless for her. One picture, freezes, reboot the phone, opens picture from gallery, then hipsters it out, then shares it.. not exactly the seamless method she was looking for lol
Please help guys, I really don't want to see another iPhone laying around the house.. ugh..
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?
Is anyone besides me still using this phone? I'm impatiently waiting for a 2015 Nexus or carrier neutral/Project Fi capable Motorola.
For the most part my phone works fine and does what I need it to do. I've been running v11 M12 since its release without any serious issues EXCEPT...
Lately I've noticed after a few days the phone will slow to a crawl. I'll open Running Apps and see a bunch of apps restarting at one time. Only a reboot will resolve the issue. I'm not running any obscure or obviously misbehaving apps and everything works fine for a few days. It doesn't appear to be 4G/WiMax related (turning it off doesn't resolve the issue).
I flashed the last milestone build, XNG3CAO1L7, without a factory reset and it seemed really buggy right away. I'm trying the latest NIGHTLY right now and it also seems a little buggy. I'd rather not factory reset, but I will if that is what it takes to resolve my issue.
Just curious about the status of anyone else running these builds. Thanks!
Nexus 7 keyboard and on-screen buttons not working
Hey guy, since quite a while, my nexus 7 has been randomly giving me this problem, which only got worse with time. Every now and then the keyboard would refuse to show up when I tap on a textbox. When this happens, my back button would also stop working. Also, YouTube videos would go all black (no video) while the audio continues to play and/or the on-screen controls would refuse to hide after a while.
I googled a bit and found out that greenify and xposed are causing this problem but in my case even getting rid of them didn't solve the problem. I even uninstalled every new àpp, reverted every new changes but no luck.
I'm really getting sick of this problem and this is the last time I'm seeking for any help before I go ahead and format my device. I'm a bit techie (the reason why I don't wanna go the format way) but this one's really gotten to my nerves.
I'm on KitKat 4.4.4 using Pacman Rom (KK RC-3 dev) with the kernel ElementalX v3.4.0.
I've frozen literally every app I could blame for this issue.
Please help me out guys!!!
No one??? Not even a guess??? Come on guys, pleeaaasssseeeee!!!!!