Database Develop

Is Froyo (FRF50) official - or just an "accident"?

I have updated my stock 2.1 N1 to Froyo (Build FRF50) manually. I'm wondering, though, if this release is really meant to be the official, final Google-supported update.
Is there any word from Google (except for MG Siegler's "The roll out to Nexus One devices has begun!" over at Seeking Alpha) that this is the one?

Same question here. Also if this turns out to be a pre released update, can the stock N1 be updated to a official version?

from what i understand there is no actual official word. That said im loving froyo: As with previous updates, froyo added features and bug fixes and also brought some new issues, so if you are thinking maybe its not official because of some bugs, to me that wouldnt be sufficient evidence: I havent experienced any of the complaints save one- Anyone else having the phone randomly go to sleep and not wake up?
The scrolling,
updated native apps (youtube is amazing now),
overall speed increase,
awesome camera/camcorder updates,
very smooth BETA flash,
simple and effective tethering,
fantastic new setting options throughout the OS,
left AND right rotating
updated UI (love the phone/app drawr/ browser buttons)
and im sure im forgetting stuff...All extremely awesome features and my personal new issues of freezing and hard sleep i can live with i just hope they arent harmful.

i't doesn't feel like a complete FroYo. I have little bugs that i noticed. screen goes black and don't go on anymore, have to take out battery. When the phone is in the charger and i'm playing with it, It gets really really hot.
The new features are great i miss some CM tweaks The UI was a little different at the IO so maybe there will be more surprises?

this was a prerelease to the developer holiday phone the official is coming out around the 29th of may and will continue to roll out till all nexus ones have the update

jdmoore81 said:
this was a prerelease to the developer holiday phone the official is coming out around the 29th of may and will continue to roll out till all nexus ones have the update
Click to expand...
Click to collapse
How do you know this? also will we get that update too?

Well the "leaked" URL was pulled, wasn't it?

this was very likely to be a pre test release. I've looked into the build.prop and there are signs that it is a test release as the word test appears several times throughout.

Given the silence from Google, and the subsequent removal of the link, I suspect this was an accident... meant it to go to a select few whilst forgetting how easy it was to distribute the location of the update.zip.

Wouldn't bother me any if this was the official ... its flawless for me. No freezes or any wierd stuff. Pure froyoness

m00moo said:
this was very likely to be a pre test release. I've looked into the build.prop and there are signs that it is a test release as the word test appears several times throughout.
Click to expand...
Click to collapse
Thnx for the info, so this is a test version. felt that way
Rusty! said:
Given the silence from Google, and the subsequent removal of the link, I suspect this was an accident... meant it to go to a select few whilst forgetting how easy it was to distribute the location of the update.zip.
Click to expand...
Click to collapse
So the link is gone than it's definitely a accident.

I'm gonna say this ain't the final release. But I doubt it'll be any diff. How much more could they fix or improve from the accidental release to the real one.... I bet the same bugs people are seeing now will be present in the final...
Nothing's perfect
Except for me.lol no issues

oh dear... not so good if this is true!
I spose people on here flashed the update.zips from xda?
Hopefully Google will push out the live update now certainly with the potential problems people could be getting

No, I flashed with the file direct from Google before the link was pulled.

So it's all over the news Nexus has froyo now but has anyone with a legit locked stock phone actually gotten it? Like one of the ATT folks?
Anyone have any links to some real clarification on this?

No stock AT&T/Vodafone customer can get it yet.

Zenoran said:
So it's all over the news Nexus has froyo now but has anyone with a legit locked stock phone actually gotten it? Like one of the ATT folks?
Anyone have any links to some real clarification on this?
Click to expand...
Click to collapse
No, I am one of the many AT&T folks that is still waiting for the official release from Google. I have a 3 week old N1 that is still stock and with locked boot loader, and I have no problems waiting, as I am not ready to root my new N1 just yet.

the official will we the frf86 as seen in a couple threads this version will work fine for the holiday version of the nexus one . i tried it on both the holiday nexus one and the official release of the nexus one and it runs better for some reason on the holiday version

Where are you getting all the info from?
Is there likely to be much added between FRF50 and FRF86?

How SO we know if its a holiday one?

[ROM] Final Froyo Release for Obsidian by CCRoms V2.02 Next Up Gingerbread

Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.

sniffle said:
Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
Click to expand...
Click to collapse
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?

Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?

avlfive said:
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
Click to expand...
Click to collapse
No they are not. It shows all the known issues from the dl link posted above

bravo1234 said:
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Click to expand...
Click to collapse
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.

joebob296 said:
No they are not. It shows all the known issues from the dl link posted above
Click to expand...
Click to collapse
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.

avlfive said:
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
Click to expand...
Click to collapse
Those are all a must for me at least
Sent from my DROIDX using XDA App

I don't understand the gps issue or the camera issue. If there was fine GPS and a camera i would love the fact it is AOSP however not that i use them all that often but if i loaded it i would inevitably need one or both. and its still beta if you can't get a totally stable and working froyo rom how will you ever get the GB stable. Will the kexec(?) be used to use custom kernels to make the gps and camera work?

I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App

Funnyface19 said:
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
same here. it's been reported in other obsidian forums too. i was able to get around it by using an older version of market. i installed cm gapps instead of obsidian gapps. The cm gapps had a version of market from 2 month ago. everything worked fine. then i updated my market to 2.2.11 and the "There's not enough room..." error message was right back again.
other than that, i really love how clean and fast this rom is. thanks a ton cvpcs and best of luck with the cyanogenmod team.

any pics of the drop down toggles???

tttuning said:
any pics of the drop down toggles???
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=RbKJy6MPUz0

cvpcs said:
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
Click to expand...
Click to collapse
what...? What!? That is completely wrong... Nothing says you have to upgrade the kernel... unless Gingerbread uses modules not currently in the present kernel, which I can pretty much guarantee it will... Your statement could hold true for something such as minor update like 2.2 to 2.2.1 as we saw earlier, but would very like cause many things to not work come gingerbread. A good example is the previous hacked upgrades of 2.1 to 2.2 back before the proper kernels were released (specifically in memory of the HTC Incredible) sure, 2.2 could run without the proper kernel, of course your WiFi wouldn't work, GPS didn't work, if you tried to run the 720p camera it would crash, as well as several others that I cannot remember as of this moment. The kernel is not "just a low level piece of software" it is the backbone of your entire system, especially when it comes to the system talking with the hardware itself.

I think Taco that you should reread CVPS post. It stated this...
"nothing says that when you upgrade an android version you MUST upgrade the kernel as well"
Which is what you said was wrong, then said the same thing following it.

So how is the rom working for everyone? or it's pretty much dead..

ram130 said:
So how is the rom working for everyone? or it's pretty much dead..
Click to expand...
Click to collapse
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.

JagoX said:
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
Click to expand...
Click to collapse
Well that sucks ..development on this phone is so slow..

The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App

ksizzle9 said:
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
The X development has all but ceased from what I can see. Such a bummer since I'm stuck with it for another year and a half. Hopefully we can see a few updates to some ROMs once gingerbread rolls around for the phone, but after that I don't see much reason for hope.

True...so what was the most annoying issue with this rom? Im thinking about flashing it. Im on 3.4.2 now.
Also you can sell your DX on swappa.com then pay the difference and get a htc.

With new update pending, what is best way to block OTA updates?

I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus? (please vote in the poll)
Here are the 3 mentioned:
1. Rename OTA Certs
2. Use Sqllite
3. Edit Build Prop
The build.prop is sort of experimental but seems to be working so far from reports.

The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.

Really? There are 1000 other threads that compare all 3 options?
All the ones I read are where someone brings up one thing and then a few other people chime in on a different one. I was trying to find out, in one place, what the most recommended one was.
It is my fault for not creating a poll at first.
It is your fault for being a jackass.

ADude said:
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Click to expand...
Click to collapse
I'd say he's read the 1000 threads, given the fact that he rattle off a list of suggested solutions from those threads.
FWIW, I too am interested in knowing if this issue has been settled. Just rooted my NC the other night, am really enjoying all teh apps I've downloaded and would be happy to block updates and wait for a rooted 2.2 update.
So if anyone knows the definitive answer ot the OP's question, please do let us know.

for what it's worth
doncaruana said:
I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus?
Click to expand...
Click to collapse
Don,
I haven't read the reputed 1,000 other posts on this topic, so I don't know what consensus may have been reached there, but this is my take on it:
- otacerts renaming isn't going to be reliable
- the sqllite fix (modding the fota.mode item) is a permanent fix, which eliminates any possibility of OTA updates creating problems
- modding build.props may work, even if you don't have a master to reference from.
I.e., some reasonable higher settings for ro.build.version.incremental, ro.build.description, and ro.build.date MAY do the trick, even if they're not a clone from a legit updated version. I don't know (perhaps someone else does) if perhaps only one of those is really necessary, E.g., something like ro.build.description=2.1.0.428.int.enc.rrdp.s39975 may be enough to do the trick, since it holds the main versioning string (currently at 1.1.0.328).
So my recommendation if you want to be sure would be to do the sqllite fix.
- Mark

Flash CM7..... problem solved

I added links to the 3 methods I mentioned, for everyone's reference anyway. I did also read somewhere that someone said that installing CMR would stop OTA updates as well. But didn't see a lot of discussion about that.

xwint3rxmut3x said:
Flash CM7..... problem solved
Click to expand...
Click to collapse
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax

Agree. CM7 is not quite up to where it needs to be as a daily driver.

build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.

khaytsus said:
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
Click to expand...
Click to collapse
The build prop only blocks one update. In order to block the Froyo update, you'd need the build prop for the Froyo update. That would only work until there is another update. Then you need the build prop from that update to block it. It becomes a vicious, never ending cycle. I may be incorrect in my understanding though.

I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.

Pre-dawn raid said:
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Click to expand...
Click to collapse
That's what I'm going to try. I found the entry, but haven't changed it to "manual" from "auto" yet.

Update questions
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.

My rooted 1.0.0 NC (Dec. ~8 autoroot) ignores the updates *DOING NOTHING AT ALL*. I can use the Market, download books from BN, etc.
Knock on wood!

cameraz said:
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
Click to expand...
Click to collapse
From what I've read on other Andriod devices, it relocks the device and you lose superuser. Still, I'm curious if all the apps I downloaded with root will work after the update. The device was a b-day gift for my sister and she really loves the e-reader aspect, hence why HC and nookie froyo haven't been slapped on there.

Well, if you run the stock launcher on a rooted Nook, you still see all the apps you have downloaded from Market in Extras. So I would assume that the 2.2 upgrade could preserve the apps you have on there. Though, I would always recommend doing a backup, getting updated, wait for whatever exploit is employed and re-enable your apps.

colorado_al said:
Agree. CM7 is not quite up to where it needs to be as a daily driver.
Click to expand...
Click to collapse
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)

