yashsingh1/xdaforums huggingface dataset:
[HTC Incredible S] haris182:
Make it available on February 29...

So I got both Windows 8 beta CP and ICS Sense \:D/
[HTC Incredible S] santhoshpirate:
i too feel the same!!

@nik! great work broo!! way to go!
[HTC Incredible S] nikhil007mmus:
I feel the 4.0.3 version will b ready in a week or so no eta probably if everything is good il release it off :)
[HTC Incredible S] kuroro:
Nik you rock
[HTC Incredible S] djroobs:
yeah...at last.....thnx a lot nikhil brother.:)

it's been 24 days ..after a real hard work it's done.
[HTC Incredible S] cooljais:
Nice work nik. Good devs like you will never let the IncS go down without a fight.

Cheers!
[HTC Incredible S] saneksem:
I can help with UV levels here too

and with testing)

if you need,contact me)
[HTC Incredible S] ajeya:
well done bro...great job :)
[HTC Incredible S] jiangchao87:
cooooooooool~~
[HTC Incredible S] kent_lkc:
Looks very promising bro.
[HTC Incredible S] crunchyHTC:
Awesome work nik, keep it up!
[HTC Incredible S] way2shree:
Awesome bro!! It's looking great !! Thanks for all your hard work and for these amazing ROMS !!

You rock !!

Swyped from my HTC Incredible S using xda premium
[HTC Incredible S] zawthetnaing:
waiting waiting :D

be patient :P
[HTC Incredible S] kensheen:
nice!!! eagerly waiting
[HTC Incredible S] NoteGarner2020:
Great work man congratulations.
[HTC Incredible S] smallesmets:
Super nice!!!!

Looking forward to it!

Keep up the good work man thx!
[HTC Incredible S] Cookie Ninja:
Awesome! Looking forward to this. Anyway in which I can help? Pls do let me know....

Sent from my HTC Incredible S
[HTC Incredible S] AmareKa:
Awesome bro!!:eek:
[HTC Incredible S] TheCrow1372:
GEEZZ buddy, the race is on and your in the lead plus nice work!
[HTC Incredible S] Psyloid:
Awesome news ! Have it ready when my incs gets back from repair ;)
[HTC Incredible S] nikhil007mmus:
I guess 4.0.3 will be later .. But i guess i have got the permission to post this one :) I will just be working on some fixes with the ramdisk and some more things , I hope all the incs related devs contribute to the fixing of rest of the parts of the rom .. Release in 2 days on Tuesday :)
[HTC Incredible S] shiningarmor:
nik, i suggest u dont give etas yet. after 2 days people if something goes wrong that delays the release, people will start spamming asking where's the rom..

even if you do release in 2 days time, u'll be in such a rush that there's bound to be something wrong..

i think u should make sure basic functions such as calls, data, wifi, bt, etc works fine first before releasing .. :D
[HTC Incredible S] nikhil007mmus:
@shiningarmor Thanks for telling me about that . In these two days i will be trying and fixing things whatever i possibly can but the thing is there are some other devs who are willing to work on this version of the rom and probably the things i am not able to fix they might be able to fix .. There are so many good devs in the incs section i will be waiting for some contributions from their side .. what i feel is for now when i release the rom , i will mention what works and what doesn't ...

But i feel everyone wants to feel the ics sense on their phones .. so the first release will be an alpha for devs and for other users just a feel of ICS SENSE on their incredible s .. Dont wanna spoil the excitement for everyone :)
[HTC Incredible S] Litestar:
only two days,i wili keep waiting for the great rom:)
[HTC Incredible S] Juventus1897:
This rom is looking champion, can't wait for it.
[HTC Incredible S] qarclub:
What kernel do you use?
[HTC Incredible S] nitsuj17:
again awesome job man...eagerly awaiting kernel source so we can get ics sense booting on the vivow as well!

