yashsingh1/xdaforums huggingface dataset:
[Gen8 General] awink1:
Well, I say: let's cross the Honeycomb bridge after paying a visit to the Gingerbread man :)

I think Gingerbread will make this a much better alrounder than it already is. I have a feeling honeycomb will have the "Windows Vista" effect and then they'll start streamlining the programming again, without the fluff... Giving us the Android equivalent of Win7, but that's my opinion only
[Gen8 General] kingohearts2005:
I have to admit that when I read this yesterday I was a bit disappointed. If this is in fact the case I will be highly upset due to the fact the honeycomb is supposedly the more "tablet specific" OS so lets hope that this is not the case
[Gen8 General] hackmeister69:
As long as we're able to eventually root the device and get a custom ROM installed I wouldn't worry about it. I had a G1 prior to my Nexus One phone. Installing Cyanogenmod on the G1 made the phone much more usable then the vanilla ROM that it came with. The custom ROM guys love to backport the newer stuff for older devices.
[Gen8 General] LargePrime:
http://twitter.com/morrildl/status/12380827807653888

No minimums?
[Gen8 General] RollerCoasting:
That's GingerBread, not Honeycomb.
[Gen8 General] stanglx:
Asus just demoed their EEPad guess what? Honeycomb tablet NOT running Tegra 2... Dont fret though.... Its using the Qualcom dual core processor... (Note the dual core processor)... Its out in June at 499..
[Gen8 General] hough77:
This bothers me due to the fact that I just returned the GTab (the screen is terrible) and should have my 70 tab tomorrow or Thursday, wtf.

Sent from a Fresh Evo
[Gen8 General] stanglx:
See it this way... with the 70 you will have many many many many months of enjoyment before you are forced to upgrade. Even if Honeycomb comes out tomorrow I highly doubt there will be any proprietary/optimized applications for the OS. You wont see Honeycomb optimized applications till the 3rd or 4 quarter and applications will not use the dual core probably till later next year (though since the applications run through a JVM is is conceivable the JVM will have the added benefit of brining true multi threading without the developer needing to know how to implement the multi-threading)

Net net is... I still think the GTablet/Archos line of products are short term fixes for a need... the long term fix comes 2nd half when all tablets are out the market.. next year until we get hardware that is at a reasonable price.

Not for nothing if they come in at or around the 500 or 600 mark... Why wouldn't I get a IPAD 2(talking from my wifes point of view)?
[Gen8 General] hough77:
Indeed, thanx for the positive outlook, it will be a fun toy, and its not hard on check book either! Like it will be the last tab I ever buy or something.

sent from a rooted EVO running Fresh Rom
[Gen8 General] stanglx:
Well... after seeing some of the demos and the units which have Honeycomb I can honestly say with some level of confidence that

1. HoneyComb will most certainly be a tablet only OS - I think this is a horrible approach. This will just splinter the development with Phones always having the priority as there are more of them. Apple did it right having the base OS the same and leaving the difference up to the developers on which form factor to target for their app (Microsoft is doing the same if you have ever developed on the new mobile,desktop or gaming platform you know what I mean)

2. It will most certainly require dual core. Everything is a dual core even the EEPAD (not tegra based) that has been talked about that will run Honeycomb...

Positive is Archos will drop in price in a few weeks once pre-orders start for these devices...

Now I want to see what move apple makes... (they will most certainly wait to hear HoneyComb release date and some prices)..
[Gen8 General] 7895123:
ASUS Eee Pad MeMO:

•BXL Qualcomm Snapdragon 8260 1.2Ghz

Motorola XOOM with no Button (back, home, menu, ect..)

All kind nearly with our cheap Archos... nothing to worry about Honeycomb... just how long they do ^_^
[Gen8 General] Kashban:
Not so bad now.

I just read on n-tv that a google developer said there will be no hard requirements like screen sizes or cpu cores for Android 3.0.

Thing is, with only 256 MiByte of Ram the Archos will most likely have to be modded to run it. Like adding swap space and overclock.
[Gen8 General] stanglx:
It will install.. but will it run... I can install Windows Vista on an old 386... takes 2 days to install... but it boots.. and "technical runs"
[Gen8 General] czesiu:
as predicted, total BS ;)

https://twitter.com/#!/morrildl/status/22845294886518785
[Gen8 General] stanglx:
See this -->http://xdaforums.com/showpost.php?p=10375484&postcount=16
[Gen8 General] JasonOT:
Actually, you can't do that. There are hard minimums for supported architecture.
[Gen8 General] Chupracabra:
burn. just saying.
[Gen8 General] earlster:
I heard from somebody who is involved in the development of one of the upcoming Honeycomb tablets, that there is no dual core requirement, but it does need a lot of memory to run decent.