migrax said:
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Click to expand...
Click to collapse
I'm with you. Tried the CM7 from SDCard yesterday. It was okay, but it didn't exactly rock my world. Waiting for all the bugs to get worked out. In the meantime, sticking with Nookie Froyo.

Divine_Madcat said:
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
Click to expand...
Click to collapse
I skipped over Nookie Froyo, but I used stock Root for awhile, and i've been on Cm7 for awhile and I love it. I agree video is not at 100% on cm7, but I really don't spend alot of time watching video on my nc at all. I downloaded the nook app from the market, and the tablet works great. The devs have done a great job, I have no issues using CM7 as my daily driver.
Gotta back you up madcat since we're the only pro CM7 users on this thread

[Q] n00b Questions about HoneyStreak

OK, I'm a n00b to this forum, so I can't post in the development forum yet. So I guess I'll ask here.
I have some questions about HoneyStreak.
Is everyone's screen in HoneyStreak kinda off? (See image below)
Is there a way to make the font larger?
How come everything is so tiny? (fonts and icons and everything)
What launcher should I be using with HoneyStreak?
Will a different launcher make a difference with the icon/font size?
Is the answer to all of my questions just that its a Beta release of Honeycomb, and that they are working on all of that? (or is it supposed to be like that? or did I mess up my install?)