super work
[HTC Incredible S] Blaaargh:
Oh momma....give it to me! :D
[HTC Incredible S] Abdullah Dot:
+1 good idea
[HTC Incredible S] clandes:
That's very good news. Been waiting for this. Got my Sensation running on ICS and just loving it. Guess we'll also need super cid and firmware update for the IS?
[HTC Incredible S] slym84:
Eagerly waiting.....
[HTC Incredible S] vido.ardes:
Just to try and steer this back to a dev topic a bit, will you also be giving people access to the kernel source? Just in case some of the issues are kernel related. Aklso setting up a bug tracker for people you want to give access to might help, that way we can get a concise bug list for fixing without it being spammed with the same issues over and over.
[HTC Incredible S] nikhil007mmus:
@l0st.prophet bro there is no kernel source available right now .. this rom is based on the aosp kernel from virtuous quattro .. We will setup a bug tracker soon .. for now i got the sound working on the rom .. il release it tmr ..trying to fix some more bugs
[HTC Incredible S] vido.ardes:
Cool, thanks for the update. At least we know most of the issues are in the ROM rather than the kernel, which narrows it down a little. Good news you got the sound working!
[HTC Incredible S] buller22:
I look highly forward to the a release of the alpha version
[HTC Incredible S] gunswordx:
can't wait to try out sens +ics!!!
[HTC Incredible S] xerosoft:
which rom you using? rc4 virtous? where to download
[HTC Incredible S] TheCrow1372:
I (think) RC3 cuz thats what I'm using (4 now) ;) and its all flawless accept for camera works 98% but no camera so I think Nik will get all the proper gears working.:D
[HTC Incredible S] khaidir84:
any update??? cant wait..
[HTC Incredible S] Cookie Ninja:
Check this thread for updates:

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

Sent from my HTC Incredible S
[HTC Incredible S] nikhil007mmus:
Virtuous got wifi working ..wonder if they will gimme the fix :) but im happy wifi will b available to us :) anything for the community ..

http://www.virtuousrom.com/2012/03/working-on-affinity-ics.html
[HTC Incredible S] shiningarmor:
@nik

if u havent noticed yet

http://xdaforums.com/showthread.php?t=1543572
[HTC Incredible S] nikhil007mmus:
was downloading it but the downloads are failing will try again tmr
[HTC Incredible S] shiningarmor:
yeah the download server is being hit really hard now.

currently has 450 parallel downloads lol

let me find a mirror link for u
[HTC Incredible S] Cookie Ninja:
There is a 4shared mirror. Try it....

http://www.4shared.com/rar/-jwLktjG/RUU_Ville_U_HTC_Europe_1094011.html

Sent from my HTC Incredible S
[HTC Incredible S] nikhil007mmus:
Yup download from dropbox wrking noww :)
[HTC Incredible S] Abdullah Dot:
at last we gotta leak

i hope now we get ICS sense 4.0
[Xperia Play Q&A, Help & Troubleshooting] pelly_jelly:
hi guys.

I know it's a funny question, but i really be happy if it can be done. I played translated seiken densetsu 3 on snesoid cause it worked there (even if i had flashing screen at avery conversation bubble), now i found out with latest update of snes9x (which was my favourite to begin with) seiken densetsu 3 works PERFECTLY.

But yeah, don't wanna start over again. So, again, is it possible to transfer my save state or save point (you know, the save feature existing in "battery" inside every cartridge-stuff) to snes9x from snesoid?
[Xperia Play Q&A, Help & Troubleshooting] fma965:
could you load that save then save it as a emulator .sav file then use that on the other emulator

----------------------------------------

Fma965 - ForgottenCoders

http://forgottencoders.co.uk[/B]
[Xperia Play Q&A, Help & Troubleshooting] Mael5trom:
Yea you can, only the battery save though, not save states. You just change the .sav from snesoid to a .srm that snes9x uses, its been a while since i did it but i think they are the correct extensions.
[Xperia Play Q&A, Help & Troubleshooting] pelly_jelly:
thanks to both, you're the best ;)

didn't actually believed someone would give 2 shts and answer :D

God saves online communities :D:D
[Xperia Play Q&A, Help & Troubleshooting] fma965:
so did it work?

-------------------------------------------

Fma965 - ForgottenCoders

http://forgottencoders.co.uk
[Xperia Play Q&A, Help & Troubleshooting] Mael5trom:
it works, i did it myself, they are basically the same core emulator, yongzh just changes the save file output for some reason.

you can also use save files off many pc emulators and put them on the play if you wish. They might not all work but some will.
[Xperia Play Q&A, Help & Troubleshooting] wolframio74:
ups, delete me pls...
[Atrix 4G Q&A, Help & Troubleshooting] elfiloso:
well tell them that after so much screaming in my room solution for not having the death of my Atrix trying and trying to achieve sarbarlo of the error that I did it "SVF: 105:1:2" clear case of the same mistake that I had: good point we were :::::::::::>

If you let down the volume down button and you get the error on and off the screen:

What I did was just turn on the normal cell and I present some options, with some numbers from 1 to 14 possibly ....

After my cable is connected to the computer normally and opened a command window in windows .....

from there run the following steps:

Remember that you must have a folder with the files: fastboot.exe, adbwinapi and also adbwinusbapi.dll Or search your folder androidsdk, tools

1: Open the command window.

2: Located in the folder where the files are.

3: Run fastboot oem unlock.

