Related
I now have jf adp 1.5, but I want an apps2sd firmware, but I can't decide which one is the best! probably both are the best, I know!
which are the difference between Lucid Rem and the Dude?
JF's firmware comes already supporting Apps2SD. In fact you can do it all right from the terminal on your phone. And where did you d/l from again? Because I know for a fact JF not only states this fact on his blog (the page you probably got it from) but also links to a page of concise and easy to follow instructions. Personally I think you should try all 3 (be sure to READ everything TWICE when using any firmware w/ unionfs).
Also it dosen't hurt to search as I know EVERY freaking bit of this info is w/in the first 2 pages of this forum or on JF's site....RTFM
yes I know JF is compatible to app2sd, but the process to have apps2sd is not so concise and easy: lucid Rem and the Dudes seem to be more easy!
I'm sorry if I asked: I actually red the first 3 pages, not only 2, but it is not so easy to summarize tons of information!
i went through about 8 hours worth of wiping upgrading and testing the builds.
first thing i did was wipe the ext2 partition onthe card using gparted on linux. (i actually removed the partition and repartitioned it to do so. for more stability in case of bad partitioning from before] and then i wiped the phone. before upgrading.
- original JF 1.5 stable. but apps2sd was a bit complicated.
rewipe. repartition.
- thedude's rom is stable, but i found that i could not for the life of me install games. at all. it kept coming up as con.[game].whatever and i couldn't run any of them. [tested with jewellust and tangram pro]. also, the apps2sd is in collaboration with marcusmaximus and while i love the way he did the apps2sd, there wasn't much in instructions on how to make upgrading to thedude's build + marcus' app2sd work perfectly. [i got it to work, but it was w/o it's share of problems]
another rewipe. repartition.
- using Lucidrem's modded 1.5 + apps2sd steps laid out by mailman. simple perfect. 73mb free. apps2sd and stable as hell. i would recommend this.
but most of all, just wipe the ext2 partition for stability reasons. the move from rc33 to 1.5 was not a simple upgrade with apps2sd involved.
Exegence said:
i went through about 8 hours worth of wiping upgrading and testing the builds.
first thing i did was wipe the ext2 partition onthe card using gparted on linux. (i actually removed the partition and repartitioned it to do so. for more stability in case of bad partitioning from before] and then i wiped the phone. before upgrading.
- original JF 1.5 stable. but apps2sd was a bit complicated.
rewipe. repartition.
- thedude's rom is stable, but i found that i could not for the life of me install games. at all. it kept coming up as con.[game].whatever and i couldn't run any of them. [tested with jewellust and tangram pro]. also, the apps2sd is in collaboration with marcusmaximus and while i love the way he did the apps2sd, there wasn't much in instructions on how to make upgrading to thedude's build + marcus' app2sd work perfectly. [i got it to work, but it was w/o it's share of problems]
another rewipe. repartition.
- using Lucidrem's modded 1.5 + apps2sd steps laid out by mailman. simple perfect. 73mb free. apps2sd and stable as hell. i would recommend this.
but most of all, just wipe the ext2 partition for stability reasons. the move from rc33 to 1.5 was not a simple upgrade with apps2sd involved.
Click to expand...
Click to collapse
really thanks a lot! it answers to my question!
just a dubt: my G1 is from uk, so originally it had the RC9, and after few change I came up to adp jf 1.5., the sd card (a trascendent 8gb class 6) is brand new, I just partitioned it for making ext2 partition and I didn't write anything on it. Should I wipe it as well? if yes how I should do?
if lucid rem is rteally smooth I'll go for it!
Hey there, I have the same card, if you already partitioned it but havent written anything to EXT2 you should be good. As for Lucidrem I have been using the modded JFRC33 since day one and props to all the other methods and designers of apps to sd but lucid's was the easiest for me since I dont have a home CPU. I was able to use terminal emulator to run the commands and it was extremely quick & simple. If you're unsure or not able to run adb shell on a cpu like me I would definately go with his modded version
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
borodin1 said:
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
Click to expand...
Click to collapse
I do agree that the dudes build is awsome but is it faster at first it was fast but now that i have almost 100 apps on my class 6 sd card I see the phone almost pausing when I oper certian apps. emample it I go to bettercut and try to change an icon and click on use icon pack if i have one or two icon packs its fine but if I have 6 or 8 it has a hard time opening the pop up window with the different icon packs... I have no tryed JF with apps to sd only without apps to sd and it was fine maybe i need to give it a shot and see which one is faster!!!!
borodin1 said:
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
Click to expand...
Click to collapse
A slight oversimplification of my reasoning in using unionfs, so I'll try to explain my motivations here. My primary motivation was to make the process of moving apps to the sd card more stable. Unfortunately, I think many have misunderstood what I mean by that. I don't actually mean that it will have fewer problems, it pretty much has an equal amount from what I've seen.
What I mean by it is that in the case of a problem, the phone will still start. With the symlink method I was seeing constant problems of boot looping for no clear reason. It seemed to work *most* of the time but when it didn't the system crashed... hard. With unionfs it's extremely rare that I get any reports of problems causing the phone to not start, and when I do it's always a corrupted file system on the sd card. By far the most common problems have been certain specific apps not working(at this point togglesettings is the only one I know of that just straight doesn't work with this method... and it actually works, it just force closes on boot) and some apps having to be re-downloaded when the method is applied. There's no more than a handful of more serious problems(such as apps showing up perfectly in their correct locations on the filesystem but not showing up in the launcher... wtf) which I definitely couldn't say for the symlink method. Actually even problems with a corrupted file system are massively down from the symlink method now that mine won't let you move the app caches(responsible for every single freakin' report of stale nfs handles).
Aside from that was the ability to have some apps/storage on the sd card. This is primarily for stability reasons, just in case there's any apps that freak out(or go really slow) from being on the sd card, they can be moved to the internal memory without having to undo the whole process.
At any rate, I'm not mad at anyone(just in case anyone thought I'm upset about anything said about the unionfs method), just explaining my motivations behind making it a reality.
Maybe I'm missing something, but I really don't understand why there's umpteen different threads about moving apps to the SD card, why there are *paid* apps to do this, etc.
Is it really that hard to type:
cp -a /data/app /system/sd
cp -a /data/app-private /system/sd
rm -r /data/app
rm -r /data/app-private
ln -s /system/sd/app /data/app
ln -s /system/sd/app-private /data/app-private
Why do people make this complicated?
As for instability with the symlink method, I haven't experienced any, and I think it's specifically because I did NOT move the dalvik cache, and there are a number of good reasons for leaving it in place regardless of the method used.
ok, now everything is more... clear but complicate
another question (remember I'm a noob): what is the dalvik cache? why I shouldn't move it? is it huge?
anbd the last (for now ) which is the difference between unionsf and symlink methods?
iso67 said:
ok, now everything is more... clear but complicate
another question (remember I'm a noob): what is the dalvik cache? why I shouldn't move it? is it huge?
anbd the last (for now ) which is the difference between unionsf and symlink methods?
Click to expand...
Click to collapse
Dalvik is the name of the Java VM on Android. It's what's used to run all of the Java programs.
Dalvik-cache is a directory on the filesystem that stores optimized versions of the dex files that are contained within an application's apk archive (think of the dex file as the executable and the apk as a zip file that contains the dex file and other files).
The reason moving it can cause problems is that if dalvik-cache is not accessible, no Java programs (including system programs) can run.
I have tried every combo of build and SD card mods and must say.........they all work, and I think 90% of problems are user error, I know 9 out of 10 of my mistakes were.
My biggest advice, if you dont understand what is happening you will always make dumb mistakes and be "that guy". Try to understand what you are doing before you do it and it you may be able to understand how to fix your own problem.
brandenk said:
I have tried every combo of build and SD card mods and must say.........they all work, and I think 90% of problems are user error, I know 9 out of 10 of my mistakes were.
My biggest advice, if you dont understand what is happening you will always make dumb mistakes and be "that guy". Try to understand what you are doing before you do it and it you may be able to understand how to fix your own problem.
Click to expand...
Click to collapse
While I completely agree with you, I still think that this community needs to agree on whichever way is better and stick with it. This would make it better for developers and users.
I thinks that a pro (hint: MarcusMaximuss) needs to do some bench testing and see if both ways are equal in speed and reliability. If we prove that unionfs method is as fast as symlink onem and stays that way after few weeks of use we can conclude that it is ready for prime time and gear all efforts towards using only that method.
I am in the process of doing a so called "user test". Dude's 1.1a with unionfs apps2sd felt slow to me. At this point I switched to JF1.50 and did symlinks and it's blazing fast!!! Give me couple of days and I'll convert JFs build to unionfs and see if that stays that fast or slows down. I'll do the same thing on Dude's build once 1.2 comes out. But these will be just my impressions, no solid data to back them up.
As always, thank god for Nandroid and good luck to everyone.
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
I think another group interested in advancing these methods should come together and do a test that is more "third-party", so we can have clear and unbiased results.
Having said that, I feel that this method (unionfs) will continue to stabilize as he works on it. Especially since he has commissioned the guidance of the 3 top ROM devs. Very promising in its infancy and just needs to be refined.
cal3thousand said:
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
.
Click to expand...
Click to collapse
Agreed !!!
cal3thousand said:
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
I think another group interested in advancing these methods should come together and do a test that is more "third-party", so we can have clear and unbiased results.
Having said that, I feel that this method (unionfs) will continue to stabilize as he works on it. Especially since he has commissioned the guidance of the 3 top ROM devs. Very promising in its infancy and just needs to be refined.
Click to expand...
Click to collapse
Well... I haven't quite gotten Haykuro on board yet.
Well i have done the rooting and now i have more ques
1-best rom = i tried like 2/3 roms but they always get force close soo i need fast/stable/2.1based rom and yes dont eat much battery .....plz plz plz i m not gud at finding right rom.also what do the ppls think about CaNNon202 rom??is it stable?
2nd-do i always need to dangerSPL and Radio while installing any rom??
3-App2SD.. i idk how can i create ext2 in windows i use paragon partition manger process but when i put sd card in mobile it say i need to format it and after i just create complete 1 fat32 partition do i need to 1st create partition and then install the rom or what do i need to do to install apps on my sd card and also i need the files which i downloaded from marketplace into my card...
Thanks
Jamb
jamb said:
Well i have done the rooting and now i have more ques
1-best rom = i tried like 2/3 roms but they always get force close soo i need fast/stable/2.1based rom and yes dont eat much battery .....plz plz plz i m not gud at finding right rom.also what do the ppls think about CaNNon202 rom??is it stable?
2nd-do i always need to dangerSPL and Radio while installing any rom??
3-App2SD.. i idk how can i create ext2 in windows i use paragon partition manger process but when i put sd card in mobile it say i need to format it and after i just create complete 1 fat32 partition do i need to 1st create partition and then install the rom or what do i need to do to install apps on my sd card and also i need the files which i downloaded from marketplace into my card...
Thanks
Jamb
Click to expand...
Click to collapse
1, no such thing IMHO, if you want stable, stick to stock ROM
2, no
3, there are tuts telling you how to get it done in console, and, I don't recommend app2sd, slow like hell
Jimmy_Z said:
3, there are tuts telling you how to get it done in console, and, I don't recommend app2sd, slow like hell
Click to expand...
Click to collapse
Why wouldn't you run apps2sd? I've got the csdi roms with apps2sd and this thing is blazing fast. Besides, if you're going for apps with larger sizes, you're going to want apps2sd.
I find I'm OK with the 1.6 roms with Eclair bits. Don't need live wallpapers, and the Eclair bits have all the necessary things anyway. Personally I think the 1.6 roms are very stable at this point. Very few fcs and they're speedy.
fellows plz mention me the rom name ..i don't need live wallpapers coz it just slow the os and saying force close and what about 3d gallery coz i m not able to see the pics there..
@nmw407...mate plzz mention the rom name or i just need to unroot it and use 1.6
right?
i really recommend cyanogen. i stopped using it at 4.0.4. flashed every version he's ever made and i never really had good speed. this latest one is NICE, though, and i've hopped back on. for now. but i hear these CSDI ROMs are fast. just try any of them.
http://forum.xda-developers.com/forumdisplay.php?f=448
just look for CSDI in the post title.
as for partitioning, i use amon_ra's recovery.
I've tried cyanogen, superD, and now I'm currently on sciencetest. All these have been very stable. For those starting out, cyanogen has the best step-by-step guide, however, it does require additional steps because he went legal. Some of the other 1.6 roms out there are one step roms.
Use amon-ra's recovery, partitioning sd cards have never been simpler. Much better than partition manager. I used to get read/write errors all the time with partition manager. With the latest amon-ra's recovery, you can pretty much do everything on the phone.
Just remember to nandroid/bart backup, and completely wipe before flashing a rom (again... super easy with amon-ra recovery.) Having a backup will save your life or at least some hair.
Right now using CaNNon202....but as as always its slow
CSDI is really fast and really reliable for me (not using apps2sd). I've had like 1 or 2 app crashes total, and I've been running it for the past month or so, so it's been a lot more stable than any other rom I've flashed previously.
Plus, you get a lot of options like customizing the number of columns in app drawer and number of home screens.
Go Cyanogen. v5 is on the way, which wont be a generic half-assed 2.1 port with reduced functionality.
This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).
andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack
Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?
spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?
andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)
I'm still a complete failure and now i get stuck at the galaxy s boot screen
Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?
after i put in
busybox cp -a /data/*
nothing happens it just sits there
igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data
but there is no trailing dot it just repeats what i typed and then leaves a blank space
same thing it just repeats it
igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.
WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!
Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App
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...
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?