Makes me think the 256MB will be an issue.
[Gen8 General] stanglx:
If your going to say what are they? (and don't quote Microsoft's marketing minimums)...
[Gen8 General] JasonOT:
What difference does it make?

x86 architecture has evolved tremendously since the late 1980s. The 386 didn't even have a built in math coprocessor, much less advanced instruction sets like MMX or SSE.

There have been no such incredible advances in the ARM instruction set. Even the newest SOCs based on Cortex A9 architecture are still using ARMv7. It was foolish to think from the get-go that Android 3.0 would make obsolete hardware that was top of the line only 6 months prior to its introduction.

Is it plausible that much older ARM11 based devices, like the G1, might not be able to run 3.0? Sure. As it is, ARM11 devices generally don't even run 2.0+ very well.

But since you asked, XP requires a P5 or newer processor, and Vista requires a P6 or newer. Not because of Microsoft marketing, but because older processors lack the necessary instruction set for the OSes to function. Microsoft had a good 10-15 year gap in technical obsolescence.
[Gen8 General] stanglx:
Very complete and accurate answer... ;)

If we circle back around to whether or not what we believe Honeycomb is able run on the Archos platform I just dont believe so due to some limiting factors which to me are fairly evident in the current hardware configuration and what has been demoed over the last day or so at CES.

In either case it is fun to speculate and debate..
[Gen8 General] JasonOT:
Sigh.

There is zero reasonable chance that Google will make recently released phones such as the Nexus One, HTC EVO, Droid Incredible, Droid X, Droid 2, etc. incompatible with Honeycomb.

Oh, but Honeycomb for tablets isn't necessarily the same as Honeycomb for phones, you say? Likewise, there is zero reasonable chance the Google will put the Galaxy Tab into obsolescence less than six months after its release. Unlike our Archos, the Galaxy actually has true market access and Samsung worked with Google for this.

It's possible the 256MB we have may be a tad lacking, but that's what swap files are for. There are no other "fairly evident" limiting factors that make the Gen8s, the 101 in particular, any different from any of the devices I've mentioned.
[Gen8 General] stanglx:
I tend to agree with your thought... I am speculating that yes the Kernel could be based on Honeycomb (or the same) and just the UI may not be for phones/devices that have less then 512Mb... I see this being the best of both worlds from everyones point of view (like running Windows 7 on a device that has less then 256 Video Memory - same fundamental UI with out all the Glitter)

I am also speculating that Apple may go this roughte - I am surprised with the rumors of it having a Dual Core Also with 512 - 1gb of Memory...

Anyway.. As I posted earlier.. who cares at this point.. we buy these things now because we want it now and dont care about future upgrades... use it for what it is now and enjoy.. when the next best thing comes out... upgrade then..

Enjoy!
[Gen8 General] Kashban:
That's why I think you need to root and add Swap Space. With OC to 1200 or even 1300 MHz it might be able to run at reasonable Speed.

Then again the Archos has some Hardware built in to speed up things like Videos and the like, this might help too.

In the current Configuration it performs better than some Tegra2-Devices, which's Hardware Specs are way above the Archos.
[Gen8 General] ExploreMN:
Call me crazy...and I'm sure some of you will...but I would be perfectly content if the Archos 101 was only upgraded to Gingerbread. However, unless someone hacks a version in there, I would bet Archos doesn't even go beyond Froyo. The 256MB is a major limiting factor and I don't see them working very hard to force that large Honeycomb shaped peg into the Froyo sized hole.

I guess when I bought this tablet I made an assumption that I will only get 1-2 years out of it before upgrading to something new. Maybe longer if it can still do what I need it to do...
[Gen8 General] iztoogood:
If it run on nook ...why it wouldn't om gen 8?

http://downloadsquad.switched.com/2...-tablet?icid=sphere_blogsmith_inpage_engadget
[Gen8 General] superflysocal:
nook color has 512mb of memory, not 256mb
[Gen8 General] ExploreMN:
I guess I won't do much crying if we can't get honeycomb on our devices. I mean seriously...we spent < $300 for these things. On the other hand, if I dropped $799 or whatever the price of the Xoom will be and found it to not be upgradable, I would be highly pissed.