4: run fastboot oem unlock # # # # # # # number of device given by the previous command.

5: Wait for the screen says unlocked cell in the upper left.

6: After a long time if not restart remove the battery, reassemble, turn on the cell normally and wait for restart.

NOTE: This will erase everything I had in into your system android and may not work for everyone so that no bad comments beyond that is a false thanks for your attention

Excuse me for my English use google translator

And excuse me if I give false hope that they might not work at all
[Motorola Atrix 2] bubb18:
Has anyone else had touchscreen problems after the 2.3.6 (55.13.25) update?

ie: it stops registering touch after about a second of your finger being in the same place.

or is it just mine and i should get it fixed?

(i did search and didn't find a thread for this, only atrix 1, so sorry if one already exists)
[Motorola Atrix 2] throwawayaccount9500:
****...I thought it was Osmos HD. But this has been happening after the update while playing the game, really frustrating
[Motorola Atrix 2] Calundle:
I've been noticing less general reliability from the touch screen.
[Motorola Atrix 2] cowenby:
No noticeable problems here, but I'll be sure to pay attention to it now...
[Motorola Atrix 2] cogeary:
It's working fine for me.

Try installing "Touch Test" from the Android Market and see if anything weird is happening.
[Motorola Atrix 2] bubb18:
it works fine, unless you hold your finger in one spot for about a second
[Miscellaneous Android Development] sztupy:
Hi!

I haven't really found any kind of guides on how to build a complete AOSP android build from source (kernel and software) for Allwinner A10 tablets like the Ainol Novo 7 Advanced or the Teclast P76Ti.

I have a Teclast P76TI (rev4), and the following guide is only tested on such a device. As it's mostly based on the source drop of the Ainol Novo 7 Advanced, it should also work on that too.
[Miscellaneous Android Development] sztupy:
Part 2: Building the kernel

Change to the directory of the kernel. Now edit the file scripts/build_sun4i_crane.sh

Change the line "export CROSS_COMPILE=" to point to the ARM compiler. For example if you extracted the CodeSourcery files to /opt then use:

export CROSS_COMPILE=/opt/arm-2009q3/bin/arm-none-linux-gnueabi-

The default .config file is more or less the same that is supplied with your tablet. On the Teclast P76TI you can actually extract the .config file used from /proc using "adb pull /proc/config.gz" Not sure about other vendors.

Now you have to compile. Issue the command:

./build.sh -p sun4i_crane

This will build the kernel and modules inside the the "output" directory.

Next step is to compile Android
[Miscellaneous Android Development] sztupy:
Part3

Part 3: Building Android

Go to the android directory. Now setup android using:

$ source build/envsetup.sh
$ lunch

You will get simething like this:

You're building on Linux

Lunch menu... pick a combo:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
6. crane_Ainol_Novo7A-eng
7. crane_Teclast_P76TI_REV4-eng

Which would you like? [generic-eng]

Here select your device (option 6 or 7 depending on your tablet)

After you have selected it issue a make command:

$ make

This will take a while. If you're using ubuntu 11.10 make might fail, but you can fix it using these fixes: http://groups.google.com/group/android-building/browse_thread/thread/3484e7797909d014

After the building is complete you have to create the image files. Run the following command:

$ ./device/softwinner/crane-tcp76ti_r4/mkfs.sh

(substitute tcp76ti_r4 with ainovo7a if you're using the other tablet)

The image files will be ready in the directory "out/target/product/crane-tcp76ti_r4/images/" or "out/target/product/crane-ainovo7a/images/"

Copy the three files from here (root.img, recovery.img, system.img), and the "bImage" file from the "output" directory of the kernel to your Windows machine.

The next step is creating the flashable image, and flashing your build
[Miscellaneous Android Development] sztupy:
Part 4: Flashing

A: Initialize kitchen

First download my A10 flash kitchen from this site: http://android.sztupy.hu/dl/a10/a10_flash_kitchen_v1.zip

This is based on the ainol novo 7 soruce drop, but only contains the nescessary files, and has a few batch scripts to automate the process.

There is also a v2, wich also supports ICS firmwares: http://android.sztupy.hu/dl/a10/a10_flash_kitchen_v2.zip

First unzip the files to a directory. You will see a few directories and to commands here: extract_image.bat and create_image.bat

First we have to extract an official image for your tablet. Simply comply the image file to this directory, and rename it to "original.img". If done, run extract_image.bat. This command should extract your image to the _extract directory.

Next you need to extract the bootfs inside the _bootfs directory. You have multiple options on how to do this:

1. Get the bootfs from your device on-line using adb:

> cd _bootfs
> adb shell
$ cd /
$ mount -o remount,rw -t ext4 /dev/root /
$ mkdir bootfs
$ mount -t vfat /dev/block/nanda /bootfs
(Control-C: exit adb shell)
> adb pull /bootfs

2. Get the bootfs from the extracted image file using Linux:

A. Copy the RFSFAT16_BOOTFS_000000000.fex file to linux

B.

$ mkdir bootfs
$ sudo mount -o loop RFSFAT16_BOOTFS_000000000.fex bootfs
$ cp -a bootfs b2
$ sudo umount bootfs

C. Copy the contents of the b2 directory to Windows, inside the _bootfs directory of the kitchen

B: Create image

If you have initialized the kitchen, you have to copy the four files from linux (system.img, root.img, recovery.img and bImage) inside the _input directory. You will also need to rename the .img files to .fex (so they should be system.fex, root.fex, recovery.fex).

If you are done with this, then run create_image.bat. It will create an output.img file, that can be flashed to the device using LiveSuite.
[Miscellaneous Android Development] sztupy:
Additional information for developers:

1. Difference between AOSP 2.3.4 and Novo7 android 2.3.4

Download the diff file from here: http://android.sztupy.hu/dl/a10/diff_ainovo_aosp.gz

Filelist of differences: http://android.sztupy.hu/dl/a10/diff_ainovo_aosp_filelist.txt
[Miscellaneous Android Development] fonix232:
sztupy, did you figure out why eDragonEx and FSBuild have an apparently unused Lua library next to each? I was interested by it, as it might be possible that some parts of the apps are actually written in Lua (would it be possible? Lua in a native DLL?), what would help reversing it.
[Miscellaneous Android Development] sztupy:
Yeah, saw that. Also their build script used "convert" on the image.cfg, but that file wasn't in lua anyway (except for the image parts part which seems to be a lua hash).

There are also a lot of compiled files that are compiled inside the image file and which are neither the bootfs nor android or the kernel. I don't yet know what they are for, but I think they are used by LiveSuite during the flashing.
[Miscellaneous Android Development] fonix232:
I know most of the files from the flashing, they are the following:

- SYS_CONFIG is used as a command bunch for LiveSuite. It tells the app how to flash, what to flash, where, and it configures the device too (screen size, ram info, cpu info, etc)

- Boot0 and Boot1 bins are NAND bootloaders

- FED FES and FET tools are NAND flashing utilities, checksums, hardware scanner, and other tools used during flashing.

- '12345678' files are bootloaders, config files, and tools for SDMMC flashing, if there's a device with SDMMC internal instead of NAND, these are used

- Split seems to be some kind of ID string, I had no luck retrieving it's usage and meaning.

So you say, that the actual Lua parts are the image encryption parts of eDragonEx? Interesting, maybe I've missed that spot with my tool...

Might I ask if you have tried disassembling (and decompiling) unimg.exe? I had several problems with it, but that would greatly help understanding how the images are created. I've got a C# framework, with image config parser, etcetera etcetera, to be able to read and create images in a much more advanced environment (filtering user errors, having tools for everything (bootfs modding, script.bin reversal, etcetera), and creating a working image as a final result), and it only needs the image file format (and some of my work, to create a parser).

The problems with unimg were all about positive sp values, and as I'm not a big assembly programmer, I couldn't make out anything from that. Maybe you understand it a bit more :D

Illetve beszélhetünk egy kicsit magyarul is. Tabletrepublic-on írtam hogy vegyél fel MSNre és részletezem a különböző Crane SDK elemek funkcióit, működését, egyebeket, amit eddig sikerült kiderítenem az egészről.

Sajnos elég zavaros, mivel vagy négyféle csomagoló rendszer készíti a fileokat, és ezek közül csak egy működött rendesen (crane_pack.exe). Jó lenne megérteni ezt a file formátumot, hogy egy kicsit normálisabb módon hozhassam létre, különféle vacakolások nélkül.
[Miscellaneous Android Development] sztupy:
Thanks for these. Seems I was mostly right

I think lua is not really used anymore. It probably had more relevance back in the past.

No, haven't tried disassembling it yet. I was very glad that it worked, and that I could create a whole working build just from the sources. I know there are a lot of quirks, like if the extension of the file is not .fex, then it will encrypt(?) it, etc. I might try it, but currently I'm more interested in getting a working AOSP ICS on my tablet. Besides for disassembly I need to be in a special mood, which I'm not really in now :)

Már egy jó ideje nem használok MSN-t. Skype/GTalk/email viszont van. :) Ha nem használsz olyanokat, akkor azért majd felrakom.
[Miscellaneous Android Development] sztupy:
Made a diff between AOSP android 2.3.4 and the Novo 7 2.3.4 source drop. The list can be found at post 6: http://xdaforums.com/showpost.php?p=22397984&postcount=6
[Miscellaneous Android Development] FezzFest:
Nice tutorial! Do you mind if I fork your Github repo and add the device tree for the Bmorn V11 to the lunch list?
[Miscellaneous Android Development] fonix232:
Most of the things changed aren't even needed for the device - ril can be replaced with a local one (and suggested by Google to do so), just like recovery changes, in ICS we already have USB BT support enabler, so BT changes can be dropped, just like framework changes (they are for the softbuttons on the notification bar), camera and mediaplayer changes should be local too (in the device tree), so 99% of changes can be dropped.

Additions are different, some can be totally erased, and some are needed. From your github, I see that you've already began making a cleaned up, generic A10 tree, but I miss a few things - libsensor for one, stagefright, camera, and audio. The AOSP stock ALSA should work, if the proper audio config is placed in a ROM, but I have bad feelings about the missing libsensors source, and camera. Stagefright has a chance too to work, but camera definitely won't, and the used sensors aren't the common ones to be included.

Használok GTalk-ot is, ott is ugyanez a nicknevem, gmail utótaggal, szóval a szokásos :D
[Miscellaneous Android Development] sztupy:
That's what github is for :)
[Miscellaneous Android Development] sztupy:
libsensor and stagefright are still there, as I could manage them to get compiled. Not that they work though. For the libcamera it depends on CedarX, which I couldn't manage to compile, that's why I removed it (for now). Besides CedarX unfortunately not "open-source", so in theory we couldn't use it either (well... not that I actually care about licence violations).

I'm still compiling ICS. Will put back libcamera and try to get the other hardware libs to work after I managed to get ICS to boot.
[Miscellaneous Android Development] fonix232:
Please be noted that ICS requires new stagefright, camera HAL, new GPU drivers, and so on.

ICS also should have some differences in the build tree, make a new branch for sure (as an example, it requires a device.mk and device_base.mk, both being the base containers without target definition, full_[devicename].mk for the actual full target, and cm.mk for CyanogenMod, what I'd suggest you to build).

I couldn't find any of the sources, but must have overlooked something. Will check it further.
[Miscellaneous Android Development] esxgx:
hi, I'm the author of unimg(esxgx).

and your unimg is not up-to-date(the version still have bugs to lead to fail the packing process.

Here is the latest version (fix bugs but no virus alarm[compared with the former version]), and you can use it in the same way.

please update your file.

PS. yes, the unimg can unpack and pack all allwinner's firewares without diffculty, good luck.

sorry for my english.
[Miscellaneous Android Development] esxgx:
I think you should use unimg.exe.

unimg is the only tool to unpack it correctly.

you know, allwinner didn't want me to release the tool in public last year(the tool is for sc9800[the former chip]). for some commercial reason, the offical toolchain of a10 only contains pack_tool.

so I released the tool with other tools(rootcr, rootpk,etc..) in a small group.

but some person posted it on the internet. so....

I developed the analysis tools in the form of many files(unimg, rootcr, rootpk, unimg2), because I want to keep each of the packing stages simple.

you can use a "bat" file / a GUI shell to communicate with each other, and that is what I expected.

I can't smoothly speak english, so I modified several times.
[Miscellaneous Android Development] fonix232:
Thank you very much!

If I may ask, would it be possible to release the source code too?
[Miscellaneous Android Development] esxgx:
I cannot released yet, but I will release it in a proper time on github (I have been touching with allwinner company, so I have to consider many factors).
[General Questions and Answers] CurtisAndroid5:
Hello,

I decided to create a Widgetlocker theme, I have created the files (preview file, left slider and background) I saved them as the following;

Android_background_3.png

Android_slider_left.png

Android_slider_right.png

Android_preview.png

I then used Winrar make them into an ZIP Archive. I called it SimplisticGingerbread.wltheme.zip, I then dragged it into the Widgetlocker data section of my device but it isn't appearing in WidgetLocker. The themes I've downloaded from the XDA Widgetlocker theme thread appear but mine don't.

Anyone have an idea what I've done wrong?

When I get this sorted I will be posting it up for the community:-)
[General Questions and Answers] CurtisAndroid5:
Nobody know what the problem is?
[General Questions and Answers] CurtisAndroid5:
Finally sorted it out.

I renamed the files to iphone_ and Widgetlocker picked it up.
[General Questions and Answers] Rajamia:
Nobody know what the problem is?
[General Questions and Answers] Jinghis:
I've got the same problem and I had tried everything ... please help :S