Related
Hi installed Android 2.0.1 on my Fuze
Issues Found
- Consumes 4 times battery than windows
- When we put screen off, the round bottom light keeps blinking(Same as when we charge in windows)
- No option to switch off
- No option to go back or close a window from touch screen
- After some hours phone hangs up you need to remove battery to restart windows.
Pros
- Amazing graphics
- Very fast as compared to windows 6.1
Question
- Now to remove this should I just the android related files from Sd card, nothing needs to be removed from phone memory am I right ?
But I wish I could install a better working version of Android on my Fuze because despite of all bugs I am loving it
gaurav12 said:
Hi installed Android 2.0.1 on my Fuze
Issues Found
- Consumes 4 times battery than windows
- When we put screen off, the round bottom light keeps blinking(Same as when we charge in windows)
- No option to switch off
- No option to go back or close a window from touch screen
- After some hours phone hangs up you need to remove battery to restart windows.
Pros
- Amazing graphics
- Very fast as compared to windows 6.1
Question
- Now to remove this should I just the android related files from Sd card, nothing needs to be removed from phone memory am I right ?
But I wish I could install a better working version of Android on my Fuze because despite of all bugs I am loving it
Click to expand...
Click to collapse
Well of course this has many bugs cuz this is not a native android device, also u should credit the develepors for their hard work this isnt really easy at all, also over the past months it has been improving greatly, and since u want to remove android from ur phone unfortunatley, all u must do is remove the android realated files like haret or android apps.
gaurav12 said:
Hi installed Android 2.0.1 on my Fuze
Issues Found
- Consumes 4 times battery than windows
- When we put screen off, the round bottom light keeps blinking(Same as when we charge in windows)
- No option to switch off
- No option to go back or close a window from touch screen
- After some hours phone hangs up you need to remove battery to restart windows.
Pros
- Amazing graphics
- Very fast as compared to windows 6.1
Question
- Now to remove this should I just the android related files from Sd card, nothing needs to be removed from phone memory am I right ?
But I wish I could install a better working version of Android on my Fuze because despite of all bugs I am loving it
Click to expand...
Click to collapse
- People get 15 hours + of battery, so considering that it is a work in progress, that's very good.
- The light is a debugging thing, it means that your phone is in deep sleep (that's good) it's a LED light and barely makes any difference on battery life and you CAN turn it off if you want to, read the main thread.
- No, no such option for now, but as i said it's a work in progress for now.
- That's not even related to the port, that's just how Android is.
- No need to remove the battery, you can just press the reset hole.
- Yes, just the files from the SD card, nothing is saved on the phone's memory.
Why don't you learn to read a thread before installing a non native OS onto a phone. All the points you brought up were or are bugs that are known. If you don't like it get it off your phone and be done with it. No need to start another thread only to rehash what is already known.
gaurav12 said:
Hi installed Android 2.0.1 on my Fuze
Issues Found
- Consumes 4 times battery than windows
- When we put screen off, the round bottom light keeps blinking(Same as when we charge in windows)
- No option to switch off
- No option to go back or close a window from touch screen
- After some hours phone hangs up you need to remove battery to restart windows.
Pros
- Amazing graphics
- Very fast as compared to windows 6.1
Question
- Now to remove this should I just the android related files from Sd card, nothing needs to be removed from phone memory am I right ?
But I wish I could install a better working version of Android on my Fuze because despite of all bugs I am loving it
Click to expand...
Click to collapse
I am in the same boat with you. I just keep updating it. It used to be pretty good Battery and stuff but the newer updates just aren't as efficient. I'll keep updating mine untill I get the money to just buy the damn NEXUS ONE since now they have an AT&T version that supports 3G
The original threads warned that Android on your WinMo device is merely proof of concept and experiment and was in no way meant to replace WinMo as your full time operating system on your device. I think the developers have made fantastic strides in the performance of Android on the FUZE given that they have managed to put an OS on a device that does not support it with neither hardware or software. And maybe it's just me, but if you have the right ROM WinMo 6.1 can be pretty fast (I haven't had such luck with WinMo 6.5, but I like 6.1 anyway)
Android has worse battery life than WinMo. I tried both Android devices on Sprint and even Android 1.5 is a hog. My neighbor just purchased the latest Android device Verizon released on Thursday and he is complaining of charging at 3PM everyday.
I've read all the threads and come to release Android on our devices is merely experimental. If you think its going to work flawlessly then you're not that bright. If I really need an Android device then I'll buy one. In fact I may try the EVO under the 30 day trial just for fun. I am interested in 720p / HDMI video recording, video call and other new features.
For everyone reading this post you know this guy only joined to complain or discurruge people from using it. Member with only 1 post trying to review software that was neer made to run on a specific hardware. Only a idiot would consider his words useful. Basically all he did was complain so that he could ask a question and get people to answer him without searching.
Well Hello Fellows...
As u ppls can see on my Sig...i just returned my Htc G1 due to some keyboard issue..and i m ready to do some nasty work for my TP2 but i need some answers before doing something with my TP2..
1st-- y we need some custom rom like 6.5.5...while we are already getting everything on the stock rom..and custom roms are same as stock rom some of the difference that the apps tab icons are big(as i am seeing on Custom Rom )<---- Prove me if i m wrong about it
2nd-- i m sooooooo exited to see android on HP2 and i really appreciate the hard work of the developers but i will wait till complete rom comes out ...and my main cause was to buy that machine is to use android on it but i need some user experience.....
3-- i want to know that difference between dual boot ..
3a --- as i saw that a dev created an app that we can directly boot android when we turn on the phone without booting in to WM...
3b---other is that 1st we need to turn on windows mobile then android ...
4--i will ask later when i get my other answers
i want to know which process is best like which process drain minimum battery and run android kinda normal speed...i know that its not that fast but come on ..
these are the main ques that are like dancing all time in my mind..Plz ignore my dictionary and answer my ques
ThankYou..
1. Different ROMs provide different experiences. For instance, the 6.5.x ROMs have a more finger-friendly navigation altogether, with the Windows Start button being at the bottom of the screen instead of the top.
Different ROMs will also give you different benefits. NRGZ ROM comes cooked with a radio app that doesn't need headphones (but of course, if you have a CDMA TP2, you won't have a radio to begin with). Deep Shine ROM makes the most of the Zoom Bar down at the bottom of the screen of your TP2. And Valkyrie's ROMs (the one I use) provides the most stability.
Note though that 6.5.x ROMs tend to be slower than most stock-ROMs.
2. You should just try Android for yourself. In my experience, Android was good. I actually downloaded the Facebook app with it, right after I downloaded the Facebook app for WinMo. So it was funny to see those two updates on my Facebook.
Regardless, sound doesn't work, and Camera doesn't work. When those two functions work, I myself will probably be using Android more than WinMo. I don't care much about BT. Look in the Android section of this sub-forum, find out for yourself.
3. Dual-boot simply allows you to boot one operating system first. So say you didn't want to boot WinMo first, then Android, the dev's app allows your to just boot Android first before WinMo. Simple as that.
Ask anything else, but take a look around first.
thanks buddy for your quick reply
well i have Vodafone Tp2..idk that is Cdma or not right now i using stock rom for windows mobile 6.5.5..that what the device says it have Sense UI i think TF3d 2.5...so i saw not much difference between my stock rom and the custom rom..and for the android ques well i was asking that which way is better ot use android like i think if i boot throught windows mobile then windows mobile will also take some ram else if i directly turn on android then android will use all the ram.and atleast runs better for this direct process and drain less battery....thats what i think and well i watched alot of videos and surfing web for this like 2weeks before asking these ques....
4---well for some games i want to use fpecse emulator...so any way to overclock the tp2..becoz i saw some of the videos of the emulator on Hd2 .. it runs the game pretty smooth...
5--App2SD..well can we use ap2sd on TP2 while using android?? <---Dump ques
4. There isn't a way (yet) to overclock your TP2. Oddly enough, Android on the TP2 is overclocked. But overclocking it via WinMo isn't possible as of current.
Regardless, playing certain games on FPSCE like FF7 works just fine. The more graphically enhanced the game is, the more the phone will lag. Every game I've loaded onto my phone (including the graphically beautiful Call of Duty 2) has worked just fine. Certain games are only in VGA, so download the WVGA fix (it's located in the "Programs to Download for your TP2" thread in the sub-section "Themes and Apps").
5. I wouldn't know about that, but if you want to put programs on your SD card, I believe they have a fix for that in the Android programs already. So, see that thread in "Android Development."
thanks mate for your quick reply .. well what about ram consuming?? speed effects.. direct android boot or android through windmo??
i know that i need to test it my self but also want to know the ppls expreience about android
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
First off, there is an insanely huge list of guys who are responsible for making this possible.
Thanks to phhusson, dbz, Stinebd, ACL, arrrghhh , viruscrazy, WisTilt2, Klinux, kama, Reefermattness, chkms, davidebeatrice, elroy944, kstephens98, DracoLX, zenulator, Chamonix, Makkonen, Mrpippy, cr2, Markinus, Babijoee, Lmiller1708, natemcutty, and anyone else forgotten!. I WILL ADD MORE
SPECIAL THANKS TO THE NAND TEAM. ACL AND THE A TEAM
THANKS TO F22 FOR HIS KERNELS
THANKS TO VIRUSCRAZY FOR HIS CAMERA KERNELS
BLAZN 2.2.2 2011.03.06
CHANGE LOGS
youtube in HQ. man this looks like DVD. MAKE SURE WHEN OPEN YOUTUBE FOR THE FIRST TIME. CLICK MENU, SETTING, ENABLE HQ ON DATA. THEN GO ANY VIDEO TO TEST IT.
camera. works great with a new camera app.
camcorder. works super nice. no sound. i hear people saying it's working. i thinks rhod user having issue with video sound. i'm doing some testing about this.
gps.
3g. super super super fast 3G.
data. super super super fast data.
google goggles. works like it charm.
wifi is fixed
theme is fixed
and many many many more
not working
3.5 jack
BT
MMS.
APPS
all stock apps
astro
add it more app. look for it in files folder
NOT WORKING IN THIS BUILD
MMS
BT. so far not for rhod. my 2 friend, one with a blackstone and the other with diamond, they told me is working for them.
3.5 MM jack
PREPARE YOUR SD CARD
1-FORMAT YOUR SD CARD TO FAT32. FULL FORMAT
2-DOWNLOAD FROYO 2.2.2 BLAZN
3-UNZIP IT INTO YOUR SD CARD. ANDBOOT OR TO ROOT SD CARD
4-USE YOUR STARTUP.TXT FOR YOUR DEVICES. ADD THIS COMMAND YOUR STARTUP. rel_path=andboot.
5- for cdma devices. add this command for the camera on your startup. board-htcrhodium.is_cdma=1.
for gsm devices. add this command for the camera on your startup. board-htcrhodium.is_gsm=0.
FOR CDMA PHONES. REMOVE THE SIM CARD
6- for cdma & gsm devices make sure you have this command on your startup for data. force_cdma=1. for gsm devices is force_cdma=0
SETTUP FROYO 2.2.1 BLAZN FOR THE FIRST TIME
1. On WinMo, navigate to the andboot or root sd card folder on your SD card and launch haret.exe.
2. First boot will take several minutes for the data.img to be created... Be patient... enjoy the animation.
3. Do not touch. Wait for green light, you are at the home screen. Wait for green light.
4. Open Spare Parts and change End button behavior to go to home
5. Go to to Settings - Call setting and set up your voice mail for sprint,verizon. etc..
6. Go to Settings - Sound. Test the volume settings, test phone ringtones and notification ringtones
7. Go to Settings - Display-Brightness. automatic brightness. screen timeout set it to 10 minutes
8. Go to Settings - Location & security- Enable use wireless networks and gps
9. Go to Settings - Applications- Enable unknown sources
10. Go to Settings - Language & keyboard - Set your language or use more locale 2 to add language. Press the menu key and follow the screen.
11. Go to Accessibility. this is the power button ends call. check it
12. Now you can sync your phone by going to Settings - Setting account & sync
13. Let the phone sync. Do not touch. Wait for green light
14. Open all apps to get full performance. Make sure all apps fully open.
* DO NOT OPEN CAMERA.APK UNTIL YOU HAVE SWITCHED TO THE CAMERA KERNEL ON FUTURE BOOTS
* Open the market app LAST - allow it to do updates for existing apps
15. Boot back to WinMo
16. Open File Explorer; you can now switch to the camera, 1250 or 1253 kernel located in the files folder; just copy the zImage and modules*.tar.gz to the andboot folder level.
* files\first boot zimage and modules 1276 - kb backlight
17. Boot haret, alway wait for green light. Make a test call, send a text, tell someone to call you. Tell someone to send you a text.
Requirements:
* Your WinMo needs to be running at stock speed (528Mhz); DO NOT OVERCLOCK under WinMo before booting to Android, it will just crash. Don't ask how, it just doesn't work. You need to be running WinMo at stock speed since your last boot; you can't just throttle it down to stock speed and then launch Android.
* Optional but recommended: backup the data on your SD card, format it using SD Formatter as FAT32, restore your data on it, and create the Froyo X distribution with the instructions below.
Reserved
==============
THINGS YOU NEED
Current Kernel Builds
http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Current rootfs Builds
http://files.xdandroid.com/rootfs/
Current initrd.gz Builds
http://files.xdandroid.com/initramfs/
Frequently Asked Questions
http://sites.google.com/site/androidport/faq
still non-partition version, can release partition version(has npkinstall folder)
Well.. This is a useless thread and a major letdown..
great work tiad
you are awesome tiad8 great work you are soooooo active
thanks tiad and we want more and more biulds
muziling said:
still non-partition version, can release partition version(has npkinstall folder)
Click to expand...
Click to collapse
Sounds like you are looking for Neopeek. You should try there.
Thelightning87 said:
Well.. This is a useless thread and a major letdown..
Click to expand...
Click to collapse
People must eat!
Must consume!
starter to test BLAZN 2.2.1
man, browser, 3g and market downloads are super super fast. i mean fast.
it's coming
thanks
oh man can't wait for this.....go...go....go.....
hi, guys. UPDATE ON BT
my best friend leave 25 miles from me. he got a blackstone phone. he just call me. he said he can use BT on his car.
i add it info on the build.prop about BT, i add it permission for BT on system/etc and on my startup.txt i add it this line hw_bt.enable=1. i told him to enable BT on WM first.
don't know if this works, i don't have BT on my card.
his going to call me later to confirm what he did.
thanks
sounds good !
I have a blackstone and can't wait to test this version!
Thanks a lot for your amazing work on android for our htc phones!
Update BLAZN
Well guys. I been testing the new blazn. I just got to tell you guys, I'm really impress with this build. This build it so good and fast, I'm listening to pandora while I'm writing this words.
You guys will get. A mix of 3 diffrerent build. FRX03, FROYO X, AND BLAZN. I use the speed of froyo x, to get fast data, like 3g, market, market download, and a fast browser. I use the stability of frx03 to get a very stable build, and I use the blazn theme to give this build the final look. Look amazing
Thanks
tiad8 said:
Update BLAZN
Well guys. I been testing the new blazn. I just got to tell you guys, I'm really impress with this build. This build it so good and fast, I'm listening to pandora while I'm writing this words.
You guys will get. A mix of 3 diffrerent build. FRX03, FROYO X, AND BLAZN. I use the speed of froyo x, to get fast data, like 3g, market, market download, and a fast browser. I use the stability of frx03 to get a very stable build, and I use the blazn theme to give this build the final look. Look amazing
Thanks
Click to expand...
Click to collapse
Do you think you can me a favor and let me know what in FROYO X makes data faster? I had some complaints that all the XDAndroid builds are much more stable, but much slower on 3g. Wifi they said is about the same, but I've had complaints that 3g is significantly slower. If there is something we can do to improve that on the XDAndroid builds, I'd love to apply it. Thanks!
It warms the heart to see Arrrrghhh and Tiad8 working together!
It can't get much sweeter than this!
arrrghhh said:
Do you think you can me a favor and let me know what in FROYO X makes data faster? I had some complaints that all the XDAndroid builds are much more stable, but much slower on 3g. Wifi they said is about the same, but I've had complaints that 3g is significantly slower. If there is something we can do to improve that on the XDAndroid builds, I'd love to apply it. Thanks!
Click to expand...
Click to collapse
Ok. Everything start with the build.prop, I add it a few commands. I add 5 drivers to the system/lib/modules. And few other things. When I get home I will pm you all this info.
Thanks
FROYO X/SPRINT TOUCH PRO 2/RHOD
tiad8 said:
Ok. Everything start with the build.prop, I add it a few commands. I add 5 drivers to the system/lib/modules. And few other things. When I get home I will pm you all this info.
Thanks
FROYO X/SPRINT TOUCH PRO 2/RHOD
Click to expand...
Click to collapse
Thanks man. I haven't independently confirmed, but if it's true I want to spread the fast data to the vanilla bundles. You are doin great work making custom builds - keep it up.
scattaman said:
It warms the heart to see Arrrrghhh and Tiad8 working together!
It can't get much sweeter than this!
Click to expand...
Click to collapse
**** doesn't stink until you poke it......
It warms the heart to see Arrrrghhh and Tiad8 working together!
It can't get much sweeter than this!
Click to expand...
Click to collapse
**** doesn't stink until you poke it......
Click to expand...
Click to collapse
Your right, good thing this isn't ****
-------------------------------------
Sent via the XDA Tapatalk App
Data Image
Tiad AAAAarrgghhhhhh
will we be able to use our current Data Image from FRx03 with this or will we have to start over?
BigOnes69 said:
Tiad AAAAarrgghhhhhh
will we be able to use our current Data Image from FRx03 with this or will we have to start over?
Click to expand...
Click to collapse
You can try, but no promises. Usually when you go between system images you need a new data.img.
If you have weird odd issues, delete your data.img. That's troubleshooting step #1 if you have issues that nobody else does.
Titanium Backup makes it much easier.
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from a RAPH100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
Test device: RAPH100 running latest NRG build w/sencity
Using everything supplied in the previous posts above minus my ts-calib file; everything seems to work on my RAPH100 (I'm not sure it matters that it has the orange brand on the back cover). Also, this does include sound! I booted without a SIM (yes, this is a GSM version RAPH). The first time I booted, it rebooted to winmo; second time was the charm.
Additional info(statistical maybe?):
Time to boot animation: 3 minutes
Time from boot animation to home: N/A (after 3 minutes my device rebooted to winmo on first try)
(Second trial)
Time to boot animation: 1 - 1.5 minutes (maybe 2 minutes?)
Time from boot animation to home: S/A (same as above)
*Successful boot to lock screen after second boot* (I wonder should this be expected behavior?)
NOTES: Hard keys "Home" and "left arrow"/back key remain highlighted after activated but deactivate after playing around(for the lack of a better word) and/or screen times out. (My opinion)At the very least it doesn't go crazy like earlier froyo builds. Also note that wifi should be working (works on mine) with this build and kernel package (included with package). (I like)New power off boot menu (long press of power key brings this up while short press seems to turn off screen, as usual). "Silent mode" (as expected), "Airplane mode" (as expected), "Kexec" (not sure yet, seems to be the same as "Reboot" or probably vise versa?), "Reboot" brings you all the way back before boot animation and "Power Off" (as expected).
Still test driving (more to come!)
R^7Z said:
"Kexec" (not sure yet, seems to be the same as "Reboot" or probably vise versa?), "Reboot" brings you all the way back before boot animation and "Power Off" (as expected).
Click to expand...
Click to collapse
So reboot didn't work properly?
Let's focus on what's changed. Audio mainly... I do appreciate the report tho .
Kexec is for swapping kernels. This way you can swap kernels and not have to go back to WinMo... Goooogle it .
I ran it for a day, and had no audio problems
only had a few small problems:
it did reboot once
orientation is inverted but i never use auto rotate
market is kinda slow
Edit:
had another reboot during gps app, and i think previous reboot might also have been while gps app was opend
but audio seems to be perfect atm
Greetings
Jeroen
DIAM100
So I've been in the Windows Mobile for quite sometime, came back and noticed the new Gingerbread Build, and it runs fine thus far... I have two issues, no google maps or facebook (incompatible with this device)? Is this something new, or unique to gingerbread?
Problem Solved...
An update to my previous post... changing the DPI back to 240 in startup.txt has resolved the problem.
I really want to try this, as the FRX build lacked the ability to use Bluetooth. Only problem is, I have no .csv files in my WinMo directory. I am running the Energy Sense ROM 2.5 29017.
What do I do now? Do I really need those files?
EDIT: Never mind. I'm an idiot! But I do only have 5 .csv files.
I have it running now, but I get no audio from the phone. Also, bluetooth pairs but I get no audio from it either.
I have a RAPH800, BTW.
SkinsFan said:
I really want to try this, as the FRX build lacked the ability to use Bluetooth. Only problem is, I have no .csv files in my WinMo directory. I am running the Energy Sense ROM 2.5 29017.
What do I do now? Do I really need those files?
EDIT: Never mind. I'm an idiot! But I do only have 5 .csv files.
Click to expand...
Click to collapse
I've also only 5 .csv files in my windows folder:
AudioFilterTable.csv
AudioPara.csv
AudioPara3.csv
AudioPreProcessTable.csv
TIAGC.csv
In the second posting from arrrghhh you will find the *.csv for the RAPH100 in a zip archive (http://forum.xda-developers.com/showpost.php?p=20869601&postcount=2 - it contains only 4 .csv files).
I've tested this Release on my RAPH100 and it is running well.
- Phone works
- Audio works
- Wireless works
- Camera works
On my phone, the hardware buttons light up irregularly (without touching or pressing them - see attachement). The result is that the focus on the screen jumps back and forth. This happens at irregular intervals. Has anyone else this problem?
(I think) It's a design flaw by HTC. This has been a long standing bug even without Android (it's just not as apparent in winmo) and unless we can figure out how to either ignore the additional key pressing being picked up by the touchpad sensor or possibly ignore the touchpad altogether, we may just have to "deal" with it as is. However, I think this is starting to get away from the actual intent of the XDAndroid team's intent to find out about noting any audio irregularities with these files. I'm guessing we either need to start posting our csv files or figuring out what the differences in changing the values mean in terms of audio(or perhaps both?). I really haven't had the time to do much testing aside from describing my experience with loading the GB test bundle.
R^7Z said:
(I think) It's a design flaw by HTC. This has been a long standing bug even without Android (it's just not as apparent in winmo) and unless we can figure out how to either ignore the additional key pressing being picked up by the touchpad sensor or possibly ignore the touchpad altogether, we may just have to "deal" with it as is. However, I think this is starting to get away from the actual intent of the XDAndroid team's intent to find out about noting any audio irregularities with these files. I'm guessing we either need to start posting our csv files or figuring out what the differences in changing the values mean in terms of audio(or perhaps both?). I really haven't had the time to do much testing aside from describing my experience with loading the GB test bundle.
Click to expand...
Click to collapse
Eh, we really just want to know if there are any dramatic differences in the CSV's between devices - XDAndroid tries really hard to support WAY too many devices .
So this thread is mainly to find out if all our new changes dramatically break any one device. Doesn't seem like it... so the next step is to aggregate all the CSV's together (why I asked everyone to post theirs) and see if we can make a big mix of them, or if we'll have to do it similar to the keyboard layout where each device gets its own folder... then it gets into proper variant detection, etc. Hairy!
But yes, the touch panel issue has ALWAYS been present folks. Let's not rehash old bugs, that doesn't do anyone a darn bit of good. Thanks!!
arrrghhh said:
But yes, the touch panel issue has ALWAYS been present folks. Let's not rehash old bugs, that doesn't do anyone a darn bit of good. Thanks!!
Click to expand...
Click to collapse
I haven't heard from this issue before. So it is good to know that.
I've compared your 4 csv files with mine (RAPH 100 - running with Energy ROM 29022) and there is no difference between them.
I've one additional csv file in my windows folder (TIAGC.csv). If you need it I can upload it.
I have a RAPH800 (Sprint) and I was in the process of doing the Pre-install Prep with Total Commander to get the .csv files. However after copying the files to my SD card, I see only 5 files.
AudioFilterTable
AudioFilterTable_Raphael#C
AudioPara3
AudioPara3_Raphael#C
AudioPreProcessTable
I don't see the AudioPara file. Am I doing something wrong? What should I do?
Also I did a Beyond Compare comparison between the files from my phone and the downloaded RAPH100 files and the files are not the same.
ericdabbs said:
I have a RAPH800 (Sprint) and I was in the process of doing the Pre-install Prep with Total Commander to get the .csv files. However after copying the files to my SD card, I see only 5 files.
AudioFilterTable
AudioFilterTable_Raphael#C
AudioPara3
AudioPara3_Raphael#C
AudioPreProcessTable
I don't see the AudioPara file. Am I doing something wrong? What should I do?
Also I did a Beyond Compare comparison between the files from my phone and the downloaded RAPH100 files and the files are not the same.
Click to expand...
Click to collapse
Every phone model will probably have different files. You didn't do anything wrong. Just use the files for your device.
Hi guys,
do you see any kind of battery consumption improvement over FRX release?
shinden said:
Hi guys,
do you see any kind of battery consumption improvement over FRX release?
Click to expand...
Click to collapse
Not really no. Weren't really expecting one either, the only thing that changed was userland. Same kernel (for the most part).
Been running GBX0B 2.3.7 Build on Fuze since the 31st.
I didnt have 10 .csvs, so i just used the his zip. Took me 3 times to get a stable build, they kept self destructing.
Sound: Perfect
Gps: Faster than FRX07.1, when it worked. I justed stop using it
Data: Only used Wifi, works fine
I have a sim in the Fuze, but i have no service.
FRX07.1 would drain my battery over night even plugged in to the wall. GBX0B 2.3.7 fixed that.
I get alot longer battery life. I got maybe 5 (est) hours with FRX07.1, 8 - 10 (est) hours GBX0B 2.3.7
This is the BEST android build for fuze (and i have tried them all).
Smoother, little faster. GPS works alot better. I think we finally got a build we can run full time
popetorak said:
Been running GBX0B 2.3.7 Build on Fuze since the 31st.
I didnt have 10 .csvs, so i just used the his zip. Took me 3 times to get a stable build, they kept self destructing.
Sound: Perfect
Gps: Faster than FRX07.1, when it worked. I justed stop using it
Data: Only used Wifi, works fine
I have a sim in the Fuze, but i have no service.
FRX07.1 would drain my battery over night even plugged in to the wall. GBX0B 2.3.7 fixed that.
I get alot longer battery life. I got maybe 5 (est) hours with FRX07.1, 8 - 10 (est) hours GBX0B 2.3.7
This is the BEST android build for fuze (and i have tried them all).
Smoother, little faster. GPS works alot better. I think we finally got a build we can run full time
Click to expand...
Click to collapse
hmmmmmmm, on my RAPH100 battery discharges faster than on FRX07.1
drugusv said:
hmmmmmmm, on my RAPH100 battery discharges faster than on FRX07.1
Click to expand...
Click to collapse
Honestly the battery shouldn't be different at all. The kernel didn't change much at all in the battery saving or sucking department.
As always, if you use the device a lot - and use a lot of the hardware (GPS, wifi, etc) it will suck your battery dry.