[Q] Some problems in XGin4.0 2.3.4 - XPERIA X8 General

Hi guys! I have to post in this general section just because I have not reached 10posts yet in "android development".
So I upgraded shpit's ROM from XGin3.0 to XGin4.0 just one hour ago, and i discovered two (maybe stupid) problems: i can't install Facebook and Applanet!
But system seems to work fine just for now.
Anyone can help me?
Thanks in advance.

achill3r said:
Hi guys! I have to post in this general section just because I have not reached 10posts yet in "android development".
So I upgraded shpit's ROM from XGin3.0 to XGin4.0 just one hour ago, and i discovered two (maybe stupid) problems: i can't install Facebook and Applanet!
But system seems to work fine just for now.
Anyone can help me?
Thanks in advance.
Click to expand...
Click to collapse
Reboot to xrecovery, clear cache and delvik cache..
then try to download again...

Working!
malungkot said:
Reboot to xrecovery, clear cache and delvik cache..
then try to download again...
Click to expand...
Click to collapse
Thank you man! I solved!

Hi, ive just installed Xging 4.0 and its great Rom but i have some problems, i hope you can help me to solve them:
- I cant get the Overclock: i put the X8oc.ko module into system/lib/modules and edit the permissions but nothing happens, after reboot i cant modify the Max or Min Cpu fercuency...
- I cant see the Mddi lag fix in system/lib/modules, thats not usefull in this rom??
ive been looking for this module because i have some lags in games.
thanks and sorry for my bad english.

leonardv128 said:
Hi, ive just installed Xging 4.0 and its great Rom but i have some problems, i hope you can help me to solve them:
- I cant get the Overclock: i put the X8oc.ko module into system/lib/modules and edit the permissions but nothing happens, after reboot i cant modify the Max or Min Cpu fercuency...
- I cant see the Mddi lag fix in system/lib/modules, thats not usefull in this rom??
ive been looking for this module because i have some lags in games.
thanks and sorry for my bad english.
Click to expand...
Click to collapse
first try this
reboot to xrecovery and flash xgin4
factory reset ( full wipe )
exit and with root explorer just and only copy X8oc.ko in system/modules
don't edit hw_config it's already configured
go to settings and and choose cyanogenmod settings
then go to performance and select cpu settings
there should be max and minimum set maximum speed on whatever works just don't try to get it too much high the higher freq won't always make the system better sometimes it won't even reboot and works fine but the speed isn't better than lower freq
u can use quadrant to find it out and check your cpu score when you increase freq your score should be higher if you noticed that it's not increased or it just got lower on score ! revert it back to lower freq and see if your phone works without reboots and hangs
and second
mddi module is preinstalled it is present on modules and yes it is not configured in hw_config but i believe it is loaded and the run command must be somewhere in firmware and maybe in lib files

dragunov_lq said:
first try this
reboot to xrecovery and flash xgin4
factory reset ( full wipe )
exit and with root explorer just and only copy X8oc.ko in system/modules
don't edit hw_config it's already configured
go to settings and and choose cyanogenmod settings
then go to performance and select cpu settings
there should be max and minimum set maximum speed on whatever works just don't try to get it too much high the higher freq won't always make the system better sometimes it won't even reboot and works fine but the speed isn't better than lower freq
u can use quadrant to find it out and check your cpu score when you increase freq your score should be higher if you noticed that it's not increased or it just got lower on score ! revert it back to lower freq and see if your phone works without reboots and hangs
and second
mddi module is preinstalled it is present on modules and yes it is not configured in hw_config but i believe it is loaded and the run command must be somewhere in firmware and maybe in lib files
Click to expand...
Click to collapse
Ok thanks ill try again.

Wipe partition cache and full wipe.
Sent from my X8 using XDA Premium App

Related