This line of Archos systems are not even meant to do all the things we are doing with them...like having the full market access, running all kinds of "unapproved" apps, etc. When Archos comes out with their Gen9 series (and yes, they will) you will see Honeycomb tablets with better specs.

If you are basing your buying decisions on the idea of upgrading, these tablets are not for you. Buy them because they can do what you want to do now and in the near future...
[Gen8 General] minterbartolo:
but couldn't Archos make some adjustment in the firmware to use some of the 8GB as swap/virtual memory?
[Gen8 General] czesiu:
they could, but we probably would not want to use that device if Honeycomb really needs 512;)
[Galaxy S I9000 Android Development] Alberto96:
I have got CM7 to boot on my Galaxy S using some of the same methods used to boot the stock Gingerbread ROM.

I take credit for nothing... All I did was switched around a couple files to boot CM7 instead of GB.

Requirements

You must be root on your phone

Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.

You must have proceed to complete backups before

Some busybox installation is also useful for tar.

Another Important note

Be absolutely 100% sure you have access to the download mode using the 3 buttons combination.

If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.

This is the gingerbread Folder to push in /data/: h**p://dl.dropbox.com/u/17890197/gingerbread.tar

Steps:

1: Download CM7 dump to SDCARD:

h**p://dl.dropbox.com/u/17890197/CyanogenMod/CM7.tar

2: Run the following via ADB

adb shell

su

busybox mount -o remount,rw /data

cd /data

mkdir gingerbread

cd gingerbread

busybox tar zxvf /sdcard/CM7.tar

busybox cp -a /efs efs

sync

reboot recovery

3: Flash "nsonsgs-unsigned-cwm-update.zip" via CWM Recovery

Watch CyanogenMod 7 boot on your phone!

How do I get back?

This is a dual-boot setup... Everything is still intact that you were running before this.

All you have to do is download and flash your previous kernel via ODIN. Once you do this, the phone will reboot into Froyo. Simply reinstall the nsonsgs-unsigned-cwm-update.zip and your back on CM7 again, just like you left it. MAGIC!

What's about this port:

- It uses the Nexus S kernel compiled from sources by supercurio

- It runs the exact /system image release, that I pulled from a CM7 alpha .zip file posted in the NS forums.

Which filesystem?

This is simply a mod of supercurio's early gingerbread preview, so it runs on Ext4. no RFS at all, the kernel don't support RFS.

Does everything work ?

No; will update as I discover more of what does and doesn't work.

Camera is not working.

Wifi is not working.

This can fry the front camera.

Phone could not work . ( sometimes it works )

KEEP IN MIND

CyanogenMod ROMs do not come with any Gapps and using this method, you will not be able to access CWMrecovery to flash the Gapps files floating around. I hope to have an answer to getting Gapps installed with ease by late tonight.

Thanks for all the devs who did this hard work in such a short period of time... please donate to them.

DOWNLOADS:

Kernel : h**p://dl.project-voodoo.org/nexus-s-kernel-on-galaxy-s/nsonsgs-unsigned-cwm-update.zip

CM7 : h**p://dl.dropbox.com/u/17890197/CyanogenMod/CM7.tar

Gingerbread Folder: h**p://dl.dropbox.com/u/17890197/gingerbread.tar
[Galaxy S I9000 Android Development] xan:
Does this kernel fry front-facing camera?

Just a heads up.
[Galaxy S I9000 Android Development] Alberto96:
Camera app is not working.
[Galaxy S I9000 Android Development] awia:
where did this CM7 come from?
[Galaxy S I9000 Android Development] Alberto96:
from nexus s alpha build . http://xdaforums.com/showthread.php?t=886903
[Galaxy S I9000 Android Development] jodue:
sounds nice, thanks for sharing! :D

do phone/sms/data/wifi work?
[Galaxy S I9000 Android Development] Rawat:
Based on my experience from when running the GRH78 build, data etc will work (polling problems persist) Wifi will not work.
[Galaxy S I9000 Android Development] st4rk:
Just a heads up for people codeworkx and coolya said not to use this kernel as the voltages are wrong and can cause for you to fry your front facing camera.

They are working on a proper port. Be patient.

Plus its not really alpha because you are not really working in it so how can there be a beta?

This shouldn't really be in the development section.
[Galaxy S I9000 Android Development] webstar1:
I was thinking of doing this, never mind :D
[Galaxy S I9000 Android Development] touness69:
@Alberto96, your CM7.tar.gz file is corrupted !

I've just tried your tutorial in the first post all went well until I typed the line "busybox tar zxvf /sdcard/CM7.tar.gz" then it gived an error :

