[Q] Why your kaiser is NOT stable - Tilt, TyTN II, MDA Vario III Android Development

Most of you reading this probably have unstable kaisers. I am here to tell you why. Many of the issues you are facing are due to old kernel's, bad overclocks, having data corruption etc.
The simplest way to get the latest kernel is to view the kernel thread that is stickied at the top. That alone may solve your issues. Also please do make sure you have the latest build of the one you choose to use.
Others of you out there have overclocked your kaiser. This is fine to do, I myself am overclocked to 572 Mhz. But this only fine if you do it right. Do not overclock through Atools. That causes some instabilities as the kaiser for some reason does not like being overclocked through the kernel. Use Rogue Tools instead and you should see issues going away and perhaps even be able to go to a higher overclock.
Finally, the most stable installation is to have SYS on NAND and Data on SD. Does it make sense to keep your eggs in one baskete? Certainly not. Also with this method Data goes through an additional check if it is not cleanly unmounted. This makes a big difference if you have a lot of apps.

aceoyame said:
Most of you reading this probably have unstable kaisers. I am here to tell you why. Many of the issues you are facing are due to old kernel's, bad overclocks, having data corruption etc.
The simplest way to get the latest kernel is to view the kernel thread that is stickied at the top. That alone may solve your issues. Also please do make sure you have the latest build of the one you choose to use.
Others of you out there have overclocked your kaiser. This is fine to do, I myself am overclocked to 572 Mhz. But this only fine if you do it right. Do not overclock through Atools. That causes some instabilities as the kaiser for some reason does not like being overclocked through the kernel. Use Rogue Tools instead and you should see issues going away and perhaps even be able to go to a higher overclock.
Finally, the most stable installation is to have SYS on NAND and Data on SD. Does it make sense to keep your eggs in one baskete? Certainly not. Also with this method Data goes through an additional check if it is not cleanly unmounted. This makes a big difference if you have a lot of apps.
Click to expand...
Click to collapse
This really really confused me a lot So... if I follow ur advice, i should install data over an... ext2 partition??? I thought all the oposite... that this made the system unstable... cause NAND allready included yaffs precisely to avoid or at least minimize this... or do u mean to an ext3, but someone told me journaling isnt a good idea for our oldtimers... so please correct me if im wrong....

Yes nand does have yaffs but nand itself is somewhat unstable still. What I mean is to install Sys on nand like usual and then pick the data on SD with ext2.img.

uhmm... thanks for ur quick answer aceoyame... gonna try this later...

