Related
I just finished flashing IHOP_BELL then OrangeFR 2.3.4 w/ ram fix and also the Bell GB radio onto my Bell Atrix. I then used Titanium Backup to restore my settings/apps. I now get a mysterious program simply called "X" in my battery usage which is eating up my battery, mainly when the screen is turned on. I left my phone on over night on battery power and X didn't significantly affect it then. I've tried searching the forums and on google but it's hard searching for a single letter problem even with additional search terms. I've attached screenshots of battery usage showing the app in question. I could try flashing something else and hope that solves the problem but I'd prefer to fix the problem directly.
Anthrox- said:
I just finished flashing IHOP_BELL then OrangeFR 2.3.4 w/ ram fix and also the Bell GB radio onto my Bell Atrix. I then used Titanium Backup to restore my settings/apps. I now get a mysterious program simply called "X" in my battery usage which is eating up my battery, mainly when the screen is turned on. I left my phone on over night on battery power and X didn't significantly affect it then. I've tried searching the forums and on google but it's hard searching for a single letter problem even with additional search terms. I've attached screenshots of battery usage showing the app in question. I could try flashing something else and hope that solves the problem but I'd prefer to fix the problem directly.
Click to expand...
Click to collapse
Htf did you get that..?
Try: System Panel and/or Watchdog, both from the Market or http://forum.xda-developers.com/show...php?p=15869868 Between the three of them you should be able to figure something out, hopefully.
Realized I could search for the process with Terminal Emulator. Shows up as /usr/bin/X which lead me to this: http://forum.xda-developers.com/showthread.php?t=1171020 too bad there's no response. I can't seem to kill the process either even with root.
I froze everything I could related to webtop but it's still running on boot and can't be killed. It may also help to know that I came from greyblur framework since I batch restored my apps and data. I did the same thing the other guy did and moved X for now but that's not really the root of the problem.
My market also doesn't download/install properly now apparently. I'm just going to clear my data.
Edit:
I've found the offending code in init.rc but even if I mount it as rw, when I restart my phone the code is back to normal. I'm also not 100% sure of the best way to edit this so I can still load webtop if that's what I'm actually doing (though I probably won't ever).
Code:
# OSH properties
setprop sys.SystemMode RM_SM_MOBILE
setprop sys.FbOwner 3
setprop sys.DispOwnerLcd 3
setprop sys.DispOwnerHdmi 1
setprop sys.AiwFocus 3
setprop sys.AMActiveTask 2
# Mount OSH
exec /system/bin/mountosh -d /dev/block/mmcblk0p13
and later in the file
Code:
#OSH Startup
service slrestart /usr/local/bin/start_syslog.sh
class pre-zygote_services
oneshot
disabled
on property:ro.build.type=userdebug
start slrestart
on property:ro.build.type=eng
start slrestart
service fbcp /etc/init.d/start_fbcp.sh
class pre-zygote_services
user mot_osh
group mot_osh
oneshot
on property:dev.bootcomplete=1
setprop ro.webtop.boot 1
start loadpreinstalls
on property:ro.webtop.boot=1
exec /system/bin/logwrapper /ubuntu.sh
on property:sys.SystemMode=RM_SM_DOCKED
exec /osh/etc/init.d/startX.sh
I don't know why the startX.sh would run though since it has a different value, and I've double checked via adb after boot.
I have the same problem and I hope there is a solution!
You can see that /usr/bin/x uses 50% CPU (100% of one core) all the time with "top"!
I had the exact same issue on OrangeFR as well as Ninja. I SBFed back to 2.2.2 (where there was no problem) and back to OrangeFR only to see X resume eating half my CPU.
Strangely, the moment I installed kennethpenn's Beta 4.5, the problem disappeared. Since then I've wiped and installed Ninja once more and things have been fine. My CPU usage is normal again and I don't see X listed at all. I have no idea how it got fixed. Doesn't make much sense at all.
kennethpen said it must have something to do with a broken Webtop but I don't know how to fix that.
Any help?
From my experience, and the experience of another person posting in the Dev forum, you'll need to install an updated webtop. The one in kennethpenn's Beta 4.5 rom worked for the two of us. You can't get it on Xda anymore, but it's still on his briefmobile site. There's also a thread in the Xda dev forum for an updated webtop. I haven't tried that one but it could be worth a go.
I had terrible battery life, before, but I do not recall having an X under battery usage. Then I installed 2.3.4 from Samcripps Fruitcakes.
Specifically 234-sb-release.zip,(system and boot) and then 234-w-release.zip(webtop)
After that I flashed latest GB bellradio from Samcripp, and then INTL-MBR-1100-GB-Kernel-0.1.2-ext4-sv.zip
I just put [ROM] R-9 2.3.4GB [Base 4.5.91] with EXTRAS! *V5* on, after that I reflashed latest GB bellradio from Samcripp, and then INTL-MBR-1100-GB-Kernel-0.1.2-ext4-sv.zip
Everything seems to be working great.
Starts fast, shuts down fast, everything loads fast, 3g is fast, wifi is fast,
no issues yet. Hopefully this can help someone else get their phone running better.
AND it has D3 camera!
frelnik said:
From my experience, and the experience of another person posting in the Dev forum, you'll need to install an updated webtop. The one in kennethpenn's Beta 4.5 rom worked for the two of us. You can't get it on Xda anymore, but it's still on his briefmobile site. There's also a thread in the Xda dev forum for an updated webtop. I haven't tried that one but it could be worth a go.
Click to expand...
Click to collapse
Do you have a link for that? I don't want to flash a whole new system...
MaluNoPeleke said:
Do you have a link for that? I don't want to flash a whole new system...
Click to expand...
Click to collapse
A poster above seemed to have luck with Samcripp's webtop in his Fruitcake thread here:
http://forum.xda-developers.com/showthread.php?t=1163009
There's another webtop CWM download here:
http://forum.xda-developers.com/showthread.php?t=1169457
I can't speak to whether either of those solve the X problem, but it's worth a try.
frelnik said:
A poster above seemed to have luck with Samcripp's webtop in his Fruitcake thread here:
http://forum.xda-developers.com/showthread.php?t=1163009
There's another webtop CWM download here:
http://forum.xda-developers.com/showthread.php?t=1169457
I can't speak to whether either of those solve the X problem, but it's worth a try.
Click to expand...
Click to collapse
Thanks a lot, the first link worked!
MaluNoPeleke said:
kennethpen said it must have something to do with a broken Webtop but I don't know how to fix that.
Any help?
Click to expand...
Click to collapse
on the page at briefmobile.com/alien the newest webtop is available for download. Flash it and maybe it will fix the issue.
Cobbled together fix
Try downloading the webtop update from:
briefmobile.com/alien
If that doesnt help and you don't mind losing webtop access, rename the "/osh/ubuntu.sh" file to "/osh/ubuntu.sh.bak" and essentially cripple webtop and prevent if from starting.
Worked for me.
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
Hello,
I installed the new 3.3.4 rom and I wanted to install the v6 SuperCharger and after following all the steps and rebooting I go into the script and it says that its weak, and that values dont match supercharge.
The only thing that i did not see on the instructions nor remember how to do is activate a script and set it to run at boot.
Anyone running the script on the new rom, please help me a little bit.
Electroniko said:
Hello,
I installed the new 3.3.4 rom and I wanted to install the v6 SuperCharger and after following all the steps and rebooting I go into the script and it says that its weak, and that values dont match supercharge.
The only thing that i did not see on the instructions nor remember how to do is activate a script and set it to run at boot.
Anyone running the script on the new rom, please help me a little bit.
Click to expand...
Click to collapse
is the script that runs on boot running on boot?
It does not seem like it is.
First make sure you have buisybox 1.18 or lower installed. Second load up script manager and and at the top hit "..." twice. Then hit menu and options and choose browse as root. Then select the data folder then choose 99supercharger. Check run as root and run at boot. For dx2 at least running eclipse 0.2.2 option 9 in supercharger runs it the best. Option 9 should be megaram with 512mb. There are two it should be the second one. Im running update 8 so im not sure which option it is anymore.
Also you mean you are running the ATRIX 2.3.4 right? If so has the audio problem been solved with that? That's the main thing I want to know with that rom since it has android 2.3.4 on it.
Sent from my DROID X2 using XDA App
well im not sure what you are running but make sure that either /system/etc/init.d is being run on boot
I followed the directions, but when I go into data there is no file 99etc... to run at boot.
Did you first run supercharger. Run it but don't reboot the x2. And make sure you are browsing as root. You choose that in the options of script manager. Also are you running buisy box with 1.18?
Sent from my DROID X2 using XDA App
running busybox 1.18.1
Tried it like four times, and no go.
do you have root?
Are you using script manager? Cause that just odd. Just to be sure you're going to "/data" as browsing as root in script manager and scrolling down to the end of that file and not choosing the other data folder to make it "/data/data" cause it should be there as long as you first ran v6 supercharger and chosen which ever option that 99supercharger script should have been made.
I say unsupercharge. Delete scriptmanager and reinstall it and then try again just to see id there was a glitch. If this doesn't help then your pretty much out of luck. But I thought navens. Mods where included in the rom so you shouldn't need it(could be wrong).
Sent from my DROID X2 using XDA App
Its weird because I had been able to run supercharger on eclipse, I will keep diging around to see what I can find.
Just a question... Isn't supercharger unnecessary for 2.3.3 and above?
Sent from my Droid X² Eclipse Rom + BNB Theme
I have the same problem, and no its not the users. I don't think it is working correctly. Or at least not placing the files where they are normally found.
if you run the 99supercharger script that is suppose to run at boot as root then rerun the "installer" script are the mem splits correct?
Versatile1 said:
Just a question... Isn't supercharger unnecessary for 2.3.3 and above?
Sent from my Droid X² Eclipse Rom + BNB Theme
Click to expand...
Click to collapse
its quite usefull just not so much for music on stock gb blur. it gives you a faster boot and screen transission but thats about it on blur.
on elcipse 0.2.2 if you use v6 supercharger (update8 option 9), 98kickasskernal safe and v6noop nearly got rid of all the music skips and pops. about three songs per 85 on my playlist skips or pops if im not doing anything other then listen to music and it will only skip once if its the first time i opened the internet and then runs fine. but the 3 songs are complete random. and sometimes it goes to 5 songs.
without them running this phone skips, pops on nearly every single song on my 85 song playlist (i have 2 gb of music on my phone this is just my most used playlist).
so it makes a difference just not much on blur as it does on eclipse.
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
dvigue said:
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
There is a huge debate about this, but if you are not ready for a new Kernel, you can try an app call Autokiller Memory Optimizer and set it to the Optimum setting.
This will kill apps that are eating up your RAM and over time can slow your phone. This is one simple and quick solution.
This app adjust the memory killer that is already used by the phone. This just helps it to work more efficiently.
dvigue said:
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
Join the club; I just did the same thing
Has anyone seen John Connor?
moved
sageDieu said:
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my Fascinate was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Relaxasaurus said:
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my device was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Click to expand...
Click to collapse
oh trust me i want to be on CM7 or MIUI, but i CANNOT get around the SD mount error. i have another thread about it. i have tried everything and nothing works. i was thinking of ordering a smaller 8 gig card to try and see if its my cards, what class/type card should i get just to install and MTD rom?? i cant CM7 and MIUI bad
Where's your other thread? I had an SD Card mount error but found a fix and posted it here:
http://forum.xda-developers.com/showthread.php?t=1296694&page=2#post18859876
Let me read your thread and I'll see if it's the same issue.
here is mine http://forum.xda-developers.com/showthread.php?t=1325525
Jsut so I have the steps down:
1) You have the ROM zip file on your SD Card
2) Reboot into ClockworkMod
3) Select install Zip from SD card
4) Navigate to the Zip file
5) Install
You're saying the process breaks for you at #3 because CWM can't read your SD Card?
If the above problem is true, try using rom manager to find and flash the file. if not try a different sd card.
Sent from my MIUI SCH-i500
back to the lag issue...when running these roms are you restoring backups from Titanium. If so, are your backups from a froyo rom, that could be part of the problem if you also get force closes. I had the same problem a while back. I have also noticed if changing fonts(such as with absolute system root tools) certain more elaborate fonts can cause some lag as well. also check into the widgets you are using, even on CM7.1 i get insane lag and launcher force closes if I use Fancy Widgets but everything else is fine.
Hopefully one of those things will solve the issue...if not wipe it clean and start fresh lol but seriously hope you figure it out
after re-reading the op it really sounds like your problem could be with restoring apps, it sounds identical to when I first switched to the GB roms. You run smooth as butter for a while the it all goes to hell. I would start with wipe data/factory reset but when intalling backups try WITHOUT DATA if you still get lag, wipe again and install your apps manually from the market or where ever. I ended up going with the latter and haven't had issues since.
Since I keep getting msgs from people asking me how I have optimized my Xperia S for less lag and such, I thought I would make a thread teaching others all I know. First a little background info.
I have used a HTC Hero for 3 years before I got this phone, so I know a few things about optimizing and getting the most out of old hardware. This means that I am quite versed in memory management, deleting unneeded apks and proper overclocking for maximum effect and battery life. I hope to install my knowledge upon others so we can stop getting noob threads like "I have less than 1gb of ram" or "ICS lags so I am going back to gingerbread, you suck Sony!".
Before we start, if you have used any of the older kernels with old CWM versions, those versions of CWM can bork your data or system. This leads to root issues, apps still showing after clearing, unable to mount partitions in CWM and any other number of issues. To fix this i recommend flashing a stock Sony ICS firmware, then fastbooting the latest version of Advanced Stock Kernel. This will give you a nice clean slate to work with. Also you can make a backup of stock firmware to roll back to if you have problems.
Now off to the races.
Build.prop tweaks
there are plenty of build prop tweaks out there, but here are the ones i use. I will continue to update this list as I try new stuff
davlik.vm.execution-mode=int:jit
dalvik.vm.heapsize=110m
ro.max.fling_velocity=150000
ro.min.fling_velocity=80000
ro.semc.batt.capacity=1750
ro.telephony.call_ring.delay=0
view.scroll_friction=0.01
windowsmgr.max_events_per_sec=250
Systcl Tweaks
Coming soon.
Memory Management/Free Ram - Many many people complaining about free RAM just don't understand how it works. In any efficient modern OS (Windows 7, ICS) free ram is wasted ram. I theory you should be using your free space to preload resources you might possibly be needing or using them to run a variety of apps and such. The only time where you would really need a large amount of free RAM would be when you want to play a game/ use an app which requires a larger amount of memory than is normally required. Sometimes Android will have a problem freeing up this required space which can lead to lag/freezing or even a reboot. If you don't play a ton of games, then don't worry about having a ton of free RAM. Secondly, more lag is created by the OS needing to resart an app or service (ie Home launcher) than if it needs to kill an app to free RAM. This is why you get Home redraws which lag for a split second, because the OS has killed off the home and it is restarting it. So less free RAM generally means less lag.
PS. Android takes up space for the system and this space is not shown on the ram usage screen. This means that if you have a device that says 1gb of RAM, the free RAM may show only 600mb. Don't freak out, this is normal all devices have it though it varies depending on skinned versions of android and which android version it is using (ie ICS uses more ram than previous versions).
How to fix Android Memory Management - Android memory management has made massive steps forward from how terrible it used to be, but it is still not optimal to say the least. We can help fix this by running a script by our not so friendly XDA member Zepplinrox.
http://forum.xda-developers.com/showthread.php?t=991276
Go to this link and read everything that you can comprehend before reading my explanation. This can be tricky and can force bootloops so make sure you back up with Nandroid.
Step Zero - Get script manager off the market. Run as root
Step One - Download the kit and the latest Supercharger Script
Step Two - Run the kit, generally on the ROMS i have tried at least, you dont need to install a new busybox or root version so skip those.
Step Three - Run the auto mode in the script or Download the automatic patcher which patches your smali files and pushes over the new services jar required for locking the home in memory. (alternatively you can do it the hard way with the smali patcher script but I dont recommend it)
Step Four - Run the script and read through things. It should make sense but ask me if you need help.
Step Five - Clean and Reboot. Sometimes it can freeze on first boot, hold vol up and power to restart. This latest script is still in testing so you may have issues but it is certainly better than the original setup.
I love the Sh1t out of supercharging and have used it for years.
Supercharging is really easy on KA17 as the services.jar is already ready to go. Just run the script which fixes oom memory settings and you are done. Dont forget to clean and reboot.
Follow-up- Run a flush engine option in the script which will then create a quick launch script in V6 supercharger directory. Put this on a schedule to run every few hours and you wont have to worry about rebooting your phone as much. Run it as superuser.
Want even less lag? - Delete any unneeded apk files either with a root explorer or Titanium Backup. This way you wont have apps you dont use fighting for memory and cpu. I delete powersaver and the exchange client as I dont use either. Other roms may have much more.
Kernel - Your kernel and kernel settings will make a huge difference in the feel of the device. I recommend XSX v6 (doesnt have crappy CWM). Set it to 1876-30 hotplug and try things out. Not every chip is the same so they all wont run great. My Hero hated the max frequencies, but my Xperia S will take all the way up to 1900 just fine. Choose a scheduler, I use deadline, but CFQ or noop are good too.
Thanks for the helpful info
Btw which setting do you use in the superscript? Aggressive, balanced etc?
does the new v6 supercharger script patch services.odex automatically? because 'im using stock .45 rom, and it is odexed which made it a lot harder to patch in the past
in the past i did the smali edits myself but i just couldn't be bothered doing it with every new stock ICS release
ttiimm said:
does the new v6 supercharger script patch services.odex automatically? because 'im using stock .45 rom, and it is odexed which made it a lot harder to patch in the past
in the past i did the smali edits myself but i just couldn't be bothered doing it with every new stock ICS release
Click to expand...
Click to collapse
Use the windows patcher or there is a new auto patcher that works pretty good integrated. Check it out.
Windows Patcher for some reason doesnt work for me :/ Btw, which auto patcher are you talking abt? Is it in the script? Which number config?
Btw, if I use a deodexed ROM such as KA ROM, do I have to follow the same steps or are there fewer steps compared? Thanks
SickL1408 said:
Windows Patcher for some reason doesnt work for me :/ Btw, which auto patcher are you talking abt? Is it in the script? Which number config?
Btw, if I use a deodexed ROM such as KA ROM, do I have to follow the same steps or are there fewer steps compared? Thanks
Click to expand...
Click to collapse
Hmm, the windows patcher works good for me. Try the ICS center in the latest version of the script. I use KA rom and have no problems. If you need to I can post an edited services.jar file, but try and see if you can get it to work yourself first.
When I try to run the script it says missing essential tables, what does that mean? Running it without root works until, it asks for root
EDIT: If it is about the starter kit, I have successfully used it
googleye said:
When I try to run the script it says missing essential tables, what does that mean? Running it without root works until, it asks for root
EDIT: If it is about the starter kit, I have successfully used it
Click to expand...
Click to collapse
Its a root problem. What kernel and rom are you on and did you install the root version from the starter kit or not.
V6 supercharger can be a pain to deal with when you havent used it, but hang in there and I will help you with it. Once you figure it out, it is easy to do.
mrsatan said:
Its a root problem. What kernel and rom are you on and did you install the root version from the starter kit or not.
Click to expand...
Click to collapse
Advanced stock kernel build 15 stock .45. Yes, should I flash the kernel again?
EDIT: Reflashing kernel did not work.
Skickat från min LT26i
googleye said:
Advanced stock kernel build 15 stock .45. Yes, should I flash the kernel again?
EDIT: Reflashing kernel did not work.
Skickat från min LT26i
Click to expand...
Click to collapse
Its probably the stock .45 version. Stock roms can be notoriously difficult to supercharge. I use KA12 and havent had any problems beyond a couple root problems caused by the XSX version with the bad ramdisk.
mrsatan said:
Its probably the stock .45 version. Stock roms can be notoriously difficult to supercharge. I use KA12 and havent had any problems beyond a couple root problems caused by the XSX version with the bad ramdisk.
Click to expand...
Click to collapse
Ah. Well compared to KAxx I'm very happy with stock so this will have to wait I guess
googleye said:
Ah. Well compared to KAxx I'm very happy with stock so this will have to wait I guess
Click to expand...
Click to collapse
Yeah I can see that, I love KA12 though.
googleye said:
Ah. Well compared to KAxx I'm very happy with stock so this will have to wait I guess
Click to expand...
Click to collapse
I'll update my kernel soon now I'm upating my rom
Sent from my LT26i using xda app-developers app
I've installed it on my Acso S (LT26w) and don't see some difference.
My steps:
download all, copy to sdcard and prepare
path jar file via exe
run script and follow instructions
What I must to get in sum?
mrsatan said:
Yeah I can see that, I love KA12 though.
Click to expand...
Click to collapse
Sorry for ot but. Compared to KA10, how's the rom now? When trying both stock was significantly faster and more smooth for me. And do you use the ka kernel?
Skickat från min LT26i
Desperanto86 said:
I've installed it on my Acso S (LT26w) and don't see some difference.
My steps:
download all, copy to sdcard and prepare
path jar file via exe
run script and follow instructions
What I must to get in sum?
Click to expand...
Click to collapse
What does the final part of supercharger script say? What percentage supercharged?
googleye said:
Sorry for ot but. Compared to KA10, how's the rom now? When trying both stock was significantly faster and more smooth for me. And do you use the ka kernel?
Skickat från min LT26i
Click to expand...
Click to collapse
No I dont use KA kernel, I use XSX kernel. KA12 is faster than stock for me and has more options.
mrsatan said:
What does the final part of supercharger script say? What percentage supercharged?
Click to expand...
Click to collapse
something about he (script) finished and now I can manualy choose options from 1 to 33. Option EXIT also was there. I chose exit
Desperanto86 said:
something about he (script) finished and now I can manualy choose options from 1 to 33. Option EXIT also was there. I chose exit
Click to expand...
Click to collapse
You should be fine then