Develop Bugs

Incubus26Jc's Super Eclair Lite 2.1 for kaiser [RLS5]:OLD

His work has a bug: received some messages later (3days afterwards!): I think anyone should consider Aqtrans CM 5.07 (slower than warm eclair but fewer bugs) build or Warm eclair (myns).
This is the latest and fastest 2.1 release I've found that works out of the box with the Kaiser (f.e. wifi/BT/GPS/...). It's really much faster then the old polymod 2.1d most users (did) use. EDIT: now it's even faster. Mounting on windows x64 works fine (no need to install addition software).
original thread:
http://forum.xda-developers.com/showthread.php?t=670240
Recommend Wiping Data with This Release!
RLS5 Features
- Much Faster System
- Extra Apps and Widgets are Now Optional
- Fixed Full Market (Thanks Pandemic187)
- Fixed Lockscreen Not Showing Up
- Fixed Power off option on red button (Reboot option still not functioning)
- Fixed Kaiser Wifi (Tested)
- Atttempt at fixing Apn Problem
- Fixed Voice Search Crash Problem
- Added More Stable Live Wallpapers To App Pack That work without Crashing on Sleep
Optional Extra Apps
- Rogue Tools
- Live Wallpapers
- Facebook
- NavLauncher
- Dialer One App
- NFL Mobile Live
- Shazam
- Google Maps
- Skyfire 2.0
- AutoMount
Optional Widgets
- Battery Widget
- Internal\Storage Space Widgets
- Calendar Widgets
- Messaging Widgets
- Weather Flipclock Widget
- Rockon (3) Music Player Widgets
- Manup Hero Toggle Widgets
- Hero Clock Widgets
- Sticky Notes Widgets
- Audio Config Widget
- Data Toggle Widget
RLS 4 Features
- Fixed Voice Search
- Fixed Live Wallpapers
- Fixed Apps2sd, Compcache, Home app in Memory ect..
- Fixed Standard Launcher Force Close
- Added Kaiser Wifi Support
- Added Linux Sd Mount Support (Thanks Myn)
- Added New Notification Bar with New Battery
- Added Dialer1 App
- Added New Boot Animation
- Added Astro, CorpCal, Terminal Emulator
- Lots of Bug Fixes
This is incubus26jc's Super Eclair Lite 2.1 Build ported from XxKOLOHExX's Eclair based on mssmisons Eclair ver.7
Thanks to mssmison for his Vogue Parts App and Great Build
Thanks to Myn for his Great Rogue Tools App and Full Market
Thanks to XxKOLOHExX for his great build
- Nand or SD
- Its Very Fast And Stable for 2.1
RLS3 Features:
- Kaiser Wifi Support Built In (Thanks kallt_Kaffe) (Not tested:works!)
- QVGA Dialer Fixed
- Removed Some Apps For Build to Fit on Standard Eclair NBH so you can update nbh when needed
- GPS and Gmail Updates really added This Time
- Added Standard Launcher to choose if you prefer it
- Added Latest Version of NAvLauncher for Brut Support
- Added Eclair Gallery
- Removed Visualization Wallpapers and Added Others that work.
- Even Faster
Bug:
- Voice search force close (HVGA Users Enable HCT_IME Keyboard to Eliminate Problem)
Not Working:
- Camera
- Voice Search
INSTRUCTIONS:
- Flash The latest eclair nbh with resloution of choice from Dzo's Site
- If you Flashed 320x480 NBH, You will need to convert to hvga with vogue parts app. Everything will be tiny until you do
- To Change to qvga or hvga, open Vogue parts and switch to readwrite, then switch res in application options, then switch back to write, reboot
- Install to Nand or SD
- SD Card Should Mount without any mounting app.
- To enable 7 screens, open menu button and click configure
- Use Spare Parts if you want to Keep Home In Memory and change comcache size
---------------------------------------------------------------------------------------
Use this together with this kernel or NBH if you want an excellent working GPS feature:
http://forum.xda-developers.com/showthread.php?t=660158
(thanks kallt_kaffe!)
edit: New kernels from DZO should include the changes made by kallt_kaffe
---------------------------------------------------------------------------------------
Post your questions in the authors thread. This thread is just to inform you and others.
---------------------------------------------------------------------------------------
I've added a working kaiser130 config bundle (SD card): extract to andboot on your MicroSD card and add the androidinstall.tar file (from Incubus's thread or others). Start haret (win explorer mobile) and wait for instructions (press D-button when asked for).
Installing to EXT2 goes faster, but you must format the ext2 partiions each time you reïnstall android. Please wait while installing, it can take a while (you'll see lot's of errors and in the end a black screen for a few minutes).