albertorodast2007 said:
uhmm... thanks for ur quick answer aceoyame... gonna try this later...
Click to expand...
Click to collapse
We like data on NAND for two reasons:
SPEED, NAND is several times faster than the best SD card out there (probably more due to the kaiser sd reader than the SD itself.
Data access, DATA on NAND makes it impossible to mount the SD, unless you partition , yet Windows itself cannot access partitons other than the first on Removable drives.
Yet, ext2 is more stable than Yaffs. Now don't get us wrong, you get errors on DATA and not on SYSTEM with both on NAND, because DATA is mounted rw and system ro... otherwise, we would have errors on both of them.

daedric said:
We like data on NAND for two reasons:
SPEED, NAND is several times faster than the best SD card out there (probably more due to the kaiser sd reader than the SD itself.
Data access, DATA on NAND makes it impossible to mount the SD, unless you partition , yet Windows itself cannot access partitons other than the first on Removable drives.
Yet, ext2 is more stable than Yaffs. Now don't get us wrong, you get errors on DATA and not on SYSTEM with both on NAND, because DATA is mounted rw and system ro... otherwise, we would have errors on both of them.
Click to expand...
Click to collapse
shure, i've got that idea allready, I know they dont have the same function but /sys its like if we talk about the FLASH/BIOS on a regular PC, can't be accesed unless its flashed, and /data is more like the RAM, its constantly under I/O process... so... basically what ur saying is that: if /data is installed on an .img on sd, it will REDUCE (but wont completely solve) data corruption, sacrificing some of the speed, and the fact that u wont be able to unmount, unless its partitioned... pros are, i guess, u got more free space for ur apps, and less Data corruption
Again, please correct me if im wrong.

albertorodast2007 said:
shure, i've got that idea allready, I know they dont have the same function but /sys its like if we talk about the FLASH/BIOS on a regular PC, can't be accesed unless its flashed, and /data is more like the RAM, its constantly under I/O process... so... basically what ur saying is that: if /data is installed on an .img on sd, it will REDUCE (but wont completely solve) data corruption, sacrificing some of the speed, and the fact that u wont be able to unmount, unless its partitioned... pros are, i guess, u got more free space for ur apps, and less Data corruption
Again, please correct me if im wrong.
Click to expand...
Click to collapse
Yet i feel the biggest, baddest reason for the instability.... is due to the way we are (forced to) porting the Android. We're hacking our way, getting bits from here... bits from there... compiling generic rils because we can't make the official one work, creating strange scripts to mount data/sys instead of using vold (i assume this is standard), dealing with battery issues first for the hacking situation, second because, and we must accept this, our device is OLD, so are our batteries. Perhaps WM is more accepting of damaged/old/failing batteries, but android is not. Due to extreme power draws on situations, it's normal that our batteries drop to 3.3... 3.2.... perhaps even 3.0V. This won't happen as often with a new battery. Power is more constant.
We have to remind ourselves, this is a hack, a unsuported port.
We do our best, and we try to fix issues as they come. But we, as of yet, are not able to keep up with the issues. There's simply to many problems, to few resources for help...
I'm gratefull to the comunity, i've been using Android since cupcake on the Kaiser... on first boot, i as :O with its speed... how fluid it was against windows... i only wish they get better and better... but its like trying to read a book in a dark room in a foreign language suffering of extreme eye sight problems
To be correct... and honest.... i'me using Android on a Kaiser with a 2800mAh bat. The battery is sufficient. It lasts days with extreme usage. The device is constant, but unstable. I've found out that the longer i can keep the device from crashing/soft-reseting, the less i loose from /DATA. So, as of now, i'm happy.

But all this hard work is worthwhile when u slide ur hw keyb and decide to... PLAY POKEMON RUBY ON ANDBOID! and all ur friends are like: man how u do that?? f*** awsome!

albertorodast2007 said:
But all this hard work is worthwhile when u slide ur hw keyb and decide to... PLAY POKEMON RUBY ON ANDBOID! and all ur friends are like: man how u do that?? f*** awsome!
Click to expand...
Click to collapse
Please to be explaining!!!!!!
Like.... NOW

Dont u know another gameboy emulator? i remembered to even play a ds emulator on my iphone!

Related

[UTIL][OUTDATED] One Click Lag Fix 2.0

[size=+2]This version is now deprecated in favor of the 2.0 APK version. Please see this link: http://forum.xda-developers.com/showthread.php?t=784691[/size]
This version is not recommended for use any longer.
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513
Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.
Oh, awesome. I managed to post this in the wrong forum. Doh!
Could a moderator please move this to Android Dev sub forum?
haha looks awesome dude but you are correct, wrong section im gonna try it now, will report in 5 mins!
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
abra-cadabra...
*POOF*
Done!
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
sirphunkee said:
abra-cadabra...
*POOF*
Done!
Click to expand...
Click to collapse
Thanks.
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
I'm running the manual ext2 fix with Q scores 2000+. I'll try 2.0 Util tonight and post feedback....
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
gonna test report in 5minutes
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
About what lag is this?
Sent from my HTC Desire using XDA App
Dominik06 said:
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Benchmarks are roughly the same as 1.0. You can expect about 100 points more on average though, at least on my phone.
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Zilch25 said:
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
Click to expand...
Click to collapse
Just as long as you point out that this fix isn't heavily tested yet!
RyanZA said:
Just as long as you point out that this fix isn't heavily tested yet!
Click to expand...
Click to collapse
Oh I know, I'm going to emphasize that heavily, lord knows I don't want to get stuck on tech support all night
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Thoughts? That's bad.
You should be seeing roughly 215mb free. Did you see any errors in the log at all?
Everything is working fine for me. First reboot after lagfix had some problems with downloading apps from market, but after a second reboot it got fixed.
"Biggest" problem now, is just the phone stating that my internal phone storage is too low, with an icon on notification bar that I cannot remove. Already deleted some .bak from /data folder, any more tips what I can delete to get rid from this message?
Regarding the fix. apps are indeed much more snappier, no lag on the system when installing apps from market, and overall if the phone would continue like this for the next 48 hours, lag fix form me is solved. I had some problems after some 24h, with some lag, even with the previous version of the lag fix.
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Looking through my old V1 remove script, I believe I was leaving behind the .bak files! Nastyyy... I'll update V2 to remove those if they're there on install. Will hopefully clear up any problems.

[Q] How to boot from Android first

Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.

Kernel With Separate Cache Partition

Hello everyone,
I've compiled a kernel which separates the NAND memory into 3 partitions (well more then that but anyway). These partitions are system, data and cache like a native Android phone (which also has recovery but we don't need that). Previously cache was linked to a directory on the data partition which was constantly becoming corrupt causing errors on start-up. Often clearing dalvik-cache would allow Android to boot but data was lost. There's nothing to say that this will solve the problem but i'm giving it a go so thought I would post it up for you to try also.
The cache partition is 20mb which means the data partition is only 90mb or so. If you like a million apps on your phone either put some on your SD card or don't use it
I haven't completely incorporated this partition into the initrd which means that currently it will only mount if data is also on NAND but this can be changed easily enough, but for testing purposes I want everything on the NAND chip anyway.
Downloads from market on all versions of Android, unless the init.rc directory is changed in Gingerbread, all go to the cache partition and are deleted on restart. What this means is that you can't download and install an app larger then 20mb (which isn't recommended anyway with the small amount of data space available). This is a drawback but for those that use data on SD it should be possible in the future to utilise more of the NAND memory for cache so you can install whatever you want. I don't know of many apps larger then 20mb anyway though.
I have included a modified version of ATools in the zip. The standard version will overwrite the partition values and the kernel won't work properly so if you need to modify the kernel use the version included. It is also important that you DO NOT change the system or data partition sizes in ATools as this hasn't been modified to account for the cache partition so will mess it all up.
I have also included an androidupdate.tar modules update for the kernel in case your wifi doesn't work after flashing the kernel.
I think that's it for now, let me know how it goes!
EDIT::
One last thing, you will need to wipe your DATA partition to use this kernel because some of your data may be positioned where the cache partition is now, so if you load this kernel and android is heavily corrupt you know what you have to do!
To check the kernel is working correctly you can type "df -h" into a terminal and it should show all of the current partitions including one called cache on mtdblock4.
Should now work with polaris, kaiser and vogue. There is a VOGUEIMG.NBH included for those who have trouble with ATools. It is completely untested on Vogue so sorry if it doesn't work.
EDIT
I have re-uploaded a modified kernel because there was some issues with data with the last one. If you have already applied the last one flash the new one and apply the module update again
testing will leave feedback
Ok, using your Scoot CyanogenMod 6.1.2 (RLS6) [16.03.2011], overclock via atools+roguetools to 529, gpu oc, battery units tweaked to suit my battery.
No SIM card yet, don't have one to put there, sync with google to get contacts.
Installed GoLauncher. Enabled JIT and Keep Launcher in memory.
Once in a while, Android is killing all apps, launcher included... strange...
Nevermind that, it was Cyanogen and the LongPress BackKey. LongPress on our Kaisers during lag can become short press
First couple of days of heavy use I've had in ages with no corruption. First day of my new job today so it's been on Google Navigation for 3 hours and used extensively during the day. Had to do a hard reset at one point and everything was fine. had a few soft reset's too. Don't get me wrong, i'd be surprised if this is a fix, but it's been a while since I've used my Kaiser this much and not had to wipe my data partition!
Update: CM is a bit slow, trying:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
And everyting seems good. I've pushed it a little, several normal reboots.
Had to reflash system (didn't reflash data). No errors, FC's, whatevar. Everything works, yet didn't try to make/receive calls. Its 1am here...
Now this particular version, has a god damn bug that is get the best of me. The Power Button and the red button won't make the phone go to standby. If i long press, i get the normal reboot/power off/airplane etc menu, on both keys. But single press is ignore... Any idea ?
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Using this kernel with Valentine 1.02. GPU overclocked and CPU @ 520mhz. Super fast and for the first time... no data corruption! Verry happy so far!
daedric said:
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Click to expand...
Click to collapse
Well in theory not too hard, there is a feature built into the linux kernel called cpufreq which is currently disabled in our kernel because our cpu and chipset code doesn't support it but krazy-killa has been working on getting it working in his kernels with a little success as far as i'm aware but i'm not that sure. I haven't personally looked into it but if I get some spare time I definitely will. I've started a new job now which i'm sure will keep me quite busy but I still intend to so some work on the Kaiser when I get time
Best of luck on your new job! I wish i had enough knowledge to continue the kernel development, but i'm quite a ignorant
Still, thank you, till now it's one of the best kernels i've used.
Hi Scoot!
I love your kernel. No data corruption so far (two days). did a few stylus resets and stuff.. Magical =D. Now IMO we only need better sleeping and autofocus to call kaiser a fully android device! Please Keep up the awesome job, scoot! thanx, danke, sposeeba, bedankt, aciu, dzenkuja!
Nice job scooter, I've been using Scoot CyanogenMod 7.0.2 RLS2 [28/04/11] @ 500MHz, and it seems fine so far.
I tried Fat Free Froyo before CyanogenMod, which also worked great for the few hours it was running. I'm not sure which one to stick with though.
Keep up the good work. I wish I could help with the development, but I have yet to learn programming (been ten years now ).
This kernel looks pretty stable, but just a few quick questions:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Thanx for your great work, finally it seems to be fully usable for me and if you and Krazy-Killa would be able to work together to manage the power consumption, then it would be amazing, because I am going to get new phone (running some new extensive business and I can not afford to be not reachable when something happends on Kaiser) and give this lovely piece of HW to my son... And I really do not want him to have a WM machine But Android needs to be stable for him to use Well... he will get it for his 10th birthday at 6.9. so we still have some time to tweak it a bit more
if this works then it would be magical, your CM builds were so fast and awesome and if there's no data loss then... <3
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
PoXFreak said:
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
Click to expand...
Click to collapse
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
a.s.j said:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Click to expand...
Click to collapse
1) The cache partition is still using Yaffs2 because it is the easiest filesystem to configure at the minute, but the idea of making it a separate partition like on a native android device is that it can be changed to another filesystem in the initrd relatively easily. If it gets corrupted it will do what it used to I guess, but I haven't had any corruption as of yet so it's difficult to say. Hopefully if the cache partition get's corrupted it shouldn't affect data so you should just be able to wipe and format dalvik-cache in the install menu.
2) I made it 20mb because most android devices have 30mb or bigger and this is mainly because market app downloaded get downloaded here before being installed, so if you installed google maps for instance it would use up 6mb, plus the standard 1-2mb normally being used, but if you only had a 10mb cache for instance, you would only be able to install apps less then 8mb which is a little limiting really. I don't really care much about installing lots of apps in data or on the phone at all for that matter so having 95mb for data is more then enough for me.
3) You can put apps in the system partition in /system/app. The system partition is read only so all data for the app still goes to the data partition. You can still save a little data partition space though if you need it. Most installs of android are 80-95mb which should leave you 5mb or so to play with. Some all language builds pretty much use up all of the partition though so you need to look and see what space you have to play with before putting apps on the system partition. If you overload it you will probably end up corrupting it and having to reinstall. But to answer your last question, the system partition works in the same way as the data partition apart fro the fact that it is read-only and data is read/write.
I've modified my Kernel to use the NAND mtdblock3 (/data for everyone else) as the cache partition, since my NAND is pretty much shot to begin with, and have system and data on SD Card. So far it's made downloading Market Apps twice as fast, loading webpages pretty fast, and basically anything else that the cache is used for.
scooter1556 said:
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
Click to expand...
Click to collapse
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
PoXFreak said:
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
Click to expand...
Click to collapse
Can you not do all of this using the ATools i provided in the attachment in the first post? You should be able to load the nbh into ATools and then set the CPU speed, change the keyboard type and remap the buttons and then save it before flashing. Just don't change the partition sizes as this will mess up the cache partition I added until I make it more permanent.

