Related
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Are there any ways that I can actually speed this thing up?
Ive used ATK and thats about it. Im out of ideas here.
Also: 1) Is there anyway to fix the backlight issue when coming out of sleep mode? (It stays at minimum brightness)
2) Is there anyway to transfer winmo contacts to XD?
howeasy said:
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Click to expand...
Click to collapse
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
You could try overclocking but it should be pretty speedy already. Is this your first build of Android? Have you deleted data.img and let it remake it. Try formatting your sd card.
ben_duder said:
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
Click to expand...
Click to collapse
That is indeed the build i'm currently using.
The official XDAndroid build of 2.1 would give me the endless fireworks screen even and updated zImage.
If there's a version that will work on my Fuze then please link me to it as I have been unable to track it down.
But regardless, I've been working on trying to get it to run faster, Ive had moderate luck using ATK but thats about it.
Im baffled as to why its running this slow.
Also, using the 2.0.1 build caused the phone not to send SMS messages, hence the reason I came looking for a new build and came across the Sense one.
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Here's proof (if you want it) that it's normal for it to take ages to load on first boot.
ben_duder said:
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Click to expand...
Click to collapse
Indeed I did. It simply played the Nexus one boot animation for a while, froze for around 5 seconds, and then went back and played the nexus one animation from the beginning.
The sense build im using works in all aspects other than the fact I would prefer the normal Android layout, I want it to run smoothly, and I want a more constantly updated version.
I used the Fuze startup text with and without the overclocking script thrown in.
I'd be more than willing to go at it again if its worth the shot.
I really recommend having another go: XDAndroid is exactly what you're looking for with regards to the lack of Sense and the frequent updates. There's no hardware-related reason why it shouldn't work on your Fuze, so delete everything from the build that's already on there, get the right startup.txt and give it a go
Thanks for the positive reinforcement!
If you could possibly directly link me to the 2.1 build you'd personally recommend that would be appreciated.
Ive been trying a build for the RAPH800 that was linked to in your sig and its giving me to the same problem I described earlier.
I have the RAPH110, as you know, but the RAPH800 build was the closest thing I could track down.
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
ben_duder said:
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
Click to expand...
Click to collapse
Oopsy! I had a hard time tracking that down.
Im using the one labeled "03.05.10 | 2.1 builds". Is that correct?
It also says it already has the lastest zImage that should work so do I need to go update that?
I swear, if there was a super mega +rep button i'd press it.
You're what support forums are all about <3
(3:42PM: Just calibrated touch screen)
Yep, that's the one I'm trying. I've had some experience with the 2.0.1 but I've never actually used this build before, so it's possible there's something missing that I don't know about.
Haha thanks, although there are much nicer and more knowledgeable people on here than me
Well you're the one putting forth the effort to help a guy in need, so I truly do appreciate it.
I'm still getting the constant Nexus one boot animation sadly enough.
Maybe I'll go test out the 2.0.1 build and see if I can get that one to work, but like I said earlier, I had SMS issues with that one.
EDIT: I was able to get the 2.0.1 build working with SMS after zImage and etc..
Going to test sound and whatnot now and come back with another edit to verify.
I would still like the 2.1 build though but this might have to suffice.
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
ben_duder said:
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
Click to expand...
Click to collapse
AWESOME!
Mind uploading whatever it is you did and tell me what I have to do to get the same result?
Sorry, Im still pretty new to this whole thing.
I won't upload it, but just check your startup.txt and there should be two lines of text that look like they should be separated. Press return just before the second, save it and delete your data.img file. Then run HaRET again and it should work fine.
You have to try this build - it's brilliant.
Well I suppose I'll have to give that a shot.
I found and edited the lines and also threw in the overclocking script.
After deleting the data.img Im giving it one last shot now.
If that doesnt seem to work then I'll just deal with the 2.0.1 build until I find a way to get this to work.
EDIT: anddddd, no such luck.
Guess I'm left to stick with 2.0.1 for now, it was running pretty fast as well.
So if anyone reading this gets 2.1 working please feel free to post.
Is there a way to get Android on the phone itself rather than SD? I'd love to ditch Winmo and save some battery life here.
Shame... I can't understand how it's not working now. All I did was edit the startup.txt, delete my data.img and try again, then wait for ages while everything loaded. If you're not sure if you've edited your startup right you can try using the one that works for you with 2.0.1.
As for not having to use the SD, that would require NAND flashing, which has some way to go before we can use it on our Touch Pros to replace Windows Mobile. There's a thread about it here. There are dual-booting and light WM ROMs designed for XDAndroid users, however.
In case you don't believe me
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk
Did you happen to update the zImage or anything or did you just copy and paste and throw in the startup?
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
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Seriously. No one else has experienced this problem? I've literally spent hours searching XDA trying to find a solution.
Youtube works on mine... tell you what. Flash the nbh with panel type 1.
Even if you get screen artifacts, or other issues, try the video. If you can play, then you've isolated the problem to the panel type. If not... oh well.
I'll try meridian and see what i get.
Just out of curiosity, I tried flashing it with all three different panel types; same results. I have overclocked to 520 mhz; would this cause any problems? Every other program seems to work fine. I'm honestly baffled.
Via Atools or RogueTools ?
Via atools. Thanks.
Do not OC via Atools. Might not have nothing to do with it, but RogueTools seems MUCH more stable. Just and advice
Removing the overclocking from atools has not made any difference. Thanks for the suggestion, though.
Same problem. I managed to play some videos with poor quality, so maybe this is a performance related problem.
Looks like it's back to WM for me. The lack of video is a dealbreaker for me. Sorry that you're having the same issue, sloikas. Windows plays everything I've thrown at it.
Back to the dark ages on our kaisers lol? What may be affecting your video playback is the radio rom. It actually contains a little more than the radio and in my experience can affect playback of videos. Also if your trying to stream over edge, good luck with that. Over wifi I have next to no issues with Barebones 4.55, overclocked to 575 mhz and on wifi.
Thanks for the reply. Just out of curiosity, I tried three different radios: 1.70.18.02, 1.70.19.09, and 1.71.09.01. Same results with each of them. I don't have a data connection with my phone, so I am only using wifi. I have also tried to play MP4's on my SD card.
Video is supposed to be working. How exactly do you have it set up atm?
erickrause01 said:
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Click to expand...
Click to collapse
use KAISIMG, And mind that you need a corresponding kernel. Atools is creating problems for me in editing the kernels. I suggest you try a stock kernel with respective build. (FROYO kernel for FROYO, Eclair kernel for Eclair and Donut's for Donut). So far, Meridian is the best media player for me and I am using it on Donut (Warbyte's or Myn's ? your choice).
To check which panel type is nice and good is to check your SCREEN's colours. Are they perfect? is Touchscreen working good? and is brightness set good. First thing you notice after flashing wrong panel type is colours. Deformed Colours, usually u see each pixel as showing rainbows.
Flash a KAISIMG kernel I say and do not play with them on Atools / iHex or what so ever.
For instance try this,
http://phobos-lab.net/android/Warbyte Donut RLS04.zip
kernel is included and panel type is set to 1, Device keyboard is set to HTC Kaiser default. I say use iHex to edit the nbh for your suited panel type/keyboard.
Installing Data on SD Card can cause browsers to malfunction and almost Force Close on anything. Try installing on NAND (both SYS and DATA)
erickrause01 said:
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Click to expand...
Click to collapse
To play video, convert your clips/video to mp4 and use yxplayer to play them. This was the only working solution for video issues for me. Now I can play any video as long as it's in mp4 format and i'm using yxplayer to play it.
About youtube...are you on WIFI or mobile net? Youtube on wifi defaults to HQ video which our kaisers cannot play for some reason. Solution use 3G/H or if you're on wifi .......when the clip is loading click a HQ icon on the screen it should be in the right upper corner on the screen(depending on youtube app. version) that should load LQ/MQ version which plays fine on kaiser.
Thanks so much to dark_prince. His instructions worked perfectly for me. I now have a perfectly working (for me) Android phone. Awesome! Thanks to all that tried to assist.
Was just curious as to what build you were using. It basically sounded like he said to use a vanilla build with atools edit'd for whatever build you are going to use. I hate Donut just due to how old and slow it is. I do not think the build you are using matters, it sounds like you had a kernel configuration problem if it is now working.
erickrause01 said:
Thanks so much to dark_prince. His instructions worked perfectly for me. I now have a perfectly working (for me) Android phone. Awesome! Thanks to all that tried to assist.
Click to expand...
Click to collapse
I am glad that I was of to good use for humanity.
Cheers mate
aceoyame said:
Was just curious as to what build you were using. It basically sounded like he said to use a vanilla build with atools edit'd for whatever build you are going to use. I hate Donut just due to how old and slow it is. I do not think the build you are using matters, it sounds like you had a kernel configuration problem if it is now working.
Click to expand...
Click to collapse
for OLD I might agree. But for SLOW I wont ever. Donut is far far far far far far better than those eclairs or froyos out there. Particularly when my battery lasts for a day on Eclair / Froyo, it lasts for almost 48 hours crisp while using Donut. So please sir...
Well its like I said before, it is really the kernel that is making battery last longer. My barebones with a proper .32 kernel (Still waiting for clemsyn's .32 to be committed to git) and stock speeds is plenty fast and gets almost equal battery with more features and apps. I of course could overclock it but that drops battery to around a day which is more than adequate.
video doesn't work for me either....
I have VOGUIMG-320-FROYO-01-16-11 changed to kaiser and to panel 2 with atools... CM 6.1 barebones build both sys and data on nand... and is working really fine ( is the only one i've tried... )
already installed meridian and rockplayerbass the best i could get was with rockplayerbass with software render but the image was very ver slow... =(
erickrause01 , did you installed only kernel or entire build that dark_prince advised? and did you changed panel? what is the difference to change panel with atools and ihex? ( dunno how to use it ;P but if necessary will learn...
If only the kernel is needed to be changed, if i install new kernel do my installed build be ok or the process is re-installing kernel and then build again? i'm still with this doubt...
I would like to stay with this build because almost everything is running fine... little by little i'm getting my android to "perfection" hehe although some apps aren't working i'm finding solutions for almost everything.. video and camera is not one of that .. yet ;P
sorry for the bad english ;P
edit: when installing kernel i've changed name to KAISIMG
edit2: build is Scoot CyanogenMod 6.1 RLS5.5 not barebones....
Hello,
Currently I'm running Debian Wheezy [armel] [xfce] on my vk810. I love this app; however I would like to use the framebuffer instead of VNC.
I am also having issues properly configuring the frame buffer so that it functions. currently the device freezes when I stop the android gui and initiate the debian gui. I have yet to get it working successfully, trying multiple DPI, and frame buffer settings.
I'm thinking it would be awesome to run debian from my vk810, having the enviroment displayed through my slimport. Idealy it would be nice to assign debian a seperate framebuffer than the android enviroment so that I can use both enviroments simultaniously without using a 3rd party machine running the VNC client.
So.
Has anyone had any luck with successfully running the linux deploy enviroment through their frame buffer, if so what settings/enviroment/architecture did you use.
Is it possible to run android and linux deploy environments on seperate frame buffers? ie. Android on the device display and debian on the slimport attached display.
I'd also love to hear some feedback from those who have been successfully using Linux Deploy on their LG G Tab 8.3's. What do you find works best, what distro/arch are you running, and how are you dealing with limited arm7 support.
For those of you who do not know what Linux Deploy is, you can check it out here. If you also have a better recommendation for a linux deployment suite please share!
Thanks.
Very interested in this. Was running AntiX with Fluxbox, and now Mint on my laptop and couldn't get vnc to work at all. Must have been doing something wrong.
Anyway, having a separate partition for Linux on android would be awesome! Don't really know what I would do with it other than a decent browser and maybe gimp?
I'm willing to give it a go as well. I'm sure it will be a learning curve though.
How are you doing this with a locked boot loader? Or is it not relevant? Regards,
sleekmason said:
Very interested in this. Was running AntiX with Fluxbox, and now Mint on my laptop and couldn't get vnc to work at all. Must have been doing something wrong.
Anyway, having a separate partition for Linux on android would be awesome! Don't really know what I would do with it other than a decent browser and maybe gimp?
I'm willing to give it a go as well. I'm sure it will be a learning curve though.
How are you doing this with a locked boot loader? Or is it not relevant? Regards,
Click to expand...
Click to collapse
basically you use the already running kernal for your android system, using linux deploy or a few other scripts i've seen around the web allow you to boot an armel or armhf architecture using the already running android kernal.
To get a native debian or Arch system running on this device would be awesome, but I would just be happy with figuring out native frame buffer setup and having the ability to switch from the device screen or the slimport hdmi output.
I'm thinking this may be possible seeing how the device screen has an independent frame buffer from the slimport [fb1].
I'm personally just starting to experiment with it, I'm not that experienced but I think it has a lot of potential on the vk810, not just because of the dpi [243] but also becuase of the slimport accessibility.
crashtheface said:
basically you use the already running kernal for your android system, using linux deploy or a few other scripts i've seen around the web allow you to boot an armel or armhf architecture using the already running android kernal.
To get a native debian or Arch system running on this device would be awesome, but I would just be happy with figuring out native frame buffer setup and having the ability to switch from the device screen or the slimport hdmi output.
I'm thinking this may be possible seeing how the device screen has an independent frame buffer from the slimport [fb1].
I'm personally just starting to experiment with it, I'm not that experienced but I think it has a lot of potential on the vk810, not just because of the dpi [243] but also becuase of the slimport accessibility.
Click to expand...
Click to collapse
I'm running the 510, so it may or may not be the same, but have you looked into the kernel settings for the framebuffer? When messing around in the 510 file I remember seeing a couple of options there for the config but don't know if they are relevant or not. I will look at it again to see if there might not be something else that needs to be turned on or compiled in.
sleekmason said:
I'm running the 510, so it may or may not be the same, but have you looked into the kernel settings for the framebuffer? When messing around in the 510 file I remember seeing a couple of options there for the config but don't know if they are relevant or not. I will look at it again to see if there might not be something else that needs to be turned on or compiled in.
Click to expand...
Click to collapse
I would look into the kernal issue but I have no idea what I'm doing. You could very well be right. I'm using the stock vk810 kernal I wonder if the 510 builds are compatible, and if they are if anyone has messed with the frame buffering.
crashtheface said:
I would look into the kernal issue but I have no idea what I'm doing. You could very well be right. I'm using the stock vk810 kernal I wonder if the 510 builds are compatible, and if they are if anyone has messed with the frame buffering.
Click to expand...
Click to collapse
Well, the cool thing is that if you look in my signature below you will see a link on How to roll your own kernel, and it is literally copy and paste all the way through. The only difference for your device would be in the read me that comes with the kernel source. Specifically, the version of the google toolchain to use, and the name of your devices "defconfig" in the kernel source..
In other words, one line to change slightly, and that's about it. You should be able to get the source from lg... Same basic location as I have outlined.
Wheezy should be just fine.
on another note, I did look at my kernel source file and for the most part everything looks real good. Slim bus is the way it should be with no further options and everything enabled. Frame buffer support should all be there except for console support. Which, I don't think we need any way. There was also support for virtual frame buffer, which is used for debugging purposes and I turned off for my most recent compile just to see how it'll work because it may or may not use a little more memory. Also there was a pretty cool option for turning on one of three Linux logos for your Android during boot I may mess with that a little bit.
Seriously, you should check out the kernel building. Its all there. The only thing that isn't is the Loki support, and that should be no sweat using one of the 500 kernel zip scripts. Either of the other two active kernel developers would help you with that. I'm sure.
---------- Post added at 06:52 PM ---------- Previous post was at 06:19 PM ----------
Okay, just checked out linux deploy through your link. Looks pretty cool but I dont understand the vnc bit. Is it installing a linux image on the sdcard and then booting from that? AND where does vnc come in? is it all in the device itself?
Okay, I get it now. Am downloading now. Using Ubuntu with precise and armhf. We'll see
sleekmason said:
Okay, I get it now. Am downloading now. Using Ubuntu with precise and armhf. We'll see
Click to expand...
Click to collapse
Yeah the VNC work around is kind of gimmicky, it also is assumed as the default config. I'm sure what is being done with Linux Deploy is easily accomplished with chroot and a few scripts in android terminal, but the gui is pretty straightforward and has worked pretty well for the distro's i've tried it with. Like I said earlier our LG's have a lot of potential with the slimport and the ability to run two environments side by side.
I just started reading into your make your own kernal I'm looking forward to what I learn. Thanks so much for this resource!
Okay, couple of things...
Our devices should support armhf no problem and it will be faster than armel. Also, might want to go testing rather than wheezy even though wheezy will be stable. I'm thinking here of the packages for armhf, and I really don't have any evidence this would be better. just a thought.
Also, From what ive read (which isn't much yet), SSH is what most are using as an interface, but vnc is for the graphical environment? Eh.. okay.
Our framebuffer should support 32 bit. I don;t have a clue about most of this yet.
Tried the unbuntu distro and there were packages missing. giving it a go on Debian testing now. Probably be tomorrow before I try anything more.
Looked up other ways to install linux and only saw this and another as a viable option, with this one being the better of the two.
and, here's the skinny...Debian Wheezy was the only one that would work. I tried testing, unstable, and squeeze. I didn't feel the need to go back any further.
using the frame buffer only wouldn't help you unless all you wanted to use is the terminal environment. All of the controls are through the VNC client. This kind of makes the framebuffer environment obsolete unless you have only a specific task in a script that you want to run.
I was able to use armhf no problem it worked just fine. I also used multi VNC as my VNC client.
I understand what they did now. I think it would be easier to simply break apart their program to see what all was put into the image, make your own image on your home computer with everything that you want to have. for instance, instead of using Debian Wheezy, you can use a lite version of Debian running fluxbox, with only the apps that you think are good, and nothing else and transfer it over to your tablet. This would make the image very small. I didn't have any trouble at all with the processing power of our tablet. So that won't really be a factor, but space will.
the 1 item I discussed being off in the kernel may very well be the one that needs to be checked in order to use the frame buffer. Or it is also possible that there is only one option that he gives that allows for that and you can see that option when you set everything up. if I remember right, it was under the distribution choices? Anyway, not a very usable or useful beastie at this point is it? I downloaded gimp and Iceweasel just to try a few apps and it pretty much sucked trying to navigate around.
if you can think of some really cool reason to use it, maybe some script or useful app that doesn't require a lot of navigation I might try to build an image with it already together.