[Q] SetCPU on Tattoo

Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
eljanor said:
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Now I'll check your link, thanks.
EDIT: GREAT! IT WORK PERFECTLY! Now it's only find the way to run at boot a script for activating wifi, but I think it's easy, with or without a program.
Thanks a lot
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
x1l0n said:
How did you try to do it?
Anyway, there are a lot of ways to do it. Let's try first with adb (I'm writting this for a windows environment, because I'm too lazy to boot into linux, so sorry):
You plug in your tattoo through UsB on your PC. You start your command prompt and go to the folder where adb.exe is contained. The you write adb pull /etc/init.d/02squashsf c:\02squashsf <- this will save 02squashsf from your tattoo to your pc in the c:\ directory/partition. After that open the 02squashsf file with ... notepad/notepad++ and comment the line as described in my previous post. After you save the now modified 02squashsf file go to command prompt again and execute : adb push c:\02squashsf /etc/init.d/02squashsf <- this will copy 02squashsf from your c:\ to your tattoo. Pretty easy!
2nd Way:
Start RootExplorer on your tattoo and go to the folder /etc/init.d. Then click the small button in the upper right corner which says "Mount as R/W" (this will mount the system partition as Read/Write access). Find the 02squashsf file and long click it (until the menu pops up) and then choose edit as text file (or something similar). After it has been opened comment out the line as described in my previous post and save the file after the modification. That is all.
By the way, there is a 3rd way - unpacking the squash and editing its contents to be correct. But I don't really have the time...
And remember that a backup takes only a few minutes to make, but a mistake can cost you hours to fix if you have no backup
Click to expand...
Click to collapse
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
eljanor said:
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
Click to expand...
Click to collapse
Eheheheheeh I'm using a safe "fourth way", that I thought.
A normal way (not that 3) is typing these commands on Terminal Emulator directly from the phone.
Well, so why don't insert them into "Preferences -> Initial command" and give to Terminal Emulator the superuser authorization (with flag "Remember")?
Now, every boot, I simply open Terminal Emulator with a link on the desktop, waiting few seconds and it work!
Sometimes the default power widget doesn't work, so I must enter in Settings -> WiFi and turn it on. But it work without typing nothing more or modify a system file
Baboo85 said:
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Click to expand...
Click to collapse
Talking about voltages, are they controllable in some accessible way? I'd give it a go any time if I could find any useful information on the subject. Any help?
Baboo85 said:
Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
Click to expand...
Click to collapse
Just a question of confirming something.
With the new SPQRom 0.7 room we still have to flash a new kernel like eljanor user advised?
[Q] SetCPU on Tattoo
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/show...767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
Or it's this new room already is ready to be Over-clocked?
Thanks in advance
So, how far have you guys have went? I've read that for some of you, 710 MHz is the stable max, but for me, my tattoo seems to crash occasionally on that clock speed. My stable max is one step lower, 691 MHz.
bladez said:
My stable max is one step lower, 691 MHz.
Click to expand...
Click to collapse
I agree. Most stable and powerful is 691MHz. I have tested tatto by System Benchmark from market and its shows max results on 619MHz, next 710MHz are got worst resulsts in Cpu and Graphics tests. 691MHz optimal.
I also experimented with System Benchmark, and I got the best results on 730, though it did reboot occasionally.
my is 680

[Q] x8 does not overclock