I've tried re-downloading it three times, wipe dalvik cache, update busybox, activate USB debugging but it always gived me this error :(

tried with supercurios dump and all went well so it can only come from your dump

help will be much apreciated
[Galaxy S I9000 Android Development] Alberto96:
i will upload a new CM7.tar soon . now i can't because is too late . tomorrow you will have the working one . However, it worked on my Galaxy. Maybe the upload is unsuccessful.

Edit : I did a test and found intact , not corrupted.

7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18

Processing archive: C:\Users\Utente\Downloads\.ptmp573137\system.tar

Testing system

Testing system\app

Testing ..............

Testing system\xbin\vim

Everything is Ok

Folders: 63

Files: 1267

Size: 114894721

Compressed: 115906048
[Galaxy S I9000 Android Development] touness69:
O.o

Will check that another time then...

Maybe that's because I tried to download it within the phone, I'm downloading now from my PC but... it is now a CM7.tar.tar file ??

will report back after few minutes...
[Galaxy S I9000 Android Development] touness69:
still the same problem here :(

I've made a screenshot if it can help...

When you said u tested it what are you meanig ? did you try to flash or do you just clicked on the properties thing on the file ?

@Rawat, you are really boring if you don't want to test it on your GS just go get a life and leave this thread alone ! you are ridiculous...
[Galaxy S I9000 Android Development] skyworxx:
Just bumping this.

This Rom/Port whatever will most likely fry your front camera
[Galaxy S I9000 Android Development] touness69:
Not correct if you don't use it at all :cool:
[Galaxy S I9000 Android Development] My20:
thanks for soft.

but loop boot, not work

device nexus, device android ... device nexus, device android ....
[Galaxy S I9000 Android Development] sirphunkee:
Everyone, we (the mods) have gone over this thread and the ROM posted here, and while it certainly will have a limited appeal and use, it is still within the guidelines for what is allowed...the proper credits, etc are included, and it doesn't violate GPL or any other regulations. Therefore the thread will remain, and I will ask everyone here to keep the discussions related to troubleshooting of the ROM itself.
[Galaxy S I9000 Android Development] dcarr622:
I firmly believe that we should wait until an official alpha is posted by the CMSGS team.

After hearing of the front camera overvoltage, who knows what else could happen? The devs do, and they are working hard to bring us a great experience.

Excitement is great, but so is patience :) I'm sure it will be available very soon, so just hold on.
[Galaxy S I9000 Android Development] Alberto96:
If you have a boot loop you must convert your data in EXT4 . I'm uploading the new file . And you must have mounted has R/W the data folder
[Galaxy S I9000 Android Development] Alberto96:
i uploaded the new CM7.tar . Please test it on your phones .
[Galaxy S I9000 Android Development] Alberto96:
Anyone can do a script ?? I'm trying but i have a lot of errors XD
[Galaxy S I9000 Android Development] codeworkx:
If you want to start developing, you should get sources and play around with these. A little bit knowledge of C, C++ and Java is required. If you've no experience with these languages, start to learn.

Also required are some linux basics, knowledge about hardware and how android works.

Google will help you to find the right stuff you need.

But with the use of winzip, you'll never learn something usefull.

If you join IRC and meet us there, we'll normally help you to get your feets into the world of black magic. But we'll not explain basics, only things you can't google. ;-)
[Galaxy S I9000 Android Development] Alberto96:
the new version works??

