Originally Posted by GeologistVegan
1. Edit - The wifi is on, I'm connected to a working network, but there is no traffic. not in the browser or apps. Ideas ?
2. Is there a way to calibrate my screen again without installing everything from the start ?
1. No idea, my issues with wifi are very inconsistent, so I don't think my troubleshooting will help for the moment.
2. If you have everything under the root of the microSD card and your startup.txt doesn't have rel_path=(customnamedfolder)
, then just delete the file called ts-calibration
under root. If not, it should be under the custom named folder
Originally Posted by yaronimo
Here is what I've done:
After Formatting to fat32 and copying the content of both zips I still needed a startup.txt for my blackstone, so I took one from the startup configs of the 2.2V1.6, but I wonder, since android freezes after a few moments, is it the right thing to do?
Here is its content, should it work with this last build?
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=528 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3 msm_blackstone_pad.vibrate=1"
If this is not right then what should be the best "startup.txt" for non-overclocked Blackstone ?
I've tried with the startup.txt that came with the first zip, same results.
You are heading in the right direction but I'm not so sure about the startup.txt Check HERE
for a better collection. If you don't use a subfolder, you will have to remove rel_path=andboot
from the startup.txt as everyone of them has this option. Also, you might want to minimize what extra options you have enable for the initial boot. I don't know why this is happening now. I am noticing the same thing on my end with my device, Fuze/RAPH110. However, I had to sort of troubleshoot the heck out of my process to get a good sucessful boot. What I did was to rename the AndroidApps folder if I had apps I wanted to eventually install (example: ZndroidApps
). I went a step further and removed the extra options
(keeping in mind this is only for the initial boot), such as the andboot option (I took out rel_path=andboot)
NOTE: Be careful when you do this, that you don't remove one of the parenthesis. If you were using one of the startup.txt that included the OC/overclock option, I would take that out as well (just for the initial boot).
NOTE: If you are using an older package, you might want to push everything from the andboot folder to the root
Also, when you are initially booting into Android, DO NOT TOUCH THE SCREEN UNTIL IT ASKS YOU TO
(just until the screen calibration comes up of course) Additionally, I also let it sit a few minutes more after the boot animation and before I actually begin playing around in Android. Keeping in mind the screen will time out on you and possibly SOD/screen of death. So, what I do is touch the top bar/notification bar every so often until I see the date; I tap and hold the bar till I see the date fade in and then let go. After I decide it should be done doing whatever it was doing, (still initial boot) I go ahead and turn off Auto-Screen rotation, All animations and I enable auto-dim after setting it to the lowest level. All of these options you can get to under: Settings - Display. Then I power it down and rename the folder ZndroidApps
This should help those of you who are experiencing lag issues on initial boot. Keep in mind, you don't have to do this nor should you have to but this is just what I find helpful when I am having one of those troublesome boots!