1. Yes.
2. Yes, but you lose the HoneyComb Google Apps if you do that (you can bump the screen density up).
3. See #2.
4. Stock is probably best.
5. Not to my knowledge, but I could be wrong.
6. Yes.
Most of this has been covered in the HoneyStreak thread. I know it's a bit to read through, so I'm not annoyed; just saying you could probably find the answer to these questions and more on there if you're willing to put some time in.
Honeycomb isn't ready for primetime on the Streak 7, yet. This is more of an early beta, but it shows a lot of promise. Once AOSP drops, it ought to be significantly better (though that may not be until Ice Cream Sandwich). Keep watching.

Thanks Zandar, once again.
It is definitely a very promising beta. I can't wait until it's ready for prime time. Until then, I think I'll go back to the stock ROM, but rooted. I don't see too much advantage to StreakDroid, so I'll just wait for HoneyStreak.

That's exactly what I did. StreakDroid doesn't have functioning bluetooth, so that was a no-go for me. Try Gingerbreak for rooting stock 2.2.2; easiest root I've ever done.

I got excited when I saw a post about GingerStreak, but that's for the Streak 5. It kinda stinks having Gingerbread on my old phone and Froyo on my new tablet. LOL
I guess no one is interested in working on a Gingerbread ROM while Honeycomb is in beta. I don't blame them.
GingerBreak was an easy root. The hardest part was getting the .apk file onto the Streak and running it - which wasn't hard at all.
Another off-the-wall question for you:
How come none of the ROMs for the Streak 7 are Cyanogenmod based? I'm curious because I've gotten used to a lot of the Cyanogenmod features on my phone and I miss them on the Streak.