stop comments about words or other . in the comments you must talk only about the rom . Please
[Galaxy S I9000 Android Development] touness69:
Still the same "invalid tar magic" problem :(

Well.. guess I will wait for a stable release then
[Galaxy S I9000 Android Development] Alberto96:
I have tried it on my Galaxy S with JPY Darky's 8.0 rom and i haven't the invalid tar magic error . I don't why.
[Galaxy S I9000 Android Development] codeworkx:
Was the tar created under windows or linux?

Tar's created under windows are FAIL.
[Galaxy S I9000 Android Development] Alberto96:
i'm uploading the gingerbread folder so you can copy it in data folder and continue the rest of the commands ( efs , ... ) .
[Galaxy S I9000 Android Development] Alberto96:
Unfortunately from windows . Shi* . I have a dual boot with linux and i , like an idiot , i created it from windows . XDXD Sorry for the inconvenience
[Galaxy S I9000 Android Development] g00ndu:
Try IZARC to tar from Windows, should be able to work.
[Galaxy S I9000 Android Development] touness69:
Gingerbread folder did work for me, nice and smooth but no wifi nor data :(

I thought CM7 alpha 2 has wifi (looked at it in the nexus S forum)

GSM work tho

thanks for the sharing anyway :)
[Galaxy S I9000 Android Development] Alberto96:
The gingerbread folder is alpha 2
[Galaxy S I9000 Android Development] Rawat:
It has wifi that works on the *Nexus S*

Galaxy S != Nexus S
[Galaxy S I9000 Android Development] davidf:
Not really, if you are interested in following the progress of CM7 for the galaxy S you can follow the real thread on this subject

http://xdaforums.com/showthread.php?t=877800

Although the original experiment to see how the nexus S rom would behave on a galaxy S was concluded the thread continues with a lot of information on whats happening with a CM7 development for the Galaxy S.
[General Questions and Answers] dekela:
Hi XDA!

Does anyone have or know how I can get a list of all Mobile Carriers IP ranges/subnets from around the world?

I am doing a research on Geo Locations and need this.

Thanks in advance!

D.
[General Questions and Answers] dekela:
I hope I am not breaking the rules but I am bumping the Q again in case someone missed it.
[G2 and Desire Z Q&A, Help & Troubleshooting] jthornton71707:
I've permrooted with visioanary and installed rom manager. Then I've flashed clockwork recovery from rom manager but each time I go into recovery I just get the regular recover icon, not the clockwork recovery icon or anything. I've tried this with all 3 versions of clockwork recovery on rom manager. Still only get the un modifier recovery screen. Am I doing something wrong???
[G2 and Desire Z Q&A, Help & Troubleshooting] thatruth132:
are you sure your rooted and does your device show s-off when in bootloader
[G2 and Desire Z Q&A, Help & Troubleshooting] jthornton71707:
I just noticed it says s on still. However I Dow loaded visionary and did the permroot and have superuser.... how do I fix this?
[G2 and Desire Z Q&A, Help & Troubleshooting] thatruth132:
if you want root you should read up here

http://xdaforums.com/wiki...Rooting_the_G2

and also here

http://xdaforums.com/showthread.php?t=855764
[G2 and Desire Z Q&A, Help & Troubleshooting] jthornton71707:
So visionary doesn't root?
[G2 and Desire Z Q&A, Help & Troubleshooting] thatruth132:
i didnt use it personally i took the long route
[G2 and Desire Z Q&A, Help & Troubleshooting] steviewevie:
Just flash Clockwork again from ROM Manager. It seems to usually take more than one flash before it "sticks".
[G2 and Desire Z Q&A, Help & Troubleshooting] jthornton71707:
I've flashed it about 20 times now into recovery. None have worked
[G2 and Desire Z Q&A, Help & Troubleshooting] steviewevie:
Sounds like you only have root and not S-OFF then. S-OFF is needed to flash custom recovery.
[G2 and Desire Z Q&A, Help & Troubleshooting] raitchison:
I had read that it's not behaving consistently/predictably which leads to issues. Even though I used Visionary when I was temp rooting (the first month I had the phone) when I went to permanent root I used the gfree method.
[Desire Q&A, Help & Troubleshooting] SeanBond:
I am running 2.3 Oxygen V2.0 RC5 with Widgetlocker Locksceen and am wondering if there is any way to stop it from waking up with any key press, as it wakes up with any key but the Trackball, I want it to only wake up with the power button.

I have unticked "Any Hardware Button Wakeup" in Widgetlocker but it has no effect

Help?
[Desire Q&A, Help & Troubleshooting] SeanBond:
Anyone? :(
[Nook Color General] WhiskeySlx:
I've been a googlin, but found nothing on this yet!

Last night I finally got around to rooting. Everythings running smoothly except for one minor thing, which is that the open book icon on the status bar [that normally opens the book you're currently reading] is no longer working.

It was working after I'd initially rooted, i.e. before installing any apps or doing anything. But then after a bunch of otherwise successful tinkering (install/config of ADW, uninstalling soft keys, modding the volume buttons, etc) I noticed it's not working any more.

Has anyone else seen this happen?

I tried one thing to fix it thus far: I reverted to the .bak copies of the keylayout files and rebooted; this successfully returned the volume buttons to their original function [no longer menu and back], yet the open book icon still doesn't do anything. (The icon glows while pressed, but no action follows)
[Nook Color General] peiziyu:
The book icon to return to your previously read book only works when you're using the nook home screen as your default home screen. You can use soft keys to configure one press for nook home and two presses for ADW, and then it should work.