yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] imilka:
yep, I still have the same problem with TS on my port too.

logcat says TS device is recognized, but I still have to use my device through on-screen pointer (touchscreen works, yes, but i can't use interface directly using my fingers)

None of the idc files I tried had worked.

I would be very grateful if you could show us the right way.
[Nexus One Android Development] tolgapaksoy:
How about you compare the SDK .idc file and the Gingerbread .idc file. You see that there is something called a "cursor" which is also set. The cursor mode is set to "navigation". I can deduct from this that the cursor is the reason the interface doesn't pick "clicks".

I've got a lot of things I would like to test, but I'm simply not able to flash anything, as I actually need my phone working.
[Nexus One Android Development] pconwell:
Working flashable zip

Here is a working, flashable zip that will work from CWM.

This is just the OPs files that are correctly signed. Other than signing the zip, this is 0% my work.

http://dl.dropbox.com/u/x19839791x/anarchron-N1_ICS-f851984-signed-2011-10-23.zip

**********************************************

EDIT: Dropbox suspended my public links. Give me a minute to upload to megalinks or some other crappy site.

EDIT2: http://www.4shared.com/file/jrQ4KLsm/anarchron-N1_ICS-f851984-signe.html
[Nexus One Android Development] davehasninjas:
Good call, I just got to work, so I wont be able to look at it till tonight, I brought the nexus with me so I can mess with the apn proxy settings but I won't be able to mess with the rild or libril.so till I can get on my laptop, thanks for the pointers though.
[Nexus One Android Development] rosarafael:
3g vodafone_ES working, i need a market.apk: (

good job, that's pretty cool.
[Nexus One Android Development] darknessrise1234:
I would think an idc from 2.3.7 would work with a little editting.
[Nexus One Android Development] tolgapaksoy:
It is the exact same file as the 2.3.5. I just checked it out.
[Nexus One Android Development] zerodi:
Is this Flashable from AmonRA also ?
[Nexus One Android Development] sirius b:
Anybody else come across this in the System Update? Nice time stamp
[Nexus One Android Development] magma9495:
Just flashed it via AmonRA and it worked perfect for me!

Mine says 12/31/1969.
[Nexus One Android Development] crackmulah:
how does this vary from ICS SDK port Flasheable zip / ALPHA 3?

what in this ROM is working and what is not working?

looking through the forum but didn't see any of this information cohesively.

sorry if i missed anyones post tho, if i did, repost for me please :)
[Nexus One Android Development] tonymontezuma:
+1 - I want to know 2, tks
[Nexus One Android Development] stefanrusek:
Works:

touch screen

wireless data

SMS

phone calls (though no audio)

proximity sensor

Don't work:

Wifi (though dr1337 has posted screen shots of this working he hasn't updated his git repository)

Audio

GPS

Hardware acceleration
[Nexus One Android Development] Unclassified:
http://dl.dropbox.com/u/19839791/anarchron-N1_ICS-f851984-signed-2011-10-23.zip

maybe someone can upload it to megaupload?

sorry, it's already done while i was posting my reply
[Nexus One Android Development] uberamd:
Here is a direct download link to the signed file (see page 6). No ad-spam or anything here, I just have a server with a decent connection and plenty of bandwidth (for now anyway). I did no work on this, just tossed it on my server.

Download: http://stevemorrissey.com/android/roms/nexusone/ICS/anarchron-N1_ICS-f851984-signed-2011-10-23.zip

For those who want to copy/paste the download:

http://stevemorrissey.com/android/roms/nexusone/ICS/anarchron-N1_ICS-f851984-signed-2011-10-23.zip
[Nexus One Android Development] sirius b:
Noooooooo! Your device predates mine by one day!!!!!
[Nexus One Android Development] zerodi:
Pants , the wifi dont work on mine , no drama its early stages anyway - keep up the good work guys !!
[Nexus One Android Development] exb0:
itching.. itching.. itching.. google just release the source already :(
[Nexus One Android Development] pendo:
where did you see that? I thought it was only the GPL stuff we had access to, and wasn't enough for a full build.
[Nexus One Android Development] Azurael:
I think it was a rhetorical request :)
[Nexus One Android Development] blunden:
The GPL parts is only the kernel and we really don't need a new kernel in most cases to run the new version. This is based on the kernel included in the 2.3.6 OTA update but with changes to init.rc. The rest is based on a modified and deodexed SDK image.
[Nexus One Android Development] sucon:
Great work!
[Nexus One Android Development] nandryshak:
I want to help with this rom. I have experience with linux and I'm an undergrad comp sci student, but i've never done something like this and i have no idea where to start. what can i do?
[Nexus One Android Development] DaXmax:
Wtf? Nexus S 4G has ICS Port fully working?

Sent from My Nexus One using CM 7.1.0.1 Nightlies #231
[Nexus One Android Development] sirius b:
Not even close, you have to use two fingers to use the touch screen, and that's so you can slide a circle to what you want to access, or activate and once you've used two fingers to slide it to your desired selection, you must use both to select the item. At least that was still the case I read last night.
[Nexus One Android Development] cred05:
Get data working :)
[Nexus One Android Development] nandryshak:
like i said, no idea where to start. i assume we'd have to configure some library or driver or such.
[Nexus One Android Development] :
Looks like a Gingerbread mashup with ICS assets.
[Nexus One Android Development] fonix232:
Could you please check if the "show touch" stuff is enabled under Settings - Development? If yes, disable, and try again!
[Nexus One Android Development] sirius b:
This was on the Nexus S and according this thread http://xdaforums.com/showthread.php?t=1313337&page=2 those issues are now gone and its considered a decent enough daily driver.
[Nexus One Android Development] fonix232:
I still can't see how could a driver resolve a clearly Android-level problem (it DETECTS touch, but needs double tapping, atleast that's what I got from your messages).
[Nexus One Android Development] pendo:
lol...my bad, for some reason I read that as a past participle rather than an imperitive.

