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.
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
Well, my Nook appears to be in trouble.
The long and the short of it is that it got wet. Not too wet, but wet.
It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.
All ROMs complain of "System process" and Wireless issues, with FCs.
I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.
The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.
However, I was able to see I had the correct files in /rom once, so those are there.
Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"
CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.
The uboot and the uboot menu work as well.
I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.
I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.
I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.
I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.
Any suggestions?
Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.
old cell phone trick
Fill a bowl with rice (uncooked).....the rice will draw the moisture out.
you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car
Whoa, isopropyl alcohol. I feel like that would take some stones...
I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)
I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.
It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.
It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...
Thanks for the ideas...any and all welcome!
You can take the back off. I have not done it, but somebody just said they did it to disconnect the battery to reset. Look at that recent thread in q/a. Maybe he can tell you how he did it.
Attempt at your own risk, no support will be provided.
I'm not the battery guy leapinlar was talking about but,
Open the battery flap, remove SD card, remove the tape dots from the T-5 torque screws then remove the screws. Slowly and carefully so as not to break any of the hooky thingies that are holding the back on pry the cover up from that point moving slowly around the unit.
I've only done this once, it was a while back and I ended up breaking two of the little hooky thingies. That's why I suggested providing points for evaporation to escape and attempting to accelerate evaporation. Heck we don't even know if moisture is the issue anymore.
Thanks for the extra suggestions.
I tend to think at this point that whatever water got in there is gone. It's been four days, and it wasn't soaking. I may just go ahead and try and take out the battery, I don't know exactly why that would help, but what have I got to lose?
If I had to guess, I would think that the wifi chip might be shorted, as that is the only thing that doesn't seem to work at least for some period of time.
The FC's sure do look software related though. I fail to see how CWM could read and mount the sdcard while the ROM cannot as being anything other than sotware. Unless they use wildly different methods to do the same thing.
This nagging feeling that I should be able to at least fix that with some software methods keeps me thinking the same or the other problems. I'd be okay with an non-networked tablet, if it came to that. But maybe the thing has to have wifi as an option to work right. I don't know...
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Malave said:
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Click to expand...
Click to collapse
Considering that this is basically what is happening to me (but with some additional Wifi setting crashes) this gives me hope.
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
Anyway, of interest (before I shut it down 2 days ago):
internal sd card is not wiped, it can be explored in CWM.
The /ROM partition is at least somewhat functional, as battery stats can be wiped
When I request a log, I get:
Code:
Battery Stats
Block Groups: 3
reserved block group size: 23
Created filesystem with 11/22608 inodes
and 2883/90357 blocks
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure. Maybe that is why I am having trouble with ADB. It just kept saying insufficient permissions and ???????????. I tried setting up android-rules for udev with no luck.
Unless I hear anything else promising, I will go get the proper screwdriver and try the battery thing. It has been sitting off for a couple days now...
Thanks for all the ideas, people.
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Try your edits to /rom... and if you have to try: mount /dev/block/mmcblk0p2 /rom
DizzyDen said:
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Click to expand...
Click to collapse
I actually didn't try to do anything. I just wiped system, cache, davlik, battery stats and asked for a log prior to flashing a new zip in the hopes that the rom would work if provided a blank slate.
I wiped battery stats since the .bin that holds them is in /rom. The log was something I had never done before.
The notes from above were just the CWM output from the log.
edit: I just saw your second paragraph. Don't know how I missed it.
But I don't know what you mean by edits. I haven't been able to get ADB working. I have been able to mount and unmount through CWM that's it. Unless you might know anther way to resolve insufficient permissions with beaucoup question marks instead of device number?
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
DizzyDen said:
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
Click to expand...
Click to collapse
Which I was. I got it from Leapinlar, and was under the impression, since I had seen him warn that roms flashed from that recovery would go to emmc, that it would work.
I did make a regular 3.2.0.1 bootable, and tried again, but with the same result, so I don't know if that made a difference. But it did seem hopeful, so thanks for the response.
I am going to finally go get the torque screwdriver and take this battery off and give it some days. It's been almost a week already, but you never know.
Thanks a bunch for the reponses, Diz.
mateorod said:
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)[/CODE]
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure.
Click to expand...
Click to collapse
Mateorod, if you got that log using my CWM boot SD version 5.5.0.4, the recovery.fstab lists /dev/block/mmcblk1p2 as SD-EXT, which for some devices is the extended partition on SD for storing additional apps to supplement /data. Our implementation of CM does not use that. So when recovery tries to do some wiping, formating, backing up, etc, it always fails when it looks for that partition. It has nothing to do with /system or /rom.
If you told it to do a factory reset, it tries to wipe /SD-EXT as part of that and it fails to wipe that because it cannot find that partition.
Edit: That CWM SD does do its modifications to emmc. It only referenced mmcblk1p2 because of sd-ext.
Here is the filesystem table from my log using it on SD:
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
The alcohol trick does work, I did it on my old HTC Kaiser. I disassemble it as much as I was comfortable, and then completely submerged it in alcohol until It stopped throwing up air bubbles; Thus showing there was no air left in the unit. I then removed the pieces from the alcohol and put them in a bowl of rice. I let it stand for about a week. Once the time was up a reassembled and turned it on like nothing had happened.
Little note: I was in the possession of a AT&T Go Phone for use as a back up in case this destroyed the unit. If you feel that there might be another way to repair it, I would suggest you explore that option first as I do not know what a significant time in alcohol will do to the inner workings of the Nook. However if you are at the point of already replacing or upgrading to a different tablet, than you have nothing to lose and can only gain a working Tablet or fancy Paper-weight from this.
Okay, a little update.
I had taken apart the Nook and let it sit for almost a week. But upon reconnecting the battery and clearing system/cache/davlik and reflashing anything, it still wouldn't allow in-ROM mounting of sdcard or adb or wireless and I would still get some version of "process System not responding" and "Setting Wireless not responding" toasts and then a crash, either in CM7, CM9 or Stock. Unusable.
What I think I have is a totally borked wifi chip. Which is okay, in the long run, but the Nook kept crashing and I would have liked to use it in some capacity.
What I decided (which was difficult to diagnose with no terminal or no ADB) was that the Nook was crashing upon trying to access the network and the saved network info. (which I know is mad persistent, as the wifi network I used to originally register the device still shows up in the stats, even after many many system wipes and 8x reboots and so forth.)
I had never reset to factory from stock settings and I couldn't now completely erase and deregister because you need wifi to do so.
However, I found this (which I had never heard of, sounds like a boon to thieves everywhere). After skipping out-of-box experience I could boot into stock recovery and finally erase the wireless settings.
Now I have a stable (albeit un-registered) stock nook, where I can at least read the books I have on sdcard.
I will eventually reflash a CM build now that the network settings have been forgotten and see if that is usable, even if there is no wifi.
But I am pretty happy to have some semblance of the Nook back, even if it is just a neutered (literally) stock.
I'll let you know how CM goes one day soon.
Thanks for the help!
Excellent, (and powerful), link.
And by virtue of that link I will find a way to proclaim my absolute geekitude within the company by dropping Kate's name. :good:
Well, I finally tried flashing Cyanogen 7 and 9 to the thing, but as it crashes when it tries to access wifi, I can't get it stable.
Unless anyone knows a code edit (smali maybe? I know there are a bunch of boolean settings in the SystemUI.apk, maybe there) where I can change the default wifi setting, I may just be stuck with stock.
Which is way better than nothing, at least it has use. Skipping OOBE was a life-saver for getting to a place where I could erase the WiFi info.
Okay, here's another shot in the dark, still trying to get this thing to successfully boot in CM...
I am working on a little project for the Nook, which will be infinitely easier to debug if I can actually boot into CM.
Does anyone familiar with the source code know how to modify it so that WiFi is set to off by default? I am thinking about changing the 'true' to 'false' in the /device/bn/encore/overlay/frameworks/base/core/res/res/values/config.xml entry for wifi found here...
Code:
<!-- This string array should be overridden by the device to present a list of network
attributes. This is used by the connectivity manager to decide which networks can coexist
based on the hardware -->
<!-- An Array of "[Connection name],[ConnectivityManager connection type],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
before automatically restore the default connection. Set -1 if the connection
does not require auto-restore. -->
<!-- the 6th element indicates boot-time dependency-met value. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<!-- item>"ethernet,9,9,2,-1,true"</item -->
</string-array>
This looks like I am on the right track (this will eventually end up being compiled into the res folder of framework-res.apk) but I may need to track down the ConnectivityManager. Although the cursory look I have given this seems like I may be close to on the right track...
(The wifi being on at boot always crashes my CM installs due to shorted wifi chip, for those of you who may be new to the thread.)
I am asking here just in case someone knows, I may just go ahead and try it if no one chimes in. But better to ask than to blindly shoot in the dark, I figure...
Update: Success. I am back on CM9 (well, a hybrid, actually...HINT), without wifi.
Update 2: Due to the fact that this nook is now in a Cyanogen-usable state, a new rom will be posted in development tomorrow from eyeballer and I. Thanks for the suggestions, everyone. I wish I had dipped it in isopropyl alcohol, just so I could say I did it...
First of all, I'am not a dev, so it isn't sure that this idea will see a future.
So, in the last month, I tried to use F2FS instead of the ext4 on my Nexus 7: I was curious to see if it is only a placebo mod like the Seeder entropy generator, and the good news is that it seems not to be the case.
It is already known to the raspberry pi community that infact this filesystem do a difference, and also on some devices seems to do the job (some benchmark, this of anandtech, or this done on a Z1 for example); maybe it is less reliable than the ext4, but we are talking of mobile device not web server (also I have seen lot of mods that disable the journaling of ext4 attempting to increase the performance, so I think that this is the minor problem).
To use it we need to add the driver into the kernel (here i find some backports, there is not a 3.4 backports but I think that adapting the 3.5 version would be quite easy), edit the fstab and if I understand correctly to build the recovery with the support for F2FS (here are the cyanogenmod tools), so we need to modify the kernel; @mikeioannina, maybe you can try this if it isn't too much work, if we use it only to the data partition we only need to format it, if we wont to use it also on cache and system we also need some edits to the rom.
If my explanation wasn't clear (sorry for my crappy English BTW), this is the topic for the Nexus 7, I took all of the information from that topic.
I agree with you that in f2fs is something which makes devices faster. Im using it on my tf300t and its awesome.
Would like to see it for our play, but truely on devices like ur nexus, my transformer and some other (which have possibility to use f2fs) /data is for apps and other files not only for apps like in our play, so I dont think it will give so much "speed".
However if there would be possibility to mount (fast) sdcard as both /data and /sdcard in the same time (and dont use real /data partition or repartition it as a part of /system for ie mods) and format it as f2fs? Here we could gain something.
It all was about /data partition, coz I dont know how works device with /system as f2fs. It should be faster too.
How to Trim Your Partitions in TWRP for a Truly Clean Install
Do you flash a lot of ROMs? Do you ever think to yourself, "I wish I could go through extra steps to get a performance boost?" Do you lie awake at night and wonder what happens to your old data when the "mkfs.ext4" command gets passed in TWRP?
If you answered 'Yes!' to 2 or more of those questions then this guide is for you! I'll explain how to run the Trim command in TWRP prior to a clean flash of a ROM to give you peace of mind and perhaps a performance boost! I emphasize perhaps because the level of performance we're talking about here may or may not translate to real world applicability, but I do it anyway because science!
Steps!***WARNING: I highly recommend making a backup of your previous ROM because if you follow this guide we are going to send everything that isn't a binary zero to the data abyss until the only thing left on your device is a bunch of zeroes and TWRP. YOU'VE BEEN WARNED!***
Follow this method prior to a clean install only (TRIM command can be run at any time)
1.) Reboot to TWRP and Choose 'Wipe' from the main menu
2.) Choose 'Advanced Wipe' and select Data, System, Cache, and Dalvik Cache
OPTIONAL (Most people shouldn't do this step): If you copied your TWRP backup to your PC and want to wipe out your SD card select 'Internal Storage' otherwise do NOT check this option!
3.) Swipe to wipe the selected partitions
4.) Hit the home button and choose 'Mount'
5.) Mount the System partition (data and cache should already be mounted)
6.) Hit back or home, choose, 'Advanced', and then choose 'Terminal Command'
7.) Hit 'Select' in the bottom right corner to get to the command prompt (you'll be in the root directory)
8.) type this at the prompt, "fstrim -v /system" and hit enter (do not add the quotes)--it will show wiped space
9.) type this at the prompt, "fstrim -v /data" and hit enter (do not add the quotes)--it will show wiped space
10.) type this at the prompt, "fstrim -v /cache" and hit enter (do not add the quotes)--it will show wiped space
11.) Reboot to Recovery
12.) Install ROM and Gapps of choice then reboot to system when prompted
13.) Super clean install complete
But, Why?!Here's a good article that sums up the answer to this question: http://arstechnica.com/gadgets/2015/04/ask-ars-my-ssd-does-garbage-collection-so-i-dont-need-trim-right/
F.A.Q.Q: What does the TRIM command do?
A: When data is deleted by an operating system it gets flagged for deletion. Which basically means that it gets overwritten if the OS needs more space. Otherwise, it just sits there invisible on your drive for an arbitrary amount of time. I can't stand arbitrary. I prefer weekly.
Q: Who else uses this command?
A: fstrim specifically is a Linux/GNU command, but if you try to defrag an SSD in any modern version of Windows they pass this command as well. OSX recently decided to extend this trick to third-party drives that owners installed themselves. How...kind of them.
Q: Do I need to run this?
A: Absolutely not. Running fstrim just accelerates a process that Android will do itself eventually. There is even a hardware trim built into modern SSD drives, but I don't know that all smartphone flash memory has this feature.
Q: Break down the "fstrim -v / " command for me cause I wanna learn!
A: fstrim is the linux command, -v stands for verbose output so you can see the results, and / is your partition that you are calling to run trim on. We only have 3 partitions to choose from and those are: System, Cache, and Data.
Q: I get the error: fstrim command not found. Halp?
A: Reboot to TWRP, re-mount the System partition, and re-run the commands.
Q: Does it work on F2FS?
A: It seems to. I ran it on my data and cache partition after converting them to F2FS and it trimmed like normal.
Q: Running fstrim, rebooting recovery, and running fstrim nets the same output. Why?
A: I don't know why this happens. If you run fstrim twice in a row you'll see the first one gives a byte output and the second run shows zero if passed on the same partition. However, rebooting recovery and perhaps remounting the drives causes it to think trim hasn't been passed yet and does it anyway? I'm guessing honestly.
Q: Will you add more questions to this as members find errors in your guide and remind you that you left something out because you're human and clearly don't know everything?
A: Absolutely.
Wow... nice!!
Great OP, too. Very informative!
"give you peace of mind and perhaps a performance boost"..
lol, perhaps? performance boost you will not get, its more like when you just run a rom after clearing your "dalvik". it will "feel" quicker for about an hour or so. i say "feel" because there actually isnt a boost there, its just cleaner on the first run. anyways, and regardless, this is still a good thread
Redundant file fragments take up space and slow performance as they're automatically deleted. You may not notice much of a difference, but it's definitely not a bad thing
This is great!! Thank you for this information
simms22 said:
"give you peace of mind and perhaps a performance boost"..
lol, perhaps? performance boost you will not get, its more like when you just run a rom after clearing your "dalvik". it will "feel" quicker for about an hour or so. i say "feel" because there actually isnt a boost there, its just cleaner on the first run. anyways, and regardless, this is still a good thread
Click to expand...
Click to collapse
Lol you're correct to an extent, it is a lot like clearing cache/dalvik in a sense. But the main difference is that it actually overwrites the written sections and not just wiping the MFT like mkfs.ext4 does when you wipe a partition.
I'll put it this way, if the fine people at ASUS include it in my UEFI BIOS for prepping a new install of Windows, I think it should be a recommended step in installing a new phone ROM. For advanced users of course
Sounds like a great idea. So to clarify, by doing this trim we do not delete the internal storage (SD card) files we use such as files listed under the "downloads" folder. Is that correct?
Nickchapstick said:
Sounds like a great idea. So to clarify, by doing this trim we do not delete the internal storage (SD card) files we use such as files listed under the "downloads" folder. Is that correct?
Click to expand...
Click to collapse
Correct. As long as you don't choose 'Internal Storage' when wiping with TWRP you can safely trim the entire data partition. The fstrim command only overwrites data that has been marked for deletion through user intervention or from a wipe command in TWRP.
So I just did this and wow there was a lot of data there. For me that short 5 minutes was worth knowing my phone has less trash just sitting around. Kudos AlkaliV2. I'll remember this til the end of time.
Followed the instructions perfectly and enjoyed the next few hours reapplying all of my settings.
enginuity2 said:
Followed the instructions perfectly and enjoyed the next few hours reapplying all of my settings.
Click to expand...
Click to collapse
I love a good clean flash. I even deny automatic restore and pick, "Setup as new device" each time because I love choosing what will and won't be on my phone. It's a rush exceeded by many things. But still a pretty good way to end the day.
After Years Of installing many roms on my s3 mini (download mode showed 180 counts of custom binaries download!!!) this article brings first day freshness to my phone :laugh:
this gave me performance again; but my progress bar in some apps is bad again
AlkaliV2 said:
I love a good clean flash. I even deny automatic restore and pick, "Setup as new device" each time because I love choosing what will and won't be on my phone. It's a rush exceeded by many things. But still a pretty good way to end the day.
Click to expand...
Click to collapse
Is this method feasible on a device that has a A/B partitions?