[IDEA] Android rescue.zip project..

So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
chadouming said:
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I told it already, the "custom" folder is not filled. It will be kept empty. The user can put a file, which ofcourse is the file of the device he/she have or want to get repaired. All he has to do is copy and paste the file from the working zip( zip file of his currently installed rom, that encounter the problem) of his rom to the custom folder inside the rescue.zip.
And the things that are common will be scripts, but those too will contains device specific mound points, paths, etc. I think that will be common( ie, the working of script, once the mound is done). Am i right?
So all i have to figure out is mount points, paths etc.. i got a couple of them, about 15 or so. And pls help me to find the rest.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Mikevhl said:
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
Click to expand...
Click to collapse
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
wilwilwel said:
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Pls pm me the idea how to make the checking script. Or links that have info in this. Thank u in figuring out such a prob. I am unaware of that.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
showlyshah said:
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
Click to expand...
Click to collapse
I'll send this as a PM as well, but people might learn from this. I am not talking about any specific mount points for LG phones, I just pointed out that there are some roms which use sed to check the filename of its update.zip and do tasks according to that, you need to have one line in your updater script to run the script which detects what to do. That way a user of a Galaxy Nexus would rename it to update-maguro.zip and it would know to use mount points for the maguro, while if the exact same update.zip was to be named update-p990.zip, it would know to use the mount points for the LG optimus 2x. This way you could easily keep the zip up to date for any device, because they all use the same update.zip
About the recovery, you would need to build it for every phone once, but you could make one change to the recovery source and easily compile the recovery for all phones which are capable of running CWM. I believe this method to be more user friendly, as a recovery image has support for actually choosing what you want to do, instead of having to rename the file. A recovery image also has a better way of communicating with the user. Where a update.zip can only say "Hey, I had an error and I'm quitting now, I won't give you any details what the problem was because that's just how update.zips roll", a recovery image would be able to give more advanced outputs, like "An error occurred when trying to mount /data." And then give you the option to either try again, manually fix it by using a computer with adb, or quitting.
But that's just my personal opinion. The recovery would be way harder to make, but I was the original porter of CM6, CM7 and HTC Sense to the xperia mini pro and mini back in the days. I also made a custom recovery and roms for the HTC desire Z, maintain a CWM port for the HTC Chacha which I don't even own and have used the LG optimus 2x before. (currently a maguro owner) but I'm trying to say that I've been experimenting a lot with different phones and know what the possibilities of Android are. you could even make a live Android build, tailored for recovering your phone, which is ran by an update.zip! How cool is that? That would be VERY device specific though..
let me know what you think is the best way to do this. I was thinking of making a mobile time machine app for some time so it's good I saw this thread.

