Related
Everything is working nice for me now, except for missing ÆØÅ, but I guess Ill get used to it.
The os is a bit slow, but meh.
So my I have found answers to my questions, but below are the original ones.
New questions:
Hello again!
Thanks for the information. Big thanks to this wonderful forum, because I can run Android on my phone!
But as I have tested it I have some questions:
1. The wifi is really slow. It feels like I am using Internet through the SIM card, but I am indeed not. (I took out the SIM card to test). And there isn't any problem with our Internet, because it is fast and good on everything else.
Downloaded some older files and the WiFi is working much better now!
2. I got some problems with vertical lines, but after readings some FAQs I found out about a setting. It has worked overnight, but is it permanent?
This problem is solved, haven't experienced any vertical lines after boot fix.
3. I'm not sure if GPS is working, because it take ages to start. Just says loading... loading... etc.
GPS is working, but slow.
4. Since I am from Norway it seems like I have custom physical keyboard. (with ÆØÅ) And because of that all the FN keys are messed up, well except for numbers.But as I read somewhere the default mapping for Tytn II should be FN + Q = @
And that is how my keyboard look now. But it should be FN + Q = ? according to the text on the keyboard and how it worked in WM.
And is there any way to do the same for the Android keyboard?
Anything I can edit without too much hazzle to fix this? Cause its a pain to write texts without the Norwegian letters.
I found a custom kernel and it is working nice (I have asked for a custom build of it so I can have ÆØÅ too, but mapping is good)
Besides that I am SO happy with it! I just love the menus and how its so easy to touch compared to WM.
Original questions:
Code:
Okey, first of all.. this is probably a newbie question and I might have found my answer if I searched for a while.
But as both you and me know, it would've taken me much more time to search and read a bunch of threads than it would be to just simply ask the question.
I am a newbie at the whole ROM and radio business on phones. To be honest I just found out yesterday that it was even possible.
As you might have guessed I want to run Android on my phone. Im going to run it from the microSD card etc.
Well there werent really any problems to download the Android files together with Haret and then put them on the sd card. (If I wasnt able to do that I wouldnt bother.)
The problem is that when trying to run Android from within WM (6.1) it just freezes at full bar with the text "Go Go Go". The whole phone is just frozen and I have to restart it.
Well as I read on the troublehooting guide on "androidonhtc.com" I have to update my radio which then leads me to this website.
Fine so far. The problem is that I do not really want to mess with the phone itself. First I want to know how I can "backup" the radio so if I mess up something while flashing I can easily go back.
Second of all Im not really sure which radio which works with which rom.
I am running the original rom which came with the phone and I do not really want to mess up anything.
Here are the infos I got from the phone:
Rom version: 3.29.409.0 NOR (Yeah, Im from Norway)
Rom date: 05/05/08
Radio version: 1.65.16.25
Protocol version: 25.83.40.02H
The phone is HTC Tytn II running Windows Mobile 6.1
The guide on androidonhtc said that I needed "1.65.24.xx or 1.71.xx.xx"
Can I then use a 1.71.xx even though I have a 1.65.16.25 now?
tl;dr:
I want to know which radio I can use for the phone with the specs above.
The recommended radio for most android builds is 1.71.xx, however it will still run on older radios, but may experience some audio, wifi, bt, gps, and possibly other issues.
If you intend to run from SD card, then this may not be much more than an annoyance, since you can reboot to Winmo at any time, and as a newcomer to android this would have been my advice anyway.
To upgrade the radio is a simple step usually, provided your device is prepared properly.
A prepared device means that is ready and able to be flashed, and this requires HardSPL, ( basically an unlocked bootloader that allows you to flash roms/radios/ splash screens etc).
I recommend reading through the guides and tutorials sticky in the 'main' rom forum: http://forum.xda-developers.com/showthread.php?t=533976
This should give you an understanding of what might be involved in starting to flash your device, and should answer many of your questions about radios, flashing, unlocking, roms and other things you may need to know about before proceeding.
Good luck, and remember, I was once as new as you, and that thread was where I learned all I know about my devices
So if I update to 1.71.09.01 while still using the original ROM, I wont get any big problems?
Or do I have to upgrade the ROM too?
You see.. this stuff is confusing to me. I consider myself a PC geek, but I suck at phones.
The instructions are pretty easy to follow, but its not so easy to know if I'm able to revert the stuff I'm doing.
I want to do as little "damage" to the phone as possible.
Is it necessary to backup the radio which is on the phone now, or do I have to find another radio from here and flash it on?
And one last question. Is there any difference between the original radio on the phone and the radios I'm downloading from here?
cXhristian said:
So if I update to 1.71.09.01 while still using the original ROM, I wont get any big problems?
Or do I have to upgrade the ROM too?
You see.. this stuff is confusing to me. I consider myself a PC geek, but I suck at phones.
The instructions are pretty easy to follow, but its not so easy to know if I'm able to revert the stuff I'm doing.
I want to do as little "damage" to the phone as possible.
Is it necessary to backup the radio which is on the phone now, or do I have to find another radio from here and flash it on?
And one last question. Is there any difference between the original radio on the phone and the radios I'm downloading from here?
Click to expand...
Click to collapse
You don't need to upgrade the ROM. All you need to do is install hardSPL, then install the radio. If you install hardSPL properly, your phone will be almost impossible to brick. It's really the first thing any person should do to their phone when beginning to do modifications. You can't "back up" your radio, but all available radio versions, including the one you currently have, are available HERE. So if you ever want to go back to your original radio, it will always be there. I honestly don't know the difference between the radios, I just know that certain versions are recommended depending on what ROM you are using, for the best signal and least bugs with wifi and bluetooth, as zenity previously mentioned. Hope this helps you some, good luck!
Thanks, thats what I wanted to hear.
The reason why I want to try out other mobile OS and ROMs is that I hate how the menus are so frigging tiny on the WM 6.1
If I'm trying to do stuff fast I always click the wrong button.. And yeah I have lost my stylus.
Anyway, thanks for all the help. After getting some answers and reading some threads I feel ready to update the radio.
cXhristian said:
And one last question. Is there any difference between the original radio on the phone and the radios I'm downloading from here?
Click to expand...
Click to collapse
Basically the higher the radio version number, the newer the radio software, as our devices aged, HTC brought out a number of software updates.
Our network carriers usually have custom ROM's which have a 'matched' radio for best operation, however even these 'matched' radios had small bugs, which were patched by releasing newer radio versions, of which 1.71.xx was the lastest and last official HTC radio for the Kaiser series.
There are also radios from other devices which work with our kaisers, but these are not recommended unless you have a particular need for one of those.
As far as the ability to 'undo' any modifications you make is concerned, it can all be reversed and your device put back the way it was relatively easily, instructions for this are best found on the wiki pages for the kaiser, along with a load of other information about radios, roms, flashing etc.
But unless the reason for not messing with your kaiser is in case you have warranty concerns, then pretty much everything is 'safe' to do, ( there is ALWAYS a risk of a bad flash, or unforseen power cut, but even these are recoverable in all but the most extreme circumstances).
Finally, take everything one step at a time, don't be tempted to rush in and try everything at once, you will make mistakes, you will also learn how to fix them.
As with everything else, remember to backup anything you really cannot afford to lose, get a 128Mb SD card with an HTC ROM on it, and don't panic
Hello again!
Thanks for the information. Big thanks to this wonderful forum, because I can run Android on my phone!
But as I have tested it I have some questions:
1. The wifi is really slow. It feels like I am using Internet through the SIM card, but I am indeed not. (I took out the SIM card to test). And there isn't any problem with our Internet, because it is fast and good on everything else.
2. I got some problems with vertical lines, but after readings some FAQs I found out about a setting. It has worked overnight, but is it permanent?
3. I'm not sure if GPS is working, because it take ages to start. Just says loading... loading... etc.
4. Since I am from Norway it seems like I have custom physical keyboard. (with ÆØÅ) And because of that all the FN keys are messed up, well except for numbers.But as I read somewhere the default mapping for Tytn II should be FN + Q = @
And that is how my keyboard look now. But it should be FN + Q = ? according to the text on the keyboard and how it worked in WM.
And is there any way to do the same for the Android keyboard?
Anything I can edit without too much hazzle to fix this? Cause its a pain to write texts without the Norwegian letters.
Besides that I am SO happy with it! I just love the menus and how its so easy to touch compared to WM.
I'm having the exact reverse, m FN + Q is ?.
If i remember, fn+q='?' means you are using a tilt keymap on a non tilt keyboard, if you are running from nand, try a non-tilt nbh, if you are running from SD theres a setting in default.txt. ( board-kaiser-keypad.atttilt=1 ) if it's set to 1 change it to 0
No, on the nbh i'm using, the tilt keypad layout is set to 0. But I'm back on ext2 now so it isnt a problem anymore.
I'd like to ask those wishing help with troubleshooting to please help us to help you.
When reporting a problem it is useful to get as much information as possible, the more information we have, the easier it is to help.
Is it running from SD or Nand.
What radio version.
What build are you having the problem with.
What kernel/nbh are you using.
If you can, try to post any error messages.
Please try to post your questions in the thread for the build you are having issues with, it's more likely to get noticed there, and other users of that build may have the solution you need.
All this information saves a lot of time, and helps cut down on confusion, especially the SD/Nand part.
I have trouble with signal, it's weak than WM, when I used WM my radio is 1.65, I'm up to 1.71.09.01 and flash Android (NAND menthod) and the signal so weak
So Android support radio 1.65??? I want to back 1.65
I'm using TYTN 2 Kaiser _ WarmDonut version
Another Qs:
Q.How can I use my fone like a modem? I see in Menu have Modem but I don't know how to connect with my PC as a modem
Q.How can I connect to my PC via Wifi ad-hoc? (if available, please guide step by step- because I'm... chicken )
Q.GPS so slow and weak (in Vietnam)
Q.It so hard to power off (It's hang)
Best regard
I had issues with 1.71.xx radios too, and went back to 1.65.21.14 and my signal was good once more.
To change radio, download the radio you wish to use from this thread http://forum.xda-developers.com/showthread.php?t=393182, post 3 has the download links you need.
Once you have it downloaded, rename the ruu_signed.nbh to kaisimg.nbh and copy to SD card, flash using the power+camera method you used to flash the nand nbh, you will not have to reinstall Android when you do this.
The modem in question refers to the gprs modem used for data, it should be possible to use the phone as a modem, but as far as I know this is not working properly yet.
Not sure if you can do this either, I know wifi works for data transmission, but accessing the computer this way with android may not be possible, yet.
Gps problems may depend on which nbh you have installed, some of the more recent nbh's perform better than older ones. I'd recommend Kallt_Kaffes NBH's as I know these are quite good for gps, for me at least. http://forum.xda-developers.com/showthread.php?t=660158, you will need to load the nbh into the editor and set the correct panel type, keyboard, and 3d type, ( donut in your case), then save as kaisimg.nbh and copy to SD and flash using power+camera, again this will not affect your android install.
Power off issues may be nbh related also, however this can still happen anyway, usually pulling out the battery will sort out the reboot issues.
many thank for quick reply, I love Android on my phone
thank you again
I was wondering what steps to take when the android loader gets stuck in a loop, when I install andriod right after install it boots fine but when I try to boot second time, after andriod appears on the bottom of the screen it will go into some kind of loop. I have tried different radios and a different version of hardspl, and a few nbh panels as well as reinstalling the system, any help would greatly appreciated.
Phone: AT&T Branded TILT
OS: Nand w/Incubus Super Froyo Installed
Radio: 1.70.18.02
NBH: kaisimg-panel2-320-tilt-froyo-07-07-10
HardSPL: v3.34.hard
Everything looks fine, although I haven't used that particular build, however bootloops are commonly build or kernel related.
Have you tried other builds? Or is it just this build that does this?
Generally panel type only affects the display on the screen itself, or sometimes problems with sleep mode.
Since you have a froyo kernel installed, maybe you could install this build to see if it helps? http://forum.xda-developers.com/showthread.php?t=724821
Yeah I have tried other Froyo builds and they worked, but I just like the way Super Froyo build is put together. But if it is the build then its is the build. Oh well maybe next release. Ok thank you for your time, guess I will give the GZO build or the one you suggested a try.
Installed the kernel you suggested, it works. It boot looped once, then I cleared the dalvik cache and it booted again after install. I don't know if that is what it is used for, but it worked after that.
It is a awesome build, battery life works correctly, signal is good with radio, and wi-fi works good. But I had one more questions.
1. What is up with live wallpapers, on some builds I have used some work on one build but not the other, I have looked through the forums, but can find no solution for this. Is it because of the amount of RAM in the TILT as I saw somewhere or is there a fix. Even in this build when I try to load a live wallpaper on a couple of them is just stays on wallpaper loading and stay black screen.
I would like to take a minute to thank the people that make this awesome stuff, now my TILT has more current software than my BACKFLIP, so my older phone is now newer than my new phone, and I would also like to thank the people who help others out on this forum, I don't think a lot of people like myself would get anywhere without your help.
Forgot to mention dalvik cache. oops, ah well, you found it anyway
It's another of those occasionally useful things, like fix permissions, I have used it before to fix unusual behaviour, but not tried it on a bootloop.
Live wallpapers are usually pretty buggy at best, it's complicated, memory is one problem, cpu speed another, and 3d handling yet another, some wallpapers work ok, but slow, others just won't, ever. I just delete them before install, along with a few other minor customisations such as deleting a few ringtones and notification sounds, changing boot animations, nothing that affects the core of the build, just personalising a bit
I'm using:
1)incubus's Super Eclair 6.1, with the downgraded settings.apk which enables wifi (another member offered the settings.apk from a previous version (3, I think) as an androidupdate.tar)
2) Currently radio 1.71.09.01 (thinking of switching to 1.65.21.18 to improve reception)
3.) Currently using the latest Dzo kernel for eclair (07-02-2010, I think)
My problem is that my data connection doesn't work (and this has been an issue on just about every release, save for one Froyo install where the data autostarted once, and then I never saw a 2g/3g notification and mobile internet didn't work).
I'm currently in India, and I've used the correct APN settings (they have worked on other phones including Nokias, iPhone, and a USB modem). I've tried asking the question in the SuperEclair vogue thread, but alas, no love. I'd really appreciate if you could help me on this, or at least guide me in the right direction, because android (especially eclair) is too awesome to abandon for this single issue.
By the way, everything else works, Wifi (with the mentioned update), GPS, Voice, and SuperEclair is the fastest that I've found so far.
I have seen a number of issues with data such as this, and i'm afraid none have had a truly satisfying resolution.
However I would try:
Downgrade the radio as planned, this may help, and certainly won't hurt.
Boot to installer, and run fix permissions and clear dalvik cache, this has been known to fix various issues, not certain why yet.
Double check the apn settings, especially the MCC and MCN settings, a lot of online guides seem to miss these two, but they are important.
Not sure where to point you after this, apart from a long trawl through the thread here, however if you do get it resolved please post back, and if not, try another post on it in the build thread, along with the steps you have taken to resolve it, it may convince someone to have a closer look at this issue.
data connection
I too have had this problem after installing a recent froyo build to nand....I had checked no.start data when flashing dzo's latest kernel using nbh editor and had to reset my apn settings. Remember to open your modem utility and press connect twice....this actually starts the connection......Radio type could also be an issue..Ive had good luck with the 165's with 2 different froyo builds....Hope this helps.....
Thanks for the replies! I'm going to try this out (need to recharge the data service on my prepaid) but one thing I did notice was that the MNC/MMC were different that those listed on my providers website. Hopefully this will help.
I have tried to switch on the data using the modem utility, and the utility itself says that data is connected, but it never really worked. In settings, there is an on/off switch for mobile internet, and a mobile internet settings. When I click the on/off switch, then mobile internet just goes gray and does nothing. I'll try to post back to the Super Eclair vogue board, but I think that Incubus might have moved on...
I'll update once I get my gprs service paid up. Again, thanks for the help!
The process com.android.phone has stopped
Those are my first Android experiences, so I`ve got problems .
Phone : Kaiser (TyTN II)
OS : Win Mo 6 Profess (original-not flashed)
Radio : 1.27.15.32
I`m trying to install Android on the SD card, without additional partitioning. I`m currently trying this Android version : Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 gamma [Based on OpenEclair 1.2.2 (XDA thread)]
and using this too : How to run Polymod’s AWESOME 2.1 Eclare Build and Updates (the forum didn`t allow me to post links for the Android versions). I`ve tryed this too : VaniljEclair RLS7c - A fast and stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-07-02] - the same result
I`ve done everything according the instructions... Starting Haret.. Hit D-Pad, Install, clear data... etc. etc... It actually starts to install... and everything seems fine... At some point it brings me again the install menu, I`m hitting exit, and then come some errors ?!? I forgot to type them down... Something like that some files cannot be found... And after rolling errors for a while the Android actually boots ! But then come errors too... At the first time it brings me the dial pad to enter my pin-code... I entered it , but it says it is wrong...I wasn`t wrong ofc . For the next time I simply disabled my pin in Win Mobile and try again... After the Android booted it says : The process com.android.phone has stopped unexpectedly. Please try again. , and some button like "cancel" or something like that. I'm hitting it , the Android guy appears and a message " Hit the android to begin" with a hand pointing it. I`m hitting the android - nothing happened !
I`ll be greatfull if someone can help me , or at least give me some clues !
Thank you .
p.s. sorry for my english... not my native language ;-)
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Thanks
zenity said:
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Click to expand...
Click to collapse
Thank you for your fast response . But I`ve tryed (I`ve tryed again today) before to download an official WinMo 6.1 ROM from HTC_com , but according to my TyTN II`s serial number , they said : "Sorry, this software download is not suitable for your device". And I want an original ROM... I`m not sure that I can manage to flash a cooked one on my HTC . So I guess I`ll stay with the original WinMo 6.0 withut Android .
Thanks anyway
To flash a cooked rom you would need HardSPL, it is possible to do this for WM 6.0.
Regarding an upgrade to WM6.1, this too should be possible, I'd tend to disregard the warnings about upgrades being 'unsuitable'. The unavailability of certain upgrades is more to do with them being designed for certain providers or areas, rather than their actual unsuitability for the device itself.
If you have a need for a language specific rom this too is probably available from another source, if the wiki was available then there is a table of rom upgrades that would almost certainly contain just what you would need.
Note that the wiki links are all official HTC roms, and would not need HardSPL.
@Zenity - You had given me some advice on getting the gprs working on my eclair install (Eclair problems/Android problems thread). Well, I ended up ditching Super Eclair for polymod 2.1d, and mobile data started working out of the box (which is odd, because it wasn't really working before, but who am I to question?!). Now my only issue is that if I activate wifi without first deactivating mobile data, then wifi gets caught in a loop and won't connect (i.e "Connecting, obtaining address, unsuccessful, connecting, obtaining address, unsuccessful" and on on on...). Then if I try to deactivate data or wifi, both get grayed out and say turning off, but never do. I'm fairly positive this is some conflict between data and wifi, because I've connected to the same AP without any issues while the data connection is off. Regardless, this is the most fully functional implementation that I've found. Still playing around, now that I have the time I'm diving a little further into tweaking and hacking through these releases.
Thanks for the help man. I've been on xda-devs since I first got this Att Tilt, mainly reading and learning, but I've noticed that a fair number of people don't take the time to further explicate and help people through problems and troubleshooting. You and kallt_kafee are both awesome when it comes to responding to less knowledgable users, and I for one really appreciate it. So Cheers, bro!
Thanks matcha, the main reason I still find polymod 2.1D my build of choice is that of them all, it just works, all the other builds do to, but I have found less issues from users on Polymod than the other builds, perhaps it's age has something to do with it, it has less 'new' features than the others, so less to go wrong, and perhaps also that it has grown with the whole android on kaiser project.
Anyway, appreciate the vote of confidence, really I'm just trying to give back a small measure of what Xda-Developers has given me
First, the story: Kaiser / leaky shower / drip drip drip / RIP!
My kaiser has gradually come back from the dead after drying on my desk for a month.
I can no longer flash anything except the stock 6.1 winmo rom. I've tried all methods: SD & USB both work for the said stock rom but nothing else.
My tricolor screen reads: KAIS130/ SPL 3.28.0000 / CPLD-8
I'd like to flash android back on this thing but I can't Any clue?
I have mtty access too if it helps. When I flash anything through usb or SD card, I'm stuck at 0% or on the "loading screen".
I've read many threads here but no solution works for me. I'm not excluding the idea that something may have fried permanently in this kaiser so I'm more looking for some troubleshooting directions, to make sure.
Water immersion can cause a lot of problems, not so much from the water itself, but rather the deposition of metal across leads and junctions caused by electrolysis of the solder used to join components to the pcb.
Provided the damage is not too widespread it is sometimes possible to revive the device, however it requires a complete disassembly and careful inspection of practically every component and connection on the mainboard, and the careful brushing clean of any 'furry' component terminations or leads.
I am surprised that it actually boots and is able to be flashed with WM.
If it is a stock SPL then you will need to HardSPL it anyway, since it will not allow you to flash anything other than stock otherwise.
Note that as far as I am aware, 3.28 is a stock spl, rather than HardSPL which is usually 2.29 or above.
Another thing, have you tried running android from SD? I know it is not quite the same, but if it works on SD, there is no reason for it not to be nand'able
This is actually the second time my Kaiser has been drowned in water (first time is now referred to as "the 2009 faulty Roman air-conditionning incident" and it took 6months for the Kaiser to recover) and full disassembly and cleaning helped A LOT in both cases (green stuff inside). I can now say that my Kaiser is water-proof At least it's built like a tank - except for the cheap breakable plastic shell.
I tried so many complicated solutions that I didn't even try android on SD I'll look into it tomorrow.
PS: Latest stock rom from Hong Kong can't be flashed ("not allowed"), only my French rom is flashable.
Provided you can flash something 6.1 you can run android from SD, and also should be able to HardSPL it to allow flashing of other roms, including the android nand boot nbh.
I think it's incredible that your kaiser has survived this twice, I'd take good care of it from now on, third time you may not be as fortunate
coincoinlapin said:
First, the story: Kaiser / leaky shower / drip drip drip / RIP!
My kaiser has gradually come back from the dead after drying on my desk for a month.
I can no longer flash anything except the stock 6.1 winmo rom. I've tried all methods: SD & USB both work for the said stock rom but nothing else.
My tricolor screen reads: KAIS130/ SPL 3.28.0000 / CPLD-8
I'd like to flash android back on this thing but I can't Any clue?
I have mtty access too if it helps. When I flash anything through usb or SD card, I'm stuck at 0% or on the "loading screen".
I've read many threads here but no solution works for me. I'm not excluding the idea that something may have fried permanently in this kaiser so I'm more looking for some troubleshooting directions, to make sure.
Click to expand...
Click to collapse
if you flased the 1.65 radio version i have heard people having issues with it. i think somewhere on this forum there are instructions to get a different version on which wil then reopen your ability to flash the custom roms.
Yes
ghghgh14702 said:
if you flased the 1.65 radio version i have heard people having issues with it. i think somewhere on this forum there are instructions to get a different version on which wil then reopen your ability to flash the custom roms.
Click to expand...
Click to collapse
Radio could interrupt some things. But then again, with jumpspl or sspl (dont know which one is correct, the one with the froggy icon) makes you go into bootloader mode from ram if im correct. You should be able to hardspl then...
The radio version which does that is 1.65.17.10, which is not available from the Ultimate Radio Thread, for that very reason, it is only that particular radio, not the other radios in the 1.65 series that causes the problem.
I am using the 1.65 radio in my sig, and have flashed and reflashed many times, with no problems.
zenity said:
The radio version which does that is 1.65.17.10, which is not available from the Ultimate Radio Thread, for that very reason, it is only that particular radio, not the other radios in the 1.65 series that causes the problem.
I am using the 1.65 radio in my sig, and have flashed and reflashed many times, with no problems.
Click to expand...
Click to collapse
sorry, knew it was one of the 1.65, since he said he flashed an official rom if he has 1.65 it will be that version so I didn't look up the complete version as that was enough info for him.
I was too optimistic...The Kaiser recovered only for two days - I tried haret to load Android from SD, but it hung at some point.
Now there's a new error message, which also appeared after the first drowning: The sim door is open ... device will shut down in 10 secs. ZAP!
@MathijsNL
I'll have to look into your Froggy thing
The UK 3.4.2-117 froyo showed up not to be as stable as first seen, some apps crash all time and the phone to from time to time, especially the screens keeps to timeout alot and sometimes freezing the phone totaly when doing it.
Anyway, when trying to install the sbf rom with eclair 2.51 with RDS i am able to install it but not able to make the phone to start after that. Any suggestions to why, is this due to the current 2.51 eclaire version beeing branded? I started out with a 2.21 version before going to the new gb froyo rom. Pherhaps not downgradable meant exactly what it said
Thanks for suggestion...!
I have had no problems whatsoever with the UK Froyo release. In fact, I find it to be the smoothest release yet, as I have mentioned in its respective thread; Even without overclocking, it is a lot smoother than the Chinese Froyo and 2.34.1 and 2.21.0 before that. Ofcourse the quadrant 'score' is lower, but as I do not use my phone mainly for benchmarking, I do not mind in the slightest.
Anyway, before I go off-topic too far..
Have you made any modifications to the release after you put it on your phone? Did you perhaps not wipe the data/cache? Is it possible that you are overclocking your phone to such an extent that it is no longer stable?
And for some specifics - which applications crash all the time for you?
And indeed - you can not downgrade unless you've followed the instructions in this thread by Higgsy, but I doubt you have.
Incidentally, nor have I, but I have no problems whatsoever with this release and since we have the same phone, I suspect you have changed or installed something to cause your problems.
Hi!
Yes basically i got a new defy, UK retail, it was never rooted or anything and i just applied the new ROM with RDS. So no, I had not done any changes to the version what so ever and i reinstalled it twice, always making sure to offcoures wipe it also.
My main issue is actually that the screen times out alot, and sometimes locks the phone so i need to take the battery out. Also a music app (spotify) crash inevitably all time, it comunicates with the memory card as it catch up the music as you listen so thinkning that it may be some issue there. Have seen some of my other apps also force close, and this has never happen to me on this or my second (my gf's) defy i had had for some months now.
I to however are supprised about this as I can see that no other is experience this issue, espeically the screen timeout issue wich is very annoying and happens alot especially when using the browser
Will try to find a new microSD card later tonight to see if my memory card pherhaps have been somehow dammaged during the ROM installation... (dont belive at all this would have happend but worth a try i guess)
Thanks
Hm. That is quite the pickle you are in.
Can you install Catlog, filter on Errors, and tell us what it reports? You can run the application after you start the phone and have it log to file - you can put the file in
Code:
tags here to make it easier on the eyes. There may, or rather - should be a clue in there.
Alternatively, you can use 'adb logcat' from a command prompt in the Android SDK/platform-tools to get the log files to display outside the phone.
another reinstall of sbf did the trick! Will try to run the logcat to later to figure out what the app problem could be (maybe sd card read write issue I think as sameprobkem with second card) but now the phone works otherwise perfect, many thanks...
Good to hear - enjoy the shiny new release
Same problem help.
Hi I flashed the UK 3.4.2-117 froyo ROM with RSD.
My Defy was T-Mobile UK, 2.51 ROM.
After flashing the phone starts but I only get a black screen.
The softkeys are not responding but I can tap down the notification bar and open a task manager program that I had pre-installed which allows me to switch through applications. I can open various applications and the phone seems to be working like this.
I rooted successfully and then I tried to reboot into recovery using Clockwork Mod but the phones stays at the motoblur logo.
Is there anyway to downgrade or at least make this rom working?
Michalis
I have experienced some things like you sayed; some apps get closed, and frozen phone and can't even turn off the phone
so i uninstall some apps that i don't need, and get a app name SystemPanel that monitorize the CPU use to see whats going on
Since then, i don't see more those things. I'm watching see whats going on
Here is a pre-made Haret install of Fat Free Froyo RLS5 Odex'd (http://forum.xda-developers.com/showthread.php?t=819082) for those like me who had problems finding everything and getting it up and running.
For the KTC Kaiser with panel type 2. This build is optimized for a 512 MB SD card (instructions for changing SD card size below).
Simply extract the zip file to your SD card, safely remove the card, stick it in the phone and run Haret from the /andboot folder.
For different size SD cards, simply edit install-seq.sh in notepad to change all instances of the number 524288 to the correct size, e.g. for a 1GB SD card, do 1*1024*1024 = 1048576, so 1048576 is the number you change it to. Same goes for 2 GB 2*1024*1024 and so on.
DOWNLOAD FAT FREE FROYO RLS5 ODEX HARET BOOT
Thanks for this, nice hassle-free way to get things onto SD.
It's eating my battery something fierce, though, and battery calibration doesn't seem to work either.
Could be my setup though (stock 6.0 ROM due to needing it to work with my RedFly and stock 1.2something radio, which isn't supposed to work well with Android builds), but I'm wondering if you happen to know which kernel this uses?
Holy Bear said:
Thanks for this, nice hassle-free way to get things onto SD.
It's eating my battery something fierce, though, and battery calibration doesn't seem to work either.
Could be my setup though (stock 6.0 ROM due to needing it to work with my RedFly and stock 1.2something radio, which isn't supposed to work well with Android builds), but I'm wondering if you happen to know which kernel this uses?
Click to expand...
Click to collapse
Major Requirement:
HardSPL v3.29 (recommended for flashing NAND kernel through SD)
Radio version 1.65 or higher
The lower radio version will cause unusual behavior. Hyperdragon IV Mega WM6.1 comes with Radio version 1.65, you can flash it after having hardSPL 3.29 on your phone. Then just proceed with froyo
dark_prince said:
Major Requirement:
HardSPL v3.29 (recommended for flashing NAND kernel through SD)
Radio version 1.65 or higher
The lower radio version will cause unusual behavior.
Click to expand...
Click to collapse
Thanks for the reply.
Because I'm stuck with WM6.0 for the RedFly, I´m trying to figure out whether flashing the 1.65 Radio will cause problems with WM6.0.
But yeah, I figured the 1.27 Radio was part of Android sucking batterylife like a vampire...
Holy Bear said:
Thanks for the reply.
Because I'm stuck with WM6.0 for the RedFly, I´m trying to figure out whether flashing the 1.65 Radio will cause problems with WM6.0.
But yeah, I figured the 1.27 Radio was part of Android sucking batterylife like a vampire...
Click to expand...
Click to collapse
Install HYPERDRAGON IV Mega WM6.1 (after having HARDSPL v3.29), You will automatically get a WM6.1 with 1.65 Radio version
dark_prince said:
Install HYPERDRAGON IV Mega WM6.1 (after having HARDSPL v3.29), You will automatically get a WM6.1 with 1.65 Radio version
Click to expand...
Click to collapse
No, see, that's the problem: I need the 6.0 ROM to have the Kaiser work with my RedFly.
The 6.1 ROMs have all given me trouble after installing the RedFly app.
I guess the point is: I could get a 6.1 ROM with a 1.65+ Radio and probably have better results with Android.
But right now I need it to work with my RedFly (it's my only mobile that works well with it, and I have others for Android if I really want that) and that only seems to be flawless with WM6.0
I could check it with WM6.0 with a 1.65+ Radio, but I'm fairly sure that those two don't mix.
For all I know the RedFly app might actually not play well with 1.65+ Radios.
Works only on Windows OS ? if i want to chance my version of android from linux(ony my phone) ? i need the KaisIMG.nbh ? (and the kaisdiag.nbh)
im flashing my phone whit the sdcard from android to android and use the kaisdiag.nbh, i don't know if is necesary file, but i reboot the phone froim android, and hold the Dpad, and instal the new system. And works !
i think i can change the kernel for overclock to 495Mhrz and works fine, what you think?
greetings
sicstifor said:
im flashing my phone whit the sdcard from android to android and use the kaisdiag.nbh, i don't know if is necesary file, but i reboot the phone froim android, and hold the Dpad, and instal the new system. And works !
i think i can change the kernel for overclock to 495Mhrz and works fine, what you think?
greetings
Click to expand...
Click to collapse
Probably all possible, but this post is meant as a complete set of files to install FFF to boot from the SD-card with Haret.
So this post isn't meant for what you're trying to do, I think.
Still, installing this build by renaming it KaisIMG.nbh and placing it in the root of your SD-card for flashing is probably what you describe as working.
works, and still works, but no wifi-camera (on the older rom for droid he works) , ._. anyway, i test any versions and i never find a stable version for my kaiser, on WinMo works really fine, on android works fine for a shor time
Some android roms stable?
This process will erase windows mobile? I would like to try it!
Hello Mark from Rome
Battery issues solved with this rom
For me 2.6.25 kernel solved the battery issues with radio 1.70.19.09 (that radio also enabled camera to work). Took me 2-3 days to find out...
Thanks, big help!
I am trying to make the data connection work, any tips?
Tried already: lots of radios, connect data in WM before starting haret, different kernels from dzo, l1q1, and so on...
download link is dead..can someone please post a new one?
thanx