Thanks robuser. Tried this last night but couldn't get wireless working. trying again now.
Will post how I get on.

Yup working now thanks to the zimage. WLAN still not working out of box for me though.
Installing kallt_kaffe's gps and wifi update did the trick this time though.
Next thing is to flash to NAND one a decent TomTom replacement is out there.

for sd mount..i had installed polys build..i partitioned it 1 fat 32 and 2 ext...should i reformat and do it??
also wat gps are u using?? is it tom tom..i dont have a dataplan..nor am i gonna use the phone to make fonecalls..i just want to do gps..

IS BTaudio works on that build?

OpenGl ES
With SuperEclair Lite 2.1 RLS3, OpenGL ES hw acceleration is not working
I'm using dzo's kaiser nbh of 20100408
Is the kernel missing the hardware driver ??

piotrv said:
With SuperEclair Lite 2.1 RLS3, OpenGL ES hw acceleration is not working
I'm using dzo's kaiser nbh of 20100408
Is the kernel missing the hardware driver ??
Click to expand...
Click to collapse
DZO's Kaiser NBH's are usually without the hw3d.version parameter and it defaults to 0. Eclair NBH's have this set to 1. Use the NBH that I compiled instead (see first post of this thread).

kallt_kaffe said:
DZO's Kaiser NBH's are usually without the hw3d.version parameter and it defaults to 0. Eclair NBH's have this set to 1. Use the NBH that I compiled instead (see first post of this thread).
Click to expand...
Click to collapse
In eclair, with hw3d.version 1, games or anything using hw acceleration come out as extremely distorted for me. Any idea whats causing this? thanks.

xPreSiDenT said:
In eclair, with hw3d.version 1, games or anything using hw acceleration come out as extremely distorted for me. Any idea whats causing this? thanks.
Click to expand...
Click to collapse
Are those games written for OpenGL ES 1.0 or 1.1?

kallt_kaffe said:
DZO's Kaiser NBH's are usually without the hw3d.version parameter and it defaults to 0. Eclair NBH's have this set to 1. Use the NBH that I compiled instead (see first post of this thread).
Click to expand...
Click to collapse
That's great. Working now
Thanks for all your efforts, saving our kaiser's life...

piotrv said:
Are those games written for OpenGL ES 1.0 or 1.1?
Click to expand...
Click to collapse
I have no idea.. I'll add a list of the games I tried in this post, alongwith any info I can find about them(ie opengl 1.0 or 1.1 etc).

Should Polaris use it?

I installed kallt_kaffe's GPS fix and installed Incubus26Jc's Super Eclair Lite 2.1 [RLS 3]. So far so good. Though I haven't had a moment to try out GPS, as I have no data plan and need to install iGO8. Unless someone can recommend me a better GPS application.
The only problem I noticed is that I removed the SD card and I needed to reboot in order for it to be detected. Been a while since I ran Android on NAND, so I don't know if this bug still exists.
**EDIT**
Can I install apps to SD, or do I need APPS2SD or am I screwed?

Dukenukemx said:
I installed kallt_kaffe's GPS fix and installed Incubus26Jc's Super Eclair Lite 2.1 [RLS 3]. So far so good. Though I haven't had a moment to try out GPS, as I have no data plan and need to install iGO8. Unless someone can recommend me a better GPS application.
The only problem I noticed is that I removed the SD card and I needed to reboot in order for it to be detected. Been a while since I ran Android on NAND, so I don't know if this bug still exists.
**EDIT**
Can I install apps to SD, or do I need APPS2SD or am I screwed?
Click to expand...
Click to collapse
The best way to have increased apps memory IMO is to set /data to ext2 data.img or sdcard partition. For me the first one is the most stable and fast option.

