Related
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?
Hi guys, i'm back from exams with a fresh and funky release
This is the latest version of Desire Z Sense FRG83D - 1.72 (very close to stock). Basically everything is working and I have been using it for a couple of days now.
Speed should be WAY better than on Desire HD ROMs, but still not as fast as stock Desire, comes close though. Costs are some additional trash menu options, like the one for the hardware keyboard and no arrow keys on the on-screen keyboard.
Focus in this ROM is on battery life, free space in NAND and to be close to stock.
I have squashfsed some directories, which saves a lot of space. (Desire Z ROMs are a bit lighter than HD ones, because of the less capable hardware, but still space hungry). Finally got it down to use only 200 MB + (6MB free in /system, because mkyaffs2image does strange stuff), which means you will have ~230MB of storage space available for your user files (if you use the partitioning layout I supplied with the DFT flasher and depending on if you chose to use the EXTROM area/last 24 MB of NAND space in MAGLDR - if you have a TMOUS LEO you will of course have more). This is more than enough in my opinion, no need for apps2sd so far, but i may add it in the future.
You will be able to "overwrite" the squashfsed stuff in lib, framework and app, because i just used deep symlinking there.
Things i have removed (i can remember..):
Maps (it's an outdated version anyway - download a new version from Market)
eReader stuff + eBooks (takes 50 MB or so - WTF, not worth it)
Some commercial stuff
Most of the included wallpapers
All skins except Slate
Notes:
This ROM comes as ODEX-ROM, because that again saves a lot of space, which would otherwise be taken twice (once in davlik cache and once in /system/app / system/framework)
My own kernel is included, based on the latest linux_on_wince_htc git. It has the SMARTASS and INTERACTIVE governor, as well as support for CIFS and EXT4 (for those who need it)
Of course this ROM comes with RMNET enabled. My version of the libhtc_ril_wrapper allows you to choose between PPP and RMNET by file. If /system/ppp exists (create it with touch /system/ppp) then PPP will be used, otherwise RMNET. RMNET is working quite well, so i would suggest you use that.
If you want notifications working, install Led me know from market. I had battery drainage issues with it, so i removed it.
Known issues:
Currently none
Version 0.1 -> Multiupload
Important:
To all those having trouble flashing the ROM with Cotulla's flasher
Please go to Cotulla's thread and ask for help there, this is not the place for this.
Instructions taken from Cotulla:
1. download MAGLDR
2. download NAND Android ROM
3. Install MAGLDR to your LEO (ROMUpdateUtility.exe)
4. Boot LEO and select in the menu "4. USB Flasher"
5. Run DAF.exe on your computer. Do all steps.
6. Wait while it's flashing.
7. After flashing device will make auto-reset.
8. It should boot directly to Android.
9. If any errors happens, please report in Cotulla's thread, which is here.
Click to expand...
Click to collapse
Kernel sourcecode diff to linux_on_wince_htc: http://pastebin.com/FUsLfypk
So finally i want to thank some people.. Without you that all would not have been possible.
* Cotulla: for his great MAGLDR and trusting me while testing it.
* mdeejay: for supplying me with userspace stuff.
* Markinus, LeTama, Rajko and all the other great devs from #htc-linux who contributed
* Everyone else I forgot
Tell me your suggestions for improvements on this ROM in this thread please, not in PMs
If you want to buy me a beer you can do so by clicking the link in my signature. I put a lot of time in all this.
And of course buy Cotulla a beer, without him we wouldn't have come so far in that little time!
Great I will download and test it for you.........
third...... downloading. great work will test sounds good!
Testers please let me know how the call volume is on this ROM.
Thanks!
welcome back! your DHD was a big hit to me. will flash soon
Hey gauner1986, any chance of a non-squashfs'd, non-stripped build for those of us with T-Mobile US devices? Or is it possible to de-squash it ourselves?
The only thing I don't like about the Z series is the rotating homescreens. When they rotate back to port, it's like reloading all the homescreens from fresh and it takes a while. There's always a lag for the screen elements to appear. That's one reason I don't use the imilka Vision ROM and have been waiting for an updated HD.
thanks gauner.. i will download it now ..but please i need u to think to build one on glacier it is more looking and stable
Great TNX,
I will download and try it....
EDIT: would like this rom to support DATA2EXT
good work gauner. Fan of your work!
Keep it up bud.
What's about
bluetooth mac, wake up lag and streaming video (SPB TV)????
I'm currently running gauners hd rom... what would be better with this build?
Any improvement?
juergenn said:
What's about
bluetooth mac, wake up lag and streaming video (SPB TV)????
I'm currently running gauners hd rom... what would be better with this build?
Any improvement?
Click to expand...
Click to collapse
Speeds seems way better.
And I have 194Mb free Internal after first boot.
first contact : anoyng startup sound. very fast startup
I like sense but i don't like HD, it too big, so this is my best choice.
criszz said:
first contact : anoyng startup sound. very fast startup
Click to expand...
Click to collapse
Yes Gauner, get the HTC sound out please
NIce to see u back and ur great build! No support of A2sd+
Its led notification work?
Sent from my HTC HD2 using XDA App
Does this version have FM Radio? I didn't use it much in WinMobile, but I realize now that I miss it. Other than this, I will monitor the evolution of this ROM closely.
Hi Gauner, any chance of making your kernel work with an extended battery?
shree.cse said:
NIce to see u back and ur great build! No support of A2sd+
Click to expand...
Click to collapse
I know, it's 2bad, cant restore my apps with TitaniumBackup, I'm out of space....
Can't use this rom
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!!!!
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 RHOD/TOPA) 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). I think this also breaks the stock browser, I recommend using Dolphin Mini!
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.
Data - very flaky - CDMA users have data break for them after every phone call, and GSM users seem to have better luck but it's not flawless. Even seen reports of wifi having issues with data not going out to the WAN. There is a bug filed on this issue.
Anything that's broken in Froyo, is probably broken in this build. Although what is interesting, I noticed that in this build I don't have the landscape-on-boot issue that I get with Froyo...
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)
Works good so far
Been using this for about 3 hours so far. Here's a little review. Upgraded through Stinebd's link in the XDAndroid thread (same as this I guess, but the arggggh's complete package includes all files needed). I deleted the data.img and replaced my system2 file. The first boot set itself up and then rebooted to winmo. The second boot worked. I was able to download Titanium backup from the market and restore my apps that I was using in Froyo. Overall it was working well. The default keyboard is tiny on my screen. My data connection is a little finicky as it was working when I restored my apps, but I could not connect after a while (same thing happened in my Froyo build periodically). As far as speed is good and bad, sometimes it's quick, other times it's quite slow. Overall, it's pretty good considering it was just released to us. Looking forward to future builds.
Edit: I reused my calibration file from Froyo. No issues
Rhod400, 2/10 Zimage and Rootfs from GIT
mmm, I may be blind but I can't see any download link! I'd like to test it and let you know!
anyway I already want to thank you for the hard work!
The system file was posted by stinebd in this thread:
http://forum.xda-developers.com/showthread.php?t=627997&page=1226
Thanks, I've included the original link to stinebd's post in my first post.
Still working out kinks, and stine will probably want me to host it on files.xdandroid.com - sorry for the delay... It will be here soon .
so this is the neopeek build only in an image?
husam666 said:
so this is the neopeek build only in an image?
Click to expand...
Click to collapse
This has nothing to do whatsoever with neopeek. This is AOSP code, modified to work on our phones. The system image work is done entirely by stinebd, and I have made a bundle - Link up!
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
edit- nvm I reread it a 5th time and understood heh
randomblame said:
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
Click to expand...
Click to collapse
You mean the calibration issue? Some commit broke it, not sure which one. There's rumors that we can read it from the spl, then we won't need a kernel-based calibration - we'll be able to do it in userland, which is really what we want especially going forward to NAND.
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
JBS2 said:
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
Click to expand...
Click to collapse
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
arrrghhh said:
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
Click to expand...
Click to collapse
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
JBS2 said:
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
Click to expand...
Click to collapse
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
arrrghhh said:
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
Click to expand...
Click to collapse
I know, you asked which kernel I was using
Just wondering if these release has something to do with the panel issues but I realize this is a kernel related problem.
Keep up the goog work, I'll keep testing the testing kernels to see if the known problem could be fixed
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
steyn_e said:
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
Click to expand...
Click to collapse
That entry is no longer required. Put it in and see... Thanks!
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
kdub94 said:
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
Click to expand...
Click to collapse
I've already included a fix in the second post, thanks!
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.