I'm well aware of how things work at this stage with sdk "roms" and such, I just had misread illumiarias post to say that the source had been pushed out to aosp. Even after that does happen (google promises they'll release the full source, unlike honeycomb), we'll still be waiting for the proprietary binaries/blobs. Hopefully though we'll be able to cobble something together like we did with 2.3 before the N1 OTA was pushed out.

I'm sure some may have already seen this, but JBQ posted this a few days ago regarding system build requirements:
[Nexus One Android Development] sirius b:
Not double tapping, you use two fingers at the same time to select your target that you dragged the circular cursor to. Watchntjis video, you'll see what I mean. Skip to 4:45 in the video it shows him attempting to select the OK button on screen.

http://www.youtube.com/watch?v=iOcAnpnZ2Fc&feature=youtube_gdata_player
[Nexus One Android Development] fonix232:
Oh right, now I see, well, that's a driver problem then. The driver translated the coordinates with some offset, apparently :D
[Nexus One Android Development] blunden:
I did some research on that elusive lib_renderControl_enc.so that the emulator EGL-libs reference when disassembled. From what I understand it might be emulator-specific. It's purpose: "encoder for rendering control commands" (See this) The link is to the CM source as the official AOSP is no longer browsable.

This random pastebin is the only thing I've found that contradicts it. It clearly shows it being included in a build for the N1. That could just be someone messing around with some Android.mk file to add it.

Some inspiration can probably also be gotten from this rom. They have at least some HW-accel working but are using the standard gralloc lib. It could just be that they got the GN drivers leaked to them as they should work fine for the NS too.

I would mess around with this myself but after having reinstalled about 50 apps manually twice after having issues when restoring from my nandroid and not having Android detect apps installed on the sdcard I'd rather not. Hopefully someone else feels up to the task. :)
[Nexus One Android Development] dr1337:
Interesting....it could just be that the GPU in the Nexus S is the same as the Galaxy Nexus, so if someone had leaked out the drivers then it might work. Need to get in touch with their team to see how they got it to work.
[Nexus One Android Development] blunden:
Yeah, that was my theory as I know at one person who has a full dump from the GN. Just for the heck of it, I registered in their forum and did a search of all posts by made the user they credit making it "buttery smooth" to but that turned up nothing.
[Nexus One Android Development] dr1337:
Can you download the ROM and have a look at what's in /system/lib/ego?
[Nexus One Android Development] DiGi91:
are you talking about the Nexus S ICS rom? if so I have it.
[Nexus One Android Development] blunden:
I already did. Strangely there is almost nothing in there. It contains the egl.cfg file that correctly specifies it should use the POWERVR_SGX540_120 driver. There are no other lib-files in there though except a different libGLES_android.so than we have. There are no actual driver libs like there use to be and I don't find them at all actually. They have a different libEGL.so though and a few other libs that they have removed. libOpenglSystemCommon.so, libGLESv1_enc.so and libGLESv2_enc.so are all missing in their rom. They have a lib called libhwui.so that sounds interesting based on the name alone.

