Related
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
atomiq said:
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
Click to expand...
Click to collapse
not exactly sure....when u tried each cab, did u completely uninstall and delete all traces of each build including the fsck files? alot of times if not, and u try to install a new one, itll stick pick up the old data and mix with the new and cause issues. The one to try thats the easiest is the AOSP. data and service works off tops without doing anything.
try this...whatever cab u got in there..uninstall it...then ...go into file explorer or whatever and delete any and all traces of the previous build. after that, if u have clear temp or clean ram, use that. then soft reset.
get the build cab of ur choice, but id recommend the AOSP for the quickest start. download it to root of storage card which is /storage , not in a folder in storage(example /storage/programs). it has to b in the root. then install. then soft reset. once it boots back up, go to the android icon. press it..then update all the new files for the build b4 ur first boot up. u should see the tab to let u update. after update complete, then press run android...and hopefully any little issues or residual files are gone and u can complete the startup or bootup of android. let us know if that didnt wrk for ya.
ok now boots, and works fine
i'm using AOSP 2.1 updated
EDIT MY INTERNET WORKS NOW, LOL,
I'm having the same exact error on my AT&T Tilt 2 with stock ROM. I downloaded the AOSP into the storage/programs folder of the SD card, installed it to the SD card, then ran the update. After the update, I got the "Failed to mount the SD Card. Cannot Continue" error. I uninstalled the program and got rid of everything ans started from scratch with the same error.
Any idea?
Okay.... I've tried this a few times with no luck. Here is what I have:
AT&T Tilt 2 with stock ROM. I started with a fresh Hard Reset this morning (due to problems with Good Mobile Messaging) and loaded the AOSP file to my micro SD card (\Storage Card\ProjectAndroid 2.1AOSP 042610.cab). I ran a level 3 CleanRAM, then double clicked on the AOSP file on the SD card using TotalCommander. The file asked where to load it to and I chose the SD card. It successfully installed and I did a Soft Reset using the red reset button behind the battery cover.
Once turned back on I go to Start and press Project Android. Once loaded up, I went to Menu and Update. It updated successfully in about 5-10 minutes and I then clicked Run Android. The screen goes black and runs a bunch of script until it gets to this:
Welcome to Vogue Linux
Running an fsck on SD card
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Logical sector size is zero
mount:mounting/dev/block/mmcglkopl on/sdcard failed: Invalid argument
Failed
Failed to mount the SD card. Cannot continue
/bin/shi can't access tty; job control turned off
It then freezes at this point and stays there. I've uninstalled and removed all sources of the files (that I could find) and started from scratch several times and it does the same thing each time.
Is something wrong? Am I missing something simple?
ROM Version: 1.59.502.3 (67150) WWE
Rom date: 09/25/09
Radio Version: 4.48.25.20
Protocol version: 61.39tc.25.30U
is there any other info you need?
i did use this formatter
http://www.megaupload.com/?d=287HD74A
extract, install, open, select your unit, click on option, select full erase ON
let ir run..
this promise to fix this error acording to a forum that i read
outside of XDA, it can also throw that same error if you are using
a SLOW storage card.
pls report what happened so we help other people with the same issue..
The error message is normal. Just ignore it unless the thing wont boot overnight
thebulletfromhell said:
The error message is normal. Just ignore it unless the thing wont boot overnight
Click to expand...
Click to collapse
So just leave it there and let it keep running? I'll give it a try.....
sethjamto said:
So just leave it there and let it keep running? I'll give it a try.....
Click to expand...
Click to collapse
No joy..... it hung up on the same screen that I quoted above for over 5 hours. I soft reset and then uninstalled the software. I guess if I'm destined to have Android, then I'll just go out and buy an Android based phone.....
i guess you didnt tried the FORMATTER that i've posted
anyways
maybe you should wait for the release of HTC VISION
or wait much looooooonger a couple of years for an official android rom
for our poor htc rhodium..
good luck.
I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.
I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.
replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.
I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.
SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers
SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.
I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.
Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs
@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks
I have currently Fat Free Froyo with the only 2.6.32 kernel, I was able to make working with my Kaiser, KAIS130 with DATA on SD Card Partition and SYS on NAND
I configured contacts, added a music player application. Did some settings with ADW Launcher. Then activated wifi, tested it working, openned browser and KABOOOM, phone forces ever application as NOT RESPONDING. So, I just long pressed power button to turn it off and then turn on again. All of the stuff I configured is gone, except the Widgets I manually added on the homescreen.
So my question, in the endo is, How can I get my settings saved and not to lose contacts / installed apps?
My SD Card setup:
870MB Fat32 (for Android install, a number of music files and android apk installers)
520MB ext2
510MB ext2 (no idea on what partition its saving DATA)
Most of the time it goes on the last partition of the SD Card, now if you configured data using atools, then p2 would be partition 2 of the card, and p3 is partition 3.
Never heard of data corruption occuring on the SD Card.
Have you tried restoring your phone back to stock OS (WinMo 6.1)?
If not, try flashing the stock ROM back onto the phone so it flashes the stock radio as well back onto the phone. As long as you don't include KAISDIAG.NBH, the bootloader won't be reflashed even though the flashing process states it's being flashed.
Then reflash the kernel you're using, then reinstall your build.
Also you're stating you can only get one type of 2.6.32 kernel working? Have you tried the latest kernel under the Kernel help thread?
Make sure you use atools to configure the kernel for your kaiser.
Krazy-Killa said:
Most of the time it goes on the last partition of the SD Card, now if you configured data using atools, then p2 would be partition 2 of the card, and p3 is partition 3.
Never heard of data corruption occuring on the SD Card.
Have you tried restoring your phone back to stock OS (WinMo 6.1)?
If not, try flashing the stock ROM back onto the phone so it flashes the stock radio as well back onto the phone. As long as you don't include KAISDIAG.NBH, the bootloader won't be reflashed even though the flashing process states it's being flashed.
Then reflash the kernel you're using, then reinstall your build.
Also you're stating you can only get one type of 2.6.32 kernel working? Have you tried the latest kernel under the Kernel help thread?
Make sure you use atools to configure the kernel for your kaiser.
Click to expand...
Click to collapse
Just recently installed my apps again without any re-formatting. Installed the widgets again. Rebooted. Now its showing everything fine.
Mine kernel is 2.6.32, Panel Type 1, Keyboard type: tytn II, 240x320 (This one is my first attempt in making an nbh and wifi works on it).
This release (Fat free Froyo) is hell slow while opening applications etc. What can be the problem? The previously used Eclair Polymod 2.1D wasnt this much of a turtle.
P.S: When I connected USD, disable debugging mode and enable USB Storage, the button "Turn off USB storage" turns back to "Turn on USB Storage" after 5 seconds. I can't connect my SD Card as USB Storage :/
dark_prince said:
Just recently installed my apps again without any re-formatting. Installed the widgets again. Rebooted. Now its showing everything fine.
Mine kernel is 2.6.32, Panel Type 1, Keyboard type: tytn II, 240x320 (This one is my first attempt in making an nbh and wifi works on it).
This release (Fat free Froyo) is hell slow while opening applications etc. What can be the problem? The previously used Eclair Polymod 2.1D wasnt this much of a turtle.
P.S: When I connected USD, disable debugging mode and enable USB Storage, the button "Turn off USB storage" turns back to "Turn on USB Storage" after 5 seconds. I can't connect my SD Card as USB Storage :/
Click to expand...
Click to collapse
I have that same problem with USB Storage, I found that if I leave Debugging enabled in certain cases, I can enable USB Storage just fine. In Windows, no matter what you do, it won't connect, and in Linux it's still pretty buggy.
You've made your own kernel, sweet! Still trying to get mine to compile, but overall really haven't had time with the holidays, but will start up again this week.
Fat Free Froyo is a pretty decent build, but yes some apps do take awhile to load. I found that Gingerbones build is very stable, at least with my testing. You should give it a try, though it is pretty stripped down, so you might want to grab whatever apps you want and throw them in /system.
Krazy-Killa said:
I have that same problem with USB Storage, I found that if I leave Debugging enabled in certain cases, I can enable USB Storage just fine. In Windows, no matter what you do, it won't connect, and in Linux it's still pretty buggy.
You've made your own kernel, sweet! Still trying to get mine to compile, but overall really haven't had time with the holidays, but will start up again this week.
Fat Free Froyo is a pretty decent build, but yes some apps do take awhile to load. I found that Gingerbones build is very stable, at least with my testing. You should give it a try, though it is pretty stripped down, so you might want to grab whatever apps you want and throw them in /system.
Click to expand...
Click to collapse
Right now on Gingerbones:
Radio version 1.70.19 (I'm sure about that)
Wifi Turn ON = ERROR
Installing Polymod 2.1D and checking if it works with 2.6.32 (though the kernel's tagged as Froyo's)
ALOT OF TEXT ROLLS REGARDING SOME SCHEDULE thingi, idk but hope that everything goes ok
Re-Partitioned SD Card and now Data is on 800Megs and FAT32 is on 900Megs
I loved polymod 2.1D but it had wifi error with 2.6.25
Edit: 2.1D says "Unable to Start wifi"
Back to the one and only Fat free Froyo
Edit3:Again settings are not saved :/ Battery is stuck at 15% (even I kept it connected for more than an hour)
Back to Windows mobile for charging fuss
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D Follow this link if you need an NBH suiting your type. (use the only ones with prefix KAISIMG)
Just for kicks, i tried turning my phone off, taking out the SD card, and turning it back on. holy frig! It loaded the apps (in settings, to clear caches and stuff, force stop if needed), turned off, SO much faster!! Like, warp speed. Compared to the well over a minute with my current class 4 sd card installed... im truly amazed!!
I need one of these like, tomorrow!! lol
The one thing i didnt understand, is that since moving app data to the external SD card isnt actually possible (despite the deceptive "move to SD card" in the app settings)... alot of the apps didnt show their correct icons or names in the app settings menu with my card out. But - even to just take the card out and look at it on the computer, all thats on there is camera photos, wallpapers..... a couple of things in directory bind, but only for 2 apps. well over 2 apps showed the incorrect icon and name. But... why??
ok, so ive since invested in a class 10 sd card...... and i notice no difference with having the phone calculate storage, powering off (the 2 main time wasters) since when i had my class 4 card.....
the only extreme difference is with no card in it.
For all of you who used class 10 SD cards, did it take the storage roughly 3 minutes to calculate (when you keep your caches cleaned out regularly), and the phone over a minute to power down, when you power down or at least restart once a day??
im just wondering if the extreme difference in speed is to be expected. even with the best type of sd card.
Hi
what ROM and Kernel?
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
Hi
what ROM and Kernel?
Click to expand...
Click to collapse
The rom is this one here actually: http://forum.xda-developers.com/showthread.php?t=1994902
Since i was new to the android world and rooting and such (still kind of am), i went with the pure stock version. I had actually decided to use the legit update, but it turned out my "brand new" phone had already been rooted, realized after a couple hours of trying to get it to update the legit way... maybe they had to to carrier unlock it, not sure. I knew for sure once i got into recovery for the first time, that it was already non factory. But, i didnt complain, the phone worked well and had no physical scratches or anything.
The kernel says (im not sure what much of this means):
"3.1.10-I927UCLJ3-CL970642
[email protected] #3
smp preempt thu oct 11 14:00:57 KST 2012"
Im guessing that last line isnt important but i didnt want to leave anything out.
Im not too sure what kernel means, unless referring to corn. Is that an important factor in the speed? Would changing it if needed ruin my whole current rom setup?
Ok so it is more or less stock and rom and kernel are UCLJ3. Thats fine just wanted to be sure. Btw: the whole kernel line is important as one can see the build, builder and build time which all is important to identify.
You can try another kernel without any impact to your ROM as long as it is ICS compatible. You may take a look into sediROM its installer has all available Kernels where you can choose from (v2.0 beta has absolutely all added). You can start sediROM installer and choose to not install the ROM but only modify the kernel. That way you can be sure that all requirements for flashing a new kernel are met (e.g. removing dalvik cache) without loosing data. But be warned i never tested that on pure stock!!
A better way may be to install sediROM and then choose the modify mode instead but I absolutely do not want to force you to choose sediROM !!
Nevertheless flashing sediROM or simply flashing a new kernel only:
As always keep in mind that doing a nandroid backup is essential!!
But back to topic: to be honest I'm not sure about your problem itself. You told that you have slow speed when opening your app drawer in the launcher? The other thing mentioned was calculating storage (I believe you meant those in settings?) and powering down.
Well i have a class 10 card with atm 1 GB free storage and need 10sec for all calculatings (settings). A power off need about 10-30sec and opening my app drawer with 114 apps installed take less than 1 sec.
I use sediROM v2.0 beta.
So you may try flashing a litekernel version. Maybe removing the dalvik cache may help a little, too - at least it will not harm (remove dalvik cache from within recovery).
My recommendation would be - if I were you:
0) backup! /efs and nandroid!
1) remove dalvik cache and /cache
2) if that doesnt help: flash a litekernel
3) if that doesnt help: flash another ROM
-----
Sent from my SGH-I927 using XDA Android mobile app
I do go into recovery regular and clean the regular cache, but never the dalvik cache. Ive read everywhere that people recommend doing that just before formatting and installing a new rom, so ive always thought that the dalvik cache held something important (like user data).
is that something i should be regularly cleaning out too? If so, and i havent for over a year, could that be any part of the issue??
The main 2 spots i notice it very slow is when opening the storage (within settings), and when powering down. the app drawer does open right away, but it does take a while for everything to load up and all app sizes are accurate, probably the same 3ish minutes as when starting from storage.
but other than that its been running great so its weird that only those 2 spots are slower.
Pawprints1986 said:
I do go into recovery regular and clean the regular cache, but never the dalvik cache. Ive read everywhere that people recommend doing that just before formatting and installing a new rom, so ive always thought that the dalvik cache held something important (like user data).
is that something i should be regularly cleaning out too? If so, and i havent for over a year, could that be any part of the issue??
The main 2 spots i notice it very slow is when opening the storage (within settings), and when powering down. the app drawer does open right away, but it does take a while for everything to load up and all app sizes are accurate, probably the same 3ish minutes as when starting from storage.
but other than that its been running great so its weird that only those 2 spots are slower.
Click to expand...
Click to collapse
Cleaning the cache on a regular base will not harm but IMO not doing anything useful.
The dalvik cache does not contain anything important like user data. It is filled when you boot your ROM with let me say "uncompressed" version of all your applications. That means because they are "uncompressed" they will open faster. Removing that cache will only let the ROM re-create that cache and this can solve some problems too. But it is an important thing you ever should do after flashing a kernel. Normally each ROM out there will do that for you, too because there it is needed too of course.
So no you do not need to do that on a regular base Android will update the cache for you (normally). Only when you encounter problems, flashing or upgrading ROM or Kernel.