[Tip] Going 'Pristine' : What, Why, How

People keep asking me what "Pristine" means, and I'm tired of having to re-re-retype everything every time, so I think I'll just gather everything about "Going Pristine" in this thread
What does "Going Pristine" means
Going 'Pristine' means: Installing a ROM with no leftover from the previous ROM
Why should I "Go Pristine"?
Short answer: To prevent 95% of the problems experienced by others when installing a Custom ROM
Long answer:
When you install an App (.apk), the data saved by the App -- even the .apk itself! -- might be optimized/customized based on your previous ROM. This means that if you change your ROM, the data might cause problems due to the differences between your previous ROM and your latest ROM.
This is especially a problem if you 'change generations' (e.g., upgrading from GB to ICS or ICS to JB/JB+).
I *always* do Pristine ROM installations, and am glad to say that I managed to avoid about 95% of the problems experienced by other users of the ROM I used.
Additional Info: There's a hidden folder called .android_secure in the root directory of your SD Card. This folder is not visible when the card is mounted in your phone. It might contain settings that depends on what ROM you're using.
Are there Drawbacks of "Going Pristine"?
Unfortunately, there's no such thing as a free lunch. Here's a list of some potential drawbacks of Going Pristine. See if you can live with them; if you can't, then you shouldn't go pristine.
You will lose your savegames.
And thus, avid gamers will likely go insane due to having to repeat all the levels
However, please read the 2nd post of this thread for some interesting thoughts.
.
You will have to re-download all apps.
Which will be *very* time-consuming unless you have a fast HSDPA connection, or able to access a fast & free Wifi hotspot, or both.
Also, please read the 2nd post of this thread for some interesting thoughts.
.
You have to set some (relatively) significant time to do the process.
Trust me, copying 10 GB worth of stuff from/to the SD Card takes a loooong time, especially if there are a huge number of small files like porn pics cute kitten & puppies pics.
How do I "Go Pristine"?
Make sure that you have ClockWorkMod installed
.
Make a backup of important data, such as SMS Log, Call Log, Contacts (if you don't sync to Google), etc.
No need to perform backup of apps, especially System apps!
.
Create a Nandroid backup of your current system, I suggest in .tar format instead of dup format.
This will be necessary if you need to go back to your previous ROM.
.
Turn off your phone, eject the SD Card
.
Backup (copy) the whole contents of the SD Card to a PC (Windows, Mac, Linux, no matter)
-- or --
Prepare a new SD Card
.
(Optional, but recommended, especially if you want to use Link2SD later on) Repartition your SD Card, even if it's previously partitioned.
Make 2 primary partitions; the 1st one as FAT32, the 2nd one as ext2
(You *don't* want ext3/4 on a flash memory. Trust me)
.
Format your SD Card accordingly. (I.e., 1st partition as FAT32, 2nd partition (if you made one) as ext2
.
Copy the following to the root directory of your SD Card:
Your ROM installer updatezip
(If needed/specified by the ROM) GApps updatezip
The /clockworkmod directory from the previous SD Card contents (you did backup your SD Card, didn't you?)
.
Insert your (partitioned, formatted, and copied-to) SD Card into your phone
.
Boot into Recovery
.
Wipe/format the following (find the proper entry in the CWM menu structure):
/data
/system
/cache
Dalvik Cache -- please note that this is *different* from the /cache of the previous line!
Internal SD
Battery Stats
Leave the External SD alone!
.
Install your new ROM, following exactly the instructions by the ROM-cooker/dev
.
Now, this is VERY IMPORTANT: DO NOT EVER RESTORE ANY APP FROM YOUR PREVIOUS TITANIUM BACKUP SET!!!
ALWAYS DO FRESH INSTALLS FROM THE PLAY STORE!
You are allowed to restore some data, though: SMS Log, Call Log, and Contacts Book. That's it. Nothing else
However, please read the 2nd post of this thread for some interesting thoughts.
.
I have been installing my ROMs with "Pristine" way. Yes, reinstalling everything *is* tedious, but as a benefit, the new ROM runs smoothly, and a lot of problems that others (who did not go the "Pristine" way) never happened on me.
=====
There you have it, a clear and complete description of "Going Pristine", complete with the steps and explanations.
Feel free to link to this thread, and as usual, if you find this thread helpful, leave a Thanks and/or rate this thread 5 stars.
Thoughts and Considerations on Restoring Apps
After doing *lots* of Pristine installs, and some deep spelunking within the folders and settings of various apps...
... and based on valuable inputs from XDA friends ...
... I've come to the conclusion that:
Perhaps 90% of apps are safe to be reinstalled from Titanium Backup.
A sizable number of apps are also safe to have their data restored by copying the relevant data directory in /data.
The question is: How to make sure that the app you're trying to restore is part of the 90%?
My terse answer: Unless you know *exactly* what the app is doing (e.g., by perusing its source code), you can't really be sure.
You can always experiment, though; just remember to do a Nandroid Backup prior to restoring an app.
What I can give you, are several guidelines:
Games that are not too 3D-oriented are most likely safe; they are not likely to install additional libraries to mitigate whatever shortcoming the W has
Games that heavily rely on 3D ... unknown. Some of them are known to delve really deep into the Android library files, and even install their own custom libraries depending on your ROM/kernel capability
Productivity apps, e.g., Office Suites or To-Do Lists or PDF Viewer or ... many others of their ilk, are most likely safe to be restored. They are never known to install their own libraries, and/or have settings dependent on the ROM/kernel
Utilities... now we're getting into unknown territory... some of them are safe (the ones that don't mess up with the innards of Android); some of them are dangerous. I recommend re-downloading from Play Store
Be wary of apps that, when they were first installed, requested to add "additional files", either via Play Store (you can see in the Notification Tray, "Additional Files") or on first run (usually they will call it "Downloading assets"); these apps might be downloading binaries that depends greatly on what the system state is at download time. Let's call them the unknowns.
That's it. So, the warning that "You'll lose your savegames" is not really absolute; if you're lucky, you can restore from a TiBU-made backup.
Always remember to do Nandroid Backup.
========================================
Games known to be restore-able:
Funky Smugglers
Minecraft
Subway Surfer
Utilities known to be restore-able:
ClockSync
Solid Explorer
-- Sent from Opera Mobile for Windows --
I think this topic must be stickies
.... coz this topic very important
Sory if my english is noot good
In some way thats true, i do believe though that much people never have a look at the stickies. Would be a shame if this topic wouldnt be seen
Sent from Galaxy W with CM10 (thanks to Arco!)
actually i dont think extensive rom flasher will follow this guide but i do agree with pep about going pristine
Sent from my GT-I8150
hadidjapri said:
actually i dont think extensive rom flasher will follow this guide but i do agree with pep about going pristine
Sent from my GT-I8150
Click to expand...
Click to collapse
Hehe... too much things to do for them, likely...
But if you're like me, flashing only to fix bugs, and already settled on a (relatively) stable ROM, going Pristine should be a habit
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
hadidjapri said:
actually i dont think extensive rom flasher will follow this guide but i do agree with pep about going pristine
Sent from my GT-I8150
Click to expand...
Click to collapse
Well doing this just seems alot more effort if you have alot of apps and games and why alot of people won't do this. I mean I have 70 apps/games installed so having to manually install all of them again is just to much effort.
Broken Puzzles said:
Well doing this just seems alot more effort if you have alot of apps and games and why alot of people won't do this. I mean I have 70 apps/games installed so having to manually install all of them again is just to much effort.
Click to expand...
Click to collapse
Well, I also have a lot of apps and games, but for me the added stability is totally worth it.
Especially since there's a café providing fast and free wifi near my office
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Broken Puzzles said:
Well doing this just seems alot more effort if you have alot of apps and games and why alot of people won't do this. I mean I have 70 apps/games installed so having to manually install all of them again is just to much effort.
Click to expand...
Click to collapse
If you didn't want to install again all your apps one by one just backup your apps with titanium backup pro and then restore ONLY the apps after doing pristine route.
For me the pro version of titanium backup will automate the installation so just leave your phone after restoring from titanium backup cause it will automagically install all your backed up apps without you having to select it one by one.
And don't restore the apps data because it will ruins your halfway through pristine route.
Sent from my GT-I8150 using Xparent ICS Tapatalk 2
reddvilzz said:
If you didn't want to install again all your apps one by one just backup your apps with titanium backup pro and then restore ONLY the apps after doing pristine route.
For me the pro version of titanium backup will automate the installation so just leave your phone after restoring from titanium backup cause it will automagically install all your backed up apps without you having to select it one by one.
And don't restore the apps data because it will ruins your halfway through pristine route.
Sent from my GT-I8150 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Well... *most* .apk's *should* be safe...
But, considering that Play Store *can* detect what's your OS and *does* offer apps based on your OS, there's a possibility that the .apk has been optimized for your (previous) OS's generation (e.g., GB or ICS or JB). If you stick with the same generation, in general there shouldn't be any problems. But if you change generations, there *might* be problems.
I decided that it's better to be careful than sorry, so I don't restore any apps, even without attached data
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
pepoluan said:
Well, I also have a lot of apps and games, but for me the added stability is totally worth it.
Especially since there's a café providing fast and free wifi near my office
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Click to expand...
Click to collapse
Thats weird since the stability is the same after factory reset your phone 5 times before flashing anything new and restore from Titanium backup. Also I don't know if you see the flaw in your method especially if you play alot of games and thats if you only reinstall the apk and not the data you have to start all over again and let me tell you that pisses off any gamer when it happens. Not just on a phone but on anything but just saying.
reddvilzz said:
If you didn't want to install again all your apps one by one just backup your apps with titanium backup pro and then restore ONLY the apps after doing pristine route.
For me the pro version of titanium backup will automate the installation so just leave your phone after restoring from titanium backup cause it will automagically install all your backed up apps without you having to select it one by one.
And don't restore the apps data because it will ruins your halfway through pristine route.
Sent from my GT-I8150 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I do use titanium backup to restore all my apps but I was just pointing out that while this method is good and has a possibility of making the ROM more stable it does provide more problems like I said above if you are an avid gamer and losing all your save data and having to start again will drive you insane.
Broken Puzzles said:
Thats weird since the stability is the same after factory reset your phone 5 times before flashing anything new and restore from Titanium backup.
Click to expand...
Click to collapse
Factory reset 5 times?? What's the point? Since a single factory reset already means a reformatting of your partition...
Your flash memory is not like an overly-dirty carpet that needs to be shampooed and vacuumed several times before all the grime comes out of it. One format -- done. Nothing left.
I'm just pointing out the fact: Many problems that many experienced when they flashed CM9 -- did not happen to me. Ever. And I *strongly* suspect that leftover bits (settings, incompatible code, etc.) is the culprit.
Broken Puzzles said:
Also I don't know if you see the flaw in your method especially if you play alot of games and thats if you only reinstall the apk and not the data you have to start all over again and let me tell you that pisses off any gamer when it happens. Not just on a phone but on anything but just saying.
Click to expand...
Click to collapse
That is a flaw that I'm perfectly capable of living with.
As you note, in the thread's title, I'm not claiming of something along the lines of: "Want your CM9 to be stable? This is the way!!1!one!!eleven". I use a simple title of "Going Pristine: What, Why, How".
The onus lies on the viewer of this thread, whether they can live with the consequences or not.\
Broken Puzzles said:
I do use titanium backup to restore all my apps but I was just pointing out that while this method is good and has a possibility of making the ROM more stable it does provide more problems like I said above if you are an avid gamer and losing all your save data and having to start again will drive you insane.
Click to expand...
Click to collapse
For me -- and other non-gamers, or non-avid gamers -- losing save data is not a 'problem'. An 'annoyance', for sure, but not 'problem'.
Again, I am not forcing my methods on you or other W users here. I'm just stating the fact: 1) What is meant by 'going pristine', 2) Why 'going pristine' is good, and 3) How to 'go pristine'.
That said...
I understand your concerns, and I'll edit my first posting to warn avid gamers that they will go insane :cyclops:
pepoluan said:
Factory reset 5 times?? What's the point? Since a single factory reset already means a reformatting of your partition...
Your flash memory is not like an overly-dirty carpet that needs to be shampooed and vacuumed several times before all the grime comes out of it. One format -- done. Nothing left.
I'm just pointing out the fact: Many problems that many experienced when they flashed CM9 -- did not happen to me. Ever. And I *strongly* suspect that leftover bits (settings, incompatible code, etc.) is the culprit.
Click to expand...
Click to collapse
Well I had problems in the past with only 1 factory reset as some left over stuff from the old rom was carried over to the new one so I do that just in case and it cleared up the problems I was having.
That is a flaw that I'm perfectly capable of living with.
As you note, in the thread's title, I'm not claiming of something along the lines of: "Want your CM9 to be stable? This is the way!!1!one!!eleven". I use a simple title of "Going Pristine: What, Why, How".
The onus lies on the viewer of this thread, whether they can live with the consequences or not.\
Click to expand...
Click to collapse
Not saying your not fine with that flaw but just pointing out that while your method is best suited to someone not using their phone for its entertainment features but more serious stuff.
For me -- and other non-gamers, or non-avid gamers -- losing save data is not a 'problem'. An 'annoyance', for sure, but not 'problem'.
Again, I am not forcing my methods on you or other W users here. I'm just stating the fact: 1) What is meant by 'going pristine', 2) Why 'going pristine' is good, and 3) How to 'go pristine'.
That said...
I understand your concerns, and I'll edit my first posting to warn avid gamers that they will go insane :cyclops:
Click to expand...
Click to collapse
Well obviously its not a problem if your not a gamer otherwise you would freak when losing your save data, not just on a phone but on any gaming device.
Not saying your forcing others to do this but again just pointing out that unless you are more of a casual user of your phone and don't really bother with gaming then this method is great otherwise like me you are going to just restore all your apps with data anyway.
Broken Puzzles said:
Well I had problems in the past with only 1 factory reset as some left over stuff from the old rom was carried over to the new one so I do that just in case and it cleared up the problems I was having.
Click to expand...
Click to collapse
Ah, you mean doing a factory reset after flashing the ROM?
I see. That might help... but since the non-resetted portion of your phone (SD cards) still contain leftover bits from the previous ROM, there is a possibility of additional problems. Which will lead to yet-another-factory-reset, ad nauseam (or at least until it's stable enough).
I personally prefer having it started out stable, then adding bits and pieces until it becomes unstable... easier to troubleshoot which part is the culprit
Broken Puzzles said:
Well obviously its not a problem if your not a gamer otherwise you would freak when losing your save data, not just on a phone but on any gaming device.
Not saying your forcing others to do this but again just pointing out that unless you are more of a casual user of your phone and don't really bother with gaming then this method is great otherwise like me you are going to just restore all your apps with data anyway.
Click to expand...
Click to collapse
Point taken. :good:
I've edited the OP to more clearly indicate some (potential) drawbacks in a (hopefully) humorous way
Is link2sd still work in our phone? I read somewhere that link2sd never work with cmw 6. Even myself see a wierd note when I boot into recovery after flashing link2sd.
Another question, please give me a reason why I use ext2 compare to ext3/4? I search the net but I only found speed for ext2 and data loss prevention and stability in ext3/4. I wonder why if there's any benefit specifically in our phone.
Thank you...
Sent from my GT-I8150 using Tapatalk 2
vhick said:
Is link2sd still work in our phone? I read somewhere that link2sd never work with cmw 6. Even myself see a wierd note when I boot into recovery after flashing link2sd.
Click to expand...
Click to collapse
Yes, it still works.
The 'weird' note that you saw must have been CWM's warning that the ROM *seems* to want to install a Recovery that will overwrite CWM.
Just ignore it. Choose 'No' for the answer (that is, just press the Home button to execute the first answer, which should be 'No' IIRC).
CWM shows the warning because the method used by Link2SD to initialize the 2nd partition hooks directly into a known method of restoring Recovery.
vhick said:
Another question, please give me a reason why I use ext2 compare to ext3/4? I search the net but I only found speed for ext2 and data loss prevention and stability in ext3/4. I wonder why if there's any benefit specifically in our phone.
Click to expand...
Click to collapse
Okay, the explanation is technical, please bear with me.
ext3/4 introduce what is known as 'journaling' to prevent inconsistent metadata on unclean interrupted writes. The 'journal' is a region of storage set aside to write a 'log' of metadata changes, circularly. Due to the circular log, the region will be intensively used. No problem on magnetic disks, *big* problem on flash memory due to two factors:
1. Limited number of write cycles. Every update to the circular log shortens the life of the Flash memory extensively.
2. The necessity of wiping a whole block of memory (1 or 4 MB, depends on manufacturer) even if ext3/4 need to overwrite just 1 KB of data. This requires *extremely* expensive read-modify-write cycles. Compounded with the single core we have on the W, this means expensive context switching as writes get stalled and the OS hands over timeslice to other waiting threads.
ext2 has no journal, so it's much more flash-friendly, but if writes (in this case, creation/deletion of files) got interrupted uncleanly, you might lose some data or worse.
However, since Link2SD only put apk files in the 2nd partition, and these apk files are never edited (except on upgrades), the drawback of ext2 is not really applicable (IOW, ext2 is *extremely* suitable for nearly-read-only storage access pattern).
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Hi Pepoluan, hope you don't mind, but I've linked to this thread in my "Rooting, ClockworkMod and Custom ROMs" (sticky) thread....think it will help a lot of people
Sent from my CM10 powered Wonder with Tapatalk 2......it's all good......
keithross39 said:
Hi Pepoluan, hope you don't mind, but I've linked to this thread in my "Rooting, ClockworkMod and Custom ROMs" (sticky) thread....think it will help a lot of people
Sent from my CM10 powered Wonder with Tapatalk 2......it's all good......
Click to expand...
Click to collapse
No problem. In fact, the honor is mine
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
pepoluan said:
Yes, it still works.
The 'weird' note that you saw must have been CWM's warning that the ROM *seems* to want to install a Recovery that will overwrite CWM.
Just ignore it. Choose 'No' for the answer (that is, just press the Home button to execute the first answer, which should be 'No' IIRC).
CWM shows the warning because the method used by Link2SD to initialize the 2nd partition hooks directly into a known method of restoring Recovery.
Okay, the explanation is technical, please bear with me.
ext3/4 introduce what is known as 'journaling' to prevent inconsistent metadata on unclean interrupted writes. The 'journal' is a region of storage set aside to write a 'log' of metadata changes, circularly. Due to the circular log, the region will be intensively used. No problem on magnetic disks, *big* problem on flash memory due to two factors:
1. Limited number of write cycles. Every update to the circular log shortens the life of the Flash memory extensively.
2. The necessity of wiping a whole block of memory (1 or 4 MB, depends on manufacturer) even if ext3/4 need to overwrite just 1 KB of data. This requires *extremely* expensive read-modify-write cycles. Compounded with the single core we have on the W, this means expensive context switching as writes get stalled and the OS hands over timeslice to other waiting threads.
ext2 has no journal, so it's much more flash-friendly, but if writes (in this case, creation/deletion of files) got interrupted uncleanly, you might lose some data or worse.
However, since Link2SD only put apk files in the 2nd partition, and these apk files are never edited (except on upgrades), the drawback of ext2 is not really applicable (IOW, ext2 is *extremely* suitable for nearly-read-only storage access pattern).
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Click to expand...
Click to collapse
For long searching....at last I found the solution! Kudos!
Thank you so much, and its clearly now, specially using link2sd and understanding ext2/3/4 filesystem
sorry for the noob question but y should i have 2 partitions on my sdcard and wts the use of the second partition (ext2) and if i have a 32 GB sdcard wt will be the best partitioning for it (how much for the fat32 and for the ext2)

Categories

Resources