EDIT: I'm currently downloading a Nexus S OTA update to see what the drivers are normally called and if the setup differs.

EDIT 2: The Nexus S 2.3.6 OTA doesn't include those files either. I saw some mentions about that driver potentially being open source. Firing up my VM to run the provided scripts. Nvm, it just extracted the precompiled drivers. I guess the blogs just misunderstood.
[Nexus One Android Development] DiGi91:
I am really hoping most of you by now realize that it's not an SDK port but it's an earlier leaked build of ICS that was for testing on the Nexus S.. everywhere I look it says SDK port.. it's not, look at all the differences and compare it to the first EVER leaked ICS video that was shown on the Nexus S.. it's the same build.
[Nexus One Android Development] blunden:
I kind of got that feeling when looking at it. That would also explain the strange version references in the AndroidManifest.xml file in some of their gapps they include. It mentions ICS and version 13 but it's actually built with target platform 11 (Honeycomb) and a minimum platform of 8 (this could be changed though).

There are still things that we might learn from a built that's for an actual device though. :) Too bad it's an older build which means we can't be sure if it lacks a few libs because of something that was added or changed after that build was produced or not.

EDIT: I forgot to post this. I find it interesting that the driver files mentioned here don't exist in the latest roms.
[Nexus One Android Development] DiGi91:
Yeah it's version 13 and pretty early compared to what was shown off.. missing the "Final" ICS launcher, the analog clock (though looks better than the ICS final) is way different and a bunch of other things it's just annoying me that people are not that informed about it.. everyone thinks it's some sort of SDK Port miracle and it's not..

now that being said I still think it's pretty cool and would likely run it on my device if I could.. (I don't have a nexus one) and I doubt porting it would be very possible especially to the two devices I do own. (Incredible & Incredible 2)

Ohh also platlogo.png in framework-res.apk is really cool and check out the adb icon they had some cool ideas before they changed it and fair to say the "zombie ice cream sandwich android" looked pretty badass!

Okay.. </rant>

:D
[Nexus One Android Development] lolobabes:
Sad day for us N1 owners! Very disappointing Google!
[Nexus One Android Development] fonix232:
Shouldn't the Nexus S's EGL libs sit under /system/vendor/lib/egl? My Samsung chipset based chinese tablet has them there, and every Samsung case I saw, they were there, not in /system/lib/egl!
[Nexus One Android Development] blunden:
You are right. Thanks for noticing. It contains a bunch of new GPU-related libs, most of them indicating that they are PowerVR-specific. It also contains a new gralloc. Too bad. :(
[Nexus One Android Development] fonix232:
Ehh, right, the Galaxy Nexus' SoC is an OMAP one, with the same SGX540 PowerVR GPU!
[Nexus One Android Development] blunden:
Yes, exactly.

I can confirm that lib_renderControl_enc.so isn't needed in a retail build.
[Nexus One Android Development] DJ_Jedi:
Right, maybe with an higher clock (like on Optimus 3D) but they have an ICS driver and we (Nexus One-and-Desire's users) lack it. So, for now, just force the rendering through CPU under development settings (at least untill we get an Adreno driver or understand how to create one).
[Nexus One Android Development] blunden:
Does the allow more of the apps to run without FC? I interpreted that setting like "force apps to use hardware acceleration, even if not specified in the manifest", not like force CPU rendering. Did I misread it? :)
[Nexus One Android Development] Deathwish238:
Is there something the Nexus One lacks to be able to run ICS?
[Nexus One Android Development] :
$$$ for development.
[Nexus One Android Development] nandryshak:
not really, just the drivers for gpu acceleration. but that's only because google/qualcomm are too lazy to make them.
[Nexus One Android Development] TheYang:
Since i have no idea...

is it feasible that "the community" writes those drivers?

or would you need "inside information" of how this thing is built or something?
[Nexus One Android Development] blunden:
No, it's not feasible to write them without detailed knowledge of the chip. It's much more likely that some workaround could be written to translate any missing calls to something that will produce a similar effect. That might also be hard though, I guess mostly depending on how big changes there have been to the ABI.

If we are really lucky, it's just that some new libraries have to be built from ICS sources that link to the Gingerbread drivers. I noticed a few related libs that I've not seen before so lets hope it is as simple as that. I have very little to base that on so it might turn out to be very hard. We simply don't know yet without the source for ICS available.
[Nexus One Android Development] :
It's business, not laziness.
[Nexus One Android Development] nosaturn:
where is the git for this project?

where are you guys working from?
[Nexus One Android Development] blunden:
It's the link in the first post of this thread.

https://github.com/anarchron/N1_ICS
[Nexus One Android Development] DJ_Jedi:
I understand it like "use CPU instead GPU", i noticed a more smooth experience, but maybe it's just self suggestion :D
[Nexus One Android Development] blunden:
I just skimmed over it so I might have misread it. Did you try apps like the ICS Music app?
[Nexus One Android Development] sudseh:
And I'm jealous you even got wifi to turn on.

3G has been on and off for me. It works, then crashes after about 10minutes, and has a connect/disconnect loop.
[Nexus One Android Development] blunden:
There is still a DNS issue with the wifi.
[Nexus One Android Development] sudseh:
Would that prevent the wifi from turning on, or from fully connecting to an access point?
[Nexus One Android Development] supperbas:
Anyone knows if the WIFI will be in the git soon? or will you guys wait till the DNS issue is resolved?

Great work so far =]
[Nexus One Android Development] info[]box1:
I know what you mean about the smooth experience. I noticed the difference.