Tom2112 said:
I got excited when I saw a post about GingerStreak, but that's for the Streak 5. It kinda stinks having Gingerbread on my old phone and Froyo on my new tablet. LOL
I guess no one is interested in working on a Gingerbread ROM while Honeycomb is in beta. I don't blame them.
GingerBreak was an easy root. The hardest part was getting the .apk file onto the Streak and running it - which wasn't hard at all.
Another off-the-wall question for you:
How come none of the ROMs for the Streak 7 are Cyanogenmod based? I'm curious because I've gotten used to a lot of the Cyanogenmod features on my phone and I miss them on the Streak.
Click to expand...
Click to collapse
There aren't the devs for that, right now. There's a thread over on the Cyanogenmod forums asking for develops and even offering money for a port; no response, yet. I loved CM on my old Droid, but this device simply didn't have the dev support that the OG Droid had (not yet, anyway).

Dont count on no cm devs
Sent from my Dell Streak using Tapatalk

Hey Steve! Thanks for all that you do for our Streaks!! You are the man.
I do hope that recent price drops for the Streak 7 bring on some more interest. The more popular the device the more people will want to work on it.

DJ_Steve said:
Dont count on no cm devs
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
First off, I love what you've done for the Streak 7. You're really the only one pushing the device, and I know you're also busy with the Streak 5 (and, you know, have a life and stuff, too). I'm very grateful to have you developing.
That said, you're only one man (though a very talented one). I'm pretty excited to hear that some other devs might join the team. This device has so much potential, and it would be great to see people working to unlock it.
Any other info you can share, or is it all top secret, hush-hush right now?

another noob with question
i am ordering a streak 7 from t-mobile and will have it next week. in the mean time reading this forum and ready to get on honeystreak.
Do i just follow step by step direction in DJSteve honeystreak thread? is there anything i have to do before that, like root, fastboot,....?
thanks in advance,

You'll need to root your device in order to install honeystreak.
I wouldn't mess with the SuperOneClick method of rooting. GingerBreak is the easiest method. Check the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=1105165

Since I don't have enough posts I wasn't allowed to post in the development Honeystreak thread (10 posts required) so I figure I'll post here.
I just installed Honeystreak RC2 and so far it's GREAT! Thanks to DJ_Steve and others who made it possible!
My question though is regarding Facebook. I'm unable to find the FB app in the Android or Amazon marketplaces. Is this an issue for anyone else?
I searched for the .apk, but could only find version 1.4, and I know it has been recently updated. Anyone have the most recent apk?
Thanks for any input!
Jeff

rattlehead02 said:
Since I don't have enough posts I wasn't allowed to post in the development Honeystreak thread (10 posts required) so I figure I'll post here.
I just installed Honeystreak RC2 and so far it's GREAT! Thanks to DJ_Steve and others who made it possible!
My question though is regarding Facebook. I'm unable to find the FB app in the Android or Amazon marketplaces. Is this an issue for anyone else?
I searched for the .apk, but could only find version 1.4, and I know it has been recently updated. Anyone have the most recent apk?
Thanks for any input!
Jeff
Click to expand...
Click to collapse
Not to provide a non-answer, but the Android FB app sucks. I'd just use the mobile site.

No arguments there. But I do like having the FB widget on my home screen.
Also I figure I'd do my part to help point out any bugs or what-not with the RC build.

Facebook mobile shows up in rc3 and you dont need to be rooted to flash honeystreak.
Sent from my Atrix via tapatalk

If you'd just read the instructions then you wouldn't have asked your question I guess. LOL.

DJ_Steve said:
Facebook mobile shows up in rc3 and you dont need to be rooted to flash honeystreak.
Sent from my Atrix via tapatalk
Click to expand...
Click to collapse
Facebook mobile and the official Facebook for Android app are two completely different beasts. Facebook for Android does not show up in the RC3 marketplace. I had to push it from my phone to my HoneyStreak 7. Doing that though doesn't allow it to integrate with your Gallery and therefore can't share photos and videos on Facebook via RC3 unless you use the mobile site, which has intermittent issues. I'm pretty sure I could in RC2 as I had Facebook on there working properly. That's an Issue for me since technically it's my wife's streak 7 and she uses it primarily for facebook and surfing the web... oh yeah, and Angry Birds, gotta have Angry Birds.
Bear