xPreSiDenT said:
The best way to have increased apps memory IMO is to set /data to ext2 data.img or sdcard partition. For me the first one is the most stable and fast option.
Click to expand...
Click to collapse
Does that mean I gotta reinstall Android again? Not that big of a deal, but I like avoiding to redo a lot of things.
Also, I installed iGO and the screen doesn't show everything. I can't get past the select language screen. Can I change the DPI in Rogue Tools to fix this, or I gotta flash with a higher resolution?

Ok well I re-flashed it with 320-480 resolution, which makes the text barely readable. I used Rogue-tools to set the DPI to 144, and things look better, but I'd hate to see how this looks on a sunny day.
I set the data to SD card, and I'm hoping that's all I gotta do.

Dukenukemx said:
Ok well I re-flashed it with 320-480 resolution, which makes the text barely readable. I used Rogue-tools to set the DPI to 144, and things look better, but I'd hate to see how this looks on a sunny day.
I set the data to SD card, and I'm hoping that's all I gotta do.
Click to expand...
Click to collapse
To use the option of data on sd card partition, you need to have at least three partitions on your sdcard. The first should be Fat32, the second and third should be ext2. The third ext2 is used by data on sdcard. A more simpler way is to set data to ext2 data.img, in which case all you need is a single fat32 partition, and the data.img is placed in the andboot folder. For resolution, many people find 320x428 @ 144 to be the best combination.

xPreSiDenT said:
To use the option of data on sd card partition, you need to have at least three partitions on your sdcard. The first should be Fat32, the second and third should be ext2. The third ext2 is used by data on sdcard. A more simpler way is to set data to ext2 data.img, in which case all you need is a single fat32 partition, and the data.img is placed in the andboot folder. For resolution, many people find 320x428 @ 144 to be the best combination.
Click to expand...
Click to collapse
At 320X480 I set the DPI @ 181 and everything looks much better. I started up iGO and could select the correct options. Though iGO either frooze or was waiting for GPS signal, as I had control over my phone but not iGO. I probably need GPSTest running first before I start iGO.
I thought that ext2 on SD card need me to partition the SD card? I'm changing to that option now since it's the easiest. I have a 2 GB card with Android installation and a 8 GB for everyday use. This won't be a problem with ext2 on SD card data.img, would it?
**EDIT**
I set data to ext2 data.img, and it won't boot. I stop at the Android text and nothing happens for over 5 minutes. Tried deleting the data.img on the SD card and still nothing.

Dukenukemx said:
At 320X480 I set the DPI @ 181 and everything looks much better. I started up iGO and could select the correct options. Though iGO either frooze or was waiting for GPS signal, as I had control over my phone but not iGO. I probably need GPSTest running first before I start iGO.
I thought that ext2 on SD card need me to partition the SD card? I'm changing to that option now since it's the easiest. I have a 2 GB card with Android installation and a 8 GB for everyday use. This won't be a problem with ext2 on SD card data.img, would it?
Click to expand...
Click to collapse
Once youre using your sdcard for data or system, you cant remove it while the phone is on or your android will crash. So if you use the 2gb card for installation you cant install onto the 8gb card, unless you first install android, and then through the installer menu set data to ext2 data.img after changing cards. Or you could just simply add the androidinstall.tar to your 8gbs andboot folder. Thats how I do it, I keep the install file in the andboot folder for 'situations'. Whatever works for you though, just keep in mind the limitation.

xPreSiDenT said:
Once youre using your sdcard for data or system, you cant remove it while the phone is on or your android will crash. So if you use the 2gb card for installation you cant install onto the 8gb card, unless you first install android, and then through the installer menu set data to ext2 data.img after changing cards. Or you could just simply add the androidinstall.tar to your 8gbs andboot folder. Thats how I do it, I keep the install file in the andboot folder for 'situations'. Whatever works for you though, just keep in mind the limitation.
Click to expand...
Click to collapse
That did the trick, thanks.

Help..cant get anything to flash

Hi I am using hardspl 3.34
I decided to put android on my kaiser as I love it on my desire..
I flashed the latest android kernel from kallt_kaffe, when booted error messages came up about not being able to mount various locations..and a final one "unable to open persistent property directory"
I tried pressing the D pad to load an Android nbh from and boot and nothing.
I have since tried to reflash both winmo and android kernel images from the sd card and through USB but nothing flashes.
If I try with the sd card, naming the image KAISimg.nbh all I get is a white screen with loading on it..nothing more.
when I try via usb it gets as far as trying to flash the rom, then comes up with a communication errror.
anyone any ideas what has happened and how to fix it.
Regards
Robbie

