please close thread - Touch CDMA General

Development has been integrated with the new rootfs.
Please see the thread here:
http://forum.xda-developers.com/showthread.php?t=584707
New version coming soon:
Version 2.3 info:
-Newer simplified setup, whether you use a partition or not you will use the same files;
- fixed copying issues that were stopping some Donut builds from working. All builds should now work file.
-there are no additional files unlike previous builds.
- support for a data partition as well.
- supports all phones that the rootfs is supporting, kaiser vogue diamond etc.
Version 2.2 info;
updated for better data file backup naming.
updated to support donut
updated to support wifi (thanks enate for this)
Version 2 info;
On boot it will prompt you to boot the new recovery image, if you press a key it will load the recovery image, (the first boot you must do this to install the system) if not it will boot as normal.
If you have a system.sqsh on your sd card it will prompt you to install to your ext2 partition
- after installing the system it will move it to /sdcard/installedsystem/installedsystem.sqsh
- it will move your data file to /sdcard/datafilebackup/data$date
and create a new one. After the inital boot you can reboot and copy back your data file again.
There is one caveat that was pointed out to me today. Do not change systems twice in one day unless you don't care about your data. Because it creates the data file based on date it will overwright the old one.
Why not data to? Well our current data.img solution is awesome for backing it up.
What's coming;
Native support for update.zip's from the dream themes forum.
Menu support with several different usefull options for setting up android (this is proving to be tough but I'm working on it)
here it is!
http://code.google.com/p/vogue-andr...name=recoverfiles2.2.rar&can=2&q=#makechanges

mssmison said:
Hey guys, I've got something new coming for vogue android, I need 2 people with VOGUES's only to test something for me.
Requirements; linux install, vogue only, be able to provide bug reports, be serious!
pm me; I'm hoping to have testing ready by the end of the day.
Click to expand...
Click to collapse
sure
have linux and vogue pmed you. dang, guess i didnt pm you in time...

I don't know what this is, but you've sure got me curious as hell.
If you need another tester, let me know.

Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?

stickus said:
Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?
Click to expand...
Click to collapse
Technically, Android doesnt run "native" on any device. You don't have to port a device to android..just the linux kernel to get api's to work. I know your refering to booting android on our faster but much smaller enternal flash but the speed difference would be minimal and we would be confinded to smaller builds. I think it has to do with a memory limitation in android from the dalvik vm it uses. I'm not 100% sure on what im talking about but this is the impression ive had for android for a while. Please enlighten me if I have missed something..

posting in epic thread

stickus said:
Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?
Click to expand...
Click to collapse
It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards

mssmison said:
It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards
Click to expand...
Click to collapse
Interesting.
I really don't understand why the internal NAND is so slow. Windows Mobile runs just fine from NAND, so why would running Android from it be any different?
Alternatively, it seems that a flashable Android would be much more convenient, and permanent.
I'm very curious to know what you're working on, mssmison.

Shidell said:
Interesting.
I really don't understand why the internal NAND is so slow. Windows Mobile runs just fine from NAND, so why would running Android from it be any different?
Alternatively, it seems that a flashable Android would be much more convenient, and permanent.
I'm very curious to know what you're working on, mssmison.
Click to expand...
Click to collapse
Duel booting would a better option in my opinion..wm is just a better mini PC OS(Windows) and Android is a better phone/internet OS . This makes our devices even more versitle then phones just running android. I dont get how just having android would makes things better..since we just manually boot android instead of it booting once the phones is turned on...how about a linux bootloader that launches before wm does..and a graphical UI to choose from the two OS's

ajclai08 said:
Duel booting would a better option in my opinion..wm is just a better mini PC OS(Windows) and Android is a better phone/internet OS . This makes our devices even more versitle then phones just running android. I dont get how just having android would makes things better..since we just manually boot android instead of it booting once the phones is turned on...how about a linux bootloader that launches before wm does..and a graphical UI to choose from the two OS's
Click to expand...
Click to collapse
My understanding is that there isn't enough room to dual-boot both WinMo and Android from the NAND on the Vogue.
You could possibly put the bootloader in NAND and run WinMo and Android from storage, but that sorta defeats the purpose.

mssmison said:
It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards
Click to expand...
Click to collapse
Sounds delicious.

UHHHHHH
Well this sounds cool, Nice to see that you are back......CANT WAIT......
DROID FOR LIFE

Freezell said:
Well this sounds cool, Nice to see that you are back......CANT WAIT......
DROID FOR LIFE
Click to expand...
Click to collapse
I never left.. I was just working in the background

what's the harm in saying what's being worked on?

bug666 said:
what's the harm in saying what's being worked on?
Click to expand...
Click to collapse
Suspense is just too much fun....?

If all goes well I should have something tomorrow night for everyone.

hintttttttttttt lol

mssmison said:
If all goes well I should have something tomorrow night for everyone.
Click to expand...
Click to collapse
Is it gonna require serious work to do, like flashing a rom? Or still just files on an SDCard, just in a different way?

TheKartus said:
Is it gonna require serious work to do, like flashing a rom? Or still just files on an SDCard, just in a different way?
Click to expand...
Click to collapse
..............

lol, i've been working on stuff in the background too. haha.
but anyways, i was like wtf, this is a total bs thread, then i saw your name everywhere. haha. so i guess it's not.
good to see a vogue developer still around!!
I'm working on getting another one so I can mess with the vogue again. it's a fun phone.

Related

best rom for MT3G 32b?

what is the best rom for the MT3G right now.
I tried cyanogen 3.9.11.2 and seems like it has intermitant problems unlocking the screen were it will blink horizontal lines and then after a few times then unlock fine. Seems to happen more with the device when it is warm
I have also tried both v1.3 jacxrom builds and the full v3 hero and works fine when first booted but when I lock the screen and unlock it looks like the screen is overlayed with another copy of itself but a little to the right. Almost taking one verticle line of pixels and switching it wiht the row next to it in pairs al the way across the screen. Any ideas on which one I should be running.
TheArtiszan said:
what is the best rom for the MT3G right now.
I tried cyanogen 3.9.11.2 and seems like it has intermitant problems unlocking the screen were it will blink horizontal lines and then after a few times then unlock fine. Seems to happen more with the device when it is warm
I have also tried both v1.3 jacxrom builds and the full v3 hero and works fine when first booted but when I lock the screen and unlock it looks like the screen is overlayed with another copy of itself but a little to the right. Almost taking one verticle line of pixels and switching it wiht the row next to it in pairs al the way across the screen. Any ideas on which one I should be running.
Click to expand...
Click to collapse
The new Cyanogen 4.1 that just came out is absolutely amazing. I just flashed it over on my MT3G today and have had no troubles. It's a must have.
http://forum.xda-developers.com/showthread.php?t=537204 Link to the Cyanogen 4.01
tazz9690 said:
The new Cyanogen 4.1 that just came out is absolutely amazing. I just flashed it over on my MT3G today and have had no troubles. It's a must have.
Click to expand...
Click to collapse
Do you have all the tmobile apps that came with the mytouch (myfaves etc...)
Im still trying to decide whether or not to root. I have rooted "jailbroken" my iphone. Is rooting give you the same benefit as jailbraking? I mainly used the jailbreak for denied apps from the app store, themes, and tethering. Tethering is not so important (unless I'm traveling haha)
hypmatize said:
Do you have all the tmobile apps that came with the mytouch (myfaves etc...)
Im still trying to decide whether or not to root. I have rooted "jailbroken" my iphone. Is rooting give you the same benefit as jailbraking? I mainly used the jailbreak for denied apps from the app store, themes, and tethering. Tethering is not so important (unless I'm traveling haha)
Click to expand...
Click to collapse
Same idea and then some. Cyan does not include myFaves in his builds but it can be added. Check the G1 forum where he posts his ROMS. I saw a post about it the other day but can't remember where. Search. When in doubt, ROOOOOOT!!! No other way to use Android IMO.
aaronratner said:
Same idea and then some. Cyan does not include myFaves in his builds but it can be added. Check the G1 forum where he posts his ROMS. I saw a post about it the other day but can't remember where. Search. When in doubt, ROOOOOOT!!! No other way to use Android IMO.
Click to expand...
Click to collapse
So the myfaves app that came with my mytouch ("Magic" I like that name so much better btw mytouch sounds so girly) can't be pushed to me by tmobile. I happened to me once where it completely disappeared from my phone and cs refreshed my myfaves and i got it within 5 min. I guess its not a big deal if I can download it. How about the other apps like youtube, android market; will they work as they would on a non rooted mytouch?
The main thing stopping me from rooting is that I can't return it to the original factory state like I could for my iphone. Not sure how stuff works on android (im still a noob with this OS) but on the iphone it wasn't a big deal to jailbreak as it just modifies just a small part of the OS to allow non apple approved apps/themes etc... but with this its like it flashes a whole different OS. How about all the new updates like donut etc...that we will get ota. I guess the devs here will include all those features in their new ROMs (as they are doing now) so that is not such a big deal.
Thanks for the quick answer btw.
MOD EDIT
Moved to general discussion forum
hypmatize said:
So the myfaves app that came with my mytouch ("Magic" I like that name so much better btw mytouch sounds so girly) can't be pushed to me by tmobile. I happened to me once where it completely disappeared from my phone and cs refreshed my myfaves and i got it within 5 min. I guess its not a big deal if I can download it. How about the other apps like youtube, android market; will they work as they would on a non rooted mytouch?
The main thing stopping me from rooting is that I can't return it to the original factory state like I could for my iphone. Not sure how stuff works on android (im still a noob with this OS) but on the iphone it wasn't a big deal to jailbreak as it just modifies just a small part of the OS to allow non apple approved apps/themes etc... but with this its like it flashes a whole different OS. How about all the new updates like donut etc...that we will get ota. I guess the devs here will include all those features in their new ROMs (as they are doing now) so that is not such a big deal.
Thanks for the quick answer btw.
Click to expand...
Click to collapse
Sorry for not answering your response as quickly as the first answer. I can't speak for the iPhone but the G1/myTouch (I have both) are a MUST root IMO. I think having total control over the phone and OS is so important. As far as Market, YouTube, etc. they all work. Every app works, as far as I am concerned and I have 225 apps (all paid for if they weren't free) installed. As far as updates are concerned, the devs here are months ahead of Google and TMO. Cyanogen (best ROMs here, IMO, if you aren't into Hero and things like that) already has some Donut stuff in his stable 4.0.1 ROM and adds quite a bit of cool features in his experimental ROMs. You can also add bits from other devs if Cyan doesn't include something you like. Cyan does not include myFaves (I forget why) but it can be added after. Just search around for that. Even without the app on your phone, you can always update them online and still make free calls to your faves. It just won't show on the phone, that is unless you have the "after market" app installed. Hope this helps. And like I said, root is absolutely the way to go. Nothing frightening. In fact, I feel more comfortable with tools like Nandroid built-in so I can always restore my phone if/when I mess something up or install and unstable ROM/theme. I flash almost daily for that reason.
aaronratner said:
Sorry for not answering your response as quickly as the first answer. I can't speak for the iPhone but the G1/myTouch (I have both) are a MUST root IMO. I think having total control over the phone and OS is so important. As far as Market, YouTube, etc. they all work. Every app works, as far as I am concerned and I have 225 apps (all paid for if they weren't free) installed. As far as updates are concerned, the devs here are months ahead of Google and TMO. Cyanogen (best ROMs here, IMO, if you aren't into Hero and things like that) already has some Donut stuff in his stable 4.0.1 ROM and adds quite a bit of cool features in his experimental ROMs. You can also add bits from other devs if Cyan doesn't include something you like. Cyan does not include myFaves (I forget why) but it can be added after. Just search around for that. Even without the app on your phone, you can always update them online and still make free calls to your faves. It just won't show on the phone, that is unless you have the "after market" app installed. Hope this helps. And like I said, root is absolutely the way to go. Nothing frightening. In fact, I feel more comfortable with tools like Nandroid built-in so I can always restore my phone if/when I mess something up or install and unstable ROM/theme. I flash almost daily for that reason.
Click to expand...
Click to collapse
wow dude you have been a lot of help, I feel a lot more about rooting now (wow you flash almost everyday haha awesome). I think I'm gonna try it tonight haha.
So I wont need to restore to the original shipped state if I ever need to do a warranty claim?
oh yeah so should I flash cyanogen 3.9.X.X or 4.0.1 ( I know 3.9.X.X has some donunt features but its experimental...but is it better?)
so far JACxHero is my fav rom
mykenyc said:
so far JACxHero is my fav rom
Click to expand...
Click to collapse
really is there a main/any difference between the 2?
i've used cyanogen and its amazing rom but i don't know if its me but JACxHero seems waay more smooth and faster...
and the crazy part is im using a class 2 sd i can only imagine using class 6
mykenyc said:
i've used cyanogen and its amazing rom but i don't know if its me but JACxHero seems waay more smooth and faster...
and the crazy part is im using a class 2 sd i can only imagine using class 6
Click to expand...
Click to collapse
So it looks like sense ui from the hero? I heard all those roms are slow due to the ram limitation on the mytouch (192mb) vs the hero (288mb)
btw I have a class 2 card too as of right now so that is good to know
JACxHero is not a hero port its a regular cupcake with hero type theme and htc music port try it out have nothing to lose really
mykenyc said:
JACxHero is not a hero port its a regular cupcake with hero type theme and htc music port try it out have nothing to lose really
Click to expand...
Click to collapse
Yeah I think I will since it is pretty safe to do (especially since aaronranter flashes everyday it has to be lol)
hypmatize said:
Yeah I think I will since it is pretty safe to do (especially since aaronranter flashes everyday it has to be lol)
Click to expand...
Click to collapse
i have too trust me i went through 8 roms already went right back to JACxHero
mykenyc said:
i have too trust me i went through 8 roms already went right back to JACxHero
Click to expand...
Click to collapse
WOW lol
So to flash it all I have to do it to do the 1 click root method and flash that rom? (not sure where to get it btw)
How about when i want to change roms what do I do?
do I do a nandroid backup every time i switch roms?
hypmatize said:
WOW lol
So to flash it all I have to do it to do the 1 click root method and flash that rom? (not sure where to get it btw)
How about when i want to change roms what do I do?
do I do a nandroid backup every time i switch roms?
Click to expand...
Click to collapse
I am a noob, but if you use search option you will find out that JacHero needs latest Radio and SPL which is 2005. One click method doesnt change it. I still have 2006, "perfect".
you can always use the old method just follow the instructions step by step don't feel discourage ... but you must and i repeat follow each step ... one... by ..one
schtuka said:
I am a noob, but if you use search option you will find out that JacHero needs latest Radio and SPL which is 2005. One click method doesnt change it. I still have 2006, "perfect".
Click to expand...
Click to collapse
Ah thanks for the info. I think i'll flash with cyanogen's rom since I currently don't have another micro sd card to do the old method

Cyanogen 6 on HTC Dream - Things to avoid?

Hey guys,
Just modded my HTC Dream with CM6, and it seems pretty cool.
I read somewhere that you should partition the SD card? Something about ext2 to ext3? Can anyone comment on that?
Also, read that you need to be careful installing themes because it could brick the phone? Does that mean full themes, not just wallpapers?
Anything else I should be cautious of?
Thank you in advance
damien8 said:
Hey guys,
Just modded my HTC Dream with CM6, and it seems pretty cool.
I read somewhere that you should partition the SD card? Something about ext2 to ext3? Can anyone comment on that?
Also, read that you need to be careful installing themes because it could brick the phone? Does that mean full themes, not just wallpapers?
Anything else I should be cautious of?
Thank you in advance
Click to expand...
Click to collapse
ext2 is optimal for this application. ext3 will just wear out your card faster. You don't necessarily need an ext partition on the card though -- only if you want to install applications to the sdcard without using that horrible froyo2sd nonsense that google added.
Themes won't brick the phone unless they overwrite things that they most definitely have NO REASON to be overwriting. Having said that, EVERY theme is horribly ugly compared to how it looks without messing with it. JUST LEAVE IT ALONE!
lbcoder said:
ext2 is optimal for this application. ext3 will just wear out your card faster. You don't necessarily need an ext partition on the card though -- only if you want to install applications to the sdcard without using that horrible froyo2sd nonsense that google added.
Themes won't brick the phone unless they overwrite things that they most definitely have NO REASON to be overwriting. Having said that, EVERY theme is horribly ugly compared to how it looks without messing with it. JUST LEAVE IT ALONE!
Click to expand...
Click to collapse
Thanks for the reply!
I'm having a problem with Google Navigation. Seems that when I turn it on, it just freezes at the "searching for GPS" screen.
I also have a problem with Goggles (downloaded it from Market). It starts up, goes through the tutorial, and then when I advance to start it, it just hangs.
Any ideas?
Thanks again
damien8 said:
Thanks for the reply!
I'm having a problem with Google Navigation. Seems that when I turn it on, it just freezes at the "searching for GPS" screen.
I also have a problem with Goggles (downloaded it from Market). It starts up, goes through the tutorial, and then when I advance to start it, it just hangs.
Any ideas?
Thanks again
Click to expand...
Click to collapse
Don't forget that you're playing with CM. Not exactly a stable setup.
lbcoder said:
Don't forget that you're playing with CM. Not exactly a stable setup.
Click to expand...
Click to collapse
Does anyone have Navigation running smoothly on a G1/Dream?
"Cyanogen 6 on HTC Dream - Things to avoid?"
Cyanogen 6 on HTC Dream
jubeh said:
"Cyanogen 6 on HTC Dream - Things to avoid?"
Cyanogen 6 on HTC Dream
Click to expand...
Click to collapse
I was about to say 'turning it on', but I like yours too.
May I ask, why this is your opinion? I use CM6 on my Dream.
jdb78 said:
May I ask, why this is your opinion? I use CM6 on my Dream.
Click to expand...
Click to collapse
Because it is a memory hog, unstable, and slow. They're trying to please everyone with ever nonsense request, and it really has bloated into a monster. The tmobile magic 32b froyo image (as converted for DREAM) is an excellent 2.2 build, extremely fast and stable. Just tweak to suit.
Hi,
I'm sorry I am brand new to all of this, just yesterday I rooted my g1 (first time) and installed CM6. I like it but it is running a bit slow and I am having a few issues with 3g.
If CM6 isnt all that great, could you link me to a good rom/setup please (preferably with installation instructions)? I was trying to find what is good at this point but for 2 hours now can not figure out which rom to get at this date. Is zx donut v3.0 a good candidate? Its been popping up a lot
p.s. I am getting a g2 in 2 weeks and passing this phone to a friend, wanna give him the best setup possible,
Thanks for your time
Edit -just installed Super F 1.0 from here: http://forum.xda-developers.com/showthread.php?t=799693, seems to be a lot faster than CM6, op might wanna give it a shot It is definitely not as good looking as CM, also few of CM features that were nice are missing, but it seems to run much better so far!
But if you guys can suggest something better (doesn't have to be froyo) I'd appreciate it
I appreciate your answer. Well, to be honest I am not 100% satisfied with how CM6 runs on my G1/dream. I thought I configured it wrong. I agree with the poster iokke, I'd like to know which setup still runs smooth on the dream. I need a usable and reliable phone. Sure. the features of CM6 are really nice but what price to pay for it?
to the op:
try this rom, it was updatied in October of this year, just installed it, but so far is running fine on my phone, and its froyo + has themes (you can find them from the installation page link)
http://forum.xda-developers.com/showthread.php?t=745478
A cool thing about these ROM (given that I am a noob) - my g1 seems to be running on the H network now without me having to do anything
Another mod worth looking at, that I have not tried so far, also updated last month is the Sparksmod 1.4, you can find it here:
http://forum.xda-developers.com/showthread.php?t=753893
Not sure which one of the two is faster, though I read somewhere that the Sparksmod is the faster one. This is also froyo, but havent tried this one yet
iokke said:
to the op:
try this rom, it was updatied in October of this year, just installed it, but so far is running fine on my phone, and its froyo + has themes (you can find them from the installation page link)
http://forum.xda-developers.com/showthread.php?t=745478
A cool thing about these ROM (given that I am a noob) - my g1 seems to be running on the H network now without me having to do anything
Another mod worth looking at, that I have not tried so far, also updated last month is the Sparksmod 1.4, you can find it here:
http://forum.xda-developers.com/showthread.php?t=753893
Not sure which one of the two is faster, though I read somewhere that the Sparksmod is the faster one. This is also froyo, but havent tried this one yet
Click to expand...
Click to collapse
The H icon is a cosmetic tweak, that was put into CM6 or 6.1 onwards, your phone has been accessing the same speeds before, it just wasn't doing the icon change when it went to the higher speeds.
I have always had trouble and lagginess with 2.2 on my G1, even after a full system wipe, so I'm rockin 5.0.8 at the moment, and it flies. I just miss custom LED notifications, though I have yet to try the official TMO 2.2.
If you make nandroid backups from recovery, you should have no fear if you want to mess around with different roms or flashing themes .
Thanks, time to go read nandroid backup for noobs))
One question, with Danger SPL installed for Froyo ROMs, can I go back to donut ROMs and simply flash them, or should I remove it somehow??
iokke said:
Thanks, time to go read nandroid backup for noobs))
One question, with Danger SPL installed for Froyo ROMs, can I go back to donut ROMs and simply flash them, or should I remove it somehow??
Click to expand...
Click to collapse
I'm pretty sure you won't have to change the SPL anymore except for very special roms. Just make sure you do a full wipe from recovery after a backup, for new roms to ensure that there aren't any lingering problems.
I have been really enjoying EZTerrys new kernel with biffmod. fast. seems to be stable. LOTS of features (Overclock added =]). i was restarting my phone 3 times a day on CM6 and now once in the morning is ok for the whole day. also, when i used super F, the camera didnt work.
timekeeper said:
I'm pretty sure you won't have to change the SPL anymore except for very special roms. Just make sure you do a full wipe from recovery after a backup, for new roms to ensure that there aren't any lingering problems.
Click to expand...
Click to collapse
Ty, I'm flashing Froyo 2.2.1 for T-Mobile G1 " Froyo for Trout right now to see how it goes, but I will also try the EZ Terry

