Hi all,
Sorry if this is a easy one, but im having a bit of a day and cant work out how to sort this (I swear ive had this problem before but cant remember how or if I fixed it).
When I press keys like fn and Q (to get @) I get ! instead.
Ive looked around and it seems that I can fix this by adjusting the default.txt file which ive tried and hasnt worked.
Id rather not do a reinstall.
Thanks
easy
in default.txt
look for key you should set it to one i think
XCougar said:
Hi all,
Sorry if this is a easy one, but im having a bit of a day and cant work out how to sort this (I swear ive had this problem before but cant remember how or if I fixed it).
When I press keys like fn and Q (to get @) I get ! instead.
Ive looked around and it seems that I can fix this by adjusting the default.txt file which ive tried and hasnt worked.
Id rather not do a reinstall.
Thanks
Click to expand...
Click to collapse
add what's between the ' (if it's not already there):
Code:
'board-kaiser-keypad.atttilt=0' normal
'board-kaiser-keypad.atttilt=1' AT&T tilt
'board-kaiser-keypad.atttilt=2' Nordic (Swedish, Norwegian, Danish, Finnish)
'board-kaiser-keypad.atttilt=3' azerty (French)
'board-kaiser-keypad.atttilt=4' qwertz (German)
Hi, ive tried this and it doesnt seem to work. I am editing the correct default.txt? Its in andboot?
I cant work out where to change it to 0, do I add it at the beginning by adding set board-kaiser-keypad-atttilt ?
Getting more confused. =S
XCougar said:
Hi, ive tried this and it doesnt seem to work. I am editing the correct default.txt? Its in andboot?
I cant work out where to change it to 0, do I add it at the beginning by adding set board-kaiser-keypad-atttilt ?
Getting more confused. =S
Click to expand...
Click to collapse
post your default.txt
loserskater said:
post your default.txt
Click to expand...
Click to collapse
As attached, many thanks.
Right at the end of the default.txt the line
Code:
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-htckaiser.panel_type=1 board-kaiser-keypad.atttilt=0 hw3d.version=1"
boot
Since your default.txt says board-kaiser-keypad.atttilt=0 change that to board-kaiser-keypad.atttilt=1
(looks like you got a tilt keyboard version, instead of the 'normal' one)
zenity said:
Right at the end of the default.txt the line
Code:
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-htckaiser.panel_type=1 board-kaiser-keypad.atttilt=0 hw3d.version=1"
boot
Since your default.txt says board-kaiser-keypad.atttilt=0 change that to board-kaiser-keypad.atttilt=1
(looks like you got a tilt keyboard version, instead of the 'normal' one)
Click to expand...
Click to collapse
Still doesnt work right =(
zenity said:
Right at the end of the default.txt the line
Code:
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-htckaiser.panel_type=1 board-kaiser-keypad.atttilt=0 hw3d.version=1"
boot
Since your default.txt says board-kaiser-keypad.atttilt=0 change that to board-kaiser-keypad.atttilt=1
(looks like you got a tilt keyboard version, instead of the 'normal' one)
Click to expand...
Click to collapse
I think he has the "normal" keymapping as he's trying to get @ with fn + q.
so it should be 'board-kaiser-keypad.atttilt=0'.
Just to make sure, you have a folder called andboot on your sd? and there's only one default.txt inside? if so and you're still getting problems. Try to wipe the sd and start over. You should only have androidinstall.tar, initrd.gz, default.txt, haret.exe, and zImage inside the andboot folder.
or try this default.txt
loserskater said:
I think he has the "normal" keymapping as he's trying to get @ with fn + q.
so it should be 'board-kaiser-keypad.atttilt=0'.
Just to make sure, you have a folder called andboot on your sd? and there's only one default.txt inside? if so and you're still getting problems. Try to wipe the sd and start over. You should only have androidinstall.tar, initrd.gz, default.txt, haret.exe, and zImage inside the andboot folder.
or try this default.txt
Click to expand...
Click to collapse
Hi, thanks for putting up with me, there is only one default.txt in a folder called andboot on my sd card.
I tried making the changes as well as using the default.txt you supplied.
Something isnt right here as its not working, my android is installed to the sd card, so it has system.img etc, does this make a difference?
I dont understand what im doing wrong, im not an expert on Android, but I do work in IT support so im not a complete idiot, lol.
Thanks
XCougar said:
Hi, thanks for putting up with me, there is only one default.txt in a folder called andboot on my sd card.
I tried making the changes as well as using the default.txt you supplied.
Something isnt right here as its not working, my android is installed to the sd card, so it has system.img etc, does this make a difference?
I dont understand what im doing wrong, im not an expert on Android, but I do work in IT support so im not a complete idiot, lol.
Thanks
Click to expand...
Click to collapse
Only thing I would suggest doing is starting completely over. Wipe your sd card and start with a fresh andboot folder and install a fresh system. If that doesn't work, then I am out of options.
Ok I did a complete reinstall to the device itself rather then on the sd card.
It worked but only for a while, it then changed back to the wrong key mapping.
I did this reinstall along with another Kaiser, both with same OS, same setup etc, only difference is the one that has "changed" back has a sim in it.
I tried looking for a default.txt but there isnt one? Does one not exist for direct installs to Kaiser?
I am really confused.
Thanks,
XCougar said:
Ok I did a complete reinstall to the device itself rather then on the sd card.
It worked but only for a while, it then changed back to the wrong key mapping.
I did this reinstall along with another Kaiser, both with same OS, same setup etc, only difference is the one that has "changed" back has a sim in it.
I tried looking for a default.txt but there isnt one? Does one not exist for direct installs to Kaiser?
I am really confused.
Thanks,
Click to expand...
Click to collapse
If it's a nand install there is only the nbh (which is flashed to the phone) and the androidinstall which is installed to the internal memory. the default.txt just told haret what to do, and since you're not using haret, no need for a default.txt. When you install the system again, try going to Setting>Language & keyboard and uncheck Touch Input. I've had issues where capital letters weren't working, etc. and that solved it so maybe it goes beyond that. Worth a shot.
Related
Theoretically, this method eliminates the need for using GParted or any Linux Ubuntu to install Neopeek android ports (or XDandroid if babijoee decides release Ext2 ) Partition within Windows.
>> http://www.youtube.com/watch?v=oyO6DOS1leQ << Watch in 720p please
Recording program used: Camstudio
Partitioning program used: MiniTool Partition Wizard Home Edition
Operating system: Windows 7
Partitioning tool >>http://www.partitionwizard.com/free-partition-manager.html <<
If I did anything wrong such as partitioning as "primary" instead of "logical" please tell me...
I have also found a program (shareware) that can open, add files, and recompress tar.gz files (especially androidinstall.tar.gz) I have tried using 7-zip, Win-Zip, and Win-Rar to do this but Winrar and Winzip will not allow me to do thos. 7-zip just gives me a memory allocation error.
Normally, you would have to install .apk files one by one which is time consuming but by adding the apk files you want to install to the directory /sdcard/npkinstall/androidinstall.tar.gz/data/apps , you can save time and it will automatically install it when you run install.exe or when you first install a neopeek android port onto your device.
The program name is "PowerArchiver"
http://www.powerarchiver.com/ <<the official website. It gives you a 30 day trial, sort of like winrar but better
A video to demonstrate the process of installing neopeek builds..
http://www.youtube.com/watch?v=ArWYwjKEACo
I am going to use this video on my site if you don't mind!?!? Some users still have problems to get an EXT2 partition working! Especially windows users have this kind of problems! Anyway thank you for sharing this. Great work!
e334 said:
I have also found a program (shareware) that can open, add files, and recompress tar.gz files (especially androidinstall.tar.gz) I have tried using 7-zip, Win-Zip, and Win-Rar to do this but Winrar and Winzip will not allow me to do thos. 7-zip just gives me a memory allocation error.
Normally, you would have to install .apk files one by one which is time consuming but by adding the apk files you want to install to the directory /sdcard/npkinstall/androidinstall.tar.gz/data/apps , you can save time and it will automatically install it when you run install.exe or when you first install a neopeek android port onto your device.
The program name is "PowerArchiver"
http://www.powerarchiver.com/ <<the official website. It gives you a 30 day trial, sort of like winrar but better
Click to expand...
Click to collapse
I could add apk into the tar.gz with total commander with installed bzip plugin.
i didnt try to install the new androidinstall, but next time i'll add some apps before installing.
I haven't tried total commander for PC with the bzip plugin but I'm sure its a better method than using PowerArchiver but it works both ways.
I also tried G-zip but it wasn't very noob friendly.
2 build on same sd card?
hi. is it possible to install both neopeek build ang xdandroid build on same sd card? i am too lazy to clear my sd card each time a new build came out. tq
kazuya87 said:
hi. is it possible to install both neopeek build ang xdandroid build on same sd card? i am too lazy to clear my sd card each time a new build came out. tq
Click to expand...
Click to collapse
Yes, but to my knowledge you can only run one neopeek build.
I basically have a folder called "Androids" and then I have several builds in their own folders. You just have to adjust the startup.txt in each to reflect the folder location.
Oh and if you're having problems dual booting windows mobile and neopeek builds with GEN.Y dual boot (not dual booting 2 android builds though) follow this link..
http://www.neopeek.com/en/forum/12-...EODual-Boot-Neopeeks-Android-Ports-by-Mohamad
arrrghhh said:
Yes, but to my knowledge you can only run one neopeek build.
I basically have a folder called "Androids" and then I have several builds in their own folders. You just have to adjust the startup.txt in each to reflect the folder location.
Click to expand...
Click to collapse
did u mean by adding rel_path=XXXXXXXX on the startup.txt? i will give it a try to store neopeek build and xdandroid build on same sd card this way.
by the way, i already dual booting my winmo and android but i just can't resist the temptation to try latest android build by xandroid and noepeek. they both awesome
kazuya87 said:
did u mean by adding rel_path=XXXXXXXX on the startup.txt?
Click to expand...
Click to collapse
Yes, that is correct.
kazuya87 said:
did u mean by adding rel_path=XXXXXXXX on the startup.txt?
Click to expand...
Click to collapse
can someone elaborate on this, for a andn00b?
benjamminzIS said:
can someone elaborate on this, for a andn00b?
Click to expand...
Click to collapse
You add "rel_path=path/to/android" to the cmdline section... This would be if the build was 3 folders deep from the root. If you just have Android say in a folder 'andboot' off of the root of the SD, your statement would read "rel_path=andboot" - make sense?
You also realize this has absolutely nothing to do with the builds that require an ext2 partition right? It's just a way to organize multiple builds of Android, but only the "normal" builds that don't require an ext2 partition.
How about the 8 gigabyte sd memory?
I understand 2G sd rom format, but when I format 8G sd as you showen with my own size, android phone could not distinguish it exactly. Could you explain about the 8G sd card?
necafe said:
I understand 2G sd rom format, but when I format 8G sd as you showen with my own size, android phone could not distinguish it exactly. Could you explain about the 8G sd card?
Click to expand...
Click to collapse
From what i know on the sd card there must be 3 partition:ext2 and swap have to be always the same size (EXT2: about 350 mb and SWAP: 64 mb) and the fat32 one has to be the free space should be something like 6.5-7gb on 8 gb card,
What problem do you experience?
Added, how to change keymaps under linux
e334 said:
Added, how to change keymaps under linux
Click to expand...
Click to collapse
Great! Thanks e334, updating rootfs.img in Neopeek's ROMs should now be easier with your how to guide.
Do you think it should deserve a new thread instead of using this "howto format ..." thread? If I may, would suggest something like [Howto] Update rootfs.img in Neopeek ROMs. "Older ROMs" do not apply to XDAndroid ROMs because updating those even if older is straightforward.
Ok.. I will do that then..
thanks! mod may now delete off-topic post's from this thread ... including this & my previous post.
STARTUP.TXT File
set ramsize 0x8000000
set ramaddr 0x10000000
set mtype 2006
set FBDURINGBOOT 0
set cmdline "root=/dev/mmcblk0p2 init=/init rootwait rw rootdelay=3 console=tty0 rootdelay=3 fbcon=rotate:2 ro.sf.hwrotation=180 lcd.density=240 msmvkeyb_toggle=off msmts_calib=0x0366.0x04b.0x0c8.0x038e acpuclock.oc_freq_khz=600000 pmem.extra=1 no_console_suspend clock-7x00.mddi=0xa51 physkeyboard=kovsq hw3d.force=1"
boot
i boot up android and when i reset i cant boot it up again can anyone help
Hey,
I had the same porblem I think? From what I gather u run xda android reset phone and when u try to reload it, it says something like "can't find default.txt." if that is the case your startup.txt is corrupt. What I did was format SDcard, do a fresh install and from there create a new folder and copy and paste the startup.txt in there. If it happens again just paste it back in the root directory. Oh yea, to tell if its a bad startup.txt the one in root will be 0bytes.
Hope this helps,
Lord Craigus
Sent from my MSM using XDA App
The fix in the post above works like a charm (I originally saw it in the Project Android thread). It also helps to copy a version of the startup.txt file, rename it default.txt, and move it to the andboot folder. If the error comes up again, just hit "run" and it will use the default.txt instead of startup.txt.
Also, try to have a thread title which is more descriptive of your isse/question.
redpoint73 said:
The fix in the post above works like a charm (I originally saw it in the Project Android thread). It also helps to copy a version of the startup.txt file, rename it default.txt, and move it to the andboot folder. If the error comes up again, just hit "run" and it will use the default.txt instead of startup.txt.
Also, try to have a thread title which is more descriptive of your isse/question.
Click to expand...
Click to collapse
This is the fix that I recommend. It requires less copy/pasting.
I just started doing the xdandroid (since it was 'finalized' on 9/16), by downloading the cab, and installing the reference version of the package.
Everything installs and runs fine. The first time. After a graceful shut-down, and re-starting, I learn that the startup.txt file is 0 bytes -- empty! So, Android won't boot.
Why is my startup.txt continually being modified and cleared?
Any info appreciated.
Thx.
Jon
I have the same Problem...
Did you guys search? If I search in the android thread on "0 bytes" I get 20 results. It's a bug of the startup utility. Don't use it or rename startup.txt to default.txt. Maybe putting the startup.txt to read only should work to.
Best option: DON'T USE MGJDROIDUTIL!!!
Also, for you cab peoples - it uses this by default - use haret.exe!!!
i had the same prob. it goes to haret and if u click run it will say it cant find default text. uninstall android. delete all files in andboot folder. reinstall. copy and paste the "startup.txt" file to the same folder. rename it "default.txt" or just "default."
the same thing will happen to the startup.txt but the default.txt will always work. you just have to hit run when it gets to haret.
I had the same issue, the problem only seems to occur when you check/uncheck the Hardware 3D Box.
starmena said:
I had the same issue, the problem only seems to occur when you check/uncheck the Hardware 3D Box.
Click to expand...
Click to collapse
Dude... it's MGJDroidUtil that's causing the issue. I hear there's an update coming, but for the time being
DON'T USE IT!!!!!!!!!
Sorry I had to get forceful with the text, but it seems some aren't getting the point...
Lol relax, I've learned that the hard way. I just wanted to explain to these guys my side of the symptom and what I notice that seems to have caused the problem. I agree with you though.
I do not even know MGJDroidUtil, but I have the same issue. It happens along side with SD card corruption (file000.chk)
sukru said:
I do not even know MGJDroidUtil, but I have the same issue. It happens along side with SD card corruption (file000.chk)
Click to expand...
Click to collapse
Are you using the cab install & using that shortcut it put in your start menu? Then you are using MGJDroidUtil.
uncleswoop said:
i had the same prob. it goes to haret and if u click run it will say it cant find default text. uninstall android. delete all files in andboot folder. reinstall. copy and paste the "startup.txt" file to the same folder. rename it "default.txt" or just "default."
the same thing will happen to the startup.txt but the default.txt will always work. you just have to hit run when it gets to haret.
Click to expand...
Click to collapse
this will fix the problem. lol THE ANSWER IS HERE!!!
uncleswoop said:
this will fix the problem. lol THE ANSWER IS HERE!!!
Click to expand...
Click to collapse
Jesus why can't you just not use the MGJDroidUtil?!? I'm not sure why that's so difficult. If you don't use it, it won't screw up your startup.
I had the same issues. What I did is after installing it go into file explorer and long press haret.exe and add it to programs and set it on your home screen as the link. )
There is a new startup tool, use that. Delete the old one.
arrrghhh said:
Are you using the cab install & using that shortcut it put in your start menu? Then you are using MGJDroidUtil.
Click to expand...
Click to collapse
Interesting. I've always used the CAB install. Shall I remove the CAB and go with the RAR?
sukru said:
Interesting. I've always used the CAB install. Shall I remove the CAB and go with the RAR?
Click to expand...
Click to collapse
I would, just because then you get a better feel of what's really happening. I installed the cab for the first time last night... that thing is an atrocity.
At any rate, MGJDroidUtil was also updated, so you should be safe using it again - assuming you're using the newly updated version that is.
hi there i got the new build 28-9 and i got the problem when i want to boot it...its says storagecard/andboot directory does not exist...while its exist... someone told me to:
Startup.txt, in the cmdline section. Don't use the startup utility (MGJDroidUtil) if you edit the startup manually tho. It'll blast out whatever you put in there.
but i dont know where the Startup.txt is..in my sd card i been searching but no results and i got a gsm touch pro 2... well maybe i should delete everything again...are these FSCK0000.REC files also from this builds?cuase i didnt delete that..i only deleted the andboot and 100android(dcim) files
peruwan said:
hi there i got the new build 28-9 and i got the problem when i want to boot it...its says storagecard/andboot directory does not exist...while its exist... someone told me to:
Startup.txt, in the cmdline section. Don't use the startup utility (MGJDroidUtil) if you edit the startup manually tho. It'll blast out whatever you put in there.
but i dont know where the Startup.txt is..in my sd card i been searching but no results and i got a gsm touch pro 2... well maybe i should delete everything again...are these FSCK0000.REC files also from this builds?cuase i didnt delete that..i only deleted the andboot and 100android(dcim) files
Click to expand...
Click to collapse
Yes, the .rec files are from the build. You can put an entry in your froyo.user.conf that deletes them for you.
Also, you can't find your startup.txt...? How are you running Android, it should be where haret.exe is!
its after you install and load android. after exiting android and returning to winmo, somewhere along the lines startup text gets deleted. for what reason? i know not..
hey atleast it teaches us workarounds lol
ye i know but i could find that file thats why i think it didnt work this time for me
is com.handcent.nextsms-2.9.29 a android file? and EncFiltLog to?
tnx cheers..btw im just gonna install it all over again
i have the sprint htc touch pro 2, and when i go to file exploer and boot to the haret, when i click it a screen that says haret version 0.5.2 appears. then a box that says default.txt and run. soon as i hit run. i get a error that says please set start of ram (Ramaddr) did i not instal somethin right please help
Sounds like your startup.txt is messed up or not present. Not knowing who your provider is, or what exact phone you have means it's impossible for me to post one that'll work for you.
Please read the FAQ and make sure your startup.txt is good.
Your startup.txt is corrupt. This happens randomly, and is a known issue. To confirm this, if you go to the andboot folder of your SD card, the file size will be 0 b.
Find the appropriate file on the FAQ (as suggested in the previous reply) and copy to the andboot folder on your SD card:
http://sites.google.com/site/androidport/faq
As a backup, save a copy and name it "default.txt"
where do i find a non currupt startup.txt for the haret file, i have the sprint htc touch pro 2 rhod400, unlocked to simple mobile,
dazzgrier said:
where do i find a non currupt startup.txt for the haret file, i have the sprint htc touch pro 2 rhod400, unlocked to simple mobile,
Click to expand...
Click to collapse
Did you even READ the FAQ!?!?
See the section, Startup.txt Database. Oy ve.
dazzgrier said:
where do i find a non currupt startup.txt for the haret file, i have the sprint htc touch pro 2 rhod400, unlocked to simple mobile,
Click to expand...
Click to collapse
Probably by following the link in the post right above yours...
Haret was running fine then for some reason it doesnt want to run anymore, it just says "failed to load file /storage card/XDAndroid/initrd.gzset. I tried deleting the initrd file that i have in my sd card then replace it with the FRX07.1 bundle initrd but it still doesnt work
x12CHRIS18x said:
Haret was running fine then for some reason it doesnt want to run anymore, it just says "failed to load file /storage card/XDAndroid/initrd.gzset. I tried deleting the initrd file that i have in my sd card then replace it with the FRX07.1 bundle initrd but it still doesnt work
Click to expand...
Click to collapse
Is the file named initrd.gz or initrd.gzset...?
Might want to delete everything but your startup.txt, data.img and ts-calibration. Replace everything else from the bundle. Re-download the entire bundle perhaps.
x12CHRIS18x said:
Haret was running fine then for some reason it doesnt want to run anymore, it just says "failed to load file /storage card/XDAndroid/initrd.gzset. I tried deleting the initrd file that i have in my sd card then replace it with the FRX07.1 bundle initrd but it still doesnt work
Click to expand...
Click to collapse
check your register if u use a programm , under lok.machine> software > check if your android has still the right path, otherwise you need to replace your start txt
N_Wolve said:
check your register if u use a programm , under lok.machine> software > check if your android has still the right path, otherwise you need to replace your start txt
Click to expand...
Click to collapse
I already tried replacing my startup.txt, it still didnt want to work
arrrghhh said:
Is the file named initrd.gz or initrd.gzset...?
Might want to delete everything but your startup.txt, data.img and ts-calibration. Replace everything else from the bundle. Re-download the entire bundle perhaps.
Click to expand...
Click to collapse
It said initrd.gzset
x12CHRIS18x said:
It said initrd.gzset
Click to expand...
Click to collapse
Did you read my post, or just skim it...
I didn't ask what the error said, I asked what the file was named. It should be initrd.gz. Try my other suggestion if that file is named correctly...
arrrghhh said:
Did you read my post, or just skim it...
I didn't ask what the error said, I asked what the file was named. It should be initrd.gz. Try my other suggestion if that file is named correctly...
Click to expand...
Click to collapse
I already tried it, it still doesnt work
x12CHRIS18x said:
I already tried it, it still doesnt work
Click to expand...
Click to collapse
K, if you won't provide more info or be more verbose, I can't help you any further.
Seriously. If starting from square one doesn't fix the problem, there's no square 0. Format the card, start completely over - doesn't work? Then I don't know how it was ever working .
arrrghhh said:
K, if you won't provide more info or be more verbose, I can't help you any further.
Seriously. If starting from square one doesn't fix the problem, there's no square 0. Format the card, start completely over - doesn't work? Then I don't know how it was ever working .
Click to expand...
Click to collapse
It works but it freezes every time I run haret
x12CHRIS18x said:
It works but it freezes every time I run haret
Click to expand...
Click to collapse
Then I would analyze WinMo. There have been some off the wall configurations in WinMo that have caused issues with HaRET recognizing the device.
arrrghhh said:
Then I would analyze WinMo. There have been some off the wall configurations in WinMo that have caused issues with HaRET recognizing the device.
Click to expand...
Click to collapse
Never mind I fixed it. It was some commands in the froyo.user.conf that was messed up
x12CHRIS18x said:
Never mind I fixed it. It was some commands in the froyo.user.conf that was messed up
Click to expand...
Click to collapse
Heh, so you didn't really follow my directions... But glad you found the culprit.
arrrghhh said:
Might want to delete everything but your startup.txt, data.img and ts-calibration. Replace everything else from the bundle. Re-download the entire bundle perhaps.
Click to expand...
Click to collapse