You've downloaded and flashed the kernel (which allows you to run Android), but have you downloaded an Android build yet?
It sounds like you're missing the androidinstall.tar file in the andboot folder of your SD card.
Find a build in this forum, download the build (should be about 80/90mb or so when zipped) and then place the file in /andboot/
If you've already done this, apologies if that was patronising in any way!
The Kaiser is somewhat picky when it comes to SD cards, it may not read KAISIMG.nbh even if everything is fine. My 1GB Kingston card, for example, is useless when it comes to flashing this way, I had to buy a new 4GB card so I could sort out a rather useless Android build.

Thanks NatAvery
I have the andboot folder with the tar file in, but as I get errors from the android kernel i think that is why it doesn't read it.
My main concern is my inability to flash anything..I have tried a different sd card as you suggested and I still have the same problem, it comes up as loading the KAISimg.nbh but goes no further.
Robbie

Hi Vampires,
Did your issue resolve?.........since even i have a similar issue. I flashed HardSPL first & then flashed a rom from then whenever i switch on the phone it comes to this screen as if loading and is stuck with the error you mentioned ' unable to open persistent property directory'
And this happen to me just like it happen to me .......in the pursuit of having android on the phone.
I'm not able to flash any other rom's just stuck on this screen.

I have the same problem. I also use hardspl 3.34
I flashed the kernel installed the built, bu i didn´t pick the right display setting..
everytime I try to reflash it only says loading.. (left it for about 2 hours)
any ideas?

still looking for a solution, please anyone with usefull info help ..