What is really nand?

I will be able to run any build on from nand or it will be like a new two build sense and non sense, somebody enlightme pls ( N-00B i Know)
You'll be able to boot android without windows mobile
startekee said:
You'll be able to boot android with windows mobile
Click to expand...
Click to collapse
withOUT
DN41
Mda, that's what everybody know but how ? we will have android on internal memory? SOmebody cand describe some steps please ?
Only the team in charge of the project and their beta members have all the steps but essentially all parts of windows mobile will be removed aside from perhaps the basic splash and startup files, those will then boot directly into windows. This should cause less battery consumption as well as eliminate screen freezes and the other errors that plague us.
DN41 said:
withOUT
DN41
Click to expand...
Click to collapse
Yeah, thanks for the correction
Guys. Can you tell me is there any complete Android ROM for our hd2? I mean android without Linux...
Sorry for offtop.
Sorry for my bad English..
Sent from my HTC HD2 using XDA App
Android is built with linux so no, there is no possible way that any android phone will work without linux. If you're annoyed by that little 3 second pop-up where you actually see the linux booting then you're being too anal about it. I'm currently using HTCClays SuperHD2 found HERE and it runs with minimal screenfreezes and a great battery life. I personally believe it's the closest we have to a perfect rom currently.
z33dev33l said:
Only the team in charge of the project and their beta members have all the steps but essentially all parts of windows mobile will be removed aside from perhaps the basic splash and startup files, those will then boot directly into windows. This should cause less battery consumption as well as eliminate screen freezes and the other errors that plague us.
Click to expand...
Click to collapse
i suppose you mean android
yeah, one day ill remember to sleep xD

