[Q] How is android supposed to run? - Touch Diamond, MDA Compact IV ROM Development

I have tried both a Froyo variant and a Gingerbread variant on my Diamond but for me its not usable at all .. It lockups every 30 seconds for like 1 minute. Just when my devices screen goes black i am barely able to turn it back on again.
Now im not complaining about the devs work here, dont take it that way.. I just want to know if its supposed to run this way or if its something i do wrong?

Da9L said:
I have tried both a Froyo variant and a Gingerbread variant on my Diamond but for me its not usable at all .. It lockups every 30 seconds for like 1 minute. Just when my devices screen goes black i am barely able to turn it back on again.
Now im not complaining about the devs work here, dont take it that way.. I just want to know if its supposed to run this way or if its something i do wrong?
Click to expand...
Click to collapse
try to install android rom on your device's internal storage and use GenYDualBoot to be able to run it from windows !

Hakim Rahman said:
try to install android rom on your device's internal storage and use GenYDualBoot to be able to run it from windows !
Click to expand...
Click to collapse
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.

Lipinsky said:
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Click to expand...
Click to collapse
I have two 2 months applying it to my Htc diamond {dual boot = Eto.Y 2.4a WWE + XDAndroid FRX07.1 (on internal storage)}

Lipinsky said:
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Click to expand...
Click to collapse
The usability has definitely increased over the years but it is still more a concept than a real operating system as the hardware and software dont work together very well. This is because there are no official kernels, drivers or anything provided by HTC. The xdandroid team has done an incredible work to get android running on this device, but they couldnt find a way to properly get android on the NAND because the storage is too small. Thats also why you have to start it via windows mobile and cant directly boot to it, it runs out of the SD Card. So you will never achieve a nice performance as long as the OS isnt located on the NAND. The lags and force closes you are certainly experiencing derive from this problem. The device itself would definitely have the power to run android at an acceptable performance.
As far as I know the development has ceased. If you search the corresponding threads you will find the statement of the devs. Here is were you can look:
Froyo, Gingerbread: http://forum.xda-developers.com/showthread.php?t=951981
Froyo 07: http://forum.xda-developers.com/showthread.php?t=951811
Gingerbread 0A: http://forum.xda-developers.com/showthread.php?t=711692
wiki: http://xdandroid.com/wiki/Main_Page
blog: http://southcape.org/category/android/

yeah development seems to be halted, its nice to play with, but not as main os for day to day use

Related

android as main use

can i use android as a main system.
so i want to turn my phone on, and get directly in android..
is this possible... ??
thnks
larsoss said:
can i use android as a main system.
so i want to turn my phone on, and get directly in android..
is this possible... ??
thnks
Click to expand...
Click to collapse
Why would you want to do that? It is still in BETA stage and battery drainage is completely high....unbelievably high.
If you still want to go with it 2 options:
1 - Buy a Android Phone if you love it so much.
2 - http://forum.xda-developers.com/showthread.php?t=601751
This link will give you the steps - this is what it has to say:
15.01.10 UPDATE NEW*GSM RAPH ONLY: MichyPrima has created a lite WinMo that automatically loads haret from your SD card. It loads pretty quick and i can confirm it works Give it a go if you're tired of waiting for WinMo to load. It now has a boot option so just wait until you see Booting countdown and touch the screen. It will offer 4 options
Reboot, Shutdown, USB mass Storage and Continue Booting Android
Best of Luck
man, can u make a rom based on wm6.5 look like android?
salim1001 said:
Why would you want to do that? It is still in BETA stage and battery drainage is completely high....unbelievably high.
If you still want to go with it 2 options:
1 - Buy a Android Phone if you love it so much.
2 - http://forum.xda-developers.com/showthread.php?t=601751
This link will give you the steps - this is what it has to say:
15.01.10 UPDATE NEW*GSM RAPH ONLY: MichyPrima has created a lite WinMo that automatically loads haret from your SD card. It loads pretty quick and i can confirm it works Give it a go if you're tired of waiting for WinMo to load. It now has a boot option so just wait until you see Booting countdown and touch the screen. It will offer 4 options
Reboot, Shutdown, USB mass Storage and Continue Booting Android
Best of Luck
Click to expand...
Click to collapse
From my experience, the android rom by babijoee is good for daily uses. It's fast, and battery drain is not an issue any more.
calvin83 said:
From my experience, the android rom by babijoee is good for daily uses. It's fast, and battery drain is not an issue any more.
Click to expand...
Click to collapse
I have been following the thread for Android on regular basis and i still see that Batter Drainage is an open issue where the chefs are trying to get a fix. I am sure if you use the Android...it will not last more than 3 hours!
Carry your charger along
salim1001 said:
I have been following the thread for Android on regular basis and i still see that Batter Drainage is an open issue where the chefs are trying to get a fix. I am sure if you use the Android...it will not last more than 3 hours!
Carry your charger along
Click to expand...
Click to collapse
Sorry to tell you that you are wrong. My diamond can use for 8 hrs (normal phone calls and sms, etc) using the latest build. I think you may have missed most of the threads talking about the latest development?
8 hour...sounds nice...would love to try that...you got the link for this build?
in my opinion because of the intense overheating that you can get if u use your phone like a dayli one ( internet ..bla bla bla) , yopu can damage it..
yesterday y was on the android on the net with my diamond and radio 1.13.25.55 the device uverheated and my touch went nuts....was not usable .. even in winmo..changed the rom ... the same..after changing the radio is ok now but i have a strange impresion that something is wrong with it because it overheats even in winmo...so:
thx very much to the guys that port android on our phones and can harddly whait to have it as a stand alone but..:|...for now i am not trying android anymore... this is only my opinion thx
What zimage were you using??? I was very surprised today when I started using this one: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100116_163203.tar
It doesn't run very hot anymore and speed is very good.
You can take a look at my post here if you like: http://forum.xda-developers.com/showpost.php?p=5391590&postcount=167

