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?
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.
Hi!I just installed Android 2.0.1 on my Diamond with no problems at all(although the battery drains damn fast,camera and bluetooth kissed us goodbyes and GPS...wrong!)!
However,having used the Hero for a while now(I have both),I miss the Sense UI.I know I might be asking for a little too much,as it is still under development,but is there any way I can find an Android build with Sense?
Thanks in advance!
tolis626 said:
Hi!I just installed Android 2.0.1 on my Diamond with no problems at all(although the battery drains damn fast,camera and bluetooth kissed us goodbyes and GPS...wrong!)!
However,having used the Hero for a while now(I have both),I miss the Sense UI.I know I might be asking for a little too much,as it is still under development,but is there any way I can find an Android build with Sense?
Thanks in advance!
Click to expand...
Click to collapse
Hi
Sense isn't gonna be on the diamond for a while yet, check the main thread
If you used search, you would of found that out, please don't just make a new thread for everything
Badwolve1
has anyone had a look at THIS..i think if touch hd n rapheal can have it, we can also ( i got to the boot screen which kept looping at a lower res)
Do keep in mind that the diamonds RAM is a lot lower and the ram usage in android is not very good with the current builds..
imrock said:
has anyone had a look at THIS..i think if touch hd n rapheal can have it, we can also ( i got to the boot screen which kept looping at a lower res)
Click to expand...
Click to collapse
Did you try the SensePack for Android?
Yeah,RAM is IMO the worst aspect of the diamond...192?What is that?That's not only an android problem!WinMo also has issues with lack of RAM,especially 6.5!
And btw the reason why I created this thread was that I couldn't find a satisfying answer to my question!
Anyway,I tried aHome Lite(full version and GDE are paid and currently not available here in Greece) and it crashed like ****.It only popped the well known message that the process ahome.blah blah blah is not responding.
A question I'd like to ask is whether it actually runs ON WinMo or is WinMo closing before Android boots?Anyway the ****ty amount of RAM makes it annoying whatever the case is!
imrock said:
has anyone had a look at THIS..i think if touch hd n rapheal can have it, we can also ( i got to the boot screen which kept looping at a lower res)
Click to expand...
Click to collapse
I got to the main screen of Sense Hero..
1 - changed startup.txt : mtype to 1805
2 - i took the zimage from latest eclair (Keep the same if you want to)
3 - while booting it got stuck to HTC shiny screen so i deleted the Swapfile and tried...it booted up but PATIENCE is what we need. it takes a longtime and too much of Lag.
lets keep trying it...Best of luck!
There are android phones with the same amount of ram as the diamond (ie. galaxy/spica). So it should do fine but the build is just an early alpha . Patience patience..
Nickschot I hope you're right!It's such a nice phone!Why would it get stuck with WinMo 6.1(because 6.5 isn't it's thing) and get no attention?
Anyway...Will try Sensepack...Be back for report!
Well...First off it's laggy and buggy as **** and using it really needs patience!However as I see that's because of Sense...Is there any way to disable it?It appears to be working better than bare android...
salim1001 said:
I got to the main screen of Sense Hero..
1 - changed startup.txt : mtype to 1805
2 - i took the zimage from latest eclair (Keep the same if you want to)
3 - while booting it got stuck to HTC shiny screen so i deleted the Swapfile and tried...it booted up but PATIENCE is what we need. it takes a longtime and too much of Lag.
lets keep trying it...Best of luck!
Click to expand...
Click to collapse
the swapfile get recreated every time i try to boot haret n my sensepack always get stuck at the hero bootscreen, n u having it in fullscreen??
imrock said:
the swapfile get recreated every time i try to boot haret n my sensepack always get stuck at the hero bootscreen, n u having it in fullscreen??
Click to expand...
Click to collapse
Yes Data and sensepack gets created .... Yes it came in as a fullscreen but it was too laggy so decided to put a hold on to it...will stick to Android Eclair testing as of now...
I suppose I too will stick with Eclair(vanilla) cause sense messes things up really much...Right now,except for unbearable lagging and countless bugs Sense doesn't support fullscreen so you have to turn it off,Wi-Fi doesn't work(unlike vanilla Eclair which has a pretty much normal connection) and many things cause Android to reset.So I came to think...Android is really nice and functional without Sense!
However,is there any way to port Hero's look to the diamond?Without Sense crap.As long as the device is recognised as the Hero it seems to work better,more smoothly and fluid...Plus I love the black menus!
tolis626 said:
I suppose I too will stick with Eclair(vanilla) cause sense messes things up really much...Right now,except for unbearable lagging and countless bugs Sense doesn't support fullscreen so you have to turn it off,Wi-Fi doesn't work(unlike vanilla Eclair which has a pretty much normal connection) and many things cause Android to reset.So I came to think...Android is really nice and functional without Sense!
However,is there any way to port Hero's look to the diamond?Without Sense crap.As long as the device is recognised as the Hero it seems to work better,more smoothly and fluid...Plus I love the black menus!
Click to expand...
Click to collapse
Try Panda Home from Market Place and search for Hero Theme.....
Dude...I didn't know about panda home!It kicks ass!And it's really light!Less lag!And to think I was stuck with aHome Lite as my home replacement...Of course aHome full and GDE(?) must be better,however there are no paid apps available for Greece yet!
I know that I am going to be verbally destroyed for asking this but...
lol
I have an AT&T Tilt. Is there any single android distribution that has Working sound, wifi, camera, keypad, gps etc. I've tried a few different versions and each seems to have something good and something bad. Feel free to burn me up with flames of hatred, but hopefully I can get a clear answer somewhere in the inferno
Thanks!
xtty said:
I know that I am going to be verbally destroyed for asking this but...
lol
I have an AT&T Tilt. Is there any single android distribution that has Working sound, wifi, camera, keypad, gps etc. I've tried a few different versions and each seems to have something good and something bad. Feel free to burn me up with flames of hatred, but hopefully I can get a clear answer somewhere in the inferno
Thanks!
Click to expand...
Click to collapse
Myn's Warm Donut is near perfect (android 1.6). The only problem I've noticed with it is that the battery status is inaccurate, but that's true for all android builds for the kaiser to my knowledge. Other than that, it runs perfectly fine, very stable and quick, even from the sd card.
Fantastic Thanks!
I'm an idiot, wrong thread ;0
kallt_kaffe produces excellent kernel binaries and VanilijEclair is great!
Alright next question. Everything works but the sound. I can go in to adjust the volume, but when I try to leave that menu option I get "Activity Sound & Display (in application Settings) is not responding."
And in the jewels game I can not hear any sound either.
Any ideas?
xtty said:
Alright next question. Everything works but the sound. I can go in to adjust the volume, but when I try to leave that menu option I get "Activity Sound & Display (in application Settings) is not responding."
And in the jewels game I can not hear any sound either.
Any ideas?
Click to expand...
Click to collapse
are you running haret? currently (to my knowledge) sound does not work.
updating your radio, if its not already, could help
I also have an AT&T Tilt.
To answer your question, it's all about the kernel.
Look for DZO's kernels, and use the newest.
If you use Haret get the newest zImage and pay attention to the correctly editing the txt file where things have to be configured correctly for a Tilt.
If you burn to internal flash, use the NZH editor.
sound: yes
wifi: yes
camera: yes
keypad: yes
gps: yes
Right now I have an ATT Tilt running VaniljEclair with the 6/25 dzo nbh file edied with the nbh editor for my panel type.
Build from here: http://forum.xda-developers.com/showthread.php?t=700669
NBH from here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
NBH Editor here: http://forum.xda-developers.com/showthread.php?t=689813&highlight=nbh+editor
Has anyone tried running the latest zimages under haret? I've tried warm eclair and superfroyo, and both are having the same problem: If I put the phone to sleep, I get a solid white screen when I wake it up. Every time.
Frustrating that the latest distros of Android are unusable on my phone, warm donut worked like a charm.
TransparentHuman said:
Has anyone tried running the latest zimages under haret? I've tried warm eclair and superfroyo, and both are having the same problem: If I put the phone to sleep, I get a solid white screen when I wake it up. Every time.
Frustrating that the latest distros of Android are unusable on my phone, warm donut worked like a charm.
Click to expand...
Click to collapse
in default.txt change your panel type to 1,2 or 3
dadevil666 said:
in default.txt change your panel type to 1,2 or 3
Click to expand...
Click to collapse
Thanks, that worked, although I could swear I tried that already.
TransparentHuman said:
Has anyone tried running the latest zimages under haret? I've tried warm eclair and superfroyo, and both are having the same problem: If I put the phone to sleep, I get a solid white screen when I wake it up. Every time.
Frustrating that the latest distros of Android are unusable on my phone, warm donut worked like a charm.
Click to expand...
Click to collapse
Actually as far as I am aware this only affects panel 2 and 3, which appear very similar, but use slightly different power management signals, so if you use panel 2 on a device with panel 3, it looks fine, but suffers from strange issues when waking, although I have not heard any issues with setting panel 3 on a panel 2 device yet... maybe I should try it, just for research purposes
I get a solid white background as well, but it goes away after half a second.
I hate to reopen a dying thread but. . .
I have tried 5 different roms, from donut up, and have tried the roms suggested in this thread. I cannot get the camera on my tilt to work for anything. Not a single install has yeilded a working camera. I have the latest radio, newest froyo_tilt kernal, and im using VaniljEclair_RLS7c. . .i get nothing. . .nada. . .is there a fix anywhere for this damnable tilt camera?
Using a froyo kernel on an eclair build results in a non-working camera, you should be using an eclair kernel.
hmm. seems common sense. . .i will be annoyed if that is the issue. . .all the guides say grab the latest kernel and use the nbh editor to set parameters to whatever build ver. I will try the eclair kernel. thank you zenity
OMG common sense ftw!! sorry to waste your time with this, I really appreciate it! gravy!
No problem, it has been mentioned in a few other threads, but it's not that easy to find, unless you are a forum addict like myself
Note that when using the nbh editor, setting donut or eclair refers to the HW3d option only, since donut and eclair have different 3d settings.
And it's never wasted time, someone else with the same problem may read this, so it helps everyone
yea, helped me just now, doing exact same, using froyo nbh with donut,
thanks
^^ there are no stupid questions, and time spent answering questions is never wasted if it helps others also
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
I have tried both a Froyo variant and a Gingerbread variant on my Diamond but for me its not usable at all .. It lockups every 30 seconds for like 1 minute. Just when my devices screen goes black i am barely able to turn it back on again.
Now im not complaining about the devs work here, dont take it that way.. I just want to know if its supposed to run this way or if its something i do wrong?
Da9L said:
I have tried both a Froyo variant and a Gingerbread variant on my Diamond but for me its not usable at all .. It lockups every 30 seconds for like 1 minute. Just when my devices screen goes black i am barely able to turn it back on again.
Now im not complaining about the devs work here, dont take it that way.. I just want to know if its supposed to run this way or if its something i do wrong?
Click to expand...
Click to collapse
try to install android rom on your device's internal storage and use GenYDualBoot to be able to run it from windows !
Hakim Rahman said:
try to install android rom on your device's internal storage and use GenYDualBoot to be able to run it from windows !
Click to expand...
Click to collapse
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Lipinsky said:
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Click to expand...
Click to collapse
I have two 2 months applying it to my Htc diamond {dual boot = Eto.Y 2.4a WWE + XDAndroid FRX07.1 (on internal storage)}
Lipinsky said:
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Click to expand...
Click to collapse
The usability has definitely increased over the years but it is still more a concept than a real operating system as the hardware and software dont work together very well. This is because there are no official kernels, drivers or anything provided by HTC. The xdandroid team has done an incredible work to get android running on this device, but they couldnt find a way to properly get android on the NAND because the storage is too small. Thats also why you have to start it via windows mobile and cant directly boot to it, it runs out of the SD Card. So you will never achieve a nice performance as long as the OS isnt located on the NAND. The lags and force closes you are certainly experiencing derive from this problem. The device itself would definitely have the power to run android at an acceptable performance.
As far as I know the development has ceased. If you search the corresponding threads you will find the statement of the devs. Here is were you can look:
Froyo, Gingerbread: http://forum.xda-developers.com/showthread.php?t=951981
Froyo 07: http://forum.xda-developers.com/showthread.php?t=951811
Gingerbread 0A: http://forum.xda-developers.com/showthread.php?t=711692
wiki: http://xdandroid.com/wiki/Main_Page
blog: http://southcape.org/category/android/
yeah development seems to be halted, its nice to play with, but not as main os for day to day use