[UPDATE 7/24][ROM][BL1.2] Honeycomb Android Illuminate for The Gtablet\Zpad T2

Mod Edit: As stated by forum moderator jerdog in post 814:
FORUM RULES:
"Encouraging members to participate in forum activities on other phone related sites is prohibited."
The issue here is that directing traffic elsewhere is against XDA rules, and while there is no requirement to actively support your development efforts here at XDA, saying it probably won't be supported at XDA and that they can get support on your forum is kind of low and has been removed after requesting LBS do so - to which he did not after 2 days.
Click to expand...
Click to collapse
Thread closed.
will test this one. thanks
on v1.6
update 6.20.2011
~watching youtube on app and in browser are hit or miss, you should work on it to be more compatible
~so far so good though, thanks
update 6.21
~facebook FC's
will update this when i find more problems, when i find more time
ninditsu said:
will test this one. thanks
Click to expand...
Click to collapse
cool let me know what you think so far and if you let me know what the things are you missing the most and really need besides Flash. LOL but yeah I want to make this a Honeycomb that is a well rounded Android. So i want the advice of new features and such they have heard about.
Checked out the youtube video, looks pretty sweet. Will try it out tomorrow to see the improvements with hardware acceleration etc.
Edit: Let's see some benchmark comparisons between BoS and Illuminate.
Make sure you do the following
Unzip recover.zip and move recovery folder to /sdcard folder
The recover.zip file can be found in the Roebeets thread
http://forum.xda-developers.com/showthread.php?t=1078897
Regards,
Kenny N
Humm -- I got stuck with the boot loop . I am updating from 3588 stock recovery
Regards,
Kenny N
After half an hour struggling, I am able to load your HoneyComb edition. I am going to play around with it.
To make everyone's life easier.
Make sure you nvflash your device first using the following nvflash image
http://www.mediafire.com/?g7vorg66iiq29vm
1. Download the nvflash image above.
2. Download the recover.zip from (http://forum.xda-developers.com/attachment.php?attachmentid=596319&d=1305415712 ) and extract the recovery folder to SD root
3. Download this honeycomb image and rename it to update.zip and copy it to your SD root
4. nvflash the nvflash image
5. Reboot with Power + Volumn up. This should bring you to the new bootloader
6. Flash the SDCard external update.zip
7. Wipes
9. Restart
G'd luck . Thanks linuxboxsolution for his contribution. I will comment later.
Nice -- OpenGL is working perfectly. The benchmark from Quandrant is 1780. Not great but can't really complain
linuxboxsolution said:
Last Update 6/6/2011​
NOTICE: Flash still not currently Working please see
Click to expand...
Click to collapse
That's funny, I could have sworn you claimed previously to have "fixed flash" too!
Does enabling OpenGL break the stock browser? Or have you done something to work around this issue?
Is the main difference from Roebeet's HCAdam and Vegacomb mashup that is Bottle of Smoke that you have enabled opengl?
This looks very promising, currently running BoS 3.3 and was about to jump to 4.1 but I might have to try this first. My apologies if this has already been covered but what exactly is the difference between this ROM and roe's BoS? How were you able to get hw acceleration on here while BoS lacks it?
Thanks alot for your contribution, and I'll be sure to post my findings later today.
just wondering
so if the opengl is fixed, how come flashed is still hasnt fixed?
i believ robeet said the opengl is what makes flash doesn't work
OpenGL is enabled but not working.. it lacks on driver and without flash no OPENGL.. note on that..
and one more thing.. BoS has HWaccel and working, like gingerbread... the only problem is video HWaccel HD playback..
BoS 3.3 or 4.0+ boot quickly too, smooth UI like that, so i can't really tell what's the difference between the two, except for bootanimation.. LOL
I, for one, appreciate your efforts
Going to start posting in XDA's GTAB forums, at least sporadically. I think enough time has passed and things have changed around here (ie a lot of 1.2 mods are popping up, which I think is a good thing). Plus I'm not really seeing the moderator "changes" that were heavily present in April. So maybe things are back to normal. Maybe.
With that in mind, I wanted to say that your efforts are much appreciated - the end goal is to get a good working HC ROM for the users out there and if you have the ear of some people to make that happen, then that's what counts. I already mentioned in Slatedroid that I plan to pull back a bit after this month with modding the GTAB, so any extra dev / modding work is ALWAYS appreciated, imo.
Thanks again.
Looks awesome, will flash once I get my new PC built >
Thanks roe
So first of all thank you for your work.
But this is different from bottle of smoke because it enables OpenGL right?
Any other changes?
I hate to be a Richard but, can we get some screenies fam?
cgingermany said:
I hate to be a Richard but, can we get some screenies fam?
Click to expand...
Click to collapse
Not quite sure what that means, but if you want to see what it looks like, you can watch the youtube preview. It's at the bottom of the OP or here.
cgingermany said:
I hate to be a Richard but, can we get some screenies fam?
Click to expand...
Click to collapse
Rich, there is an almost 9 minute video in the first post.

ROM development, based on Eclair/Froyo anyone?

Hey
I've recently got my NST and, after TouchNootering it, I reverted it back to stock and manually rooted & installed stuff on it. I managed to install latest busybox too (1.19.1), even better than what TouchNooter installs.
Anyways, I've been wondering if anybody here is up to the challenge of making a ROM for this device. Modifying the actual ROM is nice... but it's buggy and it feels sloppy at times, not to mention it semi-works. Some features do, some don't.
I think, that if we make it possible to run a basic Eclair ROM, we can move to Froyo and maybe then, with enough experience and all, get GB or ICS installed on it. I think it's -very- possible... it just needs to be put some work on
Anyone?
Two issues: Drivers and memory. Unless drivers are available for the version of Android you want to build, you're going to have a tough time. Unless B&N releases a newer version of Android for the NST, this is probably unlikely. I suspect we're stuck on 2.1 eclair.
The NST only has 256M of memory, so a lot of what works on other devices is going to have to trimmed down.
This isn't to say that it can't be done, but by the time you're done, it may not be so much better than what we've got. Anything is possible, of course, but I'm not aware of anything along the lines of CyanogenMod in the works for the NST. I'd be happy to be wrong.
In the meantime, there's no reason improved software can't be written to run on what we've got. At least rooting makes that possible.
bobstro said:
Two issues: Drivers and memory. Unless drivers are available for the version of Android you want to build, you're going to have a tough time. Unless B&N releases a newer version of Android for the NST, this is probably unlikely. I suspect we're stuck on 2.1 eclair.
The NST only has 256M of memory, so a lot of what works on other devices is going to have to trimmed down.
This isn't to say that it can't be done, but by the time you're done, it may not be so much better than what we've got. Anything is possible, of course, but I'm not aware of anything along the lines of CyanogenMod in the works for the NST. I'd be happy to be wrong.
In the meantime, there's no reason improved software can't be written to run on what we've got. At least rooting makes that possible.
Click to expand...
Click to collapse
Hey
Well, yes, there's the issue with drivers. Thing is, and I might be wrong at this, that a driver can be kept in newer versions and still be used. For example, in HTC Magic, the video driver hasn't been updated in *ages*, and the little device can even run ICS now. Froyo, Donut & Gingerbread both use almost the same driver versions and it hasn't had any issues so far. I'm using my own experience as base on this though.
About the memory, again experience, HTC Magic has like 512 Mb ROM and 256 Mb RAM. The NST has 256 MB RAM and 2GB ROM. I find it very possible.
Thing is, I'm not very satisfied with "what we've got". See, I bought it planning to use it as a tablet instead, since... I rarely read, lol. So far so good, I can VNC/TeamView to computers at work and my computer at home, take notes and even browse the web (well, kiiiinda...), but it's buggy as hell. I mean, the rooters we have are pretty good at what they do, but the OS itself, the way B&N built it, it's broken.
See, LatinIME doesn't work correctly or is almost impossible to use with Dolphin (or any other browser) because they also broke WebCore =/. Not to mention the colors are a bit off since it's all B&W and some texts are in the same color as the background (thanks to their Framework.res theme) so...
Taking that into account, I wanted to give a go at a ROM instead, since there isn't any ROM for this device yet, and considering we have CWM working, I find it very possible to compile a ROM and use it, or hell, at least have a pure Android OS booting.
I've made some research here:
http://elinux.org/Android_on_OMAP
http://www.omappedia.org/wiki/Android_Getting_Started#Video_Tutorials
https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Compile_CyanogenMod_(Linux)
And I think it's very possible to build a ROM, using the first two links + the tutorial at google docs. Also, it seems that some procedures, tools or code made for the Nook Color are also able to be used for the NST, since they share almost the same exact hardware.
However, I'm confused on how to start. This is my first time building an Android ROM after some few failed attempts at an HTC Magic ROM, though the instructions seem to be waaaay easier than HTC's. Right now I'm downloading Ubuntu Server 11.10 x64 so I can set up a simple OpenBox environment and start pulling code... but it's confusing
I'm up for the challenge, and I'm trying to work on it, but I'm no genius and I feel that if there's more than one person working on this, we can take a ROM out which would be better than the stock ROM and would have better and cooler stuff, like USB Host Mode already included or the refresh rate fixed/faster. Hell, I even restored it to factory defaults and then rooted it manually and installed BusyBox 1.19.1 in it, something which isn't mentioned in any tutorial that I've found yet.
darkguy2008 said:
Hey
Well, yes, there's the issue with drivers. Thing is, and I might be wrong at this, that a driver can be kept in newer versions and still be used. For example, in HTC Magic, the video driver hasn't been updated in *ages*, and the little device can even run ICS now. Froyo, Donut & Gingerbread both use almost the same driver versions and it hasn't had any issues so far. I'm using my own experience as base on this though.
Click to expand...
Click to collapse
The issue with drivers isn't so much it being old, it's getting a driver for the E-Ink screen. It's like video cards; you can put any driver you want on any computer, but unless it's the right one, you'll be stuck at 640x480 (or in the case of Android, no display).
darkguy2008 said:
About the memory, again experience, HTC Magic has like 512 Mb ROM and 256 Mb RAM. The NST has 256 MB RAM and 2GB ROM. I find it very possible.
Click to expand...
Click to collapse
It's not ROM, it's flash storage or whatever the correct term. ROM (read-only-memory) cannot be written to, and the flash storage is just storage space.
darkguy2008 said:
See, LatinIME doesn't work correctly or is almost impossible to use with Dolphin (or any other browser) because they also broke WebCore =/. Not to mention the colors are a bit off since it's all B&W and some texts are in the same color as the background (thanks to their Framework.res theme) so...
Click to expand...
Click to collapse
WebKit could probably be fixed eventually, and fixing the framework-res.apk shouldn't be too difficult, just unpack the thing with apktool and grab notepad++ or something.
darkguy2008 said:
Taking that into account, I wanted to give a go at a ROM instead, since there isn't any ROM for this device yet, and considering we have CWM working, I find it very possible to compile a ROM and use it, or hell, at least have a pure Android OS booting.
Click to expand...
Click to collapse
If we had CWM working, would this thread exist? Yes, it's working on the Nook Color, but getting it to work on the NST would require removing so many things and so much more, and even when it does happen it'd probably be a hollow shell of what it normally is.
darkguy2008 said:
I'm up for the challenge, and I'm trying to work on it, but I'm no genius and I feel that if there's more than one person working on this, we can take a ROM out which would be better than the stock ROM and would have better and cooler stuff, like USB Host Mode already included or the refresh rate fixed/faster. Hell, I even restored it to factory defaults and then rooted it manually and installed BusyBox 1.19.1 in it, something which isn't mentioned in any tutorial that I've found yet.
Click to expand...
Click to collapse
I didn't mean to put you down by all this or flame you, so hey, good luck!
Googie2149 said:
The issue with drivers isn't so much it being old, it's getting a driver for the E-Ink screen. It's like video cards; you can put any driver you want on any computer, but unless it's the right one, you'll be stuck at 640x480 (or in the case of Android, no display).
Click to expand...
Click to collapse
Hmm, you're right. I have the idea of using Eclair's drivers included in the B&N update files (1.1.2), I dunno how to use them but if the .so file exists, there must be a way to invoke their methods, no? It's just a theory, I kinda suck at this thing of kernel drivers 'n stuff.
Googie2149 said:
It's not ROM, it's flash storage or whatever the correct term. ROM (read-only-memory) cannot be written to, and the flash storage is just storage space.
Click to expand...
Click to collapse
Oh okay, then I can't seem to find any official specs of how much RAM does the NST have =/. Pretty weird.
Googie2149 said:
WebKit could probably be fixed eventually, and fixing the framework-res.apk shouldn't be too difficult, just unpack the thing with apktool and grab notepad++ or something.
Click to expand...
Click to collapse
Yeah, I have an idea of trying to fix that APK, but I wanted something more... Android-ish xD.
Googie2149 said:
f we had CWM working, would this thread exist? Yes, it's working on the Nook Color, but getting it to work on the NST would require removing so many things and so much more, and even when it does happen it'd probably be a hollow shell of what it normally is.
Click to expand...
Click to collapse
Actually, we -have- CWM working in the NST, just look here -> http://forum.xda-developers.com/showthread.php?t=1360994 . If a recovery was made possible in NST, which means some ROM (or whatever) compiling to display and use the hardware buttons, I'm very sure it is possible to build an Android ROM the same way o.o...
Googie2149 said:
I didn't mean to put you down by all this or flame you, so hey, good luck!
Click to expand...
Click to collapse
Hehe, it's okay, didn't take it as that, so, thanks
---
On another news, I followed this tutorial: http://www.omappedia.org/wiki/Android_Getting_Started up to the "repo sync" stage. It says it should take an hour and all, but it doesn't. It takes like 5 seconds, no output, nada. I don't know what could be wrong
Any help?
darkguy2008 said:
I can't seem to find any official specs of how much RAM does the NST have =/.
Click to expand...
Click to collapse
> adb shell
$ busybox free -m
Learn to love the command line.
darkguy2008 said:
Actually, we -have- CWM working in the NST, just look here -> http://forum.xda-developers.com/showthread.php?t=1360994 . If a recovery was made possible in NST, which means some ROM (or whatever) compiling to display and use the hardware buttons, I'm very sure it is possible to build an Android ROM the same way o.o...
Click to expand...
Click to collapse
Derp, I thought you were talking about Cyanogenmod for some reason.
notriddle said:
> adb shell
$ busybox free -m
Learn to love the command line.
Click to expand...
Click to collapse
Hey, I love the command line I -have- to ... Anyways, didn't thought of that first, so thanks
According to this:
Code:
total used free shared buffers
Mem: 227 212 14 0 8
-/+ buffers: 204 23
Swap: 0 0 0
The device only has 256 Mb RAM? I find it enough up to ICS. My previous HTC Magic could run ICS quite happily even without hardware acceleration, Froyo ran as fast as the stock 1.5 ROM and Gingerbread ran pretty okay. I didn't have the chance to work on optimizing it because my Magic got stolen, but I bet it could've been made to work as fast as the stock ROM if correctly optimized. Taking that into account, I'm sure this device can withstand a greater android version .
Googie2149 said:
Derp, I thought you were talking about Cyanogenmod for some reason.
Click to expand...
Click to collapse
Lol, nah XD. It it would be cool if it worked but nah, those guys prefer the most powerful devices :/ sucks though.
Okay, according to this wiki: http://wiki.samat.org/Nook ... NST's source code is here (for 1.1):
http://images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1-1.tgz
Anybody have an idea on how to compile it though? it doesn't seem complete to me.
Look here : http://forum.xda-developers.com/showthread.php?t=1290524
mdall said:
Look here : http://forum.xda-developers.com/showthread.php?t=1290524
Click to expand...
Click to collapse
That doesn't make any sense, that's for compiling a Kernel... this source code is for a whole ROM (it seems)... it has the kernel, u-boot, x-loader and some android source.
---
EDIT:
Actually... it makes sense now (after reading the whole thread, of course)... I'll see what I can do. Thanks for the link
I think radical changes of the Android version is too much to expect.
There's not a lot of ram on the Nook.
However, I just read that one of the big differences between 2.1 and 2.2
is that big changes were made to the Dalvik VM which sped it up 2X to 5X.
I think that that would be a worthy goal.
Renate NST said:
There's not a lot of ram on the Nook.
Click to expand...
Click to collapse
We won't know if nobody tries. Besides, GB has been ported to phones with less. (HTC Magic, as he already mentioned)
However, I just read that one of the big differences between 2.1 and 2.2
is that big changes were made to the Dalvik VM which sped it up 2X to 5X.
I think that that would be a worthy goal.
Click to expand...
Click to collapse
That would be awesome for stock users, but what about those apps that break under the hackish stock ROM? (ColorNote Sync, for example) Or things like NoRefresh that could take advantage of the underlying system's knowledge.
I think working around CM sources, like someone already has posted about trying, is a good idea.
CM9 might be a bit much, but CM7 is well in the device's range.
After all, it runs a CPU like my Motorola Defy, which runs CM9 without hassle (now with HWUI). It has 512MB ram though.
Look here: http://forum.xda-developers.com/showthread.php?t=1684782
imachine said:
I think working around CM sources, like someone already has posted about trying, is a good idea.
CM9 might be a bit much, but CM7 is well in the device's range.
After all, it runs a CPU like my Motorola Defy, which runs CM9 without hassle (now with HWUI). It has 512MB ram though.
Look here: http://forum.xda-developers.com/showthread.php?t=1684782
Click to expand...
Click to collapse
This thread is over a month old, and the thread specifically about CM7 is about 3 days old. But either way, I think that the NST can handle CM. The screen refresh may make it seem slow, but it actually is a little powerful (but seeing as it was my first Android device, and my only other one is a Nook Color, it might actually be as terrible as others say).

Categories

Resources