Sent from a Bugless Beast GPA19 Nexus S 4G using xda premium
[Nexus One Android Development] DJ_Jedi:
Good, i don't have my port flashed so i can't even read again that setting, but a feedback like yours is very helpful :D Thanks
[Nexus One Android Development] twistedumbrella:
Have the file, verified against ones that work, see it load during boot, no response. Any further information?
[Nexus One Android Development] DaXmax:
@ drewgaren is porting ics Sdk 14 and his say in his twitter it turned up to be better....?? SO Guys, do u think that he port there is no bugs??
[Nexus One Android Development] imilka:
Your .idc file has to be named exactly like it is named in kernel.

Look for it in logcat, it says the name of touchscreen device on boot.

For example, we on HD2 always had .idc file named synaptics-rmi-touchscreen.idc.

But in our kernels touchscreen has the name 'htcleo-touchscreen', so I had to rename .idc file to htcleo-touchscreen.idc.
[Nexus One Android Development] twistedumbrella:
Did getevent for the name, renamed to atmel-touchscreen and added the missing "dummy" kl and kcm files and that hadn't changed anything.
[Nexus One Android Development] blunden:
Getting an SDK port 100% bug free and fast is close to impossible. If he gets more features working though we won't complain. :)
[Nexus One Android Development] twistedumbrella:
It isn't hard or impossible when the sdk uses your device configuration as the test image.
[Nexus One Android Development] :
The SDK/ICS is built from a Galaxy Nexus, not an N1.
[Nexus One Android Development] blunden:
It helps sure, but there are still lots of things missing. First of all, there are no updated GPU-drivers which has happened the last few versions. Other drivers might also be incompatible. There are also lots of weird differences like hardcoded paths causing bugs that you have to dig up.

Maybe we have different views on what makes a 100% good ROM. To me that means full performance (well, no worse than the latest official version), no more bugs than those that would exist on the device if the code was compiled for that target. It also means having all Google services working as they should.

If you want to claim that the above isn't time-consuming and hard, please show me that it isn't by fixing it up. I wouldn't mind being wrong in this case. :)

Btw. the Nexus S (and devices running the same GPU) is different in this regard because a working build, though a few months older was leaked for it. That provides many of the pieces we are missing for the SDK port normally.
[Nexus One Android Development] twistedumbrella:
When I get a Nexus One, I will... Lol
[Nexus One Android Development] DaXmax:
@twistedumberella, Jcopernicus,

Yes, its not easy to port ics sdk 14 to nexus one but actually Drew made it work but it has bugs like

Bluetooth not working

Camera not working

Wifi is some sort spotty

Audio not working

He said that he will work on the kernel meanwhile he release the beta 5 for nexus s
[Nexus One Android Development] j00m:
@DaxElectro: where ICS Launcher2.apk for nexus one?

