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.
Related
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Are there any ways that I can actually speed this thing up?
Ive used ATK and thats about it. Im out of ideas here.
Also: 1) Is there anyway to fix the backlight issue when coming out of sleep mode? (It stays at minimum brightness)
2) Is there anyway to transfer winmo contacts to XD?
howeasy said:
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Click to expand...
Click to collapse
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
You could try overclocking but it should be pretty speedy already. Is this your first build of Android? Have you deleted data.img and let it remake it. Try formatting your sd card.
ben_duder said:
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
Click to expand...
Click to collapse
That is indeed the build i'm currently using.
The official XDAndroid build of 2.1 would give me the endless fireworks screen even and updated zImage.
If there's a version that will work on my Fuze then please link me to it as I have been unable to track it down.
But regardless, I've been working on trying to get it to run faster, Ive had moderate luck using ATK but thats about it.
Im baffled as to why its running this slow.
Also, using the 2.0.1 build caused the phone not to send SMS messages, hence the reason I came looking for a new build and came across the Sense one.
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Here's proof (if you want it) that it's normal for it to take ages to load on first boot.
ben_duder said:
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Click to expand...
Click to collapse
Indeed I did. It simply played the Nexus one boot animation for a while, froze for around 5 seconds, and then went back and played the nexus one animation from the beginning.
The sense build im using works in all aspects other than the fact I would prefer the normal Android layout, I want it to run smoothly, and I want a more constantly updated version.
I used the Fuze startup text with and without the overclocking script thrown in.
I'd be more than willing to go at it again if its worth the shot.
I really recommend having another go: XDAndroid is exactly what you're looking for with regards to the lack of Sense and the frequent updates. There's no hardware-related reason why it shouldn't work on your Fuze, so delete everything from the build that's already on there, get the right startup.txt and give it a go
Thanks for the positive reinforcement!
If you could possibly directly link me to the 2.1 build you'd personally recommend that would be appreciated.
Ive been trying a build for the RAPH800 that was linked to in your sig and its giving me to the same problem I described earlier.
I have the RAPH110, as you know, but the RAPH800 build was the closest thing I could track down.
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
ben_duder said:
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
Click to expand...
Click to collapse
Oopsy! I had a hard time tracking that down.
Im using the one labeled "03.05.10 | 2.1 builds". Is that correct?
It also says it already has the lastest zImage that should work so do I need to go update that?
I swear, if there was a super mega +rep button i'd press it.
You're what support forums are all about <3
(3:42PM: Just calibrated touch screen)
Yep, that's the one I'm trying. I've had some experience with the 2.0.1 but I've never actually used this build before, so it's possible there's something missing that I don't know about.
Haha thanks, although there are much nicer and more knowledgeable people on here than me
Well you're the one putting forth the effort to help a guy in need, so I truly do appreciate it.
I'm still getting the constant Nexus one boot animation sadly enough.
Maybe I'll go test out the 2.0.1 build and see if I can get that one to work, but like I said earlier, I had SMS issues with that one.
EDIT: I was able to get the 2.0.1 build working with SMS after zImage and etc..
Going to test sound and whatnot now and come back with another edit to verify.
I would still like the 2.1 build though but this might have to suffice.
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
ben_duder said:
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
Click to expand...
Click to collapse
AWESOME!
Mind uploading whatever it is you did and tell me what I have to do to get the same result?
Sorry, Im still pretty new to this whole thing.
I won't upload it, but just check your startup.txt and there should be two lines of text that look like they should be separated. Press return just before the second, save it and delete your data.img file. Then run HaRET again and it should work fine.
You have to try this build - it's brilliant.
Well I suppose I'll have to give that a shot.
I found and edited the lines and also threw in the overclocking script.
After deleting the data.img Im giving it one last shot now.
If that doesnt seem to work then I'll just deal with the 2.0.1 build until I find a way to get this to work.
EDIT: anddddd, no such luck.
Guess I'm left to stick with 2.0.1 for now, it was running pretty fast as well.
So if anyone reading this gets 2.1 working please feel free to post.
Is there a way to get Android on the phone itself rather than SD? I'd love to ditch Winmo and save some battery life here.
Shame... I can't understand how it's not working now. All I did was edit the startup.txt, delete my data.img and try again, then wait for ages while everything loaded. If you're not sure if you've edited your startup right you can try using the one that works for you with 2.0.1.
As for not having to use the SD, that would require NAND flashing, which has some way to go before we can use it on our Touch Pros to replace Windows Mobile. There's a thread about it here. There are dual-booting and light WM ROMs designed for XDAndroid users, however.
In case you don't believe me
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk
Did you happen to update the zImage or anything or did you just copy and paste and throw in the startup?
Here is a desire build I have been tinkering around with for a long while. There are several several issues still in need of work so I am going to leave it to the community to help me out.
I failed to mention this is a full NAND install
I will get some screen shots up as soon as I can get time.
Much faster and much more responsive in my opinion than the legend / hero / mytouch builds
Here it is in a nutshell
- I am not a hardcore developer I have just been using existing files and putting something together that works most optimal. This build has a lot of polymod, and mssmison mixed.
- Hardware keyboard does not work correctly while using Rosie, disable Touch Input to correct this issue. Also speeds up system somewhat.
- clock.sh is in /system/bin use at your own risk It is only there for those that wish to use it is not enabled at boot. Modify sysinit.rc for this
- Disable vibrate on ring and quiet when phone is moved helps with incoming calls
- This build will leave approximately 37mb of free space for data, I do store apps on SD but it is a little unorthodox maybe someone can do better than me. I create an app folder on sdcard and symlink to it. I do not recommend this but I will be upgrading soon and could careless about damaging my cards they are old.
- Livewallpapers are questionable I don't use them or like them If they dont work and you want them then you are welcome to work on their developement.
- Bluetooth not working Help Please
- Wifi not working Help Please
- Widgets may need influenced to work just go to applications / manage applications / Find HTC Sense and Force stop and Clear Data if widgets do not load on boot.
- First boot takes an extreme amount of time.
- CompCache is disabled use it if you will I find that it causes stability issues try to keep the mem size down to 28 or less if you use it.
- Media folder is not built into this system it is included in the download just add it to your sdcard should look like this /sdcard/media
ONCE AGAIN I AM NOT A DEVELOPER I WILL WORK ON WHAT IS OUTSTANDING AS I GET TIME. I MAY OR MAY NOT MAINTAIN THIS BUILD IF YOU HAVE A FIX FOR ISSUES PLEASE PM ME I WILL UPDATE FIRST POST TO REFLECT THE FIX AND BY WHO.
DOWNLOAD
USE ONE OF THE 320x480 NBH FILES FOR YOUR KAISER
Why you name it Desire build.. android on desire looks differently
Michga said:
Why you name it Desire build.. android on desire looks differently
Click to expand...
Click to collapse
This is an old build, mssmison put it out as a sdcard install on the vogue a long time ago before the legend builds were put out. I kept hold of it and tweaked it to work on my kaisers nand. That is why it looks much different than the most recent builds
Post it in the vogue forum. They get more attention so easier chance of a wifi/bluetooth update.
kallt_kaffe can probably help you with the wifi.
Dukenukemx said:
kallt_kaffe can probably help you with the wifi.
Click to expand...
Click to collapse
Try this (NOT TESTED!). I actually think just putting the correct wlan.ko in /system/lib/modules might be all it takes but I included the usual stuff just in case.
does anyone have a mirror for this build. I would like to try it out
Does anyone have market problem. I can't even enter the market, it just kick me out
crackeyes said:
does anyone have a mirror for this build. I would like to try it out
Click to expand...
Click to collapse
It should download for you I just checked it to make sure it was still validwhat issue are you having
Presenting FroydVillain 1.1.1, TeamVillain's Froyo ROM (Android 2.2)
FroydVillain 1.1.1 INFO & Release Notes:
IMPORTANT INFORMATION:
REMEMBER the ROM will only be at peak performance after it's been rebooted a couple of times, and when you've opened your apps once prior.
adb install won't work on this ROM, until you tick "Unknown Sources" in the Menu > Settings > Applications menu.
This appears to be a new security feature. Similarly, apps pushed to /data/app won't work either. You might not notice the issue, but the app does not get any of its permissions it should have, meaning that it is probably useless, and might FC constantly or whatever. So remember to tick the Unknown Sources box
The stock camera doesn't work properly - it takes photos OK, but it doesn't do live preview. The app "Camera Magic", which is free on the market, works fine, so we recommend that.
RELEASE NOTES:
Fixed in this release:
Multi-touch restored to improved touchscreen driver
Applied workaround for akmd running at 100% cpu utilisation (Thanks alankila)
Fixed GMail app resolution
VillainROM Updater now works
Compcache enable/disable script fixed (compcache on by default)
HTC Sense ringtones added
Issues outstanding:
Camera
Notification and chargeLEDs
Autobrightness (only dims when screen is turned off)
INSTRUCTIONS:
Coming from FroydVillain 1.1.0:
Do a wipe of data and dalvik at least.
Coming from any other ROM (Including FroydVillain 1.0.0):
Do a Full wipe, preferably including EXT.
DO NOT POST SUPPORT REQUESTS WITHOUT DOING THIS.
Click here to download
Enjoy, and be sure to leave any feedback
Thank you,
The VillainROM team.
dam gonna have to try this!
Sounds awesome. Just out of curiosity, is the fix for the camera live preview planned at all?
Mind making a quick list of the differences over 2.1? and is flash 10.1 planned for the near future? i remember getting it to work (pretty slow mind) with a .apk someone made.
Thanks anyway, great job guys!
How does the apps on ext work? Do widgets and apps stored on ext show on home screen? Been using the test alpha as this problem occurred in full alpha.
Sent from my HTC Hero using XDA App
Nice. I've been waiting for a fully working froyo port. The camera issue was the last big problem for me. Will probably try this out tomorrow and report back (it's late here in the uk)
Sent from my HTC Hero using XDA App
Thought that with the official 2.1 out and most ROMs being based on that, I'd thought that that I would stop playing around with new roms for a while...
Well that's gone for a toss now - thanks Villain team - downloading now...
Jep TeamVillain did it again, they make my heart beat faster! Thanks again guys!
donated
kyleblyth said:
is flash 10.1 planned for the near future? i remember getting it to work (pretty slow mind) with a .apk someone made.
Click to expand...
Click to collapse
Wait - what? Where from??
wow a very small rom only 60mb.....
sheridan2000 said:
wow a very small rom only 60mb.....
Click to expand...
Click to collapse
Well it doesn't have Sense, which is quite sizeable, bloaty and memory hungry.
wehaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Froyo On my Herooooooooooooo thanx maaan i will test it now !!!!!!!!!!!!!!!!!!
re
How about the A2SD and JIT? Are they enabled by default? Or have to do some setup manually?
Tomorrow I have an exame, but now I have to install this rom... feedback coming soon
without_wings said:
Wait - what? Where from??
Click to expand...
Click to collapse
was round here somewhere, i got farmville working for abit i think but crashed abit and a flash website but pretty slow...so uninstalled and deleted it, while back now.
Trying to download, but going sloooow...
Anyone have a mirror that isn't being battered?
great stuff, worked fine off first boot, coupel more, ran even better ..
one thing ...
the phone, when a call comes in, no slider for pick up/ignore ??
you have to use the phone hard-button to pick up ... how do you ignore call ? aside from turning volume down?
aside from that, camera magic is amazing, much better than stock camera anyways, even supports burst photos... amazing!! ...
but, if an update is made, a slider on the calls coming in woudl be sweet!
love this ROM so far, very snappy, and much better than the ezhero ROM's i've been using ... although, ezhero is 2nd best .. so no offence xenoside ...
i'll defn' donate when incoming calls have slider
worth downloading this ROM ... really well done, thanks villainrom.
Are my eyes deceiving me? Holy crow 2.2 for my Hero? DOWNLOADING HELLO!
just about to install after wiping everything fingers crossed!!!
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
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Caveats:
BT - works now! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details .
Yay! No more "when is FRX07 coming out?" posts!
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
And to that effect, I would like to personally apologize to everyone for how long it took. Life has been crazy busy the past couple months. Hopefully we'll get GRX01 out in a more timely manner.
Woooohooooo!!! Thanks to all of the dev's on this, Stine, Hyc, Emwe, Arrrghhh (for putting up with all the BS!), and anyone else involved.
Can't wait to try this out. Thanks to all who contributed =)
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
Just to get a sense of things, is it too soon for a "when is FRX08 coming out" post?
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
bluenote73 said:
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Ah yea... I need to test this on a RAPH800 I just got my hands on, thanks for reminding me!
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
wmg316 said:
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
Click to expand...
Click to collapse
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
arrrghhh said:
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
Click to expand...
Click to collapse
Thank you sir!
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
webxplore said:
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
Click to expand...
Click to collapse
Figured out...Had a corrupt zimage file. Able to launch now.
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
First Impressions
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
EDIT: Figured I'd list what is and isn't working for me. Again, I'm using all the default components like kernel and whatnot on the Tilt2 and have the phone overclocked to 710.400MHz now:
WiFi - Works
Data - Works (most stable I've experienced)
Bluetooth - Works (haven't tried headset)
WiFi HotSpot - Buggy; Turns on, but disabling keeps the notification icon and enabling again causes reboot. Different kernel doesn't fix.
USB Tethering - Works/Turns On (Don't have the driver to test quite yet )
Camera/Camcorder - Works (Camcorder doesn't record sound.. known issue?)
Phone - Works flawlessly
MMS - Incoming/Outgoing Works
maff1989 said:
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
Click to expand...
Click to collapse
+1
Come from FroyoB Hercules v2.
Any possible to run FRX07 on CWM?
FRX07 on cwm is being worked on by Eodun,wich sadly yesterday released FRX06 for cwm
rtrip said:
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
Click to expand...
Click to collapse
I would bet that the new audio routing stuff fixes the static problems. It definitely cleaned things up for me. But at this point I think we need a newer kernel in addition to the new audio libraries, the stuff in that audio routing thread is rather out of date at the moment.
I've been running most of this stuff for more than a month without issues. It's definitely going to be a lot more solid than any previous builds...