Related
This is for all Sense versions of Flan 2.1. This is development and not for general use yet until it's more stable and faster. If you are new to Android, start here www.androidonhtc.com it will tell you what you need and where to get all the files. If you need further help, check the bottom of this post for more links.
It's very early and there are a lot of bugs with it. This is a work in progress. I'm hoping for some help from the community to get this stable enough.
I don't need any bug reports, just development to get this to beta.
If you can help develop this I will keep the updates (and credits) on this post as we move forward.
Expect a lot of changes very quickly. I'm operating on the release early and often approach to get this out to the community. This is high priority for me because Flan is a very nice release but it needs work.
========================================
STATUS
* Hero and Espresso boot to Rosie. From there it gets complicated
* Espresso (I think Hero too, so much switching back and forth) FC's acore when dialing at the moment.
* Hardware keys do work
* HTC widgets do not work (for now)
* More I forget at the moment..
========================================
Download Section:
----------------------------
[CURRENT]
* Espresso
DOWNLOAD: Espresso Flan 2.1 01-13-10
Stable Espresso based on Eugene's V2 port for G1/MT3G. Many thanks to him and mssmison for pointing me to it. Just came out (01-12-10) with working everything but HTC widgets so far. Still a little slow but usable.
* Hero
DOWNLOAD: Hero_2.1_enate_011210
Based on Hero21 Community port
[DEPRECATED]
* Espresso-2.1_enate_01-10-2010
Based on Eugene's port
The dialer FC's due to vibrate hardware permissions.
Also you need to add flanhero init to your rootfs or change it to eclairhero. The boot class paths are the same either way. If you don't know what I'm talking about you should really wait for us to get further along. The stable current release uses Eclair settings so should boot right away like it does for me.
* Test Version 1 of Espresso
Original test image based on Kingklick's Espresso port.
A lot of bugs such as hardware keys are broken. Need I go on? You have to use ADB to kill the current screen to get back home..
========================================
Credits to everyone including dzo, vilord, zenulator, mssmison, jamezelle, jeckyllhavok, polyrythmic, drizzy and the rest of the G1 and MT3G devs, maxisma, barakinflorida, the list goes on. I don't take donations but some of them do and they deserve it.
========================================
Helpful links and people who have helped me get where I'm at:
Google Android and Linux for KAISER!!-- Main thread for Android on our phones
Linux and Android for Vogue (Kernel Thread)-- Dzo's thread for kernel development. He got us started and is a legend here.
Zenulator's threads for Vogue (they work for us too). He has dedicated a lot of time to helping us out.
Android with sense UI for the vogue
Vogue Android 1.6 Donut
Android 2.0 Eclair for the Vogue
_________________________________________________________________
Looks nice! I think I'll definitely give it a spin. Is there any way to get WiFi on this build?
Using Eugene's port now. Hardware buttons work, HTC widgets don't, dialer crashes acore. Looking good but will need some tweaking before I upload it.
Thanks for the update man, looking forward to this in more of a complete state. Does this work with qvga?
ajclai08 said:
Thanks for the update man, looking forward to this in more of a complete state. Does this work with qvga?
Click to expand...
Click to collapse
i HIGHLY doubt it.
We've got some major issues. I guess the G1 and MT3G have HTC widgets working. Something is wrong but it's going to be a little while. Look where we are with Eclair and this is Flan. Also, I'm switching this thread around to include all Flan images shortly. Just need some more dev to make it worthwhile. I can either make a call but lose hardware buttons or not make a call and have them...
enatefox said:
We've got some major issues. I guess the G1 and MT3G have HTC widgets working. Something is wrong but it's going to be a little while. Look where we are with Eclair and this is Flan. Also, I'm switching this thread around to include all Flan images shortly. Just need some more dev to make it worthwhile. I can either make a call but lose hardware buttons or not make a call and have them...
Click to expand...
Click to collapse
with eugenes port? what is breaking the hardware buttons now?
No, Eugene's has working buttons but the dialer is broken. He said to use another dialer until he fixes the permissions. I'm going to just try to fix the permissions myself though. Still can't get the HTC widgets again like I had before and there are very little debug messages to help. At first boot it just says "can't find widget xxx" over and over again on Espresso and Hero 2.1
I'm booting Espresso again. If I can get somewhere now (at least the dialer to work) I will update the post. It's 2am now so we'll see...
enatefox said:
No, Eugene's has working buttons but the dialer is broken. He said to use another dialer until he fixes the permissions. I'm going to just try to fix the permissions myself though. Still can't get the HTC widgets again like I had before and there are very little debug messages to help. At first boot it just says "can't find widget xxx" over and over again on Espresso and Hero 2.1
I'm booting Espresso again. If I can get somewhere now (at least the dialer to work) I will update the post. It's 2am now so we'll see...
Click to expand...
Click to collapse
its 2 am here too. i feel so helpless without my hdd i wish i could help!
Regardless of what comes of this, this is cool to see. I'm still digging polyrhythmic's Eclair build, but it would be awesome if we were running Flan in the future.
EDIT: Oh, I was being a n00b and didn't read the post completely to see that this isn't actually Flan. That's okay though - any Android work is good work.
This is Flan. I started with Eclair and moved up (thanks jamezelle). I should update..
enatefox said:
This is Flan. I started with Eclair and moved up (thanks jamezelle). I should update..
Click to expand...
Click to collapse
hey you should check out kings/eugene's who ever the hell it is. lol any way check out the latest release, mostly bug fixes from what i remember reading. im still hard-driveless running off of karmic live cd for now. so ill help when i get set back up
The deprecated test image on the OP is King's. I'm using Eugene's now and it fixed a lot of bugs. I'm messing around again hopefully can get some new images added soon
enatefox, the permissions in bin are not correct in the image you have uploaded last. I will try to correct them and see if I can help with something
Ok, I have corrected the permissions in bin and managed to boot the image.
First it took very long time to boot and second most of the applications become not responsive, while they are trying to load in memory. I saw the problem you are talking about with the HTCDailer.apk and hope you find solution for it (I will also try to check it).
Another thing is that I cannot see HTC widgets, which is strange, because I can see some of them in the app folder. Others have to be added.
About wifi it starts successfully, but when I try to connect to ap it says Obtaining address and cannot manage to get an address - what permissions are missing in this case? Maybe tiwlan.ini?
Borkata81, thanks. I don't know what was wrong with the perms, I ran genext2fs on it. I guess I can compare them or could you post "ls -l" on the right ones so I can fix that?
The dialer will need to be hex edited if I'm right about the issue. Not even Stericson can convert XML back to binary without compiling the app we don't have source code for so I'm on to fixing it if I can.
The widgets are broken. I had them working once but issues with King's version (on the OP) had me delete it and now I've lost what I did. But it is fixable if I can remember what that was...
I have not even touched wifi as I can barely use this thing and the dialer doesn't work. I haven't put any of the right files for that in there.
Code:
chown root:2000 bin/*
chmod 755 bin/*
chmod 2755 bin/netcfg
These are the commands
Hmm, I do recall seeing root:root now that you mention it.. Thanks did you notice any adverse effects though or you just letting me know? Particulary like dialer perms or anything?
Well, applications load very slowly sometimes and message to FC or wait is shown and after pressing several times wait they manage to load. Maybe we can try to optimize some of them. I made a search and saw that for current Sense UI some of the app shouldn't be optimized, but I am sure that most of them can be.
To be honest Rossie is pretty fast though - of course it take time to initialize at the beginning.
P.S. I am currently downloading latest Kingx Espresso 1.1 to see what can be taken from there, but I will continue experiments tomorrow maybe.
King's was way too problematic for me as noted on the OP but maybe a good blend can be made. For HTC apps you want almost none optimized outside of images yet Rosie is small already. Dragon's version is about 18MB just by itself.. There are also 3 other apps/services that run to help Rosie now and that's killing memory.
There will be a lot of improvement on the usability but I need it to at least work as a phone before I do any of that.
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?
This is my port of Cyanogen's latest Eclair build, v5.07-stable.
It is basically mssmison's 5.07-test3 build updated, I used the same process he did to port this one.
Included Apps:
-Connectbot
-Astro
-RogueTools
-LinPack
-HomeSwitcher
Notes:
-No major problems found so far (besides Eclair-specific problems like the Camera not working).
-Speed is comparable to other Eclair builds, maybe even a bit zippier at times.
-It should be fully compatible with any themes/mods made for Cyanogenmod v5.07-stable. (Although my attempt at flashing this theme sent my phone into an "android.power wakeup" loop, so be cautious!)
--Darkstar theme isn't working either, thx for trying @thebulletfromhell!
-It is set to 120DPI by default, so if running anything other than 320x240, you'll have to use RogueTools to adjust it. I am currently running it at 320x240x120dpi and haven't experienced many problems, except the top and bottom of the Dialer are cutoff, button's still reachable though. (If someone wants to help me fix this, please do, I just don't know where to start)
-Wifi support for the Kaiser is built in, should work out of the box!
-Starting with v1.2, Userinit.conf is added to the root of your SD, by default it has 16MB of Compcache, but this can be adjusted by editing the file.
Download! [Last updated on 5/29/10]
Changelog:
v1.3
-Removed userinit.conf, now everything is run directly from /system/bin/userinit.sh
-32MB Compcache by default
-Removed overclocking from the get-go. You can set it manually via RogueTools.
-Userinit.sh now renice's com.android.phone to try and improve ringing delay.
v1.2.1
-Removed redundant wlan.ko
-Replaced wlan.ko with kallt_kaffe's
-Reverted a change to userinit.sh that was causing awful performance
v1.2
-Removed Dropbox, Speedtest, Twicca, Shazam, 3Banana Notes, and LiveWallpapers
-Added Camera back (Fixes FC when trying to crop a wallpaper)
-Fixed Facebook Sync
-Userinit.conf is added to the root of SD card on first boot. This allows you to control Compcache, swap, and many other settings.
Click to expand...
Click to collapse
Thanks go out to mssmision for his port+quick guide to porting, Cyanogen for the build, and all the other developers that worked on getting Android running on this phone! You guys have made this phone so much more usable.
Woah, it's weird being in a different forum.
What is updated in this new version (1.1)? I'm still running the first one you posted in the Vogue forums (on a Vogue) and it's working great.
Cool!
Gonna try this one out.
Thanks a lot!
pastaeter said:
Cool!
Gonna try this one out.
Thanks a lot!
Click to expand...
Click to collapse
Let me know how it goes.
drkow19 said:
Woah, it's weird being in a different forum.
What is updated in this new version (1.1)? I'm still running the first one you posted in the Vogue forums (on a Vogue) and it's working great.
Click to expand...
Click to collapse
The updated version has wifi working for Kaiser, and some compcache tweaks done to /system/bin/userinit.conf. The first version I think I disabled compcache entirely, and it really showed once you got the build fully loaded.
any screens? how to install themes on Kaiser? Little guide please...
just downloaded going to give it a try
all live wallpapers dont work and show force close (exclude polar clock)
but its cool and fast (default it set at 450MHz and i set it to 500MHz)
Bench at 500MHz: MFLOPS:2.141
Times: 2.53s
Norm Res: 3.36
Precision: 2.224...
Maybe you add-in many of not neccessary app..
and one very good thing.. i have i think 320x428 and 120DPi in RogueTools. and its less blurry than thats sets in myn
Congrats for good rom.
exist CM with sense 2.1 on kaiser?
Compared to super eclair it has a few advantages:
-language dutch is included and fully working
-more options: look at call settings.
-market is fully working (for now), but no paid apps (super eclair market broke after using a time, not all apps can be found).
But less free ram.
Not really worth upgrading for me (I have 2 kaisers).
i've installed this build on my kaiser and it works great.
tested the wifi, the market, both work great. bluetooth turns on but i haven't had the chance to send or receive any files or to connect it to my wireless headsets.
did not test the data yet.
installed helix launcher and i think it moves a little bit faster than the regular home screen.
thank for the upload
mazz8y said:
any screens? how to install themes on Kaiser? Little guide please...
Click to expand...
Click to collapse
Here's a guide to installing to NAND. The build is not themed at all, so you can check out the official Cyanogen thread for screenshots, they should look identical (besides a smaller res).
Michga said:
all live wallpapers dont work and show force close (exclude polar clock)
but its cool and fast (default it set at 450MHz and i set it to 500MHz)
Bench at 500MHz: MFLOPS:2.141
Times: 2.53s
Norm Res: 3.36
Precision: 2.224...
Maybe you add-in many of not neccessary app..
Click to expand...
Click to collapse
Yeah I just noticed the Live Wallpapers crash, didn't try this out before. Not sure if it's possible to fix it, I don't remember them working on any other Eclair builds.
Also, I noticed that /system is running low on space, so I will definitely try to trim some fat by removing pre-installed apps.
Michga said:
exist CM with sense 2.1 on kaiser?
Click to expand...
Click to collapse
Not that I know of. But there is a QVGA Android phone with Sense coming out sometime this summer, and I'm sure someone will attempt to port it.
From the vogue thread...
Great build, I'm running it right now, and it thus far seems to be fast and stable! (bumped up the o/c to 500)
Two pieces of feedback...
If you can get facebook sync to work with the most current facebook app (the one with the "inbox" button rather than the "take photo" button it would be amazing. As of now, the only way to get facebook sync to work is to run the Moto Droid apk, which is the previous version.)
Anyway to get full market from the getgo? I have marketenabler working, but it isn't always consistent.
That being said, amazing build. Good work.
Click to expand...
Click to collapse
@GeJohnO: Looks like this is a known issue with the original Cyanogen
A few known issues;
* Facebook from market breaks sync for Market users (see forum for alternative apk) - only on Dream, Sapphire is OK. Blame Facebook.
Click to expand...
Click to collapse
I'll look into including whatever alternate APK in the next build.
Also I found that taking out the Camera app causes Gallery to FC when trying to crop a wallpaper, so I'll fix that as well.
I just got a text message from the 24th of this months with super ecalir lite, I don't know if this version hzs those issues too?
aqtrans said:
This is my port of Cyanogen's latest Eclair build, v5.07-stable.
It is basically mssmison's 5.07-test3 build updated, I used the same process he did to port this one.
Included Apps:
-Connectbot
-Twicca
-3banana Notes
-Astro
-RogueTools
-Dropbox
-LinPack
-Speedtest
-MetaMorph
-HomeSwitcher
(I will probably cut this down a lot in future builds, kind of made this for my own personal use and threw in all the Apps I usually reinstall)
Notes:
-No major problems found so far (besides Eclair-specific problems like the Camera not working).
-Speed is comparable to other Eclair builds, maybe even a bit zippier at times.
-It should be fully compatible with any themes/mods made for Cyanogenmod v5.07-stable. (Although my attempt at flashing this theme sent my phone into an "android.power wakeup" loop, so be cautious!)
-It is set to 120DPI by default, so if running anything other than 320x240, you'll have to use RogueTools to adjust it. I am currently running it at 320x240x120dpi and haven't experienced many problems, except the top and bottom of the Dialer are cutoff, button's still reachable though. (If someone wants to help me fix this, please do, I just don't know where to start)
-Wifi support for the Kaiser is built in, should work out of the box!
Download!
Thanks go out to mssmision for his port+quick guide to porting, Cyanogen for the build, and all the other developers that worked on getting Android running on this phone! You guys have made this phone so much more usable.
Click to expand...
Click to collapse
Add the darkstar theme to not working as well. It put it in a permanent loop
thebulletfromhell said:
Add the darkstar theme to not working as well. It put it in a permanent loop
Click to expand...
Click to collapse
The darkstar theme hasn't been released for 5.0.7 stable. The most current release is for test5. This may be why it's not working for you
I tried mssmison's test 3 out, and it was problematic. A lot of stuff would end up resetting the phone, back to the start up animation. Haven't tried this one yet, but my experience with Eclairs have been bad so far.
Wish there was a way to run Android on both NAND and SD cards. That way, I can test them out on the SD card, without destroying my NAND installation.
Running this port since yesterday and I must say I'm really impressed. Fast, responsive and also it seems not to drain battery as fast as other builds.
Any chance of getting Corporate Calendar in the next version (currently Exchange sync works only for Mail and Contacts in this build).
Version 1.2 posted! Changelog in the OP.
I tried adding the modded Market, but it kept FC'ing whenever an app would go to install. Looking at the thread, it seems like a known issue, without a fix that I could find
robuser007 said:
I just got a text message from the 24th of this months with super ecalir lite, I don't know if this version hzs those issues too?
Click to expand...
Click to collapse
I haven't experienced any such issues. As far as I know, I've been receiving texts on time, without delay.
thebulletfromhell said:
Add the darkstar theme to not working as well. It put it in a permanent loop
Click to expand...
Click to collapse
Added a note to the OP about this. Thanks!
aqtrans said:
Version 1.2 posted!
Click to expand...
Click to collapse
Suggestions for 1.3
- Remove /system/etc/wifi/wlan.ko (not needed)
- Replace wlan.ko /system/lib/modules/wlan.ko with the attached version (I believe it works better for Polaris users)
I was about to suggest increasing the wlan scan interval but I noticed that you hade allready done that.
I've had problems with builds that have sensors.msm7k.so all by itself so I added the sapphire sensors before I installed v1.1 as a precaution but I'll try without doing that once I reinstall with v1.2 and I'll let you know how it goes.
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...