Update: New release (RLS 5)
-Comes with 'rogue tools' for overclocking and setting display density will need an update over market to support nike, myn told me he will push it to the market during the next day or so)
-feels smoother, connectivity seems to be a lot better (I never had a faster browsing experiance on my nike than with this build and opera mini), rejoining network after lost signal also seems to be faster
-nice new weather/clock widget
-if you use installd version, the androidupdate.tar from rls4 is still necessary for powermanagement
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
Get it from the vogue forums (SQSH version):
http://forum.xda-developers.com/showthread.php?t=619980
Here is a link to the basefiles I am using:
http://84.23.71.227/kerneloftheday/RootfsBasefiles20100318.zip
The kernels are from dzo's branch with a few minor fixes (vibration, irq-wakeup, red led blinking when in sleep mode). Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
HowToInstallInANutshell:
-delete old android files from sd
-extract basefiles to sdcard
-extract system.sqsh from myns package and copy to sd
-if you are on a nike100 make sure deafault.txt points at the kernel without vibration (included)
-otherwise default.txt should be fine, most parameters are ignored anyway.
-run haret
-be happy
Impressions:
-sleepmode 1 ok, wakes up, red led blinking. Battery life seems ok, but i only tested a few hours...
-very fast
-many locales, not just english like in good ol' ion
-quite stable net, nice apn autodetect (just had to select from two alternatives), working google stuff
-still not working: bt, incall volume, cam
So, give it a shot and leave your impreesions here!
mblaster
********** UPDATE ************
Installation with the NoRootfs Method is now possible with working net and powermanagement. This gives us the possibility to use the Themes and the default font and everything else that can be provided via androidupdate.tar
See the Wiki for installation instructions. Make sure that you have the provided 'androidupdate.tar' (see attachment, file is in the zip archieve) in your andboot folder along with the androidinstall.tar when installing.
To install themes just copy them in you andboot folder (must be named androidupdate.tar), reboot into menu -> update (-> fix permissions).
PS: Doesn't seem to work with eclair builds, but could work with other donuts
PPS: This should also work with ext2, if someone tried successfully please let me know. €: Works with ext2
Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
Click to expand...
Click to collapse
you've added hw3d support? I tried to do that - all that I got is 3D without textures or simply nothing - black screen. I did same as in this commit in repo.
I did the same. The only build i saw it working was aosp eclair for kaiser (gallery3d worked). Otherwise i got the same errors. I read that the other devices suffer from similar problems.
Ps: Writing this on myns donut. Everything stable so far.
mblaster said:
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
...
So, give it a shot and leave your impreesions here!
mblaster
Click to expand...
Click to collapse
Hi mblaster,
works like a charm here. Very fast and stable. This is the first ever Donut Build with stable working Data i've seen....
Only Point is, that icons are really very small. Seem to me even smaller than in the old Cupcake Releases with 320x480...
Tried higher settings for lcd.density, but screens don't fit than anymore.
Have you tried it with a non modded system Image ?
Greetz, lagloose
ECLAIR
because you are starting another section of the eclair?
already has almost no one accessing the other thread ...... I have a question there for two days and no one responds more ..
I am very impressed with the progress of the android in my eclair NIKI100 (20 keys)
is making calls, receiving messages, all volumes of the system are working (calls, music (I had to install another player why that came standard did not work), alarm etc. ..) I'm using it for three days, battery lasts long , it does not heat the unit, since I use it in everyday life.
now I have some questions for you:
is so difficult to operate the headphones?
I love listening to music, especially in the way of work, if possible, please someone do work ....
particularly hate wm, I think one day we niki users, we can get the WM and definitely use the android, (because you can try to do everything, are the gods of HTC ....).
another question, I can change the theme of the eclair? wanted it like this: http://forum.xda-developers.com/showthread.php?t=600154, it is possible??
I'm not charging, just begging! rsrsrsrs
Congratulations XDA....( GODS OF HTC)
Hi there,
together with mblaster's combination of basefiles in the first post of this Thread, the sqsh Version of the image in this thread http://forum.xda-developers.com/showthread.php?t=591104 works also...
mblaster; seem's you've found/made the ultimate combination for Donut Images. PERFECT !
Greetz, lagloose
Theming with Metamorph
I been reading around on Vogue's thread and Metamorph catched my attention. It can style up android theme. Is this apps runs well on this build. I am confused because based on this site http://www.androlib.com/android.application.stericson-xda-metamorph-xnFD.aspx it can only run n Rooted phones. What is rooted phones anyway and can this run well in nike100 with the android build posted in this thread?
When is the nand version available? I think the only thing missing now in nike100 are camera and vibration features. Great job!
More Power!!!
Anyone encountered the "Half Size" icon problem ?
This is, when there's a reload of the Home Screen, all icons are suddenly half the size than normal. I had this after leaving the Browser.
Couldn't find a solution for that behaviour. Any ideas ?
Greetz, lagloose
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
jefins said:
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
Click to expand...
Click to collapse
You have to disable PIN in WinMobile afaik for all builds so far.
About wifi: The stickies say no wifi on nike. Never.
"never ever say never" ;DD
thanks anyway for Pin code tip.
Network problem
got two bugs here.
1. browsed from wm then switchd to android. i cannot connect anymore when in android. even if i reconfigure my apn.
2. switching from phon mode to airplane mode and airplane mode to phone mode will stuck in airplane mode.
@mblaster
how to enable apn autodetect?
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
lagloose said:
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
Click to expand...
Click to collapse
me again...
just got a flash in my brain...
probably a story about the rootfs because of different load types (NoRootFs vs. Classical sqsh File) ?
so what about mounting the original sqsh Image and untaring the update "over" the rootfs ? ...
@lagloose: Might be an issue because the androidupdate.tar files are made for norootfs. Perhaps its time to move on to an installed version without rootfs...
@ebautista: Sorry, but I do not maintain myn's build. Perhaps it would be a good idea to report bugs in myn's thread in the vogue forums. APN detection worked for me right out of the box. Do you use the basefils from this thread?
€: your brainflash was faster than my typing... but perhaps you should at laest try to set the right permissions, it might work
Hi all,
Just tested sqsh Image from http://forum.xda-developers.com/showthread.php?t=628459. Not completely tested but seem to work also with our basefiles.
I'm working on a way to get themed Images for us Nike Users. Still some problems to solve, but shouldn't be that difficult...
As soon as i've found a way, i'll state it here.
Greetz, lagloose
I really would suggest to move on to NoRootFs for various reasons:
The theme packages are already available there
The basefiles are still supported and regularly updated, while SQSH is dying out, and as there are very few devs for nike we should try to profit from the progress made on other devices
There should be no drawbacks, just a few more MB on sd-card for the system
The installer for systems / updates is extremely useful (theming, installing your favourite apps in one shot ...)
Give it a try, you will find a little howto and links to ressources in the wiki
mblaster,
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
mblaster said:
...
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
Click to expand...
Click to collapse
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
hi, mblaster,
i want to download the file as "Get it from the vogue forums (SQSH version):
but i cant aceessed "mediafire"
Could you email to me a file that it can running on nike100, thnks
my mail is [email protected]
See Post 1 for UPDATE!
lagloose said:
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
Click to expand...
Click to collapse
I am quite sure now that the initrd is fine and the problem is in the Rootfs, or better what is left of it. The latest working basefiles include a Rootfs dated to 2009-11-16. There is a newer Rootfs on sourceforge (sometime in december 09) that shows the same problems (net/powermanagement/shutdown). As parts of the rootfs are included in the androidinstall.tar images, thos errors are still there. My update file (now included in post 1) overwrites those files with versions from the 11/16 rootfs. That leeds to a working system (with the new initrd).
Unfortunately the update is incompatible with the newer eclair builds that are around. Seems like they use another rootfs that rejects the old files...
Does anyone maintain a git repo of the rootfs? It would be interesting to patch the problem for good
Related
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
8-11-2004 20:57 GMT: New version V2 uploaded.
I added a small archive containing the changed ExtROM files to solve the earlier reported errors (not updating ExtROM version and not making IIWPO un-installable).
Comment on IIWPO and making it un-installable: After having customized & installed IIWPO, you will have to do one of the following to make it un-installable if youre using the 1.72.902 ExtROM:
a. Another hard-reset
b. Running Version_172_902.cab from the ExtROM
NOTE: This thread is being replaced by
http://forum.xda-developers.com/viewtopic.php?p=68652#68652
Thank You!!!!!!!!!!!!
I am d/l'ing right now and will be installing shortly...
One request... You might want to include the cab for setting up IIWPO in case someone is installing it into the phone.
edsub Thanks.
Question tho. Can I use this for T-Mobile USA and does it fix the MMS problem ?
asking because the version says NL, isnt that the Netherlands country code ?
Thanks again
Well from first look everything seemed ok.
THese are a few of the things I have noticed since loading.
1. The ext rom version # doesn't show up in the info
2. If you use the IIWPO then it still shows in the remove list
3. The new apps from the 187 version will not install no matter what you do. (I have tried adding the ver # in the Reg, both 902, and 187 (not at same time)) Niether worked.
These are the few things that I have found since loading. If I find any more I will loet you know. Other than these I think you havea winner here!
I was wondering about the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 packages, and why you didn't include or update to them? Was there some incompatibality issue?
Thanks and great job!
Re: Home-cooked 1.72.902 upgrade package (1.72.00/1.17.00) T
edsub said:
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
Click to expand...
Click to collapse
Is SRS included?
SRS is not included due to the fact that I don't see any use for it personally. Since it is an ExtROM installer, you could add it yourself.
The NL is only there because some sdetting are more or less specific to the Netherlands. I had feedback on my earlier 1.72.901 package that it worked for other countries (incl USA) as well. Be prepared that the date format will be dutch by default (easy to change via settings though).
Also MMS is suposed to be working (but I have not tried it due to lack of interest in MMS)
The ExtRom# is not showing because some bug in the Version_172_902.cab. Working on that now.
IIWPO not showing in the remove programs list is a bit more difficult than it seems if you install for the first time. Normally you would boot up the device with new rom. IIWPO is NOT installed at this point. Once you have customised & installed IIWPO, you will have to do ANOTHER hard-reset (ie run the ExtRom contents again) to disable the uninstall. You could force this by hand first time to re-run Version_172_902.cab after installing the customised IIWPO. BUT as this cab is not OK, it wont work anyway. Working on that now.
I did not find the time to look into the new O2 apps. If someone finds a solutiuon here, I am more than happy to includew it in a new version.
For the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 the basic reason is lack of time. I dont know what 'extra' new there is on bluetooth in the O2 builds? OS Rom 1.72 allready has an updated BT stack that fixes most open issues. I have no experience (& interest) in MMS / streaming MMS . . .
I suppose the issue with TomTom locking up without GPS enabled is not solved with this rom ?
I know: wishful thinking..........
@Pleun: Nope. I WISH I would have solved that one!!! FYI: I tested he new TomTom GPS 3.07. It doesnt solve any locking issue and next to that makes my Headset react very slow. Also the 'Bluetooth GPS' option that is supposed to solve the locking has gone, at least with my installation. Not advisable. I reverted back to TomTom GPS 3.03.
@all: I solved the issue of not setting the Ext Rom version and making IIWPO non-uninstallable. New version V2 will be up in 10mins (incl. incremental fix for all that downloaded the version from yesterday).
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
edsub said:
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
Click to expand...
Click to collapse
I feel like my MDA2 is a little bit slower to respond not sure why! I added PocketMVP, Belkin Bluetooth GPS, Resco Explorer 2003 V5.0 and .NET Compact Framework 1.0 SP2 for Pocket PC 2003.
I am having problem with Belkin BT GPS; I got it to bond, detect the COM port (COM5) and baud rate(4800) to use but my MDA2 hangs up and had to soft reset. Any idea why?
I will try to install one by one and see what's causing it and report here.
edsub thanx for me it works great its a great improvement!
machine seems faster and no more lock-ups.
Keep up the good work (ill be following you)
p.s only one thing my battery seems to give me no more than 4 hours of on-time
4 hours is very different from my (and others!) experience. The 1.72 rom should even improve battery life.
My battery lasts for about 1,5 days (not measured but recalled from my memory) with approx 1-1.5 hours on the phone and bluetooth permanently switched on . . .
were can I download this rom from?
from the first msg in this thread : RUU172902WWE_eDsuBsofT V2.exe
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Anonymous said:
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Click to expand...
Click to collapse
You cannot download it as a guest! If you are a member of this forum you have to log-in before you can see the file you want to download. That's what I encountered before so just try logging in first.
Good luck!
THank you very much superperry. Should have registered before but was always too lazy.
I have put together rom upgrade 1.72.903
This thread can be closed. See http://forum.xda-developers.com/viewtopic.php?p=68652#68652 for the new one
Edit: The new upgrade files are now available (see refered post)
An error need help please
I downloaded the files then followed the instruction below but now I get error
the flashing process
first the devicedata is obtained from the device, with HimaGetDeviceData.exe, this gets the operatorname, and language/country code from the extended rom, sector 2 of the BDK.
Then a tool 'HimaClearJumpCode' is executed, which erases the jump at the start of the kernel. causing the bootloader to start at next reboot.
the upgrade tool then connects to the bootloader of the xda, via serial over usb. ( port \\.\WCEUSBSH001 )
warning do not just run the 'HimaClearJumpCode' program, it will erase part of your OS rom, after which you will have to repair your device by running an entire upgrade again.
ok....
here's the deal:
I've been using an OEM-package in mylast roms for tomtom version 7.915.
This has been working without troubles.
Now I cooked a new ROM based on new 21018 XIP/SYS
The device really flies and everything seems to working flawless....EXCEPT tomtom.
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
I did not change anything to the OEM-package. So I guess it has something to do with the new SYS.
Do more people have this problem and/or does somebody now the fix....
Thnx all in advance for your help!!
Greetz Merten
p.s. I used the search function of course and saw a lot of similar errors but no sollutions.....
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
crazyC said:
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
Click to expand...
Click to collapse
I got the exact same oem-package working in M-rom v1.71!
So it really beats me why I get the error.
I tried cooking the rom again but still the error....
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
crazyC said:
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
Click to expand...
Click to collapse
Ok OEM can be found here in the map: packages
Package looks OK at first glance - hope to be able to try it tonight and will post back tomorrow with results.
If this doesn't work - you could try simply using the cab via UC etc as I do - I have checked and the cab of the same version in your OEM DOES work for me.
In fact, I think I might leave it in my UC, (but will flash tonight anyway with it just to see)
merten3000 said:
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
Click to expand...
Click to collapse
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
GenghisZ said:
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
Click to expand...
Click to collapse
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
merten3000 said:
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
Click to expand...
Click to collapse
Nope, did not help...
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
crazyC said:
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
Click to expand...
Click to collapse
I always change my roms pp to 32mb...can that make a difference? I did it in v1.71 and tomtom worked fine...
I don't know - I have been around here long enough to know that your skills far outweigh mine. If it used to work then I see no reason for the change.
All I know is that my rom is based on Da_Gs really clean latest (ie 5.08) from his simple kitchen thread (from his post near the end not the first post) plus Eras2rs package updates.
The only other packages I add are a few utilities and personal tweaks. I import an advanced config xml as part of the UC process but that just ensures the various settings in Advanced Config are set to advised etc.
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Harikoss said:
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Click to expand...
Click to collapse
Maps work(ed) fine..
btw I bypassed the error by removing the OEM-package and made it a cab which is installed during system configuration. It takes more system space but this way it is uninstallable....but it remains a mistery to me why the OEM does not work in this SYS and does in 21014 SYS...
First things first! As the topic states, this is a *TEST ROM*
DO NOT expect this ROM to be usable for every day use
DO NOT expect this ROM to be well tweaked for performance
DO NOT expect this ROM to ... you get the idea, i hope!
This is the first Test ROM for the Image Update service - this ROM has a 1024KB free space buffer for NK partition, 20MB free space for OS partition. This should be enough to facilitate several ImageUpdates for testing. (It's not intended to have enough space for you to add all your chosen apps for every day use - this is just for TESTING!)
It's based on WM 6.5 21812. This ROM is unique in that both the NK and OS partitions are completely uncompressed, rather than using either XPR or LZX - so i'm testing that too. Please report on overall system performance of the BUILT IN applications (not cabs or packages you install) - i'm wondering if Uncompressed is viable at all vs. XPR and LZX. So far i'm thinking no (60MB LZX -> 80MB XPR -> 150MB Uncompressed) - but testing is warranted!
The Image Update packages for this ROM are now in post 2!
Here's the download link!
Again, this is BAREBONES, the ONLY thing it has is drivers and comm manager, this is done on purpose, so that we can have as few variables as possible while testing deployment
http://rapidshare.com/files/244900505/ImageUpdate-ready-ROM-Raphael.rar
Some notes:
The ROM has an OS pagepool size of 26MB
The ROM has a ULDR pagepool size of 4MB (up from 1mb)
All compression is disabled entirely (not XPR or LZX, but Uncompressed - both on NK and OS partition, also compression is disabled on individual modules and files)
Dr. Watson (Error reporting) buffer reduced from 300K to 0K
Update Packages
QuickGPS
EzInput+eT9
Camera - This will install the Camera, Dshow, Mhub, and SensorSDK packages (Camera is dependant on the others)
Here's the test case scenario - create a directory named "Release" in your filesystem, at the root \ folder (so \Release)
Copy the cab.pks to your device, or sd card, and run it as you would a cab
Note any errors or anything that might occur before the process succeeds or fails
If the process fails - please attach the logs found in \ and \Release to a post, so we can analyze it further
If it succeeds, time to hard reset your device!
Check and see if the package remains after hard resetting.
If it does - We have a winner
A live-updating rom with no need to reflash the device after each upgrade? I love it!
Keep up the good work!
Interesting concept.
this is awesome! cant wait to cook one for kaiser(hint, hint) thanks for all your work, this is going to change EVERYTHING.
Image Update System
I have been following the WM Image Update System thread and the idea sounds very doable. How can we help?... David.
I can Hard reset my phone every day, so if you in need of any volunteers Im here .
I have been following your kitchens for a while, and it's time to return the favor.
Thanks so much for your hard work Da_G!!
-------
HTC Fuze - WM6.5 21812
Da_G...Sir, you are a saint and a scholar...when this is finished it will be the coolest thing since velcro...
I would love to help just let me know how...would be happy to test..report...etc.
Dreaming of the day...no more hard reset
Da_G,
Thanks for your hard work.
I'll been dreaming of the day when I don't have to reflash my ROM or hard reset just to update the software.
I'll beta test and give you report.
D/Ling now, will report after work this evening. :excited:
i am really enjoying the speed. its unreal. every thing else seems normal. i am still loading up my apps right now. i'll post up some more when i get home.
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
rzanology said:
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
Click to expand...
Click to collapse
I'm going to need you to test your awesome space bar, it seems to be more than working well... =P
LOL, didn't overwrite CompIME.dll in this release (again for compatibility reasons) so that's why the jacked up spacebar..
But hey, it's a test
Hoping to have packages for you soon
Everything is working smoothly, no issues yet. I read your other post on the image update and want to know how far into user customizablity we can go without messing up the update process, ie. regedits, packages, etc.. Or if its a secure core that we can't really mess up.
Oh, yeah, its supper snappy and extremely responsive. And running at 26% Memory isn't bad either.
Is it safe to assume any updates needed to be deployed, such as over writing the CompIME.dll will be done thru the this new Updating system, correct?
Thanks for your hard work Da_G!!!
So, am I correct that any chefs who want to incorporate the working updating system into their roms will have to cook unprotected? This could get really interesting, LoL.
Thanks for the awesome work!
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Da_G said:
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Click to expand...
Click to collapse
A working one? This one is working beatifully lol .
Im curious, I checked the system tab, and I didnt see the Windows Update Icon...
How will we check for the update then? Just wondering, thats all.
My apologies if im asking too many questions
Great news Da_G. I'll test it once you post the update tomorrow. How do the updates get delivered?
Is the .cab.pkg a small file which contains the server information so the phone can go out and retreive it? Or is the .cab.pkg the whole kitten caboodle?
hey guys,
for the fun i tried to run Eclair android on my niki, with in my mind it would not work.
well i did follow a tutorial which was meant for Kaiser/Vogue/Polaris.
then it just booted in Eclair, i made some pictures for you guys to take a look at.
Ill also make a vid, with booting in it, and some things to show.
enjoy!
sorry for my bad english, im from the netherlands
PICTURES
This are some pictures i made from Android Eclair on the HTC Touch-Dual *NIKI*
http://img175.imageshack.us/gal.php?g=img0741.jpg
VIDEO(S)
Here i will post all video's made by me, or people from xda-developers.
VID 1(made by me, do not mind my voice)
http://www.youtube.com/watch?v=z0u1ejw6AF8
DOWNLOADS
Here i will post all downloads you will need to run android eclair on your HTC Touch-Dual *NIKI*
SD-Card rips
Fast tutorial for installing SD-Card rips
1. Download the SD-Card rip package you want from this page.
2. Extract it to your desktop.
3. Now select all the folders, and right-click Copy.
4. Connect your HTC Touch-Dual *NIKI* to your computer.
5. Go to your explorer(right-click on start)
6. Go to your device, and select in there the SD-Card
7. Now copy all the just selected files to your SD-Card, this can take up to 20 minutes.
8. Now the copy process is finished, take your HTC Touch-Dual *NIKI* and go to the file explorer.
9. Go to your SD-Card, and run Haret.exe
10. Now just wait till android is started up.
SD-Card rip polymod 2.1 alpha 4(OLD)
This is a rip of my SD-Card, i do not know if it works on your HTC Touch-Duals *NIKIS*
But you can always try
http://www.mediafire.com/?gouyxj5igcy
SD-Card rip Android Eclair 2.1 Vogue(NEW)
This is a rip of my SD-Card, i do not know if it works on your HTC Touch-Duals*NIKIS*
http://www.mediafire.com/?mt1wblydryd
SD-Card rip Myn’s Warm Donut(NEWEST)
Here i will post the fastest android release that i found untill now.
This is a SD-Card rip which was installed on a HTC Kaiser, because the NIKI does not have as many keys as the Kaiser, i could not start the installation on my HTC Touch-Dual *NIKI*.
So there only will be a SD-Card rip untill now.
Here is the download link:
http://www.mediafire.com/?mmdihjjez1o
Android install folders
Fast tutorial for installing Install folders
1. Download the Install folder you want from this page.
2. Extract it to your desktop.
3. Now select all the folders, and right-click Copy.
4. Connect your HTC Touch-Dual *NIKI* to your computer.
5. Go to your explorer.(right-click on start)
6. Go to your device, and select in there the SD-Card.
7. Now copy all the just selected files to your SD-Card, this can take up to 20 minutes.
8. Now the copy process is finished, take your HTC Touch-Dual *NIKI* and go to the file explorer.
9. Go to your SD-Card, and run Haret.exe
10. Now you have to watch your screen very careful, when the text “Hold dpad center to launch installer” appears, press the middle button.
11. Now a install menu will come up, select the 1st option, Install system
12. Now there will pop-up a messenge “This will wipe your existing system!” just select YES, this will not remove your windows mobile installation, it should delete a previous android installation, which is not installed yet..
13. Now there will pop-up another messenger “Would you like to clear data too?(Suggested)” select YES again.
14. Now android will be installed on your SD-Card, when it is done, you will return to the install menu, now just select Quit and it will boot in android.
rip polymod 2.1 alpha 4 Install folder(OLD)
This is the Install folder of polymod 2.1 alpha 4.
This is the slowest android i runned untill now, i do not recommand it.
Download link:
http://www.mediafire.com/?zznwujznouz
Android Eclair 2.1 Vogue Install folder(NEW)
This is the installation folder.
Download link:
http://www.mediafire.com/?nxniyktlkuu
Myn’s Warm Donut Install folder(NEWEST)
Please take a look at the SD-Card rip.
Good news
I would to try it out. Can you upload your android package here?
yes, nike users can use the package for the vogue. the problem for me was that nike could not wake up after sleeping because we have different key mapping than vogue or kaiser. how is ur battery life?
im on school right now.
when im home, ill upload a complete rip of my SD card.
what i've done is the following:
i downloaded the pack for the HTC kaiser/vogue etc.
then i used the default.txt from a android made for the htc niki.
the only thing i changed in there was change "Zimage" to "Zimage-monsha"
then i could just install the andoid on my sd card and run it.
i don't know about the battery life yet, i didn't test it very well yet.
it's pretty laggy though so it will need some very good improvements.
Did your data work? I also got eclaire runniung on nike on ext2 partition using the methods from the vogue forums, but I noticed some issues:
- No data
- Slow
- I Tried to patch the new 3d driver stuff into the kernel. Afterwards i had accellerated graphics without textures (live wallpapers). But i have the same issue on some combinations of older builds, kernels and rootfs.
I also tried other builds from ext2 (all without rootfs, no working data on any of them , but it seems like the old versions with rootfs work better (-> data works)
i did not test it anymore.
i was at school.
rightnow im at home, so ill make a rip of my sd card, this is not formatted in ext2 or something.
i just deleted all the data on the sd card, and i just installed it.
it will take a while to upload, cause its pretty big.
right now im going to upload the .rar file.
it is 115 MB big, so make sure your sd-card is bigger than 512 MB
ritzky said:
yes, nike users can use the package for the vogue. the problem for me was that nike could not wake up after sleeping because we have different key mapping than vogue or kaiser. how is ur battery life?
Click to expand...
Click to collapse
i tryed with sleepmode on 0, and it just worken, also on 1 it just worked.
i do not know how to see if full sleep is working, but it could be also working on the HTC Touch-Dual *NIKI*
set pm.sleep_mode=4. Data don´t work. Data don´t work on Nike with more new Android OS like donuts(1.6) or eclair(2.1) only in olders like android 1.5. Nike handsets lacks of android developers. We have no luck like Polaris/Vogue/Kaiser/Diamond users
i know, but i edited the default.txt a lil, by changing the resolution, i had less lagg, but it does not show the whole screen :S
even when im using the resolution of the screen :X
if u set the sleepmode to 0, can u wake the device? i never been able to. could u post just your default.txt here? anyway, data is working for me.
Running
I tried this, i'ts running, here's my report:
1. I cannot make a call (incoming or outcome).
2. I cannot send the SMS
but the operators carries found..
ritzky said:
if u set the sleepmode to 0, can u wake the device? i never been able to. could u post just your default.txt here? anyway, data is working for me.
Click to expand...
Click to collapse
yes it awakes then.
and i did not test it with sim yet, the first thing i wanted to do is a good fast stable android build.
i found one, only one problem:
you cannot install it on your niki, i have to take the data.img and system.img from a HTC Kaiser(which uses my dad)
i already got a rip, right now im going to test if that works.
then i will delete all settings in there, and upload it here, one thing; it is REALLY fast!!
podelz said:
I tried this, i'ts running, here's my report:
1. I cannot make a call (incoming or outcome).
2. I cannot send the SMS
but the operators carries found..
Click to expand...
Click to collapse
I had the same problem first, then reboot the phone and it works great !
My only problem is the qwerty keyboard layout ... mine is azerty
great port thanks !
ok, thx man!
i'm in France right now, so i can't update my thread, when i'm back, i'll look for some newer versions and upload some other SD-Card rips, and Install folders
mrassol said:
I had the same problem first, then reboot the phone and it works great !
My only problem is the qwerty keyboard layout ... mine is azerty
great port thanks !
Click to expand...
Click to collapse
Hi there,
Tried it here in Germany. Boots fine, but no Data. Carrier shows up and after creating a new APN, The Modem APP shows active Connection, IP Address and so on. But for some Reason, there's no Flow of Data...
Any Ideas ?
Greetz lagloose
(BTW: Phone seems to work normal...)
lagloose said:
Hi there,
Tried it here in Germany. Boots fine, but no Data. Carrier shows up and after creating a new APN, The Modem APP shows active Connection, IP Address and so on. But for some Reason, there's no Flow of Data...
Any Ideas ?
Greetz lagloose
(BTW: Phone seems to work normal...)
Click to expand...
Click to collapse
Data don´t work on Nike with the more newest android builts. We lack developers
I noticed that data works on eclair and donut, but the connection drops after a (very) short time. Sometimes I was able to load one or two webpages after a fresh boot until the connection went down (20Key Nike, O2 Germany). I also got google sync once working for a few seconds (enough to fetch mail).
So it seems to be more a stability issue than a general lack of data connection.
Does anyone have developent experience with android? I am now compiling the eclair build with the latest libraries from the vogue andoid git tree, but if someone already knows were the data problem is or what it could be i could find a faster solution, any in the development would be great.
mblaster said:
I noticed that data works on eclair and donut, but the connection drops after a (very) short time. Sometimes I was able to load one or two webpages after a fresh boot until the connection went down (20Key Nike, O2 Germany). I also got google sync once working for a few seconds (enough to fetch mail).
So it seems to be more a stability issue than a general lack of data connection.
Click to expand...
Click to collapse
It´s true. It is like get freezed. If you go to modem and you want to disconnect it say disconnected but you can see still the icon and sometimes the up arrow. After this if you want to turn off the hanset you can´t and its needed a soft reset. So after get connect and with a luck to browse two webpages it get freezed
Hello everyone.
I know that there is already a big thread to discuss about Diamond2 clones, but I've decided to create my own thread, only focused on T5388++, to make it clean and organized as I like.
In this thread you'll find all my cooked ROMs. You should be able to get it from my T5388++ 4shared folder! You can bookmark this link. The password to access the folder is XDA-Developers.
Feel free to post your comments. I hope you like it!
EDIT: Don't you forget to donate for all my work. I've made some improvements over the official ROMs and you all know it. A lot of downloads of my ROMs have been made, but only a few people have donated. Remember that I do this in my spare time and a little contribution is highly appreciated.
Just for your information, in less than 2 months, there were more than 100 downloads of V1 ROM.
Available ROMs
Here you can find my custom made T5388++ ROMs. Please be sure to read this carefully in order to avoid unnecessary questions.
Removed from OEM:
*.mui files
ROMs download links:
Please check my 4shared folder link in the the first post.
Version History:
v1
Initial release, based on WM Build 23123 and OEM Drivers from official T5388++ C03.020.01 ROM
Includes HiSilicon Camera v1.1
HTC EzInput v2.1 (Build 2012.2024) and EzInput SIP Menu integrated
Microsoft default keyboard removed
Includes LockDevice to automatically lock the device after screen power off (more info)
WM LockScreen is enabled by default
Includes MortScript v4.3b15
Added a HTC Diamond2 sync icon (created by me) that appears in Windows Mobile Device Center
HTC GSensor SDK integrated (more info)
Disabled Start / OK softkeys and enabled text mode (more info)
v2
Based on WM Build 23144 and OEM Drivers from official T5388i C03.021.08 ROM
Removed HiMMITest and all it's modules
Includes ArcsoftMMS v5.2.8.45
Includes HTC Connection Setup v3.1 (Build 2011.1725) with the latest database for an easy MMS/GPRS network configuration
v3
Based on WM Build 28244 (WMD)
Includes TAN messages fix
Minor cosmetic fixes
P.S.: My ROMs can’t be flashed using the SD flashing method because I have removed IPL, RAMInit, USBLoad and XLDR in order not to flash those parts every time and avoid bricks. You have to use IDT flasher, which for me is the best solution.
* Reserved for future use.
** Reserved for future use.
Finally i uploaded this ROM ... and I'm pleased at first sight.
This man just have done great work. It's fast and clean and with good bonuses! Ultra FAST
I hope that i'll be able to donate few $$ soon.
I have question to the cooker : How can i boost to maximum screen sensitivity ?
The only 1 problem is described below by another good user:
And don't remember to fully charge before you begin
MicAlter said:
BTW what is the latest original ENG ROM?
I've found a list at "3w.htc-topaz.co.cc/files/index.php?dir=ChineseClone_Files" and flashed to S650WM653_20100412_C0302001_english.rar. I think that this may be the latest one, isn't it? Proofed don't know newer. It works on 5388++
Here I go:
Flashed from C03.001.01 ENG to your WM23135-ROM
Result: Restart Loop
[1] Flashing finishes without error
[2] After flashing ROM the device restarts itself
[3] Removed USB Cable
[4] Blue "Touch Diamond 2" is displayed
[5] New animated Windows Mobile Welcome-Screen is displayed
[6] Display goes black and device restarts
[7] goto [4]
Flashed from C03.001.01 ENG to C03.020.01 ENG
Result: Flashing successfull
[1] Flashing finishes without error
[2] WM is working properly
Flashed from C03.020.01 ENG to your WM23135-ROM
Result: Flashing successfull - BUT!!!
[1] Flashing finishes without error
[2] Now WM is starting without restart
Click to expand...
Click to collapse
Thanks a lot!
Thanks a lot bgcngm for all your hard work already so fast. I will try your new ROM next week. Good that you removed the boot firmware so all of us have less chance that the phone will becomes a brick
I would like to see the extendir version if I don't ask too much the Manila2D package for DUAL SIM
Have fun with cooking.
Thank you Eer.
I will work on the Extendir ROM maybe this weekend.
Right now I only wanted to release a normal one so that everyone can install without a problem. I had it running in my T5388++ for 3 days and haven't experienced a single SoD. I'm now starting to believe that the SoD's reported by some users are due to hardware problems... Additionally Wifi, GPS, GSensor, Bluetooth, Phone1/2 are fully working.
bgcngm said:
Thank you Eer.
I'm now starting to believe that the SoD's reported by some users are due to hardware problems...
Click to expand...
Click to collapse
That's NOT true! I had SOD on my T5388++ every day until i have flashed ROM from previous thread!
Well, if you are so sure about that, then you should have no SoD with my V1 ROM either. As I said, I have been running it for 4 days without experiencing any SoD.
First of all, thanks for your work. I think that SOD is a mixture of both, software and hardware, surely these are not all made mobile with the same components, causing problems of instability depending on models depending on hardware. I do not think the solution comes from a magical software, surely that one will be good for another will not.
These are all assumptions clear jejejeje.
I had just installed this ROM.
Common impression: it's VERY fast.
PS:
Today's item "Wireless" is still "squashed"
BIG666 said:
PS:
Today's item "Wireless" is still "squashed"
Click to expand...
Click to collapse
I guess that it will always be squashed. To be honest I haven't tried to fix it because I don't use the old Today anymore. As far as I understand, the plugin doesn't "work" properly with this WM build.
Just for curiosity, why do you enable the old Today screen? Don't you like Titanium?
bgcngm said:
I guess that it will always be squashed. To be honest I haven't tried to fix it because I don't use the old Today anymore. As far as I understand, the plugin doesn't "work" properly with this WM build.
Just for curiosity, why do you enable the old Today screen? Don't you like Titanium?
Click to expand...
Click to collapse
I don't like new WM6.5-Style "Today" (IMHO it suxx). I'd prefer to use more "ascetic" WM6.1-Style, with several items(plugins) on it: Date/Time, Wireless, SPB Weather, SPB Pocket Plus or Resco Today Plugin
bgcngm said:
...
P.S.: This ROM can’t be flashed using the SD flashing method because I have removed IPL, RAMInit, USBLoad and XLDR in order not to flash those parts every time and avoid bricks. You have to use IDT flasher, which for me is the best solution.
Click to expand...
Click to collapse
I flashed it using the SD method, successfully .
(Maybe IDT is better, but all of my machines use Win7 x64... which is not working with IDT. Flashing from Virtual XP under Win7 x64 was not option last time, so I was brave.)
ThoSi, can you tell me how were you able to flash the ROM via SD? When I tried it, I got a message telling that the file size was not correct. My microSD card is formatted as FAT32, but the size (4GB) may be the problem.
I'm also running Win7 x64 in my laptop, so I have to use XP Mode in order to flash via IDT. It fails a lot of times, that's why I choose to remove unneeded parts from the ROM.
bgcngm said:
I'm also running Win7 x64 in my laptop, so I have to use XP Mode in order to flash via IDT. It fails a lot of times, that's why I choose to remove unneeded parts from the ROM.
Click to expand...
Click to collapse
I have Win7x64. I'm using VMware with WinXP to run IDT without any problems.
bgcngm said:
ThoSi, can you tell me how were you able to flash the ROM via SD? When I tried it, I got a message telling that the file size was not correct. My microSD card is formatted as FAT32, but the size (4GB) may be the problem.
I'm also running Win7 x64 in my laptop, so I have to use XP Mode in order to flash via IDT. It fails a lot of times, that's why I choose to remove unneeded parts from the ROM.
Click to expand...
Click to collapse
Kingston micro-SDHC, 4 GB ,FAT32
Phone Off, Turn on with Volume Down button + Power button, then choose yes to upgrade. The ROM was renamed to K3img.bin in the root of SD card.
(I never had error with XP Mode (although sometimes hard to attach USB device to VirtualXP), just i had to lend one of my 2GB RAM, so I have low memory now - not running VXP)
BIG666 said:
I don't like new WM6.5-Style "Today" (IMHO it suxx). I'd prefer to use more "ascetic" WM6.1-Style, with several items(plugins) on it: Date/Time, Wireless, SPB Weather, SPB Pocket Plus or Resco Today Plugin
Click to expand...
Click to collapse
I believe it has nothing to do with this build, it will look 'squashed' on all VGA and WVGA devices? At least, I had the same sort of issues on my Touch HD when using plugin's that did were not specifically programmed to also support VGA.
bgcngm said:
...
v1
Initial release, based on WM Build 23123
Includes HiSilicon Camera v1.1
HTC EzInput v2.1 (Build 2012.2024) and EzInput SIP Menu integrated
Microsoft default keyboard removed
Includes LockDevice to automatically lock the device after screen power off (more info)
WM LockScreen is enabled by default
Includes MortScript v4.3b15
Added a HTC Diamond2 sync icon (created by me) that appears in Windows Mobile Device Center
HTC GSensor SDK integrated (more info)
Disabled Start / OK softkeys and enabled text mode (more info)
Click to expand...
Click to collapse
great job!
Maybe also integrate AAreset? I find Windows Mobile behaves a lot better with a daily scheduled reset (I have it at 06h30). I think it may be a good habit for all WM devices. Dump the exe's in /windows and a link in the system menu.
But why remove MS keyboard? Could you not just make it non-default?
PS: did you not also had MMS integrated before?
I had a bit of improvement with touch screen sensitivity with following adjustments:
I've found this in another thread but dll is the same so.. i think there is kind of
improvement - test and reply
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
Here i added two lines:
"TouchSensitivity"=dword:8 ; Touch screen sensitivity, max sens. = 1,
min sens. = 63 - of course 1
"PressureFilter"=dword:0 ; 0 - disable Pressure Treshold Filter, 1 -
enable Pressure Treshold Filter - of course 0
I didn't tested other values as long as i sensed improvement, you could.
I also checked this:
HKLM\system\GWE\touch\filter and change the value to 0. Wait 25sec and restart.