im wondering if the facebook app doesn exist on honeycomb. i havent got a native hc device to try it

[Q] New DS7 in the mail

Hey all, I'm a new DS7 owner (well, UPS is right now but I will be). My interest was grabbed when I heard the news about the official Honeycomb being released for the DS7. After some add'l reading around about it (including discovering Honeystreak), I decided to trade my Nook Color in for a DS7.
I'm by no means new to Android hacking but I am totally new to the DS7. So I was wondering if a couple peeps would mind helping me play catch-up so I know what all is going on with it. For example:
What's the recovery situation? I see a stickied CWM thread but I also see comments such as "I doubt we'll be seeing cmw any time soon since partitions keep changing and we all know how badly cmw has screwed.us in the past...". If not CWM, then whatcha got?
Are there generally-accepted bugs with the device that I should be aware of before I waste time banging my head against the wall? For example, all AOSP ROMs for the Thunderbolt have a GPS and Network Location bug, and MMS only works if Wifi is disconnected.
What firmware-flashing tool is used? (equivalent to Odin, HBoot, RSDLite, etc.)
What other things are there that I should know about that are specific to the DS7?
If not here on XDA, where is DJ Steve posting new HoneyStreak updates?
I appreciate your help and a bit of patience while I ask the dumb questions.

Hey Jax, good to see a fellow Thunderbolt owner over here, well....the rom game is slow around these parts. Most owners including myself are waiting for the official 3.2 ota which may be days or weeks away for the wifi model. DJsteve is the streak dev but has CHOSEN to take his work elsewhere due to GPL issues.
The known bugs or issues for the most part have been well documented, battery life and screen, although I wouldn't call the later a "bug". Battery life is supposed to be addressed in the ota as well. In my opinion this is going to be a sweet little tab once 3.2 arrives and will hopefully attract some devs.
Sent from my ADR6400L using Tapatalk

Hi Jax,
Welcome to the Streak7 world. I too am a new DS7 user (wifi only). Only just getting mine back on the 2nd of Sept. I used the stock rom and thought it was a decent running system. In fact, I kinda disagreed with most who said it was a bit sluggish, as mine seemed to run quite well. Got my DS7 on Friday afternoon,by late Saturday night I had it rooted to Honeycomb.Why live with last years model when you can have this years model. I worked under that for a few days to see how it ran. Then I went back to the stock Dell rom for comparison. Well... after going back to the stock rom I saw just what everyone was saying about it being sluggish. Now granted the stock rom ran fine & I was fine with it untill I rooted. Then I got spoiled. SO not only does the stock rom run a bit slower, it has a lot of bloat. (as one would expect). Going over to the root rom fixes these issues. Its a clean fast running system now. I have not found any troubles with the rom Im using or the stock rom. I think you'll be happy with the DS7 & even more so after rooting it.
I use DJ_Steve's HoneyStreak HD7 2.0 (3.2)R4 (Going to R5 today as he just posted the R5 yesterday) & I love it. You'l need to install R2 first,then update to R4 or R5.
DJ_Steve has moved over to another site & his work can be found here :
R2 : http://tabletroms.com/forums/honeyc...[r2]-honeystreak-hd7-2-0-release-2-3-2-a.html
R5 : http://tabletroms.com/forums/honeyc...m][r5]-honeystreak-hd7-2-0-release-3-2-a.html
Good luck with your new DS7. If I can help any more please feel free to drop me a line. And keep us posted on your goings on with it.

^^^I also think the stock rom isn't so bad, I do have adwex on top of it though. I'm yet to root mines. I'm shocked how much I'm liking my DS7.
Sent from my ADR6400L using Tapatalk

Before you go installing HC, can you check what stock rom you have installed first?
The version is in system -> about phone
You might have a newer version rom then what's available. Dell has been releasing most of their updates as preinstalled only recently.

TheManii said:
Before you go installing HC, can you check what stock rom you have installed first?
The version is in system -> about phone
You might have a newer version rom then what's available. Dell has been releasing most of their updates as preinstalled only recently.
Click to expand...
Click to collapse
I bought mine used on Ebay. I had honeycomb on it within 3 hours of playing with my Streak.