Hi everybody...
I know I'm not a dev, but I like to explore my android phone. So you are developing, and right after i'll be trying to do it... on my own
I believe I followed all the steps refered in x8 overclock module thread in devs section, but since I can't ask this there, i'll ask it here.
1st - Download and unzip x8oc.zip (the right version), then copy x8oc.ko to system/lib/modules (I'm sure the file is there, system is mounted rw).
2nd - Edit hw_config.sh on pc with notepad++ (my edited file is attached) and "glue it" back to system/etc after editing.
3rd - Reboot... and then what?! It reboots, but when I go to set cpu, I have same frequencies as before (122-600mhz). So, my x8 is not overclocked right?!
Beside this steps do I need to do something else?! In set cpu, do I select any device configuration or just auto detect frequencies?!
Do I need to set custom frequencies in any other files?!
I've just tried lot's of changes and nothing worked.
Please help me on this...
I'm using floyo 0.15 on my x8, rooted and with xrecovery on it...
Thank you all
the attachment is correct..and don't change the set cpu. i use the same roms like yours
Do you think that having baseband version 006 instead of the 015 could be the cause for this problem? I never updated it...
Because, I've done it again without touching set cpu and still no overclock... If you say it's correct, then I really don't know what else could it be...
Thank anyway for the reply
I think it is very influential on baseband cuz for the rom said that use xx15,...if yours non xx15 so try to change it ...what you've applied on the hw_config is same on mine so it's quitely correct.
Hi mate
So, I'll tell you what i've done.
Went to SE's site and repaired to the original 2.1 so restarted the phone, updated to baseband 015, then root, then xrecovery... and then, installed miniCM. As you know, miniCM has an update.zip to easily overclock it to 710MHz.
I tried it and it worked fine. BUT! I prefer Floyo 0.15 (the best till the moment for me) and so I tried to do something, when I restored back to Floyo.
Adding the code to the original hw_config.sh in floyo's file didn't work again. So I thougt... Let's trie to put MiniCM's hw_config (the file that comes in the update.zip) to floyo's system. And... It's working FINE!!! I'm currently running at 749(x27)Mhz and it doesn't go off... it's stable. Also handles 767(x28)Mhz but it's not so stable. Now I'm really satisfied with my overclocked x8.
But there is one reason that made me think of where was the mistake.
When I opened floyo's original hw_config and added the code, in notepad++ it was apparently correct and the visual configuration of the file was equal to miniCM's hw_config file (already with the code). But, when I opened the both in wordpad, the file I edited had the same format as in notepad++ and the file from MiniCM had all together and a different layout. So I thought that it was possible that android wasn't reading the file well, since the configuration of the code was different. And it worked so smoothly
So my question is, does notepad++ write in the language needed for this to work?! or is there anything needed to change in order to make it legible to android system?
Thanks again
Sorry for all this noob questions, but since you use the same rom as mine, it's a good chance to ask what I don't know. lol
Our rom comes out with app2sd pre installed right?
So it was suposed that I could move some programs to sd.
But, when I go to settings/apps manager There's the option to move apps to sd, but they all say "fail moving the app".
What do I have to do to make it work well?! Heard that the sd had to be partitioned. What program did you use to do that?!
That's the only thing left to make x8 perfect and full of memory lol
Thanks
I managed to OC it manually to 710 MHz in miniCM6, BUT no performance increase was detected. Quadrant score was consistently lower (~750) compared to no overclock (~850),
Any ideas?
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
MaScXDA said:
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
Click to expand...
Click to collapse
and about battery life, noticed any difference after OverClock your Phone?
biscoitu said:
and about battery life, noticed any difference after OverClock your Phone?
Click to expand...
Click to collapse
it drains a bit faster with the PERFORMANCE-govenor, but my phone is loaded every night anyway.
It is even less important to me, because when it reacts faster, i don't need to have it turned on as long as when it is laggy. And the display really needs most of the battery-power, so i may even save battery, when i can turn it off earlier.
Return to 600mhz
I can not use the overclock because when I reboot the phone it is on 691Mhz soon after he returns to 600mhz. I know that the CPU clock is dynamic, but he never returns to 691mhz. What did I do wrong? I used the XDA tutorial for overclocking.
Don't work yet
I just try full wipe and did not work. I think it's some parameter or file permission...

GUIDE:improoving speed,and saving battery,overclocking guide,v6supercharger guide.

first what i do when i flash a new rom.
1. i install system app remover,and uninstall all apps i dont use.such as radio,DSPmanager,voice dialer,voice search,email apk.
2.for speed improovement:if you know and want to overclock your phone its ok.but dont expect your battery to last two days.it will last one day,maybie lower.it depends on wich frequency you set.i think 710Mhz is the best frequency.juwe's ram script is also good,but use v6 supercharger.it blasts.i dont use overclock,but still i get 1200+ quadrant points.
3.battery save:use program fast reboot from market.it frees ram,and kills background running apps.undervolt-lowering cpu frequency.your phones battery usage will be much lower,but expect some lag and your phone will be slower.but overall its not worth it.
battery calibration.you can do it manualy,but i use a program from market.its all explained there.use juice defender,it helps a little.
4.for those who dont know how to use supercharger script!
1,download this attachment from this post: http://forum.xda-developers.com/showthread.php?t=991276 (third attachment,its called like this txt V6_SuperCharger_for_Android-update8.sh.txt
2. put it on your sd card,and rename it to v6.sh
3.run terminal emulator,type su,then enter,and you will be prompted for superuser permission.click allow.
4.type in this command: sh sdcard/v6.sh
5.then its easy later,choose an option you want.
If you brick your device with it,its not my problem.if you dont feel safe,dont use it.i never encountered any problems.
OVERCLOCKING!
ok it seems like every starter vonders how its done.so lets start.
1.download the attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1020313&highlight=overclock+module the attacment is called x8oc-v004.zip
2.copy the x8oc.ko from your sd card to system/lib/modules using root explorer.
3.now go to system/etc folder,and find file that is called hw_config.sh,long touch on it,then choose an option "open in text editor".
4.now when you opened it,put in this line in top- insmod / system/lib/modules/x8oc.ko # x8 overclocking
5.save changes,and go to setcpu app and choose how much you want to overclock it.for me the best frequency is from 710Mhz to 787Mhz.but you can go higher.
Tell me if i forgot something,and most importantly,dont TROLL!I am only here to help.
so here it is in short.i hope i helped
Thanx alot mate for your effort, here's what I do :
1. Advanced Task Killer
2. Memory Manager
3. Battery Booster
That's it... and I've found 40% boost in battery timing...
Use app called fast reboot.because task killers spend more battery.
xperiauser132 said:
2.for speed improovement:if you know and want to overclock your phone its ok.but dont expect your battery to last two days.it will last one day,maybie lower.it depends on wich frequency you set.i think 710Mhz is the best frequency.juwe's ram script is also good,but use v6 supercharger.it blasts.i dont use overclock,but still i get 1200+ quadrant points.
Click to expand...
Click to collapse
how to use it on x8??
1. post updated,check it out.
ok , I unistalled all those three apps and trying fast reboot , will check if it improves battery or not, but it's causing 1 problem though , whenever I hit fast reboot I got a notification on status bar "Data traffic Disabled" and 1 Missed called...
while I've already cleared those two notifications by using that clear button on status bar...
I did disable data traffic intentionally !! why is that ?
p.s by celebrating battery you mean wipe battery status after a month ???
I never had that issue with fast reboot.and battery calibration is somethong like this: charge the battery to 100%,then use it untill the phone shuts down,and charge it to 100% again.its the manual way.but download the program from market called battery calibration,its easier.
I tried the Supercharger script a week ago on my FroyoBread and choosing option 4 (balanced) would just make launcherpro loop-crash when i booted the phone and then after a while just reboot itself and repeat.. It totally broke everything... How come?
Some options dont work good with x8.try using agressive 1 or agressive two.try to experiment with various options.it cant harm you.for me,the best is agressive 1,or megaram.
xperiauser132 said:
Some options dont work good with x8.try using agressive 1 or agressive two.try to experiment with various options.it cant harm you.for me,the best is agressive 1,or megaram.
Click to expand...
Click to collapse
Yes, it does harm me because when it ****s i cant use xrecovery or anything... I have to reroot and everything all over again.
Sorry man,i didnt know.it never happened to me,and i tried all options.
sorry bro,but i never had that problem.
and now i have exactly the same problem..i cant boot neither to ROM or xRecovery or CWM..what can i do now??
Flash it again with seus.
i actually did the thing, just some hours ago no issues, i chose multitasking.
seems to be pretty good!
And how exactly will i update with SEUS?..as i said earlier i cannot boot to rom..i had floyo 2.2.5 v1.0..and i can't load to xrecovery..and the phone must be connected first to pc companion to recognize the phone and fw version..to do that, the phone must be powered on and functual..hmm..is there any way to bypass that and go straight to flash an x8? i thought about using another x8 but i cannot find any
sokopa said:
And how exactly will i update with SEUS?..as i said earlier i cannot boot to rom..i had floyo 2.2.5 v1.0..and i can't load to xrecovery..and the phone must be connected first to pc companion to recognize the phone and fw version..to do that, the phone must be powered on and functual..hmm..is there any way to bypass that and go straight to flash an x8? i thought about using another x8 but i cannot find any
Click to expand...
Click to collapse
Assuming your phone is off, hold the back button and connect it to the PC via USB. The green LED should light up. PC should recognize it as flash mode or some such thing. When you run SEUS and it says connect your phone to the PC just do this and proceed with it. Then re root, xrecovery bla bla youre good to go
As for supercharger, for minfrees to stick you have to run the script everytime you reboot and the best setting for daily use is Balanced 3 (option 6) Ive pretty much tested all of them.
@xperiauser132 there is a instalation problem on supercharger
correct installation for supercharger:
1.use script manager Download:Here
2.Press menu --> more --> Advanced options --> config tick Browse as root
3.Run v6.sh from sdcard dont forget to check run as root
4.choose an option you want
5.select reboot (number 16 on supercharger option)
6.re-run the script (v6.sh)
7.again choose an option you want
8.Type exit (17)
9.go to /Data find 99supercharger.sh --> open as script Tick run as root and run at boot Save (for stock only (2.1) )
10. reboot
Well, I've tried this supercharger thing, and for me, at least, there was no improvement, if anything, the phone was slightly worse - with quadrant giving me an average of 34 points less compared to how my phone normally runs - using GingerDX v010 at 710Mhz on Smartass.
Maybe i'm doing it wrong?
Backed up phone now to pre-supercharger status.
Impster

[TELUS T959D Fascinate]-Running S.U.R.F.A.C.E ICS

First of all I would like to give credit where credit is due and say thank you to SamHaLeKe for all the work he put into this port and all the other Developers involved to bring ICS to the SGS
If you would like a full run down of this ROM and what is included as any new developments, please visit the ROM thread
Now off to the good bits ...
Install
I AM NOT RESPONSIBLE IF SOMETHING GOES WRONG AND YOUR PHONE CEASES TO WORK. THIS IS NOT A DETAILED WALK THROUGH BY ANY MEANS. I AM ASSUMING YOU READ ONE OF THE MANY OTHER TELUS THREADS THAT HAVE THE FULL INSTRUCTIONS INCLUDED TO PERFORM THE BELOW STEPS.
Note: I am not going to post all the links to files as I do not have the time to update them everyday when something changes. I will however post links to the ROM and Kernel threads for your reference.
I decided to start fresh (and I mean fresh) from stock FROYO with a full SD format and the works.
Step 1
Flashed back to stock with ODIN. Again I used FROYO but I am sure GB would work. If you want to start fresh as I did, go to options storage and format the internal SD (13 GB).
Step 2
Download the ROM and Glitch V13 kernel (what I used) and copy them to the SD card of the phone. I suggest removing any external SD as not to copy the files to the wrong spot (guess what I did LOL).
Step 3
Flash voodoo kernel from ODIN to root and install clockwork recovery making sure that you do not repartition in ODIN
Step 4 - Note: The older voodoo kernel gave an "assert failed" error trying to flash the ROM through recovery)
Boot into recovery and wipe cache and dalvik then flash the Glitch V13 kernel from zip and reboot. At this point you will most likely be boot looping but no worries everything is OK
Step 4
Pull the battery and then boot into recovery with volume up + volume down +power. Wipe cache and dalvik and flash the ROM from the ZIP
Let the ROM boot and then again boot to recovery and flash the essentials zip.
Voila you should be running S.U.R.F.A.C.E ICS, aint it beautiful?
I continued and flashed add on packs 1 and 2 but that is up to you
Now for my findings thus far ...
I am in no way a power user when it comes to my phone but I do play with it a lot. I have to say that this ROM seems to be the one of the smoothest to date and seems to take to our device nicely.
Battery has been nothing short of great for me. Through the week I can easily get 2 days out of it (work all day). Now I also try to minimize the drain by turning off whatever I don't need like WIFI seeing as there is none where I work.
I flashed the JL3 modem and it seems to work good for me but then I don't live where you do so you may have better luck with another.
The kernel included in the ROM (if you read the ROM post) is Glitch V14 pre which runs amazing as usual although still in the development stage. This kernel has a lot of new features that I will let you read up on yourself here
The ROM also includes supercharger and thunderbolt scripts (I admit I have little to no experience with these but I do know they help).
No FC's with this ROM other then the video camera but I have seen some posts regarding this and have not got around to working on it but will be I am sure very soon. It looks like just a file update maybe but too soon to tell.
Live overclock seems to work if I leave the voltage settings alone but that could just be a lack of experience in this area but it never hurts to try. If anyone has settings that are working for them I would love to know what they are. I have set the live overclock to 120% or 1.2ghz and it runs fine again if I do not change the voltage.
It's only been about 3 days since the install but this is what I got so far. I would recommend giving it a try for sure.
I know there are a few of us on this ROM so post up your findings here.
Thank you
Buck
Similar but running Glitch v14
Thanks for the write up Buck. I have been running this rom (Surface) for a few days also but I came from cm7 to this one. I have also been toying around with it over the last few days which has gotten me in a few tight spots lol. I have my Volt control set to 1304, no voltage changes and it runs flawlessly. The modem I put on was the JVT which also seems to work well.
What I have learn about Live OC:
First you set your clock speed in Volt control, then flip over to NStools (that is the easy part)
IMPORTANT.... If you choose to mess with this, make sure settings in NStools is NOT set to apply on boot or make sure you have a good recovery to go back to. Found this out the hard way
Click on live oc and you can make changes here... If you read the articale from Glitch on this it will help alot (found in the OP for T959D).
Live oc clocks up the cpu AND bus so it affects the gpu and memory along with the cpu (very important).
Findings... some settings work fine, 105, 106,110, 114, 116. 115 seems to have issues and provides lower performance considerably lower.
I use AnTuTu to check how things are working. That being said, if you apply set at boot and you hit a setting that first craps out the phone, causes a reboot then your going to be in a bootloop or it will start reboot start reboot. This is why you DON'T do this or like I said earlier have a good recovery handy.
Right now I am only running 1304 and 100% and everything is fine except the prior mentioned FC on video cam. Oh I should mention also I am running the Lazy governor atm which also seems to work fine (default is on demand).
Anyways
Well I think we may have broken the record for the longest 2 posts on the first page in xda history lol. Happy flash year everyone
Sent from my GT-I9000 using XDA App
Didn't notice you guys mention this, but Glitch V14 has an option in CWM to clear NSTools settings. It's right above the option to clear voltage settings under the Glitch Menu.
It works well, believe me!!
-Maniac
I'm on ICS!
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
baino said:
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
Click to expand...
Click to collapse
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
bucknetbucky said:
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
Click to expand...
Click to collapse
Hey Guys,
Why not just use rom toolbox? the build.prop tweaks give ya a niffty slider... no hackin involved...
Anyone got the files for stock GB?
cowvun said:
Anyone got the files for stock GB?
Click to expand...
Click to collapse
you looking for T959D?
Yes
Sent from my T959D on Darky's Rom 10.3.
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
baino said:
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
Click to expand...
Click to collapse
Nothing like that here maybe the way it was flashed I am not sure. Have you added anything?
Sent from my GT-I9000 using XDA App
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
baino said:
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
Click to expand...
Click to collapse
Depends what you did before flashing. I had issues after flashing a lot and never deleting anything lol
Sent from my GT-I9000 using XDA App
Working NSTools values for OC and UV
CPU:
Governor = Lazy
Min CPU = 100 (109 after live OC)
Max CPU = 1200 (1308 after live OC)
OC Value = 109%
Deep Idle = On
Custom Voltage
Arm:
1400 = unchanged
1304 = 1375
1200 = 1325
1000 = 1225
800 = 1150
400 = 975
200 = 875
100 = 875
Int Voltage
1400 = Unchanged
1304 = 1150
1200 = 1125
1000 = 1075
800 = 1050
400 = 1025
200 = 1025
100 = 925
Just set these values tonight and so far all is good and no crashes or reboots. See if it helps the battery as the days go by. Give it a shot or post your working values for others to try.
AND NO I NEVER SLEEP
bucknetbucky said:
Working NSTools values for OC and UV
Click to expand...
Click to collapse
Thanks for posting your OC and UV values. I'll give those a try.
I've been experiencing random crashes and reboots (woke up this morning to a dead phone). It was plugged in overnight but crashed at some point and did not charge. Battery voltage dropped down to almost nothing.
Anyone else experiencing random reboots?
I was using an OC value of 1304 (no live OC). UV values left stock. Ondemand governor, Deep idle ON, noop IO scheduler.
I did not format my sdcard prior to install. Just did a data wipe/factory reset, format cache and dalvik then installed according to the instructions. Installed Add-on Essentials and Add-on Pack One. All other apps were reinstalled from the market (after using market enabler and changing DPI back to 240 using ROM manager).
Everything works great except for the random crashes and reboots. I'll probably start from scratch again when v1.3 comes out (except I will format the SD card). Maybe even start from stock Froyo as recommended in the OP.
EDIT:
Tried the settings and my phone was not happy. It froze when setting the UV values. My phone seems to have a problem with any live OC value other than 100%. As soon as I increase it I lose all stability.
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Settings
I'm on Glitch v14 pre5 and I just clocked it up to 1300 and added 104% live OC for a stable 1352, no undervolting battery sitting @ 68% 1 day 22hrs. I did turn off some stuff I dont use and had data running on and off for the whole time.
For the guys that are having problems with flashes, I generally wipe everything I know its a pain but I don't experience any problems either. I also wait until i have a full battery too. It seems to pay off in the long run...
Happy Flashing!!!
Phone and contacts are working well now, but I can't get app data to save. For example some apps t's&c's keep asking for approval everytime I open the app. Also beautiful widgets skins keep reverting back to default. I'm going to wipe, format the SD card and install 1.3 from stock Froyo. here's hoping.
bucknetbucky said:
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just wiped and running 1.3 now. So far seems much better and faster than my last flash. You guys know of any way to change the haptic feedback intensity in ics?