I dont understand all these roms :(

hi all, if im right then my warrenty on my TP2 finishes in september.
So what im looking to do is stick a new cooked rom on there.
im pi55ed off with my phone because its sooo slow and it keeps failing on me but i dont want to get rid of it really because 99% of my friends either have crackberrys or ipoones and i want to be different.
i am a complete n00b with all the techy stuff like tweeking the phone.
I have a few questions for people with cooked roms
1 - what sort of memory does your rom run at?
2 - how long does your battery last and on what type of usage?
3 - do you need to keep doing soft re-sets?
4 - is your new rom quick and reliable?
5 - are all the features quick and realiable such as bluetooth?
i think thats it for now, i will start looking into the roms more from now on so i can hopefully just do it once and do it right the first time.
however if there are any chefs in london who are willing to build me a complete custom rom then PM me and we will discuss it further about the rom and pricing for your time ect...
THANKS in advance!!
1. The memory of some chef's ROMs can run as low as 40% on startup, moving up to about 50-60%. It depends. Look for the "lite" or "clean" ROMs for better memory.
2. The battery lasts me all day, heavy use through texting, phone calls, and internet. Using GPS, I'd imagine your battery would die fast, and phone calls don't seem to last longer than 3 hours before needing to be recharged.
3. Sadly, soft resets are needed for almost every WinMo device. That's the downside of all WinMo devices, though on the plus side, you get infinite customizability.
4. One of the most reliable ROMs with the most features is Valkyrie's ROM by Agent_47. I'm honestly no fanboy, but I have tried everyone else's ROMs, normal version, not lite or clean, and they all lack, or are crippled.
5. I don't use bluetooth, but wifi, phone signal, and GPS signal depend really on what radio you use. The different radios can be found in the ROM section. I use the most current one, .77, and I get good strength on all of the above.
thanks for the info, heres a bit more about my phone and its uage atm...
on the stock rom im using with using cleanram my phone runs around 60% - 70% but startup is just over 40%
Also i found my battery lasted 2 days when i had a 2gb card and now just over a day if im lucky with the 8gb card, so i may change it for a 4gb card which should be enough space for me.
Well, some clean and lite ROMs have as much as 80 MB free at start up (meaning, I believe that you would only have 20% on startup; any members can correct me if I'm wrong). I have only had 40% at most at startup, because I use feature packed ROMs.
I don't know anything about the SD card using more phone power, but you can give the 4 GB card a try. I get over 2 days on minimum usage with an 8 GB SD card. With max usage, as I said, I get about a full days use, with around 40-50% of battery life left.
also if anyone is local to me and wouldnt mind letting me have a quick play with there tp2 with a cooked rom to see how different it is to stock then please PM me
i went into a vodafone store today to double check about my warrenty, but after the 12 months manufacturer warrenty is over then vodafone have their own warrenty to cover the phone untill my contract is over.
now i know this im unsure if i should flash my rom now incase i do have anymore problems with the phone ??
what do you all suggest?
Just do the flash and get it over with You only have ONE first flash and then after that everything wont be as stressfull..
Also.. if you want to see what custom roms look like running on the phone just search for some custom roms on youtube. I'm sure you'll see some there. You'd get a more thurough view of what they do then if you were just bumbling around with it for 5 minutes on your own.
fair enough, i need to get my compuuter working then i guess to flash it!!
when tmo had a rom flash from wm 6.1 to 6.5, all i had to do was download the file...why are these roms on here implemented differently...???
da9th_one said:
when tmo had a rom flash from wm 6.1 to 6.5, all i had to do was download the file...why are these roms on here implemented differently...???
Click to expand...
Click to collapse
Because custom ROM's don't have the critical "signature" that can only come from the manufacturer or carriers themselves. The stock SPL won't allow ROM's that don't have that signature, so that's why you have to replace SPL with a custom one when you want to flash ROM's issued by anybody than the carriers or HTC.
Sorry for the threadjack... but i was wondering the same things as the topic starter...
May i just add a few more questions?
*Roms like Energy, do they support BT and GPS?
*Is the problem with the sms lag (phone not waking on receiving) solved by a cooked rom?
*What are the major drawbacks when switching for standard to cooked? Ok the waranty is cancelled but anymore?
*I have a WWE version with WM6.5 ==> can i only install rom for 6.5 or can i install roms based on 6.1?
*I've looked at radios and the compatiblitylist... does this mean i have to install the wwe radio to get my device working?
feel free to ask questions here about roms ans im interested in the answers too
also the other week i saw a thread that had 2 cabs that make the TP2 run quicker and i had to get off of the laptop and now i cant find it. does anyone know what i mean if so can you help me locate the cabs.
Thanks
SMF_12 said:
also the other week i saw a thread that had 2 cabs that make the TP2 run quicker and i had to get off of the laptop and now i cant find it. does anyone know what i mean if so can you help me locate the cabs.
Thanks
Click to expand...
Click to collapse
I don't know about two cabs to make it run faster, but there's two that will help with the memory management and help keep more of it free for you, is that what you're thinking about? They're called the SSK Dynamic Resource Proxy cab and the no push internet cab.
I recently flashed deepshining x7 rom and I can't believe I waited so long. My TP2 feels faster and I love all the options available such as Cookie's home tabe editor and the such. If you haven't already done so, I suggest you flash. You can always flash back to the original if you don't like it.
sirphunkee said:
I don't know about two cabs to make it run faster, but there's two that will help with the memory management and help keep more of it free for you, is that what you're thinking about? They're called the SSK Dynamic Resource Proxy cab and the no push internet cab.
Click to expand...
Click to collapse
I think those are the ones and i will search for them when i am on next time, thanks!!!
SMF_12 said:
I think those are the ones and i will search for them when i am on next time, thanks!!!
Click to expand...
Click to collapse
Here they are, just wanted to make sure we were thinking of the same things
thank you very much!! I wish this forum had a reputation thing like other forums
SMF_12 said:
thank you very much!! I wish this forum had a reputation thing like other forums
Click to expand...
Click to collapse
You bet! And yeah, these are the first two cabs I recommend all new Rhodium owners run...I don't know if they'll clear up all your issues, but you should at least see a significant change in available RAM.
Ive just put them onto my phone and doing a soft reset!
Ive also changed to the windows today menu last night and its running a bit better with that!!

Current integration of Android with HTC diamond

I am a newbie to WinMo and Android devices.
I know it is possible to run Android on HTC window mobile pre-installed device, with the matter of the non-working camera.
I wanna know actually what is process/method which can makes Android possibly runs on HTC diamond, and does it mean once we have this boot system, we can boot any Android even the latest 2.2 Froyo?
All I want is to get some knowledge which can help me to step into this area, I love software engineering and find that this forum is the one which most positive users come, so hopefully I can start building sth from sketch in here.
Many thanks in advance, and thanks for the patiences and the kindness of knowledge sharing.
Hi, as you said, it is currently possible to boot an Android system from a WinMo one. But they are some issues left, mainly the battery life. Indeed, battery drains pretty fast with Android (and the indicator is not accurate at all).
Concerning Froyo (2.2), I ran many android systems on my Diamond 100, and Eclair versions (2.1) are really very slow, that is why I am currently using a Donut version (1.6), which is pretty fast and stable. So I'm not sure the Diamond will be able to run smoothly Froyo.
Last thing: today, the only way to have a working Android is to boot on WinMo and then launch a program (Haret) which will "kill" WinMo and boot to Android from internal storage (or SD card for other devices). There is currently no way of flashing an Android as you can do with WinMo.
Hope we'll get asap a fully working Android for our WinMo's HTCs
damien2702 said:
Hi, as you said, it is currently possible to boot an Android system from a WinMo one. But they are some issues left, mainly the battery life. Indeed, battery drains pretty fast with Android (and the indicator is not accurate at all).
Concerning Froyo (2.2), I ran many android systems on my Diamond 100, and Eclair versions (2.1) are really very slow, that is why I am currently using a Donut version (1.6), which is pretty fast and stable. So I'm not sure the Diamond will be able to run smoothly Froyo.
Last thing: today, the only way to have a working Android is to boot on WinMo and then launch a program (Haret) which will "kill" WinMo and boot to Android from internal storage (or SD card for other devices). There is currently no way of flashing an Android as you can do with WinMo.
Hope we'll get asap a fully working Android for our WinMo's HTCs
Click to expand...
Click to collapse
instead i think that froyo will run well...because yesterday i saw some benchmark over the nexus one and the preformance were multiplyied by 2...and i saw the internet browsing benchmark and was the fastest browser i saw
So let's hope you are right about Froyo =)
damien2702 said:
So let's hope you are right about Froyo =)
Click to expand...
Click to collapse
i hope it too..i love android...i'm waiting for froyo and for a flashable android...i don't like a lot wm
And so do I ^^ I recently tried the Desire with Android 2.1, and I'll certainly buy one when I'll change my Diamond =)
Correct me if I'm wrong, but I guess you are the one trying to cook a Sense XDAndroid ?
damien2702 said:
And so do I ^^ I recently tried the Desire with Android 2.1, and I'll certainly buy one when I'll change my Diamond =)
Correct me if I'm wrong, but I guess you are the one trying to cook a Sense XDAndroid ?
Click to expand...
Click to collapse
i was trying but i was having porblem using ubuntu(no ethernet,no wireless and some other things) so when i will resolve those problem i will start
so haret in fact is a simulator?? just to provide a simulated environment to run Android?
If I'm right, Haret isn't a simulator. It is a program which, launched under WinMo, will kill all WinMo processes and boot on internal storage with Android files. Have you ever tried it?
if you want to try it the easy way:
http://forum.xda-developers.com/showthread.php?p=5420781#post5420781
there is an cab to download, just install it
than you can run android
bewhare, android uses a huge amount of internetactivity ( maybe it costs money with your telephon provider )
or just for testing remove the sim card...
its the easy way to run android, for multiboot
you need to install a multibootmanager on your phone
for me there are some problems with android on the diamond,
i get sometimes time outs of some programs, but its possible to use it... and test it...
maybe some thing in settings but i tryed it only for some hours ( telephonprovier... i got only 300 minutes of mobile internet connection for free )
but remember, back up your data...

