Spacemoose1 has a special request:
ssserpentine presents......
Android 3.x Honeycomb for the Samsung Galaxy Tab (GSM)
Download Rom: GSM | Source Repository | Development Log | Donate
A Spacemoose1 production
Firstly, if you cannot commit to reading 3 posts completely, and carefully, please go here. for a quick look into your future.
Or go here for a look into your tabs future.
1) Yes, you MUST start off in FROYO, no exceptions! your reported bugs will be useless and of no help to me or anyone else. & as everyone should be following the guide, & coming from FROYO, don't expect to not get yelled at!
2) Everyone follow the installation guides in post # 2 step by step exactly!
3) This is presented in unfinished Alpha mode, for you to see what is to come and help bug test. EVERYONE needs to install exactly the same way so that they may report actual bugs, and not ones because you didn't listen.
4) Please, everyone, start off EVERY reply with your carrier (T-Mobile, Unbranded, AT&T, ect..) & country of origin of the Tab, so that it may be decided if any bugs are specific to any of these conditions.
This is an ALPHA version.
There is no 3g nor phone, among many other things (like BT, gyro, hardware accel.)
Using an alpha rom can be very dangerous. Don't just flash, because you see its HONEYCOMB, read everything very carefully first!
Wackymixing has created an excellent video of this HONEYCOMB alphaV2.5 running on GSM device.
(6/14/11)
After being up way too many hours in a row, and trying to do too many things at once, work on a new kernel has officially begun!
*what's in the oven. .
»new cwr with internal external support.
»1.2ghz
»uc ability
»reliable charging while power is off.
«doubtful, but cross your fingers for lagfix?
(6/13/11)
GSM owners. Alpha 2.5 has arrived!! (No 3g nor phone, ect.)
I highly recommend you start off in FROYO, as coming from GINGERBREAD causes crashes, and will make your bug tests not needed by me.
But, beware, changing your bootloaders is very dangerous![/COLOR]
*modded build.prop to identify itself as a Samsung Galaxy Tab as GT-P1000. - test runs, not included in cdma release
*modded audioflinger to accept dsp manager setting. (more equalizers coming soon) - test runs, not included in cdma release
*what I have planned, and currently in the works.** New kernel with 1.2, 1.4 oc
* Flexible scaling
* Attempted lagfix
* New CRW version with internal and external sd support
* SD cart mount upon boot
Until SD card load upon boot happens,
Instal Terminal Emulator from the market, and try these commands:
su
mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/
Now your SD cards should be mounted!
(6/11/11)
GSM owners, I'm sorry to say that I have to put you off once again. The new kernel works and the crash issues have been resolved but I can't get vold to behave and the sd card simply refuses to mount at boot. The files in the repository are current though, so feel free to download and install them that way if you would like to test. You can mount the SD from a command line (adb shell) and activate UMS after boot using the following commands:
mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/
echo /dev/block/mmcblk1p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
-or-
download Android Terminal from the Android Market, and try these lines:
su
mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/
Hopefully this issue will be resolved soon.
Edit: Also had a tester report the return of the screen sleep-state crash (power button), but the issue was resolved by flashing froyo, and then installing HC. He used the overcome 1.6 instructions. It ended his crash issues and returned his lock-screen. Just FYI.
Alpha GSM v2.5 has the following!
*A fully working tablet marketplace.
*Maps, places and streetview.
*Working audio (it needs work, but it's there.)
*The lastest version of voodoo sound integrated into the kernel.
*The voodoo sound control app.
*A couple of widgets from the Asus Transformer.
*A setup wizard that allows you to select your language at startup.
*A tablet keyboard apk that makes text entry easier.
*Multitouch.
*And a handful of stability and speed fixes.
What it doesn't have...yet
*Gyro (no rotation, there is an app installed but rotates wrong way)
*Settings window not appearing when expanding from the Notifications menu
*3g data nor phone abilities
*BT,
*gyro,
*hardware acceleration
*SD card on boot
*headphone audio
*mic
*GPS
The Guides
A very important thread for all to read before you do anything!
http://forum.xda-developers.com/showthread.php?t=1047500
How to go back to stock FROYO and get HONEYCOMB
Download the overcome based guide, created by thepittbull
and modded with help and permission by Sҡȳᴪʌɩҡͼṟ
Be sure to thank both, as this is an great guide.
(You will know it is going well if it goes from SAMSUNG splash screen, to dark, then your soft button lights will blink and then it will boot. - the time in between these things is hard to gauge)
TWEAKS
Tired of that red border?
1) Open up Dev Tools
2) Go to Development Settings
3) StricktMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
WANT STREAMING MUSIC VIDEOS?
try looking for
Qello (get tbe tablet version)
its like you tube for music videos. thanks chris 49424 in cdma thread.
WANT IMPROVED UI AND SCROLLING?
Try adw launcher. for some reason just having it instaled helps just as much as using it.
PROBLEMS CONNECTING TO WIFI?
some users have problems with routers that use high channels. try to set your channel around 7 on router.
TV SHOWS STREAM
A very few users have reported that this does work.
Does not for me, but you might wanna try. there is a free version on market, but not our market. Google or maybe appbrain.
Dropbox
Great way to transfer files on gsm hc!
Apps confirmed working on port:
http://forum.xda-developers.com/showthread.php?t=1114916
thanks jjhiza!
Great news for GSM users! Thanks for your efforts.
Sounds good. Let's kick this thing!
Time to get this party started
ETA ON DOWNLOADABLE ROM:
SOON! sorry no exact time, i need to make sure everything is perfect!
ssserpentine said:
ETA ON DOWNLOADABLE ROM:
SOON! sorry no exact time, i need to make sure everything is perfect!
Click to expand...
Click to collapse
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Edit got so excited I forgot to read
maxtcee said:
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Click to expand...
Click to collapse
would still recommend on going back to Froyo, as mentioned in previous posts. There are way too many crashes and random errors if you were to start from Gingerbread.
That could change in the future though.
Sounds like it's flashing time again. Awesome stuff.
Looking forward to a new thread of garbage posts and new releases
Sent from my GT-P1000 using XDA App
maxtcee said:
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Edit got so excited I forgot to read
Click to expand...
Click to collapse
I was on CM7 before trying out Alpha 2.5 (GSM). As said, I got frequent crashes and reboot problems. Just follow Overcome 1.6's guide and go back to Froyo. And then install Alpha 2.5, you will get less crashes.
maxtcee said:
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Edit got so excited I forgot to read
Click to expand...
Click to collapse
FROYO.
everyone please start from froyo, as if you come from gb, i cannot promise sd cards will mount, wifi will work or power button will not cause crashes.
Thank goodness we get our own thread! Having to check the general thread was getting tiresome reading about those lucky CDMA users
Thanks for this ssserpentine! Ill be flashing as soon as I wake up
| Don't Revive Me Bro | Follow me on Twatter
robkoehler said:
Looking forward to a new thread of garbage posts and new releases
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
hopefully this thread will be clean.
Final testing, getting really close.
robkoehler said:
looking forward to a new thread of garbage posts and new releases
sent from my gt-p1000 using xda app
Click to expand...
Click to collapse
hahahaha! Lolz
Can't wait to test it.
This is the best thing since sliced Moose!
Sent from my SPH-D700 using Tapatalk
hussmanne said:
This is the best thing since sliced Moose!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
0.o Er...
Just out of curiosity, do we refer to the GSM version as a fork? Or does that pertain just to the kernel? I want to know how to refer to the GSM version, relative to the CDMA, in the You Tube video that I throw up.
EDIT: Or, is it more of a port? Burning questions, people! Gotta make sure that we get our terminology right.
Related
So guys, I didn't want you to wait more days so I am just releasing current state. So far this build seems to be the one I will work on as it runs fast.
My wife's sitting in my neck last days cause I was sitting too much in front off my netbook. Anyone wanna help me?
As I said it runs very smooth. Just try it for your own and give me feedback
Important:
- This release runs fast but keep in mind: When first booting it. Don't touch your device the first 10mins after it has booted into Android cause it will execute a script and do optimizations and therefore be slow. Next boots will be fast and also device will be fast.
If anyone would provide me with Linpack Benchmarks I would be grateful
You are responsible for everything what you do with your device. Don't blame me for not reading instructions carefully. It works when you know what you are doing. read thread posts
Installation:
Like the last EXT2-builds: Use my Haret-Paket. You may download latest on my Homepage.
Installation Instructions
Download latest Release here
Report Bugs here
Wishlist for next release
Video which shows how I run LinPack and get a result of 3.6MFLOPS. When overclocking I get 4.04MFLOPS:
Video
What has changed in the latest Build:
- Removed uneccessary apps
- Replaced Launcher with ADW Launcher (screenshots will follow)
- GPS works now
- Updated apns-conf.xml
- some other smallies
- you will have to use an app called "Quick Boot" for correct powerdown / reboot (go into Market and download it for free -> will be included in next release)
Known bugs:
Setting ringer volume only works with up/down buttons when changing ringer
Camera does not work
Battery draining
Google Mail ?
Reboot procedure (see Hint above)
some smallies (please let me know in Bug + Wishlist)
This should work on your device. Diamond Users get it running. Anyone get it working here? It's based on XDAndroid rootfs + kernel. So it should work. Maybe an experienced user wanna try it?
You may follow main-thread in Diamond-section of XDA-Developers
Wow...
Do you have some screenshots?
i apologize but i'm a bit confused.
whats the difference between your build and any other 1.6 build?
i see you made it an ext2 instead of a sqsh but whats different in yours than the original 1.6?
as far as i know the development on the 1.6 is at the same place as the 2.1. same features minus those found in 2.1 and not in 1.6.
I'd be curious as to what differentiates this build as well... perhaps I'll just have to wait and see for when you post it & I can run it and see for myself...
I am rather curious, but you should have perhaps waited till you had more time to introduce a better post rather than confusing some people ;P.. (such as me!) Did you create a proper bootloader for the Touch Pro devices or what? Haha.. Sorry, I'm rather curious!
Well using partition means you don't have to edit the System.sqsh to add apps and do modifications, Looking forward to it!
Re: [UPCOMING][Neopeek's ANDROID DONUT 1.6] ext2-filesystem - NoSquash
The ext2 can be made very easily from our sqsh systems. There is a program called staysafe that will do it for you in android. There is a thread for it somewhere on xda with all the needed files. It says that it is for cupcake and donut but I've used it in eclair without problems. Using rootexplorer, I needed to change to an ext2 system to get root accesss writeable. Worked very nicely. Only downside is the ext2 system is huge compared to sqsh. I want to say the ext2 was aroung 500mb.
Sent from my AOSP on XDANDROID MSM using Tapatalk
vatoloco said:
Hi all,
just wanted to let you know that i succeeded in putting Android on EXT2 of internal memory. SO THIS WILL WORK FOR YOU AND YOUR SD_CARD, TOO! IT WILL ALSO WORK ON THE OTHER DEVICES LIKE TOPAZ RAPHAEL ETC.
I will later explain how to get it running and offer the complete package for download. I will need some hours, though cause I am at work now. So you will have to be patient. Tomorrow is my birthday, so don't expect too much support. Only thing I can say: This build's gonna rock your phone and ist extremely fast!!!
First build is based upon Android Donut 1.6
I will contribute a Froyo build some days later, though this will be just for testing and is instable / not productive
I don't know if this is going to be on top or anyone is going to make this sticky. But the original thread is created at DIAMOND-Forum. So beware of cross posts and please post your comments to original thread here. On the other hand: If no one posts then this thread won't be up any more. Regardless: I will only post updates and comments to original thread.
Click to expand...
Click to collapse
I you using the same method as this
i really dont see anything new here, other than just providing something that balsat has been provding for the past 3-4 months, with a step by step guide that anyone can follow
amazing extremely fast on my diamond thanks vatoloco
1.6 work very fast but froyo is slow.
Just to bring this up again. Perhaps someone wanna try ports from HTC Vogue (need feedback)
vatoloco said:
Just to bring this up again. Perhaps someone wanna try ports from HTC Vogue (need feedback)
Click to expand...
Click to collapse
I could give it a try.
TheDeadCpu said:
I could give it a try.
Click to expand...
Click to collapse
Ok. So please let me know what you are thinking about this.
The main-thread can be found here:
http://forum.xda-developers.com/showthread.php?t=695215
Ok new build is coming up, soon! Just to let you know:
I got 4.04MFLOPS in Linpack with my build. You may check main-thread for screenshots and video.
First post updated with screenshots
vogue port htc pro 2
I need help cannot get donut 1.6 to work keeps coming up at the android boot suspend and alot numbers come up it want boot into android
First post updated.
Just wanted to let you know that CyanogenMod SuperE-Port is available for download (follow signature). The build from the first post of this thread is also confirmed by users to work on Touch Pro & Diamond2. Have fun!
Very fast
But i have one problem:
I can't install apps. There is a error message which says there is no free disk space.
I have a 8gb microsd. 3,6GB fat and 4gb ext. Booth partitions have more than 2GB free diskspace ...
Can someone help me?
(Sorry for my bad english )
UPDATE statement.
As original author for this thread, videos and first demos, I'm not currently working on the Gingerbread port these days (heavily busy working on Voodoo sound improvements).
It doesn't mean I lost interest in it, only that I miss time at the moment.
CyanogenMod team work on a serious port of Gingerbread for Galaxy S, witch won't be just a technical demo like the original spirit of this one.
Of course, such goal requires a lot of work, dedication, and also some calm.
There is a lot of natural interest about Gingerbread on Galaxy S, and it's perfectly understandable too.
Giving an ETA until the porting work is done or some major advance is made would be dishonest.
It means that not asking for ETA will be appreciated. However, you're welcome discussing other aspects.
If you want more technical insights and a few updates by most actives developers for this port, i would recommend to follow:
http://twitter.com/CMSGSTeam
http://twitter.com/codeworkx
http://twitter.com/dumdidum
[list needs to be completed, thanks for input]
Thank you!
Original post:
Galaxy S with Nexus S kernel - Booting Nexus S Android Gingerbread
Videos are here:
http://www.youtube.com/supercurioxda
Early demo Releases - V6
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
Verizon Fascinates are not yet supported - Epic4G will require a lot more development.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be 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.
Steps:
1/ Download this system dump on your sdcard:
system dump archive
2/ Run these commands
Code:
adb shell
su
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/system-dump-as-root.tar.gz
busybox cp -a /efs efs
sync
reboot download
3/ unzip the attached nsonsgs.tar.zip to nsonsgs.tar
4/ flash the kernel with Odin or Heimdall - no pit - no re-partition
Watch Gingerbread boot on your phone !
How do I get back?
Everything is still in place on your phone - no harm done.
All you need to do is to flash your preferred custom (that support Ext4 obviously) Kernel back on your phone
What's about this port:
- It uses the Nexus S kernel compiled from sources
- It runs the exact /system image release, we dumped on IRC from an actual Nexus S device.
Am i French ?
Now you don't have any doubt anymore
Which filesystem ?
This early preview runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
Nope, but there are progresses.
Don't work: GPS / Voice / camera
Work: everything else: like sound, GL acceleration etc
Will it work ?
I think most of it will work after countless hours spent on it.
Is it flashable with Odin ?
Won't be so easy, but it's one of the goals
Do you work alone ?
Credits go the IRC channel #NSdev on freenode, and now a team formed regrouping most Captivate/Vibrant/Fascinate/I9000 developers and CyanogenMod team, with Kernel and ROM developers and also newcomers.
When will this/that work ?
The only honest answer is: there is no answer.
Please don't ask for ETA, don't pressure developers, they need peace of mind
Is this Open Source ?
Everything is fully published under an open source license
Latest initramfs: https://github.com/project-voodoo/nsonsgs-initramfs
Kernels: https://github.com/galaxys-kernel
Who are the actual contributors to the code?
For the kernel, you can follow works here : who / when.
https://github.com/galaxys-kernel/linux_samsung_galaxys_port/commits/galaxys-port
As it is a team work, sometimes it's not the guy who had the idea who commits the code, but still
Articles:
http://www.engadget.com/2010/12/18/samsung-galaxy-s-receives-gingerbread-port-right-from-the-nexus/
http://briefmobile.com/samsung-galaxy-s-android-2-3-gingerbread
And a lot of other ones now!
Versions:
V6
- Easy root. You only need to install Superuser app from Market.
Downloads :
Kernel you can flash with Odin / heimdall / kernel flashing apps
ClockWorkMod unsigned update.zip
V5
- Wifi semi-working (tend to crash the phone on Wifi sleep timeout)
- Calls working but no DATA for me (coolya had data, which means: erratic) - voice not tested.
- kind of laggy, but there is a lot of headroom.
- GPS working only by Wifi/Triangulation networking - No satellites.
Fantastic job by coolya who did most of the advancement, for Wifi, baseband and also OneDRAM partitions configuration. Really really awesome work.
We were so lucky the snow forced him to stay at home instead of going to work
This time you can really start to play with the phone, install apps, surf on the Internet all this with Gingerbread! kind of cool
V4
Buttons fixed thanks to the contributions of xcaliburhands, pawitp, fenfir
No need to create some directories manually anymore.
Kernel available as ClockWorkMod recovery update.zip - be sure you have access to 3 buttons !
V3
SDcard now works
- As internal storage
- As USB storage
V2
improved pre-init script and mounts:
no more insufficient space
improved dual-boot solution
faster boot
faster disk I/O
V1
initial
Edit: we started working now as a team, joining XDA forces with CyanogenMod.
Gingerbread CM is AOSP, which means the port will be the real Google experience, using clean source modified just as we need to.
Holy moly..... I can't wait! Thanks Curio (and any other devs)!
I wonder how fast this ROM will be! 2.2.1 is smooth as butter as it is!
That was quick! I saw the title before saw who posted I thought it was just going to to someone asking for eta's... Nice work!
LOL are u serious? Doc was trying to run it the other day but couldn get pass the boot screen haha
Let's wait patiently for the port, and let the dev do his work.
Sent from my GT-I9000 using Tapatalk
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
We're waiting...
heymanator said:
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Patience, it will come to all in time
Sent from my GT-I9000 using XDA App
heymanator said:
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What works on one GSM Galaxy S works on every GSM Galaxy S with only minor tweaks.
Time to dust off my i9000 and get it out of the drawer.
why was it in the drawer?
boodies said:
why was it in the drawer?
Click to expand...
Click to collapse
Cause I was fed up GPS not working among other things... been using my Desire for about 6 weeks. Boy, definitely missed this screen, and Swype... but not the lag.
I want the package more than the video!
I think I just wet myself!
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Red John said:
Cause I was fed up GPS not working among other things... been using my Desire for about 6 weeks. Boy, definitely missed this screen, and Swype... but not the lag.
Click to expand...
Click to collapse
If your GPS doesn't work and you have lag then it is your fault for being too lazy to fix it
Sent from my GT-I9000 using XDA App
TettZor said:
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Click to expand...
Click to collapse
That made my day lol
Sent from my GT-I9000 using XDA App
TettZor said:
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Click to expand...
Click to collapse
HAHAHA I'm hoping Samsung hire some of these devs! And I guess there's not much use of a "Nexus S" now that the Galaxy S is able to run what the Nexus S runs.
Waiting waiting.....
Sent from my bad-ass i9000
Looks like it will be out later.
supercurio François Simond
But I guess that in about than 1 day I will publish a method, and you will be able to boot #Android #Gingerbread on your #GalaxyS
1 hour ago Favorite Retweet Reply
»
François Simond
supercurio François Simond
Ok the video will come later, no ETA
1 hour ago Favorite Retweet Reply
Original thread here! >>http://www.neopeek.com/forum/Android-ROMs/5764-Ooops-WE-did-it-again!-Gingerbread-Alpha2-available <<
EDIT: Not for Sony Xperia X1. Works on my HTC Diamond so I can't say what other devices will do...Thanx everyone for testing the Pre-Alpha! I could fix several bugs! Now we are officially Alpha and it's quite usable on my HTC Diamond!
Ooops WE did it again...
My wife's still knocking my brain saying I am an idiot B) (while writing this she stands behind me). I spent some hours yesterday and several hours during the night cause I know everyone wanna try this out. I want especially say thanx to Chann who always is inspiring me with his ideas while I am doing some nice conversations with him on dev-section of this forum. It's really helpful to have such kind of member here.
More details later -> as always: I don't have time to test anything out on my own -> so I didn't! It's up to you to come back and report your experiences.
Alpha-release 26-12-2010
Before continuing be aware of: This is an Alpha release and now it seems usable (on my HTC Diamond it is!)! So before you do anything I suggest you to make a backup of your data / files! So read everything careful now :
What's inside ?? :
[ul]
[li]Gingerbread 2.3[/li]
[li]Working: Wifi, Data, Phone, SD-Card, Compcache 25%, automatic lcd-density settings and maybe more[/li]
[li]BT activating produces reboot (needs fix)[/li]
[/ul]
Important now!!!!!! Read:
[ul]
[li]First boot takes quite some time! [/li]
[li]I suggest you to open all apps and sync your account with google. Then reboot your device![/li]
For Download, click above link!
As always: Use this on your own risk!
Thanx go to: Balsat, XDAndroid-Project, Martin DZO and everyone else whom I forgot!
Download is a 1-file-download, again! Including everything you need!
EDIT: I need your experiences / feedback in this thread!
Installation:
[ul]
[li]Installation Instructions (Link) thanx to chase21[/li]
[li]Test-Kernels to try out (Link) thanx to hayabusa94[/li]
[/ul]
Please update your signature! It's always hard to find out which device / smartphone you use and which kernel(s) you are referring to!
Click to expand...
Click to collapse
-Neopeek!
Don't thank me! Thank Vatoloco/Neopeek!!
HTC raphael 800 can run but wifi not working (status: error) and battery drain fast.
I still waiting for Neopeek Team.
I am just instaling it... I can not wait for the final fully functioning version.
Cheers
Not stable enough for me at least (Fuze/RAPH110)... Guess I'll just have to deal with FRX03/FRX02 for now... ^_^
Kernel package: htc-msm-linux @ 20101204_005141
I have a Fuze and it works fine for me, but it is just a bit laggy (kernel does not support so well).
Remember he just hacked gingerbread to work with froyo settings but I can promise that future builds will be much better once every one else has started the development of gingebread on our devices
I kind of figured, just wanted to report my experience since it seems most of the newer kernels seems to half work on my Fuze with FRX03. Might just be something I'm looking over About to try again with newest kernel from Glemsom's site and see if the FCs are any less frequent.
Yeah, i'm using the latest glemsom kernel and it is slightly laggy but stability is much better. I have not tried any other kernels yet..
I'm using the old kernel & module 01238 from FRG83 R5 build in this Raph100 & it works just fine except for the known Android issues that we still have.
Some minor glitches in Gmail & root access rights reported by SetCPU, but overall a good build (stable) considering that it's still in Alpha stage. Anyway, we get to test run Gingerbread while most native Android devices are still running Eclair or Froyo!
hello, it runs fine with kernel 1190 from camera thread, for the keyboard use jap input. Reboot you can, do with the dev tools-bad behavior-crash system server. keep going man very good!
UPDATE
Gingerbread is working nicely! I have not tested everything but at least there are less FCs! I am using kernel package from Dec 26, 2010:
zImage & modules
NOTE: Check out F22's note about this specific kernel package from THIS post.
Better performance ?
Gingerbread is supposed to be faster than Froyo. I wonder whether this will translate into a better performance on the Diamond. The Diamond is a slow device (compared to the HD2) and there's not much that can be done about it, except overclocking.
HD2_addict said:
Gingerbread is supposed to be faster than Froyo. I wonder whether this will translate into a better performance on the Diamond.
(post trim)
Click to expand...
Click to collapse
Anyway we could interest you into test driving and giving it a once-over with your diamond?
I would love to try it myself on my touch pro cdma (raph800), but i can't afford to mess around with creating the separate partition to try this. Is there yet an alternative way, as i would love to test this out also?
I suppose I could try to make it into a .sqsh file so you can just boot off of it on sd card but no garuantee it will work...
I wouldn't mind trying it if you don't mind doing that. I keep my android2.2 in "setpath=android2.2" directory, and assume i could also do the same with this "setpath=android2.3" to keep them separate.
here it is: http://www.multiupload.com/6QEW8OFBMJ
*may or may not work*
Thank you much sir. I just unzip the sqsh file from that archive file into the main SD stick directory, correct? So far i followed the instructions and (at the time of writing this) was at the "run the install from the subdirectory, after it's done, it will reboot back into WM" part, and continuing.
Yes, that is correct. You don't need to run "install.exe" or need the npkinstall folder. It should be fully compatible with xdandroid and you don't need the files from neopeek.com.
Just boot it as if it were an xdandroid build and hopefully, it should display android logo. Ext2 is much faster.. give it a try when you can.
I might have to do that. All i get is the following (last 2 lines of the screen at boot)
"mmc1: error -22 whilst initialising SDIO card"
"Waiting for root device /dev/mmcblk0p2..."
and then just sits there for ever.
Are you using an xdandroid startup.txt or neopeek?
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RAPH/DIAM) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
DIAM users have reported the g-sensor is flipped -
emc02 said:
ok, the solution for DIAM100 is:
change "gsensor_axis=2,-1,3" to "gsensor_axis=-2,1,3"
works perfect!
Click to expand...
Click to collapse
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post.
Anything that's broken in Froyo, is probably broken in this build.
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
[R^7Z EDIT]I don't suppose that would work if you were re-working this from the beginning or starting over from scratch (doh!). Lucky me, I save just about every new/update regardless of kernel package or rootfs update[/R^7Z EDIT]
R^7Z said:
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
Click to expand...
Click to collapse
If you already have a ts-calibration file, there's no need to create a new one .
A note to all troubled users
And additionally, to those who are reporting issues, it would behoove you to help the devs out by not making them guess what you are using (device) to include but not limited to, which rootfs and kernel package (date of release and commit ID might be helpful). That being said, be aware of what you are talking about (app discussion should not fall into this thread) and please keep talks of neopeek variants to a minimum (I know a little bit about these builds and will help out where I can, PM me if you really think I can help and if you really need some assistance)
arrrghhh said:
[CUT]
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho...
[CUT]
Click to expand...
Click to collapse
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
thebranded said:
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
Click to expand...
Click to collapse
Hrm. I'm going to go with format your SD card using the HP Tool. Full format, FAT32.
Also, might want to try kernel 1258. Let me know if neither of those things improve it. Is it creating a data.img...?
g3rm0 said:
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
Click to expand...
Click to collapse
Sorry forgot to respond to this. Two things, there's an app called "gingberbread keyboard". Find it on the market, see if it works better for you.
Second, I've heard the new 1258 kernel is fixed - not sure how, but it seems the clocks commit from jb's tree did it.
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
thebranded said:
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
Click to expand...
Click to collapse
Glad it's working for you. I think we've narrowed down the calib issue, so hopefully we'll get that fixed for all devices soon. Not sure why but RHOD's don't seem to have the issue any longer - no matter, we will get it resolved for all devices. Sometimes just takes longer for the old devices unfortunately...
[xda Link] Gingerbread keyboard
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
R^7Z said:
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
Click to expand...
Click to collapse
I've heard it doesn't work... Per another user, I have added a different recommendation:
arrrghhh said:
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho... If it does bother you, user "webxplore" said the app "gingerbread keyboard" (on the Market) fixes the issue. Thanks webxplore!
Click to expand...
Click to collapse
Gingerbread keyboard (market version)
Will see about getting the market version upped for those who are not able to access a wifi or have the awesome pull-out keyboard the RAPH/TP has
[R^7Z EDIT]Keep in mind, I have a RAPH110/TP/at&t Fuze
Free for all!
n-Joie! (Enjoy)
[/R^7Z EDIT]
Please note, we now have a source fix for the keyboard size and it will be integrated in the next testing image.
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
R^7Z said:
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
Click to expand...
Click to collapse
No need. I'll let stinebd know, I'm not sure what the difference would be... if he can backport something to Froyo, or if we are just going to be moving forward and focusing on GB. Thanks again for testing!
Thanks alot man this build is great! seems to boot and run faster and smoother then froyo ever did for me...only issues i ran into were not being able to see the calibration which if youtap on the screen it glitches and shows part of it.....but the main thing is i seem to have a problem staying connected to the internet and have to soft reset to get it working again....also airplane mode seems to get stuck once clicked and only a soft reset fixes it
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
xtremists said:
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
Click to expand...
Click to collapse
Read the second post. Gsensor doesn't work yet, but there's a fix in the pipeline. Keyboard fix as well, in the meantime... read the second post!!!!
Hi Guys,
*edit*
Teaser time is over, here is the build.
Version alpha 1 is here, nothing new for A101, it just adds touchscreen for A80 owners.
Preliminary warning: this is buggy as hell, don't expect a functional build. This is only if you want to get an early taste of ICS. And as usual, I'm not responsible if you blow your tablet.
What works:
- Framebuffer with 3D driver enabled.
- Touchscreen (A101 only)
- Wifi
What doesn't work:
- Everything else
- Internal storage is not mounted.
- Most notably, audio/video/power management/charging.
Instructions:
- You need sde menu enabled, see instructions here if you didn't do it already.
- Copy sysroot_ice.img to internal storage root:
Code:
adb push sysroot_ice.img /data/media
- In developer menu, flash kernel and initrd from zip file:
On boot menu, select "Recovery system"
Select "developer edition menu"/"flash kernel and initramfs"
A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
Select OK, the kernel should flash.
Select OK to reboot.
- Choose developer edition in boot menu
You should see two menus coming before boot, just wait for timeout. Other options won't work for your device.
Informations/Tips:
- Wifi AP scan doesn't work at first. Just add a dummy network, it doesn't matter if it doesn't exist really, scan will work after that (on wifi panel, click on "Add Network" button, top right of the screen then type "dummy" as network SSID, then OK).
- As I didn't want to interfere with regular build, data partition is the same as system image file, so there is only about 90M for apps.
I don't need feedback on bugs and problem running it as there is too many in current state. But let me know if you were able to run it though.
Updates
12/12/2011 - version alpha1, should support A80 now. Thanks to a1Pha for the test!
Thanks,
LeTama
* reserved *
for the buzz
http://www.jbmm.fr/?p=24451
Archos 70?
If this can be done on an Archos 101, could it be done on an Archos 70 as well? [The 8GB version without the hard drive.] My old Archos 70 needs a new lease of life!
pstjmack said:
If this can be done on an Archos 101, could it be done on an Archos 70 as well? [The 8GB version without the hard drive.] My old Archos 70 needs a new lease of life!
Click to expand...
Click to collapse
This a 101 G9, not G8... I believe it could be done on G8, even though ram will probably an issue. I'll try probably someday.
Build released, see first post.
how use the 2 anothers files ?
Hi Cajl,
The zImage and initramfs.cpio.gz ? These are the one that must be flashed through sde. I added the instructions in first post, this is the same thing as previous rooted firmware.
As it is, the initrd is not compatible with previous rooted firmware, you'll loose the possibility to run it after flashing ice kernel+initrd. You can reflash it again afterwards though.
Alpha 1 released, touchscreen should now work for 80 G9. Let me know if it doesn't work for you, there is two touchscreen drivers and only one is confirmed to work.
Market Working
Good news, after digging with it and deleting all Archos's craps. I finally make Market to work + Wifi, so this will be a great news now.
First google and download Market_v3.4.4.apk
then adb push Market_v3.4.4.apk /system/app
then adb shell
#cd /system/app
#rm Phonesky.apk
#cp Market_v3.4.4.apk Phonesky.apk
#rm Market_v3.4.4.apk
#chmod 777 Phonesky.apk
there we go!
letama said:
This a 101 G9, not G8... I believe it could be done on G8, even though ram will probably an issue. I'll try probably someday.
Click to expand...
Click to collapse
Please try for A70 when you have time as there is a large audience of us.
wozhere said:
Please try for A70 when you have time as there is a large audience of us.
Click to expand...
Click to collapse
I did this weekend, results are not very good so far... It's quite slow, few seconds to go from apps to widgets for instance. I didn't play much with it, touchscreen driver need more work and I couldn't make it work properly yet.
We'll see. Much work needed and slowness could come for a hidden problem somewhere, but I couldn't see anything obvious.
letama said:
I did this weekend, results are not very good so far... It's quite slow, few seconds to go from apps to widgets for instance. I didn't play much with it, touchscreen driver need more work and I couldn't make it work properly yet.
We'll see. Much work needed and slowness could come for a hidden problem somewhere, but I couldn't see anything obvious.
Click to expand...
Click to collapse
Sounds a challenge, thanks for working on it whenever you have spare time and keep us posted from time to time. If pulled off, even in a limited version, it will be a great coup.
+1+1+1+1+1+1+1
Yeah... everyones leaching for ICS these days
The limited RAM on Gen8 will be definitely a blocker...
On the other hand people even made efforts to run ICS on the good old Dream device. But this of course is a technical challenge, it's far from daily use.
Anyway i like reading your threads, letama...
Regards,
scholbert
Just saw this, ICS on the old HTC G1 (528MHz CPU & 256MB of RAM):
http://forum.xda-developers.com/showthread.php?p=19648827
Works so far on my G9 80, no problems with the touchscreen driver. Good work
you are the man, keep on the good work
link is down
i want to help with developing (I have a AOSP ICS rom for the play so i know how ics works)
I re-uploaded on uploading.com, first post updated.