Fix for Stock Kitkat aggressive app killing

Update: I found an even better solution. Instead of setting "dalvik.vm.heapsize=256m" use "dalvik.vm.heapsize=128m"
Warning! Please make a backup of your /system partition using recovery incase you get a bootloop from changing vm heapsize. Don't go below 128m as it may cause a bootloop.
If you want additional memory you can download "Ram Manager Free" from the Google playstore and set up a disk swap. Within the app, go to swap and delete the given directory and set it to "/cache and use a value of 256 MB. It won't steal from your already limited storage as it will use the cache partition which goes mainly unused. Warning though as it may degrade your internal storage from constant writing. If you ask me I don't care about degradation of my Moto G as I plan to get a better phone soon. I only recommend you use swap with the stock kernel as there is virtually no lag. I tested with other kernels and there is noticeable lag.... Aero Kernel lags noticeably and so does faux kernel. Oh! and make sure you set it to balanced and check the apply at boot option to stick. I stopped using swap, but you can try for yourself to see if you like it.
This is for the Moto G XT1034 as I don't know if the build.prop is different for the other variants, but you can always check if you have the duplicate entries.
While going through the build.prop of the stock 4.4.4 ROM I found duplicate entries of the same value with different parameters. The culprit being "dalvik.vm.heapsize" seemed to have been causing my music apps force closing when there was "insufficient" RAM. Other apps running in the background can also be killed like night screen filters while browsing the web using Chrome just to name another. You'll find two entries called "dalvik.vm.heapsize=36 and dalvik.vm.heapsize=256." They are the same value, but with different parameters. I deleted the one for "36m" and my multitasking issues disappeared without changing the MINFREE TASKKILLER values. I used Performance Control that can be found here on XDA to edit the build.prop. When you delete "dalvik.vm.heapsize=36m" make sure you re-add the value "dalvik.vm.heapsize=256m" because deleting one deletes BOTH! My screen filter app "EasyEyes" has yet to be killed by low memory situations.
Why would Motorola include duplicate entries of the heapsize? I'd like to be enlightened on why they included both.
NOW, your music app may be killed if you run very low on memory, this happens when you use chrome and view heavy pages, so modifying your MINFREE TASKKILLER values may be of additional assistance. I attached a screenshot of MINFREE values if you want to use my values, although I'm not using them since I'm using stock values. At the end of the day you have to understand that 1GB is now "low-end" and is simply not enough for multitasking anymore on Android. Apps are becoming larger and browsers and websites are becoming more complex; more RAM is needed. As soon as you open Chrome expect your apps to be killed since it needs at least 200 MB to run adequately.
Any reports of success with this? I just sold my Moto G last week because of the multi tasking issue... if this solves 90% of the problem, that would be pretty awesome.
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Jorge_007 said:
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Click to expand...
Click to collapse
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
NextGenGTR said:
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
Click to expand...
Click to collapse
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Jorge_007 said:
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Click to expand...
Click to collapse
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
NextGenGTR said:
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
Click to expand...
Click to collapse
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Jorge_007 said:
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Click to expand...
Click to collapse
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work!!!
Suprisingly enough that worked and nothing has been deleted and everything is how it is suppose to be! I have all my applications and my backgrounds and files intact!!! Add this in your tutorial if anyone faces the issue, flash the system files.
NextGenGTR said:
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work
Click to expand...
Click to collapse
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Jorge_007 said:
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Click to expand...
Click to collapse
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
NextGenGTR said:
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
Click to expand...
Click to collapse
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Jorge_007 said:
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Click to expand...
Click to collapse
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
Well you can install RAM Manager free from Playstore https://play.google.com/store/apps/details?id=com.smartprojects.RAMOptimizationFree&hl=en Go to "Extra" and select VM Heap Size it should read 128m. Also, listening to music should not be killed when multi-tasking. Apps such as iHeartRadio would always get killed when browsing the internet with Chrome. It doesn't happen anymore on my end. Also if you're not worried about your phones internal ssd from degrading you can set up a swap file to disk. Under Extra select swap file and delete the default directory and type "/cache" without quotes and set it to 256mb. It'll use the cache partition, so you'll still have your disk space for apps. It may degrade the life of your Moto G because of the constant writes, so it's up to you if you want to set up a swap. AND set it on Balanced on the main tab and check set on boot. Only do this on the stock kernel as I noticed lag on other kernels. Anyways you don't have to use swap or the ram manager app after your verify vm heap is 128m. I don't use it as just setting 128m vm heap no longer kills my music apps.
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Jorge_007 said:
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Click to expand...
Click to collapse
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
NextGenGTR said:
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
Click to expand...
Click to collapse
Okay, let me know how thing go
Jorge_007 said:
Okay, let me know how thing go
Click to expand...
Click to collapse
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
NextGenGTR said:
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
Click to expand...
Click to collapse
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Jorge_007 said:
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Click to expand...
Click to collapse
Currently with your settings + a build.prop code for the launcher to keep it in ram i am not experiencing any issues, also i have installed Rom toolbox pro which comes with build.prop editor and many other cool features, one being the minfree value changer, others have reported using the aggressive min free values from minfreemanager helps out so i am using that in romtoolbox and everything is in one single app so its nice and tidy, i recomend you give it a shot
Seems to work on lollipop as well!
Sent from my XT1032 using XDA Free mobile app

Categories

Resources