- Question: Suppose I want to try another ROM which supports ext4. Can I do a Nandroid restore to restore my Data2SD based StarBurst, or is there anything else? You can simply do a Nandroid restore, provided Data2SD was working for you previously. Nothing more needs to be done
- Question: How do I do an Alpharev S-OFF when I have StarBurst installed?
- Do a complete Nandroid backup from Recovery (This will backup your StarBurst Data2SD configuration)
- Wipe everything.
- Install StarBurst Main Rom
- do not flash the Data2SD installer.
- Boot into Android
- Boot PC with Alpharev ISO
- Alpharev should work perfectly now.
- Once you have S-OFF, go back to recovery and Nandroid restore the things you backed up
- Question: Which Alpharev Hboot do I need for StarBurst? The Bravo Stock 1.8 250M 40M 147M
- Question: I’ve installed StarBurst recently and notice force closes of apps all the time.
- These force closes occur when you try to install some apps on your first install and then restart to apply the data2sd installer..You shouldnt do that. That’s why I’ve given clear instructions that immediately after the system stabilizes on first boot and you set up language, you are supposed to reboot and install the Data2SD installer. You shouldnt install any app on first boot, and for safety it is better not to input your google account settings/start the market app, since that might auto-install some app updates!
- If this happens while in a reinstall, you’d have to wipe and do a reinstall from scratch
Question: How do I query and set cpu supply voltages for each frequency through a sysfs interface, while using the snq based kernel?
- Please see snq’s thread for instructions
Question: After installing StarBurst and using it for some time (or after restoring apps), now I am having issues with Market with messages like “packet file is invalid”?
- For improving performance, we have shifted Dalvik-cache of apps to /system in W version Data2SD (The Beta version). This means that even though your ext may be huge, there will still be a practical limit to the number of apps that can be installed. Reason for this is that dalvik-cache becomes full (only happens in W version of Data2SD) and blocks any further installation of new apps. The Market will report errors like “Package file is invalid”. If you have been using W version Data2SD, use the Migrate to Settingfix version X to solve this issue.
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
- This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.
Question: This morning I rebooted my phone via the Reboot menu. After that, my phone went into a loop, displaying the message “Android.process.acore has stopped unexpectedly” with forced closes at startup.
- We’ve always felt that the instant reboot option on it would corrupt the Data2sd config. When you used it, it corrupted the system, which explains all the FCs you’ve seen. A wipe system followed by install: Rom>Reboot>Data2sd installer>Reboot>Recover with Titanium should solve it.
Question: My ROM was working properly till today. Today I’ve started getting a lot of force closes. See Answer above
Question: My language and Wifi settings keep resetting to default every time I reboot.
- When the first time you reboot after ROM install (before Data2sd install), you are supposed to setup everything except Google account username and password. Whatever settings you setup at that time will be saved, anything changed after the Data2sd install will not be saved. This is a feature peculiar to the Stable version of Data2sd code. If you’re using the beta code (W version) or Settingfix version (X version), you will not face this issue
Question: How do I know which version of Data2SD is installed on my system?
- Use the GetLogs Tool to generate an info report. Read that file /sdcard/data2sd.log
Question: What are the differences between the various Data2SD versions?
Question: Recently, after updating to one of the newer versions of StatBurst, I have noticed that system takes a lot of time to wake up from standby
This may be caused by the Rosie patch which adds Helicopter mode Drag and Drop. You can unpatch Rosie by using this flash. Look for Rosie Unpatcher in the Downloads section
Question: Is it safe to delete/wipe my Dalvik-cache?
- Answer is a BIG NO!!
- It’s because StarBurst is deodexed. The kernel has scripts to dexopt it (make optimized dex files from the apks and store it in dalvik-cache; in other words, to create dalvik-cache) in init.rc, which kicks in at first rom install. When we make it data2sd, we modify the location of /data by manual scripts, so the kernel doesnt understand what happened to /data since it mounts it at its default Nand location and finds it missing. Normally when dalvik-cache is deleted, dexopt kicks in and recreates it. In data2sd, kernel ramdisk isnt modified, only the busybox runparts script (init.d/*) is modified, so boot process goes into an infinite bootloop.
So, dont delete Dalvik-cache from recovery. I believe it should be possible to delete it from Titanium, and from adb with the system running (the latter is not recommended though). Since dex is recreated while system is running.
In tiny version, we have shifted the whole of the old /data to ext4 partition, which is mounted as /data at boottime (busybox runparts). Advantage of this version is that the amount of internal storage and number of apps that you can install is virtually limitless. Disadvantage is that System settings (Wifi, language etc) tends to be forgotten/reset at each boot.
In beta version (W), we moved the actual Nand settings data (back) to Nand along with dalvik-cache (after creating the /data mount) so that there is a huge performance boost. We found that there was a disadvantage of running this code on non-deodexed systems, in that that dalvik-cache tends to increase and fill the Nand space so that there is a limit imposed on the absolute number of apps that can be installed. The Market will, when the space is depleted, give an error (Read FAQ 8 above), and block any further app installs even when you apparently seem to have a lot of free space still left on your ext4.
The Settingfix version tends to overcome the app install limit of beta version, while overcoming the “settings forgotten” bug of the stable version. In this, Sibere has left dalvik-cache of apps on sdcard along with the rest of /data, while shifting the settings portion back to Nand. So this is in effect the most advanced version. There is a performance drop however compared to beta version.