i tried replace /system/app/Launcher2.apk, but doesn't work!

which file need to copy?
[Nexus One Android Development] blunden:
I see very little written about his Nexus One port. The things he wrote make it sound very similar to this current port if you factor in the stuff that is still unreleased.

When it comes to the Nexus S port, that's totally different. The much older ICS build that was leaked for it provides working drivers for pretty much everything. Also, since it has the same GPU (though lower clocked) it should be able to use the Galaxy Nexus drivers if needed. Because of this it's much much easier to make a working ROM.

Please don't take this thread off topic. The other N1 SDK port thread has been completely derailed by unrelated posts. :(

What are you trying to do? You can't just take the apk and put it on Gingerbread and expect it to work. First of all, Gingerbread doesn't fullfill the specified API requrements so it will refuse to install. At the very least you would need to decompile it, change the minimum API level specified in AndroidManifest.xml. Most likely it won't work even if you did that though as it probably uses some parts of the new ICS API.
[Nexus One Android Development] twistedumbrella:
The new version that was a "true" sdk port was just updating the previous build. None of the 4.0.1 parts are really included. It is more or less just porting the xoom with a system dump. Is the honeycomb source out? If so, just build from that and you can fix pretty much anything for that build.
[Nexus One Android Development] blunden:
I see. Honeycomb seems to have more in common with Gingerbread when it comes to some drivers. N1 GPU drivers from Gingerbread allow hardware acceleration in the N1 Honeycomb SDK port.

What do you mean with "Is the honeycomb source out?"? Surely you must know that Honeycomb isn't open source except for the kernel (the latter because of GPL). In theory Honeycomb will be open source when the ICS source drops since it should be possible to revert all ICS-related commits with a bit of guessing, even if they never tag a certain point in the commit history as such. I don't see why you would want to though since ICS is an improvement all around.
[Nexus One Android Development] twistedumbrella:
Surely I must... Sorry I haven't been as focused as I should have. So what was the benefit of this talk anyway? I forgot, so moving on...
[Nexus One Android Development] imfloflo:
Back on topic please.

Dev of ICS SDK on N1
[Nexus One Android Development] twistedumbrella:
Who was off topic? And why did it take 4 days to respond? If you wanted to bump the topic, say bump. Go look at DrewGaren's site, he did a port for N1
[Nexus One Android Development] imfloflo:
For me, Honeycomb source aren't related to development of this N1 ICS Rom from ICS SDK.

That's all.

BTW can you link Drew's post to the rom please. I only saw NexusS roms available at this time.

Regards.

F.
[Nexus One Android Development] TheStrider:
Ice Cream Sandwich development build for the Galaxy Nexus out.

http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/

Source is Modaco.
[Nexus One Android Development] addam360:
Maybe this will help...

Was just about to post this here. Beat me to it!:D Hope it helps the devs though.
[Nexus One Android Development] alr11389:
Where are the download link for the N1 port? I only saw NS ROMs and a post related about porting to N1 and some features not working.. but nothing about download
[Nexus One Android Development] tonymontezuma:
http://drewgaren.com/DrewGaren.com/ICS/Entries/2011/10/30_OTHER_Ports_Progress_Reports.html
[Nexus One Android Development] imfloflo:
This thread is reserve for Developement progress talks

If you want to discuss about an existing port/rom use appropriate thread or general section
[Nexus One Android Development] twistedumbrella:
Well that is fine, but unless you are a developer and can say without a doubt it isn't related, you really can't say without a doubt that it was off topic, either.

The title says Nexus One and one of the "other ports" was for a Nexus One... What's your deal? The link even has the word progress in it...
[Nexus One Android Development] johnston9234:
Has anyone packaged the current rom for CWM yet? Also, has there been any progress since the initial release? Would love to see this have a nice start before the source code is released in a couple weeks
[Nexus One Android Development] lch920619x:
Hi Guys , DrewGaren just released an ICS taste for N1.

Here it is for the itchy fingers

http://drewgaren.com/DrewGaren.com/ICS/Entries/2011/11/9_ICS_SDK_NEXUS_ONE_PORT_Beta_4.html
[Nexus One Android Development] atoyu:
Mirror MULTIUPLOAD : http://t.co/0iDqCrF4
[Nexus One Android Development] lyicon:
Anyone tried this?