Combining FRX03 with Neopeek FRG83.R5 with working Bluetooth ?

Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
-------------------------------------
----------------
EDIT:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
d0nate110 said:
Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
Click to expand...
Click to collapse
1) as far as I understand Neopeek uses large parts of Xdandroid projects, starting from the kernels/rootfs. This is not hidden/secret, so he and xda devs may know each other pretty well.
Therefore I can't understand how he can have bluetooth working and Xdandroid not.
then ...
2) maybe he shares branches of code and patches with our devs, but while our devs decided that the code to make bluetooth working is still too buggy, he could have decided to shoot it in for good. In fact reading comments on the thread you posted you will see that at the end the people crying for not-working BT are a lot ...
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
I just installed it, on a blank 2Gb I had spare.
At start it's quite a pain in the arse ...
cmdline was a little different, I just set correct keyboard.
But I immediately put the latest kernel (24.11.2010). Both in installer and main.
Much faster than Xdandroid. Much faster at boot, much snappier in launcher etc., but this may be related also to the age (of the FAT32 file system) of the other SD I use for Xdandroid. Will format it and see what happens swapping.
But then, when it went to sleep it just crashed.
I tampered with the startup, added pmsleepmode=2, this worked, tried =1 and works quite well.
As I expected, BT doesn't work on my RHOD100.
This neopeek build comes nearly all from xdandroid, so it seems it's not as up to date.
But while that guy takes most of development from XDA, he must work a lot on tweaks, therefore XDA should take something back ...
I'll try cleaning the other SD and check what happens.
Installed on extra card. Rhodium 400 . It is fast. Boots quicker. The initial setup screens are very friendly. Power off and other buttons work more like winmo. Bluetooth will not turn on. Phone works. Data does not work. Have to use WiFi for data. USB while in Android does work (sweet). Key board backlighting not working. I am going to reinstall with bluetooth enabled initially in winmo.
Neopeek SuperFroyo Repack into system.ext2
arrrghhh said:
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
Click to expand...
Click to collapse
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
reinstalled Bluetooth not working. Rhodium 400
Only things that could make improvements to XDA android are Speaker phone is working. USB in android does work. Buttons function as they should. It works with SIM card installed. Speed. Boots faster. Screen adjusts to right profile on start lockscreen.USB headset works without line in startup.
Still not working
Data does work but have to manually set APN. Headset does not work ( Does work with line in Startup and calling during boot). Problems with the market downloading.
Does work tethering. pretty much everything
One nice thing is they have a seperate install folder so if your system is corrupted you just reinstall with file manager in winmo. It reformats the ext2 partition on the card. I assume the sizing of partition is in place of the sizing the data.img file on the card.
Being open source borrowing a few items should not be considered crossing a line.
d0nate110 said:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
Click to expand...
Click to collapse
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
First Full Day Of Testing
[ACL] said:
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
Click to expand...
Click to collapse
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
d0nate110 said:
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
Click to expand...
Click to collapse
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
too buggy things would work then stop working. I could plug in a usb headset have it work in a call or music unplug it then plug it back in and it does not work. Many other things like that. Same with the 3.5 jack trick it would work sometimes then sometimes not. If u left it stock it works great and is very fast. Diamond users were happy. I have a diamond that I will try it on sometime next week, but it is not good for rhodium. It did something to the usb on my Rhodium in winmo would not work so gave me a chance to jack in energy rom like that so far.
[ACL] said:
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
Click to expand...
Click to collapse
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Sorry about that
sad0felix said:
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
First of all I AM NOT Donate - I'm donatello written with numbers
I don't want any donations and hate money
Second I apologize, but I can't implement FRG83.R5 to use without formating my SD-card thats why I use a SuperFroyo. The member DmK75 gave me this link to system.ext2 file with SuperFroyo release in it...
I try though to repack FRG83.R5 also in system.ext2 file later... I just don't have the know-how yet...
sad0felix said:
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
[ACL] said:
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
Click to expand...
Click to collapse
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Here's the PPCG thread on NAND boot testing. Not for the faint of heart...
sad0felix said:
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Click to expand...
Click to collapse
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
[ACL] said:
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Click to expand...
Click to collapse
Hep, I am just a curious guy.
One of those many that want to put their nose everywhere, but also one of the few that:
a) most of the times will need to read the guide just once (if guide isn't enough there are FAQs and Google),
b) will follow instructions easily because normally understands what they mean/what they are for
c) will never give it up until success
d) will never come to the forum writing: "I have a phonez, tried to put some android on it, doesn't work HELP1!!1!!1!"
Moreover, my TP2 is just 6 months old, is a gift, I use it for work, so to not void the warranty I didn't even install HardSPL on it.
So do not worry.
I am just curious to read how you can do it.
But will not die if I don't know yet
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
Click to expand...
Click to collapse
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
sad0felix said:
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
Click to expand...
Click to collapse
Not to my knowledge. I guess we should *try* it just to see if there's a big difference... perhaps Neopeek can help us here muhahahahaha!
But I think the theory was the tradeoff would be small - a lot more work for very little reward. However, I would be interested to see if there is a difference, and if it is big or not. At the very least just to know if it's our build or just the ext2 partition that's making it feel snappier.
In addition, AFAIK swap partitions on SD cards should be avoided, unless they have a write-levelling scheme (I believe they only put these in SSD's... I don't think any SD card has this tech because it's typically unnecessary) - I've heard swap partitions can just destroy a normal SD card because of writing and re-writing to the same area of the card many, many times... I mean physically on the card, not just logically in the folder hierarchy.
Just installed it on my diamond Bluetooth does work but it doesnt pair. The screen eventually graduates to the center dividing it in opposite. I thought maybe because I was running the hot version. Repartitioned reinstalled the normal clock version runs for a time then the same. Its no better than XDA

[Q] need a rom that DOES NOT crash

so far i've tried mighty rom (fat and slow), energy rom(still fst and slow) and sharkie rom (reasonabhle but still not setup 100% and a bit slow).
all 3 have stability issues. requiring a reset at least once and often 2-3 times a week. itks very important that my phone does not lock up as i need the alarm and other things to work continuously.
any suggestions? so far i've only used windows 6.5.x roms as i like the start menu at the bottok. but would 6.5 or 6.1 be more stable?
http://forum.xda-developers.com/showthread.php?t=1144615
This ROM is available in two versions...wm6.5 and wm6.5.x....they're both as stable as all heck ...take your pick...I personally prefer 6.5 (21916)...but that's the case on anyones rom I'm using...I don't like the start key on the bottom...I like it on top, where it's supposed to be lol
The device will reboot itself after it starts up for the first time and it's suggested you restart twice afterwards....BUT...DON'T freak out after it restarts itself, it's a built in feature...also...you need to set your time in the windows settings not sense...and if you have any weather location issues, add your city, select it, and then remove it in the "remove locations" screen and you'll be good to go
Sergio76's Core Cell Evo
I recommend trying Sergio76's Core Cell Evo version 4.0 ROM. Here's the link:
http://forum.xda-developers.com/showthread.php?t=617142"
When you click on the download link, the file you want is "TP2 Core Cell Evo v4".
If you decide to install the ROM, click on the link in my signature and get the latest patch for this ROM. Follow the instructions provided on how to install the ROM and the patch and you will have the fastest ROM with the most stability and a lot of eye candy! Feel free to ask any questions you may have.
are there any differences between 6.5 and 6.5.x that affect speed or stability? or is it purely cosmetic?
what about 6.1?
6.5.x uses more ram
Lavell7298 said:
I recommend trying Sergio76's Core Cell Evo version 4.0 ROM. Here's the link
Click to expand...
Click to collapse
I should of mentioned I have a Sprint TP2 which needs CDMA roms, neither of the above 2 are CDMA
Would it be best to make a new thread in the CDMA section?
qwerty-1234 said:
I should of mentioned I have a Sprint TP2 which needs CDMA roms, neither of the above 2 are CDMA
Would it be best to make a new thread in the CDMA section?
Click to expand...
Click to collapse
Yes. You need to post this request in the CDMA section.
I suggest Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.DinikGlass.Jul.04. It has been extremely stable!! I have a custom made app for my job and it has always caused issues for me. With this version of NRG's rom I haven't had any issues!!
Love this ROM.
i'm trying the 21xxx build of titanium energy rom. It's a bit faster but still not snappy like my super oldschool nokia 2690. Anyway so far it has managed to freeze up once right after a phone call. If it freezes again i'll assume it's not the rom thats the issue. Though come to think of it it does seem to freeze up around the time someone calls
Could it perhaps have something to do with the phone part and not anything else? i'm running the latest sprint radio (2.32?) but before that was 1.96? and it still froze using that one. Also I do a task29 before each flash
I read a post somewhere suggesting that I force GSM and also the band as that may stop it freezing. But I can't seem to find a way to force 900mhz or 2100mhz?
Best asking in his thread for support on the ROM
Regards,
WC
GT247 said:
http://forum.xda-developers.com/showthread.php?t=1144615
This ROM is available in two versions...wm6.5 and wm6.5.x....they're both as stable as all heck ...take your pick...I personally prefer 6.5 (21916)...but that's the case on anyones rom I'm using...I don't like the start key on the bottom...I like it on top, where it's supposed to be lol
The device will reboot itself after it starts up for the first time and it's suggested you restart twice afterwards....BUT...DON'T freak out after it restarts itself, it's a built in feature...also...you need to set your time in the windows settings not sense...and if you have any weather location issues, add your city, select it, and then remove it in the "remove locations" screen and you'll be good to go
Click to expand...
Click to collapse
That
Illuminati series is the best I tried so far
Hussam, you wont find a more stable CHT ROM than Illuminati...or faster...or with more available device storage...it really is an amazing rom
dude, that's what i run, im also a beta tester
Hussam...sorry, I never know anything about anything...lol
GT247 said:
Hussam...sorry, I never know anything about anything...lol
Click to expand...
Click to collapse
lol, it's ok
husam666 said:
Illuminati series is the best I tried so far
Click to expand...
Click to collapse
Is there a CDMA version?
qwerty-1234 said:
Is there a CDMA version?
Click to expand...
Click to collapse
no
10characters

Categories

Resources