Related
Right ... I think I'd better "pull the plug" as they say on this ROM.
There are currently too many problems apparent, which can not be directly fixed.
The problems unfortunately run deep.
Known Issues:
Pictures & Videos Fails to Start
IE can lockup (randomly) on Images
Odd ActiveSync Behaviour & non-communications
Phone Settings Page failures
Button Page (strangely?) still present
Backlight Level/Flickering
Duplicate Items (bad decision on my part)
BT Profile not appearing in Startup (Profile Bug actually)
Power Manager Bug
Battery Polling/Timing & Reporting
UPX'd Applications may be causing failures
Eval Calc continually reports "Error"
Repllog fills the event reporting
These problems most likely stem from various sources:
Optimization features to improve speed (Data issues / PIM corruption)
Interaction of AKU2 elements with AKU0 (repllog.exe Errors / ActiveSync)
UPX compressed applications (Random 'odd' behaviour)
Filesystem Respecification (standard Directories instead of PermDirs)
Possible stability issues in vBar (Phone Application Restarting)
GWES subsystem / IE extensions (Images, Pictures & Video Failure)
Application resource allocation failures (Eval Calc Failing, & other failing installs)
I will be addressing these issues over the weekend. There WILL be a new ROM at the end of this time (called v1.5) which will be either one of two possible incarnations:
1). Returning to a prior Alpha Test version which proved VERY stable, but contained a lot less of the AKU2 elements from Himalaya (incl. updated BT for reliability *sigh*)
2). Moving even MORE of the Himalaya AKU2 ROM into the current Beta (and correcting the other issues) so as to have as few as possible AKU0 elements coexisting.
Until that time I STRONGLY recommend that everyone not use this ROM - except for further BETA testing and/or bug reporting and/or suggestions for improvement (which would be VERY appreciated!)
TuMa v1.5 WILL still have the SAME feature-set, and SAME feature-rich look, but this will also be working on ENABLING CABs, instead of being a complete 'out of the box' ROM.
Wherever possible everything will still be entirely contained in the ROM to save as much Storage Space as possible and be feature complete, requiring only shortcuts, or registry entries to enable the full 'power'.
Otherwise, in it's "AU NATURELLE" state, the v1.5 ROM will functionally operate as a 'base only' ROM - which can then be used to build from.
My sincere apologies for the troubles you've encountered so far ... however it has been INVALUABLE with all the feedback, and I will be addressing as many of the issues found as quickly as possible.
I'd gotten so close ... the "race" was almost won ... but, it just 'blew up' in the final 50 meters.
____________________________________________________________
TuMa v1.4 has been released now for public BETA testing.
As with any BETA, backup your important data ... only time will tell how well everything has been edited/fixed/corrected in this ROM.
NOTE: There could still be some issues with this ROM, in that the performance has been increased to 'appease' those craving it, and also the feature set of the ROM has been updated to encompass everything requested.
There have been FAR too many changes, and FAR too many updates from v1.3 to even begin describing it. The ROM is now composed of 60% Wizard (Core), 20% Himalaya AKU2 (Updates), 10% Blue Angel (Drivers), and features taken from 5% Jasjar, 3% of Atom, 1% Acer, and 1% Custom Hex Edited Modules. 8)
Battery life should be much improved, speed should be about equal to Ivan's, bugs should be squashed.
Known BIG issues:
1). Sim Toolkit doesn't seem to work 100% for me - I get the menus up, but can't access all the data.
2). Bluetooth disconnect is still in this ROM.
3). Pictures & Videos Application is not working (fix being researched).
Otherwise ... let me know if you find anything!
Needless to say it's been a laborious process to get this done. So rather than bore you with words - here are some pictures instead ...
Download from:
ftp://xda:[email protected]/BlueAngel/BA_WM5/Shipped_Extracted_Updates/TuMa 1.4/
Remember ANY and ALL CABs which are in the EXTROM Folder are OPTIONAL to install. If you don't want that feature (MMS, Java Midlets, Camera, Intellipad Languages) ... then don't install it!
Use the SetOperator.bat file to set your operator for the ROM approproately.
NOTE: SX66 Users - use the SetOperatorSX66.bat file, and DO NOT install the Camera CAB.
EDIT MDAIIIUSer 02/05/06
Changed the ftp link
TuMa Boot Logos
Since I love my Blue Angel sooooo much. I've made a few custom Boot Logos for you to use.
Download from:
ftp://xda:[email protected]/Uploads/BlueAngel/WM5_TuMa/TuMa_Logos.rar
You can obviously also make your own one now ... just replace BootLogo.bmp in the /Windows directory with your own 8-Bit bitmap. Make sure that the file is the same size as the one there - then you know you have the right format. 8)
*** EDIT ***
Since I've had a couple of requests for the original artwork behind these Boot Screens, I've now prepared the PhotoShop Original Artwork file for ALL of these Logos. You can now readily make your own "Blue Angel" Logo, with or without the background, or using a solid colour, or just overlaying the Windows Mobile 5.0 elements overtop. I leave it entirely up to you! It's your BootLogo after all. 8)
ftp://xda:[email protected]/Uploads/BlueAngel/WM5_TuMa/TuMa_Blue_Angels.rar
Enjoy!
And last but not least ...
Some Games which can while away the time ...
Download from:
ftp://xda:[email protected]/Uploads/BlueAngel/WM5_TuMa/TuMa_Games.rar
Fun, fun, fun!
Gr8 work Tuma
Good
Flashing right now...
Will be back later with some news.
Thanks for all the amazing work!!
Nice Release Tuatara!
Going to try it on the weekend
Thanks
Great work Tuatara, thanks will be flashing tonight. And extra thanks for the Xmen Angel logo, that will be my logo from now on. Mutants Rule!
great job!
got this version on my sx66. No major issues.
quick question: is there a way someone can extract the "shutdown" plugin for today. My friend with a sprint 6700 wants it.
AGAIN, Great job ! and I wish I had half the brains you did so I could contribute some coding/hack. At least I will be able to help report any issues in this Beta, to make the release version a better experience for all...
i have instaled to this version, and for now now issues. to report (exept the bt )
thanks for this good work tuatara. :mrgreen:
OK, I've messed around with this new rom for a bit, and I've actually gotta say I prefer Tuma 1.3. The speed increase isn't significant enough to be worth adding more problems I outline below, without actually correcting any of the problems that I disliked in 1.3.
Improvements:
1) Single, fully functional WLAN Manager is nice.
2) I like the category based Program list, but your choice in some instances is well, strange. (ex. Windows Media in Office folder)
New Problems:
1) Phone settings was missing the first page (ring tone/style selection) on my first boot. Seems to be there now though. Odd.
2) Pictures & Videos (Renamed...) does not work at all. Definately a big piss off for me.
3) Internet explorer just locked up my PPC. I used it alot in 1.3, and I never experienced that. I'll see if I can reproduce it.
Dislikes:
1) Renamed Programs. I don't really like that you chose to rename the shortcuts to many Microsoft Programs. Ex: Pictures & Videos to Picture Viewer, File Explorer to Windows Explorer. Since every copy of WM5 has all these programs named the same since they are core programs, I don't think you should be renaming the shortcuts.
2) Some hefty programs. I liked that in Tuma 1.3 there was a nice balance between what was already there, and how much was left up to user discretion. By adding large programs with many alternatives such as Total Commander and vBar, I can't help feel you've crossed the line.
Further updates will come as I keep testing. Thanks for working so hard on this.
Going to flash tomorrow...
Thanks for all the precious work so far Tuatara!
Going to flash tomorrow...
Thanks for all the precious work so far Tuatara!
I am going to test this ROM. I am still wondering whether this one is better than Ivan's. Anyone who has any ideas please let me know, for the reason that I just want to bring my Blue Angel into full play.
good job!!!
flashing it right now
Thanks,I do in now
hmm.. cant get it to ActiveSync
Hiya..
Had major problems getting it to sync
Have reinstalled the Activesync twice now.. It connects (at bloody last! 3 hours and multiple soft resets later!) , goes through the new device blah blah, and then just sits at the Activesync page! Says it is connected, with LOADS of datat flowing between the device and A/S.. bot not synchronizing!
Any ideas?
Nowt has changed since TuMa 1.3 or Ivan... I had both working!
WOW.. damn.. I love this Forum...
Make a post, and low and behold the little fairies jump out of the screen, and waving their wands and throwing fairy dust on my PPC, it does a little beep and starts working!!!
WTF! Problem solved... Ask the fairies what they did if you can catch them!
TheLastOne said:
OK, I've messed around with this new rom for a bit, and I've actually gotta say I prefer Tuma 1.3. The speed increase isn't significant enough to be worth adding more problems I outline below, without actually correcting any of the problems that I disliked in 1.3.
Click to expand...
Click to collapse
Ok ... there were a few problems in v1.3 which are definately fixed in v1.4. The speed should be noticable, but isn't the biggest 'draw-card'. Stability, and integration should be ... but as always ... can't please everyone.
Improvements:
1) Single, fully functional WLAN Manager is nice.
2) I like the category based Program list, but your choice in some instances is well, strange. (ex. Windows Media in Office folder)
Click to expand...
Click to collapse
1). That was a bit of work ... required some 'artwork', 'hex-editor' and 'resource hacker' customization to achieve.
2). So, is "Windows Media Player" a "Tool" then? I couldn't decide either. Well ... in the end I wasn't quite sure 'where' to put that one ... you can move them easily y'know. Besides ... it is delibrately put into the main start menu as "Media Player" so you have direct access to it from there, but also have access through the Programs Menu.
New Problems:
1) Phone settings was missing the first page (ring tone/style selection) on my first boot. Seems to be there now though. Odd.
2) Pictures & Videos (Renamed...) does not work at all. Definately a big piss off for me.
3) Internet explorer just locked up my PPC. I used it alot in 1.3, and I never experienced that. I'll see if I can reproduce it.
Click to expand...
Click to collapse
1). Hmmm ... can't say I've ever seen that. Works fine on my device - so maybe something subtle is happening in the Radio Layer. Most of the RIL core is now from the Himalaya AKU2.
2). Now that's a BUG which MUST BE FIXED. Damn. It was working perfectly all the previous times I have tested and worked with it. I must have done something registry-wise which is now preventing load on my last build. I will find a fix/patch for this and post it as a CAB.
3). I've been using IE over WiFi for quite a lot of surfing - not one lockup to date - incl. having BT Stereo Wireless Headset playing (albeit a bit stutteringly) in the background. I will test further when I have more time.
So ... I'll add my own one ...
4). BT Wireless Stereo Profile has some (irritating) stuttering, but otherwise works quite reliably. Need to look at performance requirements and/or wave audio driver.
Dislikes:
1) Renamed Programs. I don't really like that you chose to rename the shortcuts to many Microsoft Programs. Ex: Pictures & Videos to Picture Viewer, File Explorer to Windows Explorer. Since every copy of WM5 has all these programs named the same since they are core programs, I don't think you should be renaming the shortcuts.
2) Some hefty programs. I liked that in Tuma 1.3 there was a nice balance between what was already there, and how much was left up to user discretion. By adding large programs with many alternatives such as Total Commander and vBar, I can't help feel you've crossed the line.
Click to expand...
Click to collapse
1). Well, you will notice that there are TWO copies of each of the applications you mention. FIRST in the Start Menu (for direct access - named as normal), and a SECOND time in the Programs folder. In order to NOT have naming conflicts for two shortcuts (if moved), they MUST be named differently. This is an unfortunate side-effect of how the Menu Manager works. You could just delete the copy you don't want. That's what Total Commander is for.
2). Again ... both of those apps can be readily 'hidden' if you wish. vBar can be quickly disabled (just turn it off in it's control panel), and similarly the icon for Total Commander can be removed. It costs NOTHING to have them in the ROM - all of your storage space is still 100% free for you to use however you wish, for whatever you wish.
Further updates will come as I keep testing. Thanks for working so hard on this.
Click to expand...
Click to collapse
No worries ... as said - the ROM is aimed at an audience to work "out of the box", not necessarily for the "power hacker" who needs to customize every last element.
But having said that - everything is READILY possible to disable in the ROM, either through checkboxes, or simply by removing shortcuts. Nothing is so 'entrenched' as to be necessary, and nothing is so necessary as to not be 'disabled' easily.
Anyways ... as before, this is BETA, and I welcome constructive feedback (and criticisms) such as this! I want to resolve the last few 'annoying' bugs and try to get to a robust and stable (feature-rich) ROM.
So ... speak your thoughts ... good / bad / ugly ... let me know!
great!
@Tuatara
Great job, Im using it for a couple of hours and until now everything is going very good.
I really like the idea of a custom build, with shortcuts names changed, lots of small softwares installed and a well tweaked registry.
I need to sleep a little. I will be using my device tomorrow as usual and will report in the end of the day.
Thanks again for the hard work :!: :!: :!:
Re: WOW.. damn.. I love this Forum...
Juggles said:
Make a post, and low and behold the little fairies jump out of the screen, and waving their wands and throwing fairy dust on my PPC, it does a little beep and starts working!!!
WTF! Problem solved... Ask the fairies what they did if you can catch them!
Click to expand...
Click to collapse
Hmmm ... this is a bit ODD. There shouldn't be any 'fairies' dancing around in the OS. Maybe a few "Angels" ... but no "Fairies".
Please let me know if you're experiencing any 'odd' behaviour. Such as 'Phone Panels' not appearing, 'Active Sync' not working immediately, 'WiFi' issues, or otherwise. Maybe a 'Gremlin' has snuck into my 'Frankenstein' ROM Monster.
Hi Just a quick query ------ any ideas if there is a beta nix for trinity in the pipline soon or do we just put that aside and come idea to see how it all is in 12 months
no info???????? no pulse?
Just might be helpful as an general update for myself and the others who desperatly await a decent operating system for their Trinity.......
Thanks all
http://wiki.xda-developers.com/index.php?pagename=Xanadux
when there is news that page would prob be the place it would be shown
looks like they need people maybe it could be you?
can't program can test
well i can't program but I would test it till the cows come home ------ I will wait
Cheers for the funny signature ---- I also come from a long line of jedi's ----- jedi taxi drivers
andytof47 said:
Hi Just a quick query ------ any ideas if there is a beta nix for trinity in the pipline soon or do we just put that aside and come idea to see how it all is in 12 months
Click to expand...
Click to collapse
I started working on a linux port for trinity. I nearly got the kernel running but there was some problems with the uart driver (if I remember correctly) that prevented it from loading completely.
I had to stop working on it due to lack of sparetime to use on this project.
I will weep uncontrollably
That hurts more than you will ever know
but I will let anyone know that any effort that is spent towards this is appreciated and time very well spent... I'm sure your work wasn't in vain
cheers
Needing linux, feeling WM6 is limiting
check out news on ubuntu mobile - they are hoping to release a distrib later this year working on as many smartphones as possible
kimusan said:
I started working on a linux port for trinity. I nearly got the kernel running but there was some problems with the uart driver (if I remember correctly) that prevented it from loading completely.
I had to stop working on it due to lack of sparetime to use on this project.
Click to expand...
Click to collapse
Hi,
Your work is quite intersting !
Would it be possible you publish the kernel version, the patches and the .config you used in the wiki ?
Thanks ^^
I've checkedout the linux kernel sources and installed the ARM toolchain from handhelds.org.
The kernel compile fines:
Code:
make htctrinity_defconfig
make
After copying the zImage file created, I tryed to launch it with Haret (also recompiled from latest sources). Since the Trinity seems to be not supported "out of the box", I had to set set the RAM start address and the mahchine type:
Code:
set RAMADDR 0xa0000000
set MTYPE 0x000004C9
set KERNEL zImage
bootlinux
The result is the screen gets black as soon as Haret jumps to the kernel... (see attached Haret's log).
Any hints on how to have more debug from the kernel ?
Where the console is supposed to be displayed ?
A big problem appears to be the fact that our device and the hermes use the SD driver in the ATI chip, not the friendly PXA27x drivers most others use. This is causing all sorts of headaches for the guys working on it and as I understand it they really need someone who can write a driver from scratch for it.
I personally thought about working on this and almost started (got a haret patch at least) and then decided that without a hardware keyboard this is gonna utterly SUCK for debugging and testing. As much as I hate to say it, I'm gonna wait for the kaiser to play with getting linux fulling running on the device. Then again, that's gonna suck since it uses a wacked cpu compared to any other...
bump ... . ..
This thread is for development discussion only. If you are not actively working on the project, please go to the discussion thread where your contribution will be more valuable. By keeping this thread clean, we can hope to get Android working on our devices much quicker.
Project Status:
We now have a 2.6.27 kernel which is capable of booting Angstrom and Android. Android looks good and is responsive, but most core functions are not there yet. Work is focused on kernel development to provide us with a stable base with working hardware. You can find test files in the second post.
We have a Wiki page where the project gets documented in some detail.
History
The development had a slow start while Orux worked out how to make the mdp talk to mddi to get a working display. We hope that progress will be faster now as there has been considerable work on the Diamond and Raphael hardware, which is quite similar to the Blackstone.
23Feb09
Screen problems fixed at last - many weeks work from Orux got the mdp talking to mddi and give us a working display.
03Mar09
Wow! So much progress in just a week! We now have working SD (some issues with brands of cards - under investigation), allowing booting direct from the SD card; working hardware buttons, and some GSM functionality (the network connects and reports of sending SMS successfully). Credit to Orux, Pichurri, Cybersalsero, Jonlar (and have I missed anyone out - not me, I have been spectating!). Pichurri has posted a full install package on teh wiki, go try it and give feedback in the testing thread.
(to be continued!)
Current tasks
Debugging SD card problems many ppl having
Getting our own version of Android (currently using builds optimised for Raph/Diam
More GSM functions - who will be first to make a call???
What can I do?
You tell us! First thing would be to get yourself set up with a development environment. You need Linux on your PC - either installed as the main OS or if you use Windows, in a virtual machine (eg Virtualbox). Then follow the instructions on the wiki to get the sources and latest diff.
Reserved for files
Here you will find the up to date files related to the project.
Pichurri's full 2.6.27 install package is on the wiki here
You should correct the posts: 2.6.26 and 2.6.27 is the kernels used. More info: www.kernel.org
brumbrum said:
You should correct the posts: 2.6.26 and 2.6.27 is the kernels used. More info: www.kernel.org
Click to expand...
Click to collapse
We are using 2 kernels:
2.6.25 --> htc-msm-2.6.25 branch in git.linuxtogo.org. This is the kernel that we are testing in our machines these days.
2.6.27 --> htc-msm-2.6.27 branch in git.linuxtogo.org. Where we will stay in a few days. Better kernel, more improvements. Here is where people from other projects are working now.
orux said:
We are using 2 kernels:
2.6.25 --> htc-msm-2.6.25 branch in git.linuxtogo.org. This is the kernel that we are testing in our machines these days.
2.6.27 --> htc-msm-2.6.27 branch in git.linuxtogo.org. Where we will stay in a few days. Better kernel, more improvements. Here is where people from other projects are working now.
Click to expand...
Click to collapse
Sorry, my mistake. Typed the message above late in the night.
But in the first and second post in this thread it says 2.2.65 and 2.2.67.
Thanks, was posted in a rush, just pm me if you see more errors. We use the odd numbered dev kernels, they will always have the most recent stuff.
A challenge for someone who likes graphic drivers:
I think linux is using ~10% of epson controller capabilities.
We have a lot of information about this controller, and open source code from epson.
Perhaps someone would like to work with this stuff.
orux said:
A challenge for someone who likes graphic drivers:
I think linux is using ~10% of epson controller capabilities.
We have a lot of information about this controller, and open source code from epson.
Perhaps someone would like to work with this stuff.
Click to expand...
Click to collapse
Do you mean things like picture-in-picture? Would be good later on in the gui - multiple desktops, that kind of thing. Also I noticed the Epson controller handles TV-out. Do we know if the out-connection exists for this, or have they just not connected it up?
Another thing to consider maybe USB on-the-go - the MSM72xx supports it; if (big if) the usb port has the right connections, it would be possible to mount external storage.
But I think it's more for later on - core functionality would be about making calls, sms, GPRS/3G. Let's see what we get from the latest kernel. Orux have you talked to the RAPH/DIAM guys on irc about merging?
orux said:
A challenge for someone who likes graphic drivers:
I think linux is using ~10% of epson controller capabilities.
We have a lot of information about this controller, and open source code from epson.
Perhaps someone would like to work with this stuff.
Click to expand...
Click to collapse
what makes you believe that?
whatever makes you believe it, share it!
if you have anything like docs,etc to share or point to lets have it !
Blackstone has got 2 graphic processors:
--->mdp, inside the chip. We have drivers in the kernel (mdp.c, mdp_ppp.c ...) I am not sure what capabilities are being used in current kernel. There are not good docs about mdp processor (I haven't got any useful).
--->epson controller. It can do:
• Picture in Picture, Transparency, Alpha Blending
• Image Rotation (90°, 180°, 270°) and Mirroring
• Scroll Assist
• AME (Auto Movie Enhancement)
• Supports up to three layers
• Image Doubling
• Bi-Cubic Scaling (1/2x ~ 8x)
• Over/Down Sampling Scaling (1/8x ~ 8x)
• Edge Enhancement
We don't have driver support in current kernel, but we have docs and source code from epson (link posted in discussion thread).
Htc Touch Pro has a tvout usb cable adapter, and seems to work in linux! I don't know if this cable works with our device.
USB on-the-go: interesting TODO.
patp said:
Orux have you talked to the RAPH/DIAM guys on irc about merging?
Click to expand...
Click to collapse
Not yet; perhaps your (or pichurri, ...) task when we have a good .27 diff. I have too much language limitations for an on-line discussion
p3ngwin said:
what makes you believe that?
whatever makes you believe it, share it!
if you have anything like docs,etc to share or point to lets have it !
Click to expand...
Click to collapse
OK, OK! These things take time - we all have other jobs I guess. We plan to get any open source docs online in a systematic way, we just need to figure out a reliable way - ie not RS etc. And we have to be careful of proprietry materials - we don't want copyright lawyers after us...
If anyone wants to offer us some rock solid webspace, that would be awesome.
TODO: Investigate instability of screen
I think that problems with screen are caused by onscreen keyboard. This keyboard is an excellent hack, but it is not 100% integrated with android.
We need to test a kernel without it.
orux said:
I think that problems with screen are caused by onscreen keyboard. This keyboard is an excellent hack, but it is not 100% integrated with android.
We need to test a kernel without it.
Click to expand...
Click to collapse
Or use the cup cake version with the keyboard in android it self.
Full doc of the epson controler : http://vdc.epson.com/index.php?option=com_docman&task=cat_view&gid=278&Itemid=40
Link is at the bottom of the wiki, add yours
I don't think we need to put all the docs at the same place, just add links at the bottom of the wiki, either hosted or link to website.
I can provide hosting if you need, just pm me.
repository
what do you guys think about creating some kind of repository(git or svn) to upload and share our blackstone kernel? i think it would make development much easier if you could see changes of other people immediately. we could use github or sourceforge.
I also think the On-Screen Keyboard is a problem.
Earlyer today I was goofing around in Android and every time I moved the keyboard, the graphics started acting very weird.(scrolling, not updating etc.)
When I hit F5 on the OSK, it would refresh Android and go back to the home page and the screen would be normal again.
Maybe route the OSK to a pip on the epson?
It's git for kernel dev, anyways svn sucks (inc troll)
If we set up a git, we'll need a guy working as a maintainer and pulling from everyone. This may become usefull when people start working in many different areas of the kernel, but for now diffs are better as they can be easily shared, and there's a howto in the wiki.
patp said:
OK, OK! These things take time - we all have other jobs I guess. We plan to get any open source docs online in a systematic way, we just need to figure out a reliable way - ie not RS etc. And we have to be careful of proprietry materials - we don't want copyright lawyers after us...
If anyone wants to offer us some rock solid webspace, that would be awesome.
Click to expand...
Click to collapse
hey i have a servage account that i hardly use which has massive space and bandwidth i could give you a ftp account to and any sql servers you may need. let me know
Rewpparo said:
Full doc of the epson controler : http://vdc.epson.com/index.php?option=com_docman&task=cat_view&gid=278&Itemid=40
Link is at the bottom of the wiki, add yours
I don't think we need to put all the docs at the same place, just add links at the bottom of the wiki, either hosted or link to website.
I can provide hosting if you need, just pm me.
Click to expand...
Click to collapse
Agreed, the wiki is the best place for this. Would you be happy for me to mention your hosting offer on the front page (which will quite soon need a better structure I'm sure).
JanSchotsmans said:
I also think the On-Screen Keyboard is a problem.
Earlyer today I was goofing around in Android and every time I moved the keyboard, the graphics started acting very weird.(scrolling, not updating etc.)
When I hit F5 on the OSK, it would refresh Android and go back to the home page and the screen would be normal again.
Maybe route the OSK to a pip on the epson?
Click to expand...
Click to collapse
Now that my friend, is a stunning idea (if it can be done simply). How does it relate to the Android OSK mentioned by xmoo? I guess the linux one is low level whereas the Android one is basically an app in the gui. Advantages to both, but if it works out of the box, the android one would mean we could essentially get rid of the linux one. We have ssh if we want to type in a console (or maybe android terminal app?).
PLEASE READ POST #2 FOR UPDATES. POST #1 IS STRICTLY INSTRUCTIONS ONLY. UPDATES ARE IN POST 2. THANKS!
Okay! Time to breathe some new life into the Shift. That's right folks. OS X now runs flawlessly on the HTC Shift and graphics are running without a hitch thanks to modified GMA 950 kexts. It's nice to play around with other devices. TBH the HD2 is too plain for me atm and I'm waiting for a Desire HD build of Android for it. In the mean time, here is some darwin goodness for the worlds favourite UMPC. First of all, to answer a few questions I encountered in the other threads, OS X will run perfectly fine on the Shift. Some people are blindly saying that the 950 has issues with OS X. Guys please do some research before posting misleading information. The 950's were the original on-boards for the MacBooks. It's impossible for it not to be supported. Better, with HW Acceleration! Okay so what works and what doesn't?
Working
- GMA 950 w HW Acc.
- Camera
-Trackpad
- Keyboard
- Speakers
- 3.5mm
- Internal drive
- Ethernet/USB Expansion Hub
- Battery/Charging recognition
- Display (although I tried forcing 1024x600 it will only create a scaled view and it's not useable)
- SD Card slot
Not Working
- WiFi
- Bluetooth
- Fingerprint Scanner (I'm not surprise, OS X doesn't have support for it anyway)
So almost everything works! Which is good news. I'm not sure if WiFi and bluetooth will work. Theoretically WiFi should work because the iPhone 2G and 3G use the exact same card that the Shift uses. However I need to find a way to extract the kexts from a firmware file which is proving to be difficult as Apple is now ridiculously locking down access to the images. Once I find this kext, WiFi should be a go. Bluetooth, I'm not sure about. I don't even know what stack it is so I can't look for a driver. Fingerprint scanner I'm not worried about as it proves useless most of the time anyway.
Okay so how do you get this working. Well I went through the trouble (and a majority of my download quota) to find which builds work best so you don't have to. Now don't come asking me for download links to these builds because I will NOT give them to you. Try google. Below is a rundown of the tested builds.
iAtkos 5i - Boots into verbose mode and kernel panics.
iPC - Does not boot at all. Installed netkas PCEFI - no change
XXX_10.5.6 - Boots into installer, won't run after installation
Leo4Allv3 - Boots into verbose mode and kernel panics.
Leopard 10.5.6 Pendrive - Boots perfectly to blue screen, loginwindows.app hangs
So the above builds were pretty helpless. The only ones that worked to some degree were iAtkos, XXX, and Pendrive, pendrive having the most success. Loginwindow.app was the only thing stopping boot. So I tried a number of things. First thing that comes to mind is replacing the app file. This didn't work and continued to crash. Then something else got my attention. the blue screen after the Apple logo turns black and then back to blue again. The only explanation to this would do this is that the graphics drivers were trying to load but failing. So this was a problem with the 950 kexts. The iAtkos disk came with excellent modified 950 drivers. Installing these onto the pendrive bulid solved this and it booted to the desktop. Below is the complete set of instructions to getting everything working including dual boot.
If you want dual boot working properly, I strongly recommend installing Windows first. That is, if you want to avoid a lot of hassle. Now as you may know, OS X is an HFS OS and Windows is an MBR. If you go about installing Windows on a drive with no other system on it, it is going to convert the entire partition table. This can be solved by creating two partitions under GPT. If OS X is on one partition, Windows will create a hybrid partition table. (MBR/GPT)
1) First you are going to need to find a copy of the leopard pendrive build and restore it to an external drive or usb. You are going to need access to a working hackintosh or Mac to be able to do this.
2) Once the restore is complete you need to go ahead and install the GMA950a.pkg and the GMA950b.pkg from inside the iAtkos disk. If you aren't able to find these I will attach these below.
3) Once these are installed, we are going to need a bootloader for the machine to see the drives. There is a great bootloader credits to netkas here.
http://www.mediafire.com/?zybzmmm5uyz
4) Plug in the external drive that you restored and installed these to and fire up your shift. Boot into the external drive bask in the glory of OS X. But we're not done yet.
5) Go and download IOATAFamily_ICH10 that's attached below and install it onto the boot drive. Reboot.
6) You need to head over to /Applications/Utilities/Disk Utility.app. Now we are going to partition the internal drive and it WILL ERASE THE WINDOWS INSTALLATION. It should come up on the top left as a grey hard disk. Now you need to select the one at the very top. i.e. the parent directory. You should now have a tab labeled "Partition." Click on that an you will get a box that has your hard drive name in it. Select "Volume Scheme" -> 2 Partitions and click on the first box. On the right, name this to whatever you like. I had Macintosh HD and select the size. Make sure the Format is set to Mac OS Extended (Journaled).
7) Now select the second partition and name it to something. I had Windows. Adjust the size and set it to MS-DOS (FAT). Now click options. and there will be three partition tables to choose from. Select GUID Partition Table (GPT). Click apply and this will erase the internal disk and replace it with two partitions.
8) Close disk utility and boot into your Windows disk. Install Windows onto THE WINDOWS PARTITION YOU CREATED. Not the Mac one.
9) After the install is complete, reboot into the external drive that you originally booted OS X off and open Disk Utility.
10) Now click on the Mac partition that you created in step 6 and click the restore tab. There will be two entry fields here, one called source, the other destination. Now depending on what the external drive is, it will either be an orange disk or a white disk. What you are going to do is drag the orange/white disk that you booted off into the source, and the Mac partition you created into destination. Tick the erase destination box and click restore. This will take roughly about 20 minutes.
11) When restore is complete, we have two more things left to do. We need to install the bootloader and set the partition as active. Now remember the bootloader we installed onto the external drive? All you need to do is install the same thing, but to the internal this time.
12) Almost there! Just need to mark the partition as active. I will post a screenshot incase this step is confusing. You need to go to /Applications/Utilities/Terminal.app. If you are familiar with Linux, this is a piece of cake. Just type the commands below.
diskutil list
Now there should be all the attached drives listed. Take not of your internal drives now. You should see on the left, /dev/diskX (where X is a positive integer) and under that will be a hash followed by a series of sequential numbers. select the appropriate number for your internal Mac partition. Mine was disk0s2. In most circumstances, it should be disk0 that you are after as it is the main drive. Next type the command below.
sudo frisk -e /dev/rdisk0 (or whatever the 0 is meant to be in your circumstance)
Ignore the error "fdisk: could not open MBR file ..."
next type:
f X (where X is the number that was next to the partition. In my case 2, in disk0s'2'. "
then:
write (hit enter key)
y (hit enter)
exit (to quit)
I FORGOT TO ADD THIS STEP! Before rebooting, run the bootloader from http://www.mediafire.com/?zybzmmm5uyz on the newly imaged internal drive. If you do not do this, the machine will boot up to a flashing underscore. You need to do this as the boot files are not copied from the first time you do it.
Now restart the machine, pull out the external drive and boot into the internal drive. There should now be a countdown timer. Press any key to interrupt this and you will get a list of your partitions. Mac OS X and Windows. if you want to go into Windows, just select it and hit enter. Similarly for Mac.
Hope this wasn't too confusing. Running OS X on alien hardware is not an easy task and if you succeeded, consider it a great accomplishment! Any questions, just ask below. I am on school holiday at the moment so I'll have a lot more time to answer! I will post up developments on WiFi so stay tuned!
Update 21/09/10
- Bluetooth operational with generic bluetooth kext
- 1024x600 mode. I've posted again after the server overload
- Ethernet works on the external hub. Only just tried it.
- For those who are experiencing problems with apps such as iTunes not syncing with iPhones or the store, there is a fix. Open the SystemVersion.plist in /System/Library/Core Services/ and change the system version 10.5.6 to 10.5.8. This will not update the system to 10.5.8 but it will trick software update into thinking you have it so you can update the software without dramas. There isn't much difference between the two except for a few bug fixes and core frameworks. Just remember not to do the security updates or the combo update.
Great work!
Seems like a great guide. I'll surely try this as soon as I get my hands on a crapple device.
Thanks
thaihugo said:
Seems like a great guide. I'll surely try this as soon as I get my hands on a crapple device.
Thanks
Click to expand...
Click to collapse
Haha! yeah i got tired of waiting around for a os x tablet. the shift is a beast.
I'm curious, why didn't you try Snow Leopard? Also, with something as non-generic as the Shift, I would have used Chameleon and went with a vanilla install so I can load each individual kext
EGOvoruhk said:
I'm curious, why didn't you try Snow Leopard? Also, with something as non-generic as the Shift, I would have used Chameleon and went with a vanilla install so I can load each individual kext
Click to expand...
Click to collapse
Good questions and thankfully I have answers for you. First of all note that 10.6 is a very lean version of 10.5. The install goes down from roughly 8GB to 5.5GB. How did they do this? They removed a truckload of obsolete drivers, most of which are needed to run the shift's older hardware. Snow Leopard also requires SSE3 to boot, which the A110 doesn't support. Also, the only practical and surefire way to patch 10.6 is using NBI (netbook installer). Don't get me wrong I did try but if NBI doesn't make SL bootable, nothing will. Anyway, Snow Leopard has a 1GHz cap which is quite hard to bypass without causing stability problems. Even running Leopard on my 667 Powerbook lagged like a b**ch (excuse the language). As for chameleon. The bootloader is a pcefi/chameleon hybrid. The reason for this is that GUI chameleon caused incredible graphics issues. The drive images on boot would be multi-colored and stretched. So GUI was a no go. Vanilla worked but it didn't WORK. The whole point of vanilla is for system updates and stability increases. Unmodified kexts did nothing of the sort for the shift. For example unmodified 950 drivers caused severe disproportionality and VGA out didn't work. In fact, the modified system kexts increased stability and boot time on an ssd is roughly 25 seconds to desktop.
Did you get touch screen working ?
I have also installed 10.5.8 version I used version fromn ASUS eee 701
as you sad there is no bluetooth wifi touchscreen working...
About wifi 8686 iPhone use ARM version the driver must be rewriten to be used on our devices...
-=xXx=- said:
Did you get touch screen working ?
I have also installed 10.5.8 version I used version fromn ASUS eee 701
as you sad there is no bluetooth wifi touchscreen working...
About wifi 8686 iPhone use ARM version the driver must be rewriten to be used on our devices...
Click to expand...
Click to collapse
Bluetooth DOES work. Touchscreen as you said doesn't work. ARM/Intel won't matter as the kexts for peripherals are OS level not architecture level. Hence the reason a PPC kext will work on an Intel based Mac.
Do you know what kind of touch screen is used in shift ?
There are some drivers from usb touck screen maybe we can use them but I didn't find any information about shift touch screen need to see linux drivers...
-=xXx=- said:
Do you know what kind of touch screen is used in shift ?
There are some drivers from usb touck screen maybe we can use them but I didn't find any information about shift touch screen need to see linux drivers...
Click to expand...
Click to collapse
I'm begging to have the same question answered. I've exhausted all resistive touch drivers for OS X and none of them are working. I'm beginning to think its a prop. touch display instead. Anyway, Linux drivers wouldn't work. Darwin has almost nothing in common. The closest thing is bsd as far as OS X applications are concerned, but again, this is just a bsd flavouring and no drivers designed for bsd will work. Sure they can be ported, but it's a much quicker route if it was to be rewritten from scratch.
Do you know what interface is used for touck screen comunication ?
Maybe it can be used for tracing output data and accomodation existing driver to our needs...
And about wifi did you get any progress ?
-=xXx=- said:
Do you know what interface is used for touck screen comunication ?
Maybe it can be used for tracing output data and accomodation existing driver to our needs...
And about wifi did you get any progress ?
Click to expand...
Click to collapse
Touch is definitely USB based (device manager->usb hid device). WiFi is looking slim at the moment. I've gone through a few iPhone firmware files to find a suitable kext with no luck. So it is looking to be a complete rewrite of the driver which will be quite difficult as there is no support for Marvell as far as WiFi goes. Apple only ethernet by Marvell/Yukon, thus ruling out the possibility of common driver properties between other kexts.
Just in reply to a post before the server crashed. None of the touchscreen drivers worked and the panel didn't get recognised. Also the download for the resolution enabler is back up in post 2 again. And it looks like we made it on engadget. AGAIN.
Featured article on egadget congrats.
Sent from my htc hd2 using XDA App
roflcoptrbbq said:
Featured article on egadget congrats.
Sent from my htc hd2 using XDA App
Click to expand...
Click to collapse
Hahaha thanks. Its actually on a lot more now. Its almost a virus! hahaha
could you get the drivers from 10.5 and shove them into 10.6, also see if you can use the axitotron modbook drivers
http://www.axiotron.com/index.php?id=home
i will try all of this next week, as i was about to sell my shift....
it's on marketplace here.
ayilm1 you are awesome.
shad0wfire said:
could you get the drivers from 10.5 and shove them into 10.6, also see if you can use the axitotron modbook drivers
http://www.axiotron.com/index.php?id=home
Click to expand...
Click to collapse
Yeah mate. that did cross my mind until i realised axiotron hasn't done anything to do with Synergy touch yet, meaning no finger touch at all. It's all wacom based. Synergy will incorporate resistive with this, or maybe even capacitive, but no guarantees on it working with the shift. I have started to build a kext for it but it's really difficult when you don't even know the manufacturer of the panel you are writing the driver for! Thanks Seb, just trying to help out the xda community!
Wifi
If it uses the same wifi card as the iPhone 3G, the firmware is decryptable. Head onto the idroidproject.org forums. I spent time on there putting android onto my 3G and the wifi binary files were needed as they were copyrighted material.
If you like get back to me and I can get the binaries for you? If not it's pretty simple just requires some simple linux command line skills, which I'm
Sure you have since you undertook this project.
Anyway good luck, hope this helps with getting wifi to work!!
I'm putting up this thread because there is a good bit of questions that get asked about the difference between the SYS builds. While Microsoft and its partners don't give us a real breakdown of them, we can at least get results on which one is faster than the other. That is the purpose of this thread. If you have any relevant information for me to add to this, let me know. If I add your suggestion, I will, of course, credit you. This is relevant to pretty much all WM6 devices, but I'm making this specific to the Rhodium as that is the only device I plan to support with benchmark results. I'm following the same pattern from the benchmark thread that was started HERE by daeron.be.
To start off, Da_G, a1d2catz, and Cotulla originally posted about the different builds. OndraSter posted to elaborate on a couple of the builds.
Branches of WM Development: Here is what all these different version numbers relate to, and a summary of their features.
212xx = AKU1, all builds leading up to and including WM 6.5
213xx = MOT motorola
214xx = ???
215xx = SAM samsung
216xx = HTC htc
217xx = COM1, continuing dev of 6.5.0.1 - 6.5.0.40
218xx = COM2, continuing dev of 6.5.0.50
219xx = MD, feature test branch, pretty much dead now. (unstable features are added here, this tree is based on COM1, so older base OS code, but the UI/UX code is newer)
22xxx = SEMC sony ericsson
*230xx = COM3, continuing development
*234xx = COM4, appears to be abandoned.
*235xx = COM5, more GUI changes here. New Outlook Interface.
*236xx = LG Electronics Branch
*24xxx = Possible HTC branch
*25xxx = SEMC - Sony Ericsson
*280xx, 282xx = WMD. This is a continuation of com3 from 23090. Most of the changes appear to be with IE
235xx is the only branch that has threaded email natively
290xx = Unknown branch
There was 219xx about half year ago, with numbers ending about 21936 (or maybe 45 or about that). It was test branch, where new features (like... supernew, something like previous 230xx where appeared huge softkeybar etc) were added. This branch was dead, just as looks 234xx now.
But, there was also COM2, with numbers 218xx. Well it reached its maximum, 21899. But instead of making new number line, MS/HTC chose to use already used 219xx. Here is where the mess comes from
The WM version numbers are as follows:
216xx = 6.5.3
219xx = 6.5.0
220xx = 6.5.3
231xx = 6.5.3
235xx = 6.5.5
236xx = 6.5.3
246xx = 6.5.3
250xx = 6.5.3
282xx = 6.5.3
290xx = 6.5.3
Click to expand...
Click to collapse
Updates:
14 March 2011: Finished benchmarks on 21689, 28245, 29011, 29013.
09 March 2011: New builds have begun rolling out. Testing begins tonight on 21687, 29008, and 29009.
...trimmed every month...
Results
I based these blank uncompressed ROMs on the latest shipped T-Mobile 6.5 ROM (1.91.531.4), disabled all ext packages, and swapped builds. I've listed all of the builds that I currently have. If you have one for me to test that's not on the list, send it my way as long as it's WVGA.
SYS builds tested:
216xx: 21659, 21661, 21663, 21665, 21671, 21674, 21677, 21679, 21680, 21681, 21682, 21683, 21684, 21685, 21686, 21687
219xx: 21904, 21905, 21907, 21908, 21909, 21911, 21914, 21916
220xx: 22013, 22018, 22019, 22021, 22022, 22024, 22027, 22031, 22036, 22037, 22038, 22040, 22041, 22042, 22044, 22046, 22047
231xx: 23120, 23121, 23129, 23130, 23132, 23133, 23134, 23135, 23136, 23138, 23139, 23140, 23142, 23144, 23145, 23146, 23148, 23149, 23150, 23151, 23152
235xx: 23569
236xx: 23651, 23654, 23656, 23658, 23659, 23662, 23664, 23667, 23670, 23676, 23678, 23680, 23683, 23686, 23688, 23689, 23690, 23691, 23694, 23697, 23698, 23699
246xx: 24609, 24610, 24611, 24614, 24618, 24619, 24620, 24626, 24627, 24628, 24630, 24631, 24635
250xx: 25018, 25024, 25026, 25027, 25028
282xx: 28233, 28236, 28237, 28238, 28240, 28242, 28243, 28244
290xx: 29002, 29003, 29005, 29007, 29008, 29009
Custom ROMs tested so far:
NRGZ28 Energy: 21916, 21684, 28244, 23148, 23699 - Update coming soon!
Ondraster LBFAR: 21899, 23569
dotcompt DeepShining: Coming soon!
Problem builds:
These are builds I was either unable to import into my kitchen, or cook for various reasons:
22016, 21664, 23123, 23125, 23126, 23127, 23566, 23694
Method and relevant information
If you are planning to send me results or anything, be sure to include the version numbers of the programs you used. SPBBenchmark and Test OpenGL are both freeware. Coreplayer Mobile costs around $30.
Benchmark programs used:
1. SPBBenchmark 1.6
2. Test OpenGL 18.01.2010
3. CorePlayer Mobile 1.2.5
Test Method for blank builds:
1. task29 then flash the ROM without the SIM card.
2. The storage card is left in to install the benchmark cabs.
3. Go into airplane mode.
4. Disable switching screen off and turning the device off.
5. Install benchmarking apps
6. Soft Reset
7. Run SPBbenchmark and disable the following:
Built-in applications (whole category)
Arkaball frames per second
Copy 1 MB using memcpy
8. Run TestOpenGL for about 3 cycles of benchmarks (each cycle is 4 benchmarks) and then turn it off
9. Run three Avatar trailers, note down the results (%). Use default Coreplayer settings and run benchmark immediately after files are loaded.
Trailer found HERE. Note that trailers ARE copyrighted material and are NOT subject to fair use. The link provided is to show what I am using. I own the BluRay disk and ripped it from there. The link is also 720p. My original clip was 1080p. Each exported trailer was set to 800x480 resolution.
One trailer was converted to 25fps, 768 kbps - XHQ
One trailer was converted to 23.976fps, 512 kbps - HQ
One trailer was converted to 20fps, 384 kbps -MED
I wasn't able to determine the original qualities from daeron.be's thread, so I made my own. If you know more about it, please let me know for more accurate results.
10. Run Video Flash benchmark with PIE using a downloaded version of the animation found HERE. If you plan on doing this yourself, download it to your device and run it with IE. Just put it in a root dictionary (\) and then input \benchmark.swf address in IE. On some ROMs you might have to wait a while before the flash starts (there won't be any signs of loading). Run the benchmark (if you want your result to be compatible with mine you MUST run it with flash file in full screen).
11. Collect results
Test Method for Custom ROMs:
Same as above with three exceptions.
1. Run SPB Benchmark with ONLY "Built-in applications (whole category)" test disabled. Leave everything else on.
2. Connect the device to the PC after running the SPB Benchmark test. You may have to go to Start > Settings > Connections > USBtoPC and untick the "Enable faster data synchronization" box to get it to work.
3. Copy the "Spb Benchmark Results.xml" from \My Documents to the PC and grab the results from there with the decimals. I use every decimal in the file. I then trim the trailing zeros in the Excel results file.
I figure since some people will probably use this as a guide of which ROMs are "best" or "fastest," that the results should be as accurate as possible, which is why I'm including the decimals in the custom ROM results, but not in the blank builds.
FAQ
When posting to this thread, please use proper English only, and do not use profanity.
You should not type like a high school girl, either. Leave the "plz," "sum1," and "u" back on the playground.
Ask for help like an adult and be treated like one.
1. What are these benchmarks for?
Basically this is just a measure of performance on different SYS builds to see which one is the fastest. These tests do not indicate which build is really “the best.” It is a measurement of speed on the process of copying files, reading directories, and playing video. To truly “test” a ROM, you need to spend a few days with it.
2. Which radio version are you using?
To the best of my knowledge, this has no affect on the results. However, my current radio version can be found in my sig. I do not change it for these tests.
3. Does a task29 before each flashing affect the results?
There are problems with "ghosting" in ROMs where residual data is left over from a previous ROM. To avoid this, I perform a task29 first. If you want to know more about task29, then visit that thread.
4. Are those benchmarks accurate?
I test the ROMs with SPBBenchmark once as it averages the results of 13 tests each. I use three rounds of OpenGL and use those results as it takes the highest result from there, which is what we want. An average in that category is useless as we want to know what the best result is for this, not the average. I run each Avatar trailer three times and take that average. Flash is pretty straightforward and kind of just for fun, so I only do one test. All of this means that the results may vary by a very small margin. If you don't believe my findings, you are always welcome to test yourself. Anything within a 1% margin of error is acceptable.
5. Why do you disable "Built-in applications (whole category)," "Arkaball frames per second," and "Copy 1 MB using memcpy" for SPB Benchmark on the blank builds?
They don't make a noticeable difference in the results. I could grab the *.xml results file from \My Documents, but it's not that big of a deal in the blank builds as they are just a stepping stone for chefs to see what they like and don't like. If you want to see the results, test them. I use them for custom ROMs because it makes sense to do so. People will interpret these results loosely, and it is better to be more accurate with them.
6. Why aren't you using Linpack?
Great question! I would if this were Android as there are current programs for it. The only one available for use on the WinCE platform is almost three years old at this point. Also, SPBBenchmark measures MFlops, so I don't really need it, do I?
7. Why don't you test battery life?
Battery life testing takes too long, plain and simple. When you flash a new ROM, getting the battery set properly takes about two or three cycles (drained to 10% and then charged to 100%) before it "settles." Even if I did nothing but play movies with the backlight and sound at max while downloading files via wifi and using Bluetooth file transfer, it would still take about an hour or so to drain the battery enough to charge it back again. You would need to drain and then charge AT LEAST once, preferably twice, before running a battery meter to test. This means I would be stuck on one ROM for hours before moving to the next one. My current set up allows for about 30-45 minutes per ROM to test. This is much more reasonable than 4 hours each, don't you think? If you decide to do test it yourself and want to share, then be my guest.
8. I didn't see you use xxxxx version of a build. Why is that?
I either don't have access to that build, or it isn't a WVGA build. If it is a WVGA build and I don't have it listed, send me a link, and I'll test it out.
9. Can I test the ROMs too?
Sure, why not? I won't use your results, though. There was a massive flame war in the aforementioned original thread that was partly fueled by other users posting results. I don't plan to start any nonsense here.
10. Would you mind testing a custom ROM for me?
YOU MUST GET THE CHEF'S PERMISSION FOR THEIR ROM'S RESULTS TO BE POSTED. I need them to PM me with an ok. I basically want it in writing. NOTE: Once a chef says it's ok to test, I will not remove them from the tests; make sure they understand this.
11. Why am I getting different results?
There are several little nuances that can influence the results in minor ways. If you're getting significantly different results than I am, then I'll look into it again. Keep in mind that using a different device than I am may affect the results as well. However, I will not use any other users' results without verifying them myself.
12. Some of this material looks familiar. Did you steal this?
Yes, basically I did. I figured I'd restart something similar for reasons I've mentioned as well as making it more Rhodium specific. Besides, the original poster, daeron.be, hasn't even logged on in a long time. His thread hasn't been updated since September of 2009 as well. I'm going to use most of their formatting and previous material to build on. If someone has a legitimate problem with this, then PM me.
13. I don't believe that you got "X" results with "X" ROM! I think it's WAY better than all the rest!
I don't care what you think. That isn't a question anyhow. I'm doing this for myself and sharing with you all. Either take it for what it's worth or do it yourself.
14. You didn't respond to my post. What gives?!
I have a life. I'm on XDA way more than I should be as it is. I will generally respond to questions and the like. If you just post to say "Good job" or "Thanks, man," don't expect me to respond. I might, just don't expect it. Just consider this answer here as a general "Thanks" and "You're welcome."
15. You're from New Orleans? What's it like?
People are wonderful; food is amazing; Mardi Gras rocks. Let's keep the thread on topic, please.
Requests
If someone wants to change the BG colors of the spreadsheet to something they like better, be my guest. If I like the colors, I'll keep it.
Please take the poll at the top of the page. If enough people use this thread with other devices, then I will consider moving it to the Chef's Central forum.
I am slowly adding custom ROMs to the results. I need a few people to notify me when the ROMs you're using are updated. This includes Energy, Simplicity, DeepShining, Core Cell, and other popular ROMs.
Custom ROM testing
Ask your chef if he/she would mind having their ROM(s) tested and compared in my results. See below for rules:
All custom ROMs would be separate of the clean builds, but compared all together.
Understand that once permission is given, it cannot be taken away. (I don't want anyone trying to revoke permission after results are posted to take advantage of my system.)
Have the chef PM me with the green light if they want it included.
All results will either be performed by me, or verified by me.
I will not measure battery performance. See FAQ.
These results are not conclusive to picking a "good" ROM. It's a jumping off point. Test yourself and see which one works for you. This tests certain factors of the ROMs. This doesn't test for stability or feel of the ROM. Do that yourself.
Chefs are allowed to "pick and choose" which ROMs they want tested. If they cook multiple flavors or builds, they can decline to have certain ones excluded from results.
If you have a problem with my methods, you are welcome to do them yourself. I am doing my best to ensure that this is as objective as possible.
Contact
If you feel like contacting me or need to request info or whatever, you may PM, e-mail, or message me on Twitter.
Donate
Coffee keeps me cranking out results. DONATE to keep the caffeine flowing. If I see that you've donated, I will probably take a bit more care in listening to your problem/suggestion/comment. Make sure that you include your XDA user name so I can give you credit.
beautiful... cant wait to see results
Subscribed.
Imho you should test blank WM builds. Or at last be sure that the EXT/XIP packages are same. However the idea of testing different builds fits me.
Shame that usually the fastest builds leak memory like hell.
Jackos said:
Subscribed.
Imho you should test blank WM builds. Or at last be sure that the EXT/XIP packages are same. However the idea of testing different builds fits me.
Shame that usually the fastest builds leak memory like hell.
Click to expand...
Click to collapse
I used to believe that until we started seeing the 21680 and 21681 builds come out. They really are quite faster than most of the others. When NRG was using the 23xxx builds, that was the case where the faster they ran the more memory was "spirited away," so to speak. I'm finding a much more stable experience with the 21680 and 21681 builds than most that I've seen.
In any case, the results will speak for themselves. The first three should be posted in a few hours or so.
For anyone who missed it, I've posted the first test file. I only did a single test for each one. In the future I will do an average of three results per test. I only did a single one due to time constraints mostly. That being said, this first file is just a test both for me and for anyone viewing to get a feel for what it's going to look like.
Any questions; let me know.
cajunflavoredbob said:
Requests
The first thing I could use help with to speed up my testing is for someone to point me to the reg key that disables Sense. This would make it easier for me to just drop it into XDA_UC to have the changes made automatically.
[..]
Click to expand...
Click to collapse
This isn't a reg key, but I think there are mortscripts that disable Sense. Maybe this might help?
http://forum.xda-developers.com/showthread.php?p=8684203
I think JVH3 talked about scripts that disable sense too, so perhaps he might be able to help you out there too?
Great work, this is really interesting!
Using mortscript you can do this:
Code:
RegWriteDword("HKLM","\Software\Microsoft\Today\Items\" & ManilaName,"Enabled","0")
RedrawToday
Sleep(5000)
ManilaName is usually HTC Sense, I think. The sleep can probably be shortened. Nice thread!
why not just build a rom free of all ext packages?
just sys and oem packages.
that way it is a better comparsion of sys builds.
no?
sh4d0w86.
cajunflavoredbob said:
The first thing I could use help with to speed up my testing is for someone to point me to the reg key that disables Sense. This would make it easier for me to just drop it into XDA_UC to have the changes made automatically.
I could also use the reg key that sets the device into flight mode for the same reasons.
Click to expand...
Click to collapse
Disable Sense:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:0
Flight mode on boot:
Code:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State]
"Phone"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
"LastEquipmentState"=dword:00000001
[HKEY_LOCAL_MACHINE\System\State\Phone]
"Status"=dword:00400030
"Radio Ready State"=dword:00000000
Random offtopic: I believe that all roms should have the radio turned off by default.
Jackos said:
Random offtopic: I believe that all roms should have the radio turned off by default.
Click to expand...
Click to collapse
I'm curious, why?
seeM_ZA said:
I'm curious, why?
Click to expand...
Click to collapse
Because not anyone wants to run the Connection setup after rom upgrade? Not anyone wants to get all those sms messages right after flash. It's just more convenient then taking the sim card out and putting it back into the device when you're ready (not healthy for the card too).
Not to mention the CDMA phones without simcard, having the radio enabled by default in ROM must be a pain in the ass if you flash several times or hardreset to test different software!
Excellent work on this, cajunflavoredbob!
I look forward to reviewing the results that you come up with on your comparisons.
I am already interested in some of the results that you found in the first tests and will watch that pretty closely.
One thing that I noticed - when I first opened the spreadsheet the colors pretty much come on like a freight train - can those be toned down a tad? These old eyes finally adjusted to them but a lighter shade of colors may be more aesthetic...
Thanks for this contribution!
sh4d0w86 said:
why not just build a rom free of all ext packages?
just sys and oem packages.
that way it is a better comparsion of sys builds.
no?
sh4d0w86.
Click to expand...
Click to collapse
If you read the first two posts, I addressed this twice. That's what I plan to do. I need to get a feel for this myself and find ways of doing it quickly before I move on to the kitchen.
Jackos said:
Disable Sense:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:0
Flight mode on boot:
Code:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State]
"Phone"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
"LastEquipmentState"=dword:00000001
[HKEY_LOCAL_MACHINE\System\State\Phone]
"Status"=dword:00400030
"Radio Ready State"=dword:00000000
Random offtopic: I believe that all roms should have the radio turned off by default.
Click to expand...
Click to collapse
Wonderful! Thanks. This will save some time! I agree with you on the radio being off by default. With the number of times I flash my device during the week, it would really help not to hear the alerts going off twenty times when I start up. I use NRG's ROMs by day, backup with Sprite Backup, and then toy with my personal ROM at night normally. Now, of course, I'm going to be flashing even more than that with this new project.
toucan said:
Excellent work on this, cajunflavoredbob!
I look forward to reviewing the results that you come up with on your comparisons.
I am already interested in some of the results that you found in the first tests and will watch that pretty closely.
One thing that I noticed - when I first opened the spreadsheet the colors pretty much come on like a freight train - can those be toned down a tad? These old eyes finally adjusted to them but a lighter shade of colors may be more aesthetic...
Thanks for this contribution!
Click to expand...
Click to collapse
I can't promise you that I'll get to it, but I'll put it on my to-do list. I basically stole the formatted speadsheet from the other thread. I was about 2/3 of the way through with making my own, when it dawned on me that there was probably one already made. Their formulas covered some things I hadn't yet thought of, so I'm going to be using this for a while.
In other news, I'll be working on this again today, so check for updates tonight. I'll post any updates in the second post.
cajunflavoredbob said:
To-Do List
Change crazy background colors on spreadsheet.
Build clean ROM based on latest T-Mobile shipped ROM
Clean up first post.
Finish learning Italian.
Click to expand...
Click to collapse
One down (see attached).
piaqt said:
One down (see attached).
Click to expand...
Click to collapse
Thanks, but I still need the backgrounds. It helps me find the fields more easily. I'm going to experiment with different colors soon. This isn't my top priority, though. I think, lighter, not brighter colors would do better. We'll see what happens. I'm working on cooking the new ROM right now. Well, not right now, but I'll be starting soon. Hopefully I can get this completed within the week. I can only flash/work at night on this as I need a functioning device during the day.
cajunflavoredbob said:
Thanks, but I still need the backgrounds. It helps me find the fields more easily. I'm going to experiment with different colors soon. This isn't my top priority, though. I think, lighter, not brighter colors would do better. We'll see what happens. I'm working on cooking the new ROM right now. Well, not right now, but I'll be starting soon. Hopefully I can get this completed within the week. I can only flash/work at night on this as I need a functioning device during the day.
Click to expand...
Click to collapse
Haha... I wholeheartedly agree - it is absolutely necessary to have the colors - but perhaps not so bright!