i had similar problems before, my system is:
HTC tytn ii (kaiser 130)
Hard SPL 3.34, radio 1.70.19.09
DZO's kernel and froyo 15-07 (latest thas it), NAND flashed
4gb SD card
(109mb internal phone memory after 1st boot)
Haret Install (SD card, run side by side with WinMo)
- dload kallt_kaffe froyo, extract and put andboot in SD card, root, not subfolder
- rename default-kaiser.txt into default.txt
- edit default.txt change panel-type into 2 (panel 1 got some issue with res)
- run haret.exe
- don't press d-pad (center) just yet, wait until message 'press d-pad/volume to ..' then immediately press and hold d-pad until you're in install menu.
- select install, ok
- next, select fix permission (optional, but it fix some prob)
- select quit
- let it boot, no need to press d-pad anymore.
- you may get "unable to open persistent property directory", but no worries, restart phone, run haret again, if still the same, reinstall, sometimes twice install should fix it. (don't ask me why)
NAND flash
- dload DZO's kernel and OS build file.
- use Loser's NBH editor to change panel type to 2, and keyboard type. it will then save as KAISIMG.nbh
- put KAISIMG.nbh into SD card, root.
- make folder andboot inside SD card at root, and copy dzo's android build, rename it to androidinstall.tgz (tar/tgz)
- press and hold power btn + camera btn, reset with stylus
- press power again to flash kernel, then reset after complete
- now it will try to boot android, immediately press d-pad when you see 'press d-pad/volume..' and install (sys on NAND, data on NAND), next step same as haret above.
- you're now officially android.
note: additionally you can also try 'sys on NAND' + 'data on SD Card', --> use this EXT2 partitionto partition your sd card
side note:>
zImage = is the haret version of the KAISIMG.nbh file, it's the kernel.
androidinstall.tar/tgz = the android OS files
hope this helps.
Attn: if you're experiencing battery stucked at 15% or something, go into boot menu (d-pad), backup data, flash winmo rom, charge to 100%, then reflash+reinstall android, restore data. that should fix it.

[Q] android install..please help!!..ive read guides

hey guys, im sure this is getting old for some..but yes im a newbie, 8925 user. ive read the android install on htc by l1q1d, which i thought brought me in the correct position.. (not to say it wasnt a good guide, im sure it is..im a noob) i was wrong heres what im using and trying to accomplish, i sarted out reading "How to replace Windows Mobile with Android (Guide)" the first thread, i used jump spl 1.93 , flashed hard spl 3.56, flashed radio 1.71.09.01, then i used the htc on droid guide on atools to configure my kernal (which i loaded while in atools, i tried both 2.6.52 and 2.6.32-which is the current one im using )saved the KAISIMG.NBH in the root of my sd card(2GB HP i think its class 4) then set up my androidinstall.tgz(Incubus26Jc's Super FroYo RLS16 All Languages) in the atools mixer with the unique module update in atools V1.0.4 and extracted them together. saved the androidinstall.tgz in the /storagecard/andboot. then used BSE boot script editor, to setup my install-seq.sh which i also saved to the /andboot folder.
Heres my current specs again in line:
jump spl 1.93
hardspl 3.56
radio 1.71.09.01
kernal 2.6.32
Build Incubus26Jc's Super FroYo RLS16 All Languages with atools module update extracted together
when installing , the farthest point i reached was a succesful install of kernal, then reboot, install-seq.sh started---end result "could not determine file system size", failed, failed to format.
im currently trying to use nand for system and sd card for data , not sure what SWAP means?...
as for the seetings for fstab on atools ( which was the most confusing for me), i p
SYSTEM- NAND p2
DATA- sd partition p2
SWAP- sd partition p3
ive also tried system as nand p2, and data as nand p3 and swap at auto, cause i figured im having issues with my sd card , but then it said something about "install update module for kernal". im stumped any information you can helkp with would be greatly appreciated, here a few links to pics of the settings i made in atools, thanks alot

Hmmm, I have just tried that myself and I think it might be a bug in atools - I was changing nand partition sizes and the only combination I could get to work was Atools 1.0.4 with all fstab setting set to auto (I haven't tried Atools 1.0.5 yet, but 1.1.0 didn't work for any combination of settings for me)
Also I've never used the install-seq.sh so I can't help with that.
As a "good" starting point try using Atools 1.0.4 , latest kernel, don't change system/data partition sizes and leave all fstab settings on auto.
Flash that nbh then install through the boot menu (hold D-pad centre on boot)
If that works, then it will be easier to work from there to find out what exactly was causing the problem

huh, yup im learning as i go lol , i have tried to boot without using the install-seq file but have not tried to install with fstab on auto. what does that mean though, if its placed on auto is it going to just pick whatever i feel like at the moment , im assuming system will be on nand , but what about data. and also ive tried looking it up but what does SWAP mean? thanks alot im gonna try what u said
EDIT: ok i tried that out i got into the manual install by pressing the dpad center button, then i picked system and data to be installed on nand , then installed, then quit, then it, loaded for a while then it went to a droid screen and a animated green ball that seemed to be loading but just stayed there and did nothing. so i turned off the phone.... could it be because i didnt press 4. install update(do i even need to)? OR should i have installed system on nand then data on sd partition?

try again, and leave it a bit longer, the first boot of an un-odexed build can take aver long time, maybe about 10 minutes
swap is extra space for RAM, but on the NAND memory or SD card - like a swap partition on linux or a pagefile on windows. By default there is no swap partition used.
option 4: "install update" extracts the contents of an androidupdate.tar or .tgz file in the andboot folder, if you haven't got an androidupdate file you're trying to use then you don't need to use this option

allright ill try it now thanks man

i tried it again, but this time i used thoughtlesskyles not so super froyo rls18 and i waited , and it finally came up its installed ive checked a few things, calling works, wifi ,navigation maps some cool stuff. im gonna use this for a while then try my luck on some other endeavors. thanks again

[BUILD] [GingerBread] CM7 from Neopeek!! **Dev Preview** ClockworkMod!

Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!

****Not Working****​
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.

Dev Content​
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.

This is amazing work. Props to all involved.

Does anyone have any feedback on this build?

arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?

PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks

Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .

vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe

I wonder if CDMA data is working with this...that is my biggest issue with GB right now...

HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?

i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?

Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!

Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.

Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.

Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?

(...solved...)

it's necessary create a swap partition?
What works in this build?

fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .

Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert

Cyanogen Mod Beta 1 (30-11-2011)

CYANOGEN MOD BETA 1 FEATURES
Phone
WiFi
GPS (first time slow, next time very fast)
Data connections (GPRS)
Sensors (all)
2D/3D
MP4/3GP movie play (camera hardware button doesn't work yet)
Camera in photo (up to 5MP) and movie recording mode (we are working on new driver)
Bluetooth
ADB/UMS
Autobrightness
it's already rooted
Note1: There is a new parameter to startup.txt (vmalloc=256M), so if You are installing it manually also read README.
Note2: To change clock color go to SpicaGen Mod settings in settings menu.
FROYO BETA 3 FEATURES
-Phone
-WiFi
-GPS (because of another way of loading phone is a bit slower now)
-Data connections (GPRS)
-Sensors (all)
-2D/3D
-MP4/3GP movie play (camera hardware button doesn't work yet)
-Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
-Bluetooth
-ADB/UMS
-Autobrightness
-It's already rooted
Note1: There is a bug when calling via BT or speaker, when screen goes off, only way to turn it on is finish call.
FROYO BETA 2 FEATURES
- Android 2.2 Froyo compiled from sources with some O2 optimizatios
- Phone
- WiFi
- GPS
- Data connections (GPRS)
- Sensors (all)
- 2D/3D
- MP4/3GP movie play (camera hardware button doesn't work yet)
- Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
- ADB/UMS
- it's already rooted
LATEST NEWS & DEVELOPMENT
30.11.2011: CyanogenMod beta 1, update 1. Headset detection (3,5mm jack) update + today's kernel update (incomming call screen appearing fix) in one package. Download here.
30.11.2011: Kernel update. Kernel update contains incomming call screen appearing fix. Now it's instant. Download here.
28.11.2011: CyanogenMod beta 1. Introducing CM beta 1 (based on SpicagenMod 4 from voku). It's very fast, has IMEI working on beta2 phone image, has JIT enabled, I/O speed is increased. For both Americas there is an update script in case of phone not working.
16.11.2011: Froyo beta3, update 1 fix. Update contains kernel which fixes App2SD problem. Download here.
07.11.2011: Froyo beta3, update 1. Update contains following: sensors lib fixes, charging battery fixes, compass calibration caused discharging even when connected to usb, memory bug fix, reserved memory change (GUI should be smoother now), WiFi should connect now faster. Remember to reboot after update, because modules changed. Download here.
18.10.2011: Froyo beta3. Introducing working Bluetooth, autobrightness, phone working for all (IMEI is ok now, signal is much better), boot logo, , some other fixes like: proximity bug when calling, WiFi should obtain DNS addresses and sleep well now, reserved memory for 3D is increased - it should not cause white squares - result is less memory for system, that's why additional swap partition is created and used. Download:
Automatic install package - full install package for external SD. Experimental (not tested, but should work) install for Internal Storage - before using read included README file and make backup. Automatic installer requires 1160MB of SD space.
Beta2 to beta3 update - update from official beta2 (SD card install only).
20.09.2011: Automatic installer is ready for download. Check main site. Quick howto is available inside archive. It assumes that Your My Storage wasn't touched (so it is mmcblk1p5). You have to use 2GB SD card or bigger. If You already have two partitions eg. from first beta installer (vfat and ext2/3/4), it should only format ext2/3/4 partition and install android. Otherwise it will try to shrink existing fat32 and create new one with ext4.
17.09.2011: Froyo beta2 is ready for download (please check project site for link)! It contains new kernel (2.6.32.9) and many bugs fixed (ie. You don't need call light anymore).
MANUALS & GUIDES (BETA 2)
Note1: Pink screen at boot
It's normal because of no logo compiled in. If it's too long (longer than 30s) tap the screen. If this not helps, You probably set wrong partition in startup.txt.
Note2: WiFi
- There is a bug with WiFi. If it's on and phone go sleep, after wake there is a chance it would not work again. Only fix is to reboot. We suggest to turn off WiFi before suspending phone.
- Sometimes phone cannot connect to router (it connects, but no DNS addresses). Workaround: in build.prop uncomment following entries:
Code:
#net.dns1=8.8.4.4
#net.dns2=8.8.8.8
to:
Code:
net.dns1=8.8.4.4
net.dns2=8.8.8.8
Note3: Black screen after call
There is a bug in a phone call. When call is finished, screen stays black. Workaround is to swipe through proximity sensor
Note4: Automatic installer
Requires:
- untouched My Storage with automatic installer content
- ext4.tar.gz from manual install package
- at least 2GB SD card (class 6 at least will be enough) with one FAT32 partition or with 2 partitions (FAT32 + ext2/3/4)
Note 5: Manual install
Example: if You have two partitions on SD card (first vfat, second ext4) You should set in startup.txt following: root=/dev/mmcblk0p2. Full file example for this (do not change anything other, only root device):
Code:
Set ramsize 180*1024*1024
Set mtype 1626
Set ramaddr 0x50000000
Set kernelcrc 1
Set CMDLINE "rootdelay=2 root=/dev/mmcblk0p2 init=/init console=ttySAC2,115200"
setbitp 0x7F008808 5 1
pfw 0x7f005800 4 0x3
pfw 0x7f005804 4 0x805
pfw 0x7f005808 4 0x7
pfw 0x7f00580c 4 0x0
pfw 0x7f005828 4 0x11
pfw 0x7f00582c 4 0x80
boot
Note 6: Internal Storage Installation
If You want install on My Storage (Internal Storage):
mmcblk1p5 - by default is My Storage partition (this partition is mounted by default by Android as /storage)
mmcblk1p6 - by default is hidden partition
You have to resize mmcblk1p5, then create mmcblk1p7 (this will be root device in startup.txt) and format it with ext4.

Just a question: install android needs a hardreset my current WM settings?
I asked that because I have a lot of configurations at now (SPB Mobile Shell, Pocket Breeze, Pocket Weather etc.) and I really don't want to lose them or need to do all again.
Thanks.

hiroshi.rio said:
Just a question: install android needs a hardreset my current WM settings?
I asked that because I have a lot of configurations at now (SPB Mobile Shell, Pocket Breeze, Pocket Weather etc.) and I really don't want to lose them or need to do all again.
Thanks.
Click to expand...
Click to collapse
no need to hard reset,android has nothinf to do with wm except running haret ,Theoretically

no need to hard reset,android has nothinf to do with wm except running haret ,Theoretically
Click to expand...
Click to collapse
Thanks for your answer.
I'm a little affraid because I read here (http://forum.xda-developers.com/showthread.php?t=1066313) that I need to create a partition at 'My Storage'. So I think this operation will automatically hardreset my device.

the installation is the same as the beta 1??

Is the Zimage missing???

not anymore. zimage is up.

i m sorry. Where can find the updates? 2011-09-17

no link
There is no link.
Where can we find the package?

Modaco thread.
http://www.modaco.com/topic/346446-froyo-beta-2-for-omnia-2/
Project Download Page
http://o2droid.phj.hu/index_en.php

lalinde89 said:
the installation is the same as the beta 1??
Click to expand...
Click to collapse
Currently you'll have to do it manually, with Ubuntu.

damn. when i tried to partition the 2GB My Storage into 1000mb FAT32 and remaining 959mb ext4 (in ubuntu), i got an error when applying in gparted.
And now, all 2GB appears unallocated, and ubuntu cant mount anything. So im stuck. Tried creating a partition under Disk Utility, but it just hangs and doesn't do anything. At the same time, using windows 7, im stuck with 1000mb of FAT32 and 959mb that appears unallocated. Cant do anything to extend or delete the partitions (using disk management). All options are greyed out.
So now winmo can only effectively recognise 1GB of My storage. I effectively reduced my storage in half.
Anyone know what to do?

l3ong91 said:
Currently you'll have to do it manually, with Ubuntu.
Click to expand...
Click to collapse
I have extracted the ext4.tar to my ext4 partition on omnia 2 (i8000 8gb) as i always do.
Copied the startup and zimage to my root and changed the startup to reflect my partition. This works perfectly for beta 1
But all i got with beta 2 was a pink screen, so i waited for 10 minutes and nothing...
So i downloaded the debug zimage to see what's going on.
I can see it's "jumping to kernel" and then a cursor is blinking for a few seconds and then the screen goes all black.
Any idea what's going wrong?

exactly the same problem than fran_nic....
i'll tell you if i find a solution....

vpnair said:
damn. when i tried to partition the 2GB My Storage into 1000mb FAT32 and remaining 959mb ext4 (in ubuntu), i got an error when applying in gparted.
And now, all 2GB appears unallocated, and ubuntu cant mount anything. So im stuck. Tried creating a partition under Disk Utility, but it just hangs and doesn't do anything. At the same time, using windows 7, im stuck with 1000mb of FAT32 and 959mb that appears unallocated. Cant do anything to extend or delete the partitions (using disk management). All options are greyed out.
So now winmo can only effectively recognise 1GB of My storage. I effectively reduced my storage in half.
Anyone know what to do?
Click to expand...
Click to collapse
If gparted is not working for you, then try to re-format or delete all the existing partition on your My Storage using Minitool PArtition Wizard (Do it on Windows instead of Ubuntu).
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
fran_nic said:
I have extracted the ext4.tar to my ext4 partition on omnia 2 (i8000 8gb) as i always do.
Copied the startup and zimage to my root and changed the startup to reflect my partition. This works perfectly for beta 1
But all i got with beta 2 was a pink screen, so i waited for 10 minutes and nothing...
So i downloaded the debug zimage to see what's going on.
I can see it's "jumping to kernel" and then a cursor is blinking for a few seconds and then the screen goes all black.
Any idea what's going wrong?
Click to expand...
Click to collapse
Did you do the extracting in Ubuntu? And did you set the destination to the correct partition?
First boot it will took some times for the pink screen to disappear, for me it's around 1-2 minutes, before the shiny Android logo pops out.

ok i have found a solution.
re-format sd card with g-parted under ubuntu.
-unmount device
- completly erased partitions.
- create new partition in fat32 in primary mode 7go
- create new parttion in ext4 in extended mode 1go
- extract . tar files in ext partition.
my first install was a 2go ext4 parttion , it seems to be the pb, i've read somewhere that if ext 4 partitions are more than 1.5 go = troubles.
hope i have help you....

l3ong91 said:
If gparted is now working for you, then try to re-format or delete all the existing partition on your My Storage using Minitool PArtition Wizard (Do it on Windows instead of Ubuntu).
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
Did you do the extracting in Ubuntu? And did you set the destination to the correct partition?
First boot it will took some times for the pink screen to disappear, for me it's around 1-2 minutes, before the shiny Android logo pops out.
Click to expand...
Click to collapse
Yes i did the extracting in ubuntu. I checked my previous startup to be sure i had the correct partition cause it always worked.

fran_nic said:
Yes i did the extracting in ubuntu. I checked my previous startup to be sure i had the correct partition cause it always worked.
Click to expand...
Click to collapse
Then make sure you set to the correct partition in the startup.txt, coz for this 2nd version of beta is different from the froyo beta 1.
For your reference:
mmcblk(X)p(Y)
For (X): Root of partition
mmcblk0: SD Card (If you want to extract the ext4.tar.gz to SD Card)
mmcblk1: My Storage (If you want to extract the ext4.tar.gz to My Storage)
For (Y): Specific partition number
You need to find out what is the partition number of the newly created partition.
ie. if it's 2, then it will be mmcblk(X)p2
In this beta, it's normally p5,p6 or p7.
Hope this helps you understand better and good luck.

Thanks for your advise l3ong91.
Problem was... windows would see My Storage while ubuntu would not. Minitool was able to resize my partition so i could use all of it. BUT still ubuntu would not recognise. After a lot of work, i found the problem was in my micro usb cable. It was faulty. So i replaced that and voila! ubuntu mounted My Storage. I was then able to create the partitions. Unpack the ext4, set startup.txt to My Storage (mine was mmcblk1p2 after following youtubeguide by JerryTech11).... Then had to redownload zImage (as i download my version early on and it was 2.2mb while the current link is to 2.4mb). And android is now running! Hoping battery lasts a day with moderate use. If so my omnia 2 is once again my favourite device.

l3ong91 said:
Then make sure you set to the correct partition in the startup.txt, coz for this 2nd version of beta is different from the froyo beta 1.
For your reference:
mmcblk(X)p(Y)
For (X): Root of partition
mmcblk0: SD Card (If you want to extract the ext4.tar.gz to SD Card)
mmcblk1: My Storage (If you want to extract the ext4.tar.gz to My Storage)
For (Y): Specific partition number
You need to find out what is the partition number of the newly created partition.
ie. if it's 2, then it will be mmcblk(X)p2
In this beta, it's normally p5,p6 or p7.
Hope this helps you understand better and good luck.
Click to expand...
Click to collapse
Thanks for your reply.In beta 1 mystorage was seen as mmcblk0.
That was my problem.
I changed it to 1 and it boots perfectly.
Thank you very much for helping me out here.