Hi,
I have a LG G2 32 GB running CloudyFlex 2.2 with Stock Kernel. I have tried normal apk with data from play store, modded apk and everything but still the games crashes at the launching screen. Please tell how to fix it.
reinstall, clear some stuff from memory, then in settings of game set details to low and something to fixed. that should enhance loading and speed.
It will bring gameplay also on par with asphalt 7, which I prefer actually over all the flashy new stuff lol.
It works pretty good on mahdi, in kernel settings with memory on minimal and read ahead value on 1024, all levels load without crashing and no more crashing on loadup on d802
Af8,af7 not running on oppo find7a, too.
«devteam.vn®-devos™»
Related
This is my 2nd n7 "wifi model" Despite trying different roms and kernels i get lag, bad battery life and weird rendering, especially on websites. I usualy do not overclock and i use stock voltage. Right now im running carbonrom + the dmore kernel. Its weird becuase carbon runs flawless on my note 2.
Any suggestions?
fix-this! said:
This is my 2nd n7 "wifi model" Despite trying different roms and kernels i get lag, bad battery life and weird rendering, especially on websites. I usualy do not overclock and i use stock voltage. Right now im running carbonrom + the dmore kernel. Its weird becuase carbon runs flawless on my note 2.
Any suggestions?
Click to expand...
Click to collapse
I'm not sure how to advise somebody with over 1400 posts to their name... but here goes... I suggest you boot into recovery and clear CACHE and DALVIK... and reboot.
(I use TWRP... but I assume there would be similar options in CWM)...
This clears a lot of crap out... and upon reboot you should see the following message (after the boot animation)...
'Android is upgrading... optimising app 69 of 209'... and so on and so forth, until DALVIK is rebuilt again.
I have experienced some speed gains by doing this intermittently.
-------
You should also check out this app...
LagFix (fstrim) - http://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en
This helps a lot.
-------
With regard to battery life...
Turn OFF everything you don't use... Google enables a lot of stuff by default.
So, in...
SETTINGS>>WIRELESS & NETWORKS>>WIFI>(Menu)>>KEEP WIFI ON DURING SLEEP... set to NEVER.
SETTINGS>>WIRELESS & NETWORKS>>BLUETOOTH... disable.
SETTINGS>>WIRELESS & NETWORKS>>More... disable NFC.
SETTINGS>>DISPLAY... disable auto-brightness, and manually set your own level.
SETTINGS>>DISPLAY... set SLEEP to as short a time as tolerable.
SETTINGS>>BACKUP & RESET... disable 'Backup my Data' to Google servers, if you have backups elsewhere.
SETTINGS>>ACCOUNTS>>Your Google Account...disable auto synchronization of anything you don't use.
So any these these...
CALENDER, CHROME, CONTACTS, GMAIL, GOOGLE CURRENTS, GOOGLE PHOTOS, GOOGLE PLAY BOOKS, GOOGLE PLAY MAGAZINES, GOOGLE PLAY MOVIES, GOOGLE PLAY MUSIC - they're all enabled by default!
-------
Beyond these tips, and my own custom ROM/KERNEL recommendation (see SIG), I can only add that I have never experienced any serious lag on my Nexus 7... even with factory stock.
-------
I tend to get around 7 hours screen time over two days.... from one charge... which I don't think is that bad really.
Hope this helps....
Rgrds,
Ged.
More detail would help a lot.
Does it lag after a clean install before losing any apps
Are you restoring apps - if so how
How are you flashing (wipes, etc)
Does it lag on stock
What launcher are you using
Is there an app in particular that lags
And anything else that might be helpful
Current: Note 2 - Nexus 7 - Charge
Retired: Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
Hi all,
I guess ever since getting the Nexus 7 when it came out, I've been trying to reduce lag. It has become as sort of project of mine. The last year, I have gone over lots of ROMs, kernels, tweaking tools, and tried lots of good (and very much bad) stuff.
So far, I've come quite far and I am quite happy with the way my Nexus 7 runs. The Nexus runs great in all other apps, really. Browsing is smooth and not comparable in any way to what I started out with. I have some Danish, poorly designed sites that are quite heavy, and I get no lag.
Apart from one thing - i get BAD lag when scrolling down a list which has images in it. I also get minor lag at other lists, but images makes it horrible. My two best examples are the play store (almost unusable) and gReader (slightly better with images off in lists, but hey, shouldn't have to be like that).
I've been googling loads and it seems very few people have the same problem? I've had this problem with all kinds of ROMs, kernels, tweaks, whatever really. I can have a crap setup with a million services running and a google now process gone haywire with cpu at 75 degrees celsius, yet the stutter is just the same in play store and greader (e.g.).
My current setup (but note, I've tried many with same result):
- Completely fresh install of recent CM10.1 nightly
- franco kernel (1.7GHz CPU, 700MHz GPU, 512Kb read-ahead, interactive, deadline, fsync off, gpu scaling off, wifi performance streaming)
- Almost all services disabled, including most of google's, meaning I have greenify running, a few under google services and android keyboard
- Sync is currently off
- Currents is not installed
- I've got fstrim installed and run that recently on all partitions
- I've got 9GB of 13-ish free at the moment
- Location sharing off
- Accessibility off
- No widgets, completely empty homescreen (I use Apex, not locked in memory)
I've been testing on a 100/100Mbit line fiber and 60/15Mbit LTE and identical experience.
I DO have Xposed installed atm, but after this fresh install (and many other similar times), I go straight to play store on a fresh install before installing anything. Same problem always there.
I had been using Trinity kernel for quite some time, at the time I adjusted read-ahead a lot, but in this situation a standard read-ahead actually means less lag for me. I guess it means more, small lags, actually, less noticeable.
I've been testing Seeder and similar apps recently, but get no particular difference with this problem.
When using the older version of Google Play, it is much more smooth, yet in the lists with apps it still stutters. Like 2-3 stutters a second, at times it hangs for a whole second, when scrolling down. It stutters each time and image is placed.
My experience: It seems the act of scrolling AND loading images doesn't work well in parallel.
I really hope someone can help me understand the problem, or, if so lucky, help me eradicate (or at least) reduce it.
Mkay, so it seems I am in a situation, where lagfix etc. doesn't alleviate the problem with very low random write speeds. I have done Forever Gone and various other things, but it just doesn't help. So, after googling a lot again, with inconclusive results:
What the feck is the conclusion on those low read speeds? I have plenty of space free...
delanvital said:
the play store (almost unusable)
Click to expand...
Click to collapse
The Play Store has always stuttered horribly when scrolling, as does Play Music. From my own observations, this is an issue with the implementation of rendering in these applications, rather than a lack of system performance. It is not isolated to the Nexus 7 either; it occurs within these applications on every Android device.
When you load the Play Store (or Play Music with album art) and begin to scroll, images are loaded when they come into view and unloaded once you move past them. I would surmise that the behaviour is intended to conserve RAM on less capable devices, however the consequence appears to be that this constant loading and unloading of images while scrolling results in stuttering. I have tested this hypothesis by comparing image-based applications (such as HTC Music) which do not implement the aforementioned function against those that do. The result is always that the former are completely smooth, while latter stutter incessantly.
Now that most new Android devices are shipping with 2GB of RAM, I do hope that Google will either remove this function or disable it on current devices (based on the brand/model the device identifies as).
So here's the rundown...
Need for Speed Most Wanted is amazing on this phone! I love how much smoother it is compared to my good 'ol GNex. Been running Eclipse V5 since I got the phone and all has been well.
Then I saw it...
ROOTBOX PORTED TO RAZR M!!!
Absolutely had to have it as it was by far the best ROM on my GNex. And it is on here too. Buttery smooth, fast as all hell and oh so stable.
So I go about reinstalling all my apps from Titanium Backup, made sure to save everything from my Android/data and mucked around a bit gettingmy Moga Pro to work with CoD: BOZ. After 23 beautiful rounds i decided to give it a go with NFS. I set up all my touch placements in game keyboard, booted my game aaaaaannnnndddddd...
Black textures as soon as I went to select my car. No textures whatsoever in race.
OK so I wipe my phone and go back to Eclipse
Black textures
Deleted the game files, restored an OLDER backup from my PC of NFS, before I ever made a TB of it (which is how it initially worked) reinstalled the app directly from the Play Store
Black textures
Deleted EVERYTHING, wiped out the entire phone, restored to bone stock 4.1.2 with RAZR M Utility, downloaded from Google Play, let it download the additional 560 Mbs of data so I was sure it was all fresh
Black &$+&;%($;$-$($73*%*$73-3-$84;48%;%-393/%-%8$; <----frustrated finger rage
What the balls happened after I installed Rootbox?!?!?!
dragonhart6505 said:
So here's the rundown...
Need for Speed Most Wanted is amazing on this phone! I love how much smoother it is compared to my good 'ol GNex. Been running Eclipse V5 since I got the phone and all has been well.
Then I saw it...
ROOTBOX PORTED TO RAZR M!!!
Absolutely had to have it as it was by far the best ROM on my GNex. And it is on here too. Buttery smooth, fast as all hell and oh so stable.
So I go about reinstalling all my apps from Titanium Backup, made sure to save everything from my Android/data and mucked around a bit gettingmy Moga Pro to work with CoD: BOZ. After 23 beautiful rounds i decided to give it a go with NFS. I set up all my touch placements in game keyboard, booted my game aaaaaannnnndddddd...
Black textures as soon as I went to select my car. No textures whatsoever in race.
OK so I wipe my phone and go back to Eclipse
Black textures
Deleted the game files, restored an OLDER backup from my PC of NFS, before I ever made a TB of it (which is how it initially worked) reinstalled the app directly from the Play Store
Black textures
Deleted EVERYTHING, wiped out the entire phone, restored to bone stock 4.1.2 with RAZR M Utility, downloaded from Google Play, let it download the additional 560 Mbs of data so I was sure it was all fresh
Black &$+&;%($;$-$($73*%*$73-3-$84;48%;%-393/%-%8$; <----frustrated finger rage
What the balls happened after I installed Rootbox?!?!?!
Click to expand...
Click to collapse
shot in the dark here, but have to tried adjusting your display settings, and seeing the developer options? perhaps overclocking?
Hi All
I have an SM-N900 (exynos variant) running 4.4.2 XXUDNB2.
I am usually never bothered about the RAM usage even if it shows very high value regularly. While typing this msg I checked and it was 2.37 out of 2.66. I trust android itself to do the necessary memory management !!!
What I have been seeing recently is this :
Dolphin is trying to load a page... maybe lots of pic nd all.... while doing this if I try to bring down the notification bar, ir does come down but gets stuck on the way.... similarly if I try to scroll the page it gets stuck while doing it.... essentially it is not at all smooth...
Now, if I just launch the task manager, clear some memory and retry, everything works smoothly...
The Note 3 is supposed to be a beast.... when the beast stutters in front of my friends its rather annoying/embarrassing at times !!!
Anyone seeing something similar ?
stanzlavos said:
Hi All
I have an SM-N900 (exynos variant) running 4.4.2 XXUDNB2.
I am usually never bothered about the RAM usage even if it shows very high value regularly. While typing this msg I checked and it was 2.37 out of 2.66. I trust android itself to do the necessary memory management !!!
What I have been seeing recently is this :
Dolphin is trying to load a page... maybe lots of pic nd all.... while doing this if I try to bring down the notification bar, ir does come down but gets stuck on the way.... similarly if I try to scroll the page it gets stuck while doing it.... essentially it is not at all smooth...
Now, if I just launch the task manager, clear some memory and retry, everything works smoothly...
The Note 3 is supposed to be a beast.... when the beast stutters in front of my friends its rather annoying/embarrassing at times !!!
Anyone seeing something similar ?
Click to expand...
Click to collapse
Well just remeber that your phone its like a pc, if your running several apps on the background the system will run of memory for other apps, its try android manage memory and all but if it doesnt have free memory to load up an app, it will close some to free ram and that will cause lag on the phone, my recomendation is to look on the running apps tab and check witch apps at runing and close/froze the ones that u dont use to clear up some ram, im usually at 600 free ram all the time, if i clear ram i get almost 1gb free. so you should check what apps are messing with you.
Dear XDA,
So I have a rooted Nexus 7 (2012) with the latest TWRP running an android 6.0.1 ASOP rom. I have a Nova launcher running with only 2 widgets (one kwgt and one zooper). So it lags at the lock screen, in chrome and facebook. Other apps run fine as long as there is no lag. I have a governor set to interactive. Emulators and games work, gnuroot debian (i.e. linux) works. Most benchmarks accept Pcmark work. So is it the hardware or can I do something to fix it? Clearing cache used to work but not any more.
Only using 12/32 GB on flash memory.
Any suggestions?
EternalSeekerX said:
Dear XDA,
So I have a rooted Nexus 7 (2012) with the latest TWRP running an android 6.0.1 ASOP rom. I have a Nova launcher running with only 2 widgets (one kwgt and one zooper). So it lags at the lock screen, in chrome and facebook. Other apps run fine as long as there is no lag. I have a governor set to interactive. Emulators and games work, gnuroot debian (i.e. linux) works. Most benchmarks accept Pcmark work. So is it the hardware or can I do something to fix it? Clearing cache used to work but not any more.
Only using 12/32 GB on flash memory.
Any suggestions?
Click to expand...
Click to collapse
Yes, you can try to flash Parrotmod:
http://forum.xda-developers.com/showthread.php?t=3300416
Sent from my Nexus 7 using Tapatalk
Honestly facebook and chrome are a problem for older hardware. Suggest you go with Facebook Lite and Firefox instead. Uninstall Facebook and Chrome.
Sent from my LGLS991 using Tapatalk
I read somewhere else that eventually, as it gets older, and you write to the memory more and more, it decreases the efficiency of the memory. It's usually a sign of wear and tear on the device. I know mine got REAL laggy to the point it freezes up on me after using it for awhile, usually with very intensive games such as Game of War, Walking Dead No Man's Land, etc.
Some have stated, if you're rooted, to use LagFix from Google play to run TRIM (you must be rooted for this). If you are not rooted, you can use Forever Gone as an alternative. I haven't tried these on my N7 (don't use it anymore), but the premise is they fill up your storage with empty files and then removes them, which causes Android to execute the TRIM command against your storage. This is supposed to help with the slow down many see after a few years of use.
In the end though, eventually the writeable memory just wears down. It's like external SD cards that, after so many writes, start to exhibit errors in various sectors. The writeable memory is just not immortal. We haven't found the right technology for that apparently. Just like a hard drive goes bad after so much write and rewrite, so goes the writeable firmware memory in mobile devices and SD cards.